Edge Application Server Deployment Across EDNs Under Service Constraints
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing 5G network slicing and edge computing management systems face challenges in efficiently deploying Edge Application Servers (EAS) across multiple Edge Data Networks (EDNs) while ensuring compliance with specific requirements such as service area, affinity, anti-affinity, cost, latency, and resource availability, which is critical for supporting diverse communication services and user equipment.
Innovation Solution
An Edge Computing Management Service Provider (ECMSP) system is introduced to manage the lifecycle of EAS by selecting appropriate EDNs based on predefined requirements, using a processor, memory, and communication units to extract, prioritize, and create Managed Object Instances (MOIs) that comply with EAS deployment requests, considering factors like service area, affinity, anti-affinity, cost, and resource availability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If EAS is deployed on multiple Edge Data Networks (EDNs) to support diverse communication services, then service coverage and adaptability are improved, but deployment complexity and management difficulty increase
Solution Approach 1:
The patent introduces an Edge Computing Management Service Provider (ECMSP) as an intermediary system that manages EAS deployment across multiple EDNs. The ECMSP receives deployment requests, extracts requirements, selects appropriate EDNs, and creates Managed Object Instances to orchestrate the deployment process, thereby reducing the complexity burden on individual operators and services.
Solution Approach 2:
The patent segments the EAS deployment process into distinct manageable components: requirement extraction, EDN selection based on multiple criteria, MOI creation, and deployment execution. This segmentation allows each step to be independently optimized and managed, reducing overall deployment complexity while maintaining multi-EDN support.
2Reliability
If strict requirements (service area, affinity, anti-affinity, cost, latency) are enforced for EAS deployment, then service quality and reliability are improved, but deployment flexibility and speed decrease
Solution Approach 1:
The patent performs preliminary actions by pre-defining deployment requirements (service area, affinity, anti-affinity, cost, latency) and pre-selecting appropriate EDNs before actual EAS deployment. The ECMSP extracts requirements from deployment requests and pre-evaluates EDN suitability, so that when deployment is executed, it can proceed quickly with pre-validated configurations, maintaining both quality and speed.
Solution Approach 2:
The patent utilizes parameter changes by adjusting deployment criteria weights and EDN selection parameters based on service requirements. The system can dynamically change parameters such as cost thresholds, latency requirements, and affinity rules to balance service quality with deployment speed, allowing flexible optimization for different service scenarios.
3Reliability
If manual EAS deployment management is used across multiple EDNs, then deployment control is maintained, but operational efficiency and resource utilization deteriorate
Solution Approach 1:
The patent implements self-service through the ECMSP system that automatically receives deployment requests, extracts requirements, selects appropriate EDNs based on predefined criteria, creates Managed Object Instances, and executes deployment without manual intervention. The system serves itself by maintaining deployment control through automated decision-making while significantly improving operational efficiency.
Solution Approach 2:
The patent incorporates feedback mechanisms where the ECMSP continuously monitors deployment status, EDN performance, and service quality metrics. This feedback enables the system to adjust deployment decisions, optimize resource allocation, and maintain control while improving efficiency through data-driven automated management across multiple EDNs.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
In an embodiment, a method, for deploying an edge application server (EAS) is disclosed. The method includes receiving an EAS deployment request to create an EAS instance associated with an EASFunction class, identifying, based on the EAS deployment request, one or more requirements for the EAS instance, selecting an edge data network (EDN) based on the one or more requirements for the EAS instance, and creating a managed object instance (MOI) corresponding to the EAS deployment request.