WO2023046026A1

WO2023046026A1 - Containerized vnf deployment method and apparatus

Info

Publication number: WO2023046026A1
Application number: PCT/CN2022/120590
Authority: WO
Inventors: 李世涛
Original assignee: 华为技术有限公司
Priority date: 2021-09-27
Filing date: 2022-09-22
Publication date: 2023-03-30
Also published as: CN115883283A

Abstract

The present application discloses a containerized VNF deployment method and apparatus, which may solve the technical problems in the existing technology when deploying containerized VNFs that telecom scenario requirements cannot be met, or although telecom scenario requirements can be met, a new network cannot be dynamically created as needed, resulting in the excessive workload and resource wastage of deploying the containerized VNFs. The method is applied to a VNFM, and comprises: acquiring a VNFD file; sending a resource authorization request to an NFVO, and receiving a resource authorization response returned by the NFVO; if the resource authorization response does not carry information about a created VL network, then sending a network creation request to a VIM according to connection information of the VIM, and sending a container deployment request to a CISM when a network creation success response returned by the VIM is received; and if the resource authorization response carries the information about the created VL network, then sending a container deployment request to the CISM.

Description

A containerized VNF deployment method and device

Cross References to Related Applications

This application claims the priority of the Chinese patent application with the application number 202111133879.3 and the application title "A Containerized VNF Deployment Method and Device" submitted to the China Patent Office on September 27, 2021, the entire contents of which are incorporated by reference In this application.

technical field

The present application relates to the field of communication technologies, and in particular to a containerized VNF deployment method and device.

Background technique

Network function virtualization (network function virtualization, NFV) is a technology that reduces the expensive cost of deploying dedicated equipment by using general-purpose hardware devices and virtualization technology to carry the functions of dedicated equipment in traditional networks. In the NFV architecture, the device that receives the instantiation request and instantiates the corresponding service according to the request is called a virtualized service providing device, and the device that sends the instantiation request is called a virtualized service requesting device.

The virtualized network service (network service, NS) in NFV, for example, can be an IP multimedia subsystem (IP multimedia subsystem, IMS) network service, or an evolved packet core network (evolved packet core, EPC )Internet service. An NS may contain several virtualized network function (virtualized network function, VNF) modules, and a VNF is a software implementation of a network function that can be deployed on the NFV infrastructure. When an NS is deployed for virtualization, the virtualization service requesting device first needs to submit the description information (network service descriptor, NSD) of the network service to the virtualization service provisioning device, mainly describing the topology of the network service and the included VNFs Description information (VNF descriptor, VNFD). The topology uses virtual link (virtual link, VL) information to describe the connection between each VNF. VNFD describes the topology and deployment requirements of a VNF, including the virtual deployment unit (virtualization deployment unit, VDU) contained in the VNF, the connection point (CP), the VDU that the CP needs to connect to, and the VL that the VNF needs to connect to . If the virtualization technology adopted by the NS during virtualization deployment is virtual machine technology, several VNFs contained in the NS are virtualized VNFs, and a VDU contained in the VNF will represent a virtual machine. The virtualization technology used in virtualization deployment is container technology. Several VNFs contained in the NS are containerized VNFs. A VDU contained in the VNF will represent a group of containers. The containers in this group all have the same resource requirements. And share the same network information.

The existing technology can complete the deployment of containerized VNF through the container infrastructure service management (CISM) in the NFV architecture. For example, the container management platform Kubernetes (k8S) is created on the managed cluster with Pod as the smallest unit. Containers, where a Pod can contain one or more containers. Since each Pod has one and only one network interface, each Pod can only access the default network of the cluster, that is, multiple containers can only access one network. However, in most telecom scenarios, applications generally need to access multiple networks at the same time. For example, when deploying a 5G core network, some network elements will require simultaneous access to the control plane network and the management plane network. Install the Multus plug-in to create multiple network interfaces for Pods, but the Multus plug-in cannot dynamically create new networks in the cluster, that is, it cannot dynamically create new networks according to the needs of deploying containerized VNFs. Usually, it is necessary to manually configure the new network in advance. The creation is successful, resulting in a very heavy creation workload, and because it cannot be created on demand, it may also cause waste of resources.

It can be seen that when deploying containerized VNFs, the existing technologies either cannot meet the needs of telecom scenarios, or although they can meet the requirements of telecom scenarios, they cannot dynamically create new networks on demand, resulting in excessive workload for deploying containerized VNFs and The problem of wasting resources.

Contents of the invention

The embodiment of the present application provides a containerized VNF deployment method and device, which are used to solve the problems existing in the prior art when deploying containerized VNFs that either cannot meet the requirements of telecommunication scenarios, or can meet the requirements of telecommunication scenarios but cannot Dynamic creation of new networks leads to technical problems such as excessive workload of deploying containerized VNFs and waste of resources.

In the first aspect, the embodiment of the present application provides a containerized VNF deployment method, which is applied to the virtual network function manager VNFM, including:

Obtaining a virtualized network function description VNFD file, wherein the VNFD file includes description information of a virtual connection VL network, and the description information of the VL network is used to indicate whether the VL network is a network between container cluster nodes;

Sending a resource authorization request to the network function virtualization orchestrator NFVO, and receiving a resource authorization response returned by the NFVO, wherein the resource authorization request carries the information of the VL network, and the resource authorization response carries virtual infrastructure Connection information for manager VIM;

If the resource authorization response does not carry the information of the VL network that has been created, send a network creation request to the VIM according to the connection information of the VIM, and when receiving the network creation success response returned by the VIM , sending a container deployment request to the container infrastructure manager CISM;

If the resource authorization response carries information about the created VL network, then send a container deployment request to the CISM.

Based on the above technical solution, after VNFM obtains the VNFD file, it sends a resource authorization request to NFVO and receives the resource authorization response returned by NFVO. The VNFD file includes the description information of the VL network, and the description information of the VL network is used to indicate whether the VL network is a For the network between container cluster nodes, the VL network information is carried in the resource authorization request, and the VIM connection information is carried in the resource authorization response. The VIM sends a network creation request, and sends a container deployment request to the CISM when it receives the network creation success response returned by the VIM, and sends a container deployment request to the CISM if the resource authorization response carries information about the created VL network. VNFM can determine whether the VL network is a network between container cluster nodes and the information of the VL network according to the VNFD file, and then VNFM sends a request to VIM, or VNFM and CISM send requests to VIM respectively, or NFVO and CISM Send requests to the VIM respectively, complete the creation of the VL network between the container cluster nodes and the network interface of the container cluster nodes as needed, and send the request to the CISM by the VNFM to complete the deployment of the container and the connection between the container and the VL network, so as to Dynamically create network interfaces of container cluster nodes and VL networks between container cluster nodes, which not only meets the requirements of telecom scenarios, but also reduces workload and avoids waste of resources.

In a possible design, the virtualized network function description VNFD file is obtained, including:

receiving the virtualized network function VNF instance identifier creation request sent by the NFVO, wherein the VNF instance identifier creation request carries a virtualized network function description VNFD identifier;

Obtain the corresponding VNFD file according to the VNFD identifier.

In a possible design, the description information of the VL network includes description information of the type of the VL network, where the type of the VL network is used to indicate whether the VL network is a network between container cluster nodes.

Based on the above technical solution, the description information of the VL network type is added to the description information of the VL network, so that VNFM can determine whether the VL network is a network between container cluster nodes according to the VNFD file, thereby creating a network between container cluster nodes on demand The VL network not only meets the requirements of telecom scenarios, but also reduces workload and avoids waste of resources.

In a possible design, the VNFD file further includes the description information of the affinity or anti-affinity group and the description information of the virtual deployment unit VDU, wherein the description information of the affinity or anti-affinity group is used to indicate the The corresponding relationship between the connection point CP of the VDU and the network interface of the container cluster node and the corresponding relationship between the VDU and the container cluster node. The description information of the VDU is used to indicate the container resources and CP contained in the VDU and the VDU The CP needs to connect to the VL network.

In a possible design, the description information of the affinity or anti-affinity group includes the description information of the CP range of the VDU, where the CP range of the VDU is used to indicate any two of the VDU Whether the CP is connected to the network interface of the same container cluster node.

Based on the above technical solution, add the description information of the CP range of the VDU to the description information of the affinity or anti-affinity group, so that VNFM can determine whether any two CPs of the VDU are connected to the same network interface of the container cluster node according to the VNFD file , and then determine whether to create a new network interface on the container cluster node where the VDU is located, so as to create the network interface of the container cluster node on demand, which not only meets the requirements of the telecom scenario, but also reduces the workload and avoids resource waste.

In a possible design, sending a resource authorization request to the network function virtualization orchestrator NFVO also includes:

If it is determined that the VL network is a network between container cluster nodes, a resource authorization request is sent to the NFVO.

Based on the above technical solution, when the VL network is determined to be a network between container cluster nodes, a resource authorization request is sent to NFVO to create a VL network between container cluster nodes on demand, which not only meets the needs of telecom scenarios, but also reduces work amount, avoiding wastage of resources.

In a possible design, the information of the VL network is used to indicate the network interface of the container cluster node to which the VL network needs to be connected and the CP of the VDU to which the network interface of the container cluster node needs to be connected.

In a possible design, the network creation request is used to request to create the VL network and the network interface of the container cluster node to be connected to the VL network.

In a possible design, the container deployment request is used to request to deploy a container and connect the container to the VL network, and the container deployment request carries the created VL network and the VL network to be connected Information about the network interfaces of the container cluster nodes.

In a possible design, the network creation request is used to request creation of the VL network.

In a possible design, the container deployment request is used to request to create a network interface of a container cluster node that needs to be connected to the VL network, deploy a container and connect the container to the VL network, and the container deployment request carries The connection information of the VIM and the information of the created VL network.

In the second aspect, the present application also provides a containerized VNF deployment method, which is applied to the network function virtualization orchestrator NFVO, including:

Send a virtualized network function VNF instance identifier creation request to the virtual network function manager VNFM, wherein the VNF instance identifier creation request carries a virtualized network function description VNFD identifier, and the VNFD file corresponding to the VNFD identifier includes a virtual connection VL network The description information of the VL network is used to indicate whether the VL network is a network between container cluster nodes;

receiving the resource authorization request sent by the VNFM, and sending a resource authorization response to the VNFM, wherein the resource authorization request carries the information of the VL network, and the resource authorization response carries the information of the virtual infrastructure manager VIM connection information.

Based on the above technical solution, NFVO sends a VNF instance ID creation request to VNFM, wherein the VNF instance ID creation request carries the VNFD ID, and the VNFD file corresponding to the VNFD ID includes the description information of the VL network, and the description information of the VL network is used to indicate the VL network Whether it is a network between container cluster nodes, receive the resource authorization request sent by VNFM, and send a resource authorization response to VNFM, where the resource authorization request carries VL network information, and the resource authorization response carries VIM connection information. VNFM can determine the corresponding VNFD file according to the VNFD identifier sent by NFVO, and then determine whether the VL network is a network between container cluster nodes and the information of the VL network, so as to dynamically create the network interface of the container cluster node and the container cluster node on demand The VL network between them not only meets the requirements of telecom scenarios, but also reduces workload and avoids waste of resources.

In a possible design, sending a resource authorization response to the VNFM includes:

Send the resource authorization response to the VNFM, so that the VNFM sends a network creation request to the VIM according to the connection information of the VIM, and when receiving the network creation success response returned by the VIM, send a request to the container base The facility manager CISM sends container deployment requests.

In a possible design, sending a resource authorization response to the VNFM also includes:

Send a network creation request to the VIM;

When receiving the network creation success response returned by the VIM, send the resource authorization response to the VNFM, so that the VNFM sends a container deployment request to the CISM, wherein the resource authorization response carries the created information of the VL network.

In a possible design, sending a network creation request to the VIM includes:

Sending a network creation request to the VIM according to the connection information of the VIM, and receiving a network creation success response returned by the VIM; or,

Send a network creation request to the container cluster manager CCM, so that the CCM sends a network creation request to the VIM according to the connection information of the VIM, and receives a network creation success response returned by the VIM, wherein the network creation The successful response carries the connection information of the VIM.

In the third aspect, the present application also provides a VNFM, the VNFM has the function of realizing the above-mentioned first aspect or any possible design method of the first aspect, and the function can be realized by hardware or executed by hardware corresponding software implementation. The hardware or software includes one or more modules corresponding to the above functions, for example, including an acquisition module, a first processing module, a second processing module, and a third processing module.

An acquisition module, configured to acquire a virtualized network function description VNFD file, wherein the VNFD file includes description information of a virtual connection VL network, and the description information of the VL network is used to indicate whether the VL network is a container cluster node network of;

The first processing module is configured to send a resource authorization request to the network function virtualization orchestrator NFVO, and receive a resource authorization response returned by the NFVO, wherein the resource authorization request carries the information of the VL network, and the resource The authorization response carries the connection information of the virtual infrastructure manager VIM;

The second processing module is configured to send a network creation request to the VIM according to the connection information of the VIM if the resource authorization response does not carry the information of the created VL network, and upon receiving the VIM When the returned network creates a successful response, send a container deployment request to the container infrastructure manager CISM;

A third processing module, configured to send a container deployment request to the CISM if the resource authorization response carries information about the created VL network.

In a possible design, the acquisition module is specifically used for:

Obtain the corresponding VNFD file according to the VNFD identifier.

In a possible design, the first processing module is also used for:

In the fourth aspect, the present application also provides an NFVO, the NFVO has the function of realizing the above-mentioned second aspect or any possible design method of the second aspect, and the function can be implemented by hardware or executed by hardware corresponding software implementation. The hardware or software includes one or more modules corresponding to the above functions, such as including a first processing module and a second processing module.

The first processing module is configured to send a virtualized network function VNF instance identifier creation request to the virtual network function manager VNFM, wherein the VNF instance identifier creation request carries a virtualized network function description VNFD identifier, and the VNFD identifier corresponds to The VNFD file includes description information of a virtual connection VL network, and the description information of the VL network is used to indicate whether the VL network is a network between container cluster nodes;

The second processing module is configured to receive the resource authorization request sent by the VNFM, and send a resource authorization response to the VNFM, wherein the resource authorization request carries the information of the VL network, and the resource authorization response carries Connection information for the virtual infrastructure manager VIM.

In a possible design, the second processing module is specifically used for:

Send a network creation request to the VIM;

In a possible design, the second processing module is specifically used for:

In the fifth aspect, the present application also provides a device for deploying a containerized VNF, the device for deploying a containerized VNF includes at least one processor and a memory; the memory stores one or more computer programs; when the memory stores When one or more computer programs are executed by the at least one processor, the device for deploying the containerized VNF is made to execute the above-mentioned first aspect or any possible design method of the above-mentioned first aspect, or the above-mentioned second aspect Or any possible design method of the second aspect above.

In a sixth aspect, the present application further provides a computer storage medium, the computer storage medium includes a computer program, and when the computer program runs on a computer, the computer executes the above-mentioned first aspect or any one of the above-mentioned first aspects. A possible design method, or the above-mentioned second aspect or any possible design method of the above-mentioned second aspect.

In the seventh aspect, the present application also provides a program product, which, when the program product is run on a computer, causes the computer to execute the above-mentioned first aspect or the method of any possible design of the above-mentioned first aspect, or the above-mentioned The second aspect or any possible design method of the second aspect above.

In the eighth aspect, the present application also provides a chip, which can be coupled with the memory of the containerized VNF deployment device, and is used to call the computer program stored in the memory and execute the above-mentioned first aspect and any possible design thereof method, or the above-mentioned second aspect or any possible design method of the above-mentioned second aspect.

Description of drawings

FIG. 1 is a schematic diagram of the architecture of a NFV system provided in an embodiment of the present application;

FIG. 2a is a schematic flowchart of a containerized VNF deployment method provided by an embodiment of the present application;

FIG. 2b is a schematic diagram of description information of a VDU provided by an embodiment of the present application;

FIG. 2c is a schematic diagram of description information of a VL network provided by an embodiment of the present application;

Fig. 2d is a schematic diagram of description information of an affinity or anti-affinity group provided in the embodiment of the present application;

FIG. 2e is a schematic diagram of a container cluster node provided by an embodiment of the present application;

FIG. 2f is a schematic diagram of a VL network provided by an embodiment of the present application;

FIG. 3 is a schematic flowchart of another containerized VNF deployment method provided by the embodiment of the present application;

FIG. 4 is a schematic structural diagram of a NFVO provided in an embodiment of the present application;

FIG. 5 is a schematic structural diagram of a VNFM provided in an embodiment of the present application;

FIG. 6 is a schematic structural diagram of a device for deploying a containerized VNF provided by an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.

As shown in Figure 1, it is a schematic diagram of the architecture of a NFV system provided by the embodiment of the present application. The NFV system includes the following functional components: a network function virtualization orchestrator (NFV orchestrator, NFVO) 102, a virtualized network function manager (virtualized network function manager (VNFM) 104, CISM 106, virtualized infrastructure manager (virtualized infrastructure manager, VIM) 108, VNF 110, equipment management system (equipment management system, EMS) 112, operations support system and business support system (operations support system and business support system, OSS/BSS) 126.

Among them, NFVO102 is mainly responsible for handling the lifecycle management of virtualization services, as well as the allocation and scheduling of virtual resources in virtual infrastructure and network functions virtualization infrastructure (network functions virtualization infrastructure, NFVI). NFVO 102 can communicate with one or more VNFM 104 to execute resource-related requests, send configuration information to VNFM 104 , and collect status information of VNF 110 . In addition, NFVO102 can also communicate with VIM108, perform resource allocation, resource reservation, query virtualization hardware resource configuration and status information.

It should be noted that, in the embodiment of this application, NFVI is the infrastructure layer of NFV, which includes hardware components, software components or a combination of both, and is used to establish a virtualized environment, deploy, manage and implement VNF110, and NFVI includes virtual computing 120 , a virtual storage 122 , and a virtual network 124 . The virtualization layer and hardware resources of NFV are used to provide VNF110 with virtualized resources, such as virtual machines and other forms of virtual containers, and the hardware resources include computing hardware 114 , storage hardware 116 , and network hardware 118 . In a possible design, the resources of computing hardware 114 and storage hardware 116 can be pooled together. The virtualization layer in NFVI can abstract hardware resources and decouple VNF110 from the underlying physical network layer.

VNFM104 is mainly responsible for the lifecycle management of one or more VNF110, such as instantiating, updating, querying, scaling, and terminating VNF110. The VNFM 104 can communicate with each VNF 110 to complete lifecycle management of each VNF 110 and exchange of virtualized hardware resource configuration and state information. In the NFV architecture, there may be multiple VNFMs, which are responsible for managing the life cycle of different VNFs 110 .

CISM106 is mainly responsible for container resource management, including container creation, updating, query, scaling, terminating, etc. When the VNF is deployed in the form of containers, the VNFM 104 can communicate with the CISM 106 to request the creation of container resources.

VIM 108 is mainly responsible for controlling and managing the interaction between VNF 110 and computing hardware 114 , storage hardware 116 , network hardware 118 , virtual computing 120 , virtual storage 122 , and virtual network 124 . For example, VIM 106 performs resource management functions, including managing infrastructure resources, allocation (such as adding resources to virtual containers), and running functions (such as collecting NFVI fault information). VNFM104 and VIM108 can communicate with each other, request resource allocation, and exchange virtualized hardware resource configuration and status information.

EMS 112 is a system used to configure and manage equipment in traditional telecommunication systems. In the NFV architecture, the EMS 112 can also be used to configure and manage the VNF 110 , and initiate lifecycle management operations such as instantiation of a new VNF to the VNFM 104 .

OSS/BSS126 is mainly responsible for supporting various end-to-end telecommunication services. The management functions supported by OSS include network configuration, service provisioning, fault management, etc., and the management functions supported by BSS include product management, order management, revenue management, and customer management.

It should be understood that an NFV system is exemplarily shown in FIG. 1 for ease of understanding, but this should not constitute any limitation to the embodiment of the present application. The NFV system may also include more or less components than shown in the figure, Or combine some parts, or split some parts, or different parts arrangement. The illustrated components can be realized in hardware, software or a combination of software and hardware. In addition, the combination or connection relationship between the components in FIG. 1 can also be adjusted and modified, which is not specifically limited in this embodiment of the present application.

The above describes the NFV system provided by the embodiment of the present application, and then introduces the deployment method of the containerized VNF provided by the embodiment of the present application with reference to the accompanying drawings.

It should be understood that the term "at least one" in the embodiments of the present application refers to one or more, and "multiple" refers to two or more. "And/or" describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural. The character "/" generally indicates that the contextual objects are an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one item (piece) of a, b, or c may represent: a, b, c, a and b, a and c, b and c, or a and b and c.

And, unless otherwise stated, the ordinal numerals such as "first" and "second" mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the order, timing, priority or priority of multiple objects. Importance. For example, the first priority criterion and the second priority criterion are only for distinguishing different criteria, but do not represent the difference in content, priority or importance of the two criteria.

Embodiment one

As shown in Figure 2a, it is a schematic flowchart of a containerized VNF deployment method provided by the embodiment of the present application, and the containerized VNF deployment method can be applied to the NFV system shown in Figure 1 or with a functional structure similar to Figure 1 . In this embodiment, the creation of the VL network between container cluster nodes and the network interface of the container cluster nodes is completed by VNFM sending a request to VIM, or the VL network between container cluster nodes is completed by VNFM sending a request to VIM , the creation of the network interface of the container cluster node is completed by sending a request from CISM to VIM.

S201. The NFVO sends a VNF instance identifier creation request to the VNFM. Correspondingly, the VNFM receives the VNF instance ID creation request from the NFVO.

Here, the VNF instance identifier creation request carries the VNFD identifier.

S202. The VNFM creates a VNF instance identifier, obtains a VNFD file corresponding to the VNFD identifier, and sends the VNF instance identifier to the NFVO. Correspondingly, the NFVO receives the VNF instance identifier from the VNFM.

Here, the VNFM can obtain the corresponding VNFD file according to the VNFD identifier carried in the VNF instance identifier creation request. For example, the VNFM can determine whether there is a VNFD file corresponding to the VNFD identifier locally, and if not, send the VNFD file to NFVO to obtain request, and receive a VNFD file acquisition response returned by the NFVO, wherein the VNFD file acquisition request carries the VNFD identifier, and the VNFD file acquisition response carries the VNFD file corresponding to the VNFD identifier.

It should be noted that, in the embodiment of the present application, the VNFD file may include the description information of the VL network, the description information of the affinity or anti-affinity group (affinity or anti-affinity group), and the description information of the VDU.

Wherein, the description information of the VL network is used to indicate whether the VL network is a network between container cluster nodes, for example, the description information of the VL network may include the description information of the VL network type (type), and the VL network type may be used to indicate the VL network Whether the network is a network between container cluster nodes.

The description information of the affinity or anti-affinity group is used to indicate the corresponding relationship between the CP of the VDU and the network interface of the container cluster node and the corresponding relationship between the VDU and the container cluster node. For example, when the description information of the affinity or anti-affinity group is used When indicating the corresponding relationship between the CP of the VDU and the network interface of the container cluster node, the description information of the affinity or anti-affinity group can include the description information of the scope of the CP of the VDU, and the scope of the CP of the VDU can be used to indicate the VDU Whether any two CPs are connected to the network interface of the same container cluster node.

The description information of the VDU is used to indicate the container resource and CP contained in the VDU and the VL network to which the CP of the VDU needs to be connected.

Exemplarily, as shown in FIG. 2b, it is a schematic diagram of the description information of a VDU provided by the embodiment of the present application. The mciopProfile in FIG. 2b is the deployment package information used by CISM for container deployment, and the mciopProfile includes the deployment package identifier ( mciopId) information and related VDU (associatedVdu) information, wherein, mciopId is M-123, that is, the corresponding deployment package can be obtained in the file package containing the VNFD file by identifying M-123, and associatedVdu is VDU1, VDU2 and VDU3, namely The resources included in the corresponding deployment package are the resources of VDU1, VDU2 and VDU3. VDU1 in Figure 2b contains 2 container resources (osContainerDesc) and 1 CP: osContainerDesc-1, osContainerDesc-2 and cp-1, VDU2 contains 2 container resources and 1 CP: osContainerDesc-3, osContainerDesc-4 and cp -2, VDU2 contains 1 container resource and 1 CP: osContainerDesc-5 and cp-3. The vnic types of cp-1 and cp-2 in Figure 2b are both IPVLAN, the vnic type of cp-2 is MACVLAN, and the VL networks to be connected to cp-1, cp-2 and cp-3 are VL-1. Each osContainerDesc in Figure 2b describes the resource requirement information of each container, such as the central processing unit requirement information (requested Cpu Resources) and memory requirement information (requested Memory Resources). For example, the requested Cpu Resources of osContainerDesc-1 is 2. The requested Memory Resources is 500MB.

Exemplarily, as shown in FIG. 2c, it is a schematic diagram of description information of a VL network provided by the embodiment of the present application. The layer protocol (LayerProtocol) used by the VL-1 network in FIG. 2c is Ethernet, IPV4, VL-1 The network type (type) is node-network, indicating that the VL-1 network is a network between container cluster nodes.

Exemplarily, as shown in Figure 2d, it is a schematic diagram of the description information of an affinity or anti-affinity group provided by the embodiment of the present application. Figure 2d contains 3 affinity or anti-affinity groups, which are group- 1. group-2 and group-3. Among them, the affinity or anti-affinity (affinity or anti-affinity) of group-1 is defined as affinity (AFFINITY), indicating that group-1 is an affinity group, the information defined by group-1 is correct, group-2 and The affinity or anti-affinity of group-3 is defined as anti-affinity (ANTI-AFFINITY), indicating that group-2 and group-3 are anti-affinity groups, and the information defined by group-1 is incorrect. For example, the affinity group group-1 defines the scope of VDU1 and VDU2 as the common node (NFVI-node), that is, VDU1 and VDU2 are on a container cluster node. The anti-affinity group group-2 defines the scope of VDU2 and VDU3 as NFVI-node, that is, VDU2 and VDU3 are not on the same container cluster node. The anti-affinity group group-3 defines the range of cp-1 and cp-2 as a common network interface (host-nic), that is, cp-1 and cp-2 will not connect to the network interface of the same container cluster node. According to the definitions of group-1, group-2 and group-3, it can be determined that VDU1 and VDU2 are on one container cluster node, and VDU3 is on another container cluster node, because cp-1 and cp-2 will not connect to the same container The network interface of the cluster node, so there must be a new network interface connected to cp-2 on the container cluster nodes where VDU1 and VDU2 are located.

As shown in Figure 2e, it is a schematic diagram of a container cluster node provided by the embodiment of the present application. VDU1 and VDU2 in Figure 2e are on a container cluster node. If the range of cp-1 and cp-2 is host-nic, That is, cp-1 and cp-2 are connected to the network interface of the same container cluster node, and both cp-1 and cp-2 are connected to the network interface NIC-1 of the container cluster node, and there is no need to create a new one on the container cluster node Network interface, if the scope of cp-1 and cp-2 is not host-nic, that is, cp-1 and cp-2 will not connect to the network interface of the same container cluster node, you need to create a new one on the container cluster node The network interface NIC-2 is connected to cp-2.

S203. The NFVO sends a VNF instantiation request to the VNFM. Correspondingly, the VNFM receives the VNF instantiation request from the NFVO.

Here, the VNF instantiation request is used to request to create a VNF instance corresponding to the VNF instance identifier.

S204. The VNFM sends a resource authorization request to the NFVO. Correspondingly, NFVO receives the resource authorization request from VNFM.

Here, the resource authorization request carries the information of the resource to be created, for example, the information of the container resource and the information of the VL network.

The container resource information is used to indicate the VDU that needs to be deployed on the container cluster node and the container that needs to be deployed on the VDU. Exemplarily, as shown in Figure 2b, VDU1 and VDU2 need to be deployed on the container cluster node Node-1, osContainerDesc-1 and osContainerDesc-2 need to be deployed on VDU1, osContainerDesc-3 and osContainerDesc-4 need to be deployed on VDU2, and the container cluster node VDU3 needs to be deployed on Node-2, and osContainerDesc-5 needs to be deployed on VDU3, then the resource authorization request will carry the corresponding creation resource (addResource) information allocated for each container to be created (such as osContainerDesc-1~osContainerDesc-5) , wherein, the addResource information includes resource definition (ResourceDefinition) information, and the ResourceDefinition information is used to indicate the type and corresponding identifier of the resource, for example, the type is OSCONTAINER, and the identifier is osContainerDesc-1.

The information of the VL network is used to indicate the network interface of the container cluster node to be connected to the VL network and the CP of the VDU to be connected to the network interface of the container cluster node. Exemplarily, as shown in FIG. 2f, it is a schematic diagram of a VL network provided by the embodiment of the present application. The network interface of the container cluster node that needs to be connected to the VL-1 network in FIG. 2f is: on the container cluster node Node-1 The network interface NIC-1 on the container cluster node Node-2 and the network interface NIC-2 on the container cluster node Node-2, the CP of the VDU that needs to be connected to the network interface NIC-1 on the container cluster node Node-1 is: CP-1 of VDU1 and CP of VDU2 CP-2, the network interface NIC-2 on the container cluster node Node-2 needs to connect to the CP of the VDU: CP-3 of VDU3, you need to create a new network interface NIC-1 on the container cluster node Node-1, Create a new network interface NIC-2 on the container cluster node Node-2, and the resource authorization request will carry the allocation for each network interface and VL network (such as NIC-1, NIC-2, VL-1 network) that needs to be created The corresponding addResource information.

It should be noted that, in this embodiment of the application, before sending a resource authorization request to NFVO, it can be determined whether the VL network is a network between container cluster nodes. If it is determined that the VL network is a network between container cluster nodes, then the Send resource authorization request.

S205. The NFVO sends a resource authorization response to the VNFM. Correspondingly, VNFM receives the resource authorization response from NFVO.

Here, NFVO can return corresponding authorization information (GrantInfo) for each addResource information in the resource authorization request, that is, the resource authorization response sent by NFVO to VNFM will carry the GrantInfo corresponding to each addResource information. Information, the GrantInfo will carry the connection information of the CISM, and for the information of the VL network, the GrantInfo will carry the connection information of the VIM.

S206. The VNFM sends a network creation request to the VIM according to the connection information of the VIM, and sends a container deployment request to the CISM when receiving a network creation success response returned by the VIM.

Here, if the network creation request is used to request the creation of a VL network and the network interface of the container cluster node that the VL network needs to connect to, the container deployment request is used to request the deployment of the container and connect the container to the VL network. The container deployment request carries the created The VL network and the network interface information of the connected container cluster nodes need to be connected to the VL network.

Exemplarily, the VNFM first sends a network creation request to the VIM according to the connection information of the VIM. The network creation request is used to request to create a VL-1 network, to create a new network interface NIC-1 on the container cluster node Node-1 and to create a new network interface NIC-2 on the container cluster node Node-2. After receiving the successful network creation response returned by VIM, it sends a container deployment request to CISM. Among them, the container deployment request is used to request to deploy VDU1 and VDU2 on container cluster node Node-1, deploy osContainerDesc-1 and osContainerDesc-2 on VDU1, deploy osContainerDesc-3 and osContainerDesc-4 on VDU2, and deploy osContainerDesc-3 and osContainerDesc-4 on container cluster node Node-1. VDU3 needs to be deployed on -2, osContainerDesc-5 needs to be deployed on VDU3, and each container is connected to the VL-1 network. The container deployment request carries the deployment package and information about the created VL-1 network, network interface NIC-1, and network interface NIC-2. Thus, VIM completes the creation of the VL-1 network, the network interface NIC-1 on the container cluster node Node-1 and the network interface NIC-2 on the container cluster node Node-2, and CISM completes the creation of the container cluster node Node-1 and Node- Deployment of the container on 2 and the connection of the container to the VL-1 network.

If the network creation request is used to request the creation of a VL network, the container deployment request is used to request the network interface of the container cluster node that needs to be connected to the VL network, deploy the container and connect the container to the VL network. The container deployment request carries the connection information of the VIM and Information about the created VL network.

Exemplarily, the VNFM first sends a network creation request to the VIM according to the connection information of the VIM. Wherein, the network creation request is used to request to create a VL-1 network. After receiving the successful network creation response returned by VIM, it sends a container deployment request to CISM. Among them, the container deployment request is used to request to create a new network interface NIC-1 on the container cluster node Node-1, create a new network interface NIC-2 on the container cluster node Node-2, and create a new network interface NIC-2 on the container cluster node Node-1. Deploy VDU1 and VDU2, deploy osContainerDesc-1 and osContainerDesc-2 on VDU1, deploy osContainerDesc-3 and osContainerDesc-4 on VDU2, deploy VDU3 on container cluster node Node-2, and deploy osContainerDesc-5 on VDU3, And connect each container with the VL-1 network. The container deployment request carries the deployment package, the connection information of the VIM and the information of the created VL-1 network. Thus, VIM completes the creation of the VL-1 network, CISM completes the creation of the network interface NIC-1 on the container cluster node Node-1 and the network interface NIC-2 on the container cluster node Node-2, and the container cluster node Node-1 and Deployment of containers on Node-2 and connection of containers to VL-1 network.

S207. When receiving the container deployment success response returned by the CISM, the VNFM sends a VNF instantiation success response to the NFVO.

Based on the above technical solution, the VNFM can determine whether the VL network is a network between container cluster nodes and the information of the VL network according to the VNFD file, and then the VNFM sends a request to the VIM, or the VNFM and the CISM send requests to the VIM respectively, according to It is necessary to complete the creation of the VL network between the container cluster nodes and the network interface of the container cluster nodes, and the VNFM sends a request to the CISM to complete the deployment of the container and the connection between the container and the VL network, so as to dynamically create the network of the container cluster nodes on demand The interface and the VL network between the container cluster nodes not only meet the requirements of the telecom scenario, but also reduce the workload and avoid resource waste.

Embodiment two

As shown in Figure 3, it is a schematic flowchart of another containerized VNF deployment method provided by the embodiment of the present application. The containerized VNF deployment method can be applied to the NFV shown in Figure 1 or with a functional structure similar to that in Figure 1 system. In this embodiment, the VL network between the container cluster nodes is completed by sending a request from the NFVO to the VIM, and the creation of the network interface of the container cluster nodes is completed by sending a request to the VIM from the CISM.

S301. The NFVO sends a VNF instance identifier creation request to the VNFM. Correspondingly, the VNFM receives the VNF instance ID creation request from the NFVO.

For the S301, refer to the introduction of the above S201, which will not be repeated here.

S302. The VNFM creates a VNF instance identifier, acquires a VNFD file corresponding to the VNFD identifier, and sends the VNF instance identifier to the NFVO. Correspondingly, the NFVO receives the VNF instance identifier from the VNFM.

For the S302, refer to the introduction of the above S202, which will not be repeated here.

S303. The NFVO sends a VNF instantiation request to the VNFM. Correspondingly, the VNFM receives the VNF instantiation request from the NFVO.

For the S303, refer to the introduction of the above S203, which will not be repeated here.

S304. The VNFM sends a resource authorization request to the NFVO. Correspondingly, NFVO receives the resource authorization request from VNFM.

For the S304, refer to the introduction of the above S204, which will not be repeated here.

S305. The NFVO sends a network creation request to the VIM, and sends a resource authorization response to the VNFM when receiving a network creation success response returned by the VIM. Correspondingly, VNFM receives the resource authorization response from NFVO.

Here, NFVO can determine whether there is connection information of VIM locally. If so, it can send a network creation request to VIM according to the connection information of VIM, and receive the network creation success response returned by VIM. If not, it can send a request to the container cluster manager (container identification system cluster manager, CCM) sends a network creation request, so that the CCM sends a network creation request to the VIM according to the connection information of the VIM, and receives the network creation success response returned by the VIM, wherein the network creation request is used to request the creation of a VL network , the network creation success response carries the VIM connection information.

When receiving the network creation success response returned by VIM, NFVO can return the corresponding GrantInfo for each addResource information in the resource authorization request, that is, the resource authorization response sent by NFVO to VNFM will carry the GrantInfo corresponding to each addResource information and the For the created VL network information, the GrantInfo will carry the CISM connection information for the container resource information, and the VIM connection information for the VL network information.

S306. The VNFM sends a container deployment request to the CISM.

Here, the container deployment request is used to request to create the network interface of the container cluster node that needs to be connected to the VL network, deploy the container and connect the container to the VL network. The container deployment request carries the connection information of the VIM and the information of the created VL network.

Exemplarily, the VNFM sends a container deployment request to the CISM. Among them, the container deployment request is used to request to create a new network interface NIC-1 on the container cluster node Node-1, create a new network interface NIC-2 on the container cluster node Node-2, and create a new network interface NIC-2 on the container cluster node Node-1. Deploy VDU1 and VDU2, deploy osContainerDesc-1 and osContainerDesc-2 on VDU1, deploy osContainerDesc-3 and osContainerDesc-4 on VDU2, deploy VDU3 on container cluster node Node-2, and deploy osContainerDesc-5 on VDU3, And connect each container with the VL-1 network. The container deployment request carries the deployment package, the connection information of the VIM and the information of the created VL-1 network. Thus, CISM completes the creation of the network interface NIC-1 on the container cluster node Node-1 and the network interface NIC-2 on the container cluster node Node-2, the deployment of the containers on the container cluster nodes Node-1 and Node-2, and The connection of the container to the VL-1 network.

S307. When receiving the container deployment success response returned by the CISM, the VNFM sends a VNF instantiation success response to the NFVO.

Based on the above technical solution, VNFM can determine whether the VL network is a network between container cluster nodes and the information of the VL network according to the VNFD file, and then NFVO and CISM send requests to VIM to complete the VL between container cluster nodes as needed The creation of the network interface of the network and container cluster nodes, and the VNFM sending a request to the CISM to complete the deployment of the container and the connection between the container and the VL network, thereby dynamically creating the network interface of the container cluster nodes and the VL between the container cluster nodes on demand The network not only meets the needs of telecom scenarios, but also reduces workload and avoids waste of resources.

It should be understood that in the embodiment of the present application, NFVO and VNFM in the NFV system can perform some or all of the steps in the embodiment of the present application, these steps are only examples, and the embodiment of the present application can also perform other steps or variations of various steps . In addition, each step may be performed in a different order presented in the embodiment of the present application, and it may not be necessary to perform all the steps in the embodiment of the present application.

In each embodiment of the present application, if there is no special explanation and logical conflict, the terms and/or descriptions between different embodiments are consistent and can be referred to each other, and the technical features in different embodiments are based on their inherent logic Relationships can be combined to form new embodiments.

The foregoing mainly introduces the solution provided by the embodiment of the present application from the perspective of the interaction between the NFVO and the VNFM. It should be understood that, in order to realize the above-mentioned functions, the above-mentioned NFVO or VNFM includes corresponding hardware structures and/or software modules for performing each function. Those skilled in the art should easily realize that the present application can be implemented in the form of hardware or a combination of hardware and computer software in combination with the units and algorithm steps of each example described in the embodiments disclosed herein. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

The embodiment of the present application can divide the functional modules of NFVO or VNFM according to the above method example, for example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation.

In the case of using an integrated unit (module), FIG. 4 shows a schematic structural diagram of a VNFM provided by an embodiment of the present application. As shown in FIG. 4 , VNFM400 may include: an acquisition module 401 , a first processing module 402 , a second processing module 403 , and a third processing module 404 .

The obtaining module 401 is configured to obtain a virtualized network function description VNFD file, wherein the VNFD file includes description information of a virtual connection VL network, and the description information of the VL network is used to indicate whether the VL network is a container cluster node network between

The first processing module 402 is configured to send a resource authorization request to the network function virtualization orchestrator NFVO, and receive a resource authorization response returned by the NFVO, wherein the resource authorization request carries the information of the VL network, and the The resource authorization response carries the connection information of the virtual infrastructure manager VIM;

The second processing module 403 is configured to send a network creation request to the VIM according to the connection information of the VIM if the resource authorization response does not carry the information of the created VL network, and upon receiving the When the network creation success response returned by VIM sends a container deployment request to the container infrastructure manager CISM;

The third processing module 404 is configured to send a container deployment request to the CISM if the resource authorization response carries information about the created VL network.

In a possible design, the acquiring module 401 is specifically used for:

Obtain the corresponding VNFD file according to the VNFD identifier.

In a possible design, the first processing module 402 is also configured to:

In the case of using an integrated unit (module), FIG. 5 shows a schematic structural diagram of an NFVO provided by an embodiment of the present application. As shown in FIG. 5 , NFVO 500 may include: a first processing module 501 and a second processing module 502 .

The first processing module 501 is configured to send a virtualized network function VNF instance identifier creation request to the virtual network function manager VNFM, wherein the VNF instance identifier creation request carries a virtualized network function description VNFD identifier, and the VNFD identifier corresponds to The VNFD file includes description information of a virtual connection VL network, and the description information of the VL network is used to indicate whether the VL network is a network between container cluster nodes;

The second processing module 502 is configured to receive the resource authorization request sent by the VNFM, and send a resource authorization response to the VNFM, wherein the resource authorization request carries the information of the VL network, and the resource authorization response contains Carries connection information for the virtual infrastructure manager VIM.

In a possible design, the second processing module 502 is specifically configured to:

Send a network creation request to the VIM;

Based on the same technical concept, the embodiment of this application also provides a containerized VNF deployment device, as shown in Figure 6, the device 600 may include:

at least one processor 601; and, a communication interface 603 communicatively connected to the at least one processor 601;

Wherein, the at least one processor 601 executes instructions stored in the memory 602, so that the apparatus 600 executes the methods shown in FIGS. 2a-3.

Optionally, the memory 602 is located outside the device 600 .

Optionally, the apparatus 600 includes the memory 602, the memory 602 is connected to the at least one processor 601, and the memory 602 stores instructions executable by the at least one processor 601. FIG. 6 shows with dashed lines that memory 602 is optional for device 600 .

Wherein, the processor 601 and the memory 602 may be coupled through an interface circuit, or may be integrated together, which is not limited here.

The specific connection medium among the processor 601, the memory 602, and the communication interface 603 is not limited in the embodiment of the present application. In the embodiment of the present application, in FIG. 6, the processor 601, the memory 602, and the communication interface 603 are connected through a bus 604. The bus is represented by a thick line in FIG. 6, and the connection mode between other components is only for schematic illustration. , is not limited. The bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used in FIG. 6 , but it does not mean that there is only one bus or one type of bus.

It should be understood that the processor mentioned in the embodiments of the present application may be implemented by hardware or by software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like. When implemented by software, the processor may be a general-purpose processor implemented by reading software codes stored in a memory.

Exemplary, the processor can be a central processing unit (central processing unit, CPU), and can also be other general-purpose processors, digital signal processors (digital signal processors, DSP), application specific integrated circuits (application specific integrated circuits, ASICs) , off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.

It should be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile memory and nonvolatile memory. Among them, the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory can be random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, many forms of RAM are available such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data eat SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM ) and direct memory bus random access memory (direct rambus RAM, DR RAM).

It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, the memory (storage module) may be integrated in the processor.

It should be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

Based on the same technical idea, an embodiment of the present application also provides a computer storage medium, the computer storage medium includes a computer program, and when the computer program is run on a computer, the method shown in Figure 2a-Figure 3 is executed .

Based on the same technical concept, an embodiment of the present application further provides a chip, the chip is coupled with a memory, and is used to read and execute program instructions stored in the memory, so that the methods shown in FIGS. 2a-3 are executed.

Based on the same technical idea, an embodiment of the present application further provides a computer program product, which causes the methods shown in FIGS. 2a-3 to be executed when the computer program product is run on a computer.

It should be understood that all relevant content of the steps involved in the above method embodiments may be referred to the functional description of the corresponding functional modules, which will not be repeated here.

Those skilled in the art should understand that the embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the present application. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby The instructions provide steps for implementing the functions specified in the flow chart or blocks of the flowchart and/or the block or blocks of the block diagrams.

Obviously, those skilled in the art can make various changes and modifications to the application without departing from the spirit and scope of the application. In this way, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these modifications and variations.

Claims

A containerized VNF deployment method, characterized in that it is applied to a virtual network function manager VNFM, comprising:

Obtaining a virtualized network function description VNFD file, wherein the VNFD file includes description information of a virtual connection VL network, and the description information of the VL network is used to indicate whether the VL network is a network between container cluster nodes;

Sending a resource authorization request to the network function virtualization orchestrator NFVO, and receiving a resource authorization response returned by the NFVO, wherein the resource authorization request carries the information of the VL network, and the resource authorization response carries virtual infrastructure Connection information for manager VIM;

If the resource authorization response does not carry the information of the VL network that has been created, send a network creation request to the VIM according to the connection information of the VIM, and when receiving the network creation success response returned by the VIM , sending a container deployment request to the container infrastructure manager CISM;

If the resource authorization response carries information about the created VL network, then send a container deployment request to the CISM.
The method according to claim 1, wherein obtaining a virtualized network function description VNFD file comprises:

receiving the virtualized network function VNF instance identifier creation request sent by the NFVO, wherein the VNF instance identifier creation request carries a virtualized network function description VNFD identifier;

Obtain the corresponding VNFD file according to the VNFD identifier.
The method according to claim 1 or 2, wherein the description information of the VL network includes description information of the type of the VL network, wherein the type of the VL network is used to indicate whether the VL network is The network between container cluster nodes.
The method according to any one of claims 1-3, wherein the VNFD file further includes the description information of the affinity or anti-affinity group and the description information of the virtual deployment unit VDU, wherein the affinity or anti-affinity The description information of the affinity group is used to indicate the corresponding relationship between the connection point CP of the VDU and the network interface of the container cluster node and the corresponding relationship between the VDU and the container cluster node, and the description information of the VDU is used to indicate that the VDU The contained container resource and CP and the CP of the VDU need to be connected to the VL network.
The method according to claim 4, wherein the description information of the affinity or anti-affinity group includes description information of the range of the CP of the VDU, wherein the range of the CP of the VDU is used to indicate the range of the CP of the VDU. Whether any two CPs of the above-mentioned VDU are connected to the network interface of the same container cluster node.
The method according to any one of claims 1-5, wherein sending a resource authorization request to the network function virtualization orchestrator NFVO also includes:

If it is determined that the VL network is a network between container cluster nodes, a resource authorization request is sent to the NFVO.
The method according to any one of claims 1-6, wherein the information of the VL network is used to indicate the network interface of the container cluster node that the VL network needs to connect to and the network interface of the container cluster node that needs to be connected The CP of the VDU.
The method according to any one of claims 1-7, wherein the network creation request is used to request to create the VL network and a network interface of a container cluster node to be connected to the VL network.
The method according to claim 8, wherein the container deployment request is used to request to deploy a container and connect the container to the VL network, and the container deployment request carries the created VL network and the VL network. The above VL network needs to connect to the information of the network interface of the container cluster node.
The method according to any one of claims 1-7, wherein the network creation request is used to request creation of the VL network.
The method according to claim 10, wherein the container deployment request is used to request to create a network interface of a container cluster node that needs to be connected to the VL network, deploy a container and connect the container to the VL network, so The container deployment request carries the connection information of the VIM and the information of the created VL network.
A containerized VNF deployment method is characterized in that it is applied to a network function virtualization orchestrator NFVO, including:

Send a virtualized network function VNF instance identifier creation request to the virtual network function manager VNFM, wherein the VNF instance identifier creation request carries a virtualized network function description VNFD identifier, and the VNFD file corresponding to the VNFD identifier includes a virtual connection VL network The description information of the VL network is used to indicate whether the VL network is a network between container cluster nodes;

receiving the resource authorization request sent by the VNFM, and sending a resource authorization response to the VNFM, wherein the resource authorization request carries the information of the VL network, and the resource authorization response carries the information of the virtual infrastructure manager VIM connection information.
The method according to claim 12, wherein sending a resource authorization response to the VNFM comprises:

Send the resource authorization response to the VNFM, so that the VNFM sends a network creation request to the VIM according to the connection information of the VIM, and when receiving the network creation success response returned by the VIM, send a request to the container base The facility manager CISM sends container deployment requests.
The method according to claim 12, wherein sending a resource authorization response to the VNFM further comprises:

Send a network creation request to the VIM;

When receiving the network creation success response returned by the VIM, send the resource authorization response to the VNFM, so that the VNFM sends a container deployment request to the CISM, wherein the resource authorization response carries the created information of the VL network.
The method according to claim 14, wherein sending a network creation request to the VIM includes:

Sending a network creation request to the VIM according to the connection information of the VIM, and receiving a network creation success response returned by the VIM; or,

Send a network creation request to the container cluster manager CCM, so that the CCM sends a network creation request to the VIM according to the connection information of the VIM, and receives a network creation success response returned by the VIM, wherein the network creation The successful response carries the connection information of the VIM.
The method according to claim 13, wherein the network creation request is used to request to create the VL network and a network interface of a container cluster node to which the VL network needs to be connected.
The method according to claim 16, wherein the container deployment request is used to request to deploy a container and connect the container to the VL network, and the container deployment request carries the created VL network and the VL network. The above VL network needs to connect to the information of the network interface of the container cluster node.
The method according to any one of claims 13-15, wherein the network creation request is used to request creation of the VL network.
The method according to claim 18, wherein the container deployment request is used to request to create a network interface of a container cluster node that needs to be connected to the VL network, deploy a container and connect the container to the VL network, so The container deployment request carries the connection information of the VIM and the information of the created VL network.
A device for deploying a containerized VNF, characterized in that the device includes a memory and a processor, wherein the memory is used to store computer instructions, and the processor is used to call the computer instructions stored in the memory to execute such as The containerized VNF deployment method described in any one of claims 1-11 or 12-19.
A computer-readable storage medium, characterized in that it includes a program or an instruction, and when the program or instruction is run on a computer, the containerized VNF according to any one of claims 1-11 or 12-19 The deploy method is executed.