CAPIF Core Entity API Sharing Across Multiple PLMNs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing CAPIF system architecture is limited in publishing APIs to multiple Common Application Programming Interface Core (CAPIF Core) entities, particularly in scenarios like vehicle-to-everything (V2X) services where APIs need to be shared across different Public Land Mobile Networks (PLMNs) and regions, requiring enhanced interconnection and interworking capabilities.
Innovation Solution
The proposed solution involves an API publish method that allows a first CCF entity to determine and share APIs with multiple target CCF entities, using specific interfaces and protocols such as CAPIF-4 and CAPIF-6e, enabling API publication across multiple domains and regions, and includes entities like API invoking entities, API exposure functions, and API management functions to facilitate secure and managed API sharing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If an API is published to only one CCF entity in the current CAPIF architecture, then the system maintains simple architecture and operation, but it cannot meet the requirement for API sharing across multiple PLMNs and regions in V2X scenarios
Solution Approach 1:
The patent segments the CAPIF system into multiple independent CCF entities distributed across different PLMNs and regions. Each CCF entity maintains local API publication capabilities while the segmentation enables parallel API sharing operations across multiple entities, resolving the contradiction between adaptability and complexity by distributing functionality rather than centralizing it.
Solution Approach 2:
The patent introduces an API publishing function entity as an intermediary between the API exposure function and multiple CCF entities. This intermediary manages the complexity of multi-entity API publication by abstracting the interaction model, allowing API sharing across PLMNs and regions without requiring each entity to directly manage complex interconnections.
2Area of stationary object
If the CAPIF system supports interconnection and interworking between different PLMNs and regions, then service coverage is expanded, but the difficulty of system management and coordination increases
Solution Approach 1:
The patent implements universal CCF entities that can operate across multiple PLMNs and regions with consistent functionality. Each CCF entity is designed to handle API publication, discovery, and invocation universally, regardless of the specific PLMN or region context. This multi-functionality allows service coverage expansion while maintaining manageable complexity through standardized behaviors.
Solution Approach 2:
The patent extends the CAPIF system from a single-domain architecture to a multi-dimensional architecture spanning multiple PLMNs and geographic regions. By adding the dimension of cross-PLMN and cross-region operation, the system achieves broader service coverage while the modular CCF entity design prevents management complexity from becoming unmanageable.
3Adaptability or versatility
If multiple CCF entities are introduced to support cross-PLMN and cross-region services, then API discovery and utilization become more comprehensive, but the interface definitions and interconnection requirements become more complex
Solution Approach 1:
The patent applies homogeneity by defining standardized interfaces and protocols that all CCF entities must implement uniformly. The CAPIF-4 and CAPIF-6e interfaces use consistent message formats, authentication mechanisms, and operational procedures across all entities. This homogeneity enables comprehensive API discovery across multiple PLMNs and regions while preventing interface complexity from becoming unmanageable through standardization.
Data Source
Figure 1A
Figure 1B
Figure 2~3
AI summary
Embodiments of this application relate to the field of communications technologies, and disclose an API publish method and an apparatus, to publish an API to a plurality of CCF entities. The method may include: determining, by a first CCF entity, a to-be-shared API; and sharing, by the first CCF entity, information about the to-be-shared API with a target CCF entity of the to-be-shared API.