Communication method and device

Abstract

An embodiment of this application provides a communication method and device. The method includes: a container cluster management CCM receives a first request message from a network device, the first request is used to request the CCM to associate a target customized container cluster management characteristic with a target container cluster, the first request message includes an identification information of the target customized container cluster management characteristic and an identification information of the target container cluster, the network device is a consumer entity of the CCM, and the CCM associates the target customized container cluster management characteristic with the target container cluster based on the first request message. According to the solution of this application, dynamic deployment of container cluster management characteristics can be realized, so that the requirements of carriers can be better met. In addition, the solution for realizing dynamic deployment of container cluster management characteristics provided in this application does not need to perform interaction between the CCM and the CISM, so that the increase in the integration cost of interoperation between the functions of the container platform layer in a multi-vendor environment can be avoided.

Description

[Technical Field]

[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] This application claims priority to Chinese Patent Application No. 202111303494.7, entitled "COMMUNICATION METHOD AND APPARATUS," filed with the State Intellectual Property Office of the People's Republic of China on November 5, 2021, the entire contents of which are incorporated by reference.

[0002] [Technical field] TECHNICAL FIELD Embodiments of this application relate to the field of communication technologies, and in particular to communication methods and devices. [Background technology]

[0003] Currently, container cluster management characteristics are deployed to container clusters in a static configuration manner. For example, in the process of creating a container cluster, certain container cluster management characteristics may be added to the container cluster, and in the process of deleting a container cluster, the container cluster management characteristics used by the container cluster are deleted accordingly, thereby realizing a tight coupling between the container cluster management characteristics and the container cluster. However, deploying container cluster management characteristics in a static configuration manner cannot meet carrier requirements, especially in scenarios where the container cluster is applied to a multi-tenant management environment. Carriers urgently expect a method for dynamically deploying container cluster management characteristics to container clusters based on their operational management requirements. Therefore, how to realize dynamic deployment of container cluster management characteristics is an urgent problem to be solved. Summary of the Invention

[0004] The embodiments of this application provide a communication method and apparatus for realizing dynamic deployment of container cluster management features.

[0005] According to a first aspect, there is provided a communication method, the method including:

[0006] The container cluster management CCM receives a first request message from a network device, the first request message is used to request the CCM to associate a target customized container cluster management characteristic with a target container cluster, the first request message includes identification information of the target customized container cluster management characteristic and identification information of the target container cluster, the network device is a consumer entity of the CCM, and the CCM associates the target customized container cluster management characteristic with the target container cluster based on the first request message.

[0007] In a possible implementation, the network device is a network function virtualization orchestrator NFVO.

[0008] According to the solution of this application, the CCM can receive a first request message from the NFVO and associate target customized container cluster management characteristics with the target container cluster based on the first request message. In this way, dynamic deployment of container cluster management characteristics is realized, and carrier requirements are better met. Furthermore, the solution for realizing dynamic deployment of container cluster management characteristics provided in this application does not need to perform interaction between the CCM and the CISM, thereby avoiding an increase in integration costs in a multi-vendor environment due to interoperation between functions of the container platform layer.

[0009] Referring to the first aspect, in some implementation methods of the first aspect, the first request message further includes scope information of the association operation, and the scope information of the association operation indicates that the target customized container cluster management characteristics are applied to all naming spaces in the target container cluster, or the scope information of the association operation indicates that the target customized container cluster management characteristics are applied to several naming spaces in the target container cluster, and the first request message further includes identification information of the several naming spaces.

[0010] Referring to the first aspect, in some implementation methods of the first aspect, the first request message further includes information regarding a consumer that is in the target container cluster and uses the target customized container cluster management characteristics, and the consumer that uses the target customized container cluster management characteristics is a control plane functional entity and / or a user plane functional entity.

[0011] Referring to the first aspect, in some implementations of the first aspect, the method further includes:

[0012] The CCM sends a first response message to the network device, where the first response message indicates that the target customized container cluster management characteristic has been successfully associated with the target container cluster.

[0013] Referring to the first aspect, in some implementation manners of the first aspect, before the CCM receives the first request message from the network device, the method further includes:

[0014] The CCM receives a second request message from the network device, the second request is used to request the CCM to load an object file, the second request message includes specific information, the specific information is for determining the object file, the object file includes configuration, state and policy information for deploying and executing the target customized container cluster management properties, the CCM determines the object file based on the second request message and verifies whether the object file is loadable, the CCM loads the object file when the object file is loadable, and the CCM sends a second response message to the network device, the second response message indicating that the CCM has successfully loaded the object file.

[0015] Referring to the first aspect, in some implementation methods of the first aspect, the object file is a management container cluster object declaration descriptor (MDD) file, and the specific information includes identification information of the object file and / or storage path information of the object file.

[0016] Referring to the first aspect, in some implementations of the first aspect, after the CCM loads the object file, the method further includes:

[0017] The CCM receives a third request message from the network device, the third request is used to request the CCM to create a target customized container cluster management property, the third request message includes specific information, the CCM determines an object file based on the third request message, the CCM creates a target object instance based on deployment information in the object file, the target object instance corresponds to the target customized container cluster management property, the CCM sends a third response message to the network device, the third response message indicates that the CCM has successfully created the target customized container cluster management property, and the third response message includes identification information of the target object instance.

[0018] Referring to the first aspect, in some implementation manners of the first aspect, after the CCM associates the target customized container cluster management characteristics with the target container cluster, the method further includes:

[0019] The CCM receives a fourth request message from the network device, the fourth request is used to request that the target customized container cluster management properties be disassociated from the target container cluster, the fourth request message includes identification information of the target customized container cluster management properties and identification information of the target container cluster, the CCM disassociates the target customized container cluster management properties from the target container cluster based on the fourth request message, and the CCM sends a fourth response message to the network device, the fourth response message indicating that the CCM has successfully disassociated the target customized container cluster management properties from the target container cluster.

[0020] According to the solution of this application, the CCM can receive a fourth request message from the NFVO, and complete the disassociation between the target customized container cluster management characteristic and the target container cluster based on the fourth request message. In this way, the customized container cluster management characteristic can be dynamically removed from the container cluster without deleting the container cluster, and the carrier's requirements can be better met.

[0021] According to the solution of this application, the CCM can receive a fourth request message from the NFVO, and complete the disassociation between the target customized container cluster management characteristic and the target container cluster based on the fourth request message. In comparison, in the solution of this application, the customized container cluster management characteristic can be dynamically disassociated from the container cluster without a container cluster deletion process, thereby better meeting the carrier change requirements.

[0022] Referring to the first aspect, in some implementation manners of the first aspect, after the CCM disassociates the target customized container cluster management properties from the target container cluster, the method further includes:

[0023] The CCM receives a fifth request message from the network device, the fifth request is used to request the deletion of a target customized container cluster management characteristic, the fifth request message includes identification information of the target customized container cluster management characteristic, the CCM deletes the target customized container cluster management characteristic based on the fifth request message, and the CCM sends a fifth response message to the network device, the fifth response message indicating that the CCM has successfully deleted the target customized container cluster management characteristic.

[0024] According to a second aspect, there is provided a communication method, the method including:

[0025] The network device determines to associate a target customized container cluster management characteristic with a target container cluster, the network device sends a first request message to a container cluster management CCM, the first request is used to request the CCM to associate the target customized container cluster management characteristic with the target container cluster, the first request message includes identification information of the target customized container cluster management characteristic and identification information of the target container cluster, and the network device is a consumer entity of the CCM.

[0026] In a possible implementation, the network device is a network function virtualization orchestrator NFVO.

[0027] According to the solution of this application, the NFVO can determine that target customized container cluster management characteristics need to be associated with the target container cluster. Furthermore, the NFVO sends a first request message to the CCM. In this way, the CCM associates the target customized container cluster management characteristics with the target container cluster based on the first request message, thereby realizing dynamic deployment of container cluster management characteristics and better meeting carrier requirements. Furthermore, the solution for realizing dynamic deployment of container cluster management characteristics provided in this application does not require interaction between the CCM and the CISM, thereby avoiding an increase in integration costs in a multi-vendor environment due to interoperation between functions in the container platform layer.

[0028] Referring to the second aspect, in some implementation methods of the second aspect, the first request message further includes scope information of the association operation, and the scope information of the association operation indicates that the target customized container cluster management characteristics are applied to all naming spaces in the target container cluster, or the scope information of the association operation indicates that the target customized container cluster management characteristics are applied to several naming spaces in the target container cluster, and the first request message further includes identification information of the several naming spaces.

[0029] Referring to the second aspect, in some implementation methods of the second aspect, the first request message further includes information regarding consumers that are within the target container cluster and that use the target customized container cluster management characteristics, and the consumers that use the target customized container cluster management characteristics are control plane functional entities and / or user plane functional entities.

[0030] Referring to the second aspect, in some implementations of the second aspect, the method further includes:

[0031] The network device receives a first response message from the CCM, where the first response message indicates that the target customized container cluster management characteristic has been successfully associated with the target container cluster.

[0032] Referring to the second aspect, in some implementations of the second aspect, the method further includes:

[0033] The network device determines an object file, the object file including configuration, state and policy information for deploying and executing the target customized container cluster management properties; the network device sends a second request message to the CCM, the second request is used to request the CCM to load the object file, the second request message includes specific information, the specific information is for determining the object file; the network device receives a second response message from the CCM, the second response message indicating that the CCM has successfully loaded the object file.

[0034] Referring to the second aspect, in some implementation methods of the second aspect, the object file is a management container cluster object declaration descriptor (MDD) file, and the specific information includes identification information of the object file and / or storage path information of the object file.

[0035] Referring to the second aspect, in some implementations of the second aspect, the method further includes:

[0036] The network device decides to create a target customized container cluster management property, the network device sends a third request message to the CCM, the third request is used to request the CCM to create the target customized container cluster management property, the third request message includes specific information, the network device receives a third response message from the CCM, the third response message indicates that the CCM has successfully created the target customized container cluster management property, the third response message includes identification information of the target object instance, the target object instance corresponds to the target customized container cluster management property.

[0037] Referring to the second aspect, in some implementations of the second aspect, the method further includes:

[0038] The network device decides to disassociate the target customized container cluster management property from the target container cluster, the network device sends a fourth request message to the CCM, the fourth request is used to request that the target customized container cluster management property be disassociated from the target container cluster, the fourth request message includes identification information of the target customized container cluster management property and identification information of the target container cluster, the network device receives a fourth response message from the CCM, the fourth response message indicates that the CCM has successfully disassociated the target customized container cluster management property from the target container cluster.

[0039] According to the solution of this application, when the target customized container cluster management characteristic needs to be disassociated from the target container cluster, the NFVO may send a fourth request message to the CCM, so that the CCM completes the disassociation between the target customized container cluster management characteristic and the target container cluster based on the fourth request message. In this way, the customized container cluster management characteristic can be dynamically removed from the container cluster without deleting the container cluster, and the carrier's requirements are better met.

[0040] Referring to the second aspect, in some implementations of the second aspect, the method further includes:

[0041] The network device decides to delete the target customized container cluster management characteristic, the network device sends a fifth request message to the CCM, the fifth request is used to request the deletion of the target customized container cluster management characteristic, the fifth request message includes identification information of the target customized container cluster management characteristic, the network device receives a fifth response message from the CCM, the fifth response message indicates that the CCM has successfully deleted the target customized container cluster management characteristic.

[0042] According to a third aspect, there is provided a container cluster management (CCM) including a transceiver unit and a processing unit connected to the transceiver unit.

[0043] The transceiver unit is configured to receive a first request message from the network device, the first request being used to request the CCM to associate a target customized container cluster management characteristic with the target container cluster, the first request message including identification information of the target customized container cluster management characteristic and identification information of the target container cluster, and the network device being a consumer entity of the CCM.

[0044] The processing unit is configured to associate the target customized container cluster management characteristics with the target container cluster based on the first request message.

[0045] With reference to the third aspect, in some implementation methods of the third aspect, the first request message further includes scope information of the association operation, and the scope information of the association operation indicates that the target customized container cluster management characteristics are applied to all naming spaces in the target container cluster, or the scope information of the association operation indicates that the target customized container cluster management characteristics are applied to several naming spaces in the target container cluster, and the first request message further includes identification information of the several naming spaces.

[0046] Referring to the third aspect, in some implementation methods of the third aspect, the first request message further includes information regarding consumers that are within the target container cluster and that use the target customized container cluster management characteristics, and the consumers that use the target customized container cluster management characteristics are control plane functional entities and / or user plane functional entities.

[0047] With reference to the third aspect, in some implementation manners of the third aspect, the transceiver unit is further configured to send a first response message to the network device, wherein the first response message indicates that the target customized container cluster management characteristics have been successfully associated with the target container cluster.

[0048] With reference to the third aspect, in some implementation manners of the third aspect, the transceiver unit is further configured to receive a second request message from the network device, the second request being used to request the CCM to load an object file, the second request message including specific information, the specific information being for determining the object file, and the object file including configuration, state and policy information for deploying and executing target customized container cluster management properties.

[0049] The processing unit is further configured to determine the object file based on the second request message, and to verify whether the object file is loadable.

[0050] The processing unit is further configured to load the object file when the object file is loadable.

[0051] The transceiver unit is further configured to send a second response message to the network device, the second response message indicating that the CCM successfully loaded the object file.

[0052] Referring to the third aspect, in some implementation methods of the third aspect, the object file is a management container cluster object declaration descriptor (MDD) file, and the specific information includes identification information of the object file and / or storage path information of the object file.

[0053] With reference to the third aspect, in some implementation manners of the third aspect, the transceiver unit is further configured to receive a third request message from the network device, the third request being used to request the CCM to create a target customized container cluster management characteristic, and the third request message includes specific information.

[0054] The processing unit is further configured to determine the object file based on the third request message.

[0055] The processing unit is further configured to create a target object instance based on the deployment information in the object file, where the target object instance corresponds to the target customization container cluster management characteristics.

[0056] The transceiver unit is further configured to send a third response message to the network device, the third response message indicating that the CCM has successfully created the target customized container cluster management property, and the third response message including identification information of the target object instance.

[0057] With reference to the third aspect, in some implementation manners of the third aspect, the transceiver unit is further configured to receive a fourth request message from the network device, the fourth request being used to request disassociation of the target customized container cluster management characteristics from the target container cluster, and the fourth request message includes identification information of the target customized container cluster management characteristics and identification information of the target container cluster.

[0058] The processing unit is further configured to disassociate the target customized container cluster management property from the target container cluster based on the fourth request message.

[0059] The transceiver unit is further configured to send a fourth response message to the network device, the fourth response message indicating that the CCM has successfully disassociated the target customized container cluster management characteristic from the target container cluster.

[0060] With reference to the third aspect, in some implementation schemes of the third aspect, the transceiver unit is further configured to receive a fifth request message from the network device, the fifth request being used to request deletion of a target customized container cluster management characteristic, and the fifth request message including identification information of the target customized container cluster management characteristic.

[0061] The processing unit is further configured to delete the target customized container cluster management property based on the fifth request message.

[0062] The transceiver unit is further configured to send a fifth response message to the network device, the fifth response message indicating that the CCM has successfully deleted the target customized container cluster management characteristic.

[0063] According to a fourth aspect, there is provided a network device including a transceiver unit and a processing unit connected to the transceiver unit.

[0064] The processing unit is configured to determine to associate a target customized container cluster management characteristic with the target container cluster.

[0065] The transceiver unit is configured to send a first request message to the container cluster management CCM, the first request being used to request the CCM to associate a target customized container cluster management characteristic with the target container cluster, and the first request message including identification information of the target customized container cluster management characteristic and identification information of the target container cluster.

[0066] Network devices are consumer entities in the CCM.

[0067] With reference to the fourth aspect, in some implementation methods of the fourth aspect, the first request message further includes scope information of the association operation, and the scope information of the association operation indicates that the target customized container cluster management characteristics are applied to all naming spaces in the target container cluster, or the scope information of the association operation indicates that the target customized container cluster management characteristics are applied to several naming spaces in the target container cluster, and the first request message further includes identification information of the several naming spaces.

[0068] Referring to the fourth aspect, in some implementation methods of the fourth aspect, the first request message further includes information regarding consumers that are within the target container cluster and that use the target customized container cluster management characteristics, and the consumers that use the target customized container cluster management characteristics are control plane functional entities and / or user plane functional entities.

[0069] With reference to the fourth aspect, in some implementation schemes of the fourth aspect, the transceiver unit is further configured to receive a first response message from the CCM, the first response message indicating that the target customized container cluster management characteristics have been successfully associated with the target container cluster.

[0070] With reference to the fourth aspect, in some implementations of the fourth aspect, the processing unit is further configured to determine an object file, the object file including configuration, state and policy information for deploying and executing target customized container cluster management properties.

[0071] The transceiver unit is further configured to send a second request message to the CCM, the second request being used to request the CCM to load an object file, the second request message including specific information, the specific information being for determining the object file.

[0072] The transceiver unit is further configured to receive a second response message from the CCM, the second response message indicating that the CCM has successfully loaded the object file.

[0073] Referring to the fourth aspect, in some implementation methods of the fourth aspect, the object file is a management container cluster object declaration descriptor (MDD) file, and the specific information includes identification information of the object file and / or storage path information of the object file.

[0074] Referring to the fourth aspect, in some implementations of the fourth aspect, the processing unit is further configured to determine to create a target customized container cluster management property.

[0075] The transceiver unit is further configured to send a third request message to the CCM, the third request being used to request the CCM to create a target customized container cluster management characteristic, and the third request message including specific information.

[0076] The transceiver unit is further configured to receive a third response message from the CCM, the third response message indicating that the CCM has successfully created the target customized container cluster management property, the third response message including identification information of the target object instance, the target object instance corresponding to the target customized container cluster management property.

[0077] Referring to the fourth aspect, in some implementations of the fourth aspect, the processing unit is further configured to determine to disassociate the target customized container cluster management property from the target container cluster.

[0078] The transceiver unit is further configured to send a fourth request message to the CCM, the fourth request being used to request disassociation of the target customized container cluster management characteristics from the target container cluster, and the fourth request message including identification information of the target customized container cluster management characteristics and identification information of the target container cluster.

[0079] The transceiver unit is further configured to receive a fourth response message from the CCM, the fourth response message indicating that the CCM has successfully disassociated the target customized container cluster management property from the target container cluster.

[0080] With reference to the fourth aspect, in some implementations of the fourth aspect, the processing unit is further configured to determine to remove the target customized container cluster management property.

[0081] The transceiver unit is further configured to send a fifth request message to the CCM, the fifth request being used to request deletion of the target customized container cluster management characteristic, and the fifth request message including identification information of the target customized container cluster management characteristic.

[0082] The transceiver unit is further configured to receive a fifth response message from the CCM, the fifth response message indicating that the CCM has successfully deleted the target customized container cluster management property.

[0083] According to a fifth aspect, there is provided a communication device including a communication interface and a processor. When the communication device operates, the processor executes a computer program or instructions stored in a memory, thereby causing the communication device to perform the method in either of the possible implementations of the first or second aspect. The memory may be located in the processor, or may be realized by a chip separate from the processor. This is not particularly limited in this application.

[0084] According to a sixth aspect, there is provided a computer-readable storage medium containing a computer program which, when run on a computer, enables the computer to carry out the method of either the first or second aspect in any possible implementation manner.

[0085] According to a seventh aspect, there is provided a chip, wherein a processing circuit is disposed on the chip, the processing circuit being configured to perform the method of either the first aspect or the second aspect in any possible implementation manner.

[0086] According to an eighth aspect, there is provided a computer program product, which includes a computer program (which may also be referred to as code or instructions), which, when executed, enables a computer to carry out the method of either the first aspect or the second aspect in any possible implementation manner. [Brief explanation of the drawings]

[0087] [Figure 1] 1 shows a system to which this application is applicable. [Figure 2] 1 shows a system to which this application is applicable. [Figure 3] 1 is a schematic flow chart of the solution according to the present application; [Figure 4] 1 is a schematic block diagram of a communication device according to the present application; [Figure 5] 1 is a schematic block diagram of a communication device according to the present application; DETAILED DESCRIPTION OF THE INVENTION

[0088] Below, the technical solutions in the embodiments of this application are described with reference to the accompanying drawings.

[0089] First, a system to which the embodiments of this application can be applied will be described with reference to FIGS.

[0090] A network functions virtualization (NFV) system mainly includes the following functional entities:

[0091] Network Functions Virtualization Orchestrator (NFVO): The NFVO is primarily responsible for the lifecycle management of network services (NSs) and the allocation and scheduling of virtual resources in the network functions virtualization infrastructure (NFVI). The NFVO may communicate with one or more virtualized network function managers (VNFMs) to perform operations related to instantiating NSs. For example, the NFVO may send corresponding configuration information to the VNFMs and request state information of one or more virtualized network functions (VNFs) from the VNFMs. Additionally, the NFVO may further communicate with a virtualized infrastructure manager (VIM) to allocate and / or reserve resources in the NFVIs, exchange resource configurations, state information, etc.

[0092] VNFM: A VNFM is primarily responsible for lifecycle management of one or more VNFs, e.g., instantiating a VNF, updating a VNF, querying a VNF, scaling a VNF, terminating a VNF, etc. A VNFM may communicate with a VNF to manage the lifecycle of the VNF and exchange configuration information, state information, etc. with the VNF. It may be understood that an NFV system may include one or more VNFMs, with each VNFM performing lifecycle management separately for different types of VNFs.

[0093] NFVI: NFVI is the infrastructure of an NFV system and includes hardware components, software components, and combinations thereof to establish a virtualized environment and help deploy, manage, and realize VNFs in the virtualized environment. NFVI may include at least computing hardware, storage hardware, and network hardware. The virtualization layer of NFVI may abstract the above hardware and decouple it from VNFs to obtain corresponding virtual computing resources, virtual storage resources, and virtual network resources, thereby providing virtualized machines (VMs) and other forms of virtualized containers to VNFs.

[0094] VIM: The VIM is mainly configured to control and manage interactions between VNFs and computing hardware, storage hardware, network hardware, virtual computing resources, virtual storage resources, and virtual network resources. For example, the VIM may perform resource management functions, such as adding corresponding virtual resources to a virtual machine or other form of virtualization container, collecting fault information of NFVIs in the system execution process, etc. Furthermore, the VIM may communicate with the VNFM, such as receiving resource allocation requests from the VNFM and feeding back resource configuration and status information to the VNFM.

[0095] VNF: An NFV system may include one or more VNFs (and typically multiple VNFs), running one or more virtual machines or other forms of virtualized containers, corresponding to groups of network functions originally implemented by dedicated devices.

[0096] Element management system (EMS): An EMS may be configured to configure and manage VNFs and initiate lifecycle management operations such as instantiating new VNFs into a VNFM. It may be understood that an NFV system may include one or more EMSs.

[0097] Operations support system (OSS) or business support system (BSS): An OSS / BSS may support various end-to-end telecommunications services. Management functions supported by an OSS may include network configuration, service provisioning, fault management, etc. A BSS may be configured to process related services such as orders, payments, and revenues, and support functions such as product management, order management, revenue management, and customer management. It should be noted that an OSS / BSS may be used as a service requester to request an NFVO to instantiate an NS, and the OSS / BSS or the computing device on which the OSS / BSS relies may be correspondingly referred to as a service requester in general.

[0098] It may be understood that in the NFV system shown in Figure 1, the above functional entities may be located in different computing devices, or some functional entities may be integrated into the same computing device, but this is not limited thereto.

[0099] Furthermore, the transformation of telecommunication networks is undergoing an evolution from NFV to cloud-native. Cloud-native is a new system realization paradigm for building, running, and managing software in a cloud environment. Cloud-native refers to an architectural implementation that fully utilizes cloud infrastructure and platform services, adapts to the cloud environment, and has key characteristics such as (micro)service orientation, scalability, distribution, high availability, multitenancy, and automation. In this transformation, the introduction of container management into the NFV management and orchestration (MANO) reference architecture is an important part of the implementation of NFV evolving to cloud-native. Therefore, the following two new logical functions are introduced into the NFV MANO system, as shown in Figure 2:

[0100] Container infrastructure service management (CISM): CISM is also called CaaS management. The open source prototype of CISM is Kubernetes. CISM is responsible for managing container objects invoked by containerized VNFs, including creating, updating, and deleting container objects, and scheduling container objects to corresponding node resources in the container cluster node resource pool managed by CISM. CISM is also responsible for managing container infrastructure service (CIS) instances in container user plane processes.

[0101] Container Cluster Management (CIS Cluster Management, CCM): CCM is also called CIS cluster management. CCM is responsible for managing container clusters, including creating node resource pools used by the container cluster and scaling nodes, for example, allocating new virtualized or bare-metal machines (BMs) within a specified container cluster node resource pool.

[0102] It should be understood that both the CISM and the CCM are independent logical functions. In the function deployment process, the CCM and the CISM may be located in different physical entities, for example, the CISM is deployed in the VNFM and the CCM is deployed in the VIM, or the CCM and the CISM may be co-located in the same physical entity, for example, both are deployed in the VNFM.

[0103] Currently, container cluster management characteristics are deployed to container clusters in a static configuration manner. For example, in the process of creating a container cluster, certain container cluster management characteristics may be added to the container cluster, and in the process of deleting a container cluster, the container cluster management characteristics used by the container cluster are deleted accordingly, thereby realizing a tight coupling between the container cluster management characteristics and the container cluster. However, deploying container cluster management characteristics in a static configuration manner cannot meet carrier requirements, especially in an environment where the container cluster is applied to a multi-tenant management environment. Carriers urgently need a method for dynamically deploying container cluster management characteristics to container clusters based on their operational management requirements.

[0104] Based on this, this application provides a communication method 300 as shown in Fig. 3 to realize dynamic deployment of container cluster management features. The method 300 is applicable to the systems shown in Fig. 1 and Fig. 2. For ease of explanation, an example in which the consumer entity of the CCM is an NFVO is used in the following description. The method 300 includes the following steps:

[0105] S310: The NFVO decides to associate customized container cluster management characteristic #1 (an example of a target customized container cluster management characteristic) with container cluster #1 (an example of a target container cluster).

[0106] If possible, the NFVO may decide to associate customized container cluster management characteristic #1 with container cluster #1 based on requirements (e.g., based on policies of the carrier deploying the container cluster).

[0107] For example, initially, the policy of the carrier deploying container cluster #1 is that container cluster #1 is not associated with customized container cluster management characteristic #1. Subsequently, the carrier's policy for container cluster #1 is adjusted to associate container cluster #1 with customized container cluster management characteristic #1. In this case, the NFVO may decide to associate customized container cluster management characteristic #1 with container cluster #1 based on the adjusted policy for container cluster #1.

[0108] Below is an example of Customized Container Cluster Management Property #1.

[0109] Example 1

[0110] The customized container cluster management characteristic #1 may be a container cluster enhanced characteristic (CIS cluster enhanced characteristic, CCEC), and the open source community prototype of the characteristic is a Kubernetes custom resource definition (CRD). To meet new requirements for deploying containerized VNFs or for operating additional container cluster functions (e.g., auxiliary container network for virtualized environments), the container cluster may support adding new enhanced characteristic functions to the baseline characteristic capability set of the container cluster. The container cluster enhanced characteristic CCEC may be applied to the container cluster to realize advanced characteristics and operations in the container cluster. For example, a container cluster enhanced characteristic (a characteristic for selecting an appropriate container network interface (CNI) plug-in in the container cluster network for auxiliary purposes) is added to a CISM instance to extend the CISM northbound application programming interface (API).

[0111] Example 2

[0112] Customized container cluster management feature #1 may be a daemon workload, also called a daemon object. The open-source community prototype of the feature is the Kubernetes daemon set. A Kubernetes daemon set loads a daemon for a specific purpose (e.g., collecting logs or monitoring status) onto a CIS cluster node to monitor the running status of the CIS cluster node. The daemon load is configured to deploy a customized container cluster management feature with the same functionality to all applicable container cluster nodes. The following is an example of using daemon workloads: a managed CIS cluster object (MCCO) instance runs on each container cluster node to collect logs, an MCCO instance runs on each container cluster node to monitor the node status, and an MCCO instance runs on each container cluster node to dynamically configure routing information. A CISM instance uses daemon workloads to simultaneously control groups of daemons across different container clusters.

[0113] It should be understood that the customized container cluster management characteristic #1 may alternatively be other examples, which are not limited in this application, and may be a specific process (e.g., a specific binary process).

[0114] S320: The NFVO sends a first request message to the CCM, where the first request is used to request that the customized container cluster management characteristic #1 be associated with the container cluster #1. In response, the CCM receives the first request message.

[0115] The first request message includes identification information of the customized container cluster management characteristic #1 and identification information of the container cluster #1.

[0116] Optionally, the first request message is one of the following: Scope information for the association action and information about consumers using customized container cluster management feature #1 in container cluster #1 It may further include one or more of:

[0117] For example, the scope information of the association operation may indicate that customized container cluster management property #1 is associated with all name spaces within container cluster #1.

[0118] In another example, the scope information of the association operation may indicate that the customized container cluster management property #1 is associated with several naming spaces within the container cluster #1, in which case the first request message further includes identification information of the several naming spaces.

[0119] A consumer of customized container cluster management characteristic #1 may be a functional entity within container cluster #1. For example, the functional entity may be a control plane functional entity (e.g., a CISM entity) within container cluster #1. In another example, the functional entity may be a user plane functional entity (e.g., a CIS entity) within container cluster #1. In yet another example, the functional entity may be a control plane functional entity and a user plane functional entity within container cluster #1.

[0120] S330: The CCM associates the customized container cluster management characteristic #1 with the container cluster #1 based on the first request message.

[0121] In one possible scheme, the CCM may create a list (shown as List #1) of customized container cluster management characteristics associated with container cluster #1, and the CCM may add identification information for customized container cluster management characteristic #1 to List #1, thereby causing customized container cluster management characteristic #1 to be associated with container cluster #1.

[0122] Optionally, the CCM may further configure the type of consumer that uses the customized container cluster management characteristic #1 in the container cluster #1 based on the first request message.

[0123] For example, the CCM may configure the control plane functional entities in container cluster #1 using customized container cluster management characteristic #1.

[0124] In another example, the CCM may configure user plane functional entities within container cluster #1 using customized container cluster management characteristic #1.

[0125] In yet another example, the CCM may use customized container cluster management characteristic #1 to configure both control plane functional entities and user plane functional entities within container cluster #1.

[0126] Optionally, before the CCM associates the customized container cluster management characteristic #1 with the container cluster #1, the CCM may further send a request message #A to the NFVO, which is used to request the NFVO to allow the NFVO to allocate an infrastructure resource (denoted as infrastructure resource #1) for deploying the customized container cluster management characteristic #1 to the container cluster #1. For example, the infrastructure resource #1 may be a virtualized machine resource or a bare machine resource. In some cases, the NFVO may send a response message #A to the CCM, which indicates that the infrastructure resource #1 is authorized to be allocated in the container cluster #1. Furthermore, the CCM sends a request message #B to the VIM, which requests that the infrastructure resource #1 be allocated to the customized container cluster management characteristic #1 in the container cluster #1. The VIM allocates the corresponding infrastructure resource #1 in the container cluster #1 based on the request message #B. This process is similar to the resource management granting process of VNF life cycle management (LCM) operations.

[0127] According to the solution of this application, the CCM may receive a first request message from the NFVO and associate the customized container cluster management characteristic #1 with the container cluster #1 based on the first request message. In this way, dynamic deployment of the container cluster management characteristic is realized, and carrier requirements are better met. Furthermore, the solution for realizing dynamic deployment of the container cluster management characteristic of this application does not need to perform interaction between the CCM and the CISM, thereby avoiding an increase in integration costs for interoperation between functions of the container platform layer in a multi-vendor environment.

[0128] Optionally, at S340, the CCM sends a first response message to the NFVO, where the first response message indicates that the customized container cluster management characteristic #1 has been successfully associated with the container cluster #1.

[0129] Optionally, before S310, the method 300 further includes S301 to S309.

[0130] S301: The NFVO determines File #1 (an exemplary object file).

[0131] File #1 is a template file that contains configuration, state and policy information for deploying and running customized container cluster management feature #1.

[0132] For example, file #1 is a managed container cluster object (MCCO) declarative descriptor (MDD) file. MCCO is an abstract NFV object used in the container cluster management process, and the characteristics of the MCCO are expressed as its configuration, state, requested and allocated infrastructure resources, and applicable operational policies. Based on the applicability and functional scope of the MCCO object, the MCCO may represent a managed object in the following scenarios: a group of associated containers running on a container user plane CIS instance, or a configuration object in a container management plane CISM instance.

[0133] The CCM is responsible for the lifecycle management of the MCCO by requesting the CISM to create and deploy the MCCO, install the MCCO in a container cluster, remove the MCCO from a container cluster, etc., for example, by using a daemon workload object. Additionally, since an MCCO instance consumes compute, network, and / or storage resources of a CIS cluster, the CCM is also responsible for requesting the NFVO to enable the deployment of resources required by the MCCO instance. The CCM: (a) enhancing or adding a group of container cluster management features; (b) supporting container cluster management processes, e.g., enabling or ensuring container cluster deployment; Responsible for.

[0134] The MDD is a template file that describes the basic characteristics of an MCCO. For example, the expected state of the MCCO is included in the file. The MDD file may be realized by using a native descriptor template file used by the open source community. Specifically, file #1 contains the following information: Compute, storage, and network resource information required to deploy customized container cluster management feature #1, role-based access control (RBAC) information for a security authentication mechanism that deploys access to customized container cluster management feature #1, and information about a cloud provider controller that monitors the execution of customized container cluster management feature #1. Contains one or more of the following.

[0135] If possible, the carrier may configure File #1 for the NFVO, and the NFVO may store File #1 in the corresponding storage space.

[0136] S302: The NFVO sends a second request message to the CCM, the second request is used to request the CCM to load file #1, and the second request message includes information #A for determining file #1.

[0137] For example, information #A includes the identification information of file #1.

[0138] In another example, information #A includes access path information for file #1.

[0139] S303: The CCM determines file #1 based on information #A and verifies whether file #1 can be loaded.

[0140] For example, the CCM may verify the authentication mechanisms of file #1 in the container cluster, such as the integrity, authenticity, validity, and availability of file #1. The CCM may further verify whether the enforcement attributes of file #1 are ready.

[0141] If possible, file #1 can be loaded if the integrity and / or authenticity and / or validity and / or availability and / or enforceability of file #1 in the container cluster meets pre-set conditions.

[0142] S304: When file #1 is available for loading, the CCM loads (onboards) file #1.

[0143] If possible, the CCM may store file #1 in a corresponding storage space, which may be a local storage space of the CCM or a storage space of another device. It should be understood that the CCM has permission to access the storage space.

[0144] It should be understood that if file #1 is not loadable, the CCM will not load file #1.

[0145] Optionally, at S305, the CCM sends a second response message to the NFVO, where the second response message indicates whether the CCM successfully loaded file #1.

[0146] It should be understood that S301 to S305 may alternatively exist independently, in other words, other steps in this application may not be included after S301 to S305.

[0147] S306: The NFVO determines that customized container cluster management property #1 needs to be created.

[0148] If possible, the NFVO may determine, based on requirements (e.g., based on the policies of the carrier deploying the container cluster), that a customized container cluster management characteristic #1 needs to be created.

[0149] S307: The NFVO sends a third request message to the CCM, where the third request is used to request creation of customized container cluster management property #1. In response, the CCM receives the third request message.

[0150] The third request message includes the identification information of file #1.

[0151] S308: The CCM creates a customized container cluster management property #1 based on the third request message.

[0152] Specifically, the CCM may access file #1 based on the identification information of file #1 in the third request message, analyze the deployment information of object instance #1 in file #1, and create object instance #1 based on the deployment information of object instance #1. This object instance #1 corresponds to customized container cluster management characteristic #1. In other words, object instance #1 is an abstract representation of customized container cluster management characteristic #1.

[0153] For example, object instance #1 may be managed container cluster object (MCCO) instance #1.

[0154] Optionally, at S309, the CCM sends a third response message to the NFVO, where the third response message indicates that the CCM has successfully created the customized container cluster management property #1.

[0155] The third response message includes the identification information of object instance #1 (eg, MCCO instance #1).

[0156] It should be understood that S306 to S309 may alternatively exist independently, in other words, other steps in this application may not be included before or after S306 to S309.

[0157] Optionally, after S340, the method 300 further includes S341 to S344.

[0158] S341: The NFVO decides to disassociate customized container cluster management characteristic #1 from container cluster #1.

[0159] If possible, the NFVO may decide to disassociate customized container cluster management characteristic #1 from container cluster #1 based on requirements (e.g., based on policies of the carrier deploying the container cluster).

[0160] "Disassociate" should be understood to mean removing an association relationship.

[0161] S342: The NFVO sends a fourth request message to the CCM, where the fourth request is used to request the CCM to disassociate the customized container cluster management characteristic #1 from the container cluster #1. In response, the CCM receives the fourth request message.

[0162] The fourth request message includes the identification information of the customized container cluster management characteristic #1 and the identification information of the container cluster #1.

[0163] S343: The CCM disassociates the customized container cluster management property #1 from the container cluster #1 based on the fourth request message.

[0164] In an optional manner, the CCM may remove the identification information of customized container cluster management characteristic #1 from the above list #1.

[0165] According to the solution of the present application, the CCM may receive a fourth request message from the NFVO, and complete the disassociation between the customized container cluster management characteristic #1 and the container cluster #1 based on the fourth request message. In comparison, in the solution of the present application, the customized container cluster management characteristic can be dynamically disassociated from the container cluster without a container cluster deletion process, thereby better meeting the changing container cluster management requirements of the carrier.

[0166] Optionally, at S344, the CCM sends a fourth response message to the NFVO, where the fourth response message indicates that the CCM has successfully disassociated the customized container cluster management characteristic #1 from the container cluster #1.

[0167] It should be understood that steps S341 to S344 may alternatively exist independently. For example, steps S341 to S344 are not executed based on steps S310 to S340. In other words, before disassociating customization management characteristic #1 from container cluster #1, the CCM does not have to execute steps S310 to S340 to dynamically associate customization management characteristic #1 with container cluster #1.

[0168] Optionally, after S344, the method 300 further includes S345 to S348.

[0169] S345: The NFVO decides to delete customized container cluster management characteristic #1.

[0170] If possible, the NFVO may decide to remove customized container cluster management characteristic #1 based on requirements (e.g., based on a policy for deploying container clusters by a carrier).

[0171] S346: The NFVO sends a fifth request message to the CCM, where the fifth request is used to request to delete the customized container cluster management property #1. In response, the CCM receives the fifth request message.

[0172] The fifth request message includes the identification information of customized container cluster management characteristic #1.

[0173] S347: The CCM deletes the customized container cluster management characteristic #1 based on the fifth request message.

[0174] It should be understood that when S347 is executed based on S343, in other words, when S347 is executed, there is no container cluster that uses the customized container cluster management property #1, and in this case, the customized container cluster management property #1 may be directly deleted.

[0175] In other cases, if S347 is not performed based on S343, the CCM needs to determine whether there is a container cluster that uses customized container cluster management characteristic #1. For example, the CCM determines that container cluster #1 uses customized container cluster management characteristic #1. In this case, the CCM may first disassociate customized container cluster management characteristic #1 from container cluster #1, and then delete customized container cluster management characteristic #1.

[0176] Optionally, at S348, the CCM sends a fifth response message to the NFVO, where the fifth response message indicates that the CCM has successfully deleted customized container cluster management characteristic #1.

[0177] It should be understood that steps S345 to S348 may alternatively exist independently. For example, steps S345 to S348 are not executed based on steps S310 to S340. In other words, before deleting customization management characteristic #1, the CCM does not have to execute steps S310 to S340 to dynamically associate customization management characteristic #1 with container cluster #1.

[0178] According to the above method, Figure 4 shows a communication device according to an embodiment of this application. The communication device includes a transceiver unit 401 and a processing unit 402.

[0179] The transceiver unit 401 may be configured to implement corresponding communication functions. The transceiver unit 401 may also be referred to as a communication interface or a communication unit. The processing unit 402 may be configured to perform processing operations.

[0180] Optionally, the device may further include a storage unit, which may be configured to store instructions and / or data. The processing unit 402 may read the instructions and / or data in the storage unit, thereby causing the device to implement the device operations in the above method embodiments.

[0181] In a first design, the device may be the CCM in the above embodiments, or may be a component (such as a chip) of the CCM.

[0182] The transceiver unit is configured to receive a first request message from the network device, the first request being used to request the CCM to associate target customized container cluster management characteristics with the target container cluster, and the processing unit is configured to associate the target customized container cluster management characteristics with the target container cluster based on the first request message.

[0183] In some cases, the transceiver unit is further configured to send a first response message to the network device, the first response message indicating that the target customized container cluster management characteristic has been successfully associated with the target container cluster.

[0184] In other cases, the transceiver unit is further configured to receive a second request message from the network device, the second request being used to request the CCM to load the object file. The processing unit is further configured to determine the object file based on the second request message and verify whether the object file is loadable, and the processing unit is further configured to load the object file when the object file is loadable. The transceiver unit is further configured to send a second response message to the network device, the second response message indicating that the CCM has successfully loaded the object file.

[0185] In other cases, the transceiver unit is further configured to receive a third request message from the network device, the third request being used to request the CCM to create a target customized container cluster management property. The processing unit is further configured to determine an object file based on the third request message. The processing unit is further configured to create a target object instance based on deployment information in the object file. The transceiver unit is further configured to send a third response message to the network device, the third response message indicating that the CCM has successfully created the target customized container cluster management property, the third response message including identification information of the target object instance.

[0186] In other cases, the transceiver unit is further configured to receive a fourth request message from the network device, the fourth request being used to request disassociating the target customized container cluster management property from the target container cluster. The processing unit is further configured to disassociate the target customized container cluster management property from the target container cluster based on the fourth request message. The transceiver unit is further configured to send a fourth response message to the network device, the fourth response message indicating that the CCM has successfully disassociated the target customized container cluster management property from the target container cluster.

[0187] In other cases, the transceiver unit is further configured to receive a fifth request message from the network device, the fifth request being used to request deleting the target customized container cluster management property. The processing unit is further configured to delete the target customized container cluster management property based on the fifth request message. The transceiver unit is further configured to send a fifth response message to the network device, the fifth response message indicating that the CCM has successfully deleted the target customized container cluster management property.

[0188] In the second design, the device may be the NFVO in the above embodiments, or may be a component (such as a chip) of the NFVO.

[0189] The processing unit is configured to determine to associate the target customized container cluster management characteristic with the target container cluster. The transceiver unit is configured to send a first request message to the container cluster management CCM, the first request being used to request the CCM to associate the target customized container cluster management characteristic with the target container cluster.

[0190] In some cases, the processing unit is further configured to determine the object file. The transceiver unit is further configured to send a second request message to the CCM, the second request being used to request the CCM to load the object file. The transceiver unit is further configured to receive a second response message from the CCM, the second response message indicating that the CCM has successfully loaded the object file.

[0191] In other cases, the processing unit is further configured to determine to create the target customized container cluster management property. The transceiver unit is further configured to send a third request message to the CCM, the third request being used to request the CCM to create the target customized container cluster management property. The transceiver unit is further configured to receive a third response message from the CCM, the third response message indicating that the CCM has successfully created the target customized container cluster management property.

[0192] In other cases, the processing unit is further configured to determine to disassociate the target customized container cluster management property from the target container cluster. The transceiver unit is further configured to send a fourth request message to the CCM, the fourth request being used to request to disassociate the target customized container cluster management property from the target container cluster. The transceiver unit is further configured to receive a fourth response message from the CCM, the fourth response message indicating that the CCM has successfully disassociated the target customized container cluster management property from the target container cluster.

[0193] In other cases, the processing unit is further configured to determine to delete the target customized container cluster management property. The transceiver unit is further configured to send a fifth request message to the CCM, where the fifth request is used to request to delete the target customized container cluster management property. The transceiver unit is further configured to receive a fifth response message from the CCM, where the fifth response message indicates that the CCM has successfully deleted the target customized container cluster management property.

[0194] It should be understood that the specific processes by which the units perform the above corresponding steps have been described in detail in the above method embodiments, and for the sake of brevity, the details will not be described again here.

[0195] It should also be understood that the apparatus herein may be embodied in the form of a functional unit. The term "unit" herein may refer to an application-specific integrated circuit (ASIC), an electronic circuit, a processor (e.g., a shared processor, a dedicated processor, or a group processor) and memory configured to execute one or more software or firmware programs, a merge logic circuit, and / or other suitable components supporting the described functionality. In an optional example, those skilled in the art may understand that the apparatus may specifically be the first network element in the above embodiment and may be configured to perform procedures and / or steps corresponding to the first network element in the above method embodiment. Alternatively, the apparatus may specifically be the network management network element in the above embodiment and may be configured to perform procedures and / or steps corresponding to the network management network element in the above method embodiment. To avoid repetition, the details will not be described again here.

[0196] The communication device has functions for implementing corresponding steps performed by the device in the above-mentioned methods. The functions may be implemented by using hardware, or by executing corresponding software by the hardware. The hardware or software includes one or more modules corresponding to the above-mentioned functions. For example, a transceiver unit may be replaced by a transceiver (e.g., a transmitting unit in a transceiver unit may be replaced by a transmitter, and a receiving unit in a transceiver unit may be replaced by a receiver) and other units such as a processing unit may be replaced by a processor to separately perform transmitting and receiving operations and related processing operations in each method embodiment.

[0197] Furthermore, the transceiver unit 401 may be a transceiver circuit (eg, may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit.

[0198] It should be noted that the device in Fig. 4 may be the device in the above method embodiment, or may be a chip or a chip system, such as a system on chip (SoC). The transceiver unit may be an input / output circuit or a communication interface. The processing unit may be a processor, a microprocessor, or an integrated circuit integrated on a chip, which is not limited here.

[0199] An embodiment of the present application further provides a communication device. As shown in Fig. 5, the communication device includes a processor 501 and a communication interface 502. The processor 501 is configured to execute a computer program or instructions stored in a memory 503, or to read data stored in the memory 503, to perform the method in the above method embodiments. Optionally, there are one or more processors 501. The communication interface 502 is configured to receive and / or transmit signals. For example, the processor 501 is configured to control the communication interface 502 to receive and / or transmit signals.

[0200] Optionally, as shown in Figure 5, the communication device further includes a memory 503, which is configured to store computer programs or instructions and / or data. The memory 503 may be integrated with the processor 501 or may be located separately. Optionally, there are one or more memories 503.

[0201] Optionally, the processor 501, the communication interface 502, and the memory 503 are connected to each other through a bus 504. The bus 504 may be a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, etc. The bus 504 may be categorized into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in FIG. 5 for representation, but this does not indicate that only one bus or only one type of bus is present.

[0202] In the solution, the communication device is configured to implement the operations performed by the CCM or the NFVO in the above method embodiments.

[0203] For example, the processor 501 is configured to execute computer programs or instructions stored in the memory 503 to implement the relevant operations of the CCM in the above method embodiments.

[0204] In another example, the processor 501 is configured to execute computer programs or instructions stored in the memory 503 to implement the relevant operations of the NFVO in the above method embodiments.

[0205] It should be understood that the processors (such as processor 501) referred to in this embodiment of this application may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP. The processor may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field programmable gate array (FPGA), a generic logic array (GAL), or any combination thereof.

[0206] It should be further understood that the memory referred to in this embodiment of this application (e.g., memory 503) may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. Nonvolatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM), used as an external cache.

[0207] Those skilled in the art should easily recognize that the units and algorithm steps in the examples described with reference to the embodiments disclosed herein can be realized by electronic hardware, or a combination of computer software and electronic hardware. Whether a function is implemented in the form of hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to realize the described functions for each specific application. However, the implementation should not be considered to go beyond the scope of the embodiments of this application.

[0208] Those skilled in the art can clearly understand that for the purpose of convenient and concise description, the detailed operation processes of the above systems, devices and units may be referred to the corresponding processes in the above method embodiments, and the details will not be described again here.

[0209] In some embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be realized in other ways. For example, the described device embodiments are merely schematic. For example, the division into units is merely a logical division of functions. In actual applications, other division methods may exist. For example, multiple units or components may be combined or integrated into other systems, or some features may be ignored or not implemented. Furthermore, the shown or discussed mutual couplings or direct couplings or communication connections may be realized by using some interfaces. Indirect couplings or communication connections between devices or units may be realized in electronic, mechanical, or other forms.

[0210] Units described as separate parts may or may not be physically separate, and parts shown as units may or may not be physical units, and may be located in one place or distributed across multiple network units. Some or all of the units may be selected based on actual requirements to achieve the objectives of the solutions of the embodiments.

[0211] Furthermore, the functional units in the embodiments of this application may be integrated into one processing unit, or each of the units may exist physically alone, or two or more units may be integrated into one unit.

[0212] When a function is realized in the form of a software functional unit and sold or used as an independent product, the function may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application may essentially, or a portion of the technical solution or a portion of the technical solution may be realized in the form of a software product. A computer software product is stored in a storage medium and includes some instructions for instructing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method described in the embodiments of this application. The above storage medium includes any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0213] The above description is merely a specific implementation of this application and is not intended to limit the scope of protection of this application. Any variations or replacements that can be easily conceived by those skilled in the art within the technical scope disclosed in this application shall fall within the scope of protection of this application. Therefore, the scope of protection of this application shall be subject to the scope of protection of the claims.

Claims

1. 1. A communication method comprising: receiving, by a container cluster management (CCM), a first request message from a network device, the first request message being used to request the CCM to associate a target customized container cluster management characteristic with a target container cluster, the target customized container cluster management characteristic corresponding to a custom resource definition (CRD), the first request message including identification information of the target customized container cluster management characteristic and identification information of the target container cluster, the network device being a network function virtualization orchestrator (NFVO); associating, by the CCM, the target customized container cluster management characteristics with the target container cluster based on the first request message; A method comprising:

2. the first request message further includes applicability information of the association operation; the applicability information of the association operation indicates that the target customized container cluster management characteristics apply to all namespaces within the target container cluster; or The method of claim 1 , wherein the scope information of the association operation indicates that the target customized container cluster management characteristics apply to several namespaces within the target container cluster.

3. The method of claim 2 , wherein the first request message further includes identification information of the number of naming spaces.

4. The method of claim 1, wherein the first request message further includes information about consumers that are in the target container cluster and that use the target customized container cluster management characteristics, and the consumers that use the target customized container cluster management characteristics are control plane functional entities and / or user plane functional entities.

5. The method comprises:

2. The method of claim 1, further comprising: sending, by the CCM, a first response message to the network device, the first response message indicating that the target customized container cluster management characteristics have been successfully associated with the target container cluster.

6. Before receiving a first request message from the network device by the CCM, the method includes: receiving, by the CCM, a second request message from the network device, the second request message being used to request the CCM to load an object file, the second request message including specific information for determining the object file, the object file including configuration, state, and policy information for deploying and executing the target customized container cluster management characteristics; determining, by the CCM, the object file based on the second request message, and verifying whether the object file can be loaded; loading the object file when the object file is loadable by the CCM; sending, by the CCM, a second response message to the network device, the second response message indicating that the CCM successfully loaded the object file; The method of claim 1 further comprising:

7. The method of claim 6 , wherein the object file is a Managed Container Cluster Object Declaration Descriptor (MDD) file, and the specific information includes identification information of the object file and / or storage path information of the object file.

8. After loading the object file by the CCM, the method comprises: receiving, by the CCM, a third request message from the network device, the third request message being used to request the CCM to create the target customized container cluster management characteristics, the third request message including the specific information; determining, by the CCM, the object file based on the third request message; creating, by the CCM, a target object instance based on deployment information in the object file, the target object instance corresponding to the target customization container cluster management characteristics; sending, by the CCM, a third response message to the network device, the third response message indicating that the CCM has successfully created the target customized container cluster management property, the third response message including identification information of the target object instance; The method of claim 6 further comprising:

9. After associating the target customized container cluster management characteristics with the target container cluster by the CCM, the method includes: receiving, by the CCM, a fourth request message from the network device, the fourth request message being used to request disassociation of the target customized container cluster management characteristic from the target container cluster, the fourth request message including the identification information of the target customized container cluster management characteristic; disassociating, by the CCM, the target customized container cluster management characteristics from the target container cluster based on the fourth request message; sending, by the CCM, a fourth response message to the network device, the fourth response message indicating that the CCM has successfully disassociated the target customized container cluster management property from the target container cluster; The method of claim 1 further comprising:

10. After the CCM disassociates the target customized container cluster management property from the target container cluster, the method further comprises: receiving, by the CCM, a fifth request message from the network device, the fifth request message being used to request deleting the target customized container cluster management property, the fifth request message including the identification information of the target customized container cluster management property; deleting, by the CCM, the target customized container cluster management characteristic based on the fifth request message; sending, by the CCM, a fifth response message to the network device, the fifth response message indicating that the CCM has successfully deleted the target customized container cluster management property; The method of claim 9 further comprising:

11. 1. A communication method comprising: determining, by the network device, to associate a target customized container cluster management characteristic with the target container cluster; sending, by the network device, a first request message to a container cluster management (CCM), the first request message being used to request the CCM to associate the target customized container cluster management characteristic with the target container cluster, the target customized container cluster management characteristic corresponding to a custom resource definition (CRD), the first request message including identification information of the target customized container cluster management characteristic and identification information of the target container cluster, the network device being a network function virtualization orchestrator (NFVO); A method comprising:

12. the first request message further includes applicability information of the association operation; the applicability information of the association operation indicates that the target customized container cluster management characteristics apply to all namespaces within the target container cluster; or The method of claim 11 , wherein the scope information of the association operation indicates that the target customized container cluster management characteristics apply to several namespaces within the target container cluster.

13. The method of claim 12 , wherein the first request message further includes an identification of the number of naming spaces.

14. The method of claim 11, wherein the first request message further includes information about consumers that are in the target container cluster and that use the target customized container cluster management characteristics, and the consumers that use the target customized container cluster management characteristics are control plane functional entities and / or user plane functional entities.

15. The method comprises:

12. The method of claim 11, further comprising: receiving, by the network device, a first response message from the CCM, the first response message indicating that the target customized container cluster management characteristics have been successfully associated with the target container cluster.

16. The method comprises: determining, by the network device, an object file, the object file including configuration, state, and policy information for deploying and executing the target customized container cluster management features; sending a second request message to the CCM by the network device, the second request message being used to request the CCM to load the object file, the second request message including specific information for determining the object file; receiving, by the network device, a second response message from the CCM, the second response message indicating that the CCM successfully loaded the object file; The method of claim 11 further comprising:

17. The method of claim 16 , wherein the object file is a Managed Container Cluster Object Declaration Descriptor (MDD) file, and the specific information includes identification information of the object file and / or storage path information of the object file.

18. The method comprises: determining, by the network device, to create the target customized container cluster management characteristics; sending a third request message to the CCM by the network device, the third request message being used to request the CCM to create the target customized container cluster management characteristics, the third request message including the specific information; receiving, by the network device, a third response message from the CCM, the third response message indicating that the CCM has successfully created the target customized container cluster management property, the third response message including identification information of a target object instance, the target object instance corresponding to the target customized container cluster management property; 17. The method of claim 16, further comprising:

19. The method comprises: determining, by the network device, to disassociate the target customized container cluster management characteristic from the target container cluster; sending a fourth request message to the CCM by the network device, the fourth request message being used to request disassociation of the target customized container cluster management characteristic from the target container cluster, the fourth request message including the identification information of the target customized container cluster management characteristic; receiving, by the network device, a fourth response message from the CCM, the fourth response message indicating that the CCM has successfully disassociated the target customized container cluster management property from the target container cluster; The method of claim 11 further comprising:

20. The method comprises: determining, by the network device, to remove the target customized container cluster management characteristic; sending a fifth request message to the CCM by the network device, the fifth request message being used to request deleting the target customized container cluster management property, the fifth request message including the identification information of the target customized container cluster management property; receiving, by the network device, a fifth response message from the CCM, the fifth response message indicating that the CCM has successfully deleted the target customized container cluster management property; 20. The method of claim 19 further comprising:

21. A communication device comprising a unit adapted to carry out the method according to any one of claims 1 to 10.

22. A communication device comprising a unit adapted to carry out the method of any one of claims 11 to 20.

23. A communication system comprising an apparatus according to claim 21 and an apparatus according to claim 22.

24. A communication device including a communication interface and a processor, A communications device, wherein the processor is configured to execute computer programs or instructions, thereby causing the communications device to perform a method according to any one of claims 1 to 20.

25. A computer-readable storage medium containing a computer program or instructions, A computer readable storage medium, the computer program or instructions being executable on a computer to enable the computer to carry out the method of any one of claims 1 to 20.

26. A computer program comprising instructions, A computer program product, the instructions of which, when executed on a computer, enable the computer to carry out the method of any one of claims 1 to 20.

Images