Federated API Translation for Network Component Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional networks require manual configuration of unique APIs for each component, leading to inefficiencies and vulnerabilities due to the need for manual linking of components and applications, which complicates network traffic management and exposes the network to failures.
Innovation Solution
An API integration module detects active components, determines their APIs, and generates a federated API for intra-network communications, allowing API calls to be translated into a language-agnostic format like JSON, enabling human-readable and modifiable messages for configuring network components.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual configuration of unique APIs for each network component is used, then each component can be configured with its specific API requirements, but the network configuration process becomes cumbersome and inefficient
Solution Approach 1:
The patent introduces a translation module as an intermediary between network components with different APIs and the unified federated API. This mediator automatically translates between various proprietary APIs (Cisco, Nokia, Juniper) and the standard JSON-based federated API, eliminating manual configuration complexity while maintaining adaptability to different hardware vendors and component types
Solution Approach 2:
The system implements a universal federated API that serves multiple network components with different native APIs through a single standardized interface. The translation module enables one API to perform multiple functions by adapting to various underlying component APIs, reducing configuration complexity while maintaining versatility across different network hardware
2Reliability
If manual linking of components to destinations is performed, then each component can be explicitly connected to its service destinations, but the process is time-consuming and exposes the network to vulnerabilities
Solution Approach 1:
The translation module performs self-service by automatically detecting network components, discovering their native APIs, and configuring the translation mappings without manual intervention. The system autonomously builds the translation table by analyzing API calls from network components, eliminating both manual configuration time and the vulnerabilities associated with manual setup
Solution Approach 2:
The system performs preliminary actions by pre-configuring the translation module to automatically detect and register network components before they need to communicate. The translation table is built in advance through automatic API analysis, so when components need to communicate, the translation infrastructure is already in place and ready to handle the traffic
3Ease of operation
If conventional compilers for modeling languages are used, then data can be monitored in a human-readable fashion, but runtime operation is compromised with valuable data excluded
Solution Approach 1:
The patent changes the fundamental parameter of data format by translating between proprietary modeling languages (YANG, TOSCA) and a unified JSON-based federated API. This parameter change enables human-readable monitoring while preserving complete data through automatic translation, eliminating the trade-off between readability and data completeness that plagues conventional compilers
4Adaptability or versatility
If multiple proprietary APIs are implemented for different network components, then each component can operate according to its specific requirements, but the network becomes difficult to manage and scale
Solution Approach 1:
The translation module serves as a mediator that enables component compatibility across different vendors and technologies. By automatically translating between proprietary APIs and the federated API, the system maintains adaptability to Cisco, Nokia, Juniper, and other components while dramatically improving network management efficiency through a single standardized interface
Solution Approach 2:
The system segments the API translation function into a dedicated translation module that operates independently from network components. This segmentation allows the translation infrastructure to be maintained and updated without affecting individual components, improving overall system productivity and manageability while preserving component compatibility
Data Source
AI summary
Systems and methods are disclosed for improving data modeling and translating. The system receives network-related data from external systems, wherein the data is formatted in various modeling languages corresponding to the system or network components from which it is transmitted. The system parses and extracts the network-related data for identifying parameters within the data, wherein the parameters correspond to the system or network component's operational status. The system translates the extracted data to a human-readable format for displaying the data to a system user and allowing the user to modify or provide additional parameters. The system generates a new instance of the network-related data including the user-provided parameters, wherein the new instance is translated into a format in accordance with the modeling language of the initially received network-related data.