WO2024114645A1 - 一种虚拟化网络功能vnf的实例化方法及装置 - Google Patents

一种虚拟化网络功能vnf的实例化方法及装置 Download PDF

Info

Publication number
WO2024114645A1
WO2024114645A1 PCT/CN2023/134807 CN2023134807W WO2024114645A1 WO 2024114645 A1 WO2024114645 A1 WO 2024114645A1 CN 2023134807 W CN2023134807 W CN 2023134807W WO 2024114645 A1 WO2024114645 A1 WO 2024114645A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
connection point
virtual connection
microservice
configuration information
Prior art date
Application number
PCT/CN2023/134807
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 华为技术有限公司
Publication of WO2024114645A1 publication Critical patent/WO2024114645A1/zh

Links

Definitions

  • the present application relates to the field of communication technology, and in particular to a method and device for instantiating a virtualized network function (VNF).
  • VNF virtualized network function
  • Network function virtualization (NFV) technology uses general hardware devices and virtualization technology to build virtualized network functions (VNF). VNF then carries the functions of dedicated devices in traditional networks, reducing the expensive cost of deploying dedicated devices.
  • VNF network function virtualization
  • a container management platform is a platform based on containerization technology, such as the Kubernetes (K8S) platform.
  • K8S Kubernetes
  • a container management platform manages a cluster, which includes several physical machines or virtual machines. Container objects can be deployed on physical machines or virtual machines.
  • the present application provides a VNF instantiation method and device for creating an entry container object for a microservice to facilitate meeting the access requirements of the microservice.
  • an embodiment of the present application provides a VNF instantiation method, which can be executed by a VNFM.
  • the VNFM receives a first instantiation request from a network function virtualization orchestrator NFVO, where the first instantiation request is used to request instantiation of the VNF, and the first instantiation request includes configuration information of K microservices of the network function NF corresponding to the VNF, where K is a positive integer; according to the configuration information of the K microservices, configuration information of a first ingress container object is determined, where the first ingress container object is used to provide an access portal for the K microservices; and the configuration information of the first ingress container object is sent to a container infrastructure manager CISM, where the configuration information of the first ingress container object is used to create the first ingress container object.
  • VNFM receives a first instantiation request from NFVO, the first instantiation request is used to request instantiation of the VNF, the first instantiation request includes configuration information of a first virtual connection point of the VNF, the configuration information of the first virtual connection point includes configuration information of K microservices of the network function NF corresponding to the VNF, K is a positive integer; according to the configuration information of the first virtual connection point, the configuration information of a first ingress container object corresponding to the first virtual connection point is determined, the first ingress container object is used to provide access to the K microservices; the configuration information of the first ingress container object is sent to a container infrastructure manager CISM, the configuration information of the first ingress container object is used to create the first ingress container object.
  • VNFM can determine the configuration information of the entry container object used to provide an access entry for the microservice according to the configuration information of the microservice in the instantiation request sent by NFVO (or the configuration information of the virtual connection point including the configuration information of the microservice), and then create an entry container object for the microservice. Since the access address (such as fqdn) of the microservice defined by the entry container object belongs to the 7th layer, it is easy to meet the access requirements of the microservice.
  • determining configuration information of a first ingress container object corresponding to the first virtual connection point according to configuration information of the first virtual connection point includes: obtaining a virtualized network function description VNFD of the VNF, the VNFD including mapping information, the mapping information being used to indicate a mapping relationship between configuration information of the first virtual connection point and configuration information of the first ingress container object; and determining configuration information of the first ingress container object according to the configuration information of the first virtual connection point and the mapping information.
  • the mapping information includes first mapping information corresponding to a first microservice among the K microservices; the first mapping information includes at least one of the following: domain name mapping information, the domain name mapping information is used to indicate parameters mapped to the domain name of the first microservice in the configuration information of the first microservice; priority mapping information, the priority mapping information is used to indicate parameters mapped to the priority of the first microservice in the configuration information of the first microservice.
  • the VNFD includes description information of the first microservice, and the first mapping information is included in the description information of the first microservice.
  • the description information of the first microservice further includes at least one of the following:
  • Service type information where the service type information includes the name of the first microservice
  • Domain name type information where the domain name type information is used to indicate the domain name type supported by the first microservice for configuration, where the domain name type includes an internal access domain name and/or an external access domain name;
  • Priority information where the priority information is used to indicate that the first microservice supports configuration priority.
  • VNFD virtual connection point
  • the mapping between network element microservices and ingress container objects is realized, and the management of ingress container objects is realized by introducing parameters such as container object type information, service type information, domain name type information, priority information, etc. in VNFD, so that cloud-native technology can be better used to realize the transformation of network element microservices, and the creation and lifecycle management of network element microservices can be realized through MANO.
  • the VNFD also includes container object type information corresponding to the first virtual connection point, where the container object type information is used to indicate that the container object type corresponding to the first virtual connection point is an ingress container object.
  • the VNFD also includes description information of the virtual deployment unit VDU of the VNF, and the description information of the VDU includes service type information, and the service type information is used to indicate the microservice corresponding to the VDU.
  • the method further includes: receiving an access address of the first entry container object from the CISM.
  • the method further includes: receiving first request information from the NFVO, the first request information being used to request an access address of the first virtual connection point; and sending, according to the first request information, an access address of the first ingress container object as an access address of the first virtual connection point to the NFVO.
  • an embodiment of the present application provides a VNF instantiation method, which can be executed by an NFVO.
  • the NFVO receives a second instantiation request from an operation support system/business support system OSS/BSS, the second instantiation request is used to request the instantiation of the VNF, and the second instantiation request includes the configuration information of M microservices of the NF corresponding to the VNF; according to the configuration information of K microservices corresponding to the first virtual connection point of the VNF, the configuration information of the first virtual connection point is obtained; wherein the K microservices belong to the M microservices, M and K are positive integers, and K is less than or equal to M; a first instantiation request is sent to the VNFM, the first instantiation request includes the configuration information of the first virtual connection point, the configuration information of the first virtual connection point is used to determine the configuration information of a first entry container object corresponding to the first virtual connection point, and the first entry container object is used to provide an access entry
  • the method further includes: obtaining a VNFD of the VNF, the VNFD including description information of the first virtual connection point, the description information of the first virtual connection point being used to indicate that the first virtual connection point corresponds to the K microservices.
  • the description information of the first virtual connection point includes the names of the K microservices.
  • the method also includes: receiving second request information from the OSS/BSS, the second request information being used to request resource utilization information of a first microservice among the K microservices; obtaining resource utilization information of at least one VDU corresponding to the first microservice according to the second request information; determining resource utilization information of the first microservice according to the resource utilization information of the VDU corresponding to the first microservice; and sending the resource utilization information of the first microservice to the OSS/BSS.
  • the method further includes: obtaining a VNFD of the VNF, where the VNFD is used to indicate at least one VDU corresponding to the first microservice.
  • the VNFD includes description information of each VDU in the at least one VDU, the description information of the VDU includes service type information, and the service type information is used to indicate that the microservice corresponding to the VDU is the first microservice.
  • the present application provides an instantiation device of a VNF, which has the function of implementing the functions involved in the first or second aspect above.
  • the device includes modules or units or means corresponding to the operations involved in the first or second aspect above.
  • the functions or units or means can be implemented by software, or by hardware, or the corresponding software can be implemented by hardware.
  • the device includes a processing unit and a communication unit, wherein the communication unit can be used to send and receive signals to achieve communication between the device and other devices, for example, the communication unit is used to send system information to a terminal device; the processing unit can be used to perform some internal operations of the device.
  • the functions performed by the processing unit and the communication unit can correspond to the operations involved in the first aspect or the second aspect described above.
  • the device includes a processor, which can be coupled to a memory.
  • the memory can store necessary computer programs or instructions to implement the functions involved in the first aspect or the second aspect.
  • the processor can execute the memory to store A computer program or instruction, when the computer program or instruction is executed, enables the device to implement the method in any possible design or implementation of the first aspect or the second aspect above.
  • the device includes a processor and a memory
  • the memory can store necessary computer programs or instructions for implementing the functions involved in the first aspect or the second aspect.
  • the processor can execute the computer program or instructions stored in the memory, and when the computer program or instructions are executed, the device implements the method in any possible design or implementation of the first aspect or the second aspect.
  • the device includes a processor and an interface circuit, wherein the processor is used to communicate with other devices through the interface circuit and execute the method in any possible design or implementation of the first aspect or the second aspect above.
  • the processor can be implemented by hardware or by software.
  • the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory.
  • the above processors can be one or more, and the memories can be one or more.
  • the memory can be integrated with the processor, or the memory can be separately set from the processor. In the specific implementation process, the memory can be integrated with the processor on the same chip, or can be set on different chips respectively.
  • the embodiment of the present application does not limit the type of memory and the setting method of the memory and the processor.
  • the present application provides a VNF instantiation system, which may include a VNFM and a NFVO, wherein the VNFM is used to execute a method in any possible design of the first aspect, and the NFVO is used to execute a method in any possible design of the second aspect.
  • the present application provides a computer-readable storage medium, in which computer-readable instructions are stored.
  • a computer reads and executes the computer-readable instructions, the computer executes a method in any possible design of the first aspect or the second aspect.
  • the present application provides a computer program product.
  • the computer reads and executes the computer program product, the computer executes the method in any possible design of the first aspect or the second aspect mentioned above.
  • the present application provides a chip, comprising a processor, wherein the processor is coupled to a memory and is used to read and execute a software program stored in the memory to implement a method in any possible design of the first aspect or the second aspect above.
  • FIG1 is a schematic diagram of an NFV architecture provided in an embodiment of the present application.
  • FIG2 is a diagram of a Kubernetes container management orchestration architecture provided in an embodiment of the present application.
  • FIG3 is an NFV architecture that introduces a container management platform provided in an embodiment of the present application.
  • FIG4A is a schematic diagram of the relationship between a service and a pod provided in an embodiment of the present application.
  • FIG4B is a schematic diagram of the relationship between ingress and service provided in an embodiment of the present application.
  • FIG5 is a schematic diagram of an implementation process of containerized deployment of VNFs provided in an embodiment of the present application.
  • FIG6 is an example of a corresponding relationship provided in an embodiment of the present application.
  • FIG7 is a schematic diagram of a flow chart corresponding to a VNF instantiation method provided in an embodiment of the present application.
  • FIG8 is a possible exemplary block diagram of a device involved in an embodiment of the present application.
  • FIG. 9 is a schematic diagram of the structure of a device provided in an embodiment of the present application.
  • the network architecture and service scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application. It does not constitute a limitation on the technical solutions provided in the embodiments of the present application. A person skilled in the art may appreciate that, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • the NFV architecture may include an NFV management and orchestration system (NFV-MANO) 110, an NFV infrastructure (NFV infrastructure, NFVI) 150, multiple VNFs 140, multiple element management (EM) 130, and one or more operation support systems/business support systems (OSS/BSS) 120.
  • the NFV-MANO 110 may include an NFV orchestrator (NFV orchestrator, NFVO) 111, one or more virtualized network function managers (VNFM) 112, and one or more virtualized infrastructure managers (VIM) 113.
  • NFV orchestrator NFV orchestrator
  • VNFM virtualized network function managers
  • VIP virtualized infrastructure managers
  • NFVO 111 Mainly responsible for handling the lifecycle management of virtualized services, as well as the allocation and scheduling of virtual resources in the virtual infrastructure and NFVI.
  • NFVO 111 can communicate with one or more VNFMs 112 to execute resource-related requests, send configuration information to VNFMs 112, and collect status information of VNFs 140.
  • NFVO 111 can also communicate with VIMs 113 to perform resource allocation and/or reservation, and exchange virtualized hardware resource configuration and status information.
  • VNFM112 Mainly responsible for the lifecycle management of one or more VNFs, such as instantiating VNF140, updating VNF140, querying VNF140, scaling VNF140, and terminating VNF140.
  • VNFM112 can communicate with VNF140 to complete VNF lifecycle management and exchange configuration and status information.
  • VIM113 Mainly responsible for controlling and managing the interaction between VNF140 and computing hardware 1521, storage hardware 1522, network hardware 1523, virtual computing 1511 (e.g., virtual machine (VM)), virtual storage 1512, and virtual network 1513.
  • VIM113 performs resource management functions, including managing infrastructure resources, allocation (e.g., adding resources to virtual containers), and operation functions (e.g., collecting NFVI fault information).
  • VNFM112 can communicate with VIM113 to request resource allocation and exchange virtualized hardware resource configuration and status information.
  • NFVI 150 It may include a hardware resource layer consisting of computing hardware 1521, storage hardware 1522, and network hardware 1523, a virtualization layer, and a virtual resource layer consisting of virtual computing 1511, virtual storage 1512, and virtual network 1513.
  • the computing hardware 1521 in the hardware resource layer may be a dedicated processor or a general-purpose processor for providing processing and computing functions, such as a central processing unit (CPU); the storage hardware 1522 is used to provide storage capabilities, such as a disk or network attached storage (NAS); and the network hardware 1523 may be a switch, a router, and/or other network devices.
  • the virtualization layer in NFVI 150 is used to abstract the hardware resources of the hardware resource layer, decouple the VNF 140 from the physical layer to which the hardware resources belong, and provide virtual resources to the VNF.
  • the virtual resource layer may include virtual computing 1511, virtual storage 1512, and virtual network 1513.
  • Virtual computing 1511 and virtual storage 1512 may be provided to VNF 140 in the form of virtual machines or other virtual containers.
  • one or more virtual machines may constitute a VNF 140.
  • the virtualization layer forms a virtual network 1513 by abstracting network hardware 1523.
  • Virtual network 1513 is used to implement communication between multiple virtual machines or between multiple other types of virtual containers carrying VNFs.
  • EM130 It is a system used to configure and manage equipment in traditional telecommunications systems. In the NFV architecture, EM130 can also be used to configure and manage VNFs, as well as initiate lifecycle management operations such as instantiating new VNFs to VNFM112.
  • OSS/BSS120 Supports various end-to-end telecommunications services.
  • OSS supports management functions including network configuration, service provision, and fault management.
  • BSS processes orders, payments, and revenue, and supports product management, order management, revenue management, and customer management.
  • VNF140 corresponds to the physical network function (PNF) in the traditional non-virtualized network, such as the virtualized core network node (such as access and mobility management function (AMF), session management function (SMF) network element, etc.).
  • PNF physical network function
  • AMF access and mobility management function
  • SMF session management function
  • the functional behavior and status of the network function have nothing to do with virtualization or not.
  • the NFV technology requirements hope that VNF and PNF have the same functional behavior and external interface.
  • CaaS container as a service
  • PaaS platform as a service
  • API application programming interface
  • helm is the package manager of K8S, which is mainly responsible for managing the deployment packages (also called helm charts) used to deploy applications.
  • the helm chart can encapsulate another markup language (yet another markup language, YAML) files of K8S native applications.
  • helm can be included in K8S or it can be an independent package management tool. In the embodiments of this application, helm is included in K8S as an example.
  • FIG. 2 is a diagram of the Kubernetes container management orchestration architecture.
  • Kubernetes divides the devices in the cluster into a Kubernetes master node (master) and a group of worker nodes (node).
  • master a group of processes related to cluster management
  • RC replication controller
  • These processes implement resource management, pod scheduling, elastic scaling, security control, system monitoring and error correction and other management functions of the entire cluster.
  • Three components, kubelet, kube-proxy, and container engine run on each Node, which are responsible for managing the life cycle of the pod on this node and realizing the function of the service proxy.
  • Pod is the basic scheduling unit in Kubernetes.
  • the API Server provides the only operation entry for resource objects. All other components must operate resource data through the API interface it provides, and complete related business functions by "full query” and “change monitoring” of related resource data.
  • Controller Manager is the management and control center of the cluster. Its main purpose is to realize the automatic fault detection and recovery of the kubernetes cluster. For example, it can complete the replication or removal of pods according to the definition of RC to ensure that the number of pod instances meets the definition of RC, and complete the creation and update of service endpoints objects, node discovery, management and status monitoring, and cleanup of locally cached container image files according to the management relationship between services and pods.
  • the kubelet component is responsible for the full life cycle management of pods on this node, including creation, modification, monitoring, and deletion. At the same time, Kubelet periodically reports the status information of this node to the API Server.
  • the proxy component is used to implement service proxy and software mode load balancing.
  • the docker component is the operating environment of the container.
  • a container infrastructure service management (CISM) 114 is added to the NFV MANO.
  • CISM is a container management platform in the NFV architecture and is responsible for managing container objects called by VNFs, including the creation, update, and deletion of container objects.
  • VNFs When VNFs are deployed in container form, CISM 114 can create container objects based on requests from VNFM 112.
  • CISM will be described as kubernetes.
  • network elements other than CISM can refer to the description in FIG1 above, and will not be repeated.
  • the network elements (such as NFVO, VNFM, CISM, etc.) described in the above Figures 1 to 3 are only examples and not limitations. During the process of standard evolution, the names of the above network elements may change, and the functions performed by each network element may be further split or combined, which is not limited in the embodiments of the present application.
  • multiple refers to two or more than two. In view of this, in the embodiments of the present application, “multiple” can also be understood as “at least two". "At least one” can be understood as one or more, for example, one, two or more. For example, including at least one means including one, two or more, and there is no restriction on which ones are included. For example, including at least one of A, B and C, then A, B, C, A and B, A and C, B and C, or A and B and C can be included. "And/or" describes the association relationship of associated objects, indicating that three relationships can exist.
  • a and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone.
  • the character "/”, unless otherwise specified, generally indicates that the objects associated before and after are in an “or” relationship.
  • system and network in the embodiments of the present application can be used interchangeably.
  • ordinal numbers such as “first” and “second” mentioned in the embodiments of the present application are used to distinguish multiple objects and are not used to limit the order, timing, priority or importance of the multiple objects.
  • Kubernetes can create a variety of container objects, such as pod container objects, service container objects, and ingress container objects.
  • container objects such as pod container objects, service container objects, and ingress container objects.
  • ETSI European Telecommunications Standards Institute
  • MCIO managed container infrastructure objects
  • Pod container object Kubernetes creates containers on the managed cluster with pod as the smallest unit.
  • a pod can contain one or more containers, so pod can also be called a container cabin.
  • Kubernetes pods have a life cycle. They can be created and destroyed. Once destroyed, their life ends forever. Kubernetes can dynamically create and destroy pods based on resource associations (for example, if you need to scale up or down, or perform rolling upgrades).
  • Service container object Service is the core concept of Kubernetes. Multiple pods can be accessed by the same service. The service selects the associated pods through labels. Even if the pods are changed, the corresponding applications (other pods or newly created pods) can be accessed by accessing the service.
  • Figure 4A shows the relationship between service and pod.
  • the service can provide load balancing capabilities, such as routing access requests to the service to the appropriate pod for processing based on the current load of the associated pod.
  • the service is expressed in the form of IP:Port, which means it works at the TCP/IP layer, that is, the service can provide 4-layer load balancing capabilities.
  • IP:Port which means it works at the TCP/IP layer, that is, the service can provide 4-layer load balancing capabilities.
  • Table 1 the definition of a service is shown in Table 1.
  • Ingress container object Ingress is a higher-level abstraction of service. Service works at the TCP/IP layer. For services based on the hypertext transfer protocol (HTTP), different uniform resource locators (URL) often correspond to different backend services or virtual servers. These application layer forwarding mechanisms cannot be implemented only through the kubernetes service mechanism. Ingress was added in kubernetes V1.1 to forward access requests from different URLs to different backend services to implement the HTTP layer business routing mechanism. As shown in Figure 4B, it is a schematic diagram of the relationship between ingress and service.
  • HTTP hypertext transfer protocol
  • URL uniform resource locators
  • rules can be defined in an ingress to associate multiple services.
  • definition of rules in an ingress is shown in Table 2.
  • the access party can access different services by accessing the access addresses of different services, and the access address of the service defined by ingress rules (i.e., host value) belongs to layer 7, i.e., fully qualified domain name (fqdn) address.
  • IP Internet protocol
  • fqdn domain name
  • the DNS server For the access party, after obtaining the access address of the service (i.e., the access address of the service defined in the host), the DNS server will be queried for the IP address corresponding to the access address.
  • the DNS server returns the IP address assigned by the ingress to the access party, and then the access party sends an HTTP request to the IP address and specifies the access address of the service to be accessed in the host header, thereby achieving access to the service.
  • the three container objects described in the embodiments of the present application are merely examples, and the three container objects may have other possible names.
  • the entry container object may have other names, and the embodiments of the present application do not limit this.
  • the virtualized network service in NFV is called a network service (NS), such as an IP multimedia subsystem (IMS) network or a fifth generation (5G) core network.
  • NS network service
  • IMS IP multimedia subsystem
  • 5G fifth generation
  • a NS can contain several VNFs.
  • NSD network service descriptor
  • VNFD VNF description
  • VNF deployment template the topology information
  • VNF descriptor, VNFD the description information of each VNF contained in the NS
  • VNFD VNF description
  • the topology information may include virtualization connection information (for example, network service virtual link descriptor (NsVld)), which can be used to describe the connection between VNFs, for example, describing the connection type, bandwidth and other information.
  • NsVld network service virtual link descriptor
  • VNFD is used to provide description information of VNF, which may include virtualization deployment unit connection point (VDU), connection point descriptor (CPD) and virtual link descriptor (VLD).
  • VDU virtualization deployment unit connection point
  • CPD connection point descriptor
  • VLD virtual link descriptor
  • VNFD may also include references to managed container infrastructure object packages (MCIOP), which may be helm chart used by kubernetes.
  • MCIOP managed container infrastructure object packages
  • a VDU represents a virtual machine, and the description information of the VDU may include the resource requirements of the virtual machine, such as the resource types required to create the virtual machine and the number of resources of each resource type, etc.
  • a VDU represents a group of containers, and the description information of the VDU may include the resource requirements of this group of containers, which is used to indicate the resource information required to deploy this group of containers.
  • the containers in this group of containers have the same resource requirements and share the same network information.
  • CPD may include description information of the external connection point of the VNF, such as a virtual connection point (virtual Cp).
  • VLD can describe the virtual network connection requirements between VDUs, such as connection type and/or bandwidth.
  • the core network architecture of the 5G communication system defines multiple network elements, such as AMF network element, SMF network element, etc.
  • a network element can be understood as a network function (NF).
  • NF network function
  • multiple Microservices, such as the microservices defined in the AMF network element are shown in Table 3.
  • Table 3 Examples of microservices defined within an AMF network element
  • each microservice can be accessed and called by other network elements or microservices by defining a corresponding domain name (such as fqdn).
  • the domain names in the embodiments of the present application can be divided into two types, namely internal access domain names and external access domain names.
  • the microservice can include internal access domain names and external access domain names; for example, taking namf_location as an example, the internal access domain name of namf_location can be myAMF_location.mynetwork.com, and the external access domain name can be myAMF_location_external.mynetwork.com.
  • microservices can be made independent, and the deployment, upgrade, and expansion of different microservices can be carried out separately without affecting other microservices in the network element, making it more convenient to use and more agile to upgrade.
  • the container management platform is introduced into the NFV architecture, and the VNF can be deployed in a container (i.e., instantiated).
  • a possible implementation process is described below in conjunction with FIG5 .
  • FIG5 is a schematic diagram of the implementation process of containerized deployment of VNF. As shown in FIG5 , the process may include:
  • OSS/BSS sends an instantiation request 1 to NFVO, where the instantiation request 1 is used to request the instantiation of VNF.
  • the instantiation request 1 may include information about the VNFD of the VNF to be instantiated, such as the identifier of the VNFD (ie, VnfdId).
  • NFVO sends instantiation request 2 to VNFM according to instantiation request 1, where instantiation request 2 is used to request instantiation of VNF.
  • the instantiation request 2 may include information about the VNFD of the VNF to be instantiated, such as the identifier of the VNFD (ie, VnfdId).
  • the VNFM obtains the VNFD file (or VNFD file package) of the VNF according to the instantiation request 2, and determines the configuration information of at least one container object corresponding to the VNF according to the VNFD file.
  • the VNFM may send a VNFD request to the NFVO, where the VNFD request is used to request to obtain the VNFD file.
  • the VNFD request includes the identifier of the VNFD file.
  • the NFVO receives the VNFD request from the VNFM.
  • the NFVO determines the VNFD file corresponding to the identifier of the VNFD file and sends the VNFD file to the VNFM.
  • the VNFD file package may include a VNFD file and an MCIOP, and may also include other possible files, which are not specifically limited; the VNFD file in the embodiment of the present application may also be referred to as VNFD.
  • VNFD an example of a VNFD file package is shown in Table 4.
  • the myVNFD.yaml file may include description information of at least one VDU. Taking VDU_1 as an example, the description information of VDU_1 is shown in Table 5.
  • VDU_mapping describes the mapping relationship between the configuration information of VDU_1 and the parameters in MCIOP.
  • the above MCIOP may include parameters of the pod corresponding to the vdu (values.yaml file), wherein the values.yaml file is shown in Table 6.
  • VNFM can update the values of the corresponding parameters in the values.yaml file according to the corresponding relationship in VDU_mapping, that is, use the value of min_number_of_instances to update the value of minReplicas of podDB, and use the value of max_number_of_instances to update the value of maxReplicas of podDB.
  • the updated values.yaml file is shown in Table 7.
  • VNF can include multiple VDUs, and the way in which VNFM determines the configuration information of the pods corresponding to other VDUs can be implemented with reference to the above.
  • the VNFM sends configuration information of at least one container object to the CISM; correspondingly, the CISM receives the configuration information of the at least one container object.
  • the VNFM may send an updated MCIOP to the CISM, where the updated MCIOP includes configuration information of at least one container object, for example, the updated MCIOP includes configuration information of the pod corresponding to the above VDU_1, and also includes configuration information of pods corresponding to other VDUs.
  • CISM creates at least one container object according to the configuration information of the at least one container object, and sends a response of instantiation success to the VNFM.
  • VNFM sends a response of instantiation success to NFVO.
  • NFVO sends a response of instantiation success to OSS/BSS.
  • the VNFD of the VNF includes a reference to MCIOP, so that the containerized deployment of the VNF can be realized.
  • MCIOP containerized deployment of the VNF
  • the ETSI NFV standard introduces the concept of service into VNFD, and describes the service through virtualCp in VNFD, and VDU represents pod.
  • the parameters currently defined by virtualCp are shown in Table 8.
  • the above-mentioned servicePortData includes parameters used to describe the service, such as port, etc., and the details can be referred to the ETSI NFV standard and will not be repeated here.
  • the service only provides Layer 4 (TCP/IP) load balancing capabilities, but not Layer 7 capabilities (such as forwarding based on application layer protocols, such as http, forwarding based on domain names, URLs, etc.), and thus cannot be accessed by defining fqdn.
  • Layer 4 TCP/IP
  • Layer 7 capabilities such as forwarding based on application layer protocols, such as http, forwarding based on domain names, URLs, etc.
  • Microservices are accessed by other network elements or microservices by defining fqdn. Therefore, when using the service in kubernetes to implement containerized deployment of microservices, the access requirements of microservices cannot be met.
  • an embodiment of the present application provides a VNF instantiation method, which deploys network element microservices through an ingress container object (i.e., ingress). Since the access address of the service defined by ingress belongs to layer 7 (refer to the description of ingress above), it is easy to meet the access requirements of microservices.
  • ingress container object i.e., ingress
  • VNFD can be improved.
  • new parameters can be defined in the virtualCP of VNFD to achieve mapping between microservices and ingress, so as to facilitate deployment of network element microservices through ingress.
  • VNFD includes two virtual connection points, which are divided into a first virtual connection point (expressed as virtualCp1) and a second virtual connection point (expressed as virtualCp2).
  • VNFD may include description information of the first virtual connection point and description information of the second virtual connection point.
  • the description information of the first virtual connection point may include container object type (mcio_type) information, and the container object type information is used to indicate the container object type corresponding to the first virtual connection point, which may be ingress or service, or other possible container types.
  • the description is made by taking the container object type corresponding to the first virtual connection point as ingress as an example.
  • the description information of the first virtual connection point also includes description information of K microservices, that is, the first virtual connection point corresponds to K microservices.
  • the K microservices include the first microservice.
  • the description information of the first microservice includes at least one of the following:
  • Service type (service_type) information may include the name of the first microservice.
  • the domain name type information is used to indicate the domain name type supported by the first microservice.
  • the domain name type includes an internal access domain name and/or an external access domain name.
  • 3 Domain name mapping information which is used to indicate the parameters to which the domain name of the first microservice is mapped.
  • the priority information is used to indicate that the first microservice supports configuration priority.
  • Priority mapping information is used to indicate the parameters to which the priority of the first microservice is mapped.
  • Table 9 Example of description information of the first virtual connection point and the second virtual connection point
  • a virtual connection point can correspond to multiple microservices and multiple VDUs.
  • service type information can be added to the VDU, and the service type information is used to indicate the microservice corresponding to the VDU.
  • VDU_1 to VDU_5 in Table 9 above are described below.
  • VNFD may also include other possible information, which can be specifically referred to in the prior art and will not be described in detail here.
  • the process of instantiating the VNF provided in the embodiment of the present application is described below.
  • the VNFD involved in the process may be the improved VNFD described above.
  • the method is applied to the NFV architecture shown in Figure 3 as an example, that is, the OSS/BSS below may be the OSS/BSS120 shown in Figure 3, the NFVO may be the NFVO111 shown in Figure 3, the VNFM may be the VIM112 shown in Figure 3, and the CISM may be the CISM114 shown in Figure 3.
  • FIG7 is a flow chart of a VNF instantiation method according to an embodiment of the present application. As shown in FIG7 , the method includes:
  • OSS/BSS sends a second instantiation request to NFVO, where the second instantiation request is used to request instantiation of VNF, and the second instantiation request includes configuration information of M microservices of the NF corresponding to the VNF; accordingly, NFVO receives the second instantiation request.
  • the M microservices include the first microservice, and the configuration information of the first microservice may include at least one of the following: the name of the first microservice (serviceName), the domain name of the first microservice, and the priority of the first microservice; M is a positive integer.
  • the domain name of the first microservice may include an internal access domain name (expressed as fqdn) and an external access domain name (expressed as interPlmnFqdn).
  • the second instantiation request may also include other possible information, such as the identifier of the VNFD of the VNF.
  • the purpose of the second instantiation request is to request the instantiation of the VNF.
  • the second instantiation request can be an instantiation request for the NS or an update request for the NS. This is not limited in the embodiments of the present application.
  • the NFVO obtains the configuration information of the first virtual connection point according to the configuration information of the K microservices corresponding to the first virtual connection point of the VNF.
  • K microservices belong to M microservices, that is, K microservices are part or all of the M microservices, K is a positive integer, and K is less than or equal to M.
  • the NFVO may first determine which microservices of the M microservices the first virtual connection point corresponds to, and then after determining that the first virtual connection point corresponds to K microservices, obtain the configuration information of the first virtual connection point according to the configuration information of the K microservices.
  • the NFVO may obtain the VNFD of the VNF, and the VNFD includes the description information of the first virtual connection point (such as shown in Table 9 above), and the description information of the first virtual connection point is used to indicate that the first virtual connection point corresponds to the K microservices.
  • the description information of the first virtual connection point includes the names of the K microservices (i.e., service_type).
  • NFVO can also determine the configuration information of other virtual connection points (such as the second virtual connection point) of VNF.
  • the first virtual connection point of VNF corresponds to namf-location and namf-mt
  • the second virtual connection point corresponds to namf-communication.
  • the configuration information of the first virtual connection point and the second virtual connection point is shown in Table 12.
  • Table 12 Example of configuration information of the first virtual connection point and the second virtual connection point
  • the NFVO sends a first instantiation request to the VNFM, where the first instantiation request includes configuration information of a first virtual connection point of the VNF; accordingly, the VNFM receives the first instantiation request.
  • the first instantiation request includes the configuration information of the first virtual connection point of the VNF.
  • the first instantiation request may also include the configuration information of other virtual connection points (such as the second virtual connection point) of the VNF.
  • the first instantiation request may include an extVirtualLink parameter (or cell), and the NFVO may add the configuration information of the first virtual connection point and the second virtual connection point in the extVirtualLink parameter.
  • the extVirtualLink parameter is used to describe the network information of the VNF's external connection, and the extVirtualLink contains the configuration information of (one or more) VNF's external connection points (i.e., extCp).
  • extCp VNF's external connection points
  • virtualCp1 and virtualCp2 are used as a kind of extCp to provide connection information to the outside, so the configuration information of the first virtual connection point and the second virtual connection point can be added to extCp, as shown in Table 12 above.
  • the first instantiation request may also include other possible information, such as the identifier of the VNFD of the VNF.
  • the VNFM determines configuration information of a first ingress container object corresponding to the first virtual connection point according to the configuration information of the first virtual connection point, where the first ingress container object is used to provide access portals for the K microservices.
  • the VNFM may obtain a VNFD of the VNF, where the VNFD includes mapping information, where the mapping information is used to indicate the first virtual connection The mapping relationship between the configuration information of the connection point and the configuration information of the first inlet container object; further, the VNFM determines the configuration information of the first inlet container object according to the configuration information of the first virtual connection point and the mapping information.
  • mapping information is used to indicate the first virtual connection
  • the VNFM determines the configuration information of the first inlet container object according to the configuration information of the first virtual connection point and the mapping information.
  • the mapping information is used to map the information of the virtual connection point in the VNFD to information that can be parsed by the CISM (i.e., the configuration information of the ingress container object).
  • the mapping information may include the first to Kth mapping information corresponding to the K microservices respectively. Taking the first mapping information corresponding to the first microservice as an example, the first mapping information may include at least one of the following:
  • the domain name mapping information may be mciop:ingress1.host1, mciop:ingress1.host2, which means that the parameters mapped to the internal access domain name of the first microservice are mciop:ingress1.host1, and the parameters mapped to the external access domain name of the first microservice are mciop:ingress1.host2.
  • Priority mapping information used to indicate the parameters mapped to the priority of the first microservice included in the configuration information of the first microservice.
  • the priority mapping information may be mciop:ingress1.path1, which means that the parameter mapped to the priority of the first microservice is mciop:ingress1.path1.
  • the VNFD includes description information of a first virtual connection point
  • the description information of the first virtual connection point includes description information of a first microservice
  • the first mapping information may be included in the description information of the first microservice.
  • the description information of the first virtual connection point further includes container object type information, where the container object type information is used to indicate that the container object type corresponding to the first virtual connection point is ingress.
  • the description information of the first microservice also includes at least one of the following: service type information (including the name of the first microservice), domain name type information (used to indicate the domain name type supported by the first microservice for configuration), and priority information (used to indicate the configuration priority supported by the first microservice).
  • service type information including the name of the first microservice
  • domain name type information used to indicate the domain name type supported by the first microservice for configuration
  • priority information used to indicate the configuration priority supported by the first microservice.
  • the VNFM can map the internal access domain names and external access domain names to corresponding parameters according to the domain name mapping information; when the domain name type information is used to indicate that the domain name types supported by the first microservice for configuration only include internal access domain names (and the configuration information of the first microservice includes internal access domain names and external access domain names), the VNFM can select the internal access domain name from the configuration information of the first microservice according to the domain name type information, and then map the internal access domain name to the corresponding parameters according to the domain name mapping information.
  • VNFD includes a reference to MCIOP, such as the original values.yaml file in MCIOP as shown in Table 13.
  • the VNFM updates the original values.yaml file according to the configuration information of the first virtual connection point and the second virtual connection point and the mapping information in the VNFD.
  • the updated values.yaml file is shown in Table 14.
  • the updated values.yaml file includes the configuration information of the first inlet container object and the configuration information of the second inlet container object.
  • Tables 13 and 14 are simplified examples of values.yaml files, which are used to illustrate the differences between the original values.yaml file and the updated values.yaml file.
  • the specific format of the values.yaml file can refer to the prior art.
  • the VNFM sends configuration information of the first ingress container object to the CISM, where the configuration information of the first ingress container object is used to create the first ingress container object.
  • the VNFM may send the updated MCIOP to the CISM so that the CISM creates a container object according to the MCIOP to complete the instantiation of the VNF.
  • the updated MCIOP includes configuration information of at least one container object, and the first inlet container object is taken as an example here.
  • S706 CISM creates a first entry container object according to the configuration information of the first entry container object.
  • CISM can also create other container objects corresponding to the VNF to complete the instantiation of the VNF.
  • the CISM (such as an ingress controller in the CISM) may allocate an access address (ie, an IP address) for the first ingress container object, and send the IP address of the first ingress container object to the VNFM.
  • an access address ie, an IP address
  • VNFM can determine the configuration information of the ingress container object corresponding to the virtual connection point according to the configuration information of the virtual connection point in the instantiation request sent by NFVO (one virtual connection point corresponds to one or more microservices), and then create an ingress container object for the microservice. Since the access address (such as fqdn) of the service defined by the ingress container object belongs to the 7th layer, it is easy to meet the access requirements of the microservice.
  • the mapping between the network element microservice and the ingress container object is realized, and the management of the ingress container object is realized by introducing parameters such as container object type information, service type information, domain name type information, priority information, etc. in the VNFD, so that the cloud-native technology can be better utilized to realize the transformation of the network element microservice, and the creation and lifecycle management of the network element microservice can be realized through MANO.
  • the above method may also include S707-S708 and/or S709-S710.
  • the NFVO sends first request information to the VNFM, where the first request information is used to request an access address of the first virtual connection point.
  • NFVO needs to check the access information of the first virtual connection point of the successfully deployed VNF.
  • the VNFM sends the access address of the first ingress container object as the access address of the first virtual connection point to the NFVO according to the first request information.
  • NFVO can send the access address of the first virtual connection point to OSS/BSS.
  • OSS/BSS sets the binding relationship between the microservice's fqdn and the IP address to the DNS server based on the IP address of the first virtual connection point (i.e., virtualCp1) fed back. For example, it can be
  • the access party can query the DNS server for the IP address corresponding to the access address.
  • the DNS server returns the IP address assigned by ingress to the access party, and then the access party sends an HTTP request to the IP address and specifies the access address of the accessed microservice in the host header, thereby achieving access to the microservice.
  • the OSS/BSS may send a second request message to the NFVO, where the second request message is used to request resource utilization information of the first microservice among the K microservices.
  • the NFVO obtains resource utilization information of at least one VDU corresponding to the first microservice according to the second request information, determines resource utilization information of the first microservice according to the resource utilization information of the VDU corresponding to the first microservice, and then sends the first microservice to the OSS/BSS. Resource utilization information of a microservice.
  • the NFVO may obtain the VNFD of the VNF according to the second request information, and the VNFD is used to indicate at least one VDU corresponding to the first microservice, and then determine that the first microservice corresponds to at least one VDU according to the VNFD.
  • the VNFD includes description information of each VDU in the at least one VDU, and the description information of the VDU includes service type information, and the service type information is used to indicate the microservice corresponding to the VDU, as shown in Table 10 above.
  • the NFVO may send an acquisition request to the VNFM, the acquisition request being used to request resource utilization information of at least one VDU corresponding to the first microservice; after receiving the acquisition request, the VNFM may acquire resource utilization information of a pod corresponding to at least one VDU from the CISM, and send the resource utilization information of the pod as the resource utilization information of the VDU to the NFVO. Furthermore, the NFVO may determine the resource utilization information of the first microservice based on the resource utilization information of the at least one VDU.
  • the OSS/BSS may determine whether it is necessary to perform operations such as expansion or update on the first microservice according to the resource utilization information of the first microservice.
  • the configuration information of the virtual connection point is carried in the first instantiation request sent by NFVO to VNFM as an example.
  • NFVO may also send the configuration information of multiple microservices to VNFM.
  • a new cell may be added to the first instantiation request to carry the configuration information of multiple microservices; accordingly, after receiving the configuration information of multiple microservices, VNFM may obtain the corresponding relationship between the virtual connection point and the microservice according to the virtualCp in VNFD, and further determine the configuration information of the virtual connection point.
  • step numbers of the flowcharts described in the above embodiments are only examples of the execution process and do not constitute a limitation on the order of execution of the steps. In the embodiments of the present application, there is no strict execution order between the steps that have no temporal dependency relationship with each other. In addition, not all the steps shown in the flowcharts are steps that must be executed, and some steps can be added or deleted based on the actual needs of each flowchart.
  • NFVO and VNFM may include hardware structures and/or software modules corresponding to the execution of each function.
  • NFVO and VNFM may include hardware structures and/or software modules corresponding to the execution of each function.
  • Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.
  • the embodiment of the present application can divide the functional units of NFVO and VNFM according to the above method example.
  • each functional unit can be divided according to each function, or two or more functions can be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or software functional unit.
  • FIG8 shows a possible exemplary block diagram of the device involved in the embodiments of the present application.
  • the device 800 may include: a processing unit 802 and a communication unit 803.
  • the processing unit 802 is used to control and manage the actions of the device 800.
  • the communication unit 803 is used to support the communication between the device 800 and other devices.
  • the communication unit 803 is also called a transceiver unit, and may include a receiving unit and/or a sending unit, which are used to perform receiving and sending operations, respectively.
  • the device 800 may also include a storage unit 801 for storing program code and/or data of the device 800.
  • the device 800 may be the VNFM in the above embodiment, or may be a component (such as a circuit or a chip) provided in the VNFM.
  • the processing unit 802 may support the device 800 to perform the actions of the VNFM in the above method examples.
  • the processing unit 802 mainly performs the internal actions of the VNFM in the method examples, and the communication unit 803 may support the communication between the device 800 and other devices.
  • the communication unit 803 is used to: receive a first instantiation request from the NFVO, the first instantiation request is used to request the instantiation of the VNF, the first instantiation request includes configuration information of a first virtual connection point of the VNF, the configuration information of the first virtual connection point includes configuration information of K microservices of the network function NF corresponding to the VNF, K is a positive integer;
  • the processing unit 802 is used to: determine, according to the configuration information of the first virtual connection point, the configuration information of a first ingress container object corresponding to the first virtual connection point, the first ingress container object is used to provide access to the K microservices;
  • the communication unit 803 is also used to: send the configuration information of the first ingress container object to the CISM, the configuration information of the first ingress container object is used to create the first ingress container object.
  • the processing unit 802 is specifically configured to: obtain a VNFD of the VNF, wherein the VNFD includes a mapping information
  • the mapping information is used to indicate a mapping relationship between the configuration information of the first virtual connection point and the configuration information of the first entry container object; and the configuration information of the first entry container object is determined according to the configuration information of the first virtual connection point and the mapping information.
  • the mapping information includes first mapping information corresponding to a first microservice among the K microservices; the first mapping information includes at least one of the following: domain name mapping information, the domain name mapping information is used to indicate parameters mapped to the domain name of the first microservice in the configuration information of the first microservice; priority mapping information, the priority mapping information is used to indicate parameters mapped to the priority of the first microservice in the configuration information of the first microservice.
  • the VNFD includes description information of the first microservice, and the first mapping information is included in the description information of the first microservice.
  • the description information of the first microservice also includes at least one of the following: service type information, the service type information including the name of the first microservice; domain name type information, the domain name type information is used to indicate the domain name type supported by the first microservice for configuration, the domain name type including an internal access domain name and/or an external access domain name; priority information, the priority information is used to indicate the configuration priority supported by the first microservice.
  • the VNFD also includes container object type information corresponding to the first virtual connection point, where the container object type information is used to indicate that the container object type corresponding to the first virtual connection point is an ingress container object.
  • the VNFD also includes description information of the VDU of the VNF, and the description information of the VDU includes service type information, where the service type information is used to indicate the microservice corresponding to the VDU.
  • the communication unit 803 is further used to: receive an access address of the first entry container object from the CISM.
  • the communication unit 803 is further used to: receive a first request message from the NFVO, the first request message being used to request an access address of the first virtual connection point; and send, according to the first request message, an access address of the first ingress container object as an access address of the first virtual connection point to the NFVO.
  • the device 800 may be the NFVO in the above embodiment, or may be a component (such as a circuit or a chip) disposed in the NFVO.
  • the processing unit 802 may support the device 800 in performing the actions of the NFVO in the above method examples.
  • the processing unit 802 mainly performs the internal actions of the NFVO in the method example, and the communication unit 803 may support the communication between the device 800 and other devices.
  • the communication unit 803 is used to: receive a second instantiation request from the OSS/BSS, the second instantiation request is used to request instantiation of the VNF, and the second instantiation request includes configuration information of M microservices of the NF corresponding to the VNF;
  • the processing unit 802 is used to: obtain configuration information of the first virtual connection point according to the configuration information of K microservices corresponding to the first virtual connection point of the VNF; wherein the K microservices belong to the M microservices, M and K are positive integers, and K is less than or equal to M;
  • the communication unit 803 is also used to: send a first instantiation request to the VNFM, the first instantiation request includes configuration information of the first virtual connection point, the configuration information of the first virtual connection point is used to determine configuration information of a first entry container object corresponding to the first virtual connection point, and the first entry container object is used to provide access to the K microservices.
  • the processing unit 802 is further used to: obtain a VNFD of the VNF, the VNFD including description information of the first virtual connection point, and the description information of the first virtual connection point is used to indicate that the first virtual connection point corresponds to the K microservices.
  • the description information of the first virtual connection point includes the names of the K microservices.
  • the communication unit 803 is also used to: receive a second request information from the OSS/BSS, where the second request information is used to request resource utilization information of a first microservice among the K microservices; the processing unit 802 is also used to: obtain resource utilization information of at least one VDU corresponding to the first microservice according to the second request information; determine the resource utilization information of the first microservice according to the resource utilization information of the VDU corresponding to the first microservice; the communication unit 803 is also used to: send the resource utilization information of the first microservice to the OSS/BSS.
  • each unit in the device can be a separately established processing element, or it can be integrated in a certain chip of the device.
  • it can also be stored in the memory in the form of a program, and called by a certain processing element of the device to execute the function of the unit.
  • these units can be fully or partially integrated together, or they can be implemented independently.
  • the processing element mentioned here can also be called a processor, which can be a kind of An integrated circuit with signal processing capability.
  • a processor which can be a kind of An integrated circuit with signal processing capability.
  • each operation or each unit of the above method can be implemented by an integrated logic circuit of hardware in a processor element or in the form of software called by a processing element.
  • the unit in any of the above devices may be one or more integrated circuits configured to implement the above method, such as one or more application specific integrated circuits (ASIC), or one or more digital singnal processors (DSP), or one or more field programmable gate arrays (FPGA), or a combination of at least two of these integrated circuit forms.
  • ASIC application specific integrated circuits
  • DSP digital singnal processors
  • FPGA field programmable gate arrays
  • the unit in the device can be implemented in the form of a processing element scheduler
  • the processing element can be a processor, such as a general-purpose central processing unit (CPU), or other processors that can call programs.
  • CPU general-purpose central processing unit
  • these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • the above unit for receiving is an interface circuit of the device, which is used to receive signals from other devices.
  • the receiving unit is an interface circuit of the chip used to receive signals from other chips or devices.
  • the above unit for sending is an interface circuit of the device, which is used to send signals to other devices.
  • the sending unit is an interface circuit of the chip used to send signals to other chips or devices.
  • FIG. 9 it is a schematic diagram of the structure of a device provided in an embodiment of the present application, which is used to implement the operation of VNFM or NFVO in the above embodiments.
  • the device 900 may include a processor 901, a memory 902, and an interface circuit 903.
  • the processor 901 may be used to process the communication protocol and the communication data, and to control the device 900.
  • the memory 902 may be used to store programs and data, and the processor 901 may execute the method performed by the AP in the embodiment of the present application based on the program.
  • the interface circuit 903 may be used for the device 900 to communicate with other devices, and the communication may be wired communication or wireless communication, and the interface circuit may also be replaced by a transceiver.
  • the above memory 902 may also be externally connected to the device 900, in which case the device 900 may include an interface circuit 903 and a processor 901.
  • the above interface circuit 903 may also be externally connected to the device 900, in which case the device 900 may include a memory 902 and a processor 901.
  • the device 900 may include a processor 901.
  • the device shown in FIG9 can implement various processes involving VNFM or NFVO in the above method embodiment.
  • the operations and/or functions of each module in the device shown in FIG9 are respectively to implement the corresponding processes in the above method embodiment.
  • the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) that contain computer-usable program code.
  • a computer-usable storage media including but not limited to disk storage, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.
  • These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

Landscapes

  • Stored Programmes (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请涉及NFV技术领域，公开一种虚拟化网络功能VNF的实例化方法及装置。其中方法包括：VNFM接收来自NFVO的第一实例化请求，第一实例化请求包括VNF的第一虚拟连接点的配置信息，第一虚拟连接点的配置信息包括VNF对应的NF的K个微服务的配置信息；进而，确定第一虚拟连接点对应的第一入口容器对象的配置信息，第一入口容器对象用于提供K个微服务的访问入口；以及，向CISM发送第一入口容器对象的配置信息，第一入口容器对象的配置信息用于创建第一入口容器对象。如此，可以实现为微服务创建入口容器对象，由于通过入口容器对象定义的微服务的访问地址可以为域名(比如fqdn)，从而便于满足微服务的访问需求。

Description

一种虚拟化网络功能VNF的实例化方法及装置
相关申请的交叉引用
本申请要求在2022年11月30日提交中国专利局、申请号为202211524508.2、申请名称为“一种虚拟化网络功能VNF的实例化方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种虚拟化网络功能VNF的实例化方法及装置。
背景技术
网络功能虚拟化(network functions virtualization，NFV)技术通过使用通用的硬件设备及虚拟化技术，构建虚拟化网络功能(virtualization network functions，VNF)，进而通过VNF承载传统网络中专用设备的功能，降低因部署专用设备而带来的昂贵成本。
容器管理平台是基于容器化技术实现的平台，例如kubernetes(简称K8S)平台。一个容器管理平台管理一个集群，该集群包括若干个物理机或虚拟机，容器对象可以部署在物理机或在虚拟机上。
随着容器化技术的不断发展，容器管理平台被引入到NFV架构中。在引入容器管理平台的NFV架构中，如何满足微服务的访问需求，仍需进一步研究。
发明内容
本申请提供了一种VNF的实例化方法及装置，用于实现为微服务创建入口容器对象，便于满足微服务的访问需求。
第一方面，本申请实施例提供一种VNF的实例化方法，该方法可以由VNFM执行，在该方法中，VNFM接收来自网络功能虚拟化编排器NFVO的第一实例化请求，所述第一实例化请求用于请求实例化所述VNF，所述第一实例化请求包括所述VNF对应的网络功能NF的K个微服务的配置信息，K为正整数；根据所述K个微服务的配置信息，确定第一入口容器对象的配置信息，所述第一入口容器对象用于提供所述K个微服务的访问入口；向容器基础设施管理器CISM发送所述第一入口容器对象的配置信息，所述第一入口容器对象的配置信息用于创建所述第一入口容器对象。
具体来说，在该方法中，VNFM接收来自NFVO的第一实例化请求，所述第一实例化请求用于请求实例化所述VNF，所述第一实例化请求包括所述VNF的第一虚拟连接点的配置信息，所述第一虚拟连接点的配置信息包括所述VNF对应的网络功能NF的K个微服务的配置信息，K为正整数；根据所述第一虚拟连接点的配置信息，确定所述第一虚拟连接点对应的第一入口容器对象的配置信息，所述第一入口容器对象用于提供所述K个微服务的访问入口；向容器基础设施管理器CISM发送所述第一入口容器对象的配置信息，所述第一入口容器对象的配置信息用于创建所述第一入口容器对象。
采用上述方法，VNFM可以根据NFVO发送的实例化请求中微服务的配置信息(或者包括微服务的配置信息的虚拟连接点的配置信息)，确定用于为微服务提供访问入口的入口容器对象的配置信息，进而实现为微服务创建入口容器对象，由于通过入口容器对象定义的微服务的访问地址(比如fqdn)属于7层，从而便于满足微服务的访问需求。
在一种可能的设计中，根据所述第一虚拟连接点的配置信息，确定所述第一虚拟连接点对应的第一入口容器对象的配置信息，包括：获取所述VNF的虚拟化网络功能描述VNFD，所述VNFD包括映射信息，所述映射信息用于指示所述第一虚拟连接点的配置信息与所述第一入口容器对象的配置信息之间的映射关系；根据所述第一虚拟连接点的配置信息和所述映射信息，确定所述第一入口容器对象的配置信息。
在一种可能的设计中，所述映射信息包括所述K个微服务中第一微服务对应的第一映射信息；所述第一映射信息包括以下至少一项：域名映射信息，所述域名映射信息用于指示所述第一微服务的配置信息中的所述第一微服务的域名所映射的参数；优先级映射信息，所述优先级映射信息用于指示所述第一微服务的配置信息中的所述第一微服务的优先级所映射的参数。
在一种可能的设计中，所述VNFD包括所述第一微服务的描述信息，所述第一映射信息包含在所述第一微服务的描述信息中。
在一种可能的设计中，所述第一微服务的描述信息还包括以下至少一项：
服务类型信息，所述服务类型信息包括所述第一微服务的名称；
域名类型信息，所述域名类型信息用于指示所述第一微服务支持配置的域名类型，所述域名类型包括内部访问域名和/或外部访问域名；
优先级信息，所述优先级信息用于指示所述第一微服务支持配置优先级。
如此，通过在VNFD内对虚拟连接点进行扩展，实现了网元微服务与入口容器对象之间的映射，并通过在VNFD中引入容器对象类型信息、服务类型信息、域名类型信息，优先级信息等参数实现了对入口容器对象的管理，从而可以更好的利用云原生的技术实现网元微服务的改造，并通过MANO实现网元微服务化的创建以及生命周期管理。
在一种可能的设计中，所述VNFD还包括所述第一虚拟连接点对应的容器对象类型信息，所述容器对象类型信息用于指示所述第一虚拟连接点对应的容器对象类型为入口容器对象。
在一种可能的设计中，所述VNFD还包括所述VNF的虚拟部署单元VDU的描述信息，所述VDU的描述信息包括服务类型信息，所述服务类型信息用于指示所述VDU对应的微服务。
在一种可能的设计中，所述方法还包括：接收来自所述CISM的所述第一入口容器对象的访问地址。
在一种可能的设计中，所述方法还包括：接收来自所述NFVO的第一请求信息，所述第一请求信息用于请求所述第一虚拟连接点的访问地址；根据所述第一请求信息，将所述第一入口容器对象的访问地址作为所述第一虚拟连接点的访问地址发送给所述NFVO。
第二方面，本申请实施例提供一种VNF的实例化方法，该方法可以由NFVO执行，在该方法中，NFVO接收来自运营支撑系统/业务支撑系统OSS/BSS的第二实例化请求，所述第二实例化请求用于请求实例化所述VNF，所述第二实例化请求包括所述VNF对应的NF的M个微服务的配置信息；根据所述VNF的第一虚拟连接点对应的K个微服务的配置信息，得到所述第一虚拟连接点的配置信息；其中，所述K个微服务属于所述M个微服务，M、K为正整数，K小于或等于M；向VNFM发送第一实例化请求，所述第一实例化请求包括所述第一虚拟连接点的配置信息，所述第一虚拟连接点的配置信息用于确定所述第一虚拟连接点对应的第一入口容器对象的配置信息，所述第一入口容器对象用于提供所述K个微服务的访问入口。
在一种可能的设计中，所述方法还包括：获取所述VNF的VNFD，所述VNFD包括所述第一虚拟连接点的描述信息，所述第一虚拟连接点的描述信息用于指示所述第一虚拟连接点对应所述K个微服务。
在一种可能的设计中，所述第一虚拟连接点的描述信息包括所述K个微服务的名称。
在一种可能的设计中，所述方法还包括：接收来自所述OSS/BSS的第二请求信息，所述第二请求信息用于请求所述K个微服务中第一微服务的资源利用信息；根据所述第二请求信息，获取所述第一微服务对应的至少一个VDU的资源利用信息；根据所述第一微服务对应的VDU的资源利用信息，确定所述第一微服务的资源利用信息；向所述OSS/BSS发送所述第一微服务的资源利用信息。
在一种可能的设计中，所述方法还包括：获取所述VNF的VNFD，所述VNFD用于指示所述第一微服务对应的至少一个VDU。
在一种可能的设计中，所述VNFD包括所述至少一个VDU中每个VDU的描述信息，所述VDU的描述信息包括服务类型信息，所述服务类型信息用于指示所述VDU对应的微服务为所述第一微服务。
可以理解的是，第二方面所描述的方法与第一方面所描述的方法相对应，因此，第二方面所描述的方法中相关技术特征的有益效果可以参照第一方面，具体不再赘述。
第三方面，本申请提供一种VNF的实例化装置，该装置具备实现上述第一方面或第二方面涉及的功能，比如，所述装置包括执行上述第一方面或第二方面涉及操作所对应的模块或单元或手段，所述功能或单元或手段可以通过软件实现，或者通过硬件实现，也可以通过硬件执行相应的软件实现。
在一种可能的设计中，所述装置包括处理单元、通信单元，其中，通信单元可以用于收发信号，以实现该装置和其它装置之间的通信，比如，通信单元用于向终端设备发送系统信息；处理单元可以用于执行该装置的一些内部操作。处理单元、通信单元执行的功能可以和上述第一方面或第二方面涉及的操作相对应。
在一种可能的设计中，所述装置包括处理器，处理器可以用于与存储器耦合。所述存储器可以保存实现上述第一方面或第二方面涉及的功能的必要计算机程序或指令。所述处理器可执行所述存储器存储 的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述装置实现上述第一方面或第二方面任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述装置包括处理器和存储器，存储器可以保存实现上述第一方面或第二方面涉及的功能的必要计算机程序或指令。所述处理器可执行所述存储器存储的计算机程序或指令，当所述计算机程序或指令被执行时，使得所述装置实现上述第一方面或第二方面任意可能的设计或实现方式中的方法。
在一种可能的设计中，所述装置包括处理器和接口电路，其中，处理器用于通过所述接口电路与其它装置通信，并执行上述第一方面或第二方面任意可能的设计或实现方式中的方法。
可以理解地，上述第三方面中，处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现。此外，以上处理器可以为一个或多个，存储器可以为一个或多个。存储器可以与处理器集成在一起，或者存储器与处理器分离设置。在具体实现过程中，存储器可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
第四方面，本申请提供一种VNF的实例化系统，该系统可以包括VNFM和NFVO，VNFM用于执行上述第一方面的任一种可能的设计中的方法，NFVO用于执行上述第二方面的任一种可能的设计中的方法。
第五方面，本申请提供一种计算机可读存储介质，所述计算机存储介质中存储有计算机可读指令，当计算机读取并执行所述计算机可读指令时，使得计算机执行上述第一方面或第二方面的任一种可能的设计中的方法。
第六方面，本申请提供一种计算机程序产品，当计算机读取并执行所述计算机程序产品时，使得计算机执行上述第一方面或第二方面的任一种可能的设计中的方法。
第七方面，本申请提供一种芯片，所述芯片包括处理器，所述处理器与存储器耦合，用于读取并执行所述存储器中存储的软件程序，以实现上述第一方面或第二方面的任一种可能的设计中的方法。
附图说明
图1为本申请实施例提供的一种NFV架构示意图；
图2为本申请实施例提供的kubernetes容器管理编排架构图；
图3为本申请实施例提供的引入容器管理平台的NFV架构；
图4A为本申请实施例提供的service和pod的关系示意图；
图4B为本申请实施例提供的ingress和service的关系示意图；
图5为本申请实施例提供的对VNF进行容器化部署的实现流程示意图；
图6为本申请实施例提供的一种对应关系示例；
图7为本申请实施例提供的VNF的实例化方法所对应的流程示意图；
图8为本申请实施例中所涉及的装置的可能的示例性框图；
图9为本申请实施例提供的一种装置的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。本申请将围绕可包括多个设备、组件、模块等的系统来呈现各个方面、实施例或特征。应当理解和明白的是，各个系统可包括另外的设备、组件、模块等，并且/或者可以并不包括结合附图讨论的所有设备、组件、模块等。此外，还可以使用这些方案的组合。
在本申请实施例中，“示例性地”、“比如”等词语用于表示例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例”一词旨在以具体方式呈现概念。本申请实施例中，“的(of)”，“相应的(corresponding，relevant)”和“对应的(corresponding)”有时可以混用，应当指出的是，在不强调其区别时，其所要表达的含义是一致的。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案， 并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
下面对本申请实施例提供的网络架构进行介绍。
一、NFV架构
参见图1，为本申请实施例提供的一种NFV架构示意图。如图1所示，该NFV架构可以包括NFV管理和编制系统(NFV management and orchestration system，NFV-MANO)110，NFV基础设施(NFV infrastructure，NFVI)150，多个VNF140，多个设备管理(element management，EM)130，以及一个或多个运营支撑系统/业务支撑系统(operation support system/business support system，OSS/BSS)120。其中，NFV-MANO 110可以包括NFV编排器(NFV orchestrator，NFVO)111、一个或多个虚拟网络功能管理器(virtualized network function manager，VNFM)112，以及一个或多个虚拟基础设施管理器(virtualized infrastructure manager，VIM)113。
(1)NFVO111：主要负责处理虚拟化业务的生命周期管理，以及虚拟基础设施及NFVI中虚拟资源的分配和调度等。NFVO111可以与一个或多个VNFM112通信，以执行资源相关请求，发送配置信息给VNFM112，收集VNF140的状态信息。另外，NFVO111也可与VIM113通信，以执行资源分配和/或预留、交换虚拟化硬件资源配置和状态信息。
(2)VNFM112：主要负责一个或多个VNF的生命周期管理，比如实例化(instantiating)VNF140、更新(updating)VNF140、查询VNF140、弹性伸缩(scaling)VNF140、终止(terminating)VNF140。VNFM112可以与VNF140通信，以完成VNF生命周期管理及交换配置和状态信息。在NFV架构中VNFM可以有多个，负责对不同类型的VNF进行生命周期管理。
(3)VIM113：主要负责控制和管理VNF140与计算硬件1521、存储硬件1522、网络硬件1523、虚拟计算1511(例如虚拟机(virtual machine，VM))、虚拟存储1512和虚拟网络1513的交互。例如VIM113执行资源管理功能，包括管理基础设施资源、分配(例如增加资源给虚拟容器)及运行功能(例如收集NFVI故障信息)。VNFM112可以与VIM113通信，以请求资源分配、交换虚拟化硬件资源配置和状态信息。
(4)NFVI150：可以包括计算硬件1521、存储硬件1522、网络硬件1523组成的硬件资源层、虚拟化层、以及虚拟计算1511、虚拟存储1512和虚拟网络1513组成的虚拟资源层。硬件资源层中的计算硬件1521可以为专用的处理器或通用的用于提供处理和计算功能的处理器，如中央处理器(central process unit，CPU)；存储硬件1522用于提供存储能力，例如，磁盘或网络附属存储(network attached storage，NAS)；网络硬件1523可以是交换机、路由器和/或其他网络设备。NFVI 150中的虚拟化层用于抽象硬件资源层的硬件资源，将VNF 140和硬件资源所属的物理层解耦，向VNF提供虚拟资源。虚拟资源层可以包括虚拟计算1511、虚拟存储1512和虚拟网络1513。虚拟计算1511、虚拟存储1512可以以虚拟机或其他虚拟容器的形式向VNF140提供，例如一个或多个虚拟机组成一个VNF140。虚拟化层通过抽象网络硬件1523形成虚拟网络1513。虚拟网络1513，用于实现多个虚拟机之间，或多个承载VNF的其他类型的虚拟容器之间的通信。
(5)EM130：是传统电信系统中用于对设备进行配置、管理的系统；在NFV架构中，EM130也可以用于对VNF进行配置和管理，以及向VNFM112发起新的VNF的实例化等生命周期管理操作。
(6)OSS/BSS120：支持各种端到端电信业务，比如OSS支持的管理功能包括：网络配置、业务提供、故障管理等；BSS处理订单、付费、收入等，支持产品管理、订单管理、收益管理及客户管理。
(7)VNF140：对应于传统非虚拟化网络中的物理网络功能(physical network function，PNF)，如虚拟化的核心网节点(例如接入和移动性管理功能(access and mobility management function，AMF)、会话管理功能(session management function，SMF)网元等)。网络功能的功能性行为和状态与虚拟化与否无关，NFV技术需求希望VNF和PNF拥有相同的功能性行为和外部接口。
二、容器即服务架构
在电信网络中，通常会用到另一种虚拟化技术，即容器即服务(container as a service，CaaS)技术，CaaS是一种特定类型的平台即服务(platform as a service，PaaS)。在电信网络功能云化进程中引入容器即服务架构，为电信行业的开发运维(DevOps)带来了敏捷性的变革。与之相呼应的变化是，传统的大颗粒单体网络功能逐渐被解构进行服务化，甚至进一步进行微服务化。每个服务化的功能可以独立进行开发、交付和维护，版本的升级变得更加频繁；但另一方面容器化网络功能数量的激增不会对互操 作测试带来指数级工作量的增长，稳定的应用程序编程接口(application programming interface，API)定义保证了接口功能调用的一致性和可靠性。由于CaaS技术没有虚拟硬件，也没有操作系统，只有进程，因此，CaaS技术相比NFV技术更轻量，管理也更方便。
当前在容器管理编排领域流行的应用是谷歌(google)基于开源平台的kubernetes容器集群管理技术，一个kubernetes平台管理一个集群，集群内包含若干个物理机资源或者虚拟机资源，如果管理的是物理机资源，则kubernetes将创建的容器直接部署在物理机上，如果管理的是虚拟机资源，则kubernetes将创建的容器部署在虚拟机上。helm是K8S的包管理器，主要负责管理用于部署应用的部署包(也称为helm chart)，helm chart中可封装K8S原生应用程序的另一种标记语言(yet another markup language，YAML)文件。helm可以包含在K8S中，也可以是独立的包管理工具。本申请实施例中以helm包含在K8S中为例。
图2为kubernetes容器管理编排架构图。如图2所示，kubernetes将集群中的设备划分为一个kubernetes主节点(master)和一群工作节点(node)。其中，master节点上运行着集群管理相关的一组进程，例如应用程序编程接口服务(application programming interface server，API server)、复制控制器(replication controller，RC)等，这些进程实现了整个集群的资源管理、豆荚(pod)调度、弹性伸缩、安全控制、系统监控和纠错等管理功能。在每个Node上运行kubelet、kube-proxy、容器引擎三个组件，负责对本节点上的pod的生命周期进行管理，以及实现服务代理的功能。pod是kubernetes中的基本调度单位。
其中，API Server提供了资源对象的唯一操作入口，其他所有组件都必须通过它提供的API接口来操作资源数据，通过对相关的资源数据“全量查询”以及“变化监听”，完成相关的业务功能。
controller manager是集群的管理控制中心，其主要目的是实现kubernetes集群的故障检测和恢复自动化工作。例如，可以根据RC的定义完成pod的复制或移除，以确保pod实例数符合RC的定义、根据服务(service)与pod的管理关系，完成service的端点(endpoints)对象的创建和更新、node的发现、管理和状态监控、以及本地缓存的容器镜像文件的清理等。
kubelet组件负责本节点上的pod的创建、修改、监控、删除等全生命周期管理，同时Kubelet定时向API Server上报本节点的状态信息。
proxy组件用于实现service的代理与软件模式的负载均衡。
docker组件为容器的运行环境。
三、NFV技术与CaaS技术的结合
随着NFV技术的不断发展，提出了将CaaS技术和NFV技术进行结合，从而形成了NFV MANO系统和容器管理编排系统进行互操作的场景。如图3所示，为引入容器管理平台的NFV架构的一种示例。
在图3中，在NFV MANO中增加容器基础设施管理器(container infrastructure service management，CISM)114。CISM为NFV架构中的容器管理平台，负责管理VNF所调用的容器对象，包括容器对象的创建、更新和删除等。当VNF以容器形式部署时，CISM114可基于VNFM112的请求创建容器对象。
本申请实施例中将以CISM为kubernetes为例进行描述。此外，图3中，除CISM以外的网元可以参照上述图1中的描述，不再赘述。
上述图1至图3所描述的网元(如NFVO、VNFM、CISM等)仅为示例而非限定，在标准演进的过程中，上述各网元的名称可以发生变化，各网元执行的功能可以被进一步地拆分或组合，本申请实施例不做限制。
可以理解的是，本申请实施例中“多个”是指两个或两个以上，鉴于此，本申请实施例中也可以将“多个”理解为“至少两个”。“至少一个”，可理解为一个或多个，例如理解为一个、两个或更多个。例如，包括至少一个，是指包括一个、两个或更多个，而且不限制包括的是哪几个，例如，包括A、B和C中的至少一个，那么包括的可以是A、B、C、A和B、A和C、B和C、或A和B和C。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，字符“/”，如无特殊说明，一般表示前后关联对象是一种“或”的关系。本申请实施例中的术语“系统”和“网络”可被互换使用。
除非有相反的说明，本申请实施例提及“第一”、“第二”等序数词用于对多个对象进行区分，不用于限定多个对象的顺序、时序、优先级或者重要程度。
下面对本申请实施例所涉及的相关技术特征进行解释说明。需要说明的是，这些解释是为了让本申请实施例更容易被理解，而不应该视为对本申请所要求的保护范围的限定。
(1)容器对象
kubernetes可以创建多种容器对象，比如pod容器对象、service容器对象和入口(ingress)容器对象。容器对象在欧洲电信标准协会(European telecommunications standards institute，ETSI)NFV标准中对应的概念是被管理的容器基础设施对象(managed container infrastructure object，MCIO)。
pod容器对象：kubernetes在管理的集群上创建容器是以pod为最小单元，其中一个pod内可以包含1个或者多个容器，因此pod也可以称为容器舱。kubernetes的pod是有生命周期的，它们可以被创建，也可以被销毁，一旦被销毁生命就永远结束。kubernetes针对资源的关联可以动态地创建和销毁pod(例如，需要进行扩缩容，或者执行滚动升级)。
service容器对象：service是kubernetes的核心概念，多个pod能够被同一个service访问到，service通过标签来选取关联的pod，即使pod发生了改变，通过访问service也可以访问到对应的应用(其它pod或者新创建的pod)。如图4A所示，为service和pod的关系示意图。
此外，service可以提供负载均衡的能力，比如根据所关联的pod当前的负载情况，将访问service的请求路由到合适的pod上进行处理。service的表现形式为IP:端口(Port)，即工作在TCP/IP层，即service可以提供4层负载均衡的能力。比如，一个service的定义如表1所示。
表1：service的定义示例
ingress容器对象：ingress是对service的更高层次的抽象，service是工作在TCP/IP层，而对于基于超文本传输协议(hypertext transfer protocol，HTTP)的服务来说，不同的统一资源定位符(uniform resource locator，URL)地址经常对应到不同的后端服务或者虚拟服务器，这些应用层的转发机制仅通过kubernetes的service机制是无法实现的。kubernetes V1.1版本中新增了ingress，以便将不同URL的访问请求转发到后端不同的service，实现HTTP层的业务路由机制。如图4B所示，为ingress和service的关系示意图。
示例性地，ingress中可以定义不同的规则来关联多个service。比如，一个ingress中规则的定义如表2所示。
表2：ingress中规则的定义示例

如此，访问方通过访问不同service的访问地址，就可以访问到不同的service，而通过ingress rules定义的service的访问地址(即host值)属于7层，即全限定域名(fully qualified domain name，fqdn)地址。在实现ingress的过程中，当一个ingress创建成功后，可以将为该ingress分配的互联网协议(internet protocol，IP)地址和rules里定义的fqdn一起配置在外部访问的域名系统(domain name system，DNS)服务器中，对于访问方，在获取到service的访问地址(即host中定义的service的访问地址)后，会向DNS服务器查询访问地址对应的IP地址，DNS服务器将ingress分配的IP地址返回给访问方，进而访问方向该IP地址发送HTTP请求，并在host头中指定访问的service的访问地址，从而实现对service的访问。
可以理解的是，本申请实施例所描述的三种容器对象仅为一种示例，这三种容器对象也可以有其它可能的名称，比如随着标准协议的演进，入口容器对象可以有其它名称，本申请实施例对此不做限定。
(2)VNF部署模板
NFV中虚拟化的网络业务称为一个网络服务(network service，NS)，比如IP多媒体子系统(IP multimedia subsystem，IMS)网络，或一个第五代(the 5th generation，5G)核心网网络。一个NS中可以包含若干个VNF。
一个NS在进行虚拟化部署时，业务请求方首先需要向业务提供方提交该NS的描述信息，称为网络服务描述(network service descriptor，NSD)或NS部署模板。NSD包括NS的拓扑结构以及NS包含的每个VNF的描述信息，称为VNF描述(VNF descriptor，VNFD)或VNF部署模板。其中，拓扑结构信息中可包含虚拟化连接信息(例如，网络服务虚拟化连接模板(network service virtual link descriptor，NsVld))，该虚拟化连接信息可用于描述VNF之间的连接，例如，描述连接类型、带宽等信息。
VNFD用于提供VNF的描述信息，VNFD可包括虚拟部署单元(virtualization deployment unit connection point，VDU)、连接点模板(connection point descriptor，CPD)和虚拟连接模板(virtual link descriptor，VLD)等。对于容器实现，VNFD里还可以包含有对被管理的容器基础设施对象包(managed container infrastructure object packages，MCIOP)的引用，MCIOP例如可以为kubernetes使用的helm chart。
VDU：对于虚拟机实现，一个VDU代表一个虚拟机，该VDU的描述信息可包括该虚拟机的资源需求，例如创建该虚拟机所需的资源类型以及每种资源类型的资源数量等。对于容器实现，一个VDU代表一组容器，该VDU的描述信息可包括这一组容器的资源需求，用于表示部署这组容器所需的资源信息，这组容器内的容器都具有相同的资源需求，并且公用相同的网络信息。
CPD：可包括VNF的外部连接点的描述信息，外部连接点比如可以为虚拟连接点(virtual connection point，virtual Cp)。
VLD：可描述VDU之间的虚拟网络连接需求，例如连接类型和/或带宽等信息。
(3)微服务
以5G通信系统为例，5G通信系统的核心网架构中定义了多个网元，比如AMF网元、SMF网元等；一个网元可以理解为一个网络功能(network function，NF)。进一步地，每个网元内还定义了多个 微服务，比如AMF网元内定义的微服务如表3所示。
表3：AMF网元内定义的微服务示例
其中，每个微服务可以通过定义相应的域名(比如fqdn)供其他网元或者微服务访问和调用。本申请实施例中的域名可以分为两种类型，即内部访问域名和外部访问域名。当一个微服务同时支持内部访问和外部访问时，该微服务可以包括内部访问域名和外部访问域名；比如以namf_location为例，namf_location的内部访问域名可以为myAMF_locati on.mynetwork.com，外部访问域名可以为myAMF_location_external.mynetwork.com。
通过引入网元微服务化，可以使得微服务之间独立，不同微服务的部署、升级和扩缩容可以单独进行，不影响网元内的其他微服务，从而在使用上更加方便，升级更加敏捷。
基于上述内容的描述，在NFV架构中引入容器管理平台，可以对VNF进行容器化部署(即实例化VNF)。下面结合图5描述一种可能的实现流程。
图5为对VNF进行容器化部署的实现流程示意图，如图5所示，该流程可以包括：
S501，OSS/BSS向NFVO发送实例化请求1，实例化请求1用于请求VNF的实例化。
示例性地，实例化请求1中可以包括需要实例化的VNF的VNFD的信息，比如VNFD的标识(即VnfdId)。
S502，NFVO根据实例化请求1向VNFM发送实例化请求2，实例化请求2用于请求VNF的实例化。
示例性地，实例化请求2中可以包括需要实例化的VNF的VNFD的信息，比如VNFD的标识(即VnfdId)。
S503，VNFM根据实例化请求2，获取VNF的VNFD文件(或VNFD文件包)，并根据VNFD文件，确定VNF对应的至少一个容器对象的配置信息。
此处，VNFM获取VNF的VNFD文件的方式可以有多种，作为一种可能的实现，VNFM接收到实例化请求2后，可以向NFVO发送VNFD请求，该VNFD请求用于请求获取VNFD文件，例如该VNFD请求包括该VNFD文件的标识。相应的，NFVO从VNFM接收该VNFD请求。NFVO确定与VNFD文件的标识对应的VNFD文件，并将该VNFD文件发送给VNFM。
示例性地，VNFD文件包可以包括VNFD文件和MCIOP，还可以包括其它可能的文件，具体不做限定；本申请实施例中的VNFD文件也可以简称为VNFD。比如VNFD文件包的例子如表4所示。
表4：VNFD文件包示例
上述myVNFD.yaml文件可以包括至少一个VDU的描述信息，以VDU_1为例，VDU_1的描述信息如表5所示。
表5：VDU_1的描述信息示例
其中，VDU_mapping中描述了VDU_1的配置信息与MCIOP中的参数的映射关系。
上述MCIOP中可以包括vdu对应的pod的参数(values.yaml文件)，其中，values.yaml文件如表6所示。
表6：values.yaml文件示例
VNFM可以根据VDU_mapping中的对应关系，对values.yaml文件中相应参数的取值进行更新，即使用min_number_of_instances的取值更新podDB的minReplicas的取值，max_number_of_instances的取值更新podDB的maxReplicas的取值。更新后的values.yaml文件如表7所示。
表7：更新后的values.yaml文件示例
可以理解的是，上述表7中更新后的values.yaml文件所包括的内容可以理解为VDU_1对应的pod的配置信息，上述是确定VDU_1对应的pod的配置信息为例进行描述的。VNF可以包括多个VDU，VNFM确定其它VDU对应的pod的配置信息的方式可以参照上文实施。
S504，VNFM向CISM发送至少一个容器对象的配置信息；相应地，CISM接收至少一个容器对象的配置信息。
此处，VNFM可以向CISM发送更新后的MCIOP，更新后的MCIOP包括至少一个容器对象的配置信息，比如更新后的MCIOP包括上述VDU_1对应的pod的配置信息，还包括其它VDU对应的pod的配置信息。
S505，CISM根据至少一个容器对象的配置信息，创建至少一个容器对象，并向VNFM发送实例化成功的响应。
S506，VNFM向NFVO发送实例化成功的响应。
S507，NFVO向OSS/BSS发送实例化成功的响应。
如上可以看出，VNF的VNFD中包括对MCIOP的引用，从而可以实现VNF的容器化部署。而当在网元中定义微服务后，一种可能的方式是，通过kubernetes中的service来实现微服务的容器化部署。具体来说，ETSI NFV标准中将service的概念引入到VNFD里，通过VNFD中的virtualCp来描述service，VDU表示pod。示例性地，目前virtualCp定义的参数如表8所示。
表8：virtualCp定义的参数示例
其中，上述servicePortData包括用于描述service的参数，比如port等，具体可以参照ETSI NFV标准，不再赘述。
然而，service只提供4层(TCP/IP)负载均衡的能力，而没有7层的能力(比如基于应用层协议转发，例如http、可以根据域名、url等转发)，进而不能通过定义fqdn来访问service。而微服务是通过定义fqdn供其他网元或者微服务访问，因此，当通过kubernetes中的service来实现微服务的容器化部署时，无法满足微服务的访问需求。
基于此，本申请实施例提供一种VNF的实例化方法，通过入口容器对象(即ingress)对网元微服务进行部署，由于通过ingress定义的service的访问地址属于7层(参照上文有关ingress的描述)，从而便于满足微服务的访问需求。
下面结合附图介绍本申请实施例提供的技术方案。
示例性地，在本申请实施例提供的方法中，可以对VNFD进行改进，比如可以在VNFD的virtualCP中定义新的参数，实现微服务与ingress之间的映射，以便于通过ingress对网元微服务进行部署。
下面结合一个具体示例，对改进VNFD的具体实现进行描述。
以VNF包括两个虚拟连接点为例，这两个虚拟连接点分为第一虚拟连接点(表示为virtualCp1)和第二虚拟连接点(表示为virtualCp2)。VNFD可以包括第一虚拟连接点的描述信息和第二虚拟连接点的描述信息，以第一虚拟连接点为例，第一虚拟连接点的描述信息可以包括容器对象类型(mcio_type)信息，容器对象类型信息用于指示第一虚拟连接点对应的容器对象类型，该容器对象类型可以为ingress或service，还可以为其它可能的容器类型。本申请实施例中是以第一虚拟连接点对应的容器对象类型为ingress为例进行描述的。
进一步地，第一虚拟连接点的描述信息还包括K个微服务的描述信息，即第一虚拟连接点对应K个微服务。比如，K个微服务包括第一微服务，以第一微服务为例，第一微服务的描述信息包括以下至少一项：
①服务类型(service_type)信息，服务类型信息可以包括第一微服务的名称。
②域名类型(host_type)信息，域名类型信息用于指示第一微服务支持配置的域名类型，域名类型包括内部(internal)访问域名和/或外部(external)访问域名。
③域名映射(mapping)信息，域名映射信息用于指示第一微服务的域名所映射的参数。
④优先级(priority)信息，优先级信息用于指示第一微服务支持配置优先级。
⑤优先级映射信息，优先级映射信息用于指示第一微服务的优先级所映射的参数。
基于上述描述，下面结合表9对第一虚拟连接点和第二虚拟连接点的描述信息进行说明。
表9：第一虚拟连接点和第二虚拟连接点的描述信息示例

进一步地，针对于VNFD中的VDU，如上所述，一个虚拟连接点可以对应多个微服务和多个VDU，为建立微服务和VDU之间的关联，本申请实施例中，可以在VDU中新增服务类型信息，服务类型信息用于指示VDU对应的微服务。下面结合表10，对上述表9中的VDU_1至VDU_5进行说明。
表10：VNFD中的VDU示例

其中，上述表9和表10所描述的对应关系如图6所示。
可以理解的是，上述主要对VNFD中的virtualCp和VDU进行了描述，上述表9和表10仅为一种可能的示例。此外，VNFD中还可以包括其它可能的信息，具体可以参照现有技术，此处不再赘述。
下面对本申请实施例提供的VNF的实例化的流程进行描述，该流程中所涉及的VNFD可以为上述改进后的VNFD。
在下文的介绍过程中，以该方法应用于图3所示的NFV架构为例，也就是说，下文中的OSS/BSS可以是图3所示的OSS/BSS120，NFVO可以是图3所示的NFVO111，VNFM可以是图3所示的VIM112，CISM可以是图3所示的CISM114。
图7为本申请实施例提供的VNF的实例化方法所对应的流程示意图。如图7所示，该方法包括：
S701，OSS/BSS向NFVO发送第二实例化请求，第二实例化请求用于请求实例化VNF，第二实例化请求包括VNF对应的NF的M个微服务的配置信息；相应地，NFVO接收第二实例化请求。
示例性地，M个微服务中包括第一微服务，第一微服务的配置信息可以包括以下至少一项：第一微服务的名称(serviceName)、第一微服务的域名、第一微服务的优先级；M为正整数。其中，第一微服务的域名可以包括内部访问域名(表示为fqdn)和外部访问域名(表示为interPlmnFqdn)。以M个微服务包括namf-location、namf-mt、namf-communication(即M＝3)为例，M个微服务参见表11所示。
表11：M个微服务的配置示例
可选地，第二实例化请求还可以包括其它可能的信息，比如可以包括VNF的VNFD的标识。
可以理解的是，第二实例化请求的目的是用于请求VNF的实例化，具体实现中可以通过多种可能的请求实现，比如第二实例化请求可以为NS的实例化请求或NS的更新请求，本申请实施例中对此不做限定。
S702，NFVO根据VNF的第一虚拟连接点对应的K个微服务的配置信息，得到第一虚拟连接点的配置信息。
此处，K个微服务属于M个微服务，也即K个微服务为M个微服务中的部分或全部微服务，K为正整数，且K小于或等于M。
示例性地，NFVO可以先确定第一虚拟连接点对应M个微服务中的哪些微服务，进而在确定出第一虚拟连接点对应K个微服务后，根据K个微服务的配置信息，得到第一虚拟连接点的配置信息。其中，NFVO确定第一虚拟连接点对应的微服务的具体实现可以有多种，比如NFVO可以获取VNF的VNFD，VNFD中包括第一虚拟连接点的描述信息(比如前文表9所示)，第一虚拟连接点的描述信息用于指示第一虚拟连接点对应K个微服务。比如，第一虚拟连接点的描述信息包括K个微服务的名称(即service_type)。
可以理解的是，NFVO还可以确定VNF的其它虚拟连接点(比如第二虚拟连接点)的配置信息。以VNF的第一虚拟连接点对应namf-location和namf-mt，第二虚拟连接点对应namf-communication。第一虚拟连接点和第二虚拟连接点的配置信息参加表12所示。
表12：第一虚拟连接点和第二虚拟连接点的配置信息示例
S703，NFVO向VNFM发送第一实例化请求，第一实例化请求包括VNF的第一虚拟连接点的配置信息；相应地，VNFM接收第一实例化请求。
此处是以第一实例化请求包括VNF的第一虚拟连接点的配置信息，第一实例化请求还可以包括VNF的其它虚拟连接点(比如第二虚拟连接点)的配置信息。
示例性地，第一实例化请求可以包括extVirtualLink参数(或者说信元)，NFVO可以将第一虚拟连接点和第二虚拟连接点的配置信息添加在extVirtualLink参数中。其中，extVirtualLink参数用于描述VNF对外连接的网络信息，extVirtualLink里包含(一个或多个)VNF的外部连接点(即extCp)的配置信息。在本申请实施例中，virtualCp1和virtualCp2作为一种extCp对外提供连接信息，所以第一虚拟连接点和第二虚拟连接点的配置信息可以添加在extCp中，如上述表12所示。
可选地，第一实例化请求还可以包括其它可能的信息，比如可以包括VNF的VNFD的标识。
S704，VNFM根据第一虚拟连接点的配置信息，确定第一虚拟连接点对应的第一入口容器对象的配置信息，第一入口容器对象用于提供K个微服务的访问入口。
示例性地，VNFM可以获取VNF的VNFD，VNFD包括映射信息，映射信息用于指示第一虚拟连 接点的配置信息与第一入口容器对象的配置信息之间的映射关系；进而，VNFM根据第一虚拟连接点的配置信息和映射信息，确定第一入口容器对象的配置信息。其中，VNFM获取VNF的VNFD的具体实现方式可以有多种，比如参照S503中的描述，不再赘述。
可以理解的是，映射信息用于将VNFD中虚拟连接点的信息映射为CISM可解析的信息(即入口容器对象的配置信息)。作为一种可能的实现，映射信息可以包括K个微服务分别对应的第一至第K映射信息。以第一微服务对应的第一映射信息为例，第一映射信息可以包括以下至少一项：
①域名映射信息，用于指示第一微服务的配置信息包括的第一微服务的域名所映射的参数。
比如，参见表9所示，域名映射信息可以为mciop:ingress1.host1、mciop:ingress1.host2，即表示第一微服务的内部访问域名所映射的参数为mciop:ingress1.host1，第一微服务的外部访问域名所映射的参数为mciop:ingress1.host2。
②优先级映射信息，用于指示第一微服务的配置信息包括的第一微服务的优先级所映射的参数。
比如，参见表9所示，优先级映射信息可以为mciop:ingress1.path1，即表示第一微服务的优先级所映射的参数为mciop:ingress1.path1。
在一个示例中，VNFD包括第一虚拟连接点的描述信息，第一虚拟连接点的描述信息包括第一微服务的描述信息，第一映射信息可以包含在第一微服务的描述信息中。
可选地，第一虚拟连接点的描述信息还包括容器对象类型信息，容器对象类型信息用于指示第一虚拟连接点对应的容器对象类型为ingress。
可选地，第一微服务的描述信息还包括以下至少一项：服务类型信息(包括第一微服务的名称)、域名类型信息(用于指示第一微服务支持配置的域名类型)、优先级信息(用于指示第一微服务支持配置优先级)。
可以理解的是，当域名类型信息用于指示第一微服务支持配置的域名类型包括内部访问域名和外部访问域名时，VNFM可以根据域名映射信息，将内部访问域名和外部访问域名映射到相应的参数中；当域名类型信息用于指示第一微服务支持配置的域名类型只包括内部访问域名(而第一微服务的配置信息包括内部访问域名和外部访问域名)时，VNFM可以根据域名类型信息，从第一微服务的配置信息选择内部访问域名，进而根据域名映射信息，将内部访问域名映射到相应的参数中。
举个例子，VNFD包括对MCIOP的引用，比如MCIOP中原始values.yaml文件如表13所示。
表13：原始values.yaml文件
VNFM根据第一虚拟连接点和第二虚拟连接点的配置信息以及VNFD中的映射信息，对原始values.yaml文件进行更新，更新后的values.yaml文件如表14所示，更新后的values.yaml文件包括第一入口容器对象的配置信息和第二入口容器对象的配置信息。
表14：更新后的values.yaml文件

需要说明的是，上述表13和表14为简化的values.yaml文件示例，用于说明原始values.yaml文件和更新后的values.yaml文件的差异之处，values.yaml文件的具体格式可以参照现有技术。
S705，VNFM向CISM发送第一入口容器对象的配置信息，第一入口容器对象的配置信息用于创建第一入口容器对象。
示例性地，VNFM可以向CISM发送更新后的MCIOP，以便CISM根据MCIOP创建容器对象，已完成VNF的实例化。其中，更新后的MCIOP包括至少一个容器对象的配置信息，此处是以第一入口容器对象为例。
S706，CISM根据第一入口容器对象的配置信息，创建第一入口容器对象。
此处，CISM还可以创建VNF对应的其它容器对象，已完成VNF的实例化。
示例性地，针对于第一入口容器对象，CISM(比如CISM中的ingress控制器)可以为第一入口容器对象分配访问地址(即IP地址)，并向VNFM发送第一入口容器对象的IP地址。
采用上述方法，VNFM可以根据NFVO发送的实例化请求中虚拟连接点的配置信息(一个虚拟连接点对应一个或多个微服务)，确定虚拟连接点对应的入口容器对象的配置信息，进而实现为微服务创建入口容器对象，由于通过入口容器对象定义的service的访问地址(比如fqdn)属于7层，从而便于满足微服务的访问需求。
此外，本申请实施例中通过在VNFD内对virtualCP进行扩展，实现了网元微服务与入口容器对象之间的映射，并通过在VNFD中引入容器对象类型信息、服务类型信息、域名类型信息，优先级信息等参数实现了对入口容器对象的管理，从而可以更好的利用云原生的技术实现网元微服务的改造，并通过MANO实现网元微服务化的创建以及生命周期管理。
可选地，在完成VNF的实例化后，上述方法还可以包括S707-S708和/或S709-S710。
S707，NFVO向VNFM发送第一请求信息，第一请求信息用于请求第一虚拟连接点的访问地址。
此处，触发NFVO向VNFM发送第一请求信息的情形可以有多种，比如NFVO需要查看部署成功的VNF的第一虚拟连接点的访问信息。
S708，VNFM根据第一请求信息，将第一入口容器对象的访问地址作为所述第一虚拟连接点的访问地址发送给NFVO。
进一步地，NFVO可以将第一虚拟连接点的访问地址发送给OSS/BSS，OSS/BSS根据反馈的第一虚拟连接点(即virtualCp1)的IP地址，将微服务的fqdn同IP地址的绑定关系设置到DNS服务器中，比如可以是
ip1:
myAMF_location.mynetwork.com
myAMF_location_external.mynetwork.com
myAMF_mt.mynetwork.com
如此，访问方在获取到微服务的访问地址(即fqdn)后，可以向DNS服务器查询访问地址对应的IP地址，DNS服务器将ingress分配的IP地址返回给访问方，进而访问方向该IP地址发送HTTP请求，并在host头中指定访问的微服务的访问地址，从而实现对微服务的访问。
S709，OSS/BSS可以向NFVO发送第二请求信息，第二请求信息用于请求K个微服务中第一微服务的资源利用信息。
S710，NFVO根据第二请求信息，获取第一微服务对应的至少一个VDU的资源利用信息，并根据第一微服务对应的VDU的资源利用信息，确定第一微服务的资源利用信息，进而向OSS/BSS发送第 一微服务的资源利用信息。
示例性地，NFVO可以根据第二请求信息后，可以获取VNF的VNFD，VNFD用于指示第一微服务对应的至少一个VDU，进而可以根据VNFD确定第一微服务对应至少一个VDU。比如，VNFD包括至少一个VDU中每个VDU的描述信息，VDU的描述信息包括服务类型信息，服务类型信息用于指示VDU对应的微服务，参见前文表10所示。
进一步地，NFVO可以向VNFM发送获取请求，获取请求用于请求第一微服务对应的至少一个VDU的资源利用信息；VNFM接收到获取请求后，可以从CISM获取至少一个VDU对应的pod的资源利用信息，并将pod的资源利用信息作为VDU的资源利用信息发送给NFVO。进而，NFVO可以根据至少一个VDU的资源利用信息，确定第一微服务的资源利用信息。
后续，OSS/BSS接收到第一微服务的资源利用信息后，可以根据第一微服务的资源利用信息判断是否需要对第一微服务执行扩容或者更新等操作。
可以理解的是：(1)上述实施例中，是以NFVO向VNFM发送的第一实例化请求中携带虚拟连接点的配置信息为例进行描述的，在其它可能的实施例中，NFVO也可以向VNFM发送多个微服务的配置信息。比如，可以在第一实例化请求中新增加一个信元，用于承载多个微服务的配置信息；相应地，VNFM接收到多个微服务的配置信息后，可以根据VNFD中的virtualCp，获得虚拟连接点与微服务之间的对应关系，进而也可以确定出虚拟连接点的配置信息。
(2)上述实施例所描述的各个流程图的步骤编号仅为执行流程的一种示例，并不构成对步骤执行的先后顺序的限制，本申请实施例中相互之间没有时序依赖关系的步骤之间没有严格的执行顺序。此外，各个流程图中所示意的步骤并非全部是必须执行的步骤，可以根据实际需要在各个流程图的基础上增添或者删除部分步骤。
上述主要从NFVO和VNFM交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，为了实现上述功能，NFVO和VNFM可以包括执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请的实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对NFVO和VNFM进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
图8示出了本申请实施例中所涉及的装置的可能的示例性框图。如图8所示，装置800可以包括：处理单元802和通信单元803。处理单元802用于对装置800的动作进行控制管理。通信单元803用于支持装置800与其他设备的通信。可选地，通信单元803也称为收发单元，可以包括接收单元和/或发送单元，分别用于执行接收和发送操作。装置800还可以包括存储单元801，用于存储装置800的程序代码和/或数据。
(1)情形1
该装置800可以为上述实施例中的VNFM、或者还可以为设置在VNFM中的部件(例如电路或者芯片)。处理单元802可以支持装置800执行上文中各方法示例中VNFM的动作。或者，处理单元802主要执行方法示例中的VNFM的内部动作，通信单元803可以支持装置800与其它设备之间的通信。
比如，在一个实施例中，通信单元803用于：接收来自NFVO的第一实例化请求，所述第一实例化请求用于请求实例化所述VNF，所述第一实例化请求包括所述VNF的第一虚拟连接点的配置信息，所述第一虚拟连接点的配置信息包括所述VNF对应的网络功能NF的K个微服务的配置信息，K为正整数；处理单元802用于：根据所述第一虚拟连接点的配置信息，确定所述第一虚拟连接点对应的第一入口容器对象的配置信息，所述第一入口容器对象用于提供所述K个微服务的访问入口；通信单元803还用于：向CISM发送所述第一入口容器对象的配置信息，所述第一入口容器对象的配置信息用于创建所述第一入口容器对象。
在一种可能的设计中，处理单元802具体用于：获取所述VNF的VNFD，所述VNFD包括映射信 息，所述映射信息用于指示所述第一虚拟连接点的配置信息与所述第一入口容器对象的配置信息之间的映射关系；根据所述第一虚拟连接点的配置信息和所述映射信息，确定所述第一入口容器对象的配置信息。
在一种可能的设计中，所述映射信息包括所述K个微服务中第一微服务对应的第一映射信息；所述第一映射信息包括以下至少一项：域名映射信息，所述域名映射信息用于指示所述第一微服务的配置信息中的所述第一微服务的域名所映射的参数；优先级映射信息，所述优先级映射信息用于指示所述第一微服务的配置信息中的所述第一微服务的优先级所映射的参数。
在一种可能的设计中，所述VNFD包括所述第一微服务的描述信息，所述第一映射信息包含在所述第一微服务的描述信息中。
在一种可能的设计中，所述第一微服务的描述信息还包括以下至少一项：服务类型信息，所述服务类型信息包括所述第一微服务的名称；域名类型信息，所述域名类型信息用于指示所述第一微服务支持配置的域名类型，所述域名类型包括内部访问域名和/或外部访问域名；优先级信息，所述优先级信息用于指示所述第一微服务支持配置优先级。
在一种可能的设计中，所述VNFD还包括所述第一虚拟连接点对应的容器对象类型信息，所述容器对象类型信息用于指示所述第一虚拟连接点对应的容器对象类型为入口容器对象。
在一种可能的设计中，所述VNFD还包括所述VNF的VDU的描述信息，所述VDU的描述信息包括服务类型信息，所述服务类型信息用于指示所述VDU对应的微服务。
在一种可能的设计中，通信单元803还用于：接收来自所述CISM的所述第一入口容器对象的访问地址。
在一种可能的设计中，通信单元803还用于：接收来自所述NFVO的第一请求信息，所述第一请求信息用于请求所述第一虚拟连接点的访问地址；根据所述第一请求信息，将所述第一入口容器对象的访问地址作为所述第一虚拟连接点的访问地址发送给所述NFVO。
(2)情形2
该装置800可以为上述实施例中的NFVO、或者还可以为设置在NFVO中的部件(例如电路或者芯片)。处理单元802可以支持装置800执行上文中各方法示例中NFVO的动作。或者，处理单元802主要执行方法示例中的NFVO的内部动作，通信单元803可以支持装置800与其它设备之间的通信。
比如，在一个实施例中，通信单元803用于：接收来自OSS/BSS的第二实例化请求，所述第二实例化请求用于请求实例化所述VNF，所述第二实例化请求包括所述VNF对应的NF的M个微服务的配置信息；处理单元802用于：根据所述VNF的第一虚拟连接点对应的K个微服务的配置信息，得到所述第一虚拟连接点的配置信息；其中，所述K个微服务属于所述M个微服务，M、K为正整数，K小于或等于M；通信单元803还用于：向VNFM发送第一实例化请求，所述第一实例化请求包括所述第一虚拟连接点的配置信息，所述第一虚拟连接点的配置信息用于确定所述第一虚拟连接点对应的第一入口容器对象的配置信息，所述第一入口容器对象用于提供所述K个微服务的访问入口。
在一种可能的设计中，处理单元802还用于：获取所述VNF的VNFD，所述VNFD包括所述第一虚拟连接点的描述信息，所述第一虚拟连接点的描述信息用于指示所述第一虚拟连接点对应所述K个微服务。
在一种可能的设计中，所述第一虚拟连接点的描述信息包括所述K个微服务的名称。
在一种可能的设计中，通信单元803还用于：接收来自所述OSS/BSS的第二请求信息，所述第二请求信息用于请求所述K个微服务中第一微服务的资源利用信息；处理单元802还用于：根据所述第二请求信息，获取所述第一微服务对应的至少一个VDU的资源利用信息；根据所述第一微服务对应的VDU的资源利用信息，确定所述第一微服务的资源利用信息；通信单元803还用于：向所述OSS/BSS发送所述第一微服务的资源利用信息。
应理解以上装置中单元的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且装置中的单元可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分单元以软件通过处理元件调用的形式实现，部分单元以硬件的形式实现。例如，各个单元可以为单独设立的处理元件，也可以集成在装置的某一个芯片中实现，此外，也可以以程序的形式存储于存储器中，由装置的某一个处理元件调用并执行该单元的功能。此外这些单元全部或部分可以集成在一起，也可以独立实现。这里所述的处理元件又可以成为处理器，可以是一种 具有信号的处理能力的集成电路。在实现过程中，上述方法的各操作或以上各个单元可以通过处理器元件中的硬件的集成逻辑电路实现或者以软件通过处理元件调用的形式实现。
在一个例子中，以上任一装置中的单元可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(application specific integrated circuit，ASIC)，或，一个或多个微处理器(digital singnal processor，DSP)，或，一个或者多个现场可编程门阵列(field programmable gate array，FPGA)，或这些集成电路形式中至少两种的组合。再如，当装置中的单元可以通过处理元件调度程序的形式实现时，该处理元件可以是处理器，比如通用中央处理器(central processing unit，CPU)，或其它可以调用程序的处理器。再如，这些单元可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现。
以上用于接收的单元是一种该装置的接口电路，用于从其它装置接收信号。例如，当该装置以芯片的方式实现时，该接收单元是该芯片用于从其它芯片或装置接收信号的接口电路。以上用于发送的单元是一种该装置的接口电路，用于向其它装置发送信号。例如，当该装置以芯片的方式实现时，该发送单元是该芯片用于向其它芯片或装置发送信号的接口电路。
参见图9，为本申请实施例提供的一种装置的结构示意图，用于实现以上实施例中VNFM或NFVO的操作。
如图9所示，装置900可包括处理器901、存储器902以及接口电路903。处理器901可用于对通信协议以及通信数据进行处理，以及对装置900进行控制。存储器902可用于存储程序和数据，处理器901可基于该程序执行本申请实施例中由AP执行的方法。接口电路903可用于装置900与其他设备进行通信，该通信可以为有线通信或无线通信，该接口电路也可以替换为收发器。
以上存储器902也可以是外接于装置900，此时装置900可包括接口电路903以及处理器901。以上接口电路903也可以是外接于装置900，此时装置900可包括存储器902以及处理器901。当接口电路903以及存储器902均外接于装置900时，装置900可包括处理器901。
图9所示的装置能够实现上述方法实施例中涉及VNFM或NFVO的各个过程。图9所示的装置中的各个模块的操作和/或功能，分别为了实现上述方法实施例中的相应流程。具体可参见上述方法实施例中的描述，为避免重复，此处适当省略详述描述。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (32)

  1. 一种虚拟化网络功能VNF的实例化方法，其特征在于，所述方法包括：
    接收来自网络功能虚拟化编排器NFVO的第一实例化请求，所述第一实例化请求用于请求实例化所述VNF，所述第一实例化请求包括所述VNF的第一虚拟连接点的配置信息，所述第一虚拟连接点的配置信息包括所述VNF对应的网络功能NF的K个微服务的配置信息，K为正整数；
    根据所述第一虚拟连接点的配置信息，确定所述第一虚拟连接点对应的第一入口容器对象的配置信息，所述第一入口容器对象用于提供所述K个微服务的访问入口；
    向容器基础设施管理器CISM发送所述第一入口容器对象的配置信息，所述第一入口容器对象的配置信息用于创建所述第一入口容器对象。
  2. 根据权利要求1所述的方法，其特征在于，根据所述第一虚拟连接点的配置信息，确定所述第一虚拟连接点对应的第一入口容器对象的配置信息，包括：
    获取所述VNF的虚拟化网络功能描述VNFD，所述VNFD包括映射信息，所述映射信息用于指示所述第一虚拟连接点的配置信息与所述第一入口容器对象的配置信息之间的映射关系；
    根据所述第一虚拟连接点的配置信息和所述映射信息，确定所述第一入口容器对象的配置信息。
  3. 根据权利要求2所述的方法，其特征在于，所述映射信息包括所述K个微服务中第一微服务对应的第一映射信息；
    所述第一映射信息包括以下至少一项：
    域名映射信息，所述域名映射信息用于指示所述第一微服务的配置信息中的所述第一微服务的域名所映射的参数；
    优先级映射信息，所述优先级映射信息用于指示所述第一微服务的配置信息中的所述第一微服务的优先级所映射的参数。
  4. 根据权利要求3所述的方法，其特征在于，所述VNFD包括所述第一微服务的描述信息，所述第一映射信息包含在所述第一微服务的描述信息中。
  5. 根据权利要求4所述的方法，其特征在于，所述第一微服务的描述信息还包括以下至少一项：
    服务类型信息，所述服务类型信息包括所述第一微服务的名称；
    域名类型信息，所述域名类型信息用于指示所述第一微服务支持配置的域名类型，所述域名类型包括内部访问域名和/或外部访问域名；
    优先级信息，所述优先级信息用于指示所述第一微服务支持配置优先级。
  6. 根据权利要求2至5中任一项所述的方法，其特征在于，所述VNFD还包括所述第一虚拟连接点对应的容器对象类型信息，所述容器对象类型信息用于指示所述第一虚拟连接点对应的容器对象类型为入口容器对象。
  7. 根据权利要求2至6中任一项所述的方法，其特征在于，所述VNFD还包括所述VNF的虚拟部署单元VDU的描述信息，所述VDU的描述信息包括服务类型信息，所述服务类型信息用于指示所述VDU对应的微服务。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述CISM的所述第一入口容器对象的访问地址。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    接收来自所述NFVO的第一请求信息，所述第一请求信息用于请求所述第一虚拟连接点的访问地址；
    根据所述第一请求信息，将所述第一入口容器对象的访问地址作为所述第一虚拟连接点的访问地址发送给所述NFVO。
  10. 一种VNF的实例化方法，其特征在于，所述方法包括：
    接收来自运营支撑系统/业务支撑系统OSS/BSS的第二实例化请求，所述第二实例化请求用于请求实例化所述VNF，所述第二实例化请求包括所述VNF对应的NF的M个微服务的配置信息；
    根据所述VNF的第一虚拟连接点对应的K个微服务的配置信息，得到所述第一虚拟连接点的配置信息；其中，所述K个微服务属于所述M个微服务，M、K为正整数，K小于或等于M；
    向VNFM发送第一实例化请求，所述第一实例化请求包括所述第一虚拟连接点的配置信息，所述第一虚拟连接点的配置信息用于确定所述第一虚拟连接点对应的第一入口容器对象的配置信息，所述第 一入口容器对象用于提供所述K个微服务的访问入口。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    获取所述VNF的VNFD，所述VNFD包括所述第一虚拟连接点的描述信息，所述第一虚拟连接点的描述信息用于指示所述第一虚拟连接点对应所述K个微服务。
  12. 根据权利要求11所述的方法，其特征在于，所述第一虚拟连接点的描述信息包括所述K个微服务的名称。
  13. 根据权利要求10至12中任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述OSS/BSS的第二请求信息，所述第二请求信息用于请求所述K个微服务中第一微服务的资源利用信息；
    根据所述第二请求信息，获取所述第一微服务对应的至少一个VDU的资源利用信息；
    根据所述第一微服务对应的VDU的资源利用信息，确定所述第一微服务的资源利用信息；
    向所述OSS/BSS发送所述第一微服务的资源利用信息。
  14. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    获取所述VNF的VNFD，所述VNFD包括所述至少一个VDU中每个VDU的描述信息，所述VDU的描述信息包括服务类型信息，所述服务类型信息用于指示所述VDU对应的微服务为所述第一微服务。
  15. 一种VNF的实例化装置，其特征在于，所述装置包括通信单元和处理单元；
    所述通信单元用于：接收来自NFVO的第一实例化请求，所述第一实例化请求用于请求实例化所述VNF，所述第一实例化请求包括所述VNF的第一虚拟连接点的配置信息，所述第一虚拟连接点的配置信息包括所述VNF对应的网络功能NF的K个微服务的配置信息，K为正整数；
    所述处理单元用于：根据所述第一虚拟连接点的配置信息，确定所述第一虚拟连接点对应的第一入口容器对象的配置信息，所述第一入口容器对象用于提供所述K个微服务的访问入口；
    所述通信单元还用于：向CISM发送所述第一入口容器对象的配置信息，所述第一入口容器对象的配置信息用于创建所述第一入口容器对象。
  16. 根据权利要求15所述的装置，其特征在于，所述处理单元具体用于：
    获取所述VNF的VNFD，所述VNFD包括映射信息，所述映射信息用于指示所述第一虚拟连接点的配置信息与所述第一入口容器对象的配置信息之间的映射关系；
    根据所述第一虚拟连接点的配置信息和所述映射信息，确定所述第一入口容器对象的配置信息。
  17. 根据权利要求16所述的装置，其特征在于，所述映射信息包括所述K个微服务中第一微服务对应的第一映射信息；
    所述第一映射信息包括以下至少一项：
    域名映射信息，所述域名映射信息用于指示所述第一微服务的配置信息中的所述第一微服务的域名所映射的参数；
    优先级映射信息，所述优先级映射信息用于指示所述第一微服务的配置信息中的所述第一微服务的优先级所映射的参数。
  18. 根据权利要求17所述的装置，其特征在于，所述VNFD包括所述第一微服务的描述信息，所述第一映射信息包含在所述第一微服务的描述信息中。
  19. 根据权利要求18所述的装置，其特征在于，所述第一微服务的描述信息还包括以下至少一项：
    服务类型信息，所述服务类型信息包括所述第一微服务的名称；
    域名类型信息，所述域名类型信息用于指示所述第一微服务支持配置的域名类型，所述域名类型包括内部访问域名和/或外部访问域名；
    优先级信息，所述优先级信息用于指示所述第一微服务支持配置优先级。
  20. 根据权利要求16至19中任一项所述的装置，其特征在于，所述VNFD还包括所述第一虚拟连接点对应的容器对象类型信息，所述容器对象类型信息用于指示所述第一虚拟连接点对应的容器对象类型为入口容器对象。
  21. 根据权利要求16至20中任一项所述的装置，其特征在于，所述VNFD还包括所述VNF的VDU的描述信息，所述VDU的描述信息包括服务类型信息，所述服务类型信息用于指示所述VDU对应的微服务。
  22. 根据权利要求15至21中任一项所述的装置，其特征在于，所述通信单元还用于：
    接收来自所述CISM的所述第一入口容器对象的访问地址。
  23. 根据权利要求22所述的装置，其特征在于，所述通信单元还用于：
    接收来自所述NFVO的第一请求信息，所述第一请求信息用于请求所述第一虚拟连接点的访问地址；
    根据所述第一请求信息，将所述第一入口容器对象的访问地址作为所述第一虚拟连接点的访问地址发送给所述NFVO。
  24. 一种VNF的实例化装置，其特征在于，所述装置包括通信单元和处理单元；
    所述通信单元用于：接收来自OSS/BSS的第二实例化请求，所述第二实例化请求用于请求实例化所述VNF，所述第二实例化请求包括所述VNF对应的NF的M个微服务的配置信息；
    所述处理单元用于：根据所述VNF的第一虚拟连接点对应的K个微服务的配置信息，得到所述第一虚拟连接点的配置信息；其中，所述K个微服务属于所述M个微服务，M、K为正整数，K小于或等于M；
    所述通信单元还用于：向VNFM发送第一实例化请求，所述第一实例化请求包括所述第一虚拟连接点的配置信息，所述第一虚拟连接点的配置信息用于确定所述第一虚拟连接点对应的第一入口容器对象的配置信息，所述第一入口容器对象用于提供所述K个微服务的访问入口。
  25. 根据权利要求24所述的装置，其特征在于，所述处理单元还用于：
    获取所述VNF的VNFD，所述VNFD包括所述第一虚拟连接点的描述信息，所述第一虚拟连接点的描述信息用于指示所述第一虚拟连接点对应所述K个微服务。
  26. 根据权利要求25所述的装置，其特征在于，所述第一虚拟连接点的描述信息包括所述K个微服务的名称。
  27. 根据权利要求24至26中任一项所述的装置，其特征在于，所述通信单元还用于：接收来自所述OSS/BSS的第二请求信息，所述第二请求信息用于请求所述K个微服务中第一微服务的资源利用信息；
    所述处理单元还用于：根据所述第二请求信息，获取所述第一微服务对应的至少一个VDU的资源利用信息；根据所述第一微服务对应的VDU的资源利用信息，确定所述第一微服务的资源利用信息；
    所述通信单元还用于：向所述OSS/BSS发送所述第一微服务的资源利用信息。
  28. 根据权利要求27所述的装置，其特征在于，所述处理单元还用于：
    获取所述VNF的VNFD，所述VNFD包括所述至少一个VDU中每个VDU的描述信息，所述VDU的描述信息包括服务类型信息，所述服务类型信息用于指示所述VDU对应的微服务为所述第一微服务。
  29. 一种VNF的实例化方法，其特征在于，所述方法包括：
    NFVO接收来自OSS/BSS的第二实例化请求，所述第二实例化请求用于请求实例化所述VNF，所述第二实例化请求包括所述VNF对应的NF的M个微服务的配置信息；NFVO根据所述VNF的第一虚拟连接点对应的K个微服务的配置信息，得到所述第一虚拟连接点的配置信息，并向VNFM发送第一实例化请求，所述第一实例化请求包括所述第一虚拟连接点的配置信息；其中，所述K个微服务属于所述M个微服务，M、K为正整数，K小于或等于M；
    VNFM接收来自所述NFVO的所述第一实例化请求，根据所述第一虚拟连接点的配置信息，确定所述第一虚拟连接点对应的第一入口容器对象的配置信息，所述第一入口容器对象用于提供所述K个微服务的访问入口，并向容器基础设施管理器CISM发送所述第一入口容器对象的配置信息，所述第一入口容器对象的配置信息用于创建所述第一入口容器对象。
  30. 一种VNF的实例化系统，其特征在于，包括：
    VNFM，用于实现如权利要求1-9任一项所述的方法；
    NFVO，用于实现如权利要求10-14任一项所述的方法。
  31. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行权利要求1-14任一项所述的方法。
  32. 一种芯片，其特征在于，所述芯片与存储器耦合，所述芯片读取所述存储器中存储的计算机程序，执行权利要求1-14任一项所述的方法。
PCT/CN2023/134807 2022-11-30 2023-11-28 一种虚拟化网络功能vnf的实例化方法及装置 WO2024114645A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211524508.2A CN118118348A (zh) 2022-11-30 2022-11-30 一种虚拟化网络功能vnf的实例化方法及装置
CN202211524508.2 2022-11-30

Publications (1)

Publication Number Publication Date
WO2024114645A1 true WO2024114645A1 (zh) 2024-06-06

Family

ID=91216779

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/134807 WO2024114645A1 (zh) 2022-11-30 2023-11-28 一种虚拟化网络功能vnf的实例化方法及装置

Country Status (2)

Country Link
CN (1) CN118118348A (zh)
WO (1) WO2024114645A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016121834A1 (ja) * 2015-01-29 2016-08-04 日本電気株式会社 ネットワーク機能仮想化管理方法とシステムと装置とプログラム
CN109347716A (zh) * 2018-09-25 2019-02-15 中国联合网络通信集团有限公司 消费者vnf的实例化方法及装置
CN109788040A (zh) * 2018-12-27 2019-05-21 北京航天智造科技发展有限公司 微服务授权与调度方法和系统
CN111698112A (zh) * 2019-03-15 2020-09-22 华为技术有限公司 一种容器化虚拟网络功能vnf的资源管理方法及装置
US11074091B1 (en) * 2018-09-27 2021-07-27 Juniper Networks, Inc. Deployment of microservices-based network controller
CN114124740A (zh) * 2020-08-03 2022-03-01 华为技术有限公司 一种vnf实例化的方法和装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016121834A1 (ja) * 2015-01-29 2016-08-04 日本電気株式会社 ネットワーク機能仮想化管理方法とシステムと装置とプログラム
CN109347716A (zh) * 2018-09-25 2019-02-15 中国联合网络通信集团有限公司 消费者vnf的实例化方法及装置
US11074091B1 (en) * 2018-09-27 2021-07-27 Juniper Networks, Inc. Deployment of microservices-based network controller
CN109788040A (zh) * 2018-12-27 2019-05-21 北京航天智造科技发展有限公司 微服务授权与调度方法和系统
CN111698112A (zh) * 2019-03-15 2020-09-22 华为技术有限公司 一种容器化虚拟网络功能vnf的资源管理方法及装置
CN114124740A (zh) * 2020-08-03 2022-03-01 华为技术有限公司 一种vnf实例化的方法和装置

Also Published As

Publication number Publication date
CN118118348A (zh) 2024-05-31

Similar Documents

Publication Publication Date Title
WO2018024059A1 (zh) 一种虚拟化网络中业务部署的方法和装置
CN111542064B (zh) 一种用于无线接入网的容器编排管理系统及编排方法
US7257817B2 (en) Virtual network with adaptive dispatcher
US7899047B2 (en) Virtual network with adaptive dispatcher
US10397132B2 (en) System and method for granting virtualized network function life cycle management
WO2017080391A1 (zh) 一种网络服务部署方法和装置
EP4109251A1 (en) Vnf instantiation method and device
CN113301116A (zh) 微服务应用跨网络通信方法、装置、系统及设备
WO2022148363A1 (zh) 数据传输方法及数据传输服务器
WO2020108443A1 (zh) 一种虚拟化管理方法及装置
EP4191907A1 (en) Vnf instantiation method and apparatus
WO2019153880A1 (zh) 集群中镜像文件下载的方法、节点、查询服务器
WO2021088444A1 (zh) 实例化ns的方法及nfvo
US20240179092A1 (en) Traffic service threads for large pools of network addresses
WO2021175105A1 (zh) 连接方法、装置、设备和存储介质
CN116800616B (zh) 虚拟化网络设备的管理方法及相关装置
WO2020249080A1 (zh) 一种虚拟网络功能vnf部署方法及装置
WO2024114645A1 (zh) 一种虚拟化网络功能vnf的实例化方法及装置
WO2021143183A1 (zh) 一种部署虚拟机的方法及相关装置
WO2021022947A1 (zh) 一种部署虚拟机的方法及相关装置
JP2017184195A (ja) 通信管理装置、通信管理方法及びプログラム
CN114816651A (zh) 一种通信方法、装置以及系统
WO2022183796A1 (zh) 一种创建网络服务ns的方法及相关装置
JP7450072B2 (ja) 仮想化ネットワーク・サービス配備方法及び装置
WO2023179580A1 (zh) 一种部署vnf的方法、装置及设备