Communication method and communication apparatus

Abstract

The application provides a communication method and a communication device, which can be applied to the field of communication. In the technical scheme, the producer entity in the telecommunication cloud architecture can determine a basic information model required for the NFV object to change from an actual state to an expected state based on the expected state and the actual state of the NFV object, and determine an LCM operation instruction based on the required basic information model, so as to avoid the low efficiency of the process of determining the LCM operation instruction caused by determining the LCM operation instruction based on the full information of the expected state.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to communication methods and communication devices. Background Technology

[0002] In the evolution of Network Function Virtualization (NFV) architecture towards a new future telecom cloud architecture, the new architecture's declarative system design greatly simplifies the interface functions in the original NFV management and orchestration architecture. Lifecycle management (LCM) operations are introduced into communication systems to ensure that NFV services can flexibly and efficiently respond to ever-changing network demands and service challenges. The method for determining LCM operation instructions uses NFV descriptors in conjunction with declarative interfaces to translate the "desired state" of NFV objects. However, existing methods for determining LCM operation instructions suffer from low efficiency. Therefore, improving the efficiency of determining LCM operation instructions remains a pressing issue that needs to be addressed. Summary of the Invention

[0003] The communication method and communication device provided in this application enable the producer entity to determine LCM operation instructions based on the set of basic information models required to indicate the change of NFV objects from their actual state to their desired state, thereby improving the efficiency of determining LCM operation instructions.

[0004] Firstly, this application provides a communication method that can be implemented by a producer entity.

[0005] This communication method includes: receiving first information, the first information being used to indicate the desired state of a Network Function Virtualization (NFV) object; determining a first basic information model set of the NFV object based on the first information, the first basic information model set being used to indicate the change of the NFV object from its actual state to its desired state; and sending a first message based on the first basic information model set, the first message being used to instruct the NFV object to perform Lifecycle Management (LCM) operations.

[0006] For example, NFV objects can be network services (NS), virtualized network functions (VNF), container infrastructure service clusters (CISC), managed container infrastructure service objects (MCIO), managed container cluster objects (MCCO), etc.

[0007] As will be understood by those skilled in the art, the desired state is the state that the consumer entity expects the NFV object to reach after the producer entity performs the LCM operation.

[0008] As will be understood by those skilled in the art, the actual state is the current state of the NFV object as monitored by the producer entity.

[0009] In this design, the producer entity determines the first basic information model set based on the expected state of the NFV object, and determines the LCM operation instructions based on the first basic information model set. By reducing the number of information units that need to be loaded to determine the LCM operation instructions, the efficiency of determining the LCM operation instructions is improved.

[0010] In one possible design, determining the first basic information model set of the NFV object based on the first information includes determining an information unit set, the information unit set containing at least one information unit of the NFV object, the information in the information unit set corresponding to the desired state being different from the information in the information unit set corresponding to the actual state, and determining the first basic information model set based on the information in the information unit set and the information in the information unit set corresponding to the desired state.

[0011] It can be understood that the expected state and actual state of an NFV object are collections of information units. The information units included in the expected state and actual state of an NFV object correspond one-to-one. That is, the expected state and actual state of an NFV object are represented by a set of information units with the same name but different values.

[0012] In this design, the first basic information model is determined based on the different information units in the expected state and the actual state of the NFV object. These different information units are the information units required for the NFV object to change from the actual state to the expected state. Based on these required information units, the LCM operation instructions are determined. By reducing the number of information units that need to be loaded to determine the LCM operation instructions, the efficiency of determining the LCM operation instructions is improved.

[0013] In one possible design, the communication method further includes: receiving second information, the second information being used to indicate a second basic information model set, the first basic information model set being a subset of the second basic information model set, and the second basic information model set containing all or part of the information units in the NFV descriptor.

[0014] For example, the second information includes a basic information model of telecommunications cloud infrastructure resources.

[0015] In this design, the producer entity receives a second set of basic information models to determine the first set of basic information models. It selects the required basic information models from the second set of basic information models to form the first set of basic information models, thus determining the first set of basic information models.

[0016] In one possible design, this communication method further includes: the basic information models in the second set of basic information models do not contain the same information units.

[0017] This design ensures that there are no identical information units between basic information models by limiting the overlap between them, thus preventing the same information units from being transmitted multiple times and improving the efficiency of information unit transmission between basic information models.

[0018] In one possible design, this communication method further includes: acquiring third information, which indicates the actual state of the NFV object.

[0019] In this design, the producer entity determines the actual state of the NFV object by obtaining third-party information.

[0020] For example, obtaining third-party information can be achieved by a producer entity obtaining third-party information from VIM through methods such as subscribing to notifications (push) or querying (pull).

[0021] For example, the third piece of information could be the status of infrastructure resource objects, such as the occupancy status of computing node resources, storage resources, or network resources in the current telecommunications cloud infrastructure.

[0022] In one possible design, the producer entity includes Telecom Cloud Infrastructure Management (TCIM).

[0023] In one possible design, the producer entity is TCIM or container cluster management (or container infrastructure service cluster management, CCM).

[0024] This design uses TCIM as the producer entity, realizing the application of this method in a telecom cloud architecture.

[0025] In one possible design, NFV objects include container clusters.

[0026] In this design, a container cluster is selected as the NFV object, and LCM operation is implemented when the NFV object is a container cluster.

[0027] In one possible design, the desired state of a container cluster includes one or more of the following information elements: container cluster category, container cluster node architecture, container cluster deployment sample, container cluster version, or container cluster access control information.

[0028] In this design, when the NFV object is a container cluster, the information unit content of the expected state ensures a comprehensive description of the expected state of the container cluster.

[0029] In one possible design, the basic information model set of the container cluster includes one or more of the following basic information models: a metadata description of the container cluster, a description of the container cluster nodes required to make up the member instances of the container cluster, a description of the container cluster storage resources, and / or, a description of the container cluster network resources.

[0030] This design defines which basic information models can be included in the basic information model set when the NFV object is a container cluster, thus enabling the description of the container cluster at the basic information model level.

[0031] In one possible design, this communication method further includes: first information carried in an application operation request message.

[0032] This design achieves the transmission of the first information by sending the first information through the application operation request, thereby realizing the consistency of the results of multiple operations by modeling the expected state of the NFV object.

[0033] Secondly, this application provides a communication method that can be implemented by a consumer entity.

[0034] This communication method includes: determining second information, the second information being used to indicate a second basic information model set, the second basic information model set containing all or part of the information units in the NFV descriptor, and sending the second information to the producer entity.

[0035] The producer entity receives a second set of basic information models to determine the first set of basic information models. It selects the required basic information models from the second set of basic information models to form the first set of basic information models, thus determining the first set of basic information models.

[0036] In one possible design, the basic information models in the second set of basic information models do not contain the same information units.

[0037] For example, the second set of basic information models may include the following basic information models:

[0038] Metadata of the infrastructure resource object information model includes information elements such as: the name, identifier, design vendor, and version of the information model;

[0039] The resource requirements information of infrastructure resource objects includes the following information units: resource specifications (deployment template flavor) of container cluster nodes and identification information of other associated infrastructure resource objects;

[0040] Information about container cluster nodes includes: CPU specifications, memory size, identifiers of associated storage resource objects, software images, etc.

[0041] Information about container cluster storage resources includes the following information units: type and size of storage resource objects, and identifier of associated container cluster nodes;

[0042] Information about container cluster network resources includes information elements such as the type of network connection object, protocol, and quality of service (QoS).

[0043] In one possible design, the consumer entity includes telco cloud application management (TCAM), or network functions virtualization orchestrator (NFVO), or operation support systems (OSS) / business support systems (BSS), or telco cloud platform (TCP) components.

[0044] In one possible design, the consumer entity is TCAM, NFVO, or OSS / BSS.

[0045] This design uses TCIM as the producer entity, realizing the application of this method in a telecom cloud architecture.

[0046] Thirdly, this application provides a communication device. This communication device can execute modules corresponding to the methods / operations / steps / actions described in the first aspect or any possible implementation thereof. These modules can be hardware circuits, software, or a combination of hardware circuits and software.

[0047] In one design, the device may include a processing module and a communication module. The communication module is used to perform the sending and receiving actions in the method described in the first aspect or any possible implementation thereof, while the processing module is used to perform the processing actions involved in the method described in the first aspect or any possible implementation thereof.

[0048] In one design, the device can be a producer entity, or a device, module, circuit, or chip configured in the producer entity, or a device that can be used in conjunction with the producer entity.

[0049] Fourthly, this application provides a communication device. This communication device may include modules corresponding to the methods / operations / steps / actions described in the second aspect or any possible implementation thereof.

[0050] In one design, the device may include a processing module and a communication module. The communication module is used to perform the sending and receiving actions in the method described in the second aspect or any possible implementation thereof, while the processing module is used to perform the processing actions involved in the method described in the second aspect or any possible implementation thereof.

[0051] In one design, the device can be a consumer entity, or a device, module, circuit, or chip configured in the consumer entity, or a device that can be used in conjunction with the consumer entity.

[0052] Fifthly, an apparatus is provided, including a processor, wherein instructions, when executed by the processor, cause a method as described in the first aspect or any possible implementation thereof to be implemented.

[0053] Optionally, the device may further include a storage medium that stores the instructions executed by the processor.

[0054] A sixth aspect provides an apparatus including a processor, wherein instructions, when executed by the processor, cause the method as described in the second aspect or any possible implementation thereof to be implemented.

[0055] Optionally, the device may further include a storage medium that stores the instructions executed by the processor.

[0056] In a seventh aspect, a chip is provided, including processing circuitry for running a program or instructions to cause the methods described in the first aspect or any possible implementation thereof to be implemented.

[0057] Optionally, the chip may further include a memory for storing programs or instructions.

[0058] Optionally, the chip may also include the transceiver circuit, or an input / output interface.

[0059] Eighthly, a chip is provided, including processing circuitry for running a program or instructions to implement a method as described in the second aspect or any possible implementation thereof.

[0060] Optionally, the chip may further include a memory for storing programs or instructions.

[0061] Optionally, the chip may also include the transceiver circuit, or an input / output interface.

[0062] A ninth aspect provides a computer-readable storage medium comprising instructions that, when executed by a processor, cause the method as described in the first aspect or any possible implementation thereof to be implemented.

[0063] In a tenth aspect, a computer-readable storage medium is provided, the computer-readable storage medium including instructions that, when executed by a processor, cause the method as described in the second aspect or any possible implementation thereof to be implemented.

[0064] Eleventhly, a computer program product is provided, the computer program product including computer program code or instructions, which, when the computer program code or instructions are run, cause the method as described in the first aspect or any possible implementation thereof to be implemented.

[0065] In a twelfth aspect, a computer program product is provided, the computer program product comprising computer program code or instructions that, when the computer program code or instructions are executed, cause the method as described in the second aspect or any possible implementation thereof to be implemented.

[0066] In a thirteenth aspect, a communication system is provided, comprising: means for performing the first aspect or any possible implementation thereof, and means for performing the second aspect or any possible implementation thereof.

[0067] It is understood that the technical effects of any of the second to thirteenth aspects of this application can be referred to the relevant content in the first aspect, and will not be repeated here. Attached Figure Description

[0068] Figure 1 This is a schematic diagram illustrating the principle of an NFV descriptor according to an embodiment of this application;

[0069] Figure 2 This is a flowchart illustrating a communication method according to an embodiment of this application;

[0070] Figure 3 This is a flowchart illustrating another communication method according to an embodiment of this application;

[0071] Figure 4 This is a schematic diagram illustrating a specific NFV object communication method according to an embodiment of this application;

[0072] Figure 5 This is a schematic diagram illustrating another specific NFV object communication method according to an embodiment of this application;

[0073] Figure 6 This is a flowchart illustrating yet another communication method according to an embodiment of this application;

[0074] Figure 7 This is a diagram illustrating the relationship between an NFV service and an NFV object according to an embodiment of this application.

[0075] Figure 8 This is a schematic diagram of the structure of a communication device according to an embodiment of this application;

[0076] Figure 9 This is a schematic diagram of another communication device according to an embodiment of this application. Detailed Implementation

[0077] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0078] To facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0079] It should be noted that, in the embodiments of this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design scheme described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0080] In this application embodiment, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and / or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0081] The existing NFV technology framework is based on the NFV Management and Orchestration (MANO) architecture, developed by the NFV industry standards group under the European Telecommunications Standards Institute (ETSI) since 2013. After more than a decade of development, the NFV-MANO architecture has seen an increasing number of functional components, leading to more complex interoperability between these layered and decoupled components and difficulties in system integration. Therefore, starting in 2023, the ETSI NFV organization began researching the future evolution architecture of NFV telecom clouds. The new architecture prioritizes the principle of "architectural simplification," correspondingly applying more declarative APIs to reduce the complexity of interface interoperability.

[0082] The basic idea of ​​using declarative APIs in the new architecture of NFV telecom cloud is as follows: First, determine the managed objects in the NFV telecom cloud management domain, such as network service NS, container clusters, VNFs, etc. The attribute associated with the managed object is the object's "desired state"; then, submit the description of the managed object's "desired state" in the declarative API, and then "apply" the update to achieve the desired state of the managed object.

[0083] As those skilled in the art will understand, in industry-standard declarative API practices, such as the Cloud Native Computing Foundation (CNCF) open-source container orchestration system (Kubernetes), users declare the "desired state" of resource objects by writing manifest files in YAML or Jason format for Kubernetes resources. These files are submitted by users to the Kubernetes API server, where the controller and scheduler execute corresponding operational procedures based on the resource definitions, such as creating, updating, or deleting the corresponding Kubernetes resources, ensuring that the actual state of the Kubernetes cluster matches the "desired state" of the resource objects in the manifest files.

[0084] A key feature of existing NFV technologies is that LCM (Limited-Time Management) of managed objects is based on information in the NFV Descriptor. For example, during the lifecycle management of a Virtual Network Function (VNF), the Network Function Virtualisation Orchestrator (NFVO) or VNF Manager (VNFM) invokes virtual resource management functions from the Virtualized Infrastructure Manager (VIM). This is done by accessing the VNF Descriptor (VNFD) and its descriptions of the VNF's compute resource requirements, as well as descriptions of specific hardware resource requirements (such as acceleration), to determine the virtual machine resources used by the VNF instance. The NFVO then authorizes the virtual machine resources used for LCM operations through the VNF lifecycle management licensing process. In short, an NFV descriptor is a deployment template for an NFV object (e.g., a Network Service, VNF). This template is typically defined in the design phase of the NFV object and contains descriptions of the requirements during the NFV object's runtime activities (e.g., deployment and operation of the object instance).

[0085] The working principle of NFV descriptors is as follows: Figure 1As shown, the NFV descriptor is first created by the NFV descriptor designer. This includes defining the resource requirements and configuration parameters of the Virtual Network Function (VNF). The designed NFV descriptor is then delivered to the Operations Support System (OSS) / Business Support System (BSS), a system used by telecom operators to manage network services and customer orders. Next, the OSS / BSS loads the NFV descriptor into the NFV-MANO system. This step imports the descriptor information into the MANO system for subsequent use.

[0086] The NFV-MANO system uses information from the NFV descriptor to create local NFV object instances. During the creation of an NFV object instance, the MANO system creates an Info image of the NFV object. The Info image is instance information formed after the NFV object is instantiated; this instance information contains the information model required by the NFV object instance in runtime.

[0087] When the new NFV architecture adopts a declarative system design, the original NFV-MANO interface functionality will be greatly simplified. It will no longer define interface operations that are sticky to specific NFV object API endpoints, such as instantiation of object A, resource scaling of object B, creation of object C, and updating of object D. Correspondingly, the declarative API design adopts a unified operation form: the API consumer entity defines the "desired state" of an object, and then passes this desired state to the API producer entity. The API producer then uses its internal operation execution sequence to bring the system state to the desired state of the object.

[0088] The translation process of the "desired state" of an NFV object between the translation entity and the execution entity can use the existing NFV-MANO interface functionality. The execution entity creates an NFV object instance identifier based on the full description information of the NFV object in the NFV descriptor. For each LCM operation of the NFV object, the configuration information needs to be updated and stored by referring to the full description of the object in the NFV descriptor.

[0089] like Figure 2 The diagram shows a flowchart of a method according to an embodiment of this application, including S201, S202, S203 and S204, wherein the execution entities are a consumer entity and a producer entity. The producer entity includes a translation entity and an execution entity, wherein the translation entity is responsible for converting high-level expected states into specific operation instructions, which are used by the execution entity to manage NFV objects; the execution entity actually performs LCM operations according to the instructions provided by the translation entity.

[0090] S201, the consumer entity sends an application operation request (the desired state of the NFV object), and the corresponding producer entity receives the application operation request.

[0091] For example, a consumer entity (such as Telecom Cloud Application Management (TCAM) first defines the desired state of an NFV object, which typically involves the configuration and deployment requirements of a network service or Virtual Network Function (VNF). It then sends a request to the producer entity to apply this desired state.

[0092] S202, Translate the entity to load the NFV object descriptor into the execution entity.

[0093] For example, upon receiving a request, the producer entity (such as Telecom Cloud Infrastructure Management (TCIM) loads the corresponding NFV object descriptor. These descriptors contain detailed information about the NFV object, such as resource requirements and configuration parameters.

[0094] S203, The translation entity creates an NFV object instance identifier and loads the NFV object instance identifier into the execution entity.

[0095] For example, the producer entity creates an identifier for the NFV object instance based on the loaded descriptor. This identifier is used to uniquely identify and manage the NFV object instance, facilitating effective management and tracking within the TCIM management system.

[0096] S204, Translate the entity to determine the LCM operation for the NFV object instance and load the LCM operation into the execution entity.

[0097] For example, a producer entity performs LCM operations on an NFV object instance. These operations may include instantiating, configuring, starting, monitoring, updating, scaling up or down, or terminating the NFV object instance.

[0098] Understandably, after the translation entity loads the instructions into the execution entity, the execution entity will reply with a response to indicate that the operation instructions were successfully received.

[0099] However, the structural complexity and completeness of the NFV descriptor itself make the process of TCIM determining LCM operation instructions based on the NFV descriptor of the expected state very inefficient. This leads to increased costs in maintaining NFV descriptors during declarative API operations. To address this, this application proposes a method whereby, when a consumer entity initiates a declarative management operation request for an NFV object to a producer entity, the producer entity combines the basic information model of the telecom cloud infrastructure resource object with the "expected state" description of the NFV object in the request message to form an NFV descriptor that supports the state migration of the NFV object. This descriptor then interacts with the management entity to execute the management operation of the NFV object, ultimately achieving the expected state of the NFV object in the request message.

[0100] like Figure 3 The diagram illustrates a communication method according to an embodiment of this application, including steps S303, S304, and S305. This method is executed by a consumer entity, a producer entity, and a management entity.

[0101] S303, the consumer entity sends a first message, which indicates the desired state of the NFV object. The corresponding producer entity receives the first message.

[0102] In some implementations, the first information is carried in the application operation request message.

[0103] For example, the consumer entity can be TCAM as the sender of the interface, and the producer entity can be TCIM as the receiver of the interface.

[0104] For example, an NFV object can be a container cluster or a managed container cluster object (MCCO).

[0105] Taking an NFV object as an example of a container cluster, the expected or actual state can contain the following information units:

[0106] Metadata of the container cluster, such as: cluster name, ID, display name alias, tag, creation time, etc.

[0107] The specifications of container clusters include: cluster types, providing a multi-scenario, highly stable container runtime environment based on a high-performance network model, such as: virtual machine deployment clusters, bare metal server deployment clusters, hybrid deployment clusters, CPU node deployment clusters (general computing), GPU / NPU node deployment clusters (intelligent computing), and CPU / GPU / NPU heterogeneous node hybrid deployment clusters.

[0108] The cluster master node architecture can be x86, ARM, etc.

[0109] Cluster deployment specifications (flavors), such as: single control node cluster, multi-control point (high availability) cluster, small (50 nodes), medium (200 nodes), large (1000 nodes), and ultra-large scale (2000 nodes);

[0110] Cluster version and cluster platform version information; host network information and container network information, including network type and network segment address information; cluster API access control information.

[0111] S304, the producer entity determines the first basic information model set of the NFV object based on the first information. The first basic information model set is used to indicate the change of the NFV object from the actual state to the desired state.

[0112] In some implementations, the producer entity obtains third-party information that indicates the actual state of the NFV object.

[0113] For example, obtaining third-party information could be a producer entity periodically checking the actual state of an NFV object, or subscribing to notifications (push) / queries (pull) about the actual state of an NFV object.

[0114] For example, the third piece of information could be the status of infrastructure resource objects, such as the occupancy status of computing node resources, storage resources, or network resources in the current telecommunications cloud infrastructure.

[0115] An exemplary first set of basic information models may include the following basic information models:

[0116] Metadata of the infrastructure resource object information model includes information elements such as: the name, identifier, design vendor, and version of the information model;

[0117] The resource requirements information of infrastructure resource objects includes the following information units: resource specifications (deployment template flavor) of container cluster nodes and identification information of other associated infrastructure resource objects;

[0118] Information about container cluster nodes includes: CPU specifications, memory size, identifiers of associated storage resource objects, software images, etc.

[0119] Information about container cluster storage resources includes the following information units: type and size of storage resource objects, and identifier of associated container cluster nodes;

[0120] Information about container cluster network resources includes information elements such as the type, protocol, and QoS of network connection objects.

[0121] In some implementations, the producer entity determines a set of information units, which contains at least one information unit of an NFV object. The information in the set of information units corresponding to the desired state is different from the information in the set of information units corresponding to the actual state. A first basic information model set is determined based on the information units and the information in the set of information units corresponding to the desired state.

[0122] For example, the information unit set includes the cluster size. The information for the cluster size corresponding to the expected state is a medium-sized cluster of 200 nodes, while the information for the cluster size corresponding to the actual state is a small-sized cluster of 50 nodes. It can be determined that this information is different. The cluster size is a subset of the basic information model of container cluster specifications, so the required basic information model set includes container cluster specifications.

[0123] S305, a first message is sent based on the first basic information model set. The first message is used to instruct the NFV object to perform an LCM operation. The corresponding management entity receives the first message.

[0124] For example, sending a first message based on a first set of basic information models could mean that the first message contains the first set of basic information models.

[0125] For example, the parameters in the first message are determined based on the information units in the first basic information model set.

[0126] For example, the management entity can be an entity used to maintain and manage NFV objects, such as container cluster management (CCM) or container infrastructure service management (CISM).

[0127] For example, taking an NFV object as a container cluster, the "desired state" of the container cluster object includes a container cluster category of a hybrid deployment of virtual machines and bare metal servers. The information unit deployment flavor in the first basic information set indicates that a medium-sized multi-control point cluster is being deployed. Then, TCIM searches the VIM resource pool for virtual machine nodes and bare metal server nodes that match the resource requirements of a multi-control point (high availability) cluster and checks the availability status of these node resources:

[0128] If the available virtual machine nodes and bare metal server nodes found meet the resource requirements of the target container cluster and the number of nodes is of medium size, then TCIM sends a container cluster lifecycle management operation request to CCM as the first message, and the request message carries the identification information of the available virtual machine nodes and bare metal server nodes found.

[0129] If the available virtual machine nodes and bare metal server nodes found meet the resource requirements of the target container cluster, but the number of nodes is lower than medium scale, then TCIM will combine the basic information models of the virtual machine nodes and bare metal server nodes to be newly created to form a container cluster description information model (CCD) that meets the current scenario, and send a container cluster lifecycle management operation request to CCM as the first message. The request message carries the identification information of the available virtual machine nodes and bare metal server nodes found, as well as the identification information of the combined CCD.

[0130] If no available virtual machine nodes and bare metal server nodes are found that meet the resource requirements of the target container cluster, TCIM will combine the basic information models of the virtual machine nodes and bare metal server nodes to be created, as well as the basic information models of the associated storage and network resources, to form a container cluster description information model (CCD) that meets the current scenario. TCIM will then send a container cluster lifecycle management operation request to CCM as the first message, with the request message carrying the combined CCD identification information.

[0131] Optionally, this communication method may also include S301.

[0132] S301, the consumer entity determines the second information, which is used to indicate the second basic information model set, the first basic information model set is a subset of the second basic information model set, and the second basic information model set contains all or part of the information units in the NFV descriptor.

[0133] For information on the basic information models included in the second set of basic information models, please refer to the description of the first set of basic information models in S304.

[0134] For example, determining the second set of basic information models can be done by dividing the full descriptors of NFV objects into different basic information models according to the basic information models in S304.

[0135] In some implementations, the basic information models in the second basic information model set do not contain the same information units.

[0136] It is understandable that, in order to avoid the repeated loading of the same information units, different basic information models are limited to not containing the same basic information model.

[0137] Optionally, this communication method may also include S302.

[0138] S302, the consumer entity sends the second information. The corresponding producer entity receives the second information.

[0139] For example, the second information includes a basic information model of telecommunications cloud infrastructure resources.

[0140] For example, the consumer entity sending a second message could be the consumer entity loading a basic information model of the telecommunications cloud infrastructure resources into the producer entity.

[0141] The following section describes the specific process of this application embodiment using a specific NFV object as an example.

[0142] like Figure 4 The diagram illustrates a communication method according to an embodiment of this application, where the NFV object is a container cluster, including S401 to S407. This method is executed by TCAM, TCIM, CCM, and VIM.

[0143] S401, TCAM sends an application operation request message (the "desired state" of the container cluster object, including the specifications and / or capacity of the container cluster object's infrastructure resources and deployment constraints). Correspondingly, TCIM receives the application operation request message.

[0144] This step can be referred to in the description of the expected state in S303, and will not be repeated here.

[0145] S402, VIM sends the status of the infrastructure resource object, and the corresponding TCIM receives the status of the infrastructure resource object.

[0146] This step can be referred to in the explanation of obtaining the desired state in S304, and will not be repeated here.

[0147] S403, TCIM determines the infrastructure resource objects for state transition of container cluster objects in declarative operations based on the state of infrastructure resources, and combines the basic information models of infrastructure resource objects to form a container cluster descriptor (CCD).

[0148] This step can refer to the method for determining the first message in S305, and will not be repeated here.

[0149] S404, TCIM sends a container cluster LCM operation, which includes a CCD identifier. The corresponding CCM receives the container cluster LCM operation.

[0150] S405, CCM performs corresponding container cluster management operations based on the CCD identifier.

[0151] For example, these operations may include instantiating, configuring, starting, monitoring, updating, scaling up or down, or terminating NFV container cluster objects.

[0152] S406, CCM sends a response to the container cluster LCM operation. Correspondingly, TCIM receives the response to the container cluster LCM operation.

[0153] S407, TCIM confirms that the desired state of the container cluster object has been achieved after receiving the response.

[0154] like Figure 5 The diagram illustrates a communication method according to an embodiment of this application, where the NFV object is a managed container cluster object (MCCO), including steps S501 to S507. This method is executed by TCAM, TCIM, CISM, and VIM.

[0155] S501, TCAM sends an application operation request message (specifications and / or capacity of the infrastructure resources of the MCCO object, deployment constraints message). Correspondingly, TCIM receives the application operation request message.

[0156] This step can be referred to in the description of the expected state in S303, and will not be repeated here.

[0157] S502, VIM sends the status of the infrastructure resource object, and the corresponding TCIM receives the status of the infrastructure resource object.

[0158] This step can be referred to in the explanation of obtaining the desired state in S304, and will not be repeated here.

[0159] S503, TCIM determines the infrastructure resource objects for MCCO object state transitions in declarative operations based on the status of infrastructure resources, and combines the basic information models of infrastructure resource objects to form MCCO description information.

[0160] This step can refer to the method for determining the first message in S305, and will not be repeated here.

[0161] S504, TCIM sends an MCCO management operation request, which includes MCCO description and identification information. The corresponding CCM receives the MCCO management operation request.

[0162] S505, CISM performs corresponding MCCO management operations based on the MCCO description information.

[0163] For example, these operations may include instantiating, configuring, starting, monitoring, updating, scaling up or down, or terminating MCCO objects.

[0164] S506, CCM sends an MCCO management operation response. Correspondingly, TCIM receives the MCCO management operation response.

[0165] S507, after receiving the response, TCIM confirms that the expected state of MCCO has been achieved.

[0166] like Figure 6The present invention illustrates a communication method according to an embodiment of the present application, wherein the executing entities are a consumer entity and a producer entity, including steps S601 to S604.

[0167] S601, analyze the operational requirements of the consumer entity management service, and select atomic NFV descriptors from the NFV descriptor set according to the operations, and match the combined NFV descriptors with the operational requirements of the management service.

[0168] For example, the consumer entity can be OSS / BSS, and the producer entity can be TCAM.

[0169] This step refers to the process of selecting the basic information model in S304, and will not be repeated here.

[0170] S602, the consumer entity loads the combined NFV descriptor. The corresponding producer entity receives the NFV descriptor.

[0171] S603, Consumer entity calls management service.

[0172] S604, the producer entity executes the corresponding operation of the management service based on the combined NFV descriptor information model.

[0173] This step can be referred to as the process of determining the first message in S305, and will not be repeated here.

[0174] Figure 7 This illustrates the relationship between NFV services and NFV objects under the NFV-MANO service architecture in this application embodiment.

[0175] This includes NFV services under a service-oriented architecture, such as NFV descriptor loading, lifecycle management, performance management, and fault management, as well as NFV objects under a service-oriented architecture, such as VNFD, NSD, VNF packets, network services (NS), and VNFs. In this method, NFV services and NFV objects can be combined according to the needs of management operations; for example, performing LCM operations on VNFs or loading operations on VNF packets. When performing the same NFV service operation on different NFV objects, the operation method of the NFV service is standardized, and the same NFV service does not need to be defined repeatedly for different NFV objects.

[0176] Figure 8 This is a schematic diagram of the structure of a communication device according to an embodiment of this application. Figure 8 As shown, the communication device 800 may include a processing module 810 and a communication module 820.

[0177] As a first example, device 800 can be used to implement Figures 3 to 6The embodiment shown illustrates a communication method implemented by a producer entity. For example, processing module 810 is used to implement... Figures 3 to 6 The embodiments shown depict processing steps performed by the producer entity, implemented by the communication module 820. Figures 3 to 6 The embodiments shown depict steps such as sending and / or receiving performed by the producer entity.

[0178] For example, the processing module 810 can determine the first basic information model set of the NFV object based on the first information.

[0179] For example, the communication module 820 can receive first information, send a first message, or receive second information.

[0180] As a second example, device 800 can be used to implement Figures 3 to 6 The embodiments shown illustrate a communication method implemented by a consumer entity. For example, processing module 810 is used to implement... Figures 3 to 6 The steps related to the processing performed by the consumer entity in the illustrated embodiment are implemented by the communication module 820. Figures 3 to 6 The embodiments shown depict steps such as sending and / or receiving performed by a consumer entity.

[0181] For example, the processing module 810 can determine the second information.

[0182] For example, the communication module 820 can send a first message or a second message to the producer entity.

[0183] Figure 9 This is a schematic diagram of the structure of a communication device provided in another embodiment of this application, which can realize this application. Figures 3 to 6 The communication method shown is as follows. Figure 9 As shown, the communication device 900 includes a processor 910 and a communication circuit 920. The processor 910 and the communication circuit 920 are coupled to each other. It is understood that the communication circuit 920 can be a transceiver or an input / output interface.

[0184] Optionally, the communication device 900 may further include a memory 930 for storing instructions executed by the processor 910, or storing input data required for the processor 910 to execute instructions, or storing data generated after the processor 910 executes instructions. It is understood that the memory 930 may be located externally to the processor 910, or internally to the processor 910.

[0185] As an example, processor 910 is used to implement the functions of the processing module 810 described above, and communication circuit 920 is used to implement the functions of the communication module 820 described above.

[0186] The communication device 900 can be a producer entity or a chip applied in a producer entity.

[0187] It is understandable that when the communication device 900 is a producer entity, the communication circuit 920 can be a transceiver. When the communication device 900 is a chip, the communication circuit 920 can be an input / output interface.

[0188] The communication device 900 can be a consumer entity or a chip used in a consumer entity.

[0189] It is understandable that when the communication device 900 is a consumer entity, the communication circuit 920 can be a transceiver. When the communication device 900 is a chip, the communication circuit 920 can be an input / output interface.

[0190] In some embodiments of this application, a computer program product is also provided, which, when run on a processor, can implement the methods implemented by the producer entity in any of the above embodiments, or can implement the methods implemented by the consumer entity in any of the above method embodiments.

[0191] In some embodiments of this application, a computer-readable storage medium is also provided, which contains computer instructions that, when executed on a processor, can implement the methods implemented by the producer entity in any of the above embodiments, or the methods implemented by the consumer entity in any of the above method embodiments.

[0192] In some embodiments of this application, a communication system is also provided, which can implement the methods implemented by the producer entity and the consumer entity in any of the above embodiments.

[0193] It is understood that the processor in the embodiments of this application may be any of the following devices or all or part of the circuitry used for processing functions: a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0194] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Additionally, the ASIC can reside in a network device or terminal device. Alternatively, the processor and storage medium can exist as discrete components in a consumer entity or terminal device.

[0195] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive.

[0196] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0197] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A communication method, characterized in that, Applied to producer entities, the method includes: Receive first information, which is used to indicate the desired state of the Network Function Virtualization (NFV) object; Based on the desired state and the actual state of the NFV object, a set of information units is determined, which includes information units whose values ​​are different from those of the actual state. Based on the set of information units, a first set of basic information models is determined. The first set of basic information models is used to indicate the change of the NFV object from the actual state to the desired state. A first message is sent based on the first basic information model set. The first message is used to instruct the NFV object to perform a lifecycle management (LCM) operation; wherein the number of information units that need to be loaded for the LCM operation is reduced.

2. The method according to claim 1, characterized in that, The method further includes: Receive second information, which is used to indicate a second basic information model set, wherein the first basic information model set is a subset of the second basic information model set, and the second basic information model set contains all or part of the information units in the NFV descriptor.

3. The method according to claim 2, characterized in that, The basic information models in the second set of basic information models do not contain the same information units.

4. The method according to claim 1, characterized in that, The method further includes: Obtain third information, which is used to indicate the actual state of the NFV object.

5. The method according to claim 1, characterized in that, The producer entity includes Telecom Cloud Infrastructure Management (TCIM) or Container Cluster Management (CCM).

6. The method according to claim 1, characterized in that, The NFV object includes a container cluster.

7. The method according to claim 6, characterized in that, The desired state of the container cluster includes one or more of the following information elements: container cluster category, container cluster node architecture, container cluster deployment sample, container cluster version, or container cluster access control information.

8. The method according to claim 6 or 7, characterized in that, The set of basic information models for the container cluster includes one or more of the following basic information models: metadata description of the container cluster, description of the container cluster nodes required to form the member instances of the container cluster, description of container cluster storage resources, and / or, description of container cluster network resources.

9. The method according to claim 1, characterized in that, The first information is carried in the application operation request message.

10. A communication device, characterized in that, The communication device includes a module for performing the method as described in any one of claims 1-9.

11. A communication device, characterized in that, The communication device includes a processor; the processor is configured to run a computer program or instructions to cause the communication device to perform the method as described in any one of claims 1-9.

12. A chip or chip system, characterized in that, The chip or chip system includes a processor coupled to a memory for storing programs or instructions that, when executed by the processor, cause the method as described in any one of claims 1-9 to be performed.

13. A computer-readable storage medium, characterized in that, A computer-readable storage medium stores computer instructions or programs that, when executed on a computer, cause the method described in any one of claims 1-9 to be performed.

14. A computer program product, characterized in that, The computer program product includes computer instructions; when some or all of the computer instructions are run on a computer, the method described in any one of claims 1-9 is performed.

Images