ECS Instance Object Class for Automated 5G Lifecycle Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication systems, particularly fifth-generation (5G) systems, face challenges in efficiently managing the lifecycle of Edge Configuration Servers (ECS) and Edge Enabler Servers (EES), including instantiation, termination, and scaling, which are crucial for optimizing edge computing services.
Innovation Solution
The implementation of an Edge Configuration Server (ECS) Instance Object Class (IOC) within the 3GPP Network Resource Model (NRM) to manage the lifecycle of ECS, including attributes such as endpoint information and service area, enabling efficient deployment and management of ECS instances through the Edge Computing Management Service Provider (ECMS_P).
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If manual management methods are used for ECS lifecycle, then implementation simplicity is maintained, but management efficiency and automation level deteriorate
Solution Approach 1:
The patent introduces an Edge Configuration Server (ECS) as an intermediary component that automates the management of Edge Enabler Servers (EES). The ECS receives deployment requests, retrieves configuration data from the network repository, and automatically configures multiple EES instances, thereby improving management efficiency without requiring direct manual intervention for each server.
Solution Approach 2:
The system enables self-service automation where the ECS automatically retrieves configuration data from the network repository, generates deployment configurations, and configures EES instances without human intervention. This automated self-service approach significantly improves productivity while the standardized processes keep system complexity manageable.
2Extent of automation
If standardized ECS IOC is implemented in NRM, then management automation is improved, but implementation complexity increases
Solution Approach 1:
The patent implements a universal Edge Configuration Server (ECS) that can manage multiple Edge Enabler Servers (EES) across different networks and configurations. This multi-functional ECS design improves automation extent by providing a single standardized interface for managing diverse edge computing resources, while the standardization itself helps control implementation complexity through reusability.
Solution Approach 2:
The system uses parameter-based configuration where the ECS retrieves and manages configuration data through structured parameters in the network repository. By changing and managing system state through standardized parameters rather than hard-coded configurations, the patent achieves high automation while maintaining implementation clarity through consistent parameter interfaces.
3Manufacturing precision
If comprehensive configuration data is stored in network repository, then deployment accuracy is improved, but data management complexity increases
Solution Approach 1:
The patent segments configuration data into distinct, organized components stored in the network repository, including deployment configuration data, service area information, and server-specific parameters. This segmentation improves deployment accuracy by ensuring all necessary configuration elements are captured, while the modular structure reduces management complexity by making data organization systematic and manageable.
Solution Approach 2:
The system performs preliminary action by pre-storing all necessary configuration data in the network repository before ECS deployment. This advance preparation ensures deployment accuracy by having all configuration elements ready and validated beforehand, while the centralized pre-organization of data reduces the complexity of real-time configuration management during deployment.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present invention discloses a systema and method for deploying an Edge Configuration Server (ECS). The method comprising receiving, at a provider entity, an operation request for deploying an ECS from a consumer entity, wherein the operation request comprises one or more requirements associated with the ECS. Thereafter, the method identifies an ECSfunction Information Object Class (IOC) for creating an ECS instance, based on the one or more requirements included in the operation request and an IOC database, wherein the IOC database comprises a plurality of IOCs and deploys the ECS based on the identified ECSfunction IOC and the one or more requirements.