Edge Application Relocation for Low-Downtime MEC Handover

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The interdependence between network and computer configurations in edge computing poses challenges for maintaining application availability and resource allocation in edge-native use cases, particularly due to user mobility and resource limitations, leading to application instantiation delays and downtime.

Innovation Solution

A method for relocating application functions between Edge Data Network components, involving an indication of user mobility, resource optimization, and key performance indicators, with a Protocol Data Unit session establishment procedure and communication with an ETSI Multi-access Edge Computing orchestrator to manage User Plane Functions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If edge application functions are relocated to optimize resource allocation or respond to user mobility, then resource efficiency and adaptability improve, but application instantiation delay and downtime increase

Engineering Contradiction:
Improveresource allocation optimizationVSAvoidapplication instantiation delay
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-establishing target Edge Data Network components and pre-configuring their capabilities before relocation is needed. The system proactively identifies suitable target locations and prepares them in advance, so when relocation is triggered by user mobility or resource optimization needs, the target is ready to receive and instantiate the application function immediately, minimizing instantiation delay.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements dynamics by making the Edge Data Network component selection adaptive and flexible. The system dynamically determines source and target EDN components based on real-time conditions such as user location, network load, and application requirements. This dynamic approach allows the system to optimize resource allocation while managing relocation impact through continuous monitoring and adaptive decision-making.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If edge application functions are relocated to respond to user mobility, then network adaptability improves, but application availability and service continuity worsen

Engineering Contradiction:
Improvenetwork reconfiguration capabilityVSAvoidapplication availability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies preliminary action by pre-identifying and preparing target Edge Data Network components before user mobility triggers relocation. The system maintains a registry of suitable target locations with pre-configured capabilities, so when mobility events occur, the target is ready to receive the application function context immediately, minimizing service disruption and maintaining availability during the relocation process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary coordination mechanism between the network and edge application functions. This intermediary layer manages the relocation process by coordinating between source and target EDN components, handling context transfer, and ensuring seamless switchover. The intermediary ensures that relocation operations maintain application availability by synchronizing network reconfiguration with application state migration.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If robust coordination mechanisms are implemented between network and computer, then application reliability improves, but system complexity increases

Engineering Contradiction:
Improvecoordination between network and computerVSAvoidcoordination mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies universality by designing a multi-functional Edge Data Network component that can serve multiple purposes: it acts as a network function, a data network function, and an application function host. This universal component simplifies the coordination mechanism by consolidating multiple functions into a single entity, reducing the complexity of interactions between network and computer while maintaining robust coordination capabilities.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent implements self-service by enabling the Edge Data Network component to autonomously manage its own relocation and coordination tasks. The component automatically detects relocation triggers, selects target locations, transfers context, and establishes new connections without requiring complex external coordination. This self-service capability reduces system complexity by eliminating the need for sophisticated centralized control mechanisms while maintaining high reliability.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20260113382A1Edge application server relocation
Publication Date: 2026.04.23 INTERDIGITAL PATENT HOLDINGS INC
  • US20260113382A1 patent drawing
  • US20260113382A1 patent drawing
  • US20260113382A1 patent drawing

AI summary

Methods and apparatuses for reducing application instantiation delay and downtime are described herein. A method may comprise relocating an application function from a source Edge Data Network (EDN) component to a target EDN component. The method may comprise receiving an indication, and/or determining, based on at least one of a user mobility, resource optimization requirement, key performance indicator (KPI), or a failed relocation attempt, to relocate the application function. The method may further comprise performing a Protocol Data Unit (PDU) session establishment procedure toward the target EDN component. The method may further comprise determining, based on one or more received parameters for edge usage and capabilities, to relocate the application function. The method may further comprise sending, to a European Telecommunications Standards Institute (ETSI) Multi-access Edge Computing (MEC) orchestrator, an indication that the application function will be relocated. The application function may be a User Plane Function (UPF).