scope:

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 simply 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 Architecture 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.

Purpose

The purpose of this document is to provide the industry 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 specific 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, correlated, and thresholded to raise higher-level alarms.

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, or at a time where faults have been detected. Fault codes can be used for troubleshooting IPTV service troubles and finding root causes.