Edge Application Server Instantiation for Missing or Noncompliant EAS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods fail to define how to dynamically instantiate an edge application server (EAS) when it is not deployed or does not meet the requirements of user equipment (UE) in an edge data network (EDN), leading to inefficiencies in operation and maintenance management.
Innovation Solution
A method for instantiating an edge application server based on specific conditions, such as the absence or inadequate performance of the EAS, using network elements to determine and dynamically instantiate the server when certain thresholds are met, improving efficiency and user experience.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the EES detects that the deployed EAS does not meet application information or finds no instantiated EAS, then the UE access request cannot be fulfilled, but the system lacks a defined mechanism to dynamically instantiate a new EAS
Solution Approach 1:
The patent applies preliminary action by pre-defining the instantiation mechanism and threshold conditions in advance. When the EES detects missing or non-compliant EAS, it triggers a predetermined workflow involving event reporting to the ECS, threshold evaluation, and automated instantiation decisions, eliminating the need for ad-hoc complex decision-making at runtime.
Solution Approach 2:
The patent introduces the ECS (Edge Configuration Server) as an intermediary between the EES and the EAS instantiation process. The ECS receives event information from the EES, evaluates thresholds, and coordinates the instantiation of new EAS, simplifying the complexity by centralizing the decision-making logic in a dedicated intermediary component.
2Speed
If the system immediately instantiates a missing EAS upon first detection, then UE access is restored quickly, but unnecessary instantiations occur without considering persistence of the problem
Solution Approach 1:
The patent implements feedback by continuously monitoring the presence and compliance of EAS and reporting events to the ECS. The ECS uses this feedback to evaluate whether the missing EAS condition persists beyond a threshold, making instantiation decisions based on sustained need rather than transient events, thus avoiding unnecessary instantiations.
Solution Approach 2:
The patent applies dynamics by making the instantiation decision adaptive rather than static. The system dynamically adjusts the instantiation trigger based on the frequency and persistence of missing EAS events, using threshold-based logic to determine when the problem is persistent enough to warrant instantiation, thereby balancing speed with resource efficiency.
3Loss of energy
If the system implements comprehensive threshold counting and evaluation logic, then unnecessary instantiations are avoided, but the decision-making process becomes more complex
Solution Approach 1:
The patent extracts the complex threshold evaluation and decision-making logic from the EES and places it in the ECS. This separation allows the EES to remain simple in its detection and reporting functions, while the ECS handles the sophisticated threshold counting and instantiation decision-making, reducing overall system complexity through functional decomposition.
Solution Approach 2:
The patent segments the EAS management system into distinct functional components: the EES for detection and event reporting, the ECS for threshold evaluation and decision-making, and the instantiation mechanism for EAS deployment. This segmentation distributes complexity across specialized components, making the overall system more manageable and maintainable.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
Embodiments of this application provide a method for instantiating an edge application server and an apparatus, and relate to the field of communication technologies, to dynamically instantiate the edge application server. In the method, the first network element may receive first information from a second network element. The first information may include network information and application information. The network information may indicate a first network, and the application information may indicate a first application. The first information may further include information about a first event that is related to the first application and that is in the first network. The first event includes at least one of the following: an edge application server corresponding to the first application is not found in the first network, the edge enabler server corresponding to the first application is not found in the first network, and performance information of the edge application server corresponding to the first application in the first network. The first network element may determine, when the first event meets a first condition, to instantiate a first edge application server corresponding to the first application in the first network.