Flexible Key Value Configuration for Network Control Requests
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In existing ACTN network architectures, the lack of unified service identifiers between network management systems and control systems leads to complexity, requiring physical network controllers to have multiple interfaces for identifier conversion, which hinders cross-vendor interworking and unified key value allocation.
Innovation Solution
A method for sending control requests based on a key value configuration, using a flexible key value, control object name, and universally unique identifier (UUID), to unify data structures and reduce processing complexity, enabling unified key value allocation and improved client-side key value allocation mechanisms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If physical network controller uses two sets of interfaces to interconnect with MDSC and network management system separately, then identifier conversion can be performed, but device complexity increases
Solution Approach 1:
The patent applies universality by designing a unified interface that can handle multiple types of identifiers (service identifier, UUID, IP address) through a single interface mechanism. The physical network controller uses one interface to communicate with both MDSC and network management system, eliminating the need for separate interfaces for each system while maintaining compatibility with different identifier formats.
Solution Approach 2:
The patent introduces an intermediary mechanism in the form of a unified data model and identifier conversion module. This intermediary layer translates between different identifier formats (service identifier from MDSC and UUID from network management system) without requiring separate interfaces for each system, thereby reducing interface complexity while maintaining adaptability.
2Reliability
If physical network controller allocates unique identifier after receiving service request, then service can be identified, but standard protocol compliance is violated and cross-vendor interworking cannot be implemented
Solution Approach 1:
The patent applies preliminary action by pre-defining a unified data model and identifier allocation mechanism before service requests are processed. The physical network controller pre-configures to accept both service identifiers from MDSC and UUIDs from network management system, and automatically translates between them. This preliminary setup ensures standard protocol compliance and cross-vendor compatibility without requiring post-request identifier allocation.
Solution Approach 2:
The patent uses parameter changes by dynamically selecting and translating identifier parameters based on the source system. When receiving a service request, the system changes the identifier parameter from service identifier format (MDSC) to UUID format (network management system) or vice versa. This parameter transformation enables reliable service identification while maintaining cross-vendor compatibility and standard protocol adherence.
3Reliability
If manual operations are used to implement joint management and control across IP and optical layers, then control can be established, but operation efficiency decreases
Solution Approach 1:
The patent applies self-service by implementing automated identifier translation and unified data model processing. The physical network controller automatically translates identifiers between MDSC and network management system formats, and automatically establishes control relationships across IP and optical layers without requiring manual intervention. This automation maintains reliable control establishment while significantly improving operation efficiency.
Solution Approach 2:
The patent replaces manual mechanical operations with automated software-based identifier translation and data processing mechanisms. Instead of manual configuration and control establishment, the system uses automated software modules that translate identifiers and establish control relationships programmatically. This substitution maintains control reliability while dramatically improving operational efficiency.
Data Source
AI summary
A method, an apparatus, and a system for sending a control request based on a key value configuration. The method includes generating, by a client controller, a control request, wherein having a plurality of configuration parameters, wherein the plurality of configuration parameters comprise a flexible key value, a control object name, and a universally unique identifier (UUID), where the flexible key value identifies a requested control object, and the flexible key value is determined using at least one of the control object name or the UUID, and sending, by the client controller, the control request to a server controller, where the control request indicates to the server controller to configure the control object.