What is OMCI?
OMCI stands for ONU Management and Control Interface. It is the management protocol an OLT (Optical Line Terminal) uses to configure, manage, and monitor the ONUs and ONTs sitting at the subscriber end of a GPON. OMCI was first specified in ITU-T G.984.4 for GPON and is now defined in the technology-independent recommendation ITU-T G.988, which also covers XG-PON, XGS-PON, and NG-PON2.
In short, OMCI is how a single OLT brings hundreds of remote ONUs to life: turning up services, allocating bandwidth, collecting performance data, and raising alarms, all without a technician touching the device in the field.
Where OMCI sits in a GPON
A GPON (Gigabit Passive Optical Network) connects one OLT in the central office to many ONUs through a passive optical splitter. There is no powered equipment between the two ends, so all management has to travel in-band over the fiber itself. That is the job of OMCI.
OMCI messages flow across a dedicated OMCC (ONU Management and Control Channel). The OMCC is carried in its own GEM port (GPON Encapsulation Method port) inside the same downstream and upstream traffic the ONU uses for subscriber data. The relationship is strictly master-slave: the OLT is the master and issues every command, and the ONU is the slave that responds. An ONU never initiates a configuration change on its own.
The Managed Entity model
OMCI does not send raw CLI or vendor-specific blobs. Instead it models every function of the ONU as a Managed Entity (ME). Each ME has attributes the OLT can get and set, plus actions, alarms, and counters. The full set of MEs forms a structured MIB that both ends agree on, which is what lets an OLT manage ONUs from different vendors in a consistent way.
Common Managed Entities include:
- ONU-G e ONU2-G: the ONU itself, its capabilities and overall state.
- ANI-G: the access network interface, the PON-side optical port.
- UNI entities (for example PPTP Ethernet UNI): the subscriber-facing ports.
- T-CONT: the upstream transmission container used for bandwidth scheduling.
- GEM Port Network CTP: the connection termination point that maps user traffic onto GEM ports.
- MAC Bridge e VLAN tagging MEs: how the ONU switches and tags subscriber frames.
What OMCI does
Through these Managed Entities, OMCI handles the full lifecycle of an ONU:
- Provisioning: creating T-CONTs, GEM ports, bridges, and VLAN mappings so a new subscriber gets the right services.
- Bandwidth setup: binding T-CONTs to the DBA (dynamic bandwidth allocation) policy so upstream capacity is shared fairly.
- Performance monitoring (PM): reading counters for errors, traffic, and optical levels over 15-minute and 24-hour intervals.
- Alarms and AVCs: the ONU reports fault alarms and Attribute Value Change notifications, so the OLT learns about loss of signal, link faults, or status changes.
- Software download: OMCI defines a windowed image-download flow to upgrade ONU firmware remotely.
OMCI vs EPON OAM
OMCI belongs to the ITU-T G.984 and G.988 GPON family. EPON (Ethernet PON) is a different standard defined by the IEEE in 802.3ah and 802.3av, and it does not use OMCI. EPON manages its ONUs with Ethernet OAM extensions, often paired with vendor mechanisms such as DBA reporting and proprietary OAM. So if you are working in GPON, XG-PON, or XGS-PON you use OMCI, and if you are working in EPON or 10G-EPON you use OAM. Knowing which world you are in tells you which management toolset applies.
Why it matters for open access networks
Because OMCI is a standard ME model rather than a vendor protocol, it is the foundation for multi-vendor access networks where the OLT, the ONUs, and the network operating system can come from different suppliers. An operator can run a standards-based OLT with ONUs from several vendors and still manage them through one consistent interface.
In an open PON, the OLT and its OMCI function are one element; the routing and aggregation layer above them is where IP Infusion fits. OcNOS-SP runs the open broadband routing stack, OLT aggregation, middle-mile SR-MPLS transport, and BGP internet edge, on open whitebox hardware, so operators can pair their choice of OLT and ONU vendors with a standards-based broadband and access network. The result is a PON that is easier to automate, monitor, and scale across multi-vendor hardware.