Edge Application Handover Using Context-Aware Server Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing 5G Edge Application and V2X Application Architectures lack adequate support for seamless handovers of Application Clients (ACs) between Edge Application Servers (EASs), particularly in scenarios requiring frequent handovers, leading to service disruptions and inefficient resource management in edge networks.

Innovation Solution

An Edge Application Handover (EAH) framework is introduced, comprising an Edge Application Handover Client (EAHC) on UEs and an Edge Application Handover Server (EAHS) in the network, which assist ACs with seamless handovers by analyzing service requirements, managing EASs, and optimizing resource usage through policies and context information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional handover mechanisms are used in 5G Edge Application and V2X architectures, then basic connectivity is maintained, but seamless handovers between Edge Application Servers cannot be achieved, leading to service disruptions

Engineering Contradiction:
Improveservice continuityVSAvoidhandover management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an Edge Application Handover Client (EAHC) as an intermediary component that mediates handover operations between Application Clients and Edge Application Servers. The EAHC maintains context information about multiple EAS instances and coordinates handovers seamlessly, preventing service disruptions without requiring complex modifications to existing AC architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The EAHC performs preliminary actions by pre-establishing context information about multiple Edge Application Server instances and their capabilities before handovers are needed. This includes maintaining service requirements, context information, and availability status of EASs, enabling rapid seamless handovers when mobility events occur.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If frequent handovers are supported in dynamic environments like vehicular applications, then service continuity is improved, but resource management efficiency deteriorates

Engineering Contradiction:
Improveservice continuityVSAvoidnetwork resource utilization efficiency
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The EAHC implements feedback mechanisms by continuously monitoring the availability status, load conditions, and performance metrics of multiple Edge Application Server instances. Based on this feedback, the EAHC intelligently selects optimal target EASs for handover, avoiding unnecessary handovers and reducing network resource waste while maintaining service continuity in dynamic vehicular environments.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system dynamically changes parameters such as EAS selection criteria, handover thresholds, and context information based on current network conditions, UE mobility patterns, and service requirements. This allows the system to optimize resource utilization efficiency while supporting frequent handovers when necessary for service continuity.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If context information is collected and analyzed for handover decisions, then handover optimization is improved, but processing overhead increases

Engineering Contradiction:
Improvehandover optimizationVSAvoidprocessing time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The EAHC performs preliminary actions by pre-collecting and organizing context information about Edge Application Servers, including their service capabilities, current load status, and geographical distribution. This pre-processed context information is stored and readily available when handover decisions need to be made, reducing real-time processing overhead while maintaining comprehensive optimization capabilities.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12604239B2Seamless edge application handover
Publication Date: 2026.04.14 INTERDIGITAL PATENT HOLDINGS INC
  • US12604239B2 patent drawing
  • US12604239B2 patent drawing
  • US12604239B2 patent drawing

AI summary

An edge application handover client in a user equipment may use application client information, such as type service, provider, location, context, and sendee requirements, to assist seamless edge application handovers of application clients between edge application servers. For example, a handover client may use context information to determine an anticipated route of the user equipment, and thereby determine a next, edge application server for a handoff. The handover client may weigh the needs of multiple application clients m selecting servers for handovers. The handover client may issue requests to servers requesting assistance in handover operations, and may issue subscription requests to servers, and further may determine the success of handovers by monitoring application state synchronization or migration between edge application handover servers.