Nfv orchestration method, apparatus, device, and storage medium

Abstract

The application discloses a kind of NFV arrangement method, device, equipment and storage medium, it is related to communication technical field, to solve the problem that existing technology cannot be arranged to fusion VNF.For application on NFVO, it include: receiving user uploaded fusion VNF package;Fusion VNF package is parsed, and VNF deployment information and CNF deployment information are acquired;According to VNF deployment information, VNF is deployed, and the deployment result of VNF is acquired;According to CNF deployment information, CNF is deployed, and the deployment result of CNF is acquired;The deployment result of VNF and the deployment result of CNF are as the joint deployment result of the fusion VNF corresponding to fusion VNF package of fusion VNF, and send to user.The technical scheme disclosed in the application can be applied to the process of fusion VNF NFV arrangement.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to NFV orchestration methods, apparatus, devices and storage media. Background Technology

[0002] Network function virtualization (NFV) is a technology that configures network devices to perform functions in software using virtualization techniques. NFV orchestration is the process of automating the deployment and provisioning of multiple network components. Orchestration combines multiple VNFs with physical network components into service chains to provide services to business or consumer users. It also provides virtual network functions (VNFs) configuration and linking, as well as dynamic scaling and elastic services.

[0003] Existing NFV orchestration technologies primarily target VNF ​​network elements. They consist of a Network Function Virtulization Orchestrator (NFVO), a Virtualization Network Function Manager (VNFM), and a Virtualized Infrastructure Manager (VIM). The NFVO manages multiple VIM resource pools. The NFVO instructs the VNFM to select VIMs with available resources from the VIM resource pools based on the VIM's own resource information for deploying VNF entities.

[0004] However, NFV not only has virtual machine-type VNF network elements, but also converged VNF network elements that include both VNFs and cloud-native network functions (CNFs). How to orchestrate these converged VNF network elements has become a pressing issue. Summary of the Invention

[0005] This application provides an NFV orchestration method, apparatus, device, and storage medium to solve the problem that the prior art cannot orchestrate converged VNFs.

[0006] In a first aspect, embodiments of this application provide an NFV orchestration method, applied to the Network Functions Orchestration Platform (NFVO), including:

[0007] Receive user-uploaded Converged Virtualized Network Function (VNF) packets;

[0008] The converged VNF packet is parsed to obtain VNF deployment information and cloud-native network function (CNF) deployment information;

[0009] Based on the VNF deployment information, deploy the VNF and obtain the deployment result of the VNF;

[0010] Based on the CNF deployment information, deploy the CNF and obtain the deployment result of the CNF;

[0011] The deployment results of the VNF and CNF are used as the joint deployment results of the fused VNF corresponding to the fused VNF package and sent to the user.

[0012] Optionally, the method for generating the merged VNF package includes: adding a Helm chart package corresponding to the CNF deployment information to the VNF package, wherein the Helm chart package includes: a Deployment resource object and a Service resource object.

[0013] Optionally, the NFVO includes a k8splugin, and the step of deploying the CNF according to the CNF deployment information and obtaining the CNF deployment result includes:

[0014] Based on the CNF deployment information, the k8splugin is invoked;

[0015] During CNF instantiation, the CNF is deployed through the k8splugin, and the deployment result of the CNF is obtained.

[0016] Optionally, calling the k8splugin based on the CNF deployment information includes:

[0017] Send a definition creation notification to the k8splugin;

[0018] The helm chart package is sent to the k8splugin, which then creates the definition based on the helm chart package.

[0019] Optionally, during the CNF instantiation process, deploying the CNF through the k8splugin and obtaining the CNF deployment result includes:

[0020] Create a fused VNF instance based on the fused VNF package;

[0021] Obtain the Kubernetes cluster and tenants required to instantiate CNF in the fused VNF instance;

[0022] Query the deployment information of the instantiated CNF from the k8splugin;

[0023] Receive CNF instantiation parameters sent by the user for the deployment information of the instantiated CNF;

[0024] Based on the CNF instantiation parameters, the system initiates a CNF instantiation request to the Kubernetes cluster through the k8splugin and obtains the CNF instantiation result.

[0025] Optionally, deploying the VNF based on the VNF deployment information and obtaining the deployment result of the VNF includes:

[0026] Based on the VNF deployment information, the corresponding Virtual Network Function Manager (VNFM) is invoked;

[0027] During the VNF instantiation process, the VNF is deployed through the VNFM, and the deployment result of the VNF is obtained.

[0028] Secondly, embodiments of this application also provide an NFV orchestration apparatus, applied to the Network Functions Orchestration Platform (NFVO), comprising:

[0029] The first module is used to receive VNF packets uploaded by users;

[0030] The second module is used to parse the converged VNF packet to obtain VNF deployment information and cloud-native network function (CNF) deployment information;

[0031] The third module is used to deploy the VNF according to the VNF deployment information and obtain the deployment result of the VNF;

[0032] The fourth module is used to deploy the CNF based on the CNF deployment information and obtain the deployment result of the CNF.

[0033] The fifth module is used to send the deployment results of the VNF and CNF as the joint deployment results of the converged VNF corresponding to the converged VNF package to the user.

[0034] Optionally, the fourth module is specifically used to call the k8splugin according to the CNF deployment information, and deploy the CNF through the k8splugin during the CNF instantiation process to obtain the CNF deployment result.

[0035] Optionally, the fourth module is specifically used to send a definition creation notification to the k8splugin, send the Helm chart package to the k8splugin, and enable the k8splugin to create the definition based on the Helm chart package.

[0036] Optionally, the fourth module is specifically used to create a converged VNF instance based on the converged VNF package, obtain the Kubernetes cluster and tenant required for instantiating CNF in the converged VNF instance, query the deployment information of the instantiated CNF from the k8splugin, receive CNF instantiation parameters sent by the user for the deployment information of the instantiated CNF, initiate a CNF instantiation request to the k8s cluster through the k8splugin based on the CNF instantiation parameters, and obtain the CNF instantiation result.

[0037] Optionally, the third module is specifically used to call the corresponding Virtualization Network Function Manager (VNFM) based on the VNF deployment information, deploy the VNF through the VNFM during the VNF instantiation process, and obtain the deployment result of the VNF.

[0038] Thirdly, embodiments of this application also provide a path NFV orchestration apparatus, including: a processor and a transceiver;

[0039] The transceiver is used to receive the converged virtualization network function (VNF) packets uploaded by the user, and send the deployment results of the VNFs and CNFs as the joint deployment results of the converged VNFs corresponding to the converged VNF packets to the user.

[0040] The processor is used to parse the converged VNF packet to obtain VNF deployment information and cloud-native network function (CNF) deployment information, deploy the VNF according to the VNF deployment information, obtain the deployment result of the VNF, deploy the CNF according to the CNF deployment information, and obtain the deployment result of the CNF.

[0041] Optionally, the processor is further configured to, based on the CNF deployment information, invoke the k8splugin to deploy the CNF during the CNF instantiation process and obtain the CNF deployment result.

[0042] Optionally, the transceiver is further configured to send a definition creation notification to the k8splugin, send the helm chart package to the k8splugin, and enable the k8splugin to create the definition based on the helm chart package.

[0043] Optionally, the transceiver is further configured to: obtain the k8s cluster and tenant required for instantiating CNF in the merged VNF instance; query the deployment information of the instantiated CNF from the k8splugin; receive CNF instantiation parameters sent by the user for the deployment information of the instantiated CNF; initiate a CNF instantiation request to the k8s cluster through the k8splugin according to the CNF instantiation parameters; and obtain the CNF instantiation result.

[0044] The processor is also configured to create a fused VNF instance based on the fused VNF package.

[0045] Optionally, the processor is further configured to, based on the VNF deployment information, invoke the corresponding Virtualization Network Function Manager (VNFM), deploy the VNF through the VNFM during the VNF instantiation process, and obtain the deployment result of the VNF.

[0046] Fourthly, embodiments of this application also provide a network device, including: a transceiver, a memory, a processor, and a program stored in the memory and executable on the processor; the processor is configured to read the program in the memory to implement the steps in the NFV orchestration method as described above.

[0047] Fifthly, embodiments of this application also provide a readable storage medium for storing a program, characterized in that the program, when executed by a processor, implements the steps in the NFV orchestration method as described above.

[0048] In this embodiment, the converged VNF package includes VNF deployment information and CNF deployment information, enabling NFVO to jointly deploy VNF and CNF based on the VNF deployment information and CNF deployment information, thus solving the problem that the prior art cannot orchestrate converged VNFs; since NFVO can jointly deploy VNF and CNF, NFVO enables virtual machines and containers to coexist, thereby enabling operators to use containerized applications in combination according to actual business needs. Attached Figure Description

[0049] Figure 1 This is a flowchart of the NFV orchestration method provided in the embodiments of this application;

[0050] Figure 2 yes Figure 1 The flowchart shown is a step 103 of the NFV orchestration method provided in the embodiment of this application;

[0051] Figure 3 yes Figure 1 The flowchart shown is a step 104 of the NFV orchestration method provided in the embodiment of this application;

[0052] Figure 4 yes Figure 3 The flowchart shown is a step 301 flowchart of the NFV orchestration method provided in the embodiment of this application;

[0053] Figure 5 yes Figure 3 The flowchart shown is a step 302 in the NFV orchestration method provided in the embodiment of this application;

[0054] Figure 6 yes Figure 1 The timing diagram shown illustrates the combined completion of the invocation process by steps 103 and 104 of the NFV orchestration method provided in this embodiment of the application.

[0055] Figure 7 yes Figure 1 The timing diagram shown illustrates the configuration process jointly completed by steps 103 and 104 of the NFV orchestration method provided in this embodiment of the application.

[0056] Figure 8 This is one of the structural diagrams of the NFV orchestration apparatus provided in the embodiments of this application;

[0057] Figure 9 This is the second structural diagram of the NFV orchestration device provided in the embodiments of this application. Detailed Implementation

[0058] In the embodiments of this application, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0059] In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.

[0060] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0061] See Figure 1 , Figure 1 This is a flowchart of the NFV orchestration method provided in an embodiment of this application. In this embodiment, the NFV orchestration method is applied to NFVO. Figure 1 As shown, it includes the following steps:

[0062] Step 101: Receive the fused VNF package uploaded by the user.

[0063] In this embodiment, the VNF package provided by the prior art can be modified in advance in the design state to add CNF deployment information to the VNF package and generate a fused VNF package.

[0064] In this embodiment, the method for generating a merged VNF package may specifically include: adding a Helm chart package corresponding to the CNF deployment information to the VNF package, wherein the Helm chart package includes: a Deployment resource object and a Service resource object.

[0065] To enable those skilled in the art to more clearly understand the fused VNF packet structure in this embodiment, it is described below through specific computer program code:

[0066] In this embodiment, the directory structure of the Helm chart package corresponding to the CNF deployment information is as follows:

[0067]

[0068] The directory structure of the VNF package is as follows:

[0069]

[0070]

[0071] After adding the Helm chart package corresponding to the CNF deployment information to the VNF package, the generated merged VNF package directory structure is as follows:

[0072]

[0073] Generating fused VNF packets using the above methods can mask the differences between NFVO-parsed VNF packets and containerized CNF packets, thus reducing the complexity of network element packet creation.

[0074] Of course, the above are just specific examples. In actual use, the generation method of fused VNF packages can include other methods, which will not be elaborated here.

[0075] Step 102: Parse the merged VNF package to obtain VNF deployment information and CNF deployment information.

[0076] Step 103: Deploy the VNF according to the VNF deployment information and obtain the deployment result of the VNF.

[0077] In this embodiment, as Figure 2 As shown, step 103 may include:

[0078] Step 201: Based on the VNF deployment information, call the corresponding VNFM.

[0079] Step 202: During the VNF instantiation process, deploy the VNF through VNFM and obtain the deployment result of the VNF.

[0080] Step 104: Deploy CNF according to CNF deployment information and obtain CNF deployment results.

[0081] Since CNF is a containerized network element, in order to deploy CNF, in this embodiment, a k8splugin is configured on NFVO, such as... Figure 3 As shown, step 104 may include:

[0082] Step 301: Based on the CNF deployment information, call the k8splugin.

[0083] In this embodiment, as Figure 4 As shown, step 301 may include:

[0084] Step 401: Send a definition creation notification to the k8splugin.

[0085] Step 402: Send the Helm chart package to the k8splugin so that the k8splugin can create a definition based on the Helm chart package.

[0086] pass Figure 4 The steps shown can complete the CNF configuration call on the k8splugin, thus providing the conditions for subsequent CNF deployment through the k8splugin.

[0087] Step 302: During CNF instantiation, deploy CNF using k8splugin and obtain the CNF deployment result.

[0088] In this embodiment, as Figure 5 Step 302 may include:

[0089] Step 501: Create a Fusion VNF instance based on the Fusion VNF package.

[0090] Step 502: Obtain the Kubernetes cluster and tenants required to instantiate CNF in the merged VNF instance.

[0091] Step 503: Query the deployment information of the instantiated CNF from the k8splugin.

[0092] Step 504: Receive CNF instantiation parameters sent by the user for the deployment information of the instantiated CNF.

[0093] Step 505: Based on the CNF instantiation parameters, initiate a CNF instantiation request to the Kubernetes cluster through the k8splugin and obtain the CNF instantiation result.

[0094] In this embodiment, step 104 can deploy CNF as a container using k8splugin. Containers require less memory and disk space, start up quickly, and can implement a microservice architecture.

[0095] Step 105: Send the deployment results of VNF and CNF as the joint deployment results of the converged VNF corresponding to the converged VNF package to the user.

[0096] In this embodiment, steps 103 and 104 are both completed in two steps:

[0097] 1. Call

[0098] Specifically, step 103 is: Step 201: Based on the VNF deployment information, call the corresponding VNFM.

[0099] Specifically, step 104 is: Step 301, call k8splugin based on CNF deployment information.

[0100] 2. Configuration

[0101] Specifically, step 103 involves step 202: during the VNF instantiation process, deploying the VNF via VNFM and obtaining the deployment result of the VNF.

[0102] Specifically, step 104 involves step 302: during CNF instantiation, CNF is deployed using k8splugin, and the deployment result of CNF is obtained.

[0103] The converged VNF described in this embodiment is a network element that includes both VNF and CNF; therefore, steps 103 and 104 are performed jointly. Specifically, in terms of timing, steps 103 and 104 can first jointly complete the invocation step, and then jointly complete the configuration step.

[0104] To enable those skilled in the art to more clearly understand the process of steps 103 and 104 being performed together, the following is an explanation using a timing diagram.

[0105] like Figure 6 As shown, the steps 103 and 104 combined to complete the calling process are as follows:

[0106] Step 601: After NFVO parses the user-uploaded converged VNF package through the catalog to obtain VNF deployment information and CNF deployment information, the catalog can send a VNF package subscription notification to the corresponding VNFM based on the VNF deployment information.

[0107] The step of calling VNFM is completed by sending a VNF package subscription notification to VNFM in step 601.

[0108] Optionally, in this embodiment, such as Figure 6 As shown, the process of calling VNFM may also include: the step of the user sending the associated VIM to the catalog, and the step of the catalog sending the virtual machine image required by the VNF to the associated VIM according to the VNF deployment information.

[0109] Step 602: Catalog sends a definition creation notification to k8splugin.

[0110] Step 603: The catalog sends the Helm chart package corresponding to the CNF deployment information to the k8splugin.

[0111] Complete the steps of calling the k8splugin through steps 602 and 603.

[0112] Optionally, in this embodiment, such as Figure 6 As shown, the process of calling the k8splugin may also include: the user sending the associated k8s cluster to the catalog, and the catalog sending the container image required by CNF to the associated k8s cluster based on the CNF deployment information.

[0113] After the calls to VNFM and k8splugin are completed, as follows Figure 6 As shown, it may also include a step where the catalog returns a notification to the user that the packet upload is complete, thereby informing the user that the converged VNF network element can be deployed.

[0114] like Figure 7 As shown, the steps for completing the deployment process by combining steps 103 and 104 are as follows:

[0115] Step 701: The user creates a converged VNF instance for NFVO's Lightweight Communication and Marshalling (LCM). The converged VNF instance includes: instantiated VNF and instantiated CNF.

[0116] Step 702: The user sends a notification to LCM to select VNFM.

[0117] Step 703: The user sends the VIM and tenant required for instantiating the VNF to the LCM.

[0118] Step 704: The user sends the Kubernetes cluster and tenant required for CNF instantiation to the LCM.

[0119] Step 705: The LCM sends a query for the Virtual Network Function Descriptor (VNFD) to the VNFM selected by the user.

[0120] Step 706: VNFM returns the query results to LCM.

[0121] Step 707: LCM queries the CNF parameters from the k8splugin.

[0122] Step 708: k8splugin returns the query results to LCM.

[0123] Step 709: LCM receives VNFD information sent by the user.

[0124] Step 710: LCM receives CNF instantiation parameters sent by the user.

[0125] Step 711: LCM sends a VNF instantiation request to VNFM.

[0126] Step 712: Perform VNF instantiation between VNFM and the VIM required to instantiate VNF.

[0127] Step 713: LCM sends a CNF instantiation request to k8splugin.

[0128] Step 714: The k8splugin initiates the CNF instantiation operation to the k8s required for CNF instantiation.

[0129] Step 715: LCM sends a query to k8splugin to obtain the CNF instantiation result.

[0130] Step 716: After completing the VNF instantiation operation with VIM, VNFM returns the VNF instantiation result to LCM.

[0131] Based on the above Figure 7 The steps shown can be used to complete the joint deployment of VNF and CNF.

[0132] Furthermore, such as Figure 7 As shown, LCM can send the VNF instantiation result and CNF instantiation result as a joint deployment result of the merged VNF to the user.

[0133] In this embodiment, the converged VNF package includes VNF deployment information and CNF deployment information, enabling NFVO to jointly deploy VNF and CNF based on the VNF deployment information and CNF deployment information, thus solving the problem that the prior art cannot orchestrate converged VNFs; since NFVO can jointly deploy VNF and CNF, NFVO enables virtual machines and containers to coexist, thereby enabling operators to use containerized applications in combination according to actual business needs.

[0134] This application also provides an NFV orchestration apparatus. See [link to relevant documentation]. Figure 8 As shown, the NFV orchestration device 800, applied on the Network Functions Orchestration Platform (NFVO), includes:

[0135] The first module 801 is used to receive converged virtualization network function (VNF) packets uploaded by users;

[0136] The second module 802 is used to parse the converged VNF packet to obtain VNF deployment information and cloud-native network function (CNF) deployment information;

[0137] The third module 803 is used to deploy the VNF according to the VNF deployment information and obtain the deployment result of the VNF;

[0138] The fourth module 804 is used to deploy the CNF according to the CNF deployment information and obtain the deployment result of the CNF;

[0139] The fifth module 805 is used to send the deployment results of the VNF and CNF as the joint deployment results of the converged VNF corresponding to the converged VNF package to the user.

[0140] Optionally, the fourth module 804 is specifically used to call the k8splugin according to the CNF deployment information, and deploy the CNF through the k8splugin during the CNF instantiation process to obtain the CNF deployment result.

[0141] Optionally, the fourth module 804 is specifically used to send a definition creation notification to the k8splugin, send the Helm chart package to the k8splugin, and enable the k8splugin to create the definition based on the Helm chart package.

[0142] Optionally, the fourth module 804 is specifically used to create a converged VNF instance based on the converged VNF package, obtain the k8s cluster and tenant required for instantiating CNF in the converged VNF instance, query the deployment information of the instantiated CNF from the k8splugin, receive CNF instantiation parameters sent by the user for the deployment information of the instantiated CNF, initiate a CNF instantiation request to the k8s cluster through the k8splugin based on the CNF instantiation parameters, and obtain the CNF instantiation result.

[0143] Optionally, the third module 803 is specifically used to call the corresponding Virtualization Network Function Manager (VNFM) according to the VNF deployment information, deploy the VNF through the VNFM during the VNF instantiation process, and obtain the deployment result of the VNF.

[0144] In this embodiment, the converged VNF package includes VNF deployment information and CNF deployment information, enabling NFVO to jointly deploy VNF and CNF based on the VNF deployment information and CNF deployment information, thus solving the problem that the prior art cannot orchestrate converged VNFs; since NFVO can jointly deploy VNF and CNF, NFVO enables virtual machines and containers to coexist, thereby enabling operators to use containerized applications in combination according to actual business needs.

[0145] The specific implementation method of the NFV orchestration device provided in the embodiments of this application can be found in the NFV orchestration method provided in the embodiments of this application, and will not be repeated here.

[0146] This application also provides an NFV orchestration device, see [link to relevant documentation]. Figure 9 As shown, it includes: processor 901 and transceiver 902;

[0147] The transceiver 902 is used to receive the converged virtualization network function (VNF) packet uploaded by the user, and send the deployment results of the VNF and CNF as the joint deployment results of the converged VNF corresponding to the converged VNF packet to the user.

[0148] The processor 901 is used to parse the converged VNF packet, obtain VNF deployment information and cloud-native network function (CNF) deployment information, deploy the VNF according to the VNF deployment information, obtain the deployment result of the VNF, deploy the CNF according to the CNF deployment information, and obtain the deployment result of the CNF.

[0149] Optionally, the processor 901 is further configured to, based on the CNF deployment information, invoke the k8splugin to deploy the CNF during the CNF instantiation process and obtain the CNF deployment result.

[0150] Optionally, the transceiver 902 is further configured to send a definition creation notification to the k8splugin, send the Helm chart package to the k8splugin, and enable the k8splugin to create the definition based on the Helm chart package.

[0151] Optionally, the transceiver 902 is further configured to: obtain the k8s cluster and tenant required for instantiating CNF in the converged VNF instance; query the deployment information of the instantiated CNF from the k8splugin; receive CNF instantiation parameters sent by the user for the deployment information of the instantiated CNF; initiate a CNF instantiation request to the k8s cluster through the k8splugin according to the CNF instantiation parameters; and obtain the CNF instantiation result.

[0152] The processor 901 is further configured to create a fused VNF instance based on the fused VNF package.

[0153] Optionally, the processor 901 is further configured to, based on the VNF deployment information, call the corresponding Virtualization Network Function Manager (VNFM), deploy the VNF through the VNFM during the VNF instantiation process, and obtain the deployment result of the VNF.

[0154] In this embodiment, the converged VNF package includes VNF deployment information and CNF deployment information, enabling NFVO to jointly deploy VNF and CNF based on the VNF deployment information and CNF deployment information, thus solving the problem that the prior art cannot orchestrate converged VNFs; since NFVO can jointly deploy VNF and CNF, NFVO enables virtual machines and containers to coexist, thereby enabling operators to use containerized applications in combination according to actual business needs.

[0155] This application also provides a network device, including: a transceiver, a memory, a processor, and a program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps in the NFV orchestration method described above.

[0156] In this embodiment, the converged VNF package includes VNF deployment information and CNF deployment information, enabling NFVO to jointly deploy VNF and CNF based on the VNF deployment information and CNF deployment information, thus solving the problem that the prior art cannot orchestrate converged VNFs; since NFVO can jointly deploy VNF and CNF, NFVO enables virtual machines and containers to coexist, thereby enabling operators to use containerized applications in combination according to actual business needs.

[0157] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0158] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0159] This application also provides a readable storage medium storing a program. When executed by a processor, this program implements the various processes of the above-described NFV orchestration method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here. The readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (e.g., floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND flash), solid-state drives (SSDs)).

[0160] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0161] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0162] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A Network Functions Virtualization (NFV) orchestration method, applied to the Network Functions Orchestration Platform (NFVO), characterized in that, The method comprises the following steps: receiving a user uploaded converged virtualized network function (VNF) package; parsing the converged VNF package to obtain VNF deployment information and cloud native network function (CNF) deployment information; deploying a VNF according to the VNF deployment information to obtain the deployment result of the VNF; deploying a CNF according to the CNF deployment information to obtain the deployment result of the CNF; sending the deployment result of the VNF and the deployment result of the CNF as the joint deployment result of the converged VNF corresponding to the converged VNF package to the user; The method for generating the converged VNF package comprises the following steps: adding a helm chart package corresponding to the CNF deployment information in the VNF package, wherein the helm chart package comprises a Deployment resource object and a Service resource object.

2. The method of claim 1, wherein, The NFVO comprises a k8splugin, and the deployment of the CNF according to the CNF deployment information to obtain the deployment result of the CNF comprises the following steps: calling the k8splugin according to the CNF deployment information; deploying the CNF through the k8splugin in the CNF instantiation process to obtain the deployment result of the CNF.

3. The method of claim 2, wherein, The calling of the k8splugin according to the CNF deployment information comprises the following steps: sending a creation defination notification to the k8splugin; sending the helm chart package to the k8splugin to enable the k8splugin to create the defination according to the helm chart package.

4. The method of claim 2, wherein, The deployment of the CNF through the k8splugin in the CNF instantiation process to obtain the deployment result of the CNF comprises the following steps: creating a converged VNF instance according to the converged VNF package; obtaining a k8s cluster and a tenant required for the instantiation of the CNF in the converged VNF instance; inquiring the deployment information of the instantiated CNF from the k8splugin; receiving a CNF instantiation parameter sent by the user for the deployment information of the instantiated CNF; sending an instantiation CNF request to the k8s cluster through the k8splugin according to the CNF instantiation parameter, and obtaining a CNF instantiation result.

5. The method according to any one of claims 1 to 4, characterized in that, The deployment of the VNF according to the VNF deployment information to obtain the deployment result of the VNF comprises the following steps: calling a corresponding virtualized network function manager (VNFM) according to the VNF deployment information; deploying the VNF through the VNFM in the VNF instantiation process to obtain the deployment result of the VNF.

6. An NFV orchestration apparatus, applied on a network function orchestration platform (NFVO), characterized in that, The method comprises the following steps: a first module for receiving a user uploaded converged virtualized network function (VNF) package; a second module for parsing the converged VNF package to obtain VNF deployment information and cloud native network function (CNF) deployment information; a third module for deploying a VNF according to the VNF deployment information to obtain the deployment result of the VNF; a fourth module configured to deploy the CNF according to the CNF deployment information and obtain a deployment result of the CNF; a fifth module configured to send the deployment result of the VNF and the deployment result of the CNF to the user as a joint deployment result of a converged VNF corresponding to the converged VNF package; The generation of the converged VNF package includes adding a helm chart package corresponding to the CNF deployment information in the VNF package, where the helm chart package includes a Deployment resource object and a Service resource object.

7. An NFV orchestration apparatus comprising: A processor and a transceiver; characterized in that, the transceiver is configured to receive a converged virtualized network function (VNF) package uploaded by a user, and send the deployment result of the VNF and the deployment result of the CNF to the user as a joint deployment result of a converged VNF corresponding to the converged VNF package; the processor is configured to parse the converged VNF package to obtain VNF deployment information and cloud native network function (CNF) deployment information, deploy the VNF according to the VNF deployment information to obtain a deployment result of the VNF, and deploy the CNF according to the CNF deployment information to obtain a deployment result of the CNF; The generation of the converged VNF package includes adding a helm chart package corresponding to the CNF deployment information in the VNF package, where the helm chart package includes a Deployment resource object and a Service resource object.

8. A network device comprising: A transceiver, a memory, a processor, and a program stored in the memory and executable on the processor; characterized in that the processor is configured to read the program in the memory to implement the steps in the NFV orchestration method according to any one of claims 1 to 5.

9. A readable storage medium for storing a program, characterized in that, The program, when executed by the processor, implements the steps in the NFV orchestration method according to any one of claims 1 to 5.

Images