API Orchestration Architecture for Device-Network-Cloud Collaboration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network capability architectures in, in the 5th generation (5th generation, 5G) network, existing network capability exposure architectures, such as the common application programming interface framework (CAPIF), limit network capability exposure, making it difficult to support diversified services and device-network-cloud collaboration.
Innovation Solution
A communication system and apparatus that includes a service application programmable interface API repository function and API orchestration function, enabling devices, networks, and clouds to provide and combine APIs for diverse services, supporting device-network-cloud collaboration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a traditional network capability exposure architecture (e.g., CAPIF) is used where control plane network elements provide service APIs, then the network can provide basic services, but the network capability exposure is limited and cannot support diversified services and device-network-cloud collaboration
Solution Approach 1:
The patent introduces a unified API management platform that serves multiple functions: API registration, API combination/orchestration, API publishing, and API invocation management. This single platform handles diverse API sources (terminal devices, network devices, cloud devices, campus devices, private network devices) and provides comprehensive service support, eliminating the need for separate management systems for each device type and enabling diversified services through a universal architecture
Solution Approach 2:
The API management platform acts as an intermediary between various API providers (terminal, network, cloud, campus, private network devices) and API consumers. It receives registration requests from diverse providers, combines their APIs through orchestration functions, publishes the combined APIs, and manages invocation requests. This intermediary layer abstracts the complexity of multi-source API integration while expanding network capability exposure to support diversified services
2Adaptability or versatility
If multiple first APIs from different device types are combined to create a second API, then diversified services and device-network-cloud collaboration are supported, but the API orchestration and management complexity increases
Solution Approach 1:
The patent segments the API management process into distinct functional modules: API registration function (receiving first registration requests from various device types), API combination function (orchestrating multiple first APIs into a second API), API publishing function (making the second API available), and API invocation function (handling requests to invoke the second API). This segmentation reduces orchestration complexity by providing clear separation of concerns while enabling service diversity through coordinated module operations
Solution Approach 2:
The API management platform enables self-service through automated API registration, combination, and publishing processes. Devices can independently register their first APIs with the platform, which then automatically orchestrates them with other APIs based on service requirements, publishes the combined second API, and manages invocations. This self-service mechanism reduces manual orchestration complexity while supporting diverse service combinations
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
Embodiments of this application provide a communication system based on a network capability exposure architecture and a communication apparatus. The method includes: A terminal device, a network device, a cloud device, a campus device, or a private network device each may serve as an API provider to register a first API with an API repository function in a network; and an API orchestration function in the network may combine at least two first APIs provided by providers of a same type or different types to obtain a second API for invoking by an invoker. The method can implement a device-network-cloud collaboration function, support diversified services, and improve user experience.