Edge Enabler Server Graceful Shutdown via Control Message
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The EDGEAPP architecture lacks specifications for planned shutdown procedures of Edge Enabler Servers (EES), specifically for notifying registered Edge Enabler Clients (EECs) and transferring context to alternative EES before shutdown, which can lead to service disruptions.
Innovation Solution
Implementing a control message system where EES sends notifications to an Edge Configuration Server and User Equipment (UE) about scheduled shutdown, prompting the UE to initiate EEC registration requests to alternative EES, ensuring seamless context transfer and deregistration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If EES is shut down without advance notification, then shutdown operation is simple and quick, but service continuity is disrupted and EEC context is lost
Solution Approach 1:
The EES sends a shutdown notification message to the ECS and registered EECs in advance before actually shutting down. This preliminary action allows EECs to deregister and transfer contexts to alternative EESs before the original EES becomes unavailable, ensuring service continuity while maintaining a relatively simple shutdown procedure.
2Reliability
If EES sends shutdown notification to all registered EECs, then service continuity is maintained, but network signaling overhead increases
Solution Approach 1:
The ECS acts as an intermediary between the EES and EECs. The EES sends the shutdown notification to the ECS, which then manages the distribution of this information to the appropriate EECs. This intermediary approach consolidates signaling management and reduces the direct signaling burden on the EES while maintaining service continuity.
Data Source
AI summary
A first edge enabler server (EES) (5A) sends a control message to an edge configuration server (7) or an edge enabler client (EEC) (2) of a User Equipment (UE) indicating that the first EES is scheduled to be shut down or be unavailable. This can allow, for example, the edge configuration server or the EEC or both to perform any processing or procedure necessary to avoid or mitigate the effects of a planned shutdown of the EES.