WO2018050013A1

WO2018050013A1 - Method and apparatus for managing network function node

Info

Publication number: WO2018050013A1
Application number: PCT/CN2017/100709
Authority: WO
Inventors: 陈丽萍
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-09-13
Filing date: 2017-09-06
Publication date: 2018-03-22
Also published as: CN107819598A

Abstract

A method for managing a network function node, comprising: a first management node receiving a message, sent by a second management node, instructing the addition or deletion of a network function node; the first management node determining the size of a VNF after adding or deleting the network function node; and the first management node sending a request for expanding the VNF or shrinking the VNF to a VNFM according to the size of the VNF after adding or deleting the network function node.

Description

Method and device for managing network function nodes

Technical field

The present application relates to, but is not limited to, the field of network function virtualization, and in particular, to a method and apparatus for managing network function nodes.

Background technique

In the existing network architecture, network functions and network devices are super-coupling relationships, and network functions are implemented through specially designed, vendor-specific devices. This brings a lot of inconvenience: for example, the performance improvement of these devices is limited by the development of hardware that meets specific or customized requirements while maintaining carrier-class reliability; for example, when operators deploy new services. Newly designed devices with associated dedicated functions must be deployed in advance, which will increase the operator's business deployment costs. On the other hand, with the rapid improvement of the performance of the CPU (Central Processing Unit) and the memory, the basic function of running the network function in the form of software on the general-purpose server, Network Function Virtualization (NFV, Network Function Virtualization) Technology has also emerged. Its goal is to run network functions on common hardware devices, thereby reducing capital expenditures (CAPEX, Capital Expenditure) through a wide range of deployments. "Virtualization" enables network functions to be deployed and updated on demand, and greatly facilitates remote management and maintenance, reducing administrative expenses (OPEX, Operating Expense).

In a virtualized environment, the existing network functions will be implemented on the Virtual Network Function (VNF), which can be regarded as the application layer of the VNF. Each VNF can implement different network functions according to the specific application configuration. The virtualization of network functions has caused a great change in the management architecture of existing networks. As shown in Figure 1, Figure 1 shows the architecture and reference points of NFV Management and Orchestration (NFV-MANO, NFV Management and Orchestration). The NFV (Network Functions Virtualization Orchestrator) is responsible for the life cycle management of network services, and the network function virtualization infrastructure (NFVI) of the virtualized infrastructure manager (VIM). Function, VNF Manager (VNFM, VNF Manager) is responsible for the lifecycle management of VNF instances. Each VNF instance assumes an associated VNFM, VIM. Responsible for controlling and managing NFVI computing, storage and network resources.

The traditional network management system adopts a three-layer management structure including network management (NM), network element management (EM), and network elements. The NM is also called a Network Management System (NMS), and the EM is also called an Element Management System (EMS). The NM is generally considered to be part or a part of the Operation Support System (OSS). The interface between the NM or the OSS and the EM is a northbound interface, and the southbound interface between the EM and the network element.

The virtualization of mobile networks means that traditional network elements (network function nodes) will be virtualized. The network functions of traditional network elements are implemented by VNF, but traditional network elements and VNFs are not necessarily one-to-one. A VNF may also implement the functions of multiple network function nodes, as shown in Figure 2. For a traditional network management system, adding a network function node means that a network element device needs to be added correspondingly. When the traditional network element and the VNF are in a one-to-one relationship, correspondingly, a separate VNF is added to the network. However, when a VNF implements multiple network function nodes, the operator needs to increase or decrease a network function node. It is not necessarily to increase or decrease a single VNF. It may only need some VNF components (VNFC, VNF) for the VNF. Component) operates, and the current management system does not have an effective solution to this situation.

Summary of invention

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

The embodiment of the present application provides a method and apparatus for managing a network function node.

An embodiment of the present application provides a method for managing a network function node, where the method includes:

Receiving, by the first management node, a message sent by the second management node indicating that the network function node is added or deleted;

The first management node determines the size of the VNF after adding or deleting the network function node;

The first management node sends a request to extend the VNF or shrink the VNF to the VNFM according to the size of the VNF after adding or deleting the network function node.

The embodiment of the present application further provides an apparatus for managing a network function node, where the apparatus includes:

a receiving unit, configured to receive, by the second management node, a message indicating that the network function node is added or deleted;

a determining unit configured to determine a size of the VNF after adding or deleting a network function node;

The sending unit is configured to send a request for extending the VNF or shrinking the VNF to the VNFM according to the size of the VNF after adding or deleting the network function node.

In addition, the embodiment of the present application further provides a computer readable medium storing a program for managing a network function node, where the program is executed by a processor to implement the steps of the method for managing a network function node.

In the embodiment of the present application, the first management node receives a message sent by the second management node to increase or delete the network function node; the first management node determines the size of the VNF after adding or deleting the network function node; Increase or delete the size of the VNF after the network function node, send a request to extend the VNF or shrink the VNF to the VNFM. In this way, when a VNF can support multiple network function nodes, the addition or deletion of the network function nodes can be effectively managed, so that the operator can flexibly and effectively manage the virtual network from a service perspective.

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

BRIEF abstract

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

2 is a schematic diagram of a VNF implementing one or more network function nodes;

3 is a schematic flowchart of a method for managing a network function node according to an embodiment of the present application;

4 is a schematic flowchart of a method for adding a network function node according to an embodiment of the present application;

FIG. 5 is a schematic flowchart of a method for deleting a network function node according to an embodiment of the present application;

FIG. 6 is a schematic structural diagram of an apparatus for managing a network function node according to an embodiment of the present application.

Detailed

In order to understand the features and technical contents of the embodiments of the present application, the implementation of the embodiments of the present application will be described in detail below with reference to the accompanying drawings. It is used to define embodiments of the present application.

FIG. 3 is a schematic flowchart of a method for managing a network function node according to an embodiment of the present application. As shown in FIG. 3, the method for managing a network function node includes the following steps:

Step 301: The first management node receives a message sent by the second management node indicating that the network function node is added or deleted.

The first management node may be: EM or NFVO;

The second management node may be: NM or OSS.

In this embodiment, the message indicating that the network function node is added may include: a type of the network function node that needs to be added, and an identifier of the VNF that implements the network function node;

The message indicating deletion of the network function node may include: an identifier of the network function node that needs to be deleted.

Step 302: The first management node determines the size of the VNF after adding or deleting the network function node.

In this embodiment, the size of the VNF after the network function node is added may be: the level of the instantiation of the VNF after adding the network function node or the level of expansion or expansion of each expansion or the VNFC to be increased;

The size of the VNF after the network function node is deleted may be: the level of the instantiation or the level of expansion of the VNF after the network function node is deleted or the VNFC that needs to be deleted.

In the above solution, the scaling aspect refers to the dimension that can be scaled by the VNF vendor, and the dimension of one VNF to be scaled may be multiple.

In the first embodiment of the present application, the determining the size of the VNF after adding or deleting the network function node may include:

Determining a correspondence between a network function node and an instantiated level of the VNF, the correspondence being used to indicate a type and a number of network function nodes supported by each instantiation level of the VNF;

And adding, according to the indication, a message of the network function node and the corresponding relationship, determining an instantiated level corresponding to the VNF adding or deleting the network function node.

In the second embodiment of the present application, the determining the size of the VNF after adding or deleting the network function node may include:

Determining a correspondence between each of the network function nodes and the VNF, and the corresponding relationship is used to indicate the type and number of network function nodes supported by the combination of the scaling levels of each of the scaling aspects;

And according to the indication, adding or deleting a message of the network function node and the corresponding relationship, determining a scaling level of each scaling aspect corresponding to the VNF after adding or deleting the network function node.

In the third embodiment of the present application, the determining the size of the VNF after adding or deleting the network function node may include:

Determining a correspondence between the network function node and the VNFC, where the correspondence is used to indicate a VDU (Virtualization Deployment Unit) and a number of the VNFCs of the VNFC required to support the network function node;

And adding, according to the indication, a message of the network function node and the corresponding relationship, determining that the VNF increases or deletes the VNFC that the network function node needs to be added or deleted.

Corresponding relationships in the above three embodiments may be stored in the VNFD (VNF Description, VNF Description) of the VNF.

Step 303: The first management node sends a request for extending the VNF or shrinking the VNF to the VNFM according to the size of the VNF after adding or deleting the network function node.

In this embodiment, the request for sending the extended VNF to the VNF manager VNFM may include: sending a request for adding a VNFC to the VNFM, or extending the request of the VNF to the VNFM;

The request to send the shrink VNF to the VNF manager VNFM may include: sending a request to reduce the VNFC to the VNFM, or requesting the VNFM to extend the VNF or terminate the VNF to the VNFM.

In this embodiment, the request for scaling the VNF may include: a request to scale the VNF to a set instantiation level, or a request to scale to a set scaling level in terms of target scaling.

4 is a schematic flowchart of a method for adding a network function node according to an embodiment of the present application. As shown in FIG. 4, the method for adding a network function node includes the following steps:

Step 401: The EM or NFVO receives a message sent by the NM or OSS indicating that the network function node is added.

Step 402: EM or NFVO determines the size of the VNF after adding the network function node.

Step 403: The EM or NFVO sends an extended VNF request to the VNFM to indicate that the VNFM increases the VNFC.

Step 404: The EM or NFVO receives the extended VNF complete message sent by the VNFM.

Step 405: The EM or NFVO sends a message to the NM or OSS to complete the node for adding the network function.

FIG. 5 is a schematic flowchart of a method for deleting a network function node according to an embodiment of the present disclosure. As shown in FIG. 5, the method for deleting a network function node includes the following steps:

Step 501: The EM or NFVO receives a message sent by the NM or OSS indicating deletion of the network function node.

Step 502: EM or NFVO determines the size of the VNF after deleting the network function node.

Step 503: The EM or NFVO sends a Shrink VNF request to the VNFM to indicate that the VNFM reduces the VNFC or terminates the VNF.

Step 504: The EM or NFVO receives the Shrink VNF Complete message sent by the VNFM.

Step 505: The EM or NFVO sends a message to the NM or OSS to complete the deletion of the network function node.

A method for managing a network function node in the embodiment of the present application is described below in conjunction with an application scenario.

Embodiment 1:

The EM receives a message of creating a management object (CreateMO) sent by the NM or the OSS, indicating that a new network function node is added, including the type, number of network function nodes that need to be added, and the identifier of the VNF that implements the network function node;

The EM determines the size of the VNF after adding the network function node, and may determine, for example, a correspondence relationship between the network function node and the instantiated level of the VNF, where the correspondence indicates a network function node supported by each specific instantiation level of the VNF, The network function node type and the number are included, and the instantiated level corresponding to the VNF adding a new network function node is determined according to the received indication message and the corresponding relationship.

The EM sends a scaled VNF request message (ScaleVnfToLevelRequest) to the VNFM, which carries the instantiated level corresponding to the VNF to add a new network function node.

The EM receives the message sent by the VNFM indicating that the extended VNF is completed or receives the message sent by the VNF indicating that the network function node is added, creates a corresponding management object instance for the newly added network function node, and creates a new network function node and the VNF. Correspondence of VNFC;

The EM sends a notification to create a new management object to the NM or OSS.

Embodiment 2:

The EM receives a message of the scalable VNF (ScaleVnf) sent by the NM or the OSS, indicating that a new network function node is added, including the type, number of network function nodes that need to be added, and the identifier of the VNF that implements the network function node;

The EM determines the size of the VNF after adding the network function node, and may determine, for each thread, the corresponding relationship between the network function node and the VNF, and the corresponding relationship indicates the network function node supported by the combination of the specific scaling level in each of the scaling aspects. The network function node type and the number are included, and the scaling level of each scaling aspect corresponding to the VNF adding a new network function node is determined according to the indication message and the corresponding relationship.

The EM sends a scaling VNF request message (ScaleVnfToLevelRequest) to the VNFM, and carries the scaling level of each scaling aspect corresponding to the VNF to add a new network function node. However, when the newly added network function node only needs to extend a scaling aspect of the VNF, the EM sends a scaling VNF request message (ScaleVnfRequest) to the VNFM, carrying the VNF scaling type Scale out and the number of scaling steps.

The EM sends a notification to create a new management object to the NM or OSS.

Embodiment 3:

The EM determines the size of the VNF after the network function node is added, and may determine the correspondence between the network function node and the VNFC, where the correspondence indicates the VNFC required to support the network function node. The VDU and the number of VNFCs corresponding to the VNFC are included, and the VNFC that the VNF needs to add to the new network function node is determined according to the indication message and the correspondence.

The EM sends a request message indicating that the VNFC is added to the VNFM, and carries the number of VDUs and VNFCs corresponding to the VNFC.

The EM receives the message sent by the VNFM to increase the VNFC completion message or receives the message sent by the VNF to indicate the newly added network function node, creates a corresponding management object instance for the newly added network function node, and creates a new network function node and the VNF. Correspondence of VNFC;

The EM sends a notification to create a new management object to the NM or OSS.

Embodiment 4:

Receiving, by the EM, a message of deleting a management object (DeleteMO) sent by the NM or the OSS, indicating that the network function node is deleted, including the identifier of the network function node that needs to be deleted;

The EM determines the size of the VNF after deleting the network function node, and may determine, for example, a correspondence relationship between the network function node and the instantiated level of the VNF, where the correspondence indicates a network function node supported by each specific instantiation level of the VNF, The network function node type and the number are included, and the instantiated level corresponding to the VNF deleting the network function node is determined according to the received indication message and the corresponding relationship.

The EM sends a scaling VNF request message (ScaleVnfToLevelRequest) to the VNFM, which carries the instantiated level corresponding to the VNF to delete the network function node.

The EM deletes the managed object corresponding to the network function node, and deletes the correspondence between the network function node and the VNF and the VNFC;

The EM sends a delete management object notification to the NM or OSS.

Embodiment 5:

The EM receives the message of the scalable VNF (ScaleVnf) sent by the NM or the OSS, and indicates that the network function node is deleted, including the identifier of the network function node that needs to be deleted;

The EM determines the size of the VNF after deleting the network function node, and may determine, for each thread, a corresponding relationship between the network function node and the VNF, and the corresponding relationship indicates a network function node supported by the specific scaling level of each scaling aspect. Include the network function node type and the number, and determine, according to the indication message and the corresponding relationship, the corresponding extension of the VNF after deleting the network function node The level of expansion and contraction.

The EM sends an extended VNF request message (ScaleVnfToLevelRequest) to the VNFM, and carries the scaling level of each scaling aspect corresponding to the VNF to delete the network function node. However, when the VNF has no other network functions after deleting the network function node, the EM sends a termination VNF request message (TerminateVnfRequest) to the VNFM.

The EM sends a delete management object notification to the NM or OSS.

Example 6:

The EM determines the size of the VNF after deleting the network function node, and may determine the correspondence between the network function node and the VNFC, and determine, according to the indication message and the corresponding relationship, the VNF that the VNF deletes the network function node to delete.

The EM sends a request message to the VNFM indicating that the VNFC is deleted.

The EM sends a delete management object notification to the NM or OSS.

Example 7:

The NFVO receives a message of an Update Network Service (UpdateNsRequest) sent by the NM or the OSS, indicating that a new network function node is added, including the type, number of network function nodes that need to be added, and the identifier of the VNF that implements the network function node;

The NFVO determines the size of the VNF after increasing the network function node, and may determine, for example, a correspondence relationship between the network function node and the instantiated level of the VNF, the correspondence indicating a network function node supported by each specific instantiation level of the VNF, The network function node type and the number are included, and the instantiated level corresponding to the VNF adding the new network function node is determined according to the received indication message and the corresponding relationship.

The NFVO sends a scaled VNF request message (ScaleVnfToLevelRequest) to the VNFM, which carries the instantiated level corresponding to the VNF to add a new network function node.

The NFVO receives the telescopic VNF completion message sent by the VNFM and sends a message to the NM or OSS to update the completion of the network service.

Example 8:

The NFVO receives a message of a scaled network service (ScaleNsRequest) sent by the NM or the OSS, indicating that a new network function node is added, including the type, number of network function nodes that need to be added, and the identifier of the VNF that implements the network function node;

The NFVO determines the size of the VNF after adding the network function node, and may determine, for each node, the corresponding relationship between the network function node and the VNF, and the corresponding relationship indicates the network function node supported by the combination of the specific extension level of each extension. The network function node type and the number are included, and the scaling level of each scaling aspect corresponding to the VNF adding a new network function node is determined according to the indication message and the corresponding relationship.

The NFVO sends a scaling VNF request message (ScaleVnfToLevelRequest) to the VNFM, and carries the scaling level of each scaling aspect corresponding to the VNF to add a new network function node. However, when the newly added network function node only needs to extend a scaling aspect of the VNF, the NFVO sends a scaling VNF request message (ScaleVnfRequest) to the VNFM, carrying the VNF scaling type Scale out and the number of scaling steps.

The NFVO receives the telescopic VNF completion message sent by the VNFM and sends a message to the NM or OSS to complete the extension network service.

Example 9:

The NFVO receives a message of an update network service (UpdateNsRequest) sent by the NM or the OSS, indicating that the network function node is deleted, including the identifier of the network function node that needs to be deleted;

The NFVO determines the size of the VNF after deleting the network function node, and may determine, for example, a correspondence relationship between the network function node and the instantiated level of the VNF, the correspondence indicating a network function node supported by each specific instantiation level of the VNF, The network function node type and the number are included, and the instantiated level corresponding to the VNF deleting the network function node is determined according to the received indication message and the corresponding relationship.

The NFVO sends a scaled VNF request message (ScaleVnfToLevelRequest) to the VNFM, which carries the instantiated level corresponding to the VNF to delete the network function node.

Example 10:

The NFVO receives the message of the scalable VNF (ScaleVnf) sent by the NM or the OSS, and indicates that the network function node is deleted, including the identifier of the network function node that needs to be deleted;

The NFVO determines the size of the VNF after deleting the network function node, and may determine, for each thread, the corresponding relationship between the network function node and the VNF, and the corresponding relationship indicates the network function node supported by the combination of the specific scaling level of each scaling aspect. The network function node type and the number are included, and the scaling level of each scaling aspect corresponding to the VNF deletion network function node is determined according to the indication message and the corresponding relationship.

The NFVO sends an extended VNF request message (ScaleVnfToLevelRequest) to the VNFM, and carries the scaling level of each scaling aspect corresponding to the VNF to delete the network function node. However, when the VNF has no other network functions after deleting the network function node, the NFVO sends a termination VNF request message (TerminateVnfRequest) to the VNFM.

The NFVO receives the telescopic VNF sent by the VNFM or terminates the VNF completion message, and sends a message to the NM or OSS to complete the extension network service.

FIG. 6 is a schematic structural diagram of an apparatus for managing a network function node according to an embodiment of the present application. As shown in FIG. 6, the apparatus includes:

The receiving unit 61 is configured to receive, by the second management node, a message indicating that the network function node is added or deleted;

The determining unit 62 is configured to determine a size of the VNF after adding or deleting the network function node;

The sending unit 63 is configured to send a request for extending the VNF or shrinking the VNF to the VNFM according to the size of the VNF after adding or deleting the network function node.

In this embodiment, the device is applied to the first management node, and the first management node may be: EM or NFVO; and the second management node may be: NM or OSS.

In this embodiment, the message indicating that the network function node is added may include: a type of a network function node, an identifier of a VNF that implements the network function node;

In this embodiment, the sending unit 63 may be further configured to send a request for adding a VNFC to the VNFM, or a request for scaling the VNF to the VNFM; or send a request for reducing the VNFC to the VNFM, or request the VNF to be extended to the VNFM. Or terminate the VNF request to VNFM.

In this embodiment, the determining unit 62 may include: a first determining subunit configured to determine a correspondence relationship between the network function node and the instantiated level of the VNF, where the corresponding relationship is used to indicate each instance of the VNF The type and number of network function nodes supported by the level; the message of the network function node and the corresponding relationship are added or deleted according to the indication, and the instantiated level corresponding to the VNF is added or deleted after the network function node is determined.

In this embodiment, the determining unit 62 may include: a second determining subunit configured to determine a correspondence between each of the network function node and the VNF, wherein the corresponding relationship is used to indicate the scaling of each scaling aspect. Combining the types and the number of network function nodes supported by the level; adding or deleting the message of the network function node and the corresponding relationship according to the indication, determining each expansion aspect corresponding to the VNF after adding or deleting the network function node The level of expansion.

In this embodiment, the determining unit 62 may include: a third determining subunit configured to determine a correspondence between the network function node and the VNFC, where the corresponding relationship is used to indicate a VDU of the VNFC required to support the network function node. And the number of the VNFCs; adding or deleting a message of the network function node according to the indication and the corresponding relationship, determining that the VNF increases or deletes the network function The node corresponds to the VNFC that needs to be added or deleted.

Those skilled in the art should understand that the implementation function of each unit in the apparatus for managing network function nodes shown in FIG. 6 can be understood by referring to the related description of the foregoing method for managing network function nodes. The function of each unit in the device for managing the network function node shown in FIG. 6 can be realized by a program running on the processor, or can be realized by a logic circuit.

Those skilled in the art will appreciate that embodiments of the present application can be provided as a method, system, or computer program product. Accordingly, the application can take the form of a hardware embodiment, a software embodiment, or an embodiment in combination with software and hardware. Moreover, the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.

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

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

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

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

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

Claims

A method of managing network function nodes, comprising:

The first management node receives a message (301, 401, 501) sent by the second management node indicating that the network function node is added or deleted;

Determining, by the first management node, a size (302, 402, 502) of the virtual network function VNF after adding or deleting the network function node;

The first management node sends a request to extend the VNF or shrink the VNF to the VNF manager VNFM (303, 403, 503) according to the size of the VNF after adding or deleting the network function node.
A method of managing a network function node according to claim 1, wherein

The first management node is: a network element management EM or a network function virtualization orchestrator NFVO;

The second management node is: a network management NM or an operation support system OSS.
A method of managing a network function node according to claim 2, wherein

The message indicating that the network function node is added includes: a type of the network function node that needs to be added, and an identifier of the VNF that implements the network function node;

The message indicating that the network function node is deleted includes: an identifier of a network function node that needs to be deleted.
A method of managing a network function node according to claim 2, wherein

The size of the VNF after the network function node is added refers to: the level of the instantiation of the VNF after adding the network function node or the level of expansion of each expansion or the VNF component VNFC that needs to be increased;

The size of the VNF after the network function node is deleted refers to the level of the instantiation or the level of expansion of the VNF after the network function node is deleted or the VNFC that needs to be deleted.
A method of managing a network function node according to claim 4, wherein

The request for sending the extended VNF to the VNFM includes: sending a request to add a VNFC to the VNFM, or a request to extend the VNF to the VNFM;

The sending a request to shrink the VNF to the VNFM includes: sending a request to reduce the VNFC to the VNFM, or requesting the VNFM to extend the VNF or terminate the VNF to the VNFM.
The method of managing a network function node according to claim 5, wherein the request for the scaling VNF comprises: a request to scale the VNF to a set instantiation level, or a request to scale to a set scaling level in terms of target scaling .
The method of managing a network function node according to claim 2, wherein the determining the size of the VNF after adding or deleting the network function node comprises:

Determining a correspondence between a network function node and an instantiated level of the VNF, the correspondence being used to indicate a type and a number of network function nodes supported by each instantiation level of the VNF;

And adding, according to the indication, a message of the network function node and the corresponding relationship, determining an instantiated level corresponding to the VNF adding or deleting the network function node.
The method of managing a network function node according to claim 2, wherein the determining the size of the VNF after adding or deleting the network function node comprises:

Determining a correspondence between each of the network function nodes and the VNF, and the corresponding relationship is used to indicate the type and number of network function nodes supported by the combination of the scaling levels of each of the scaling aspects;

And according to the indication, adding or deleting a message of the network function node and the corresponding relationship, determining a scaling level of each scaling aspect corresponding to the VNF after adding or deleting the network function node.
The method of managing a network function node according to claim 2, wherein the determining the size of the VNF after adding or deleting the network function node comprises:

Determining a correspondence between the network function node and the VNF component VNFC, where the correspondence is used to indicate the number of the virtualized deployment unit VDU and the VNFC of the VNFC required to support the network function node;

And adding, according to the indication, a message of the network function node and the corresponding relationship, determining that the VNF increases or deletes the VNFC that the network function node needs to be added or deleted.
A device for managing network function nodes, comprising:

The receiving unit (61) is configured to receive a message sent by the second management node indicating that the network function node is added or deleted;

a determining unit (62) configured to determine a size of the virtual network function VNF after adding or deleting a network function node;

The sending unit (63) is configured to send a request for extending the VNF or shrinking the VNF to the VNF manager VNFM according to the size of the VNF after adding or deleting the network function node.
The device for managing a network function node according to claim 10, wherein the device is applied to a first management node, the first management node is: a network element management EM or a network function virtualization orchestrator NFVO;

The second management node is: a network management NM or an operation support system OSS.
The apparatus for managing a network function node according to claim 11, wherein

The message indicating that the network function node is added includes: a type of the network function node that needs to be added, and an identifier of the VNF that implements the network function node;

The message indicating that the network function node is deleted includes: an identifier of a network function node that needs to be deleted.
The apparatus for managing a network function node according to claim 11, wherein

The size of the VNF after the network function node is added refers to: the level of the instantiation of the VNF after adding the network function node or the level of expansion of each expansion or the VNF component VNFC that needs to be increased;

The size of the VNF after the network function node is deleted refers to the level of the instantiation or the level of expansion of the VNF after the network function node is deleted or the VNFC that needs to be deleted.
The apparatus for managing a network function node according to claim 13, wherein the sending unit (63) is further configured to send a request for adding a VNFC to the VNFM, or a request for scaling the VNF to the VNFM; or send an indication to reduce the VNFC. Request to VNFM, or request to extend VNF to VNFM or terminate VNF to VNFM.
The apparatus for managing a network function node according to claim 14, wherein the request for the scaling VNF comprises: a request to scale the VNF to a set instantiation level, or a request to scale to a set scaling level in terms of target scaling .
The apparatus for managing a network function node according to claim 11, wherein the determining unit (62) comprises: a first determining subunit configured to determine a correspondence relationship between a network function node and an instantiated level of the VNF, wherein The correspondence is used to indicate the type and number of network function nodes supported by each instantiation level of the VNF; adding or deleting network functions according to the indication The message of the node and the corresponding relationship determine the level of instantiation corresponding to the VNF after adding or deleting the network function node.
The apparatus for managing a network function node according to claim 11, wherein the determining unit (62) comprises: a second determining subunit configured to determine a correspondence relationship between each of the network function node and the VNF, wherein the The corresponding relationship is used to indicate the type and number of network function nodes supported by the combination of the scaling levels of each scaling aspect; the message of the network function node and the corresponding relationship are added or deleted according to the indication, and the VNF is determined to be added or deleted. The level of scaling for each scaling aspect corresponding to the network function node.
The apparatus for managing a network function node according to claim 11, wherein the determining unit (62) comprises: a third determining subunit configured to determine a correspondence relationship between the network function node and the VNF component VNFC, wherein the corresponding The relationship is used to indicate the number of the virtualized deployment unit VDU and the VNFC of the VNFC required to support the network function node; the message of the network function node is added or deleted according to the indication, and the corresponding relationship is determined, and the VNF is determined to add or delete the network. The function node corresponds to the VNFC that needs to be added or deleted.