OMCI Description Mechanism for ONT Capability Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing Optical Management and Control Interface (OMCI) in passive optical networks (PONs) faces issues such as optional or conditional components, version upgrades, and manufacturer-specific configurations, leading to inefficiencies and errors in communication between Optical Line Terminals (OLT) and Optical Network Terminals (ONTs.

Innovation Solution

Implementing an OMCI Description mechanism within network components, comprising Managed Entity Objects and Attribute Objects, which describe the supported features and attributes of the OMCI, allowing the OLT to determine and adapt message transmission to match the capabilities of individual ONTs, thereby enhancing communication efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the OMCI includes optional or conditional portions, then the OMCI can be customized for different configurations, but the OLT cannot determine which portions are supported by a particular ONT

Engineering Contradiction:
ImproveOMCI configuration adaptabilityVSAvoidONT capability information
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent applies preliminary action by having the ONT send its OMCI capability description to the OLT before the OLT attempts to manage the ONT. This allows the OLT to know in advance which OMCI portions the ONT supports, eliminating the information loss problem while maintaining configurability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback by establishing a communication mechanism where the ONT provides information about its supported OMCI portions back to the OLT. This feedback loop enables the OLT to adapt its management actions based on the actual capabilities of the connected ONT.

Inventive Principle:
Principle #23Feedback

2Adaptability or versatility

If the OMCI is frequently upgraded, then the OMCI can support new features, but the OLT and ONTs may not support upgraded versions causing communication failures

Engineering Contradiction:
ImproveOMCI feature supportVSAvoidOMCI version compatibility
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies preliminary action by having the ONT declare its OMCI version and supported features before the OLT attempts to use them. This allows the OLT to verify compatibility in advance and avoid communication failures due to version mismatches.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements dynamics by making the OMCI configuration adaptive rather than static. The OLT can dynamically adjust its management actions based on the actual OMCI version and capabilities reported by the ONT, allowing the system to work reliably across different versions.

Inventive Principle:
Principle #15Dynamics

3Manufacturing precision

If the OMCI is customized for one manufacturer's equipment, then the OMCI can be optimized for that equipment, but the OMCI will not recognize equipment from other manufacturers

Engineering Contradiction:
ImproveOMCI configuration precisionVSAvoidMulti-manufacturer compatibility
Core Design Contradiction:
Manufacturing precisionVSAdaptability or versatility

Solution Approach 1:

The patent applies universality by creating a standardized OMCI capability description mechanism that works across different manufacturers. Each ONT describes its own capabilities using the same standardized format, allowing any OLT to adapt to any ONT regardless of manufacturer while maintaining optimized control.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent implements local quality by allowing each ONT to specify its unique capabilities and configurations through its OMCI description. This enables the OLT to treat each ONT individually with the appropriate level of customization while using a universal communication framework.

Inventive Principle:
Principle #3Local quality

4Manufacturing precision

If manual configuration updates are required for different ONT configurations, then the OMCI can be precisely configured, but the system complexity and time required for configuration increases

Engineering Contradiction:
ImproveOMCI configuration accuracyVSAvoidConfiguration time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent applies self-service by having the ONT automatically generate and send its own capability description to the OLT. This eliminates the need for manual configuration updates, as the ONT provides its own configuration information automatically, reducing both time and human intervention while maintaining precision.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent implements preliminary action by having the ONT prepare and transmit its capability information before the OLT needs to configure or manage it. This preliminary provision of configuration data eliminates the need for time-consuming manual setup while ensuring accurate configuration from the start.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8121479B2Optical network terminal management and control interface (OMCI) containing a description of the OMCI
Publication Date: 2012.02.21 FUTUREWEI TECHNOLOGIES INC
  • US8121479B2 patent drawing
  • US8121479B2 patent drawing
  • US8121479B2 patent drawing

AI summary

A network component is disclosed that includes a memory comprising a data structure comprising an optical network terminal management and control interface (OMCI) comprising a plurality of managed entities (MEs), wherein one of the MEs is a description of the OMCI. Also disclosed is a network component comprising a processor configured to implement a method comprising promoting the sending of an OMCI Description to an optical line terminal (OLT), wherein the OMCI Description comprises an OMCI Object, whose instance describes the types of MEs supported by an OMCI, a plurality of Managed Entity Objects, whose instances describe each ME supported by the OMCI, and a plurality of Attribute Objects, whose instances describe each attribute supported by the OMCI.