1、 International Telecommunication Union ITU-T G.983.2TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Amendment 1(03/2006) SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS Digital sections and digital line system Optical line systems for local and access networks ONT management a
2、nd control interface specification for B-PON Amendment 1: Omnibus improvements for OMCI ITU-T Recommendation G.983.2 (2005) Amendment 1 ITU-T G-SERIES RECOMMENDATIONS TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS G.100G.199 GENERAL CHAR
3、ACTERISTICS 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
4、METALLIC LINES G.400G.449 COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY G.450G.499 TRANSMISSION MEDIA 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 for optical fibre
5、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 systems G.950G.959 D
6、igital 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 Access networks G.990G.999 QUALITY OF SERVICE AND PERFORMANCE GENERIC AND USER-RELATED ASPECTS G.1000G
7、.1999 TRANSMISSION MEDIA CHARACTERISTICS G.6000G.6999 DATA OVER TRANSPORT GENERIC ASPECTS G.7000G.7999 ETHERNET OVER TRANSPORT ASPECTS G.8000G.8999 ACCESS NETWORKS G.9000G.9999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. G.983.2 (2005)/Amd.1 (03/2006) i ITU-T R
8、ecommendation G.983.2 ONT management and control interface specification for B-PON Amendment 1 Omnibus improvements for OMCI Summary This amendment includes assorted improvements and corrections for the ONT management and control interface Recommendation, ITU-T Rec. G.983.2 (2005). The major topics
9、include: Voice over Internet Protocol (VoIP) management; ONT equipment management; ONT power shedding; ONT remote debug; Test command extensions; Video ANI enhancements; Protocol Implementation Conformance Statement. In addition to these items, there are several minor corrections of editorial errors
10、 in the Recommendation. Source Amendment 1 to ITU-T Recommendation G.983.2 (2005) was approved on 29 March 2006 by ITU-T Study Group 15 (2005-2008) under the ITU-T Recommendation A.8 procedure. Keywords B-PON, G-PON, management, optical. ii ITU-T Rec. G.983.2 (2005)/Amd.1 (03/2006) FOREWORD The Inte
11、rnational Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. 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 Recommend
12、ations 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 ITU-T study groups which, in turn, produce Recommendations on these topics. The appr
13、oval of ITU-T Recommendations is covered by the procedure laid down in 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 “Administrat
14、ion“ 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
15、 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 req
16、uired of any party. INTELLECTUAL PROPERTY 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 Intelle
17、ctual 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. Howev
18、er, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. ITU 2006 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. IT
19、U-T Rec. G.983.2 (2005)/Amd.1 (03/2006) iii CONTENTS Page 1 Introduction 1 1.1 Purpose and Scope 1 2 Modifications and additions to ITU-T Rec. G.983.2 (2005) 1 2.1 Modifications to clause 3 1 2.2 New clause 4.4 2 4.4 Voice over IP management 2 2.3 Modifications to clause 5.2. 3 2.4 Modifications to
20、clause 5.3. 3 2.5 Modifications to clause 6.1. 3 2.6 Modifications to clause 6.2. 6 2.7 Modification to clause 7.1 ONT equipment management 11 2.8 Modifications to clause 7.1.1 ONTB-PON12 2.9 Modifications to clause 7.1.2 ONT Data 12 2.10 Modifications to clause 7.1.3 Subscriber Line Cardholder 12 2
21、.11 Modification to clause 7.1.4 Subscriber line card 17 2.12 Modifications to clause 7.1.5 PON IF line cardholder. 19 2.13 Modifications to clause 7.1.6 PON IF line card . 19 2.14 Modifications to clause 7.1.7 Software image . 19 2.15 Add new clauses 7.1.9, 7.1.10, 7.1.11, 7.1.12 and 7.1.13 21 2.16
22、 Modification to clause 7.2.1 PON physical path termination point . 28 2.17 Modification to clause 7.2.2 ANI . 28 2.18 Modification to clause 7.2.4 T-CONT buffer. 28 2.19 Modification to subclauses within clause 7.3. 29 2.20 Modifications to clause 7.3.26 Physical path termination point POTS UNI 30
23、2.21 Modifications to clause 7.3.29 MAC bridge service profile 30 2.22 Modifications to clause 7.3.31 MAC bridge port configuration data. 30 2.23 Modifications to clause 7.3.49 VLAN tagging operation configuration data . 30 2.24 Modifications to clause 7.3.51 MAC bridge port filter preassign table .
24、 31 2.25 Modifications to clause 7.3.53 Physical path termination point video ANI 31 2.26 Modifications to clause 7.3.62 802.11 PHY FHSS DSSS IR tables 32 2.27 Modifications to clauses 7.3.73-7.3.76 and 7.3.94. 32 2.28 Modifications to clause 7.3.95 802.1p mapper service profile. 32 2.29 New subclau
25、ses to clause 7.3 . 32 2.30 Modifications to clause 7.5.1 Priority QueueB-PON. 67 2.31 Modifications to clause 7.5.5 Traffic scheduler . 68 2.32 Modifications to clause 9 ONT management and control protocol . 69 iv ITU-T Rec. G.983.2 (2005)/Amd.1 (03/2006) Page 2.33 New clause 9.1.10 Test result enu
26、meration 70 2.34 Modifications to Appendix I OMCI common mechanisms and services. 70 2.35 Modifications to clause I.2.1 Start-up phase of ONT. 70 2.36 Modifications to clause I.2.3 On-demand equipment provisioning (formerly Subscriber line card provisioning/deprovisioning) 71 2.37 Modifications to A
27、ppendix II OMCI message set 71 2.38 Modifications to clause II.2.1 Create . 71 2.39 Modifications to clause II.2.27 Test. 71 2.40 Modifications to clause II.2.45 Test result . 72 2.41 Add new Appendix VII 74 ITU-T Rec. G.983.2 (2005)/Amd.1 (03/2006) 1 ITU-T Recommendation G.983.2 ONT management and
28、control interface specification for B-PON Amendment 1 Omnibus improvements for OMCI 1 Introduction 1.1 Purpose and Scope This amendment is intended to outline the requirements and recommended implementation of the OMCC management for a variety of new features supported in ONTs, including Voice over
29、IP (VoIP) service, equipment management, power shedding, remote debug, extended test commands, and video ANI enhancements. The primary focus of this amendment is the definition of new standard OMCC managed entity objects and attributes, and expected behaviour of those objects. 2 Modifications and ad
30、ditions to ITU-T Rec. G.983.2 (2005) 2.1 Modifications to clause 3 Add the following new abbreviations alphabetically to clause 3: AID Access Identifier ASCII American Standard Code for Information Interchange ASCII string A sequence of ASCII encoded characters, terminated by the NULL character (0x0
31、0) CID Customer/Caller Identification DHCP Dynamic Host Configuration Protocol LOS Loss of Signal RTCP RTP Control Protocol RTP Real-Time Transport Protocol SIP Session Initiation Protocol TCP Transmission Control Protocol TLS Transport Layer Security TOS Type of Service UDP User Datagram Protocol V
32、oIP Voice over IP 2 ITU-T Rec. G.983.2 (2005)/Amd.1 (03/2006) 2.2 New clause 4.4 Add the following new clause 4.4: 4.4 Voice over IP management While OMCI is always used to manage PON service and ONT equipment, VoIP service may optionally be managed by means external to OMCI. This allows operators m
33、ore flexibility in choosing how to manage their overall VoIP service regardless of the access technology involved. VoIP service on an ONT may be managed via one of two paths: 1) OMCI Path OMCI has full view and control of all VoIP service attributes. 2) IP Path OMCI is only used to configure attribu
34、tes that allow non-OMCI based control of VoIP service attributes. Specifically, if the OMCI path is used to manage VoIP service, all of the managed entities defined here may be read and/or written. If the IP path is used to manage SIP VoIP service, only the following MEs may be read and/or written:
35、IP Host Config Data; IP Host Monitoring Data; VoIP Config Data; PPTP POTS UNI; Call Control PM History Data; RTP Monitoring Data; SIP Call Initiation Performance Monitoring History Data; SIP Agent Monitoring Data; SIP Config Portal; VoIP Line Status. If the IP path is used to manage H.248 VoIP servi
36、ce, only the following MEs may be read and/or written: IP Host Config Data; IP Host Monitoring Data; VoIP Config Data; PPTP POTS UNI; Call Control PM History Data; RTP Monitoring Data; MGC Monitoring Data; H.248 Config Portal; VoIP Line Status. ITU-T Rec. G.983.2 (2005)/Amd.1 (03/2006) 3 2.3 Modific
37、ations to clause 5.2 Modify items b and c, and add new items to the list of MEs as follows: b) Cardholder (formerly “Subscriber Line Cardholder“); c) Circuit pack (formerly “Subscriber Line Card“); o) Equipment extension package; p) Physical Path Termination Point Video ANI; q) Physical Path Termina
38、tion Point Video UNI; r) Physical Path Termination Point ISDN UNI; s) VoIP Config Data; t) SIP Agent Config Data. 2.4 Modifications to clause 5.3 Add the following new items to the list of MEs in this clause: z4) IP Host PM History Data; z5) SIP Agent Monitoring Data; z6) SIP Call Initiation PM Hist
39、ory Data; z7) RTP Monitoring Data; z8) Call Control PM History Data; z9) MGC Monitoring Data. 2.5 Modifications to clause 6.1 Modify the following lines in Table 1 to read as follows: Managed entity Required/ Optional Description Defined in Section PON IF Line Card Deprecated Used for the PON line c
40、ard plug-in, only used if PON interface is implemented on a plug-in unit. This managed entity is deprecated in favour of the generalized circuit pack ME. 7.1.6 PON IF Line Cardholder Deprecated Used for the PON line card plug-in slot, only used if PON interface is implemented on a plug-in unit. This
41、 managed entity is deprecated in favour of the generalized cardholder ME. 7.1.5 Software image R Used for the software image of the ONT or its components that contain independently manageable software. 7.1.7 Circuit pack (formerly “Subscriber Line card“) CR (Note) Used for a plug-in circuit pack mod
42、ule. Can also represent a virtual circuit pack to distinguish types of ports in an integrated ONT. 7.1.4 Cardholder (formerly “Subscriber Line Cardholder“) CR (Note) Used for a circuit pack plug-in slot. Can also represent a virtual cardholder to distinguish types of ports in an integrated ONT. 7.1.
43、3 4 ITU-T Rec. G.983.2 (2005)/Amd.1 (03/2006) Add the following new entries to Table 1 and change the Note at the end of the table as follows: Managed Entity Required/ Optional Description Defined in Section IP Host Config Data CR Used to define the internet protocol service that may be used with a
44、MAC Bridge Port. Member of IPHostData group. 7.3.98 IP Host PM History Data O Used to hold PM counters and alarms for the IP Host. Member of IPHostData group. 7.3.99 TCP/UDP Config Data CR Used for the TCP or UDP configuration for a TCP/UDP service. Member of IPHostData group. 7.3.100 Network Addres
45、s CR Used to bind a network address (URI, IP Address) to its associated security method. Member of IPHostData group. 7.3.116 VoIP Config Data CR Used to discover VoIP signalling protocols supported and select a VoIP signalling to use. Also used to select a VoIP configuration method. Member of VoIPDa
46、ta group. 7.3.101 VoIP Voice CTP CR Used for VoIP voice channel termination point. Member of VoIPData group. 7.3.110 Call Control PM History Data O Used for call control performance monitoring history. Member of VoIPData group. 7.3.111 VoIP Line Status O Used for VoIP line status that relates to a P
47、OTS port. Member of VoIPData group. 7.3.114 VoIP Media Profile CR Used to define codec and other media selection criteria. Member of VoIPData group. 7.3.107 RTP Profile Data CR Used for RTP configuration for VoIP service. 7.3.108 RTP Monitoring Data O Used to hold the last completed 15-minute interv
48、al PM data for RTP. Member of VoIPData group. 7.3.109 Network Dial Plan Table O Used to support network defined dial plans. Member of VoIPData group. 7.3.112 VoIP Application Service Profile O Used for VoIP calling feature services. Member of VoIPData group. 7.3.113 VoIP Feature Access Codes O Used
49、to define feature access codes for a POTS port. Member of VoIPData group. 7.3.115 Authentication Security Method O Used for the user id/password configuration to associate a session used between the client and destination server. 7.3.117 ITU-T Rec. G.983.2 (2005)/Amd.1 (03/2006) 5 Managed Entity Required/ Optional Description Defined in Section SIP Config Portal CR Used to view SIP configuration when the IP path is being used to manage SIP. Member of SIPrelatedData group. 7.3.102 SIP Agent Config Data CR
