Network API Capability Reporting for 4G-5G Handover Accuracy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In interworking architectures where 4G and 5G networks are jointly deployed, the Service Capability Server/Application Server (SCS/AS) or Application Function (AF) entity cannot accurately determine the API capabilities of the network serving the terminal device during handovers, leading to incorrect API invocations and feature usage.
Innovation Solution
A network API capability reporting method where a first entity, such as the SCEF or NEF, sends information to a second entity, such as the SCS/AS or AF, about the current API capabilities and availability features of the network serving the terminal device when the network type changes, ensuring accurate and timely updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the SCS/AS or AF entity requests API capability in interworking architecture, then the entity can access the 3GPP network, but the entity cannot accurately learn the API capability when the terminal device is handed over between 4G and 5G networks, leading to incorrect API invocation
Solution Approach 1:
The patent implements a feedback mechanism where the first entity (SCEF or NEF) continuously monitors network type changes and sends capability information to the second entity (SCS/AS or AF). When the network type changes between 4G and 5G, the first entity detects this change and feeds back the updated API capability information, ensuring the second entity always has accurate capability data for the current network environment.
Solution Approach 2:
The patent applies preliminary action by having the first entity proactively send capability information to the second entity before the second entity needs to invoke APIs. The capability information is pushed in advance when network type changes occur, so the second entity is already prepared with accurate capability data when handover happens, preventing incorrect API invocation.
2Reliability
If the first entity sends capability information whenever network type changes, then the second entity can avoid incorrect API invocation, but this increases signaling overhead and network traffic
Solution Approach 1:
The patent implements periodic action by triggering capability information transmission only at specific moments when network type changes occur, rather than continuously or at fixed intervals. This event-driven periodic transmission ensures capability accuracy is maintained while minimizing unnecessary signaling overhead during stable network conditions.
Solution Approach 2:
The patent extracts and transmits only the specific capability information that changed due to network type changes, rather than transmitting all capability data continuously. This selective extraction of necessary information reduces signaling overhead while ensuring the second entity receives the critical updates needed to avoid incorrect API invocation.
Data Source
AI summary
A network API capability reporting method includes: A first entity receives first information, where the first information is used to subscribe to an API capability of a network that serves a terminal device. The first entity sends second information to a second entity when a type of the network that serves the terminal device changes, where the second information includes an API capability of a network that currently serves the terminal device, and where the API capability includes an API supported by the network that serves the terminal device and an availability feature of at least one API in the supported API.