Network-Triggered Application Context Relocation for Efficient Data Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing standardized cellular network procedures rely on user equipment (UE) or application servers to initiate application context relocation based on geographical location, leading to inefficient data routing and increased power consumption due to incorrect or outdated network routing information, without the network itself monitoring UE location and managing UPF and application server reselection.
Innovation Solution
A network entity, such as the edge enabler server (EES), monitors UE location in terms of network topology and autonomously triggers application context relocation when the UE leaves the service area, managing UPF and application server reselection to optimize data routing and reduce power consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If UE or application server initiates application context relocation based on geographical location, then application server reselection can be triggered, but incorrect or outdated network routing information is used leading to inefficient data routing
Solution Approach 1:
The patent introduces a network entity (edge enabler server) as an intermediary between the UE/application server and the core network. This intermediary maintains accurate network routing information and provides it to the UE or application server, ensuring they use correct information for initiating application context relocation. The intermediary resolves the contradiction by decoupling the location monitoring function from the routing information management, allowing accurate routing information to be provided without requiring the UE or application server to directly access network internals.
Solution Approach 2:
The network entity autonomously monitors UE location and manages UPF and application server reselection without requiring UE or application server intervention. The system uses network-based location information from the AMF to trigger application context relocation, ensuring decisions are based on accurate, real-time network routing information. This self-service approach eliminates the information accuracy problem while maintaining routing efficiency.
2Productivity
If UE monitors its own location to trigger application context relocation, then relocation can be initiated, but power consumption increases due to continuous GPS or network location monitoring
Solution Approach 1:
The patent extracts the location monitoring function from the UE and relocates it to the network entity. The AMF continues to monitor UE location as part of its normal mobility management functions, and the edge enabler server utilizes this existing location information to trigger application context relocation. This extraction eliminates the need for separate UE-based location monitoring, significantly reducing power consumption while maintaining relocation responsiveness.
Solution Approach 2:
The network entity acts as an intermediary that utilizes location information already being collected by the AMF for mobility management. Instead of the UE performing separate location monitoring, the network entity subscribes to location updates from the AMF and uses this information to trigger application context relocation when appropriate. This approach leverages existing network resources to reduce UE power consumption.
3Reliability
If application context relocation is triggered by geographical location changes, then service continuity can be maintained, but latency increases due to unnecessary re-routing when network topology changes
Solution Approach 1:
The patent changes the triggering parameter for application context relocation from purely geographical location to a combination of location and network routing information. The network entity monitors both UE location and network topology, triggering relocation only when network routing information indicates that a change would improve or maintain service quality. This prevents unnecessary re-routing when geographical location changes do not correspond to network routing changes, reducing latency while maintaining service continuity.
Solution Approach 2:
The network entity implements feedback mechanisms by continuously monitoring network routing information and using it to determine whether application context relocation is appropriate. The system receives feedback from the core network about UPF locations and network topology, and uses this feedback to make intelligent decisions about when to trigger relocation. This feedback loop ensures that relocation is triggered only when it will maintain or improve service continuity, avoiding unnecessary re-routing and latency.
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
A method of initiating application context relocation in a telecommunications network is provided. The method comprises receiving a request from a user equipment, UE, for an application client running on the UE to connect to an application server selected from one or more registered application servers. The method further comprises determining a selected application server from the one or more registered application servers. The method further comprises determining a service area of the selected application server. The method further comprises sending a request to monitor a location of the UE. The method further comprises determining that the UE has left the service area. The method further comprises initiating application context relocation in response to determining that the UE has left the service area.