ITUT 984.4

transcript

ITU-T Recommendation G.984.4

Gigabit-capable Passive Optical Networks ( G-PON ) : ONT management and control interface specification

Reference models and terms

6.1 OMCI in ITU-T Rec. G.984.2The architecture reference model is in ITU-T Rec. G.984.2 .While this document provides some minimal modelling for ONUs with service interfaces ,detailed OMCI support for ONUs with 802.11 and xDSL interface is in ITU-T Recs G.983.9 and G.983.10 . ( OMCI = ONT management and control interface )

6.2 ONT/ONU functions

access network line termination function (AN-LT)user network interface line termination function (UNI-LT)service multiplexing and de-multiplexing function (Service MUX and DEMUX).

6.3 VP/VC Mux functionality in the ONT In ITU-T Rec. G.984.3, the end-to-end G-PON system (i.e., OLT, ODN and ONT) can function as an ATM VP or VC cross-connection.

6.4 Encapsulation in GEM frameAs the GEM is embedded in the PON section, it is independent of the types of UNIs . The UNI traffic is always encapsulated in GEM frames .(GEM = G-PON encapsulation method)

6.5 Support of Multicast connectionWhile a Port-ID is assigned to a T-CONT in a unicast connection, a Port-ID is shared by multiple T-CONTs in a multicast connection.(T-CONT = Transmission Container)

Requirements of the management interface specifications

The OMCI is used by the OLT to control an ONT. This protocol allows the OLT to:

establish and release connections across the ONTmanage the UNIs at the ONTrequest configuration information and performance statisticsautonomously inform the system operator of events such as link failures

The OMCI protocol is asymmetric: the controller in the OLT is the master and the one in the ONT is the slave.The OMCI requirements given in this Recommendation are needed to manage the ONT in the following areas:

configuration managementfault managementperformance management security management

7.1 Configuration managementIt involves the following:

Configuration of equipmentConfiguration of the UNIsConfiguration of the VP Network CTP-Gs, ATM VP Cross-Connections, and GEM Port Network CTPsConfiguration of Interworking Termination PointsConfiguration of the OAM flows

Configuration of the physical portsConfiguration of AAL profilesConfiguration of service profilesConfiguration of traffic descriptorsConfiguration of GAL profiles( CTP = Connection Termination Point )( AAL = ATM Adaptation Layer )( GAL = GEM Adaptation Layer )

For ONT that supports ATM mode

ANI (G-PON)

UNI (not ATM)

ANI (G-PON)

For cases as the supports of ONUs with xDSL interface

7.2 Fault managementThe ONT supports limited fault management only.

ONT-G;Subscriber Line Cardholder;Subscriber Line Card;PON IF Line Card-G;Physical Path Termination Point ATM UNI;

Physical Path Termination Point Ethernet UNI;Physical Path Termination Point CES UNI;Physical Path Termination Point ISDN UNI;Physical Path Termination Point POTS UNI;Physical Path Termination Point Video UNI;Physical Path Termination Point Video ANI;Physical Path Termination Point ADSL UNI;Physical Path Termination Point VDSL UNI;

TC AdapterB-PON;ATM Interworking VCC Termination Point;GEM Interworking Termination Point;VP Network CTP-G;VC Network CTP-G;GEM Port Network CTP;ONU-G.

7.3 Performance managementThe ONT has only limited performance monitoring.

UPC Disagreement Monitoring History DataB-PON;AAL1 Protocol Monitoring History DataB-PON;AAL5 Protocol Monitoring History DataB-PON;Ethernet Performance Monitoring History Data;Ethernet Performance Monitoring History Data 2;

CES Physical Interface Monitoring History Data;TC Adapter Protocol Monitoring History Data;AAL 2 CPS Protocol Monitoring History Data B-PON;AAL 2 SSCS Protocol Monitoring History Data B-PON;Priority Queue-G;MAC Bridge PM History Data;MAC Bridge Port PM History Data;

Voice PM History Data;VP PM History Data;VC PM History Data;ICMP PM History Data1;ICMP PM History Data2IP Router PM History Data1;IP Router PM History Data2;802.11 Counters;

GEM Port Protocol Monitoring History Data;GAL TDM Protocol Monitoring History Data;GAL Ethernet Protocol Monitoring History Data;ADSL ATU-C Performance Monitoring History Data;ADSL ATU-R Performance Monitoring History Data;ADSL ATU-C Channel Performance Monitoring History Data;ADSL ATU-R Channel Performance Monitoring History Data;TC Adaptor Performance Monitoring History Data ADSL;VDSL VTU-O Physical Interface Monitoring History Data;

VDSL VTU-R Physical Interface Monitoring History Data;VDSL VTU-O Channel Performance Monitoring History Data;VDSL VTU-R Channel Performance Monitoring History Data.( GAL = GEM Adaptation Layer )( CPS = Common Part Sublayer )( PM = Protocol Monitoring ) ( ATU-C = ADSL Transceiver Unit, Central office end )( ATU-R = ADSL Transceiver Unit, Remote Terminal End )( VDSL = Very High Speed Digital Subscriber Line )( VTU-O = VDSL Transceiver Unit, ONU end )( VTU-R = VDSL Transceiver Unit, Remote Terminal end )

7.4 Security management The protection configuration that is defined in ITU-T Rec. G.983.5 is considered in this Recommendation. Though ITU-T Rec. G.983.6 specifies the OMCI for B-PON protection, a new scheme for G-PON protection is needed because G-PON has a different protocol stack from ‑B PON.

Protocol-independent MIB for the OMCI

This Recommendation defines a protocol necessary to support capabilities identified by ITU-T Recs G.984.2 and G.984.3.A protocol-independent MIB is used to describe the exchange of information across the OMCI.

Protocol-independent MIB for the OMCI

8.1 Managed entitiesThe protocol-independent MIB presented in this Recommendation has been defined in terms of managed entities. The managed entities are abstract representations of resources and services in an ONT. This Recommendation uses three levels for indicating the degree of compliance necessary for specific functions and managed entities associated with the OMCI specification:

Requirement (R)Conditional Requirements (CR)Option (O)

Figure 5 is a managed entity relation diagram from the

viewpoint of ONT configuration.

Figure 6 is a managed entity relation diagram from the viewpoint of user traffic.

Figure 7 shows the Managed entity relation diagram in the case of MAC bridged LAN.

Figure 8 shows the managed entity relation diagram in the case of structured CES ( circuit emulation service ).

Figure 9 shows a part of ME relation diagram in that an ONT supports 1+1 protection

function.

Figure 10 shows a part of ME relation diagram in that an ONT supports 1:1

protection function.

ITUT 984.4

Documents