VNFM Software Modification Initiation in NFV Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current NFV standards lack a defined operation for updating or upgrading Virtualization Network Function (VNF) software, and conventional methods are inadequate for managing VNF software updates in Network Function Virtualization (NFV) systems, which require two separate management systems.
Innovation Solution
A software modification initiation method and apparatus that automatically initiates software modifications for VNF software in NFV systems by receiving lifecycle management requests, determining the relevant VNF instances, and performing software upgrades or updates without user intervention, ensuring stability and continuity through sequential execution and resource management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If conventional software update methods are used in NFV systems, then manual intervention is required for each update operation, but this increases operation complexity and reduces update efficiency
Solution Approach 1:
The VNFM is configured to automatically initiate software modification operations for VNF instances based on received LCM requests, eliminating the need for manual intervention. The system self-services by autonomously determining the software modification type, identifying target VNF instances, and executing update procedures without user involvement, thereby improving efficiency while maintaining operational simplicity
Solution Approach 2:
The system pre-configures the VNFM with the capability to automatically process software update requests. By establishing the automatic initiation mechanism in advance, the system prepares the necessary logic and workflows before actual updates are needed, enabling rapid execution when LCM requests are received without requiring manual setup each time
2Productivity
If automatic software modification is implemented without defined operations, then update speed increases, but system reliability decreases due to lack of standardized procedures
Solution Approach 1:
The patent defines a universal software modification operation that can handle multiple update scenarios (new software versions, bug fixes, security patches) through a single standardized mechanism. The VNFM uses a unified approach to process all software modification requests, ensuring consistency and reliability across different update types while maintaining high update speed through automation
Solution Approach 2:
The system implements feedback mechanisms where the VNFM monitors the execution status of software modification operations and adjusts its behavior accordingly. By receiving feedback on update success or failure, the system can retry failed operations, notify appropriate systems, or rollback changes, thereby maintaining reliability while preserving automatic operation capability
3Device complexity
If software updates are performed without instance verification, then update process simplifies, but risk of service disruption increases
Solution Approach 1:
The VNFM performs preliminary verification of VNF instances before initiating software modifications. It checks instance status, compatibility with new software versions, and dependencies in advance. This preliminary action ensures that updates are only applied to suitable instances, preventing service disruptions while maintaining a relatively simple update process
Solution Approach 2:
The system implements cushioning measures by creating backup configurations and verifying instance readiness before software updates. It prepares rollback plans and ensures service continuity mechanisms are in place beforehand, so that if an update fails or causes issues, the system can recover without significant service disruption
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
This application discloses a software modification initiation method and a metadata release method and apparatus. The method includes: receiving, by a VNFM, a virtualized network function VNF lifecycle management LCM request sent by an NFVO, where the VNF LCM request includes an instance identifier of a VNF instance of to-be-modified first-version VNF software; determining, by the VNFM, that a type of the VNF LCM request is a software modification operation, and obtaining metadata according to the VNF LCM request, where the metadata includes a version identifier of the first-version VNF software and a software modification type; determining, by the VNFM, a first VNF instance of the first-version VNF software based on the instance identifier of the VNF instance of the to-be-modified first-version VNF software; and initiating, by the VNFM, a software modification operation for the first VNF instance of the first-version VNF software based on the software modification type. According to embodiments of this application, automatic modification operations for VNF software in an NFV system can be implemented.