Method and apparatus for deploying virtualized network functions - Patents.com
The method and apparatus enable the deployment of load balancers and externally named services as external connection points in NFV architectures, improving flexibility and functionality by managing resource allocation and communication, thus enhancing the capabilities of virtualized network functions.
Patent Information
- Application Number
- JP2024523774
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-10-20
- Filing Date
- 2022-10-17
- Publication Date
- 2024-11-06
- Estimated Expiration
- 2042-10-17
AI Technical Summary
There is a lack of effective solutions for deploying services within Network Functions Virtualization (NFV) architectures as external connection points, limiting the flexibility and functionality of virtualized network functions.
A method and apparatus for deploying virtualized network functions that create and allocate resources for load balancers and externally named services as external connection points within NFV architectures, using a container infrastructure service management system to manage resource allocation and communication between network elements.
Enhances the flexibility and functionality of NFV architectures by allowing multiple types of external connection points, reducing processing and communication overhead, and expanding the range of services that can be supported by virtualized network functions.
Smart Images

Figure 2024540964000001_ABST
Abstract
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 Office on October 20, 2021, which is incorporated by reference in its entirety.
[0002] The present application relates to the field of communications technologies, and in particular to a method and apparatus for deploying virtualized network functions. [Background technology]
[0003] Network functions virtualization (NFV) technology uses general-purpose hardware devices and virtualization technologies to build virtualized network functions (VNFs), and uses VNFs to carry the functions of dedicated devices on traditional networks, thereby reducing the costs incurred by deploying dedicated devices.
[0004] The container management platform is implemented based on containerization technology, for example, the K8S (Kubernetes) platform. One container management platform manages one cluster, and the cluster includes several physical machines or virtual machines. The physical machines or virtual machines may be regarded as nodes. Correspondingly, containers are deployed on the physical machines or virtual machines. The container management platform creates containers in the management 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] With the continuous development of containerization technology, a container management platform is introduced into the NFV architecture. In this way, one or more pods can be deployed within a VNF. In the NFV architecture where the container management platform is introduced, an external connection point (ExtCp) is defined, and a service can be used as an entrance for an external node to access a pod of an NFV. An external node can be understood as a node other than a VNF. However, there is still no solution for deploying a service within the NFV architecture as an external connection point. Summary of the Invention
[0006] Embodiments of the present application provide a method and apparatus for deploying a virtualized network function to provide a mechanism for deploying services within a VNF to act as an external attachment point. [Means for solving the problem]
[0007] According to a first aspect, an embodiment of the present application provides a method for deploying a virtualized network function. The method may be executed by a container infrastructure service management (CISM), or may be executed by a chip system or a communication system having a function of CISM. For ease of explanation, the following uses an example in which a CISM executes the method for explanation. The method includes: receiving first resource information, the first resource information indicating resources pre-allocated to a first type of external connection point, the external connection point being an entrance for accessing the virtualized network function VNF by an external node, the first type including a load balancer and / or an external name; and creating a first type of external connection point and allocating a part or the whole 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, the CISM receives first resource information of resources pre-allocated to a first type of external connection point, creates a first type of external connection point, and allocates a part or the whole of the resources indicated by the first resource information to the first type of external connection point. A mechanism is provided for deploying a load balancer and / or an externally named service within a VNF to function as an external connection point. The load balancer and / or the externally named service to function as an external connection point may be deployed within a VNF to enable the VNF to support more types of external connection points. In addition, the service ranges that may be supported by different types of external connection points may be different, and a VNF may support multiple types of external connection points. Thus, the service ranges supported by a VNF can be expanded. In addition, the resources required to deploy different types of external connection points may be different, so that the resources that may be used to deploy an external connection point are enhanced.
[0009] In a possible implementation, the step of creating a first type external connection point and allocating some or all of the resources indicated by the first resource information to the first type external connection point includes the steps of receiving a resource creation request from a virtualized network function manager VNFM, where the resource creation request is used to request to create a first type external connection point, where 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, creating the first type external connection point and allocating the resources indicated by the second resource information to the first type external connection point.
[0010] In this implementation, the CISM receives second resource information from the VNFM, and the CISM determines resources used to create a first type of external connection point based on the second resource information. The CISM does not need to determine resources specifically assigned to the first type of external connection point from the resources indicated by the first resource information. Thus, the process of the CISM creating a first type of external connection point is simplified. In addition, the 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 to ensure the accuracy of the resources indicated by the second resource information. In addition, the VNFM may further carry the second resource information in a resource creation request and send the resource creation request to the CISM. The CISM does not need to receive the second resource information from the VNFM through a dedicated message, thereby reducing the amount of interaction between the CISM and the VNFM.
[0011] In a possible implementation, the CISM sends address information of a container infrastructure service management CISM to a network function virtualization orchestrator NFVO, where the address information of the CISM indicates the CISM to create an external connection point of the first type.
[0012] In this implementation, the CISM may send the address information of the CISM to the NFVO, which may then send the address information of the CISM to the VNFM. In this manner, the VNFM communicates with the CISM based on the address information of the CISM. The VNFM does not need to perform a process of discovering the CISM, thereby reducing the communication steps between the VNFM and the CISM.
[0013] According to a second aspect, an embodiment of the present application provides a method for deploying a virtualized network function. The method may be executed by an NFVO, or may be executed by a chip system or a communication system having the function of an NFVO. For ease of explanation, the following uses an example in which an NFVO executes the method for explanation. The method includes: determining first resource information, where the first resource information indicates a resource pre-allocated to a first type of external connection point, where the external connection point is an entrance for accessing the virtualized network function VNF by an external node, and the first type is a load balancer and / or an external name; and sending the first resource information to a container infrastructure service management CISM, where the resource indicated by the first resource information is used to create the first type of external connection point.
[0014] In this embodiment of the present application, the NFVO determines first resource information and sends the first resource information to the CISM. A method is provided for indicating 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, such that the CISM deploys a load balancer and / or an externally named service to function as the external connection point. The CISM does not need to determine the first resource information by itself, thereby reducing the amount of processing by the CISM.
[0015] In a possible implementation, the first resource information includes information about an address assigned by the first type of external connection point. Alternatively, the first resource information further includes information about functions supported by the first type of external connection point.
[0016] In this implementation, the first resource information includes information about the address. The CISM may then assign the address indicated by the information about the address to the first type of external connection point, so that the external node can access the external connection point based on the address. A method is provided for the external node to discover the first type of external connection point. In addition, the first resource information may further include information about functions supported by the first type of external connection point. In this way, the CISM may then create a first type of external connection point that better meets the function requirements based on the information about the functions.
[0017] In a possible implementation, the instantiation request is sent to the VNFM, and the instantiation request is used to request the VNF to be instantiated. The resource authorization request is received from the VNFM, the resource authorization request including a first resource parameter, and the first resource parameter is used to determine 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 the first resource parameter to the NFVO, which does not need to determine the first resource parameter by itself, thereby reducing the amount of processing by the NFVO.
[0019] In a possible implementation, the first resource parameter is determined from a virtualized network function descriptor VNFD corresponding to the VNF, and the first resource parameter is used to determine first resource information, where the VNFD includes type information of external attachment points of the VNF and resource parameters corresponding to each type of external attachment 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 by itself, and determines the first resource information based on the first resource parameter. The VNFM does not need to determine the first resource parameter, thereby reducing the amount of processing by the VNFM. In addition, the VNFD is generally configured in the NFVO, and the NFVO analyzes the VNFD by 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 a possible implementation, second resource information is sent to the VNFM, where the resources indicated by the second resource information are a subset of the resources indicated by the first resource information, and where the resources indicated by the second resource information are used to create an external attachment point of the first type.
[0022] In this implementation, the NFVO determines second resource information and transmits the second resource information to the VNFM. The VNFM may then transmit the second resource information to the CISM. This corresponds 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 resources to be used from the resources indicated by the first resource information, thereby reducing the amount of processing by the CISM.
[0023] In a possible implementation, address information of the CISM is received from the CISM, and the address information of the CISM is sent to the VNFM, where the address information of the CISM indicates the CISM on which to create the first type external connection point.
[0024] In this implementation, the CISM may send the address information of the CISM to the NFVO, which may then send the address information of the CISM to the VNFM. In this manner, the VNFM may directly communicate with the CISM based on the address information of the CISM, thereby simplifying the communication process between the VNFM and the CISM.
[0025] According to a third aspect, an embodiment of the present application provides a method for deploying a virtualized network function. The method may be executed by a VNFM, or may be executed by a chip system or a communication system having the function of the VNFM. For ease of explanation, the following uses an example in which the VNFM executes the method for explanation. The method includes: receiving an instantiation request from a network function virtualization orchestrator NFVO, where the instantiation request is used to request a virtualized network function VNF to be instantiated; and sending a resource authorization request to the NFVO, where the resource authorization request includes a first resource parameter, where the first resource parameter is used to determine first resource information, where the first resource information indicates a resource pre-allocated to a first type of external attachment point, where the external attachment point is an entrance for accessing the virtualized network function VNF by an external node.
[0026] In this embodiment of the present application, a method for determining a first resource parameter is provided, so that the VNFM can determine the first resource parameter and send the first resource parameter to the NFVO, and the NFVO does not need to determine the first resource parameter by itself, thereby reducing the amount of processing by the NFVO.
[0027] In a possible implementation, the first resource parameter is determined from a VNFD corresponding to the VNF, the first resource parameter is used to determine the first resource information, and the VNFD includes type information of external attachment points of the VNF and resource parameters corresponding to each type of external attachment point.
[0028] In this implementation, the VNFM may parse 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, second resource information is received from a network function virtualization orchestrator NFVO, the second resource information indicating pre-allocated resources for a first type of external connection point, the external connection point being an entrance for accessing the virtualized network function VNF by an external node, the first type being a load balancer and / or an external name, the second resource information is sent to a container infrastructure service management CISM, the second resource information is used to create the first type of external connection point.
[0030] In this implementation, the VNFM may receive second resource information from the NFVO and send the second resource information to the CISM. In this manner, the CISM may determine which resources should be assigned to the first type of external attachment point based on the second resource information. The CISM does not need to determine the specific resources to be used from the resources indicated by the first resource information, thereby reducing the amount of processing of the CISM.
[0031] According to a fourth aspect, an embodiment of the present application provides a method for deploying a virtualized network function. The method may be executed by a VNFM, or may be executed by a chip system or a communication system having a function of the VNFM. For ease of explanation, the following uses an example in which the VNFM executes the method for explanation. The method includes: receiving second resource information from a network function virtualization orchestrator NFVO, where the second resource information indicates resources pre-allocated to a first type of external connection point, the external connection point is an entrance for accessing the virtualized network function VNF by an external node, and the first type is a load balancer and / or an external name; and sending the second resource information to a container infrastructure service management CISM, where the resources indicated by the second resource information are used to create the first type of external connection point.
[0032] In a possible implementation, an instantiation request is received from a network function virtualization orchestrator NFVO, the instantiation request is used to request a virtualized network function VNF to be instantiated, a resource authorization request is sent to the NFVO, the resource authorization request includes first resource parameters, the first resource parameters are used to determine first resource information, the first resource information indicates resources pre-allocated to a first type of external attachment point, the external attachment point being an entry point for accessing the virtualized network function VNF by an external node.
[0033] In a possible implementation, the first resource parameter is determined from a VNFD corresponding to the VNF, the first resource parameter is used to determine the first resource information, and the VNFD includes type information of external attachment points of the VNF and resource parameters corresponding to each type of external attachment point.
[0034] In addition, for other technical effects provided 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 corresponding embodiments.
[0035] According to a fifth aspect, an embodiment of the present application provides a method for deploying a virtualized network function. The method may be executed by a communication system including a VNFM, a CISM, and an NFVO, or may be executed by a communication system having the functions of a VNFM, a CISM, and an NFVO. For ease of explanation, the following uses an example in which a communication system includes a VNFM, a CISM, and an NFVO for explanation. The method includes a step in which a virtualized network function manager VNFM receives an instantiation request from a network function virtualization orchestrator NFVO, where the instantiation request is used to request a VNF to be instantiated. The VNFM sends a resource authorization request to the NFVO, where the resource authorization request includes a first resource parameter, where the first resource parameter is used to determine first resource information, where the first resource information indicates a resource pre-allocated to a first type of external attachment point, where the external attachment point is an entrance for an external node to access the virtualized network function VNF. The NFVO determines first resource information, where the first resource information indicates resources pre-allocated to a first type of external connection point, where the external connection point is an entrance for accessing the virtualized network function VNF by an external node, where the first type is a load balancer and / or an external name. The NFVO sends the first resource information to a container infrastructure service management CISM, where the resources indicated by the first resource information are used to create the 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 the instantiation request, the VNFM may determine a first resource parameter required to deploy a first type of external attachment point in the VNF and send the first resource parameter to the NFVO. The NFVO determines the first resource information based on the first resource parameter to send the first resource information to the CISM. The CISM receives and creates the first type of external attachment point. A mechanism is provided to deploy a load balancer and / or an externally named service in the VNF to function as an external attachment point. In addition, the VNFM determines the first resource parameter. The NFVO does not need to determine the first resource parameter, thereby reducing the amount of processing by the NFVO.
[0037] In addition, for other technical effects provided by the fifth aspect, please refer to the description of the technical effects of the first aspect, the second aspect, the third aspect, or the corresponding embodiments.
[0038] According to a sixth aspect, an embodiment of the present application provides a method for deploying a virtualized network function. The method may be executed by a communication system including a VNFM, a CISM, and an NFVO, or may be executed by a communication system having the functions of a VNFM, a CISM, and an NFVO. The method includes a step of an NFVO determining first resource information, the first resource information indicating resources pre-allocated to a first type of external connection point, the external connection point being an entrance for accessing the virtualized network function VNF by an external node, and the first type being a load balancer and / or an external name. A network function virtualization orchestrator NFVO sends the first resource information to a container infrastructure service management CISM, and the resources indicated by the first resource information are used to create the first type of external connection point. The virtualized network function manager VNFM determines second resource information from the NFVO, the second resource information indicating resources pre-allocated to a first type of external connection point, the external connection point being an entrance for accessing the virtualized network function VNF by an external node, the first type being a load balancer and / or an external name. The second resource information is sent to a container infrastructure service management CISM, and the resources indicated by the second resource information are used to create the first type of external connection point. The CISM receives a resource creation request from the VNFM, the resource creation request is used to request to create the first type of external connection point, the resource creation request including 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 the first resource information and send the first resource information to the CISM. In addition, the NFVO may further determine the second resource information and send the second resource information to the VNFM. When deploying the first type of external attachment point, the CISM may deploy the first type of external attachment point based on the resources indicated by the second resource information. A mechanism is provided to deploy a load balancer and / or an external name service within the VNF to function as the external attachment point. Since the NFVO may directly specify that the first type of external attachment point is to be created, the CISM does not need to determine the specific resources used to create the first type of external attachment point from the resources indicated by the first resource information. Therefore, the process of the CISM deploying the first type of external attachment point is relatively simplified.
[0040] In addition, for other technical effects provided by the sixth aspect, please refer to the description of the technical effects of the first aspect, the second aspect, the third aspect, or the corresponding embodiments.
[0041] According to a seventh aspect, an embodiment of the present application provides a communication device. The communication device may be a CISM in the first aspect, or an electronic device (e.g., a chip system) configured in the CISM, or a relatively large device including the CISM. The CISM includes corresponding means or modules configured to implement the first aspect or any of the optional implementation forms. For example, the communication device includes a processing module (which may also be referred to as a processing unit) and a transceiver module (which may also be referred to as a transceiver unit).
[0042] For example, the transceiver module is configured to receive first resource information, the first resource information indicating resources pre-allocated to a first type of external connection point, the external connection point being an entrance for accessing the virtualized network function VNF by an external node, the first type including a load balancer and / or an external name, and the processing module is configured to create the first type of external connection point and assign 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 the memory and configured to execute instructions in the memory to implement the method performed by the fifth network element in the first aspect or implementation. Optionally, the communication device further includes other components, such as an antenna, an input / output module, and an interface. These components may be hardware, software, or a combination of software and hardware.
[0044] In addition, for other technical effects provided by the seventh aspect or some implementation forms of the seventh aspect, please refer to the description of the technical effects of the first aspect or corresponding embodiments.
[0045] According to an eighth aspect, an embodiment of the present application provides a communication device. The communication device may be an NFVO in the second aspect, or an electronic device (e.g., a chip system) configured in the NFVO, or a relatively large device including the NFVO. The NFVO includes corresponding means or modules configured to implement any of the implementation forms of the second aspect or options. For example, the communication device includes a processing module (which may also be referred to as a processing unit) and a transceiver module (which may also be referred to as a transceiver unit).
[0046] For example, the processing module is configured to determine first resource information, the first resource information indicating resources pre-allocated to a first type of external connection point, the external connection point being an entrance for accessing the virtualized network function VNF by an external node, the first type being a load balancer and / or an external name. The transceiver module is configured to transmit the first resource information to the CISM, the resources indicated by the first resource information being used to create the first type of external connection point.
[0047] In an optional implementation, the communication device includes a processor coupled to the memory and configured to execute instructions in the memory to implement the method performed by the fifth network element in the first aspect or implementation. Optionally, the communication device further includes other components, such as an antenna, an input / output module, and an interface. These components may be hardware, software, or a combination of software and hardware.
[0048] In addition, for other technical effects provided by the eighth aspect or some implementation forms of the eighth aspect, please refer to the description of the technical effects of the second aspect or corresponding embodiments.
[0049] According to a ninth aspect, an embodiment of the present application provides a communication device. The communication device may be a VNFM in the third aspect, or an electronic device (e.g., a chip system) configured in the VNFM, or a relatively large device including the VNFM. The VNFM includes corresponding means or modules configured to implement any of the implementation forms of the first aspect or options. For example, the communication device includes a transceiver module (which may also be referred to as a transceiver unit). Optionally, the communication device further includes a processing module (which may also be referred to as a processing unit).
[0050] For example, the transceiver module is configured to receive an instantiation request from a network function virtualization orchestrator NFVO, where the instantiation request is used to request that a virtualized network function VNF be instantiated, and to send a resource authorization request to the NFVO, where the resource authorization request includes a first resource parameter, where the first resource parameter is used to determine first resource information, where the first resource information indicates resources pre-allocated to a first type of external attachment point, where the external attachment point is an entrance for accessing the virtualized network function VNF by an external node.
[0051] Optionally, the processing module is configured to determine a first resource parameter from a VNFD corresponding to the VNF, the first resource parameter being used to determine first resource information, the VNFD including type information of external attachment points of the VNF and resource parameters corresponding to each type of external attachment point.
[0052] In an optional implementation, the communication device includes a processor coupled to the memory and configured to execute instructions in the memory to implement the method performed by the fifth network element in the first aspect or implementation. Optionally, the communication device further includes other components, such as an antenna, an input / output module, and an interface. These components may be hardware, software, or a combination of software and hardware.
[0053] In addition, for other technical effects provided by the ninth aspect or some implementation forms of the ninth aspect, please refer to the description of the technical effects of the third aspect or corresponding embodiments.
[0054] According to a tenth aspect, an embodiment of the present application provides a communication device. The communication device may be a VNFM in the fourth aspect, or an electronic device (e.g., a chip system) configured in the VNFM, or a relatively large device including the VNFM. The VNFM includes corresponding means or modules configured to implement any of the implementation forms of the first aspect or options. For example, the communication device includes a transceiver module (which may also be referred to as a transceiver unit). Optionally, the communication device further includes a processing module (which may also be referred to as a processing unit).
[0055] For example, the transceiver module is configured to receive second resource information from a network function virtualization orchestrator NFVO, where the second resource information indicates pre-allocated resources for a first type of external connection point, where the external connection point is an entrance for accessing the virtualized network function VNF by an external node, where the first type is a load balancer and / or an external name, and send the second resource information to a container infrastructure service management CISM, where the second resource information is used to create the first type of external connection point.
[0056] Optionally, the processing module is configured to determine a first resource parameter from a VNFD corresponding to the VNF, the first resource parameter being used to determine first resource information, the VNFD including type information of external attachment points of the VNF and resource parameters corresponding to each type of external attachment point.
[0057] In an optional implementation, the communication device includes a processor coupled to the memory and configured to execute instructions in the memory to implement the method performed by the fifth network element in the first aspect or implementation. Optionally, the communication device further includes other components, such as an antenna, an input / output module, and an interface. These components may be hardware, software, or a combination of software and hardware.
[0058] In addition, for other technical effects provided by the tenth aspect or some implementation forms of the tenth aspect, please refer to the description of the technical effects of the fourth aspect or corresponding embodiments.
[0059] According to an eleventh aspect, an embodiment of the present application provides a communication system. The communication system includes a communication device according to the seventh aspect, the eighth aspect, and the ninth aspect. Alternatively, the communication system includes a communication device according to the seventh aspect, the eighth aspect, and the tenth aspect.
[0060] According to a twelfth aspect, an 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 the instructions, a method according to the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, or the sixth aspect is performed.
[0061] According to a thirteenth aspect, there is provided a computer readable storage medium configured to store a computer program or instructions which, when executed, perform a method according to the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect or the sixth aspect.
[0062] According to a fourteenth aspect there is provided a computer program product comprising instructions which, when executed on a computer, perform a method according to the first, second, third, fourth, fifth or sixth aspect. [Brief description of the drawings]
[0063] [Figure 1A] FIG. 1 is a schematic diagram of an NFV architecture to which an embodiment of the present application can be applied. [Figure 1B] FIG. 1 is a schematic diagram of the structure of a VNF. [Figure 1C] FIG. 2 is a schematic diagram of another NFV architecture to which an embodiment of the present application can be applied. [Figure 1D] FIG. 1 is a schematic diagram of the structure of a communication system according to an embodiment of the present application; [Diagram 2] 1 is a schematic flowchart of a method for deploying virtualized network functions according to an embodiment of the present application. [Diagram 3] FIG. 1 is a schematic diagram of deploying an external connection point within a VNF according to an embodiment of the present application. [Figure 4] 4 is another schematic flowchart of a method for deploying virtualized network functions according to an embodiment of the present application. [Diagram 5] FIG. 1 is a schematic diagram of the structure of a communication device according to an embodiment of the present application. [Figure 6] FIG. 2 is a schematic diagram of the structure of a communication device according to an embodiment of the present application. [Figure 7] 3 is a schematic diagram of the structure of a communication device according to an embodiment of the present application. [Figure 8] 4 is a schematic diagram of the structure of a communication device according to an embodiment of the present application. [Figure 9] 5 is a schematic diagram of the structure of a communication device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0064] In order to make the objectives, technical solutions and advantages of the embodiments of the present application clearer, the following will describe in detail the technical solutions of the embodiments of the present application with reference to the accompanying drawings and specific implementation forms herein.
[0065] The following describes terms used in the embodiments of the present application.
[0066] 1. A network element in an embodiment of the present application may be a physical device in a network, or may be a device that integrates multiple physical devices. Alternatively, a network element in an embodiment of the present application may be a logical concept, such as a software module in a physical device, or a network function corresponding to a service provided by each network device. A network function may be understood as a virtualization function implemented using virtualization technology.
[0067] 2. A connection point in the embodiment of the present application may be understood as an interface of a VNF. The connection point includes an internal connection point and an external connection point. The connection point includes an internal connection point and an external connection point. The internal connection point may be, 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 the VNFCs may communicate with each other through the internal connection points. The external connection node is used for communication between a VNF and an external node. The external connection point may be a virtual connection point (virtual Cp) type. The virtual connection point may be implemented using a service. The service includes a node port, a load balancer, an external name, and other types. The node port, the load balancer, and the external name may be further understood as three technologies for implementing a service. Correspondingly, the external connection point of a node port in the embodiment of the present application may also be called a virtual connection point of a node port, a service of a node port, or an external connection point implemented using a node port technology. The external connection point of a load balancer in the embodiment of the present application may also be called a virtual connection point of a load balancer, a service of a load balancer, or an external connection point implemented using a load balancer technology. The external connection point of an external name in the embodiment of the present application may also be called a virtual connection point of an external name, a service of an external name, or an external connection point implemented using an external name technology.
[0068] In an embodiment of the present application, the CISM in 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 may access the service by accessing the port. For a load balancer service, information about a load balancer provided by a network service vendor (e.g., an internet protocol (IP) address) of the load balancer) may be configured for the service. An external node may 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 accesses the service by accessing the external name.
[0069] In the embodiment of the present application, the three types of external connection points are represented by node ports, load balancers, and external names, which are merely examples and not limitations. In a standard evolution process, the names of node ports, load balancers, or external names may be changed. This is not a limitation in the embodiment of the present application.
[0070] 3. A virtualization deployment unit (VDU) in the embodiments of this application is used to describe a unit for deploying a VNF. If a VNF is deployed using a virtual machine technology, one VDU represents one virtual machine. Alternatively, if a VNF is deployed using a containerization technology, one VDU represents one group of containers.
[0071] 4. The virtualized network function descriptor (VNFD) of the embodiment of the present application may also be referred to as the deployment identifier of a VNF. The VNFD is generally configured in an NFV orchestrator (NFVO). The VNFD is used to describe a VNF. The VNFD includes information about a virtualization deployment unit (VDU), information about a connection point descriptor (CPD), information about a virtual link descriptor (VLD), etc. For example, if one VDU represents one virtual machine, the information about the VDU includes descriptive information about the resource requirements of the virtual machine, 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 resource requirements of the group of containers. The information about the CPD includes type information and resource parameters for each type of external connection point in the VNF. The type information of the external connection point indicates the type of the external connection point. The resource parameters of the external connection point indicate resources required to create this type of external connection point. The resource parameters of the external connection point include, for example, an address expression format of the external connection point. The address expression format expresses an address by, for example, an internet protocol. Optionally, the resource parameters of the external connection point further include a type of function supported by the external connection point. The information on the VLD describes the virtual network connection requirements between the VDUs, such as information such as connection type and / or bandwidth. In one example, when a VNF includes a first type of external connection point, but the VNFD of the prior art does not actually include a related definition of the first type of external connection point, the type information of the first type of external connection point in the embodiment of the present application can be reconfigured in the VNFD corresponding to the VNF.For example, type information of the first type of external attachment point may be added to type information of the virtual attachment point in the VNFD.
[0072] 5. The container in the embodiment of the present application can be understood as a software unit. The container includes necessary elements, such as system tools, that enable an application to run smoothly in different environments. The container simplifies the development and deployment of applications.
[0073] 6. A name space in the embodiment of this application is an organization mechanism for classifying, filtering, and managing objects, such as services, in a cluster managed by a container management platform. An object added to a cluster may belong to one namespace. Within the same namespace, the name of an object is unique, but within different namespaces, different objects may have the same name.
[0074] In the embodiment of the present application, "multiple" means two or more. In view of this, "multiple" can also be understood as "at least two" in the embodiment of the present application. "At least one" can be understood as one or more, for example, one, two, or more. For example, including at least one means one, two, or more, without limiting which are included. For example, if at least one of A, B, and C is included, A, B, C, A and B, A and C, B and C, or A and B and C may be included. The term "and / or" describes an association relationship to describe related objects, and represents that three relationships may exist. For example, A and / or B may represent the following three cases, namely, when only A exists, when both A and B exist, and when only B exists. In addition, the character " / " generally indicates an "or" relationship between related objects. The terms "system" and "network" in the embodiment of the present application may be used interchangeably.
[0075] Unless otherwise specified, ordinals such as "first" and "second" referred to in the embodiments of the present application are used to distinguish between multiple objects, and are not used to limit the order, chronological order, priority, or importance of the multiple objects. For example, "first resource information" and "second resource information" in the embodiments of the present application are used to represent two pieces of resource information, and are not used to limit the priority of the two pieces of resource information.
[0076] For ease of understanding, the following provides a brief overview of NFV concepts and architecture.
[0077] 1.NFV NFV decouples software from hardware, so that the functionality of network devices is no longer dependent on dedicated hardware. In addition, cloud computing capabilities enable flexible resource sharing, which allows for rapid development and deployment of new services. A network service implemented using NFV is called a network service (NS). For example, an NS includes the internet protocol multimedia subsystem (IMS) network service, or the core network service of the 5th generation system (5GS). Each NS includes 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 the embodiments of the present application are applicable, or may be understood as a schematic diagram of an NFV architecture in which a container management platform is introduced. 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 managing and orchestrating the entire NFVI resource. The NFV MANO 110 includes an NFVO 111, one or more virtualized network function managers (VNFMs) 112, a virtualized infrastructure manager (VIM) 113, and a CISM 114.
[0080] The NFVO 111 is mainly responsible for managing the life cycle of NSs, allocating hardware resources (e.g., computing hardware, storage hardware, and network hardware in FIG. 1A) and virtual resources (e.g., virtual computing, virtual storage, and virtual network in FIG. 1A) in the NFVI 150, scheduling hardware resources and virtual resources in the NFVI, etc. The NFVO 111 may further communicate with one or more VNFMs 112 to perform corresponding resource requests, etc. In addition, the NFVO 111 may also communicate with a virtualized infrastructure manager (VIM) 113 for resource allocation, reservation, etc.
[0081] The VNFM 112 is primarily responsible for the lifecycle management of one or more VNFs 140. Lifecycle management includes instantiating, updating, querying, auto scaling, terminating, etc. of the VNFs 140. The VNFM 112 may communicate with the VNFs 140 to finalize the lifecycle management of the VNFs and exchange information about configuration and state. Optionally, there may be multiple VNFMs 112, and each VNFM 112 may be responsible for the lifecycle management of a different type of VNF 140.
[0082] The VIM 113 controls and manages interactions between the VNFs 140 and hardware or virtual resources in the NFVI 150. For example, the VIM 113 performs resource management functions, including managing infrastructure resources, allocating (e.g., adding resources to containers), and executing functions (e.g., collecting fault information for the NFVI 150). The VNFM 112 and the VIM 113 may communicate with each other to request resources, exchange virtual resources, and exchange information about status.
[0083] The CISM 114 corresponds to a container management platform in the NFV architecture and is responsible for managing container resources, including creating, updating, querying, auto scaling, terminating, etc. When a VNF is deployed in the form of a container, the VNFM 112 may communicate with the CISM 114 to request to create a container resource.
[0084] The OSS / BSS 120 is primarily targeted at telecommunication service providers, and provides integrated network management, such as fault monitoring and network information collection, as well as service operation management functions, such as billing management and customer service management.
[0085] The EMS 130 is configured to perform traditional functions of fault management, configuration management, account management, performance management, and security management (FCAPS) for the VNFs 140. The EMS includes one or more EMs (e.g., EM1 and EM2 in FIG. 1A).
[0086] The VNF 140 includes one or more VNFCs. The VNF 140 may be implemented using virtual machine technology or containerization technology. If the VNF 140 is implemented using virtual machine technology, the VNFCs included in the VNF may be deployed on one or more virtual machines. If the VNF 140 is implemented using containerization technology, the VNFCs included in the VNF may be deployed on one or more containers. Instantiating a VNF may be understood as allocating or creating resources required by the VNF to implement a corresponding function. Instantiating a VNF includes creating a virtual machine or container and deploying a VNFC included in the VNF on the created virtual machine or container. In addition, instantiating a VNF further includes creating a connection point of the VNF, for example, creating an external connection point within the VNF. To more clearly explain the structure of a VNF, an example is described below with reference to a schematic diagram of the structure of a VNF shown in FIG. 1B. Referring to FIG. 1B, a VNF includes two VNFCs (VNFC1 and VNFC2 shown in FIG. 1B), an internal connection point (CP1 and CP2 shown in FIG. 1B), and an external connection point (CP3 shown in FIG. 1B). CP1 and CP2 are configured to implement communication between VNFC1 and VNFC2. CP3 is configured to implement communication between the VNF and an external node, etc. The two VNFCs in FIG. 1B may be deployed on virtual machines (not shown in FIG. 1B) or containers (not shown in FIG. 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, virtual networks, etc., as shown in FIG. 1A. The virtualization layer 152 may form a virtual network through hardware resources in the virtualization hardware resource layer. The virtual network is, for example, a virtual local area network (VLAN), a virtual extensible local area network (VXLAN), etc. The hardware resource layer 153 is configured to provide hardware resources. For example, the hardware resource layer 153 may provide hardware resources in the form of physical machines. The hardware resource layer includes computing hardware, storage hardware, network hardware, etc., as shown in FIG. 1A.
[0088] It should be understood that the network elements (NFVO, VNFM, CISM, etc.) described in Figure 1A are merely examples and are not limiting. In a standard evolution process, the names of the network elements may be changed, and the functions performed by the network elements may be further divided or combined. This is not limited in the embodiments of the present application.
[0089] Please refer to FIG. 1C. FIG. 1C is a schematic diagram of another NFV architecture to which the embodiment of the present application can be applied, or may be understood as a schematic diagram of an NFV architecture in which a container management platform is introduced. Different from FIG. 1A, the NFV architecture shown in FIG. 1C further includes a container cluster manager (CCM) 115. The CCM 115 may communicate with both the NFVO 111 and the CISM 114. The CCM 115 may cooperate with the NFVO 111 to manage the CISM 114. For the functions of the network elements other than the CCM in FIG. 1C, please refer to the contents described in FIG. 1A. The details will not be re-enumerated here.
[0090] It should be understood that the network elements (NFVO, VNFM, CISM, CCM, etc.) described in Figure 1C are merely examples and are not limiting. In a standard evolution process, the names of the network elements may be changed, and the functions performed by the network elements may be further divided or combined. This is not limited in the embodiments of the present application.
[0091] In order to support the deployment of a service in a VNF to function as an external connection point, an 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 an external name) is deployed in a VNF to be instantiated, first resource information of the first type of external connection point may be determined. The first resource information indicates resources pre-allocated for creating the first type of external connection point. Subsequently, a part or the whole 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 a load balancer and / or an external name service in a VNF to function as an external connection point. In addition, a VNF may support more types of services to function as an external connection point, and the resources required to create different types of services may be different. In this way, the number of deployed external connection points is not limited by the number of resources, so that more external connection points are created in the VNF. Thus, the VNF can meet the requirements of more services. In addition, the resources required to create different types of external connection points may be different, so that the resources for creating external connection points are enhanced.
[0092] The following describes the technical solutions provided in the embodiments of the present application with reference to the accompanying drawings.
[0093] One embodiment of the present application provides a method for deploying virtualized network functions, the method may be implemented through a communication system.
[0094] The communication system may include NFVO and CISM, or may include NFVO, VNFM, and CISM, or may include a device or chip system having the functions of NFVO and CISM, or may include a communication device or chip system having the functions of NFVO, VNFM, and CISM. In the embodiment of the present application, the implementation form of the communication system is not limited. The following uses an example to describe the structure of the communication system.
[0095] Please refer to Figure 1D. Figure 1D is a schematic diagram of the structure of a communication system according to an embodiment of the present application. The communication system includes an NFVO, a VNFM, and a CISM. The communication system may be deployed in 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] It should be noted that one NFVO, one CISM, and one VNFM are used as an example in FIG. 1D, and in practice, the number of NFVOs, CISMs, and VNFMs is not limited.
[0097] Please refer to Figure 2. Figure 2 is a flowchart of the method. In the description of the process in Figure 2, the communication system shown in Figure 1D is used as an example of the 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 to create an identifier of a VNF instance.
[0099] If a VNF is configured without resources, the VNF may be referred to as a VNF. If a VNF is configured with resources, the VNF may be referred to as an instantiated VNF or a VNF instance. Of course, if resources are configured for a VNF in the form of a container, the VNF configured with resources may be referred to as a containerized VNF. To facilitate subsequent identification of the VNF, an identifier for the VNF instance may be created during instantiation. For example, the NFVO may send a first creation 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 a VNFD in the NFVO. The service requester may be, for example, a user or an EM. The VNFD includes an identifier of the VNFD. The identifier of the VNFD indicates a VNFD corresponding to the VNF. For a description of the VNFD, see the above description. Optionally, the first creation request includes an identifier of the VNFD to facilitate the VNFM to subsequently obtain a VNFD corresponding to the VNF. It should be noted that in this embodiment of the present application, it is used as an example that the NFVO sends the identifier of the VNFD to the VNFM through the first creation request. In addition, the NFVO may further send the identifier of the VNFD to the VNFM through another message.
[0101] In this embodiment of the present application, the VNF may include only the first type of external connection point. Alternatively, the VNF may further include other types of external connection points in addition to the first type of external connection point. For example, the VNF further includes an external connection point of a node port.
[0102] Step 202: The VNFM sends an identifier of the VNF instance to the NFVO. In response, the NFVO receives an identifier of the VNF instance from the VNFM, where the identifier of the VNF instance indicates the VNF instance.
[0103] After receiving the first creation request, the VNFM may create a VNF instance identifier for the VNF. The VNFM sends the VNF instance identifier to the NFVO.
[0104] It should be noted that steps 201 to 202 describe one example of how the NFVO determines the identifier of the VNF instance. In addition, the NFVO may determine the identifier of the VNF instance in multiple ways, which is not limited in this embodiment of the present application.
[0105] Step 203: The NFVO sends an instantiation request to the VNFM. In response, the VNFM receives the instantiation request from the NFVO. The instantiation request is used to request an instance of a VNF, and the instantiation request may include an identifier of the VNF instance.
[0106] Optionally, the instantiation request further includes information about the VLD and / or information about the VDU. The information about the VLD and the information about the VDU may be determined by the NFVO, for example, by the NFVO based on the VNFD. For the meaning of the information about the VLD and the information about the VDU, please refer to the above description.
[0107] Step 204: The VNFM obtains the VNFD.
[0108] For example, as described above, the NFVO may be pre-configured with a VNFD corresponding to the VNF. The VNFM may request the VNFD from the NFVO based on an identifier of the VNFD.
[0109] For example, the VNFM may send a VNFD request to the VNFM. The VNFD request is used to request to obtain a VNFD. For example, the VNFD request includes an identifier of the VNFD. In response, the NFVO receives a VNFD request from the VNFM. The NFVO determines a VNFD corresponding to the identifier of the VNFD and sends the VNFD to the VNFM. In response, the VNFM receives a VNFD from the NFVO and obtains the VNFD. For the meaning of the VNFD, please refer to the above description.
[0110] Step 205: The VNFM determines a first resource parameter based on the VNFD.
[0111] The VNFM parses the VNFD to determine type information of the external connection point included in the VNF and resource parameters of the external connection point of the type. 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 parsing the VNFD, the VNFM correspondingly determines type information of the first type of external connection point and first resource parameters of the first type of external connection point. The type information of the external connection point may indicate a 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 an external name. The first resource parameter indicates a resource required to create the first type of external connection point. For example, the first resource parameter indicates a type of resource allocated to create the external connection point.
[0112] When the first type is different, the type information and / or specific content of the resource parameters of the first type of external connection point determined by the VNFM may be correspondingly different. The following provides an example for illustration.
[0113] 1. If the first type includes a load balancer, the VNFD includes type information of the external connection point of the load balancer and resource parameters of the external connection point of the load balancer.
[0114] The type information of the external connection point of the load balancer indicates that the type of the external connection point is a load balancer. The resource parameters of the external connection point of the load balancer include, for example, information on the address expression format of the external connection point of the load balancer. Regarding the information on the address expression format of the external connection point of the load balancer, the information on the address expression format indicates that the address of the external connection point of the load balancer is represented by an IP address of a public network address or an IP address of a private network address.
[0115] Optionally, the resource parameters of the load balancer external connection point in the VNFD further include information about a function type of the load balancer external connection point. The information about the function type indicates a type of function supported by the load balancer external connection point. The functions supported by the load balancer external connection point include, for example, a health check function and / or an auto scaling function. The health check function enables the load balancer external connection point to report exceptions of pods associated with the external connection point to the CISM. The auto scaling function enables the load balancer external connection point to scale pods associated with the external connection point. For example, the load balancer external connection point may add pods and manage the added pods, and / or the load balancer external connection point may remove pods.
[0116] Table 1 is an example of resource parameters of an external connection point of a load balancer included in a VNFD according to an embodiment of the present 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 type information of the external connection point of the load balancer in the VNF from the VNFD, where the type is service and the sub-type is load balancer. In this case, the first type includes the sub-type here. Optionally, the first type may further include the type here. The first resource parameters include that the external connection point of the load balancer is represented by a public network address, and the external connection point of the load balancer supports a health check function and an auto-scaling function.
[0119] 2. If the first type includes an external name, the VNFD includes type information of the external connection point of the external name and resource parameters of the external connection point of the external name.
[0120] The type information of the external connection point of the external name indicates that the type of the external connection point is an external name. The resource parameters of the external connection point of the external name include information about an address representation format. The information about the address representation format of the external connection point of the external name indicates that the address of the external connection point of the external connection point of the external name is represented by a name and a namespace applicable to the name. The name is unique within the same namespace. Thus, the name and the namespace can be used to uniquely identify the external connection point of the external connection point. Optionally, the resource parameters of the external connection point of the external name may further include information about a functional type of the external connection point of the external connection point of the external name. The information about the functional type of the external connection point of the external connection point of the external name indicates a type of functionality supported by the external connection point of the external connection point of the external connection point of the external name.
[0121] Table 2 is an example of resource parameters for an external connection point of an external name included in a VNFD according to an embodiment of the present application.
[0122] [Table 2]
[0123] For example, it is used as an example that the VNFD includes the resource parameters shown in Table 2. The VNFM determines type information of the external attachment point of the external name in the VNF from the VNFD, where the type is service and the sub-type is the external name. In this case, the first type includes the sub-type here. Optionally, the first type may further include the type here. The first resource parameters include that the address of the external name is represented by a name and a namespace.
[0124] 3. If the first type includes a load balancer and an external name, the VNFD includes type information of the external connection point of the load balancer, resource parameters of the external connection point of the load balancer, type information of the external connection point of the external name, and resource parameters of the external connection point of the external name.
[0125] For the type information of the load balancer external connection point, the resource parameters of the load balancer external connection point, the type information of the external name external connection point, and the resource parameters of the external name external connection point, please refer to the above description.
[0126] When the first type includes a load balancer and an external name, type information of the external connection point of the first type determined by the VNFM based on the VNFD includes type information of the external connection point of the load balancer and type information of the external connection point of the external name, and first resource parameters determined by the VNFM based on the VNFD include resource parameters of the external connection point of the load balancer and resource parameters of the external connection point of the external name.
[0127] In one example, the VNFM may determine from the VNFD further resource information required to instantiate the VNF, where the further resource information indicates further resources. The further resources are resources other than the resources indicated by the first resource parameter in the resources required to instantiate the VNF. For further resource information, e.g., information regarding the VDU and / or information regarding the VLD corresponding to the VNF, see the above description of the meaning of the information regarding the VDU and the information regarding the VLD.
[0128] It should be noted that step 204 uses an example in which the VNFM determines the first resource parameter based on the VNFD. In addition, the VNFM may determine the first resource parameter in multiple ways, which is not limited in this embodiment of the present application. For example, the VNFM may be pre-configured with the first resource parameter corresponding to the VNF, and there is no need to determine the first resource parameter 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 a first resource parameter.
[0130] To instantiate a VNF, a large amount of resources (e.g., resources indicated by the first resource parameter) may be required. A part of the resources may need to be granted by the NFVO. For example, the resources indicated by the first resource parameter need to be granted by the NFVO. In this embodiment of the present application, it is used as an example that the resources indicated by the first resource parameter need to be granted by the NFVO. The resources indicated by the first resource parameter need to be granted by the NFVO. As a result, the VNFM may request from the NFVO to grant the resources indicated by the first resource parameter. For example, the resource grant request may request the NFVO to grant the resources indicated by the first resource parameter. The NFVO may determine the resources indicated by the first resource parameter that the VNFM requests to grant, for example, referred to as the first resource, based on the first resource parameter included in the resource grant request.
[0131] For example, the NFVO determines a first resource to be pre-allocated to the first type of external attachment point based on the first resource parameter.
[0132] Optionally, the resource authorization request may further include type information of the first type of external attachment point. The NFVO may determine that the first type of external attachment point needs to be deployed for instantiation of the VNF based on the type information of the first type of external attachment point. In this case, the NFVO directly determines from the VNFM that the VNF includes the first type of external attachment point, thereby reducing the amount of processing by the NFVO.
[0133] Alternatively, since the resource parameters corresponding to different types of external attachment points are different, the NFVO may determine that the first type of external attachment point needs to be deployed for instantiation of the VNF based on the first resource parameter and the pre-stored resource parameters corresponding to the different types of external attachment points. In this case, the NFVO may not need to receive type information of the first type of external attachment point from the VNFM. Thus, the amount of data transmitted between the VNFM and the NFVO can be relatively reduced.
[0134] In this embodiment of the present application, the first resource parameter is carried in the resource grant request is used as an example. In addition, the VNFM may send the first resource parameter to the NFVO through another message. This is not limited in this embodiment of the present application.
[0135] In steps 204 to 206, it is used as an example that the NFVO receives the first resource parameter from the VNFM. In another example, the NFVO may determine the first resource parameter by itself, and the VNFM does not need to send the first resource parameter. In this case, steps 204 to 206 do not need to be performed. For example, the NFVO may determine the first resource parameter from the VNFD. For how to determine the first resource parameter by the NFVO, please refer to the process of determining the first resource parameter by the VNFM. Details are not enumerated again here. In addition, other resource information may also be determined by the NFVO. For the meaning of the other resource information, please refer to the above description.
[0136] Step 207: The NFVO determines first resource information based on the first resource parameter, where the resource indicated by the first resource information is used to create a first type external attachment point.
[0137] For example, the NFVO manages resource pool information. The resource pool information includes resource information required to create each type of external connection point in one or more types of external connection points. For example, the resource pool information includes resource information required to create an external connection point of a load balancer, resource information required to create an external connection point of an external name, etc. The NFVO may determine one or more resource information that satisfies a first resource parameter from the resource pool information, and each resource information in the one or more resource information indicates a resource that is required to create one external connection point of the first type. In this case, the first resource information may include one or more resource information. Alternatively, the NFVO may select resource information that satisfies a use condition as the first resource information from the one or more resource information. The use condition is, for example, resource information that has not yet been used.
[0138] Alternatively, the NFVO does not need to determine the first resource information by itself, but may receive the first resource information from another network element. In this case, step 207 may be replaced by another network element sending the first resource information to the NFVO, and the NFVO receiving the first resource information from the other network element in response. The other network element is, for example, a network element other than the NFVO in FIG. 1A or FIG. 1B, specifically, for example, a VIM. For a method of determining the first resource information by another network element, please refer to the method of determining the first resource information by the NFVO.
[0139] Of course, in steps 204 to 207, it is used as an example that the NFVO determines the first resource information based on the first resource parameter. In addition to the above-mentioned method, the NFVO may further determine the first resource information in other ways, which is not limited in this embodiment of the present application. For example, after determining that the VNF includes a first type of external attachment point, the NFVO may determine the first resource information required to create the first type of external attachment point from the management resource pool information.
[0140] In one example, a VNF may include a plurality of external attachment points of a first type. In this embodiment of the present application, the first resource information determined by the NFVO may, for example, indicate pre-allocated resources for the plurality of external attachment points of the first type.
[0141] When the first type is different, the first resource information may also be different. In the following, an example is used for explanation.
[0142] (1) When the first type includes a load balancer, the first resource information includes address information of an external connection point of the load balancer.
[0143] The information about the address of the external connection point of the load balancer indicates the address and address type of the external connection point of the load balancer, for example, an IP address and an IP address type. The IP address type may indicate whether the IP address is a public network or a private network address.
[0144] Optionally, the first resource information further includes information about functions supported by the external connection point of the load balancer. The information about functions supported by the external connection point of the load balancer indicates functions supported by the external connection point of the load balancer.
[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). The types of Serv1 and Serv2 are both load balancers. Therefore, the NFVO may determine to pre-allocate the first resource information shown in Table 1 to both Serv1 and Serv2.
[0148] (2) When the first type includes an external name, the first resource information includes address information of an external connection point of the external name. The information about 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 includes a 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) When the first type includes a load balancer and an external name, the first resource information includes the first resource information of the external connection point of the load balancer and the first resource information of the external connection point of the external name. For the first resource information of the two types, please refer to the above description.
[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] The NFV architecture may include one or more CISMs. If there are multiple CISMs, the NFVO may determine a first CISM from the multiple CISMs and send the first resource information to the first CISM. For example, the NFVO randomly selects a CISM from the multiple CISMs as the first CISM, or selects a CISM with the lightest load from the multiple CISMs as the first CISM. If the NFV architecture includes only one CISM, the NFVO directly uses the CISM as the first CISM.
[0155] In this case, the first CISM does not need to temporarily create the first type 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 receipt response to the NFVO. In response, the NFVO receives a successful receipt response from the first CISM.
[0157] The successful receipt response indicates that the first CISM successfully received the first resource information.
[0158] Optionally, the successful receipt response further includes connection information of the first CISM. The connection information of the first CISM, for example, includes address information of the first CISM. The address information of the first CISM may indicate an address of the first CISM, for example, an IP address of the first CISM. Optionally, the connection information of the first CISM further includes a uniform resource identifier (URL) of the first CISM, etc.
[0159] When the NFV architecture includes only one CISM, the VNFM does not need to create a first type external connection point from a specific CISM among the multiple CISMs later. Therefore, the successful receipt 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 successful receipt response includes the connection information of the first CISM.
[0160] It should be noted that in this embodiment of the present application, the successful receipt response carries the connection information of the first CISM as an example. In addition, the first CISM may further send the connection information of the first CISM to the NFVO through another message. This is not limited in this embodiment of the present application.
[0161] In this embodiment of the present application, the successful receipt response carries the connection information of the CISM as an example. In addition, the first CISM may further send the connection information of the CISM to the NFVO through another message. This is not limited in 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 the connection information of the first CISM.
[0163] If the successful receipt response in step 209 includes the connection information of the first CISM, the resource authorization response in step 210 also includes the connection information of the first CISM. If the successful receipt response in step 209 does not include the connection information of the first CISM, the resource authorization response in step 210 also does not include the connection information of the CISM.
[0164] In this embodiment of the present application, the resource authorization response carries the connection information of the CISM as an example. In addition, the NFVO may further send the connection information of the first CISM to the VNFM through another message. This is not limited in this embodiment of the present application.
[0165] The first resource information may indicate one or more resources. However, it may be uncertain which resources of the one or more resources are specifically used by the first type of external attachment point to create the VNF. Therefore, optionally, the NFVO may further determine second resource information. The second resource information may indicate resources used by the VNFM to create the first type of external attachment point of 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, in this embodiment of the application, an example is used in which the second resource information is sent through a resource authorization response.In practice, the NFVO sends the second resource information to the VNFM in multiple ways, which is not limited in this application.
[0167] Optionally, the NFVO may further mark the state of the resource indicated by the second resource information, for example, the NFVO marks the state of the resource indicated by the second resource information as used, so that the NFVO later determines which resource indicated by the first resource information is used based on the state.
[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 to create a first type of external connection point.
[0169] If the NFV architecture includes one CISM, the VNFM may directly use this CISM as the first CISM and send the resource creation request to the first CISM. Alternatively, if the NFV architecture includes multiple CISMs, the VNFM may determine the first CISM to be used to create the first type of external connection point from the multiple CISMs based on the address information of the first CISM.
[0170] When the VNFM receives the second resource information from the NFVO, optionally, the VNFM may carry the second resource information in the resource creation request to indicate, through the second resource information, the resources needed to create the first type of external attachment point.
[0171] Optionally, the resource creation request may further indicate to create a container required to instantiate the VNF. In one implementation, the VNFM may determine the resource information required by the created container based on the other resource information, and convey the resource information required by the created container in the resource creation request. For the meaning of the other resource information, see the above description.
[0172] Alternatively, the resource creation request may not need to indicate to create a container required to instantiate the VNF. The VNFM may send the 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 a container required to instantiate the VNF. Optionally, the container creation request includes resource information required by the created container. If the VNFM further sends the container creation request to the first CISM, the VNFM may first send the resource creation request and then send the container creation request. Alternatively, the VNFM may first send the container creation request and then send the resource creation request. Alternatively, the VNFM may send the two messages simultaneously.
[0173] Step 212: The first CISM creates a container.
[0174] The first CISM may determine a 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 on a physical machine or a virtual machine in the NFVI. Optionally, the first CISM may further deploy a VNFC in the container to instantiate the VNF. For example, the first CISM includes a first application programming interface configured to create a container. The CISM may call the first application programming interface (API) to create a container based on a resource indicated by the other resource information. For example, the CISM may call the first application programming interface to access a physical machine or a virtual machine in the NFVI based on the other resource information to deploy a container on the physical machine or a 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, where 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 external connection point, and allocates a part or all of the resources indicated by the first resource information to the first type external connection point.
[0177] If the first CISM deploys the container on a physical machine, the first CISM may also deploy a first type external connection point on the physical machine and assign some or all of the resources indicated by the first resource information to the first type external connection point. If the CISM deploys the container on a virtual machine, the first CISM may alternatively deploy a first type external connection point on the virtual machine and assign some or all of the resources indicated by the first resource information to the first type 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 invoke the second application programming interface to create the first type of external connection point. For example, the first CISM may invoke the second application programming interface to access a physical or virtual machine in the NFVI to deploy the first type of external connection point on the 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 may be a different application programming interface.
[0179] Continuing to use FIG. 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 assigns the IP address 10.70.36.37 to Serv2.
[0180] If the resource creation request does not include the second resource information, the first CISM may allocate a part or all of the resources indicated by the first resource information to the first type of external connection point. For example, the first CISM may randomly select a part of the resources from the entire resources indicated by the first resource information and allocate the resources to the first type of external connection point.
[0181] Alternatively, if the resource creation request includes second resource information, the first CISM may allocate the entirety of the resource indicated by the second resource information to the first type of external connection point.
[0182] Meanwhile, theoretically, the NFVO determines, for the VNF, second resource information indicating a subset of resources indicated by the first resource information. However, it is difficult to guarantee that no error occurs in the process in which the VNFM forwards the second resource information. For example, the VNFM confuses the second resource information of the VNF with the second resource information of other VNFs. Meanwhile, 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, optionally, the first CISM may verify the resources indicated by the second resource information 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 to determine whether the resources indicated by the second resource information are correct. The first CISM determines whether the resource indicated by the second resource information is a subset of the resource indicated by the first resource information. The result of the determination may include several types:
[0183] A first type of the result of the determination 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 determination indicates that the entirety of the resources indicated by the second resource information is correct, and the first CISM may allocate the resources indicated by the second resource information to the first type of external connection point.
[0185] For example, 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, and 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, the first CISM determines that the resource indicated by the second resource information is correct.
[0186] A second type of decision result is that a part of the resources indicated by the second resource information is a subset of the resources indicated by the first resource information, and another part 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 determination may indicate that the portion of the resources indicated by the second resource information is correct, and the first CISM may allocate the correct resources indicated by the second resource information to the first type of external connection point. Alternatively, the first CISM may directly allocate the portion of the resources indicated by the first resource information to the first type of external connection point without considering the second resource information.
[0188] The third type of the result of the decision is that none of the resources indicated by the second resource information is included in the resources indicated by the first resource information, or 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 of determination indicates that none of the resources indicated by the second resource information are correct. The first CISM may allocate a portion of the resources indicated by the first resource information to the first type of 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 of external connection point has failed. In this case, steps 201 to 213 may be repeated to create the first type of 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 external attachment point is successfully created, the first CISM may create a successful creation response and send the successful creation response to the VNFM. For example, the successful creation response may include an identifier of the VNF instance.
[0192] Optionally, the first CISM may send information about the created first type external connection point and an identifier of the VNF instance to the OSS. The first CISM may actively send information about the first type external connection point and an 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 request information about the first type external connection point and an identifier of the VNF instance corresponding to the first type external connection point from the first CISM periodically or irregularly. The information about the first type external connection point includes, for example, address information of the first type external connection point. For example, continue to use FIG. 3 as an example. The first CISM may send an 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] The OSS publishes information about the first type of external connection point and an identifier of a VNF instance corresponding to the first type of external connection point to an external node, such that the external node accesses the VNF based on the 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 has been successfully instantiated.
[0195] If the VNFM indicates that the first type of external attachment point was successfully created, the container was successfully deployed, etc., the VNFM may generate an instantiation success response. For example, the instantiation success response carries an identifier of the VNF instance. After receiving the instantiation success response, the NFVO determines that the VNF was successfully instantiated.
[0196] Steps 201 to 206, 209 to 210, 212, and 214 to 215 are optional steps, which are indicated by dashed lines in FIG.
[0197] In this embodiment of the present application, the VNFM may determine whether the VNF currently to be instantiated includes a first resource parameter of a first type of external attachment point. Since the NFVO does not need to determine the first resource parameter, the amount of processing by the NFVO is relatively reduced. The NFVO receives the first resource parameter from the VNFM, determines first resource information of the first type of external attachment point based on the first resource parameter, and sends the first resource information to the CISM. The CISM may allocate a part or the whole of the resources indicated by the first resource information to the first type of external attachment point. A mechanism is provided to create a load balancer and / or an external name as an external attachment point. In addition, more types of external attachment points can be deployed within a VNF, thereby expanding the service scope to which the VNF can be applied. In addition, since the resources required to create different types of external attachment points are different, different resources may be used to create different types of external attachment points, thereby improving the flexibility to deploy external attachment points within a VNF.
[0198] In the following, the method will be described using an example with reference to the flowchart of the method for deploying virtualized network functions shown in Fig. 4. In the description of the process in Fig. 4, the communication system shown in Fig. 1D is used as an example of the communication system, and the communication system is deployed in the NFV architecture shown in Fig. 1A.
[0199] Step 401: The NFVO sends a first creation request to the VNFM. In response, the VNFM receives a first creation request from the NFVO. For the content of the first creation request, please refer to the above description.
[0200] Step 402: The VNFM sends an identifier of the VNF instance to the NFVO. In response, the NFVO receives an identifier of the VNF instance from the VNFM. For the content of the identifier of the VNF instance, see the above description.
[0201] Step 403: The NFVO sends an instantiation request to the VNFM. In response, the VNFM receives an instantiation request from the NFVO. For the content of the instantiation request, please refer to the above description.
[0202] Step 404: The NFVO determines a first resource parameter.
[0203] The NFVO may determine the first resource parameter based on a preconfigured VNFD, or the NFVO may be preconfigured with the first resource parameter. For the method of determining the first resource parameter by the NFVO based on the VNFD, the meaning of the VNFD, and the content of the first resource parameter, please refer to the above description.
[0204] Step 405: The NFVO determines first resource information based on the first resource parameter.
[0205] For the method of determining the first resource parameter by the NFVO and the meaning of the first resource information, please refer to the above description.
[0206] It should be noted that in this embodiment of the present application, the NFVO determines the first resource information based on the first resource parameter as an example. However, the NFVO may determine the first resource information without using the first resource parameter. This is not limited in this embodiment of the present application.
[0207] Step 406: The NFVO sends the first resource information to the first CISM through the CCM. In response, the first CISM receives the first resource information from the NFVO through the CMM. For the meaning of the first resource information, please refer to the above description.
[0208] Specifically, step 406 includes step 406a and step 406b. Step 406a: The NFVO sends the first resource information to the CCM. In response, the CCM receives the first resource information from the NFVO. Step 406b: The CCM sends the first resource information to the first CISM. In response, the first CISM receives the first resource information from the CCM.
[0209] For the method of determining the first CISM by the NFVO, please refer to the above description.
[0210] It should be noted that in this embodiment of the present application, the NFVO sends the first resource information to the first CISM through the CCM as an example. In addition, the NFVO sends the first resource information to the first CISM in multiple ways, which is not limited in this embodiment of the present application.
[0211] Step 407: The first CISM sends a successful receipt response to the NFVO through the CCM. In response, the NFVO receives a successful receipt response from the first CISM through the CCM.
[0212] Specifically, step 407 includes step 407a and step 407b. Step 407a: The first CISM sends a successful reception response to the CCM. In response, the CCM receives the successful reception response from the first CISM. Step 407b: The CCM sends a successful reception response to the NFVO. In response, the NFVO receives the successful reception response from the CCM.
[0213] Optionally, the successful receipt response includes the connection information of the first CISM. For the meaning of the successful receipt response and the connection information of the first CISM, please refer to the above description.
[0214] It should be noted that in this embodiment of the present application, the first CISM sends a successful reception response to the NFVO through the CCM as an example. In addition, the first CISM sends a successful reception response to the NFVO through the CCM in multiple ways, which is not limited in this embodiment of the present application.
[0215] Step 408: The NFVO determines second resource information.
[0216] For the meaning of the second resource information and the method for determining the second resource information, please refer to the above description.
[0217] Step 409: The VNFM sends a resource authorization request to the NFVO. In response, the NFVO receives a resource authorization request from the VNFM.
[0218] For the meaning of resource authorization requests, see the above explanation.
[0219] Optionally, the NFVO may first determine the second resource information, and then the VNFM sends a resource authorization request to the NFVO. Alternatively, the VNFM may first send a resource authorization request, and then the NFVO determines the second resource information. Alternatively, the NFVO determines the second resource information while the VNFM sends a resource authorization request to the NFVO.
[0220] Step 410: The NFVO sends a resource authorization response to the VNFM. In response, the VNFM receives a resource authorization response from the NFVO.
[0221] Optionally, the resource authorization response includes the connection information of the first CISM and / or the second resource information. For the meaning of the second resource information and the connection information of the first CISM, please refer to the above description.
[0222] Step 411: The VNFM sends a resource creation request to the first CISM. In response, the first CISM receives a resource creation request from the VNFM.
[0223] For the meaning of the resource creation request, please refer to the contents shown in Figure 2.
[0224] Optionally, the resource creation request includes second resource information. In this embodiment of the present application, an example in which the resource creation request includes the second resource information is used.
[0225] Step 412: The first CISM creates a container.
[0226] See above for information on how CISM creates containers.
[0227] Step 413: The first CISM creates a first type external connection point, and allocates a part or all of the resources indicated by the first resource information to the first type 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 about the verification method and possible verification results, please refer to the above description.
[0229] Optionally, the first CISM may send information about the created first type external connection point and an identifier of the VNF instance to the OSS. For how the first CISM sends information to the OSS, see the above description. The OSS publishes information about the first type external connection point and an identifier of the VNF instance corresponding to the first type external connection point to an external node, so that the external node accesses the VNF based on the information about the first type 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 the meaning of a successful creation response, see the explanation above.
[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, see the above description.
[0233] In one example, steps 401 to 404, steps 407 to 410, step 412, and steps 414 to 415 are optional steps. These optional steps are indicated by dashed lines in FIG.
[0234] In this embodiment of the present application, the NFVO determines first resource information of a first type of external attachment point and sends the first resource information to the CISM. The CISM may allocate a part or the whole of the resources indicated by the first resource information to the first type of external attachment point. A mechanism is provided for deploying a load balancer and / or an externally named service in the VNF to function as an external attachment point. In addition, the service range that may be supported by different types of external attachment points may be different, and the VNF may support the deployment of more types of external attachment points. Thus, the service range supported by the VNF can be expanded. In addition, the NFVO may determine the first resource parameter by itself to determine the first resource information based on the first resource parameter. The VNFM does not need to determine the first resource parameter, thereby reducing the amount of processing by the VNFM. In addition, the interaction between the VNFM and the NFVO is reduced compared to the VNFM not needing to send the first resource parameter to the NFVO.
[0235] Based on the same inventive concept, an embodiment of the present application further provides a communication device. Figure 5 is a schematic diagram of the structure of a communication device according to an embodiment of the present application. The communication device shown in Figure 5 may be configured to implement the function of the first network element in the above-mentioned method embodiment, and thus can also achieve the beneficial effects of the above-mentioned method embodiment. In this embodiment of the present application, the communication device shown in Figure 5 may be a chip system with CISM function.
[0236] As shown in FIG. 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 the CISM in the method embodiment shown in Figure 2 or Figure 4. For specific functions, please refer to the description of the above method embodiment. For example, the communication device may be configured to implement the functions of the CISM in the method embodiment shown in Figure 2 or Figure 4.
[0238] Based on the same inventive concept, an embodiment of the present application further provides a communication device. Figure 6 is a schematic diagram of the structure of a communication device according to an embodiment of the present application. The communication device shown in Figure 6 may be configured to implement the function of the first network element in the above-mentioned method embodiment, and thus can also achieve the beneficial effects of the above-mentioned method embodiment. In this embodiment of the present application, the communication device shown in Figure 6 may be a chip system with NFVO function.
[0239] As shown in FIG. 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 functionality of the NFVO in the method embodiment shown in Figure 2 or Figure 4. For specific functions, please refer to the description of the above method embodiment. For example, the communication device may be configured to implement the functionality of the NFVO in the method embodiment shown in Figure 2 or Figure 4.
[0241] Based on the same inventive concept, an embodiment of the present application further provides a communication device. Figure 7 is a schematic diagram of the structure of a communication device according to an embodiment of the present application. The communication device shown in Figure 7 may be configured to implement the function of the first network element in the above-mentioned method embodiment, and thus can also achieve the beneficial effects of the above-mentioned method embodiment. In this embodiment of the present application, the communication device shown in Figure 7 may be a chip system with the function of a container as a service manager.
[0242] As shown in Fig. 7, the communication device includes a transceiver module 701. Optionally, the communication device further includes a processing module 702. In Fig. 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 functions of the VNFM 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 functions of the VNFM in the method embodiment shown in Figure 2.
[0244] Based on the same inventive concept, an embodiment of the present application further provides a communication device. Figure 8 is a schematic diagram of the structure of a communication device according to an embodiment of the present application. The communication device shown in Figure 8 may be configured to implement the function of the VNFM in the above-mentioned method embodiment, and thus can also achieve the beneficial effects of the above-mentioned method embodiment. In this embodiment of the present application, the communication device shown in Figure 8 may be a chip system with VNFM function.
[0245] As shown in Fig. 8, the communication device includes a transceiver module 801. Optionally, the communication device further includes a processing module 802. In Fig. 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 functions of the VNFM 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 functions of the VNFM in the method embodiment shown in Figure 4.
[0247] Based on the same inventive concept, an embodiment of the present application further provides a communication device. Figure 9 is a schematic diagram of the structure of a communication device according to an embodiment of the present application. The communication device shown in Figure 9 may be configured to implement the function of the first network element in the above-mentioned method embodiment, and thus can also achieve the beneficial effects of the above-mentioned method embodiment.
[0248] 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. The processors 901 may also be referred to as processing units and may implement certain control functions. The processors 901 may be general-purpose processors or special-purpose processors, including, for example, baseband processors, central processing units, etc. The baseband processors may be configured to process communication protocols and communication data. The central processing units may be configured to control the communication device, execute software programs, and / or process data. The different processors may be separate components or may be located in one or more processing circuits, for example integrated in one or more application specific integrated circuits.
[0250] Optionally, the communication device includes one or more memories 903 configured to store instructions. The instructions may be executed on a processor such that the communication device performs the methods described in the preceding method embodiments. The memory 903 in the communication device is an optional component and is illustrated in FIG. 9 using a dashed box.
[0251] Optionally, the memory 903 may further store data. The processor and the memory may be located separately or integrated together.
[0252] Optionally, the communication device may further include a memory 903 configured to store instructions to be executed by the processor 901, or to store input data required by the processor 901 to execute the instructions, or to store data generated after the processor 901 executes the instructions.
[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 the CISM in the method embodiment shown in Figure 2 or Figure 4. For specific functions, please refer to the description of the above method embodiment. 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 function of the NFVO in the method embodiment shown in Figure 2 or Figure 4. For specific functions, please refer to the description of the above method embodiment. In this case, the communication device may further implement the function 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 Fig. 2, the communication device may be configured to implement the functions of the VNFM in the method embodiment shown in Fig. 2. For specific functions, please refer to the description of the above method embodiment. In this case, the communication device may further implement the functions of the communication device shown in Fig. 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 functions of the VNFM in the method embodiment shown in Figure 4. For specific functions, please refer to the description of the above method embodiment. 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, an embodiment of the present application further provides a communication system, which may include the communication device shown in FIG. 5, the communication device shown in FIG. 6, and the communication device shown in FIG.
[0258] Based on the same inventive concept, an embodiment of the present application further provides a communication system, which may include the communication device shown in FIG. 5, the communication device shown in FIG. 6, and the communication device shown in FIG.
[0259] Based on the same inventive concept, an embodiment of the present application provides a computer-readable storage medium, which is configured to store a computer program, which, when executed on a computer, enables the computer to perform the method according to any one of FIG. 2 or FIG. 4.
[0260] Those skilled in the art should understand that the embodiments of the present application may be provided as a method, a system, or a computer program product. Thus, the present application may use the form of a hardware-only embodiment, a software-only embodiment, or an embodiment having a combination of software and hardware. In addition, the present application may use the form of a computer program product embodied on one or more computer usable storage media (including, but not limited to, disk memory, CD-ROM, optical memory, etc.) that contains computer usable program code.
[0261] The present application is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the present application. It should be understood that computer program instructions can be used to implement each procedure and / or each block in the flowcharts and / or block diagrams, and combinations of procedures and / or blocks in the flowcharts and / or block diagrams. These computer program instructions can be provided to a general-purpose computer, a special-purpose computer, an embedded processor, or a processor of another programmable data processing device to generate a machine such that the procedures executed by the processor of the computer or another programmable data processing device generate an apparatus for implementing a particular function in one or more instructions in the flowcharts and / or one or more blocks in the block diagrams.
[0262] These computer program instructions may alternatively be stored in a computer readable memory capable of instructing a computer or another programmable data processing device to operate in a particular manner to generate an artifact comprising an instruction apparatus, the instruction apparatus implementing a particular function of one or more steps of the flowcharts and / or one or more blocks of the block diagrams.
[0263] These computer program instructions may be loaded onto a computer or another programmable data processing device such that a sequence of operational steps are executed on the computer or another programmable device, thereby producing a computer or another programmable device. Thus, the instructions executed on the computer or another programmable device provide steps for implementing a particular function in one or more procedures of the flowcharts and / or one or more blocks of the block diagrams.
[0264] It is obvious that a person skilled in the art can make various modifications and variations to the present application without departing from the spirit and scope of the present application. The present application is intended to cover these modifications and variations of the present application, provided that they fall within the scope of protection defined by the appended claims and their equivalent technologies. [Explanation of symbols]
[0265] 110 NFV Management and Orchestration System, NFV MANO 111 NFVO 112 Virtualized Network Function Manager, VNFM 113 Virtualization Infrastructure Manager, VIM 114 CISM 120 Operational Support Systems / Business Support Systems, 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 Module 901 Processor 902 Interface 903 Memory
Claims
1. 1. A method for deploying virtualized network functions, comprising: determining first resource information, the first resource information indicating pre-allocated resources for an external attachment point of a first type, the external attachment point being an entrance for accessing the virtualized network function VNF by an external node, the first type being a load balancer and / or an external name; sending the first resource information to a container infrastructure service management CISM, where the resource indicated by the first resource information is used to create the external connection point of the first type; The method includes:
2. The method of claim 1 , wherein the first resource information includes information regarding addresses assigned by the external attachment points of the first type.
3. The method of claim 2 , wherein the first resource information further comprises information regarding functions supported by the external attachment point of the first type.
4. said step of determining first resource information further comprising: sending an instantiation request to a Virtualized Network Function Manager VNFM, the instantiation request being used to request the VNF to be instantiated; receiving a resource grant request from the VNFM, the resource grant request including a first resource parameter, the first resource parameter being used to determine the first resource information; determining the first resource information based on the first resource parameter; The method according to any one of claims 1 to 3, comprising:
5. said step of determining first resource information further comprising: determining first resource parameters from a virtualized network function descriptor VNFD corresponding to the VNF, the first resource parameters being used to determine the first resource information, the VNFD including type information of the external attachment points of the VNF and resource parameters corresponding to each type of external attachment point; determining the first resource information based on the first resource parameter; The method according to any one of claims 1 to 3, comprising:
6. The method further comprising: sending second resource information to the VNFM, where 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 the external attachment point of the first type; 6. The method of claim 1, further comprising:
7. The method further comprising: receiving address information of the CISM from the CISM through a container cluster manager CCM or receiving address information of the CISM from the CISM; sending the address information of the CISM to the VNFM, the address information of the CISM indicating the CISM that creates the external connection point of the first type; 7. The method of claim 1, further comprising:
8. 1. A method for deploying virtualized network functions, comprising: receiving an instantiation request from a network function virtualization orchestrator NFVO, the instantiation request being used to request a virtualized network function VNF to be instantiated; 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 resources pre-allocated to a first type of external attachment point, the external attachment point being an entry point for accessing the virtualized network function VNF by an external node; The method includes:
9. The method further comprising: determining the first resource parameters from a VNFD corresponding to the VNF, the first resource parameters being used to determine the first resource information, the VNFD including type information of the external attachment points of the VNF and resource parameters corresponding to each type of external attachment point; 9. The method of claim 8, further comprising:
10. The method further comprising: receiving second resource information from the network function virtualization orchestrator NFVO, the second resource information indicating the resources pre-allocated to the external attachment points of the first type, the external attachment points being the entry points for accessing the virtualized network function VNF by the external nodes, the first type being a load balancer and / or an external name; sending the second resource information to a container infrastructure service management CISM, where the resource indicated by the second resource information is used to create the external connection point of the first type; 10. The method of claim 8 or 9, comprising:
11. 1. A method for deploying virtualized network functions, comprising: receiving first resource information, the first resource information indicating pre-allocated resources for an external attachment point of a first type, the external attachment point being an entrance for accessing the virtualized network function VNF by an external node, the first type including a load balancer and / or an external name; creating the external connection point of the first type and allocating a part or all of the resources indicated by the first resource information to the external connection point of the first type; A method comprising:
12. the step of creating a first type external connection point and allocating a part or all of the resources indicated by the first resource information to the first type external connection point; receiving a resource creation request from a virtualized network function manager VNFM, the resource creation request being used to request to create the external attachment point of the first type, the resource creation request including second resource information; creating the external connection point of the first type if the resources indicated by the second resource information are a subset of the resources indicated by the first resource information, and assigning the resources indicated by the second resource information to the external connection point of the first type; 12. The method of claim 11, comprising:
13. The method further comprising: Sending address information of a container infrastructure service management CISM to a network function virtualization orchestrator NFVO through a container cluster manager CCM, or sending address information of the CISM to the NFVO, where the address information of the CISM indicates the CISM that creates the external connection point of the first type.
13. The method of claim 11 or 12, further comprising:
14. 1. A method for deploying virtualized network functions, comprising: receiving, by a virtualized network function manager VNFM, an instantiation request from a network function virtualization orchestrator NFVO, the instantiation request being used to request that the VNF be instantiated; sending, by the VNFM, 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 resources pre-allocated to a first type of external attachment point, the external attachment point being an entry point for accessing the virtualized network function VNF by an external node; determining, by the NFVO, the first resource information, the first resource information indicating the resources pre-allocated to the external attachment point of the first type, the external attachment point being the ingress for accessing the virtualized network function VNF by the external node, the first type being a load balancer and / or an external name; sending, by the NFVO, the first resource information to a container infrastructure service management CISM, where the resources indicated by the first resource information are used to create the external attachment point of the first type; creating, by the CISM, the external connection point of the first type, and allocating a part or all of the resources indicated by the first resource information to the external connection point of the first type; The method includes:
15. a processing module configured to determine first resource information, the first resource information indicating pre-allocated resources for an external attachment point of a first type, the external attachment point being an entrance for accessing a virtualized network function VNF by an external node, the first type being a load balancer and / or an external name; a transceiver module configured to transmit the first resource information to a CISM, the resources indicated by the first resource information being used to create the external connection point of the first type; and A communication device comprising:
16. 16. The apparatus of claim 15, wherein the first resource information includes information regarding addresses assigned by the external attachment points of the first type.
17. The apparatus of claim 16 , wherein the first resource information further comprises information regarding capabilities supported by the external attachment point of the first type.
18. The processing module comprises: Sending an instantiation request to a Virtualized Network Function Manager (VNFM), the instantiation request being used to request the VNF to be instantiated; receiving a resource grant request from the VNFM, the resource grant request including a first resource parameter, the first resource parameter being used to determine the first resource information; determining the first resource information based on the first resource parameter; 18. Apparatus according to any one of claims 15 to 17, specifically adapted for:
19. The processing module comprises: Determine first resource parameters from a virtualized network function descriptor VNFD corresponding to the VNF, the first resource parameters being used to determine the first resource information, the VNFD including type information of the external attachment points of the VNF and resource parameters corresponding to each type of external attachment point; determining the first resource information based on the first resource parameter; 18. Apparatus according to any one of claims 15 to 17, specifically adapted for:
20. The transceiver module includes: sending second resource information to the VNFM, the resources indicated by the second resource information being a subset of the resources indicated by the first resource information, the resources indicated by the second resource information being used to create the external attachment point of the first type; 19. Apparatus according to any one of claims 15 to 18, specifically adapted for:
21. The transceiver module includes: receiving address information of the CISM from the container infrastructure service management CISM through a container cluster manager CCM or receiving address information of the CISM from the CISM; Sending the address information of the CISM to the VNFM, the address information of the CISM indicating the CISM that creates the external connection point of the first type; 21. Apparatus according to any one of claims 15 to 20, specifically adapted for:
22. a transceiver module configured to receive an instantiation request from a network function virtualization orchestrator NFVO, the instantiation request being used to request a virtualized network function VNF to be instantiated, and to send 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 resources pre-allocated to a first type of external attachment point, the external attachment point being an entrance for accessing the virtualized network function VNF by an external node. A communication device comprising:
23. The apparatus, Determine the first resource parameters from a VNFD corresponding to the VNF, and the first resource parameters are used to determine the first resource information, the VNFD including type information of the external attachment points of the VNF and resource parameters corresponding to each type of external attachment point; The apparatus of claim 22 , further comprising a processing module configured to:
24. The transceiver module includes: receiving second resource information from the network function virtualization orchestrator NFVO, the second resource information indicating the resources pre-allocated to the external attachment point of the first type, the external attachment point being the ingress for accessing the virtualized network function VNF by the external node, the first type being a load balancer and / or an external name; Sending the second resource information to a container infrastructure service management CISM, wherein the resource indicated by the second resource information is used to create the external connection point of the first type.
24. The apparatus of claim 22 or 23, further configured to:
25. a transceiver module configured to receive first resource information, the first resource information indicating pre-allocated resources for an external attachment point of a first type, the external attachment point being an entrance for accessing a virtualized network function VNF by an external node, the first type including a load balancer and / or an external name; a processing module configured to create the external connection point of the first type and to allocate some or all of the resources indicated by the first resource information to the external connection point of the first type; A communication device comprising:
26. The processing module comprises: receiving a resource creation request from a virtualized network function manager VNFM, the resource creation request being used to request to create the external attachment point of the first type, the resource creation request including second resource information; if the resources indicated by the second resource information are a subset of the resources indicated by the first resource information, creating the external connection point of the first type and assigning the resources indicated by the second resource information to the external connection point of the first type; 26. The device according to claim 25, specifically adapted for:
27. The processing module comprises: Send address information of a container infrastructure service management CISM to a network function virtualization orchestrator NFVO through a container cluster manager CCM, or send address information of the CISM to the NFVO, where the address information of the CISM indicates the CISM that creates the first type of the external connection point; 27. Apparatus according to claim 25 or 26, specifically adapted for:
28. A communication system comprising a communication device according to any one of claims 15 to 21, a device according to any one of claims 25 to 27 and a device according to any one of claims 22 to 24.
29. A communications device comprising a processor and a memory, the memory configured to store one or more computer programs, the one or more computer programs comprising computer executable instructions, and wherein, when the communications device is operated, the processor executes the one or more computer programs stored in the memory to enable the communications device to perform a method according to any one of claims 1 to 7, claims 8 to 10, claims 11 to 13 or claim 14.
30. A chip system comprising a processor and an interface, the processor configured to call instructions from the interface and execute the instructions, and when the processor executes the instructions, a method according to any one of claims 1 to 7, claims 8 to 10, or claims 11 to 13 is performed.
31. 15. A computer readable storage medium configured to store a computer program which, when executed on a computer, enables the computer to perform a method according to any one of claims 1 to 7, claims 8 to 10, claims 11 to 13, or claim 14.
Citation Information
Patent Citations
Containerized VNF deployment method and related equipment
CN111949364A
Network resource management method, system, network device and readable storage medium
JP7377965B2
