WO2023050947A1 - Network upgrade method, electronic device and storage medium - Google Patents

Abstract

A network upgrade method, an electronic device and a storage medium. The network upgrade method can be applied to an infrastructure entity, a network function entity or a management orchestration entity. When a host device in an infrastructure entity is upgraded, first host device information that represents a host device in a first group is first sent to a management orchestration entity, the management orchestration entity obtains a service migration request according to the first host device information and sends the service migration request to a network function entity, and the network function entity performs, according to the service migration request, migration processing on a service of a virtual machine corresponding to the first host device information. Since the service that is deployed on the virtual machine of the host device in the first group has been migrated to another host device that does not need an upgrade, the infrastructure entity then performs upgrade processing on the host device, the service migration of which has been completed.

Description

Network upgrade method, electronic equipment and storage medium

Cross References to Related Applications

This application is based on a Chinese patent application with application number 202111152285.7 and a filing date of September 29, 2021, and claims the priority of this Chinese patent application. The entire content of this Chinese patent application is hereby incorporated by reference into this application.

technical field

The present application relates to the technical field of communications, and in particular to a network upgrading method, electronic equipment and a storage medium.

Background technique

The European Telecommunications Standards Institute (ETSI) provides a reference architecture for network function virtualization (Network Functions Virtualization, NFV), which is dedicated to the deployment and implementation of network function virtualization in telecommunications. Referring to the NFV architecture design, you can To achieve a unified construction of the infrastructure layer, a large number of virtualized network functions (Virtual Network Feature, VNF) can be deployed in a data center (Data Center, DC), that is, a hardware resource pool. In related technologies, with the development of network function virtualization infrastructure (NFV infrastructure, NFVI) technology, it is necessary to upgrade or restart the devices in the hardware resource pool, and the virtual machines deployed on NFVI will also be affected. During the restart process, operations such as shutting down and restarting the virtual machine are required, resulting in interruption of network services.

Contents of the invention

The following is an overview of the topics described in detail in this article. This summary is not intended to limit the scope of the claims.

Embodiments of the present application provide a network upgrading method, electronic equipment, and a storage medium.

In the first aspect, the embodiment of the present application provides a network upgrade method, which is applied to an infrastructure entity, and the infrastructure entity is connected to a management orchestration entity, and the management orchestration entity is connected to a network function entity, and the infrastructure entity includes A plurality of host devices, each of which includes a plurality of virtual machines, the method includes: sending first host device information to the management and orchestration entity, the first host device information being represented by the first host device in the first group the host device, so that the management and orchestration entity sends a service migration request to the network function entity according to the information of the first host device, so that the network function entity transfers the first host device according to the service migration request Migrate the services of the virtual machines corresponding to the device information; receive service migration completion information sent by the management and orchestration entity; perform upgrade processing on the host devices in the first group according to the service migration completion information.

In the second aspect, the embodiment of the present application also provides a network upgrade method, which is applied to a network function entity, the network function entity is connected to a management orchestration entity, the management orchestration entity is connected to an infrastructure entity, and the infrastructure entity It includes a plurality of host devices, each of which includes a plurality of virtual machines, and the method includes: receiving a service migration request sent by the management and orchestration entity, the service migration request being the management and orchestration entity according to the basis Generated by the first host device information sent by the facility entity, the first host device information is characterized as the host device in the first group; according to the service migration request, the virtual machine corresponding to the first host device information Migrate the business; send business migration success information to the management and orchestration entity, so that the management and orchestration entity sends service migration completion information to the infrastructure entity according to the business migration success information, so that the infrastructure The entity performs upgrade processing on the host devices in the first group according to the service migration completion information.

In a third aspect, the embodiment of the present application also provides a network upgrade method, which is applied to a management and orchestration entity, and the management and orchestration entity is respectively connected to an infrastructure entity and a network function entity, and the infrastructure entity includes a plurality of host devices, Each of the host devices includes a plurality of virtual machines, and the method includes: receiving first host device information sent by the infrastructure entity, the first host device information representing the host devices in the first group ; Sending a service migration request to the network function entity according to the first host device information, so that the network function entity performs migration processing on the service of the virtual machine corresponding to the first host device information according to the service migration request ; receiving service migration success information sent by the network function entity, and sending service migration completion information to the infrastructure entity according to the service migration success information, so that the infrastructure entity completes service migration information according to the service migration completion information performing upgrade processing on the host devices in the first group.

In the fourth aspect, the embodiment of the present application also provides an electronic device, which includes a memory and a processor, the memory stores a computer program, and when the processor executes the computer program, the computer program implemented in the first aspect of the present application is implemented. The network upgrade method described in the example, or the network upgrade method described in the embodiment of the second aspect of the present application, or the network upgrade method described in the embodiment of the third aspect of the present application.

In the fifth aspect, the embodiment of the present application further provides a computer-readable storage medium, the storage medium stores a program, and the program is executed by the processor to implement the network upgrade method described in the embodiment of the first aspect of the present application, Or the network upgrade method described in the embodiment of the second aspect of the present application, or the network upgrade method described in the embodiment of the third aspect of the present application.

Additional features and advantages of the application will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the application. The objectives and other advantages of the application will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Description of drawings

The accompanying drawings are used to provide a further understanding of the technical solution of the present application, and constitute a part of the specification, and are used together with the embodiments of the present application to explain the technical solution of the present application, and do not constitute a limitation to the technical solution of the present application.

Fig. 1 is a NFV system architecture diagram provided by an embodiment of the present application;

FIG. 2 is a schematic flowchart of a network upgrade method provided by an embodiment of the present application;

FIG. 3 is a schematic flowchart of a network upgrade method provided in another embodiment of the present application;

FIG. 4 is a schematic diagram of domain-specific deployment provided by an embodiment of the present application;

FIG. 5 is a schematic flowchart of a network upgrade method provided in another embodiment of the present application;

FIG. 6 is a schematic flowchart of a network upgrade method provided in another embodiment of the present application;

FIG. 7 is a schematic flowchart of a network upgrade method provided in another embodiment of the present application;

FIG. 8 is a schematic flowchart of a network upgrade method provided in another embodiment of the present application;

FIG. 9 is an upgrade flowchart of a network upgrade method provided by an embodiment of the present application;

Fig. 10 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solution and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present application, not to limit the present application.

It should be understood that in the description of the embodiments of the present application, multiple (or multiple) means more than two, greater than, less than, exceeding, etc. are understood as not including the original number, and above, below, within, etc. are understood as including the original number. If there is a description of "first", "second", etc., it is only for the purpose of distinguishing technical features, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features or implicitly indicating the indicated The sequence relationship of the technical characteristics.

ETSI's NFV reference architecture is shown in Figure 1. The NFV system architecture can be divided into management and orchestration domain (Management and Orchestration, MANO), business network domain and infrastructure domain. The business network domain is VNF, and the infrastructure domain is NFVI. The domain is responsible for the management and orchestration of the entire NFVI resource, and manages the VNF life cycle. VNF refers to the current telecom service network, and NFVI refers to the virtualization infrastructure, that is, the virtualization of computing, storage, and network. Network cloud technologies such as virtualization improve the utilization of system resources, effectively break the bottleneck of resource utilization, reduce hardware and operating costs, simplify operation and maintenance, reduce management costs, shorten service innovation and online time, and help telecom operators make more More time and cost are transferred to business investment, providing customers with a more friendly business experience, and ultimately creating value. Referring to the NFV architecture design, it is possible to achieve a unified construction of the infrastructure layer and deploy a large number of VNFs in one DC. With the participation of various equipment vendors, operators, technical organizations, etc., the decoupling of VNF and NFVI has been realized, so it also has the ability to deploy a large number of VNFs to a DC. Currently, there are already deployments in a single DC of an operator. There are a large number of VNFs, and the number of virtual machines reaches more than 10,000. Due to various reasons such as security hardening, hardware firmware upgrades, operating system upgrades, and network facility upgrades, devices in the resource pool will restart, causing servers, network devices, storage devices, etc. to restart or be interrupted, and virtual machines deployed on NFVI will also be affected. It is necessary to perform operations such as virtual shutdown and restart, which will inevitably affect VNF services and interrupt VNF services. With the construction of large-scale DCs and VNF deployments, how to ensure that VNFs will not be affected and services will not be interrupted when NFVI is upgraded becomes increasingly problematic. urgent. Inside the VNF, the business itself has a reliability design, and there are multiple mechanisms such as active/standby or load sharing among the modules to ensure the reliability of the service itself. When a virtual machine in the active/standby virtual machine is reset, it can realize uninterrupted business ; When one or several virtual machines among the load sharing virtual machines are reset, no service interruption can be realized.

Based on this, the embodiments of the present application provide a network upgrade method, electronic equipment, and a storage medium, which can realize uninterrupted network services during the network upgrade process.

It should be noted that the infrastructure entity in the embodiment of the present application is connected to the management and orchestration entity, and the management and orchestration entity is connected to the network function entity. The infrastructure entity includes multiple host devices, and each host device includes multiple virtual machines. This application The infrastructure entity in the embodiment can be the infrastructure domain in the NFV system architecture, and can also be cloud infrastructure such as cloud and resource pool; the network function entity can be the business network domain in the NFV system architecture, or it can be APP, upper layer Software such as applications and network functional entities can be used as standard telecom network elements. The network functional entity is essentially software, and its carrier is a virtual machine in the infrastructure entity. The hardware equipment of the virtual machine is generated by software simulation; management and orchestration The entity can be the management orchestration domain in the NFV system architecture, and can also be implemented by other logical entities or functional components, which can provide orchestration and management for the network function entity. In the embodiment of this application, the infrastructure entity is the infrastructure domain, and the network function The entity is a service network domain, and the management orchestration entity is an example of a management orchestration domain, but this is not a limitation of this embodiment of the application.

Based on the NFV system architecture shown in FIG. 1 , referring to FIG. 2 , an embodiment of the present application provides a network upgrade method applied to an infrastructure entity. The network upgrade method includes but is not limited to the following steps S110 to S130.

Step S110, sending the first host device information to the management and arrangement entity, the first host device information is characterized as a host device in the first group, so that the management and arrangement entity sends a service migration request to the network function entity according to the first host device information, so that the network function entity migrates the service of the virtual machine corresponding to the first host device information according to the service migration request.

In one embodiment, the information of the first host device is represented as host devices in the first group, and the infrastructure entity divides multiple host devices into multiple groups, and when upgrading the hosts in the first batch, the The host device in the first group performs upgrade processing, and before the upgrade process, first sends the first host device information to the management and arrangement entity, so that the management and arrangement entity sends a service migration request to the network function entity according to the first host device information so that the network function entity migrates the service of the virtual machine corresponding to the first host device information according to the service migration request.

It should be noted that the first host device information is the list information of the host devices in the first group that needs to be upgraded, and the infrastructure entity sends the list information of this batch of host devices that need to be upgraded to the management and arrangement entity, so as to Perform upgrade processing.

Step S120, receiving service migration completion information sent by the management and arrangement entity.

In an embodiment, in response to the first host device information sent by the basic device entity, the network function entity migrates the business of the virtual machine corresponding to the first host device information to other hosts that do not need to be upgraded temporarily. In the virtual machine, after the service migration is completed, the service migration completion information is generated by the management and orchestration entity after the business of the virtual machine corresponding to the first host device information is migrated, and the network function entity feeds back the service migration success information to the management and orchestration entity, Then the management and orchestration entity sends the service migration completion information to the infrastructure entity according to the business migration success information. It should be noted that the service migration completion information and the service migration success information can be information in the same field, or information in different fields. The embodiments of the present application do not specifically limit it.

Step S130, upgrade the host devices in the first group according to the service migration completion information.

In one embodiment, the infrastructure device entity receives service migration completion information, indicating that the virtual machine services on the host devices in the first group have been migrated. The impact on the business will not lead to business interruption, so the basic device entity upgrades the host devices in the first group to complete the upgrade process of this batch of host devices.

It should be noted that the first group may include multiple host devices, including a first host device and a second host device, and the first host device may be a single host device or a device group composed of multiple sub-host devices, The second host device can be a single host device or a device group composed of multiple sub-host devices. The network upgrade method in the embodiment of the present application can be to first upgrade the network of the first host device, and the infrastructure entity first sends a sub-host device containing the first group The first host device information of the first host device in the group is sent to the management and arrangement entity to migrate the virtual machine business on the first host device. After the migration is completed, the first host device is upgraded and then sent to the first group. The device information of the second host device is sent to the management and arrangement entity to upgrade the second host device. It can be understood that the upgrade of the first host device and the second host device is performed for the infrastructure entity for different host devices. The batch upgrade avoids service interruption and improves the reliability of the upgrade. The upgrade process includes shutting down or restarting the host device or the virtual machine on the host device, which is not specifically limited in this embodiment of the application.

It should be noted that the first group may include multiple host devices, including a first host device and a second host device, and the first host device may be a single host device or a device group composed of multiple sub-host devices, The second host device may be a single host device or a device group composed of multiple sub-host devices, and the network upgrade method in the embodiment of the present application may be a network upgrade for the first host device, wherein the second host device has completed the upgrade process , so the basic device entity can perform network upgrades for the remaining first host devices in the first group. The batch upgrade of the host device avoids service interruption and improves the reliability of the upgrade.

It can be understood that the network upgrade method in the embodiment of the present application can realize large-scale host device upgrades, divide the host devices into multiple batches, and the host devices in the first group specifically refer to the current batches that need to be upgraded The host devices are upgraded in batches, and during the upgrade process of each batch of host devices, the business on the virtual machine of the host device is migrated to the virtual machines of other host devices, avoiding the During the upgrade process of the internal host device, network services are interrupted. Therefore, the embodiment of the present application is applicable to large-scale scenarios, and the operation is simple, and the large-scale upgrade takes a short time.

In an embodiment, the above step S110 may further include: sending the first host device information to the management and orchestration entity, so that the management and orchestration entity sends a service migration request to the network function entity according to the first host device information, so that the network function entity according to The service migration request migrates the service of the virtual machine corresponding to the first host device information to the virtual machine corresponding to the second host device information, and the second host device information is represented as a host device in the second group.

In an embodiment, the infrastructure entity is provided with a plurality of host devices, and can be grouped, including being divided into a first group and a second group, wherein, in the process of upgrading the host devices in the first group The business of the virtual machine corresponding to the first host device information can be migrated to the virtual machine corresponding to the second host device information, and the second host device information is characterized as a host device in the second group, thereby avoiding confusion in business division, To ensure the reliability of the business, on the premise of meeting the requirements of the embodiment of this application, during the process of upgrading the first host device in the first group, the business of the virtual machine corresponding to the first host device can be migrated to the first On the virtual machine corresponding to the second host device in the group, the embodiment of the present application takes the virtual machine migrated to the host device in the second group as an example, but this is not meant to limit the embodiment of the present application.

Referring to FIG. 3 , in an embodiment, before the above step S110 , it may also include but not limited to the following steps S210 to S220 .

Step S210, receiving virtual machine domain division information sent by the management and orchestration entity.

Step S220, grouping multiple host devices according to the virtual machine domain information to obtain first host device information and second host device information.

In one embodiment, the network function entity performs grouping processing during service deployment, the virtual machine domain information is obtained by the management and orchestration entity according to the network function entity, and then the infrastructure entity receives the virtual machine domain information sent by the management and orchestration entity, and according to the The virtual machine domain information is grouped, including grouping multiple host devices according to the virtual machine domain information to obtain the first host device information and the second host device information, wherein the first host device information and the second host device information The information respectively represents the host devices in the first group and the host devices in the second group. During the process of upgrading the host devices in the first group, after the network function entity divides the virtual machines into domains, the infrastructure Entities are upgraded in batches based on the grouping obtained from the virtual machine domain information. It should be noted that the first group and the second group are only for distinguishing technical features, and the second group can be characterized as the infrastructure entities except the first group. A certain group other than the first group, multiple groups other than the first group, or a certain group among the multiple groups other than the first group are not specifically limited in this application.

Referring to Fig. 4, in one embodiment of the above method, first add a plurality of sub-HAs under the planned host cluster (HostAggregate, HA), that is, carry out domain division, which is also equivalent to grouping, and define sub-HAs as SHA, The number of SHAs can be set according to actual needs. The host cluster includes multiple host devices, and the SHA can be a single host device or a device group consisting of multiple sub-host devices. During the deployment process of the network function entity, that is, the VNF, for the deployment of the VNF The virtual machine is divided into domains, and the host devices of the virtual machines with the same domain are divided into the same group. For example, the VNFs configured on the virtual machines of the host devices in the first group are under the same domain, so in In the process of upgrading the host devices in the first group, the virtual machines deployed with other domain-specific VNFs will not be upgraded, so that the virtual machines in the same domain can be upgraded in the same batch, thereby avoiding business division confusion and ensuring For service reliability, it can be understood that the first group may be a certain SHA, and may also include multiple SHAs.

In an embodiment, the virtual machine domain division information is obtained by the network function entity after performing domain division processing according to the virtual machine type information and the virtual machine quantity information. The network function entity obtains a certain number of domains according to the type information of the virtual machine, and labels all virtual machines with domain division. The type information of the virtual machine corresponds to the domain division of the network function entity, and combines the number of virtual machines The information obtains the number of virtual machines, and the virtual machines are divided into domains based on the above characteristics, so that the divided virtual machines can be deployed to the same host device.

In an embodiment of the above method, the VNF is divided into multiple sub-domains according to the type information of the virtual machines during deployment, for example, divided into three sub-domains a, b, and c, and the VNF puts SHA tags on all virtual machines during deployment , can be obtained according to the upgrade_az parameter. For example, SHA can be divided into three group tags of SHA1, SHA2, and SHA3, and divided into three groups. The type information of the virtual machine corresponds to the number of sub-domains, and the virtual The host device corresponding to the machine is added to SHA1, the host device corresponding to the virtual machine in domain b is added to SHA2, and the host device corresponding to the virtual machine in domain c is added to SHA3. In one embodiment, if the host device in SHA1 The number of virtual machines on the device is not enough. According to the number of virtual machines, SHA can be divided into four labels: SHA1, SHA2, SHA3, and SHA4, and a part of the host devices corresponding to the virtual machines in domain a is added to SHA1, and the other part The host device is added to SHA2, the host device corresponding to the virtual machine in domain b is added to SHA3, and the host device corresponding to the virtual machine in domain c is added to SHA4, so as to complete the instantiation of the virtual machine.

It should be noted that, in one embodiment, for virtual machines that do not need to be divided into domains, it means that the number of virtual machines within the reset permission range will not affect any domain business. This number is obtained from the backup_instance_number parameter, and some types of VNF virtual machines themselves It has multiple mechanisms such as active/standby or load sharing. For example, the types of VNF virtual machines include management, interface, and processing. domain, there can be 20 VNF virtual machines of the processing type, but generally these 20 virtual machines are not distinguished, that is, the 20 processing type virtual machines do not need to be specially divided into domains, so they are deployed according to the backup_instance_number parameter , you can get the proportion and number of virtual machines. For example, divide this type of virtual machines that do not need to be divided into two groups, each group has 10, and can be marked with a and b labels respectively, and each 10 virtual machines can be added to SHA1 In the upgrade process of SHA1 and SHA2, host devices in SHA1 and SHA2 are upgraded in batches sequentially, so as to realize group processing of multiple host devices.

In the case that the requirements of the embodiment of the present application are met, the type and quantity of the virtual machine can also be obtained through other parameters, which are not specifically limited in the embodiment of the present application.

In one embodiment, after the infrastructure entity upgrades the host device, the infrastructure entity enters the maintenance state. In this state, operations such as creating and deleting virtual machines are no longer performed to reduce interference caused by other operations. .

In an embodiment, after the above step S130, the above method may also include but not limited to the following steps: sending upgrade success information to the management and arrangement entity, the upgrade success information indicates that the host devices in the first group have successfully upgraded, so that the management and arrangement entity The entity sends a service fetch request to the network function entity according to the upgrade success information, so that the network function entity fetches the service to the virtual machine corresponding to the host device in the first group after the upgrade is successful according to the service fetch request.

In one embodiment, after the host devices in the first group are successfully upgraded, the services originally deployed on the virtual machines of the host devices in the first group need to be migrated back to upgrade other host devices. After the host device in a group is successfully upgraded, it sends an upgrade success message to the management and orchestration entity. The management and orchestration entity sends a service relocation request to the network function entity according to the upgrade success information. For the virtual machines corresponding to the host devices in the first group, after the business is moved back, the restarted virtual machines will take on the business again, so that the next batch of host devices can be upgraded, ensuring that infrastructure entities can perform network upgrades during network upgrades. Restart but do not interrupt network services. It can be understood that after the service migration of the host device in the first group is completed, the network function entity sends the service migration success information to the management and orchestration entity, and the infrastructure entity can also receive the service migration completion information sent by the management and orchestration entity, In order to upgrade other host devices, it should be noted that the information on the completion of service relocation and the successful information on service relocation can be information in the same field, or information in different fields, and this embodiment of the application does not specify it. limit.

In an embodiment, after the upgrade operation of all host devices in the infrastructure entity is completed, the infrastructure entity exits the maintenance state, and the infrastructure entity resumes normal operation.

Based on the NFV system architecture shown in FIG. 1 , referring to FIG. 5 , an embodiment of the present application also provides a network upgrade method applied to a network function entity. The network upgrade method includes but is not limited to the following steps S310 to S330.

Step S310, receiving a service migration request sent by the management and orchestration entity. The service migration request is generated by the management and orchestration entity according to the first host device information sent by the infrastructure entity. The first host device information is represented as a host device in the first group.

In one embodiment, the information of the first host device is represented as host devices in the first group, and the infrastructure entity divides multiple host devices into multiple groups, and when upgrading the hosts in the first batch, the The host device in the first group performs upgrade processing, and before the upgrade process, first sends the first host device information to the management and arrangement entity, so that the management and arrangement entity sends a service migration request to the network function entity according to the first host device information , the network function entity receives the service migration request sent by the management and orchestration entity, and performs corresponding operations in response to the service migration request.

It should be noted that the first host device information is the list information of the host devices in the first group that needs to be upgraded, and the infrastructure entity sends the list information of this batch of host devices that need to be upgraded to the management and arrangement entity, so as to Perform upgrade processing.

In step S320, the service of the virtual machine corresponding to the first host device information is migrated according to the service migration request.

In an embodiment, in response to the first host device information sent by the basic device entity, the network function entity migrates the business of the virtual machine corresponding to the first host device information to other hosts that do not need to be upgraded temporarily. virtual machine, so as to upgrade the host devices in the first group.

Step S330: Send service migration success information to the management and orchestration entity, so that the management and orchestration entity sends service migration completion information to the infrastructure entity according to the service migration success information, so that the infrastructure entity performs service migration completion information according to the service migration completion information in the first group. The host device performs upgrade processing.

In an embodiment, after the service migration is completed, the network function entity will feed back to the management orchestration entity, send service migration success information to the management orchestration entity, and then the management orchestration entity will send service migration completion information to the basic equipment according to the service migration success information Entity, the basic equipment entity receives the service migration completion information, indicating that the virtual machine services on the host devices in the first group have been migrated. At this time, upgrading these host devices will not affect the business on the hosts. It will not cause service interruption, so the basic device entity upgrades the host devices in the first group to complete the upgrade process of this batch of host devices. It should be noted that the service migration completion information and the service migration success information can be the same The information under the fields may also be the information under different fields, which is not specifically limited in this embodiment of the present application.

It should be noted that the first group may include multiple host devices, including a first host device and a second host device, and the first host device may be a single host device or a device group composed of multiple sub-host devices, The second host device can be a single host device or a device group composed of multiple sub-host devices. The network upgrade method in the embodiment of the present application can be to first upgrade the network of the first host device, and the infrastructure entity first sends a sub-host device containing the first group The first host device information of the first host device in the group is sent to the management and orchestration entity, and the network function entity migrates the virtual machine service on the first host device after receiving the service migration request. After the migration is completed, the infrastructure entity The device is upgraded, and then the device information of the second host device in the first group is sent to the management and arrangement entity, and the second host device is upgraded. It can be understood that the first host device and the second host device are respectively Upgrading is carried out in batches for different host devices for infrastructure entities, which avoids business interruption and improves the reliability of the upgrade. The upgrade process includes shutting down or restarting the host device or the virtual machine on the host device. The embodiment of the application does not specifically limit it.

It should be noted that the first group may include multiple host devices, including a first host device and a second host device, and the first host device may be a single host device or a device group composed of multiple sub-host devices, The second host device may be a single host device or a device group composed of multiple sub-host devices, and the network upgrade method in the embodiment of the present application may be a network upgrade for the first host device, wherein the second host device has completed the upgrade process , so the basic device entity can perform network upgrades for the remaining first host devices in the first group. The batch upgrade of the host device avoids service interruption and improves the reliability of the upgrade.

It can be understood that the network upgrade method in the embodiment of the present application can realize large-scale host device upgrades, divide the host devices into multiple batches, and the host devices in the first group specifically refer to the current batches that need to be upgraded The host devices are upgraded in batches, and during the upgrade process of each batch of host devices, the network function entity migrates the services on the virtual machines of the host devices to the virtual machines of other host devices, avoiding infrastructure During the upgrade process of the host devices in the first group, the network service is interrupted. Therefore, the embodiment of the present application is applicable to large-scale scenarios, and the operation is simple, and the large-scale upgrade takes a short time.

In an embodiment, the above step S320 may further include: migrating the service of the virtual machine corresponding to the first host device information to the virtual machine corresponding to the second host device information according to the service migration request, and the second host device information is characterized as the second Host devices in the group.

In an embodiment, the infrastructure entity is provided with a plurality of host devices, and can be grouped, including being divided into a first group and a second group, wherein, in the process of upgrading the host devices in the first group , the network function module can migrate the business of the virtual machine corresponding to the first host device information to the virtual machine corresponding to the second host device information, and the second host device information is characterized as a host device in the second group, thereby avoiding The service division is chaotic to ensure the reliability of the service. On the premise of meeting the requirements of the embodiment of this application, during the upgrade process of the first host device in the first group, the network function entity can upgrade the virtual host device corresponding to the first host device. The business of the host machine is migrated to the virtual machine corresponding to the second host device in the first group. The embodiment of the present application takes the virtual machine migrated to the host device in the second group as an example, but it does not represent the implementation of the embodiment of the present application. limit.

In an embodiment, before the above step S310, it may also include but not limited to the following steps: sending the virtual machine domain division information to the management orchestration entity, so that the management orchestration entity sends the virtual machine domain division information to the infrastructure entity, so that the infrastructure The facility entity groups the multiple host devices according to the virtual machine domain information, and obtains information about the first host device and information about the second host device.

In one embodiment, the network function entity performs grouping processing during service deployment, the network function entity sends virtual machine domain division information to the management and orchestration entity, and then the infrastructure entity receives the virtual machine domain division information sent by the management and orchestration entity, and according to the virtual machine Machine domain information is grouped, including grouping multiple host devices according to the virtual machine domain information to obtain the first host device information and the second host device information, wherein the first host device information and the second host device information Respectively characterize the host devices in the first group and the host devices in the second group. In the process of upgrading the host devices in the first group, after the network function entity divides the virtual machine into domains, the infrastructure entity Batch upgrades are carried out according to the grouping obtained from the virtual machine domain information. It should be noted that the first group and the second group are only for distinguishing technical characteristics, and the second group can be characterized as the first group in the infrastructure entity. A certain group other than the first group, multiple groups other than the first group, or one of the multiple groups other than the first group, this application does not specifically limit it

Referring to Figure 4, in one embodiment of the above method, first add multiple sub-HAs to the planned HA, that is, to divide the domain, which is also equivalent to grouping, and define the sub-HA as SHA, and the number of SHAs can be determined according to Actual setting is required. The host cluster includes multiple host devices. The SHA can be a single host device or a device group consisting of multiple sub-host devices. During the deployment process of the network function entity (VNF), the virtual machine on which the VNF is deployed is divided into domains. And divide the host devices of the virtual machines with the same domain into the same group, for example, the VNF configured on the virtual machines of the host device in the first group is under the same domain, so in the first group During the upgrade process of the host device, the virtual machines deployed with other domain-specific VNFs will not be upgraded, so that the virtual machines in the same domain can be upgraded in the same batch, thereby avoiding business division confusion and ensuring business reliability. It is understood that the first group may be a certain SHA, and may also include multiple SHAs.

The above step of sending the virtual machine domain division information to the management and arrangement entity may further include the following step: performing domain division processing according to the virtual machine type information and the virtual machine quantity information to obtain the virtual machine domain division information.

In an embodiment, the virtual machine domain division information is obtained by the network function entity after performing domain division processing according to the virtual machine type information and the virtual machine quantity information. The network function entity obtains a certain number of domains according to the type information of the virtual machine, and labels all virtual machines with domain division. The type information of the virtual machine corresponds to the domain division of the network function entity, and combines the number of virtual machines The information obtains the number of virtual machines, and the virtual machines are divided into domains based on the above characteristics, so that the divided virtual machines can be deployed to the same host device.

In an embodiment of the above method, the VNF is divided into multiple sub-domains according to the type information of the virtual machines during deployment, for example, divided into three sub-domains a, b, and c, and the VNF puts SHA tags on all virtual machines during deployment , can be obtained according to the upgrade_az parameter. For example, SHA can be divided into three group tags of SHA1, SHA2, and SHA3, and divided into three groups. The type information of the virtual machine corresponds to the number of sub-domains, and the virtual The host device corresponding to the machine is added to SHA1, the host device corresponding to the virtual machine in domain b is added to SHA2, and the host device corresponding to the virtual machine in domain c is added to SHA3. In one embodiment, if the host device in SHA1 The number of virtual machines on the device is not enough. According to the number of virtual machines, SHA can be divided into four labels: SHA1, SHA2, SHA3, and SHA4, and a part of the host devices corresponding to the virtual machines in domain a is added to SHA1, and the other part The host device is added to SHA2, the host device corresponding to the virtual machine in domain b is added to SHA3, and the host device corresponding to the virtual machine in domain c is added to SHA4, so as to complete the instantiation of the virtual machine.

It should be noted that, in one embodiment, for virtual machines that do not need to be divided into domains, it means that the number of virtual machines within the reset permission range will not affect any domain business. This number is obtained from the backup_instance_number parameter, and some types of VNF virtual machines themselves It has multiple mechanisms such as active/standby or load sharing. For example, the types of VNF virtual machines include management, interface, and processing. domain, there can be 20 VNF virtual machines of the processing type, but generally these 20 virtual machines are not distinguished, that is, the 20 processing type virtual machines do not need to be specially divided into domains, so they are deployed according to the backup_instance_number parameter , you can get the proportion and number of virtual machines. For example, divide this type of virtual machines that do not need to be divided into two groups, each group has 10, and can be marked with a and b labels respectively, and each 10 virtual machines can be added to SHA1 In the upgrade process of SHA1 and SHA2, host devices in SHA1 and SHA2 are upgraded in batches sequentially, so as to realize group processing of multiple host devices.

In the case that the requirements of the embodiment of the present application are met, the type and quantity of the virtual machine can also be obtained through other parameters, which are not specifically limited in the embodiment of the present application.

Referring to FIG. 6 , in an embodiment, after the above step S330, the above method may further include but not limited to the following steps S410 to S420.

Step S410, receiving a service relocation request sent by the management and orchestration entity. The service relocation request is generated by the management and orchestration entity according to the upgrade success information sent by the infrastructure entity.

Step S420: According to the service reversion request, the service is relocated to the virtual machine corresponding to the host device in the first group after the upgrade is successful.

In one embodiment, after the host devices in the first group are successfully upgraded, the services originally deployed on the virtual machines of the host devices in the first group need to be migrated back to upgrade other host devices. After the host devices in a group are successfully upgraded, the network function entity receives the service relocation request sent by the management and orchestration entity. The service relocation request is generated by the management and orchestration entity based on the upgrade success information sent by the infrastructure entity. The business is moved back to the virtual machine corresponding to the host device in the first group after the upgrade is successful. After the business is moved back, the restarted virtual machine will assume the business again so that the next batch of host devices can be upgraded, ensuring the basic The facility entity restarts when the network is upgraded but does not interrupt network services. It can be understood that after the service migration of the host devices in the first group is completed, the network function entity sends the service migration success information to the management and orchestration entity, and can also send the service migration completion information to the infrastructure according to the service migration success information entity, so as to upgrade other host devices. It should be noted that the information on the completion of service relocation and the successful information on service relocation can be information in the same field or information in different fields. This embodiment of the application does not Make specific restrictions.

Based on the NFV system architecture shown in FIG. 1 , referring to FIG. 7 , an embodiment of the present application provides a network upgrade method applied to an infrastructure entity. The network upgrade method includes but is not limited to the following steps S510 to S530.

Step S510, receiving first host device information sent by the infrastructure entity, where the first host device information represents a host device in the first group.

In one embodiment, the information of the first host device is represented as host devices in the first group, and the infrastructure entity divides multiple host devices into multiple groups, and when upgrading the hosts in the first batch, the The host devices in the first group perform upgrade processing, and before the upgrade process, first send the first host device information to the management arrangement entity, and the management arrangement entity receives the service migration request sent by the first host device information, so that the management arrangement The entity performs corresponding operations according to the service migration request.

It should be noted that the first host device information is the list information of the host devices in the first group that needs to be upgraded, and the infrastructure entity sends the list information of this batch of host devices that need to be upgraded to the management and arrangement entity, so as to Perform upgrade processing.

Step S520: Send a service migration request to the network function entity according to the first host device information, so that the network function entity migrates the service of the virtual machine corresponding to the first host device information according to the service migration request.

In an embodiment, in response to the first host device information sent by the basic device entity, the management and orchestration entity sends a service migration request to the network function entity according to the first host device information, so that the network function entity corresponds to the first host device information The business of the virtual machine is migrated to other virtual machines on other hosts that do not need to be upgraded temporarily.

Step S530: Receive service migration success information sent by the network function entity, and send service migration completion information to the infrastructure entity according to the service migration success information, so that the infrastructure entity performs service migration completion information on the host devices in the first group according to the service migration completion information. Escalation process.

In one embodiment, after the network function entity completes the service migration, the network function entity feeds back service migration success information to the management and arrangement entity, and the management and arrangement entity receives the service migration success information sent by the network function entity, and then the management and arrangement entity The success message sends the service migration completion information to the basic equipment entity, so that the infrastructure entity can upgrade the host equipment in the first group according to the service migration completion information, and the basic equipment entity receives the service migration completion information, indicating that the first group The virtual machine services on the internal host devices have been migrated. Upgrading these host devices at this time will not affect the services on the hosts and will not cause service interruption. The host device performs the upgrade process to complete the upgrade process of this batch of host devices. It should be noted that the business migration completion information and the business migration success information can be information in the same field or information in different fields. This application implements The example does not impose specific restrictions on it.

It should be noted that the first group may include multiple host devices, including a first host device and a second host device, and the first host device may be a single host device or a device group composed of multiple sub-host devices, The second host device can be a single host device or a device group consisting of multiple sub-host devices. The network upgrade method in the embodiment of the present application can first target the network upgrade of the first host device, and the management and arrangement entity first receives the infrastructure entity first. Send the first host device information including the first host device in the first group, and send a service migration request to the network function entity to migrate the virtual machine service on the first host device according to the first host device information. After the migration is completed, the infrastructure The entity performs upgrade processing on the first host device, and then the management and arrangement entity receives the device information of the second host device in the first group, and performs upgrade processing on the second host device. It can be understood that the first host device and the The second host device is upgraded, and the infrastructure entity is upgraded in batches for different host devices, which avoids business interruption and improves the reliability of the upgrade. The upgrade process includes shutting down the host device or the virtual machine on the host device or reboot, which is not specifically limited in this embodiment of the application.

It should be noted that the first group may include multiple host devices, including a first host device and a second host device, and the first host device may be a single host device or a device group composed of multiple sub-host devices, The second host device may be a single host device or a device group composed of multiple sub-host devices, and the network upgrade method in the embodiment of the present application may be a network upgrade for the first host device, wherein the second host device has completed the upgrade process , so the basic device entity can perform network upgrades for the remaining first host devices in the first group. The batch upgrade of the host device avoids service interruption and improves the reliability of the upgrade.

It can be understood that the network upgrade method in the embodiment of the present application can realize large-scale host device upgrades, divide the host devices into multiple batches, and the host devices in the first group specifically refer to the current batches that need to be upgraded The host devices are upgraded in batches, and during the upgrade process of each batch of host devices, the business on the virtual machine of the host device is migrated to the virtual machines of other host devices, avoiding the During the upgrade process of the internal host device, network services are interrupted. Therefore, the embodiment of the present application is applicable to large-scale scenarios, and the operation is simple, and the large-scale upgrade takes a short time.

In an embodiment, the above step S520 may further include: sending a service migration request to the network function entity according to the first host device information, so that the network function entity migrates the service of the virtual machine corresponding to the first host device information according to the service migration request To the virtual machine corresponding to the second host device information, the second host device information represents a host device in the second group.

In an embodiment, the infrastructure entity is provided with a plurality of host devices, and can be grouped, including being divided into a first group and a second group, wherein, in the process of upgrading the host devices in the first group The business of the virtual machine corresponding to the first host device information can be migrated to the virtual machine corresponding to the second host device information, and the second host device information is characterized as a host device in the second group, thereby avoiding confusion in business division, To ensure the reliability of the business, on the premise of meeting the requirements of the embodiment of this application, during the process of upgrading the first host device in the first group, the business of the virtual machine corresponding to the first host device can be migrated to the first On the virtual machine corresponding to the second host device in the group, the embodiment of the present application takes the virtual machine migrated to the host device in the second group as an example, but this is not meant to limit the embodiment of the present application.

In an embodiment, before the above step S510, it may also include but not limited to the following steps: receiving the virtual machine domain information sent by the network function entity, and sending the virtual machine domain information to the infrastructure entity, so that the infrastructure entity The virtual machine domain division information performs group processing on multiple host devices to obtain first host device information and second host device information.

In one embodiment, the network function entity performs grouping processing during service deployment, the management and orchestration entity receives the virtual machine domain information sent by the network function entity, and sends the virtual machine domain information to the infrastructure entity, and then the infrastructure entity receives the management The virtual machine domain information sent by the orchestration entity is grouped according to the virtual machine domain information, including grouping multiple host devices according to the virtual machine domain information to obtain the first host device information and the second host device information, Wherein, the first host device information and the second host device information represent the host devices in the first group and the host devices in the second group respectively, and during the process of upgrading the host devices in the first group, the network After the functional entities divide the virtual machines into domains, the infrastructure entities perform batch upgrades based on the groups obtained from the domain division information of the virtual machines. It should be noted that the first group and the second group are only for distinguishing technical A group may be characterized as a group other than the first group, a group other than the first group, or a group of groups other than the first group within the infrastructure entity, This application does not specifically limit

Referring to Figure 4, in one embodiment of the above method, first add multiple sub-HAs to the planned HA, that is, to divide the domain, which is also equivalent to grouping, and define the sub-HA as SHA, and the number of SHAs can be determined according to Actual setting is required. The host cluster includes multiple host devices. The SHA can be a single host device or a device group consisting of multiple sub-host devices. During the deployment process of the network function entity (VNF), the virtual machine on which the VNF is deployed is divided into domains. And divide the host devices of the virtual machines with the same domain into the same group, for example, the VNF configured on the virtual machines of the host device in the first group is under the same domain, so in the first group During the upgrade process of the host device, the virtual machines deployed with other domain-specific VNFs will not be upgraded, so that the virtual machines in the same domain can be upgraded in the same batch, thereby avoiding business division confusion and ensuring business reliability. It is understood that the first group may be a certain SHA, and may also include multiple SHAs.

In an embodiment, the virtual machine domain division information is obtained by the network function entity after performing domain division processing according to the virtual machine type information and the virtual machine quantity information. The network function entity obtains a certain number of domains according to the type information of the virtual machine, and labels all virtual machines with domain division. The type information of the virtual machine corresponds to the domain division of the network function entity, and combines the number of virtual machines The information obtains the number of virtual machines, and the virtual machines are divided into domains based on the above characteristics, so that the divided virtual machines can be deployed to the same host device.

In an embodiment of the above method, the VNF is divided into multiple sub-domains according to the type information of the virtual machines during deployment, for example, divided into three sub-domains a, b, and c, and the VNF puts SHA tags on all virtual machines during deployment , can be obtained according to the upgrade_az parameter. For example, SHA can be divided into three group tags of SHA1, SHA2, and SHA3, and divided into three groups. The type information of the virtual machine corresponds to the number of sub-domains, and the virtual The host device corresponding to the machine is added to SHA1, the host device corresponding to the virtual machine in domain b is added to SHA2, and the host device corresponding to the virtual machine in domain c is added to SHA3. In one embodiment, if the host device in SHA1 The number of virtual machines on the device is not enough. According to the number of virtual machines, SHA can be divided into four labels: SHA1, SHA2, SHA3, and SHA4, and a part of the host devices corresponding to the virtual machines in domain a is added to SHA1, and the other part The host device is added to SHA2, the host device corresponding to the virtual machine in domain b is added to SHA3, and the host device corresponding to the virtual machine in domain c is added to SHA4, so as to complete the instantiation of the virtual machine.

It should be noted that, in one embodiment, for virtual machines that do not need to be divided into domains, it means that the number of virtual machines within the reset permission range will not affect any domain business. This number is obtained from the backup_instance_number parameter, and some types of VNF virtual machines themselves It has multiple mechanisms such as active/standby or load sharing. For example, the types of VNF virtual machines include management, interface, and processing. domain, there can be 20 VNF virtual machines of the processing type, but generally these 20 virtual machines are not distinguished, that is, the 20 processing type virtual machines do not need to be specially divided into domains, so they are deployed according to the backup_instance_number parameter , you can get the proportion and number of virtual machines. For example, divide this type of virtual machines that do not need to be divided into two groups, each group has 10, and can be marked with a and b labels respectively, and each 10 virtual machines can be added to SHA1 In the upgrade process of SHA1 and SHA2, host devices in SHA1 and SHA2 are upgraded in batches sequentially, so as to realize group processing of multiple host devices.

In the case that the requirements of the embodiment of the present application are met, the type and quantity of the virtual machine can also be obtained through other parameters, which are not specifically limited in the embodiment of the present application.

Referring to FIG. 8 , in an embodiment, after the above step S530, the above method may further include but not limited to the following steps S610 to S620.

Step S610, receiving the upgrade success information sent by the infrastructure entity.

Step S620: Send a service relocation request to the network function entity according to the upgrade success information, so that the network function entity reverts the service to the virtual machine corresponding to the host device in the first group after the upgrade is successful according to the service relocation request.

In one embodiment, after the host devices in the first group are successfully upgraded, the services originally deployed on the virtual machines of the host devices in the first group need to be migrated back to upgrade other host devices. After the upgrade of host devices in a group is successful, the management and orchestration entity receives the upgrade success information sent by the infrastructure entity, and the management and orchestration entity sends a service relocation request to the network function entity according to the upgrade success information, so that the network function entity will transfer the service according to the service relocation request. Move back to the virtual machine corresponding to the host device in the first group after the upgrade is successful. After the business is moved back, the restarted virtual machine will take on the business again, so that the next batch of host devices can be upgraded, ensuring the infrastructure The entity restarts when the network is upgraded but does not interrupt network services. It can be understood that after the service migration of the host devices in the first group is completed, the management and orchestration entity receives the service migration success information sent by the network function entity, and may also send the service migration completion information to the basic Facility entities, so as to upgrade other host devices. It should be noted that the information on the completion of business relocation and the successful information on business relocation can be information in the same field, or information in different fields. This embodiment of the application is not correct. It has specific restrictions.

Embodiment 1. The following is the domain-specific deployment process in a specific embodiment of the present application.

1) Under the planned HA, add the concept of sub-HA (SHA), that is, domain division. Under each HA, the number of SHAs can be limited, otherwise it will cause too many batches and long operation time. In the embodiment of the present application, the number of SHAs can be set to 4, and the number of SHAs can be set according to actual needs. A single VNF in each SHA can deploy at most one domain-specific virtual machine.

In one embodiment, if the VNF is divided into three domains, including domains a, b, and c, then the virtual machines in domain a can be deployed to SHA1 and SHA2, but SHA1 will no longer deploy virtual machines in domains b and c. This ensures that SHA The host device in the same batch can be upgraded and restarted.

2) Each VNF needs to divide all virtual machines into domains. The business has integrity in one domain. Restarting of all virtual machines or some virtual machines in one domain will not affect the business of another domain. However, the business of one domain is allowed to be completely migrated to another domain to ensure that when a virtual machine in this domain restarts No business interruption.

3) When the VNF is deployed, it tags all virtual machines with SHA (that is, the domain division above) according to the upgrade_az parameter. The number of virtual machines within the range does not affect any domain business. The number is controlled by the backup_instance_number parameter. A natural number indicates the number, and a decimal indicates the ratio.

4) When MANO is deployed, it sends the upgrade_az and backup_instance_number parameters to NFVI.

5) When NFVI instantiates the virtual machine, according to the domain information of the virtual machine (including at least one of the upgrade_az parameter and the backup_instance_number parameter), the corresponding host device is automatically added to the corresponding SHA, so that after the instantiation is completed, it will automatically Create SHA batches to realize group processing.

6) After the instantiation is completed, for the migration/rebirth of the virtual machine, first select the host device in the SHA where the current virtual machine is located, and then select a blank host device, and then add the host device to the SHA, so that the existing SHA will not be caused The division is chaotic, and in the end, in order to ensure the reliability of the regeneration, it will be selected on another SHA host device, which is not specifically limited in the embodiment of this application.

It should be noted that the interface between NFVI, MANO, and VNF needs to be enhanced. The parameters upgrade_az and backup_instance_number are added. Compatibility can still be guaranteed for processes that do not carry these two parameters, and support for processes that carry enhanced parameters. This enhanced function is not specifically limited in this embodiment of the application.

Embodiment 2, as shown in FIG. 9 , the following is an upgrade process in a specific embodiment of the present application: when NFVI performs an upgrade operation, it first performs maintenance status, and no longer performs operations such as creating or deleting a virtual machine, reducing other operations For the interference caused, NFVI performs batching according to the parameters passed by VNF through MANO when it is instantiated. When each batch of hosts is upgraded and restarted, the reliability mechanism of the VNF can ensure that the business will not be interrupted.

1) to 10) are included when the first batch of host devices are upgraded.

1) First, the NFVI sends the first batch of host device list information to the MANO, that is, sends the first host device information of the host devices in the first group to the MANO.

2) MANO identifies the VNFs corresponding to the virtual machines on the batch of host devices, notifies the VNFs of the identified virtual machines corresponding information, and sends a service migration request to the VNFs.

3) VNF receives the service migration request sent by MANO, confirms that the corresponding virtual machine will be restarted soon, and performs service migration by unloading methods such as active-standby switchover and load sharing for the corresponding service. 1. Load sharing and offloading to complete service migration are examples, but it does not represent a limitation to this embodiment of the application.

4) After the VNF completes the service migration, it sends a service migration success message to the MANO, indicating that the corresponding virtual machine service has been uninstalled and can be restarted.

5) MANO sends service migration completion information to NFVI according to the service migration success information.

6) NFVI upgrades and restarts the batch of host devices, that is, upgrades the host devices in the first group.

7) NFVI waits for the batch of host devices to be restarted, the upgrade is successful, and after the virtual machine is started normally, it will send an upgrade success message to MANO, indicating that the upgrade of this batch of hosts is complete.

8) MANO identifies the VNF corresponding to the host device in the first group that has been successfully upgraded, and sends a service migration request to the VNF to migrate the service back to the original host device.

9) The VNF performs service relocation, and the restarted virtual machine assumes the service again. After the relocation is completed, a service relocation success message is sent to inform the MANO that the relocation is successful.

10) The MANO sends a migration completion message to notify the NFVI of the completion of the migration based on the successful migration information.

It should be noted that the first batch of host devices was successfully upgraded. Due to the linkage process between NFVI, MANO, and VNF, it is guaranteed that NFVI restarts the host devices during the upgrade but does not interrupt the business. The other batches of host devices restart later. The process and The first batch is consistent, repeat until all host devices are upgraded and restarted.

After all host devices are upgraded and restarted, NFVI exits maintenance mode and resumes normal operation.

FIG. 10 shows an electronic device 100 provided by an embodiment of the present application. The electronic device 100 includes: a processor 101, a memory 102, and a computer program stored on the memory 102 and operable on the processor 101, and the computer program is used to execute the above-mentioned network upgrade method when running.

The processor 101 and the memory 102 may be connected through a bus or in other ways.

The memory 102, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs, such as the network upgrade method described in the embodiment of this application. The processor 101 executes the non-transitory software programs and instructions stored in the memory 102 to implement the above-mentioned network upgrade method.

The memory 102 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application program required by at least one function; the data storage area may store and execute the above-mentioned network upgrade method. In addition, the memory 102 may include a high-speed random access memory 102, and may also include a non-transitory memory 102, such as at least one storage device, a flash memory device or other non-transitory solid-state storage devices. In some implementations, the memory 102 may optionally include memory 102 remotely located relative to the processor 101 , and these remote memory 102 may be connected to the electronic device 100 through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The non-transitory software programs and instructions required to realize the above-mentioned network upgrade method are stored in the memory 102, and when executed by one or more processors 101, the above-mentioned network upgrade method is executed, for example, the method steps in FIG. 2 are executed S110 to step S130, method step S210 to step S220 in Fig. 3, method step S310 to step S330 in Fig. 5, method step S410 to step S420 in Fig. 6, method step S510 to step S530 in Fig. 7, Fig. Step S610 to step S620 of the method in 8.

The device embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

The embodiments of the present application at least include the following beneficial effects: The embodiments of the present application provide a network upgrade method, electronic equipment, and storage media, wherein the network upgrade method can be applied to an infrastructure entity, a network function entity, or a management and orchestration entity. When the host device in the infrastructure entity is upgraded, it first sends the information of the first host device represented as the host device in the first group to the management arrangement entity, and the management arrangement entity obtains the service migration request according to the information of the first host device and sends it to In the network function entity, the network function entity migrates the service of the virtual machine corresponding to the first host device information according to the service migration request, and then the infrastructure entity upgrades the host device that has completed the service migration. The services on the virtual machine of the internal host device have been migrated to other host devices that do not need to be upgraded, so the embodiments of the present application can realize uninterrupted network services during the network upgrade process.

Those skilled in the art can understand that all or some of the steps and systems in the methods disclosed above can be implemented as software, firmware, hardware and an appropriate combination thereof. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit . Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). As known to those of ordinary skill in the art, the term computer storage media includes both volatile and nonvolatile media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. permanent, removable and non-removable media. Computer storage media including, but not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tape, storage device storage or other magnetic storage devices, or Any other medium that can be used to store desired information and that can be accessed by a computer. Furthermore, as is well known to those of ordinary skill in the art, communication media typically embody computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media .

It should also be understood that the various implementation manners provided in the embodiments of the present application may be combined arbitrarily to achieve different technical effects.

The above is a specific description of some implementations of the present application, but the present application is not limited to the above-mentioned embodiments. Those skilled in the art can also make various equivalent deformations or replacements without violating the spirit of the present application. Equivalent modifications or replacements are all within the scope defined by the claims of the present application.

Claims (17)

A network upgrade method, applied to an infrastructure entity, the infrastructure entity is connected to a management orchestration entity, the management orchestration entity is connected to a network function entity, the infrastructure entity includes a plurality of host devices, and each of the host The device includes a plurality of virtual machines, the method includes: sending first host device information to the management and orchestration entity, the first host device information representing the host devices in the first group, so that the management and orchestration entity sends information to all host devices according to the first host device information The network function entity sends a service migration request, so that the network function entity performs migration processing on the service of the virtual machine corresponding to the first host device information according to the service migration request; receiving service migration completion information sent by the management and orchestration entity; Perform upgrade processing on the host devices in the first group according to the service migration completion information. The network upgrade method according to claim 1, wherein the first host device information is sent to the management and arrangement entity, and the first host device information is characterized as the host device in the first group, so that The management and orchestration entity sends a service migration request to the network function entity according to the first host device information, so that the network function entity transfers the virtual machine corresponding to the first host device information according to the service migration request Business migration processing, including: sending first host device information to the management and orchestration entity, the first host device information representing the host devices in the first group, so that the management and orchestration entity sends information to all host devices according to the first host device information The network function entity sends a service migration request, so that the network function entity migrates the service of the virtual machine corresponding to the first host device information to the virtual machine corresponding to the second host device information according to the service migration request, and the The second host device information characterizes the host devices in the second group. The network upgrade method according to claim 2, wherein, before sending the first host device information to the management and orchestration entity, the method further comprises: receiving virtual machine domain division information sent by the management and orchestration entity, where the virtual machine domain division information is obtained by the management and orchestration entity according to the network function entity; Grouping the plurality of host devices according to the virtual machine domain information to obtain the first host device information and the second host device information. The network upgrading method according to claim 3, wherein the domain division information of the virtual machine is obtained by the network function entity after performing domain division processing according to the type information of the virtual machine and the quantity information of the virtual machine. The network upgrade method according to any one of claims 1 to 4, wherein, after the host device in the first group is upgraded according to the service migration completion information, the method further include: sending upgrade success information to the management and arrangement entity, where the upgrade success information indicates that the host devices in the first group have successfully upgraded, so that the management and arrangement entity sends the upgrade success information to the network function entity according to the upgrade success information A service fetch request, so that the network function entity fetches the service to the virtual machine corresponding to the host device in the first group after the upgrade is successful according to the service fetch request. A network upgrade method, applied to a network function entity, the network function entity is connected to a management arrangement entity, the management arrangement entity is connected to an infrastructure entity, and the infrastructure entity includes a plurality of host devices, each of the host The device includes a plurality of virtual machines, the method includes: receiving a service migration request sent by the management and orchestration entity, the service migration request is generated by the management and orchestration entity according to the first host device information sent by the infrastructure entity, and the first host device information is represented by the first said host devices within a group; Migrate the business of the virtual machine corresponding to the first host device information according to the service migration request; Sending service migration success information to the management orchestration entity, so that the management orchestration entity sends service migration completion information to the infrastructure entity according to the service migration success information, so that the infrastructure entity migrates according to the service The completion information performs upgrade processing on the host devices in the first group. The network upgrading method according to claim 6, wherein the migrating the business of the virtual machine corresponding to the first host device information according to the service migration request includes: According to the service migration request, the service of the virtual machine corresponding to the first host device information is migrated to the virtual machine corresponding to the second host device information, and the second host device information is characterized as the host in the second group equipment. The network upgrade method according to claim 7, wherein, before receiving the service migration request sent by the management and orchestration entity, the method further comprises: sending virtual machine domain information to the management and orchestration entity, so that the management and orchestration entity sends the virtual machine domain information to the infrastructure entity, so that the infrastructure entity Perform group processing on the multiple host devices to obtain the first host device information and the second host device information. The network upgrading method according to claim 8, wherein before sending the virtual machine domain information to the management and arrangement entity, it includes: performing domain division processing according to the type information of the virtual machine and the quantity information of the virtual machine to obtain the domain division information of the virtual machine. The network upgrade method according to any one of claims 6 to 9, wherein, after sending the service migration success information to the management and arrangement entity, the method further includes: receiving a service relocation request sent by the management and orchestration entity, where the service relocation request is generated by the management and orchestration entity according to the upgrade success information sent by the infrastructure entity; According to the service reversion request, the service is relocated to the virtual machine corresponding to the host device in the first group after the upgrade is successful. A network upgrade method, applied to a management orchestration entity, the management orchestration entity is respectively connected to an infrastructure entity and a network function entity, the infrastructure entity includes a plurality of host devices, and each of the host devices includes a plurality of virtual machines , the method includes: receiving first host device information sent by the infrastructure entity, where the first host device information represents the host device in the first group; Sending a service migration request to the network function entity according to the first host device information, so that the network function entity performs migration processing on the service of the virtual machine corresponding to the first host device information according to the service migration request; receiving the service migration success information sent by the network function entity, and sending service migration completion information to the infrastructure entity according to the service migration success information, so that the infrastructure entity completes the service migration completion information according to the service migration completion information The host devices in the first group perform upgrade processing. The network upgrading method according to claim 11, wherein the sending a service migration request to the network function entity according to the first host device information, so that the network function entity transfers the service migration request to the network function entity according to the service migration request The business of the virtual machine corresponding to the first host device information is migrated, including: Send a service migration request to the network function entity according to the first host device information, so that the network function entity migrates the service of the virtual machine corresponding to the first host device information to the second network function entity according to the service migration request. The virtual machine corresponding to the host device information, the second host device information represents the host device in the second group. The network upgrading method according to claim 12, wherein, before receiving the first host device information sent by the infrastructure entity, the method further comprises: receiving the virtual machine domain division information sent by the network function entity, and sending the virtual machine domain division information to the infrastructure entity, so that the infrastructure entity performs the virtual machine domain division information according to the virtual machine domain division information The host device performs packet processing to obtain the first host device information and the second host device information. The network upgrading method according to claim 13, wherein the domain division information of the virtual machine is obtained by the network function entity after performing domain division processing according to the type information of the virtual machine and the quantity information of the virtual machine. The network upgrading method according to any one of claims 11 to 14, wherein, receiving the service migration success information sent by the network function entity, and sending the service to the infrastructure entity according to the service migration success information After the migration completes the information, the method further includes: receiving the upgrade success information sent by the infrastructure entity; Send a service fetch request to the network function entity according to the upgrade success information, so that the network function entity fetches the service to the service in the first group after the upgrade is successful according to the service fetch request. The virtual machine corresponding to the host device. An electronic device, including a memory and a processor, the memory stores a computer program, and the processor implements the network upgrade method according to any one of claims 1 to 5 when executing the computer program, or The network upgrading method according to any one of claims 6-10, or the network upgrading method according to any one of claims 11-15. A computer-readable storage medium, wherein the storage medium stores a program, and the program is executed by a processor to implement the network upgrade method according to any one of claims 1 to 5, or according to claims 6 to 10 The network upgrading method described in any one of claims 11 to 15, or the network upgrading method described in any one of claims 11-15.

Images