Distributed VNF unified upgrading method, device and medium

By configuring internal channels and data channels in distributed VNF, and using management virtual machines to uniformly manage and match upgrade files, the problems of inefficiency of existing VNF upgrade solutions and difficult to ensure version consistency, achieving efficient and reliable distributed VNF unified upgrade.

CN119088418APending Publication Date: 2024-12-06INSPUR NETWORK TECH (SHANDONG) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411152814.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-21
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

The existing VNF upgrade solutions are inefficient and prone to errors. Especially when the number of virtual machines is huge, it lacks automation and intelligent support, making it difficult to ensure version consistency and upgrade reliability.

Method used

By determining multiple virtual machines with the same VNF and configuring the same network segment, an internal control channel and data channel is formed, the management virtual machine is used for unified management, the upgrade file is matched according to the virtual machine type, and unified upgrade is carried out through the VNF manager, and concurrent upgrades are carried out.

Benefits of technology

Improves management efficiency, simplifies upgrade file management, provides flexible version control, significantly improves upgrade speed and system availability, and reduces downtime.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119088418A_ABST
    Figure CN119088418A_ABST
Patent Text Reader

Abstract

The invention discloses a distributed VNF unified upgrading method and device, and a medium, and relates to the technical field of computer networks. The method comprises the following steps: determining a plurality of virtual machines belonging to the same VNF, and configuring the same network segment on internal interfaces of the plurality of virtual machines to form an internal control channel and an internal data channel so as to perform unified management through a management virtual machine in the plurality of virtual machines; matching and naming the upgrade file of the corresponding type according to the type of the virtual machine, constructing a corresponding unified upgrade file after matching and naming, and uploading the unified upgrade file to a VNF manager; the VNF manager determines an upgrade file of a version to be upgraded according to a user demand, and sends an upgrade request to a corresponding management virtual machine; the unified upgrading file is decompressed through the management virtual machine so as to upgrade the management virtual machine, and if the management virtual machine is successfully upgraded, other virtual machines in the multiple virtual machines are sequentially triggered to conduct concurrent upgrading.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer network technology, and in particular to a distributed VNF unified upgrade method, device and medium. Background Art

[0002] In the current network virtualization environment, virtual network functions (VNF) under distributed architecture have become the key technology for realizing flexible and efficient network services. A typical distributed VNF consists of a management virtual machine (CTRL-VM), a business virtual machine (BIZ-VM), a forwarding virtual machine (FWD-VM), and a data virtual machine (DB-VM). These different types of virtual machines work together to realize the various functions of VNF. In order to ensure the high availability of the system, virtual machines of the same type are usually deployed on different servers in an active-standby stacking mode to avoid service interruption caused by single point failures.

[0003] In this architecture, CTRL-VM, as the core management component of VNF, is responsible for unified configuration, address management, license management, and elastic expansion and contraction. BIZ-VM focuses on processing business logic, such as remote interface management, user management, access control, authentication, authorization, and billing. FWD-VM is responsible for sending and receiving messages with external systems, while DB-VM plays an important role in data storage.

[0004] In order to effectively manage and maintain these distributed VNFs, the industry has introduced the VNF Manager (Virtualized Network Function Manager, VNF Manager), a virtual network function manager that complies with the ETSI NFV specification. The VNF Manager can not only manage multiple physical servers through the cloud host, but also flexibly configure resources according to user needs to complete the creation and deployment of VNF devices. At the same time, it can also establish a connection with the VNF device, issue the initial configuration, and manage the VNF throughout its life cycle.

[0005] However, in the existing VNF upgrade solution, users need to select and upgrade multiple virtual machines belonging to the same VNF one by one through the VNF manager, which is not only inefficient but also prone to errors. Especially when the network traffic increases and the number of virtual machines is huge, the one-by-one upgrade method is particularly cumbersome and inefficient. In addition, since different types of virtual machines require different upgrade files, how to ensure that the correct upgrade file is used to correspond to the correct type of virtual machine is also a major challenge facing the current upgrade solution. More importantly, multiple virtual machines belonging to the same VNF must maintain consistent versions to ensure that the overall functionality of the VNF is complete and available. The existing upgrade solution relies entirely on manual user operations and lacks automation and intelligent support, making it difficult to ensure version consistency and upgrade reliability. Summary of the invention

[0006] The embodiments of the present application provide a distributed VNF unified upgrade method, device and medium to solve the above-mentioned technical problems.

[0007] On the one hand, an embodiment of the present application provides a distributed VNF unified upgrade method, including:

[0008] Determine multiple virtual machines belonging to the same VNF, and configure the same network segment on the internal interfaces of the multiple virtual machines to form an internal control channel and an internal data channel, so as to perform unified management through a management virtual machine among the multiple virtual machines;

[0009] Match and name the upgrade files of the corresponding type according to the virtual machine type, construct a unified upgrade file corresponding to the matched name, and upload the unified upgrade file to the VNF manager;

[0010] The VNF manager determines the upgrade file of the version to be upgraded according to user requirements, and sends an upgrade request to the corresponding management virtual machine;

[0011] The unified upgrade file is decompressed by the management virtual machine to upgrade the management virtual machine. If the management virtual machine is successfully upgraded, other virtual machines in the multiple virtual machines are triggered in sequence to perform concurrent upgrades.

[0012] In one implementation of the present application, the determining of multiple virtual machines belonging to the same VNF and configuring the same network segment on the internal interfaces of the multiple virtual machines to form an internal control channel and an internal data channel specifically includes:

[0013] Constructing multiple virtual machines of the VNF, and deploying the multiple virtual machines on at least two computer node servers to determine that the multiple virtual machines logically belong to the same VNF;

[0014] Determine the virtual machine type corresponding to each virtual machine, and when the network between the at least two computer node servers is connected, configure the same network segment on the internal interfaces of the multiple virtual machines to establish a network connectivity relationship between the multiple virtual machines;

[0015] Internal control channels and internal data channels are formed between various virtual machines; wherein the internal control channel is used to transmit configuration sending control information and result reporting control information, and the internal data channel is used to transmit upgrade files.

[0016] In one implementation of the present application, the unified management through a management virtual machine among the multiple virtual machines specifically includes:

[0017] Determine a management virtual machine from the multiple virtual machines, and based on a link detection mechanism, detect single and double communication conditions between the management virtual machine and the service virtual machine, the forwarding virtual machine, and the data virtual machine;

[0018] After the single-pass and double-pass conditions are detected successfully, the corresponding detection results are recorded in the registration table corresponding to the management virtual machine, so that the successfully registered virtual machines can be managed by the management virtual machine to achieve unified management.

[0019] In one implementation of the present application, matching and naming the upgrade files of the corresponding types according to the virtual machine types, constructing the unified upgrade files corresponding to the matching names, and uploading the unified upgrade files to the VNF manager specifically include:

[0020] Receive the upgrade file uploaded by the user, and determine the upgrade file corresponding to each virtual machine type, so as to match and name the upgrade file of the corresponding type according to the virtual machine type;

[0021] Pack the upgrade files after matching names to build unified upgrade files corresponding to multiple virtual machines;

[0022] The unified upgrade file is uploaded to the VNF manager, and the unified upgrade file is uniformly managed through the VNF manager.

[0023] In one implementation of the present application, the VNF manager determines the upgrade file of the version to be upgraded according to user requirements, and sends an upgrade request to the corresponding management virtual machine, specifically including:

[0024] Receive user requirements, and operate the VNF manager based on the user requirements to select a corresponding VNF and determine an upgrade file for a version to be upgraded;

[0025] When it is determined that the virtual machine needs to be upgraded based on the upgrade file of the version to be upgraded, the VNF manager establishes a connection to the management virtual machine belonging to the same VNF through the NETCONF protocol and sends an upgrade request to the management virtual machine.

[0026] In an implementation of the present application, decompressing the unified upgrade file by the management virtual machine to upgrade the management virtual machine specifically includes:

[0027] The management virtual machine receives the unified upgrade file transmitted by the VNF manager, and decompresses the unified upgrade file through an internal parsing engine to determine the version to be upgraded corresponding to the management virtual machine in the unified upgrade file;

[0028] Performing a match check on the version to be upgraded of the management virtual machine and the current version of the management virtual machine, and upgrading the management virtual machine when the check passes;

[0029] If the upgrade of the management virtual machine fails, the entire upgrade process ends, and the final upgrade result of the virtual machine is recorded as failure.

[0030] In one implementation of the present application, if the management virtual machine is successfully upgraded, the other virtual machines in the multiple virtual machines are sequentially triggered to perform concurrent upgrades, specifically including:

[0031] If the management virtual machine is successfully upgraded, the upgrade files corresponding to the business virtual machine, the forwarding virtual machine, and the data virtual machine are respectively determined in the decompressed unified upgrade file, and the upgrade files of the corresponding types are transferred to the corresponding virtual machines according to the virtual machine types;

[0032] The business virtual machine, the forwarding virtual machine and the data virtual machine respectively compare the upgraded version of the corresponding virtual machine in the upgrade file with the current version of the corresponding virtual machine, and perform corresponding upgrade operations according to the upgraded version in the upgrade file when the version numbers are different.

[0033] In an implementation of the present application, after decompressing the unified upgrade file by the management virtual machine, the method further includes:

[0034] The management virtual machine subscribes to corresponding upgrade messages for each virtual machine that triggers the upgrade, and each virtual machine periodically reports the current upgrade status and the corresponding upgrade final state result to the management virtual machine;

[0035] If the final state result of the upgrade of the virtual machine is failure, the failure reason corresponding to the virtual machine is obtained, and if all registered virtual machines are upgraded successfully, the management virtual machine records the final state result of the overall upgrade as success.

[0036] On the other hand, an embodiment of the present application further provides a distributed VNF unified upgrade device, the device comprising:

[0037] at least one processor;

[0038] and, a memory communicatively coupled to the at least one processor;

[0039] Among them, the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute a distributed VNF unified upgrade method as described above.

[0040] On the other hand, an embodiment of the present application also provides a non-volatile computer storage medium storing computer executable instructions, which, when executed, implement a distributed VNF unified upgrade method as described above.

[0041] The embodiments of the present application provide a distributed VNF unified upgrade method, device and medium, which at least have the following beneficial effects:

[0042] By determining multiple virtual machines belonging to the same virtual network function VNF and configuring the same network segment on the internal interfaces of these virtual machines, internal control channels and internal data channels are formed. These multiple virtual machines can be managed uniformly through a management virtual machine, which significantly improves management efficiency and reduces management costs; the upgrade files of the corresponding types are matched and named according to the virtual machine type, and the corresponding unified upgrade files are constructed after the matching naming, which simplifies the management and identification process of the upgrade files and makes the upgrade operation more intuitive and efficient; the VNF manager can determine the upgrade file of the version to be upgraded according to user needs and send an upgrade request to the corresponding management virtual machine; a flexible version control mechanism is provided, so that on-demand upgrades can be performed according to actual needs, avoiding unnecessary upgrade operations and saving resources; the unified upgrade file is decompressed by the management virtual machine, the management virtual machine itself is upgraded, and other virtual machines in multiple virtual machines are triggered in turn for concurrent upgrades, which significantly improves the upgrade speed and reduces the overall downtime during the upgrade process, thereby improving the availability and stability of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0044] Figure 1 A flowchart of a distributed VNF unified upgrade method provided in an embodiment of the present application;

[0045] Figure 2 A schematic diagram of a distributed VNF architecture provided in an embodiment of the present application;

[0046] Figure 3 A schematic diagram of the internal structure of a distributed VNF unified upgrade device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0047] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0048] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0049] Figure 1 A flowchart of a distributed VNF unified upgrade method provided in an embodiment of the present application.

[0050] The analysis method involved in the embodiments of the present application can be implemented by a terminal device or a server, and the present application does not impose any special restrictions on this. For the convenience of understanding and description, the following embodiments are described in detail by taking a server as an example.

[0051] It should be noted that the server may be a single device or a system consisting of multiple devices, that is, a distributed server, and this application does not make any specific limitation on this.

[0052] like Figure 1 As shown, a distributed VNF unified upgrade method provided in an embodiment of the present application includes:

[0053] Step 101: Determine multiple virtual machines belonging to the same VNF, and configure the same network segment on the internal interfaces of the multiple virtual machines to form an internal control channel and an internal data channel, so as to perform unified management through the management virtual machine in the multiple virtual machines.

[0054] Specifically, in one embodiment of the present application, multiple virtual machines belonging to the same VNF are determined, and the same network segment is configured on the internal interfaces of the multiple virtual machines to form an internal control channel and an internal data channel, specifically including:

[0055] Building multiple virtual machines of the VNF, and deploying the multiple virtual machines on at least two computer node servers to determine that the multiple virtual machines logically belong to the same VNF;

[0056] Determine the virtual machine type corresponding to each virtual machine, and configure the same network segment on the internal interfaces of the multiple virtual machines when the network between at least two computer node servers is connected, so as to establish a network connectivity relationship between the multiple virtual machines;

[0057] Internal control channels and internal data channels are formed between various virtual machines; the internal control channel is used to transmit configuration delivery control information and result reporting control information, and the internal data channel is used to transmit upgrade files.

[0058] In one embodiment, multiple VMs constituting a VNF are deployed on at least two computing node servers. While ensuring smooth network connectivity between computing node servers, the same network segment is configured on the internal interfaces of multiple CTRL-VMs, BIZ-VMs, FWD-VMs, and DB-VMs that logically belong to the same VNF, thereby establishing a network connection relationship and forming an internal control channel and an internal data channel. The internal control channel can transmit control information such as configuration delivery and result reporting, and the internal data channel can transmit data information such as upgrade files.

[0059] In one embodiment, multiple virtual machines required for building a VNF include a management virtual machine (CTRL-VM), a business virtual machine (BIZ-VM), a forwarding virtual machine (FWD-VM), and a data virtual machine (DB-VM). These virtual machines are deployed on at least two computer node servers to ensure that they logically belong to the same VNF. In order to achieve high availability, virtual machines of the same type are deployed on different servers in an active-standby stacking manner.

[0060] Determine the type of each virtual machine. It should be noted that the virtual machine types in the embodiment of the present application include management virtual machine CTRL-VM, business virtual machine BIZ-VM, forwarding virtual machine FWD-VM and data virtual machine DB-VM. In the case of network connectivity between computer node servers, the same network segment is configured for the internal interfaces of multiple virtual machines to ensure that network connectivity can be established between them. In this way, different types of virtual machines can communicate and exchange data.

[0061] An internal control channel is established between virtual machines to transmit configuration delivery control information and result reporting control information. For example, CTRL-VM can deliver configuration information to other virtual machines through the internal control channel and receive the result information reported by them. At the same time, an internal data channel is established between virtual machines to transmit upgrade files. When the VNF needs to be upgraded, the upgrade file can be transferred from CTRL-VM to other virtual machines through the internal data channel.

[0062] Figure 2A schematic diagram of a distributed VNF architecture provided in an embodiment of the present application. Figure 2 As shown, the distributed VNF architecture includes multiple management virtual machines, multiple business virtual machines, multiple forwarding virtual machines, and multiple data virtual machines, and different types of virtual machines are connected through internal channels. It should be noted that the internal channels in the embodiment of the present application include internal control channels and internal data channels.

[0063] In one embodiment of the present application, unified management is performed through a management virtual machine among multiple virtual machines, specifically including:

[0064] A management virtual machine is determined from among the multiple virtual machines, and based on a link detection mechanism, single and double communication conditions between the management virtual machine and the business virtual machine, the forwarding virtual machine, and the data virtual machine are detected;

[0065] After the single-pass and double-pass detection is successful, the corresponding detection result is recorded in the registration table corresponding to the management virtual machine, so that the successfully registered virtual machine can be managed by the management virtual machine to achieve unified management.

[0066] In one embodiment, a management virtual machine (CTRL-VM) is determined among multiple virtual machines of the VNF, which is responsible for unified management of other types of virtual machines. A link detection mechanism is deployed on the CTRL-VM to detect the network connection status with other virtual machines (business virtual machine BIZ-VM, forwarding virtual machine FWD-VM, data virtual machine DB-VM).

[0067] Using the link detection mechanism on CTRL-VM, we start to detect the single-pass and double-pass conditions between CTRL-VM and BIZ-VM, FWD-VM, and DB-VM. Single-pass means that CTRL-VM can communicate with other virtual machines in one direction, while double-pass means that CTRL-VM can communicate with other virtual machines in two directions. During the detection process, we send detection messages and listen for responses to determine the status of the network connection.

[0068] Once the single-pass and double-pass detection is successful, CTRL-VM will record the corresponding detection results in its registry. The registry is used to store the information of all virtual machines in the VNF and the connection status between them and CTRL-VM. According to the detection results, CTRL-VM will manage the successfully registered virtual machines, that is, put them under unified management. Management operations include configuration delivery, status monitoring, fault recovery, etc. to ensure the overall functionality and availability of the VNF.

[0069] In one embodiment, the CTRL-VM on the computing node server can detect the single-pass situation with the BIZ-VM, FWD-VM and DB-VM through the link detection mechanism. After detecting the single-pass situation, the link is switched to detect the double-pass situation. Finally, multiple VMs that logically belong to the same VNF successfully detect the double-pass situation and record them in the registry of the CTRL-VM. The successfully registered VMs can be managed by the CTRL-VM for unified management.

[0070] Step 102: Match and name the upgrade files of the corresponding types according to the virtual machine types, construct the corresponding unified upgrade files after the matching names, and upload the unified upgrade files to the VNF manager.

[0071] Specifically, in one embodiment of the present application, matching and naming corresponding types of upgrade files according to the virtual machine type, constructing a unified upgrade file corresponding to the matching name, and uploading the unified upgrade file to the VNF manager specifically includes:

[0072] Receive the upgrade file uploaded by the user, and determine the upgrade file corresponding to each virtual machine type, so as to match and name the upgrade file of the corresponding type according to the virtual machine type;

[0073] Pack the upgrade files after matching names to build unified upgrade files corresponding to multiple virtual machines;

[0074] Upload the unified upgrade file to the VNF manager and manage the unified upgrade file through the VNF manager.

[0075] In one embodiment, the four upgrade files for upgrading CTRL-VM, BIZ-VM, FWD-VM and DB-VM are named according to type matching and packaged into a unified upgrade file. The upgrade packages of different versions are uploaded to the VNF manager, which is managed and maintained by the VNF manager.

[0076] In one embodiment, the upgrade files for VNF uploaded by the user are received. These files may include updates or repairs for the management virtual machine (CTRL-VM), the business virtual machine (BIZ-VM), the forwarding virtual machine (FWD-VM), and the data virtual machine (DB-VM). The uploaded upgrade files are analyzed to determine the upgrade files corresponding to each type of virtual machine. This step is to ensure that each type of virtual machine can obtain the correct upgrade content.

[0077] According to the virtual machine type, match and name the corresponding type of upgrade file. For example, the upgrade file for CTRL-VM is named "ctrl-vm-upgrade.zip", the upgrade file for BIZ-VM is named "biz-vm-upgrade.zip", and so on. The upgrade files with matching names are packaged to build a unified upgrade file that contains the upgrade files corresponding to multiple virtual machines. This unified upgrade file may be a larger compressed package that contains the upgrade files of all types of virtual machines.

[0078] Upload the built unified upgrade file to the VNF manager. The VNF manager is a system responsible for managing and maintaining VNF devices. It can manage the uploaded upgrade files in a unified manner. Through the VNF manager, users can more easily distribute, deploy, and monitor upgrade files. For example, users can select specific VNF devices or virtual machine types and send the corresponding upgrade files to these devices through the VNF manager.

[0079] Step 103: The VNF manager determines the upgrade file of the version to be upgraded according to user requirements, and sends an upgrade request to the corresponding management virtual machine.

[0080] Specifically, in one embodiment of the present application, the VNF manager determines the upgrade file of the version to be upgraded according to user requirements, and sends an upgrade request to the corresponding management virtual machine, specifically including:

[0081] Receive user requirements and operate the VNF manager based on the user requirements to select the corresponding VNF and determine the upgrade file of the version to be upgraded;

[0082] When it is determined that the virtual machine needs to be upgraded based on the upgrade file of the version to be upgraded, the VNF manager establishes a connection with the management virtual machine belonging to the same VNF through the NETCONF protocol and sends an upgrade request to the management virtual machine.

[0083] In one embodiment, in order to facilitate lifecycle management and version management of CTRL-VM, BIZ-VM, FWD-VM and DB-VM that logically belong to the same VNF, the VNF manager constructs a logical list of VNFs. The deployment, deletion and upgrade operations of the VNF correspond to the deployment, deletion and upgrade operations of the CTRL-VM, BIZ-VM, FWD-VM and DB-VM to which it belongs.

[0084] The user operates the VNF manager according to the needs, selects a VNF, selects the upgrade file of the version to be upgraded, and performs a unified upgrade operation. After confirming the upgrade, the VNF manager establishes a connection with the CTRL-VM that logically belongs to the VNF through the XML-based network management protocol NETCONF protocol and sends an upgrade request.

[0085] In one embodiment, the upgrade requirements submitted by the user through the interface or API are received, and these requirements include the VNF information that needs to be upgraded and the expected version number. Based on the user's requirements, the VNF manager is operated to select the corresponding VNF. The VNF manager is a system that centrally manages VNF devices and can display the status and version information of all VNFs.

[0086] In the VNF manager, determine the upgrade file of the version to be upgraded based on the version number required by the user. This upgrade file contains all the changes and fixes required to upgrade the VNF from the current version to the target version. Ensure the integrity and correctness of the upgrade file so that no errors or data loss occur during the upgrade process.

[0087] Based on the upgrade file of the version to be upgraded, the VNF manager checks whether the VMs belonging to the selected VNF need to be upgraded. This usually involves comparing the current version of the VM with the target version. If the VM is already the latest version, no upgrade operation is required. Otherwise, the upgrade process will continue.

[0088] When it is determined that the VM needs to be upgraded, the VNF manager will establish a connection to the management VM (CTRL-VM) belonging to the same VNF through the NETCONF protocol. Once the connection is established, the VNF manager will send an upgrade request to the management VM, which includes the upgrade file path, version information, and upgrade instructions. After receiving the upgrade request, the management VM will start to perform the upgrade operation and return the upgrade result to the VNF manager.

[0089] Step 104: decompress the unified upgrade file through the management virtual machine to upgrade the management virtual machine. If the management virtual machine is upgraded successfully, other virtual machines in the multiple virtual machines are triggered in sequence to perform concurrent upgrades.

[0090] Specifically, in one embodiment of the present application, decompressing the unified upgrade file by the management virtual machine to upgrade the management virtual machine specifically includes:

[0091] The management virtual machine receives the unified upgrade file transmitted by the VNF manager, and decompresses the unified upgrade file through the internal parsing engine to determine the version to be upgraded corresponding to the management virtual machine in the unified upgrade file;

[0092] The version to be upgraded of the management virtual machine is matched and verified with the current version of the management virtual machine, and when the verification passes, the management virtual machine is upgraded;

[0093] If the management virtual machine upgrade fails, the entire upgrade process ends and the final upgrade result of the virtual machine is recorded as failure.

[0094] In one embodiment, CTRL-VM receives a unified upgrade file transmitted by the VNF manager, and the internal parsing engine first parses and decompresses the upgrade file. After CTRL-VM receives the actual upgrade operation instruction, it first matches and verifies the upgrade version of CTRL-VM itself. After the upgrade file passes the verification, the CTRL-VM itself upgrade process begins. Then, the unified upgrade file is parsed and classified into upgrade files of the corresponding four VM types. After distinguishing the types according to the names, they are passed to the successfully registered BIZ-VM, FWD-VM and DB-VM respectively through the internal data channel. The file parsing engine of CTRL-VM ensures the matching and verification of the four upgrade files with the corresponding types of VMs.

[0095] In one embodiment, the management virtual machine (CTRL-VM) receives a unified upgrade file transmitted from the VNF manager. This file contains the upgrade content corresponding to all types of virtual machines in the VNF. CTRL-VM decompresses the received unified upgrade file through an internal parsing engine to extract the version file to be upgraded corresponding to CTRL-VM. The parsing engine analyzes the file structure to ensure that the upgrade data required for the management virtual machine is correctly extracted.

[0096] Verify the extracted version to be upgraded against the current version of CTRL-VM. This step is to ensure that the upgrade file version is compatible with the currently running virtual machine version. If the versions do not match, the upgrade process will be aborted and the corresponding error message will be recorded.

[0097] If the version match check passes, CTRL-VM will start to perform the upgrade operation. This includes applying new configurations, updating software components, etc. During the upgrade process, CTRL-VM will monitor the progress and ensure that all changes are applied correctly.

[0098] After the upgrade is complete, CTRL-VM will perform a self-check to confirm whether the upgrade was successful. If the upgrade fails (for example, due to a configuration error or software conflict), the entire upgrade process will end and the VM's upgrade final state will be recorded as failed. If the upgrade is successful, CTRL-VM will notify the VNF manager and update its status information to reflect the new version.

[0099] In one embodiment of the present application, if the management virtual machine is successfully upgraded, the other virtual machines in the multiple virtual machines are sequentially triggered to perform concurrent upgrades, specifically including:

[0100] If the management virtual machine is upgraded successfully, the upgrade files corresponding to the business virtual machine, forwarding virtual machine and data virtual machine are determined in the decompressed unified upgrade file, and the upgrade files of the corresponding types are transferred to the corresponding virtual machines according to the virtual machine types;

[0101] The business virtual machine, forwarding virtual machine and data virtual machine respectively compare the upgrade version of the corresponding virtual machine in the upgrade file with the current version of the corresponding virtual machine, and perform corresponding upgrade operations according to the upgrade version in the upgrade file when the version numbers are different.

[0102] In one embodiment, if the CTRL-VM upgrade fails, the entire upgrade process ends and the overall upgrade result is recorded as failure. If the CTRL-VM upgrade succeeds, the registered FWD-VM, BIZ-VM, and DB-VM will continue to be triggered to upgrade concurrently. During this process, CTRL-VM subscribes to the upgrade messages of various VMs that trigger the upgrade, and various VMs periodically report the current upgrade status and upgrade results to CTRL-VM until the upgrade process ends. Finally, CTRL-VM records the upgrade result list of each registered VM and the overall upgrade status. Only when all registered VMs are upgraded successfully, CTRL-VM records the overall upgrade result as success.

[0103] In one embodiment of the present application, after decompressing the unified upgrade file by managing the virtual machine, the method further includes:

[0104] The management virtual machine subscribes to the corresponding upgrade message for each virtual machine that triggers the upgrade, and each virtual machine periodically reports the current upgrade status and the corresponding upgrade final state result to the management virtual machine;

[0105] If the final state result of the upgrade of the virtual machine is failure, the failure reason corresponding to the virtual machine is obtained. If all registered virtual machines are upgraded successfully, the management virtual machine records the final state result of the overall upgrade as success.

[0106] In one embodiment, due to the large number of VMs to be upgraded under a VNF and the unstable network conditions, the actual upgrade process may take a long time. In order to enable users to perceive the upgrade process, the VNF Manager will record the VNF status list and the status lists of various VMs belonging to it and display them on the visualization page, where the VNF list displays the overall upgrade status and version information, and the VM list displays the upgrade status and version information of each VM separately. After each VM successfully completes the upgrade, the system version information in the VM list will be updated to the new version name after the upgrade. Only when all VMs are successfully upgraded, the system version information in the VNF list will be updated to the new version name after the upgrade, otherwise the version information in the VNF list will not change. After the VNF Manager successfully sends the upgrade request, it will initiate a NETCONF request for message subscription to the CTRL-VM, periodically obtain the upgrade results of each VM from the CTRL-VM, and record the results in the list.

[0107] The upgrade status is divided into in-progress and completed, marked as Process and Finish respectively. If the VNF Manager finds that the upgrade process of the VM is still in progress, the unstable intermediate state of the upgrade is recorded as Process and displayed in the VM list in the form of a dynamic icon, indicating that the upgrade is in progress. If the upgrade process of a VM is found to be completed, the upgrade status of the VM in the VM list is recorded as Finish, indicating that the upgrade is completed. The list item of the successfully upgraded VM will display the new system version name after the upgrade, and the original system version name will be retained if the upgrade fails. The VNF list item will only display the new system version name after the upgrade if all VMs that logically belong to the same VNF are successfully upgraded. At the same time, the system log list will display the final upgrade results and possible reasons for failure of each CTRL-VM, BIZ-VM, FWD-VM and DB-VM that logically belongs to this VNF.

[0108] Due to network anomalies and other reasons, the upgrade of a certain network element may fail during the process. If the upgrade is completed and the user observes that the name of the upgraded version is not updated for this VNF list item, the upgrade results and possible reasons for failure of each VM logically belonging to this VNF can be viewed in the system log list. After the user corrects the possible anomalies, the overall upgrade operation can be performed on this VNF again through VNFManager.

[0109] Since the successfully upgraded VM will perform version comparison verification when receiving the upgrade request, the upgraded VM will not perform any operation. Therefore, when executing the upgrade correction request again, only the VM that failed to upgrade last time will actually perform the upgrade, and there will be no redundant operations.

[0110] The above is an embodiment of the method proposed in this application. Based on the same inventive concept, the embodiment of this application also provides a distributed VNF unified upgrade device, whose structure is as follows Figure 2 shown.

[0111] Figure 2 This is a schematic diagram of the internal structure of a distributed VNF unified upgrade device provided in an embodiment of the present application. Figure 2 As shown, the device includes:

[0112] at least one processor 201;

[0113] and a memory 202 communicatively connected to the at least one processor 201;

[0114] The memory 202 stores instructions that can be executed by at least one processor 201, and the instructions are executed by at least one processor 201 to enable at least one processor 201 to:

[0115] Identify multiple virtual machines belonging to the same VNF, and configure the same network segment on the internal interfaces of the multiple virtual machines to form internal control channels and internal data channels, so as to perform unified management through the management virtual machine in the multiple virtual machines;

[0116] Match and name the upgrade files of the corresponding types according to the virtual machine types, build the corresponding unified upgrade files after matching the names, and upload the unified upgrade files to the VNF manager;

[0117] The VNF manager determines the upgrade file of the version to be upgraded according to user requirements and sends an upgrade request to the corresponding management virtual machine;

[0118] The unified upgrade file is decompressed through the management virtual machine to upgrade the management virtual machine. If the management virtual machine is upgraded successfully, other virtual machines in the multiple virtual machines are triggered in sequence to be upgraded concurrently.

[0119] The present application also provides a non-volatile computer storage medium storing computer executable instructions. When the computer executable instructions are executed, they can:

[0120] Identify multiple virtual machines belonging to the same VNF, and configure the same network segment on the internal interfaces of the multiple virtual machines to form internal control channels and internal data channels, so as to perform unified management through the management virtual machine in the multiple virtual machines;

[0121] Match and name the upgrade files of the corresponding types according to the virtual machine types, build the corresponding unified upgrade files after matching the names, and upload the unified upgrade files to the VNF manager;

[0122] The VNF manager determines the upgrade file of the version to be upgraded according to user requirements and sends an upgrade request to the corresponding management virtual machine;

[0123] The unified upgrade file is decompressed through the management virtual machine to upgrade the management virtual machine. If the management virtual machine is upgraded successfully, other virtual machines in the multiple virtual machines are triggered in sequence to be upgraded concurrently.

[0124] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0125] The above describes specific embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0126] The devices and media provided in the embodiments of the present application correspond one-to-one to the methods. Therefore, the devices and media also have similar beneficial technical effects as the corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0127] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0128] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0129] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0130] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0131] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0132] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0133] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0134] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0135] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A distributed VNF unified upgrade method, It is characterized in that The method comprises: Determine multiple virtual machines belonging to the same VNF, and configure the same network segment on the internal interfaces of the multiple virtual machines to form an internal control channel and an internal data channel, so as to perform unified management through a management virtual machine among the multiple virtual machines; Match and name the upgrade files of the corresponding type according to the virtual machine type, construct a unified upgrade file corresponding to the matched name, and upload the unified upgrade file to the VNF manager; The VNF manager determines the upgrade file of the version to be upgraded according to user requirements, and sends an upgrade request to the corresponding management virtual machine; The unified upgrade file is decompressed by the management virtual machine to upgrade the management virtual machine. If the management virtual machine is successfully upgraded, other virtual machines in the multiple virtual machines are triggered in sequence to perform concurrent upgrades.

2. A distributed VNF unified upgrade method according to claim 1, It is characterized in that The determining of multiple virtual machines belonging to the same VNF and configuring the same network segment on the internal interfaces of the multiple virtual machines to form an internal control channel and an internal data channel specifically includes: Constructing multiple virtual machines of the VNF, and deploying the multiple virtual machines on at least two computer node servers to determine that the multiple virtual machines logically belong to the same VNF; Determine the virtual machine type corresponding to each virtual machine, and when the network between the at least two computer node servers is connected, configure the same network segment on the internal interfaces of the multiple virtual machines to establish a network connectivity relationship between the multiple virtual machines; Internal control channels and internal data channels are formed between various virtual machines; wherein the internal control channel is used to transmit configuration sending control information and result reporting control information, and the internal data channel is used to transmit upgrade files.

3. A distributed VNF unified upgrade method according to claim 1, It is characterized in that The unified management through a management virtual machine among the multiple virtual machines specifically includes: Determine a management virtual machine from the multiple virtual machines, and based on a link detection mechanism, detect single and double communication conditions between the management virtual machine and the service virtual machine, the forwarding virtual machine, and the data virtual machine; After the single-pass and double-pass conditions are detected successfully, the corresponding detection results are recorded in the registration table corresponding to the management virtual machine, so that the successfully registered virtual machines can be managed by the management virtual machine to achieve unified management.

4. A distributed VNF unified upgrade method according to claim 1, It is characterized in that The matching and naming of the upgrade files of the corresponding types according to the virtual machine types, constructing the unified upgrade files corresponding to the matched names, and uploading the unified upgrade files to the VNF manager specifically includes: Receive the upgrade file uploaded by the user, and determine the upgrade file corresponding to each virtual machine type, so as to match and name the upgrade file of the corresponding type according to the virtual machine type; Pack the upgrade files after matching names to build a unified upgrade file corresponding to multiple virtual machines; The unified upgrade file is uploaded to the VNF manager, and the unified upgrade file is uniformly managed through the VNF manager.

5. A distributed VNF unified upgrade method according to claim 1, It is characterized in that The VNF manager determines the upgrade file of the version to be upgraded according to the user's needs, and sends an upgrade request to the corresponding management virtual machine, specifically including: Receive user requirements, and operate the VNF manager based on the user requirements to select a corresponding VNF and determine an upgrade file for a version to be upgraded; When it is determined that the virtual machine needs to be upgraded based on the upgrade file of the version to be upgraded, the VNF manager establishes a connection to the management virtual machine belonging to the same VNF through the NETCONF protocol and sends an upgrade request to the management virtual machine.

6. A distributed VNF unified upgrade method according to claim 1, It is characterized in that Decompressing the unified upgrade file by the management virtual machine to upgrade the management virtual machine specifically includes: The management virtual machine receives the unified upgrade file transmitted by the VNF manager, and decompresses the unified upgrade file through an internal parsing engine to determine the version to be upgraded corresponding to the management virtual machine in the unified upgrade file; Performing a match check on the version to be upgraded of the management virtual machine and the current version of the management virtual machine, and upgrading the management virtual machine when the check passes; If the upgrade of the management virtual machine fails, the entire upgrade process ends, and the final upgrade result of the virtual machine is recorded as failure.

7. A distributed VNF unified upgrade method according to claim 1, It is characterized in that If the management virtual machine is successfully upgraded, the other virtual machines in the multiple virtual machines are sequentially triggered to perform concurrent upgrades, specifically including: If the management virtual machine is successfully upgraded, the upgrade files corresponding to the business virtual machine, the forwarding virtual machine, and the data virtual machine are respectively determined in the decompressed unified upgrade file, and the upgrade files of the corresponding types are transferred to the corresponding virtual machines according to the virtual machine types; The business virtual machine, the forwarding virtual machine and the data virtual machine respectively compare the upgraded version of the corresponding virtual machine in the upgrade file with the current version of the corresponding virtual machine, and perform corresponding upgrade operations according to the upgraded version in the upgrade file when the version numbers are different.

8. A distributed VNF unified upgrade method according to claim 1, It is characterized in that After decompressing the unified upgrade file by the management virtual machine, the method further includes: The management virtual machine subscribes to corresponding upgrade messages for each virtual machine that triggers the upgrade, and each virtual machine periodically reports the current upgrade status and the corresponding upgrade final state result to the management virtual machine; If the final state result of the upgrade of the virtual machine is failure, the failure reason corresponding to the virtual machine is obtained, and if all registered virtual machines are upgraded successfully, the management virtual machine records the final state result of the overall upgrade as success.

9. A distributed VNF unified upgrade device, It is characterized in that The device comprises: at least one processor; and, a memory communicatively coupled to the at least one processor; The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute a distributed VNF unified upgrade method as described in any one of claims 1-8.

10. A non-volatile computer storage medium storing computer executable instructions, It is characterized in that When the computer executable instructions are executed, a distributed VNF unified upgrade method as described in any one of claims 1 to 8 is implemented.