| This will free up bandwidth There will be no problems when people call for channels all at once. Why you aks? because every channel is streamed to every box in the houses anyway.
Even if everybody calls for channels at once it will still use less bandwidth because each box will only ask for a few channels. Not all of them at once. |
|
| said by majortom1981:There will be no problems when people call for channels all at once. Why you aks? because every channel is streamed to every box in the houses anyway. Even if everybody calls for channels at once it will still use less bandwidth because each box will only ask for a few channels. Not all of them at once. That all depends on how many customers are hung off the edge router/switch. If there is a very large number(over a 1000 say), then the diversity of all those people's choices will result in a large number of channels being needed simultaneously, defeating the justification of going to a switched format. If a smaller number are off each switch, and most are watching the network(abc,cbs,nbc) and little else, this can work.
--
--
Join Red Room Forum
BLOG tkjunkmail.blogspot.com
My Web Page |
|
| reply to majortom1981
Every channel is NOT streamed to every box. A session for a specific channel is not setup unless someone requests it. If that channel is already setup and streaming, then when you tune your box to that channel you are directed to the session that is already setup...If everyone quits watching that channel, after a certain time frame that session stops. An MSO may have 300 channels available but only 50 or so are watched at any one time.
This has actually been around for years, but the technology to allow you to change channels without huge delays didn't make it really feasible. |
|
|
|
 RARPSL
join:1999-12-08
Suffern, NY | said by magnushsi:Every channel is NOT streamed to every box. A session for a specific channel is not setup unless someone requests it. If that channel is already setup and streaming, then when you tune your box to that channel you are directed to the session that is already setup...If everyone quits watching that channel, after a certain time frame that session stops. An MSO may have 300 channels available but only 50 or so are watched at any one time. This has actually been around for years, but the technology to allow you to change channels without huge delays didn't make it really feasible. If the MSOs would enter the 21st Century and send their TV Streams via IPV6, they could save lots of bandwidth. The channels would be sent as Multicasts which would mean that they are sent over the local branch as a single session and all boxes on that leg could receive it. A channel that no-one is watching would not be routed to that section of the network. What this means is that all channels are available but they flow only to those intermediate routers that have someone interested in seeing it. So long as IPV4 is used there are separate sessions for each viewer/STB since unlike IPV6 each box has ONE IPN. With IPV6, the STB (and Modem/CPU) can have multiple IPNs including ones that are Multicast IPNs which means that the box sees a session going to all the boxes tuned to that channel and just monitors it without needing a private session. |
|
 IgnitePremium,VIP
join:2004-03-18
UK
3 edits | Multicasting does work fine on IPv4 as well you know. You'd best tell the UK operators running multicast peering for IPTV distribution that they absolutely need to use IPv6.
Point is that IPv4 multicasting can be routed as well. IPv6 isn't necessary.
No need for IPv4 to give really slow channel changing times either. As IPv6 native hardware support is still relatively limited IPv4 is still a better option for some.
After all this hardware probably isn't using IPv6, and SA aren't stupid they do have a vague idea about this cable malarky. |
|
 oliphantI Have 8 BoobiesPremium
join:2004-11-26
Corona, CA | reply to RARPSL
Seems like that would be a great solution for ADSL2 video where bandwidth is limited in the last mile.
--
WAR HAS NEVER SOLVED ANYTHING, except ending slavery, facism, communism, Nazism.... |
|
| reply to RARPSL
RARPSL - You don't understand how SDB works or are not articulating very well.
There is NOT a private session for every stream to every STB. That happens in VOD. A single stream is started and many STBs can access it. It works that if no one is watching a channel, no session is started, thus freeing up bw.
Channel surfing works the same way as always. You don't have to call anyone or tell anyone what you want to watch. You turn the TV on and change channels. If you change channels to something not being watch a session is built and you see the video (this all happens in millseconds).
As far as MSO's stepping into the 21st century. MSOs don't build the hardware or the platform. They buy it from companies who develops it and sells it to them. The problem is the millions and millions of STBs already deployed. Do we just scrap them all and start over? You have to migrate platforms just like anything else.
SDB will be beneficial to the residential customer as well as the MSO. |
|
RARPSL
join:1999-12-08
Suffern, NY | reply to Ignite
said by Ignite:Multicasting does work fine on IPv4 as well you know. You'd best tell the UK operators running multicast peering for IPTV distribution that they absolutely need to use IPv6. Point is that IPv4 multicasting can be routed as well. IPv6 isn't necessary. Please reread my comment. I never said that IPV4 Multicasting does not work - Only that IPV6 Multicasting uses less bandwidth. With IPV4 MC, there is a separate session to each modem/STB carrying the same content. With IPV6 MC, there is one session to each sub-network (gateway router) which is monitored by those modems/STBs on the sub-network that are interested in the content. Think of it like the Broadcast Address on a sub-network (ex: for a home LAN Router at 192.168.1.1 this would be IPN 192.168.1.255) where a Node (i.e.: Modem) listens not only to its own IPN but also the IPN with all 1 bits in the node part of the IPN (i.e.: The part of the Net Mask at the end that is Zero Bits - everything past the last 1 bit in the Net Mask). Note: I am only suggesting this as an analogy, not saying that it is implemented exactly the same way.
With IPV6 a Node has multiple IPNs that it monitors and Multicasting (it may be Unicasting in this context - I do not have my IPV6 references to check right now) allows the sever to send a single version of the stream that is cloned as needed by the routers until it gets to the sub-networks where it is seen by the modems/STBs.
As to the "Does not support IPV6" so called problem, just push a new version of the Microcode that has a IPV4+IPV6 stack and that becomes a non-issue. The major reason that the STBs are IPV4-only is that the MSO Private Network-10 LAN is IPV4-Only not a IPV4+IPV6 Network. It is a Chicken-and-the-Egg/Catch-22 issue. So long as neither side gets off its butt and adds IPV6 capability there will be wasted bandwidth due to the inability to make use of the lower bandwidth consumption of IPV6 Multicasting. |
|
RARPSL
join:1999-12-08
Suffern, NY | reply to magnushsi
said by magnushsi:RARPSL - You don't understand how SDB works or are not articulating very well. There is NOT a private session for every stream to every STB. That happens in VOD. A single stream is started and many STBs can access it. It works that if no one is watching a channel, no session is started, thus freeing up bw. You might be correct about my misunderstanding. Does SDB work by sending the video to the STB over a dedicated channel (as with Analog Cable and Over-the-Air) or is it done as a TCP/IP streaming video session? If the latter, how many copies of the stream are flowing over the sub-network (i.e.: From the Gateway Router to the STBs on that sub-network) when more than one STB is tuned to the channel? If it is only one, then SDB functions the same as my suggested IPV6 Multicasting (or IS IPV6 Multicasting). Are there any technical descriptions of how SDB works "under the covers" or is it still a smoke-and-mirrors claim with no technical information available yet (i.e.: "Here is what it does" claims as opposed to "Here is how it does it" type information).
I acknowledge we might be talking past each other and saying the same thing but in the absence of information on how SDB works (as opposed to just what it does information) it is hard to tell.
said by magnushsi:As far as MSO's stepping into the 21st century. MSOs don't build the hardware or the platform. They buy it from companies who develops it and sells it to them. The problem is the millions and millions of STBs already deployed. Do we just scrap them all and start over? You have to migrate platforms just like anything else.
As to the "Does not support IPV6" so called problem, just push a new version of the Microcode that has a IPV4+IPV6 stack to the STB and that becomes a non-issue. The major reason that the STBs are IPV4-only is that the MSO Private Network-10 LAN is IPV4-Only not a IPV4+IPV6 Network. It is a Chicken-and-the-Egg/Catch-22 issue. So long as neither side gets off its butt and adds IPV6 capability there will be wasted bandwidth due to the inability to make use of the lower bandwidth consumption of IPV6 Multicasting. |
|
