Edge Enabler Client Service Delegation API
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 3GPP standards for the edge enabler layer do not specify the interface exposed by the edge enabler client towards the application client, and existing EEC services are improvident, limiting the edge enabler layer's ability to plan ahead with informed predictions.
Innovation Solution
Defining an interface, such as an application program interface (API), to simplify application client implementations and provide flexibility by allowing delegation of services to the edge enabler client (EEC), enabling the EEC to predict future requirements based on UE characteristics and user behavior patterns.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the edge enabler client (EEC) manages edge enabler layer services on behalf of the application client, then the service management complexity is reduced and productivity is improved, but the EEC requires more sophisticated prediction capabilities and authorized service lists to function properly
Solution Approach 1:
The service management function is segmented between the application client and EEC. The application client provides the list of authorized services, while the EEC handles the actual service management operations. This segmentation reduces the EEC's complexity burden while maintaining high productivity in service management.
Solution Approach 2:
The system implements a feedback mechanism where the EEC predicts future service requirements based on UE characteristics and user behavior patterns, then notifies the application client. This feedback loop enables the EEC to operate autonomously with high efficiency while the application client maintains control through authorization lists.
2Reliability
If the EEC uses UE information and monitoring of UE characteristics to predict future requirements, then network planning capability is improved, but the system requires more sophisticated prediction algorithms and data processing
Solution Approach 1:
The EEC performs self-service by autonomously monitoring UE characteristics and predicting future service requirements without requiring complex external prediction systems. The EEC uses its own integrated capabilities to analyze UE data and generate predictions, reducing overall system complexity while maintaining high reliability in network planning.
Solution Approach 2:
The system changes parameters by monitoring UE characteristics such as location, behavior patterns, and service usage history. By analyzing changes in these parameters over time, the EEC can predict future requirements accurately using relatively simple processing algorithms rather than complex prediction models.
3Ease of operation
If the interface between EEC and application client is simplified through API definition, then ease of operation is improved, but the standardization and interoperability requirements increase
Solution Approach 1:
The API interface is designed with universality to work across different application clients and EEC implementations. The standardized API allows any application client to delegate services to the EEC using a common interface, improving ease of operation while the standardization is handled at the protocol level rather than implementation level.
Data Source
AI summary
A method of wireless communication by a user equipment (UE) includes receiving, from an application client, a request to delegate edge enabler layer services. The request includes a list of edge enabler layer services for an edge enabler client (EEC) to manage on behalf of the application client. The method also includes transmitting, to the application client, an indication of which edge enabler layer services are authorized for the application client. The method further includes transmitting a confirmation that the EEC will handle authorized edge enabler layer services on behalf of the application client. The method still further includes executing one or more procedures related to the authorized edge enabler layer services on behalf of the application client. The procedure(s) includes edge enabler layer procedures, application procedures, and/or high level operating system (HILOS) procedures.