PDF(357.7 KB) View with Adobe Reader on a variety of devices
Updated:January 2, 2014
Solution Value Proposition
Q. What is Cisco
® Video Assurance Management Solution (VAMS) 1.5?
A. Cisco VAMS 1.5 delivers to service providers real-time centralized monitoring of their backbone, regional, and aggregation networks for video transport. Cisco VAMS 1.5 focuses on broadcast video over multicast. Support for unicast services across the transport network is targeted for future release. Cisco Video Assurance Management Solution 1.5 also provides the framework for a flexible end-to-end assurance platform for video.
Q. What video transport issues does the system address?
A. VAMS is targeted at:
• Identifying video continuity errors
• Identifying whether continuity errors are caused by the transport network or whether the transport network can be eliminated as a source for these errors
• Reducing the problem domain to identify where in the transport path the video service has been affected
• Correlate transport network anomalies with video anomaly detection, facilitating problem isolation and diagnosis
Q. How does Cisco VAMS integrate with my existing OSS environment?
A. Cisco VAMS is a modular architecture (Figure 1). The goal is to allow the customer to choose which aspects of the solution are appropriate and to work with Cisco Advanced Services to define how this integrates with the existing NMS/OSS environment. We have chosen a number of products to provide a fully tested, preintegrated solution reference architecture. Customers may choose to purchase the entire reference architecture with installation and deployment services only or may choose to take components of the VAMS solution with integration services as required.
Figure 1. Cisco VAMS 1.5 Reference Architecture
Q. How is Cisco VAMS different from video monitoring from third-party video probe vendors?
A. Cisco has partnered with a number of video probe vendors to demonstrate how their systems interact with Cisco VAMS. Video probe monitoring devices are typically placed at demarcation points through the video path. Examples are at the acquisition point, at the handoff from the super headend to the network, at the handoff from the network to regional or local video headends, from these headends back to the network, and from the transport network to the last mile/home environment.
By correlating these data sources with data sources in the network, it is possible to identify, isolate, and troubleshoot video errors. The benefits are twofold, reducing the time to resolve issues in the transport network and eliminating the network where it is not the cause of video errors. Both of these are cost-intensive exercises today.
Q. How do I integrate this solution into my existing OSS environment?
A. Cisco Advanced Services provides deployment and integration services for Cisco Video Assurance Management Solution and will work with the chosen integration partners to provide the required services.
Q. How does this solution relate to Cisco Video Operations Solution (VOS) and IPTV SLA
A. Cisco VOS, also known as IPTV SLA, represents the first phase of the Cisco video assurance program. Cisco VOS is a Cisco Multicast Manager-based video monitoring and troubleshooting solution and was provided as a point solution. Through enhancements to the northbound interface of Cisco Multicast Manager and integration of these into the Cisco ANA product, Cisco VAMS builds on Cisco VOS to provide a solution reference architecture that facilitates the integration of Cisco VOS into the OSS infrastructure.
Q. What are the components of Cisco Video Assurance Management Solution 1.5?
A. Cisco Video Assurance Management Solution 1.5 comprises the following Cisco products and solutions:
• Cisco Active Network Abstraction (ANA) 3.6: This system operates between the network and the OSS layers, acting as a mediation and abstraction between OSS applications and the network devices. Its abstracted network model removes the complexity of upgrading each and every OSS application when there is an upgrade of any element within the network. It also provides a gateway to the network for OSS applications supporting correlation and aggregation of events in the network and provides this correlated information northbound.
• Cisco IPTV SLA solutionbuilt around Cisco Multicast Manager 2.5: This tool provides a rich set of multicast monitoring and troubleshooting functions that allow Cisco VAMS 1.5 to be notified of any changes in multicast or threshold events on elements in the multicast trees that may affect video performance. Cisco VAMS 1.5 collects outputs from Cisco Multicast Manager into Cisco ANA, providing views of both device and multicast faults.
• Cisco Info Center: This suite of products provides the manager of managers for the VAMS 1.5 solution. Traps from ANA and Cisco Multicast Manager and video probes may be collected and correlated with affected broadcast services. In addition, the service dashboard provides a simple overview of the traps and their association to the services and allows the user to focus on specific service-related events. Making use of specific extensions to the base Cisco Info Center software, the user may cross launch Cisco Multicast Manager from multicast-related traps received to support problem isolation and multicast troubleshooting.
Q. When should Cisco VAMS be applied in the network?
A. Cisco VAMS is targeted to support the assurance of video traffic across the transport network. Cisco VAMS releases 0.5 (Cisco Multicast Manager 2.5), 1.0, and 1.5 have focused on the core, regional, and aggregation networks. Figure 1 highlights where in the transport network Cisco VAMS releases have focused to date. Future releases will expand this to the access network and to the headend, last mile, and home environments.
Cisco VAMS 0.5, 1.0, and 1.5 focus on assurance of broadcast services across the transport network. This service requires the modeling of multicast across the network and correlation of multicast with monitoring of network elements and video streams.
Q. What are the target markets for Cisco VAMS?
A. Cisco VAMS is primarily targeted at tier 1 service providers, large multiservice operators (MSOs) offering broadcast TV services, and systems integrators offering a service to tier 2/3 operators for delivering broadcast TV to their customers.
Q. What benefits does Cisco VAMS deliver?
A. Cisco VAMS provides a framework for delivering an integrated system for video assurance across the transport network. The key benefits of Cisco VAMS are:
• Proactive identification of video continuity errors before customers begin to complain
• Rapid domain isolation: Is the transport network the cause, or can it be eliminated as a source for video continuity errors?
• Problem domain reduction: For problems that occur in the transport network; where in the path has the video service been affected?
• Facilitating rapid problem isolation and diagnosis through correlation of transport network changes with video anomaly detection
Q. Cisco VAMS can help assure video across my network, but does it offer a tangible return on investment (ROI)?
A. Video is highly sensitive to packet drops. Typical targets for video performance require no more than one video impairment event in any one hour. This roughly translates to a maximum drop rate of one in one million.
Cost-effective rollout of video requires that the IP network be used to deliver this highly sensitive service. In an IP network there are typically many applications sharing the same resources. Great care must be taken in such an environment to isolate sensitive traffic and to be able to monitor and troubleshoot the network quickly and efficiently.
In particular, when customers start to call in problems in their service, it is often the case that the operator will initiate field operations (that is, truck rolls) to try to isolate the problem. This is a highly costly and time-intensive effort. Cisco VAMS helps avoid unnecessary truck rolls and helps target engineers on the right parts of the video system to reduce Mean Time to Isolate and Repair (MTTI and MTTR).
Video Transport Principles
Q. How is video encapsulated across the network?
A. The typical protocol stack for video across the transport network is constructed as shown in Table 1.
Table 1. A Typical Protocol Stack for Video across the Transport Network
MPEG-2 is a standard for the coding of video and associated audio information; it is a combination of lossy video compression and lossy audio compression methods.
The Real-Time Transport Protocol (RTP) is a transport-layer protocol to manage the real-time transmission of multimedia data. It is combined with a control protocol (RTCP) that facilitates monitoring of data delivery for large multicast networks. Monitoring allows the receiver to detect whether there is any packet loss.
User Datagram Protocol (UDP) is a stateless core Internet transport protocol that supports efficient data transmission without the guarantees of TCP. Avoiding the overhead of checking whether every packet actually arrived makes UDP faster and more efficient.
Network (see Figure 2 for an overview of a typical IP multicast network configuration)
The Internet Group Management Protocol (IGMP) is a communications protocol used to manage the membership of Internet Protocol multicast groups. IGMP is used by IP hosts and adjacent multicast routers to establish multicast group memberships.
Protocol-Independent Multicast (PIM) is a family of multicast routing protocols that can provide one-to-many and many-to-many distribution of data over the Internet.
PIM-SSM, Source Specific Multicast, is typically used to support the broadcast of video content across an IP network.
IP provides connectionless datagram delivery service for transport-layer protocols such as UDP and RTP.
Figure 2. A Typical IP Multicast Network Configuration
Q. What is the typical topology of a video broadcast service?
A. Figure 3 illustrates the typical structure of a video broadcast service. Note that video-on-demand (VoD) functions are included here for completeness.
Figure 3. Typical Structure of a Video Broadcast Service
Q. What are the critical problems the may occur end to end? From face to glass, where do video problems occur?
A. Problems may occur at any of the following points:
• Super/national headend
– Poor content quality from video provider
– Program identifier (PID) mappings or data table mappings from video source
– Transcoding lip sync issues
– Transcoding bandwidth misconfiguration
• Core/distribution network
– Packet loss, high sensitivity, for example, one loss in every one million packets
– Error correction performance: Must reconverge rapidly
– Mistakes here are catastrophic
• Local headend
– Video on demand server capacity
– VoD service availability
– Ad insertion
– Errors in local channel feed
– Subscriber management
– Error correction and channel fill capacity
• Aggregation and last mile
– Misprovisioned network
– PIM/IGMP multicast performance
– Policy management/oversubscription
– Error correction/channel fill capacity
– Loop performance and stability
– Noise and impulse on loop
• Customer premises
– Impulse noise events that impair video streams across
– Home link (such as Cat3/5 cabling, MoCA, HPNA) performance problems
Q. What is the sensitivity of video to transport problems?
A. MPEG streams consist of I frames, B frames, and P frames. B frames and P frames build upon the content of the I frame, essentially using the I frame as a reference and indicating how the next frame in the video is different from the I frame. If an I frame is lost, then all following frames are meaningless until the next I frame is received by the set-top box. Typical MPEG encodings send an I frame every 300-500 ms. Thus if an I frame is lost, the user can experience significant video impairments.
Other critical video control data, such as PAT (Program Association Tables) and PMT (Program Mapping Tables), contain information to enable the set-top box to identify and correlate video streams correctly. Loss of information can lead to such problems as loss of audio information, loss of video information, or even total loss of the channel.
Thus, dropping a single packet in the transport network can lead to major degradation in the user experience. If such losses occur frequently, the customer is unlikely to continue to use the video service.
Q. Isn't it easy to identify video-affecting problems in the network? Isn't it just packet drops?
A. In one sense, yes, it is easy to spot packet drops in the network. Simply look at the right MIB information from the network devices. The issue is that it is unclear how these affect the user experience. All packet drops are not the same. For example, error-correction protocols may be in place across the network that address certain packet drop conditions without affecting the user, or, as shown above, the dropped packet may contain information relating to multiple channels and have dramatic impact at a service level.
For this reason it is crucial to combine knowledge of network performance with analysis of the video streams from a user perspective and correlate this information to provide clear root-cause analysis.