Edge Enabler Server Context Synchronization for 5G Service Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing 5G mobile communication systems lack resilience to Edge Enabler Server (EES) failures, leading to inconsistent data delivery to Application Clients (ACs) and Edge Application Servers (EASs, necessitating improved methods for service continuity and fault recovery.
Innovation Solution
A system and method for synchronizing content between a primary and backup EES using push and pull mechanisms, involving context transfer procedures and validation to ensure service resilience during EES failures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a single EES is used to provide services to ACs and EASs, then the system structure is simple, but the system lacks resilience and service continuity during EES failures
Solution Approach 1:
The patent implements preliminary action by establishing a backup EES before the primary EES fails. The backup EES is pre-configured with the capability to take over services, and content synchronization mechanisms are prepared in advance. When failure occurs, the backup EES can immediately assume the role of the primary EES, ensuring service continuity without interruption.
Solution Approach 2:
The patent applies copying by creating a replica of the EES system. A backup EES is deployed with the same functional capabilities as the primary EES, enabling it to replicate services. This copying approach ensures that if the primary EES fails, the backup can immediately provide identical services, maintaining system reliability.
2Reliability
If content synchronization between EESs is implemented, then service resilience is improved, but data consistency management complexity increases
Solution Approach 1:
The patent implements feedback mechanisms where the backup EES continuously monitors the status of the primary EES. When the primary EES is operational, the backup receives feedback about its role status and maintains readiness without active synchronization. When failure occurs, the feedback mechanism triggers immediate role transition and content synchronization, managing data consistency through status-driven synchronization.
Solution Approach 2:
The patent uses preliminary action by pre-establishing synchronization mechanisms and content caches in the backup EES before failure occurs. This allows the backup EES to have content ready in advance, reducing the complexity of real-time synchronization during failure events while ensuring service resilience.
3Reliability
If backup EES is deployed for failover, then service dependability is improved, but resource consumption increases
Solution Approach 1:
The patent applies dynamics by implementing a dynamic resource allocation model for backup EES. The backup EES maintains minimal resource consumption in standby mode, activating full synchronization and processing capabilities only when failure occurs. This dynamic approach allows the system to maintain service dependability while minimizing resource consumption during normal operation.
Solution Approach 2:
The patent implements preliminary action by pre-caching essential content and configurations in the backup EES before failure occurs. This reduces the amount of data that needs to be synchronized in real-time during failure events, thereby reducing the resource consumption burden on the backup EES while maintaining service dependability.
Data Source
AI summary
The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Disclosed herein is a method of a first Edge Enabler Server (EES) in an edge network comprising the first EES and a second EES. The methods comprises receiving, from the second EES, a context push request message for context transfer procedures; validating and authorizing the second EES in response to the push request message; and in case that the second EES is authorized and the first EES and the second EES are part of same EES set of the edge network, storing first information included in the context push request message for synchronization with the second EES and transmitting, to the second EES, a context push response message, wherein the first information comprises at least one of a list of Edge Enabler Client (EEC) contexts, or a list of Edge Application Server (EAS) profiles.