Optical Node API Messaging for FRU-Aware Control Plane Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Optical networks face challenges in updating control plane communication when field replaceable units (FRUs) are replaced or upgraded, as the control plane is not aware of the changed functionalities, leading to inefficiencies in inter-node communication.
Innovation Solution
Implementing an API-based communication infrastructure that allows for registering and invoking APIs on remote nodes, enabling the control plane to recognize and utilize the new functionalities of FRUs through messaging networks and application plugins.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional control plane communication protocols are used with hardcoded messages, then communication stability is maintained, but adaptability to FRU functionality changes deteriorates
Solution Approach 1:
The patent implements dynamic control plane communication by replacing hardcoded messages with an API-based system where messages are dynamically generated based on FRU capabilities. The control plane applications can dynamically discover and invoke APIs on remote nodes, allowing the communication protocol to adapt to functionality changes without requiring protocol version updates or hardcoded message definitions.
Solution Approach 2:
The patent introduces an intermediary layer (messaging framework with API registry) between control plane applications and remote nodes. This intermediary handles the complexity of API discovery, invocation, and response processing, allowing control plane applications to communicate without directly managing protocol details. The messaging framework acts as a mediator that abstracts the complexity of FRU functionality changes from the control plane applications.
2Loss of information
If control plane applications directly communicate with remote nodes, then communication simplicity is maintained, but awareness of FRU functionality changes deteriorates
Solution Approach 1:
The patent implements preliminary action by having remote nodes register their available APIs with the messaging framework before control plane applications need to communicate with them. The API registry is populated in advance with information about available functionalities, allowing control plane applications to discover and utilize new FRU capabilities without requiring real-time negotiation or manual configuration. This preliminary registration ensures control plane applications are always aware of current FRU functionalities.
Solution Approach 2:
The patent establishes feedback mechanisms where control plane applications can query the messaging framework for available APIs on remote nodes, and where remote nodes can push notifications about their capabilities. This feedback loop ensures control plane applications continuously update their knowledge of FRU functionalities, preventing information loss when FRUs are replaced or upgraded.
3Adaptability or versatility
If FRUs are replaced or upgraded, then functionality is improved, but control plane communication compatibility deteriorates
Solution Approach 1:
The patent implements universality by creating a standardized API registry and messaging framework that can handle multiple FRU types and functionalities through a common interface. The messaging framework provides universal mechanisms for API discovery, invocation, and error handling that work across different FRU implementations. This universal approach allows control plane applications to communicate with any FRU type without requiring type-specific communication logic, maintaining compatibility while enabling functionality improvements.
Solution Approach 2:
The patent uses dynamic API registration and discovery mechanisms that automatically adapt to FRU replacements or upgrades. When an FRU is replaced, the new FRU's APIs are registered with the messaging framework, and control plane applications dynamically discover and utilize the new capabilities. This dynamic approach maintains communication reliability by automatically adapting to hardware changes without requiring manual protocol updates or compatibility configurations.
Data Source
AI summary
Disclosed herein is an optical node comprising an FRU and a controller. The FRU comprises a module processor and a module memory storing a control plane application (CPA) executable by the module processor. The controller comprises an interface, a controller processor, and a controller memory storing instructions and an application that cause the controller processor to: instantiate a first network having a first client and a first server; register a plugin associated with the CPA with the first network; register an interface having a callback function and operable to communicate with the CPA via a second network; receive, by the interface via the second network, a request having a request property from the CPA; transmit the request, via the plugin, to the first client; receive a response via the first client from a remote node; and transmit, by the interface, the response to the module processor via the second network.