WO2022028092A1 - 一种vnf实例化的方法和装置 - Google Patents

一种vnf实例化的方法和装置 Download PDF

Info

Publication number
WO2022028092A1
WO2022028092A1 PCT/CN2021/099147 CN2021099147W WO2022028092A1 WO 2022028092 A1 WO2022028092 A1 WO 2022028092A1 CN 2021099147 W CN2021099147 W CN 2021099147W WO 2022028092 A1 WO2022028092 A1 WO 2022028092A1
Authority
WO
WIPO (PCT)
Prior art keywords
vnf
container object
container
vnfm
request message
Prior art date
Application number
PCT/CN2021/099147
Other languages
English (en)
French (fr)
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 华为技术有限公司
Priority to EP21853168.9A priority Critical patent/EP4191907A4/en
Publication of WO2022028092A1 publication Critical patent/WO2022028092A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • 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
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
    • H04L41/0843—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on generic templates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H04L41/342—Signalling channels for network management communication between virtual entities, e.g. orchestrators, SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • 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
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method and apparatus for instantiating a VNF.
  • the ETSI NFV standard defines the information model of the network connection of the virtualized network function (Virtualized Network Function, VNF) based on the virtual machine (Virtual Machine, VM).
  • Figure 1 is a network service (Network Service, NS).
  • Composition diagram VNF is a member of NS
  • VNF internal network is a topology connection diagram composed of nodes and lines
  • nodes include components that make up VNF functions (VNF Component, VNFC)
  • lines include virtual links (Virtual links) connecting two VNFCs.
  • Link, VL The network topology inside the VNF is not visible to other members of the NS outside the VNF (eg, other VNFs or nested NSs).
  • VNF Descriptor VNF Descriptor
  • NS Descriptor NSD
  • VNFD virtualized Deployment Unit
  • VLD Virtual Link Descriptor
  • CPD Connection Point Descriptor
  • the NSD model defines the service templates of NS in the scenario of multiple deployment templates (Deployment Flavour, DF), and each service template can be deployed independently.
  • VNFD models the NFV objects required for managing VNF instances in the model template (Descriptor can be understood as a deployment template for NFV object lifecycle management):
  • VNFC is modeled as a Virtualized Deployment Unit (VDU).
  • VDU Virtualized Deployment Unit
  • a VNFC is instantiated according to the description information of the virtual resources defined in the VDU, and mapped to the computing and storage resources of a VM;
  • connection point of network service NS external interaction is called service access point, which is modeled as Service Access Point Descriptor (SAPD).
  • SAPD Service Access Point Descriptor
  • NSs interact with other NSs through Service Access Point (SAP) instances created by SAPD.
  • SAPD Service Access Point Descriptor
  • Container as a Service is a new type of virtualization technology in the process of cloud-oriented transformation of telecom operators' networks to Internet Technology (IT).
  • VNF Virtualised Network Function
  • MCIO Managed Container Infrastructure Object
  • container object managed Container infrastructure objects
  • life cycle management of containerized VNF is realized through the management of the container object it calls.
  • the current container network model is an IT flattening model, that is, the configuration of the container network mainly considers the requirements of network connections, and does not take into account the performance requirements of the VNFs (for example, 5G vertical industry applications) carried by the container network for network services. It has differentiated requirements, and differentiates the configuration of the container network according to different requirements. For example, during the instantiation process or the running state of the containerized VNF, how to generate the container object called by the containerized VNF, how to update the configuration, etc., there is no relevant description in the existing technology or standard.
  • Embodiments of the present invention provide a VNF instantiation method and device, which are used to solve the problems of how to generate container objects and how to update configurations.
  • the virtual network function manager VNFM receives the VNF instantiation request message sent by the network function virtualization orchestrator NFVO, and determines the QoS attribute of the external connection of the container object used by the VNF;
  • the VNFM sends a container object creation request message to the container infrastructure service management CISM, and the request message carries the QoS attribute of the external connection of the container object;
  • CISM receives the container object creation request message, reads the descriptor file and/or configuration file of the container object, creates the corresponding container object, and determines the connection channel type between the container object and the host node according to the QoS attribute of the external connection of the container object, Establish the corresponding type of connection channel;
  • the VNFM receives the container object creation response message returned by the CISM, and the VNFM returns the VNF instantiation response message to the NFVO to complete the VNF instantiation.
  • the VNFM when the VNFM receives the VNF instantiation request message sent by NFVO, it accesses the descriptor file VNFD of the VNF to be instantiated, reads the QoS attributes of the VNF internal virtual link from the VNFD, and according to the VNF internal virtual link
  • the QoS attribute of the container object to be created determines the QoS attribute of the external connection.
  • An embodiment of the present invention provides a container object creation method, including:
  • the container infrastructure service management CISM receives a container object creation request message sent by the virtual network function manager VNFM, where the request message carries the QoS attribute of the external connection of the container object;
  • CISM reads the descriptor file and/or configuration file of the container object, creates the corresponding container object, determines the connection channel type between the container object and the host node according to the QoS attribute of the external connection of the container object, and establishes the connection channel of the corresponding type.
  • the CISM receives the container object creation request message sent by the virtual network function manager VNFM,
  • VNFM receives the VNF instantiation request message sent by NFVO, accesses the descriptor file VNFD of the VNF to be instantiated, reads the QoS attribute of the virtual link inside the VNF from the VNFD, and determines the container according to the QoS attribute of the virtual link inside the VNF QoS properties for external connections of the object.
  • the present invention provides a virtual network function manager VNFM, including:
  • a receiving unit configured to receive a VNF instantiation request message sent by the network function virtualization orchestrator NFVO,
  • a processing unit used to determine the QoS attribute of the external connection of the container object to be created
  • a sending unit is used to send a container object creation request message to the container infrastructure service management CISM, and the QoS attribute of the external connection of the container object is carried in the request message;
  • a receiving unit for receiving the container object creation response message returned by the CISM
  • the sending unit is further configured to return a VNF instantiation response message to the NFVO to complete the VNF instantiation.
  • the present invention provides a container infrastructure service management device CISM, including:
  • a receiving unit configured to receive a container object creation request message sent by the virtual network function manager VNFM, where the request message carries the QoS attribute of the external connection of the container object;
  • the processing unit is used to read the descriptor file and/or configuration file of the container object, and create the corresponding container object; and determine the connection channel type between the container object and the host node according to the QoS attribute of the external connection of the container object to be created, and establish the corresponding type connection channel;
  • the sending unit is used to return a container object creation response message to the VNFM.
  • the embodiment of the present application also provides a physical device of a virtual network function manager VNFM, which is characterized by comprising: a processor and a memory; the processor is coupled to the memory, and the processor is configured to read and execute instructions in the memory, For performing the above method steps performed by the VNFM.
  • VNFM virtual network function manager
  • Embodiments of the present application further provide an entity device for container infrastructure service management CISM, which is characterized by comprising: a processor and a memory; the processor is coupled to the memory, and the processor is configured to read and execute instructions in the memory, For performing the above-mentioned method steps performed by the CIMS.
  • entity device for container infrastructure service management CISM which is characterized by comprising: a processor and a memory; the processor is coupled to the memory, and the processor is configured to read and execute instructions in the memory, For performing the above-mentioned method steps performed by the CIMS.
  • Embodiments of the present application also provide a computer-readable storage medium, including instructions, which, when executed on a computer, cause the computer to execute the method executed by the VNFM, NFVO, or CISM.
  • the differentiated performance requirements of the VNF network when the VNFM manages the VNF instance is transmitted to the CISM, so as to realize the dynamic generation or update of the container network, and quickly respond to the change of the performance requirements of the VNF network.
  • Fig. 1 is the composition schematic diagram of a kind of network service in the prior art
  • Figure 2 is the architecture diagram of the Kubernetes container management and orchestration system
  • FIG. 3 is a schematic diagram of an NFV architecture according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of an interworking requirement scenario of a container network according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of a method for instantiating a VNF according to Embodiment 1 of the present application
  • FIG. 6 is a flowchart of a method for updating a VNF provided in Embodiment 2 of the present application.
  • FIG. 7 is a schematic diagram of a VNFM device according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a CISM device provided by an embodiment of the present invention.
  • FIG. 9 is a hardware diagram of a VNFM/CISM device provided by an embodiment of the present invention.
  • Figure 2 is an architectural diagram of the Kubernetes (K8S) container management and orchestration system.
  • Kubernetes divides the infrastructure resources in a container cluster into a Kubernetes master node (master) and a group of worker nodes (Node).
  • master a set of processes related to container cluster management, such as Application Programming Interface Server (API Server), Replication Controller (RC), etc.
  • API Server Application Programming Interface Server
  • RC Replication Controller
  • These processes implement management functions such as resource management, pod scheduling, elastic scaling, security control, system monitoring, and error correction of the entire container cluster.
  • Run Kubelet, Proxy, and Docker three components on each worker node, which are responsible for managing the life cycle of the Pod on this node and implementing the function of service proxy.
  • a Pod can include at least one container, and a Pod can be understood as a container bin composed of one or more containers.
  • API Server provides the only operation entry for resource objects. All other components must operate resource data through the API interface provided by it, and complete related business functions through "full query” and “change monitoring” of related resource data. .
  • the Controller Manager is the management and control center of the container cluster. Its main purpose is to automate the fault detection and recovery of the Kubernetes cluster. For example, Pod can be copied or removed according to the definition of RC to ensure that the number of Pod instances conforms to the definition of RC, and the creation and update of endpoint objects of service, node discovery, management and status monitoring, as well as cleaning of locally cached image files, etc.
  • the Kubelet component is responsible for the creation, modification, monitoring, and deletion of Pods on this node throughout the life cycle management. At the same time, the Kubelet regularly reports the status information of this node to the API Server.
  • the Proxy component is used to implement the load balancing between the proxy of the service and the software mode.
  • the Docker component is the runtime environment for the container.
  • FIG. 3 is a schematic diagram of an NFV architecture.
  • the NFV architecture can implement various networks, such as Local Area Network (LAN), Internet Protocol (IP) network, or Evolved Packet Core (EPC) network.
  • LAN Local Area Network
  • IP Internet Protocol
  • EPC Evolved Packet Core
  • FIG. 3 is a deployment use case of an NFV MANO system management container cluster defined by the NFV industry standard group under the European Telecommunications Standards Institute (ETSI).
  • ETSI European Telecommunications Standards Institute
  • the deployment use case includes NFV-MANO 310, one or more operation support systems/business support systems (Operation Support System/Business Support System, OSS/BSS) 320, multiple network element management systems ( Element Manager, EM) 330, multiple VNFs 340, and NFV Infrastructure (NFVI) 350.
  • operation support systems/business support systems OEM Support System/Business Support System
  • OSS/BSS Operaation Support System/Business Support System
  • EM Network element management systems
  • VNFs 340 multiple VNFs 340
  • NFVI NFV Infrastructure
  • OSS/BSS 320 is mainly for telecom service operators, providing comprehensive network management and business operation functions, including network management (such as fault monitoring, network information collection, etc.), billing management, and customer service management.
  • the EM 330 is used to perform traditional Fault, Configuration, User, Performance and Security Management (Fault Management, Configuration Management, Account Management, Performance Management, Security Management, FCAPS) functions for VNFs.
  • the VNF 340 corresponds to a physical network function (Physical Network Function, PNF) in a traditional non-virtualized network, such as a virtualized Evolved Packet Core (EPC) node (eg, Mobility Management Entity, MME), Serving Gateway (SGW), Public Data Network Gateway (Public Data Network Gateway, PGW, etc.).
  • EPC Evolved Packet Core
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • Public Data Network Gateway Public Data Network Gateway
  • PGW Public Data Network Gateway
  • VNF 340 can be composed of one or more container objects.
  • a container object can be understood as a pod in Figure 2, and each pod can be deployed in a container cluster node resource pool, and the resources in each container cluster node resource pool It can be a virtual machine (Virtual Machine, VM) or a bare metal (Bare Metal) server, and each VM hosts one or more container objects.
  • VM Virtual Machine
  • Bare Metal bare metal
  • the NFVI 350 may include a virtual resource layer.
  • the virtual resource layer may include multiple VMs, and the multiple VMs may be used to form one or more container cluster node resource pools.
  • NFV-MANO 310 may include NFV orchestrator (NFVO) 311, one or more VNFMs 312, Container Infrastructure Service Management (CISM) 313, and Virtualized Infrastructure Manager (VIM) )314.
  • NFVO NFV orchestrator
  • VNFMs one or more VNFMs
  • CISM Container Infrastructure Service Management
  • VIP Virtualized Infrastructure Manager
  • NFVO is used to realize the management and processing of network service descriptor (NSD), virtual network function forwarding graph (VNF forwarding graph, VNFFG), management of network service life cycle, and cooperate with VNFM to realize VNF Global view capabilities for lifecycle management and virtual resources.
  • NSD network service descriptor
  • VNF forwarding graph VNFFG
  • VNFM virtual network function forwarding graph
  • VNFM implements VNF life cycle management, including management of virtualized network function descriptors (VNF descriptor, VNFD), VNF instantiation, elastic scaling of VNF instances (including scaling out/up) and scaling (Scaling in/ down)), the healing of the VNF instance (Healing), and the termination of the VNF instance.
  • VNFM also supports receiving the elastic scaling (Scaling) policy issued by NFVO to realize automatic VNF elastic scaling.
  • VIM is mainly responsible for resource management (including reservation and allocation) in NFVI, monitoring of virtual resource status and fault reporting, and providing virtualized resource pools for upper-layer applications.
  • the ETSI NFV standard has introduced the function of container management into the NFV-MANO framework since Release 3, and defined the functional requirements of the northbound service-oriented interface of the container infrastructure service management CISM to support the lifecycle management of VNF based on container implementation.
  • the CISM can also be called CaaS management, which is responsible for managing the container objects called by the VNF, including the creation, updating and deletion of container objects, and dispatching the container objects to the corresponding VMs in the container cluster node resource pool managed by the CISM.
  • the node resources include computing resources, storage resources, and network resources.
  • the VNF network connection model is to superimpose a layer of container network on the basis of the existing virtual machine network model.
  • the container network connection model of VNF describes the network connection between container objects (also called managed container infrastructure objects, Managed Container Infrastructure Object, MCIO) in the abstract container object layer, as well as the container objects and the containers that support the operation of the container objects. Interconnection between cluster nodes (eg, virtual machines or bare metal).
  • VNF components are mapped to MCIOs that request computing/storage resources (for example, Kubernetes Pod objects), and VNF external connection points (External CPs) are mapped to MCIOs that request network resources (for example, K8S network endpoint objects, Usually attached to the MCIO mapped by the VNFC).
  • computing/storage resources for example, Kubernetes Pod objects
  • VNF external connection points External CPs
  • network resources for example, K8S network endpoint objects, Usually attached to the MCIO mapped by the VNFC.
  • the container network management function is an autonomous management function that does not require the participation of NFVO or VNFM, and CISM accesses it by itself
  • the MCIO descriptor file (MCIO Descriptor) and/or the MCIO configuration file (MCIO configuration files) realizes the automatic configuration of the MCIO internal network and the network between MCIOs. Therefore, there is no MCIO corresponding to the VNF internal connection point (Internal CP) or the VNF internal virtual link (Internal VL) in the abstract container object layer, so there is no need to map the VNF internal connection point and the VNF internal virtual link in the VNFD.
  • MCIO for specific requests for network resources.
  • the containerized VNF is deployed on two container cluster nodes, CIS Cluster Node 1 and CIS Cluster Node 2 (Note: CIS is called Container Infrastructure Service in English).
  • CIS is called Container Infrastructure Service in English.
  • One part of VNFC is mapped to MCIO on CIS Cluster Node 1 (Pod1 and Pod2 in Figure 4), and the other part of VNFC is mapped to MCIO on CIS Cluster Node 2 (Pod3 and Pod4 in the figure).
  • These MCIOs are carried by one or more OS containers to carry the workloads in MCIO, and CIS Cluster Node 1 and CIS Cluster Node 2 each represent a virtual machine.
  • the Inter-Node network does not belong to the network autonomously configured by the CISM, and this segment of the network is usually still configured by the Virtualised Infrastructure Manager (VIM).
  • VIM Virtualised Infrastructure Manager
  • CISM completes the configuration of network connections between OS containers within MCIO, as well as the configuration of network connections between MCIOs of the same node.
  • the interworking requirements of the container network include four basic scenarios: container object MCIO (ie: Pod in the figure) accesses the external network, intra-node MCIO mutual access, inter-node MCIO mutual access, and external network access to MCIO.
  • the external network includes the physical network (Physical Network) or the infrastructure network (Infrastructure Network) in Figure 4.
  • the container object MCIO to access the external network or the external network to access MCIO please refer to the connection channels 41 of node 1 in Figure 4 (the connection between the virtual Ethernet port of the container object Pod1 and the Ethernet port of the host node 1) and 46 (the host node 1).
  • connection channel 47 and 43 or 47 and 44 constitute a channel in node 2.
  • connection channel 45 in FIG. 4 For intra-node mutual access, refer to connection channel 45 in FIG. 4; for inter-node mutual access, refer to connection channels 41, 46, 47 and 43 in FIG. 4, which together form a channel for inter-node mutual access.
  • Figure 4 is just a functional illustration, and the actual connection channel can adopt different establishment or connection methods.
  • the current container network model is an IT flattening model, that is, the configuration of the container network mainly considers the requirements of network connections, and does not take into account the performance requirements of the VNFs (for example, 5G vertical industry applications) carried by the container network for network services. There are differentiated requirements, and the configuration of the container network is differentially processed according to different requirements.
  • VNFs for example, 5G vertical industry applications
  • the VNF external connection point refers to an endpoint connecting a VNF instance and an external function, and the external function may be other VNF instances or nested NS instances of the NS instance to which the VNF instance belongs.
  • the VNF network performance requirements can include but It is not limited to the definition of requirements for the quality of service (Quality of Service, QoS) and reliability indicators such as availability and security of the VNF virtual link VL or connection point CP.
  • QoS usually refers to performance indicators such as bandwidth, delay, jitter, and packet loss rate transmitted by network nodes or links.
  • Embodiment 1 of the present invention relates to a containerized VNF instantiation method, which preserves the flatness of the container object layer network configuration (that is, the network configuration process only considers the connectivity of the container network), through the container cluster nodes (for example: virtual machine ) network configuration update to dynamically adapt to changes in VNF network performance, combined with the CISM function to manage the autonomy of the container network, the VNFM manages the life cycle of the VNF instance. Network generation or update to quickly respond to changes in VNF network performance requirements.
  • a method for instantiating a VNF provided in Embodiment 1 of the present invention includes the following steps:
  • the NFVO sends a VNF instantiation request to the VNFM, and the request message carries the identification information of the VNF instance.
  • the VNFM accesses the descriptor file VNFD of the VNF to be instantiated according to the identification information in step S501, reads the quality of service (QoS) attribute of the VNF internal virtual link (Internal Virtual Link, Int-VL) from the VNFD, and according to The QoS attribute of the virtual link inside the VNF determines the QoS attribute of the container object MCIO external connection used by the VNF.
  • QoS quality of service
  • the QoS attributes of the internal virtual link include requirements on the bandwidth, delay, jitter and/or packet loss rate of the internal virtual link transmission in the VNF.
  • the external connection of the container object is the connection established between the port (Virtual Ethernet, Veth) of the container object (each Pod in the figure) and the port (eth0, eth1) of the host node in FIG. 4 .
  • the QoS attribute of the external connection of the container object needs to match the QoS attribute of the internal virtual link of the VNF, and the difference cannot be too large, so as to meet the transmission performance requirements of the VNF instance; Actually, it is necessary to pre-establish a correspondence table between the QoS attributes of the external connection of the container object and the QoS attributes of the internal virtual links of the VNF, and specifically determine the QoS attributes of the MCIO external connection to be created according to the table.
  • the specific implementation manners are various and will not be repeated here.
  • the VNFM sends a container object (MCIO) creation request message to the container infrastructure service management (Container Infrastructure Service Management, CISM), and the request message carries the QoS attributes of the external connection of the container object used by the VNF to be instantiated.
  • MCIO container object
  • CISM Container Infrastructure Service Management
  • a VNF uses multiple MCIOs, multiple MCIOs need to be created, and the creation request may carry the identifiers of the multiple MCIOs to be created.
  • S504 CISM receives the container object creation request message, reads the descriptor file of the container object and/or the configuration file of the container object, and creates a corresponding container object; and according to the QoS attribute of the external connection of each container object in the request message in S503 Determine the type of the connection channel between each container object and the host node, and establish the corresponding connection channel (41, 42, 43 and 44).
  • connection channel between the container object and the host node can be realized by configuring the container network interface (Container Network Interface, CNI) plug-in of the container object, and different types of connection channels realize the MCIO external connection with different QoS attributes.
  • the connection channel type may include: Data Plane Development Kit (DPDK), NIC direct connection, virtual local area network (Virtual Local Area Network, VLAN) or virtual extensible local area network (Virtual eXtensible Local Area Network, VXLAN), the transmission delay of the above types of transmission channels gradually increases from low to high.
  • CISM determines the type of connection channel using DPDK according to the QoS attribute of the external connection of container object 1 (Pod1 in the figure) to be created, and establishes a corresponding type of connection channel; CISM according to the external connection of container object 2 to be created (Pod2 in the figure) external The QoS attribute of the connection determines the type of connection channel using VXLAN, and establishes the corresponding type of connection channel; CISM determines the type of connection channel using VXLAN according to the QoS attribute of the external connection of container object 3 (Pod3 in the figure) to be created, and establishes the corresponding type of connection channel. connection channel; and the CISM determines the connection channel type using VLAN according to the QoS attribute of the external connection of the container object 4 (Pod4 in the figure) to be created, and establishes the connection channel of the corresponding type.
  • DPDK implements data packet processing by polling
  • container applications VNF
  • VNF container applications
  • Network card direct connection (the network card vNIC of the container object and the network card vNIC of the host VM are directly connected through a network cable) is also a commonly used data acceleration technology, which sacrifices some reliability in exchange for data packet transmission performance.
  • VLANs communicate with each other through layer 3 routers to achieve LAN-level transmission performance.
  • VXLAN is an extension of XLAN.
  • connection channel with lower transmission delay (eg, DPDK) has a narrower scope of application, and additional constraints and restrictions on reliability are added.
  • a type of connection channel with higher transmission delay eg VXLAN has wider application range.
  • the above connection channel belongs to the specific physical implementation of the external connection of the container object. As mentioned above, since the connection channel itself has different types, the QoS attributes of different types of connection channels are fixed, and QoS does not need to be updated.
  • the host node of the container object can be a virtual machine or a bare metal server.
  • the CISM binds the IP address of the container object MCIO and the identifier of the connection channel between the container object of the type determined in S504 and the host node.
  • CISM binds the IP address of the container object to the VXLAN tunnel endpoint, and all packets in the container object are sent and received between the VXLAN tunnel endpoint and the endpoint of the host node.
  • the IP address of MCIO is fixed to the external presentation of MCIO.
  • the "binding" here is to associate the IP address with the VXLAN tunnel endpoint it uses through configuration operations within the same MCIO, and the two configuration information is attached to the same MCIO object.
  • CNI Consumer Network Interface
  • the CISM returns a container object creation response to the VNFM.
  • the response message may carry the identifier of the connection channel between the container object and the host node.
  • the VNFM will use the identifier and the connection channel between the container object and the host node obtained in step S506 and The External Connection Point of the VNF is bound.
  • binding can be understood as the container object is associated with the external connection point of the VNF through the connection channel with the host node, and communicates with the outside through the external connection point.
  • VNFM returns a VNF instantiation response to the NFVO, and the VNF instantiation process ends.
  • Embodiment 2 of the present invention relates to a containerized VNF update method.
  • the VNF External CP update is performed, and the container cluster node network dynamically adapts to the VNF network performance requirements.
  • This embodiment reflects how the container cluster node network dynamically updates the configuration to adapt to the changes in the performance requirements of the VNF network when the VNF instance is running (the state of the VNF instance after the VNF instantiation process has been completed).
  • a typical scenario is the process of performing a VNF external connection point update during the NS update process.
  • Embodiment 2 The specific steps of Embodiment 2 are shown in Figure 6.
  • the main difference from Embodiment 1 is that the VNFM does not read the QoS attribute of the virtual link inside the VNF by accessing the VNFD, but determines the VNF through the QoS attribute of the external connection point of the VNF The QoS properties of the external connection of the container object used.
  • the NFVO sends an update external VNF connection request message to the VNFM, and the request message carries the QoS attribute to be updated of the external connection point of the VNF instance.
  • the VNFM determines the QoS attribute of the external connection of the container object to be updated according to the QoS attribute of the external connection point of the VNF instance.
  • the QoS attribute of the internal virtual link includes the requirements for the bandwidth, delay, jitter and/or packet loss rate of the internal link transmission, and the container object MCIO to be created is determined according to the QoS attribute of the internal virtual link of the VNF (Fig. Pod) QoS attributes for external connections.
  • the external connection QoS attributes of the container object need to match the QoS attributes of the external connection points of the VNF instance, which cannot be too different, and can meet the transmission performance requirements of the VNF instance.
  • the VNFM sends a container object (MCIO) update request to the container infrastructure service management (Container Infrastructure Service Management, CISM), and the update request message carries the QoS attribute of the external connection of the container object to be updated.
  • MCIO container object
  • CISM Container Infrastructure Service Management
  • the CISM re-determines the type of the connection channel between the container object and the host node according to the QoS attribute of the external connection of the container object to be updated determined in S602, and establishes a corresponding connection channel.
  • connection channel type of the re-determined container object and the host node is the same as the existing connection channel type, it will not be updated, otherwise it will be updated to a new connection channel type.
  • connection channel please refer to the description of Embodiment 1 for details.
  • S605 The CISM binds the IP address of the container object (MCIO) with the identifier of the connection channel between the container object and the host node re-determined in S604.
  • the CISM returns a container object update response message to the VNFM.
  • the update response message may carry the identifier of the connection channel between the updated container object and the host node.
  • the VNFM will use the identifier and the connection channel between the container object and the host node obtained in step S606.
  • the External Connection Point of the VNF is bound.
  • VNFM returns an external VNF connection update response to the NFVO, and the VNF external connection point update process ends.
  • VNFM device 7 is a schematic diagram of a virtual network function manager VNFM device, the device includes:
  • the receiving unit 710 may be used to perform step S501 in the embodiment 1 shown in FIG. 5 , or may be used to perform step S601 in the embodiment shown in FIG. other processes.
  • the processing unit 720 may be used to perform steps S502 and S507 in the embodiment 1 shown in FIG. 5 , or may be used to perform steps S602 and S607 in the embodiment shown in FIG. 6 , and/or be used to support the Other procedures of the described techniques.
  • the sending unit 730 may be used to perform step S503 in the embodiment 1 shown in FIG. 5 , or may be used to perform step S603 in the embodiment shown in FIG. other processes.
  • FIG. 8 is a schematic diagram of a CISM device, the device includes:
  • the receiving unit 810 may be used to perform step S503 in the embodiment 1 shown in FIG. 5 , or may be used to perform step S603 in the embodiment shown in FIG. other processes;
  • the processing unit 820 may be used to perform steps S504 and S505 in the embodiment 1 shown in FIG. 5 , or may be used to perform steps S604 and S605 in the embodiment shown in FIG. 6 , and/or be used to support the other processes of the described technology;
  • the sending unit 830 may be used to perform step S506 in the embodiment 1 shown in FIG. 5 , or may be used to perform step S606 in the embodiment shown in FIG. other processes.
  • FIG. 9 is a hardware diagram of a VNFM apparatus provided by an embodiment of the present invention.
  • the apparatus 90 may include: a processor, a communication interface, and a memory.
  • the processor 91 may include one or more processing units, and the processing unit may be a central processing unit (English: central processing unit, CPU) or a network processor (English: network processor, NP) or the like.
  • the processing unit may be a central processing unit (English: central processing unit, CPU) or a network processor (English: network processor, NP) or the like.
  • the communication interface 94 is used to connect and exchange information with other communication devices, including receiving and sending corresponding messages; the network device 90 may also include a memory 93, and the processor 91 may be connected to the memory 93 and the communication interface 94 through a bus.
  • the memory 93 may be used to store software programs, which may be executed by the processor 91 to implement the method steps performed by the VNFM in the embodiment shown in FIG. 5 or FIG. 6 .
  • the memory 93 can also store various types of service data or user data, including various application instances and service status data in the above method steps.
  • the apparatus 90 may further include an output device 95 and an input device 97 .
  • An output device 95 and an input device 97 are connected to the processor 91 .
  • the output device 95 may be a display for displaying information, a power amplifier device or a printer for playing sound, etc.
  • the output device 95 may also include an output controller for providing output to a display screen, a power amplifier device or a printer.
  • Input device 97 may be a device such as a mouse, keyboard, electronic stylus, or touch panel for user input, and may also include an output controller for receiving and processing data from the mouse, keyboard, electronic stylus, or touch panel. Input from devices such as a stylus or touch panel.
  • the above device hardware diagram is also applicable to CISM and other related devices, the difference is that the software programs stored in the memory 93 of the two are different, and the software program stored in the memory 93 of the CISM device is executed by the processor 91 to implement Embodiment 1 or The method steps performed by the CISM device in 2 are not repeated here.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server or data center by wired (eg coaxial cable, optical fiber, Digital Subscriber Line, DSL) or wireless (eg: infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media.
  • the available media may be magnetic media (eg: floppy disk, hard disk, magnetic tape), optical media (eg: Digital Versatile Disc (DVD)), or semiconductor media (eg: Solid State Disk (SSD)) )Wait.

Landscapes

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

Abstract

本发明实施例涉及一种VNF的实例化方法和装置，包括：VNFM接收NFVO发送的VNF实例化请求消息，确定VNF使用的容器对象外部连接的QoS属性；VNFM向CISM发送容器对象创建请求消息，在请求消息中携带容器对象外部连接的QoS属性；CISM接收容器对象创建请求消息，CISM读取容器对象的描述符文件和/或配置文件，创建相应的容器对象；并根据待创建容器对象外部连接的QoS属性确定容器对象和宿主节点之间的连接通道类型，建立相应的连接通道。通过本发明实施例的方法，将VNFM管理VNF实例时对VNF网络差异化的性能需求传递到CISM，实现动态的容器网络生成或更新，快速响应VNF网络性能需求的变化。

Description

一种VNF实例化的方法和装置
本申请要求于2020年8月3日提交中国国家知识产权局、申请号为202010768159.3、申请名称为“一种VNF实例化的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种VNF的实例化方法及装置。
背景技术
当前，ETSI NFV标准定义了基于虚拟机(Virtual Machine,VM)实现的虚拟化网络功能(Virtualized Network Function,VNF)的网络连接的信息模型，图1是一种网络服务(Network Service,NS)的组成示意图，VNF是NS的组成成员，VNF内部网络是由节点和线组成的拓扑连接图，节点包括组成VNF功能的组件(VNF Component,VNFC)，线包括连接两个VNFC的虚拟链路(Virtual Link,VL)。VNF内部的网络拓扑结构对VNF之外的NS的其他成员(例如，其他的VNF或嵌套NS)不可见。
VNF描述符文件(VNF Descriptor,VNFD)和NS描述符文件(NS Descriptor,NSD)是ETSI NFV标准定义的两类主要的NFV对象VNF和NS的模型模板。VNFD模型中定义了虚拟化部署单元(Virtualized Deployment Unit,VDU)、虚拟链路描述符文件(Virtual Link Descriptor,VLD)和连接点描述符文件(Connection Point Descriptor,CPD)等对象模板，并使用policy描述VNF弹性伸缩、亲和性、安全组的策略。NSD模型定义了在多个部署模板(Deployment Flavour,DF)的场景下NS的服务模板，每个服务模板都可以独立部署。
VNFD从功能部署和运维的视角在模型模板(Descriptor可以理解为用于NFV对象生命周期管理的一种部署模板)中对管理VNF实例所需的NFV对象进行建模：
VNFC被建模为虚拟化部署单元(Virtualized Deployment Unit,VDU)。一个VNFC按照VDU中定义的虚拟资源的描述信息进行实例化，并映射为一个VM的计算和存储资源；
网络服务NS对外交互的连接点称为服务接入点，被建模为服务接入点描述符文件(Service Access Point Descriptor,SAPD)。NS通过由SAPD创建的服务接入点(SAP)实例和其他NS进行交互。
容器即服务(Container as a Service，CaaS)是电信运营商网络在面向互联网技术(Internet Technology,IT)的云化转型过程中的一种新型的虚拟化技术。在CaaS技术中，虚拟网络功能(Virtualised Network Function，VNF)调用一个或多个被管理的容器基础设施对象(Managed Container Infrastructure Object,MCIO,后面简称：容器对象)来实现它的功能，形成容器化VNF，容器化VNF的生命周期管理通过它所调用的容器对象的管理来实现。
当前的容器网络模型是一个IT扁平化的模型，即：容器网络的配置主要考虑了网络连接 的需求，没有结合考虑容器网络所承载的VNF(例如，5G垂直行业应用)对网络服务的性能需求具有差异化的需求，并根据不同的需求对容器网络的配置进行差异化处理。例如，在容器化VNF实例化过程中或运行态时，其调用的容器对象如何生成、配置如何更新等，现有技术或标准没有相关描述。
发明内容
本发明实施例提供一种VNF的实例化方法及装置，用以解决容器对象如何生成、配置如何更新的问题。
本发明实施例提供的一种VNF的实例化方法，包括：
虚拟网络功能管理器VNFM接收网络功能虚拟化编排器NFVO发送的VNF实例化请求消息，确定VNF使用的容器对象外部连接的服务质量QoS属性；
VNFM向容器基础设施服务管理CISM发送容器对象创建请求消息，在请求消息中携带所述容器对象外部连接的QoS属性；
CISM接收容器对象创建请求消息，读取容器对象的描述符文件和/或配置文件，创建相应的容器对象，并根据容器对象外部连接的QoS属性确定容器对象和宿主节点之间的连接通道类型，建立相应类型的连接通道；
VNFM接收CISM返回的容器对象创建应答消息，VNFM向NFVO返回VNF实例化应答消息，完成VNF实例化。
其中，当VNFM接收到NFVO发送的VNF实例化请求消息后，访问待实例化VNF的描述符文件VNFD，从VNFD中读取VNF内部虚拟链路的服务质量QoS属性，并根据VNF内部虚拟链路的QoS属性确定待创建的容器对象外部连接的QoS属性。
本发明实施例提供了一种容器对象创建方法，包括：
容器基础设施服务管理CISM接收虚拟网络功能管理器VNFM发送的容器对象创建请求消息，所述请求消息中携带容器对象外部连接的QoS属性；
CISM读取容器对象的描述符文件和/或配置文件，创建相应的容器对象，并根据容器对象外部连接的QoS属性确定容器对象和宿主节点之间的连接通道类型，建立相应类型的连接通道。
其中，在CISM接收虚拟网络功能管理器VNFM发送的容器对象创建请求消息之前，
VNFM接收NFVO发送的VNF实例化请求消息，访问待实例化VNF的描述符文件VNFD，从VNFD中读取VNF内部虚拟链路的服务质量QoS属性，并根据VNF内部虚拟链路的QoS属性确定容器对象外部连接的QoS属性。
本发明提供了一种虚拟网络功能管理器VNFM，包括：
接收单元，用于接收网络功能虚拟化编排器NFVO发送的VNF实例化请求消息，
处理单元,用于确定待创建的容器对象外部连接的QoS属性；
发送单元，用于向容器基础设施服务管理CISM发送容器对象创建请求消息，在请求消 息中携带容器对象外部连接的QoS属性；
接收单元，用于接收CISM返回的容器对象创建应答消息；
所述发送单元，还用于向NFVO返回VNF实例化应答消息，完成VNF实例化。
本发明提供了一种容器基础设施服务管理装置CISM，包括：
接收单元，用于接收虚拟网络功能管理器VNFM发送的容器对象创建请求消息，所述请求消息中携带容器对象外部连接的QoS属性；
处理单元，用于读取容器对象的描述符文件和/或配置文件，创建相应的容器对象；并根据待创建容器对象外部连接的QoS属性确定容器对象和宿主节点的连接通道类型，建立相应类型的连接通道；
发送单元，用于向VNFM返回容器对象创建应答消息。
本申请实施例中还提供一种虚拟网络功能管理器VNFM的实体装置，其特征在于，包括：处理器和存储器；处理器与存储器耦合，处理器被配置为读取并执行存储器中的指令，用于执行上述由VNFM执行的方法步骤。
本申请实施例中还提供一种容器基础设施服务管理CISM的实体装置，其特征在于，包括：处理器和存储器；处理器与存储器耦合，处理器被配置为读取并执行存储器中的指令，用于执行上述由CIMS执行的方法步骤。
本申请实施例中还提供一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行VNFM或NFVO或CISM所执行的方法。
通过本发明实施例的方法，将VNFM管理VNF实例时对VNF网络差异化的性能需求传递到CISM，实现动态的容器网络生成或更新，快速响应VNF网络性能需求的变化。
附图说明
图1是现有技术一种网络服务的组成示意图；
图2为Kubernetes容器管理编排系统的架构图；
图3为本发明实施例提供的一种NFV架构示意图；
图4为本发明实施例提供的一种容器网络的互通需求场景示意图；
图5为本申请实施例1提供的一种实例化VNF的方法流程图；
图6为本申请实施例2提供的一种VNF的更新方法流程图；
图7是本发明实施例提供的一种VNFM装置示意图；
图8是本发明实施例提供的一种CISM装置示意图；
图9是本发明实施例提供的一种VNFM/CISM装置硬件图。
具体实施方式
为了使本申请实施例的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施例作进一步地详细描述。
请参考图2，图2为Kubernetes(K8S)容器管理编排系统的架构图。
Kubernetes将容器集群中的基础设施资源划分为一个Kubernetes主节点(master)和一群工作节点(Node)。其中，主节点(也称管理节点)上运行着容器集群管理相关的一组进程，例如，应用程序编程接口服务(Application Programming Interface Server，API Server)、复制控制器(Replication Controller，RC)等，这些进程实现了整个容器集群的资源管理、容器仓(Pod)调度、弹性伸缩、安全控制、系统监控和纠错等管理功能。在每个工作节点上运行Kubelet,Proxy,Docker三个组件，负责对本节点上的Pod的生命周期进行管理，以及实现服务代理的功能。如图2所示，一个Pod中可以包括至少一个容器，则一个Pod可以理解为一个或多个容器组成的容器仓。
其中，API Server提供了资源对象的唯一操作入口，其他所有组件都必须通过它提供的API接口来操作资源数据，通过对相关的资源数据“全量查询”以及“变化监听”，完成相关的业务功能。
Controller Manager是容器集群的管理控制中心，其主要目的是实现Kubernetes集群的故障检测和恢复自动化工作。例如，可以根据RC的定义完成Pod的复制或移除，以确保Pod实例数符合RC的定义、根据服务(Service)与Pod的管理关系，完成service的端点(Endpoints)对象的创建和更新、node的发现、管理和状态监控、以及本地缓存的镜像文件的清理等。
Kubelet组件负责本节点上的Pod的创建、修改、监控、删除等全生命周期管理，同时Kubelet定时向API Server上报本节点的状态信息。
Proxy组件用于实现service的代理与软件模式的负载均衡。
Docker组件为容器的运行环境。
请参考图3，为一种NFV架构的示意图。该NFV架构可以实现多种网络，例如局域网(Local Area Network，LAN)、互联网协议(Internet Protocol，IP)网络或者演进分组核心网(Evolved Packet Core，EPC)网络等。
随着虚拟化技术的不断发展，业界提出了在NFV管理编排(Management and Orchestration，MANO)的参考架构内引入容器管理。请参考图3，为在欧洲通信标准协会(European Telecommunications Standards Institute，ETSI)的下属的NFV行业标准组定义的一种NFV MANO系统管理容器集群的部署用例。
如图3所示，在该部署用例中包括NFV-MANO 310、一个或多个运营支撑系统/业务支撑系统(Operation Support System/Business Support System，OSS/BSS)320、多个网元管理系统(Element Manager，EM)330、多个VNF340以及NFV基础设施(NFV Infrastructure，NFVI)350。
OSS/BSS 320主要面向电信服务运营商，提供综合的网络管理和业务运营功能，包括网络管理(例如故障监控、网络信息收集等)、计费管理以及客户服务管理等。
EM 330用于针对VNF执行传统的故障、配置、用户、性能和安全管理(Fault Management,Configuration Management,Account Management,Performance Management,Security Management，FCAPS)功能。
VNF 340对应于传统非虚拟化网络中的物理网络功能(Physical Network Function，PNF)，如虚拟化的演进分组核心网(Evolved Packet Core，EPC)节点(例如，移动性管理实体(Mobility Management Entity，MME)，服务网关(Serving Gateway，SGW)，公用数据网网关(Public Data Network Gateway，PGW)等)。网络功能的功能性行为和状态与虚拟化与否无关，NFV技术需求希望VNF和PNF拥有相同的功能性行为和外部接口。
VNF 340可以由一个或多个容器对象来组成，一个容器对象可以理解为图2中的pod， 而每个pod可以部署在一个容器集群节点资源池中，每个容器集群节点资源池中的资源可以是虚拟机(Virtual Machine，VM)或者裸金属(Bare Metal)服务器，每个VM承载一个或多个容器对象。
NFVI 350可以包括虚拟资源层。该虚拟资源层中可以包括多个VM，该多个VM可用于形成一个或多个容器集群节点资源池。
NFV-MANO 310可以包括NFV编排器(NFV orchestrator，NFVO)311，一个或多个VNFM312，容器基础设施服务管理(Container Infrastructure Service Management，CISM)313，以及虚拟基础设施管理器(Virtualized Infrastructure Manager，VIM)314。
其中，NFVO用于实现网络服务描述符(network service descriptor，NSD)，虚拟网络功能转发图(VNF forwarding graph，VNFFG)的管理及处理，网络服务生命周期的管理，以及，和VNFM配合实现VNF的生命周期管理和虚拟资源的全局视图功能。
VNFM实现VNF的生命周期管理，包括虚拟化网络功能描述符(VNF descriptor，VNFD)的管理、VNF的实例化、VNF实例的弹性伸缩(包括扩容(Scaling out/up)和缩容(Scaling in/down))、VNF实例的治愈(Healing)以及VNF实例的终止。VNFM还支持接收NFVO下发的弹性伸缩(Scaling)策略，实现自动化的VNF弹性伸缩。
VIM主要负责NFVI中资源的管理(包括预留和分配)，虚拟资源状态的监控和故障上报，面向上层应用提供虚拟化资源池。
ETSI NFV标准从Release 3开始在NFV-MANO框架中引入了容器管理的功能，并定义了容器基础设施服务管理CISM的北向服务化接口的功能需求来支持基于容器实现的VNF的生命周期管理。所述CISM也可以称为CaaS管理，负责管理VNF所调用的容器对象，包括容器对象的创建、更新和删除，并在其纳管的容器集群节点资源池中将容器对象调度到相应的VM对应的节点资源上，该节点资源包括计算资源、存储资源和网络资源等。ETSI NFV标准在Release 4继续开展容器网络的研究，VNF网络连接的模型是在现有的虚拟机网络模型基础上叠加了一层容器网络。VNF的容器网络连接模型描述了抽象的容器对象层中容器对象(也称为被管理的容器基础设施对象,Managed Container Infrastructure Object,MCIO)之间的网络连接以及容器对象和支撑容器对象运行的容器集群节点(例如，虚拟机或裸机)之间的互连。
进一步地，VNF组件(VNFC)映射为请求计算/存储资源的MCIO(例如，Kubernetes的Pod对象)，VNF外部连接点(External CP)映射为请求网络资源的MCIO(例如，K8S的网络端点对象，通常附着在VNFC所映射的MCIO上)。由于同一个容器集群节点内的容器对象之间彼此互联(全连接网络)，容器基础设施服务管理功能(CISM)对容器网络的管理是不需要NFVO或VNFM参与的自治的管理功能，CISM自行访问MCIO的描述符文件(MCIO Descriptor)和/或MCIO的配置文件(MCIO configuration files)，实现MCIO内部网络以及MCIO之间的网络自动配置。因此，在抽象的容器对象层不存在与VNF内部连接点(Internal CP)或VNF内部虚拟链路(Internal VL)对应的MCIO，进而无需在VNFD中将VNF内部连接点和VNF内部虚拟链路映射为特定的请求网络资源的MCIO。
参考图4，容器化的VNF部署在两个容器集群节点CIS Cluster Node 1和CIS Cluster Node 2上(备注：CIS英文全称为Container Infrastructure Service)。其中一部分VNFC被映射为CIS Cluster Node 1上的MCIO(图4中的Pod1和Pod2)，另一部分VNFC被映射为CIS Cluster Node 2上的MCIO(图中的Pod3和Pod4)。这些MCIO由一个或多个OS container来承载MCIO中的工作负载(workload)，而CIS Cluster Node 1和CIS Cluster Node 2各代表一个虚拟 机。节点间的网络(Inter-Node network)不属于由CISM自治配置的网络，该段网络通常仍然由虚拟化基础设施管理器(Virtualised Infrastructure Manager,VIM)进行配置。CISM完成MCIO内部的OS container之间的网络连接的配置，以及同一节点的MCIO之间的网络连接的配置。
在图4中，容器网络的互通需求包括四个基本场景：容器对象MCIO(即：图中的Pod)访问外网，节点内MCIO互访，节点间MCIO互访以及外网访问MCIO。其中外网包括图4中的物理网络(Physical Network)或基础设施网络(Infrastructure Network)。容器对象MCIO访问外网或外网访问MCIO可以参见图4中节点1的连接通道41(容器对象Pod1的虚拟以太网端口和宿主节点1的以太网端口之间的连接)和46(宿主节点1的以太网端口和外网之间的连接)，其结合在一起就构成了一个MCIO访问外网或外网访问MCIO的通道；同样地，连接通道47和43或者47和44构成了节点2中的MCIO和外网相互访问的通道。节点内互访可以参考图4中连接通道45；节点间互访可以参考图4中的连接通道41,46,47和43，其结合在一起就形成了节点间互访的通道。图4只是一个功能示意，实际的连接通道可以采用不同的建立或连接方式。
当前的容器网络模型是一个IT扁平化的模型，即：容器网络的配置主要考虑了网络连接的需求，没有结合考虑容器网络所承载的VNF(例如，5G垂直行业应用)对网络服务的性能需求具有差异化的需求，根据不同的需求对容器网络的配置进行差分的处理。
例如，在容器化VNF实例化过程中或运行态时，其调用的容器对象如何生成、配置如何更新等，现有技术或标准没有相关描述。在VNF运行态时，伴随着网络服务更新(NS update)操作中对外部VNF连接(External VNF Connectivity)的更新，容器网络的配置如何动态更新，以适配具有新的网络性能需求的VNF外部连接点。所述VNF外部连接点是指：VNF实例和外部功能进行连接的端点，外部功能可以是VNF实例所归属的NS实例的其他VNF实例或嵌套NS实例。
根据5G典型业务的网络性能特征，例如：不同的业务对高带宽、超低时延、高可靠性、高连接密度、高安全性等网络非功能性的需求不同，VNF网络性能需求可以包括但不限于对VNF虚拟链路VL或连接点CP的服务质量(Quality of Service，QoS)、可靠性指标如可用性、安全性的需求定义。其中，QoS通常指网络节点或链路传输的带宽、时延、抖动和丢包率等性能指标。
本发明实施例1涉及一种容器化VNF的实例化方法，其保留容器对象层网络配置的扁平性(即：网络配置过程仅考虑容器网络的连接性)，通过容器集群节点(例如：虚拟机)的网络配置的更新动态适配VNF网络性能的变化，结合CISM功能管理容器网络的自治性，将VNFM管理VNF实例的生命周期时对VNF网络差异化的性能需求传递到CISM，实现动态的容器网络的生成或更新，快速响应VNF网络性能需求的变化。
参考图5，本发明实施例1提供的一种实例化VNF的方法包括如下步骤：
S501：NFVO向VNFM发送VNF实例化请求，在请求消息中携带该VNF实例的标识信息。
S502：VNFM根据步骤S501中的标识信息访问待实例化VNF的描述符文件VNFD，从VNFD中读取VNF内部虚拟链路(Internal Virtual Link,Int-VL)的服务质量(QoS)属性,并根据VNF内部虚拟链路的QoS属性确定VNF使用的容器对象MCIO外部连接的QoS属性。
内部虚拟链路的QoS属性包括对VNF内部虚拟链路传输的带宽、时延、抖动和/或丢包率的要求。
所述的容器对象外部连接为图4中容器对象(图中各个Pod)的端口(Virtual Ethernet， Veth)和宿主节点的端口(eth0，eth1)之间建立的连接。
当确定容器对象外部连接的QoS属性时，容器对象的外部连接QoS属性需要跟VNF内部虚拟链路的QoS属性相匹配，不能相差太大，能够满足VNF实例的传输性能需求；当然，也可以根据实际需要预先建立一个容器对象的外部连接QoS属性和VNF内部虚拟链路的QoS属性对应关系表，根据该表来具体确定待创建的MCIO外部连接的QoS属性。具体的实现方式比较多样，这里不再赘述。
S503：VNFM向容器基础设施服务管理(Container Infrastructure Service Management,CISM)发送容器对象(MCIO)创建请求消息，在请求消息中携带待实例化的VNF使用的容器对象外部连接的QoS属性。
如果一个VNF使用多个MCIO,则需要创建多个MCIO，那么所述创建请求可以携带要创建的多个MCIO的标识。
S504：CISM接收所述容器对象创建请求消息，读取容器对象的描述符文件和/或容器对象的配置文件，创建相应的容器对象；并根据S503请求消息中的各个容器对象外部连接的QoS属性确定各个容器对象和宿主节点之间的连接通道类型，建立相应的连接通道(41,42，43和44)。
容器对象和宿主节点之间的连接通道可以通过容器对象配置容器网络接口(Container Network Interface,CNI)插件实现，不同类型的连接通道实现不同QoS属性的MCIO外部连接。作为一种可能的实现，连接通道类型可以包括：数据面开发套件(Data Plane Development Kit,DPDK)、网卡直连、虚拟局域网(Virtual Local Area Network,VLAN)或者虚拟可扩展的局域网(Virtual eXtensible Local Area Network,VXLAN)，以上类型的传输通道的传输时延从低逐渐到高。参考图4，CISM根据待创建容器对象1(图中Pod1)外部连接的QoS属性确定采用DPDK的连接通道类型，并建立相应类型的连接通道；CISM根据待创建容器对象2(图中Pod2)外部连接的QoS属性确定采用VXLAN的连接通道类型，并建立相应类型的连接通道；CISM根据待创建容器对象3(图中Pod3)外部连接的QoS属性确定采用VXLAN的连接通道类型，并建立相应类型的连接通道；以及CISM根据待创建容器对象4(图中Pod4)外部连接的QoS属性确定采用VLAN的连接通道类型，并建立相应类型的连接通道。
其中，DPDK通过采用轮询方式实现数据包的处理，容器应用(VNF)可以通过DPDK提供的接口直接从内存读取数据包，节省了CPU中断时间、内存拷贝时间，满足对时延有高要求的容器应用的数据包传输。网卡直连(容器对象的网卡vNIC和宿主机VM的网卡vNIC通过网线直连)也是一种常用的数据加速技术，以牺牲部分可靠性换取数据包的传输性能。VLAN在一组逻辑的设备和用户中通过层3的路由器实现彼此之间的通信，达到局域网级别的传输性能。VXLAN是对XLAN的一种扩展，通过引入UDP外层隧道作为数据链路层，使得数据包在二、三层网络中轻松传输。通常而言，传输时延越低的一类连接通道(如：DPDK)的适用范围越窄，附加以可靠性的相关约束和限制。传输时延越高的一类连接通道(如：VXLAN)的适用范围越宽。上述连接通道属于容器对象外部连接的具体物理实现方式，如上所述，由于连接通道本身有不同的类型，不同类型的连接通道其QoS属性是固定的，不需要更新QoS。
另外，容器对象的宿主节点可以为虚拟机或裸金属服务器。
S505：CISM将容器对象MCIO的IP地址和S504所确定类型的容器对象和宿主节点之间的连接通道的标识进行绑定。
例如，在VXLAN类型的连接通道中，CISM将容器对象的IP地址和VXLAN隧道端点进行绑定，该容器对象内的所有分组通过VXLAN隧道端点和宿主节点的端点之间进行收发。
MCIO的IP地址对MCIO外部呈现是固定的，这里的“绑定”就是在同一个MCIO内通过配置操作将IP地址和它使用的VXLAN隧道端点进行关联，两个配置信息附着于同一个MCIO对象。MCIO和宿主节点的连接通道可以有多个，通过在MCIO外置不同的CNI(容器网络接口)插件来实现。
S506：CISM向VNFM返回容器对象创建应答，可选地，在应答消息中可以携带该容器对象和宿主节点之间的连接通道的标识。
S507：可选地，如果容器对象可以作为该VNF和外部环境(例如：其他的VNF)进行互连的端点，VNFM将在步骤S506中获取的容器对象和宿主节点之间的连接通道的标识和VNF的外部连接点(External Connection Point)进行绑定。
在NFV相关标准中，上述“绑定”可以理解为容器对象通过和宿主节点的连接通道和VNF的外部连接点进行关联,并通过该外部连接点和外部进行通信。
S508：VNFM向NFVO返回VNF实例化应答，VNF实例化过程结束。
本发明实施例2涉及一种容器化VNF的更新方法，在NS更新过程中执行VNF External CP更新，容器集群节点网络动态适配VNF网络性能需求。
本实施例反映在VNF实例的运行态(已经完成VNF实例化过程后的VNF实例状态)时，伴随VNF网络性能需求的变化，容器集群节点网络如何动态更新配置以适配变化。典型的场景是在NS更新过程中执行VNF外部连接点更新的过程。
VNF实例化完成后进入运行状态，此时NFVO如果接收来自OSS/BSS的NS更新请求，请求消息中携带NS更新的操作类型是：update VNF external connectivity。本实施例2的具体步骤如图6所示，其跟实施例1的主要区别在于VNFM不是通过访问VNFD读取VNF内部虚拟链路的QoS属性而是通过VNF外部连接点的QoS属性来确定VNF使用的容器对象外部连接的QoS属性。
S601：NFVO向VNFM发送更新外部VNF连接请求消息，在请求消息中携带该VNF实例的外部连接点待更新的QoS属性。
S602：VNFM根据VNF实例外部连接点的QoS属性确定待更新的容器对象的外部连接的QoS属性。
内部虚拟链路的QoS属性包括对内部链路传输的带宽、时延、抖动和/或丢包率的要求，根据VNF内部虚拟链路的QoS属性确定待创建的容器对象MCIO(图4中的Pod)外部连接的QoS属性。同样地，容器对象的外部连接QoS属性需要VNF实例外部连接点的QoS属性相匹配，不能相差太大，能够满足VNF实例传输性能的需求。
S603：VNFM向容器基础设施服务管理(Container Infrastructure Service Management,CISM)发送容器对象(MCIO)更新请求，在更新请求消息中携带待更新的容器对象外部连接的QoS属性。
S604：CISM根据S602确定的待更新的容器对象外部连接的QoS属性重新确定容器对象和宿主节点之间的连接通道类型，建立相应的连接通道。
如果重新确定的容器对象和宿主节点的连接通道类型跟已有的连接通道类型一致，则不进行更新，否则更新成新的连接通道类型。连接通道的类型具体参见实施例1的描述。
S605：CISM将容器对象(MCIO)的IP地址和S604重新确定的容器对象和宿主节点之间的连接通道的标识进行绑定。
S606：CISM向VNFM返回容器对象更新应答消息，可选地，所述更新应答消息中可以携带更新的容器对象和宿主节点之间的连接通道的标识。
S607：可选地，如果容器对象可以作为该VNF和外部环境(例如：其他的VNF)进行互连的端点，VNFM将在步骤S606中获取的容器对象和宿主节点之间的连接通道的标识和VNF的外部连接点(External Connection Point)进行绑定。
S608：VNFM向NFVO返回外部VNF连接更新应答，VNF外部连接点更新过程结束。
图7是一种虚拟网络功能管理器VNFM装置示意图，该装置包括：
接收单元710，可以用于执行图5所示的实施例1中的步骤S501，或可以用于执行图6所示的实施例中的步骤S601，和/或用于支持本文所描述的技术的其它过程。
处理单元720，可以用于执行图5所示的实施例1中的步骤S502和S507，或可以用于执行图6所示的实施例中的步骤S602和S607，和/或用于支持本文所描述的技术的其它过程。
发送单元730，可以用于执行图5所示的实施例1中的步骤S503，或可以用于执行图6所示的实施例中的步骤S603，和/或用于支持本文所描述的技术的其它过程。
上述各个单元的功能可以参考上述实施例1或2的方法步骤的描述，这里不再重复。
图8是CISM装置示意图，该装置包括：
接收单元810，可以用于执行图5所示的实施例1中的步骤S503，或可以用于执行图6所示的实施例中的步骤S603，和/或用于支持本文所描述的技术的其它过程；
处理单元820，可以用于执行图5所示的实施例1中的步骤S504和S505，或可以用于执行图6所示的实施例中的步骤S604和S605，和/或用于支持本文所描述的技术的其它过程；
发送单元830，可以用于执行图5所示的实施例1中的步骤S506，或可以用于执行图6所示的实施例中的步骤S606，和/或用于支持本文所描述的技术的其它过程。
上述各个单元的功能可以参考上述实施例1或2的方法步骤的描述，这里不再重复。
图9是本发明实施例提供的VNFM装置硬件图，所述装置90可以包括：处理器、通信接口以及存储器。
处理器91可以包括一个或者一个以上处理单元，该处理单元可以是中央处理单元(英文：central processing unit，CPU)或者网络处理器(英文：network processor，NP)等。
通信接口94用于跟其他通信设备连接和信息交互，包括接收和发送相应的消息；该网络设备90还可以包括存储器93，处理器91可以通过总线与存储器93和通信接口94相连。存储器93可用于存储软件程序，该软件程序可以由处理器91执行，以实现图5或图6所示实施例中由VNFM执行的方法步骤。此外，该存储器93中还可以存储各类业务数据或者用户数据,包括上述方法步骤中的各种应用实例和服务的状态数据等。
可选地，该装置90还可以包括输出设备95以及输入设备97。输出设备95和输入设备97与处理器91相连。输出设备95可以是用于显示信息的显示器、播放声音的功放设备或者打印机等，输出设备95还可以包括输出控制器，用以提供输出到显示屏、功放设备或者打印机。输入设备97可以是用于用户输入信息的诸如鼠标、键盘、电子触控笔或者触控面板之类的设备，输入设备97还可以包括输出控制器以用于接收和处理来自鼠标、键盘、电子触控笔或者触控面板等设备的输入。
同样地，上述装置硬件图也适用于CISM和其他相关装置，区别是两者存储器93存储的软件程序不一样，CISM装置的存储器93存储的软件程序由处理器91执行，以实现实施例1或2中由CISM装置执行的方法步骤，这里不再重复。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意结合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按 照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如：同轴电缆、光纤、数据用户线(Digital Subscriber Line，DSL))或无线(例如：红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如：软盘、硬盘、磁带)、光介质(例如：数字通用光盘(Digital Versatile Disc，DVD))、或者半导体介质(例如：固态硬盘(Solid State Disk，SSD))等。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上所述为本申请提供的实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (17)

  1. 一种虚拟网络功能VNF的实例化方法，其特征在于，包括：
    虚拟网络功能管理器VNFM接收网络功能虚拟化编排器NFVO发送的VNF实例化请求消息，确定VNF使用的容器对象外部连接的服务质量QoS属性；
    VNFM向容器基础设施服务管理CISM发送容器对象创建请求消息，在请求消息中携带所述容器对象外部连接的QoS属性；
    CISM接收容器对象创建请求消息，读取容器对象的描述符文件和/或配置文件，创建相应的容器对象，并根据容器对象外部连接的QoS属性确定容器对象和宿主节点之间的连接通道类型，建立相应类型的连接通道；
    VNFM接收CISM返回的容器对象创建应答消息，VNFM向NFVO返回VNF实例化应答消息，完成VNF实例化。
  2. 根据权利要求1所述的实例化方法，其特征在于，所述确定VNF使用的容器对象外部连接的QoS属性包括：
    VNFM访问待实例化VNF的描述符文件VNFD，从VNFD中读取VNF内部虚拟链路的服务质量QoS属性，并根据VNF内部虚拟链路的QoS属性确定VNF使用的容器对象外部连接的QoS属性。
  3. 根据权利要求1所述的实例化方法，其特征在于，所述方法进一步包括：
    VNFM接收NFVO发送的更新外部VNF连接请求消息,所述请求消息中携带VNF外部连接点的QoS属性；
    VNFM根据VNF外部连接点的QoS属性更新所述容器对象外部连接的QoS属性；
    VNFM向CISM发送容器对象更新请求消息，在所述更新请求消息中携带所述更新的容器对象外部连接的QoS属性；
    CISM接收容器对象更新请求消息，根据所述更新的容器对象外部连接的QoS属性重新确定容器对象和宿主节点之间的连接通道类型，建立相应类型的连接通道。
    VNFM接收CISM返回的容器对象更新应答消息，VNFM向NFVO返回更新外部VNF连接应答消息，完成更新VNF外部连接点。
  4. 根据权利要求1或3所述的实例化方法，其特征在于，所述方法进一步包括：
    所述VNFM接收的CISM返回的容器对象创建应答消息或容器对象更新应答消息中携带该容器对象和宿主节点之间的连接通道的标识；
    VNFM将所述连接通道的标识和VNF的外部连接点进行绑定。
  5. 根据权利要求1到3任一项所述的实例化方法，其特征在于，所述连接通道类型包括：
    数据面开发套件、网卡直连、虚拟局域网和/或虚拟可扩展局域网。
  6. 根据权利要求1到3任一项所述的实例化方法，其特征在于，所述QoS属性包括：
    链路传输的带宽、时延、抖动和/或丢包率。
  7. 根据权利要求1到3任一项所述的实例化方法，其特征在于，所述宿主节点包括：虚拟机和/或裸金属服务器。
  8. 一种容器对象创建方法，其特征在于，包括：
    容器基础设施服务管理CISM接收虚拟网络功能管理器VNFM发送的容器对象创建请求消息，所述请求消息中携带容器对象外部连接的QoS属性；
    CISM读取容器对象的描述符文件和/或配置文件，创建相应的容器对象，并根据容器对象外部连接的QoS属性确定容器对象和宿主节点之间的连接通道类型，建立相应类型的连接通道。
  9. 根据权利要求8所述的创建方法，其特征在于，在CISM接收虚拟网络功能管理器VNFM发送的容器对象创建请求消息之前，
    VNFM接收网络功能虚拟化编排器NFVO发送的VNF实例化请求消息，访问待实例化VNF的描述符文件VNFD，从VNFD中读取VNF内部虚拟链路的服务质量QoS属性，并根据VNF内部虚拟链路的QoS属性确定容器对象外部连接的QoS属性。
  10. 根据权利要求8所述的创建方法，其特征在于，所述方法进一步包括：
    CISM接收VNFM发送的容器对象更新请求消息，所述更新请求消息中携带更新的容器对象外部连接的QoS属性；
    CISM根据更新的容器对象外部连接的QoS属性重新确定容器对象和宿主节点之间的连接通道类型，建立相应类型的连接通道。
  11. 根据权利要求10所述的创建方法，其特征在于，在CISM接收VNFM发送的容器对象更新请求消息之前，
    VNFM接收NFVO发送的更新外部VNF连接请求消息，所述请求消息中携带VNF外部连接点的QoS属性；
    VNFM根据VNF外部连接点的QoS属性更新所述容器对象外部连接的QoS属性。
  12. 根据权利要求8到11任一项所述的创建方法，其特征在于，所述连接通道类型包括：数据面开发套件、网卡直连、虚拟局域网和/或虚拟可扩展局域网。
  13. 根据权利要求8到11任一项所述的创建方法，其特征在于，所述QoS属性包括：链路传输的带宽、时延、抖动和/或丢包率。
  14. 根据权利要求8到11任一项所述的创建方法，其特征在于，所述宿主节点包括：虚拟机和/或裸金属服务器。
  15. 一种虚拟网络功能管理器，其特征在于，包括：处理器和存储器；处理器与存储器耦合，处理器被配置为读取并执行存储器中的指令，使得所述虚拟网络功能管理器执行如权利要求1至7任一项所述的方法步骤。
  16. 一种容器基础设施服务管理装置，其特征在于，包括：处理器和存储器；处理器与存 储器耦合，处理器被配置为读取并执行存储器中的指令，使得所述容器基础设施服务管理装置执行如权利要求8至14任一项所述的方法步骤。
  17. 一种通信系统，其特征在于，包括：虚拟网络功能管理器以及容器基础设施服务管理装置；
    所述虚拟网络功能管理器和容器基础设施服务管理装置，用于执行如权利要求1至7所述的任一项所述的方法步骤。
PCT/CN2021/099147 2020-08-03 2021-06-09 一种vnf实例化的方法和装置 WO2022028092A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP21853168.9A EP4191907A4 (en) 2020-08-03 2021-06-09 METHOD AND APPARATUS FOR VNF INSTANCEMENT

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010768159.3 2020-08-03
CN202010768159.3A CN114124740A (zh) 2020-08-03 2020-08-03 一种vnf实例化的方法和装置

Publications (1)

Publication Number Publication Date
WO2022028092A1 true WO2022028092A1 (zh) 2022-02-10

Family

ID=80119867

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/099147 WO2022028092A1 (zh) 2020-08-03 2021-06-09 一种vnf实例化的方法和装置

Country Status (3)

Country Link
EP (1) EP4191907A4 (zh)
CN (1) CN114124740A (zh)
WO (1) WO2022028092A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114928490A (zh) * 2022-05-20 2022-08-19 国网江苏省电力有限公司 容器场景下的多端网络管控方法、装置、存储介质和电子设备

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115941486B (zh) * 2022-11-04 2024-06-07 苏州浪潮智能科技有限公司 一种集群管理方法、系统、设备以及存储介质
CN118118348A (zh) * 2022-11-30 2024-05-31 华为技术有限公司 一种虚拟化网络功能vnf的实例化方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109428764A (zh) * 2017-09-05 2019-03-05 华为技术有限公司 虚拟网络功能的实例化方法
US10469359B2 (en) * 2016-11-03 2019-11-05 Futurewei Technologies, Inc. Global resource orchestration system for network function virtualization
CN111399968A (zh) * 2019-01-02 2020-07-10 中国移动通信有限公司研究院 一种基于容器的虚拟资源管理方法、装置及系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10432638B2 (en) * 2016-08-29 2019-10-01 Cisco Technology, Inc. Infrastructure aware adaptive resource allocation

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10469359B2 (en) * 2016-11-03 2019-11-05 Futurewei Technologies, Inc. Global resource orchestration system for network function virtualization
CN109428764A (zh) * 2017-09-05 2019-03-05 华为技术有限公司 虚拟网络功能的实例化方法
CN111399968A (zh) * 2019-01-02 2020-07-10 中国移动通信有限公司研究院 一种基于容器的虚拟资源管理方法、装置及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4191907A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114928490A (zh) * 2022-05-20 2022-08-19 国网江苏省电力有限公司 容器场景下的多端网络管控方法、装置、存储介质和电子设备
CN114928490B (zh) * 2022-05-20 2023-08-15 国网江苏省电力有限公司 容器场景下的多端网络管控方法、装置、存储介质和电子设备

Also Published As

Publication number Publication date
EP4191907A4 (en) 2024-02-14
EP4191907A1 (en) 2023-06-07
CN114124740A (zh) 2022-03-01

Similar Documents

Publication Publication Date Title
US11372802B2 (en) Virtual RDMA switching for containerized applications
US10375015B2 (en) Methods and system for allocating an IP address for an instance in a network function virtualization (NFV) system
WO2022028092A1 (zh) 一种vnf实例化的方法和装置
WO2018024059A1 (zh) 一种虚拟化网络中业务部署的方法和装置
RU2595540C9 (ru) Базовые контроллеры для преобразования универсальных потоков
US10397132B2 (en) System and method for granting virtualized network function life cycle management
WO2016155394A1 (zh) 一种虚拟网络功能间链路建立方法及装置
WO2020186911A1 (zh) 一种容器化虚拟网络功能vnf的资源管理方法及装置
CN106953848B (zh) 一种基于ForCES的软件定义网络实现方法
WO2017066931A1 (zh) 网络功能虚拟化架构中证书的管理方法及装置
WO2021098819A1 (zh) 一种路由更新方法和用户集群
US20220350637A1 (en) Virtual machine deployment method and related apparatus
US11240308B2 (en) Implicit discovery controller registration of non-volatile memory express (NVMe) elements in an NVME-over-fabrics (NVMe-oF) system
WO2018153355A1 (zh) 控制信息传递方法、服务器和系统
US10785056B1 (en) Sharing a subnet of a logically isolated network between client accounts of a provider network
EP4177742A1 (en) Multitenancy management method and apparatus
WO2021185083A1 (zh) Vnf实例化方法及装置
WO2021175105A1 (zh) 连接方法、装置、设备和存储介质
WO2020077585A1 (zh) Vnf服务实例化方法及装置
WO2021244483A1 (zh) 一种虚拟化的网络服务的部署方法及装置
US11929883B1 (en) Supporting virtual machine migration when network manager or central controller is unavailable
WO2024114645A1 (zh) 一种虚拟化网络功能vnf的实例化方法及装置
WO2022089291A1 (zh) 一种数据流镜像方法及装置
WO2022183796A1 (zh) 一种创建网络服务ns的方法及相关装置
WO2024093315A1 (zh) 一种针对多资源池网络的管理方法、云管理平台及装置

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021853168

Country of ref document: EP

Effective date: 20230303

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

Ref document number: 21853168

Country of ref document: EP

Kind code of ref document: A1