Edge Application Handover Client for Seamless Server Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current 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 involving frequent handovers, which can lead to service disruptions and inefficient resource management.

Innovation Solution

An Edge Application Handover (EAH) framework, comprising an Edge Application Handover Client (EAHC) on UEs and an Edge Application Handover Server (EAHS) in the network, facilitates seamless handovers by analyzing service requirements, managing EASs, and optimizing resource usage through policies and network interactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If Application Clients perform handovers between Edge Application Servers in current 5G architecture, then service migration is enabled, but service disruptions and inefficiencies occur due to lack of dedicated handover management

Engineering Contradiction:
Improveservice continuityVSAvoidhandover disruption time
Core Design Contradiction:
ReliabilityVSLoss of time

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 intercepts service requests, determines handover necessity based on policies, and coordinates the handover process, thereby reducing service disruptions and enabling smoother transitions between edge servers.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary handover assessments by analyzing service requirements and context information before actual handover execution. The EAHC evaluates whether handover is necessary and prepares handover decisions in advance based on configured policies, reducing the time and disruption during the actual handover execution phase.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If frequent handovers are performed without dedicated management, then application mobility is supported, but resource management efficiency deteriorates

Engineering Contradiction:
Improveapplication mobilityVSAvoidresource management efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The EAHC implements feedback mechanisms by continuously monitoring service requirements, context information, and handover outcomes. It uses this feedback to optimize handover decisions, adjusting handover triggers and parameters based on observed performance, thereby improving resource management efficiency while maintaining application mobility.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system dynamically changes handover parameters such as triggering thresholds, evaluation criteria, and policy rules based on network conditions and service requirements. This allows the handover management to adapt to different scenarios, improving resource efficiency without compromising application mobility capabilities.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If manual handover management is used by Application Clients, then implementation simplicity is maintained, but handover optimization and aggregation across multiple applications deteriorate

Engineering Contradiction:
Improvehandover implementation simplicityVSAvoidhandover aggregation efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent merges handover management functions across multiple Application Clients by introducing the EAHC that handles handover operations for multiple applications centrally. This aggregation enables coordinated handovers, reduces redundant operations, and improves overall resource utilization while maintaining the simplicity of individual application implementations.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS20260095820A1Seamless edge application handover
Publication Date: 2026.04.02 INTERDIGITAL PATENT HOLDINGS INC
  • US20260095820A1 patent drawing
  • US20260095820A1 patent drawing
  • US20260095820A1 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 client 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.