Network Entity API Publishing Checks to Prevent Cross-Domain Loops
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network entities face issues with redundant resource creation and looping during service API publishing across CAPIF provider domains, leading to resource waste and inefficiencies.
Innovation Solution
A network entity method that checks if its identifier is included in a list of published entities before publishing a service API, responding with failure if included, and creating a new resource only if not included, thereby avoiding redundant resource creation and looping.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If service API publishing is performed across multiple CAPIF provider domains without checking existing publications, then API availability and service coverage are improved, but redundant resource creation and looping occur leading to resource waste
Solution Approach 1:
The patent applies preliminary action by checking the list of published entities before performing the service API publishing operation. The network entity retrieves and examines the list of identifiers of entities that have already published the service API, and only proceeds with publishing if its identifier is not found in the list. This preventive check avoids redundant resource creation and looping while maintaining API availability across domains.
2Adaptability or versatility
If service API publishing is performed without verification of existing publications, then service coverage across domains is enhanced, but looping in the publishing process occurs causing inefficiency
Solution Approach 1:
The patent implements feedback by using the list of published entities as feedback information to control the publishing process. The network entity continuously monitors the publishing status by checking whether its identifier exists in the list of already published entities, and adjusts its behavior accordingly - proceeding with publishing only when necessary and stopping when redundancy is detected. This feedback mechanism eliminates looping while preserving service coverage.
3Loss of energy
If the network entity checks its identifier in the list of published entities before publishing, then redundant resource creation is prevented, but additional processing steps are required
Solution Approach 1:
The patent applies self-service by enabling the network entity to autonomously determine whether publishing is necessary through self-checking its identifier against the list of published entities. The entity independently retrieves the list, performs the check, and makes the publishing decision without requiring external coordination or complex inter-entity communication protocols. This self-service approach prevents redundant resources while maintaining relatively simple process complexity.
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
The present disclosure provides a method (400) in a first network entity for service Application Programming Interface, API, publishing. The method (400) includes: receiving (410), from a second network entity, an API publish request for publishing a service API, the API publish request containing a list of identifiers of network entities that have published the service API; and transmitting (420), when an identifier of the first network entity is included in the list, an API publish response indicating failure of publishing of the service API to the second network entity, without creating a new resource for the service API at the first network entity or further publishing the service API to any network entity.