Integration Platform for Network Infrastructure Orchestration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud platform infrastructure experiences connectivity issues and increased latency due to brittle connections between network devices, which are prone to failure with changes in applications or network devices, leading to inefficient modifications and configurations.
Innovation Solution
An integration platform with a service composition layer (SCL), network abstraction layer (NAL), and experience layer (EXL) provides orchestration, automation, and integration for network infrastructure, allowing for modular task execution and rollback capabilities to manage changes without affecting underlying network devices or applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If connections between network devices are made unique and specific to support application requirements, then connectivity and functionality are improved, but system reliability deteriorates because changes easily break connections
Solution Approach 1:
The patent introduces an integration platform as an intermediary layer between software applications and network infrastructure. This platform includes a service composition layer that manages connections dynamically, allowing applications to communicate with network devices through standardized interfaces rather than unique direct connections. When network devices change, the integration platform reroutes connections through the intermediary, preventing connection breakage while maintaining adaptability.
Solution Approach 2:
The patent segments the system into distinct layers: application layer, integration platform layer (with service composition layer and network abstraction layer), and network infrastructure layer. This segmentation isolates changes in each layer, so that network device modifications do not directly impact application connections. The service composition layer acts as a buffer that manages the segmented connections independently.
2Adaptability or versatility
If network devices are updated or modified to improve functionality, then system capabilities are enhanced, but connectivity issues and latency increase due to connection failures
Solution Approach 1:
The integration platform performs preliminary actions by pre-establishing standardized connection templates and protocols before network device updates occur. When network devices need updating, the platform has already prepared alternative routing paths and connection configurations, allowing seamless transitions without connection failures or latency increases. The service composition layer pre-maps application requirements to network capabilities, so updates can be applied without disrupting existing connections.
3Productivity
If direct connections are established between applications and network devices, then communication efficiency is improved, but ease of modification deteriorates because changes require reconfiguring connections
Solution Approach 1:
The patent implements universal standardized interfaces at the network abstraction layer that can serve multiple applications and network devices simultaneously. Instead of unique direct connections, the integration platform provides universal connection protocols and templates that work across different applications and network devices. This allows modifications to network devices or applications without requiring reconfiguration of individual connections, as the universal interface absorbs the changes while maintaining communication efficiency.
Data Source
AI summary
Methods, systems, and devices for network integration are described. Some systems may implement an integration platform including a service composition layer (SCL), a network abstraction layer (NAL), and one or more application programming interfaces (APIs). The integration platform may support application and network flexibility, customization, and modular design based on the SCL and NAL. For example, the SCL may receive an execution request (e.g., an intent) corresponding to a service and may parse the execution request to determine a set of modular tasks. The SCL may send a modular task (e.g., via an API) to the NAL for processing. The NAL may determine a type of infrastructure architecture (e.g., including querying for network node connections, parameters, etc.) associated with the integration platform and may modify the modular task based on the information. The NAL may execute the modular task on one or more network devices to perform the service.