WO2023046026A1 - Procédé et appareil de déploiement de vnf conteneurisée - Google Patents

Procédé et appareil de déploiement de vnf conteneurisée Download PDF

Info

Publication number
WO2023046026A1
WO2023046026A1 PCT/CN2022/120590 CN2022120590W WO2023046026A1 WO 2023046026 A1 WO2023046026 A1 WO 2023046026A1 CN 2022120590 W CN2022120590 W CN 2022120590W WO 2023046026 A1 WO2023046026 A1 WO 2023046026A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
container
request
vim
information
Prior art date
Application number
PCT/CN2022/120590
Other languages
English (en)
Chinese (zh)
Inventor
李世涛
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023046026A1 publication Critical patent/WO2023046026A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks

Definitions

  • the present application relates to the field of communication technologies, and in particular to a containerized VNF deployment method and device.
  • Network function virtualization 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.
  • NFV network function virtualization
  • 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 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.
  • VNF virtualized network function
  • 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 .
  • VDU virtualization deployment unit
  • CP connection point
  • VDU the VDU that the CP needs to connect to
  • VL the VL that the VNF needs to connect to .
  • the virtualization technology adopted by the NS during virtualization deployment is virtual machine technology
  • several VNFs contained in the NS are virtualized VNFs
  • 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
  • the existing technology can complete the deployment of containerized VNF through the container infrastructure service management (CISM) in the NFV architecture.
  • CISM container infrastructure service management
  • 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.
  • 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.
  • 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.
  • the embodiment of the present application provides a containerized VNF deployment method, which is applied to the virtual network function manager VNFM, including:
  • 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 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;
  • resource authorization response carries information about the created VL network, then send a container deployment request to the CISM.
  • VNFM 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
  • the VL network information is carried in the resource authorization request
  • 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.
  • the virtualized network function description VNFD file is obtained, including:
  • VNF instance identifier creation request sent by the NFVO, wherein the VNF instance identifier creation request carries a virtualized network function description VNFD identifier;
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • sending a resource authorization request to the network function virtualization orchestrator NFVO also includes:
  • VL network is a network between container cluster nodes
  • a resource authorization request is sent to the NFVO.
  • VL network 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.
  • 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.
  • 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.
  • 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.
  • the network creation request is used to request creation of the VL network.
  • 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.
  • the present application also provides a containerized VNF deployment method, which is applied to the network function virtualization orchestrator NFVO, including:
  • VNF instance identifier creation request carries a virtualized network function description VNFD identifier
  • 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;
  • 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.
  • sending a resource authorization response to the VNFM includes:
  • the facility manager CISM sends container deployment requests.
  • sending a resource authorization response to the VNFM also includes:
  • sending a network creation request to the VIM includes:
  • 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.
  • 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.
  • the network creation request is used to request creation of the VL network.
  • 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.
  • 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.
  • the acquisition module is specifically used for:
  • VNF instance identifier creation request sent by the NFVO, wherein the VNF instance identifier creation request carries a virtualized network function description VNFD identifier;
  • 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.
  • 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.
  • 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.
  • the first processing module is also used for:
  • VL network is a network between container cluster nodes
  • a resource authorization request is sent to the NFVO.
  • 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.
  • 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.
  • 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.
  • the network creation request is used to request creation of the VL network.
  • 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.
  • 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.
  • the second processing module is specifically used for:
  • the facility manager CISM sends container deployment requests.
  • the second processing module is specifically used for:
  • the second processing module is specifically used for:
  • 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.
  • 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.
  • the network creation request is used to request creation of the VL network.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • NFV orchestrator NFV orchestrator
  • VNFM virtualized network function manager
  • CISM virtualized infrastructure manager
  • VIM virtualized infrastructure manager
  • VNF 110 equipment management system
  • equipment management system equipment management system
  • EMS equipment management system
  • operations support system and business support system operations support system and business support system
  • operations support system and business support system operations support system and business support system
  • OSS/BSS operations support system and business support system
  • 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 .
  • NFVO102 can also communicate with VIM108, perform resource allocation, resource reservation, query virtualization hardware resource configuration and status information.
  • 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 .
  • 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.
  • CISM106 is mainly responsible for container resource management, including container creation, updating, query, scaling, terminating, etc.
  • 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 .
  • 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.
  • the management functions supported by BSS include product management, order management, revenue management, and customer management.
  • 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.
  • 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.
  • 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.
  • first and second are used to distinguish multiple objects, and are not used to limit the order, timing, priority or priority of multiple objects. Importance.
  • 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.
  • FIG. 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 .
  • 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.
  • the NFVO sends a VNF instance identifier creation request to the VNFM.
  • the VNFM receives the VNF instance ID creation request from the NFVO.
  • the VNF instance identifier creation request carries the VNFD identifier.
  • 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.
  • the NFVO receives the VNF instance identifier from the VNFM.
  • 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.
  • 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.
  • the description information of the VL network is used to indicate whether the VL network is a network between container cluster nodes
  • 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.
  • 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.
  • 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.
  • mciopId deployment package identifier
  • associatedVdu associatedVdu
  • 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).
  • the requested Cpu Resources of osContainerDesc-1 is 2.
  • the requested Memory Resources is 500MB.
  • 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.
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • FIG. 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.
  • 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.
  • the NFVO sends a VNF instantiation request to the VNFM.
  • the VNFM receives the VNF instantiation request from the NFVO.
  • the VNF instantiation request is used to request to create a VNF instance corresponding to the VNF instance identifier.
  • the VNFM sends a resource authorization request to the NFVO.
  • NFVO receives the resource authorization request from VNFM.
  • 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.
  • 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
  • the container cluster node VDU3 needs to be deployed on Node-2
  • osContainerDesc-5 needs to be deployed on VDU3
  • 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)
  • the addResource information includes resource definition (ResourceDefinition) information
  • the ResourceDefinition information is used to indicate the type and corresponding identifier of the resource, for example, the type is O
  • 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.
  • FIG. 2f it is a schematic diagram of a VL network provided by the embodiment of the present application.
  • 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.
  • VL network such as NIC-1, NIC-2, VL-1 network
  • the VL network 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.
  • the NFVO sends a resource authorization response to the VNFM.
  • VNFM receives the resource authorization response from NFVO.
  • 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.
  • GrantInfo will carry the connection information of the CISM
  • the GrantInfo will carry the connection information of the VIM.
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • VIM completes the creation of the VL-1 network
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • the container cluster node Node-1 and Deployment of containers on Node-2 and connection of containers to VL-1 network
  • the VNFM When receiving the container deployment success response returned by the CISM, the VNFM sends a VNF instantiation success response to the NFVO.
  • 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.
  • FIG 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.
  • the VL network between the container cluster nodes is completed by sending a request from the NFVO to the VIM
  • the creation of the network interface of the container cluster nodes is completed by sending a request to the VIM from the CISM.
  • the NFVO sends a VNF instance identifier creation request to the VNFM.
  • the VNFM receives the VNF instance ID creation request from the NFVO.
  • 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.
  • the NFVO receives the VNF instance identifier from the VNFM.
  • the NFVO sends a VNF instantiation request to the VNFM.
  • the VNFM receives the VNF instantiation request from the NFVO.
  • the VNFM sends a resource authorization request to the NFVO.
  • NFVO receives the resource authorization request from VNFM.
  • 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.
  • VNFM receives the resource authorization response from NFVO.
  • 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.
  • container cluster manager container identification system cluster manager, CCM
  • NFVO 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.
  • the VNFM sends a container deployment request to the CISM.
  • 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.
  • the VNFM sends a container deployment request to the CISM.
  • 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.
  • 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.
  • the VNFM When receiving the container deployment success response returned by the CISM, the VNFM sends a VNF instantiation success response to the NFVO.
  • 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 network not only meets the needs of telecom scenarios, but also reduces workload and avoids waste of resources.
  • 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 .
  • 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.
  • 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.
  • the above-mentioned NFVO or VNFM includes corresponding hardware structures and/or software modules for performing each function.
  • 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.
  • FIG. 4 shows a schematic structural diagram of a VNFM provided by an embodiment of the present application.
  • 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.
  • the acquiring module 401 is specifically used for:
  • VNF instance identifier creation request sent by the NFVO, wherein the VNF instance identifier creation request carries a virtualized network function description VNFD identifier;
  • 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.
  • 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.
  • 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.
  • the first processing module 402 is also configured to:
  • VL network is a network between container cluster nodes
  • a resource authorization request is sent to the NFVO.
  • 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.
  • 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.
  • 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.
  • the network creation request is used to request creation of the VL network.
  • 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.
  • FIG. 5 shows a schematic structural diagram of an NFVO provided by an embodiment of the present application.
  • 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.
  • the second processing module 502 is specifically configured to:
  • the facility manager CISM sends container deployment requests.
  • the second processing module 502 is specifically configured to:
  • the second processing module 502 is specifically configured to:
  • 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.
  • 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.
  • the network creation request is used to request creation of the VL network.
  • 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.
  • 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;
  • 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.
  • the memory 602 is located outside the device 600 .
  • 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 .
  • 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.
  • 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.
  • the processor mentioned in the embodiments of the present application may be implemented by hardware or by software.
  • the processor When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor When implemented by software, the processor may be a general-purpose processor implemented by reading software codes stored in a memory.
  • 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.
  • 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.
  • 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.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • double data eat SDRAM double data eat SDRAM
  • DDR SDRAM double data eat SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • serial DRAM serial link DRAM
  • SLDRAM direct memory bus random access memory
  • direct rambus RAM direct rambus RAM
  • 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.
  • 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 .
  • 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.
  • 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.
  • 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.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente demande divulgue un procédé et un appareil de déploiement de VNF conteneurisée, qui peut résoudre les problèmes techniques rencontrés dans la technologie existante lors du déploiement de VNF conteneurisées lorsque des exigences de scénario de télécommunication ne peuvent pas être satisfaites, ou, bien que des exigences de scénario de télécommunication puissent être satisfaites, un nouveau réseau ne peut pas être créé dynamiquement selon les besoins, ce qui entraîne une charge de travail excessive et un gaspillage de ressources de déploiement des VNF conteneurisées. Le procédé est appliqué à un VNFM, et comprend les étapes consistant à : acquérir un fichier VNFD ; envoyer une demande d'autorisation de ressource à un NFVO et recevoir une réponse d'autorisation de ressource renvoyée par le NFVO ; si la réponse d'autorisation de ressource ne contient pas d'informations concernant un réseau VL créé, envoyer une demande de création de réseau à un VIM selon des informations de connexion du VIM et envoyer une demande de déploiement de conteneur à un CISM lorsqu'une réponse de succès de création de réseau renvoyée par le VIM est reçue ; et si la réponse d'autorisation de ressource contient les informations concernant le réseau VL créé, envoyer une demande de déploiement de conteneur au CISM.
PCT/CN2022/120590 2021-09-27 2022-09-22 Procédé et appareil de déploiement de vnf conteneurisée WO2023046026A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111133879.3 2021-09-27
CN202111133879.3A CN115883283A (zh) 2021-09-27 2021-09-27 一种容器化vnf的部署方法及装置

Publications (1)

Publication Number Publication Date
WO2023046026A1 true WO2023046026A1 (fr) 2023-03-30

Family

ID=85720101

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/120590 WO2023046026A1 (fr) 2021-09-27 2022-09-22 Procédé et appareil de déploiement de vnf conteneurisée

Country Status (2)

Country Link
CN (1) CN115883283A (fr)
WO (1) WO2023046026A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116319322A (zh) * 2023-05-16 2023-06-23 北京国电通网络技术有限公司 电力设备节点通信连接方法、装置、设备和计算机介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020135799A1 (fr) * 2018-12-28 2020-07-02 华为技术有限公司 Procédé et dispositif d'instanciation de service vnf
CN111416727A (zh) * 2019-01-07 2020-07-14 中国移动通信有限公司研究院 Vnf上载实例化方法及装置
CN111949364A (zh) * 2019-05-16 2020-11-17 华为技术有限公司 容器化vnf的部署方法和相关设备
US20210194749A1 (en) * 2017-10-24 2021-06-24 Telefonaktiebolaget Lm Ericsson (Publ) Methods for Defining a Network Service Descriptor (NSD) for a Network Service (NS), and Network Functions Virtualization (NFV) Orchestrator (NFVO) using said NSD
CN113342456A (zh) * 2020-03-02 2021-09-03 中兴通讯股份有限公司 一种连接方法、装置、设备和存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210194749A1 (en) * 2017-10-24 2021-06-24 Telefonaktiebolaget Lm Ericsson (Publ) Methods for Defining a Network Service Descriptor (NSD) for a Network Service (NS), and Network Functions Virtualization (NFV) Orchestrator (NFVO) using said NSD
WO2020135799A1 (fr) * 2018-12-28 2020-07-02 华为技术有限公司 Procédé et dispositif d'instanciation de service vnf
CN111416727A (zh) * 2019-01-07 2020-07-14 中国移动通信有限公司研究院 Vnf上载实例化方法及装置
CN111949364A (zh) * 2019-05-16 2020-11-17 华为技术有限公司 容器化vnf的部署方法和相关设备
CN113342456A (zh) * 2020-03-02 2021-09-03 中兴通讯股份有限公司 一种连接方法、装置、设备和存储介质

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116319322A (zh) * 2023-05-16 2023-06-23 北京国电通网络技术有限公司 电力设备节点通信连接方法、装置、设备和计算机介质
CN116319322B (zh) * 2023-05-16 2023-09-12 北京国电通网络技术有限公司 电力设备节点通信连接方法、装置、设备和计算机介质

Also Published As

Publication number Publication date
CN115883283A (zh) 2023-03-31

Similar Documents

Publication Publication Date Title
EP3291499B1 (fr) Procédé et appareil pour extension de capacité de service de réseau
WO2017045471A1 (fr) Procédé et appareil d'acquisition d'informations de chaîne de service dans un système de cloud computing
US20190173802A1 (en) Sla-based resource allocation method and nfvo
WO2022206229A1 (fr) Procédé et appareil de traitement des données, dispositif et support de stockage.
WO2020177564A1 (fr) Procédé et appareil de gestion de cycle de vie de fonction réseau virtualisée (vnf)
WO2018072503A1 (fr) Procédé d'initiation de modification de logiciel, procédé et dispositif de publication de métadonnées
WO2021185083A1 (fr) Procédé et dispositif d'instanciation de vnf
WO2017185251A1 (fr) Procédé de détermination de vnfm et orchestrateur de virtualisation de fonction de réseau
WO2020108443A1 (fr) Procédé et dispositif de gestion de virtualisation
WO2021063130A1 (fr) Procédé et appareil de gestion de ressources de réseau, équipement de réseau et support de stockage lisible
WO2020211652A1 (fr) Procédé et dispositif de gestion de ressources de locataires dans un scénario à locataires multiples
US20230261950A1 (en) Method of container cluster management and system thereof
US11140091B2 (en) Openflow protocol-based resource control method and system, and apparatus
WO2023046026A1 (fr) Procédé et appareil de déploiement de vnf conteneurisée
US20220350637A1 (en) Virtual machine deployment method and related apparatus
WO2019001140A1 (fr) Procédé et dispositif de gestion d'instanciation de fonction de réseau virtualisée
EP4177742A1 (fr) Procédé et appareil de gestion multi-occupants
WO2021103657A1 (fr) Procédé, appareil et dispositif d'exécution d'opération sur un réseau, et support de stockage
WO2020135517A1 (fr) Procédé et dispositif de déploiement d'une fonction de réseau virtuel
CN114979286A (zh) 容器服务的访问控制方法、装置、设备及计算机存储介质
US20230105269A1 (en) Virtualized network service deployment method and apparatus
WO2023179580A1 (fr) Procédé, appareil et dispositif de déploiement de vnf
WO2019011180A1 (fr) Procédé et dispositif d'envoi de licence
WO2022126389A1 (fr) Procédé et dispositif d'établissement de connexion de réseau
WO2024114645A1 (fr) Procédé d'instanciation pour fonction de réseau de virtualisation (vnf), et appareil

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22872070

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE