CN108259200A

CN108259200A - A kind of physical network function PNF moving methods and relevant device

Info

Publication number: CN108259200A
Application number: CN201611246922.6A
Authority: CN
Inventors: 方海鹏
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2016-12-29
Filing date: 2016-12-29
Publication date: 2018-07-06
Anticipated expiration: 2036-12-29
Also published as: CN108259200B; WO2018121354A1

Abstract

The embodiment of the invention discloses a kind of physical network function PNF moving methods and relevant device, the method is applied to network function and virtualizes NFV systems, and the NFV systems include network function and virtualize composer NFVO, the method includes：The function of PNF nodes for triggering the NFVO is migrated to NFV systems, has the virtual network resource description for substituting PNF in NSD by the triggering migration message that the NFVO receiving network managings system OSS is sent；After PNF resource distributions in NFV described in the NFV system-kills, the NFVO is identified based on the PNFD, PNF node instanceizations mark and the virtual network resource describe to instantiate the virtual network resource of the PNF.Quickly PNF functions are migrated into VNF systems so as to realize, shorten the time that PNF is migrated to VNF.

Description

Physical network function PNF migration method and related equipment

Technical Field

The invention relates to the field of communication, in particular to a Physical Network Function (PNF) migration method and related equipment.

Background

Network Function Virtualization (NFV) is mainly used to make industry-wide standards for Network Function Virtualization.

In NFV, the functions of managing and editing the entire NFV are mainly implemented by NFV-MANO (NFV Management and organization). In the NFV-MANO, different functions of the NVF are managed by different Function modules, for example, NFVO is an important module in the NFV-MANO, and can be used to decompose requirements for each Virtual Network Function (VNF) according to Network Service Description (NSD), and implement deployment of the VNF in cooperation with a virtualized Network Function Manager (VNF Manager, VNFM). The VNFM is mainly used for decomposing the demand on virtual resources such as a virtual machine according to the VNFD template and the VNF capacity demand, and completing instantiation of the VNF in cooperation with the NFVO and the VIM.

At present, the NFV-MANO does not manage the traditional Physical Network Function (PNF), and belongs to an external docking relationship with the traditional Physical Network Function (PNF), when a PNF node in the Network Service fails or the PNF node needs to migrate to a cloud resource, an operator needs to redesign a VNFD to replace the PNF, and at the same time, a new NSD needs to be redesigned, and the deployment time is long, which results in a long Service interruption time.

Disclosure of Invention

The embodiment of the invention provides a physical network function PNF migration method and related equipment, so that PNF functions can be rapidly migrated to a VNF system, and the PNF migration efficiency is improved.

In a first aspect, an embodiment of the present invention provides a PNF migration method, where the method is applied to a Network Function Virtualization (NFV) system, where the NFV system includes a network function virtualization orchestrator NFVO, and the method includes: the method comprises the steps that NFVO receives a triggering migration message sent by an OSS (network management system) and is used for triggering the NFVO to migrate the function of a PNF node to an NFV (network virtual appliance) system, the triggering migration message comprises a physical network function descriptor PNFD (public network data field) identifier and a PNF node instantiation identifier corresponding to the PNF node, NSD has a virtual network resource description replacing the PNF, NSD is used for identifying a network service description of a network service NS where the PNF node is located, and the virtual network resource description is a virtual network function descriptor VNFD or a 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, where the virtual network resource is a virtual network function VNF corresponding to VNFD or an embedded network service nestedNS corresponding to nestedNS.

In the scheme provided by the embodiment of the invention, by designing the VNFD or the nestedNSD for replacing the PNF in the NSD in advance, when the PNF fails or an operator needs to migrate the PNF function cloud, the NFVO can rapidly migrate the PNF function to the VNF system based on the VNFD or the nestedNSD, so that the time for migrating the PNF to the VNF is shortened.

In one possible design, before the NFVO instantiates the virtual network resource of the PNF based on the virtual network resource description, the method further includes: and the NFVO receives an instantiation indication message sent by the OSS, wherein the instantiation indication message comprises a PNFD identifier and is used for indicating to carry out NS instantiation on the PNF node corresponding to the PNFD identifier so as to obtain the PNF node instantiation identifier in the migration triggering message. Through the instantiation indication message, NS instantiation can be carried out on the PNF node.

In one 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 method comprises the steps that NFVO receives a migration message sent by OSS, wherein the migration message is used for indicating the NFVO to migrate the functions of PNF nodes from NFV to PNF, and the migration message comprises PNFD identifications and PNF node instantiation identifications; the NFVO then deletes the virtual network resource configuration that replaced the PNF's use and instantiates the PNF's connection. Thereby realizing the migration of the PNF function from the virtual network resource to the PNF.

In one possible design, before the NFVO receives the migration triggering message sent by the network management system OSS, the method further includes: and the NFVO sends a state sending indication message to the OSS, wherein the state sending indication message comprises a PNF node instantiation identifier, and the state sending indication message is used for indicating the OSS to send the current state of the PNF to the NFVO when the current state of the PNF is changed. Therefore, the NFVO can timely acquire the state of the PNF, timely initiate PNF migration or migration, and improve PNF migration or migration efficiency.

In one possible design, the migration triggering message further includes a PNF failure, 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 migration notification message to the OSS, wherein the migration notification message is used for notifying the OSS, the NFVO migrates the PNF function to the NFV, and the migration notification message comprises a PNFD identifier and a PNF node instantiation identifier. Therefore, the NFVO triggers the PNF migration after receiving the PNF failure information. And when the NFVO determines to carry out PNF migration, the OSS is informed, so that the OSS can timely know the condition that PNF is about to migrate, and the corresponding function is adjusted according to the condition.

In one possible design, the migration back message further includes that the PNF is successfully repaired, and before the NFVO deletes the configuration of the virtual network resource used by the PNF and instantiates the PNF, the method further includes: the NFVO sends a migration notification message to the OSS, wherein the migration notification message is used for notifying the OSS, the NFVO migrates the PNF function from the NFV to the PNF, and the migration notification message comprises a PNFD identifier and a PNF node instantiation identifier. Therefore, after receiving the information that PNF fault repair is successful, the NFVO triggers PNF to return. And when the NFVO determines to carry out PNF migration, the OSS is informed, so that the OSS can timely know the condition that the PNF is about to return, and corresponding functions are adjusted according to the condition.

In one possible design, the instantiation indication message further includes a network node deployment identifier or a VNF replacement identifier for whether the PNF fault uses, 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, when the PNF failure indicates that the NFVO replaces the PNF at the time of the PNF failure with the VNF replacement identifier, 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 OSS can control whether the NFVO migrates the PNF to the virtual network resource more flexibly.

In a possible design, the instantiation indication message further includes an identifier of whether to migrate after the PNF has failed to repair, and the NFVO deletes the virtual network resource configuration used by the PNF and instantiates the PNF, specifically: and when the back-migration flag indicates that the PNF performs PNF back-migration after the PNF fault is repaired, the NFVO deletes the virtual network resource configuration used for replacing the PNF and instantiates the connection of the PNF. Therefore, the OSS can control whether the NFVO transfers the PNF back or not more flexibly.

In one example, after the NFVO instantiates the virtual network resource of the PNF based on the PNFD identification, the PNF node instantiation identification, and the virtual network resource description, the method further comprises: and the NFVO sends a migration success notification message to the OSS, wherein the migration success notification message is used for notifying the OSS that the instantiation of the virtual network resources of the PNF is successful. Therefore, the OSS can timely acquire the successful state of PNF migration.

In one example, the migration success notification message further includes at least one of: the PNFD, an identification of the virtual network resource description, and an identification of the virtual network resource. Thereby allowing the OSS to more directly learn of the virtualized resources that replace the PNF function.

In one example, after the NFVO deletes the virtual network resource configuration that replaces PNF usage and instantiates a connection for the PNF, the method further comprises: and the NFVO sends a message of successful migration back notification to the OSS. Therefore, the OSS can timely know the state of the PNF successfully migrated back.

In one example, the migration success notification message further includes at least one of: a PNFD identification and a PNFD instantiation identification. Thereby making the OSS more directly accessible to PNFs migrating back from the VNF.

In an example, the OSS includes a network slice manager. Thereby enabling the method to be applied to a fifth Generation mobile communication technology (5th-Generation, abbreviated as 5G) network.

In a second aspect, an embodiment of the present invention further provides a physical network function PNF migration method, where the method is applied to a network function virtualization NFV system, where the NFV system includes a network function virtualization orchestrator NFVO, and the method includes: under the condition that the function of the PNF node needs to be migrated to the NFV system, the network management system OSS generates a migration triggering message for triggering the NFVO to migrate the function of the PNF node to the NFV system, wherein the migration triggering message comprises a physical network function descriptor PNFD identifier corresponding to the PNF node and a PNF node instantiation identifier; the OSS sends the trigger migration message to the NFVO, and the NSD has a virtual network resource description replacing the PNF, and is configured to identify a network service description of a network service NS where the PNF node is located, where the virtual network resource description is a virtual network function descriptor VNFD or a nested virtual network service description nestedNSD.

In one possible design, before the OSS sends the migration triggering message to the NFVO, the method further includes: and the OSS sends an instantiation indication message to the NFVO, wherein the instantiation indication message comprises a PNFD identifier and is used for indicating to carry out NS instantiation on the PNF node corresponding to the PNFD identifier so as to obtain a PNF node instantiation identifier in the migration triggering message. Through the instantiation indication message, the OSS may instruct the NFVO to perform NS instantiation of the PNF node.

In one possible design, after the OSS sends a migration triggering message to the NFVO, the method further includes: and an OSS sends a migration message to the NFVO, wherein the migration message is used for indicating the NFVO to migrate the functions of the PNF node from the NFV to the PNF, and the migration message comprises the PNFD identification and the PNF node instantiation identification. Thereby realizing that the OSS instructs the NFVO to migrate the PNF function from the virtual network resource back to the PNF.

In one possible design, before the OSS sends the migration triggering message to the NFVO, the method further includes: the OSS receives a state sending indication message sent by the NFVO, wherein the state sending indication message comprises a PNF node instantiation identifier, and the state sending indication message is used for indicating the OSS to send the current state of the PNF to the NFVO when the current state of the PNF is changed. Through PNF state subscription, the NFVO can timely acquire the state of the PNF and timely initiate PNF migration or migration, and the PNF migration or migration efficiency is improved.

In one possible design, the migration trigger message further includes a PNF failure, 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, wherein the migration notification message is used for notifying the OSS, the NFVO migrates the PNF function to the NFV, and the migration notification message comprises a PNFD identifier and a PNF node instantiation identifier. Therefore, the NFVO triggers the PNF migration after receiving the PNF failure information. And when the NFVO determines to carry out PNF migration, the OSS is informed, so that the OSS can timely know the condition that PNF is about to migrate, and the corresponding function is adjusted according to the condition.

In a possible design, the migration back message further includes a PNF fault repair success, and after the OSS sends a migration triggering message to the NFVO, the method further includes: the OSS receives a migration notification message sent by the NFVO, wherein the migration notification message is used for notifying the OSS, the NFVO migrates the PNF function from the NFV to the PNF, and the migration notification message comprises a PNFD identifier and a PNF node instantiation identifier. Therefore, after receiving the information that PNF fault repair is successful, the NFVO triggers PNF to return. And when the NFVO determines to carry out PNF migration, the OSS is informed, so that the OSS can timely know the condition that the PNF is about to return, and corresponding functions are adjusted according to the condition.

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

In a third aspect, an embodiment of the present invention provides an NFVO, where the NFVO is applied to a network function virtualization NFV system, and the NFVO has a function of implementing the first aspect, where the function may be implemented by hardware or may be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described 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 the NFVO and OSS. Further, the NFVO may also include a memory, coupled to the processor, that holds the necessary program instructions and data for the NFVO.

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

In a sixth aspect, an embodiment of the present invention provides an OSS, where the OSS has a function of implementing the second aspect, where the function may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions.

In a seventh aspect, an embodiment of the present invention provides an OSS, which includes a processor, a receiver and a transmitter, wherein the processor is configured to support the OSS to perform corresponding functions in the above method. The receiver and transmitter are used to support communication between the OSS and the NFVO. Further, the OSS may also include a memory, coupled to the processor, that stores program instructions and data necessary for 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 of the sixth aspect, which includes a program designed to execute the OSS of the sixth aspect.

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

Compared with the prior art, in the scheme of the embodiment of the invention, by designing the VNFD or the nestedNSD for replacing the PNF in the NSD in advance, when the PNF fails or an operator needs to migrate the PNF function cloud, the NFVO can rapidly migrate the PNF function into the VNF system based on the VNFD or the nestedNSD, and the time for migrating the PNF to the VNF is shortened.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a schematic architecture diagram of a network function virtualization NFV system according to an embodiment of the present invention;

fig. 2 is a flowchart illustrating a physical network function PNF migration method according to an embodiment of the present invention;

fig. 3 is a flowchart illustrating another physical network function PNF migration method according to an embodiment of the present invention;

fig. 4 is a functional unit block diagram of a network function virtualization orchestrator NFVO according to an embodiment of the present invention;

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

fig. 6 is a functional unit block diagram of an OSS according to an embodiment of the present invention;

fig. 7 is a schematic structural diagram of another OSS according to an embodiment of the present invention.

Detailed Description

In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention.

To better understand the technical solution of the present invention, the following briefly describes the architecture of a Network Function Virtualization (NFV) system.

Referring first to fig. 1, fig. 1 is a schematic diagram of an architecture of a Network Function Virtualization (NFV) System 100 according to an embodiment of the present invention, and as shown in fig. 1, the NFV System includes a network Function Virtualization Management and Orchestration System (NFV MANO)110, a network Function Virtualization Infrastructure layer (NFV Infrastructure, NFVI)120, a plurality of Virtual Network Functions (VNFs) 130, a plurality of Element Managers (EM) 140, and an Operation/service Support System (Operation Support System/Business Support System, OSS/BSS) 150.

The NFV MANO110 includes a Network function virtualization Orchestrator (NFV editor, NFVO)111, one or more Virtualized Network function managers (VNF managers, VNFM)112, a Virtualized Infrastructure Manager (VIM) 113, a Network service directory (NS directory) 114, a Virtualized Network function directory (VNF directory) 115, a Network function virtualization Instance (NFV Instance)116, and a Network function virtualization resource (NFV Resources)117, which together complete the management and orchestration functions of the entire NVF 100.

The NFVO111 has a main function of implementing life cycle management of Network Service (NS), such as deployment, capacity expansion, capacity reduction, offline, and the like, and a function of performing resource arrangement and policy management of the NFVI 120; the NFVO111 decomposes the requirements for each VNF115 according to a Network Service Descriptor (NSD), and implements deployment of the VNF in cooperation with the VNFM 112.

The primary function of the VNFM112 is to implement lifecycle management of the VNF115, such as deployment, capacity expansion, capacity reduction, offline, and the like; the VNFM112 resolves the demand for virtual resources such as virtual machines according to a virtual network function Descriptor (VNF Descriptor, VNFD) template and the capacity demand of the VNF115, and completes instantiation of the VNF115 by cooperating with the NFVO111 and the VIM 113.

The VIM113 is used to control and manage the computation, storage, and network resources of the NFVI120, typically those resources that are in the same carrier's infrastructure domain, such as all resources at one NFVI130 Point of Presence (POP), resources that span multiple NFVI-POPs, or resources within a subnet of one NFVI-POP.

In addition, EM140 is used to uniformly manage cloud and non-cloud network elements, and BSS/OSS150 may also be used to uniformly manage cloud and non-cloud network elements.

At present, NFV-MANO does not manage a traditional Physical Network Function (PNF for short), and belongs to an external docking relationship with a traditional PNF, and in NFV-MANO110, the PNF is described by a Physical Network Function Descriptor (PNF Descriptor, PNFD), so that when a PNF node in NS fails or the PNF node needs to migrate to a cloud resource, an operator needs to redesign a VNFD to replace the PNF, and a new NSD needs to be redesigned at the same time, which results in long migration time and low efficiency. In view of the foregoing problems, an embodiment of the present invention provides a physical network function PNF migration method. The details will be described below.

In the physical network function PNF migration method provided in the embodiment of the present invention, by designing a VNFD or an embedded network service description (nestdnsd) that replaces a PNF in the NSD in advance, when a PNF fails or an operator needs to migrate a PNF function cloud, the NFVO can quickly migrate the PNF function into the VNF system based on the VNFD or the nestdnsd, and the time for migrating the PNF to the VNF is shortened.

The design of the NSD is first described in detail.

In the embodiment of the present invention, before the NFVO migrates the PNF function to the VNF, the NSD needs to be designed first, specifically, by adding fields in the following path of the NSD: a new ProfileofRepleSpF field is added in the NSD, nsDeploymentFlavoour, pnfProfile and is used for identifying the subsequent VNFD replacing the PNF node or the identifier of the nestedNSD. The specific design method is seen in the following table:

NSD information elements are seen in the following table:

the nsdepolymentflagavour information elements in the above table are seen in the following table:

the PnfProfile information elements in the above table are referred to in the following table:

thus, by the design, the NSD is provided with the identity of the VNFD or the nestedNSD of the substitute PNF node for the subsequent rapid migration of the PNF without redesigning the PNF.

The PNF migration method described above is described in detail in different scenarios, respectively.

Referring to fig. 2, fig. 2 is a schematic flowchart of a physical network function PNF migration method according to an embodiment of the present invention, where 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, when a PNF fails, a network management System (OSS) actively requests an NFVO to perform PNF migration.

In the embodiment of the present invention, after the VNFD or the nestdnsd identifier replacing the PNF node is designed in the NSD, the NS is initially instantiated to obtain the PNFD identifier and the PNF node instantiation identifier, and then the PNF node function corresponding to the PNFD identifier and the PNF node instantiation identifier is automatically migrated and migrated, that is, the PNF may be automatically migrated and migrated by executing the steps shown in fig. 2. In the step flow shown in fig. 2, step S201 to step S203 show the flow of NS initial instantiation, step S204 to step S208 show the flow of PNF migration, and step S209 to step S213 show the flow of PNF migration back. The details are as follows:

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

The instantiation indication message is used for indicating NS instantiation of the PNF node corresponding to the PNFD identification, so that a PNF node instantiation identification is obtained for performing PNF fast migration subsequently. The instantiation indication message comprises a PNFD identification.

In the embodiment of the invention, when a network service needs to be newly 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 NS initial instantiation is performed at this time, and NS instantiation is performed on a PNF node corresponding to a PNFD identifier in the process of NS initial instantiation.

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

Optionally, the instantiation indication message may also be other interface message types for implementing corresponding functions.

Optionally, in an embodiment of the present invention, the instantiation indication message may be an instantatenesrequest message, and the PNFD identifier (PNFD _ id) and the priority identifier (PNForVNF _ priority _ flag) are added to the instantatenesrequest message. The PNForVNF _ priority _ flag is used to indicate whether a network node in the NS is deployed by using a PNF or a VNF, and when the PNForVNF _ priority _ flag is PNF, the network node is deployed by using the PNF, and when the PNForVNF _ priority _ flag is VNF, the node is deployed by using the VNF.

Specifically, in an embodiment of the present invention, the message format of the instantiation indication message may be: instantatenesrequest (NS id, PNFD _ id, PNForVNF _ priority _ flag ═ PNF), where instantatenesrequest represents an instantiated NS request, NS id represents an identity of the NS that needs to be instantiated, PNFD _ id represents a PNFD identity, and PNForVNF _ priority _ flag ═ PNF represents a network node deployment using PNF.

And 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 by using the PNF, the PNF node instantiation identification information is obtained after the NS instantiation is completed.

Alternatively, in a fifth Generation mobile communication technology (5th-Generation, abbreviated as 5G) network scenario, NS initial instantiation may also be performed by a network slice.

Step S203, the NFVO sends a response message of the instantiation indication message to the OSS.

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

It is to be understood that, by adding PNForVNF _ priority _ flag to the instantiation indication message, whether the PNF deployment or the VNF deployment is performed on the network node can be indicated by the message.

In the embodiment of the present invention, after the NS initial instantiation process is performed, when the PNF fails, the PNF migration may be automatically performed using the steps of step S204 to step S208.

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

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

Specifically, when the PNF fails, the PNF reports a PNF failure message to the OSS System through an Element Management System (EMS).

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

The migration triggering message is used for triggering the NFVO to migrate the function of the PNF node to the NFV, and the migration triggering message includes a physical network function descriptor PNFD identifier and a PNF node instantiation identifier corresponding to the PNF node, the NSD has a virtual network resource description replacing the PNF, the NSD is used for identifying a network service description of a network service NS where the PNF node is located, the NSD is used for identifying a 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 a nested virtual network service description nestdnsd.

In the embodiment of the invention, the design of the NSD is finished before the function migration of the PNF node. And adding a virtual network resource description for replacing the PNF in the NSD, so that automatic migration can be realized when the PNF migration is required.

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

The PNF node instantiation identifier is used for identifying 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 number of the instantiation identifiers of the PNF nodes can be one or more.

Optionally, when the PNF fails, in a scenario where the OSS actively initiates PNF migration, the migration triggering message may be a message that the PNF performs PNF migration by reporting failure information to the OSS system through the EMS by the PNF, and then the OSS system sends a request to the NFVO. That is, at this time, the PNF migration identifier carried in the migration triggering message is used to trigger the NFVO to perform PNF migration. Specifically, the migration triggering message is an update NS request message (UpdateNsRequest) and carries a PNF to VNF migration (PNF _ Migrate _ to _ VNF) identifier.

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

Optionally, the migration triggering message may also be other newly added interface message types for implementing the above functions. For example, a pnfmigratevnfrequest message.

Specifically, in an embodiment of the present invention, the specific form of the migration triggering message may be: UpdateNsRequest (NS id, PNF _ Migratete _ to _ VNF, Be _ Migrated _ PNFD id, PNF ins id), wherein UpdateNsRequest represents an update NS request, PNF _ Migratete _ to _ VNF represents a migration of PNF to VNF, Be _ Migrated _ PNFD id represents a PNFD identification of the PNF to Be Migrated, and PNF ins id represents a PNF node instantiation identification.

Specifically, in another embodiment of the present invention, the migration trigger message may also be a new interface message, and the form of the migration trigger message may be: pnfmigratevnfrequest (NS id, Be _ classified _ PNFD id, PNFins id). Wherein pnfmigratevnfrequest represents a request for PNF migration to VNF.

Step S206, the NFVO performs a validity check of the PNF migration.

Specifically, at this time, the NFVO determines whether there is PNFD or nestedNSD in the NSD template instead of the PNF 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 validity check of the PNF migration is passed, so step S207 is executed to perform the PNF migration. Otherwise, it is not executed.

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

The virtual network resource refers to a virtual resource in the VNF system for replacing the PNF function, so that the PNF function can be migrated to the VNF system based on the virtual resource.

Specifically, the NFVO deletes the connection resource and associated configuration with the failed PNF according to the PNF instantiation identifier, and instantiates a new VNF or nestedNS.

After step S208 and PNF instantiation is completed, NFVO sends a migration success notification message to OSS. And the OSS receives a 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, an identification of the virtual network resource description, and an identification of the virtual network resource.

The identifier described by the virtual network resource and the identifier of the virtual network resource are used for indicating the NFV resource occupied by the PNF after the PNF function is migrated to the VNF.

Alternatively, if the virtual network resource replacing the PNF is an instantiated NVF, the identifier of the virtual network resource description 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).

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

Optionally, the migration success notification message may further 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 of the PNF replacement function and the identifier of the virtual network resource in the message returned by the VNFD to the OSS, the OSS can more directly know the virtualized resource of the PNF replacement function.

Specifically, the migration success notification message may be an update Ns response message UpdateNsResponse message, and 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 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 ID information of the new instantiated VNF; or if the legacy NSD is used instead of the original PNF, the migration success notification message also carries the legacy NS ID information instead of the PNF and the instantiated legacy NS ID information.

Specifically, in an embodiment of the present invention, the form of the migration success notification message is specifically: UpdateNsRequest (PNF _ Migrate _ to _ VNF _ success, Be _ Migrated _ PNFD id, VNFD id of place PNF, VNF ins id of place PNF). The UpdateNsRequest represents an update Ns request message, PNF _ Migrate _ to _ VNF _ success is a PNF migration success identifier, Be _ Migrated _ PNFD id is a PNFD identifier of a PNF to Be Migrated, VNFD id of place PNF is a VNFD of a replacement PNF, and VNF ins id of place PNF is a VNF identifier of a replacement PNF.

Specifically, in another embodiment of the present invention, the migration success notification message may also be a newly added interface message, and the specific form of the migration success notification message is as follows: PNFMIGRATETO VNFRESPENse (success, Be _ Migrated _ PNFD id, VNFD id of place PNF, and VNF ins id of place PNF), wherein PNFMIGRATETO VNFRESPENse represents a PNF migration response message to a VNF, success represents migration success identification, Be _ Migrated _ PNFD id is used for representing PNFD identification of the Migrated PNF, VNFD id of place PNF is VNFD of a replacement PNF, and VNF ins id of place PNF is VNF identification of the replacement PNF.

After receiving the message, the OSS records that the current PNF node uses the virtualization node, and stores the related information transferred by the interface.

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

Optionally, in an embodiment of the present invention, in a scenario where the OSS actively requests to perform cloud migration, the migration triggering message may also be a new interface message, where a specific message form is: pnfmigratevnfrequest (NS id, Be _ migratedpnfd id, PNF ins id), where pnfmigratevnfrequest represents a PNF migration request to a VNF, NS id represents an identification of an initially instantiated NS, Be _ migratedpnfd id represents a PNFD identification of a PNF to Be Migrated, and PNF ins id represents a PNF node instantiation identification. The migration success notification message may also be a newly added interface message, and the specific form of the migration success notification message is as follows: PNFMistrateVNFREesponse (success, Be _ Migrated _ PNFD id, VNFD id of place PNF, and VNF ins id of place PNF), wherein the PNFMistrateVNFREesponse represents that VNFD id of place PNF is the VNFD of the replacement PNF, and VNF ins id of place PNF is the VNF identification of the replacement PNF.

As can be seen from the above, in the physical network function PNF migration method provided in the embodiment of the present invention, the VNFD or the nestedNSD that replaces the PNF is designed in the NSD in advance, so that when a PNF fails or an operator needs to migrate the PNF function cloud, the NFVO can quickly migrate the PNF function to the VNF system based on the VNFD or the nestedNSD, thereby shortening the time for migrating the PNF to the VNF.

In the embodiment of the present invention, after the PNF failure is recovered, the PNF can be automatically migrated back by using the steps from step S209 to step S212.

And step S209, after the PNF fault repair is completed, the OSS sends a back migration message to the NFVO. And the NFVO receives a rollback message sent by the OSS.

Wherein the migration message is used for instructing the NFVO to migrate the PNF function from the NFV to the PNF, and the migration message includes the PNFD identifier and the PNF node instantiation identifier.

Optionally, in an embodiment of the present invention, in a scenario where the NFVO actively initiates the PNF, the migration message may be a request message that the OSS system actively requests the NFVO to perform PNF migration after completing the PNF fault repair, that is, the migration message may carry a PNF migration identifier to trigger the NFVO to perform PNF migration. Specifically, the migration back message may be an update Ns request (UpdateNsRequest) message.

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

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

Optionally, in an embodiment of the present invention, when the NFVO sends a status sending indication message to the OSS requesting subscription to the PNF status, the relocation message further includes information that the PNF fault is successfully repaired, that is, after the PNF fault is successfully repaired, the OSS sends the PNF status information to the NFVO, and then the NFVO can execute the PNF relocation process under the trigger of the relocation message.

It can be understood that the PNF fault repair message is carried in the rollback message to trigger the NFVO to perform PNF rollback. By the method, the NFVO can timely acquire the state of the PNF, timely initiate PNF migration or migration, and improve PNF migration or migration efficiency.

Optionally, in an embodiment of the present invention, the rollback message may carry a VNF to PNF migration (VNF _ Migrate _ to _ PNF) identifier, which is used to indicate that the PNF function is migrated from the VNF to the PNF, and the rollback message simultaneously carries the PNFD identifier and the PNF node instantiation identifier to be migrated. The PNFD ID and PNF instantiation identification are used to inform the NFVO which PNF function to migrate back to the PNF. The number of the instantiation identifiers of the PNF nodes can be one or more.

Specifically, in an embodiment of the present invention, the specific form of the migration back message may be: UpdateNsRequest (NS id, VNF _ Migrate _ to _ PNF, PNFD id, PNF ins id), wherein UpdateNsRequest is an update Ns request message, NS id represents instantiated NS, VNF _ Migrate _ to _ PNF represents a migration identifier of VNF to PNF, PNFD id is a PNFD identifier, and PNF ins id is a instantiation identifier of PFN node.

Specifically, in another embodiment of the present invention, the migration message may also be a new interface message, and the specific form may be: vnfmigitatepnfrequest (NS id, PNFD id, PNF ins id), where vnfmigitatepnfrequest is a message requesting a PNF to migrate back from a VNF, NS id is used to identify the NS where the PNF node is located, PNFD id is used to identify the PNFD of the migrated PNF, and PNF ins id represents an instantiation identifier of the migrated PNF.

Step S210, the NFVO performs a validity check of PNF migration.

Specifically, in an embodiment of the present invention, the NFVO determines whether the PNFD information and the VNFD or nested NSD information replacing the PNF exist in the NSD, and when the NFVO determines that the PNFD information and the VNFD or nested NSD information replacing the PNF exist in the NSD, the NFVO determines that the PNF migration validity passes.

Specifically, in one embodiment of the invention, the NFVO also determines whether the current state of the PNF is using VNF or nested NSD. When the NFVO determines that the current state of the PNF uses VNF or nested NSD, the NFVO determines that the PNF migration validity passes.

Specifically, in another embodiment of the present invention, the NFVO determines whether the NSD has information of the PNFD and information of VNFD or nested NSD instead of the PNF, and whether the current state of the PNF uses VNF or nested NSD. When the NFVO determines that the NSD has the information of the PNFD and the VNFD or the nested NSD information replacing the PNF, and the current state of the PNF uses the VNF or the nested NSD, the NFVO determines that the PNF migration validity passes.

Alternatively, if the validity check of PNF migration by the NFVO passes, step S603 is executed, and the NFVO executes a flow of PNF migration.

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

Step S211, the NFVO deletes the virtual network resource configuration used in place of the PNF and instantiates a connection of the PNF.

Specifically, the NFVO determines the VNF of the PNF replacement function according to the PNFD ID and the PNF instantiation ID in the rollback message, and then deletes the relevant connection and configuration of the VNF of the PNF replacement function.

At this point, NFVO migrates PNF functions from the virtual network resource back into the PNF.

And step S212, after the replacement is successful, the NFVO sends a message of successful migration notification to the OSS.

Wherein, the migration success notification message is used to notify the OSS that the PNF function is successfully migrated from the NFV back to the PNF.

the PNFD identification, and the PNF instantiation identification.

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

It can be understood that after the migration is successful, the message returned to the OSS by the NFVO carries one or more of the PNFD identifier and the PNFD instantiation identifier, so that the OSS can more directly acquire the PNF migrated from the VNF.

Specifically, the migration success notification message carries a VNF to PNF migration success identifier (VNF _ create _ to _ PNF _ success), a repaired PNFD identifier and a PNF node instantiation identifier, and is used to notify the OSS, the PNF node function migration function, and a specific migrated PNF node.

Specifically, in an embodiment of the present invention, the migration success notification message is in the specific form: UpdateNsRequest (VNF _ Migrate _ to _ PNF _ success, PNFD id, PNF ins id), wherein UpdateNsRequest is a request message for updating Ns, VNF _ Migrate _ to _ PNF _ success is an identifier of successful migration from the VNF to the PNF, PNFD id is a PNFD identifier corresponding to the migrated PNF, and PNF ins id is an identifier of instantiated PNF nodes of migration.

Specifically, in another embodiment of the present invention, the migration success notification message may also be a new interface addition message, and the specific form is as follows: vnfmigitetopnfresh (success, PNFD id, PNF ins id), where vnfmigitetopnfresh is a message in which the VNF returns to the PNF, success is used to identify that the VNF returns to the PNF, and PNF ins id represents an identifier of PNF instantiation of the returned PNF.

Through the steps of S209-S212, the PNF function can be automatically migrated. It should be noted that the migration process may also be applied to non-PNF failures, and when the OSS actively requests to perform cloud migration, the migration message sent by the OSS to the NFVO will not include PNF failure repair information.

It should be noted that the embodiment of the present invention may also be applied to a 5th-Generation (5G) network, in which case the OSS system may be a network slice manager.

Referring to fig. 3, fig. 3 is a flowchart illustrating another physical network function PNF migration method according to an embodiment of the present invention. The embodiment shown in fig. 3 is used in a scenario where the NFVO subscribes to the PNF state, and after the NFVO receives a fault message of the PNF, the NFVO actively initiates PNF migration. Among the methods shown in fig. 2, the same or similar contents to those shown in fig. 2 may refer to the above detailed description, and are not repeated here.

In the step flow shown in fig. 3, step S301 to step S305 show the flow of NS initial instantiation, step S306 to step S311 show the flow of PNF migration, and step S2312 to step S316 show the flow of PNF migration back. The details are as follows:

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

Optionally, in an embodiment of the present invention, in a scenario where the NFVO actively initiates PNF migration and migration, when a PNF fails, the instantiation indication message may further include whether the PNF fails to use a VNF replacement identifier, and whether the PNF fails to be repaired and then migrates the identifier. The OSS sends the two identifications to the NFVO during initialization so as to indicate whether PNF migration or migration is performed or not when the subsequent NFVO actively initiates PNF migration or migration.

Optionally, in an embodiment of the present invention, when the instantiation indication message includes whether the PNF failure can use the VNF replacement identifier, the PNF function is migrated to the VNF when the PNF failure occurs, only if whether the PNF failure can use the VNF replacement identifier is affirmative, and otherwise, the PNF function is not migrated.

Optionally, in an embodiment of the present invention, when the instantiation indication message includes a whether or not to migrate back after PNF failover flag, the PNF function is migrated back from the VNF to the PNF after PNF failover only if the whether or not to migrate back after PNF failover flag is positive, otherwise, the PNF function is not migrated back.

Specifically, in an embodiment of the present invention, in the OSS creating a Network Service request, the instantiation indication message may be an implementable Ns request message (instantaneensequest) message, and the instantaneensequest message is added with a PNFD identifier, whether a PNF fault uses a VNF replacement identifier, and whether a migrant identifier after PNF fault repair.

Specifically, in one embodiment of the present invention, the instantiation indication message has a message form of: instantetrenquest (NS id, PNFD _ id, PNForVNF _ priority _ flag PNF, PNF-fail-value _ to _ VNF _ flag, PNF-Restore-Back-flag).

The instantanesrequest is an instantiation Ns request message, and the PNF-fail-terminate _ to _ VNF _ flag, that is, whether the PNF fault can be replaced by a VNF replacement identifier, is used to identify whether the PNF fault can be replaced by a VNF, if the identifier is Yes, it indicates that the PNF fault can be replaced by a VNF, and if the identifier is NO, it indicates that the PNF fault cannot be replaced by a VNF.

The PNF-Restore-Back-flag is also called a relocation flag or not after PNF fault repair, and is used for marking whether to carry out relocation marking or not after PNF fault repair, or the flag is Yes, indicating that relocation is needed after PNF fault repair, and if the flag is No, indicating that relocation is not needed after PNF fault repair. And after receiving the instantiation indication message, the NFVO records the 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 uses the PNF for deployment, the PNF node instantiation identification information, that is, the PNF ID, is obtained after the NS instantiation is completed.

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

Step S303, the NFVO sends a response message of the instantiation indication 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. And the OSS receives the state transmission indication message transmitted by the NFVO.

The status sending indication message includes an instantiation identifier of the PNF node, and is used to indicate that the OSS sends the current status of the PNF to the NFVO when the current status of the PNF changes.

Optionally, the status sending indication message may further include a PNF status identifier for identifying status information subscribed to the PNF.

Specifically, the status transmission indication message may be a subscription (subscribe) message, and the PNF instantiation identifier and the PNF status identifier are included in the subscribe message.

In particular, the status transmission indication message may also be of other interface message types. For implementing the corresponding functions.

Optionally, in an embodiment of the present invention, when whether the PNF failure can be identified using VNF replacement 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 triggered migration message further includes the PNF fault, that is, when the PNF fault occurs, the OSS sends status information of the PNF to the NFVO, and then the NFVO can execute a PNF migration procedure under the trigger of the triggered migration message.

It can be understood that, in order to enable the NFVO to timely acquire the state information of the PNF, the NFVO may send a state subscription message to the OSS, so that when the state of the PNF changes, the OSS sends the state information of the PNF to the NFVO in time, and thus the NFVO triggers the NFVO to perform PNF migration when the state information of the PNF is acquired as a PNF fault. That is, the PNF fault message is carried in the migration triggering message, and is used for triggering the NFVO to perform PNF migration. By the method, the NFVO can timely acquire the state of the PNF, timely initiate PNF migration or migration, and improve PNF migration or migration efficiency.

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

Optionally, the status sending indication message may further include a PNF start migration flag, which is used by the NFVO to notify the OSS that PNF migration is to be started.

Specifically, in an embodiment of the present invention, the message format of the status transmission indication message is: the PNF State identifier is a PNF State identifier, and the PNF _ program _ to _ VNF is used to indicate that PNF migration is about to start.

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

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

Through the above process, the NS initial instantiation process can be realized, and the subscription of the NFVO to the PNF state information can be realized, so that the NFVO can timely receive the PNF state information and timely respond after the PNF fault or the PNF fault is recovered.

In the embodiment of the present invention, after the NS initial instantiation process is completed, when the PNF fails, the PNF may be automatically migrated using steps S306 to S311.

Step S306, the PNF has a fault, and the fault information is reported to the OSS. The OSS thus receives a PNF failure message.

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

Optionally, in an embodiment of the present invention, in a scenario that the NFVO performs PNF status subscription, and if the PNF fails and the NFVO actively initiates migration, after the OSS system receives a PNF failure message, the OSS system sends the failure information to the NFVO, and at this time, the migration triggering message includes the PNF failure message. Then, after the NFVO learns the PNF fault, PNF migration is actively performed, that is, the PNF fault message is considered to be carried in the migration triggering message to trigger the NFVO to perform PNF migration. Specifically, at this time, the migration triggering message may be a Publish (Publish) message. The Publish message includes information of PNF failure.

In the embodiment of the present invention, in the NS initial instantiation process, the NFVO initiates a PNF state subscription process to the OSS, so after a PNF failure, the OSS sends a migration triggering message to the NFVO.

In the embodiment of the present invention, the migration triggering message includes a PNFD ID, a PNF instantiation ID, and PNF status information, where the PNF status information is a PNF failure.

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

Specifically, the migration triggering message is a Publish (Publish) message, and the message has a specific form: push (PNFDid, PNF in id, PNF _ State ═ fault, cause ═ XXX), where PNFD id is used to indicate PNFD identification of the PNF to be migrated, PNF in id is used to indicate PNF node instantiation identification, PNF _ State ═ fault indicates PNF fault, and cause ═ XXX indicates fault type of the PNF.

Step S308, the NFVO performs a validity check of the PNF migration.

In the embodiment of the present invention, since the migration triggering message carries information that the PNF has failed, and specifically which PNF has failed, the NFVO may execute PNF migration under the trigger of the migration triggering message.

Specifically, in one embodiment of the present invention, NFVO determines whether there is VNFD or nestedND replacing PNF in NSD, and when NFVO determines that there is VNFD or nestedND replacing PNF in NSD, NFVO determines that the validity check of PNF migration passes.

Specifically, in another embodiment of the present invention, since it is a migration request initiated by the NFVO on its own initiative, when it is included in the instantiation indication message sent by the OSS whether a PNF failure can be identified as positive using VNF replacement, the NFVO determines that the validity check of PNF migration passes.

Specifically, in another embodiment of the present invention, when the NFVO determines that there is VNFD or nestedND in the NSD to replace the PNF, and the instantiation indication message sent by the OSS includes whether the PNF failure is identifiable as positive using VNF replacement, the NFVO determines that the validity check of the PNF migration passes.

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

Optionally, when the NFVO determines that the PNF migration validity check fails, the trigger request for triggering the migration message is ignored.

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, 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 further include a PNF migration start identifier, which is used by the NFVO to notify the OSS that PNF migration is to be started.

Specifically, the migration notification message may be a notification (Notify) message, and the message format may be: the notification (PNFD id, PNF ins id, Begin _ PNF _ Migrate _ to _ VNF), where PNFD id is PNFD of the PNF to be migrated, PNF ins id is an instantiation identifier of the PNF to be migrated, and Begin _ PNF _ Migrate _ to _ VNF is a migration start identifier of the PNF to start migration of the PNF to the VNF.

It can be understood that, in this scenario, after the NFVO determines to perform PNF migration, the OSS is notified, so that the OSS can timely know the condition that PNF is about to migrate, and adjust a corresponding function according to the condition.

Step S310, the NFVO deletes the connection resources and associated configuration with the failed PNF and instantiates a new VNF or nestedNS.

Further, the NFVO configures the corresponding network connections and configurations of the VNF or nestedNS node of the new replacement PNF.

Step S311, after the PNF instantiation is completed, the NFVO sends a migration success notification message to the OSS. And the OSS receives a 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 further includes indication information that the PNF migration is successful.

Specifically, the migration success notification message may be a notification (Notify) message, and the message form may be: the notification (PNFD id, PNF ins id, PNF _ Migrate _ to _ VNF _ success), where PNF _ Migrate _ to _ VNF _ success is used to indicate that the PNF is migrated to the VNF successfully.

Through the steps of the above steps S306 to S311, when the PNF fails, the PNF can be automatically and rapidly migrated. And because 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 an embodiment of the present invention, after the PNF failure is recovered, the automatic migration of the PNF using steps S312-S316 may be used.

Step S312, after the PNF fault repair is completed, the OSS sends a back migration message to the NFVO.

In the embodiment of the invention, the migration message comprises a PNFD identifier, a PNF node instantiation identifier and a PNF restoration success identifier.

Optionally, in an embodiment of the present invention, in a scenario where the NFVO subscribes to a PNF fault message and the NFVO actively initiates PNF migration, the migration message may also be that after PNF fault repair is completed, the OSS system sends information that the fault repair is successful to the NFVO, at this time, the triggered migration message includes the PNF fault repair success information, and then the NFVO learns that the PNF fault repair is successful, and actively performs PNF migration, that is, the OSS is considered to carry the PNF fault repair success message in the migration message to trigger the NFVO to perform PNF migration. Specifically, at this time, the rollback message may be a Publish (Publish) message. The Publish message includes information of PNF failure recovery.

Specifically, the rollback message is a Publish (Publish) message, and the message form may be: push (PNFD id, PNF ins id, PNF _ State ═ Normal), where PNFD id indicates PNFD of PNF needing to be migrated back, PNF ins id indicates PNF node instantiation identification needing to be migrated back, and PNF _ State ═ Normal indicates PNF failover success.

Step S313, the NFVO determines the validity of the transition.

Optionally, the NFVO determines whether the PNFD information and the VNFD or nested NSD information replace the PNF exist in the NSD. When the information of the PNFD and the VNFD or the nested NSD information replacing the PNF exist in the NSD, the NFVO determines that the PNF is returned legally and passes.

And, optionally, the NFVO also determines whether the current state of the PNF is using VNF or a nested NSD. When the current state of the PNF is using VNF or nested NSD, NFVO determines the validity pass of PNF migration.

Optionally, in this scenario, when the OSS includes the identity of whether to migrate after PNF failover in the instantiation indication message, the NFVO further determines whether the identity of whether to migrate after PNF failover indicates that the PNF can migrate after PNF failover, and when the identity of whether to migrate after PNF failover indicates that the PNF can migrate, the NFVO determines that the validity of PNF migration passes.

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

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

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

Specifically, the migration notification message may be a notification (notification) message, and the message form may be: the notification (PNFD id, PNF ins id, Begin _ VNF _ Migrate _ to _ PNF), where PNFD id is PNFD of the PNF to be migrated, PNF ins id is PNF node instantiation identifier to be migrated, and Begin _ PNF _ Migrate _ to _ VNF is PNF start migration identifier to indicate that the migration of the VNF to the PNF is to be started.

It can be understood that, in this scenario, after the NFVO determines that the PNF is migrated back, the OSS is notified, so that the OSS can timely know that the PNF is about to migrate back, and adjust a corresponding function according to the situation.

Step S315, the NFVO instantiates network connections and configurations to the PNF while deleting the relevant connections and configurations of the VNF that replaces the PNF function.

And step S316, after the replacement is successful, the NFVO sends a message of successful migration back notification to the OSS.

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

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

Specifically, the migration success notification message may be a notification (Notify) message, and the message form may be: the notification (PNFD id, PNF ins id, Begin _ VNF _ create _ to _ PNF _ success), where PNFDid is PNFD of PNF that has succeeded in the migration, PNF ins id is PNF node instantiation identifier that has succeeded in the migration, and Begin _ VNF _ create _ to _ PNF _ success indicates that VNF has succeeded in the migration to PNF.

Through the migration flow, the PNF can be automatically and rapidly migrated when the PNF is subjected to fault repair. And because the NFVO subscribes to the PNF state information, the NFVO can timely migrate the PNF after the PNF fault is repaired, and the PNF migration efficiency is improved.

It should be noted that the embodiment of the present invention may also be applied to a 5G network, and in this case, the OSS system may be a network slice manager.

Referring to fig. 4, fig. 4 is a block diagram of functional units of a network function virtualization orchestrator NFVO400 according to an embodiment of the present invention, where the NFVO400 includes a receiving module 410 and an instantiating module 420. Wherein:

a receiving module 410, configured to receive a migration triggering message sent by an OSS (network management system), configured to trigger the NFVO to migrate a function of a PNF node to an NFV system, where the migration triggering message includes a PNFD identifier and a PNF node instantiation identifier corresponding to the PNF node, a virtual network resource description that replaces the PNF is provided in an NSD, the NSD is configured to identify a network service description of a network service NS where the PNF node is located, and the virtual network resource description is a virtual network function descriptor VNFD or a nested virtual network service description nestdnsd.

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

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, where the instantiation indication message includes a PNFD identifier, and is used to indicate that NS instantiation is performed on a PNF node corresponding to the PNFD identifier, so as to obtain a PNF node instantiation identifier in the triggered migration message.

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

the NFVO also includes a deletion module 430 for deleting the virtual network resource configuration that replaces the PNF use and instantiating a connection for the PNF.

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

a sending module 440, configured to send a status sending indication message to the OSS, where the status sending indication message includes the PNF node instantiation identifier, and the status sending indication message is used to indicate that the OSS sends the current status of the PNF to the NFVO when the current status of the PNF changes.

Optionally, in an embodiment of the present invention, the migration triggering message further includes the PNF failure, the sending module 440 is further configured to send a migration notification message to the OSS, where 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 the PNFD identifier and the PNF node instantiation identifier.

Optionally, in an embodiment of the present invention, the migration back message further includes that the PNF failover is successful, the sending module 440 is further configured to send a migration back notification message to the OSS, where the migration back notification message is used to notify the OSS, the NFVO migrates the PNF function from the NFV back to the PNF, and the migration back notification message includes the PNFD identifier and the PNF node instantiation identifier.

Optionally, in an embodiment of the present invention, the instantiation indication message further includes a network node deployment identifier or whether the PNF failure uses the VNF replacement identifier, and the instantiation module 420 is specifically configured to:

instantiating a virtual network resource of a PNF based on the PNFD identifier, the PNF node instantiation identifier, and the virtual network resource description when the network node deployment identifier indicates that a network node uses PNF deployment in the NS; or,

instantiating a virtual network resource of the PNF based on the PNFD identification, the PNF node instantiation identification, and the virtual network resource description when the PNF failure uses a VNF replacement identification to indicate that the NFVO uses the VNF to replace when the PNF failure occurs.

Optionally, in an embodiment of the present invention, the instantiation indication message further includes a flag indicating whether to migrate after PNF failover, and the deleting module 430 is specifically configured to delete the virtual network resource configuration used for replacing the PNF and instantiate the connection of the PNF when the flag indicating whether to migrate after PNF failover indicates that the PNF performs PNF migration.

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

It should be noted that the virtual network function processing apparatus described in the embodiment of the present invention is presented in the form of a functional unit. The term "unit" as used herein is to be understood in its broadest possible sense, and objects used to implement the functions described by the respective "unit" may be, for example, an integrated circuit ASIC, a single circuit, a processor (shared, dedicated, or chipset) and memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality.

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

Referring to fig. 5, fig. 5 is a schematic structural diagram of another NFVO according to 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, where the processor 501, the memory 502, the receiver 503, and the transmitter 504 are connected by the bus 504 and complete communication therebetween.

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

receiving, by the receiver 503, a migration triggering message sent by an OSS (network management system) and used to trigger the NFVO to migrate a function of a PNF node to an NFV system, where the migration triggering message includes a PNFD identifier and a PNF node instantiation identifier corresponding to the PNF node, a virtual network resource description replacing the PNF is provided in an NSD, the NSD is used to identify a network service description of a network service NS where the PNF node is located, and the virtual network resource description is a virtual network function descriptor VNFD or a nested virtual network service description nestdnsd;

after the NFV system deletes the PNF resource configuration in the NFV, instantiating a virtual network resource of the PNF based on the PNFD identifier, the PNF node instantiation identifier and the virtual network resource description, wherein 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, 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:

receiving, by the receiver 503, an instantiation indication message sent by the OSS, where the instantiation indication message includes a PNFD identifier, and is used to indicate that NS instantiation is performed on a PNF node corresponding to the PNFD identifier, so as to obtain a PNF node instantiation identifier in the triggered migration 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:

receiving, by the transmitter 504, a migration back message sent by the OSS, the migration back message being used to instruct the NFVO to migrate the function of the PNF node from the NFV to the PNF, the migration back message including the PNFD identifier and the PNF node instantiation identifier;

deleting the virtual network resource configuration used in place of the PNF and instantiating the connections of the PNF.

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

sending, by the sender 504, a status sending indication message to the OSS, where the status sending indication message includes the PNF node instantiation identifier, and the status sending indication message is used to indicate that the OSS sends the current status of the PNF to the NFVO when the current status of the PNF changes.

Optionally, in an embodiment of the present invention, before the PNF failure is included in the migration triggering message, and before the PNFD identifier, the PNF node instantiation identifier, and the virtual network resource description instantiate a virtual network resource of the PNF, the processor 501 is further configured to:

sending, by the sender 504, a migration notification message to the OSS, the migration notification message being used to notify the OSS that the NFVO migrates the PNF function to the NFV, the migration notification message including the PNFD identifier and the PNF node instantiation identifier.

Optionally, in an embodiment of the present invention, the migration back message further includes that the PNF is successfully repaired, and before the NFVO deletes the configuration of the virtual network resource used by the PNF and instantiates the PNF, the processor 501 is further configured to:

sending, by the sender 504, a migration-back notification message to the OSS, the migration-back notification message being used to notify the OSS that the NFVO migrates the PNF function from the NFV back to the PNF, the migration-back notification message including the PNFD identifier and the PNF node instantiation identifier.

Optionally, in an embodiment of the present invention, the instantiation indication message further includes a network node deployment identifier or a PNF failure identifier that uses VNF replacement, and the processor 501 instantiates a virtual network resource of the PNF based on the PNFD identifier, the PNF node instantiation identifier, and the virtual network resource description, specifically:

Optionally, in an embodiment of the present invention, the instantiation indication message further includes an identifier of whether to migrate after PNF failover, and the processor 501 deletes the virtual network resource configuration used by the PNF and instantiates the PNF, specifically:

and when the restoration flag indicates that the PNF performs PNF restoration after the PNF fault is repaired, deleting the virtual network resource configuration used for replacing the PNF and instantiating the connection of the PNF.

It can be seen that in the solution of this embodiment, by designing a VNFD or a nestedNSD in the NSD in advance to replace the PNF, when the PNF fails or an operator needs to cloud-migrate the PNF function, the NFVO100 can quickly migrate the PNF function to the VNF system based on the VNFD or the nestedNSD, and the time for migrating the PNF to the VNF is shortened.

It should be noted that the processor 501 may be a single processor or may be a general term for multiple processing elements. For example, the processor may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits configured to implement embodiments of the present invention, such as: one or more microprocessors (digital signal processors, DSPs), or one or more Field Programmable Gate Arrays (FPGAs).

The memory 502 may be a storage device or a combination of storage elements, and is used for storing executable program codes or parameters, data, etc. required by the operation of the access network management device. And the memory 502 may include a Random Access Memory (RAM) or a non-volatile memory (non-volatile memory), such as a magnetic disk memory, a Flash memory (Flash), and the like.

The bus 505 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. The bus 505 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 5, but this is not intended to represent only one bus or type of bus.

In the foregoing embodiment shown in fig. 4, the functions of each unit may be implemented based on the structure of the NFVO shown in fig. 5. In the foregoing embodiments shown in fig. 2 or fig. 3, the method flows of the steps may be implemented based on the NFVO shown in fig. 5.

Referring to fig. 6, fig. 6 is a functional unit block diagram of an OSS600 according to an embodiment of the present invention, and as shown in the figure, the OSS600 includes a generating module 610 and a sending module 620. Wherein:

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

a sending module 620, configured to send the migration triggering message to the NFVO, where the NSD has a virtual network resource description replacing a PNF, the NSD is configured to identify a network service description of a network service NS where the PNF node is located, and the virtual network resource description is a virtual network function descriptor VNFD or a nested virtual network service description nestdnsd.

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 NS instantiation is performed on a PNF node corresponding to the PNFD identifier, so as to obtain a PNF node instantiation identifier in the triggered migration message.

Optionally, in an embodiment of the present invention, the sending module 620 is further configured to send the 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, and the migration message includes the PNFD identifier and the PNF node instantiation identifier.

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

a receiving module 630, configured to receive a status sending indication message sent by the NFVO, where the status sending indication message includes an instantiation identifier of the PNF node, and the status sending indication message is used to indicate that the OSS sends the current status of the PNF to the NFVO when the current status of the PNF changes.

Optionally, in an embodiment of the present invention, the migration triggering message further includes the PNF failure, the receiving module 630 is further configured to receive a migration notification message sent by the NFVO, where 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 the PNFD identifier and the PNF node instantiation identifier.

Optionally, in an embodiment of the present invention, the migration back message further includes that the PNF failover is successful, the receiving module 620 is further configured to receive a migration back notification message sent by the NFVO, where the migration back notification message is used to notify the OSS, the NFVO migrates the PNF function from the NFV back to the PNF, and the migration back notification message includes the PNFD identifier and the PNF node instantiation identifier.

It can be seen that in the scheme of this embodiment, by designing a VNFD or a nestedNSD in the NSD in advance to replace the PNF, when the PNF fails or an operator needs to cloud-migrate the PNF function, the NFVO can quickly migrate the PNF function to the VNF system based on the VNFD or the nestedNSD, and the time for migrating the PNF to the VNF is shortened.

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

Referring to fig. 7, fig. 7 is a schematic structural diagram of another OSS according to an embodiment of the present invention, and as shown in fig. 7, the OSS700 includes:

a transmitter/receiver 701 and a processor 702. The processor 702 may also be a controller, and is shown in fig. 7 as "controller/processor 702". The transmitter/receiver 701 is used to support information transceiving between the OSS700 and the NFVO in the above embodiments, and to support radio communication between the OSS700 and other devices. The processor 702 performs various functions for communicating with the OSS 700. On 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 traffic data and signaling information sent by the OSS 700. On the downlink, traffic data and signaling messages are processed by the processor 702 and modulated (e.g., by modulating a baseband signal to a high frequency signal) by the transmitter 701 to generate a downlink signal, which is transmitted via the antenna to other devices. It is noted that the above demodulation or modulation functions can also be performed by the processor 702. For example, the processor 702 is further configured to perform corresponding steps in the above-described method embodiments, and/or other processes of the technical solutions described in the embodiments of the present invention.

Further, OSS700 may also include a memory 703, memory 703 being used to store program codes and data for OSS 700. Furthermore, the OSS700 may also include a communication unit 704. The communication unit 704 is used to support the access router to communicate with the terminal. For example, in the LTE system, the communication unit 704 may also be an S1-MME interface, which is used to support the OSS to communicate with a Mobility Management Entity (MME).

It is to be understood that fig. 7 only shows a simplified design of OSS 700. In practice, the OSS700 may comprise any number of transmitters, receivers, processors, controllers, memories, communication units, etc., and all OSS that may implement embodiments of the present invention are within the scope of the embodiments of the present invention.

An embodiment of the present invention further provides a computer storage medium, where the computer storage medium may store a program, and the program includes, when executed, some or all of the steps of the PNF migration method described in the above method embodiment.

It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the invention. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required by the invention.

In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of some interfaces, devices or units, and may be an electric or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and the modifications or the substitutions 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

1. A Physical Network Function (PNF) migration method is applied to a Network Function Virtualization (NFV) system, the NFV system comprises a NFVO, and the method comprises the following steps:

the NFVO receives a migration triggering message sent by an OSS (network management system) and is used for triggering the NFVO to migrate the function of a PNF node to an NFV (network virtual function) system, wherein the migration triggering message comprises a Physical Network Function Descriptor (PNFD) identifier and a PNF node instantiation identifier corresponding to the PNF node, a NSD (network service description) has a virtual network resource description replacing the PNF, the NSD is used for identifying a network service description of a network service NS where the PNF node is located, and the virtual network resource description is a Virtual Network Function Descriptor (VNFD) or a nested virtual network service description (nestNDSD);

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, where the virtual network resource is a virtual network function VNF corresponding to the VNFD or an embedded network service nestdns corresponding to the nestedNS sd.

2. The method of 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:

and the NFVO receives an instantiation indication message sent by the OSS, wherein the instantiation indication message comprises a PNFD identifier and is used for indicating to carry out NS instantiation on a PNF node corresponding to the PNFD identifier so as to obtain a PNF node instantiation identifier in the migration triggering message.

3. The method of 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 migration message sent by the OSS, wherein the migration message is used for indicating the NFVO to migrate the functions of the PNF node from the NFV to the PNF, and the migration message comprises the PNFD identification and the PNF node instantiation identification;

the NFVO deletes the virtual network resource configuration that replaces the PNF use and instantiates the PNF's connection.

4. The method according to any of claims 1 to 3, wherein before the NFVO receives a migration trigger message sent by an OSS, the method further comprises:

and the NFVO sends a status sending indication message to the OSS, wherein the status sending indication message comprises the PNF node instantiation identifier, and the status sending indication message is used for indicating the OSS to send the current status of the PNF to the NFVO when the current status of the PNF changes.

5. The method of claim 4, wherein the migration trigger message further comprises the PNF failure, and wherein before instantiating the PNF virtual network resource based on the PNFD identification, the PNF node instantiation identification, and the virtual network resource description, the method further comprises:

the NFVO sends a migration notification message to the OSS, wherein the migration notification message is used for notifying the OSS, the NFVO migrates the PNF function to the NFV, and the migration notification message comprises the PNFD identification and the PNF node instantiation identification.

6. The method of claim 4, wherein the migration back message further comprises that the PNF failover is successful, and wherein before the NFVO deletes the configuration of virtual network resources used by the PNF and instantiates the PNF, the method further comprises:

the NFVO sends a migration notification message to the OSS, the migration notification message is used for notifying the OSS, the NFVO migrates the PNF function from the NFV to the PNF, and the migration notification message comprises the PNFD identification and the PNF node instantiation identification.

7. The method according to claim 2, wherein the instantiation indication message further includes a network node deployment identifier or a PNF failure identifier using VNF replacement, 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 a network node in the NS deploys by using a PNF, the NFVO instantiates a 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 a VNF replacement identifier to indicate that the NFVO uses the VNF to replace when the PNF failure occurs, the NFVO instantiates a virtual network resource of the PNF based on the PNFD identifier, the PNF node instantiation identifier and the virtual network resource description.

8. The method according to claim 3, wherein the instantiation indication message further includes an identifier of whether to migrate back after PNF failover, and the NFVO deletes the virtual network resource configuration used by the PNF and instantiates the PNF, specifically:

and when the restoration flag indicates that the PNF performs PNF restoration after the PNF fault is repaired, the NFVO deletes the virtual network resource configuration used for replacing the PNF and instantiates the connection of the PNF.

9. A Physical Network Function (PNF) migration method is applied to a Network Function Virtualization (NFV) system, the NFV system comprises a NFVO, and the method comprises the following steps:

under the condition that the function of a PNF node needs to be migrated to the NFV system, generating a migration triggering message by an OSS (network management system) for triggering the NFVO to migrate the function of the PNF node to the NFV system, wherein the migration triggering message comprises a Physical Network Function Descriptor (PNFD) identifier and a PNF node instantiation identifier corresponding to the PNF node;

and the OSS sends the migration triggering message to the NFVO, wherein NSD has a virtual network resource description for replacing PNF, the NSD is used for identifying 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 a nested virtual network service description nestedNSD.

10. The method of claim 9, wherein before the OSS sends a migration trigger message to the NFVO, the method further comprises:

and the OSS sends an instantiation indication message to the NFVO, wherein the instantiation indication message comprises a PNFD identifier and is used for indicating to carry out NS instantiation on the PNF node corresponding to the PNFD identifier so as to obtain a PNF node instantiation identifier in the migration triggering message.

11. The method of claim 10, wherein after the OSS sends a migration trigger message to the NFVO, the method further comprises:

and the OSS sends a migration message to the NFVO, wherein the migration message is used for indicating the NFVO to migrate the functions of the PNF node from the NFV to the PNF, and the migration message comprises the PNFD identification and the PNF node instantiation identification.

12. The method as claimed in claims 9 to 11, wherein before the OSS sends a migration trigger message to the NFVO, the method further comprises:

and the OSS receives a state sending indication message sent by the NFVO, wherein the state sending indication message comprises the PNF node instantiation identifier, and the state sending indication message is used for indicating the OSS to send the current state of the PNF to the NFVO when the current state of the PNF is changed.

13. The method of claim 12, wherein the migration trigger message further comprises the PNF failure, and wherein after the OSS sends a migration trigger message to the NFVO, the method further comprises:

the OSS receives a migration notification message sent by the NFVO, wherein the migration notification message is used for notifying the OSS, the NFVO migrates the PNF function to the NFV, and the migration notification message comprises the PNFD identification and the PNF node instantiation identification.

14. The method as recited in claim 13, wherein the rollback message further comprises a successful repair of the PNF failure, and wherein after the OSS sends a migration triggering message to the NFVO, the method further comprises:

and the OSS receives a migration notification message sent by the NFVO, wherein the migration notification message is used for notifying the OSS, the NFVO migrates the PNF function from the NFV to the PNF, and the migration notification message comprises the PNFD identification and the PNF node instantiation identification.

15. A network function virtualization orchestrator NFVO applied to a network function virtualization NFV system, the NFVO comprising:

a receiving module, configured to receive a migration triggering message sent by an OSS (network management system), configured to trigger the NFVO to migrate a function of a PNF node to an NFV system, where the migration triggering message includes a PNFD identifier and a PNF node instantiation identifier corresponding to the PNF node, a NSD has a virtual network resource description that replaces the PNF, the NSD is configured to identify a network service description of a network service NS where the PNF node is located, and the virtual network resource description is a virtual network function descriptor VNFD or a nested virtual network service description nestdnsd;

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

16. The NFVO of claim 15, wherein the receiving module is further configured to receive an instantiation indication message sent by the OSS, and the instantiation indication message includes a PNFD identifier, and is configured to indicate that NS instantiation is performed on a PNF node corresponding to the PNFD identifier, so as to obtain a PNF node instantiation identifier in the triggered migration message.

17. The NFVO of claim 16,

the receiving module is further configured to receive a migration message sent by the OSS, where the migration message is used to instruct the NFVO to migrate the function of the PNF node from the NFV to the PNF, and the migration message includes the PNFD identifier and the PNF node instantiation identifier;

the NFVO further comprises a deletion module for deleting the virtual network resource configuration used in place of the PNF and instantiating a connection of the PNF.

18. The NFVO of any one of claims 15 to 17, further comprising:

a sending module, configured to send a status sending indication message to the OSS, where the status sending indication message includes the PNF node instantiation identifier, and the status sending indication message is used to indicate that the OSS sends the current status of the PNF to the NFVO when the current status of the PNF changes.

19. The NFVO of claim 18, wherein the migration triggering message further comprises the PNF failure, wherein the sending module is further configured to send a migration notification message to the OSS, wherein the migration notification message is configured to notify the OSS, wherein the NFVO migrates the PNF function to the NFV, and wherein the migration notification message comprises the PNFD identifier and the PNF node instantiation identifier.

20. The NFVO of claim 18, wherein the migration back message further comprises a PNF failover success, wherein the sending module is further configured to send a migration back notification message to the OSS, wherein the migration back notification message is configured to notify the OSS, wherein the NFVO migrates the PNF function from the NFV back to the PNF, and wherein the migration back notification message comprises the PNFD identifier and the PNF node instantiation identifier.

21. The NFVO of claim 15, wherein the instantiation indication message further includes a network node deployment identifier or a PNF failure identifier using VNF replacement, and wherein the instantiation module is specifically configured to:

22. The NFVO of claim 17, wherein the instantiation indication message further includes an identifier of whether to migrate after PNF failover, and the deleting module is specifically configured to delete the virtual network resource configuration used by the PNF to replace and instantiate the connection of the PNF when the identifier of whether to migrate after PNF failover indicates that the PNF performs PNF migration.

23. A network management system, OSS, comprising:

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

a sending module, configured to send the migration triggering message to the NFVO, where an NSD has a virtual network resource description that replaces a PNF, where the NSD is configured to identify a network service description of a network service NS where the PNF node is located, and the virtual network resource description is a virtual network function descriptor VNFD or a nested virtual network service description nestdnsd.

24. The OSS of claim 23, wherein the sending module is further configured to send an instantiation indication message to the NFVO, the instantiation indication message including a PNFD identifier, and configured to indicate that NS instantiation is performed on a PNF node corresponding to the PNFD identifier, so as to obtain a PNF node instantiation identifier in the triggered migration message.

25. The OSS of claim 24, wherein the sending module is further configured to send a migration back message to the NFVO, the migration back message instructing the NFVO to migrate the function of the PNF node from the NFV to the PNF, and wherein the migration back message comprises the PNFD identifier and the PNF node instantiation identifier.

26. The OSS of any one of claims 23 to 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 PNF node instantiation identifier, and the status sending indication message is used to indicate that the OSS sends the current status of the PNF to the NFVO when the current status of the PNF changes.

27. The OSS of claim 26, wherein the migration trigger message further includes the PNF failure, wherein the receiving module is further configured to receive a migration notification message sent by the NFVO, wherein the migration notification message is used to notify the OSS, wherein the NFVO migrates the PNF function to the NFV, and wherein the migration notification message includes the PNFD identifier and the PNF node instantiation identifier.

28. The OSS of claim 27, wherein the migration back message further includes a PNF failover success, wherein the receiving module is further configured to receive a migration back notification message sent by the NFVO, wherein the migration back notification message is used to notify the OSS, wherein the NFVO migrates the PNF function from the NFV back to the PNF, and wherein the migration back notification message includes the PNFD identifier and the PNF node instantiation identifier.

29. A physical network function PNF migration system is characterized in that the system comprises a network function virtualization orchestrator NFVO and a network management system OSS;

the NFVO is the NFVO of any one of claims 15 to 22;

the OSS is according to any one of claims 23 to 28.