Communication method and communication device

Abstract

[0006] Embodiments of the present application provide a communication method and a communication device. The communication method includes: accessing a data model to obtain a target state of a managed object in an NFV MANO management domain in the data model; and invoking a first function from a function set based on the target state, where the first function is used to transition the managed object from an existing state to the target state. Thus, the data model and function set are integrated within the NFV MANO management domain, and data and function operations of managed objects in the NFV MANO management domain are separated, implementing a simplified, agile, and scalable intent-driven management architecture.

Description

[Technical Field]

[0001] This application claims priority from Chinese Patent Application No. 202211725406.7, entitled "Communication Method and Communication Apparatus," filed with the State Intellectual Property Office of the People's Republic of China on December 29, 2022.

[0002] TECHNICAL FIELD Embodiments of the present application relate to the field of wireless communication technologies, and more particularly to a communication method and a communication device. [Background technology]

[0003] Network functions virtualization (NFV) uses general-purpose hardware devices and virtualization technology to implement the functions of dedicated devices in traditional communication networks, and enables the rapid deployment of new network services (NSs) through resource sharing, thereby reducing network deployment costs and improving network operation efficiency.

[0004] Currently, the European Telecommunications Standards Institute's NFV Industry Specification Group is defining a layered and decoupled NFV management and orchestration (MANO) architecture for telco cloud management to support virtual machine / container-based deployment and operation, management, and maintenance of telecommunications network elements for infrastructure functions. The Linux Foundation has also proposed Nephio, a flat architecture, to implement automated telco cloud management.

[0005] However, in terms of large-scale networking and the requirements for high performance, high reliability, and high security in telecommunication network operation and maintenance, the existing NFV MANO architecture has drawbacks such as complex architecture and poor scalability during the long-term evolution and development of the telco cloud.The Nephio architecture has drawbacks such as insufficient telco cloud-specific attributes and excessive customization.

[0006] Therefore, in the future long-term evolution scenario of telecom cloud, how to improve the simplicity and scalability of function interactions in the management architecture is an urgent problem to be solved. Summary of the Invention

[0007] Embodiments of the present application provide a method for communicating, in an NFV MANO management domain, a data model and a set of functions are integrated, thereby separating data and function operations of managed objects in the NFV MANO management domain, implementing a simplified, agile, and scalable intent-driven management architecture.

[0008] According to a first aspect, a communication method is provided. The method may be performed by an NFV MANO management domain, or may be performed by a functional component (also referred to as a management function entity) in the NFV MANO management domain. This is not intended to be limiting. For ease of explanation, the following uses an example in which the method is performed by an NFV MANO management domain for explanation.

[0009] The NFV MANO management domain includes a data model and a function set. The method may include accessing the data model to obtain a target state of a managed object in the NFV MANO management domain in the data model; and invoking a first function from the function set based on the target state, where the first function is used to transition the managed object from an existing state to the target state.

[0010] Based on the aforementioned solution, a data model and function set are integrated within the NFV MANO management domain, thus separating the data and function operations of managed objects within the NFV MANO management domain, implementing a simplified, agile, and scalable intent-driven management architecture.

[0011] In possible embodiments, the data model further includes parameter information that supports transitions from an existing state of the managed object to a target state.

[0012] Based on the above solution, the data model further includes parameter information that supports the transition of the managed object to the target state, thereby increasing the diversity of solutions for the transition from an existing state to the target state.

[0013] In possible embodiments, using a first function to transition a managed object from an existing state to a target state includes using the first function to transition a managed object from an existing state to a target state based on parameter information.

[0014] Based on the above solution, when the first function is invoked, the existing state of the managed object can be transitioned to a target state based on the parameter information.

[0015] In a possible embodiment, prior to accessing the data model, the method further comprises the step of subscribing to changes in the target state of the managed object.

[0016] Based on the above solution, when the NFV MANO management domain learns through subscribing that the state of the managed object has changed, the NFV MANO management domain further accesses the data model in which information about the managed object is located.

[0017] In a possible embodiment, invoking a first function from the function set based on the target state includes invoking a first function from the function set based on the target state and an existing state of the managed object.

[0018] Based on the above solution, the NFV MANO management domain can invoke the first function based on the target state and existing state of the managed object, thereby increasing the diversity of solutions for invoking the first function.

[0019] In a possible embodiment, after invoking a first function from the function set based on the target state, the method further comprises updating an existing state of the managed object in the data model to the target state.

[0020] Based on the above solution, when detecting that the managed object has transitioned to a target state, the NFV MANO management domain updates the state information of the managed object.

[0021] In possible embodiments, the managed object includes any one of the following: a cloud service object, a network service NS, a virtualized network function VNF, a virtualized network function component VNFC, a container cluster, a managed container infrastructure service object, a virtual resource, and a physical resource.

[0022] In possible embodiments, the feature set includes at least one of the following: lifecycle management; fault management, configuration management, account management, performance management, and security management FCAPS; intent management; and operations management.

[0023] In possible embodiments, lifecycle management includes at least one of the following management operations functions: instantiation functions, scaling functions, termination functions, and healing functions.

[0024] In possible embodiments, the FCAPS includes at least one of the following management operations functions: configuration management functions, performance management functions, fault management functions, account management functions, and security management functions.

[0025] In a possible embodiment, intent management includes at least one of the following management operations functions: design functions, deployment functions, and closed-loop control functions.

[0026] In possible embodiments, operational management includes at least one of the following management operations functions: multi-tenant management functions, billing or metering functions, and service catalog functions.

[0027] According to a second aspect, there is provided a communication device comprising a unit configured to perform the method set forth in the first aspect. The communication device may be in an NFV MANO management domain or may be a functional component located in an NFV MANO management domain, although this is not a limitation in this application.

[0028] The NFV MANO management domain includes a data model and a function set, and the communication device a processing unit configured to access a data model and obtain a target state of a managed object in the NFV MANO management domain in the data model; Equipped with.

[0029] The processing unit is further configured to invoke a first function from the function set based on the target state, where the first function is used for transitioning the managed object from an existing state to the target state.

[0030] In possible embodiments, the data model further includes parameter information that supports transitions from an existing state of the managed object to a target state.

[0031] In a possible embodiment, the first function is used to transition the managed object from an existing state to a target state based on parameter information.

[0032] In a possible embodiment, before accessing the data model, the processing unit is further configured to subscribe to changes in the target state of the managed object.

[0033] In a possible embodiment, the processing unit is further configured to invoke a first function from the function set based on the target state and the existing state of the managed object.

[0034] In a possible embodiment, after invoking the first function from the function set based on the target state, the processing unit is further configured to update an existing state of the managed object in the data model to the target state.

[0035] In possible embodiments, the managed object includes any one of the following: a cloud service object, a network service NS, a virtualized network function VNF, a virtualized network function component VNFC, a container cluster, a managed container infrastructure service object, a virtual resource, and a physical resource.

[0036] In possible embodiments, the feature set includes at least one of the following: lifecycle management; fault management, configuration management, account management, performance management, security management FCAPS; intent management; and operations management.

[0037] In possible embodiments, lifecycle management includes at least one of the following management operations functions: instantiation functions, scaling functions, termination functions, and healing functions.

[0038] In possible embodiments, the FCAPS includes at least one of the following management operations functions: configuration management functions, performance management functions, fault management functions, account management functions, and security management functions.

[0039] In possible embodiments, intent management includes at least one of the following management operations functions: design functions, deployment functions, and closed-loop control functions.

[0040] In possible embodiments, operational management includes at least one of the following management operations functions: multi-tenant management functions, billing or metering functions, and service catalog functions.

[0041] For a description of the relevant contents and beneficial effects of the communication device provided in the second aspect, please refer to the method according to the first aspect, and the details will not be described again here.

[0042] According to a third aspect, a communication method is provided. The method may be performed by a cloud management function, or may be performed by a functional component (also referred to as a management function entity) within the cloud management function. This is not intended to be limiting. For ease of explanation, the following uses an example in which the method is performed by the cloud management function for explanation.

[0043] The NFV MANO management domain includes a cloud service data model and a function set. The method may include: a cloud management function accessing the cloud service data model to obtain a target state of a cloud service object in the cloud service data model; and the cloud management function invoking a first function from the function set based on the target state, where the first function is used to transition from an existing state of the cloud service object to the target state.

[0044] Based on the aforementioned solution, cloud service data models and function sets are integrated within the NFV MANO management domain, thus separating the data and function operations of cloud service objects and implementing a simplified, agile, and scalable intent-driven management architecture.

[0045] In possible implementations, the cloud service data model further includes parameter information that supports transitions from an existing state of the cloud service object to a target state.

[0046] Based on the above solution, the data model further includes parameter information that supports the transition of the cloud service object to the target state, thereby increasing the diversity of solutions for the transition from the existing state to the target state.

[0047] In a possible embodiment, the parameter information includes a description of the infrastructure as a service resource.

[0048] In possible implementations, using the first function to transition from an existing state of the cloud service object to a target state includes using the first function to transition from an existing state of the cloud service object to a target state based on parameter information.

[0049] Based on the above solution, when the first function is invoked, the existing state of the cloud service object can be transitioned to a target state based on the parameter information.

[0050] In a possible embodiment, before the cloud management function accesses the cloud service data model, the method further comprises the cloud management tenant setting target state and / or parameter information for the cloud service object in the cloud service data model.

[0051] Based on the above solution, the state of a cloud service object can be changed in the manner that a cloud management tenant sets the target state and / or parameter information of the cloud service object in the cloud service data model.

[0052] In a possible embodiment, before the cloud management function invokes a first function from the function set based on the target state, the method further comprises the cloud management function subscribing to changes in the target state of the cloud service object.

[0053] Based on the above solution, when a cloud management tenant sets a target state of a cloud service object in a cloud service data model, the cloud management function learns that the state of the cloud service object has changed through subscribing, and further, the cloud management function accesses the data model where information about the cloud service object is located.

[0054] In a possible embodiment, the cloud management function invoking a first function from the function set based on the target state includes the cloud management function invoking the first function from the function set based on the target state and the existing state of the cloud service object.

[0055] Based on the above solution, the cloud management function can invoke the first function based on the target state and existing state of the cloud service object, increasing the diversity of the solution for invoking the first function.

[0056] In a possible embodiment, after the cloud management function invokes the first function from the function set based on the target state, the method further comprises the cloud management function updating an existing state of the cloud service object in the data model to the target state.

[0057] Based on the above solution, when detecting that the cloud service object has transitioned to a target state, the cloud management function updates the state information of the cloud service object.

[0058] In a possible embodiment, the first function includes instantiating a cloud service object.

[0059] According to a fourth aspect, there is provided a communication device comprising a unit configured to perform the method set out in the third aspect. The communication device may be a cloud management function or a functional component located in a cloud management function, although this is not a limitation in the present application.

[0060] The NFV MANO management domain includes a cloud service data model and a function set. The communications device may include a processing unit configured to access the cloud service data model and obtain a target state of a cloud service object in the cloud service data model. The processing unit is further configured to invoke a first function from the function set based on the target state, where the first function is used to transition from an existing state of the cloud service object to the target state.

[0061] In possible implementations, the cloud service data model further includes parameter information that supports transitions from an existing state of the cloud service object to a target state.

[0062] In a possible embodiment, the parameter information includes information about infrastructure as a service resource.

[0063] In possible implementations, using the first function to transition from an existing state of the cloud service object to a target state includes using the first function to transition from an existing state of the cloud service object to a target state based on parameter information.

[0064] In a possible embodiment, the processing unit is further configured to set target state and / or parameter information of the cloud service object in the cloud service data model.

[0065] In a possible embodiment, the processing unit is further configured to subscribe to changes in the target state of the cloud service object.

[0066] In a possible embodiment, the processing unit is further configured to invoke a first function from the function set based on the target state and the existing state of the cloud service object.

[0067] In a possible embodiment, the processing unit is further configured to update an existing state of the cloud service object in the data model to the target state.

[0068] In a possible embodiment, the first function includes instantiating a cloud service object.

[0069] For a description of the relevant contents and beneficial effects of the communication device provided in the fourth aspect, please refer to the method according to the third aspect, and the details will not be described again here.

[0070] According to a fifth aspect, there is provided a communication method. The method may be performed by a tenant and an NFV MANO management domain, or may be performed by a functional component (also referred to as a functional entity) in the tenant and a functional component (also referred to as a management functional entity) in the NFV MANO management domain. This is not limited here. For ease of explanation, the following uses an example in which the method is performed by a tenant and an NFV MANO management domain for explanation.

[0071] The NFV MANO management domain includes a data model and a function set. The method may include a tenant setting a target state of a managed object of the NFV MANO management domain in the data model. The NFV MANO management domain accesses the data model to obtain the target state. The NFV MANO management domain invokes a first function from the function set based on the target state, where the first function is used to transition the managed object from an existing state to the target state.

[0072] Based on the above solution, a data model and function set are integrated within the NFV MANO management domain, where an external system (e.g., a tenant) configures the state of managed objects in the NFV MANO management domain, and the data model and function set within the NFV MANO management domain separate the data of the managed objects from their functional operations to implement a simplified, agile, and scalable intent-driven management architecture.

[0073] According to a sixth aspect, there is provided a communications device, comprising: a memory configured to store a program; and at least one processor configured to execute a computer program or instructions stored in the memory to perform the method of any one of the first, third or possible implementations of the fifth aspect.

[0074] In an embodiment, the device is an NFV MANO management domain.

[0075] In another embodiment, the device is a chip, chip system, or circuit used in an NFV MANO management domain.

[0076] According to a seventh aspect, the present application provides a processor, the processor being configured to perform the method provided in the previous aspect.

[0077] Unless otherwise specified, or unless operations such as transmitting and acquiring / receiving associated with a processor are inconsistent with the actual functionality or embedded logic of the operations in the relevant description, operations may be understood as operations such as output, reception, and input of a processor, or operations such as transmitting and receiving performed by radio frequency circuits and antennas, which is not intended to be limiting in this application.

[0078] According to an eighth aspect, there is provided a computer-readable storage medium storing program code to be executed by a device, the program code including a method according to any one of the first, third or fifth aspects and possible implementations thereof.

[0079] According to a ninth aspect, there is provided a computer program product comprising instructions which, when run on a computer, enable the computer to carry out the method of any one of the first, third or possible implementations of the fifth aspect.

[0080] According to a tenth aspect, there is provided a chip, the chip comprising: a processor and a communication interface, the processor reading instructions stored in a memory via the communication interface, and executing the method of any one of the possible implementations of the first, third, or fifth aspects.

[0081] Optionally, in an embodiment, the chip further comprises a memory. The memory stores a computer program or instruction. The processor is configured to execute the computer program or instruction stored in the memory. When the computer program or instruction is executed, the processor is configured to perform the method of any one of the possible implementations of the first, third, or fifth aspects.

[0082] According to an eleventh aspect, there is provided a communication system comprising one or more of an NFV MANO management domain and a cloud management function. [Brief explanation of the drawings]

[0083] [Figure 1] FIG. 1 is a diagram of an architecture of an NFV system applicable to an embodiment of the present application.

[0084] [Figure 2] 1 illustrates an intent-driven management architecture according to the present application.

[0085] [Figure 3] FIG. 1 is an architectural diagram of a feature set applicable to embodiments of the present application.

[0086] [Figure 4] FIG. 1 is a diagram of an architecture of a data model applicable to embodiments of the present application.

[0087] [Figure 5] 5 is a schematic flow chart of a communication method 500 according to an embodiment of the present application.

[0088] [Figure 6] 6 is a schematic flow chart of a communication method 600 according to an embodiment of the present application.

[0089] [Figure 7] 7 is a schematic flow chart of a communication method 700 according to an embodiment of the present application.

[0090] [Figure 8] 8 is a block diagram of a communication device 800 according to an embodiment of the present application.

[0091] [Figure 9] 9 is a block diagram of another communication device 900 according to an embodiment of the present application.

[0092] [Figure 10] 1 is a diagram of a chip system 1000 according to an embodiment of the present application. DETAILED DESCRIPTION OF THE INVENTION

[0093] Hereinafter, the technical solutions of the embodiments in this application will be described with reference to the accompanying drawings.

[0094] First, an architectural diagram of an NFV system applicable to embodiments of the present application is briefly described.

[0095] Network functions virtualization (NFV) refers to the use of virtualization technology in the information technology (IT) field by telecommunication network operators to perform software and hardware separation for the implementation of some telecommunication network functions (such as core network functions) on general-purpose servers, switches, and storage devices. This enables rapid and efficient deployment and operation of network services (NS) and reduces network capital expenditures (CAPEX) and operating expenses (OPEX). By applying NFV technology, telecommunication network functions are implemented in software and can run on general-purpose server hardware without the need to install new devices. They can be moved, instantiated, and deployed to different physical locations in the network as needed.

[0096] NFV standardization primarily focuses on network services, virtualized network functions (VNFs), and the dynamic management and orchestration (MANO) of virtual resources. The Interface and Architecture (IFA) Working Group of the NFV Industry Specification Group of the European Telecommunications Standards Institute (ETSI) is completing the functional design within the MANO framework. Figure 1 shows the functional architecture. The following describes the functional components in Figure 1.

[0097] (1) NFV orchestrator (NFVO): The NFVO implements the network service descriptor (NS descriptor, NSD), manages and processes the virtualized network function forwarding graph (VNFFG), and manages the network service lifecycle. It cooperates with the VNFM to manage the lifecycle of VNFs and provides a global view of virtual resources.

[0098] (2) VNF manager (VNFM): The VNFM performs lifecycle management of virtualized network functions (VNFs), including managing virtualized network function descriptors (VNFDs), instantiating VNFs, scaling VNF instances (including scaling out / up and in / down), healing VNF instances, and terminating VNF instances. The VNFM further supports receiving scaling policies delivered by the NFVO to implement VNF ​​autoscaling.

[0099] (3) Virtualized infrastructure manager (VIM): VIM is primarily responsible for managing (including reservation and allocation) virtualized resources (including virtual computing, storage, and network resources) in the infrastructure layer, monitoring the status and reporting faults of virtualized resources, and providing a virtualized resource pool for upper-layer applications.

[0100] (4) Operations and business support systems (OSS / BSS): The operator's existing operations and maintenance systems OSS / BSS.

[0101] (5) Element manager (EM): Performs traditional fault management, configuration management, account management, performance management, and security management (FCAPS) functions for VNFs.

[0102] (6) Virtualized network function (VNF): This corresponds to a physical network function (PNF) in a traditional non-virtualized network, such as a virtualized EPC node (MME, S-GW, P-GW, etc.). The functional behavior and status of a network function are independent of whether it is virtualized or not. NFV technical requirements expect VNFs to have the same functional behavior and external interfaces as PNFs.

[0103] (7) NFV infrastructure (NFVI): NFVI is the infrastructure layer for NFV functions, and includes hardware resources, virtual resources, and a virtualization layer. From the perspective of VNF, the virtualization layer and hardware resources appear to constitute a holistic entity that can provide the required virtualization resources.

[0104] (8) Container infrastructure service management (CISM) (also referred to as CaaS management, where the open source prototype is based on Kubernetes): 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 (compute, storage, and network resources) in the container cluster node resource pool managed by CISM. In the ETSI standard, a container object corresponds to a managed container infrastructure object (MCIO).

[0105] (9) Container cluster management (CIS Cluster Management, CCM) is responsible for managing container clusters, including creating node resource pools to be used by the container cluster and scaling the nodes. A container cluster is a collection of a monitoring and management system (e.g., Kubernetes Master) and a set of compute nodes. A container cluster is a dynamic system in which multiple containers can be deployed within the system, and the system can monitor the state of these containers and communication between them.

[0106] In the system architecture shown in Figure 1, functional components may communicate with each other via the reference points shown in the figure. For example, in Figure 1, the NFVO and VIM communicate with each other via the Or-Vi reference point, and the VNFM and VIM communicate with each other via the Vi-Vnfm reference point. Figure 1 shows the different reference point interfaces and the relationships between each functional component. For the sake of brevity, the details will not be described again here.

[0107] It should be understood that the system architecture shown above is merely an example for the purpose of explanation, and that the system architecture applicable to the embodiments of the present application is not limited thereto. Any system architecture capable of implementing the functions of the functional components is applicable to the embodiments of the present application.

[0108] It should be further understood that the names of the interfaces between the aforementioned functional components in Figure 1 are merely examples, and the interfaces may have other names in specific implementations, which are not specifically limited in this application. Also, the names of the messages (or signals) transmitted between the aforementioned functional components are merely examples, and do not constitute any limitations on the functions of the messages.

[0109] It can be understood that the term "and / or" herein merely describes an association relationship for associated objects and indicates that three relationships may exist. For example, A and / or B may indicate three cases: only A is present, both A and B are present, and only B is present. Furthermore, the symbol " / " herein generally indicates an "or" relationship between associated objects.

[0110] In the NFV architecture based on Figure 1, there are many reference points (i.e., connection lines between functional components) between functional components in the architecture. This results in complex interface functions defined at each reference point, overlapping of different interface functions, high integration costs for the NFV MANO system, and poor scalability for new function blocks or reference points introduced into the system. For example, when a new function block is added to the NFV MANO architecture, new reference points may be defined between the new function block and up to N existing function blocks, resulting in an exponential increase in the number of interfaces. In addition, the data models of managed objects and the infrastructure resources used by the managed objects in the NFV MANO system are distributed across different function blocks in different layers, resulting in inconsistent or redundant data for the same managed object data model across different function blocks. This poses a major weakness for supporting management automation across all NFV MANO domains, making it difficult to ensure that management analysis or intent management modules based on artificial intelligence or machine learning can complete automated closed-loop control based on accurate data input.

[0111] Currently, for example, the Nephio architecture, which combines the Linux Foundation's flat architecture to implement automated telecom cloud management, has also emerged in the industry. However, in terms of large-scale networking and the requirements for high performance, high reliability, and high security in telecom network operation and maintenance, the NFV MANO architecture has drawbacks such as a complex architecture and poor scalability during the long-term evolution and development of telecom clouds, while the Nephio architecture has drawbacks such as insufficient telecom cloud-specific attributes and excessive customization.

[0112] Accordingly, embodiments of the present application provide a method for communicating, in an NFV MANO management domain, a data model and a set of functions are integrated, thus separating data and function operations of managed objects in the NFV MANO management domain, implementing a simplified, agile, and scalable intent-driven management architecture.

[0113] In the following, we first describe the intent-driven management architecture provided in this application.

[0114] As shown in Figure 2, the intent-driven management architecture (also referred to as the NFV MANO management domain) provided herein includes MANO function blocks, function sets, and a data model. The MANO function blocks can separately invoke functions in the function sets to access information about managed objects in the data model. There are logical interaction relationships between the MANO function blocks and external systems (e.g., operations support systems (OSS)) and between the MANO function blocks; there are no physical interoperability interfaces (i.e., the dashed lines in Figure 2) between the MANO function blocks. Interactions between different function blocks are implemented by each pair of function blocks acting on the same managed object in the data model and performing "read" or "write" operations on the managed object.

[0115] The MANO function blocks are coarse-grained functional entities that implement interface interoperability between MANO function blocks and between MANO function blocks and external systems in the NFV MANO management domain. The MANO function blocks include, but are not limited to, the NFVO, VNFM, container cluster management (container infrastructure service cluster management, CCM), cloud management functions, container infrastructure service management (CISM) / container image repository (CIR), and VIM / wide area network infrastructure manager (WAN infrastructure manager, WIM). For details of the MANO function blocks, see Figure 3. The cloud management function is used to manage cloud services provided in the NFV MANO management domain, such as cloud services formed by allocating virtual computing, virtual storage, or virtual network resources at the infrastructure layer. In the intent-driven management architecture provided herein, the MANO function blocks can also be further extended. For example, a physical infrastructure manager (PIM) may be introduced, or some existing function blocks may be aggregated to form a highly autonomous function block. For example, a telco cloud management (TCM) aggregates the NFVO, VNFM, and / or CCM function blocks in the original architecture. As shown in Figure 3, the aggregation relationship between the NFV MANO function blocks is not particularly limited here.

[0116] A function set is a generic operation or notification definition (also called a Type A component), i.e., a group of function sets for performing operations or notifications on abstract "generic NFV objects", formed through the generalization and combination of management plane functions (or services) that provide the same functionality but perform operations on different managed objects in the NFV MANO architecture, based on the design principle of service-based architecture (SBA), which is independent of specific managed objects. See Figure 3 for details.

[0117] Specifically, the feature set may be further divided into general features and other types of features according to different functions of the feature set.

[0118] As shown in Figure 3, the general functions include life cycle management (LCM) for general NFV objects and fault management, configuration management, account management, performance management, and security management (FCAPS) for general NFV objects for operations, administration, and maintenance.

[0119] Lifecycle management is used to manage the entire lifecycle of a typical NFV object, from instantiation to termination.

[0120] Specifically, lifecycle management includes at least one of the following management operations functions: Instantiation, scaling, termination, and healing functions.

[0121] The instantiation function is used to instantiate generic NFV objects and create instances for objects.

[0122] The scaling function is used to perform auto-scaling on instantiated generic NFV objects and to allocate or reclaim corresponding infrastructure resources for the NFV objects.

[0123] The terminate function is used to terminate an instantiated generic NFV object and release the virtual infrastructure resources used by the object instance.

[0124] The healing function is used to heal and restore a general NFV object that has failed or is faulty.

[0125] FCAPS is used in the conventional network management field for configuration management, performance management, account management, performance management, and security management.

[0126] Specifically, FCAPS includes a configuration management function, a performance management function, a fault management function, an account management function, and a security management function.

[0127] Account management may further include log management and the like.

[0128] It should be noted that the specific description of the above FCAPS is referred to relevant descriptions in the existing network management field, and is not described in detail in this application.

[0129] In the intent-driven management architecture provided herein, the aforementioned feature set can be further extended to add other types of functionality, for example, intent management and operational management in FIG. 3.

[0130] Intent management is used to perform intent-based management on generic NFV objects.

[0131] Specifically, intent management includes at least one of the following management operations functions: It includes design, deployment, and closed-loop control functions.

[0132] Design functions are used to define the corresponding intent for the management of generic NFV objects.

[0133] The deployment function is used to deploy the intent of a general NFV object on the NFV network in a way that makes the intent valid.

[0134] The closed-loop control function is used to perform closed-loop control, e.g., intent translation and validation, on the deployed intent of the generic NFV object to ensure that the execution of that intent complies with the defined intent purpose managed by the generic NFV object.

[0135] Operational management is used to plan, organize, execute and control the operational processes of managed objects in the NFV MANO management domain.

[0136] Specifically, operational management includes at least one of the following management operations functions: Multi-tenant management functionality, billing or metering functionality, and service catalog functionality.

[0137] The multi-tenant management function is used to manage tenants that use managed objects in the NFV MANO management domain of a service type, including creating and deleting tenants.

[0138] The charging or metering function is used to measure and charge for the usage of managed objects in the NFV MANO management domain for service types.

[0139] The service catalog function is used for managing the catalog of managed objects of the NFV MANO management domain.

[0140] It should be noted that the above description of the functional configuration of the intent management and operation management is merely an example, and for details, please refer to the description of the intent management and operation management in the prior art, which is not intended to be limiting in the present application.

[0141] Data models (also referred to as Type B components) are used to uniformly store, access, and manage managed objects in the intent-driven management architecture, and the data models are independent of functional operations. The data models of managed objects stored in the data models include image information of object instances in operational states, as well as configuration, fault, and performance management information required by the objects in operation, management, and maintenance. Managed objects include, but are not limited to, container clusters, cloud service objects, network services (NSs), virtualized network functions (VNFs), virtual network function components (VNFCs), container clusters, managed container infrastructure service objects, virtual resources, and physical resources. The MANO functional blocks implement a data-driven, declarative application programming interface (API) interaction mode by accessing managed objects in the data models, as shown in Figure 4.

[0142] It should be noted that the above description of the MANO function blocks, function sets, and data models is merely an example, and the functional scope of the MANO function blocks, function sets, and data models is not limited in this application.

[0143] The communication method provided in the embodiments of the present application will be described in detail below with reference to specific embodiments.

[0144] 5 is a schematic flowchart of a communication method 500 according to an embodiment of the present application. As shown in FIG. 5, the method 500 specifically includes the following steps:

[0145] S510: Access a data model and obtain a target state of a managed object in the NFV MANO management domain in the data model.

[0146] Specifically, the NFV MANO management domain accesses a data model used to store information about managed objects in the NFV MANO management domain and obtains the target state of the managed objects in the NFV MANO management domain in the data model.

[0147] Managed objects within the NFV MANO management domain include one of the following: Cloud service objects, network services (NS), virtualized network functions (VNF), virtual network function components (VNFC), container clusters, managed container infrastructure service objects, virtual resources, and physical resources.

[0148] A cloud service object is an NFV MANO managed object, such as a computing resource or a storage resource in the infrastructure layer, that a tenant subscribes to and uses as a service in the telco cloud.

[0149] The data model includes parameter information of the managed objects, which supports transitions of the managed objects from an existing state to a target state. For example, the parameter information of the managed objects may be description information of infrastructure as a service (IaaS) resources, although this is not intended to be limiting.

[0150] Optionally, the data model may further include configuration information, management information, etc. of the managed objects, although this is not a limitation in this application.

[0151] Please note that for the above data model description, please refer to the relevant descriptions in Figures 2 and 3. To avoid repetition, the detailed description thereof is omitted here.

[0152] S520: Invoke a first function from the function set based on the goal state.

[0153] Specifically, after knowing the target state of the managed object, the NFV MANO management domain invokes a first function from the function set based on the target state.

[0154] It should be understood that the NFV MANO management domain invoking a first function from a function set based on a target state may be understood as the NFV MANO management domain determining a first function from a function set based on a target state and executing the first function to cause a managed object to transition from an existing state to the target state.

[0155] The feature set includes a number of general features and other types of features.

[0156] For example, the feature set may include general features such as lifecycle management and FCAPS. Other types of features in the feature set may include intent management, operational management, etc. For more details, see FIG. 3 and the associated description of FIG. 3. This is not a limitation of the present application.

[0157] The function set includes a first function, the first function being used to transition the managed object from an existing state to a target state.

[0158] Optionally, the first function is used for transitioning the managed object from an existing state to a target state based on the parameter information.

[0159] It should be understood that the first function being used for transitioning from an existing state of the managed object to a target state based on parameter information can be understood as the first function being performed based on configurations such as specific parameters in the parameter information for transitioning from an existing state of the managed object to a target state.

[0160] In a possible embodiment, the NFV MANO management domain invokes a first function from a function set based on the target state and the existing state of the managed object.

[0161] Specifically, after knowing the target state of the managed object, the NFV MANO management domain invokes a first function from the function set based on the target state and the existing state of the managed object.

[0162] Based on the aforementioned solution, a data model and a function set are integrated within the NFV MANO management domain, thus separating the data and function operations of managed objects within the NFV MANO management domain, implementing a simplified, agile, and scalable intent-driven management architecture.

[0163] Additionally, before the NFV MANO management domain accesses the data model, the NFV MANO management domain monitors the state of the managed objects, and the method 500 may further comprise:

[0164] S530: Subscribe to changes in the goal state of the managed object.

[0165] Specifically, the NFV MANO management domain subscribes to changes in the target state of a managed object. When the NFV MANO management domain detects that the state of a managed object has changed, or when the NFV MANO management domain is notified that the state of a managed object has changed, the NFV MANO management domain accesses a data model that stores parameter information for the managed object.

[0166] It should be understood that subscribing to changes in the target state of a managed object can be understood as monitoring whether the target state of the managed object has changed or being able to receive a subscription notification message indicating that the state of the managed object has changed. The specific method of subscribing to changes in the target state of a managed object is not limited in this application.

[0167] Further, after the NFV MANO management domain invokes the first function from the function set based on the target state, the NFV MANO management domain updates the state of the managed object.

[0168] S540: Update the existing state of the managed object in the data model to the target state.

[0169] Specifically, after the NFV MANO management domain executes the first function, if the NFV MANO management domain detects that the state of the managed object has transitioned to the target state, the NFV MANO management domain updates the existing state of the managed object in the data model to the target state.

[0170] 6 is a schematic flowchart of a communication method 600 according to an embodiment of the present application. For FIG. 6, please refer to the description of FIG. 5. As shown in FIG. 6, the method 600 specifically includes the following steps:

[0171] S610: The cloud management tenant accesses the cloud service data model.

[0172] Specifically, an enterprise user accesses the cloud service data model within the data model through a cloud management tenant portal interface to obtain the existing state of the cloud service object.

[0173] The cloud service data model is used to store parameter information of a cloud service object, which includes the existing state of the cloud service object.

[0174] For example, the existing state of a cloud service object is "object not instantiated."

[0175] Optionally, the cloud service data model may further include configuration information of the cloud service object, management information of the cloud service object, etc. This is not limited in this application.

[0176] S620: The cloud management tenant sets the target state and / or parameter information of the cloud service object in the cloud service data model.

[0177] Specifically, an enterprise user, via a cloud management tenant, sets the target state and / or parameter information of a cloud service object in the cloud service data model.

[0178] For example, an enterprise user sets the target state of a cloud service object to "object is instantiated" in the cloud service data model via a cloud management tenant and sets the required parameter information of the cloud service object in the target state, such as description information of an Infrastructure as a Service (IaaS) resource.

[0179] S630: The cloud management function subscribes to changes in the target state of the cloud service object.

[0180] Specifically, a cloud management function in the NFV MANO management domain monitors state information of cloud service objects. When a cloud management tenant sets target state and / or parameter information of a cloud service object in a cloud service data model, the cloud management function can detect that the state of the cloud service object has changed (e.g., the target state has been set for the cloud service object).

[0181] It should be understood that subscribing to changes in the target state of a cloud service object can be understood as monitoring whether the target state of a cloud service object has changed or receiving a subscription notification message indicating that the state of a cloud service object has changed. The specific method of subscribing to changes in the target state of a cloud service object is not limited in this application.

[0182] S640: The cloud management function accesses the cloud service data model and obtains the target state of the cloud service object in the cloud service data model.

[0183] Specifically, when the cloud management function detects that the state of a cloud service object has changed (e.g., a target state has been set for the cloud service object), the cloud management function accesses a cloud service data model that stores parameter information for the cloud service object and obtains the target state of the cloud service object in the cloud service data model.

[0184] Optionally, the cloud service data model further comprises parameter information, which supports a transition from an existing state of the cloud service object to a target state.

[0185] For example, the parameter information may be description information of an IaaS resource, such as a virtual computing resource, a virtual storage resource, or a virtual network resource, although this is not a limitation in the present application.

[0186] In possible embodiments, the cloud management function accesses the cloud service data model to obtain target state and parameter information for the cloud service objects in the cloud service data model.

[0187] S650: The cloud management function invokes a first function from the function set based on the target state.

[0188] Specifically, after obtaining the target state of the cloud service object, the cloud management function invokes, based on the target state, a first function in the function set that is used to transition from the existing state of the cloud service object to the target state.

[0189] In a possible embodiment, the cloud management function invokes a first function from the function set based on the target state and the existing state of the cloud service object.

[0190] The first function is used to transition from an existing state of a cloud service object to a target state.

[0191] Optionally, the first function is used for transitioning from an existing state to a target state of the cloud service object based on the parameter information.

[0192] For example, if the target state of the cloud service object obtained by the cloud management function is "object is instantiated," the cloud management function invokes the "instantiate cloud service object" function (i.e., the first function) in the function set based on the target state, and uses the IaaS resource description information obtained in S640 as a group of parameters used by the "instantiate cloud service object" function to perform the IaaS resource allocation required for the cloud service object to realize the target state.

[0193] S660: The cloud management function updates the existing state of the cloud service object in the cloud service data model to the target state.

[0194] Specifically, after the cloud management function executes the first function, if the cloud management function detects that the state of the cloud service object has transitioned to a target state, the cloud management function updates the existing state of the cloud service object in the cloud service data model to the target state.

[0195] For example, the cloud management function updates the existing state of the cloud service object in the cloud service data model to "object instantiated."

[0196] Based on the aforementioned solution, cloud service data models and function sets are integrated within the NFV MANO management domain, thus separating the data and function operations of cloud service objects and implementing a simplified, agile, and scalable intent-driven management architecture.

[0197] 7 is a schematic flowchart of a communication method 700 according to an embodiment of the present application. For FIG. 7, please refer to the description of FIG. 5. As shown in FIG. 7, the method 700 specifically includes the following steps:

[0198] S710: The NFVO accesses the VNF data model.

[0199] Specifically, the NFVO accesses the VNF data model in the data model to obtain the existing state of the VNF object.

[0200] The VNF data model is used to store parameter information of a VNF object, which includes the existing state of the VNF object.

[0201] For example, the existing state of a VNF object is "object not instantiated."

[0202] Optionally, the VNF data model may further include configuration information of the VNF object, management information of the VNF object, etc. This is not limited in this application.

[0203] It should be noted that in S710, the NFVO may alternatively be a telco cloud management (TCM) with an integrated NFVO function block, which is not limited in this application.

[0204] S720: The NFVO sets the target state and / or parameter information of the VNF object in the VNF data model.

[0205] For example, the NFVO sets the target state of the VNF object in the VNF data model to "object instantiated" and sets the required parameter information of the VNF object in the target state.

[0206] S730: The VNFM subscribes to changes in the target state of the VNF object.

[0207] Specifically, the VNFM monitors state information of VNF objects. When the NFVO sets the target state and / or parameter information of a VNF object in the VNF data model, the VNFM can detect that the state of the VNF object has changed (e.g., the target state has been set for the VNF object).

[0208] It should be understood that subscribing to a change in the target state of a VNF object can be understood as monitoring whether the target state of the VNF object has changed or being able to receive a subscription notification message indicating that the state of the VNF object has changed. The specific method of subscribing to a change in the target state of a VNF object is not limited by this application.

[0209] S740: The VNFM accesses the VNF data model to obtain a target state of the VNF object in the VNF data model.

[0210] Specifically, when the VNFM detects that the state of a VNF object has changed (e.g., a target state has been set for the VNF object), the cloud management function accesses a VNF data model that stores parameter information for the VNF object and obtains the target state of the VNF object in the VNF data model.

[0211] Optionally, the VNF data model further includes parameter information, which supports a transition from an existing state of the VNF object to a target state.

[0212] In a possible embodiment, the VNFM accesses the VNF data model to obtain target state and parameter information for the VNF objects in the VNF data model.

[0213] S750: The VNFM invokes a first function from a function set based on the target state.

[0214] Specifically, after obtaining the existing state and the target state of the VNF object, the VNFM compares the difference between the existing state and the target state and invokes a first function used to transition the VNF object from the existing state to the target state, thereby causing the VNF object to realize the target state.

[0215] In a possible embodiment, the VNFM sets a target state of the virtual machine object in a data model of the virtual machine object, and the VIM retrieves the target state of the virtual machine object from the data model of the virtual machine object and invokes a second function to enable the virtual machine object to achieve the target state.

[0216] Specifically, after the VNFM obtains the existing state and the target state of the VNF object, the VNFM further sets the target state of the virtual machine object in the VNF, i.e., the component of the data model of the virtual machine object. When detecting that the state of the virtual machine object has changed, the VNFM accesses the data model of the virtual machine object to obtain the target state of the virtual machine object, and further compares the difference between the existing state of the virtual machine object and the target state, and invokes a second function used for transitioning from the existing state of the virtual machine object to the target state, so that the virtual machine object realizes the target state and the VNF object realizes the target state.

[0217] S760: The VNFM updates the existing state of the VNF object in the VNF data model to the target state.

[0218] Specifically, after the VNFM executes the first function, if the VNFM detects that the state of the VNF object has transitioned to the target state, the VNFM updates the existing state of the VNF object in the VNF data model to the target state.

[0219] For example, the VNFM updates the existing state of the VNF object in the VNF data model to "object instantiated."

[0220] Based on the aforementioned solution, the data model and function set of managed objects are integrated within the NFV MANO management domain, thus separating the data and function operations of managed objects and implementing a simplified, agile, and scalable intent-driven management architecture.

[0221] 5 to 7 in the embodiments of the present application are merely intended to help those skilled in the art understand the embodiments of the present application, but are not intended to limit the embodiments of the present application to the specific scenarios in these examples. Those skilled in the art can obviously make various equivalent modifications or changes according to the examples of Figures 5 to 7, and such modifications or changes also fall within the scope of the embodiments of the present application.

[0222] It may be further understood that some optional features in the embodiments of the present application may be independent of other features in some scenarios, or may be combined with other features in some scenarios. This is not limited.

[0223] It can be further understood that the solutions in the embodiments of the present application can be appropriately combined for use, and the explanations or descriptions of terms in the embodiments can be mutually referenced or explained in those embodiments. This is not limited.

[0224] It can be further understood that the various numerical sequence numbers in the embodiments of the present application do not imply an execution order, but are merely for distinction for ease of explanation, and therefore should not constitute any limitation on the implementation process of the embodiments of the present application.

[0225] It can be further understood that some names in the embodiments of the present application, such as the first function or the second function, do not limit the protection scope of the embodiments of the present application.

[0226] In the above-mentioned method embodiments, it may be further understood that the methods and operations performed by the NFV MANO management domain may also be performed by functional components (also referred to as management function entities) in the NFV MANO management domain. Also, the methods and operations performed by the cloud management function may also be performed by functional components (also referred to as management function entities) within the cloud management function. This is not limited to this. Corresponding to the methods provided in the above-mentioned method embodiments, the embodiments of the present application further provide corresponding apparatuses. The apparatuses include corresponding modules configured to execute the above-mentioned method embodiments. The modules may be software or a combination of software and hardware. It may be understood that the technical features described in the method embodiments are also applicable to the following apparatus embodiments.

[0227] It should be understood that the NFV MANO management domain or the cloud management function may perform some or all of the steps in the above-described embodiments. These steps or operations are merely examples. Other operations or variations of various operations may also be performed in the embodiments of the present application. In addition, steps may be performed in a different order than presented in the above-described embodiments, and not all operations in the above-described embodiments may need to be performed.

[0228] The communication method provided in the embodiment of the present application has been described in detail above with reference to Figures 5 to 7. The communication device provided in the embodiment of the present application will be described in detail below with reference to Figures 8 to 10. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, for the content not described in detail, please refer to the above method embodiment. For the sake of brevity, some details of the content will not be described again here.

[0229] 8 is a block diagram of a communication device according to an embodiment of the present application. The device 800 includes a transceiver unit 810, which may be configured to perform corresponding communication functions. The transceiver unit 810 may also be referred to as a communication interface or a communication unit.

[0230] Optionally, the apparatus 800 may further comprise a processing unit 820, which may be configured to perform data processing.

[0231] Optionally, the apparatus 800 further comprises a storage unit. The storage unit may be configured to store instructions and / or data. The processing unit 820 may read the instructions and / or data in the storage unit, thereby causing the apparatus to perform actions of different apparatuses in the aforementioned method embodiments, for example, actions of an NFV MANO management domain or a cloud management function.

[0232] The apparatus 800 may be configured to perform actions performed by an NFV MANO management domain or cloud management function in the aforementioned method embodiments. In this case, the apparatus 800 may be an NFV MANO management domain or cloud management function, or a component of an NFV MANO management domain or cloud management function. The processing unit 820 is configured to perform operations related to processing of the NFV MANO management domain or cloud management function in the aforementioned method embodiments.

[0233] It should be further understood that the apparatus 800 herein is 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) configured to execute one or more software or firmware programs, a memory, an integrated logic circuit, and / or another suitable component supporting the described functionality. In any example, those skilled in the art will understand that the apparatus 800 may specifically be the NFV MANO management domain or cloud management function in the aforementioned embodiments and may be configured to perform procedures and / or steps corresponding to the NFV MANO management domain or cloud management function in the aforementioned method embodiments. To avoid repetition, the details will not be described again herein.

[0234] The device 800 in each of the above solutions has a function to perform corresponding steps performed by an NFV MANO management domain or a cloud management function in the above methods, or the device 800 in each of the above solutions has a function to perform corresponding steps performed by an NFV MANO management domain or a cloud management function in the above methods. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software may include one or more modules corresponding to the above functions. For example, a transceiver unit may be replaced by a transceiver (e.g., a transmitting unit in the transceiver unit may be replaced by a transmitter, and a receiving unit in the transceiver unit may be replaced by a receiver), and another unit, e.g., a processing unit, may be replaced by a processor to separately perform receiving / transmitting operations and related processing operations in the method embodiments.

[0235] Also, the transceiver unit 810 may alternatively be transceiver circuitry (eg, may include receiving circuitry and transmitting circuitry), and the processing unit may be processing circuitry.

[0236] It should be noted that the apparatus in Fig. 8 may be the device in the above-mentioned embodiments, or may be a chip or a chip system, for example, 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. This is not limited here.

[0237] 9, an embodiment of the present application provides another communication device 900. The device 900 includes a processor 910. The processor 910 is coupled to a memory 920, which is configured to store computer programs or instructions and / or data, and the processor 910 is configured to execute the computer programs or instructions stored in the memory 920 or read the data stored in the memory 920 to perform the method in the above-described method embodiments.

[0238] Optionally, there are one or more processors 910 .

[0239] Optionally, there are one or more memories 920 .

[0240] Optionally, memory 920 and processor 910 are integrated or located separately.

[0241] Optionally, as shown in Figure 9, the apparatus 900 further includes a transceiver 930. The transceiver 930 is configured to receive and / or transmit signals. For example, the processor 910 is configured to control the transceiver 930 to receive and / or transmit signals.

[0242] In one solution, the apparatus 900 is configured to perform operations performed by an NFV MANO management domain or a cloud management function in the above method embodiments.

[0243] For example, the processor 910 is configured to execute computer programs or instructions stored in the memory 920 to perform the NFV MANO management domain or cloud management functions in the method embodiments described above, such as the related operations of the NFV MANO management domain in the embodiment shown in FIG. 5 or the method of the NFV MANO management domain or cloud management functions in the embodiment shown in FIG. 5.

[0244] It should be understood that the processor referred to in the embodiments of this application may be a central processing unit (CPU), or may further be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or the like. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor or the like.

[0245] It should be further understood that the memory referred to in the embodiments of the present application may be volatile memory and / or 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). For example, RAM may be used as an external cache. By way of example and not limitation, RAM includes multiple forms such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchlink dynamic random access memory (synchlink DRAM, SLDRAM), and direct rambus random access memory (direct rambus RAM, DR RAM).

[0246] It should be noted that if the processor is a general-purpose processor, a DSP, an ASIC, an FPGA or another programmable logic device, or a discrete gate or transistor logic device, or a discrete hardware component, the memory (storage module) may be integrated into the processor.

[0247] It should be further noted that memory as described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0248] 10, an embodiment of the present application provides a chip system 1000. The chip system 1000 (also referred to as a processing system) includes a logic circuit 1010 and an input / output interface (input / output interface) 1020.

[0249] The logic circuit 1010 may be a processing circuit in the chip system 1000. The logic circuit 1010 may be coupled and connected to a storage unit to invoke instructions in the storage unit and enable the chip system 1000 to implement the methods and functions in the embodiments of the present application. The input / output interface 1020 may be an input / output circuit in the chip system 1000, which outputs information processed by the chip system 1000 or inputs data or signal information to be processed into the chip system 1000 for processing.

[0250] In one solution, the chip system 1000 is configured to perform operations performed by the NFV MANO management domain or cloud management function in the above method embodiments.

[0251] For example, the logic circuitry 1010 is configured to perform processing-related operations of the NFV MANO management domain or cloud management function in the aforementioned method embodiments, e.g., processing-related operations of the NFV MANO management domain in the embodiment shown in Figure 5. The input / output interface 1020 is configured to perform transmission and / or reception-related operations of the NFV MANO management domain in the aforementioned method embodiments, e.g., transmission and / or reception-related operations performed by the NFV MANO management domain in the embodiment shown in Figure 5.

[0252] An embodiment of the present application further provides a computer-readable storage medium storing computer instructions used to implement a method performed by an NFV MANO management domain or a cloud management function in the aforementioned method embodiment.

[0253] For example, when the computer program is executed by a computer, the computer is enabled to perform the method performed by the NFV MANO management domain or cloud management function in the above-described method embodiments.

[0254] An embodiment of the present application further provides a computer program product comprising instructions, which, when executed by a computer, cause the method to be performed by the NFV MANO management domain or cloud management function in the aforementioned method embodiments.

[0255] For the description of the relevant contents and beneficial effects of any one of the devices provided above, please refer to the corresponding method embodiments provided above, and the details will not be described again here.

[0256] In some embodiments provided herein, it should be understood that the disclosed devices and methods may be implemented in other manners. For example, the described device embodiments are merely examples. For example, the division into multiple units is merely a logical division of function, and other divisions may be used in actual implementations. For example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not implemented. Furthermore, the shown or described mutual couplings or direct couplings or communication connections may be implemented through some interfaces. Indirect couplings or communication connections between devices or units may be implemented in electronic, mechanical, or other forms.

[0257] All or some of the above-described embodiments may be implemented using software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product comprises one or more computer instructions. When the computer program instructions are loaded into a computer and executed, all or part of the procedures or functions according to the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. For example, the computer may be a personal computer, a server, a network device, or the like. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, or digital subscriber line (DSL)) or wireless (e.g., infrared, radio wave, or microwave) transmission. The computer-readable storage medium may be any available medium accessible by a computer, or a data storage device, such as a server or a data center, that integrates one or more available media. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk drive, or a magnetic tape), an optical medium (e.g., a DVD), a semiconductor medium (e.g., a solid-state drive (SSD)), or the like. For example, the available medium may include, but is not limited to, any medium that can store program code, such as a USB flash drive, a removable hard disk drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0258] The above description is merely a specific embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modifications or replacements that can be easily thought of by those skilled in the art within the technical scope disclosed in the present application shall be included in the scope of protection of the present application. Therefore, the scope of protection of the present application shall be subject to the scope of protection of the claims.

Claims

1. A method of communication, wherein a Network Function Virtualization Management and Orchestration (NFV) MANO management domain includes a data model and a function set, the method comprising: accessing the data model to obtain a target state of a managed object in the NFV MANO management domain within the data model; and calling a first function from the function set based on the target state, wherein the first function is used to transition from an existing state of the managed object to the target state; A method for providing

2. The method of claim 1 , wherein the data model further comprises parameter information, the parameter information supporting a transition from the existing state of the managed object to the target state.

3. The first function is used to transition the managed object from the existing state to the target state, The first function is used to transition the managed object from the existing state to the target state based on the parameter information. The method of claim 2 , comprising:

4. Prior to the step of accessing the data model, the method further comprises: Subscribing to changes in the target state of the managed object. The method of claim 1 , further comprising:

5. Invoking the first function from the function set based on the target state comprises: Invoking the first function from the function set based on the target state and the existing state of the managed object.

5. The method according to claim 1, wherein the

6. After the step of invoking the first function from the function set based on the target state, the method further comprises: updating the existing state of the managed object in the data model to the target state; The method of claim 1 , further comprising:

7. The managed object includes any one of the following: Cloud service object, network service NS, virtualized network function VNF, virtualized network function component VNFC, container cluster, managed container infrastructure service object, virtual resource, and physical resource 7. The method according to any one of claims 1 to 6.

8. The feature set includes at least one of the following: Lifecycle Management; Fault Management, Configuration Management, Account Management, Performance Management, and Security Management FCAPS; Intent Management; and Operational Management 8. The method according to any one of claims 1 to 7.

9. The lifecycle management includes at least one of the following management operations functions: Instantiation, scaling, termination, and healing functions The method of claim 8.

10. The FCAPS includes at least one of the following management operations functions: Configuration management function, performance management function, fault management function, account management function, and security management function The method of claim 8.

11. The intent management includes at least one of the following management operation functions: Design, deployment, and closed-loop control functions The method of claim 8.

12. The operational management includes at least one of the following management operations functions: Multi-tenant management, billing or metering, and service catalog functions The method of claim 8.

13. 1. A communications device, wherein a Network Function Virtualization Management and Orchestration (NFV) MANO management domain includes a data model and a function set, the device comprising: a processing unit configured to access a data model and obtain a target state of a managed object in the NFV MANO administrative domain in said data model; Equipped with The processing unit is further configured to invoke a first function from the function set based on the target state, the first function being used to transition the managed object from an existing state to the target state. Device.

14. The data model further includes parameter information that supports a transition from the existing state of the managed object to the target state.

14. The apparatus of claim 13.

15. The first function is used to transition the managed object from the existing state to the target state, The first function is used to transition the managed object from the existing state to the target state based on the parameter information. The apparatus of claim 14 , comprising:

16. Prior to said accessing said data model, said device: the processing unit further configured to subscribe to changes in the target state of the managed object; 16. The apparatus of claim 13, further comprising:

17. Invoking the first function from the function set based on the target state comprises: The processing unit is further configured to invoke the first function from the function set based on the target state and the existing state of the managed object.

17. The apparatus of any one of claims 13 to 16, comprising:

18. After invoking the first function from the function set based on the target state, the device: a processing unit further configured to update the existing state of the managed object in the data model to the target state; 18. The apparatus of claim 13, further comprising:

19. The managed object includes any one of the following: Cloud service object, network service NS, virtualized network function VNF, virtualized network function component VNFC, container cluster, managed container infrastructure service object, virtual resource, and physical resource 19. Apparatus according to any one of claims 13 to 18.

20. The feature set includes at least one of the following: Lifecycle Management, FCAPS, Intent Management, and Operational Management 20. Apparatus according to any one of claims 13 to 19.

21. The lifecycle management includes at least one of the following management operations functions: Instantiation, scaling, termination, and healing functions 21. The apparatus of claim 20.

22. The FCAPS includes at least one of the following management operations functions: Configuration management function, performance management function, fault management function, account management function, and security management function 21. The apparatus of claim 20.

23. The intent management includes at least one of the following management operation functions: Design, deployment, and closed-loop control functions 21. The apparatus of claim 20.

24. The operational management includes at least one of the following management operation functions: Multi-tenant management, billing or metering, and service catalog functions 21. The apparatus of claim 20.

25. 13. A computer-readable storage medium storing a computer program or instructions which, when executed by a processor, perform the method according to any one of claims 1 to 12.

26. A computer program product comprising instructions, which when said computer program product runs on a computer, performs the method of any one of claims 1 to 12.

27. A chip system comprising a processor configured to retrieve computer programs or instructions from a memory and execute said computer programs or instructions, whereby a communication device in which said chip system is installed performs the method of any one of claims 1 to 12.

Images