WO2018041086A1

WO2018041086A1 - Method and apparatus for switching nfvo, and vnfm, vim and nfvo

Info

Publication number: WO2018041086A1
Application number: PCT/CN2017/099415
Authority: WO
Inventors: 陈丽萍
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-08-30
Filing date: 2017-08-29
Publication date: 2018-03-08
Also published as: CN107786361A

Abstract

A method for switching a network function virtualisation orchestrator (NFVO), comprising: a virtualised network function manager (VNFM) or a virtualised infrastructure manager (VIM) receiving an instruction message giving an instruction for modifying a main NFVO, wherein the main NFVO is an NFVO performing operation maintenance and management on the VNFM or VIM; the VNFM or VIM sending, to an original NVFO, a request message to make a request for confirming whether to modify the main NFVO, or sending, to a target NFVO, a request message to make a request for being added as a managed node, or respectively sending, to the original NFVO or the target NFVO, a confirmation message confirming the modification of the main NFVO, so as to switch the main NFVO.

Description

Method, device, VNFM, VIM and NFVO for switching NFVO

Technical field

The present application relates to, but is not limited to, the field of communications, and in particular, to a method, an apparatus, a VNFM, a VIM, and an NFVO for switching a Network Function Virtualization Orchestrator (NFVO).

Background technique

In the existing network architecture, network functions and network devices are super-coupling relationships, and network functions are implemented through specially designed, vendor-specific devices. This brings a lot of inconvenience: for example, the performance improvement of these devices is limited by the development of hardware that meets specific or customized requirements while maintaining carrier-grade reliability; for example, when operators want to deploy targeted services. When the target-designed device with the dedicated function is deployed, the operator's service deployment cost will be increased. On the other hand, with the rapid improvement of the performance of the CPU (Central Processing Unit) and memory, the basic function of running the network function in software on the general-purpose server, Network Function Virtualization (NFV) Technology has also emerged. Its goal is to run network functions on common hardware devices, thereby reducing CAPEX (Capital Expenditure) through a wide range of deployments. "Virtualization" enables network functions to be deployed and replaced as needed, and greatly facilitates remote management and maintenance, reducing OPEX (Operating Expense).

In a virtualized environment, existing network functions will be implemented on the Virtual Network Function (VNF), which can be regarded as the application layer of the VNF. Each VNF can implement different network functions according to the specific application configuration. The virtualization of network functions has led to significant changes in the management architecture of existing networks. The architecture diagram and reference points of NFV Management and Orchestration (NFV-MANO) are shown in Figure 1. Among them, Network Functions Virtualization Orchestrator (NFVO) is responsible for network service lifecycle management, Virtualized Infrastructure Manager (VIM) network function virtualization infrastructure (Network Functions Virtualization Infrastructure) , NFVI) resource scheduling and other functions, virtualized network function manager (VNF Manager, VNFM) is responsible for the life cycle management of VNF instances, each VNF instance assumes an associated VNFM, VIM is responsible for controlling and managing NFVI computing, storage, and network resources.

The above-mentioned MANO architecture introduces the target entities NFVO, VIM and VNFM. These entities can be used as management nodes for virtualizing network functions. From the operator's point of view, it can also be regarded as adding virtualization to the target in the entire network. Related network function nodes. In the traditional management system, the network function nodes are managed by Element Managed (EM). As shown in Figure 1, after the network function is virtualized, EM is mainly used for VNF application layer management, while EM and VNFM are currently used. The reference point Ve-Vnfm-em supports VNF lifecycle management, VNF performance management, VNF alarm management, and VNF configuration management. It does not have the functions of VNFM, VIM or NFVO's own operation and maintenance management, and the other. On the other hand, the Os-Ma-Nfvo reference point between the OSS (Operation Support System) and the NFVO supports the interface functions of the network service (NS, Network Service) lifecycle management, NS performance management, and NS alarm management. There are no functions related to the operation and maintenance management of VNFM, VIM or NFVO itself. In fact, the performance of the functional nodes of these targets directly affects the management of other virtual network functions in the network, so how to manage the functional entities of these targets becomes a problem that must be solved.

When NFVO is used as the management node for operation and maintenance management of VNFM or VIM, when the NFVO for operation and maintenance management of VNFM or VIM needs to be switched (for example, when the load of NFVO for initial operation and maintenance management of VNFM or VIM is too high) How to switch the NFVO for operation and maintenance management of VNFM or VIM is a key issue to be solved by selecting NFVO as a VNFM or VIM operation and maintenance management node.

Summary of invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The embodiment of the present application provides a method for switching NFVO, which implements handover of NFVO as a VNFM or VIM operation and maintenance management node.

In a first aspect, an embodiment of the present application provides a method for switching a network function virtualization orchestrator (NFVO), where the method includes:

Virtualized Network Function Manager (VNFM) or Virtualized Infrastructure Manager (VIM) And receiving an indication message for modifying the primary NFVO; wherein the primary NFVO is an NFVO for performing operation and maintenance management on the VNFM or the VIM; the VNFM or the VIM sending a request message to the original NFVO to confirm whether to modify the primary NFVO, or sending the request message to the target NFVO The request is added to the request message of the managed node, or an acknowledgement message confirming the modification of the primary NFVO is sent to the original NFVO and the target NFVO, respectively, to switch the primary NFVO.

In a second aspect, the embodiment of the present application further provides a method for switching NFVO, where the method includes:

After the original NFVO confirms that the primary NFVO of the VNFM or VIM needs to be modified, the original NFVO deletes the VNFM or VIM from the managed node; wherein the primary NFVO is an NFVO that performs operation and maintenance management on the VNFM or VIM.

In a third aspect, the embodiment of the present application further provides a method for switching NFVO, where the method includes:

After the target NFVO confirms that the primary NFVO of the VNFM or VIM needs to be modified, the target NFVO adds the VNFM or VIM to the new managed node; wherein the primary NFVO is the NFVO for operational maintenance management of the VNFM or VIM.

In a fourth aspect, the embodiment of the present application further provides an apparatus for switching NFVO, where the apparatus includes: a first receiving unit and a first sending unit; wherein the first receiving unit is configured to receive an indication indicating that the primary NFVO is modified. a message; wherein the primary NFVO is an NFVO that performs operational maintenance management on the VNFM or the VIM;

The first sending unit is configured to send a request message to the original NFVO to confirm whether to modify the primary NFVO, or send a request message to the target NFVO to be added to the managed node, or send an acknowledgement to the original NFVO and the target NFVO to modify the primary NFVO. Confirm the message to switch the primary NFVO.

In a fifth aspect, the embodiment of the present application further provides an apparatus for switching NFVO, where the apparatus includes: a first confirming unit and a deleting unit; wherein the deleting unit is configured to: when the first confirming unit confirms that the VNFM or the VIM needs to be modified After the primary NFVO, the VNFM or VIM is deleted from the managed node; wherein the primary NFVO is an NFVO that performs operational maintenance management on the VNFM or VIM.

In a sixth aspect, the embodiment of the present application further provides an apparatus for switching NFVO, where the apparatus includes: a second confirming unit and an adding unit; wherein the adding unit is configured to be when the second confirming unit is After modifying the primary NFVO of the VNFM or VIM, the VNFM or VIM is added as a new managed node; wherein the primary NFVO is an NFVO that performs operational maintenance management on the VNFM or VIM.

In a seventh aspect, the embodiment of the present application further provides a VNFM or a VIM, where the VNFM or VIM includes: a first processor and a first memory, wherein the first memory has computer executable instructions; the first The processor is configured to perform the following operations in accordance with the computer executable instructions:

Receiving an indication message indicating that the primary NFVO is modified; wherein the primary NFVO is an NFVO that performs operation and maintenance management on the VNFM or VIM;

A request message confirming whether to modify the primary NFVO is sent to the original NFVO, or a request message added to the managed node is sent to the target NFVO, or an acknowledgement message confirming the modification of the primary NFVO is sent to the original NFVO and the target NFVO, respectively, to switch the primary NFVO.

In an eighth aspect, the embodiment of the present application further provides an NFVO, where the NFVO includes: a second processor and a second memory; wherein the second memory has computer executable instructions; and the second processor is configured to Performing the following operations according to the computer executable instructions:

After the original NFVO confirms that the primary NFVO of the VNFM or VIM needs to be modified, the VNFM or VIM is deleted from the managed node; wherein the primary NFVO is an NFVO that performs operation and maintenance management on the VNFM or VIM.

In a ninth aspect, the embodiment of the present application further provides an NFVO, where the NFVO includes: a third processor and a third memory; wherein the third memory has computer executable instructions; and the third processor is configured to Performing the following operations according to the computer executable instructions:

After the target NFVO confirms that the primary NFVO of the VNFM or VIM needs to be modified, the VNFM or VIM is added as a new managed node; wherein the primary NFVO is an NFVO that performs operational maintenance management on the VNFM or VIM.

In addition, the embodiment of the present application further provides a computer readable medium storing computer executable instructions, which are implemented by the processor to implement any of the foregoing first, second, and third aspects. The steps provided by the method of switching NFVO.

A method for switching NFVO according to an embodiment of the present application, comprising: VNFM or VIM receiving an indication message indicating modification of a primary NFVO; wherein the primary NFVO is for the VNFM or VIM NFVO for performing operation and maintenance management; sending a request message to the original NFVO to confirm whether to modify the primary NFVO, or sending a request message to the target NFVO to be added to the managed node, or sending an acknowledgement message confirming the modification of the primary NFVO to the original NFVO and the target NFVO, respectively. To switch the main NFVO. In this way, by setting the NFVO for operation and maintenance management of the VNFM or VIM, and the VNFM or VIM for operation and maintenance management performed by the NFVO, the modification instruction of the modification of the main NFVO is transmitted, and the switching of the NFVO for the operation and maintenance management is realized.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

FIG. 1 is a schematic diagram of a management architecture after network function virtualization;

2 is a schematic flowchart of a method for switching NFVO according to an embodiment of the present application;

FIG. 3 is a schematic diagram of an architecture for managing VNFM or VIM through NFVO according to an embodiment of the present application;

FIG. 4 is a schematic flowchart of another method for switching NFVO according to an embodiment of the present disclosure;

FIG. 5 is a schematic diagram of another architecture for managing VNFM or VIM through NFVO according to an embodiment of the present disclosure;

FIG. 6 is a schematic flowchart of another method for switching NFVO according to an embodiment of the present disclosure;

FIG. 7 is a schematic flowchart diagram of a method for switching NFVO according to an embodiment of the present disclosure;

FIG. 8 is a schematic flowchart diagram of a method for switching NFVO according to an embodiment of the present application;

FIG. 9 is a schematic flowchart diagram of a method for switching NFVO according to an embodiment of the present disclosure;

FIG. 10 is a schematic flowchart diagram of a method for switching NFVO according to an embodiment of the present application;

FIG. 11 is a schematic flowchart diagram of a method for switching NFVO according to an embodiment of the present application;

FIG. 12 is a schematic flowchart diagram of a method for switching NFVO according to an embodiment of the present disclosure;

FIG. 13 is a schematic structural diagram of an apparatus for switching NFVO according to an embodiment of the present disclosure;

FIG. 14 is a schematic structural diagram of another apparatus for switching NFVO according to an embodiment of the present disclosure;

FIG. 15 is a schematic structural diagram of another apparatus for switching NFVO according to an embodiment of the present disclosure;

16 is a schematic structural diagram of a VNFM or a VIM according to an embodiment of the present application;

FIG. 17 is a schematic structural diagram of an NFVO according to an embodiment of the present disclosure;

FIG. 18 is a schematic structural diagram of an NFVO according to an embodiment of the present application.

Detailed

The implementation of the technical solution will be further described in detail below with reference to the accompanying drawings.

2 is a schematic flowchart of a method for switching NFVO according to an embodiment of the present application. The embodiment of the present application provides a method for switching NFVO, which is applied to a VNFM or a VIM. As shown in FIG. 2, the method includes:

S201, VNFM or VIM receives an indication message indicating that the primary NFVO is modified; wherein the primary NFVO is an NFVO that performs operation and maintenance management on the VNFM or VIM;

When the NM or OSS determines the performance of the NFVO and the resource configuration of the VNFM or VIM, it is not suitable for the operation and maintenance management of the VNFM or VIM. Switching the primary NFVO of the VNFM or VIM, the primary NFVO currently operating and maintaining the VNFM or VIM is used as the original NFVO, and the primary NFVO for operation and maintenance management of the VNFM or VIM after the handover is used as the target NFVO, to the original NFVO and the target NFVO. At least one of the indication messages sent to modify the primary NFVO is sent to indicate that at least one of the original NFVO and the target NFVO currently needs to update the primary NFVO of the VNFM or VIM.

Here, the function of operation and maintenance management of the VNFM or VIM to which the NFVO is connected is added to the NFVO, and the function can be realized by adding a function block managed by the corresponding function module MANO entity in the NFVO. As shown in FIG. 3, when VNFM or VIM is connected to a plurality of NFVOs, only one NFVO performs operation and maintenance management on the VNFM or VIM. By default, the NFVO is the first NFVO to establish a connection with the VNFM or VIM. Wherein, all VNFMs or VIMs connected to the NFVO may be managed nodes of the NFVO.

When the NM or OSS sends an indication to at least one of the original NFVO and the target NFVO to modify the primary At the time of the indication message of the NFVO, at least one of the original NFVO and the target NFVO receives the indication message of the modification of the primary NFVO sent by the NM or the OSS, and sends the received indication message indicating that the modification of the primary NFVO is sent to the VNFM or the VIM. The VNFM or VIM receives an indication message sent by the original NFVO or the target NFVO to modify the primary NFVO to indicate that the VNFM or VIM needs to switch the primary NFVO for which operational maintenance management is performed.

It should be noted that when the original NFVO and the target NFVO receive the NM or the OSS to send an indication message indicating that the primary NFVO is modified, the original NFVO may send an indication message indicating that the primary NFVO is modified to the VNFM or the VIM, or may be the original NFVO and the target NFVO. At the same time, an indication message indicating that the primary NFVO is modified is sent to the VNFM or the VIM to instruct the VNFM or the VIM to modify the primary NFVO currently performing operation and maintenance management.

S202, VNFM or VIM sends a request message to the original NFVO to confirm whether to modify the primary NFVO, or sends a request message added to the managed node to the target NFVO, or sends an acknowledgement message confirming the modification of the primary NFVO to the original NFVO and the target NFVO, respectively, to switch Primary NFVO.

Wherein, when the indication message indicating that the primary NFVO is modified is from the target NFVO, the VNFM or VIM sends a request message to the original NFVO to confirm whether to modify the primary NFVO; when the indication message indicating that the primary NFVO is modified is from At the original NFVO, the VNFM or VIM sends a request message to the target NFVO requesting to be added to the managed node; when the indication message indicating the modification of the primary NFVO includes an indication from the original NFVO and the target NFVO When the indication message of the primary NFVO is modified, the VNFM or VIM sends an acknowledgement message confirming the modification of the primary NFVO to the original NFVO and the target NFVO, respectively.

It should be noted that, when the indication message indicating that the primary NFVO is modified is from the original NFVO, the NM or the OSS may separately send an indication message indicating that the primary NFVO is modified to the original NFVO, and may simultaneously send an indication to the original NFVO and the target NFVO. Modify the indication message of the primary NFVO.

Here, when the VNFM or VIM receives the indication message sent by the target NFVO to modify the primary NFVO, the VNFM or VIM may send a request message to the original NFVO requesting confirmation of whether to modify the primary NFVO to confirm to the original NFVO whether to modify the primary of the VNFM or VIM. NFVO. After the original NFVO receives the request message, and confirms to the NM or OSS to modify the primary NFVO of the VNFM or VIM or the primary NFVO that has confirmed to modify the VNFM or VIM, the primary NFVO is switched from the original NFVO to the target NFVO, the original NFVO. Delete the VNFM or VIM, and add the VNFM or VIM to the managed node in the target NFVO to implement the switching of the primary NFVO of the VNFM or VIM.

When the VNFM or VIM receives the indication message sent by the original NFVO to modify the primary NFVO, the VNFM or VIM sends a request message to the target NFVO requesting to be added to the managed node to confirm to the target NFVO whether to increase the VNFM or VIM to be managed. The node modifies the primary NFVO of the VNFM or VIM, and performs operation and maintenance management on the VNFM or VIM through the target NFVO. After receiving the request message, the target NFVO confirms to the NM or OSS to add the VNFM or VIM to the managed node or has confirmed to increase the VNFM or VIM as the managed node, and switches the primary NFVO of the VNFM or VIM from the original NFVO to In the case of the target NFVO, the target NFVO adds the VNFM or VIM to the managed node, and the original NFVO deletes the VNFM or VIM in the managed node to implement the switching of the primary NFVO of the VNFM or VIM.

When the VNFM or VIM receives the indication message sent by the original NFVO and the target NFVO to modify the primary NFVO, the VNFM or VIM confirms that both the original NFVO and the target NFVO have been known to need to modify the primary NFVO. At this time, the modification is determined in the VNFM or VIM. In the case of the primary NFVO, it is no longer necessary to request the target NFVO or the original NFVO to confirm whether to modify the primary NFVO of the VNFM or the VIM, but to directly send an acknowledgement message confirming the modification of the primary NFVO to the original NFVO and the target NFVO to notify the original NFVO and the target NFVO. Confirm that the current primary NFVO is modified; at this time, the VNFM or VIM is deleted from the managed node in the original NFVO, and the VNFM or VIM is added to the managed node in the target NFVO to implement the switching of the primary NFVO of the VNFM or VIM.

FIG. 4 is a schematic flowchart diagram of another method for switching NFVO according to an embodiment of the present application. The embodiment of the present application provides a method for switching NFVO, which is applied to the original NFVO in the handover process. As shown in FIG. 4, the method includes:

S401, the original NFVO confirms that the primary NFVO of the VNFM or the VIM needs to be modified; wherein the primary NFVO is an NFVO that performs operation and maintenance management on the VNFM or the VIM;

Here, the original NFVO is the main NFVO currently performing operation and maintenance management on the VNFM or VIM, and the main NFVO that performs operation and maintenance management of the VNFM or VIM is switched to the target NFVO during the execution of the handover. In this embodiment, the function of performing operation and maintenance management on the VNFM or VIM to which the NFVO is connected is added to the NFVO, wherein the function can be implemented by adding a function block managed by the corresponding function module MANO entity in the NFVO. As shown in Figure 5, when VNFM or The VIM is connected to multiple NFVOs, of which only one NFVO performs operational maintenance management on the VNFM or VIM. By default, the primary NFVO of a VNFM or VIM is the first NFVO to establish a connection with the VNFM or VIM. Wherein, all VNFMs or VIMs connected to the NFVO may be managed nodes of the NFVO.

Among them, the original NFVO confirmed the need to modify the main NFVO of VNFM or VIM, including the following ways:

(1) Receiving an indication message sent by the NM or OSS to modify the primary NFVO, and receiving an acknowledgement message that the VNFM or VIM sends an acknowledgement that the primary NFVO has been modified.

(2) After receiving the request sent by the VNFM or VIM to confirm whether to modify the request message of the primary NFVO, send a request message to the NM or OSS to confirm whether to modify the primary NFVO, and receive an acknowledgement sent by the NM or OSS to modify the primary NFVO. Confirmation message.

(3) receiving a request from the VNFM or VIM to confirm whether to modify the request message of the primary NFVO, and receiving an acknowledgement message sent by the target NFVO to modify the primary NFVO; wherein, by receiving an interface with the target NFVO A confirmation message confirming the modification of the primary NFVO.

(4) receiving the request of the target NFVO to modify the request message of the primary NFVO, and receiving an acknowledgement message sent by the VNFM or VIM to modify the primary NFVO; wherein the target NFVO is received through an interface with the target NFVO The request to modify the request message of the primary NFVO.

Among them, the (1) and (2) modes can be implemented in a network having no interface between the original NFVO and the target NVFO. For the (3) and (4) modes, it can be implemented in a network having an interface between the original NFVO and the target NVFO as shown in FIG. 5, which means that there is a physical connection between the original NFVO and the target NFVO. In addition to the transmission equipment (relay, router or switch, etc.), the two can directly exchange related information, and do not need to transparently transmit through other network function nodes to assist in the information exchange between the two.

For the first (1) mode, when the NM or OSS determines the performance of the NFVO that is managed by the VNFM or VIM, the resource configuration, etc., it is not suitable for the VNFM to confirm the current primary NFVO for the operation and maintenance management of the VNFM or VIM. Or the VIM performs operation and maintenance management, and needs to switch the primary NFVO of the VNFM or the VIM, and sends an indication message indicating that the primary NFVO is modified to the original NFVO; at this time, the original NFVO receives an indication message indicating that the primary NFVO is modified, and sends an instruction modification to the VNFM or the VIM. The indication message of the primary NFVO. In VNFM or VIM with target NFVO, After the NM or OSS interacts with the information to confirm that the target NFVO increases the VNFM or VIM as the managed node with the target NFVO as the new primary NFVO after the VNFM or VIM handover, the confirmation that the original NFVO received the VNFM or VIM transmission has been modified. After confirming the primary NFVO, confirm that the primary NFVO of the VNFM or VIM needs to be modified.

In this manner, the VNFM or VIM interacts with the target NFVO, NM, or OSS to confirm that the target NFVO increases the VNFM or VIM as a managed node, including: an indication that the primary NFVO is modified when the VNFM or VIM does not receive the target NFVO indication. When the message is sent, the VNFM or VIM sends a request message to the target NFVO to be added to the managed node, and confirms that the VNFM or VIM is added to the target NFVO when the acknowledgment message returned by the target NFVO is added to the acknowledgment message of the managed node. Node; when the VNFM or VIM receives the indication of the target NFVO to modify the indication message of the primary NFVO, it is confirmed that the target NFVO has confirmed that the VNFM or VIM is added to the managed node at the target NFVO.

For the (2) mode, when the NM or OSS determines the performance of the NFVO that is managed by the VNFM or VIM, the resource configuration, etc., it is not suitable for the VNFM to confirm the current primary NFVO for the operation and maintenance management of the VNFM or VIM. Or the VIM performs operation and maintenance management, needs to switch the primary NFVO of the VNFM or VIM, and sends an indication message indicating that the primary NFVO is modified to the target NFVO; the target NFVO sends an indication message indicating that the modification of the primary NFVO is sent to the VNFM or VIM; the VNFM or the VIM receives The indication of the target NFVO modifies the indication message of the primary NFVO, and sends a request message to the original NFVO to confirm whether to modify the primary NFVO. At this time, the original NFVO receives the request sent by the VNFM or the VIM to confirm whether to modify the request message of the primary NFVO, and the original NFVO to the NM. Or the OSS sends a request to confirm whether to modify the request message of the primary NFVO; after receiving the request of the original NFVO to confirm whether to modify the request message of the primary NFVO, the NM or the OSS confirms to modify the primary NFVO of the VNFM or VIM, and returns a confirmation to the original NFVO to modify the primary NFVO. Acknowledgment message; when the original NFVO receives an acknowledgment message confirming the modification of the primary NFVO, it is confirmed that the primary NFVO of the VNFM or VIM needs to be modified.

For the (3) mode, the original NFVO and the target NFVO directly exchange information through the interface. When the NM or OSS determines the performance of the NFVO and the resource configuration of the VNFM or VIM, it is not suitable for the operation and maintenance management of the VNFM or VIM. Switch the VNFM or The primary NFVO of the VIM sends an indication message indicating the modification of the primary NFVO to the original NFVO; the original NFVO sends an indication message indicating that the modification of the primary NFVO is sent to the target NFVO, and the target NFVO confirms to the NM or OSS to increase the VNFM or VIM as the managed node and to the VNFM Or the VIM sends an indication message indicating that the primary NFVO is modified. When it is confirmed that the VNFM or the VIM needs to be added to the managed node, the target NFVO adds the VNFM or the VIM to the managed node, and sends a confirmation message confirming the modification of the primary NFVO to the original NFVO; After receiving the confirmation message sent by the target NFVO to modify the primary NFVO, the NFVO confirms that the primary NFVO of the VNFM or VIM needs to be modified.

For the (4) mode, the original NFVO and the target NFVO directly exchange information through the interface. When the NM or OSS determines the performance of the NFVO and the resource configuration of the VNFM or VIM, it is not suitable for the operation and maintenance management of the VNFM or VIM. Switching the primary NFVO of the VNFM or VIM, and sending an indication message indicating that the primary NFVO is modified to the target NFVO; after receiving the indication message indicating that the primary NFVO is modified, the target NFVO sends a request message for modifying the primary NFVO to the original NFVO, at this time, the original NFVO Receiving the request sent by the target NFVO to modify the request message of the primary NFVO, the original NFVO confirms to modify the primary NFVO of the VNFM or VIM to the NM or the OSS, and sends an indication message indicating that the primary NFVO is modified to the VNFM or the VIM; when the VNFM or the VIM confirms the modification At NFVO, the VNFM or VIM sends an acknowledgment message confirming the modification of the primary NFVO to the original NFVO. The original NFVO confirms that the primary NFVO of the VNFM or VIM needs to be modified after receiving the confirmation sent by the VNFM or VIM to modify the primary NFVO acknowledgement message.

S402. After the original NFVO confirms that the primary NFVO of the VNFM or the VIM needs to be modified, the VNFM or the VIM is deleted from the managed node.

Here, when the original NFVO confirms that the primary NFVO of the VNFM or VIM needs to be modified, the VNFM or VIM is deleted from the managed node, wherein the managed node of the original NFVO is the VNFM or VIM with the original NFVO as the primary NFVO. Here, when the original NFVO deletes the VNFM or VIM from the managed node, the target NFVO has completed the switching of the primary NFVO of the VNFM or VIM by increasing the VNFM or VIM as the managed node by interaction with each node. When the original NFVO deletes the VNFM or VIM from the managed node, the target NFVO has not increased the VNFM or VIM as the managed node, and the VNFM or VIM is added to the managed node by interaction with other nodes. Complete the switching of the primary NFVO of the VNFM or VIM.

FIG. 6 is a schematic flowchart diagram of another method for switching NFVO according to an embodiment of the present disclosure. The embodiment of the present application provides a method for switching NFVO, which is applied to a target NFVO in a handover process. As shown in FIG. 6, the method includes:

S601, the target NFVO confirms that the primary NFVO of the VNFM or the VIM needs to be modified; wherein the primary NFVO is an NFVO that performs operation and maintenance management on the VNFM or the VIM;

Here, the target NFVO is the primary NFVO that needs to operate and maintain the VNFM or VIM after the handover process, and the primary NFVO (ie, the original NFVO) currently operating and maintaining the VNFM or VIM is switched to the target during the handover process. NFVO. In this embodiment, the function of performing operation and maintenance management on the VNFM or VIM to which the NFVO is connected is added to the NFVO, wherein the function can be implemented by adding a function block managed by the corresponding function module MANO entity in the NFVO. As shown in FIG. 3 or FIG. 5, when the VNFM or VIM is connected to a plurality of NFVOs, only one of the NFVOs performs operation and maintenance management on the VNFM or the VIM. By default, the primary NFVO of a VNFM or VIM is the first NFVO to establish a connection with the VNFM or VIM. Wherein, all VNFMs or VIMs connected to the NFVO may be managed nodes of the NFVO.

Among them, the target NFVO confirms that the way to modify the primary NFVO of VNFM or VIM includes the following ways:

(1) Receiving an indication message sent by the NM or OSS to modify the primary NFVO, and receiving the request of the VNFM or VIM to be added to the request message of the managed node or confirming that the confirmation message needs to be added to the managed node.

(2) After receiving the request for the VNFM or VIM to be added to the request message of the managed node, send a request to the NM or OSS to confirm whether to increase the request message to the managed node, and the confirmation of receiving the NM or OSS is added to be managed. The confirmation message for the node.

(3) receiving the request of the original NFVO to modify the request message of the primary NFVO of the VNFM or the VIM, and receiving the acknowledgement sent by the VNFM or the VIM to be added to the acknowledgement message of the managed node; wherein, by using the original NFVO The inter-interface receives the request message of the original NFVO requesting modification of the primary NFVO of the VNFM or VIM.

(4) receiving an indication message sent by the NM or OSS to modify the primary NFVO of the VNFM or VIM, and receiving the confirmation of the original NFVO to modify the primary NFVO of the VNFM or VIM. A confirmation message; wherein the confirmation message of the primary NFVO of the VNFM or VIM is modified by receiving an acknowledgement of the original NFVO with an interface with the original NFVO.

Wherein, the (1) and (2) modes can be implemented in a network having no interface between the original NFVO and the target NVFO, and for the (3) and (4) modes, 5 is implemented in a network with an interface between the original NFVO and the target NVFO.

For the first (1) mode, when the NM or OSS determines the performance of the NFVO that is managed by the VNFM or VIM, the resource configuration, etc., it is not suitable for the VNFM to confirm the current primary NFVO for the operation and maintenance management of the VNFM or VIM. Or the VIM performs operation and maintenance management, and needs to switch the primary NFVO of the VNFM or the VIM, and send an indication message indicating that the primary NFVO is modified to the target NFVO; after receiving the indication sent by the NM or the OSS to modify the primary NFVO, the target NFVO sends the indication message to the VNFM or After the VIM sends an indication message indicating that the primary NFVO is modified, the acknowledgment sent by the VNFM or the VIM needs to be added to the acknowledgment message of the managed node, or the request sent by the original NFVO is added to the request message of the managed node, and the target NFVO is confirmed. The primary NFVO of the VNFM or VIM needs to be modified.

Here, the VNFM or VIM sends a corresponding message to the target NFVO according to whether or not the indication message is received from the target NFVO. When the indication message indicating the modification of the primary NFVO is not received from the target NFVO and the modification of the primary NFVO is confirmed, the request message added to the managed node is sent to the target NFVO; when the indication message indicating the modification of the primary NFVO is received from the target NFVO When it is confirmed that the primary NFVO is modified, a confirmation message indicating that it needs to be added to the managed node is sent to the target NFVO.

The target NFVO, when receiving the indication message indicating that the primary NFVO is modified, has the following three conditions: First, the original NFVO does not receive an indication message indicating that the primary NFVO is modified, and at this time, the target NFVO sends the indication to the VNFM or VIM. Instructing to modify the indication message of the primary NFVO, when the VNFM or VIM confirms the modification of the primary NFVO with the original NFVO, and returns an acknowledgement message to the target NFVO to confirm that the managed node needs to be added; second, when the original NFVO receives the indication message indicating that the primary NFVO is modified simultaneously The original NFVO sends an indication message indicating that the primary NFVO is modified to the VNFM or the VIM. At this time, after receiving the indication of the original NFVO by the VNFM or the VIM, the VNFM or the VIM sends a request message to the target NFVO to be added to the managed node. Third, when the original NFVO receives the indication message indicating the modification of the primary NFVO, the original NFVO and the target NFVO are simultaneously The VNFM or VIM sends an indication message indicating that the primary NFVO is modified. At this time, after receiving the indication of the original NFVO and the target NFVO, the VNFM or the VIM returns an acknowledgement message to the target NFVO to confirm that the managed node needs to be added.

In case (2), when the NM or OSS determines the current NFVO for the operation and maintenance management of the VNFM or VIM based on the performance and resource configuration of the NFVO managed by the VNFM or VIM, it is not suitable for the VNFM. Or the VIM performs operation and maintenance management, and needs to switch the primary NFVO of the VNFM or the VIM, and send an indication message indicating that the primary NFVO is modified to the original NFVO; the original NFVO receives the indication sent by the NM or the OSS to modify the primary NFVO, and then sends the indication message to the VNFM or VIM. Sending an indication message indicating that the primary NFVO is modified; after receiving the indication message indicating that the primary NFVO is modified, the VNFM or the VIM sends a request message to the target NFVO to be added as the managed node; the target NFVO increases the request sent by the VNFM or the VIM. After being the request message of the managed node, send a request to the NM or OSS to confirm whether to increase the request message of the managed node; if the NM or OSS determines that the primary NFVO of the VNFM or VIM needs to be switched, the return confirmation to the target NFVO is added to The acknowledgment message of the managed node; after the NFVO receives the acknowledgment message of the NM or OSS and is added to the acknowledgment message of the managed node, it is confirmed that the primary N of the VNFM or VIM needs to be modified. FVO.

For the case (3), the target NFVO and the original NFVO directly exchange information through the interface. When the NM or OSS determines the performance of the NFVO and the resource configuration of the VNFM or VIM, it is not suitable for the operation and maintenance management of the VNFM or VIM. Switching the primary NFVO of the VNFM or VIM, and sending an indication message indicating that the primary NFVO is modified to the original NFVO; after receiving the indication message sent by the NM or the OSS to modify the primary NFVO, the original NFVO sends a request to the target NFVO to modify the primary NFVO of the VNFM or VIM. Request message; the target NFVO sends an indication to the VNFM or VIM after receiving the request of the original NFVO to modify the request message of the primary NFVO of the VNFM or VIM, and confirming that the VNFM or VIM needs to modify the primary NFVO with the NM or OSS. Modifying the indication message of the primary NFVO; after receiving the indication message sent by the target NFVO to modify the primary NFVO, the VNFM or the VIM confirms that the primary NFVO needs to be modified at this time, and returns a confirmation to the target NFVO that the confirmation needs to be added to the managed node. Message; when the target NFVO receives the VNFM or VIM sent confirmation needs to be added to the confirmed node's acknowledgement When it is time, confirm that you need to modify the primary NFVO of VNFM or VIM.

For the case in (4), the target NFVO and the original NFVO directly exchange information through the interface. When the NM or OSS determines the performance of the NFVO and the resource configuration of the VNFM or VIM, it is not suitable for the operation and maintenance management of the VNFM or VIM. Switching the primary NFVO of the VNFM or VIM, and sending an indication message indicating that the primary NFVO is modified to the target NFVO; after receiving the indication message sent by the NM or OSS to modify the primary NFVO, the target NFVO sends a request to the original NFVO to modify the primary NFVO of the VNFM or VIM. Request message; the original NFVO confirms the request message of the primary NFVO of the VNFM or VIM after receiving the request of the target NFVO, and confirms with the NM or OSS, VNFM or VIM that the primary NFVO needs to be modified, and the VNFM or VIM is deleted from the managed node. In the case where the original NFVO returns an acknowledgement message confirming the modification of the primary NFVO of the VNFM or VIM to the target NFVO, when the target NFVO receives the confirmation message sent by the original NFVO to modify the primary NFVO of the VNFM or VIM, it is confirmed that Modify the primary NFVO of VNFM or VIM.

S602. After the target NFVO confirms that the primary NFVO of the VNFM or the VIM needs to be modified, the target NFVO adds the VNFM or VIM to the new managed node.

Here, when the target NFVO confirms that the primary NFVO of the VNFM or the VIM needs to be modified, the VNFM or VIM is added to the managed node, wherein the managed node of the target NFVO is the VNFM or VIM whose target NFVO is the primary NFVO. Here, when the target NFVO adds the VNFM or VIM to the managed node, the original NFVO has completed the VNFM or VIM from the managed node by interaction with each node, completing the primary NFVO of the VNFM or VIM. Switching; when the target NFVO adds the VNFM or VIM to the managed node, the original NFVO has not deleted the VNFM or VIM from the managed node, and the VNFM or VIM is managed from the interaction with other nodes. The node is deleted and the switch of the primary NFVO of the VNFM or VIM is completed.

It should be noted that, in the above embodiment, one NFVO can manage multiple VNFMs or VIMs at the same time. In information interaction, information exchanged between different network nodes carries information that needs to switch VNFM or VIM of the primary NFVO to distinguish Different VNFM or VIM.

FIG. 7 is a schematic flowchart diagram of a method for switching NFVO according to an embodiment of the present application. This embodiment provides a method for switching NFVO. As shown in FIG. 7, the method includes:

Step 701: The NM or the OSS sends a message to the original NFVO to modify the primary NFVO of the VNFM or the VIM, where the message carries the information of the target NFVO.

Step 702: The original NFVO sends a message to the VNMF or the VIM to instruct the VNFM or the VIM to modify the primary NFVO, and carries the information of the target NFVO.

Step 703: The VNFM or the VIM obtains the information of the target NFVO according to the received message, and sends a message to the target NFVO to request to increase the managed node, and instructs the target NFVO to add the VNFM or VIM to the managed node.

Step 704: The target NFVO sends a message to the NM or the OSS to confirm whether to add the VNFM or the VIM to the managed node.

Step 705: The NM or the OSS returns an acknowledgement message confirming the addition to the managed node to the target NFVO.

Step 706: After receiving the acknowledgement message sent by the NM or the OSS, the target NFVO adds the VNFM or the VIM to the managed node, and sends an acknowledgement message to the VNFM or the VIM.

Step 707: After receiving the acknowledgement message sent by the target NFVO, the VNFM or the VIM sends an acknowledgement message to the original NFVO.

Step 708: After receiving the acknowledgment message sent by the VNFM or the VIM, the original NFVO deletes the VNFM or the VIM in the managed node, and sends a message to the NM or the OSS to confirm that the primary NFVO modification of the VNFM or the VIM has been completed.

FIG. 8 is a schematic flowchart diagram of a method for switching NFVO according to an embodiment of the present application. This embodiment provides a method for switching NFVO. As shown in FIG. 8, the method includes:

Step 801: The NM or the OSS sends a message to the target NFVO to modify the primary NFVO of the VNFM or the VIM, where the message carries the information of the original NFVO of the VNFM or the VIM;

Step 802: The target NFVO sends a message to the VNMF or the VIM to indicate that the VNFM or the VIM modifies the primary NFVO.

Step 803: The VNFM or the VIM sends a message to the original NFVO to confirm whether to modify the primary NFVO.

Step 804: After the original NFVO receives the request confirmation message of the VNFM or the VIM, the NM is sent to the NM. Or the OSS sends a message to confirm whether to modify the primary NFVO of the VNFM or VIM;

Step 805: The NM or the OSS sends an acknowledgement message confirming the modification of the primary NFVO of the VNFM or the VIM to the original NFVO.

Step 806, the original NFVO receives the NM or OSS confirmation message, deletes the VNFM or VIM in the managed node, and sends an acknowledgement message to the VNFM or VIM;

Step 807: The VNFM or the VIM sends a message to the target NFVO to request to increase the managed node, and instructs the target NFVO to add the VNFM or VIM to the managed node.

Step 808: After receiving the message sent by the VNFM or the VIM, the target NFVO adds the VNFM or the VIM to the managed node, and sends an acknowledgement message to the NM or the OSS.

FIG. 9 is a schematic flowchart diagram of a method for switching NFVO according to an embodiment of the present application. This embodiment provides a method for switching NFVO. As shown in FIG. 9, the method includes:

Step 901: The NM or the OSS sends a message to the original NFVO to modify the primary NFVO of the VNFM or the VIM, where the message carries the information of the target NFVO of the VNFM or the VIM;

Step 902: The NM or the OSS sends a message to the target NFVO to modify the primary NFVO of the VNFM or the VIM, where the message carries the information of the original NFVO of the VNFM or the VIM;

Step 903, the original NFVO sends a message to the VNFM or VIM to modify the primary NFVO;

Step 904: After receiving the message of the original NFVO, the VNFM or the VIM sends a message to the target NFVO to request to add the VNFM or the VIM to the managed node.

Step 905: The target NFVO adds the VNFM or the VIM to the managed node, and sends an acknowledgement message to the VNFM or the VIM.

Step 906: The target NFVO sends an acknowledgement message to the NM or the OSS.

Step 907: After receiving the confirmation message of the VNFM or the VIM, the original NFVO deletes the VNFM or the VIM from the managed node.

Step 908, the original NFVO sends an acknowledgement message to the NM or OSS.

FIG. 10 is a schematic flowchart diagram of a method for switching NFVO according to an embodiment of the present application. This embodiment provides a method for switching NFVO. As shown in FIG. 10, the method includes:

Step 1001, NM or OSS sends a message to the original NFVO to modify the VNFM or VIM. The primary NFVO, the message carrying the information of the target NFVO of the VNFM or VIM;

Step 1002: The NM or the OSS sends a message to the target NFVO to modify the primary NFVO of the VNFM or the VIM, where the message carries the information of the original NFVO of the VNFM or the VIM;

Step 1003, the original NFVO sends a message to the VNFM or VIM to modify the primary NFVO;

Step 1004: The target NFVO sends a message to the VNFM or the VIM to modify the primary NFVO.

Step 1005 and step 1006, VNFM or VIM send an acknowledgement message to the original NFVO and the target NFVO, respectively;

Step 1007: The target NFVO adds the VNFM or the VIM to the managed node, and sends an acknowledgement message to the NM or the OSS.

Step 1008: The original NFVO deletes the VNFM or VIM from the managed node and sends an acknowledgement message to the NM or OSS.

FIG. 11 is a schematic flowchart diagram of a method for switching NFVO according to an embodiment of the present application. This embodiment provides a method for switching NFVO. As shown in FIG. 11, the method includes:

Step 1101: The NM or the OSS sends a message to the original NFVO to modify the primary NFVO of the VNFM or the VIM, where the message carries the information of the target NFVO.

Step 1102: The original NFVO sends a message to the target NFVO to modify the primary NFVO of the VNFM or the VIM, and carries the information of the VNFM or the VIM;

Step 1103: The target NFVO sends a message to the NM or the OSS to confirm whether to add the VNFM or the VIM to the managed node.

Step 1104: The NM or the OSS sends an acknowledgement message to the target NFVO to confirm that the VNFM or VIM is added to the managed node.

Step 1105: After receiving the acknowledgement message sent by the NM or the OSS, the target NFVO sends a message to the VNFM or the VIM to modify the primary NFVO.

Step 1106: After receiving the indication message, the VNFM or the VIM sends a message to the original NFVO to confirm whether to modify the primary NFVO.

Step 1107, the original NFVO sends a confirmation message confirming the modification of the primary NFVO to the VNFM or the VIM, and confirms that the primary NFVO is modified;

Step 1108: After receiving the confirmation message of the original NFVO, the VNFM or the VIM sends an acknowledgement message to the target NFVO.

Step 1109: After receiving the confirmation message of the VNFM or the VIM, the target NFVO adds the VNFM or the VIM to the target managed node, and sends an acknowledgement message to the original NFVO.

Step 1110: After receiving the confirmation message of the target NFVO, the original NFVO deletes the VNFM or the VIM in the managed node, and sends a message to the NM or the OSS to confirm that the primary NFVO modification of the VNFM or the VIM has been completed.

The above step 1103 is optional in a completely trusted network environment. In step 1105, after receiving the message in step 1102, the target NFVO sends a message to the VNFM or VIM to modify the primary NFVO.

FIG. 12 is a schematic flowchart diagram of a method for switching NFVO according to an embodiment of the present application. This embodiment provides a method for switching NFVO. As shown in FIG. 12, the method includes:

Step 1201: The NM or the OSS sends a message to the target NFVO to modify the primary NFVO of the VNFM or the VIM, where the message carries the information of the original NFVO of the VNFM or the VIM;

Step 1202: The target NFVO sends a message to the original NFVO requesting to modify the primary NFVO of the VNFM or VIM;

Step 1203: After receiving the request message of the target NFVO, the original NFVO sends a message to the NM or the OSS to confirm whether to modify the primary NFVO of the VNFM or the VIM;

Step 1204: The NM or the OSS sends an acknowledgement message confirming the modification of the primary NFVO to the original NFVO.

Step 1205: After receiving the confirmation message of the NM or the OSS, the original NFVO sends a message to the VNFM or the VIM to modify the primary NFVO.

Step 1206, the VNFM or the VIM returns an acknowledgement message confirming the modification of the primary NFVO to the original NFVO;

Step 1207, after receiving the confirmation message sent by the VNFM or the VIM, the original NFVO deletes the VNFM or the VIM in the managed node, and sends an acknowledgement message to the target NFVO;

Step 1208: After receiving the acknowledgement message sent by the original NFVO, the target NFVO adds the VNFM or the VIM to the managed node, and sends an acknowledgement message to the NM or the OSS.

The above step 1203 is optional in a completely trusted network environment. After receiving the message in step 1202 in step 1205, the original NFVO sends a message to the VNFM or VIM to modify the primary NFVO.

FIG. 13 is a schematic structural diagram of an apparatus for switching NFVO according to an embodiment of the present disclosure. The present embodiment provides a device for switching NFVO, which is applied to a VNFM or a VIM. As shown in FIG. 13, the device includes: a first receiving unit 1301 and a first sending unit 1302;

The first receiving unit 1301 is configured to receive an indication message indicating that the primary NFVO is modified; wherein the primary NFVO is an NFVO that performs operation and maintenance management on the VNFM or the VIM;

The first sending unit 1302 is configured to send a request message to the original NFVO to confirm whether to modify the primary NFVO, or send a request message to the target NFVO to be added as the managed node, or send an acknowledgement to the original NFVO and the target NFVO to confirm the modified primary NFVO. Message to switch the primary NFVO.

The first sending unit 1301 may be configured to send a request message to the original NFVO to confirm whether to modify the primary NFVO when the indication message indicating that the primary NFVO is modified is from the target NFVO.

The first sending unit 1301 may be configured to, when the indication message indicating the modification of the primary NFVO comes from the original NFVO, send a request message requesting to be added to the managed node to the target NFVO.

The first sending unit 1301 may be configured to send an acknowledgement modification master to the original NFVO and the target NFVO respectively when the indication message indicating the modification of the primary NFVO includes an indication message from the original NFVO and the target NFVO indicating that the primary NFVO is modified. NFVO confirmation message.

FIG. 14 is a schematic structural diagram of another apparatus for switching NFVO according to an embodiment of the present disclosure. The embodiment provides a device for switching NFVO, which is applied to the original NFVO in the process of switching. As shown in FIG. 14, the device includes: a first confirming unit 1401 and a deleting unit 1402;

The deleting unit 1402 is configured to: after the first confirming unit 1401 confirms that the primary NFVO of the VNFM or the VIM needs to be modified, delete the VNFM or the VIM from the managed node; wherein the primary NFVO is performed on the VNFM or the VIM Operational maintenance management of NFVO.

In the above solution, the first confirmation unit 1401 may be configured to confirm that the primary NFVO of the VNFM or VIM needs to be modified by:

Receiving an indication message sent by the NM or OSS to modify the primary NFVO, and receiving an acknowledgement that the VNFM or VIM sends an acknowledgement that the primary NFVO has been modified.

The first validation unit 1401 can be configured to confirm that the primary NFVO of the VNFM or VIM needs to be modified by:

After receiving the request sent by the VNFM or the VIM to confirm whether to modify the request message of the primary NFVO, send a request message to the NM or the OSS to confirm whether to modify the primary NFVO, and receive an acknowledgement message sent by the NM or OSS to modify the primary NFVO. .

Receiving a request from the VNFM or VIM to confirm whether to modify the request message of the primary NFVO, and receiving an acknowledgement message sent by the target NFVO to modify the primary NFVO; wherein the acknowledgement is modified by an interface with the target NFVO A confirmation message from the primary NFVO.

Receiving a request of the target NFVO to modify the request message of the primary NFVO, and receiving an acknowledgement message sent by the VNFM or VIM to modify the primary NFVO; wherein the request modification of the target NFVO is received through an interface with the target NFVO The primary NFVO request message.

In an actual application, the apparatus may further include a second receiving unit configured to receive the message, and a second transmitting unit configured to transmit the message.

FIG. 15 is a schematic structural diagram of another apparatus for switching NFVO according to an embodiment of the present application. The present embodiment provides a device for switching NFVO, which is applied to a target NFVO in a handover process. As shown in FIG. 15, the device includes: a second confirmation unit 1501 and an adding unit 1502;

The adding unit 1502 is configured to add the VNFM or VIM to a new managed node after the second confirming unit 1501 confirms that the primary NFVO of the VNFM or the VIM needs to be modified; wherein the primary NFVO is for the VNFM or VIM NFVO for operational maintenance management.

In the above solution, the second confirmation unit 1501 may be configured to confirm that the primary NFVO of the VNFM or VIM needs to be modified by:

Receiving an indication sent by the NM or OSS to modify the primary NFVO, and receiving the indication The request for the VNFM or VIM is added to the request message of the managed node or the confirmation message that needs to be added to the managed node.

The second validation unit 1501 can be configured to confirm that the primary NFVO of the VNFM or VIM needs to be modified by:

After the request for receiving the VNFM or the VIM is added to the request message of the managed node, a request message for confirming whether to increase to the managed node is sent to the NM or the OSS, and the confirmation of receiving the NM or the OSS is added to the confirmation of the managed node. Message.

Receiving the request of the original NFVO to modify the request message of the primary NFVO of the VNFM or VIM, and receiving the acknowledgement sent by the VNFM or VIM needs to be added to the acknowledgement message of the managed node; wherein, through the interface with the original NFVO A request message for modifying the primary NFVO of the VNFM or VIM is received by the request to the original NFVO.

Receiving an indication message sent by the NM or the OSS to modify the primary NFVO of the VNFM or the VIM, and receiving an acknowledgement of the original NFVO confirming the modification of the primary NFVO of the VNFM or VIM; wherein, by using the primary NFVO The interface receives an acknowledgment message confirming the primary NFVO of the VNFM or VIM.

In a practical application, the apparatus may further include a third receiving unit configured to receive the message, and a third transmitting unit configured to transmit the message.

It should be noted that the first confirmation unit, the deletion unit, the second confirmation unit, and the addition unit provided by the foregoing embodiments may be implemented in the same NFVO. For the same NFVO, it can be used as both the original NFVO and the target NFVO during the handover process.

FIG. 16 is a schematic structural diagram of a VNFM or a VIM according to an embodiment of the present application. The embodiment provides a VNFM or VIM for switching NFVO. As shown in FIG. 16, the VNFM or VIM includes: a first processor 1601 and a first memory 1602, wherein the first memory 1602 has computer executable instructions therein; The first processor 1601 is configured to execute in accordance with the computer executable instructions Next operation:

Receiving an indication message indicating that the primary NFVO is modified; wherein the primary NFVO is an NFVO for performing operation and maintenance management on the VNFM or the VIM; sending a request message to the original NFVO to confirm whether to modify the primary NFVO, or sending a request to the target NFVO to be increased to The request message of the managed node, or an acknowledgement message confirming the modification of the primary NFVO is sent to the original NFVO and the target NFVO, respectively, to switch the primary NFVO.

Here, when the indication message indicating the modification of the primary NFVO is from the target NFVO, the first processor 1601 is configured to perform an operation of transmitting a request to the original NFVO to confirm whether to modify the primary NFVO according to the computer executable instructions. Request message. When the indication message indicating the modification of the primary NFVO is from the original NFVO, the first processor 1601 is configured to perform the following operation according to the computer executable instructions: sending a request to the target NFVO to be added as a managed node Message. When the indication message indicating the modification of the primary NFVO includes an indication message from the original NFVO and the target NFVO indicating that the primary NFVO is modified, the first processor 1601 is configured to perform the following according to the computer executable instructions Operation: A confirmation message confirming the modification of the primary NFVO is sent to the original NFVO and the target NFVO, respectively.

FIG. 17 is a schematic structural diagram of an NFVO according to an embodiment of the present application. The embodiment provides an NFVO. As shown in FIG. 17, the NFVO includes: a second processor 1701 and a second memory 1702; wherein the second memory 1702 has computer executable instructions; the second processor 1701 is configured to Performing the following operations according to the computer executable instructions:

The manner in which the second processor 1701 confirms that the primary NFVO of the VNFM or the VIM needs to be modified according to the computer executable instructions includes the following methods:

Manner 1, receiving an indication sent by the NM or the OSS to modify the primary NFVO, and receiving an acknowledgement that the VNFM or the VIM sends an acknowledgement that the primary NFVO has been modified;

Manner 2: After receiving the request sent by the VNFM or the VIM to confirm whether to modify the request message of the primary NFVO, send a request message to the NM or the OSS to confirm whether to modify the primary NFVO, and receive an acknowledgement sent by the NM or the OSS to modify the primary NFVO. Confirmation message;

Manner 3: receiving a request from the VNFM or VIM to confirm whether to modify the request message of the primary NFVO, and receiving an acknowledgement message sent by the target NFVO to modify the primary NFVO; wherein, by receiving an interface with the target NFVO Confirmation of confirming the modification of the primary NFVO;

Manner 4: receiving a request of the target NFVO to modify the request message of the primary NFVO, and receiving an acknowledgement message sent by the VNFM or VIM to modify the primary NFVO; wherein the target NFVO is received through an interface with the target NFVO The request to modify the request message of the primary NFVO.

FIG. 18 is a schematic structural diagram of an NFVO according to an embodiment of the present application. The embodiment further provides an NFVO. As shown in FIG. 18, the NFVO includes: a third processor 1801 and a third memory 1802; wherein the third memory 1802 has computer executable instructions; and the third processor 1801 is configured. To perform the following operations in accordance with the computer executable instructions:

The manner in which the third processor 1801 confirms that the primary NFVO of the VNFM or the VIM needs to be modified according to the computer executable instructions includes the following:

Manner 1: receiving an indication sent by the NM or OSS to modify the indication message of the primary NFVO, and receiving the request of the VNFM or the VIM to be added to the request message of the managed node or confirming that the confirmation message needs to be added to the managed node;

Manner 2: After receiving the request for the VNFM or the VIM, adding a request message to the managed node, sending a request to the NM or the OSS to confirm whether to increase the request message of the managed node, and receiving the confirmation of the NM or the OSS is added to be managed. Confirmation message of the node;

Manner 3: receiving the request of the original NFVO to modify the request message of the primary NFVO of the VNFM or the VIM, and receiving the acknowledgement sent by the VNFM or the VIM needs to be added to the acknowledgement message of the managed node; wherein, by using the original NFVO The inter-interface receives the request message of the original NFVO requesting modification of the primary NFVO of the VNFM or VIM;

Manner 4: receiving an indication message sent by the NM or the OSS to modify the primary NFVO of the VNFM or the VIM, and receiving the confirmation of the original NFVO to modify the primary NFVO of the VNFM or VIM A confirmation message; wherein the confirmation message of the primary NFVO of the VNFM or VIM is modified by receiving an acknowledgement of the original NFVO with an interface with the original NFVO.

It should be noted that the NFVO in the embodiment shown in FIG. 17 and FIG. 18 may be the same NFVO. When the same NFVO is used, the second processor 1701 and the third processor 1801 may be the same processor. For different processors, the second memory 1702 and the third memory 1802 may be the same memory or different memories.

In addition, the embodiment of the present application further provides a computer readable medium storing computer executable instructions, the steps of the method for switching NFVO in any of the above aspects when the computer executable instructions are executed by a processor.

The present application is described with reference to at least one of the flowcharts and block diagrams of the method, apparatus (system), and computer program product according to embodiments of the present application. It shall be understood that at least one of each of the processes and blocks of at least one of the flowcharts and the block diagrams, and the flow of the at least one of the flowcharts and the block diagrams, or the combination of the blocks, or the flow and the blocks, can be implemented by the computer program instructions. . These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. A device that implements at least one of the following: a function specified in a flow or a flow of a flowchart, a block or a plurality of blocks in a block diagram.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements at least one of the following: a function specified in a flow or a flow of a flowchart, a block or a plurality of blocks in a block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing at least one of the following: a function specified in a flow or a flow of a flowchart, a block or a plurality of blocks in a block diagram.

Those of ordinary skill in the art will appreciate that all or some of the steps, systems, and functional blocks or units of the methods disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules or units mentioned in the above description It does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed cooperatively by several physical components. Some or all of the components may be implemented as software executed by a processor, such as a 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 a computer readable medium, which may include computer storage media (or non-transitory media) and communication media (or transitory media). As is well known to those of ordinary skill in the art, the term computer storage medium includes volatile and nonvolatile, implemented in any method or technology for storing information, such as computer readable instructions, data structures, program modules or other data. Sex, removable and non-removable media. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridge, magnetic tape, magnetic disk storage or other magnetic storage device, or may Any other medium used to store the desired information and that can be accessed by the computer. Moreover, it is well known to those skilled in the art that communication media typically includes 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 can include any information delivery media. .

The above is only an exemplary embodiment of the present application, and is not intended to limit the scope of the present application.

Claims

A method for switching a network function virtualization orchestrator NFVO, comprising:

The virtualized network function manager VNFM or the virtualized infrastructure manager VIM receives an indication message indicating that the primary NFVO is modified; wherein the primary NFVO is an NFVO that performs operational maintenance management on the VNFM or VIM;

The VNFM or VIM sends a request message to the original NFVO to confirm whether to modify the primary NFVO, or sends a request message to the target NFVO to be added to the managed node, or sends an acknowledgement message confirming the modification of the primary NFVO to the original NFVO and the target NFVO, respectively. Switch the primary NFVO.
The method of claim 1, wherein when the indication message indicating the modification of the primary NFVO is from the target NFVO, the VNFM or VIM sends a request message to the original NFVO requesting confirmation of whether to modify the primary NFVO.
The method of claim 1, wherein when the indication message indicating the modification of the primary NFVO is from the original NFVO, the VNFM or VIM sends a request message requesting addition to the managed node to the target NFVO.
The method of claim 1, wherein when the indication message indicating the modification of the primary NFVO includes an indication message from the original NFVO and the target NFVO indicating that the primary NFVO is modified, the VNFM or VIM is respectively The NFVO and the target NFVO send a confirmation message confirming the modification of the primary NFVO.
A method for switching a network function virtualization orchestrator NFVO, comprising:

After the original NFVO confirms that the primary NFVO of the virtualized network function manager VNFM or the virtualized infrastructure manager VIM needs to be modified, the original NFVO deletes the VNFM or VIM from the managed node; wherein the primary NFVO is NFVO for operational maintenance management of the VNFM or VIM.
The method of claim 5, wherein the manner in which the original NFVO confirms that the primary NFVO of the VNFM or VIM needs to be modified comprises:

The original NFVO receives an indication message sent by the network manager NM or the operation support system OSS to modify the primary NFVO, and receives an acknowledgement message that the VNFM or VIM sends an acknowledgement that the primary NFVO has been modified.
The method of claim 5, wherein the manner in which the original NFVO confirms that the primary NFVO of the VNFM or VIM needs to be modified comprises:

After receiving the request sent by the VNFM or VIM to confirm whether to modify the request message of the primary NFVO, the original NFVO sends a request message to the network manager NM or the operation support system OSS to confirm whether to modify the primary NFVO; and receives the NM or The confirmation sent by the OSS modifies the confirmation message of the primary NFVO.
The method of claim 5, wherein the manner in which the original NFVO confirms that the primary NFVO of the VNFM or VIM needs to be modified comprises:

Receiving, by the original NFVO, the request of the VNFM or the VIM to confirm whether to modify the request message of the primary NFVO, and receiving an acknowledgement message sent by the target NFVO to modify the primary NFVO; wherein, receiving through the interface with the target NFVO The confirmation modifies the confirmation message of the primary NFVO.
The method of claim 5, wherein the manner in which the original NFVO confirms that the primary NFVO of the VNFM or VIM needs to be modified comprises:

Receiving, by the original NFVO, a request message for modifying the primary NFVO of the target NFVO, and receiving an acknowledgement message sent by the VNFM or VIM to modify the primary NFVO; wherein the target is received through an interface with the target NFVO The NFVO request modifies the request message of the primary NFVO.
A method for switching a network function virtualization orchestrator NFVO, comprising:

After the target NFVO confirms that the primary NFVO of the virtualized network function manager VNFM or the virtualized infrastructure manager VIM needs to be modified, the target NFVO adds the VNFM or VIM to a new managed node; wherein the primary NFVO NFVO for operational maintenance management of the VNFM or VIM.
The method of claim 10, wherein the manner in which the target NFVO confirms that the primary NFVO of the VNFM or VIM needs to be modified comprises:

The target NFVO receives an indication message sent by the network manager NM or the operation support system OSS to modify the primary NFVO, and the request to receive the VNFM or VIM is added to the requested message of the managed node or the confirmation needs to be added to be managed. The confirmation message for the node.
The method of claim 10, wherein the manner in which the target NFVO confirms that the primary NFVO of the VNFM or VIM needs to be modified comprises:

After receiving the request of the VNFM or the VIM, the target NFVO is added to the request message of the managed node, and sends a request message to the network manager NM or the operation support system OSS to confirm whether it is added to the managed node, and receives the NM. Or the confirmation of the OSS is added to the confirmation message of the managed node.
The method of claim 10, wherein the manner in which the target NFVO confirms that the primary NFVO of the VNFM or VIM needs to be modified comprises:

Receiving, by the target NFVO, a request message for modifying the primary NFVO of the VNFM or the VIM, and receiving an acknowledgement sent by the VNFM or VIM to be added to the acknowledgement message of the managed node; wherein, by using the original NFVO The interface between the two receives the request message of the original NFVO to modify the primary NFVO of the VNFM or VIM.
The method of claim 10, wherein the manner in which the target NFVO confirms that the primary NFVO of the VNFM or VIM needs to be modified comprises:

Receiving, by the network manager NM or the operation support system OSS, an indication message sent by the network manager NM or the operation support system OSS to modify the primary NFVO of the VNFM or the VIM, and receiving an acknowledgement that the original NFVO confirms modifying the primary NFVO of the VNFM or the VIM; And confirming the confirmation message of the primary NFVO of the VNFM or VIM by receiving an acknowledgement of the original NFVO through an interface with the original NFVO.
An apparatus for switching a network function virtualization orchestrator NFVO, comprising: a first receiving unit and a first sending unit; wherein

The first receiving unit is configured to receive an indication message indicating that the primary NFVO is modified; wherein the primary NFVO is an NFVO that performs operation and maintenance management on the virtualized network function manager VNFM or the virtualized infrastructure manager VIM;

The first sending unit is configured to send a request message to the original NFVO to confirm whether to modify the primary NFVO, or send a request message to the target NFVO to be added to the managed node, or send an acknowledgement to the original NFVO and the target NFVO to modify the primary NFVO. Confirm the message to switch the primary NFVO.
The apparatus of claim 15, wherein the first transmitting unit is configured to perform one of the following:

And when the indication message indicating that the primary NFVO is modified is from the target NFVO, sending a request message to the original NFVO to confirm whether to modify the primary NFVO;

Sending a request message added to the managed node to the target NFVO when the indication message indicating that the primary NFVO is modified is from the original NFVO;

When the indication message indicating the modification of the primary NFVO includes an indication message from the original NFVO and the target NFVO indicating that the primary NFVO is modified, an acknowledgement message confirming the modification of the primary NFVO is sent to the original NFVO and the target NFVO, respectively.
An apparatus for switching a network function virtualization orchestrator NFVO, comprising: a first confirming unit and a deleting unit; wherein the deleting unit is configured to: when the first confirming unit confirms that the virtualized network function manager VNFM needs to be modified or After virtualizing the primary NFVO of the infrastructure manager VIM, the VNFM or VIM is deleted from the managed node; wherein the primary NFVO is an NFVO that performs operational maintenance management on the VNFM or VIM.
The apparatus of claim 17, wherein the first validation unit is configured to confirm that the primary NFVO of the VNFM or VIM needs to be modified by one of:

Receiving an indication message sent by the network manager NM or the operation support system OSS to modify the primary NFVO, and receiving an acknowledgement message that the VNFM or the VIM sends an acknowledgement that the primary NFVO has been modified;

After receiving the request sent by the VNFM or the VIM to confirm whether to modify the request message of the primary NFVO, send a request message to the NM or the OSS to confirm whether to modify the primary NFVO, and receive an acknowledgement message sent by the NM or OSS to modify the primary NFVO. ;

Receiving a request from the VNFM or VIM to confirm whether to modify the request message of the primary NFVO, and receiving an acknowledgement message sent by the target NFVO to modify the primary NFVO; wherein the acknowledgement modification is received through an interface with the target NFVO Confirmation message of the primary NFVO;

Receiving a request of the target NFVO to modify the request message of the primary NFVO, and receiving an acknowledgement message sent by the VNFM or VIM to modify the primary NFVO; wherein the request modification of the target NFVO is received through an interface with the target NFVO The primary NFVO request message.
An apparatus for switching a network function virtualization orchestrator NFVO, comprising: a second confirmation unit and an adding unit; wherein the adding unit is configured to confirm that the virtualized network function manager VNFM needs to be modified or After virtualizing the primary NFVO of the infrastructure manager VIM, the VNFM or VIM is added as a new managed node; wherein the primary NFVO is an NFVO that performs operational maintenance management on the VNFM or VIM.
The apparatus of claim 19, wherein the second validation unit is configured to confirm that the primary NFVO of the VNFM or VIM needs to be modified by one of:

Receiving an indication message sent by the network manager NM or the operating system OSS to modify the primary NFVO, and receiving the request of the VNFM or VIM to be added as a request message of the managed node or confirming that the confirmation message needs to be added to the managed node ;

After the request for receiving the VNFM or the VIM is added to the request message of the managed node, a request message for confirming whether to increase to the managed node is sent to the NM or the OSS, and the confirmation that the NM or the OSS is received is added to the managed node. Confirmation message

Receiving the request of the original NFVO to modify the request message of the primary NFVO of the VNFM or VIM, and receiving the acknowledgement sent by the VNFM or VIM needs to be added to the acknowledgement message of the managed node; wherein, through the interface with the original NFVO Receiving a request message of the original NFVO to modify a primary NFVO of the VNFM or the VIM;

Receiving an indication message sent by the NM or the OSS to modify the primary NFVO of the VNFM or the VIM, and receiving an acknowledgement of the original NFVO confirming the modification of the primary NFVO of the VNFM or VIM; wherein, by using the primary NFVO The interface receives an acknowledgment message confirming the primary NFVO of the VNFM or VIM.
A virtualized network function manager VNFM or a virtualized infrastructure manager VIM, the VNFM or VIM comprising: a first processor and a first memory, wherein the first memory has computer executable instructions; The first processor is configured to perform the following operations in accordance with the computer executable instructions:

Receiving an indication message indicating that the primary network function virtualization orchestrator NFVO is modified; wherein the primary NFVO is an NFVO that performs operation and maintenance management on the VNFM or VIM;

Send a request to the original NFVO to confirm whether to modify the request message of the primary NFVO, or to the target The NFVO sends a request to the managed node's request message, or sends an acknowledgment message confirming the modification of the primary NFVO to the original NFVO and the target NFVO, respectively, to switch the primary NFVO.
A network function virtualization orchestrator NFVO, comprising: a second processor and a second memory; wherein the second memory has computer executable instructions; the second processor is configured to execute the computer executable instructions Do the following:

Deleting the VNFM or VIM from the managed node after the original NFVO confirms that the virtualized network function manager VNFM or the primary NFVO of the virtualized infrastructure manager VIM needs to be modified; wherein the primary NFVO is for the VNFM Or VIM for NFVO for operational maintenance management.
A network function virtualization orchestrator NFVO, comprising: a third processor and a third memory; wherein the third memory has computer executable instructions; and the third processor is configured to execute the computer executable instructions Do the following:

After the target NFVO confirms that the primary NFVO of the virtualized network function manager VNFM or the virtualized infrastructure manager VIM needs to be modified, the VNFM or VIM is added as a new managed node; wherein the primary NFVO is NFVO for operational maintenance management of VNFM or VIM.