1、 ATIS-0800028 FAULT CODES FOR IPTV The Alliance for Telecommunication Industry Solutions (ATIS) is a technical planning and standards development organization that is committed to rapidly developing and promoting technical and operations standards for the communications and related information techn
2、ologies industry worldwide using a pragmatic, flexible and open approach. Over 1,100 participants from over 300 communications companies are active in ATIS 22 industry committees and its Incubator Solutions Program. Notice of Disclaimer & Limitation of Liability The information provided in this docu
3、ment is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineering or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should
4、be implied. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMEN
5、T OF INTELLECTUAL PROPERTY RIGHTS. ATIS SHALL NOT BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY ATIS FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL ATIS BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. ATIS EXPRESSLY ADVISES ANY AND ALL U
6、SE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. NOTE - The users attention is called to the possibility that compliance with this standard may require use of an invention covered by patent rights. By publication of this standard, no position is taken wit
7、h respect to whether use of an invention covered by patent rights will be required, and if any such use is required no position is taken regarding the validity of this claim or any patent rights in connection therewith. ATIS-0800028, Fault Codes for IPTV Is an ATIS standard developed by the Quality
8、of Service Metrics (QoSM) Committee under the ATIS IPTV Interoperability Forum (IIF). Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2008 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of
9、 this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. For information contact ATIS at 202.628.6380. ATIS is online at . Printed in the United States of America. ATIS-0800028 ATIS Standard on FAULT CODES
10、 FOR IPTV Secretariat Alliance for Telecommunications Industry Solutions Approved January 2009 Abstract This document contains a categorized listing of fault codes for IPTV functions and components, including Linear TV, emergency alert services, device initialization and network attachment, digital
11、rights management, IPTV service subscription, and data collection. ATIS-0800028 ii FOREWORD The Alliance for Telecommunication Industry Solutions (ATIS) serves the public through improved understanding between carriers, customers, and manufacturers. The IPTV Interoperability Forum (IIF) develops req
12、uirements, standards, and specifications that will determine the industrys end-to-end solution for Internet Protocol Television (IPTV). The mandatory requirements are designated by the word shall and recommendations by the word should. Where both a mandatory requirement and a recommendation are spec
13、ified for the same criterion, the recommendation represents a goal currently identifiable as having distinct compatibility or performance advantages. The word may denotes a optional capability that could augment the standard. The standard is fully functional without the incorporation of this optiona
14、l capability. Suggestions for improvement of this document are welcome. They should be sent to the Alliance for Telecommunications Industry Solutions, IIF Staff, 1200 G Street NW, Suite 500, Washington, DC 20005. The Quality of Service Metrics (QoSM) Committee was responsible for the development of
15、this document, with the leadership of the following people: D. OCallaghan, IIF Chair R. Brand, IIF Vice Chair R. Streijl, QoSM Committee Co-Chair K. Toney, QoSM Committee Co-Chair K. Kerpez, Technical Editor C.A. Underkoffler, ATIS Chief Editor A. Blasgen, IIF Committee Administrator CONTRIBUTORS: R
16、andy Sharpe, Alcatel-Lucent Amit Kleinmann, AMDOCS Al Morton, AT&T Robert Streijl, AT&T David Whitney, AT&T David Hands, British Telecom Kinney Bacon, Cisco Tony Wasilewski, Cisco John Williams, JDSU Mowaffak Midani, Motorola Richard Brand, Nortel Kishan Shenoi, Symmetricom Stefan Winkler, Symmetric
17、om Paul McMenamin, Telchemy Ken Kerpez, Telcordia Technologies Kenneth Toney, Tektronix Harpal Bassali, Verizon Reza Shafiee, Verizon ATIS-0800028 iii TABLE OF CONTENTS 1 INTRODUCTION 1 1.1 OVERVIEW/BACKGROUND 1 1.2 GOAL 1 1.3 PURPOSE .1 1.4 SCOPE AND ASSUMPTIONS .2 1.5 ACCOMPANYING DATA .2 2 FAULT
18、CODES3 3 TERMINOLOGY .9 3.1 DEFINITIONS .9 3.2 ACRONYMS & ABBREVIATIONS 9 4 REFERENCES .10 TABLE OF TABLES TABLE 1: FAULT CODES FOR LINEAR IPTV3 TABLE 2: FAULT CODES FOR PUBLIC SERVICE AREAS4 TABLE 3: FAULT CODES FOR DIGITAL RIGHTS MANAGEMENT (DRM) 5 TABLE 4: FAULT CODES FOR METADATA .6 TABLE 5: FAU
19、LT CODES FOR NETWORK ATTACHMENT AND INITIALIZATION OF DEVICES AND CLIENT DISCOVERY OF IPTV SERVICES SPECIFIED IN ATIS-08000177 TABLE 6: FAULT CODES FOR REMOTE DEVICE MANAGEMENT.8 TABLE 7: FAULT CODES FOR IPTV SERVICE SUBSCRIPTION 8 TABLE 8: FAULT CODES FOR DATA COLLECTION FROM IPTV ELEMENTS AND SYST
20、EMS 8 ATIS STANDARD ATIS-0800028 ATIS Standard on Fault Codes for IPTV 1 1 INTRODUCTION 1.1 Overview/Background The Alliance for Telecommunications Industry Solutions (ATIS) IPTV Interoperability Forum (IIF) is interested in all aspects of measuring and detecting quality of IPTV services. This inclu
21、des not only performance measurements, but also detection of malfunctioning elements of the overall IPTV architecture. This document contains a categorized listing of fault codes for IPTV functions and components. There are many elements of the IPTV architecture that can be subject to many failure c
22、odes. Often a network element IPTV Terminal Function (ITF), Delivery Network Gateway (DNG), DRM function, probe, Element Management System (EMS), etc. can detect improper function of an IPTV component or signal. The type of fault is a vital input to service assurance, test, fault, and performance op
23、erations and systems. The fault codes here have some similarity to “status codes” in the Hyper Text Transfer Protocol (HTTP) in that they are generated internally by an IPTV subsystem. However, the fault codes here indicate the general functional area of a fault and are not intended to provide every
24、 detail. Fault codes are not specifically defined here to have any one single threshold value that needs to be crossed before they are issued. Fault codes are issued when a component of the IPTV system determines that it has experienced a fault, or when a device is queried. Other system or protocol-
25、specific data can be reported in addition to the fault codes here to provide more specific data, as the case may warrant. Fault codes generally delineate high-level errors, not individual lower-layer errors such as a missed and retransmitted packet. 1.2 Goal The goal of this document is to specify a
26、 standardized set of fault codes for IPTV, including brief definitions of each fault code. These fault codes are defined to identify faults for many ATIS IIF “Phase 1” IPTV service areas, per ATIS-0800003, IPTV Architecture Roadmap 1. 1.3 Purpose The purpose of this document is to provide the indust
27、ry with a first set of well-defined fault codes that categorizes types of failures for IPTV. Many systems, components, and functions simply either work or do not. Such information is very useful for providers of IPTV services. Fault codes are generally functional and need not be generated by any spe
28、cific device. However, they may indicate the functional area of the fault (e.g., at the client). Fault codes could be generated or interpreted in Element Management System (EMS) or Network Management System (NMS) software. An NMS could record multiple fault codes, with statistics gathered, correlate
29、d, and thresholded to raise higher-level alarms. ATIS-0800028 2 Fault codes are useful for an in-service IPTV system and can be issued any time a part in the overall system malfunctions. Not all performance measurements may be continuous and are generally expected to be issued independent of faults,
30、 or at a time where faults have been detected. Fault codes can be used for troubleshooting IPTV service troubles and finding root causes. 1.4 Scope and Assumptions Fault codes are indicators of general types of failures. A fault code may not be as specific as other QoS metrics. A fault code may simp
31、ly indicate the general area of a fault to aid monitoring or troubleshooting of areas that could otherwise be opaque. Each fault code is accompanied by a brief defining description. The following characteristic identifies the scope of this document: Only “Phase 1” work items identified in the IPTV A
32、rchitecture Roadmap 1 are addressed in this standard, generally related to linear broadcast IPTV service. A few fault codes are defined based on metrics in previous standards. Specific measurement techniques and methodologies for most fault codes are for further study. 1.5 Accompanying Data The indi
33、vidual fault codes listed here can be aggregated into counts, averages, or other statistics. These statistics can be compared to a threshold to generate alarms. They may apply to an individual stream, an aggregation of streams, transactions, overall service behavior, etc., as specified in other stan
34、dards. The description of some fault codes indicates that they should be reported by a server or client of a particular IPTV subsystem. However, fault codes here indicate the general functional area of a fault, and may not indicate the exact component or piece of software that caused a fault. Since
35、the location of a fault is not included in the fault code definition, this location should be reported or otherwise available along with the fault code. Also, the time that the fault occurs and the device causing the fault should be similarly reported or otherwise available. Ancillary data should ac
36、company a fault code to indicate: Location or unique ID of the system in fault. Time stamp. Which component or service is in a fault condition. For example: BROADCAST.TRANSMISSION.ERROR Location: . Time stamp: . Which component or service is in a fault condition: . The above format and IDs are only
37、provided as an example and are not specified in this document. ATIS-0800028 3 Further indications of details related to a fault may be useful but are not defined at this time. These details may include the definition of the fault cause as well as additional details that could refine the fault locati
38、on. Reporting severity levels of each fault code is also of interest, but is not defined at this time. 2 FAULT CODES The detailed listing of standardized QoS metrics for linear broadcast is in ATIS-0800008, QoS Metrics for Linear Broadcast IPTV 3. Table 1: Fault Codes for Linear IPTV Fault Code Desc
39、ription BROADCAST.ERROR Indicator that denotes the occurrence of a linear broadcast error of any type. BROADCAST.TRANSMISSION.ERROR Denotes the occurrence of an RTP/IP transmission layer error of any type. BROADCAST.VIDEO.ERROR Any error in a video stream. BROADCAST.AUDIO.ERROR Any error in an audio
40、 stream. BROADCAST.AUDIO.VOLUMEERROR Incorrect audio volume. BROADCAST.AUDIO.BACKGROUNDNOISEERROR Incorrect audio background noise volume. BROADCAST.LIPSYNCHERROR Mismatch between audio/video synchronization (lip synch error). BROADCAST.CONTENT_QUALITY.ERROR Any error in the broadcast content qualit
41、y, such as if the monitored picture quality falls below a threshold. BROADCAST.MULTICAST.ERROR Indicator that denotes the occurrence of a multicast error of any type. BROADCAST.TRANSACTION.ERROR Denotes the occurrence of a broadcast transaction error of any type. BROADCAST.TRANSACTION.IGMP.ERROR Den
42、otes the occurrence of an error in an IGMP (multicast) transaction. BROADCAST.MEDIA_STREAM.ERROR Denotes the occurrence of a MPEG-TS media stream error of any type. BROADCAST.MEDIA_STREAM.PCR.ERROR Non-zero number of MPEG2-TS PCR failures, metric number 31 in Table 2 of ATIS-0800008 3. BROADCAST.MED
43、IA_STREAM.PSI.ERROR Non-zero number of MPEG2-TS Program Specific Information (PSI) errors, metric number 24 in Table 2 of ATIS-0800008 3. BROADCAST.BUFFER.ERROR Buffer under-run or overflow. ATIS-0800028 4 Fault Code Description BROADCAST.TIMING.ERROR Denotes the occurrence of a timing error of any
44、type. BROADCAST.DIGITALPROGRAMINSERTION.ERROR Denotes a Digital Program Insertion (DPI) error. BROADCAST.LOWBITRATE Denotes occurrence of an insufficient bit rate at a network link, device, port, or stream. BROADCAST.INSUFFICIENT_RESOURCES Resources (for example, bit rate) are insufficient to allow
45、a new linear TV channel. This is the same as the “INSUFFICIENT_RESOURCES (4041)” Error Code (per ITU-T Q.3301.1) defined in ATIS-0800018, IPTV Linear TV Service 6. The fault codes for public service areas generally indicate unsuccessful delivery of signals related to public services. Monitoring retr
46、ansmissions, timeouts, verification, or other mechanisms may be useful for equipment to determine when it should issue one of these fault codes. Table 2: Fault Codes for Public Service Areas Emergency Alert Services (EAS) Fault Code Description EAS.ERROR Indicator that denotes the occurrence of an E
47、AS error of any type. EAS.SIGNAL.SUBSCRIBER.ABSENT EAS multicast signals arriving at subscriber absent. EAS.SIGNAL.SUBSCRIBER.INVALID EAS multicast signals arriving at subscriber invalid. EAS.SIGNAL.SUBSCRIBER.AUTHENTICATIONFAIL EAS multicast signal authentication failure at subscriber. EAS.SIGNAL.E
48、IS.ABSENT EAS signal arriving at EAS Ingestion System (EIS) absent. EAS.SIGNAL.EIS.INVALID EAS signal arriving at EIS invalid. EAS.SIGNAL.AUTHENTICATION.FAIL EAS multicast signal authentication failure at EIS. EAS.SIGNAL.ENDEC.ABSENT EAS signal arriving at endec absent. EAS.SIGNAL.ENDEC.INVALID EAS
49、signal arriving at endec invalid. ATIS-0800028 5 Closed Captioning Fault Code Description CC.SIGNAL.ABSENT Closed Captioning (CC) signal absent. Content Advisories and V-chip Technology Fault Code Description CA.SIGNAL.ABSENT Content Advisory (CA) signal absent. “DRM.Error” should be the only fault code transmitted over a non-secured communications channel. All other DRM fault codes should transmit only over a secured communications channel. Table 3: Fault Codes for Digital Rights Management (DRM) Fault Code Description DRM.ERROR Indica
