CN108259200B - A kind of physical network function PNF moving method and relevant device - Google Patents

Abstract

The embodiment of the present invention discloses a physical network function PNF migration method and related equipment. The method is applied to a network function virtualization NFV system, and the NFV system includes a network function virtualization orchestrator NFVO. The method includes: the The NFVO receives the trigger migration message sent by the network management system OSS, which is used to trigger the NFVO to migrate the function of the PNF node to the NFV system, and the NSD has a virtual network resource description that replaces the PNF; the NFV system deletes the After the PNF resource is configured, the NFVO instantiates the virtual network resource of the PNF based on the PNFD identifier, the PNF node instantiation identifier and the virtual network resource description. Therefore, the PNF function can be quickly migrated to the VNF system, and the time for migrating from the PNF to the VNF can be shortened.

Description

A physical network function PNF migration method and related equipment

technical field

The invention relates to the communication field, in particular to a physical network function (PNF) migration method and related equipment.

Background technique

Network Function Virtualization (Network Function Virtualization, NFV) mainly sets industry-wide standards for network function virtualization.

In NFV, NFV-MANO (NFV Management and Orchestration) mainly implements the management and orchestration functions of the entire NFV. In NFV-MANO, different functions of NVF are managed by different functional modules. For example, NFVO is an important module in NFV-MANO, which can be used to decompose each network service description (Network Service Descriptor, NSD). To meet the requirements of the virtualized network function (Virtualized Network Function, VNF), cooperate with the virtualized network function manager (VNF Manager, VNFM) to realize the deployment of the VNF. VNFM is mainly used to decompose the demand for virtual resources such as virtual machines according to the VNFD template and VNF capacity requirements, and cooperate with NFVO and VIM to complete the instantiation of VNF.

At present, NFV-MANO does not manage the traditional physical network function (PNF), which belongs to the external docking relationship with the traditional physical network function (PNF). When the PNF node in Network Service fails or the PNF node needs to be migrated to cloud resources, then Operators need to redesign the VNFD that replaces the PNF, and at the same time need to redesign a new NSD, which takes a long time to deploy and results in long service interruptions.

Contents of the invention

Embodiments of the present invention provide a physical network function PNF migration method and related equipment, in order to quickly migrate PNF functions to a VNF system and improve PNF migration efficiency.

In the first aspect, the embodiment of the present invention provides a PNF migration method, the method is applied to a network function virtualization NFV system, and the NFV system includes a network function virtualization orchestrator NFVO, and the method includes: NFVO receives the network management system OSS The trigger migration message is used to trigger the NFVO to migrate the function of the PNF node to the NFV system. The trigger migration message includes the physical network function descriptor PNFD identifier corresponding to the above PNF node and the instantiation identifier of the PNF node. NSD has a replacement PNF virtual network resource description, NSD is used to identify the network service description of the network service NS where the PNF node is located, the virtual network resource description is a virtual network function descriptor VNFD or a nested virtual network service description nestedNSD; delete NFV in this NFV system After the PNF resource configuration in , the NFVO instantiates the virtual network resource of the PNF based on the PNFD identifier, the PNF node instantiation identifier, and the virtual network resource description. The virtual network resource is the virtual network function VNF corresponding to the VNFD, or the nestedNSD corresponding to Embedded network service nestedNS.

In the solution provided by the embodiment of the present invention, by designing the VNFD or nestedNSD that replaces the PNF in the NSD in advance, when the PNF fails or the operator needs to migrate the PNF function to the cloud, the NFVO can quickly migrate the PNF function to the NSD based on the above VNFD or nestedNSD In the VNF system, shorten the migration time from PNF to VNF.

In a possible design, before the NFVO describes the instantiation of the virtual network resource of the PNF based on the virtual network resource, the method further includes: the NFVO receives an instantiation indication message sent by the OSS, and the instantiation indication message includes a PNFD identifier for indicating Perform NS instantiation on the PNF node corresponding to the PNFD identifier to obtain the PNF node instantiation identifier in the trigger migration message. Through the instantiation indication message, the NS can be instantiated for the PNF node.

In a possible design, after the NFVO instantiates the virtual network resource of the PNF based on the virtual network resource description, the method further includes: the NFVO receives a fetch message sent by the OSS, and the fetch message is used to instruct the NFVO to transfer the function of the PNF node from the NFV Fetching back to PNF, the fetching message includes PNFD identifier and PNF node instantiation identifier; then NFVO deletes the virtual network resource configuration used by the replacement PNF and instantiates the connection of PNF. In this way, the function of the PNF is migrated back from the virtual network resource to the PNF.

In a possible design, before the NFVO receives the trigger migration message sent by the network management system OSS, the method further includes: the NFVO sends a status sending indication message to the OSS, the status sending indication message includes the instantiation identifier of the PNF node, and the status sending indication message includes The instruction message is used to instruct the OSS to send the current state of the PNF to the NFVO when the current state of the PNF changes. In this way, the NFVO can know the status of the PNF in time, and initiate PNF migration or relocation in time, thereby improving the efficiency of PNF migration or relocation.

In a possible design, the trigger migration message also includes a PNF fault, and before the NFVO instantiates the virtual network resource of the PNF based on the PNFD identifier, the PNF node instantiation identifier, and the virtual network resource description, the method further includes: the NFVO sends a message to the OSS A migration notification message, the migration notification message is used to notify the OSS that the NFVO migrates the PNF function to the NFV, and the migration notification message includes the PNFD identifier and the PNF node instantiation identifier. Therefore, the NFVO triggers the PNF migration after receiving the information of the PNF failure. And when the NFVO determines to perform PNF migration, it notifies the OSS, so that the OSS can know the situation of the imminent migration of the PNF in time, and adjust corresponding functions according to the situation.

In a possible design, the relocation message also includes that the PNF failure is successfully repaired. Before the NFVO deletes the virtual network resource configuration used by the PNF and instantiates the PNF, the method further includes: the NFVO sends a relocation notification message to the OSS, and the relocation notification message is used. To notify the OSS, the NFVO transfers the PNF function back from the NFV to the PNF, and the notification message includes the PNFD identifier and the PNF node instantiation identifier. Therefore, after the NFVO receives the information that the PNF failure is successfully repaired, it triggers the PNF relocation. And when the NFVO determines to perform the PNF migration, it notifies the OSS, so that the OSS can know the situation that the PNF is about to be migrated back in time, and adjust the corresponding functions according to the situation.

In a possible design, the instantiation instruction message also includes a network node deployment identifier or whether a PNF failure uses a VNF replacement identifier, and the NFVO instantiates the virtual network resource of the PNF based on the PNFD identifier, the PNF node instantiation identifier, and the virtual network resource description, Specifically: when the network node deployment identifier indicates that the network node in the NS uses PNF deployment, the NFVO instantiates the virtual network resource of the PNF based on the PNFD identifier, the PNF node instantiation identifier, and the virtual network resource description; or, whether to use the VNF when the PNF fails The replacement identifier instructs the NFVO to use the VNF to replace the PNF when the PNF fails, and the NFVO instantiates the virtual network resource of the PNF based on the PNFD identifier, the instantiation identifier of the PNF node, and the virtual network resource description. In this way, the OSS can more flexibly control whether the NFVO migrates the PNF to the virtual network resources.

In a possible design, the instantiation instruction message also includes whether to move back the flag after the PNF fault is repaired, the NFVO deletes the virtual network resource configuration used by the PNF and instantiates the PNF, specifically: whether to move back the flag after the PNF fault is repaired When instructing the PNF to perform a PNF fetch, the NFVO deletes the virtual network resource configuration used by the replacement PNF and instantiates the connection of the PNF. In this way, the OSS can more flexibly control whether the NFVO will migrate the PNF back.

In an example, after the NFVO instantiates the virtual network resource of the PNF based on the PNFD identifier, the PNF node instantiation identifier, and the virtual network resource description, the method further includes: the NFVO sends a migration success notification message to the OSS, and the migration success notification message uses To notify the OSS that the virtual network resources of the PNF are instantiated successfully. In this way, the OSS can know the status of the successful PNF migration in time.

In an example, the migration success notification message further includes at least one of the following: a PNFD, an identifier of a virtual network resource description, and an identifier of a virtual network resource. In this way, the OSS can more directly know the virtualized resource that replaces the PNF function.

In an example, after the NFVO deletes the virtual network resource configuration used by the replacement PNF and instantiates the connection of the PNF, the method further includes: the NFVO sends a fetch success notification message to the OSS. In this way, the OSS can know the status of the successful PNF relocation in time.

In an example, the retrieval success notification message further includes at least one of the following: a PNFD identifier and a PNFD instantiation identifier. In this way, the OSS can obtain the PNF retrieved from the VNF more directly.

In an example, the OSS includes a network slice manager. Therefore, the method can also be applied to a fifth-generation mobile communication technology (5th-Generation, 5G for short) network.

In the second aspect, the embodiment of the present invention also provides a physical network function PNF migration method, the method is applied to a network function virtualization NFV system, and the NFV system includes a network function virtualization orchestrator NFVO, and the method includes: transferring the PNF When the function of the node is migrated to the NFV system, the network management system OSS generates a trigger migration message, which is used to trigger the NFVO to migrate the function of the PNF node to the NFV system. The trigger migration message includes the physical network function descriptor PNFD corresponding to the PNF node ID and PNF node instantiation ID; the OSS sends the trigger migration message to NFVO, and the NSD has a virtual network resource description that replaces the PNF, and the NSD is used to identify the network service description of the network service NS where the PNF node is located. The virtual network resource Described as virtual network function descriptor VNFD or nested virtual network service description nestedNSD.

In the solution provided by the embodiment of the present invention, by designing the VNFD or nestedNSD that replaces the PNF in the NSD in advance, when the PNF fails or the operator needs to migrate the PNF function to the cloud, the NFVO can quickly migrate the PNF function to the NSD based on the above VNFD or nestedNSD In the VNF system, shorten the migration time from PNF to VNF.

In a possible design, before the OSS sends the trigger migration message to the NFVO, the method further includes: the OSS sends an instantiation instruction message to the NFVO, where the instantiation instruction message includes a PNFD identifier, and is used to instruct the PNF node corresponding to the PNFD identifier to perform The NS is instantiated to obtain the PNF node instantiation identifier in the trigger migration message. Through the instantiation instruction message, the OSS can instruct the NFVO to instantiate the NS for the PNF node.

In a possible design, after the OSS sends the migration trigger message to the NFVO, the method further includes: the OSS sends a migration message to the NFVO, where the migration message is used to instruct the NFVO to migrate the function of the PNF node from the NFV To the PNF, the fetch message includes the PNFD identifier and the PNF node instantiation identifier. In this way, the OSS instructs the NFVO to move the PNF function back from the virtual network resource to the PNF.

In a possible design, before the OSS sends the trigger migration message to the NFVO, the method further includes: the OSS receives a status sending indication message sent by the NFVO, the status sending indication message includes a PNF node instantiation identifier, and the status sending indication message is used for Instructing the OSS to send the current state of the PNF to the NFVO when the current state of the PNF changes. By subscribing to the PNF status, the NFVO can know the status of the PNF in a timely manner, and initiate PNF migration or relocation in time to improve the efficiency of PNF migration or relocation.

In a possible design, the migration trigger message also includes a PNF fault, and after the OSS sends the migration trigger message to the NFVO, the method further includes: the OSS receives a migration notification message sent by the NFVO, and the migration notification message is used to notify the OSS , the NFVO migrates the PNF function to the NFV, and the migration notification message includes a PNFD identifier and a PNF node instantiation identifier. Therefore, the NFVO triggers the PNF migration after receiving the information of the PNF failure. And when the NFVO determines to perform PNF migration, it notifies the OSS, so that the OSS can know the situation of the imminent migration of the PNF in time, and adjust corresponding functions according to the situation.

In a possible design, the relocation message also includes that the PNF failure is successfully repaired, and after the OSS sends a trigger relocation message to the NFVO, the method further includes: the OSS receives a relocation notification message sent by the NFVO, and the relocation notification message is used to notify the OSS that the The NFVO transfers the PNF function back from the NFV to the PNF, and the transfer notification message includes the PNFD identifier and the PNF node instantiation identifier. Therefore, after the NFVO receives the information that the PNF failure is successfully repaired, it triggers the PNF relocation. And when the NFVO determines to perform the PNF migration, it notifies the OSS, so that the OSS can know the situation that the PNF is about to be migrated back in time, and adjust the corresponding functions according to the situation.

In an example, the OSS includes a network slice manager. Therefore, the method can also be applied to 5G networks.

In the third aspect, the embodiment of the present invention provides a NFVO, which is applied to the network function virtualization NFV system, and the NFVO has the function of realizing the above-mentioned first aspect, and the function can be realized by hardware, and the corresponding function can also be executed by hardware. Software Implementation. The hardware or software includes one or more modules corresponding to the above functions.

In a fourth aspect, an embodiment of the present invention provides an NFVO, where the NFVO includes a processor, a receiver, and a transmitter, and the processor is configured to support the NFVO to perform corresponding functions in the foregoing method. The receiver and transmitter are used to support communication between NFVO and OSS. Further, the NFVO may also include a memory, which is used for coupling with the processor, and stores necessary program instructions and data of the NFVO.

In a fifth aspect, an embodiment of the present invention provides a computer storage medium for storing the above computer software instructions for the NFVO described in the third aspect, which includes a program designed to execute the above aspect.

In a sixth aspect, an embodiment of the present invention provides an OSS, the OSS has the function of realizing the second aspect above, and the function may be realized by hardware, or may be realized by executing corresponding software on the hardware. The hardware or software includes one or more modules corresponding to the above functions.

In a seventh aspect, an embodiment of the present invention provides an OSS, where the OSS includes a processor, a receiver, and a transmitter, and the processor is configured to support the OSS to perform corresponding functions in the foregoing method. The receiver and transmitter are used to support communication between OSS and NFVO. Further, the OSS may further include a memory, which is used to be coupled with the processor, and stores necessary program instructions and data of the OSS.

In an eighth aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for the OSS described in the sixth aspect, which includes a program designed to execute the above aspect.

In a ninth aspect, an embodiment of the present invention provides a PNF migration system, which includes the NFVO and OSS described in the above aspect.

Compared with the prior art, in the solution of the embodiment of the present invention, the VNFD or nestedNSD that replaces the PNF is designed in the NSD in advance, so that when the PNF fails or the operator needs to migrate the PNF function to the cloud, the NFVO can be based on the above-mentioned VNFD or nestedNSD Quickly migrate the PNF function to the VNF system, shortening the migration time from PNF to VNF.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. Those skilled in the art can also obtain other drawings based on these drawings without creative work.

FIG. 1 is a schematic diagram of the architecture of a network function virtualization NFV system provided by an embodiment of the present invention;

FIG. 2 is a schematic flow chart of a physical network function PNF migration method provided by an embodiment of the present invention;

FIG. 3 is a schematic flow chart of another physical network function PNF migration method provided by an embodiment of the present invention;

FIG. 4 is a block diagram of functional units of a network function virtualization orchestrator NFVO provided by the device embodiment of the present invention;

Fig. 5 is a schematic structural diagram of another NFVO provided by an embodiment of the present invention;

FIG. 6 is a block diagram of functional units of a network management system OSS provided by the device embodiment of the present invention;

FIG. 7 is a schematic structural diagram of another OSS provided by an embodiment of the present invention.

Detailed ways

In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention.

In order to better understand the technical solution of the present invention, the architecture of the Network Function Virtualization (Network Function Virtualization, NFV) system is briefly described below.

Referring first to FIG. 1, FIG. 1 is a schematic diagram of the architecture of a network function virtualization (NetworkFunction Virtualization, NFV) system 100 provided by an embodiment of the present invention. As shown in FIG. 1, the NFV system includes a network function virtualization management and orchestration system (NFV Management and Orchestration, NFV MANO) 110, network function virtualization infrastructure layer (NFV Infrastructure, NFVI for short) 120, multiple virtual network functions (Virtual Network Function, VNF) 130, multiple network element managers (Element Manager, EM) 140, and an operation/business support system (Operation Support System/Business Support System, OSS/BSS) 150.

Wherein, NFV MANO110 includes a network function virtualization orchestrator (NFV Orchestrator, NFVO) 111, one or more virtualized network function managers (VNF Manager, VNFM) 112 and a virtualized infrastructure manager (Virtualized Infrastructure Manager, VIM) 113, Network Service Catalog (Network Service Catalog, NS Catalog) 114, Virtualized Network Function Catalog (VNF Catalog) 115, Network Function Virtualization Instance (NFV Instance) 116, Network Function Virtualization Resources (NFV Resources) 117, jointly complete the entire Management and orchestration functions of the NVF100.

Among them, the main function of NFVO111 is to realize the life cycle management of Network Service (NS), such as deployment, expansion, reduction, offline, etc., as well as the resource orchestration and policy management functions of NFVI120; NFVO111 according to the network service descriptor (Network Service Descriptor, NSD) decomposes the requirements for each VNF115, and cooperates with VNFM112 to realize the deployment of VNFs.

The main function of VNFM112 is to realize the life cycle management of VNF115, such as deployment, capacity expansion, capacity reduction, offline, etc.; VNFM112 decomposes the virtual machine according to the virtual network function descriptor (VNF Descriptor, VNFD) template and VNF115 capacity requirements The requirements of virtual resources, cooperate with NFVO111 and VIM113 to complete the instantiation of VNF115.

VIM113 is used to control and manage the computing, storage and network resources of NFVI120, usually these resources are in the infrastructure field of the same operator, for example, all resources in a NFVI130 network point of presence (Point of Presence, POP), across multiple NFVI - POP resources, or resources within a NFVI-POP subnet.

In addition, the EM140 is used for unified management of cloud and non-cloud network elements, and the BSS/OSS150 can also be used for unified management of cloud and non-cloud network elements.

At present, NFV-MANO does not manage the traditional Physical Network Function (PNF) and is an external docking relationship with the traditional PNF. ) to describe, so when the PNF node in the NS fails or the PNF node is to be migrated to cloud resources, the operator needs to redesign the VNFD that replaces the PNF, and also needs to redesign a new NSD, resulting in long migration time and low efficiency. In view of the above problems, an embodiment of the present invention provides a PNF migration method. Detailed description will be given below.

In the physical network function PNF migration method provided in the embodiment of the present invention, the VNFD or embedded network service description (nestedNSD) that replaces the PNF is designed in the NSD in advance, so that when the PNF fails or the operator needs to migrate the PNF function to the cloud, the NFVO can Based on the above-mentioned VNFD or nestedNSD, the PNF function is quickly migrated to the VNF system, and the time for migrating from PNF to VNF is shortened.

Firstly, the design scheme of NSD is described in detail.

In the embodiment of the present invention, before the NFVO migrates the PNF function to the VNF, it is first necessary to design the NSD, specifically, by adding a field in the following path of the NSD: NSD:nsDeploymentFlavour:pnfProfile adds a new ProfileofReplacePNF field for Identifies the identification of the VNFD or nestedNSD that will replace the PNF node subsequently. Please refer to the table below for specific design methods:

See the table below for NSD information elements:

For the nsDeploymentFlavour information elements in the above table, see the following table:

See the following table for the PnfProfile information elements in the above table:

Therefore, through this design, the VNFD or nestedNSD that replaces the PNF node has an identifier in the NSD, which can be used for subsequent rapid migration of the PNF without redesigning the PNF.

The above PNF migration methods are described in detail below in different scenarios.

First refer to FIG. 2 . FIG. 2 is a schematic flowchart of a physical network function PNF migration method provided by an embodiment of the present invention. The method is applied to a network function virtualization NFV system, and the NFV system includes a network function virtualization orchestrator NFVO. The embodiment shown in FIG. 2 is used in a scenario where the network management system (Operations Support System, OSS for short) actively requests the NFVO to perform PNF migration when the PNF fails.

In the embodiment of the present invention, after designing the identification of the VNFD or nestedNSD that replaces the PNF node in the NSD, the NS is first instantiated to obtain the PNFD identification and the instantiation identification of the PNF node, and then the PNFD identification and the PNF node The function of the PNF node corresponding to the instantiation identifier is automatically migrated and retrieved, that is, the PNF can be automatically migrated and retrieved by performing the steps shown in FIG. 2 . In the step flow shown in Figure 2, step S201-step S203 shows the flow of NS initial instantiation, step S204-step S208 shows the flow of PNF migration, and step S209-step S213 shows the flow of PNF relocation . The details are as follows:

In step S201, the OSS sends an instantiation indication message to the NFVO. The NFVO receives the instantiation indication message sent by the OSS.

Wherein, the instantiation instruction message is used to instruct to perform NS instantiation on the PNF node corresponding to the PNFD identifier, so as to obtain the PNF node instantiation identifier for subsequent PNF fast migration. The instantiation indication message includes the PNFD identifier.

In the embodiment of the present invention, when a new network service needs to be established, the OSS sends an instantiation indication message to the NFVO, for example, when a voice call service needs to be established, the OSS sends an instantiation indication message to the NFVO, so that the The initial instantiation of the NS is performed, and the NS instantiation is performed on the PNF node corresponding to the PNFD identifier during the initial instantiation of the NS.

Optionally, in the scenario where the OSS actively initiates PNF migration when the PNF fails, the instantiation instruction message may also include a network node deployment identifier, which is used to instruct the NS network node to perform PNF deployment or VNF deployment. Specifically, at this time, the instantiate indication message may be an instantiate NS request (InstantiateNsRequest) message, and the NS initialization instance process is performed by adding a PNFD identifier and a PNF or VNF deployment identifier to the InstantiateNsRequest message. Therefore, when using PNF deployment, NFVO will return the PNF node instantiation ID to OSS.

Optionally, the instantiation indication message may also be other types of interface messages, so as to realize corresponding functions.

Optionally, in an embodiment of the present invention, the instantiate indication message may be an InstantiateNsRequest message, by adding a PNFD identifier (PNFD_id) and a priority identifier (PNForVNF_priority_flag) in the InstantiateNsRequest message. PNForVNF_priority_flag is used to indicate whether the network node in the NS uses PNF or VNF for deployment. When PNForVNF_priority_flag=PNF, the network node uses PNF for deployment. When PNForVNF_priority_flag=VNF, the node uses VNF for deployment.

Specifically, in an embodiment of the present invention, the message format of the instantiate indication message may be: InstantiateNsRequest(NS id, PNFD_id, PNForVNF_priority_flag=PNF), wherein, InstantiateNsRequest represents the instantiate NS request, and NS id represents the need to instantiate The ID of the NS, PNFD_id is used to indicate the ID of the PNFD, and PNForVNF_priority_flag=PNF is used to indicate that the network node is deployed using the PNF.

In step S202, the NFVO performs an NS initial instantiation process according to the instantiation indication message.

Specifically, in the embodiment of the present invention, when the network node is deployed using PNF, the PNF node instantiation identification information is obtained after the NS instantiation is completed.

Optionally, in a fifth-generation mobile communication technology (5th-Generation, 5G for short) network scenario, the initial instantiation of the NS may also be performed by network slicing.

In step S203, the NFVO sends a response message of the instantiation instruction message to the OSS.

Specifically, the response message of the instantiation instruction message includes the PNF node instantiation identifier, which is used to notify the NFVO of the PNF node instantiated on the NS.

It can be understood that by adding the PNForVNF_priority_flag to the instantiation indication message, the message can indicate whether to deploy the PNF or the VNF to the network node.

In the embodiment of the present invention, after the NS initial instantiation process is executed, when the PNF fails, steps S204-S208 can be used to automatically perform PNF migration.

It should be noted that the above NS initial instantiation process can also be applied to non-PNF faults, and the OSS actively requests PNF cloud migration.

Step S204, when the PNF fails, the OSS receives a PNF failure message.

Specifically, when the PNF fails, the PNF reports the PNF failure message to the OSS system through an element management system (Element Manager System, EMS).

Step S205, the OSS sends a trigger migration message to the NFVO. The NFVO receives the migration trigger message sent by the OSS.

Wherein, the trigger migration message is used to trigger the NFVO to migrate the function of the PNF node to NFV, and the trigger migration message includes the physical network function descriptor PNFD identifier corresponding to the PNF node and the instantiation identifier of the PNF node. The NSD has a virtual network resource description that replaces the PNF, the NSD is used to identify the network service description of the network service NS where the PNF node is located, and the NSD is used to identify the network service description of the network service NS where the PNF node is located, The virtual network resource description is a virtual network function descriptor VNFD or a nested virtual network service description nestedNSD.

In the embodiment of the present invention, the design of the NSD has been completed before the function migration of the PNF node. Add a virtual network resource description that replaces PNF in NSD, so that automatic migration can be realized when PNF migration is required.

Wherein, the PNFD is used to identify the physical network function description of the function of the PNF node on the NS.

The PNF node instantiation identifier is used to identify the PNF node instantiated in the NS, so that the PNDF identifier and the PNF node instantiation identifier carried in the trigger migration message can be used by the OSS to inform the NFVO of the PNF node that needs to be instantiated. The PNF node instantiation identifier may be one or multiple.

Optionally, when the PNF fails, in the scenario where the OSS actively initiates the PNF migration, the trigger migration message can be that when the PNF fails, the PNF reports the fault information to the OSS system through the EMS, and then the OSS system sends the request to the NFVO for News of PNF migration. That is, at this time, the PNF migration identifier can be carried in the trigger migration message to trigger the NFVO to perform PNF migration. Specifically, the trigger migration message is an update NS request message (UpdateNsRequest) message, carrying a PNF to VNF migration (PNF_Migrate_to_VNF) identifier.

Optionally, the trigger migration message may also be a message requesting PNF migration sent by the OSS to the NFVO when the operator needs to migrate the PNF cloud node. Specifically, at this time, the trigger migration message may also be an UpdateNsRequest message.

Optionally, the trigger migration message may also be other newly added interface message types for realizing the above functions. For example, PNFMigratetoVNFRequest message.

Specifically, in an embodiment of the present invention, the specific form of the trigger migration message may be: UpdateNsRequest(NS id, PNF_Migrate_to_VNF, Be_Migrated_PNFD id, PNF ins id), wherein, UpdateNsRequest represents an update NS request, and PNF_Migrate_to_VNF represents a PNF migration For VNF, Be_Migrated_PNFD id is used to indicate the PNFD ID of the PNF to be migrated, and PNF ins id is used to indicate the PNF node instantiation ID.

Specifically, in another embodiment of the present invention, the trigger migration message may also be a new interface message, and the format of the trigger migration message may be: PNFMigratetoVNFRequest(NS id, Be_Migrated_PNFD id, PNFins id). Wherein, PNFMigratetoVNFRequest represents a request for migrating a PNF to a VNF.

Step S206, the NFVO checks the validity of the PNF migration.

Specifically, at this time, the NFVO determines whether there is a PNFD or a nestedNSD that replaces the PNF in the NSD template according to the NSD indicated by the NS id. When the NFVO determines whether there is a PNFD or nestedNSD replacing the PNF in the NSD template according to the NSD indicated by the NS id, the NFVO determines that the legality check of the PNF migration is passed, so step S207 is executed to perform the PNF migration. Otherwise, do not execute.

Step S207, the NFVO triggers the NFV system to delete the PNF resource configuration in the NFV, and instantiates the virtual network of the PNF based on the PNFD identifier, the PNF node instantiation identifier and the virtual network resource description A resource, where the virtual network resource is a virtual network function VNF corresponding to the VNFD, or an embedded network service (nestedNS) corresponding to the nestedNSD.

Wherein, the virtual network resource refers to a virtual resource used to replace the above-mentioned PNF function in the VNF system, so based on the virtual resource, the PNF function can be migrated to the VNF system.

Specifically, the NFVO deletes connection resources and related configurations with the faulty PNF according to the PNF instantiation identifier, and instantiates a new VNF or nestedNS.

In step S208, after the instantiation of the PNF is completed, the NFVO sends a migration success notification message to the OSS. The OSS receives the migration success notification message sent by the NFVO.

Optionally, in an embodiment of the present invention, the migration success notification message further includes at least one of the following information:

The PNFD, the identifier of the virtual network resource description, and the identifier of the virtual network resource.

Wherein, the identifier of the virtual network resource description and the identifier of the virtual network resource are used to represent the NFV resources occupied after the PNF function is migrated to the VNF.

Optionally, if the virtual network resource replacing the PNF is an instantiated NVF, the identifier described by the virtual network resource may be a VNFD identifier (VNFD identification, VNFD ID), and the identifier of the virtual network resource is a VNF identifier (VNF identification , VNF ID).

Optionally, if the virtual network resource replacing the PNF is an instantiated nested NS, the identifier described by the virtual network resource may be a nested NSD identifier (nested NS identification, nested NS ID), and the identifier of the virtual network resource is nested NS identification (nested NS identification, nested NS ID).

Optionally, the migration success notification message may also include a PNF migration success identifier, which is used to notify the OSS that the PNF migration is successful.

It can be understood that by carrying the identifier of the virtual network resource description and the identifier of the virtual network resource replacing the PNF function in the message returned by the VNFD to the OSS, the OSS can more directly know the virtualized resource replacing the PNF function.

Specifically, the migration success notification message may be an update Ns response message UpdateNsResponse message. In the embodiment of the present invention, the UpdateNsResponse message carries a PNF to VNF migration success (PNF_Migrate_to_VNF_success) identifier, which is used to indicate that the PNF migration is successful. The migration success notification message also carries the PNFD ID of the replaced PNF, the VNFD ID information replacing the PNF, and the new instantiated VNF ID information; or if the nested NSD is used to replace the original PNF, the migration success notification message also carries Replace the nested NS ID information of the PNF and the instantiated nested NS ID information.

Specifically, in an embodiment of the present invention, the format of the migration success notification message is: UpdateNsRequest(PNF_Migrate_to_VNF_success, Be_Migrated_PNFD id, VNFD id of replace PNF, VNF ins id of replace PNF). Among them, UpdateNsRequest represents the update Ns request message, PNF_Migrate_to_VNF_success is the PNF migration success identifier, Be_Migrated_PNFD id is the PNFD identifier of the PNF to be migrated, VNFD id of replace PNF is the VNFD of the replacement PNF, and VNF ins id of replacePNF is the VNF identifier of the replacement PNF.

Specifically, in another embodiment of the present invention, the migration success notification message may also be a new interface message, and the specific format of the migration success notification message is: PNFMigratetoVNFResponse(success, Be_Migrated_PNFD id, VNFD id of replace PNF, VNF ins id of replace PNF), where PNFMigratetoVNFResponse indicates the migration response message from PNF to VNF, success indicates the successful identification of the migration, Be_Migrated_PNFD id is used to indicate the PNFD identification of the migrated PNF, VNFD id of replace PNF is the VNFD that replaces the PNF, VNF ins id of replace PNF is the VNF identifier of the replacement PNF.

After receiving the message, the OSS records that the current PNF node uses a virtualization node, and saves the relevant information transmitted by the interface.

Through the above process, after the PNF fails, the PNF can be automatically and quickly migrated to the VNF. It should be noted that the above migration process can also be applied to non-PNF faults. When the OSS actively requests cloud migration, the first request message sent by the OSS to the NFVO will not include the PNF fault message.

Optionally, in an embodiment of the present invention, in the scenario where the OSS actively requests cloud migration, the trigger migration message can also be a new interface message, and the specific message format is: PNFMigratetoVNFRequest(NS id, Be_Migrated_PNFD id, PNF ins id ), wherein, PNFMigratetoVNFRequest represents a migration request from PNF to VNF, NS id represents the identity of the initial instantiated NS, Be_Migrated_PNFD id is used to represent the PNFD identity of the PNF to be migrated, and PNF ins id is used to represent the PNF node instantiation identity. The migration success notification message can also be a newly added interface message. The specific format of the migration success notification message is: PNFMigratetoVNFResponse(success, Be_Migrated_PNFD id, VNFD id of replace PNF, VNF ins id of replace PNF), wherein, PNFMigratetoVNFResponse indicates that VNFD id of replace PNF is the VNFD of the replacement PNF, and VNF ins idof replace PNF is the VNF ID of the replacement PNF.

It can be seen from the above that the physical network function PNF migration method provided by the embodiment of the present invention designs the VNFD or nestedNSD that replaces the PNF in the NSD in advance, so that when the PNF fails or the operator needs to migrate the PNF function to the cloud, the NFVO can be based on the above VNFD Or nestedNSD quickly migrates the PNF function to the VNF system, shortening the migration time from PNF to VNF.

In the embodiment of the present invention, after the PNF fault recovers, the steps of step S209-step S212 can be used to automatically perform PNF relocation.

Step S209, when the PNF failure is repaired, the OSS sends a relocation message to the NFVO. NFVO receives the fetch message sent by OSS.

Wherein, the fetch message is used to instruct the NFVO to fetch the PNF function from the NFV to the PNF, and the fetch message includes the PNFD identifier and the PNF node instantiation identifier.

Optionally, in an embodiment of the present invention, in the scenario where the NFVO initiates the PNF, the fetch message may be a request message that the OSS system actively requests the NFVO to perform a PNF fetch after the PNF fault repair is completed, that is, At this time, the PNF fetch identifier can be carried in the fetch message to trigger the NFVO to perform the PNF fetch. Specifically, the fetch message may be an update Ns request (UpdateNsRequest) message.

Optionally, in another embodiment of the present invention, the relocation message may also be a message sent by the OSS to the NFVO to request PNF relocation when the operator needs to perform a PNF cloud node relocation.

Optionally, in another embodiment of the present invention, the fetch message may also be other newly added interface message types for realizing the above functions.

Optionally, in an embodiment of the present invention, when the NFVO sends a status sending indication message to the OSS requesting to subscribe to the PNF status, the fetch message also includes the information that the PNF fault repair is successful, that is, when the PNF fault repair is successful Afterwards, the OSS sends the PNF status information to the NFVO, and then the NFVO can execute the process of PNF retrieval triggered by the retrieval message.

It can be understood that by carrying the PNF fault repair message in the fetch message, it is used to trigger the NFVO to perform PNF fetch. In this manner, the NFVO can be informed of the status of the PNF in a timely manner, and initiate PNF migration or relocation in time, thereby improving the efficiency of PNF migration or relocation.

Optionally, in an embodiment of the present invention, it may be carried in the fetch message, carrying the VNF to PNF migration (VNF_Migrate_to_PNF) identifier, which is used to indicate that the PNF function is migrated back from the VNF to the PNF, and the fetch message also carries The ID of the PNFD to be retrieved and the instantiation ID of the PNF node. The PNFD ID and the PNF instantiation identifier are used to notify the NFVO which PNF function to migrate back to the PNF. The PNF node instantiation identifier may be one or multiple.

Specifically, in an embodiment of the present invention, the specific form of the fetch message may be: UpdateNsRequest(NS id, VNF_Migrate_to_PNF, PNFD id, PNF ins id), wherein UpdateNsRequest is an update Ns request message, and NS id represents the instantiated NS, VNF_Migrate_to_PNF means VNF migrates back to PNF ID, PNFD id is PNFD ID, PNF ins id is PFN node instantiation ID.

Specifically, in another embodiment of the present invention, the fetch message can also be a newly added interface message, and the specific form can be: VNFMigratetoPNFRequest(NS id, PNFD id, PNF ins id), wherein, VNFMigratetoPNFRequest is the fetch message from VNF to PNF In the request message, the NS id is used to identify the NS where the PNF node is located, the PNFD id is used to identify the PNFD of the fetched PNF, and the PNF ins id represents the instantiation identifier of the fetched PNF.

Step S210, the NFVO checks the validity of the PNF retrieval.

Specifically, in one embodiment of the present invention, the NFVO judges whether there is information about the PNFD and the VNFD or nested NSD information that replaces the PNF in the NSD, and the NFVO determines whether there is information about the PNFD and the VNFD or nested NSD that replaces the PNF in the NSD. When the NSD information is nested, the NFVO determines that the PNF retrieval is legally passed.

Specifically, in an embodiment of the present invention, the NFVO also judges whether the current state of the PNF is to use a VNF or a nested NSD. When the NFVO determines that the current state of the PNF uses VNF or nested NSD, the NFVO determines that the PNF retrieval is legally passed.

Specifically, in another embodiment of the present invention, the NFVO simultaneously judges whether the NSD has the information of the PNFD and the information of the VNFD or nested NSD replacing the PNF, and whether the current state of the PNF is to use the VNF or the nested NSD. When NFVO determines that the NSD has the information of the PNFD and the VNFD or nested NSD information that replaces the PNF, and the current status of the PNF uses VNF or nested NSD, the NFVO determines that the PNF retrieval is legally passed.

Optionally, if the validity check of the PNF fetch by the NFVO is passed, step S603 is performed, and the NFVO executes the process of fetching the PNF.

Optionally, if the validity check of the PNF fetch by the NFVO fails, the NFVO does not respond to the fetch message.

Step S211, the NFVO deletes the virtual network resource configuration used by the replacement PNF and instantiates the connection of the PNF.

Specifically, the NFVO determines the VNF that replaces the PNF function according to the PNFD ID and the PNF instantiation ID in the fetch message, and then deletes related connections and configurations of the VNF that replaces the PNF function.

At this time, NFVO moves back the PNF function from the virtual network resource to the PNF.

Step S212, after the replacement is successful, the NFVO sends a migration success notification message to the OSS.

Wherein, the migration success notification message is used to notify the OSS that the migration of the PNF function from the NFV to the PNF is successful.

Optionally, in an embodiment of the present invention, the retrieval success notification message further includes at least one of the following information:

The PNFD identifier, and the PNF instantiation identifier.

Optionally, the successful retrieval notification message may also include an identifier of a successful PNF retrieval, which is used to notify the OSS that the PNF retrieval is successful. Specifically, the fetch success notification message may be a notification (Notify) message, and the Notify message may include a PNFD identifier, a PNF instantiation identifier, and an identifier of a successful PNF fetch.

It can be understood that by carrying one or more of the PNFD identifier and the PNFD instantiation identifier in the message returned by the NFVO to the OSS after the fetch is successful, the OSS can more directly obtain the fetch from the VNF. The PNF.

Specifically, the migration success notification message carries the VNF to PNF migration success identifier (VNF_Migrate_to_PNF_success), as well as the repaired PNFD identifier and the PNF node instantiation identifier, and is used to notify the OSS, the PNF node function migration function, and the specific PNF node that is migrated back. .

Specifically, in one embodiment of the present invention, the specific format of the migration success notification message is: UpdateNsRequest(VNF_Migrate_to_PNF_success, PNFD id, PNF ins id), wherein, UpdateNsRequest is the update Ns request message, and VNF_Migrate_to_PNF_success is the successful migration of the VNF to the PNF PNFD id is the PNFD identifier corresponding to the fetched PNF, and PNF ins id is the instantiation identifier of the fetched PNF node.

Concretely, in another embodiment of the present invention, the notification message of successful relocation can also be a new interface message, and the specific form is: VNFMigratetoPNFResponse(success, PNFD id, PNF ins id), wherein, VNFMigratetoPNFResponse is the relocation of VNF to PNF In the response message, success is used to indicate that the migration of the VNF to the PNF is successful, and the PNF ins id indicates the PNF instantiation identifier of the migration.

Through the above steps S209-S212, the automatic retrieval of the PNF function can be realized. It should be noted that the above migration process can also be applied to non-PNF faults. When the OSS actively requests cloud migration, the migration message sent by the OSS to the NFVO will not include PNF fault recovery information.

It should be noted that the embodiment of the present invention can also be applied to a fifth-generation mobile communication technology (5th-Generation, 5G for short) network, and in this case, the above-mentioned OSS system can be a network slice manager.

Referring to FIG. 3 , FIG. 3 is a schematic flowchart of another physical network function PNF migration method provided by an embodiment of the present invention. The embodiment shown in FIG. 3 is used in the scenario where the NFVO subscribes to the PNF state, and after the NFVO receives the PNF fault message, the NFVO actively initiates the PNF migration. Wherein, in the method shown in FIG. 2 , for content that is the same as or similar to the method shown in FIG. 2 , reference may be made to the above detailed description, and details are not repeated here.

In the step flow shown in Figure 3, step S301-step S305 shows the flow of NS initial instantiation, step S306-step S311 shows the flow of PNF migration, and step S2312-step S316 shows the flow of PNF relocation . The details are as follows:

S301. The OSS sends an instantiation indication message to the NFVO. The NFVO receives the instantiation indication message sent by the OSS.

Optionally, in an embodiment of the present invention, in the scenario where the NFVO actively initiates PNF migration and recall, when the PNF fails, the instantiation indication message may also include whether the PNF failure can use the VNF replacement identifier, and the PNF failure Whether to reset the flag after repairing. The OSS sends these two identifiers to the NFVO during initialization to indicate whether to perform PNF migration or back migration when the subsequent NFVO actively initiates PNF migration or relocation.

Optionally, in an embodiment of the present invention, when the instantiation indication message includes whether the PNF failure can use the VNF replacement flag, only when the PNF failure can use the VNF replacement flag is positive, when the PNF fault The PNF function is migrated to the VNF, otherwise the migration is not performed.

Optionally, in one embodiment of the present invention, when the instantiation indication message includes whether the flag of whether to revert after the PNF fault is repaired, then only when the flag of whether to relocate after the PNF fault is repaired is affirmative, the PNF Functions are relocated from the VNF to the PNF, otherwise no relocation is performed.

Specifically, in one embodiment of the present invention, when the OSS creates a Network Service request, the instantiation instruction message can be an InstantiateNsRequest message at this time, and the PNFD identification and PNF fault are added to the InstantiateNsRequest message. Whether to use the VNF to replace the ID, and whether to restore the ID after the PNF fault is repaired.

Specifically, in an embodiment of the present invention, the message format of the instantiate indication message is: InstantiateNsRequest(NS id, PNFD_id, PNForVNF_priority_flag=PNF, PNF-fail-Migtate_to_VNF_flag, PNF-Restore-Back-flag).

Among them, InstantiateNsRequest is the instantiated Ns request message, and PNF-fail-Migtate_to_VNF_flag is the flag of whether the PNF fault can be replaced by VNF, which is used to identify whether the PNF fault can be replaced by VNF. If the flag is Yes, it means that the PNF fault can be replaced by VNF. VNF is used for replacement. If the flag is NO, it means that PNF failure cannot be replaced by VNF.

Among them, the PNF-Restore-Back-flag is the flag of whether to restore after the PNF fault is repaired, which is used to identify whether to restore the mark after the PNF fault is repaired, or if the flag is Yes, it means that the PNF fault needs to be restored after the repair. If the mark is If No, it means that it does not need to be moved back after the PNF fault is repaired. After receiving the instantiation indication message, the NFVO records relevant information.

S302. The NFVO performs an NS initial instantiation process according to the instantiation indication message.

Specifically, in the embodiment of the present invention, when the network node is deployed using PNF, PNF node instantiation identification information, that is, PNF ID, is obtained after NS instantiation is completed.

Optionally, in a 5G network scenario, the initial instantiation of the NS can also be performed by the network slice.

In step S303, the NFVO sends a response message of the instantiation instruction message to the OSS.

Specifically, the response message of the instantiation indication message includes PNFD and PNFD instantiation ID information.

Step S304, the NFVO sends a status sending indication message to the OSS. The OSS receives the status sending indication message sent by the NFVO.

Wherein, the status sending indication message includes the instantiation identifier of the PNF node, and the status sending indication message is used to instruct the OSS to send the current status of the PNF to the NFVO when the current status of the PNF changes. state.

Optionally, the state sending indication message may also include a PNF state identifier, which is used to identify the state information subscribed to the PNF.

Specifically, the status sending indication message may be a Subscriber message, and the Subscriber message includes a PNF instantiation identifier and a PNF status identifier.

Specifically, the status sending indication message may also be of other interface message types. Used to realize the corresponding function.

Optionally, in an embodiment of the present invention, when the indication of whether the PNF failure can be replaced by the VNF is positive, the NFVO sends a status sending indication message to the OSS.

Optionally, in an embodiment of the present invention, when the NFVO sends a status sending indication message to the OSS requesting to subscribe to the PNF status, the trigger migration message also includes the PNF failure, that is, when the PNF fails, the OSS sends a notification to the NFVO The status information of the PNF is sent, and then the NFVO can execute the process of PNF migration under the trigger of the trigger migration message.

It can be understood that in order for the NFVO to know the status information of the PNF in a timely manner, the NFVO can send a status subscription message to the OSS, so that when the status of the PNF changes, the OSS sends the status information of the PNF to the NFVO in time, so that the NFVO can obtain the status information of the PNF. When the status information shows that the PNF is faulty, the NFVO is triggered to perform PNF migration. That is, by carrying the PNF failure message in the trigger migration message, it is used to trigger the NFVO to perform PNF migration. In this manner, the NFVO can be informed of the status of the PNF in a timely manner, and initiate PNF migration or relocation in time, thereby improving the efficiency of PNF migration or relocation.

Specifically, when the NFVO reads that the value of PNF-fail-Migtate_to_VNF_flag in the InstantiateNsRequest is Yes, the NFVO sends a status sending indication message to the OSS.

Optionally, the status sending indication message may also include a PNF start migration identifier, which is used by the NFVO to notify the OSS that the PNF migration is about to start.

Specifically, in one embodiment of the present invention, the message format of the state sending indication message is: Subscriber(PNF ins id, PNF-State, Begin_PNF_Migrate_to_VNF), wherein, Subscriber is a subscription message, and PNF-State is a PNF state identifier, PNF_Migrate_to_VNF_success is used to indicate that PNF migration is about to start.

Step S305, the OSS sends a status sending indication message response message to the NFVO.

Wherein, the status sending indication message response message is a response message made by the OSS after receiving the status sending indication message sent by the NVFO.

Through the above process, the NS initial instantiation process can be realized, and at the same time, the NFVO can subscribe to the PNF status information, so that the NFVO can receive the PNF status information in time, and respond in time after the PNF failure or PNF failure recovery.

In the embodiment of the present invention, after the initial instantiation process of the NS is completed, when the PNF fails, steps S306-S311 can be used to automatically migrate the PNF.

In step S306, a fault occurs in the PNF, and the fault information is reported to the OSS. Thus the OSS receives the PNF failure message.

Step S307, the OSS sends a trigger migration message to the NFVO. The NFVO receives the migration trigger message sent by the OSS.

Optionally, in one embodiment of the present invention, in the scenario where NFVO subscribes to the PNF state, and if the PNF fails, NFVO initiates migration on its own initiative, after the OSS system receives the PNF failure message, the OSS system sends the failure information to the NFVO , at this time, the trigger migration message includes the PNF failure message. Then, after learning of the PNF failure, the NFVO actively performs PNF migration, that is, it considers that the PNF failure message carried in the trigger migration message is used to trigger the NFVO to perform PNF migration. Specifically, at this time, the trigger migration message may be a publish (Publish) message. The Publish message includes PNF failure information.

In the embodiment of the present invention, since the NFVO initiated the PNF status subscription process to the OSS during the initial instantiation process of the NS, the OSS sends a trigger migration message to the NFVO after the PNF fails.

In the embodiment of the present invention, the trigger migration message includes a PNFD ID, a PNF instantiation ID, and PNF status information. At this time, the PNF status information is PNF failure.

Optionally, the trigger migration message also includes a PNF status type, for example, when the PNF status information is a PNF failure, the PNF status type is the cause of the PNF failure.

Specifically, the trigger migration message is a Publish message, and the specific form of the message is: Publish(PNFDid, PNF ins id, PNF_State=fault, cause=XXX), wherein, the PNFD id is used to represent the PNFD of the PNF to be migrated An identifier, PNF ins id is used to indicate the PNF node instantiation identifier, PNF_State=fault indicates a PNF fault, and cause=XXX indicates a PNF fault type.

Step S308, the NFVO checks the validity of the PNF migration.

In the embodiment of the present invention, because the trigger migration message carries the information that the PNF has failed, and which PNF has failed specifically, the NFVO can perform PNF migration under the trigger of the trigger migration message.

Specifically, in one embodiment of the present invention, the NFVO judges whether there is a VNFD or nestedND that replaces the PNF in the NSD. When the NFVO determines that there is a VNFD or nestedND that replaces the PNF in the NSD, the NFVO determines that the legality check of the PNF migration passes.

Specifically, in another embodiment of the present invention, since the migration request is actively initiated by the NFVO, when the instantiation indication message sent by the OSS includes whether the PNF failure can be replaced by a VNF as affirmative, the NFVO determines that the PNF The legality check of the migration is passed.

Specifically, in another embodiment of the present invention, when the NFVO determines that there is a VNFD or nestedND with a substitute PNF in the NSD, and the instantiation indication message sent by the OSS includes whether the PNF failure can be replaced by a VNF as affirmative, the NFVO determines that The legality check of PNF migration is passed.

Optionally, when the NFVO determines that the validity check of the PNF migration is passed, step S309 is executed and the PNF migration is performed.

Optionally, when the NFVO determines that the validity check of the PNF relocation fails, it ignores the trigger request for triggering the relocation message.

Step S309, the NFVO sends a migration notification message to the OSS. The OSS receives the migration notification message sent by the NFVO.

Wherein, the migration notification message is used to notify the OSS that the NFVO migrates the PNF function to the NFV, and the migration notification message includes the PNFD identifier and the PNF node instantiation identifier.

In the embodiment of the present invention, the migration notification message includes a PNFD ID, a PNF node instantiation identifier and a PNF migration identifier.

Optionally, the migration notification message may also include a PNF start migration identifier, which is used by the NFVO to notify the OSS that the PNF migration is about to start.

Specifically, the migration notification message can be a notification (Notify) message, and the message format can be: Notity(PNFD id, PNF ins id, Begin_PNF_Migrate_to_VNF), wherein, the PNFD id is the PNFD of the PNF to be migrated, and the PNF ins id is the PNF to be migrated The PNF node instantiation identifier, Begin_PNF_Migrate_to_VNF is the PNF start migration identifier, which is used to indicate that the migration from the PNF to the VNF is about to start.

It can be understood that in this scenario, when the NFVO determines to perform PNF migration, it notifies the OSS, so that the OSS can learn the situation of the imminent migration of the PNF in time, and adjust corresponding functions according to the situation.

Step S310, the NFVO deletes connection resources and related configurations with the faulty PNF, and instantiates a new VNF or nestedNS.

Furthermore, the NFVO configures the corresponding network connection and configuration of the VNF or nestedNS node that replaces the PNF.

In step S311, after the PNF instantiation is completed, the NFVO sends a migration success notification message to the OSS. The OSS receives the migration success notification message sent by the NFVO.

In the embodiment of the present invention, the migration success notification message includes a PNFD ID and a PNF node instantiation identifier.

Optionally, the migration success notification message also includes indication information of successful PNF migration.

Specifically, the migration success notification message may be a notification (Notify) message, and the message format may be: Notity (PNFD id, PNF ins id, PNF_Migrate_to_VNF_success), wherein, PNF_Migrate_to_VNF_success is used to indicate that the PNF migrates successfully to the VNF.

Through the above steps S306-S311, the PNF can be automatically and rapidly migrated when the PNF fails. Moreover, since the NFVO subscribes to the PNF state information, when the PNF fails, the NFVO can migrate the PNF in time to ensure the PNF function.

In the embodiment of the present invention, after the PNF fault recovers, steps S312-S316 can be used to automatically retrieve the PNF.

In step S312, after the PNF failure is repaired, the OSS sends a relocation message to the NFVO.

In the embodiment of the present invention, the fetch message includes a PNFD identifier, a PNF node instantiation identifier, and a PNF repair success identifier.

Optionally, in an embodiment of the present invention, in the scenario where the NFVO subscribes to the PNF fault message and the NFVO initiates the PNF reversion initiatively, the relocation message may also be the result of the successful repair of the fault by the OSS system after the PNF fault repair is completed. The information is sent to NFVO. At this time, the trigger migration message includes the successful repair information of the PNF fault. After learning that the PNF fault repair is successful, the NFVO takes the initiative to perform PNF relocation, which means that the OSS carries the PNF fault repair success message in the relocation message to trigger Perform NFVO for PNF fetch. Specifically, at this time, the fetch message may be a publish (Publish) message. The Publish message includes PNF failure recovery information.

Specifically, the fetch message is a Publish message, and the message format may be: Push(PNFD id, PNF ins id, PNF_State=Normal), where the PNFD id indicates the PNFD of the PNF that needs to be fetched, and the PNF ins id represents the PNF that needs to be fetched. PNF node instantiation identifier, PNF_State=Normal indicates that the PNF fault is repaired successfully.

Step S313, NFVO judges the legality of the retrieval.

Optionally, the NFVO judges whether there is information about the PNFD and information about the VNFD or nested NSD that replaces the PNF in the NSD. When the NSD has the information of the PNFD and the information of the VNFD or nested NSD that replaces the PNF, the NFVO determines the validity of the PNF fetch.

And, optionally, the NFVO also judges whether the current state of the PNF is to use a VNF or a nested NSD. When the current state of PNF is to use VNF or nested NSD, NFVO determines the legality of PNF fetching.

Optionally, because in this scenario, when the OSS includes the flag of whether to revert after the PNF fault is repaired in the instantiation indication message, the NFVO also judges whether the flag of whether to relocate after the PNF fault is repaired indicates that the PNF fault can be relocated after the repair, when the PNF When the fault can be relocated after the fault is repaired, the NFVO determines the legality of the PNF reversion.

Step S314, the NFVO sends a relocation notification message to the OSS.

Wherein, the fetch notification message is used to notify the OSS that the NFVO fetches the PNF function from the NFV to the PNF, and the fetch notification message includes the PNFD identifier and the PNF node instantiation identifier .

Optionally, the fetch notification message may also include a PNF fetch start identifier, which is used by the NFVO to notify the OSS that the PNF fetch is about to start.

Specifically, the migration notification message may be a notification (Notity) message, and the message format may be: Notity(PNFD id, PNF ins id, Begin_VNF_Migrate_to_PNF), wherein, the PNFD id is the PNFD of the PNF to be migrated back, and the PNF ins id is the PNF to be migrated back. The PNF node instantiation identifier, Begin_PNF_Migrate_to_VNF is the PNF start migration identifier, which is used to indicate that the migration from VNF to PNF is about to start.

It can be understood that in this scenario, when the NFVO determines to carry out the PNF rollback, it notifies the OSS, so that the OSS can know the situation that the PNF is about to roll back in time, and adjusts corresponding functions according to the situation.

Step S315, the NFVO instantiates the network connection and configuration to the PNF, and simultaneously deletes the related connection and configuration of the VNF that replaces the PNF function.

Step S316, after the replacement is successful, the NFVO sends a migration success notification message to the OSS.

Specifically, the fetch success notification message carries the PNFD ID and the PNF instantiation identifier.

Optionally, the fetch success notification message also includes indication information that the PNF fetch is successful.

Specifically, the migration success notification message can be a Notify message, and the message format can be: Notity(PNFD id, PNF ins id, Begin_VNF_Migrate_to_PNF_success), wherein, PNFDid is the PNFD of the PNF whose migration is successful, and the PNF ins id is the migration success PNF node instantiation identifier, Begin_VNF_Migrate_to_PNF_success indicates that VNF migrates back to PNF successfully.

Through the above reversion process, the PNF can be automatically and quickly relocated when the PNF fault is repaired. In addition, since the NFVO subscribes to the PNF state information, after the PNF fault is repaired, the NFVO can timely revert the PNF to improve the efficiency of the PNF relocation.

It should be noted that the embodiment of the present invention can also be applied to a 5G network, and at this time, the above-mentioned OSS system can be a network slice manager.

Please refer to FIG. 4 . FIG. 4 is a block diagram of functional units of a network function virtualization orchestrator NFVO400 provided by the device embodiment of the present invention. As shown in the figure, the NFVO400 includes a receiving module 410 and an instantiation module 420 . in:

The receiving module 410 is configured to receive a trigger migration message sent by the network management system OSS, and is used to trigger the NFVO to migrate the function of the PNF node to the NFV system, and the trigger migration message includes a physical network function description corresponding to the PNF node PNFD identifier and PNF node instantiation identifier, the NSD has a virtual network resource description that replaces the PNF, and the NSD is used to identify the network service description of the network service NS where the PNF node is located, and the virtual network resource description is a virtual network function Descriptor VNFD or nested virtual network service description nestedNSD.

The instantiation module 420 is configured to instantiate the virtual network of the PNF based on the PNFD identifier, the PNF node instantiation identifier and the virtual network resource description after the NFV system deletes the PNF resource configuration in the NFV. A network resource, where the virtual network resource is a virtual network function VNF corresponding to the VNFD, or an embedded network service nestedNS corresponding to the nestedNSD.

Optionally, in an embodiment of the present invention, the receiving module 410 is further configured to receive an instantiation indication message sent by the OSS, the instantiation indication message includes a PNFD identification, and is used to indicate that the PNFD identification The corresponding PNF node performs NS instantiation to obtain the PNF node instantiation identifier in the trigger migration message.

Optionally, in an embodiment of the present invention, the receiving module 410 is further configured to receive a fetch message sent by the OSS, where the fetch message is used to instruct the NFVO to transfer the function of the PNF node from the The NFV fetches back to the PNF, and the fetch message includes the PNFD identifier and the PNF node instantiation identifier;

The NFVO also includes a deletion module 430, configured to delete the virtual network resource configuration that replaces the PNF and instantiate the connection of the PNF.

Optionally, in one embodiment of the present invention, the NFVO400 also includes:

A sending module 440, configured to send a status sending indication message to the OSS, where the status sending indication message includes the instantiation identifier of the PNF node, and the status sending indication message is used to indicate the current status of the OSS in the PNF When a change occurs, the current state of the PNF is sent to the NFVO.

Optionally, in an embodiment of the present invention, the trigger migration message further includes the PNF failure, and the sending module 440 is further configured to send a migration notification message to the OSS, and the migration notification message is used to notify The OSS, the NFVO migrate the PNF function to the NFV, and the migration notification message includes the PNFD identifier and the PNF node instantiation identifier.

Optionally, in an embodiment of the present invention, the fetch message further includes that the PNF fault is repaired successfully, and the sending module 440 is further configured to send a fetch notification message to the OSS, and the fetch notification message is used to The OSS is notified that the NFVO fetches the PNF function from the NFV to the PNF, and the fetch notification message includes the PNFD identifier and the PNF node instantiation identifier.

Optionally, in an embodiment of the present invention, the instantiation instruction message also includes a network node deployment identifier or whether a PNF failure uses a VNF replacement identifier, and the instantiation module 420 is specifically used for:

When the network node deployment identifier indicates that the network nodes in the NS use PNF deployment, instantiate the virtual network resource of the PNF based on the PNFD identifier, the PNF node instantiation identifier, and the virtual network resource description; or ,

When the PNF failure uses the VNF replacement identifier to instruct the NFVO to use the VNF for replacement when the PNF fails, based on the PNFD identifier, the PNF node instantiation identifier, and the virtual network resource description instantiation The virtual network resource of the PNF.

Optionally, in an embodiment of the present invention, the instantiation indication message further includes whether to fetch back the flag after the PNF fault is repaired, and the deletion module 430 is specifically used to indicate whether the fetching flag indicates the When the PNF performs a PNF fetch, delete and replace the virtual network resource configuration used by the PNF and instantiate the connection of the PNF.

It can be seen that in the solution of this embodiment, by designing the VNFD or nestedNSD that replaces the PNF in the NSD in advance, when the PNF fails or the operator needs to migrate the PNF function to the cloud, the NFVO400 can quickly transfer the PNF function based on the above-mentioned VNFD or nestedNSD Migrate to the VNF system to shorten the time for migrating from PNF to VNF.

It should be noted that the virtual network function processing device described in the device embodiment of the present invention is presented in the form of a functional unit. The term "unit" used here should be understood as the broadest meaning possible. The object used to realize the functions described by each "unit" can be, for example, an integrated circuit ASIC, a single circuit, used to execute one or more software or firmware Processors (shared, dedicated, or chipsets) and memories of programs, combinational logic circuits, and/or other suitable components that provide the functions described above.

For example, those skilled in the art may consider that the NFVO may specifically be the NFVO entity device shown in FIG. 5 .

Please refer to FIG. 5 . FIG. 5 is a schematic structural diagram of another NFVO provided by an embodiment of the present invention. As shown in the figure, the NFVO500 provided by the embodiment of the present invention includes a processor 501, a memory 502, a receiver 503, a transmitter 504 and a bus 505, and the processor 501, the memory 502, the receiver 503 and the transmitter 504 are connected through the bus 504 and communicate with each other.

The processor 501 is configured to call the executable program code in the memory 502 to perform the following operations:

The trigger migration message sent by the network management system OSS is received by the receiver 503, which is used to trigger the NFVO to migrate the function of the PNF node to the NFV system, and the trigger migration message includes a physical network function description corresponding to the PNF node PNFD identifier and PNF node instantiation identifier, the NSD has a virtual network resource description that replaces the PNF, and the NSD is used to identify the network service description of the network service NS where the PNF node is located, and the virtual network resource description is a virtual network function Descriptor VNFD or nested virtual network service description nestedNSD;

After the NFV system deletes the PNF resource configuration in the NFV, instantiate the virtual network resource of the PNF based on the PNFD identifier, the PNF node instantiation identifier and the virtual network resource description, the virtual network The resource is a virtual network function VNF corresponding to the VNFD, or an embedded network service nestedNS corresponding to the nestedNSD.

Optionally, in an embodiment of the present invention, before the NFVO instantiates the virtual network resource of the PNF based on the virtual network resource description, the processor 501 is further configured to:

The instantiation instruction message sent by the OSS is received by the receiver 503, the instantiation instruction message includes a PNFD identifier, and is used to instruct to perform NS instantiation on the PNF node corresponding to the PNFD identifier, so as to obtain the triggered migration PNF node instantiation identifier in the message.

Optionally, in an embodiment of the present invention, after the NFVO instantiates the virtual network resource of the PNF based on the virtual network resource description, the processor 501 is further configured to:

The sender 504 receives the fetch message sent by the OSS, the fetch message is used to instruct the NFVO to fetch the function of the PNF node from the NFV to the PNF, and the fetch message includes the PNFD ID and the instantiation ID of the PNF node;

Delete the virtual network resource configuration that replaces the PNF used and instantiate the connection of the PNF.

Optionally, in an embodiment of the present invention, before the NFVO receives the trigger migration message sent by the network management system OSS, the processor 501 is further configured to:

Send a status sending indication message to the OSS by the transmitter 504, the status sending indication message includes the instantiation identifier of the PNF node, and the status sending indication message is used to indicate the current status of the OSS in the PNF When a change occurs, the current state of the PNF is sent to the NFVO.

Optionally, in an embodiment of the present invention, the trigger migration message further includes the PNF fault, and the instantiation of the PNF node based on the PNFD identifier, the PNF node instantiation identifier, and the virtual network resource description Before the virtual network resources of the PNF, the processor 501 is further configured to:

The migration notification message is sent to the OSS by the transmitter 504, the migration notification message is used to notify the OSS that the NFVO migrates the PNF function to the NFV, and the migration notification message includes the PNFD ID and the instantiation ID of the PNF node.

Optionally, in an embodiment of the present invention, the fetch message further includes that the PNF failure is successfully repaired, and the NFVO deletes the virtual network resource configuration used by the PNF and instantiates the PNF before the processing The device 501 is also used for:

The sender 504 sends a relocation notification message to the OSS, the relocation notification message is used to notify the OSS that the NFVO relocated the PNF function from the NFV to the PNF, and the relocation notification message It includes the PNFD identifier and the PNF node instantiation identifier.

Optionally, in an embodiment of the present invention, the instantiation instruction message further includes a network node deployment identifier or a VNF replacement identifier for a PNF failure, and the processor 501 based on the PNFD identifier, the PNF node instance The virtualization identifier and the virtual network resource description instantiate the virtual network resource of the PNF, specifically:

When the network node deployment identifier indicates that the network nodes in the NS use PNF deployment, instantiate the virtual network resource of the PNF based on the PNFD identifier, the PNF node instantiation identifier, and the virtual network resource description; or ,

When the PNF failure uses the VNF replacement identifier to instruct the NFVO to use the VNF for replacement when the PNF fails, based on the PNFD identifier, the PNF node instantiation identifier, and the virtual network resource description instantiation The virtual network resource of the PNF.

Optionally, in an embodiment of the present invention, the instantiation indication message further includes an identifier of whether to revert after the PNF failure is repaired, and the processor 501 deletes the virtual network resource configuration used by the PNF and instantiates the PNF ,Specifically:

When the flag of whether to move back after the PNF failure is repaired indicates that the PNF performs a PNF move back, delete and replace the virtual network resource configuration used by the PNF and instantiate the connection of the PNF.

It can be seen that in the solution of this embodiment, by designing the VNFD or nestedNSD that replaces the PNF in the NSD in advance, when the PNF fails or the operator needs to migrate the PNF function to the cloud, the NFVO100 can quickly transfer the PNF function based on the above-mentioned VNFD or nestedNSD Migrate to the VNF system to shorten the time for migrating from PNF to VNF.

It should be noted that the processor 501 here may be one processor, or may be a general term for multiple processing elements. For example, the processor may be a central processing unit (Central Processing Unit, CPU), or a specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention , for example: one or more microprocessors (digital signal processor, DSP), or, one or more field programmable gate arrays (Field Programmable Gate Array, FPGA).

The memory 502 may be a storage device, or may be a general term for multiple storage elements, and is used to store executable program codes or parameters and data required for the operation of the access network management device. And the memory 502 may include random access memory (RAM), and may also include non-volatile memory (non-volatile memory), such as disk memory, flash memory (Flash), and the like.

The bus 505 may be an Industry Standard Architecture (Industry Standard Architecture, ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (Extended Industry Standard Architecture, EISA) bus, etc. The bus 505 can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used in FIG. 5 , but it does not mean that there is only one bus or one type of bus.

In the aforementioned embodiment shown in FIG. 4 , the functions of each unit can be implemented based on the structure of the NFVO shown in FIG. 5 . In the aforementioned embodiment shown in FIG. 2 or FIG. 3 , the method flow of each step can be implemented based on the NFVO shown in FIG. 5 .

Please refer to FIG. 6 . FIG. 6 is a block diagram of functional units of an OSS600 provided by the device embodiment of the present invention. As shown in the figure, the OSS600 includes a generation module 610 and a sending module 620 . in:

A generating module 610, configured to generate a trigger migration message when the function of the PNF node needs to be migrated to the NFV system, for triggering the NFVO to migrate the function of the PNF node to the NFV system, the The trigger migration message includes a physical network function descriptor PNFD identifier corresponding to the PNF node and a PNF node instantiation identifier;

The sending module 620 is configured to send the trigger migration message to the NFVO, the NSD has a virtual network resource description replacing the PNF, the NSD is used to identify the network service description of the network service NS where the PNF node is located, and the virtual Network resources are described as virtual network function descriptor VNFD or nested virtual network service description nestedNSD.

Optionally, in an embodiment of the present invention, the sending module 620 is further configured to send an instantiation indication message to the NFVO, where the instantiation indication message includes a PNFD identifier, and is used to indicate that the PNFD identifier corresponds to The PNF node instantiates the NS to obtain the PNF node instantiation identifier in the trigger migration message.

Optionally, in an embodiment of the present invention, the sending module 620 is further configured to send the fetch message to the NFVO, where the fetch message is used to instruct the NFVO to transfer the function of the PNF node from the The NFV is fetched to the PNF, and the fetch message includes the PNFD identifier and the PNF node instantiation identifier.

Optionally, in an embodiment of the present invention, the OSS600 further includes:

The receiving module 630 is configured to receive a status transmission indication message sent by the NFVO, the status transmission indication message includes the instantiation identifier of the PNF node, and the status transmission indication message is used to indicate that the OSS is currently in the PNF When the state changes, send the current state of the PNF to the NFVO.

Optionally, in an embodiment of the present invention, the trigger migration message further includes the PNF failure, and the receiving module 630 is further configured to receive a migration notification message sent by the NFVO, and the migration notification message uses In order to notify the OSS, the NFVO migrates the PNF function to the NFV, and the migration notification message includes the PNFD identifier and the PNF node instantiation identifier.

Optionally, in an embodiment of the present invention, the fetch message further includes that the PNF failure is successfully repaired, and the receiving module 620 is further configured to receive a fetch notification message sent by the NFVO, and the fetch notification message uses In order to notify the OSS, the NFVO fetches the PNF function from the NFV to the PNF, and the fetch notification message includes the PNFD identifier and the PNF node instantiation identifier.

It can be seen that in the solution of this embodiment, the VNFD or nestedNSD that replaces the PNF is designed in advance in the NSD, so that when the PNF fails or the operator needs to migrate the PNF function to the cloud, the NFVO can quickly transfer the PNF function based on the above-mentioned VNFD or nestedNSD Migrate to the VNF system to shorten the time for migrating from PNF to VNF.

It should be noted that the virtual network function processing device described in the device embodiment of the present invention is presented in the form of a functional unit. The term "unit" used here should be understood as the broadest meaning possible. The object used to realize the functions described by each "unit" can be, for example, an integrated circuit ASIC, a single circuit, used to execute one or more software or firmware Processors (shared, dedicated, or chipsets) and memories of programs, combinational logic circuits, and/or other suitable components that provide the functions described above.

For example, those skilled in the art may consider that the OSS may specifically be the OSS entity device shown in FIG. 7 .

Referring to FIG. 7, see FIG. 7. FIG. 7 is a schematic structural diagram of another OSS provided by an embodiment of the present invention. As shown in FIG. 7, the OSS 700 includes:

Transmitter/receiver 701 and processor 702. Wherein, the processor 702 may also be a controller, which is represented as "controller/processor 702" in FIG. 7 . The transmitter/receiver 701 is used to support the sending and receiving of information between the OSS 700 and the NFVO in the above embodiments, and to support the radio communication between the OSS 700 and other devices. The processor 702 performs various functions for communicating with the OSS 700 . In the uplink, uplink signals from other devices are received via the antenna, demodulated by the receiver 701 (e.g. demodulating high frequency signals to baseband signals), and further processed by the processor 702 to recover the signal transmitted by the OSS 700 to business data and signaling information. On the downlink, business data and signaling messages are processed by the processor 702 and modulated by the transmitter 701 (for example, modulating the baseband signal into a high-frequency signal) to generate a downlink signal, and transmit it to other equipment. It should be noted that the above demodulation or modulation function may also be completed by the processor 702 . For example, the processor 702 is also configured to execute corresponding steps in the foregoing method embodiments, and/or other processes of the technical solutions described in the embodiments of the present invention.

Further, the OSS700 may further include a memory 703 for storing program codes and data of the OSS700. In addition, the OSS 700 may further include a communication unit 704 . The communication unit 704 is configured to support the access router to communicate with the terminal. For example, in an LTE system, the communication unit 704 may also be an S1-MME interface, configured to support communication between the OSS and a mobility management entity (Mobility Management Entity, MME).

It can be understood that FIG. 7 only shows a simplified design of OSS 700 . In practical applications, OSS700 may include any number of transmitters, receivers, processors, controllers, memories, communication units, etc., and all OSSs that can implement the embodiments of the present invention are within the protection scope of the embodiments of the present invention .

An embodiment of the present invention also provides a computer storage medium, wherein the computer storage medium can store a program, and when the program is executed, some or all steps of the PNF migration method described in the above method embodiments are included.

It should be noted that for the foregoing method embodiments, for the sake of simple description, they are expressed as a series of action combinations, but those skilled in the art should know that the present invention is not limited by the described action sequence. Because of the present invention, certain steps may be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification belong to preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

In the foregoing embodiments, the descriptions of each embodiment have their own emphases, and for parts not described in detail in a certain embodiment, reference may be made to relevant descriptions of other embodiments.

In the several embodiments provided in this application, it should be understood that the disclosed device can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or can be Integrate into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical or other forms.

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

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the essence of the technical solution of the present invention or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage media include: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes. .

As mentioned above, the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still understand the foregoing The technical solutions recorded in each embodiment are modified, or some of the technical features are replaced equivalently; and these modifications or replacements do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.

Claims (31)

1. A physical network function PNF migration method is characterized in that, the method is applied to a network function virtualization NFV system, and the NFV system includes a network function virtualization orchestrator NFVO, and the method includes: The NFVO receives a trigger migration message sent by the network management system OSS, which is used to trigger the NFVO to migrate the function of the physical network function PNF node to the NFV system, and the trigger migration message includes the physical network function descriptor PNFD corresponding to the PNF node Identification and PNF node instantiation identification, the network function descriptor NSD has a virtual network resource description that replaces the PNF, and the NSD is used to identify the network service description of the network service NS where the PNF node is located, and the virtual network resource description is virtual Network function descriptor VNFD or nested virtual network service description nestedNSD; After the NFV system deletes the PNF resource configuration in the NFV, the NFVO instantiates the virtual network resource of the PNF based on the PNFD identifier, the PNF node instantiation identifier, and the virtual network resource description, so The virtual network resource is a virtual network function VNF corresponding to the VNFD, or an embedded network service nestedNS corresponding to the nestedNSD. 2. The method according to claim 1, wherein before the NFVO instantiates the virtual network resource of the PNF based on the virtual network resource description, the method further comprises: The NFVO receives the instantiation instruction message sent by the OSS, the instantiation instruction message includes a PNFD identifier, and is used to instruct to perform NS instantiation on the PNF node corresponding to the PNFD identifier, so as to obtain the PNF node instantiation identifier. 3. The method according to claim 2, wherein after the NFVO instantiates the virtual network resource of the PNF based on the virtual network resource description, the method further comprises: The NFVO receives a fetch message sent by the OSS, the fetch message is used to instruct the NFVO to fetch the function of the PNF node from the NFV to the PNF, and the fetch message includes the PNFD identifier and the The instantiation identifier of the PNF node; The NFVO deletes and replaces the virtual network resource configuration used by the PNF and instantiates the connection of the PNF. 4. The method according to claim 3, wherein, before the NFVO receives the trigger migration message sent by the network management system OSS, the method further comprises: The NFVO sends a status sending indication message to the OSS, the status sending indication message includes the PNF node instantiation identifier, and the status sending indication message is used to indicate to the OSS when the current status of the PNF changes , sending the current state of the PNF to the NFVO. 5. The method according to claim 4, wherein the trigger migration message further includes the PNF failure, and the PNF node instantiation identifier based on the PNFD and the virtual network resource description instance Before optimizing the virtual network resources of the PNF, the method also includes: The NFVO sends a migration notification message to the OSS, the migration notification message is used to notify the OSS that the NFVO migrates the PNF function to the NFV, and the migration notification message includes the PNFD identifier and the The PNF node instantiation identifier. 6. The method according to claim 4, wherein the relocation message further includes that the PNF failure is successfully repaired, and the NFVO deletes the virtual network resource configuration used by the PNF and instantiates the PNF, the The method also includes: The NFVO sends a relocation notification message to the OSS, the relocation notification message is used to notify the OSS that the NFVO relocated the PNF function from the NFV to the PNF, and the relocation notification message includes the The PNFD identifier and the instantiation identifier of the PNF node. 7. The method according to claim 2, wherein the instantiation indication message also includes whether a network node deployment identifier or a PNF failure uses a VNF replacement identifier, and the NFVO is based on the PNFD identifier, the PNF node instance The virtualization identifier and the virtual network resource description instantiate the virtual network resource of the PNF, specifically: When the network node deployment identifier indicates that the network nodes in the NS use PNF deployment, the NFVO instantiates the virtual network of the PNF based on the PNFD identifier, the PNF node instantiation identifier, and the virtual network resource description resources; or, When the PNF failure uses the VNF replacement identifier to instruct the NFVO to use the VNF for replacement when the PNF fails, the NFVO is based on the PNFD identifier, the PNF node instantiation identifier, and the virtual network resource Describes the virtual network resource that instantiates the PNF. 8. The method according to claim 3, wherein the instantiation instruction message further includes an identifier of whether to move back after the PNF failure is repaired, and the NFVO deletes the virtual network resource configuration used by the PNF and instantiates the PNF ,Specifically: When the flag of whether to switch back after the PNF fault is repaired indicates that the PNF performs PNF rollback, the NFVO deletes the virtual network resource configuration used by the replaced PNF and instantiates the connection of the PNF. 9. A physical network function PNF migration method, characterized in that, the method is applied to a network function virtualization NFV system, and the NFV system includes a network function virtualization orchestrator NFVO, and the method includes: When it is necessary to migrate the function of the physical network function PNF node to the NFV system, the network management system OSS generates a trigger migration message, which is used to trigger the NFVO to migrate the function of the PNF node to the NFV system, so The trigger migration message includes the physical network function descriptor PNFD identifier corresponding to the PNF node and the instantiation identifier of the PNF node; The OSS sends the trigger migration message to the NFVO, the network function descriptor NSD has a virtual network resource description that replaces the PNF, and the NSD is used to identify the network service description of the network service NS where the PNF node is located. A virtual network resource is described as a virtual network function descriptor VNFD or a nested virtual network service description nestedNSD. 10. The method according to claim 9, wherein before the OSS sends a trigger migration message to the NFVO, the method further comprises: The OSS sends an instantiation instruction message to the NFVO, the instantiation instruction message includes a PNFD identifier, and is used to instruct the PNF node corresponding to the PNFD identifier to perform NS instantiation to obtain the PNF in the triggered migration message Node instantiation ID. 11. The method according to claim 10, wherein after the OSS sends a trigger migration message to the NFVO, the method further comprises: The OSS sends a fetch message to the NFVO, the fetch message is used to instruct the NFVO to fetch the function of the PNF node from the NFV to the PNF, and the fetch message includes the PNFD identifier and the PNF node instantiation identifier. 12. The method according to claim 11, wherein before the OSS sends a trigger migration message to the NFVO, the method further comprises: The OSS receives the status sending indication message sent by the NFVO, the status sending indication message includes the instantiation identifier of the PNF node, and the status sending indication message is used to indicate that the OSS changes in the current status of the PNF , send the current state of the PNF to the NFVO. 13. The method according to claim 12, wherein the trigger migration message further includes the PNF fault, and after the OSS sends the trigger migration message to the NFVO, the method further comprises: The OSS receives a migration notification message sent by the NFVO, the migration notification message is used to notify the OSS that the NFVO migrates the PNF function to the NFV, and the migration notification message includes the PNFD identifier and The PNF node instantiation identifier. 14. The method according to claim 13, wherein the relocation message further includes that the PNF failure is successfully repaired, and after the OSS sends a trigger migration message to the NFVO, the method further includes: The OSS receives the relocation notification message sent by the NFVO, the relocation notification message is used to notify the OSS that the NFVO relocated the PNF function from the NFV to the PNF, and the relocation notification message includes the The PNFD identifier and the PNF node instantiation identifier. 15. A network function virtualization orchestrator NFVO is characterized in that, applied to a network function virtualization NFV system, NFVO includes: The receiving module is configured to receive a trigger migration message sent by the network management system OSS, and is used to trigger the NFVO to migrate the function of the physical network function PNF node to the NFV system, and the trigger migration message includes the physical network corresponding to the PNF node The function descriptor PNFD identifier and the PNF node instantiation identifier, the network function descriptor NSD has a virtual network resource description that replaces the PNF, and the NSD is used to identify the network service description of the network service NS where the PNF node is located, and the virtual network The resource description is a virtual network function descriptor VNFD or a nested virtual network service description nestedNSD; An instantiation module, configured to instantiate the virtual network of the PNF based on the PNFD identifier, the PNF node instantiation identifier and the virtual network resource description after the NFV system deletes the PNF resource configuration in the NFV resource, the virtual network resource is a virtual network function VNF corresponding to the VNFD, or an embedded network service nestedNS corresponding to the nestedNSD. 16. The NFVO according to claim 15, wherein the receiving module is further configured to receive an instantiation instruction message sent by the OSS, the instantiation instruction message includes a PNFD identifier, and is used to indicate that the PNFD Identify the corresponding PNF node and instantiate the NS, so as to obtain the PNF node instantiation identifier in the trigger migration message. 17. The NFVO according to claim 16, characterized in that, The receiving module is further configured to receive a fetch message sent by the OSS, the fetch message is used to instruct the NFVO to fetch the function of the PNF node from the NFV to the PNF, and the fetch message includes the PNFD identification and the instantiation identification of the PNF node; The NFVO also includes a deletion module, configured to delete the virtual network resource configuration used by the PNF and instantiate the connection of the PNF. 18. The NFVO according to claim 17, wherein the NFVO further comprises: A sending module, configured to send a status sending indication message to the OSS, the status sending indication message including the instantiation identifier of the PNF node, and the status sending indication message used to indicate that the OSS occurs in the current state of the PNF When changed, the current state of the PNF is sent to the NFVO. 19. The NFVO according to claim 18, wherein the trigger migration message further includes the PNF failure, and the sending module is further configured to send a migration notification message to the OSS, and the migration notification message is used for The OSS is notified that the NFVO migrates the PNF function to the NFV, and the migration notification message includes the PNFD identifier and the PNF node instantiation identifier. 20. The NFVO according to claim 18, wherein the relocation message further includes that the PNF failure is successfully repaired, and the sending module is further configured to send a relocation notification message to the OSS, and the relocation notification message uses In order to notify the OSS, the NFVO fetches the PNF function from the NFV to the PNF, and the fetch notification message includes the PNFD identifier and the PNF node instantiation identifier. 21. The NFVO according to claim 15, wherein the instantiation instruction message also includes whether a network node deployment identification or a PNF failure uses a VNF replacement identification, and the instantiation module is specifically used for: When the network node deployment identifier indicates that the network nodes in the NS use PNF deployment, instantiate the virtual network resource of the PNF based on the PNFD identifier, the PNF node instantiation identifier, and the virtual network resource description; or , When the PNF failure uses the VNF replacement identifier to instruct the NFVO to use the VNF for replacement when the PNF fails, based on the PNFD identifier, the PNF node instantiation identifier, and the virtual network resource description instantiation The virtual network resource of the PNF. 22. The NFVO according to claim 17, wherein the instantiation indication message also includes whether to retrieve an identifier after the PNF fault is repaired, and the deletion module is specifically used to indicate whether to retrieve the identifier after the PNF fault is repaired. When the PNF performs PNF fetching, delete and replace the virtual network resource configuration used by the PNF and instantiate the connection of the PNF. 23. A network management system OSS, characterized in that the OSS comprises: A generating module, configured to generate a trigger migration message when the function of the physical network function PNF node needs to be migrated to the network function virtualization NFV system, and is used to trigger the NFVO to migrate the function of the PNF node to the NFV In the system, the trigger migration message includes a physical network function descriptor PNFD identifier corresponding to the PNF node and a PNF node instantiation identifier; A sending module, configured to send the trigger migration message to the NFVO, the network function descriptor NSD has a virtual network resource description replacing the PNF, and the NSD is used to identify the network service description of the network service NS where the PNF node is located, The virtual network resource description is a virtual network function descriptor VNFD or a nested virtual network service description nestedNSD. 24. The OSS according to claim 23, wherein the sending module is further configured to send an instantiation indication message to the NFVO, and the instantiation indication message includes a PNFD identification for indicating that the PNFD identification The corresponding PNF node performs NS instantiation to obtain the PNF node instantiation identifier in the trigger migration message. 25. The OSS according to claim 24, wherein the sending module is further configured to send a fetch message to the NFVO, the fetch message is used to instruct the NFVO to transfer the function of the PNF node from the The NFV fetches back to the PNF, and the fetch message includes the PNFD identifier and the PNF node instantiation identifier. 26. The OSS according to claim 25, wherein the OSS further comprises: A receiving module, configured to receive a status sending indication message sent by the NFVO, where the status sending indication message includes the instantiation identifier of the PNF node, and the status sending indication message is used to indicate the current status of the OSS in the PNF When a change occurs, the current state of the PNF is sent to the NFVO. 27. The OSS according to claim 26, wherein the trigger migration message further includes the PNF fault, and the receiving module is further configured to receive a migration notification message sent by the NFVO, and the migration notification message uses In order to notify the OSS, the NFVO migrates the PNF function to the NFV, and the migration notification message includes the PNFD identifier and the PNF node instantiation identifier. 28. The OSS according to claim 27, wherein the relocation message further includes that the PNF failure is successfully repaired, and the receiving module is further configured to receive a relocation notification message sent by the NFVO, the relocation notification message It is used to notify the OSS that the NFVO fetches the PNF function from the NFV to the PNF, and the fetch notification message includes the PNFD identifier and the PNF node instantiation identifier. 29. A physical network function PNF migration system, characterized in that the system includes a network function virtualization orchestrator NFVO and a network management system OSS; The NFVO is the NFVO according to any one of claims 15 to 22; The OSS is the OSS described in any one of claims 23 to 28. 30. A computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by hardware, the method according to any one of claims 1 to 8 can be implemented. 31. A computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by hardware, the method according to any one of claims 9 to 14 can be implemented.