Network API Capability Reporting Across 4G-5G Handovers
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 API invocation and feature usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the SCS/AS or AF entity requests API capability through T8 interface in 4G network or Nnef/N33 interface in 5G network, then the entity can obtain API capability information for that specific network, but the entity cannot accurately learn the API capability when the terminal device is handed over between 4G and 5G networks
Solution Approach 1:
The patent implements a feedback mechanism where the SCEF/NEF entity continuously monitors network type changes and sends API capability information to the SCS/AS or AF entity. When the network type changes (e.g., from 4G to 5G), the system automatically feedbacks updated API capability information, ensuring the application server always has accurate capability data without needing to requery the interface
Solution Approach 2:
The patent applies preliminary action by having the SCEF/NEF entity proactively send API capability information to the SCS/AS or AF entity before the application server needs to invoke APIs. The system anticipates network changes and prepares capability information in advance, so when handover occurs, the application server already has the necessary capability data ready
2Reliability
If the system maintains separate API capability management for 4G and 5G networks, then each network's API capabilities are accurately tracked, but the complexity of managing API capabilities during network handover increases
Solution Approach 1:
The patent merges the API capability management functions of both 4G (SCEF) and 5G (NEF) networks into a unified management approach. The system consolidates capability information from both networks and presents it through a single interface to the SCS/AS or AF entity, simplifying management while maintaining reliability through integrated monitoring of network type changes
3Measurement precision
If the SCS/AS or AF entity continuously queries API capability information, then the entity can maintain up-to-date capability knowledge, but the operation time and system overhead increase
Solution Approach 1:
Instead of continuous querying, the system uses feedback where the SCEF/NEF entity pushes updated API capability information to the SCS/AS or AF entity only when changes occur (such as network type changes). This event-driven approach maintains information freshness while eliminating unnecessary continuous queries and reducing operation time
Solution Approach 2:
The system implements periodic action by sending API capability information at specific intervals or trigger events (such as network handover detection) rather than continuously. This timing-based approach ensures capability information is updated when necessary while minimizing system overhead and operation time
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.