Cloud Adapter Mediator for VNF Lifecycle Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The communication network system faces increased load due to the need for individual handling of VNF deployment requests across different types of clouds, as type 1 clouds provide a job ID for status queries while type 2 clouds do not, requiring the life cycle manager to handle each cloud type separately.
Innovation Solution
A cloud adapter mediates communication between the life cycle manager and clouds, creating a common-format management ID independent of cloud type, allowing standardized processing of VNF setting requests and queries for processing status, thereby reducing the load on the life cycle manager.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the life cycle manager handles VNF deployment requests for each cloud type individually, then it can manage both type 1 and type 2 clouds, but the load on the life cycle manager increases
Solution Approach 1:
A cloud adapter is introduced as an intermediary component between the life cycle manager and multiple cloud platforms. The cloud adapter handles the complexity of communicating with different cloud types (type 1 and type 2), performing status queries and receiving responses, while the life cycle manager only needs to send standardized deployment requests. This mediator pattern resolves the contradiction by shielding the life cycle manager from cloud-type-specific complexity while maintaining the ability to manage diverse cloud platforms.
Solution Approach 2:
The system is segmented into distinct functional components: the life cycle manager responsible for high-level VNF deployment orchestration, and the cloud adapter responsible for cloud-specific communication and status monitoring. This segmentation allows each component to specialize in its function, reducing the load on the life cycle manager while preserving multi-cloud management capability.
2Reliability
If the life cycle manager queries each cloud directly to confirm VNF setting status, then it can obtain processing status, but the communication overhead and load increase
Solution Approach 1:
The cloud adapter serves as an intermediary that consolidates communication with multiple clouds. Instead of the life cycle manager querying each cloud separately, the cloud adapter performs batch status queries and returns unified results. This maintains reliable status confirmation while significantly improving processing efficiency by reducing the number of individual communication interactions.
3Adaptability or versatility
If type 1 clouds return a job ID for status queries while type 2 clouds do not, then each cloud type can use its native status tracking method, but the life cycle manager must handle each cloud type separately
Solution Approach 1:
The cloud adapter is designed with universal functionality to handle both type 1 clouds (that return job IDs) and type 2 clouds (that do not return job IDs). It implements cloud-type-agnostic status query mechanisms that adapt to each cloud's protocol while presenting a unified interface to the life cycle manager. This multi-functionality resolves the contradiction by maintaining protocol compatibility across different cloud types while simplifying status management through standardized interactions.
Data Source
AI summary
The communication network system according to the present disclosure comprises: a life cycle manager (LCM) that transmits a request for virtual network function (VNF) setting to one or more clouds; and a cloud adapter that mediates communication between the LCM and the cloud to which the request is addressed,The cloud adapter creates, based on a response to the request from the cloud to which the request is addressed, a common-format management ID independent of the type of the cloud to which the request is addressed, and transmits the management ID to the LCM.The LCM may transmit a query regarding a processing status of the request to the cloud adapter, including the management ID.The cloud adapter may recognize the cloud to which the query is addressed on the basis of the management ID and query the cloud to which the query is addressed such that the cloud returns the processing status.