1、 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 ITU-T G.988 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Amendment 2 (06/2016) SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS Digital sections and digital line system Optical line systems for local and
2、access networks ONU management and control interface (OMCI) specification Amendment 2 Recommendation ITU-T G.988 (2012) Amendment 2 ITU-T G-SERIES RECOMMENDATIONS TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS G.100G.199 GENERAL CHARACTE
3、RISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS G.200G.299 INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES G.300G.399 GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH META
4、LLIC LINES G.400G.449 COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY G.450G.499 TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS G.600G.699 DIGITAL TERMINAL EQUIPMENTS G.700G.799 DIGITAL NETWORKS G.800G.899 DIGITAL SECTIONS AND DIGITAL LINE SYSTEM G.900G.999 General G.900G.909 Parameters fo
5、r optical fibre cable systems G.910G.919 Digital sections at hierarchical bit rates based on a bit rate of 2048 kbit/s G.920G.929 Digital line transmission systems on cable at non-hierarchical bit rates G.930G.939 Digital line systems provided by FDM transmission bearers G.940G.949 Digital line syst
6、ems G.950G.959 Digital section and digital transmission systems for customer access to ISDN G.960G.969 Optical fibre submarine cable systems G.970G.979 Optical line systems for local and access networks G.980G.989 Metallic access networks G.990G.999 MULTIMEDIA QUALITY OF SERVICE AND PERFORMANCE GENE
7、RIC AND USER-RELATED ASPECTS G.1000G.1999 TRANSMISSION MEDIA CHARACTERISTICS G.6000G.6999 DATA OVER TRANSPORT GENERIC ASPECTS G.7000G.7999 PACKET OVER TRANSPORT ASPECTS G.8000G.8999 ACCESS NETWORKS G.9000G.9999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T G.988
8、(2012)/Amd.2 (06/2016) i Recommendation ITU-T G.988 ONU management and control interface (OMCI) specification Amendment 2 Summary Amendment 2 to Recommendation ITU-T G.988 (2012) includes circuit emulation service (CES) user network interface (UNI) refinements, threshold data 64-bit refinement, Open
9、Flow support, G.fast support, etc. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T G.988 2010-10-07 15 11.1002/1000/10891 1.1 ITU-T G.988 (2010) Amd. 1 2011-04-13 15 11.1002/1000/11126 1.2 ITU-T G.988 (2010) Amd. 2 2012-04-22 15 11.1002/1000/11501 1.3 ITU-T G.988 (2010) Cor.
10、 1 2012-06-13 15 11.1002/1000/11641 2.0 ITU-T G.988 2012-10-29 15 11.1002/1000/11784 2.1 ITU-T G.988 (2012) Amd. 1 2014-05-14 15 11.1002/1000/12185 2.2 ITU-T G.988 (2012) Amd. 2 2016-06-22 15 11.1002/1000/12795 * To access the Recommendation, type the URL http:/handle.itu.int/ in the address field o
11、f your web browser, followed by the Recommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T G.988 (2012)/Amd.2 (06/2016) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, inf
12、ormation and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a w
13、orldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down i
14、n WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts 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 adm
15、inistration 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 pr
16、ovisions 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 PROPERTY RIGHTSITU draws attention
17、 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 out
18、side 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 lates
19、t information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2016 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T G.988 (2012)/Amd.2 (06/2016
20、) iii Table of Contents Page 1) Clause 2, References . 1 2) Clause 9.8.1, Physical path termination point CES UNI 1 3) Clause 9.12.18, OpenFlow config data . 1 4) Clause 9.7.1, Physical path termination point xDSL UNI part 1 . 3 5) Clause 9.7.38, VDSL2 line inventory and status data part 4 6 6) Clau
21、se 9.7, xDSL services 6 6.1) New G.fast managed entity . 6 6.2) New FAST line configuration entities 7 6.3) New FAST line inventory and status entities . 20 7) Clause 9.9.1, Physical path termination point POTS UNI . 24 8) Clause 9.3.22, Dot1ag MEP . 26 9) Clause 8.1, Managed entities 27 10) Clause
22、11.2.4, Managed entity identifier 28 11) Clause 9.12.2, OLT-G 28 12) Clause 9.15.1, Physical path termination point RS232/RS485 UNI 28 13) Clause 9.15.3, RS232/RS485 performance monitoring history data 30 14) Clause 9.12.17, Threshold data 64-Bit . 31 Rec. ITU-T G.988 (2012)/Amd.2 (06/2016) 1 Recomm
23、endation ITU-T G.988 ONU management and control interface (OMCI) specification Amendment 2 1) Clause 2, References In clause 2, add the following references in appropriate order: ITU-T G.997.2 Recommendation ITU-T G.997.2 (2015), Physical layer management for G.fast transceivers. ITU-T G.9700 Recomm
24、endation ITU-T G.9700 (2014), Fast access to subscriber terminals (G.fast) Power spectral density specification. ITU-T G.9701 Recommendation ITU-T G.9701 (2014), Fast access to subscriber terminals (G.fast) Physical layer specification. 2) Clause 9.8.1, Physical path termination point CES UNI In cla
25、use 9.8.1, replace the existing text for CES loopback configuration as follows: CES loopback configuration: This attribute specifies and reports the loopback configuration of the physical interface. 0 No loopback 1 Payload loopback 2 Line loopback 3 OS-directed loopback 1 (loopback from/to PON side)
26、 4 OS-directed loopback 2 (loopback from/to CES UNI side) 5 OS-directed loopback 3 (loopback of both PON side and CES UNI side) 6 Manual button-directed loopback (read only) 7 Network-side code inband-directed loopback (read only) 8 SmartJack-directed loopback (read only) 9 Network-side code inband-
27、directed loopback (armed; read only) 10 Remote-line loopback via FDL 11 Remote-line loopback via inband code 12 Remote-payload loopback. Upon ME instantiation, the ONU sets this attribute to 0. (R, W) (mandatory) (1 byte) 3) Clause 9.12.18, OpenFlow config data Add the following new ME clause 9.12.1
28、8 to clause 9.12 as follows: 9.12.18 OpenFlow config data This managed entity contains the configuration data whose underlying transport method is OpenFlow. Instances of this managed entity are created and deleted by the OLT. 2 Rec. ITU-T G.988 (2012)/Amd.2 (06/2016) Relationships An instance of thi
29、s managed entity is associated with each instance per OpenFlow transportation channel. There might be more than one OpenFlow transportation channel per ONU. Attributes Managed entity ID: This attribute uniquely identifies each instance of this managed entity. (R, set by create) (mandatory) (2 bytes)
30、 TP type: This attribute specifies the type of ANI-side termination point associated with this managed entity. 1 GEM interworking TP (R, W, set by create) (mandatory) (1 byte) TP pointer: This attribute points to the instance of the TP associated with this OpenFlow configuration data. The type of th
31、e associated TP is determined by the TP type attribute. (R, W, set by create) (mandatory) (2 bytes) Version: This integer attribute reports the version of the OpenFlow protocol in use. The ONU should deny an attempt by the OLT to set or create a value that it does not support. The value 0 indicates
32、that no particular version is specified. (R, W, set by create) (mandatory) (1 byte) D/S OpenFlow message: This attribute specifies the D/S OpenFlow message which is carried over the OMCC channel. (R, W) (mandatory) (24N bytes) D/S forwading control: This Boolean attribute indicates the current D/S O
33、penFlow message is ready to be sent (true) or not. The default value is false. (R, W) (mandatory) (1 byte) D/S receiving status: This Boolean attribute indicates the ONU is ready to accept a new downstream packet (true) or not. The default value is false. (R) (mandatory) (1 byte) U/S OpenFlow messag
34、e: This attribute specifies the U/S OpenFlow message which is carried over the OMCC channel. (R, W) (mandatory) (24N bytes) U/S receiving control: This Boolean attribute controls the current U/S OpenFlow message is dafely received (true) or not. The default value is false. (R, W) (mandatory) (1 byte
35、) U/S forwarding status: This Boolean attribute reports the current U/S OpenFlow message is ready to be sent (true) or not. The default value is false. (R) (mandatory) (1 byte) Circuit ID: This attribute identifies the first access information of the user (R, W) (Optional) (24N byte) Remote ID: This
36、 attribute identifies the second access imformation of the user as an addition identifier to circuit ID. (R, W) (Optional) (24N byte) Administrative state: This attribute locks (1) and unlocks (0) the functions performed by the MPLS pseudowire TP. Administrative state is further described in clause
37、A.1.6. (R, W) (optional) (1 byte) Operational state: This attribute reports whether the managed entity is currently capable of performing its function. Valid values are enabled (0) and disabled (1). (R) (optional) (1 byte) Rec. ITU-T G.988 (2012)/Amd.2 (06/2016) 3 Actions Create, delete, get, get ne
38、xt, set Notifications Attribute value change Number Attribute value change Description 15 N/A 6 D/S receiving status The D/S packets receiving status has changed 78 N/A 9 U/S forwarding status A new ONU response has been loaded into the table for the OLT to retrieve 10-12 N/A 13 Op state Operational
39、 state 1416 reserved 4) Clause 9.7.1, Physical path termination point xDSL UNI part 1 Replace the PPTP xDSL UNI part 1 as follows: 9.7.1 Physical path termination point xDSL UNI part 1 This managed entity represents the point where physical paths terminate on an xDSL CO modem (xTU-C). The xDSL manag
40、ed entity family is used for ADSL, VDSL2 and FAST services. A legacy family of VDSL managed entities remains valid for ITU-T G.993.1 VDSL, if needed. It is documented in ITU-T G.983.2. The ONU automatically creates an instance of this managed entity per port: when the ONU has xDSL ports built into i
41、ts factory configuration; when a cardholder is provisioned to expect a circuit pack of the xDSL type; when a cardholder provisioned for plug-and-play is equipped with a circuit pack of the xDSL type. Note that the installation of a plug-and-play card may indicate the presence of xDSL ports via equip
42、ment ID as well as its type, and indeed may cause the ONU to instantiate a port mapping package that specifies xDSL ports. The ONU automatically deletes instances of this managed entity when a cardholder is neither provisioned to expect an xDSL circuit pack, nor is it equipped with an xDSL circuit p
43、ack. Relationships An instance of this managed entity is associated with each instance of a real or pre-provisioned xDSL port. Attributes Managed entity ID: This attribute uniquely identifies each instance of this managed entity. This two-byte number indicates the physical position of the UNI. The s
44、ix least significant bits of the first byte are the slot ID, defined in clause 9.1.5. The two most significant bits indicate the channel number in some of the implicitly linked MEs, and must be 0 in the PPTP itself. This reduces the possible number of physical slots to 64. The second byte is the por
45、t ID, with the range 1255. (R) (mandatory) (2 bytes) 4 Rec. ITU-T G.988 (2012)/Amd.2 (06/2016) Loopback configuration: This attribute represents the loopback configuration of this physical interface. 0 No loopback 1 Loopback2 a loopback at the ONU towards the OLT. The OLT can execute a physical leve
46、l loopback test after loopback2 is set. Upon ME instantiation, the ONU sets this attribute to 0. (R, W) (mandatory) (1 byte) Administrative state: This attribute locks (1) and unlocks (0) the functions performed by this managed entity. Administrative state is further described in clause A.1.6. (R, W
47、) (mandatory) (1 byte) Operational state: This attribute indicates whether or not the managed entity is capable of performing its function. Valid values are enabled (0) and disabled (1). (R) (optional) (1 byte) xDSL line configuration profile: This attribute points to an instance of the xDSL line co
48、nfiguration profiles (part 1, 2 and 3) managed entities, and if necessary, also to VDSL2 line configuration extensions (1 and 2) MEs, also to vectoring line configuration extension MEs. Upon ME instantiation, the ONU sets this attribute to 0, a null pointer. (R, W) (mandatory) (2 bytes) xDSL subcarr
49、ier masking downstream profile: This attribute points to an instance of the xDSL subcarrier masking downstream profile managed entity. Upon ME instantiation, the ONU sets this attribute to 0, a null pointer. (R, W) (mandatory) (2 bytes) xDSL subcarrier masking upstream profile: This attribute points to an instance of the xDSL subcarrier masking upstream profile managed entity. Upon ME instantiation, the ONU sets this attribute to 0, a null pointer. (R, W) (mandatory) (2 bytes) xDSL downstream PSD mask profile: This attribu
