ANSI SCTE 175-2017 pdf free download – Recommended Practice for Qualifying Network Devices for High Availability Streaming Video.
The ANSI/SCTE 168 series of Recommended Practices [17][18][19] describe IP video networks at MSO Headend, Core, and Hub networks. While all these configurations carry media over IP, the video flow types and distribution, link speeds, and possibly QoS policies are different at various locations. Different mixes of traffic types such as VoIP and data may be present in some locations and not in others. The recommended baseline tests in this document are intended to represent the operation of network devices in these three applications. These baseline tests provide a common set of reference results that can be used to preliminarily screen equipment and configurations during the selection, configuration, and deployment process. They will provide results to determine if the equipment under consideration provides a level of performance that is “in the ballpark” of that intended for an application. The test results indicate a per-program availability for extended “soak” tests of long term delivery of a number of realistic simultaneous video flows. They will also indicate how program availability will be affected by certain types of common realistic network events often experienced in operating complex live networks. Devices that take longer to recover from faults, that cannot accommodate simultaneously arriving persistent packet stream packets, experience crashes, or occasionally lose data for whatever reasons will fare less well in these tests compared to designs and configurations that are optimized for high availability. Other tests should also be executed to complement these baseline tests before final equipment selection and deployment. Such tests would typically include, but not be limited to, the intended load levels, number-type-and speed of active ports, level and type of non-video converged traffic expected, forwarding protocols, management protocols, etc. that are expected in the operational environment.
3. Informative References
[1] “A Proposed Media Delivery Index”, RFC 4445
[2] “High Availability Computer Systems”, J. Gray and D. P. Siewiorek, IEEE Computer 24, pp. 39-48, Sept. 1 991 .
[3] “Building a Highly-Available Enterprise Network with Juniper Networks EX-series Switches”
[4] “High Availability Network Architectures for Triple Play Services, An Overview of RESIP Core, Edge, and Access Design Guidelines”, A white paper issued by:
Siemens Communications and Juniper Networks, Inc.
[5] “Cisco – Baseline Process: Best Practices White Paper”, Document ID: 15112,Updated: Oct 04, 2005.
[6] “Cisco IOS Management for High Availability Networking: Best Practices White Paper”, Document ID: 25562, Updated: Jan 10, 2006.
[7] “Cisco IOS High Availability Curbs Downtime with Faster Reloads and Upgrades”, White Paper, 2004
[8] “Triple-play Services Quality of Experience (QoE) Requirements”, DSL Forum Technical Report TR-126
[9] “Recommended Practices for Monitoring Multimedia Distribution Quality”,ANSI/SCTE 168-6 2010
[10] ITU-T recommendation G.826 (2002), End-to-end error performance parameters and objectives for international, constant bit rate digital paths and connections
[11] ITU-T recommendation I.357 (2000), B-ISDN semi-permanent connection availability
4. Glossary, Acronyms, and Abbreviations
Availability – The number of unimpaired seconds of a multimedia stream divided by the number of tested seconds expressed as a percentage.
CBR – Constant Bit Rate
DUT – Device Under Test
Errored Second – A second during which a measured stream has one or more missing packets.
HD – High Definition; An MPEG 2 encoded HD stream is usually transmitted at greater than 10 Mb/s
IP – Internet Protocol
Link Flap – A network interface that repeatedly becomes enabled and disabled due to a layer 1 fault or other reasons
Multicast — A method for transmitting a single source stream to many receivers.
Multicast uses network devices to replicate packets that are sent to multiple receivers Packet – an IP Datagram as defined in RFC 791
Program – A program is a collection of program elements. Program elements may be elementary streams. Program elements need not have any defined time base; those that do have a common time base are intended for synchronized presentation. See ISO 13818-1.
Program Element – A generic term for one of the elementary streams or other data streams that may be included in a program. See ISO 13818-1.
Program Stream — a succession of packets (IP Datagrams) carrying multimedia content and related data for that content.ANSI SCTE 175 pdf download.