I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU G.997.1 (11/2016) SERIES G: TRANSMISSION SSTEMS AND MEDIA, DIGITAL SSTEMS AND NETWORKS Digital sections and digital line system Metallic access networks Physical layer management for digital subscriber line transceivers Recommendation G.997.1
G-SERIES RECOMMENDATIONS TRANSMISSION SSTEMS AND MEDIA, DIGITAL SSTEMS AND NETWORKS INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER- TRANSMISSION SSTEMS INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SSTEMS ON METALLIC LINES GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SSTEMS ON RADIO-RELA OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES COORDINATION OF RADIOTELEPHON AND LINE TELEPHON TRANSMISSION MEDIA AND OPTICAL SSTEMS CHARACTERISTICS DIGITAL TERMINAL EQUIPMENTS DIGITAL NETWORKS DIGITAL SECTIONS AND DIGITAL LINE SSTEM General Parameters for optical fibre cable systems Digital sections at hierarchical bit rates based on a bit rate of 2048 kbit/s Digital line transmission systems on cable at non-hierarchical bit rates Digital line systems provided by FDM transmission bearers Digital line systems Digital section and digital transmission systems for customer access to ISDN Optical fibre submarine cable systems Optical line systems for local and access networks Metallic access networks MULTIMEDIA QUALIT OF SERVICE AND PERFORMANCE GENERIC AND USER- RELATED ASPECTS TRANSMISSION MEDIA CHARACTERISTICS DATA OVER TRANSPORT GENERIC ASPECTS PACKET OVER TRANSPORT ASPECTS ACCESS NETWORKS G.100 G.199 G.200 G.299 G.300 G.399 G.400 G.449 G.450 G.499 G.600 G.699 G.700 G.799 G.800 G.899 G.900 G.999 G.900 G.909 G.910 G.919 G.920 G.929 G.930 G.939 G.940 G.949 G.950 G.959 G.960 G.969 G.970 G.979 G.980 G.989 G.990 G.999 G.1000 G.1999 G.6000 G.6999 G.7000 G.7999 G.8000 G.8999 G.9000 G.9999 For further details, please refer to the list of Recommendations.
Recommendation G.997.1 Summary Physical layer management for digital subscriber line transceivers Recommendation G.997.1 specifies the physical layer management for asymmetric digital subscriber line (ADSL) and very high speed digital subscriber line 2 (VDSL2) transmission systems. It specifies means of communication on a transport transmission channel defined in the physical layer Recommendations G.992.1, G.992.2, G.992.3, G.992.4, G.992.5 and G.993.2. It specifies network elements (NE) content and syntax for configuration, fault and performance management. The revision of this Recommendation includes the management information base (MIB) elements for the physical layer management of Recommendation G.993.2 and additional MIB elements for the physical layer management of Recommendations G.992.3 and G.992.5. The 2016 edition of this Recommendation integrates G.997.1 (2012) and all its amendments and corrigenda. This edition does not add any new technical material. History Edition Recommendation Approval Study Group Unique ID * 1.0 G.997.1 1999-07-02 15 11.1002/1000/4723 2.0 G.997.1 2003-05-22 15 11.1002/1000/6283 2.1 G.997.1 (2003) Amd. 1 2003-12-14 15 11.1002/1000/7081 2.2 G.997.1 (2003) Amd. 2 2005-01-13 15 11.1002/1000/7492 3.0 G.997.1 2005-09-06 15 11.1002/1000/8550 4.0 G.997.1 2006-06-06 15 11.1002/1000/8768 4.1 G.997.1 (2006) Cor. 1 2006-12-14 15 11.1002/1000/8994 4.2 G.997.1 (2006) Amd. 1 2006-12-14 15 11.1002/1000/8995 4.3 G.997.1 (2006) Amd. 2 2007-11-22 15 11.1002/1000/9168 4.4 G.997.1 (2006) Amd. 3 2008-08-22 15 11.1002/1000/9389 5.0 G.997.1 2009-04-22 15 11.1002/1000/9676 5.1 G.997.1 (2009) Cor. 1 2009-11-13 15 11.1002/1000/10417 5.2 G.997.1 (2009) Amd. 1 2010-06-11 15 11.1002/1000/10416 5.3 G.997.1 (2009) Amd. 2 2010-11-29 15 11.1002/1000/11016 5.4 G.997.1 (2009) Amd. 3 2011-06-22 15 11.1002/1000/11130 5.5 G.997.1 (2009) Cor. 2 2011-10-29 15 11.1002/1000/11397 5.6 G.997.1 (2009) Amd. 4 2011-12-16 15 11.1002/1000/11398 5.7 G.997.1 (2009) Amd. 5 2012-02-13 15 11.1002/1000/11504 6.0 G.997.1 2012-06-13 15 11.1002/1000/11645 6.1 G.997.1 (2012) Amd. 1 2012-12-07 15 11.1002/1000/11798 6.2 G.997.1 (2012) Amd. 2 2013-04-22 15 11.1002/1000/11893 * To access the Recommendation, type the URL http://handle.itu.int/ in the address field of your web browser, followed by the Recommendation's unique ID. For example, http://handle.itu.int/11.1002/1000/11 830-en. Rec. G.997.1 (11/2016) i
6.3 G.997.1 (2012) Amd. 3 2013-08-29 15 11.1002/1000/11996 6.4 G.997.1 (2012) Amd. 4 2015-02-13 15 11.1002/1000/12374 6.5 G.997.1 (2012) Amd. 5 2015-11-06 15 11.1002/1000/12566 6.6 G.997.1 (2012) Amd. 6 2016-03-29 15 11.1002/1000/12798 6.7 G.997.1 (2012) Cor. 1 2016-11-13 15 11.1002/1000/13108 7.0 G.997.1 2016-11-13 15 11.1002/1000/13346 ii Rec. G.997.1 (11/2016)
FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector () is a permanent organ of ITU. is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the study groups which, in turn, produce Recommendations on these topics. The approval of Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within 's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERT RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http://www.itu.int//ipr/. ITU 2017 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. G.997.1 (11/2016) iii
Table of Contents Page 1 Scope... 1 2 References... 1 3 Definitions... 2 4 Abbreviations and acronyms... 3 5 Overview... 6 5.1 Physical layer management mechanisms... 7 6 OAM communications channel... 8 6.1 Requirements on the physical media dependent (PMD) layer for the bitoriented clear embedded operations channel (EOC)... 9 6.2 Requirements on the PMD layer for the message-oriented clear EOC... 10 6.3 Data link layer... 10 6.4 The SNMP protocol... 13 7 Management information base (MIB) elements... 15 7.1 Failures... 18 7.2 Performance monitoring functions... 20 7.3 Configuration functions... 33 7.4 Inventory information... 71 7.5 Test, diagnostic and status parameters... 73 7.6 Network management elements partitioning... 96 Appendix I Processing examples... 140 I.1 Illustration of transmitter processing... 140 I.2 Illustration of receiver processing... 141 Appendix II Downstream power back-off... 142 II.1 Introduction... 142 II.2 Description of the DPBO method... 143 Bibliography... 146 iv Rec. G.997.1 (11/2016)
Recommendation G.997.1 1 Scope Physical layer management for digital subscriber line transceivers This Recommendation specifies the physical layer management for asymmetric digital subscriber line (ADSL) and very high speed digital subscriber line 2 (VDSL2) transmission systems based on the usage of indicator bits and embedded operations channel (EOC) messages defined in the G.992.x series of Recommendations and in [ G.993.2], and the clear embedded operations channel defined in this Recommendation. It specifies network management elements content for configuration, fault, and performance management. The mechanisms to provide operations, administration and maintenance (OAM) functions, and to generate OAM flows F1, F2 and F3, will depend on the transport mechanism of the physical layer transmission system as well as on the supervision functions contained within the physical layer termination functions of equipment. This Recommendation specifies only flow F3 transmission path level. For interrelationships of this Recommendation with other Recommendations of the G.99x-series, see [ G.995.1]. 2 References The following Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. [ G.992.1] [ G.992.2] [ G.992.3] [ G.992.4] [ G.992.5] [ G.993.2] [ G.993.5] [ G.994.1] Recommendation G.992.1 (1999), Asymmetric digital subscriber line (ADSL) transceivers. Recommendation G.992.2 (1999), Splitterless asymmetric digital subscriber line (ADSL) transceivers. Recommendation G.992.3 (2005), Asymmetric digital subscriber line transceivers 2 (ADSL2). Recommendation G.992.4 (2002), Splitterless asymmetric digital subscriber line transceivers 2 (splitterless ADSL2). Recommendation G.992.5 (2005), Asymmetric digital subscriber line (ADSL) transceivers Extended bandwidth ADSL2 (ADSL2plus). Recommendation G.993.2 (2011), Very high speed digital subscriber line transceivers 2 (VDSL2). Recommendation G.993.5 (2010), Self-FEXT cancellation (vectoring) for use with VDSL2 transceivers. Recommendation G.994.1 (2003), Handshake procedures for digital subscriber line (DSL) transceivers. Rec. G.997.1 (11/2016) 1
[ G.995.1] [ G.998.4] Recommendation G.995.1 (2001), Overview of digital subscriber line (DSL) Recommendations. Recommendation G.998.4 (2010), Improved impulse noise protection for DSL transceivers. [ I.432.x] Recommendations I.432.x-series, B-ISDN user-network interface Physical layer specification. [ I.610] [ T.35] [IETF RFC 1157] 3 Definitions Recommendation I.610 (1999), B-ISDN operation and maintenance principles and functions. Recommendation T.35 (2000), Procedure for the allocation of defined codes for non-standard facilities. IETF RFC 1157 (1990), A Simple Network Management Protocol (SNMP). This Recommendation defines the following terms: 3.1 accumulation period: Period of time used by the network management system (NMS) to accumulate sufficient number of parameter samples. 3.2 anomaly: An anomaly is a discrepancy between the actual and desired characteristics of an item. The desired characteristic may be expressed in the form of a specification. An anomaly may or may not affect the ability of an item to perform a required function. 3.3 bearer channel: As defined in the respective Recommendation (also referred to as "frame bearer" in various digital subscriber line (DSL) Recommendations). 3.4 clear embedded operations channel (EOC): An octet oriented data channel multiplexed in the physical layer transmission frame structure. 3.5 defect: A defect is a limited interruption in the ability of an item to perform a required function. It may or may not lead to maintenance action depending on the results of additional analysis. Successive anomalies causing a decrease in the ability of an item to perform a required function are considered a defect. 3.6 failure: A failure is the termination of the ability of an item to perform a required function. NOTE After failure, the item has a fault. Analysis of successive anomalies or defects affecting the same item can lead to the item being considered as "failed". 3.7 full initialization: Any type of initialization procedure defined in respective Recommendations, except short initialization. 3.8 masked subcarrier: A subcarrier that is not transmitted during initialization and showtime. 3.9 MEDLE set: A set of subcarriers used during the digital subscriber line (DSL) initialization. This set is defined in the respective Recommendations. 3.10 net data rate: Net data rate is defined in the G.992.x-series Recommendations and in [ G.993.2]. 3.11 short initialization: Shortened type of initialization procedure, as specified in clause 7.2.1.3.3. Short initialization includes fast retrain, as specified in [ G.992.2], and short initialization, as specified in [ G.992.3] and [ G.992.4]. 3.12 showtime: As defined in the respective Recommendations. 2 Rec. G.997.1 (11/2016)
3.13 xdsl: Any of the various types of digital subscriber line technologies. 3.14 α-interface, β-interface: between the physical media specific-transmission convergence (PMS-TC) and the transport protocol specific-transmission convergence (TPS-TC) sub-layers of the xtu, as defined in [ G.995.1] and the respective Recommendations. 3.15 γ-interface: Application interface of the xtu, as defined in [ G.995.1] and the respective Recommendations. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: ADSL Asymmetric Digital Subscriber Line ADSL2 Asymmetric Digital Subscriber Line 2 AME AN ATM ATU ATU-C ATU-R CRC CV CV-C CV-CFE DMT DPBO DSL EOC ES ES-L ES-LFE FEBE FEC FEC-C ADSL Management Entity Access Node Asynchronous Transfer Mode ADSL Transceiver Unit ADSL Transceiver Unit Central office end (i.e., network operator) ADSL Transceiver Unit Remote side (i.e., subscriber end of the loop) Cyclic Redundancy Check Code Violation Code Violation Channel Code Violation Channel Far-End Discrete MultiTone Downstream Power Back-Off Digital Subscriber Line Embedded Operations Channel Errored Second Errored Second Line Errored Second Line Far-End Far-End Block Error Forward Error Correction Forward Error Correction Channel FEC-CFE Forward Error Correction Channel Far-End FECS-L Forward Error Correction Second Line FECS-LFE Forward Error Correction Second Line Far-End FEXT FFEC HDLC HEC Far End Crosstalk Far-end Forward Error Correction High-level Data Link Control Header Error Control Rec. G.997.1 (11/2016) 3
IMA INM ISDN LCD LCD-FE LDSF LFE LINIT LOF LOF-FE LOS LOS-FE LOSS-L LPR LPR-FE LSB ME MIB Inverse Multiplexing over ATM Impulse Noise Monitoring Integrated Services Digital Network Loss of Cell Delineation Far-End Loss of Cell Delineation Loop Diagnostic mode Forced Line Far End Line Initialization Loss of Frame Far-End Loss of Frame Loss of Signal Far-End Loss of Signal LOS Second-line Loss of Power Far-End Loss of Power Least Significant Bit Management Entity Management Information Base MINEFTR Minimum Error-Free Throughput MSB NCD NCD-FE NE NEXT NMS NT OAM OLR OOS OOS-FE PDU PM PMD PMSF PMS-TC POTS Most Significant Bit No Cell Delineation Far-End No Cell Delineation Network Element Near End Crosstalk Network Management System Network Termination Operations, Administration and Maintenance On-Line Reconfiguration Out of Sync Far-End Out of Sync Protocol Data Unit Performance Monitoring Physical Media Dependent Power Management State Forced Physical Media Specific-Transmission Convergence Plain Old Telephone Service; one of the services using the voiceband; sometimes used as a descriptor for all voiceband services. 4 Rec. G.997.1 (11/2016)
PSD PSTN PTM RDI RFI SEF SES SNMP SNR STM T/S TC TCM TE TPS-TC T-R TR UAS UAS-L U-C U-R V-C Power Spectral Density Public Switched Telephone Network Packet Transfer Mode Remote Defect Indication Remote Failure Indication Severely Errored Frame Severely Errored Second Simple Network Management Protocol Signal-to-Noise Ratio Synchronous Transfer Mode (s) between ADSL network termination and Customer Installation or home network Transmission Convergence (layer) Time Compression Multiplex Terminal Equipment Transport Protocol Specific-Transmission Convergence (s) between ATU-R and switching layer (ATM, STM or PTM) Threshold Reports Unavailable Second Unavailable Second Line Loop interface-central office end Loop interface-remote side (i.e., subscriber end of the loop) Logical interface between ATU-C and a digital network element, such as one or more switching systems VDSL2 Very high speed Digital Subscriber Line 2 VME VTU VTU-O VTU-R xtu xtu-c xtu-r VDSL2 Management Entity VDSL2 Transceiver Unit VDSL2 Transceiver Unit central Office or network element end (in the 'ONU' optical network unit per [ G.993.2] i.e., network operator.) VTU at the Remote site (i.e., subscriber end of the loop) xdsl Transceiver Unit xdsl Transceiver Unit Central office end (i.e., at the network operator), used as a generic term referring to both the ATU-C of the G.992.x series of Recommendations and the VTU-O of [ G.993.2]. xdsl Transceiver Unit at the remote side (i.e., at the subscriber end of the loop), used as a generic term referring to both the ATU-R of the G.992.x series of Recommendations and the VTU-R of [ G.993.2]. Rec. G.997.1 (11/2016) 5
5 Overview Figure 5-1 shows the system reference model for this Recommendation. NMS Q TE Management entity NT Management entity AN TE Home network P H ATU-R ATU-C P H Broadband network T/S T-R U-R U-C V-C V G.997.1_F5-1 Management in Rec. G.997.1 Figure 5-1 System reference model There are four management interfaces defined in this Recommendation. The Q-interface is at the access node (AN) for network management systems (NMS). All the parameters specified in this Recommendation apply at the Q-interface. The Q-interface provides the interface between the NMS of the operator and the management entity (ME) in the access node. The near-end parameters supported in the management entity (ME) at the access node (AN) are derived from the xtu-c while the far-end parameters (from the xtu-r) can be derived by either of two mechanisms over the U-interface: Indicator bits and embedded operations channel (EOC) messages can be used to generate the required xtu-r parameters in the ME of the AN. The OAM channel and protocol (specified in clause 6) can be used to retrieve the parameters from the xtu-r, when requested by the ME of the AN. The definition of the transport of the management instrumentation over the Q-interface is outside the scope of this Recommendation. The coding of the management information transferred over the Q-interface is beyond the scope of this Recommendation. Two management interfaces U-C at the xtu-c and U-R at the xtu-r, are defined. Their main purposes are to provide: At the xtu-c: the xtu-c near-end parameters for the xtu-r to retrieve over the U-interface. At the xtu-r: the xtu-r near-end parameters for the xtu-c to retrieve over the U-interface. This Recommendation defines (see clause 6) a method for the communication of the xtu parameters defined in clause 7 over the U-interface. NOTE 1 In this Recommendation, U-C and U-R refer to the management interfaces that apply to the respective physical reference points defined in respective Recommendations. In Rec. G.993.2, the reference point U-C is referred to as U-O. 6 Rec. G.997.1 (11/2016)
At the T-/S-interface a subset of the parameters specified in this Recommendation may apply. The purpose is to indicate the ADSL or VDSL2 link status to the terminal equipment (TE). These parameters are maintained by the ME of the network termination (NT) and are made available over the T-/S-interface. The G-interface is defined and refers to the management flows from the ME on the NT directly to the NMS when that flow crosses the 'U-C' and 'U-R' interface, but the management flow is not mediated by the ME on the AN. The specification of the protocols to support flows that cross the G-interface is outside the scope of this Recommendation. The parameters supported at the G-interface are a superset of those supported at the S/T interface and they are maintained by the ME of the NT. The far-end parameters (from the xtu-c) can be derived by either of two mechanisms over the U-interface: Indicator bits and EOC messages, which are provided at the physical media dependent (PMD) layer, can be used to generate the required xtu-c parameters in the ME of the NT. The OAM channel and protocol (specified in clause 6) can be used to retrieve the parameters from the xtu-c, when requested by the ME of the NT. The definition of the transport of this management information over the T-/S-interfaces is outside the scope of this Recommendation. The coding of the management information transferred over the T-S-interface is beyond the scope of this Recommendation. Depending on the transceiver Recommendation (e.g., [ G.992.1] or [ G.992.2]), some of the parameters may not apply (i.e., fast data stream parameters for [ G.992.2]). Specific parameters may be applicable to specific transceiver Recommendations. Tables in clause 7.6 provide the applicability of any specific parameter to any particular Recommendation in the G.992.x series of Recommendations and/or to [ G.993.2]. NOTE 2 Throughout this Recommendation, the use of the term xtu-c refers to both ATU-C and VTU-O, while the term xtu-r refers to both ATU-R and VTU-R. 5.1 Physical layer management mechanisms The general definition of OAM for ATM networks is defined in [ I.610]. This Recommendation uses this model for both ATM and PTM. The physical layer contains the three lowest OAM levels as outlined in Figure 5-2. The allocation of the OAM flows is as follows: F1: regenerator section level; F2: digital section level; F3: transmission path level. Rec. G.997.1 (11/2016) 7
F5 Virtual channel level ATM layer F4 Virtual path level F3 Transmission path level Physical layer F2 Digital section level F1 Regenerator section level Endpoint of corresponding levels Connecting point of corresponding levels G.997.1_F5-2 Figure 5-2 OAM hierarchical levels and their relationship with the ATM layer and physical layer The physical levels F1-F3 in this Recommendation are coupled with upper levels F4, F5 from the fault management perspective. When an F3 fault (e.g., loss of signal (LOS)) is detected, it is reported to the NMS, but an F4/F5, as defined in [ I.610], fault is generated as well. The OAM levels F1-F3 cover the part of the system referred as "xdsl LINE" in Figure 5-3. This part includes analogue processing and digital processing for the metallic transmission medium. Levels F1-F3 provide performance monitoring of both analogue and digital line-related entities. The xdsl LINE is delimited by the two end points V-D (or ) and T-D (or β) as presented in Figure 5-3. The xdsl LINE is defined between the V-D (or ) and the T-D (or β) reference points. The xdsl ATM PATH is defined between the V-C (or γc) and T-R (or γr) reference points. The xdsl PTM PATH is defined between the V-C (or γc) and T-R (or γr) reference points. The xdsl STM PATH is for further study. ATM0 ATM1 Cell TC Cell TC AS0 LS0 AS1 LS1 Mux Digital processing Analogue processing Analogue processing Digital processing Mux AS0 LS0 AS1 LS1 Cell TC Cell TC ATM0 ATM1 Clear EOC Clear EOC V-C V-D U T-D T-R ADSL LINE ADSL ATM PATH G.997.1_F5-3 Figure 5-3 xdsl LINE and xdsl ATM or PTM PATH definition 6 OAM communications channel This clause specifies an optional OAM communication channel across the U-interface (see Figure 6-1). If this channel is implemented, the xtu-c and the xtu-r may use it for transporting physical layer OAM messages. If either the xtu-c or the xtu-r does not have the capability of 8 Rec. G.997.1 (11/2016)
this OAM channel, the far-end parameters, defined in clause 7, at the xtu-c shall be derived from the indicator bits and EOC messages defined in the G.992.x-series of Recommendations and in [ G.993.2]. Support for the OAM communication channel defined in this clause will be indicated during initialization by messages defined in [ G.994.1] for G.992.1 and G.992.2. NOTE 1 In those cases where neither the xtu-r nor the xtu-c implements this communication channel, there are some reduced physical layer OAM capabilities (see clause 7). The G.992.x-series of Recommendations and [ G.993.2] may provide one of two mechanisms to transport physical layer OAM messages. For [ G.992.1] and [ G.992.2], the mechanism is a bit-oriented clear EOC. For these Recommendations, the channel shall meet the requirements specified in clause 6.1. The data link layer shall be as specified in clause 6.3. For [ G.992.3], [ G.992.4], [ G.992.5] and [ G.993.2], the mechanism is a message-oriented clear EOC. For these Recommendations, the channel shall meet the requirements specified in clause 6.2. The data link layer shall be as specified in clauses 7.8.2.3, 7.8.2.4 and 9.4.1.8 of [ G.992.3] for [ G.992.3], [ G.992.4] and [ G.992.5]; and as specified in clauses 8.2 and 11.2.3 of [ G.993.2] for [ G.993.2]. MIB ATU-R SNMP HDLC ATU-C SNMP HDLC MIB Clear EOC Bit transmission U-interface Clear EOC Bit transmission G.997.1_F6-1 Figure 6-1 OAM communication channel layers for bit-oriented clear EOC MIB ATU-C SNMP Clear EOC Msg ATU-R SNMP Clear EOC Msg MIB HDLC Overhead channel U-interface HDLC Overhead channel G.997.1_F6-2 Figure 6-2 OAM communication channel layers for message-oriented clear EOC NOTE 2 In Figures 6-1 and 6-2, MIB represents management information base related to the xtu. 6.1 Requirements on the physical media dependent (PMD) layer for the bit-oriented clear embedded operations channel (EOC) In order to support the physical layer OAM protocols defined in this Recommendation, a physical layer Recommendation shall provide a full duplex data channel for support of the data link layer defined in clause 6.3. Rec. G.997.1 (11/2016) 9
The clear EOC serves the function of a physical layer of the protocol stack defined in this Recommendation for [ G.992.2] and [ G.992.1]. 1) The clear EOC shall be a part of the protocol overhead for the particular xdsl Recommendation. 2) The clear EOC shall be available to carry traffic whenever the xdsl protocol is in a normal transmission mode (e.g., "showtime"). 3) The clear EOC shall be available regardless of the specific configuration options or run time adaptation of an ATU-C and ATU-R that are communicating. 4) The clear EOC shall be terminated in the ATU-R and the ATU-C. 5) The clear EOC shall support traffic of at least 4 kbit/s. 6) The clear EOC shall support delineation of individual octets in order to support the link level protocol defined in clause 7.1. 7) The clear EOC should not support error correction or detection. Error correction and detection is supported by use of the OAM stack defined in this Recommendation. 8) The clear EOC should not guarantee the delivery of data carried over the channel. 9) The clear EOC should not support retransmission of data upon error. 10) The clear EOC should not acknowledge the receipt of data by the far end of the link. 11) The clear EOC should not require a specific initialization procedure. It can be assumed to be operational whenever the two modems are in synchronization for "showtime" transport of data. 6.2 Requirements on the PMD layer for the message-oriented clear EOC In order to support the physical layer OAM protocols defined in this Recommendation, a physical layer Recommendation shall provide a full duplex data channel for support of the SNMP protocol defined in clause 6.4. 1) The clear EOC shall be a part of the protocol overhead for the particular xdsl Recommendation. 2) The clear EOC shall be available to carry traffic whenever the xdsl protocol is in a normal transmission mode (e.g., "showtime"). 3) The clear EOC shall be available regardless of the specific configuration of an xtu-c and xtu-r that are communicating. 4) The clear EOC shall be terminated in the xtu-r and the xtu-c. 5) The clear EOC shall support a bit rate of at least 4 kbit/s. 6) The clear EOC shall support delineation of messages through HDLC in order to support the link level protocol defined in clause 7.1. 7) The clear EOC should not support retransmission of data upon error. 8) The clear EOC should not require a specific initialization procedure. It can be assumed to be operational whenever the two modems are in synchronization for "showtime" transport of data. 6.3 Data link layer For the transport mechanism, an HDLC-like mechanism is defined with the characteristics detailed in the following clauses. The defined method is based on [b-iso/iec 13239]. The requirements in the following clauses apply only to the bit-oriented clear EOC. 10 Rec. G.997.1 (11/2016)
NOTE For [ G.992.3], [ G.992.4] and [ G.992.5], the data link layer uses the clear EOC messages embedded in the overhead channel as defined in clauses 7.8.2.3, 7.8.2.4 and 9.4.1.8 of [ G.992.3]. For [ G.993.2], the data link layer uses the clear EOC messages embedded in the overhead channel as defined in clauses 8.2 and 11.2.3 of [ G.993.2]. The main differences between the G.997.1 data link layer and the G.992.3/ G.993.2 clear EOC protocol are: The address field and control field is defined in clause 7.8.2.4 of [ G.992.3] or clause 8.2.4.1 of [ G.993.2]. The two first bytes of the payload are always 0816 and 0116 to indicate a clear EOC command. Each clear EOC command is acknowledged by the far end xtu. 6.3.1 Format convention The basic format convention used for messages is illustrated in Figure 6-3. Bits are grouped into octets. The bits of each octet are shown horizontally and are numbered from 1 to 8. Octets are displayed vertically and are numbered from 1 to N. The octets are transmitted in ascending numerical order. The frame check sequence (FCS) field spans two octets: Bit 1 of the first octet is the MSB and bit 8 of the second octet is the LSB (see Figure 6-4). 8 7 6 5 4 3 2 1 Octet 1 2... N Figure 6-3 Format convention 8 7 6 5 4 3 2 1 Octet 2 8 2 15 1 2 0 2 7 2 6.3.2 OAM frame structure The frame structure is as depicted in Figure 6-5. Figure 6-4 FCS mapping convention 7E16 Opening flag FF16 Address field 0316 Control field Information payload Max 510 bytes FCS Frame check sequence (first octet) FCS Frame check sequence (second octet) 7E16 Closing flag Figure 6-5 OAM frame structure The opening and closing flag sequence shall be the octet 7E16. The address and control field of the frame shall be coded as FF16 and 0316, respectively. Transparency of the information payload to the flag sequence and the frame check sequence are described below. Rec. G.997.1 (11/2016) 11
6.3.3 Octet transparency In this approach, any data that is equal to 7E16 (011111102) (flag sequence) or 7D16 (control escape) shall be escaped as described below. After frame check sequence (FCS) computation, the transmitter examines the entire frame between the two flag sequences. Any data octets which are equal to the flag sequence (7E16) or the control escape (7D16) are replaced by a two-octet sequence consisting of the control escape octet followed by the original octet Exclusive-OR'ed with hexadecimal 0x20 (this is bit 5 complemented, where the bit positions are numbered 76543210). In summary, the following substitutions are made: a data octet of 7E16 is encoded as two octets 7D16, 5E16; a data octet of 7D16 is encoded as two octets 7D16, 5D16. On reception, prior to FCS computation, each control escape octet (7D16) is removed, and the subsequent octet is exclusive-or'ed with hexadecimal 2016 (unless the following octet is 7E16, which is the flag, and indicates the end of frame, and therefore an abort has occurred). In summary, the subsequent substitutions are made: a sequence of 7D16, 5E16 is replaced by the data octet 7E16; a sequence of 7D16, 5D16 is replaced by the data octet 7D16; a sequence of 7D16, 7E16 aborts the frame. Note that since octet stuffing is used, the data frame is guaranteed to have an integer number of octets. 6.3.4 Frame check sequence The FCS field is 16 bits (2 octets) in length. As defined in [b-iso/iec 13239], it shall be the one's complement of the sum (modulo 2) of: a) the remainder of x k (x 15 + x 14 + x 13 + x 12 + x 11 + x 10 + x 9 + x 8 + x 7 + x 6 + x 5 + x 4 + x 3 + x 2 + x + 1) divided (modulo 2) by the generator polynomial x 16 + x 12 + x 5 + 1, where k is the number of bits in the frame existing between, but not including, the last bit of the final opening flag and the first bit of the FCS, excluding octets inserted for transparency; and b) the remainder of the division (modulo 2) by the generator polynomial x 16 + x 12 + x 5 + 1, of the product of x 16 by the content of the frame existing between, but not including, the last bit of the final opening flag and the first bit of the FCS, excluding octets inserted for transparency. As a typical implementation at the transmitter, the initial content of the register of the device computing the remainder of the division is preset to all binary ONEs and is then modified by division by the generator polynomial (as described above) on the information field. The one's complement of the resulting remainder is transmitted as the 16-bit FCS. As a typical implementation at the receiver, the initial content of the register of the device computing the remainder of the division is preset to all binary ONEs. The final remainder, after multiplication by 16 and then division (modulo 2) by the generator polynomial x 16 + x 12 + x 5 + 1 of the serial incoming protected bits after removal of the transparency octets and the FCS, will be 00011101000011112 (x 15 through x 0, respectively) in the absence of transmission errors. The FCS is calculated over all bits of the Address, Control, and Information payload fields of the frame. The register used to calculate the CRC shall be initialized to the value FFFF16, both at the transmitter and the receiver. The LSB of the FCS is sent first, followed by the MSB. On the receiver a message received without errors results in a CRC calculation of F0B816. 12 Rec. G.997.1 (11/2016)
6.3.5 Invalid frames The following conditions result in an invalid frame: Frames which are too short (less than 4 octets in between flags, not including transparency octets). Frames which contain a control escape octet followed immediately by a flag (i.e., 7D16, 7E16). Frames which contain control escape sequences other than 7D16, 5E16 and 7D16, 5D16. Invalid frames shall be discarded. The receiver shall immediately start looking for the beginning flag of a subsequent frame. 6.3.6 Synchronism The OAM frame structure transport is octet synchronous. Octet transport and synchronism for this transport is defined in accordance with the TC layer. 6.3.7 Time fill Inter-frame time fill shall be accomplished by inserting additional flag octets (7E16) between the closing and the subsequent opening flag on the EOC transport channel. Inter-octet time fill is not supported. 6.4 The SNMP protocol If implemented, SNMP messages shall be used as the message encoding over the HDLC data link channel defined in clause 6.2, for [ G.992.1] and [ G.992.2]; or over the clear EOC message embedded in the overhead channel for [ G.992.3], [ G.992.4], [ G.992.5] and [ G.993.2]. 6.4.1 SNMP message mapping in HDLC frames This clause applies only to Recommendations defining a bit-oriented clear EOC (e.g., [ G.992.1] and [ G.992.2]). The SNMP messages are placed directly in HDLC frames together with the protocol identifier (see Figure 6-6). The protocol identifier is two bytes ahead of the SNMP message. The two bytes contain the ethertype SNMP value 814C16 as defined in [b-ietf RFC 1700]. A single HDLC frame is used to transport each SNMP message. HDCL frame 514 bytes 7E FF 03 Information payload FCS FCS 7E Open flag Header SNMP message 508 bytes CRC Close flag 81 4C SNMP message Protocol identifier for SNMP 814C'h G.997.1_F6-6 Figure 6-6 OAM communication channel protocol over the U-interface The length of an SNMP message shall be less than or equal to 508 bytes. Rec. G.997.1 (11/2016) 13
Due to the transparency mechanism described in clause 6.3.3, the number of bytes actually transmitted between opening and closing flags may be higher than 514. 6.4.2 SNMP message mapping in clear EOC messages This clause applies only to Recommendations defining message-oriented clear EOC (e.g., [ G.992.3], [ G.992.4], [ G.992.5] and [ G.993.2]). The SNMP messages are placed directly in the clear EOC messages together with the protocol identifier (see Figure 6-7). The protocol identifier is two bytes prepended to the SNMP message. The two bytes contain the ethertype SNMP value 814C16 as defined in [b-ietf RFC 1700]. A single HDLC frame is used to transport each SNMP message. Clear EOC message 7E Ad field Cntrl field 01 Information payload FCS FCS 7E Open flag Header EOC Command indicator 81 4C Protocol identifier for SNMP 814C'h SNMP message CRC Close flag G.997.1_F6-7 Figure 6-7 OAM communication channel protocol over the U-interface The length of an SNMP message shall be less than or equal to 508 bytes. Due to the transparency mechanism described in clause 6.3.3, the number of bytes actually transmitted between opening and closing flags may be greater than 516. 6.4.3 Protocol based on SNMP The SNMP protocol as defined in [IETF RFC 1157] consists of four types of operations, which are used to manipulate management information. These are: Get Get-Next Set Trap Used to retrieve specific management information. Used to retrieve, via traversal of the MIB, management information. Used to alter management information. Used to report extraordinary events. The four operations are implemented using five types of protocol data units (PDUs): GetRequest-PDU GetNextRequest-PDU GetResponse-PDU SetRequest-PDU Trap-PDU Used to request a Get operation. Used to request a Get-Next operation. Used to respond to a Get, Get-Next, or Set operation. Used to request a Set operation. Used to report a Trap operation. If implemented, SNMP messages shall be used according to the following requirements. 14 Rec. G.997.1 (11/2016)
6.4.3.1 Use of EOC channel The ADSL or VDSL2 OAM channel will be used for sending HDLC-encapsulated SNMP messages between ADSL management entities (AMEs) or VDSL2 management entities (VMEs) at both sides of the line. An AME or VME residing in the xtu-r and xtu-c will send and interpret these SNMP messages. This ADSL or VDSL2 OAM channel is used for requests, responses, and traps, differentiated according to the SNMP PDU type. 6.4.3.2 Message format The message format specified in [ G.992.1] shall be used. That is, messages shall be formatted according to SNMP version 1. All SNMP messages shall use the community name "ADSL", that is, the OCTET STRING value: "4144534C16". This string shall be used for all Recommendations covered by this Recommendation. In all SNMP Traps, the agent-addr field (which has syntax NetworkAddress), shall always have the IpAddress value: 0.0.0.0. In all SNMP Traps, the time-stamp field in the Trap-PDU shall contain the value of an AME or VME MIB object at the time of trap generation. In any standard SNMP Trap, the enterprise field in the Trap-PDU shall contain the value of the agent's sysobjectid MIB object (sysobjectid is defined in the system group of MIB-II). 6.4.3.3 Message sizes All ADSL and VDSL2 OAM implementations shall be able to support SNMP messages of size up to and including 508 octets. 6.4.3.4 Message response time Response time refers to the elapsed time from the submission of an SNMP message (e.g., GetRequest, GetNextRequest or SetRequest message) by an AME or VME across an ADSL or VDSL2 to the receipt of the corresponding SNMP message (e.g., GetResponse message) from the adjacent AME or VME. An SNMP GetRequest, GetNextRequest, or SetRequest message is defined in this context as a request concerning a single object. The AME and VME shall support maximum response times of 1 s for 95% of all SNMP GetRequests, GetNextRequests or SetRequests containing a single object received from an adjacent AME or VME independent of the ADSL or VDSL2 interface's physical line rate. 6.4.3.5 Object value data correctness Data correctness refers to the maximum elapsed time since an object value in the ADSL or VDSL2 interface MIB was known to be current. The following specifies the requirements on the data correctness of the ADSL or VDSL2 OAM objects and the event notifications. The ADSL and VDSL2 interface MIB objects shall have the data correctness of a maximum of 30 s. The AME and VME shall support event notifications (i.e., SNMP Traps) for generic SNMP events within 2 s of the event detection by the AME. 7 Management information base (MIB) elements The management information base (MIB) contains six types of information: Fault monitoring Failures (alarm indications); Fault monitoring Threshold crossing (alert messages); Performance monitoring parameters (counters); Configuration parameters; Rec. G.997.1 (11/2016) 15
Inventory parameters; Test, diagnostic and status parameters. Figure 7-1 shows the in-service performance monitoring process. The primitives are specified in the physical layer of the G.992.x-series of Recommendations and [ G.993.2]. Defect Anomaly Primitives Failure Generate parameters Scope of G.997.1 Thresholding Current Storage Previous Recent Alarm indications Alert messages Current data Historic data G.997.1_F7-1 Figure 7-1 In-service performance monitoring process As an access node can handle a large number of xtu-cs (e.g., hundreds or perhaps thousands of ADSL or VDSL2 lines), provisioning every parameter on every xtu-c may become burdensome. In response, two modes have been created to define ADSL and VDSL2 equipment configuration data profiles, as well as a mechanism to associate these profiles to the equipment. Profile tables may be implemented in one of two ways, but not simultaneously: MODE-I: Dynamic Profiles profiles used by one or multiple ADSL/VDSL2 lines. Implementations using this mode will enable the operator of the system to dynamically create and delete profiles as needed. One or more ADSL/VDSL2 lines may be configured to share parameters of a single profile (e.g., adsllineconfprofilename = 'silver') by setting its adsllineconfprofile object to the index value of this profile. If a change is made to the profile, all lines that refer to it will be reconfigured to the changed parameters. Before a profile can be deleted or taken out of service, it shall be first unreferenced from all associated lines. MODE-II: Static profiles one profile per ADSL/VDSL2 physical line. Implementations with this mode will automatically create a profile one-for-one with each ADSL/VDSL2 line. The name of this profile is a system generated read-only object whose value is equivalent to the index of the line. The management agent in the access node will not allow the operator of the system to create/delete profiles in this mode. NOTE 1 For more details on the use of profiles, refer to [b-ietf RFC 2662]. NOTE 2 The 'data profiles' discussed in this clause are not the 'Profiles' discussed in clause 6 of [ G.993.2]. This clause discusses the use of a 'profile' for simplifying the configuration of an xdsl transceiver in the field. Clause 6 of [ G.993.2] is a discussion of a technique for defining the native capabilities (e.g., the particular subset of [ G.993.2]) supported by a particular VDSL2 transceiver. 16 Rec. G.997.1 (11/2016)
At the Q-interface, a line is configured by linking the following information to the line (see Figure 7-2): one line configuration profile (see Table 7-14) for the line; one channel configuration profile (see Table 7-16) for each downstream and each upstream bearer channel; one data path configuration profile (see Table 7-18) for each downstream and each upstream bearer channel. Configuration data Operational data Line config. profile Line failures CONFIGURATION Line thresh crossing Channel config. profile Channel thresh crossing Data path config. profile Data path failures FAULT MONITORING Data path thresh crossing Channel and Data Path Config. Profile is instanciated once per bearer channel in any direction. Same number of instances is used for reporting Operational Data. Line PM counters Channel PM counters Line test, diag. and status Channel test, diag. and status Data path PM counters PERFORMANCE MONITORING TEST, DIAG. AND STATUS Line inventory INVENTOR G.997.1_F7-2 Figure 7-2 Overview of the MIB elements provided for each line Some or all of the configuration parameters contained in the line, channel and data path configuration profiles linked to the line may be written and/or read, depending on the interface under consideration: Q interface: Management interface towards the xtu-c, from the network side perspective. U-C interface: Management interface towards the xtu-c, from the xtu-r's perspective. U-R interface: Management interface towards the xtu-r, from the xtu-c's perspective. T/S interface: Management interface towards the xtu-r, from the premises side perspective. In clause 7.6, a detailed list is given of the management elements applying to each of these interfaces, with indication whether they are mandatory or optional and whether they can be read, written or both. Rec. G.997.1 (11/2016) 17
As an access node can handle a large number of lines (e.g., hundreds or perhaps thousands of ADSL or VDSL2 lines), maintaining the performance monitoring and the test, diagnostic and status information (see Figure 7-2) for every line may become burdensome. Although access to all mandatory management elements shall be supported at all times for all ports on the access node at the Q interface (see Figure 5-1), the elements may not be maintained within the management entity of the access node simultaneously for all lines at all times. Although reasonable performance shall be provided at the Q interface for access to the management elements of any line, this Recommendation does not define specific performance requirements at this interface. 7.1 Failures Any failure defined in this clause shall be conveyed to the NMS by the xtu-c (over the Q-interface) and may be conveyed by the xtu-r over the T-/S-interface after it is detected. The near-end failure detections shall be provided at the xtu-c and shall be provided at the xtu-r. The far-end failure detections shall be provided at the xtu-c (xtu-r is at the far-end), and may be provided at the xtu-r (xtu-c is at the far-end). 7.1.1 Line failures 7.1.1.1 Line near-end failures 7.1.1.1.1 Loss-of-signal (LOS) failure A LOS failure is declared after 2.5 0.5 s of contiguous LOS defect, or, if LOS defect is present when the criteria for LOF failure declaration have been met (see LOF definition below). A LOS failure is cleared after 10 0.5 s of no LOS defect. 7.1.1.1.2 Loss-of-frame (LOF) failure A LOF failure is declared after 2.5 0.5 s of contiguous SEF defect, except when an LOS defect or failure is present (see LOS definition above). A LOF failure is cleared when LOS failure is declared, or after 10 0.5 s of no SEF defect. 7.1.1.1.3 Loss-of-power (LPR) failure A LPR failure is declared after 2.5 0.5 s of contiguous near-end LPR primitive presence. An LPR failure is cleared after 10 0.5 s of no near-end LPR primitive presence. 7.1.1.1.4 Loss-of-margin (LOM) failure A LOM failure is declared when a re-initialization is triggered by a persistent near-end lom defect, except when an LOS or LOF defect or failure is present (see LOS and LOF definitions above). A LOM failure is cleared when LOS or LOF failure is declared, or after 10 0.5 s of no LOM defect. 7.1.1.2 Line far-end failures 7.1.1.2.1 Far-end loss-of-signal (LOS-FE) failure A far-end loss-of-signal LOS-FE failure is declared after 2.5 0.5 s of contiguous far-end LOS defects, or, if far-end LOS defect is present when the criteria for LOF failure declaration have been met (see LOF definition below). A far-end LOS failure is cleared after 10 0.5 s of no far-end LOS defect. 7.1.1.2.2 Far-end loss-of-frame (LOF-FE) failure A far-end loss-of-frame LOF-FE failure is declared after 2.5 0.5 s of contiguous RDI defects, except when a far-end LOS defect or failure is present (see LOS definition above). A far-end LOF failure is cleared when far-end LOS failure is declared, or after 10 0.5 s of no RDI defect. 18 Rec. G.997.1 (11/2016)
7.1.1.2.3 Far-end loss-of-power (LPR-FE) failure A far-end loss-of-power LPR-FE failure is declared after the occurrence of a far-end LPR primitive followed by 2.5 0.5 s of contiguous near-end LOS defects. A far-end LPR failure is cleared after 10 0.5 s of no near-end LOS defect. 7.1.1.2.4 Loss-of-margin (LOM-FE) failure A far-end loss-of-margin LOM-FE failure is declared when a re-initialization is triggered by a persistent far-end lom defect, except when an LOS-FE or LOF-FE defect or failure is present (see LOS and LOF definitions above). A far-end LOM failure is cleared when far-end LOS or LOF failure is declared, or after 10 0.5 s of no far-end LOM defect. 7.1.1.3 Line initialization (LINIT) failure If the line is forced to the L0 state (or into loop diagnostic mode) and an attempt to reach the L0 state (or to successfully complete the loop diagnostic procedures) fails (after a vendor discretionary number of retries and/or within a vendor discretionary timeout), then an initialization failure occurs. An initialization failure cause and last successful transmitted state are given by the line initialization failure (see clause 7.5.1.6). A line initialization failure shall be conveyed to the NMS by the xtu-c (over the Q-interface) and should be conveyed to the NMS by the xtu-r (over the T-/S-interface) after it is detected. 7.1.2 Channel failures No channel failures are defined. 7.1.3 STM data path failures The STM data path failures are for further study. 7.1.4 ATM data path failures 7.1.4.1 ATM data path near-end failures 7.1.4.1.1 No cell delineation (NCD) failure An NCD failure is declared when an NCD anomaly persists for more than 2.5 0.5 s after the start of showtime. An NCD failure terminates when no NCD anomaly is present for more than 10 0.5 s. 7.1.4.1.2 Loss of cell delineation (LCD) failure An LCD failure is declared when an LCD defect persists for more than 2.5 0.5 s. An LCD failure terminates when no LCD defect is present for more than 10 0.5 s. 7.1.4.2 Asynchronous Transfer Mode (ATM) data path far-end failures 7.1.4.2.1 Far-end no cell delineation (NCD-FE) failure An NCD-FE failure is declared when an NCD-FE anomaly persists for more than 2.5 0.5 s after the start of showtime. An NCD-FE failure terminates when no NCD-FE anomaly is present for more than 10 0.5 s. 7.1.4.2.2 Far-end loss of cell delineation (LCD-FE) failure An LCD-FE failure is declared when an LCD-FE defect persists for more than 2.5 0.5 s. An LCD-FE failure terminates when no LCD-FE defect is present for more than 10 0.5 s. Rec. G.997.1 (11/2016) 19