2005/11/10 1

ITU-T RecommendationG.984.4

厚程

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

Section 10, 11, appendix I, II

2005/11/10 2/22

ONT Management and Control Channel (OMCC)

• OMCC is programmed by OLT via PLOAM• PLOAM

• Specified in G.984.3• Activates VPI/VCI or PortID connection

Section 10

∀

2005/11/10 3/22

OMCC (cont.)

• Performance requirements• Zero cell loss priority in ATM mode• Upstream traffic on each OMCC should not

exceeds X• Response time

• High priority protocol < 1 s• Low priority protocol < 3 s

Section 10

OLT

ONT

OMCCupstream

downstream

HPQ

2005/11/10 4/22

ONT management and control protocol

• ONT OAM packet format• 53 bytes for ATM/GEM modes• Frame field are equivalent for both modes

• Except header

Section 11

2005/11/10 5/22

ATM/GEM Header

• VPI/VCI or PortID value of OMCC for ONT

Section 11

2005/11/10 6/22

Translation correlation identifier

• Associate request with response• Request message

• OLT selects a transaction ID

• Response message• Carries transaction ID of the request

Section 11

2005/11/10 7/22

Translation correlation identifier

• MSB of Transaction correlation ID• 0: low priority • 1: high priority

• Rest of bits are not standardized• Response match problem

Section 11

OLT

ONT

rep?(id=A)

cmd1(id=A),… , cmd2(id=A)

2005/11/10 8/22

Message type

• Message type (MT)• Create, delete, get, set, …

• Acknowledgement request (AR)• Acknowledgement (AK)• Destination bit (DB)

Section 11

2005/11/10 9/22

Message type

2005/11/10 10/22

Device identifier

• For system defined in G.984.3• This field is 0x0A

Section 11

2005/11/10 11/22

Message identifier

• Indicate which managed entity is target• MS2Bytes• Profile, history data, T-CONT, PM, …• 802.11, ATM, Ethernet, ADSL, …• 280 kinds of ME listed, 65536 maximum

• Identify managed entity instance• LS2Bytes

Section 11

2005/11/10 12/22

OMCI trailer

• MS4Bytes is fixed• 32’h00000028

• LS4Bytes is 32-bit CRC• specified in Rec.I.363.5

Section 11

2005/11/10 13/22

Message contents

• 4 categories• Get, get response and set• Alarm notification• Result and reason• Test, test result and test response

• Message layout defined in Appendix II

Section 11

2005/11/10 14/22

Result and reason

• command processed successfully • command processing error • command not supported • parameter error • unknown managed entity • unknown managed entity instance • device busy • attributes failed or unknown

Section 11

2005/11/10 15/22

Alarm notification

• Support up to 224 kinds of alarms•

2005/11/10 16/22

Get, get response and set

• Attribute mask coding• Attributes

• Equipment id, OMCC version, vendor product code, security capability, mode …

2005/11/10 17/22

Get, get response and set (cont.)

2005/11/10 18/22

Message layout example

Section 11

2005/11/10 19/22

OMCI handling within ONT

• Prioritized request mechanism

Section 11

Encoded in MSB of TID

1. Check last executed TIDIdentical: place ACK onlyNot identical: execute and place ACK2. Block until outgoing queue is not full

Transmit LP till HP is empty

1

2

2005/11/10 20/22

OMCI generality

• Common mechanism• MIB resynchronization• G.983.2 (ONT Management and Control Interface Specification for ATM PON)

• Common services• Equipment management

• Addition/removal of entries to IP static routes• On demand subscriber line card provisioning, …

• Connection management• Connection set-up & tear-down of ATM, MAC

bridge service, …

Appendix I

2005/11/10 21/22

Appendix I

MAC bridge service connection set-up

2005/11/10 22/22

Appendix I

MAC bridge service connection set-up(cont.)