Network Exposure Layer for Federated Cross-Network API Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional networking systems face challenges in enabling easy communication between disparate networks and secure, automatic device/application setup for remote connectivity, particularly in work-from-home scenarios, due to the lack of network and program application convergence and the need for significant user interaction.
Innovation Solution
A network-as-a-platform (NaaP) ecosystem with a network exposure layer (NEL) that federates multiple application programming interfaces (APIs), allowing seamless access to capabilities across networks through a centralized controller, enabling secure and automatic device/application setup without user interaction.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional networking systems use separate APIs for different networks, then each network maintains its own standards and security, but communication between disparate networks becomes complex and difficult
Solution Approach 1:
The patent implements a universal API framework that enables multiple networks to communicate through a common interface. The system defines standardized API contracts that work across different network types (5G, Wi-Fi, Ethernet, etc.), allowing a single application to interact with diverse networks without needing network-specific implementations. This universality reduces communication complexity while maintaining the security and reliability of individual networks through abstraction.
Solution Approach 2:
The patent introduces an intermediary layer (the API framework and service discovery mechanism) that mediates between applications and disparate networks. This intermediary handles the complexity of network-specific protocols and security requirements, translating them into uniform API calls. The service discovery component acts as a mediator that automatically matches applications with suitable networks, eliminating the need for manual configuration and reducing communication complexity.
2Adaptability or versatility
If employees connect corporate devices remotely, then work-from-home capability is enabled, but significant user interaction and IT support are required for device setup
Solution Approach 1:
The patent implements self-service capabilities where the system automatically discovers available networks, selects appropriate connections, and configures devices without user intervention. The service discovery mechanism autonomously identifies suitable networks based on application requirements and network capabilities, then automatically establishes connections. This eliminates the need for manual setup steps and IT support interaction, making remote connectivity as easy as plugging in a device.
Solution Approach 2:
The patent performs preliminary actions by pre-configuring API contracts and service descriptions that enable automatic connection establishment. Network services are advertised in advance with their capabilities and requirements, allowing the system to prepare connection parameters before actual connection needs arise. This preliminary setup of the API framework and service registry eliminates the need for real-time configuration during device setup, greatly simplifying the user experience.
3Reliability
If network APIs follow different standards body specifications, then each network maintains its own protocols, but convergence and easy communication between networks is hindered
Solution Approach 1:
The patent segments the network communication architecture into distinct layers: network-specific protocol layers that maintain their own integrity, and a universal API layer that enables convergence. Each network type (5G, Wi-Fi, Ethernet) maintains its own protocol stack and security mechanisms, ensuring protocol integrity. The universal API framework sits above these segments, providing a common interface that translates between different network protocols, thereby enabling convergence without compromising individual network reliability.
Data Source
AI summary
A network-as-a-platform (NaaP) ecosystem includes a network exposure layer (NEL). The NEL includes a plurality of federated application programming interfaces (APIs) having at least a first federated API and a second federated API different from the first federated API. The NaaP ecosystem further includes a first network in operable communication with the NaaP ecosystem through the first federated API of the NEL, and a second network, different from the first network, in operable communication with the NaaP ecosystem through the second federated API of the NEL. The NEL enables the second network access to at least one capability of the first network.