Edge Configuration Feedback for EDN Provisioning Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The EDGEAPP architecture lacks clear responses to service provisioning notifications and unclear handling of EDN configuration information updates, leading to synchronization issues between the Edge Configuration Server (ECS) and the Edge Enabler Client (EEC) regarding configuration information.
Innovation Solution
Implementing response mechanisms for service provisioning notifications and updating EDN configuration information through defined response messages and procedures, ensuring synchronization and efficient handling of configuration updates between the ECS and EEC.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If the ECS sends service provisioning notifications to the EEC without requiring responses, then the system complexity is reduced, but the reliability of configuration delivery cannot be confirmed
Solution Approach 1:
The patent implements a feedback mechanism where the EEC sends response messages to the ECS to confirm receipt of service provisioning notifications. The response includes a notification ID and success/failure status, allowing the ECS to verify whether the EEC has successfully received and processed the configuration information. This resolves the contradiction by adding minimal protocol complexity to achieve reliable delivery confirmation.
2Ease of operation
If the EEC stores EDN configuration information locally without update mechanisms, then the ease of operation is improved, but the information becomes outdated over time
Solution Approach 1:
The system implements a feedback-based update mechanism where the EEC periodically checks for updates by sending requests to the ECS with its current notification ID. The ECS responds with updated configuration information if changes are available, ensuring the EEC maintains current configuration data while keeping the local storage mechanism simple.
Solution Approach 2:
The EEC performs periodic checks for configuration updates by sending periodic requests to the ECS. This periodic action ensures that the locally stored configuration information remains current without requiring continuous connection or complex real-time synchronization mechanisms.
3Reliability
If the ECS waits for EEC initialization before providing configuration information, then the reliability of configuration delivery is improved, but the time to establish edge services increases
Solution Approach 1:
The ECS performs preliminary actions by preparing and storing configuration information in advance, assigning notification IDs to pending notifications before the EEC is fully initialized. When the EEC connects, it can immediately retrieve these pre-prepared configurations, reducing establishment time while maintaining delivery reliability through the confirmation mechanism.
Data Source
AI summary
An edge enabler client (EEC) (2) of a User Equipment (UE) (1) receives from an edge configuration server (ECS) (7) a service provisioning notification containing edge data network (EDN) configuration information for accessing an EDN (4), and responds to the ECS (7) with a response message in response to receiving the service provisioning notification. For example, this can allow the ECS to know whether or not a service provisioning notification has been successfully received by the EEC of the UE in a Subscribe/Notify model based service provisioning procedure.