Method and apparatus for deploying virtualized network functions

Abstract

The present application provides a method and apparatus for deploying a virtualized network function to support the deployment of a load balancer and / or an external connection point of an external name in a VNF. The VNFM determines first resource information of resources pre-allocated to the load balancer and / or the external connection point of the external name and sends the first resource information to a container infrastructure service management CISM. The CISM may create the load balancer and / or the external connection point of the external name based in part or in whole on the resources indicated by the first resource information. A mechanism is provided for deploying multiple types of services within a VNF to serve as an external connection point.

Description

Technical Field

[0001] Cross-reference to Related Applications This application claims priority to Chinese Patent Application No. 202111221826.7, entitled "METHOD FOR DEPLOYING VIRTUALIZED NETWORK FUNCTION AND APPARATUS", filed with the China National Intellectual Property Administration on October 20, 2021, which is incorporated herein by reference in its entirety.

[0002] This application relates to the field of communication technologies, and in particular, to a method and an apparatus for deploying virtualized network functions.

Background Art

[0003] Network function virtualization (NFV) technology uses general-purpose hardware devices and virtualization technology to construct virtualized network functions (VNFs), and uses VNFs to carry the functions of dedicated devices on a conventional network, thereby reducing the costs incurred by deploying dedicated devices.

[0004] The container management platform is implemented based on containerization technology, such as the K8S (Kubernetes) platform. One container management platform manages one cluster, and the cluster includes several physical machines or virtual machines. The physical machine or virtual machine may be regarded as a node. Correspondingly, the container is deployed on the physical machine or virtual machine. The container management platform creates containers in the managed cluster by using a pod as the smallest unit. One pod may include one or more containers. The cluster further includes a service, and one service may access one or more pods in the cluster. An external node may access one or more pods through the service.

[0005] The continuous development of containerization technology has led to the introduction of container management platforms into NFV architectures. In this way, one or more pods can be deployed within a VNF. In NFV architectures where container management platforms are introduced, external connection points (ExtCp) are defined, and services can be used as entry points for external nodes to access pods in the NFV. External nodes can be understood as nodes other than VNFs. However, there is still no solution for deploying services within the NFV architecture as external connection points. [Overview of the project]

[0006] Embodiments of this application provide a method and apparatus for deploying virtualized network functions to provide a mechanism for deploying services within a VNF to function as an external connection point. [Means for solving the problem]

[0007] According to a first aspect, one embodiment of the present application provides a method for deploying virtualized network functionality. The method may be performed by container infrastructure service management (CISM) or by a chip system or communication system having CISM functionality. For ease of explanation, the following example uses CISM performing the method. The method includes the steps of: receiving first resource information, wherein the first resource information indicates resources pre-allocated to a first type of external connection point, where the external connection point is an entry point for external nodes to access virtualized network functionality (VNF), and the first type includes load balancers and / or external names; and creating a first type of external connection point and allocating some or all of the resources indicated by the first resource information to the first type of external connection point.

[0008] In this embodiment of the present application, CISM receives first resource information of resources pre-assigned to a first type of external connection point, creates a first type of external connection point, and assigns some or all of the resources indicated by the first resource information to the first type of external connection point. A mechanism is provided for deploying load balancer and / or external name services within the VNF to function as external connection points. Load balancer and / or external name services to function as external connection points can be deployed within the VNF so that the VNF can support more types of external connection points. In addition, the range of services that can be supported by different types of external connection points may differ, and the VNF can support multiple types of external connection points. Thus, the range of services supported by the VNF can be expanded. In addition, the resources that can be used to deploy external connection points can be enhanced, as the resources required to deploy different types of external connection points may differ.

[0009] In a possible implementation, the step of creating a first type of external connection point and allocating some or all of the resources indicated by the first resource information to the first type of external connection point includes the step of receiving a resource creation request from a virtualization network function manager VNFM, wherein the resource creation request is used to request the creation of a first type of external connection point and the resource creation request includes second resource information, and if the resources indicated by the second resource information are a subset of the resources indicated by the first resource information, the step of creating a first type of external connection point and allocating the resources indicated by the second resource information to the first type of external connection point.

[0010] In this implementation, CISM receives second resource information from VNFM, and based on this information, CISM determines the resources to be used to create a first type of external connection point. CISM does not need to determine which resources are specifically allocated to the first type of external connection point from the resources indicated by the first resource information. Therefore, the process by which CISM creates the first type of external connection point is simplified. In addition, to ensure the accuracy of the resources indicated by the second resource information, CISM may verify whether the resources indicated by the second resource information belong to a subset of the resources indicated by the first resource information. Furthermore, VNFM may further carry the second resource information in a resource creation request and send the resource creation request to CISM. CISM does not need to receive the second resource information from VNFM via a dedicated message, thereby reducing the amount of interaction between CISM and VNFM.

[0011] In possible implementations, the CISM sends the Container Infrastructure Services Management CISM address information to the Network Functions Virtualization Orchestrator NFVO, and the CISM address information identifies the CISM that creates a first type of external connectivity point.

[0012] In this implementation, the CISM can send its address information to the NFVO, which can then send the CISM's address information to the VNFM. In this way, the VNFM communicates with the CISM based on its address information. The VNFM does not need to perform the process of discovering the CISM, thereby reducing the number of communication steps between the VNFM and the CISM.

[0013] According to a second aspect, one embodiment of the present application provides a method for deploying virtualized network functionality. The method may be performed by an NFVO, or by a chip system or communication system having NFVO functionality. For ease of explanation, the following example uses an NFVO performing the method. The method includes the steps of: determining first resource information, wherein the first resource information indicates a resource pre-allocated to a first type of external connection point, where the external connection point is an entry point for external nodes to access virtualized network functionality (VNF), and the first type is a load balancer and / or external name; and transmitting the first resource information to a container infrastructure service management (CISM), wherein the resource indicated by the first resource information is used to create a first type of external connection point.

[0014] In this embodiment of the present application, the NFVO determines first resource information and transmits the first resource information to the CISM. A method is provided for indicating the resources required by a first type of external connection point. In addition, the CISM may then allocate some or all of the resources indicated by the first resource information to the first type of external connection point so that the CISM deploys load balancer and / or externally named services to function as an external connection point. The CISM does not need to determine the first resource information itself, thereby reducing the workload on the CISM.

[0015] In possible implementations, the first resource information includes information about the address assigned by the first type of external connection point. Alternatively, the first resource information may further include information about the functionality supported by the first type of external connection point.

[0016] In this implementation, the first resource information includes address information. Subsequently, CISM may assign the address indicated by the address information to a first type of external connection point so that an external node can access the external connection point based on the address. A method is provided for an external node to discover the first type of external connection point. In addition, the first resource information may further include information about the functionality supported by the first type of external connection point. In this way, CISM may continue to create a first type of external connection point that better satisfies the functional requirements based on the functionality information.

[0017] In possible implementations, an instantiation request is sent to the VNFM, which is used to request that the VNF be instantiated. A resource permission request is received from the VNFM, which includes a first resource parameter, which is used to determine the first resource information. The first resource information is determined based on the first resource parameter.

[0018] In this implementation, the VNFM determines the first resource parameter and sends it to the NFVO. The NFVO does not need to determine the first resource parameter itself, thereby reducing the processing load on the NFVO.

[0019] In possible implementations, the first resource parameter is determined from the virtualized network function descriptor (VNFD) corresponding to the VNF, and the first resource parameter is used to determine the first resource information, where the VNFD includes type information of the VNF's external connection points and resource parameters corresponding to each type of external connection point. The first resource information is determined based on the first resource parameter.

[0020] In this implementation, the NFVO determines the first resource parameter from the VNFD itself and determines the first resource information based on that first resource parameter. The VNFM does not need to determine the first resource parameter, thereby reducing the processing load on the VNFM. In addition, the VNFD is generally configured within the NFVO, and the NFVO analyzes the VNFD itself. In this case, the NFVO does not need to send the VNFD to the VNFM, thereby reducing the amount of interaction between the VNFM and the NFVO.

[0021] In possible implementations, the second resource information is sent to the VNFM, the resources indicated by the second resource information are a subset of the resources indicated by the first resource information, and the resources indicated by the second resource information are used to create an external connection point of the first type.

[0022] In this implementation, the NFVO determines the second resource information and sends it to the VNFM. The VNFM may then send the second resource information to the CISM. This is equivalent to the NFVO explicitly indicating to the CISM the resources allocated to the first type of external connection point. The CISM does not need to determine the specific resource to be used from the resources indicated by the first resource information, thereby reducing the processing load on the CISM.

[0023] In possible implementations, CISM address information is received from the CISM, sent to the VNFM, and the CISM address information indicates the CISM that creates a first type of external connection point.

[0024] In this implementation, the CISM may send its address information to the NFVO, which may then send the CISM's address information to the VNFM. In this way, the VNFM may communicate directly with the CISM based on its address information, thereby simplifying the communication process between the VNFM and the CISM.

[0025] According to a third aspect, one embodiment of the present application provides a method for deploying virtualized network functions. The method may be performed by a VNFM or by a chip system or communication system having VNFM functionality. For ease of explanation, the following example uses a VNFM performing the method. The method includes: receiving an instantiation request from a network function virtualization orchestrator NFVO, the instantiation request being used to request the instantiation of a virtualized network function VNF; and sending a resource authorization request to the NFVO, the resource authorization request including a first resource parameter, the first resource parameter being used to determine first resource information, the first resource information indicating a resource pre-allocated to a first type of external connection point, the external connection point being an entry point for external nodes to access the virtualized network function VNF.

[0026] In this embodiment of the present application, the VNFM may determine a first resource parameter and transmit the first resource parameter to the NFVO, so as to provide a method for determining the first resource parameter. The NFVO does not need to determine the first resource parameter itself, thereby reducing the processing load on the NFVO.

[0027] In a possible implementation form, the first resource parameter is determined from a VNFD corresponding to a VNF, the first resource parameter is used to determine the first resource information, and the VNFD includes type information of external connection points of the VNF and resource parameters corresponding to each type of external connection point.

[0028] In this implementation form, the VNFM can analyze the VNFD to determine the first resource parameter. A method for determining the first resource parameter by the VNFM is provided.

[0029] In a possible implementation form, the second resource information is received from a network function virtualization orchestrator NFVO, the second resource information indicates resources pre-assigned to external connection points of the first type, the external connection point is an entry for an external node to access a virtual network function VNF, the first type is a load balancer and / or an external name, the second resource information is sent to a container infrastructure service management CISM, and the second resource information is used to create an external connection point of the first type.

[0030] In this implementation form, the VNFM can receive the second resource information from the NFVO and send the second resource information to the CISM. In this way, the CISM can determine which resources should be assigned to the external connection points of the first type based on the second resource information. The CISM does not need to determine the specific resources used from the resources indicated by the first resource information, thereby reducing the processing volume of the CISM.

[0031] According to a fourth aspect, one embodiment of the present application provides a method for deploying virtualized network functions. The method may be performed by a VNFM or by a chip system or communication system having VNFM functionality. For ease of explanation, the following example uses a VNFM performing the method. The method includes: receiving second resource information from a network function virtualization orchestrator NFVO, wherein the second resource information indicates resources pre-allocated to a first type of external connection point, where the external connection point is an entry point for external nodes to access a virtualized network function VNF, and the first type is a load balancer and / or external name; and transmitting the second resource information to a container infrastructure service management CISM, wherein the resources indicated by the second resource information are used to create a first type of external connection point.

[0032] In a possible implementation, an instantiation request is received from the Network Functions Virtualization Orchestrator (NFVO), which is used to request the instantiation of a virtualized network function (VNF). A resource authorization request is sent to the NFVO, which includes a first resource parameter, which is used to determine first resource information, which indicates a resource pre-allocated to a first type of external connection point, where the external connection point is the entry point for external nodes to access the virtualized network function (VNF).

[0033] In possible implementations, the first resource parameter is determined from the VNFD corresponding to the VNF, and the first resource parameter is used to determine the first resource information, where the VNFD includes type information of the VNF's external connection points and resource parameters corresponding to each type of external connection point.

[0034] In addition, for other technical effects brought about by the fourth aspect or some implementations of the fourth aspect, please refer to the description of the technical effects of the third aspect or the corresponding embodiment.

[0035] According to a fifth aspect, one embodiment of the present application provides a method for deploying virtualized network functions. The method may be performed by a communication system including a VNFM, CISM, and NFVO, or by a communication system having the functions of a VNFM, CISM, and NFVO. For ease of explanation, the following example uses a communication system including a VNFM, CISM, and NFVO. The method includes the step of a virtualized network function manager VNFM receiving an instantiation request from a network function virtualization orchestrator NFVO, the instantiation request being used to request the instantiation of a VNF. The VNFM sends a resource authorization request to the NFVO, the resource authorization request including a first resource parameter, the first resource parameter being used to determine first resource information, the first resource information indicating a resource pre-allocated to a first type of external connection point, the external connection point being an entry point for external nodes to access the virtualized network function VNF. The NFVO determines first resource information, which indicates resources pre-allocated to a first type of external connection point, where the external connection point is the entry point for external nodes to access the virtualized network function (VNF), and the first type is a load balancer and / or external name. The NFVO sends the first resource information to the Container Infrastructure Services Management (CISM), which uses the resources indicated by the first resource information to create a first type of external connection point. The CISM creates the first type of external connection point and allocates some or all of the resources indicated by the first resource information to the first type of external connection point.

[0036] In this embodiment of the present application, after receiving an instantiation request, the VNFM may determine first resource parameters required to deploy a first type of external connection point within the VNF and transmit the first resource parameters to the NFVO. The NFVO determines first resource information based on the first resource parameters in order to transmit the first resource information to the CISM. The CISM receives and creates the first type of external connection point. A mechanism is provided for deploying load balancer and / or externally named services within the VNF to function as an external connection point. In addition, the VNFM determines the first resource parameters. The NFVO does not need to determine the first resource parameters, thereby reducing the workload on the NFVO.

[0037] In addition, for other technical effects brought about by the fifth embodiment, please refer to the description of the technical effects of the first embodiment, the second embodiment, the third embodiment, or the corresponding embodiment.

[0038] According to a sixth aspect, one embodiment of the present application provides a method for deploying virtualized network functionality. The method may be performed by a communication system including a VNFM, CISM, and NFVO, or by a communication system having the functionality of a VNFM, CISM, and NFVO. The method includes the step of an NFVO determining first resource information, wherein the first resource information indicates a resource pre-allocated to a first type of external connection point, the external connection point being an entry point for external nodes to access the virtualized network functionality VNF, and the first type being a load balancer and / or external name. The network functionality virtualization orchestrator NFVO transmits the first resource information to the container infrastructure service management CISM, and the resource indicated by the first resource information is used to create a first type of external connection point. The Virtualization Network Function Manager (VNFM) determines second resource information from the NFVO, where the second resource information indicates resources pre-allocated to a first type of external connection point, where the external connection point is the entry point for external nodes to access the Virtualization Network Function VNF, and the first type is a load balancer and / or external name. The second resource information is sent to the Container Infrastructure Services Management (CISM), where the resources indicated by the second resource information are used to create a first type of external connection point. The CISM receives a resource creation request from the VNFM, which is used to request the creation of a first type of external connection point, and the resource creation request includes the second resource information. If the resources indicated by the second resource information are a subset of the resources indicated by the first resource information, the CISM creates the first type of external connection point and assigns the resources indicated by the second resource information to the first type of external connection point.

[0039] In this embodiment of the present application, the NFVO may determine first resource information and transmit the first resource information to the CISM. In addition, the NFVO may further determine second resource information and transmit the second resource information to the VNFM to the CISM. When deploying a first type of external connection point, the CISM may deploy the first type of external connection point based on the resources indicated by the second resource information. A mechanism is provided for deploying load balancers and / or externally named services within the VNF to function as external connection points. Since the NFVO may directly specify that a first type of external connection point is to be created, the CISM does not need to determine the specific resources used to create the first type of external connection point from the resources indicated by the first resource information. Thus, the process by which the CISM deploys a first type of external connection point is relatively simplified.

[0040] In addition, for other technical effects brought about by the sixth embodiment, please refer to the description of the technical effects of the first embodiment, the second embodiment, the third embodiment, or the corresponding embodiment.

[0041] According to a seventh aspect, one embodiment of the present application provides a communication device. The communication device may be a CISM in the first aspect, or an electronic device configured within the CISM (e.g., a chip system), or a relatively large device including a CISM. The CISM includes corresponding means or modules configured to implement the first aspect or any optional implementation. For example, the communication device includes a processing module (which may also be called a processing unit) and a transceiver module (which may also be called a transceiver unit).

[0042] For example, a transceiver module is configured to receive first resource information, which indicates resources pre-allocated to a first type of external connection point, where the external connection point is an entry point for external nodes to access a virtualized network function (VNF), and the first type includes a load balancer and / or external name. A processing module is configured to create a first type of external connection point and to allocate some or all of the resources indicated by the first resource information to the first type of external connection point.

[0043] In an optional implementation, the communication device includes a processor coupled to memory and configured to execute instructions in memory in order to implement the method performed by the fifth network element in the first embodiment or implementation. Optionally, the communication device further includes other components, such as antennas, input / output modules, and interfaces. These components may be hardware, software, or a combination of software and hardware.

[0044] In addition, for other technical effects brought about by the seventh aspect or some implementations of the seventh aspect, please refer to the description of the technical effects of the first aspect or the corresponding embodiment.

[0045] According to the eighth aspect, one embodiment of the present application provides a communication device. The communication device may be an NFVO in the second aspect, or an electronic device configured within the NFVO (e.g., a chip system), or a relatively large device including an NFVO. The NFVO includes corresponding means or modules configured to implement the second aspect or any optional implementation. For example, the communication device includes a processing module (which may also be called a processing unit) and a transceiver module (which may also be called a transceiver unit).

[0046] For example, a processing module is configured to determine a first resource information, which indicates a resource pre-allocated to a first type of external connection point, where the external connection point is an entry point for external nodes to access a virtualized network function (VNF), and the first type is a load balancer and / or external name. A transceiver module is configured to send the first resource information to the CISM, where the resource indicated by the first resource information is used to create a first type of external connection point.

[0047] In an optional implementation, the communication device includes a processor coupled to memory and configured to execute instructions in memory in order to implement the method performed by the fifth network element in the first embodiment or implementation. Optionally, the communication device further includes other components, such as antennas, input / output modules, and interfaces. These components may be hardware, software, or a combination of software and hardware.

[0048] In addition, for other technical effects brought about by the eighth aspect or some implementations of the eighth aspect, please refer to the description of the technical effects of the second aspect or the corresponding embodiment.

[0049] According to the ninth aspect, one embodiment of the present application provides a communication device. The communication device may be a VNFM in the third aspect, or an electronic device configured within the VNFM (e.g., a chip system), or a relatively large device including a VNFM. The VNFM includes corresponding means or modules configured to implement the first aspect or any optional implementation. For example, the communication device includes a transceiver module (which may also be called a transceiver unit). Optionally, the communication device further includes a processing module (which may also be called a processing unit).

[0050] For example, a transceiver module is configured to receive an instantiation request from a network function virtualization orchestrator (NFVO), which is used to request the instantiation of a virtualized network function (VNF), send a resource authorization request to the NFVO, which includes a first resource parameter, which is used to determine first resource information, which indicates a resource pre-allocated to a first type of external connection point, and the external connection point is an entry point for external nodes to access the virtualized network function (VNF).

[0051] Optionally, the processing module is configured to determine a first resource parameter from the VNFD corresponding to the VNF, and the first resource parameter is used to determine the first resource information, such that the VNFD includes type information of the VNF's external connection points and resource parameters corresponding to each type of external connection point.

[0052] In an optional implementation, the communication device includes a processor coupled to memory and configured to execute instructions in memory in order to implement the method performed by the fifth network element in the first embodiment or implementation. Optionally, the communication device further includes other components, such as antennas, input / output modules, and interfaces. These components may be hardware, software, or a combination of software and hardware.

[0053] In addition, for other technical effects brought about by the ninth aspect or some implementations thereof, please refer to the description of the technical effects of the third aspect or the corresponding embodiment.

[0054] According to the tenth aspect, one embodiment of the present application provides a communication device. The communication device may be a VNFM in the fourth aspect, or an electronic device configured within the VNFM (e.g., a chip system), or a relatively large device including a VNFM. The VNFM includes corresponding means or modules configured to implement the first aspect or any optional implementation. For example, the communication device includes a transceiver module (which may also be called a transceiver unit). Optionally, the communication device further includes a processing module (which may also be called a processing unit).

[0055] For example, a transceiver module is configured to receive second resource information from a network function virtualization orchestrator NFVO, where the second resource information indicates a resource pre-allocated to a first type external connection point, where the external connection point is an entry point for external nodes to access a virtualized network function VNF, where the first type is a load balancer and / or external name, and to send the second resource information to the container infrastructure service management CISM, where the second resource information is used to create the first type external connection point.

[0056] Optionally, the processing module is configured to determine a first resource parameter from the VNFD corresponding to the VNF, and the first resource parameter is used to determine the first resource information, such that the VNFD includes type information of the VNF's external connection points and resource parameters corresponding to each type of external connection point.

[0057] In an optional implementation, the communication device includes a processor coupled to memory and configured to execute instructions in memory in order to implement the method performed by the fifth network element in the first embodiment or implementation. Optionally, the communication device further includes other components, such as antennas, input / output modules, and interfaces. These components may be hardware, software, or a combination of software and hardware.

[0058] In addition, for other technical effects brought about by the tenth aspect or some implementations of the tenth aspect, please refer to the description of the technical effects of the fourth aspect or the corresponding embodiment.

[0059] According to the eleventh aspect, one embodiment of the present application provides a communication system. The communication system includes communication devices according to the seventh, eighth, and ninth aspects. Alternatively, the communication system includes communication devices according to the seventh, eighth, and tenth aspects.

[0060] According to the twelfth aspect, one embodiment of the present application provides a chip system. The chip system includes a processor and an interface. The processor is configured to call instructions from the interface and execute the instructions. When the processor executes an instruction, a method according to the first, second, third, fourth, fifth, or sixth aspect is performed.

[0061] According to the thirteenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium is configured to store a computer program or instruction. When the computer program or instruction is executed, the method according to the first, second, third, fourth, fifth, or sixth aspect is performed.

[0062] According to the 14th aspect, a computer program product including instructions is provided. When the computer program product is executed on a computer, the method according to the first, second, third, fourth, fifth, or sixth aspect is performed. [Brief explanation of the drawing]

[0063] [Figure 1A] This is a schematic diagram of an NFV architecture to which one embodiment of this application can be applied. [Figure 1B] This is a schematic diagram of the VNF structure. [Figure 1C] This is a schematic diagram of another NFV architecture to which one embodiment of this application may be applied. [Figure 1D] This is a schematic diagram of the structure of a communication system according to one embodiment of this application. [Figure 2] This is a schematic flowchart of a method for deploying virtualized network functionality according to one embodiment of this application. [Figure 3] This is a schematic diagram illustrating an external connection point deployed within a VNF according to one embodiment of this application. [Figure 4] This is another schematic flowchart of a method for deploying virtualized network functionality according to one embodiment of this application. [Figure 5] Figure 1 is a schematic diagram of the structure of a communication device according to one embodiment of this application. [Figure 6] Figure 2 shows a schematic diagram of the structure of a communication device according to one embodiment of this application. [Figure 7] Figure 3 is a schematic diagram of the structure of a communication device according to one embodiment of this application. [Figure 8] Figure 4 shows a schematic diagram of the structure of a communication device according to one embodiment of this application. [Figure 9] Figure 5 shows a schematic diagram of the structure of a communication device according to one embodiment of this application. [Modes for carrying out the invention]

[0064] To further clarify the purpose, technical solutions, and advantages of the embodiments of this application, the technical solutions of the embodiments of this application will be described in detail below with reference to the accompanying drawings and specific implementations.

[0065] The following will explain the terms used in the embodiments of this application.

[0066] 1. In embodiments of this application, the network element may be a physical device within a network, or a device that integrates multiple physical devices. Alternatively, the network element in embodiments of this application may be a logical concept, such as a software module within a physical device, or a network function corresponding to a service provided by each network device. The network function may be understood as a virtualized function implemented using virtualization technology.

[0067] 2. In embodiments of this application, a connection point may be understood as an interface of a VNF. A connection point includes internal connection points and external connection points. An internal connection point is, for example, a virtualization deployment unit connection point (VDU Cp) and may be used for internal communication of a VNF. For example, a VNF includes at least one VNF component (VNFC). Each VNFC may include one or more internal connection points, and VNFCs may communicate with each other through the internal connection points. External connection nodes are used for communication between the VNF and external nodes. An external connection point may be of the virtual connection point (virtual Cp) type. A virtual connection point may be implemented using a service. A service includes node ports, load balancers, external names, and other types. Node ports, load balancers, and external names may be further understood as three techniques for implementing a service. Accordingly, the external connection points of a node port in the embodiments of this application may also be called the virtual connection points of the node port, the node port service, or the external connection points implemented using node port technology. The external connection points of a load balancer in the embodiments of this application may also be called the virtual connection points of the load balancer, the load balancer service, or the external connection points implemented using load balancer technology. The external connection points of an external name in the embodiments of this application may also be called the virtual connection points of an external name, the external name service, or the external connection points implemented using external name technology.

[0068] In embodiments of this application, the CISM within the NFV architecture may pre-configure different information for different types of services to implement the functionality of an external connection point. For example, for a node port service, the CISM may configure a port on a cluster node managed by the CISM for the service. An external node can access the service by accessing the port. For a load balancer service, information about the load balancer provided by the network service vendor (e.g., the load balancer's Internet Protocol (IP) address) may be configured for the service. An external node can access the service through the information about the load balancer. For an external name service, the service may be associated with an external name (e.g., foo.bar.example.com). An external node can access the service by accessing the external name.

[0069] In the embodiments of this application, three types of external connection points are represented by node ports, load balancers, and external names, and it should be understood that these are merely examples and not limitations. In a standard evolutionary process, the names of node ports, load balancers, or external names may be changed. This is not limited to the embodiments of this application.

[0070] 3. In embodiments of this application, a virtualization deployment unit (VDU) is used to describe a unit for deploying a VNF. When a VNF is deployed using virtual machine technology, one VDU represents one virtual machine. Alternatively, when a VNF is deployed using containerization technology, one VDU represents one group of containers.

[0071] 4. The virtualized network function descriptor (VNFD) in the embodiments of this application may also be called the VNF deployment identifier. The VNFD is generally located within an NFV orchestrator (NFVO). The VNFD is used to describe a VNF. The VNFD includes information about virtualization deployment units (VDUs), connection point descriptors (CPDs), and virtual link descriptors (VLDs). For example, if one VDU represents one virtual machine, the information about the VDU includes descriptive information about the virtual machine's resource requirements, such as the type of resources required to create the virtual machine and the amount of resources for each type of resource. Alternatively, if one VDU represents a group of containers, the information about the VDU includes descriptive information about the group of containers' resource requirements. The information about the CPD includes type information and resource parameters for each type of external connection point in the VNF. The external connection point type information indicates the type of external connection point. The resource parameters of an external connection point indicate the resources required to create this type of external connection point. These parameters include, for example, the address representation format of the external connection point. The address representation format, for example, represents the address using the Internet Protocol. Optionally, the resource parameters of an external connection point further include the type of functionality supported by the external connection point. Information regarding the VLD describes the virtual network connectivity requirements between VDUs, such as connection type and / or bandwidth. For example, if a VNF includes a first type of external connection point, but a prior art VNFD does not actually include a relevant definition of a first type of external connection point, the type information of the first type of external connection point in embodiments of this application may be reconstructed in the VNFD corresponding to the VNF.For example, type information for a first type of external connection point may be added to the type information for a virtual connection point in the VNFD.

[0072] 5. The container in the embodiments of this application may be understood as a software unit. The container includes necessary elements, such as system tools, that enable the smooth execution of an application in different environments. The container simplifies the development and deployment of applications.

[0073] 6. In embodiments of this application, a namespace is an organization mechanism for classifying, filtering, and managing objects within a cluster managed by a container management platform, such as services. Objects added to a cluster may belong to a single namespace. Within the same namespace, object names are unique, but different objects within different namespaces may have the same name.

[0074] In embodiments of this application, “multiple” means two or more. With this in mind, “multiple” may also be understood as “at least two” in embodiments of this application. “At least one” may be understood as one or more, e.g., one, two, or more. For example, including at least one means one, two, or more, and is not limited to which is included. For example, including at least one of A, B, and C could include A, B, C, A and B, A and C, B and C, or A, B, and C. The term “and / or” describes a relational relationship for describing related subjects and indicates that three relationships may exist. For example, A and / or B could represent the following three cases: namely, only A exists, both A and B exist, and only B exists. In addition, the letter “ / ” generally indicates an “or” relationship between related subjects. The terms “system” and “network” in embodiments of this application may be used interchangeably.

[0075] Unless otherwise specified, ordinal numbers such as “first” and “second” as used in the embodiments of this application are used to distinguish between multiple symmetries and are not used to limit the order, chronological order, priority, or importance of multiple symmetries. For example, “first resource information” and “second resource information” in the embodiments of this application are used to represent two resource information and are not used to limit the priority of the two resource information.

[0076] To facilitate understanding, the concepts and architecture of NFV are briefly explained below.

[0077] 1. NFV NFV decouples software from hardware, meaning that the functionality of network devices no longer depends on dedicated hardware. In addition, cloud computing capabilities enable flexible resource sharing, thereby facilitating the rapid development and deployment of new services. Network services implemented using NFV are called network services (NS). For example, an NS might include Internet Protocol Multimedia Subsystem (IMS) network services, or the core network services of the 5th generation system (5GS). Each NS contains several virtualized network functions (VNFs); in other words, several VNFs implement one NS.

[0078] 2. NFV Architecture Please refer to Figure 1A. Figure 1A is a schematic diagram of an NFV architecture to which embodiments of this application are applicable, or may be understood as a schematic diagram of an NFV architecture with a container management platform implemented. The NFV architecture includes an NFV management and orchestration system (NFV MANO) 110, one or more operation support systems / business support systems (OSS / BSS) 120, one or more element manager systems (EMS) 130, multiple VNFs 140, and an NFV infrastructure (NFVI) 150.

[0079] The NFV MANO 110 is responsible for the management and orchestration of all NFVI resources. The NFV MANO 110 includes the NFVO 111, one or more virtualized network function managers (VNFMs) 112, virtualized infrastructure managers (VIMs) 113, and the CISM 114.

[0080] NFVO 111 is primarily responsible for managing the NS lifecycle, allocating hardware resources (e.g., computing hardware, storage hardware, and network hardware in Figure 1A) and virtual resources (e.g., virtual computing, virtual storage, and virtual network in Figure 1A) in NFVI 150, and scheduling hardware and virtual resources in NFVI. NFVO 111 may further communicate with one or more VNFM 112 to execute corresponding resource requests, etc. In addition, NFVO 111 may also communicate with a virtualized infrastructure manager (VIM) 113 for resource allocation, reservations, etc.

[0081] VNFM 112 is primarily responsible for the lifecycle management of one or more VNF 140s. Lifecycle management includes instantiating, updating, querying, auto-scaling, and terminating VNF 140s. VNFM 112 can communicate with VNF 140s to terminate their lifecycle management and to exchange information about their configuration and status. There may be multiple VNFM 112s, each responsible for the lifecycle management of different types of VNF 140s.

[0082] VIM 113 controls and manages the interaction between VNF 140 and hardware or virtual resources within NFVI 150. For example, VIM 113 performs resource management functions, including managing infrastructure resources, allocating them (e.g., adding resources to containers), and performing functions (e.g., collecting failure information for NFVI 150). VNFM 112 and VIM 113 can communicate with each other to request resource allocation, exchange virtual resources, and exchange status information.

[0083] CISM 114 is the container management platform in the NFV architecture and is responsible for managing container resources, including creating, updating, querying, auto-scaling, and terminating containers. When a VNF is deployed in the form of a container, VNFM 112 can communicate with CISM 114 to request the creation of container resources.

[0084] OSS / BSS 120 is primarily aimed at telecommunications service providers and provides integrated network management functions such as fault monitoring and network information collection, as well as service operation management functions such as billing management and customer service management.

[0085] EMS 130 is configured to perform the traditional functions of VNF 140, including fault management, configuration management, account management, performance management, security management (FCAPS). EMS includes one or more EMs (e.g., EM1 and EM2 in Figure 1A).

[0086] VNF 140 contains one or more VNFCs. VNF 140 may be implemented using virtual machine technology or containerization technology. If VNF 140 is implemented using virtual machine technology, the VNFCs contained in the VNF may be deployed on one or more virtual machines. If VNF 140 is implemented using containerization technology, the VNFCs contained in the VNF may be deployed on one or more containers. Instantiating a VNF can be understood as allocating or creating the resources required by the VNF to implement the corresponding functionality. Instantiating a VNF includes creating a virtual machine or container and deploying the VNFCs contained in the VNF on the created virtual machine or container. In addition, instantiating a VNF further includes creating connection points for the VNF, for example, creating an external connection point within the VNF. To clearly illustrate the structure of a VNF, an example is given below with reference to the schematic diagram of the VNF structure shown in Figure 1B. Referring to Figure 1B, the VNF includes two VNFCs (VNFC1 and VNFC2 shown in Figure 1B), internal connection points (CP1 and CP2 shown in Figure 1B), and an external connection point (CP3 shown in Figure 1B). CP1 and CP2 are configured to facilitate communication between VNFC1 and VNFC2. CP3 is configured to facilitate communication between the VNF and external nodes, etc. The two VNFCs in Figure 1B may be deployed on a virtual machine (not shown in Figure 1B) or a container (not shown in Figure 1B).

[0087] NFVI 150 includes a virtual resource layer 151, a virtualization layer 152, and a hardware resource layer 153. The virtual resource layer 151 is configured to provide virtual resources, which include virtual computing, virtual storage, and virtual networks, as shown in Figure 1A. The virtualization layer 152 can form virtual networks through hardware resources within the virtualized hardware resource layer. Virtual networks include, for example, virtual local area networks (VLANs) and virtual extensible local area networks (VXLANs). The hardware resource layer 153 is configured to provide hardware resources. For example, the hardware resource layer 153 can provide hardware resources in the form of physical machines. The hardware resource layer includes computing hardware, storage hardware, and network hardware, as shown in Figure 1A.

[0088] It should be understood that the network elements shown in Figure 1A (NFVO, VNFM, CISM, etc.) are merely examples and not limiting. In a standard evolutionary process, the names of network elements may be changed, and the functions performed by the network elements may be further divided or combined. This is not limited to the embodiments of this application.

[0089] Please refer to Figure 1C. Figure 1C is a schematic diagram of another NFV architecture to which embodiments of this application are applicable, or may be understood as a schematic diagram of an NFV architecture with a container management platform implemented. Unlike Figure 1A, the NFV architecture shown in Figure 1C further includes a container cluster manager (CCM) 115. The CCM 115 can communicate with both NFVO 111 and CISM 114. The CCM 115 can work with NFVO 111 to manage CISM 114. For the functionality of network elements other than the CCM in Figure 1C, please refer to the description in Figure 1A. Details are not listed again here.

[0090] It should be understood that the network elements shown in Figure 1C (NFVO, VNFM, CISM, CCM, etc.) are merely examples and not limiting. In a standard evolutionary process, the names of network elements may be changed, and the functions performed by the network elements may be further divided or combined. This is not limited to the embodiments of this application.

[0091] To support the deployment of services in a VNF to function as an external connection point, one embodiment of the present application provides a technical solution. In this technical solution, when a first type of external connection point (e.g., a load balancer and / or external name) is to be deployed in a VNF to be instantiated, first resource information for the first type of external connection point may be determined. The first resource information indicates the resources pre-allocated to create the first type of external connection point. Subsequently, some or all of the resources indicated by the first resource information may be allocated to the first type of external connection point. A mechanism is provided for deploying load balancer and / or external name services within the VNF to function as an external connection point. In addition, the VNF may support more types of services to function as external connection points, and the resources required to create different types of services may differ. In this way, the number of deployed external connection points is not limited by the number of resources so that more external connection points can be created within the VNF. Thus, the VNF can meet the requirements for more services. In addition, since the resources required to create different types of external connection points may differ, the resources for creating external connection points are enhanced.

[0092] The technical solutions provided in embodiments of this application will be described below with reference to the attached drawings.

[0093] One embodiment of this application provides a method for deploying virtualized network functionality. This method may be implemented through a communication system.

[0094] The communication system may include NFVO and CISM, or NFVO, VNFM, and CISM, or a device or chip system having the functions of NFVO and CISM, or a communication device or chip system having the functions of NFVO, VNFM, and CISM. In the embodiments of this application, the implementation form of the communication system is not limited. The structure of the communication system will be described below using an example.

[0095] Please refer to Figure 1D. Figure 1D is a schematic diagram of the structure of a communication system according to one embodiment of the present application. The communication system includes an NFVO, a VNFM, and a CISM. The communication system may be deployed within the NFV architecture shown in Figure 1A or Figure 1C. The NFVO in the communication system is, for example, the NFVO shown in Figure 1A or Figure 1C. The VNFM in the communication system is, for example, the VNFM shown in Figure 1A or Figure 1C. The CISM in the communication system is, for example, the CISM shown in Figure 1A or Figure 1C. For the functions of the NFVO and CISM in the communication system, please refer to the contents described in Figure 1A.

[0096] Note that while one NFVO, one CISM, and one VNFM are used as examples in Figure 1D, the actual number of NFVOs, CISMs, and VNFMs is not limited.

[0097] Please refer to Figure 2. Figure 2 is a flowchart of this method. In the process description in Figure 2, the communication system shown in Figure 1D is used as an example of a communication system, and the communication system is deployed in the NFV architecture shown in Figure 1A.

[0098] Step 201: The NFVO sends a first creation request to the VNFM. In response, the VNFM receives the first creation request from the NFVO. The first creation request is used to request the creation of an identifier for a VNF instance.

[0099] If a VNF is configured without resources, it may be called a VNF. If a VNF is configured with resources, it may be called an instantiated VNF, or a VNF instance. Naturally, if resources are configured for a VNF in the form of a container, the VNF configured with resources may also be called a containerized VNF. To facilitate subsequent identification of the VNF, an identifier for the VNF instance may be created during instantiation. For example, an NFVO may send a first create request to the VNFM to request the VNFM to create an identifier for the VNF instance.

[0100] For example, when a service requester needs to instantiate a VNF, the service requester may send a VNFD to the NFVO or pre-configure the VNFD within the NFVO. The service requester is, for example, a user or an EM. The VNFD includes a VNFD identifier. The VNFD identifier indicates the VNFD corresponding to the VNF. See the previous description for a description of VNFDs. Optionally, to facilitate the VNFM subsequently obtaining the VNFD corresponding to the VNF, the first creation request includes a VNFD identifier. Note that in this embodiment of the application, it is used as an example that the NFVO sends the VNFD identifier to the VNFM via the first creation request. In addition, the NFVO may further send the VNFD identifier to the VNFM via another message.

[0101] In this embodiment of the present application, the VNF may include only the first type of external connection points. Alternatively, the VNF may further include other types of external connection points in addition to the first type of external connection points. For example, the VNF may further include node port external connection points.

[0102] Step 202: The VNFM sends the VNF instance identifier to the NFVO. In response, the NFVO receives the VNF instance identifier from the VNFM, and the VNF instance identifier identifies the VNF instance.

[0103] After receiving the first creation request, the VNFM may create an identifier for the VNF instance for the VNF. The VNFM then sends the VNF instance identifier to the NFVO.

[0104] It should be noted that steps 201 to 202 describe one example of how an NFVO determines the identifier of a VNF instance. In addition, an NFVO may determine the identifier of a VNF instance in multiple ways, and this is not limited to this embodiment of the present application.

[0105] Step 203: The NFVO sends an instantiation request to the VNFM. In response, the VNFM receives an instantiation request from the NFVO. The instantiation request is used to request an instance of the VNF, and may include an identifier for the VNF instance.

[0106] Optionally, the instantiation request may further include information about the VLD and / or VDU. The VLD and VDU information may be determined by an NFVO, for example, by an NFVO based on the VNFD. See the above explanation for the meaning of the VLD and VDU information.

[0107] Step 204: VNFM obtains VNFD.

[0108] For example, as described above, an NFVO may be pre-configured using a VNFD corresponding to a VNF. A VNFM may request a VNFD from an NFVO based on the VNFD identifier.

[0109] For example, a VNFM may send a VNFD request to another VNFM. A VNFD request is used to request the acquisition of a VNFD. For example, a VNFD request includes a VNFD identifier. In response, an NFVO receives a VNFD request from a VNFM. The NFVO determines the VNFD corresponding to the VNFD identifier and sends the VNFD to the VNFM. In response, the VNFM receives the VNFD from the NFVO and acquires the VNFD. For the meaning of VNFD, please refer to the explanation above.

[0110] Step 205: VNFM determines the first resource parameter based on VNFD.

[0111] The VNFM analyzes the VNFD to determine the type information of the external connection points included in the VNF and the resource parameters of each type of external connection point. In this embodiment of the present application, it is used as an example that the VNF includes a first type of external connection point. Therefore, after analyzing the VNFD, the VNFM accordingly determines the type information of the first type of external connection point and the first resource parameters of the first type of external connection point. The type information of the external connection point may indicate the type of the external connection point. For example, the type indicated by the type information of the first type of external connection point is a first type. The first type is, for example, a load balancer and / or external name. The first resource parameters indicate the resources required to create the first type of external connection point. For example, the first resource parameters indicate the type of resources allocated to create the external connection point.

[0112] If the first type is different, the type information and / or specific details of the resource parameters of the first type external connection point, as determined by VNFM, may differ accordingly. An example is provided below for illustrative purposes.

[0113] 1. If the first type includes a load balancer, the VNFD includes type information for the load balancer's external connection point and resource parameters for the load balancer's external connection point.

[0114] The type information for the load balancer's external connection point indicates that the type of the external connection point is a load balancer. The resource parameters for the load balancer's external connection point include, for example, information about the address representation format of the load balancer's external connection point. Regarding the address representation format information for the load balancer's external connection point, the address representation format information indicates that the address of the load balancer's external connection point is represented by either a public network IP address or a private network IP address.

[0115] Optionally, the resource parameters for the load balancer's external connection point in the VNFD may include further information about the functional type of the load balancer's external connection point. This functional type information indicates the type of functionality supported by the load balancer's external connection point. Functionality supported by the load balancer's external connection point may include, for example, health check functionality and / or auto scaling functionality. Health check functionality allows the load balancer's external connection point to report exceptions to CISM for pods associated with the external connection point. Auto scaling functionality allows the load balancer's external connection point to scale pods associated with the external connection point. For example, the load balancer's external connection point may add and manage pods, and / or remove pods.

[0116] Table 1 shows an example of resource parameters for an external connection point of a load balancer included in a VNFD according to one embodiment of this application.

[0117] [Table 1]

[0118] For example, it is used as an example that the VNFD includes the resource parameters shown in Table 1. The VNFM determines from the VNFD the type information of the load balancer's external connection point in the VNF, where the type is service and the subtype is load balancer. In this case, the first type includes the subtype. Optionally, the first type may further include types. The first resource parameter includes that the load balancer's external connection point is represented by a public network address, and that the load balancer's external connection point supports health check and auto-scaling functions.

[0119] 2. If the first type includes an external name, the VNFD includes type information for the external connection point of the external name and resource parameters for the external connection point of the external name.

[0120] The type information for an external connection point of an external name indicates that the type of the external connection point is an external name. The resource parameters for an external connection point of an external name include information about its address representation format. This information indicates that the address of the external connection point of an external name is represented by a name and the namespace applicable to that name. The name is unique within the same namespace. Therefore, the name and namespace can be used to uniquely identify the external connection point of an external connection point. Optionally, the resource parameters for an external connection point of an external name may further include information about the functional type of the external connection point of an external name. This information about the functional type of the external connection point of an external name indicates the type of functionality supported by the external connection point of an external name.

[0121] Table 2 shows an example of resource parameters for an external connection point with an external name included in a VNFD according to one embodiment of this application.

[0122] [Table 2]

[0123] For example, a VNFD containing the resource parameters shown in Table 2 is used as an example. The VNFM determines from the VNFD the type information of the external connection point of the external name in the VNF, where the type is service and the subtype is the external name. In this case, the first type here includes the subtype. Optionally, the first type here may further include types. The first resource parameter includes that the address of the external name is represented by a name and namespace.

[0124] 3. If the first type includes load balancers and external names, the VNFD includes type information for the load balancer's external connection points, resource parameters for the load balancer's external connection points, type information for the external name's external connection points, and resource parameters for the external name's external connection points.

[0125] For information on the type of external connection point of the load balancer, the resource parameters of the external connection point of the load balancer, the type of external connection point of an external name, and the resource parameters of an external connection point of an external name, please refer to the explanation above.

[0126] If the first type includes a load balancer and an external name, the type information of the first type's external connection point, as determined by VNFM based on the VNFD, includes the type information of the load balancer's external connection point and the type information of the external name's external connection point, and the first resource parameters, as determined by VNFM based on the VNFD, include the resource parameters of the load balancer's external connection point and the resource parameters of the external name's external connection point.

[0127] For example, the VNFM may determine from the VNFD other resource information required to instantiate the VNF, where other resource information indicates other resources. These other resources are resources other than those indicated by the first resource parameter within the resources required to instantiate the VNF. For information on other resource information, such as information about the VDU and / or information about the VLD corresponding to the VNF, see the preceding explanation of the meaning of the information about the VDU and VLD.

[0128] It should be noted that step 204 uses an example in which the VNFM determines the first resource parameters based on the VNFD. In addition, the VNFM may determine the first resource parameters in multiple ways, and this is not limited to this embodiment of the present application. For example, the VNFM may be pre-configured with first resource parameters corresponding to the VNF, and it is not necessary to determine the first resource parameters based on the VNFD.

[0129] Step 206: The VNFM sends a resource authorization request to the NFVO. In response, the NFVO receives a resource authorization request from the VNFM. The resource authorization request may include the first resource parameter.

[0130] Instantiating a VNF may require a large number of resources (e.g., resources indicated by a first resource parameter). Some of these resources may need to be authorized by the NFVO. For example, the resources indicated by a first resource parameter need to be authorized by the NFVO. In this embodiment of the application, the resource indicated by a first resource parameter needs to be authorized by the NFVO, and this is used as an example. The resources indicated by a first resource parameter need to be authorized by the NFVO. As a result, the VNFM may request the NFVO to authorize the resources indicated by the first resource parameter. For example, a resource authorization request may request the NFVO to authorize the resources indicated by the first resource parameter. Based on the first resource parameter included in the resource authorization request, the NFVO may determine the resources indicated by the first resource parameter that the VNFM requests to authorize, for example, referred to as the first resource.

[0131] For example, an NFVO determines a first resource to be pre-allocated to a first type of external connection point based on a first resource parameter.

[0132] Optionally, the resource permission request may further include type information for a first type of external connection point. Based on the type information for the first type of external connection point, the NFVO may determine that the first type of external connection point needs to be deployed for the instantiation of the VNF. In this case, the NFVO directly determines from the VNFM that the VNF contains a first type of external connection point, thereby reducing the processing load on the NFVO.

[0133] Alternatively, since the resource parameters corresponding to different types of external connection points are different, the NFVO may determine, based on the first resource parameters and pre-stored resource parameters corresponding to different types of external connection points, that a first type of external connection point needs to be deployed for VNF instantiation. In this case, the NFVO may not need to receive type information for the first type of external connection point from the VNFM. Therefore, the amount of data transmitted between the VNFM and the NFVO can be relatively reduced.

[0134] In this embodiment of the present application, it is used as an example that the first resource parameter is carried in a resource permission request. In addition, the VNFM may send the first resource parameter to the NFVO via another message. This is not limited to this embodiment of the present application.

[0135] Steps 204 through 206 use the example that the NFVO receives the first resource parameter from the VNFM. In another example, the NFVO may determine the first resource parameter itself, and the VNFM does not need to send the first resource parameter. In this case, steps 204 through 206 do not need to be performed. For example, the NFVO may determine the first resource parameter from the VNFD. For how the NFVO determines the first resource parameter, see the process by which the VNFM determines the first resource parameter. Details are not listed again here. In addition, other resource information may also be determined by the NFVO. For the meaning of other resource information, see the explanation above.

[0136] Step 207: The NFVO determines first resource information based on the first resource parameters. The resources indicated by the first resource information are used to create a first type of external connection point.

[0137] For example, an NFVO manages resource pool information. Resource pool information includes resource information required to create each type of external connection point within one or more types of external connection points. For example, resource pool information may include resource information required to create a load balancer external connection point, resource information required to create an external name external connection point, etc. An NFVO may determine from the resource pool information one or more resource pieces that satisfy a first resource parameter, where each resource piece within the one or more resource pieces indicates the resource required to create one external connection point of the first type. In this case, the first resource piece may include one or more resource pieces. Alternatively, an NFVO may select from one or more resource pieces that satisfy usage conditions as the first resource piece. Usage conditions are, for example, resource information that has not yet been used.

[0138] Alternatively, the NFVO does not need to determine the first resource information itself, but may receive the first resource information from another network element. In this case, step 207 may be replaced by the other network element sending the first resource information to the NFVO, and the NFVO receiving the first resource information from the other network element accordingly. The other network element is, for example, a network element other than the NFVO in Figure 1A or Figure 1B, specifically, for example, the VIM. For a method of determining the first resource information by another network element, see the method of determining the first resource information by the NFVO.

[0139] Naturally, steps 204 to 207 use as an example that the NFVO determines first resource information based on first resource parameters. In addition to the methods described above, the NFVO may further determine the first resource information in other ways, and this is not limited to this embodiment of the present application. For example, after the VNF has determined that it includes a first type of external connection point, the NFVO may determine from managed resource pool information the first resource information required to create the first type of external connection point.

[0140] In one example, the VNF may include a plurality of external connection points of the first type. In this embodiment of the present application, the first resource information determined by the NFVO may, for example, indicate resources pre-allocated to a plurality of external connection points of the first type.

[0141] If the first type is different, the first resource information may also be different. Examples are used below for illustrative purposes.

[0142] (1) If the first type includes a load balancer, the first resource information includes address information of the load balancer's external connection point.

[0143] Information regarding the load balancer's external connection point addresses indicates the address and address type of the load balancer's external connection point, such as an IP address and IP address type. The IP address type may indicate whether the IP address is a public network or private network address.

[0144] Optionally, the first resource information may further include information about the features supported by the load balancer's external connection point. The information about the features supported by the load balancer's external connection point indicates the features supported by the load balancer's external connection point.

[0145] Table 3 shows an example of the first resource information provided by this embodiment of the present application when the first type includes a load balancer.

[0146] [Table 3]

[0147] For example, Figure 3 is a schematic diagram of a VNF according to an embodiment of the present application. The VNF includes four VNFCs (e.g., VNFC1, VNFC2, VNFC3, and VNFC4 shown in Figure 3). The VNF further includes two external connection points (e.g., Serv1 and Serv2 shown in Figure 3). Both Serv1 and Serv2 are of the type load balancer. Thus, the NFVO may decide to pre-allocate the first resource information shown in Table 1 to both Serv1 and Serv2.

[0148] (2) If the first type includes an external name, the first resource information includes address information for the external connection point of the external name. The information regarding the address of the external connection point of the external name indicates the address of the external connection point of the external name. For example, the address of the external connection point of the external name includes the name of the external connection point and the namespace applicable to the name.

[0149] Table 4 shows an example of the first resource information provided by this embodiment of the present application when the first type includes an external name.

[0150] [Table 4]

[0151] In Table 4, myExample and myCompany are two different namespaces.

[0152] (3) If the first type includes a load balancer and an external name, the first resource information includes the first resource information for the load balancer's external connection point and the first resource information for the external name's external connection point. See the above description for the two types of first resource information.

[0153] Step 208: The NFVO sends the first resource information to the first CISM. In response, the first CISM receives the first resource information from the NFVO.

[0154] An NFV architecture may include one or more CISMs. If there are multiple CISMs, the NFVO may determine a first CISM from among them and send first resource information to the first CISM. For example, the NFVO may randomly select a CISM as the first CISM from among multiple CISMs, or select the CISM with the lightest load as the first CISM. If the NFV architecture includes only one CISM, the NFVO will use that CISM directly as the first CISM.

[0155] In this case, the first CISM does not need to temporarily create a first type of external connection point. Therefore, after receiving the first resource information, the first CISM may optionally store the first resource information for later use.

[0156] Step 209: The first CISM sends a successful reception response to the NFVO. In response, the NFVO receives a successful reception response from the first CISM.

[0157] A successful reception response indicates that the first CISM has successfully received the first resource information.

[0158] Optionally, the successful reception response may further include connection information for the first CISM. This connection information may include, for example, the address information for the first CISM. The address information for the first CISM may indicate the address of the first CISM, for example, the IP address of the first CISM. Optionally, the connection information for the first CISM may further include the uniform resource identifier (URL) of the first CISM.

[0159] If the NFV architecture includes only one CISM, the VNFM does not need to later create a first type of external connection point from a specific CISM among multiple CISMs. Therefore, the receive success response does not need to carry the connection information of the first CISM. In this embodiment of the present application, an example is used in which the receive success response includes the connection information of the first CISM.

[0160] It should be noted that in this embodiment of the present application, it is used by example that the reception success response carries the connection information of the first CISM. In addition, the first CISM may further transmit the connection information of the first CISM to the NFVO via another message. This is not limited to this embodiment of the present application.

[0161] In this embodiment of the present application, it is used as an example that the reception success response carries the CISM connection information. In addition, the first CISM may further transmit the CISM connection information to the NFVO via another message. This is not limited to this embodiment of the present application.

[0162] Step 210: The NFVO sends a resource authorization response to the VNFM. In response, the VNFM receives a success response from the NFVO. The resource authorization response includes connection information for the first CISM.

[0163] If the successful reception response in step 209 includes connection information for the first CISM, the resource grant response in step 210 also includes connection information for the first CISM. If the successful reception response in step 209 does not include connection information for the first CISM, the resource grant response in step 210 also does not include connection information for the CISM.

[0164] In this embodiment of the present application, it is used as an example that the resource permission response carries the CISM connectivity information. In addition, the NFVO may further transmit the first CISM connectivity information to the VNFM via another message. This is not limited to this embodiment of the present application.

[0165] The first resource information may indicate one or more resources. However, it may be uncertain which of these resources will be specifically used by the first type of external connection point to create the VNF. Therefore, optionally, the NFVO may further determine second resource information. The second resource information may indicate the resources used by the VNFM to create the first type of external connection point for the VNF. The resources indicated by the second resource information are a subset of the resources indicated by the first resource information. The NFVO may carry the second resource information in a resource authorization response.

[0166] In addition, this embodiment of the application uses an example in which the second resource information is transmitted through a resource permission response. In practice, the NFVO transmits the second resource information to the VNFM in several ways, which are not limited to this application.

[0167] Optionally, the NFVO may further mark the status of the resources indicated by the second resource information. For example, the NFVO may mark the status of the resources indicated by the second resource information as used, so that the NFVO can later determine, based on the status, which resources indicated by the first resource information will be used.

[0168] Step 211: The VNFM sends a resource creation request to the first CISM. In response, the first CISM receives the resource creation request from the VNFM. The resource creation request is used to request the creation of an external connection point of type 1.

[0169] If the NFV architecture includes one CISM, the VNFM directly uses this CISM as the first CISM and sends resource creation requests to the first CISM. Alternatively, if the NFV architecture includes multiple CISMs, the VNFM may determine which of the multiple CISMs is the first to be used to create the first type of external connection point, based on the address information of the first CISM.

[0170] If the VNFM receives second resource information from the NFVO, it may optionally carry the second resource information in a resource creation request to indicate the resources required to create a first type of external connection point through the second resource information.

[0171] Optionally, a resource creation request may further indicate the creation of a container required to instantiate a VNF. In one implementation, the VNFM may determine the resource information required by the created container based on other resource information, and the resource creation request may carry the resource information required by the created container. See the above explanation for the meaning of other resource information.

[0172] Alternatively, a resource creation request may not need to indicate the creation of a container required to instantiate the VNF. The VNFM may send a container creation request to the first CISM. In response, the first CISM receives a container creation request from the VNFM. The container creation request may indicate the first CISM to create the container required to instantiate the VNF. Optionally, the container creation request includes resource information required by the created container. If the VNFM further sends a container creation request to the first CISM, the VNFM may send a resource creation request first, followed by a container creation request. Alternatively, the VNFM may send a container creation request first, followed by a resource creation request. Alternatively, the VNFM may send both messages simultaneously.

[0173] Step 212: The first CISM creates a container.

[0174] The first CISM determines the container to be created based on a request from the VNFM, and the first CISM may create the container. For example, the first CISM deploys the container onto a physical or virtual machine in the NFVI. Optionally, the first CISM may further deploy a VNFC within the container to instantiate the VNF. For example, the first CISM includes a first application programming interface configured to create the container. The CISM may call the first application programming interface (API) to create the container based on resources indicated by other resource information. For example, the CISM may call the first application programming interface to access a physical or virtual machine in the NFVI based on other resource information to deploy the container onto a physical or virtual machine in the NFVI.

[0175] Optionally, after creating the container, the first CISM may feed back a container creation success response to the VNFM. The container creation success response indicates that the first CISM has successfully created the container.

[0176] Step 213: The first CISM creates a first type of external connection point and assigns some or all of the resources indicated by the first resource information to the first type of external connection point.

[0177] If the first CISM deploys a container on a physical machine, the first CISM may also deploy a first type of external connection point on the physical machine and allocate some or all of the resources indicated by the first resource information to the first type of external connection point. If the CISM deploys a container on a virtual machine, the first CISM may, alternatively, deploy a first type of external connection point on the virtual machine and allocate some or all of the resources indicated by the first resource information to the first type of external connection point.

[0178] For example, the first CISM includes a second application programming interface configured to create an external connection point. The first CISM may call the second application programming interface to create a first type of external connection point. For example, the first CISM may call a second application programming interface for accessing a physical or virtual machine in an NFVI to deploy a first type of external connection point on a physical or virtual machine in the NFVI. The second application programming interface may be the same application programming interface as the first application programming interface described above, or it may be a different application programming interface.

[0179] We will continue to use Figure 3 as an example. After receiving the resource creation request, the first CISM determines that the resource creation request does not include the second resource information. Therefore, the first CISM may randomly determine two IP addresses (e.g., 10.70.36.36 and 10.70.36.37) from the first resource information shown in Table 3 and assign the two IP addresses to Serv1 and Serv2. For example, the first CISM assigns the IP address (10.70.36.36) to Serv1 and the IP address 10.70.36.37 to Serv2.

[0180] If a resource creation request does not include second resource information, the first CISM may assign some or all of the resources indicated by the first resource information to a first type of external connection point. For example, the first CISM may randomly select some of the resources from the entirety of the resources indicated by the first resource information and assign the resources to a first type of external connection point.

[0181] Alternatively, if the resource creation request includes second resource information, the first CISM may allocate the entire resource indicated by the second resource information to the first type of external connection point.

[0182] On the other hand, theoretically, the NFVO determines second resource information for a VNF that indicates a subset of the resources indicated by the first resource information. However, it is difficult to guarantee that no errors occur in the process by which the VNFM transfers the second resource information. For example, the VNFM may confuse the second resource information of one VNF with the second resource information of another VNF. On the other hand, the VNFM cannot obtain the first resource information from the NFVO or another network element. As a result, the VNFM cannot verify the resources indicated by the second resource information. Therefore, in this embodiment of the present application, the first CISM may optionally verify the resources indicated by the second resource information in order to improve the accuracy of the resources indicated by the second resource information. For example, the first CISM may determine whether the resources indicated by the second resource information are a subset of the resources indicated by the first resource information in order to determine whether the resources indicated by the second resource information are correct. The first CISM determines whether the resources indicated by the second resource information are a subset of the resources indicated by the first resource information. The result of this determination may include several types:

[0183] The first type of result of the decision is that the entirety of the resources indicated by the second resource information is a subset of the resources indicated by the first resource information.

[0184] The result of this type of decision indicates that the entire set of resources indicated by the second resource information is correct, and the first CISM can assign the resources indicated by the second resource information to the first type of external connection point.

[0185] For example, suppose the first resource information is shown in Table 4, and the second resource information includes that the identifier of the external connection point is name-3, the address information of the external connection point includes the name www.example3.com, and the namespace is myCompany. If the first CISM determines that the resource indicated by the second resource information belongs to the resource indicated by the first resource information, then the first CISM determines that the resource indicated by the second resource information is correct.

[0186] A second type of result in the decision is that a portion of the resources indicated by the second resource information is a subset of the resources indicated by the first resource information, while another portion of the resources indicated by the second resource information does not belong to the resources indicated by the first resource information.

[0187] The result of this type of decision indicates that some of the resources indicated by the second resource information are correct, and the first CISM can assign the correct resources indicated by the second resource information to the first type of external connection point. Alternatively, the first CISM may directly assign some of the resources indicated by the first resource information to the first type of external connection point without considering the second resource information.

[0188] A third type of result in the decision is that none of the resources indicated by the second resource information are included in the resources indicated by the first resource information. Alternatively, there is no intersection between the resources indicated by the second resource information and the resources indicated by the first resource information.

[0189] The result of this first type determination indicates that none of the resources indicated by the second resource information are correct. The first CISM may allocate some of the resources indicated by the first resource information to the first type external connection point without considering the second resource information. Alternatively, the first CISM may send a creation failure response to the VNFM. In response, the VNFM receives a creation failure response from the first CISM. The creation failure response indicates that the creation of the first type external connection point has failed. In this case, steps 201 to 213 may be repeated to create the first type external connection point.

[0190] Step 214: The first CISM sends a creation success response to the VNFM. In response, the VNFM receives a creation success response from the first CISM. The creation success response indicates that the first type of external connection point has been successfully created.

[0191] If the first type of external connection point is successfully created, the first CISM may create a creation success response and send it to the VNFM. For example, the creation success response may include the identifier of the VNF instance.

[0192] Optionally, the first CISM may send to the OSS information about the first type of external connection point that has been created, and the identifier of the VNF instance. The first CISM may actively send information about the first type of external connection point and the identifier of the VNF instance to the OSS. For example, the first CISM may send the information periodically or irregularly. Alternatively, the first CISM may not actively send the information. Alternatively, the OSS may periodically or irregularly request from the first CISM information about the first type of external connection point and the identifier of the VNF instance corresponding to the first type of external connection point. Information about the first type of external connection point may include, for example, the address information of the first type of external connection point. For example, continuing to use Figure 3 as an example, the first CISM may send the identifier of the VNF instance to the OSS and send the IP address of Serv1 (10.70.36.36) and the IP address of Serv2 (10.70.36.37).

[0193] OSS exposes information about the first type of external connection point, as well as the identifier of the VNF instance corresponding to the first type of external connection point, to external nodes so that external nodes can access the VNF based on information about the first type of external connection point.

[0194] Step 215: The VNFM sends an instantiation success response to the NFVO. In response, the NFVO receives a creation success response from the VNFM. The instantiation success response indicates that the VNF was successfully instantiated.

[0195] If the VNFM indicates that the first type of external connection point has been successfully created and that containers, etc., have been successfully deployed, the VNFM may generate an instantiation success response. For example, the instantiation success response carries the identifier of the VNF instance. After receiving the instantiation success response, the NFVO determines that the VNF has been successfully instantiated.

[0196] Steps 201 through 206, 209 through 210, 212, and 214 through 215 are optional steps. These optional steps are shown by dashed lines in Figure 2.

[0197] In this embodiment of the present application, the VNFM can determine whether the VNF currently to be instantiated includes a first resource parameter for a first type of external connection point. The NFVO does not need to determine the first resource parameter, thus reducing the processing load on the NFVO. The NFVO receives the first resource parameter from the VNFM, determines the first resource information for the first type of external connection point based on the first resource parameter, and transmits the first resource information to the CISM. The CISM may allocate some or all of the resources indicated by the first resource information to the first type of external connection point. A mechanism is provided for creating load balancers and / or external names as external connection points. In addition, more types of external connection points can be deployed within the VNF, thereby expanding the range of services to which the VNF can be applied. Furthermore, since different resources are required to create different types of external connection points, different resources may be used to create different types of external connection points, thereby improving flexibility for deploying external connection points within the VNF.

[0198] The following describes the method using an example, referring to the flowchart of the method for deploying the virtualized network functionality shown in Figure 4. In the process description in Figure 4, the communication system shown in Figure 1D is used as an example of a communication system, and the communication system is deployed in the NFV architecture shown in Figure 1A.

[0199] Step 401: The NFVO sends the first creation request to the VNFM. In response, the VNFM receives the first creation request from the NFVO. For details on the content of the first creation request, please refer to the explanation above.

[0200] Step 402: The VNFM sends the VNF instance identifier to the NFVO. In response, the NFVO receives the VNF instance identifier from the VNFM. For details on the content of the VNF instance identifier, please refer to the explanation above.

[0201] Step 403: The NFVO sends an instantiation request to the VNFM. In response, the VNFM receives the instantiation request from the NFVO. For details on the contents of the instantiation request, please refer to the explanation above.

[0202] Step 404: NFVO determines the first resource parameter.

[0203] The NFVO may determine the first resource parameter based on a pre-configured VNFD, or the NFVO may be pre-configured using the first resource parameter. For details on how the NFVO determines the first resource parameter based on the VNFD, the meaning of the VNFD, and the content of the first resource parameter, please refer to the above explanation.

[0204] Step 405: The NFVO determines the first resource information based on the first resource parameter.

[0205] For information on how NFVO determines the first resource parameter and the meaning of the first resource information, please refer to the explanation above.

[0206] It should be noted that in this embodiment of the present application, it is used as an example that the NFVO determines the first resource information based on a first resource parameter. However, the NFVO may determine the first resource information without using the first resource parameter. This is not limited to this embodiment of the present application.

[0207] Step 406: The NFVO transmits the first resource information to the first CISM via the CCM. In response, the first CISM receives the first resource information from the NFVO via the CMM. For the meaning of the first resource information, please refer to the explanation above.

[0208] Specifically, step 406 includes steps 406a and 406b. Step 406a: The NFVO transmits first resource information to the CCM. In response, the CCM receives first resource information from the NFVO. Step 406b: The CCM transmits first resource information to the first CISM. In response, the first CISM receives first resource information from the CCM.

[0209] For information on how to determine the first CISM using NFVO, please refer to the explanation above.

[0210] It should be noted that in this embodiment of the present application, it is used as an example that the NFVO transmits the first resource information to the first CISM via the CCM. In addition, the NFVO transmits the first resource information to the first CISM in multiple ways, and this is not limited to this embodiment of the present application.

[0211] Step 407: The first CISM sends a successful reception response to the NFVO via the CCM. In response, the NFVO receives a successful reception response from the first CISM via the CCM.

[0212] Specifically, step 407 includes steps 407a and 407b. Step 407a: The first CISM sends a reception success response to the CCM. In response, the CCM receives a reception success response from the first CISM. Step 407b: The CCM sends a reception success response to the NFVO. In response, the NFVO receives a reception success response from the CCM.

[0213] Optionally, the reception success response may include connection information for the first CISM. For the meaning of the reception success response and the connection information for the first CISM, please refer to the explanation above.

[0214] It should be noted that in this embodiment of the present application, it is used as an example that the first CISM transmits a successful reception response to the NFVO through the CCM. In addition, the first CISM transmits a successful reception response to the NFVO through the CCM in multiple ways, and this is not limited to this embodiment of the present application.

[0215] Step 408: NFVO determines the second resource information.

[0216] For the meaning of the second resource information and how to determine it, please refer to the explanation above.

[0217] Step 409: The VNFM sends a resource permission request to the NFVO. In response, the NFVO receives the resource permission request from the VNFM.

[0218] For an explanation of the meaning of resource permission requests, please refer to the previous explanation.

[0219] Optionally, the NFVO may first determine the second resource information, and then the VNFM may send a resource authorization request to the NFVO. Alternatively, the VNFM may first send a resource authorization request, and then the NFVO may determine the second resource information. Alternatively, the NFVO may determine the second resource information while the VNFM is sending the resource authorization request to the NFVO.

[0220] Step 410: The NFVO sends a resource authorization response to the VNFM. In response, the VNFM receives the resource authorization response from the NFVO.

[0221] Optionally, the resource permission response may include connection information for the first CISM and / or second resource information. See the previous explanation for the meaning of the second resource information and the first CISM connection information.

[0222] Step 411: The VNFM sends a resource creation request to the first CISM. In response, the first CISM receives the resource creation request from the VNFM.

[0223] For an explanation of the meaning of resource creation requests, please refer to the information in Figure 2.

[0224] Optionally, the resource creation request includes second resource information. In this embodiment of the present application, an example is used in which the resource creation request includes second resource information.

[0225] Step 412: The first CISM creates a container.

[0226] For information on how CISM creates containers, please refer to the explanation above.

[0227] Step 413: The first CISM creates a first type of external connection point and assigns some or all of the resources indicated by the first resource information to the first type of external connection point.

[0228] Optionally, after receiving the second resource information, the first CISM may verify the accuracy of the resource indicated by the second resource information. For details regarding the verification method and possible verification results, please refer to the above description.

[0229] Optionally, the first CISM may send to the OSS information about the first type of external connection point that was created, and the identifier of the VNF instance. See the previous description for how the first CISM sends information to the OSS. The OSS exposes to external nodes the information about the first type of external connection point and the identifier of the VNF instance corresponding to the first type of external connection point, so that external nodes can access the VNF based on the information about the first type of external connection point.

[0230] Step 414: The first CISM sends a creation success response to the VNFM. In response, the VNFM receives a creation success response from the first CISM.

[0231] For an explanation of the meaning of a successful creation response, please refer to the previous explanation.

[0232] Step 415: The VNFM sends an instantiation success response to the NFVO. In response, the NFVO receives an instantiation success response from the VNFM. For the meaning of the instantiation success response, please refer to the explanation above.

[0233] In one example, steps 401 through 404, 407 through 410, 412, and 414 through 415 are optional steps. These optional steps are shown by dashed lines in Figure 4.

[0234] In this embodiment of the present application, the NFVO determines first resource information for a first type of external connection point and transmits the first resource information to the CISM. The CISM may allocate some or all of the resources indicated by the first resource information to the first type of external connection point. A mechanism is provided for deploying load balancer and / or externally named services within the VNF to function as an external connection point. In addition, the range of services that can be supported by different types of external connection points may differ, and the VNF may support the deployment of more types of external connection points. Thus, the range of services supported by the VNF can be expanded. In addition, the NFVO may determine the first resource parameters itself in order to determine the first resource information based on the first resource parameters. The VNFM does not need to determine the first resource parameters, thereby reducing the workload on the VNFM. In addition, the interaction between the VNFM and the NFVO is reduced compared to the VNFM not needing to transmit the first resource parameters to the NFVO.

[0235] Based on the same inventive concept, one embodiment of this application further provides a communication device. Figure 5 is a schematic diagram of the structure of a communication device according to one embodiment of this application. The communication device shown in Figure 5 may be configured to implement the functions of the first network element in the method embodiment described above, and thus can achieve the beneficial effects of the method embodiment described above. In this embodiment of this application, the communication device shown in Figure 5 may be a chip system having CISM functionality.

[0236] As shown in Figure 5, the communication device includes a transceiver module 501 and a processing module 502.

[0237] In one embodiment, the communication device may be configured to implement the functions of CISM in the method embodiment shown in Figure 2 or Figure 4. For specific functions, please refer to the description of the method embodiment above. For example, the communication device may be configured to implement the functions of CISM in the method embodiment shown in Figure 2 or Figure 4.

[0238] Based on the same inventive concept, one embodiment of this application further provides a communication device. Figure 6 is a schematic diagram of the structure of a communication device according to one embodiment of this application. The communication device shown in Figure 6 may be configured to implement the functions of the first network element in the method embodiment described above, and thus can achieve the beneficial effects of the method embodiment described above. In this embodiment of this application, the communication device shown in Figure 6 may be a chip system having NFVO functionality.

[0239] As shown in Figure 6, the communication device includes a transceiver module 601 and a processing module 602.

[0240] In one embodiment, the communication device may be configured to implement the functions of the NFVO in the method embodiment shown in Figure 2 or Figure 4. For specific functions, please refer to the description of the method embodiment above. For example, the communication device may be configured to implement the functions of the NFVO in the method embodiment shown in Figure 2 or Figure 4.

[0241] Based on the same inventive concept, one embodiment of this application further provides a communication device. Figure 7 is a schematic diagram of the structure of a communication device according to one embodiment of this application. The communication device shown in Figure 7 may be configured to implement the functions of the first network element in the method embodiment described above, and thus can achieve the beneficial effects of the method embodiment described above. In this embodiment of this application, the communication device shown in Figure 7 may be a chip system having the function of a container as a service manager.

[0242] As shown in Figure 7, the communication device includes a transceiver module 701. Optionally, the communication device further includes a processing module 702. In Figure 7, the dashed box indicates that the processing module 702 is an optional module.

[0243] In one embodiment, the communication device may be configured to implement the VNFM functions in the method embodiment shown in Figure 2. For specific functions, please refer to the description of the method embodiment. For example, the communication device may be configured to implement the VNFM functions in the method embodiment shown in Figure 2.

[0244] Based on the same inventive concept, one embodiment of this application further provides a communication device. Figure 8 is a schematic diagram of the structure of a communication device according to one embodiment of this application. The communication device shown in Figure 8 may be configured to implement the VNFM function in the method embodiment described above, and thus can achieve the beneficial effects of the method embodiment described above. In this embodiment of this application, the communication device shown in Figure 8 may be a chip system having VNFM functionality.

[0245] As shown in Figure 8, the communication device includes a transceiver module 801. Optionally, the communication device further includes a processing module 802. In Figure 8, the dashed box indicates that the processing module 802 is an optional module.

[0246] In one embodiment, the communication device may be configured to implement the VNFM functions in the method embodiment shown in Figure 4. For specific functions, please refer to the description of the method embodiment. For example, the communication device may be configured to implement the VNFM functions in the method embodiment shown in Figure 4.

[0247] Based on the same inventive concept, one embodiment of this application further provides a communication device. Figure 9 is a schematic diagram of the structure of a communication device according to one embodiment of this application. The communication device shown in Figure 9 may be configured to implement the functions of the first network element in the method embodiment described above, and thus can achieve the beneficial effects of the method embodiment described above.

[0248] As shown in Figure 9, the communication device includes a processor 901 and an interface 902. The processor 901 and the interface 902 are coupled to each other. It can be understood that the interface 902 may be a transceiver or an input / output interface.

[0249] The communication device may include one or more processors 901. A processor 901 may also be called a processing unit and may implement specific control functions. A processor 901 may be a general-purpose processor or a dedicated processor, including, for example, a baseband processor or a central processing unit. The baseband processor may be configured to process communication protocols and communication data. The central processing unit may be configured to control the communication device, execute software programs, and / or process data. The different processors may be independent components or may be arranged in one or more processing circuits, for example, integrated into one or more application-specific integrated circuits.

[0250] Optionally, the communication device includes one or more memories 903 configured to store instructions. Instructions may be executed on a processor so that the communication device performs the method described in the above-described embodiment. The memories 903 in the communication device are optional components and are shown in Figure 9 using dashed boxes.

[0251] Optionally, memory 903 may store additional data. The processor and memory may be located separately or integrated into a single unit.

[0252] Optionally, the communication device may further include a memory 903 configured to store instructions executed by the processor 901, or input data required by the processor 901 to execute an instruction, or data generated after the processor 901 has executed an instruction.

[0253] In one embodiment, when the communication device is configured to implement the method embodiment shown in Figure 2 or Figure 4, the communication device may be configured to implement the functions of CISM in the method embodiment shown in Figure 2 or Figure 4. For specific functions, please refer to the description of the method embodiment above. In this case, the communication device may further implement the functions of the communication device shown in Figure 5.

[0254] In one embodiment, when the communication device is configured to implement the method embodiment shown in Figure 2 or Figure 4, the communication device may be configured to implement the functions of the NFVO in the method embodiment shown in Figure 2 or Figure 4. For specific functions, please refer to the description of the method embodiment above. In this case, the communication device may further implement the functions of the communication device shown in Figure 6.

[0255] In one embodiment, when the communication device is configured to implement the method embodiment shown in Figure 2, the communication device may be configured to implement the VNFM functions in the method embodiment shown in Figure 2. For specific functions, please refer to the description of the method embodiment above. In this case, the communication device may further implement the functions of the communication device shown in Figure 7.

[0256] In one embodiment, when the communication device is configured to implement the method embodiment shown in Figure 4, the communication device may be configured to implement the VNFM functions in the method embodiment shown in Figure 4. For specific functions, please refer to the description of the method embodiment above. In this case, the communication device may further implement the functions of the communication device shown in Figure 8.

[0257] Based on the same inventive concept, one embodiment of this application further provides a communication system. The communication system may include the communication device shown in Figure 5, the communication device shown in Figure 6, and the communication device shown in Figure 7.

[0258] Based on the same inventive concept, one embodiment of this application further provides a communication system. The communication system may include the communication device shown in Figure 5, the communication device shown in Figure 6, and the communication device shown in Figure 8.

[0259] Based on the same inventive concept, one embodiment of the present application provides a computer-readable storage medium configured to store a computer program, and when the computer program is executed on a computer, the computer is enabled to perform the method shown in either Figure 2 or Figure 4.

[0260] Those skilled in the art will understand that embodiments of this application may be provided as methods, systems, or computer program products. Accordingly, this application may take the form of hardware-only embodiments, software-only embodiments, or embodiments having a combination of software and hardware. In addition, this application may take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk memory, CD-ROM, and optical memory) containing computer-usable program code.

[0261] This application will be described with reference to flowcharts and / or block diagrams of the methods, devices (systems), and computer program products described herein. It should be understood that computer program instructions may be used to implement each step and / or block in the flowcharts and / or block diagrams, as well as combinations of steps and / or blocks in the flowcharts and / or block diagrams. These computer program instructions may be provided for a general-purpose computer, a dedicated computer, an embedded processor, or a processor in another programmable data processing device to generate a machine such that steps executed by the processor of the computer or another programmable data processing device generate a device for implementing one or more instructions in the flowchart and / or one or more blocks in the block diagram.

[0262] These computer program instructions may, alternatively, be stored in computer-readable memory, which can instruct a computer or another programmable data processing device to operate in a particular manner, such that the instructions stored in computer-readable memory generate artifacts including an instruction unit. The instruction unit implements one or more steps in a flowchart and / or one or more blocks in a block diagram.

[0263] These computer program instructions may be loaded onto a computer or another programmable data processing device so that a series of operational steps are executed on the computer or another programmable device, thereby creating a computer or another programmable device. Thus, instructions executed on the computer or another programmable device provide one or more steps in a flowchart and / or steps for performing a specific function in one or more blocks in a block diagram.

[0264] It is clear that a person skilled in the art can make various modifications and alterations to this application without departing from the spirit and scope of this application. This application is intended to encompass these modifications and alterations to this application, provided that they fall within the scope of protection defined by the appended claims and equivalent art. [Explanation of symbols]

[0265] 110 NFV Management and Orchestration System, NFV MANO 111 NFVO 112 Virtualization Network Function Manager (VNFM) 113 Virtualization Infrastructure Manager, VIM 114 CISM 120 Operational Support System / Business Support System, OSS / BSS 130-element management system, EMS 140 VNF 150 NFV infrastructure, NFVI 151 Virtual Resource Layer 152 Virtualization Layer 153 Hardware Resource Layer 501, 601, 701, 801 Transceiver Modules 502, 602, 702, 802 processing modules 901 Processor 902 Interface 903 memory

Claims

1. A method for deploying virtualized network functions (VNFs), A step in which a virtualized network function manager (VNFM) receives an instantiation request from a network function virtualization orchestrator (NFVO), wherein the instantiation request is used to request the instantiation of a VNF, The VNFM includes the step of determining a first resource parameter based on a virtualized network function descriptor (VNFD), The steps include: sending a resource authorization request to the NFVO via the VNFM, wherein the resource authorization request includes a first resource parameter, the first resource parameter is used to determine first resource information, the first resource information indicates a resource pre-allocated to a first type of external connection point, and the external connection point is an entry point for external nodes to access the VNF; The NFVO determines first resource information based on the first resource parameters, wherein the first resource information indicates a resource used to create a first type of external connection point, the external connection point is an entry point for external nodes to access the virtualized network function (VNF), and the first type is a load balancer and / or external name. The NFVO transmits the first resource information to Container Infrastructure Service Management (CISM), wherein the resource indicated by the first resource information is used to create the first type of external connection point. The VNFM sends a resource creation request to the CISM, the VNFM being used to request the creation of the first type of external connection point, The steps include creating the first type of external connection point using the CISM and assigning some or all of the resources indicated by the first resource information to the first type of external connection point, A method that includes this.

2. The method according to claim 1, wherein the first resource information includes information about an address assigned by the first type of external connection point.

3. The method according to claim 2, wherein the first resource information further includes information relating to the functionality supported by the first type of external connection point.

4. The step of determining the first resource information is A step of determining the first resource information based on the first resource parameter, The method according to claim 1, including the method described in claim 1.

5. The step of determining the first resource information is A step of determining a first resource parameter from a virtualized network function descriptor (VNFD) corresponding to the VNF, wherein the first resource parameter is used to determine the first resource information, and the VNFD includes the type information of the external connection point of the VNF and resource parameters corresponding to each type of external connection point. A step of determining the first resource information based on the first resource parameter, The method according to claim 1, including the method described in claim 1.

6. A communication system comprising a virtualized network function manager (VNFM), a network function virtualization orchestrator (NFVO), and a container infrastructure service management (CISM), The aforementioned VNFM is, Receiving an instantiation request from the NFVO, the instantiation request being used to request the instantiation of a virtualized network function (VNF), and receiving Sending a resource authorization request to the NFVO, wherein the resource authorization request includes a first resource parameter, the first resource parameter is used to determine first resource information, the first resource information indicates a resource pre-allocated to a first type of external connection point, the external connection point is an entry point for an external node to access the VNF, and sending It is configured to do the following: The aforementioned NFVO is, Determining a first resource information, wherein the first resource information indicates a resource of a first type reassigned to the external connection point, the external connection point is an entry point for the external node to access the VNF, and the first type is a load balancer and / or external name. Transmitting the first resource information to the CISM, wherein the resource indicated by the first resource information is used to create a first type of external connection point. It is configured to do the following: The aforementioned CISM is Create an external connection point of the first type and assign some or all of the resources indicated by the first resource information to the external connection point of the first type. A system configured in such a way.

7. The system according to claim 6, wherein the first resource information includes information relating to an address assigned to the first type of external connection point.

8. The system according to claim 7, wherein the first resource information further includes information relating to a function supported by the first type of external connection point.

9. The system according to any one of claims 6 to 8, wherein the NFVO is configured to determine the first resource information based on the first resource parameters.

10. The system according to any one of claims 6 to 8, wherein the VNFM is further configured to determine the first resource parameter from a virtualized network function descriptor (VNFD) corresponding to the VNF, the first resource parameter is used to determine the first resource information, and the VNFD includes type information of the external connection points of the VNF and resource parameters corresponding to each type of external connection point.

Images