Asynchronous LCM Operations for Edge Application Server VNF Instantiation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing provisioning management services for lifecycle management (LCM) in 5G networks face challenges with synchronous operations that require consumers to wait for extended periods during the instantiation of virtualized network functions (VNFs) in edge cloud environments, and lack clear indications of instantiation failures due to resource shortages.
Innovation Solution
The introduction of asynchronous LCM operations using the LcmProcess IOC to report the progress and result of EAS VNF instantiation, allowing for the creation of Managed Object Instances (MOIs) that notify consumers of status changes, and the use of EASLcmRequest IOC to manage the lifecycle of EAS VNFs, enabling more efficient and transparent deployment processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If synchronous LCM operations are used for EAS VNF instantiation, then consumers can obtain immediate confirmation of deployment status, but consumers must wait for extended periods during the instantiation process
Solution Approach 1:
The system transitions from synchronous to asynchronous operation modes. The LCM process accepts requests and immediately returns with a status indicating the operation has been queued, then processes the request in the background. This dynamic shift allows consumers to move from a waiting state to an active state where they can monitor progress through notifications without being blocked by the instantiation process.
Solution Approach 2:
The system implements a feedback mechanism through notifications that inform consumers about the status of LCM operations. Consumers receive updates when VNF instantiation progresses or completes, eliminating the need for continuous polling or extended waiting. The feedback loop maintains reliability by ensuring consumers are informed of deployment status without requiring them to hold the connection open during the entire instantiation process.
2Ease of operation
If synchronous LCM operations are used for EAS VNF instantiation, then consumers receive immediate response, but the system lacks clear indications of instantiation failures due to resource shortages
Solution Approach 1:
The notification-based feedback system provides comprehensive information about LCM operation outcomes, including failure conditions. When VNF instantiation fails due to resource shortages or other issues, the system sends notifications to consumers detailing the failure status and reasons. This ensures consumers receive both immediate response confirmation and complete information about the outcome, whether successful or failed.
Solution Approach 2:
The LCM process is segmented into distinct phases with clear status boundaries. The system separates the request acceptance phase (immediate response) from the execution phase (asynchronous processing), and finally from the completion/notification phase (failure information delivery). This segmentation allows the system to provide immediate acknowledgment while maintaining the ability to communicate detailed failure information when needed.
3Productivity
If asynchronous LCM operations are introduced with LcmProcess IOC, then consumers do not need to wait for VNF instantiation, but the system complexity increases
Solution Approach 1:
The LcmProcess IOC and notification mechanism serve multiple functions: they manage asynchronous operations, provide status tracking, deliver failure notifications, and enable consumer monitoring. By making this single component multi-functional, the system achieves improved productivity without proportionally increasing complexity. The universal design handles various LCM scenarios through a unified approach.
Solution Approach 2:
The LcmProcess IOC acts as an intermediary between the provisioning management service and consumers. It absorbs the complexity of asynchronous VNF instantiation processing and presents a simplified interface to consumers through standardized notifications. This intermediary layer isolates consumers from the underlying system complexity while enabling efficient asynchronous operations.
4Loss of information
If asynchronous operations with notifications are implemented, then real-time status updates are provided, but the system requires additional infrastructure for notification delivery
Solution Approach 1:
The notification system leverages existing service-oriented architecture components and message delivery mechanisms already present in the network. Rather than implementing a completely new notification infrastructure, the system uses available services to deliver status updates and failure notifications. This self-service approach provides real-time information without requiring substantial additional infrastructure.
Data Source
AI summary
An apparatus and system are provided to provide the progress and result of lifecycle management (LCM) processes of an edge application server (EAS) virtual network function (VNF) in a cloud. Network Resource Models (NRMs) include process information for the LCM of the EAS. A createMOI operation is used to create a Managed Object Instance (MOI) representing an EAS LCM request that contains EAS requirements to start EAS VNF instantiation and LCM process information is used to report the progress and result of EAS VNF instantiation. The EAS requirements include deployment requirements for the EAS VNF. An Information Object Class (IOC) representing the EAS LCM request enables provisioning MnS consumers to perform an LCM operation for the EAS VNF instantiation.