Friday, December 26, 2008
Upgrading TCP for the Heavy User
Heavy users will declare their packets to be eligible for discard and a feedback mechanism will be created that will inform core routers of congestion that is occurring in the network so that they can start discarding packets.
This approach should provide better performance to the casual user than they experience today without significantly degrading performance for the heavy user.
You can get more details from Briscoe's web site.
It looks to me that this is a much better approach than the limits being proposed by carriers today. It also seems to resolve the Net Neutrality argument by redefining what fairness means and equalizing the performance of the network to a broad set of users rather than equalizing access to bandwidth.
I question how much these techniques will help in an IP network dominated by TV traffic. TV traffic wants to use a lot of bandwidth and have a high QoS at the same time. An HDTV viewer will not like it if discarding packets from his or her video stream causes visual or audio defects.
Sunday, November 16, 2008
Telco IPTV Network Architecture
I think that these developments are a real step forward for IPTV networks. I think that their ability to support fast channel change and packet retransmission are fundamental improvements. The ad insertion and video on demand capabilities will provide significant improvements, up to a point.
The fundamental issue will be the amount of storage provided by the router. In a personalized ad insertion system, this will work fine as long as the number of personalized ads does not become too large. The issue with video on demand will be the hit rate, that is the number of video on demand requests that are served by the content on the router vs. the centralized router.
My own thinking on this issue has evolved. I did a report for MRG in the scaling of IPTV networks three years ago that identified that the amount of traffic required to support high levels of on demand traffic will be a major issue. At that time, I felt that the caching approach that Alcatel-Lucent and Cisco are talking about would be the answer.
I looked at this issue again last year in the report Networking Strategies for TelcoTV Services. With further analysis, I realized that the traffic to fill the distributed video on demand caches would be enough by itself to swam metro networks. My conclusion was that the IPTV traffic had to be removed from the IP/Ethernet networks and move down to the optical level.
My recent report Telecom 2020: Transformation Strategies looked at the issue again and took into account the consolidation of fiber access systems into large centers that would serve very large numbers of subscribers. This architecture would mean that there would be enough video on demand traffic to one of these major fiber access centers to fill a 10 Gbps or even a 100 Gbps optical link; therefor, there is no benefit for bringing this traffic up to the packet layer. It will be much more economical just to pass directly to the fiber access center over a direct optical link.
There are too philosophical points that drive my thinking. The first is that as IPTV moves from multicast to on demand and unicast, the TV traffic will dominate the network. It just makes sense to optimize the network for the dominant traffic type.
The second point is that it is very difficult to understand how a packet network can provide an acceptable SLA or QoS when 99 percent of the traffic on the network is deterministic TV traffic. On the other hand, it is easy to see how this will work over direct optical links.
There is a real question of timing here. For many carriers, the cached approach introduced by Alcatel-Lucent and Cisco will be a big help over the next three to five years. However, I do think that these carriers will be thinking seriously about a direct optical approach after that.
Thursday, November 13, 2008
Cisco Introduces 100 Gbps Ethernet Edge Router
The ASR 9000 incorporates the Cisco Advanced Video Services Module (AVSM) with 4 terabyts of flash RAM storage that offers content caching, ad insertion, fast channel change and error correction of video streams. Fast channel change and onboard error correction for both unicast and multicast video traffic helps ensure that errors can be detected by any set-top box and retransmitted within milliseconds.
This is the kind of improvement in performance that will be required as we move through the next decade as 100 GBps Ethernet links become commonplace.
The AVSM capabilities of the AVSM provide similar capabilities to Alcatel-Lucent's TPSDA 2.0 approach that provides similar capabilities. Both approach will require support from the IPTV middleware to get their full effect.
The 4 TB of storage will be enough to store about 1,000 hours of HD content. This will be enough for the most popular video on demand assets but not for the long tail of for an extensive NPVR service. Cisco will have to add a lot more storage to really offload video traffic from the network as it is currently claiming. I will write a column that will discuss this issue in more detail in a couple of days. I just don't think that a distributed approach will hold up over the long term.
Thursday, October 16, 2008
Alcatel-Lucent TPSDA 2.0 Provides Better Video Support
- For fast channel change the last few minutes of every multicast channel will be stored in the network and the new channel will be started immediately, eliminating the latency that typically occurs today. Alcatel-Lucent said that HD channel change time will be reduced from several seconds to well under a second.
- For packet retransmission the network will store enough packets to immediately service the packet retransmission request.
- For ad insertion targeted ads will be stored and inserted in the network.
If the service provider uses Alcatel-Lucent access nodes, these functions can be provided in the access network. These functions can also be provided in the Alcatel-Lucent switches or edge routers for service providers using Alcatel-Lucent's TPSDA 2.0 architecture.
Alcatel-Lucent has also discussed plans to increase the amount of storage in these network elements in order to support rewind TV and video on demand delivery.
TPSDA 2.0 can support these functions for service providers using access nodes from other manufacturers by implementing them in the switches and edge routers.
Microsoft has not announced any support for these network capabilities.
This approach will give service providers new flexibility in managing the bandwidth demands from an IPTV service, especially as more and more on demand and personalized services are provided. I think the flexibility that it gives in placing storage in the network will improve the ability of service providers to optimize their networks.
I think that this solution is a good one for the next several years. I believe over the long run that TelcoTV and other video traffic will need to be pushed down to the optical layer. There will be too much of it for packet switches to handle.