A CNF network element management method, device, storage medium and computer program product

Abstract

Embodiments of the present application provide a CNF network element management method, device, storage medium and computer program product, the method comprising: a PaaS service module listening to an application programming interface (API) server managing the CNF network element; wherein the PaaS service module contains a custom resource and a resource controller corresponding to a CNF network element management function.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, device, storage medium, and computer program product for managing Cloud Native Network Function (CNF) network elements. Background Technology

[0002] The current network architecture for Network Functions Virtualization (NFV) in telecommunications follows a "three-layer, one-domain" architecture. The three layers are the infrastructure layer, the virtualization layer, and the network element layer, while the domain is the Management and Orchestration (MANO) domain. The management of Virtual Network Functions (VNFs) in this architecture includes lifecycle management, service FCAPS (Functional Network Capabilities and Service Capabilities), and operation and maintenance management. The MANO domain is responsible for network element lifecycle management, while the Element Management System (EMS) is responsible for service FCAPS and operation and maintenance management.

[0003] To support cloud-native evolution, ETSI NFV has released a transitional architecture compatible with virtual machines and containers. It adds container management and orchestration components to the original virtualization architecture to support containerized applications. However, the deployment process for CNF network element orchestration is not yet determined. Summary of the Invention

[0004] In view of this, embodiments of this application aim to provide a CNF network element management method, device, storage medium, and computer program product.

[0005] The technical solution of this application embodiment is implemented as follows:

[0006] This application provides a cloud-native network function (CNF) network element management method, which is applied to a Platform as a Service (PaaS) service module, including:

[0007] The application programming interface (API) server monitors the management of the CNF network elements.

[0008] The PaaS service module includes custom resources and resource controllers corresponding to the CNF network element management function.

[0009] In one embodiment, before managing the CNF network element, the method further includes:

[0010] The API server receives a custom resource instance creation request from the PaaS management module; the custom resource instance creation request includes deployment parameters for creating the CNF network element.

[0011] In one embodiment, managing the CNF network element includes:

[0012] Monitor and adjust the status of the custom resource instance to the desired status of the deployment parameters; the desired status of the deployment parameters is the status required to create the CNF network element.

[0013] Lifecycle management, including CNF network element creation, is performed based on the deployment parameters of the custom resource instance in the custom resource instance creation request.

[0014] In one embodiment, after the CNF network element is created, the method further includes:

[0015] Send a PaaS service instance creation completion message to the PaaS management module; the PaaS service instance creation completion message is used to indicate that the CNF network element has been created.

[0016] In one embodiment, after the CNF network element is created, the management of the CNF network element includes:

[0017] The API server receives a custom resource instance configuration request from the PaaS management module; wherein the custom resource instance configuration request includes configuration parameters for configuring the custom resource instance of the CNF network element.

[0018] Monitor and adjust the configuration of the custom resource instance to the desired configuration parameters; the desired configuration parameters are the configuration required by the CNF network element.

[0019] CNF network element configuration management is performed based on the custom resource instance configuration parameters in the custom resource instance configuration request.

[0020] In one embodiment, after the CNF network element is configured and carries services, the management of the CNF network element includes:

[0021] The API server receives a custom resource instance maintenance request sent by the PaaS management module; wherein the custom resource instance maintenance request includes the maintenance parameters of the custom resource instance of the CNF network element.

[0022] Monitor and adjust the operation and maintenance status of the custom resource instance to the desired status of the operation and maintenance parameters; the desired status of the operation and maintenance parameters is the operation and maintenance status required by the CNF network element.

[0023] CNF network elements are monitored and managed based on the custom resource instance operation and maintenance parameters in the custom resource instance operation and maintenance request.

[0024] This application also provides a cloud-native network function (CNF) network element management method, which is applied to a Platform as a Service (PaaS) management module, including:

[0025] Deploy custom resources and resource controllers corresponding to the CNF network element management function in the PaaS service module for the PaaS service module to manage the CNF network element.

[0026] In one embodiment, the custom resources and resource controllers corresponding to the CNF network element management function include:

[0027] Call the Application Programming Interface (API) server to create PaaS service capabilities for the PaaS service module;

[0028] The PaaS service capabilities include: custom resources and resource controllers corresponding to the CNF network element management function.

[0029] In one embodiment, after deploying the custom resources and resource controllers corresponding to the CNF network element management function, the method further includes:

[0030] Receive a PaaS service instance creation request sent by the Network Function Virtualization Orchestrator (NFVO); the PaaS service instance creation request is used to request the creation of a CNF network element.

[0031] Send a custom resource instance creation request to the API server; wherein, the custom resource instance creation request includes deployment parameters for creating the custom resource instance of the CNF network element;

[0032] or,

[0033] Receive a PaaS service instance configuration request sent by the Network Function Virtualization Orchestrator (NFVO); wherein the PaaS service instance configuration request is used to request configuration of the CNF network element;

[0034] Send a custom resource instance configuration request to the API server; wherein, the custom resource instance configuration request includes the configuration parameters of the custom resource instance of the CNF network element;

[0035] or,

[0036] Receive a PaaS service instance maintenance request sent by the Network Function Virtualization Orchestrator (NFVO); wherein the PaaS service instance maintenance request is used to request monitoring and maintenance of the CNF network element;

[0037] Send a custom resource instance operation and maintenance request to the API server; wherein, the custom resource instance operation and maintenance request includes the operation and maintenance parameters of the custom resource instance of the CNF network element.

[0038] In one embodiment, after deploying the custom resources and resource controllers corresponding to the CNF network element management function, the method further includes:

[0039] Receive a PaaS service instance creation completion message sent by the PaaS service module; the PaaS service instance creation completion message is used to indicate that the CNF network element has been created.

[0040] Send the PaaS service instance creation completion message to the NFVO;

[0041] or,

[0042] Receive a PaaS service instance configuration completion message sent by the PaaS service module; the PaaS service instance configuration completion message is used to indicate that the CNF network element configuration is complete.

[0043] Send the PaaS service instance configuration complete message to the NFVO;

[0044] or,

[0045] Receive the PaaS service instance operation and maintenance start message sent by the PaaS service module; the PaaS service instance operation and maintenance start message is used to indicate that the CNF network element operation and maintenance has been completed.

[0046] Send the PaaS service instance operation and maintenance start message to the NFVO.

[0047] This application embodiment also provides a Platform as a Service (PaaS) module, including: a first communication interface and a first processor; wherein,

[0048] The first processor is used to monitor the application programming interface (API) server's management of the CNF network element;

[0049] The PaaS service module includes custom resources and resource controllers corresponding to the CNF network element management function.

[0050] This application embodiment also provides a Platform as a Service (PaaS) management module, including: a second communication interface and a second processor; wherein,

[0051] The second processor deploys custom resources and resource controllers corresponding to the CNF network element management function in the PaaS service module for the PaaS service module to manage the CNF network element.

[0052] This application also provides a Platform as a Service (PaaS) module, including: a first processor and a first memory for storing computer programs capable of running on the processor.

[0053] Wherein, when the first processor is used to run the computer program, it executes the steps of the above method.

[0054] This application also provides a Platform as a Service (PaaS) management module, including: a second processor and a second memory for storing computer programs capable of running on the processor.

[0055] The second processor is used to execute the steps of the above method when running the computer program.

[0056] This application also provides a storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the above-described method.

[0057] This application also provides a computer program product, including a computer program that implements the above-described method when executed by a processor.

[0058] The CNF network element management method, device, storage medium, and computer program product provided in this application embodiment include a PaaS service module that listens to the application programming interface (API) server to manage the CNF network elements. The PaaS service module includes custom resources and resource controllers corresponding to the CNF network element management functions. This application embodiment's PaaS service module and PaaS management module PaaS-ify CNF network element management capabilities and achieve CNF network element management by listening to the API server. This enables rapid CNF network element management, improves service activation efficiency, and enhances agility. Furthermore, the PaaS capability extensibility platform can be gradually expanded to include common network element service capabilities, improving the CNF network element PaaS level and further reducing resource costs. Attached Figure Description

[0059] Figure 1 This is a schematic diagram of the CNF network element management method described in the embodiments of this application. Figure 1 ;

[0060] Figure 2 This is a schematic diagram of the PaaS service module and PaaS management module structure described in the embodiments of this application;

[0061] Figure 3 This is a schematic diagram of the CNF network element management method described in the embodiments of this application. Figure 2 ;

[0062] Figure 4 This is a schematic diagram of the CNF network element management method described in the application example of this application;

[0063] Figure 5 This is a schematic diagram of the CNF network element management device described in the embodiments of this application. Figure 1 ;

[0064] Figure 6 This is a schematic diagram of the CNF network element management device described in the embodiments of this application. Figure 2 ;

[0065] Figure 7 This is a schematic diagram of the structure of the PaaS service module described in the embodiments of this application;

[0066] Figure 8 This is a schematic diagram of the structure of the PaaS management module described in the embodiments of this application. Detailed Implementation

[0067] The present application will now be described in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings. It should be noted that, unless otherwise specified, the embodiments and features described in these embodiments can be combined with each other. The present application will now be described in detail with reference to the accompanying drawings and embodiments.

[0068] Platform as a Service (PaaS) is a cloud computing service model. In the typical layers of cloud computing, the PaaS layer lies between Software as a Service (SaaS) and Infrastructure as a Service (IaaS), used to address the software environment on which applications depend, greatly simplifying development and operation. Currently, common IT domain PaaS services generally include databases and message queues. With the evolution of containerization and microservices in telecommunications network elements, the telecommunications (CT) domain has also begun to explore CT PaaS.

[0069] Similar to traditional physical network elements and virtualized network elements (VNFs), CNF network elements also need to meet carrier-grade requirements for high performance, high stability, and high reliability. To support cloud-native evolution, a reasonable architecture and management processes are required to support the lifecycle, monitoring, and operation and maintenance management of CNF network elements. Based on this,

[0070] This application provides a CNF network element management method, such as... Figure 1 As shown, the method is applied to a Platform as a Service (PaaS) service module, including:

[0071] Step 101: Listen to the Application Programming Interface (API) server managing the CNF network element; wherein, the PaaS service module includes custom resources and resource controllers corresponding to the CNF network element management function.

[0072] In this embodiment of the application, the PaaS service module may be configured with a resource controller and custom resources corresponding to the CNF network element management function, that is: a controller manages the entire life cycle of network elements based on different custom resources; here, the CNF network element management function may include: life cycle management (LCM), configuration management and operation and maintenance management.

[0073] In this embodiment, the CNF Operator can be responsible for the entire lifecycle, configuration, monitoring, and operation and maintenance management of CNFs, and the CNF Operator's network element management capabilities can be PaaS-ified to build a CT PaaS service for CNF network element management. The CT PaaS service for managing CNF network elements can be jointly implemented through a PaaS service module and a PaaS management module, as shown in the structural diagram below. Figure 2 As shown.

[0074] As can be seen, an Operator is a Kubernetes API (Application Programming Interface) extension mechanism, using CNFOperator to encapsulate and control network element management-related functions. This application's CNF Operator consists of custom resources and a custom resource controller. Network element management functions can include three categories: Lifecycle Management (LCM), Config, and Operation. LCM is responsible for network element lifecycle management, Config is responsible for network element configuration management, and Operation is responsible for monitoring and managing network element status, alarms, performance, etc. These three management functions are encapsulated into user-defined Kubernetes resources, and the custom resource controller listens for changes in custom resource instances through the Kubernetes API List-Watch mechanism, thus enabling the management of custom resource instances, i.e., cloud-native network elements.

[0075] The PaaS service module is used to provide users with specific PaaS services, including three network element management PaaS service capabilities: CNF LCM, CNF Config, and CNF Operation. The PaaS service module mainly completes operations such as image distribution and package file parsing of PaaS service capabilities through the PaaS management module, and calls the Kubernetes API server (i.e., the API server described in this embodiment) to create service capabilities. It creates the CNF Operator PaaS service capability in the form of a deployment, completing the deployment of CNF network element LCM, Config, Operation custom resources and resource controllers.

[0076] In one embodiment of this application, before managing the CNF network element, the method further includes:

[0077] The API server receives a custom resource instance creation request from the PaaS management module; the custom resource instance creation request includes deployment parameters for creating the CNF network element.

[0078] It should be noted that in the embodiments of this application, different CNF network element management functions correspond to their respective custom resource instance data.

[0079] In this embodiment of the application, the management of the CNF network element includes:

[0080] Monitor and adjust the status of the custom resource instance to the desired status of the deployment parameters; the desired status of the deployment parameters is the status required to create the CNF network element.

[0081] Lifecycle management, including CNF network element creation, is performed based on the deployment parameters of the custom resource instance in the custom resource instance creation request.

[0082] In one embodiment of this application, after the CNF network element is created, the method further includes:

[0083] Send a PaaS service instance creation completion message to the PaaS management module; the PaaS service instance creation completion message is used to indicate that the CNF network element has been created.

[0084] In this embodiment of the application, after the CNF network element is created, the management of the CNF network element includes:

[0085] The API server receives a custom resource instance configuration request from the PaaS management module; wherein the custom resource instance configuration request includes configuration parameters for configuring the custom resource instance of the CNF network element.

[0086] Monitor and adjust the configuration of the custom resource instance to the desired configuration parameters; the desired configuration parameters are the configuration required by the CNF network element.

[0087] CNF network element configuration management is performed based on the custom resource instance configuration parameters in the custom resource instance configuration request.

[0088] In this embodiment of the application, after the CNF network element is configured and carries services, the management of the CNF network element includes:

[0089] The API server receives a custom resource instance maintenance request sent by the PaaS management module; wherein the custom resource instance maintenance request includes the maintenance parameters of the custom resource instance of the CNF network element.

[0090] Monitor and adjust the operation and maintenance status of the custom resource instance to the desired status of the operation and maintenance parameters; the desired status of the operation and maintenance parameters is the operation and maintenance status required by the CNF network element.

[0091] CNF network elements are monitored and managed based on the custom resource instance operation and maintenance parameters in the custom resource instance operation and maintenance request.

[0092] In practical applications, if a user initiates a CNF network element creation request, a custom instance resource is declared by setting custom resource instance data (parameter values), and the LCM function in the CNF Operator creates the custom resource instance; the configuration is completed after instantiation through the Config function; after the CNF is created, configured and carries services, the Operation function is responsible for monitoring the CNF network element services and resources. By comprehensively collecting CNF service performance alarm data and CNF-related container resource information and performance alarm data, unified monitoring and management are achieved, and CNF automatic scaling can be triggered by combining scaling strategies.

[0093] This application embodiment implements complex LCM tasks, configurations, and monitoring and maintenance operations through the CNF Operator mechanism, transforming the management of CNF network elements into the management of custom resource instances by the Operator, making CNF management of network elements simpler and more efficient.

[0094] This application also provides a method for managing Cloud Native Network Functions (CNF) network elements, such as... Figure 3As shown, the method is applied to the Platform as a Service (PaaS) management module, including:

[0095] Step 301: Deploy the custom resources and resource controllers corresponding to the CNF network element management function in the PaaS service module for the PaaS service module to manage the CNF network element.

[0096] In this embodiment of the application, the PaaS management module is used to manage the PaaS service module, so that the PaaS service module can perform management of the CNF network element.

[0097] In one embodiment, such as Figure 2 As shown, the PaaS management module is used to manage and support PaaS service capabilities and instances, and may include functional modules such as service API management, service lifecycle management, operation and maintenance management, image management, and package management. Specifically, the PaaS service API connects northbound to NFVO+, reporting PaaS capabilities, and users can view and operate the required PaaS services in the service directory of the NFVO+ portal interface; PaaS service lifecycle management is responsible for the creation, deletion, and other management of PaaS service capabilities and instances; PaaS service operation and maintenance management is responsible for the monitoring and operation and maintenance management of PaaS service capabilities and instances; image management is responsible for the management of service capability and instance images; and package management is responsible for the management of service capability and instance packages.

[0098] In this embodiment of the application, the custom resources and resource controllers corresponding to the deployment of CNF network element management functions include:

[0099] Call the Application Programming Interface (API) server to create PaaS service capabilities for the PaaS service module;

[0100] The PaaS service capabilities include: custom resources and resource controllers corresponding to the CNF network element management function.

[0101] In this embodiment of the application, after deploying the custom resources and resource controllers corresponding to the CNF network element management function, the method further includes:

[0102] Receive a PaaS service instance creation request sent by the Network Function Virtualization Orchestrator (NFVO); the PaaS service instance creation request is used to request the creation of a CNF network element.

[0103] Send a custom resource instance creation request to the API server; wherein, the custom resource instance creation request includes deployment parameters for creating the custom resource instance of the CNF network element;

[0104] or,

[0105] Receive a PaaS service instance configuration request sent by the Network Function Virtualization Orchestrator (NFVO); wherein the PaaS service instance configuration request is used to request configuration of the CNF network element;

[0106] Send a custom resource instance configuration request to the API server; wherein, the custom resource instance configuration request includes the configuration parameters of the custom resource instance of the CNF network element;

[0107] or,

[0108] Receive a PaaS service instance maintenance request sent by the Network Function Virtualization Orchestrator (NFVO); wherein the PaaS service instance maintenance request is used to request monitoring and maintenance of the CNF network element;

[0109] Send a custom resource instance operation and maintenance request to the API server; wherein, the custom resource instance operation and maintenance request includes the operation and maintenance parameters of the custom resource instance of the CNF network element.

[0110] In this embodiment of the application, after deploying the custom resources and resource controllers corresponding to the CNF network element management function, the method further includes:

[0111] Receive a PaaS service instance creation completion message sent by the PaaS service module; the PaaS service instance creation completion message is used to indicate that the CNF network element has been created.

[0112] Send the PaaS service instance creation completion message to the NFVO;

[0113] or,

[0114] Receive a PaaS service instance configuration completion message sent by the PaaS service module; the PaaS service instance configuration completion message is used to indicate that the CNF network element configuration is complete.

[0115] Send the PaaS service instance configuration complete message to the NFVO;

[0116] or,

[0117] Receive the PaaS service instance operation and maintenance start message sent by the PaaS service module; the PaaS service instance operation and maintenance start message is used to indicate that the CNF network element operation and maintenance has been completed.

[0118] Send the PaaS service instance operation and maintenance start message to the NFVO.

[0119] The CNF network element management method of this application is described below with reference to an application example. For example... Figure 4As shown, the instance manages CNF network elements by managing PaaS service capability instances. The NFVO, PaaS service platform (PaaS management module and PaaS service module), and K8s cluster (API server) collaborate end-to-end to achieve CNF network element management, including:

[0120] Step 1: The user selects CNF network element data packets and sets CNF network element deployment parameters from the NFVO interface, and submits a CNF network element instantiation request;

[0121] Step 2: NFVO sends a PaaS service instance creation request to the PaaS management module;

[0122] Step 3: The PaaS management module sends a custom resource instance creation request to the API server;

[0123] Step 4: The PaaS service module monitors the status changes of resources in the cluster in real time through the List-Watch interface provided by the API server, and adjusts the custom resource status to the desired status of the deployment parameters, thereby realizing the management of CNF instance creation;

[0124] Step 5: The PaaS service module CNF LCM module completes the creation of the custom resource instance, and the CNF network element creation is complete;

[0125] Step 6: The PaaS service module sends a PaaS service instance creation completion message to the PaaS management module;

[0126] Step 7: The PaaS management module sends a PaaS service instance creation completion message to NFVO;

[0127] Step 8: NFVO can display a CNF network element instantiation completion notification on the interface, and users can view the status of the newly deployed CNF network element in the CNF network element instance list of NFVO;

[0128] Step 9: After the CNF network element is created, the PaaS service module can manage the configuration of the CNF network element through the internal CNF Config module;

[0129] Step 10: After the CNF network element is created, configured and carries services, the PaaS service module can monitor and manage the CNF network element through the internal CNFOperation module.

[0130] Steps 9 and 10 above are in Figure 4 The process shown has been simplified; its execution is similar to the CNF network element creation process. Specifically...

[0131] The configuration management process for CNF network elements includes:

[0132] Step 1: The user sets CNF network element configuration parameters from the NFVO interface and submits a CNF network element configuration request;

[0133] Step 2: NFVO sends a PaaS service instance configuration request to the PaaS management module;

[0134] Step 3: The PaaS management module sends a custom resource instance configuration request to the API server;

[0135] Step 4: The PaaS service module monitors the status changes of resources in the cluster in real time through the List-Watch interface provided by the API server, and configures the custom resource instance as expected by the configuration parameters, thereby realizing the configuration management of CNF network elements;

[0136] Step 5: The PaaS service module can manage the configuration of CNF network elements through the internal CNF Config module;

[0137] Step 6: The PaaS service module sends a PaaS service instance configuration completion message to the PaaS management module;

[0138] Step 7: The PaaS management module sends a PaaS service instance configuration completion message to NFVO.

[0139] The operation and maintenance management process for CNF network elements includes:

[0140] Step 1: The user sets the CNF network element operation and maintenance parameters through the NFVO interface and submits a CNF network element operation and maintenance request;

[0141] Step 2: NFVO sends a PaaS service instance maintenance request to the PaaS management module;

[0142] Step 3: The PaaS management module sends a custom resource instance maintenance request to the API server;

[0143] Step 4: The PaaS service module monitors the status changes of resources in the cluster in real time through the List-Watch interface provided by the API server, and adjusts the operation and maintenance status of the custom resource instance to the expected operation and maintenance parameter status, thereby realizing the monitoring and operation and maintenance management of CNF network elements.

[0144] Step 5: The PaaS service module can monitor and manage CNF network elements through the internal CNF Operation module;

[0145] Step 6: The PaaS service module sends a PaaS service instance operation and maintenance start message to the PaaS management module;

[0146] Step 7: The PaaS management module sends a PaaS service instance operation and maintenance start message to NFVO.

[0147] This application simplifies complex LCM tasks and operations by using a CNF Operator, transforming the management of cloud-native CNF network elements into the management of custom resource instances by an Operator. This makes CNF management simpler and more efficient, and fully leverages cloud-native features to improve business stability. By constructing a CT domain network element management PaaS service module, unified monitoring and management of the lifecycle, services, and resources of cloud-native network elements is achieved, solving the problems of information fragmentation and independent operation and maintenance under the two management platforms in the current VNF ​​architecture, and improving operation and maintenance capabilities and fault location efficiency. In addition, the end-to-end process of CNF network element management based on the PaaS service module makes up for the undefined problem of cloud-native network element orchestration and deployment under the current NFV architecture.

[0148] To implement the method on the PaaS service module side of this application embodiment, this application embodiment also provides a CNF network element management device, which is installed on the PaaS service module, such as... Figure 5 As shown, the device includes: a first communication unit 501 and a first processing unit 502; wherein,

[0149] The first processing unit 502 is used to monitor the application programming interface (API) server's management of the CNF network element;

[0150] The PaaS service module includes custom resources and resource controllers corresponding to the CNF network element management function.

[0151] In this embodiment of the application, before the first processing unit 502 manages the CNF network element...

[0152] The first communication unit 501 is used to receive a custom resource instance creation request sent by the PaaS management module by listening to the API server; wherein, the custom resource instance creation request includes the deployment parameters for creating the custom resource instance of the CNF network element.

[0153] In this embodiment of the application, the first processing unit 502 manages the CNF network element, including:

[0154] Monitor and adjust the status of the custom resource instance to the desired status of the deployment parameters; the desired status of the deployment parameters is the status required to create the CNF network element.

[0155] Lifecycle management, including CNF network element creation, is performed based on the deployment parameters of the custom resource instance in the custom resource instance creation request.

[0156] In this embodiment of the application, after the CNF network element is created, the first communication unit 501 is further configured to send a PaaS service instance creation completion message to the PaaS management module; the PaaS service instance creation completion message is used to indicate that the CNF network element has been created.

[0157] In this embodiment of the application, after the CNF network element is created, the first processing unit 502 manages the CNF network element, including:

[0158] The API server receives a custom resource instance configuration request from the PaaS management module; wherein the custom resource instance configuration request includes configuration parameters for configuring the custom resource instance of the CNF network element.

[0159] Monitor and adjust the configuration of the custom resource instance to the desired configuration parameters; the desired configuration parameters are the configuration required by the CNF network element.

[0160] CNF network element configuration management is performed based on the custom resource instance configuration parameters in the custom resource instance configuration request.

[0161] In this embodiment of the application, after the CNF network element is configured and carries services, the first processing unit 502 manages the CNF network element, including:

[0162] The API server receives a custom resource instance maintenance request sent by the PaaS management module; wherein the custom resource instance maintenance request includes the maintenance parameters of the custom resource instance of the CNF network element.

[0163] Monitor and adjust the operation and maintenance status of the custom resource instance to the desired state of the operation and maintenance parameters; the desired state of the operation and maintenance parameters is the state required for the operation and maintenance of the CNF network element.

[0164] CNF network elements are monitored and managed based on the custom resource instance operation and maintenance parameters in the custom resource instance operation and maintenance request.

[0165] In practical applications, the first communication unit 501 can be implemented by the communication interface in the CNF network element management device; the first processing unit 502 can be implemented by the processor in the CNF network element management device.

[0166] It should be noted that the CNF network element management device provided in the above embodiments is only illustrated by the division of the above program modules during communication. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the device and method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0167] To implement the method on the PaaS service module side of this application embodiment, this application embodiment also provides a CNF network element management device, which is installed on the PaaS service module, such as... Figure 6 As shown, the device includes: a second communication unit 601 and a second processing unit 602; wherein,

[0168] The second processing unit 602 is used to deploy custom resources and resource controllers corresponding to the CNF network element management function in the PaaS service module, for the PaaS service module to manage the CNF network element.

[0169] In this embodiment of the application, the second processing unit 602 deploys custom resources and resource controllers corresponding to the CNF network element management function, including:

[0170] Call the Application Programming Interface (API) server to create PaaS service capabilities for the PaaS service module;

[0171] The PaaS service capabilities include: custom resources and resource controllers corresponding to the CNF network element management function.

[0172] In this embodiment, after the second processing unit 602 deploys the custom resources and resource controllers corresponding to the CNF network element management function, the second communication unit 601 is used for

[0173] Receive a PaaS service instance creation request sent by the Network Function Virtualization Orchestrator (NFVO); the PaaS service instance creation request is used to request the creation of a CNF network element.

[0174] Send a custom resource instance creation request to the API server; wherein, the custom resource instance creation request includes deployment parameters for creating the custom resource instance of the CNF network element;

[0175] or,

[0176] Receive a PaaS service instance configuration request sent by the Network Function Virtualization Orchestrator (NFVO); wherein the PaaS service instance configuration request is used to request configuration of the CNF network element;

[0177] Send a custom resource instance configuration request to the API server; wherein, the custom resource instance configuration request includes the configuration parameters of the custom resource instance of the CNF network element;

[0178] or,

[0179] Receive a PaaS service instance maintenance request sent by the Network Function Virtualization Orchestrator (NFVO); wherein the PaaS service instance maintenance request is used to request monitoring and maintenance of the CNF network element;

[0180] Send a custom resource instance operation and maintenance request to the API server; wherein, the custom resource instance operation and maintenance request includes the operation and maintenance parameters of the custom resource instance of the CNF network element.

[0181] In this embodiment of the application, after the second processing unit 602 deploys the custom resources and resource controllers corresponding to the CNF network element management function, the second communication unit 601 is further used for

[0182] Receive a PaaS service instance creation completion message sent by the PaaS service module; the PaaS service instance creation completion message is used to indicate that the CNF network element has been created.

[0183] Send the PaaS service instance creation completion message to the NFVO;

[0184] or,

[0185] Receive a PaaS service instance configuration completion message sent by the PaaS service module; the PaaS service instance configuration completion message is used to indicate that the CNF network element configuration is complete.

[0186] Send the PaaS service instance configuration complete message to the NFVO;

[0187] or,

[0188] Receive the PaaS service instance operation and maintenance start message sent by the PaaS service module; the PaaS service instance operation and maintenance start message is used to indicate that the CNF network element operation and maintenance has been completed.

[0189] Send the PaaS service instance operation and maintenance start message to the NFVO.

[0190] In practical applications, the second communication unit 601 can be implemented by the communication interface in the CNF network element management device; the second processing unit 602 can be implemented by the processor in the CNF network element management device.

[0191] It should be noted that the CNF network element management device provided in the above embodiments is only illustrated by the division of the above program modules during communication. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the device and method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0192] Based on the hardware implementation of the above program modules, and in order to implement the method on the PaaS service module side of this application embodiment, this application embodiment also provides a PaaS service module, such as... Figure 7 As shown, the PaaS service module 700 includes:

[0193] The first communication interface 701 is capable of exchanging information with the PaaS management module and / or other nodes on the network side;

[0194] The first processor 702 is connected to the first communication interface 701 to enable information interaction with the PaaS management module and / or other nodes on the network side, and to execute the methods provided by one or more technical solutions on the PaaS service module side when running a computer program;

[0195] The computer program is stored in the first memory 703.

[0196] Specifically, the first processor 702 is used to monitor the application programming interface (API) server's management of the CNF network element;

[0197] The PaaS service module includes custom resources and resource controllers corresponding to the CNF network element management function.

[0198] In this embodiment of the application, before the first processor 702 manages the CNF network element...

[0199] The first communication interface 701 is used to listen to the API server to receive a custom resource instance creation request sent by the PaaS management module; wherein, the custom resource instance creation request includes the deployment parameters for creating the custom resource instance of the CNF network element.

[0200] In this embodiment of the application, the first processor 702 manages the CNF network element, including:

[0201] Monitor and adjust the status of the custom resource instance to the desired status of the deployment parameters; the desired status of the deployment parameters is the status required to create the CNF network element.

[0202] Lifecycle management, including CNF network element creation, is performed based on the custom resource instance parameters in the custom resource instance creation request.

[0203] In this embodiment of the application, after the CNF network element is created, the first communication interface 701 is further used to send a PaaS service instance creation completion message to the PaaS management module; the PaaS service instance creation completion message is used to indicate that the CNF network element has been created.

[0204] In this embodiment of the application, after the CNF network element is created, the first processor 702 manages the CNF network element, including:

[0205] The API server receives a custom resource instance configuration request from the PaaS management module; wherein the custom resource instance configuration request includes configuration parameters for configuring the custom resource instance of the CNF network element.

[0206] Monitor and adjust the configuration of the custom resource instance to the desired configuration parameters; the desired configuration parameters are the configuration required by the CNF network element.

[0207] CNF network element configuration management is performed based on the custom resource instance configuration parameters in the custom resource instance configuration request.

[0208] In this embodiment of the application, after the CNF network element is configured and carries services, the first processor 702 manages the CNF network element, including:

[0209] The API server receives a custom resource instance maintenance request sent by the PaaS management module; wherein the custom resource instance maintenance request includes the maintenance parameters of the custom resource instance of the CNF network element.

[0210] Monitor and adjust the operation and maintenance status of the custom resource instance to the desired state of the operation and maintenance parameters; the desired state of the operation and maintenance parameters is the state required for the operation and maintenance of the CNF network element.

[0211] CNF network elements are monitored and managed based on the custom resource instance operation and maintenance parameters in the custom resource instance operation and maintenance request.

[0212] It should be noted that the specific processing procedures of the first communication interface 701 and the first processor 702 can be understood by referring to the above method, and will not be repeated here.

[0213] Of course, in practical applications, the various components in the PaaS service module 700 are coupled together through the bus system 704. It can be understood that the bus system 704 is used to implement communication between these components. In addition to the data bus, the bus system 704 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 7 The general designated all buses as Bus System 704.

[0214] The first memory 703 in this embodiment is used to store various types of data to support the operation of the PaaS service module 700. Examples of such data include any computer program used to operate on the PaaS service module 700.

[0215] The methods disclosed in the embodiments of this application can be applied to the first processor 702, or implemented by the first processor 702. The first processor 702 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware or by instructions in the form of software in the first processor 702. The first processor 702 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The first processor 702 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly reflected as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in the first memory 703. The first processor 702 reads the information in the first memory 703 and completes the steps of the aforementioned method in combination with its hardware.

[0216] In an exemplary embodiment, the PaaS service module 700 may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to perform the aforementioned method.

[0217] Based on the hardware implementation of the above program modules, and in order to implement the method on the PaaS management module side of the embodiments of this application, the embodiments of this application also provide a PaaS management module, such as... Figure 8 As shown, the PaaS management module 800 includes:

[0218] The second communication interface 801 is capable of exchanging information with the PaaS service module and / or other nodes on the network side;

[0219] The second processor 802 is connected to the second communication interface 801 to enable information interaction with the PaaS service module and / or other nodes on the network side, and to execute the methods provided by one or more technical solutions on the PaaS management module side when running computer programs;

[0220] The computer program is stored in the second memory 803.

[0221] Specifically, the second processor 802 is used to deploy custom resources and resource controllers corresponding to the CNF network element management function in the PaaS service module, for the PaaS service module to manage the CNF network element.

[0222] In this embodiment of the application, the second processor 802 deploys custom resources and resource controllers corresponding to the CNF network element management function, including:

[0223] Call the Application Programming Interface (API) server to create PaaS service capabilities for the PaaS service module;

[0224] The PaaS service capabilities include: custom resources and resource controllers corresponding to the CNF network element management function.

[0225] In this embodiment, after the second processor 802 deploys the custom resources and resource controllers corresponding to the CNF network element management function, the second communication interface 801 is used for...

[0226] Receive a PaaS service instance creation request sent by the Network Function Virtualization Orchestrator (NFVO); the PaaS service instance creation request is used to request the creation of a CNF network element.

[0227] Send a custom resource instance creation request to the API server; wherein, the custom resource instance creation request includes deployment parameters for creating the custom resource instance of the CNF network element;

[0228] or,

[0229] Receive a PaaS service instance configuration request sent by the Network Function Virtualization Orchestrator (NFVO); wherein the PaaS service instance configuration request is used to request configuration of the CNF network element;

[0230] Send a custom resource instance configuration request to the API server; wherein, the custom resource instance configuration request includes the configuration parameters of the custom resource instance of the CNF network element;

[0231] or,

[0232] Receive a PaaS service instance maintenance request sent by the Network Function Virtualization Orchestrator (NFVO); wherein the PaaS service instance maintenance request is used to request monitoring and maintenance of the CNF network element;

[0233] Send a custom resource instance operation and maintenance request to the API server; wherein, the custom resource instance operation and maintenance request includes the operation and maintenance parameters of the custom resource instance of the CNF network element.

[0234] In this embodiment, after the second processor 802 deploys the custom resources and resource controllers corresponding to the CNF network element management function, the second communication interface 801 is also used for

[0235] Receive a PaaS service instance creation completion message sent by the PaaS service module; the PaaS service instance creation completion message is used to indicate that the CNF network element has been created.

[0236] Send the PaaS service instance creation completion message to the NFVO;

[0237] or,

[0238] Receive a PaaS service instance configuration completion message sent by the PaaS service module; the PaaS service instance configuration completion message is used to indicate that the CNF network element configuration is complete.

[0239] Send the PaaS service instance configuration complete message to the NFVO;

[0240] or,

[0241] Receive the PaaS service instance operation and maintenance start message sent by the PaaS service module; the PaaS service instance operation and maintenance start message is used to indicate that the CNF network element operation and maintenance has been completed.

[0242] Send the PaaS service instance operation and maintenance start message to the NFVO.

[0243] It should be noted that the specific processing procedures of the first communication interface 801 and the first processor 802 can be understood by referring to the above method, and will not be repeated here.

[0244] Of course, in practical applications, the various components in the PaaS management module 800 are coupled together through the bus system 804. It can be understood that the bus system 804 is used to implement communication between these components. In addition to the data bus, the bus system 804 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 8 The general labeled all buses as Bus System 804.

[0245] The first memory 803 in this embodiment is used to store various types of data to support the operation of the PaaS management module 800. Examples of such data include any computer program used to operate on the PaaS management module 800.

[0246] The methods disclosed in the embodiments of this application can be applied to the first processor 802, or implemented by the first processor 802. The first processor 802 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware or by instructions in the form of software in the first processor 802. The first processor 802 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The first processor 802 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in the first memory 803. The first processor 802 reads the information in the first memory 803 and completes the steps of the aforementioned method in combination with its hardware.

[0247] In an exemplary embodiment, the PaaS management module 800 may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to perform the aforementioned methods.

[0248] In an exemplary embodiment, this application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, such as a first memory 703 storing a computer program, which can be executed by the first processor 702 of the PaaS service module 700 to complete the steps described in the aforementioned PaaS service module-side method. Another example is a second memory 803 storing a computer program, which can be executed by the second processor 802 of the PaaS management module 800 to complete the steps described in the aforementioned PaaS management module-side method. The computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM.

[0249] Exemplary embodiments of this application also provide a computer program product, including a computer program that can be executed by the processor of a PaaS service module 700 to complete the steps described in any of the foregoing methods. Embodiments of this application also provide a computer program product, including a computer program that can be executed by the processor of a PaaS management module 800 to complete the steps described in any of the foregoing methods.

[0250] It should be noted that terms such as "first" and "second" are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0251] Furthermore, the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0252] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application.

Claims

1. A method for managing Cloud Native Network Function (CNF) network elements, characterized in that, The method is applied to the Platform as a Service (PaaS) service module, including: The application programming interface (API) server monitors the management of the CNF network elements. The PaaS service module includes custom resources corresponding to the CNF network element management function and a resource controller. The CNF network element management function includes lifecycle management, configuration management, and operation and maintenance management. The custom resources and resource controller corresponding to the CNF network element management function are deployed by the PaaS management module. Lifecycle management, configuration management, and operation and maintenance management each correspond to different custom resources. The resource controller is used to perform lifecycle management, configuration management, and operation and maintenance management of CNF network elements based on different custom resources. The API server is used by the PaaS service module to listen for custom resource instance creation requests, custom resource instance configuration requests, and custom resource instance operation and maintenance requests sent by the PaaS management module. Before managing the CNF network element, the method further includes: The API server receives a custom resource instance creation request from the PaaS management module; the custom resource instance creation request includes deployment parameters for creating the CNF network element.

2. The method according to claim 1, characterized in that, Managing the CNF network element includes: Monitor and adjust the status of the custom resource instance to the desired status of the deployment parameters; the desired status of the deployment parameters is the status required to create the CNF network element. Lifecycle management, including CNF network element creation, is performed based on the deployment parameters of the custom resource instance in the custom resource instance creation request.

3. The method according to claim 1 or 2, characterized in that, After the CNF network element is created, the method further includes: Send a PaaS service instance creation completion message to the PaaS management module; the PaaS service instance creation completion message is used to indicate that the CNF network element has been created.

4. The method according to claim 1, characterized in that, After the CNF network element is created, the CNF network element is managed, including: The API server receives a custom resource instance configuration request from the PaaS management module; wherein the custom resource instance configuration request includes the configuration parameters of the custom resource instance of the CNF network element. Monitor and adjust the configuration of the custom resource instance to the desired configuration parameters; the desired configuration parameters are the configuration required by the CNF network element. CNF network element configuration management is performed based on the configuration parameters of the custom resource instance in the custom resource instance configuration request.

5. The method according to claim 1, characterized in that, After the CNF network element is configured and carries services, the management of the CNF network element includes: The API server receives a custom resource instance maintenance request sent by the PaaS management module; wherein the custom resource instance maintenance request includes the maintenance parameters of the custom resource instance of the CNF network element. Monitor and adjust the operation and maintenance status of the custom resource instance to the desired status of the operation and maintenance parameters; the desired status of the operation and maintenance parameters is the operation and maintenance status required by the CNF network element. CNF network elements are monitored and managed based on the operation and maintenance parameters of the custom resource instance in the operation and maintenance request.

6. A method for managing CNF (Cloud Native Network Function) network elements, characterized in that, The method is applied to the Platform as a Service (PaaS) management module, including: A custom resource corresponding to the CNF network element management function and a resource controller are deployed in the PaaS service module for the PaaS service module to manage the CNF network element. The CNF network element management function includes lifecycle management, configuration management, and operation and maintenance management. The PaaS service module is used to listen to the API server for managing the CNF network element. Before managing the CNF network element, the PaaS service module is used to listen to the API server for receiving a custom resource instance creation request sent by the PaaS management module. The custom resource instance creation request includes deployment parameters for creating the custom resource instance of the CNF network element. The lifecycle management, configuration management, and operation and maintenance management correspond to different custom resources. The resource controller is used to perform lifecycle management, configuration management, and operation and maintenance management of the CNF network element based on different custom resources. The PaaS service module is also used to listen to the API server for receiving custom resource instance configuration requests and custom resource instance operation and maintenance requests sent by the PaaS management module.

7. The method according to claim 6, characterized in that, The custom resources and resource controllers corresponding to the deployment of CNF network element management functions include: Call the Application Programming Interface (API) server to create PaaS service capabilities for the PaaS service module; The PaaS service capabilities include: custom resources and resource controllers corresponding to the CNF network element management function.

8. The method according to claim 6, characterized in that, After deploying the custom resources and resource controllers corresponding to the CNF network element management function, the method further includes: Receive a PaaS service instance creation request sent by the Network Function Virtualization Orchestrator (NFVO); the PaaS service instance creation request is used to request the creation of a CNF network element. Send a custom resource instance creation request to the API server; wherein, the custom resource instance creation request includes deployment parameters for creating the custom resource instance of the CNF network element; or, Receive a PaaS service instance configuration request sent by the Network Function Virtualization Orchestrator (NFVO); wherein the PaaS service instance configuration request is used to request configuration of the CNF network element; Send a custom resource instance configuration request to the API server; wherein, the custom resource instance configuration request includes the configuration parameters of the custom resource instance of the CNF network element; or, Receive a PaaS service instance maintenance request sent by the Network Function Virtualization Orchestrator (NFVO); wherein the PaaS service instance maintenance request is used to request monitoring and maintenance of the CNF network element; Send a custom resource instance operation and maintenance request to the API server; wherein, the custom resource instance operation and maintenance request includes the operation and maintenance parameters of the custom resource instance of the CNF network element.

9. The method according to claim 8, characterized in that, After deploying the custom resources and resource controllers corresponding to the CNF network element management function, the method further includes: Receive a PaaS service instance creation completion message sent by the PaaS service module; the PaaS service instance creation completion message is used to indicate that the CNF network element has been created. Send the PaaS service instance creation completion message to the NFVO; or, Receive a PaaS service instance configuration completion message sent by the PaaS service module; the PaaS service instance configuration completion message is used to indicate that the CNF network element configuration is complete. Send the PaaS service instance configuration complete message to the NFVO; or, Receive the PaaS service instance operation and maintenance start message sent by the PaaS service module; the PaaS service instance operation and maintenance start message is used to indicate that the CNF network element operation and maintenance has been completed. Send the PaaS service instance operation and maintenance start message to the NFVO.

10. A Platform as a Service (PaaS) module, characterized in that, include: A first communication interface and a first processor; wherein... The first processor is used to monitor the application programming interface (API) server's management of CNF network elements; The PaaS service module includes custom resources corresponding to the CNF network element management function and a resource controller. The CNF network element management function includes lifecycle management, configuration management, and operation and maintenance management. The custom resources and resource controller corresponding to the CNF network element management function are deployed by the PaaS management module. Lifecycle management, configuration management, and operation and maintenance management each correspond to different custom resources. The resource controller is used to perform lifecycle management, configuration management, and operation and maintenance management of CNF network elements based on different custom resources. The API server is used by the PaaS service module to listen for custom resource instance creation requests, custom resource instance configuration requests, and custom resource instance operation and maintenance requests sent by the PaaS management module. Before managing the CNF network element, the first processor is configured to receive a custom resource instance creation request sent by the PaaS management module by listening to the API server; wherein, the custom resource instance creation request includes deployment parameters for creating the custom resource instance of the CNF network element.

11. A Platform as a Service (PaaS) management module, characterized in that, include: A second communication interface and a second processor; wherein... The second processor is used to deploy custom resources and resource controllers corresponding to the CNF network element management function in the PaaS service module, for the PaaS service module to manage the CNF network element; the CNF network element management function includes: lifecycle management, configuration management, and operation and maintenance management; the PaaS service module is used to listen to the API server for managing the CNF network element, and before managing the CNF network element, the PaaS service module is used to listen to the API server to receive a custom resource instance creation request sent by the PaaS management module; wherein, the custom resource instance creation request includes deployment parameters for creating a custom resource instance of the CNF network element; the lifecycle management, configuration management, and operation and maintenance management correspond to different custom resources, and the resource controller is used to perform lifecycle management, configuration management, and operation and maintenance management of the CNF network element based on different custom resources; the PaaS service module is also used to listen to the API server to receive custom resource instance configuration requests and custom resource instance operation and maintenance requests sent by the PaaS management module.

12. A Platform as a Service (PaaS) module, characterized in that, include: A first processor and a first memory for storing computer programs capable of running on the processor. Wherein, when the first processor is used to run the computer program, it performs the steps of the method according to any one of claims 1 to 5.

13. A Platform as a Service (PaaS) management module, characterized in that, include: A second processor and a second memory for storing computer programs that can run on the processor. Wherein, when the second processor is used to run the computer program, it performs the steps of the method according to any one of claims 6 to 9.

14. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1-5, or the steps of the method according to any one of claims 6-9.

15. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method of any one of claims 1-5, or the method of any one of claims 6-9.

Images