Intent capability management method, apparatus and system, and storage medium

Abstract

An intent capability management method, apparatus and system, and a storage medium. On the basis of receiving an arrived intent request, an intent requester subscribes, from an intent directory, to intent capability description information of a target intent producer of a network layer related to a service, and sends a first call instruction to the target intent producer of the network layer, wherein the first call instruction is used for instructing that the target intent producer of the network layer be called; on the basis of the first call instruction, the target intent producer of the network layer subscribes, from the intent directory, to intent capability description information of a target intent producer of a network element layer related to the service, and calls at least one target intent producer of the network element layer; and on the basis of the call instruction, the at least one target intent producer of the network element layer configures a network element related to a first service. Therefore, on the basis of intents of different users, intent function processing corresponding to product versions of manufacturers can be automatically and flexibly discovered and triggered.

Description

Intent capability management method, device, system and storage medium

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on September 12, 2023, with application number 202311171803.9 and invention name “Intent Capability Management Method, Device, System and Storage Medium”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to an intent capability management method, device, system and storage medium. Background Art

[0003] Intent-driven networking technology can address the challenges posed by evolving network technologies, rapidly expanding services, and complex operations and maintenance management. It emphasizes the intended outcomes of network services, decoupling system expectations from specific implementation details. It automatically translates, verifies, activates, and ensures network reliability based on operator intent. Through intent-driven interaction, users and operators express their service expectations and business goals declaratively, rather than describing how to achieve them. This simplifies human-computer interaction, reduces manual work for internal network administrators, and lowers the barrier to adoption for external industry application customers.

[0004] However, the currently proposed mechanism for registering and discovering intent capability description information has not yet been defined in a scenario-based manner, and there is currently no detailed definition of how to decompose a complex intent.

[0005] Summary of the Invention

[0006] The present application provides an intent capability management method, device, system and storage medium to automatically and flexibly discover and trigger the intent function processing of the corresponding manufacturer's product version based on the intentions of different users.

[0007] In a first aspect, a method for managing intent capabilities is provided, which is performed by an intent directory or a circuit or chip used for an intent directory.

[0008] The method includes: receiving a subscription request from an intent requester or an intent producer of the network layer, wherein the subscription request is used to subscribe to the intent capability description information of the target intent producer of the network layer or network element layer related to the first service; and sending a subscription response to the intent requester or the intent producer of the network layer, wherein the subscription response includes the intent capability description information of the target intent producer of the network layer or network element layer.

[0009] In this aspect, the intent requester subscribes to the intent capability description information of the target intent producer of the network layer related to the service from the intent directory based on the received intent request, and sends a first call indication to the target intent producer of the network layer, the first call indication being used to indicate the call of the target intent producer of the network layer; the target intent producer of the network layer subscribes to the intent capability description information of the target intent producer of the network element layer related to the service from the intent directory according to the first call indication, and calls at least one target intent producer of the network element layer; and the at least one target intent producer of the network element layer configures the network element related to the first service according to the call indication. This can realize automatic and flexible discovery and triggering of intent function processing of the corresponding manufacturer's product version according to the intentions of different users.

[0010] In one possible implementation, the method also includes: receiving an intent registration request from at least one intent producer of the network layer or the network element layer, the intent registration request including intent capability description information of at least one intent producer of the network layer or the network element layer; and sending an intent registration response to at least one intent producer of the network layer or the network element layer.

[0011] In this implementation, at least one intent producer of the network layer and the network element layer registers its own intent capability description information to the intent directory in advance, so that when the intent directory receives the intent request from the intent requester, it can call the corresponding intent producer of the network layer and the network element layer to execute the intent function.

[0012] In another possible implementation, the method also includes: receiving an update request from the target intent producer of the network element layer, the update request being used to request an update of the intent capability description information of the target intent producer of the network layer or the network element layer; and sending an update response to the target intent producer of the network element layer.

[0013] In this implementation, when executing the intent, the target intent producer of the network element layer determines that the intent capability description information of the network element layer has been updated, and promptly sends an update request to the intent directory. This allows the intent requester and the intent producer of the network layer to promptly obtain the updated intent capability description information of the target intent producer of the network element layer, thereby improving the efficiency of model capability management.

[0014] In another possible implementation, the method further includes: sending a subscription update notification to the intent requester or the intent producer of the network layer, wherein the subscription update notification includes updated intent capability description information of the target intent producer of the network layer or the network element layer.

[0015] In another possible implementation, the intent capability description information includes at least one of the following: the role of the intent handler, the processing capability of the intent function, the status of the intent function module, the transmission format of the intent information model, the format of the intent information model, the intent interface type, the access address of the intent function module, the level of the intent function, the supported domains, the name of the intent function, the metadata of the intent function, the intent information model, the intent input, and the intent output.

[0016] In a second aspect, an intent capability management method is provided, which is executed by an intent requester or a circuit or chip for an intent requester.

[0017] The method includes: receiving an intent request, the intent request including a first intent, the first intent being a request for a first service; sending a subscription request to an intent directory, the subscription request being used to subscribe to the intent capability description information of the target intent producer of the network layer related to the first service; receiving a subscription response, the subscription response including the intent capability description information of the target intent producer of the network layer; and sending a first call indication to the target intent producer of the network layer, the first call indication being used to indicate the call of the target intent producer of the network layer.

[0018] In this aspect, the intent requester subscribes to the intent capability description information of the target intent producer of the network layer related to the service from the intent directory based on the received intent request, and sends a first call indication to the target intent producer of the network layer, the first call indication being used to indicate the call of the target intent producer of the network layer; the target intent producer of the network layer subscribes to the intent capability description information of the target intent producer of the network element layer related to the service from the intent directory according to the first call indication, and calls at least one target intent producer of the network element layer; and the at least one target intent producer of the network element layer configures the network element related to the first service according to the call indication. This can realize automatic and flexible discovery and triggering of intent function processing of the corresponding manufacturer's product version according to the intentions of different users.

[0019] In one possible implementation, the intent capability description information includes at least one of the following: the role of the intent handler, the processing capability of the intent function, the status of the intent function module, the transmission format of the intent information model, the format of the intent information model, the intent interface type, the access address of the intent function module, the level of the intent function, the supported domains, the name of the intent function, the metadata of the intent function, the intent information model, the intent input, and the intent output.

[0020] In a third aspect, an intent capability management method is provided, which is executed by a target intent producer of a network layer or a circuit or chip for a target intent producer of a network layer.

[0021] The method includes: receiving a first call indication from an intent requester, the first call indication being used to indicate a call to a target intent producer of a network layer related to a first service; sending a subscription request to an intent directory according to the first call indication, the subscription request being used to subscribe to intent capability description information of at least one target intent producer of a network element layer related to the first service; receiving a subscription response from the intent directory, the subscription response including intent capability description information of at least one target intent producer of the network element layer; and sending a second call indication to at least one target intent producer of the network element layer, the second call indication being used to indicate a call to at least one target intent producer of the network element layer.

[0022] In this aspect, the intent requester subscribes to the intent capability description information of the target intent producer of the network layer related to the service from the intent directory based on the received intent request, and sends a first call indication to the target intent producer of the network layer, the first call indication being used to indicate the call of the target intent producer of the network layer; the target intent producer of the network layer subscribes to the intent capability description information of the target intent producer of the network element layer related to the service from the intent directory according to the first call indication, and calls at least one target intent producer of the network element layer; and the at least one target intent producer of the network element layer configures the network element related to the first service according to the call indication. This can realize automatic and flexible discovery and triggering of intent function processing of the corresponding manufacturer's product version according to the intentions of different users.

[0023] In one possible implementation, the method further includes: sending an intent registration request to the intent directory, the intent registration request including intent capability description information of the target intent producer of the network layer; and receiving an intent registration response from the intent directory.

[0024] In this implementation, at least one intent producer of the network layer registers its own intent capability description information to the intent directory in advance, so that when the intent directory receives the intent request from the intent requester, it can call the corresponding network layer and network element layer intent producer to execute the intent function.

[0025] In another possible implementation, the method further includes: receiving a subscription update notification from the intent directory, wherein the subscription update notification includes updated intent capability description information of the target intent producer of the network element layer.

[0026] In this implementation, when executing the intent, the target intent producer of the network element layer determines that the intent capability description information of the network element layer has been updated, and promptly sends an update request to the intent directory. This allows the network layer intent producer to promptly obtain the updated intent capability description information of the target intent producer of the network element layer, thereby improving the efficiency of model capability management.

[0027] In another possible implementation, the intent capability description information includes at least one of the following: the role of the intent handler, the processing capability of the intent function, the status of the intent function module, the transmission format of the intent information model, the format of the intent information model, the intent interface type, the access address of the intent function module, the level of the intent function, the supported domains, the name of the intent function, the metadata of the intent function, the intent information model, the intent input, and the intent output.

[0028] In a fourth aspect, an intent capability management method is provided, which is executed by at least one target intent producer of a network element layer or a circuit or chip for at least one target intent producer of a network element layer.

[0029] The method includes: receiving a second call indication from an intent producer at the network layer, the second call indication being used to indicate calling at least one target intent producer at the network element layer; and configuring the network element related to the first service according to the second call indication.

[0030] In this aspect, at least one target intent producer at the network element layer configures the network element related to the first service according to the call instruction, which can realize automatic and flexible discovery and triggering of intent function processing of the corresponding manufacturer's product version according to the intent of different users.

[0031] In one possible implementation, the method further includes: sending an intent registration request to an intent directory, the intent registration request including intent capability description information of a target intent producer at the network element layer; and receiving an intent registration response from the intent directory.

[0032] In this implementation, at least one intent producer at the network element layer registers its own intent capability description information to the intent directory in advance, so that when the intent directory receives the intent request from the intent requester, it can call the corresponding network layer and network element layer intent producer to execute the intent function.

[0033] In another possible implementation, the method also includes: determining that the intent capability description information of the network element is updated; sending an update request to the intent directory, wherein the update request is used to request an update of the intent capability description information of the target intent producer of the network element layer; and receiving an update response from the intent directory.

[0034] In this implementation, in this implementation, when the target intent producer of the network element layer determines that the intent capability description information of the network element layer has been updated during the execution of the intent, it promptly sends an update request to the intent directory, so that the intent requester and the intent producer of the network layer can obtain the updated intent capability description information of the target intent producer of the network element layer in a timely manner, thereby improving the efficiency of model capability management.

[0035] In another possible implementation, the intent capability description information includes at least one of the following: the role of the intent handler, the processing capability of the intent function, the status of the intent function module, the transmission format of the intent information model, the format of the intent information model, the intent interface type, the access address of the intent function module, the level of the intent function, the supported domains, the name of the intent function, the metadata of the intent function, the intent information model, the intent input, and the intent output.

[0036] In a fifth aspect, an intent capability management method is provided, which is executed by an intent capability management system, wherein the intent capability management system includes an intent requester, an intent directory, a target intent producer at the network layer, and at least one target intent producer at the network element layer.

[0037] The method includes: an intent requester receives an intent request, the intent request includes a first intent, and the first intent is a request for a first service; the intent requester sends a first subscription request to an intent directory, and the first subscription request is used to subscribe to the intent capability description information of the target intent producer of the network layer related to the first service; the intent directory sends a first subscription response to the intent requester, and the first subscription response includes the intent capability description information of the target intent producer of the network layer; the intent requester sends a first call indication to the target intent producer of the network layer, and the first call indication is used to indicate the call of the target intent producer of the network layer; the target intent producer of the network layer sends a first subscription response to the intent requester according to the first subscription response. A call indication is provided to send a second subscription request to the intent directory, where the second subscription request is used to subscribe to the intent capability description information of at least one target intent producer of the network element layer related to the first service; the intent directory sends a second subscription response to the intent producer of the network layer, where the second subscription response includes the intent capability description information of the target intent producer of the network layer or network element layer; the intent producer of the network layer sends a second call indication to at least one target intent producer of the network element layer, where the second call indication is used to indicate the call of at least one target intent producer of the network element layer; and the at least one target intent producer of the network element layer configures the network element related to the first service according to the second call indication.

[0038] In a sixth aspect, an intent capability management device is provided that can implement the method of the first aspect or any implementation of the first aspect. For example, the device can be a chip or circuit. The above method can be implemented through software, hardware, or hardware executing corresponding software.

[0039] In one possible implementation, the device includes: a transceiver unit, and may also include a processing unit; wherein the transceiver unit is used to receive a subscription request from an intent requester or an intent producer of the network layer, and the subscription request is used to subscribe to the intent capability description information of the target intent producer of the network layer or network element layer related to the first service; and the transceiver unit is also used to send a subscription response to the intent requester or the intent producer of the network layer, and the subscription response includes the intent capability description information of the target intent producer of the network layer or network element layer.

[0040] Optionally, the transceiver unit is also used to receive an intent registration request from at least one intent producer of the network layer or the network element layer, the intent registration request including intent capability description information of at least one intent producer of the network layer or the network element layer; and the transceiver unit is also used to send an intent registration response to at least one intent producer of the network layer or the network element layer.

[0041] Optionally, the transceiver unit is also used to receive an update request from the target intent producer of the network element layer, and the update request is used to request an update of the intent capability description information of the target intent producer of the network layer or the network element layer; and the transceiver unit is also used to send an update response to the target intent producer of the network element layer.

[0042] Optionally, the transceiver unit is further used to send a subscription update notification to the intent requester or the intent producer of the network layer, and the subscription update notification includes updated intent capability description information of the target intent producer of the network layer or the network element layer.

[0043] Optionally, the intent capability description information includes at least one of the following: intent handler role, processing capability of intent function, status of intent function module, transmission format of intent information model, format of intent information model, intent interface type, access address of intent function module, level of intent function, supported domains, name of intent function, metadata of intent function, intent information model, intent input, and intent output.

[0044] In a seventh aspect, an intent capability management device is provided that can implement the method of the second aspect or any implementation of the second aspect. For example, the device can be a chip or circuit. The above method can be implemented through software, hardware, or hardware executing corresponding software.

[0045] In one possible implementation, the device includes: a transceiver unit, and may also include a processing unit; wherein the transceiver unit is used to receive an intent request, the intent request includes a first intent, and the first intent is a request to perform a first service; the transceiver unit is also used to send a subscription request to the intent directory, and the subscription request is used to subscribe to the intent capability description information of the target intent producer of the network layer related to the first service; the transceiver unit is also used to receive a subscription response, and the subscription response includes the intent capability description information of the target intent producer of the network layer; and the transceiver unit is also used to send a first call indication to the target intent producer of the network layer, and the first call indication is used to indicate the call of the target intent producer of the network layer.

[0046] Optionally, the intent capability description information includes at least one of the following: intent handler role, processing capability of intent function, status of intent function module, transmission format of intent information model, format of intent information model, intent interface type, access address of intent function module, level of intent function, supported domains, name of intent function, metadata of intent function, intent information model, intent input, and intent output.

[0047] In an eighth aspect, an intent capability management device is provided that can implement the method described in the third aspect or any implementation of the third aspect. For example, the device can be a chip or circuit. The method can be implemented through software, hardware, or hardware executing corresponding software.

[0048] In one possible implementation, the device includes: a transceiver unit, and may also include a processing unit; wherein the transceiver unit is used to receive a first call indication from an intent requester, the first call indication being used to indicate a call to a target intent producer of a network layer related to a first service; the transceiver unit is also used to send a subscription request to an intent directory based on the first call indication, the subscription request being used to subscribe to intent capability description information of at least one target intent producer of a network element layer related to the first service; the transceiver unit is also used to receive a subscription response from the intent directory, the subscription response including intent capability description information of at least one target intent producer of the network element layer; and the transceiver unit is also used to send a second call indication to at least one target intent producer of the network element layer, the second call indication being used to indicate a call to at least one target intent producer of the network element layer.

[0049] Optionally, the transceiver unit is further used to send an intent registration request to the intent directory, wherein the intent registration request includes the intent capability description information of the target intent producer of the network layer; and the transceiver unit is further used to receive an intent registration response from the intent directory.

[0050] Optionally, the transceiver unit is further configured to receive a subscription update notification from the intent directory, wherein the subscription update notification includes updated intent capability description information of the target intent producer of the network element layer.

[0051] Optionally, the intent capability description information includes at least one of the following: intent handler role, processing capability of intent function, status of intent function module, transmission format of intent information model, format of intent information model, intent interface type, access address of intent function module, level of intent function, supported domains, name of intent function, metadata of intent function, intent information model, intent input, and intent output.

[0052] In a ninth aspect, an intent capability management device is provided that can implement the method of the fourth aspect or any implementation of the fourth aspect. For example, the device can be a chip or circuit. The above method can be implemented through software, hardware, or hardware executing corresponding software.

[0053] In one possible implementation, the device includes: a transceiver unit and a processing unit; wherein the transceiver unit is used to receive a second call indication from an intent producer of the network layer, and the second call indication is used to indicate the call of at least one target intent producer of the network element layer; and the processing unit is used to configure the network element related to the first service according to the second call indication.

[0054] Optionally, the transceiver unit is further used to send an intent registration request to the intent directory, wherein the intent registration request includes the intent capability description information of the target intent producer of the network element layer; and the transceiver unit is further used to receive an intent registration response from the intent directory.

[0055] Optionally, the processing unit is also used to determine whether the intent capability description information of the network element has been updated; the transceiver unit is also used to send an update request to the intent directory, and the update request is used to request an update of the intent capability description information of the target intent producer of the network element layer; and the transceiver unit is also used to receive an update response from the intent directory.

[0056] Optionally, the intent capability description information includes at least one of the following: intent handler role, processing capability of intent function, status of intent function module, transmission format of intent information model, format of intent information model, intent interface type, access address of intent function module, level of intent function, supported domains, name of intent function, metadata of intent function, intent information model, intent input, and intent output.

[0057] In combination with any one of aspects 6 to 9 or aspects 6 to 9, in another possible implementation, the intent capability management device in any one of aspects 6 to 9 or aspects 6 to 9 includes a processor coupled to a memory; the processor is configured to support the device to perform the corresponding functions in the above-mentioned intent capability management method. The memory is used to couple with the processor, which stores the necessary programs (instructions) and / or data for the device. Optionally, the intent capability management device may further include a communication interface for supporting communication between the device and other network elements. Optionally, the memory may be located inside the intent capability management device or outside the intent capability management device.

[0058] In combination with the sixth to ninth aspects or any one of the sixth to ninth aspects, in another possible implementation, the intention capability management device in the sixth to ninth aspects or any one of the sixth to ninth aspects includes a processor and a transceiver, the processor is coupled to the transceiver, and the processor is used to execute a computer program or instruction to control the transceiver to receive and send information; when the processor executes the computer program or instruction, the processor is also used to implement the above method through a logic circuit or execute code instructions. Wherein, the transceiver can be a transceiver, a transceiver circuit or an input-output interface, which is used to receive signals from other devices outside the intention capability management device and transmit them to the processor or send signals from the processor to other devices outside the intention capability management device. When the intention capability management device is a chip, the transceiver is a transceiver circuit or an input-output interface.

[0059] When the intent capability management device in any of aspects 6 to 9 or 6 to 9 is a chip or chip module, the sending unit may be an output unit, such as an output circuit or a communication interface; and the receiving unit may be an input unit, such as an input circuit or a communication interface. When the intent capability management device is a device, the sending unit may be a transmitter or a transmitter; and the receiving unit may be a receiver or a receiver.

[0060] In the tenth aspect, an intent capability management system is provided, including an intent directory, an intent requester, a target intent producer at the network layer, and at least one target intent producer at the network element layer, wherein the intent directory is used to execute the method as described in the first aspect or any one of the implementations of the first aspect, the intent requester is used to execute the method as described in the second aspect or any one of the implementations of the second aspect, the target intent producer at the network layer is used to execute the method as described in the third aspect or any one of the implementations of the third aspect, and the at least one target intent producer at the network element layer is used to execute the method as described in the fourth aspect or any one of the implementations of the fourth aspect.

[0061] In the eleventh aspect, a computer-readable storage medium is provided, in which a computer program or instruction is stored. When a computer executes the computer program or instruction, the methods described in the above aspects are implemented.

[0062] In a twelfth aspect, a computer program product comprising instructions is provided, which, when executed on an intent capability management device, causes the intent capability management device to execute the methods described in the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] Figure 1 shows an example of TMF intent capability description information;

[0064] FIG2 is a schematic diagram of the architecture of an intent capability management system provided in an embodiment of the present application;

[0065] Figure 3 is a schematic diagram of the translation and reference of the intention function module;

[0066] FIG4 is a schematic diagram of the capabilities of the intent directory according to an embodiment of the present application;

[0067] FIG5 is a flow chart of an intent capability management method provided in an embodiment of the present application;

[0068] FIG6 is a flow chart of another method for managing intent capabilities according to an embodiment of the present application;

[0069] FIG7 is a schematic diagram of the registration and subscription process in a DNN dedicated line activation scenario according to an embodiment of the present application;

[0070] FIG8 is a flowchart of an intent capability management method in a DNN dedicated line activation scenario according to an embodiment of the present application;

[0071] FIG9 is a schematic diagram of the structure of an intent capability management device provided in an embodiment of the present application;

[0072] FIG10 is a schematic structural diagram of another intent capability management device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0073] The embodiments of the present application are described below in conjunction with the drawings in the embodiments of the present application.

[0074] The following at least one (item) involved in this application indicates one (item) or more (items). More than one (item) refers to two (items) or more than two (items). "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. In addition, it should be understood that although the terms first, second, etc. may be used to describe each object in this application, these objects should not be limited to these terms. These terms are only used to distinguish each object from each other.

[0075] The terms "including" and "having" and any variations thereof mentioned in the following description of this application are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units that are not listed, or may optionally include other steps or units that are inherent to these processes, methods, products or devices. It should be noted that, in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any method or design described in this application as "exemplary" or "for example" should not be interpreted as being more preferred or more advantageous than other methods or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete way.

[0076] The following specific embodiments illustrate the implementation of the present application. Those skilled in the art can understand other advantages and effects of the present application from the contents disclosed in this specification. Although the description of the present application will be introduced in conjunction with the preferred embodiment, this does not mean that the features of this application are limited to this implementation. On the contrary, the purpose of introducing the application in conjunction with the implementation is to cover other options or modifications that may be extended based on the claims of the present application. In order to increase the in-depth understanding of the present application, the following description will contain many specific details. The present application can also be implemented without using these details. In addition, in order to avoid confusion or blurring the focus of the present application, some specific details will be omitted in the description. It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other unless there is a conflict.

[0077] Hereinafter, if used, the terms "first," "second," etc., are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly specifying the quantity of the technical features being referred to. Thus, a feature qualified as "first," "second," etc. may explicitly or implicitly include one or more of the features. Throughout the description of this application, unless otherwise specified, "plurality" means two or more.

[0078] The following are definitions of several terms that may be involved in the embodiments of this application:

[0079] Intent: An intent is a formal specification of all expectations, including requirements, goals, and constraints for a technical system. An intent object is a structured representation of an intent.

[0080] Intent handler: An intent handler accepts an intent object, parses its structured intent and its satisfaction status, and operates the domain it is responsible for accordingly.

[0081] Intent Management Function: The intent processing capability exposed by an intent handler is called the intent management function, or intent function, which can also be viewed as the function corresponding to the intent model. The intent management function module receives the intent object corresponding to the intent function, parses the module's internal intent model, and completes the execution of the intent function. An intent handler can contain multiple intent management function modules.

[0082] Intent capability description: Details describing the intent management function.

[0083] Intent management interface: Describes a type of intent capability. The intent capability type, intent input, and intent output define an intent management interface. An intent management interface can be implemented by multiple intent handlers providing intent management capabilities.

[0084] Intent Catalog: As an intent function library, it provides the ability to manage intent functions. Each intent function record stored in it is the intent capability description information.

[0085] Intent Producer: Provides intent functionality.

[0086] Intent Consumer: Uses the intent feature.

[0087] The digital economy is rapidly developing, and the global telecommunications industry is accelerating its transformation towards network automation and intelligent upgrades. Low-cost, efficient, and simplified operations and maintenance methods, along with the ability to rapidly deploy networks to meet diverse service needs, are increasingly becoming a key focus for operators. Intent-driven networking (IDN) has emerged to address the challenges presented by network technology evolution, rapid service growth, and complex O&M management. IDN emphasizes the intended outcomes of network services, decoupling system expectations from specific implementation details. It automatically translates, verifies, activates, and assures network reliability based on operator intent, achieving the desired network configuration. Through intent-driven interaction, users and operators express their service expectations and business objectives declaratively, rather than describing how to achieve them. This simplifies human-computer interaction, reduces manual work for internal network administrators, and lowers the barrier to adoption for external industry application clients.

[0088] Intent is an expectation for service or network management, including requirements, goals and constraints, and has nothing to do with system implementation. This application focuses on network operation intent. Intent expresses expectations for the management and control of a series of network elements, without paying attention to the implementation details of the management of network elements. For example, the user's intention may be to open a data network name (DNN) dedicated line in a certain area (certain network elements need to be configured), and at the same time, some specific communication requirements need to be met. Intent can be expressed in natural language or in structured data objects.

[0089] Currently, it is possible to construct an intent model through a rule-based modeling method to convert intent into specific execution strategies. For example, in the DNN dedicated line activation scenario, the intent model can be established to complete the parsing and translation of the DNN dedicated line activation intent input and generate configuration commands for related network elements. In an intent capability management system involving the collaboration of multiple products, different products usually provide corresponding intent functions. During the operation process (especially the upgrade process), changes to the intent function module of a single product will lead to modifications to the related intent model, and the intent function modules are tightly coupled. In cross-vendor scenarios, it is difficult to standardize the intent modeling language within the intent processing systems of each vendor, especially in specific scenario applications, where it is difficult for intent function modules to reference each other.

[0090] Currently, TeleManagement Forum (TMF) IG1253D has proposed a mechanism for registering and discovering intent capability description information. The intent-related model involved is based on RDF / RDFS. The defined TMF intent capability description information is shown in Figure 1. The specific TMF intent capability description information attributes are shown in Table 1 below:

[0091] Table 1

[0092] However, TMF's intent capability description information has the following shortcomings:

[0093] 1. Insufficient fields for describing intent capabilities make it difficult to express the intent capabilities provided by the intent handler for intent capability matching, such as manufacturer information and real-time processing capabilities.

[0094] 2. Intent capability descriptions have not yet been defined for specific scenarios. A complex intent can be broken down into multiple sub-intents along different dimensions, but how this decomposition is done is not defined in detail. For example, in the DNN dedicated line deployment scenario, how is a network-level intent decomposed into network element-level intents? Furthermore, each sub-intent is handled by an intent management module. How the intent capability description of a top-level intent is decomposed into each sub-intent has not yet been defined. Furthermore, no scenario-specific decomposition examples have been seen, particularly those defining how to decompose to achieve decoupling of intent management modules.

[0095] 3. The intent directory only provides passive capabilities such as adding, deleting, modifying, and querying, and lacks active initiation capabilities such as subscription / notification.

[0096] In view of this, the present application proposes a solution in which the intent capability management system automatically and flexibly discovers and triggers the intent function processing of the corresponding manufacturer's product version according to different user intentions during the intent lifecycle management process. Among them, the intent function modules are hierarchically decoupled according to different manufacturers and product components, and different products provide their own intent function modules to express the implementation of the same functional interface. The capabilities can be registered in the intent directory, and the product versions of the intent function modules can be decoupled and integrated with different manufacturers. As the products of various manufacturers change, different versions of intent function modules of different products will appear. The versions of intent function modules provided by different products need to be decoupled to eliminate the negative impact of the coupling relationship during the operation process (especially during the upgrade process).

[0097] As shown in Figure 2, it is a schematic diagram of the architecture of an intent capability management system provided in an embodiment of the present application. The intent capability management system includes an intent directory (not shown), an intent requester, one or more network layer intent producers, and one or more network element layer intent producers. Among them, the intent requester is located in the service management layer (service management layer) of the system (referred to as "service layer"), and the intent requester can be the operator's operation support system (OSS). The intent producer of the network management layer (referred to as "network layer") can be a manufacturer's cross-domain management system, which serves as a network intent processor and includes one or more intent function modules. The intent producer of the element management layer (referred to as "element management layer") can be the network element management system corresponding to each domain, which serves as a network element intent processor and includes one or more intent function modules. The domain can be a core network (CN) domain, a transmission domain, an access network domain, etc. Among them, the intent producer of the network layer can conduct parent-child intent negotiation with the intent producer of the network element layer. The parent-child intent capability negotiation refers to the calling of intent functions at different levels. Intent producers at the network element layer can conduct P2P (peer to peer) intent capability negotiation. P2P intent capability negotiation refers to the invocation of intent functions at the same level. In addition, the same intent handler can be located at different levels, and the basis for the hierarchical division is the level at which the intent function is located. This application focuses on the intent function modules at the network layer and the network element layer.

[0098] In the embodiment of the present application, the intent producers at the network layer and the network element layer act as intent processors and need to support the following during the translation process:

[0099] (1) Other intent functions can be called, for example, by referencing other intent functions through the application interface (API). When referencing, the intent input parameters involved are obtained by intent translation;

[0100] (2) You can access the intent catalog to find the required intent function and select the vendor version of the product network element. This can be obtained by inputting the intent and translating it, or automatically discovering and matching it through the intent catalog. Each intent function needs to comply with the intent function interface and can have its own logical implementation.

[0101] (3) The ability to receive notifications from the intent catalog, trigger corresponding operations, and complete the intent closed loop.

[0102] Furthermore, specifically, regarding (1) translation and reference, as shown in Figure 3, the schematic diagram of intent function module translation and reference is a simple example. In the intent capability management system, there are three intent function modules A, B, and C, involving two intent functions: Function1 and Function2. First, the northbound intent request uses Function1 and specifies module B version X; then, module A accepts the request, and the intent model corresponding to module A translates the need to reference Function2. At the same time, according to the intent input, it is parsed to obtain Function2 provided by B version X; then, the intent directory is queried for the intent function description information of Function2 of module B version X, where the intent directory will return Function2 of module B version X.1 based on the version compatibility principle; finally, module A initiates an intent request to module B to execute Function2. Furthermore, the version compatibility principles mentioned in the above steps (which need to be considered during the intent model design and release phase) are: 1) The intent function interface remains unchanged, and the intent model implementation within the intent handler changes. Only the product model itself needs to be updated (updating a minor version does not require modifying the intent input, and the major version intent input specifies a new version number); if the functional interface changes, the interface is forward compatible; only the models that use and implement the new interface need to be modified, and the models that implement the original interface do not need to change; if the functional interface changes, forward compatibility is not possible, and all related models need to change. At this point, the internal implementation update of module B or C only affects itself and does not affect other modules.

[0103] Furthermore, specifically, regarding (2) and (3), the core involved is the capability of the intent directory. As shown in FIG4 , which is a schematic diagram of the capability of the intent directory of an embodiment of the present application, the core capabilities of the intent directory include: 1) registering / deregistering intent function description information; 2) subscribing to intent functions; 3) discovering intent functions; n) updating intent function description information, including two main types: the intent handler initiates access to the intent, and the directory is passively updated; the intent directory actively accesses the intent handler for active updates. For intent consumers, they can use the capabilities of the intent directory to better complete the four stages of intent, including: 1) in the intent translation, verification, and activation stages, use the intent function discovery capability of the intent directory to call the appropriate intent function module to execute the corresponding intent function; 2) in the intent verification conflict check and intent maintenance stages, use the notification capability of the intent directory to trigger the corresponding response operations.

[0104] Furthermore, regarding the registration of intent function description information, the following table defines the intent function description information. The same functional interface (same function, same level, same intent input and output) can be implemented by multiple different manufacturers, products, and versions. Intent decomposition, that is, breaking down an intent into multiple sub-intents, not only involves selecting appropriate intent functions, but also involves translating the expectationModel in the table, that is, breaking down the expectationModel of an intent into the expectationModels of multiple sub-intents.

[0105] Table 2

[0106] The following is a detailed description with reference to specific embodiments:

[0107] As shown in Figure 5, a flowchart of an intent capability management method provided in an embodiment of the present application is provided. Exemplarily, the method may include the following steps:

[0108] S501. The intent requester receives an intent request from an intent user.

[0109] The intent request includes a first intent, wherein the first intent is a request for performing a first service. Performing the first service requires configuration of one or more network elements of one or more intent handlers at a network element layer.

[0110] S502: The intent requester sends a first subscription request to the intent directory. Correspondingly, the intent directory receives the first subscription request.

[0111] After the intent requester receives the intent request, which intent producer will execute the intent request and how the intent capability matches the intent request. The intent requester needs to first subscribe to the intent capability description information of the target intent producer of the network layer related to the first business from the intent directory. Therefore, the intent requester sends a first subscription request to the intent directory, wherein the first subscription request is used to subscribe to the intent capability description information of the target intent producer of the network layer related to the first business. The intent directory stores the intent capability description information of one or more intent producers of the network layer, and its format is shown in Table 2 above.

[0112] S503. The intent directory sends a first subscription response to the intent requester. Correspondingly, the intent requester receives the first subscription response.

[0113] After receiving the first subscription request, the intent directory obtains the intent capability description information of the target intent producer of the network layer related to the first business stored in it, and sends a first subscription response to the intent requester. The first subscription response includes the intent capability description information of the target intent producer of the network layer. The intent capability description information includes at least one of the following: the role of the intent handler, the processing capability of the intent function, the status of the intent function module, the transmission format of the intent information model, the format of the intent information model, the intent interface type, the access address of the intent function module, the level of the intent function, the supported domains, the name of the intent function, the metadata of the intent function, the intent information model, the intent input, and the intent output.

[0114] S504: The intent requester sends a first call indication to the target intent producer of the network layer. Correspondingly, the target intent producer of the network layer receives the first call indication.

[0115] The intent requester parses the intent capability description information of the target intent producer of the network layer returned by the intent directory, and then sends a first call indication to the target intent producer of the network layer, wherein the first call indication is used to indicate the call of the target intent producer of the network layer.

[0116] For example, the first call indication is an API request, the request address of the first call indication is endpoint+function+metadata.product in the intent capability description information, and the request body is an expectationModel instance.

[0117] S505: The target intent producer at the network layer sends a second subscription request to the intent directory according to the first call instruction. Correspondingly, the intent directory receives the second subscription request.

[0118] After receiving the intent request from the intent requester, the target intent producer at the network layer parses the corresponding internal intent model and translates the network element of at least one target intent producer at the network element layer involved in the scenario. Therefore, a second subscription request is sent to the intent directory, wherein the second subscription request is used to subscribe to the intent capability description information of at least one target intent producer at the network element layer related to the first business.

[0119] S506. The intent directory sends a second subscription response to the target intent producer of the network layer. Correspondingly, the target intent producer of the network layer receives the second subscription response.

[0120] The intent directory pre-stores the intent capability description information of one or more intent producers at the network element layer. Therefore, after receiving the second subscription request, the intent capability description information of at least one target intent producer at the network element layer related to the first service is searched, and a second subscription response is sent to the target intent producer at the network layer, wherein the second subscription response includes the intent capability description information of at least one target intent producer at the network element layer.

[0121] S507. The target intent producer of the network layer sends a second call indication to at least one target intent producer of the network element layer. Correspondingly, the at least one target intent producer of the network element layer receives the second call indication.

[0122] After receiving the second subscription response, the target intent producer of the network layer sends a second call indication to each of the at least one target intent producer of the network element layer, wherein the second call indication is used to indicate the call of at least one target intent producer of the network element layer, and each target intent producer of the network element layer completes the configuration of the network element related to the first service.

[0123] For example, the second call indication may be an API request, the request address of the API request is endpoint+function++metadata.product in the intent capability description information, and the request body is an expectationModel instance.

[0124] S508. At least one target intention producer at the network element layer configures the network element related to the first service according to the second call indication.

[0125] After receiving the second call indication, each target intention producer at the network element layer completes the configuration of the network element related to the first service.

[0126] According to an intent capability management method provided by an embodiment of the present application, an intent requester subscribes to the intent capability description information of the target intent producer of the network layer related to the service from the intent directory based on the received intent request, and sends a first call indication to the target intent producer of the network layer, the first call indication being used to indicate the call of the target intent producer of the network layer; the target intent producer of the network layer subscribes to the intent capability description information of the target intent producer of the network element layer related to the service from the intent directory based on the first call indication, and calls at least one target intent producer of the network element layer; and the at least one target intent producer of the network element layer configures the network element related to the first service based on the call indication. This can realize automatic and flexible discovery and triggering of intent function processing of the corresponding manufacturer's product version based on the intentions of different users.

[0127] The above embodiment describes how the intent directory can provide subscription services to intent requesters and network-layer intent producers. The following embodiment describes how network-layer intent producers and network element-layer intent producers can pre-register with the intent directory so that the intent directory can provide the above subscription services:

[0128] As shown in Figure 6, it is a flowchart of another intent capability management method provided by an embodiment of the present application. Exemplarily, the method may include the following steps:

[0129] S601. A target intent producer at the network layer sends a first intent registration request to an intent directory. Correspondingly, the intent directory receives the first intent registration request.

[0130] In this embodiment, the target intent producer of the network layer acts as an intent producer and can register the network layer intent function with the intent directory and send a first intent registration request to the intent directory, wherein the first intent registration request includes the intent capability description information of the target intent producer of the network layer.

[0131] S602: The intent directory sends a first intent registration response to the target intent producer of the network layer. Correspondingly, the target intent producer of the network layer receives the first intent registration response.

[0132] The first intent registration response is used to indicate that the intent directory has successfully registered the intent capability description information of the target intent producer at the network layer in the intent directory.

[0133] S603. The target intent producer at the network element layer sends a second intent registration request to the intent directory. Correspondingly, the intent directory receives the second intent registration request.

[0134] The target intent producer at the network element layer acts as an intent producer, registers the intent function of the network element layer with the intent directory, and sends a second intent registration request to the intent directory, wherein the second intent registration request includes the intent capability description information of the target intent producer at the network element layer.

[0135] S604. The intent directory sends a second intent registration response to the target intent producer at the network element layer. Correspondingly, the target intent producer at the network element layer receives the second intent registration response.

[0136] The second intent registration response is used to indicate that the intent directory has successfully registered the intent capability description information of the target intent producer at the network element layer in the intent directory.

[0137] It is understandable that there is no order between the above steps S601, S602 and steps S603, S604.

[0138] S605. The intent requester receives the intent request from the intent user.

[0139] The intention request includes a first intention, and the first intention is a request to perform a first business.

[0140] For the specific implementation of this step, reference may be made to step S501 of the embodiment shown in FIG5 , and details thereof will not be repeated here.

[0141] S606: The intent requester sends a first subscription request to the intent directory. Correspondingly, the intent directory receives the first subscription request.

[0142] The first subscription request is used to subscribe to the intent capability description information of the target intent producer of the network layer related to the first service.

[0143] For the specific implementation of this step, reference may be made to step S502 of the embodiment shown in FIG5 , and details thereof will not be repeated here.

[0144] S607. The intent directory sends a first subscription response to the intent requester. Correspondingly, the intent requester receives the first subscription response.

[0145] The first subscription response includes the intention capability description information of the target intention producer at the network layer.

[0146] For the specific implementation of this step, reference may be made to step S503 of the embodiment shown in FIG5 , and details thereof will not be repeated here.

[0147] S608. The intent requester sends a first call indication to the target intent producer of the network layer. Correspondingly, the target intent producer of the network layer receives the first call indication.

[0148] The first call indication is used to indicate the target intent producer of calling the network layer.

[0149] For the specific implementation of this step, reference may be made to step S504 of the embodiment shown in FIG5 , and details thereof will not be repeated here.

[0150] S609: The target intent producer at the network layer sends a second subscription request to the intent directory according to the first call instruction. Correspondingly, the intent directory receives the second subscription request.

[0151] The second subscription request is used to subscribe to the intention capability description information of the target intention producer at the network element layer related to the first service.

[0152] For the specific implementation of this step, reference may be made to step S505 of the embodiment shown in FIG5 , which will not be described in detail here.

[0153] S610. The intent directory sends a second subscription response to the intent producer of the network layer. Correspondingly, the intent producer of the network layer receives the second subscription response.

[0154] The second subscription response includes the intention capability description information of the target intention producer at the network element layer.

[0155] For the specific implementation of this step, reference may be made to step S506 of the embodiment shown in FIG5 , and details thereof will not be repeated here.

[0156] S611. The intent producer at the network layer sends a second call indication to the target intent producer at the network element layer. The target intent producer at the network element layer receives the second call indication.

[0157] The second call indication is used to indicate the target intention producer of calling the network element layer.

[0158] For the specific implementation of this step, reference may be made to step S507 of the embodiment shown in FIG5 , and details thereof will not be repeated here.

[0159] S612. The target intention producer at the network element layer configures the network elements related to the first service according to the second call instruction.

[0160] For the specific implementation of this step, reference may be made to step S508 of the embodiment shown in FIG5 , and details thereof will not be repeated here.

[0161] S613. The target intent producer at the network element layer determines that the intent capability description information of the network element is updated.

[0162] Exemplarily, the target intent producer at the network element layer finds that the network element related to the first service has an abnormality, and then determines that the intent capability description information of the network element is updated.

[0163] S614. The target intent producer at the network element layer sends an update request to the intent directory. Correspondingly, the intent directory receives the update request.

[0164] After determining that the intent capability description information of the network element layer has been updated, the target intent producer of the network element layer sends an update request to the intent directory, wherein the update request is used to request an update of the intent capability description information of the target intent producer of the network element layer.

[0165] S615. The intent directory sends an update response to the target intent producer at the network element layer. Correspondingly, the target intent producer at the network element layer receives the update response.

[0166] The update response is used to indicate that the schematic directory has successfully received the updated intent capability description information of the target intent producer at the network element layer.

[0167] S616, S617. The intent directory sends a subscription update notification to the intent requester and the intent producer at the network layer respectively. Correspondingly, the intent requester and the intent producer at the network layer receive the subscription update notification.

[0168] Since the intent requester and the intent producer of the network layer have previously subscribed to the intent directory, after the intent directory receives the updated intent capability description information of the target intent producer of the network element layer, it sends a subscription update notification to the intent requester and the intent producer of the network layer respectively, wherein the subscription update notification includes the updated intent capability description information of the target intent producer of the network element layer.

[0169] According to an intent capability management method provided by an embodiment of the present application, at least one intent producer of the network layer or the network element layer pre-registers its own intent capability description information with the intent directory, so that when the intent directory receives an intent request from the intent requester, it can call the corresponding intent producer of the network layer or the network element layer to execute the intent function;

[0170] The intent requester subscribes to the intent capability description information of the target intent producer of the network layer related to the service from the intent directory based on the received intent request, and sends a first call indication to the target intent producer of the network layer, the first call indication is used to indicate the call of the target intent producer of the network layer; the target intent producer of the network layer subscribes to the intent capability description information of the target intent producer of the network element layer related to the service from the intent directory based on the first call indication, and calls at least one target intent producer of the network element layer; and the at least one target intent producer of the network element layer configures the network element related to the first service based on the call indication. It can realize automatic and flexible discovery and triggering of intent function processing of the corresponding manufacturer's product version based on the intentions of different users;

[0171] During the execution of the intent, the target intent producer of the network element layer determines that the intent capability description information of the network element layer has been updated, and promptly sends an update request to the intent directory. This allows the intent requester and the intent producer of the network layer to promptly obtain the updated intent capability description information of the target intent producer of the network element layer, thereby improving the efficiency of model capability management.

[0172] The following uses the DNN dedicated line activation as an example to describe the definition, registration, and subscription of intent capability description information, as well as its intent capability management:

[0173] As shown in Figure 7, it is a schematic diagram of the registration and subscription process in the DNN dedicated line activation scenario of the embodiment of the present application. In the DNN dedicated line activation scenario, two types of network elements, SMF and UPF, are involved. In the intent capability management system, there is one intent requester S and three intent handlers A, X, and Y, where: S is the intent requester of the service layer, which can be the operator's OSS, and uses the intent function as an intent consumer (consumer); A is the manufacturer domain management system, that is, the intent handler of the network layer, and provides the intent function of the network layer as an intent producer (producer), and is also a consumer, using the intent function of the network element layer; X and Y are both network element management systems, that is, the intent handler of the network element layer, and provide intent functions as intent producers. There is an intent directory in the intent capability management system. The operator can provide the intent directory, and each manufacturer registers its own intent function and uses the capabilities of the intent directory; or the manufacturer can provide the intent directory and open its registration capabilities to other manufacturers; or the manufacturer can provide the intent directory and open subscription / discovery capabilities to other manufacturers. In the intent capability description information involved in the intent registration phase, the network layer's expectationModel indicates the input and output of the intent, faces northbound and externally, and adopts the 3GPP format in this embodiment; the network element layer's intent input and output expectationModel is decomposed from the network layer's model and adopts the simplest JSON format in this embodiment. The specific steps for registration and subscription are as follows:

[0174] S701. Network intent handler A, as the intent producer, registers the network layer's DNNService function with the intent directory. The specific intent capability description is as follows. The key fields are identified in the sequence diagram shown in Figure 7:

[0175] S702. Intent handler X acts as an intent producer and registers the DNNService function of the network element layer with the intent directory. The specific intent capability description information of SMF and UPF is as follows. The key fields are marked in the timing diagram shown in Figure 7.

[0176] Configuration capability description of an SMF for the DNN dedicated line of intent handler X:

[0177] A UPF configuration capability description for the DNN dedicated line of intent handler X:

[0178] S703. Intent handler Y, as the intent producer, registers the DNNService function of the network element layer with the intent directory. The specific intent capability description information of SMF and UPF is as follows. The key fields have been identified in the timing diagram shown in Figure 7. The capability description information is similar to that of X, and only the differences are reflected below.

[0179] An SMF configuration capability description for the DNN dedicated line of intent handler Y:

[0180] The UPF configuration capability description information of the DNN dedicated line of intent handler Y is as follows:

[0181] S704. The intent requester S of the service layer acts as an intent consumer and subscribes to the DNNService intent function of the network layer from the intent directory, and can initiate the DNN dedicated line activation intent.

[0182] S705. The intent processor A of the network layer acts as an intent consumer and subscribes to the intent function of the DNNService of the network element layer SMF and UPF network elements from the intent directory. It can initiate intent requests to the corresponding intent function modules and configure the corresponding network elements.

[0183] As shown in Figure 8, it is a flowchart of the intent capability management method in the DNN dedicated line activation scenario of the embodiment of the present application. Exemplarily, the method may include the following steps:

[0184] S801. Intent requester S (e.g., OSS) receives a northbound intent request. This intent request is used to request the opening of a DNN dedicated line and the configuration of the SMF network element of intent handler X and the UPF network element of intent handler Y.

[0185] For example, the intent user initiates an intent request to the intent requester S of the service layer, requesting to open a DNN dedicated line and configure the SMF network element of intent processor X and the UPF network element of intent processor Y.

[0186] S802. The intent requester sends a discovery request to the intent directory. The discovery request is used to find the DNNService intent producer at the network layer.

[0187] After receiving the discovery request, the intent directory returns the capability description information of the network layer intent function DNNService of intent handler A to the intent requester.

[0188] Exemplarily, the intent handler A may be a vendor domain management system.

[0189] S803. Intent requester S parses the intent capability description information of the network layer intent function DNNService of intent handler A returned by the intent directory, and then initiates an API request (i.e., DNN dedicated line activation intent request) to intent handler A. The request address is the endpoint+function+metadata.product in the intent capability description information, and the request body is an expectationModel instance. The example is as follows:

[0190] S804. After receiving the DNN dedicated line activation intent request from the service layer intent handler S, intent handler A, as the network layer intent producer, parses the corresponding internal intent model and translates the scenario involving one SMF network element provided by intent handler X and two UPF network elements provided by intent handler Y. It needs to further use the intent functions of two network element layers: 1) the SMF configuration function of the DNNService from intent handler X, and the corresponding intent input parameters; 2) the UPF configuration function of the DNNService from intent handler Y, and the corresponding intent input parameters.

[0191] S805. Intent handler A initiates a discovery request to the intent directory to find the intent producer of the DNNService network element SMF at the network element layer. Then, the intent directory accepts the discovery request of intent handler A and returns the intent capability description information of the network element layer intent function DNNService network element SMF of intent handler X.

[0192] S806. Intent handler A parses the intent capability description information of the network element layer intent function DNNService network element SMF of intent handler X returned by the intent directory, and then initiates an API request to intent handler X. Intent handler X, as the network element layer intent producer, completes the configuration of the SMF network element. The request address is endpoint+function++metadata.product in the intent capability description information, and the request body is an expectationModel instance. The example is as follows:

[0193] S807. Intent handler A initiates a discovery request to the intent directory to search for the intent producer of the network element layer DNNService network element UPF. Then, the intent directory accepts the discovery request of intent handler A and returns the intent capability description information of the network element layer intent function DNNService network element UPF of intent handler Y.

[0194] S808. Intent handler A parses the intent capability description information of the network element layer intent function DNNService network element UPF of intent handler Y returned by the intent directory, and then initiates two API requests to intent handler Y. Intent handler Y, as the network element layer intent producer, completes the configuration of the UPF network element. The request address is endpoint+function++metadata.product in the intent capability description information, and the request body is an expectationModel instance. The two request samples are as follows:

[0195] S809. Intent handler A calls the intent functions of intent handlers X and Y, completing the intent translation, verification, and activation of the DNN dedicated line activation scenario. The configuration is complete and the intent closed-loop control phase begins.

[0196] S810. Intent handler X discovers that the network element SMF has an anomaly, and initiates an update request to the intent directory to update its intent capability description information and enter the SMF anomaly information.

[0197] S811. After the intent catalog updates the intent capability description information of intent handler X, it sends an update notification to the relevant subscribers.

[0198] S812. Intent handler A receives update information about the network element SMF of intent function DNNService of intent handler X from the intent directory, parses it to obtain SMF exceptions, and further triggers the corresponding closed-loop strategy.

[0199] For DNN dedicated line activation intentions involving multiple network elements, the intent capability negotiation solution proposed in this embodiment can achieve collaboration between intent processors of products from multiple vendors, including:

[0200] This embodiment can achieve decoupling of intent handlers. Each network element can come from a different manufacturer and require the corresponding manufacturer to provide the corresponding intent function for processing. How to negotiate intent and select the correct manufacturer's intent function for network element configuration, while ensuring that changes in the product version of a single intent function will not cause changes to other intent functions.

[0201] Decomposition of intent and capability description information: This embodiment describes how to decompose the intent and capability description information corresponding to a northbound intent request into the intent and capability description information corresponding to each network element, and how to define this description information.

[0202] The intent catalog capabilities work together with the four stages of intent. The four stages include intent translation, intent verification, intent activation, and intent closure. This example describes the capabilities required by the intent catalog and how they work together with the four stages to enable DNN dedicated line provisioning.

[0203] It can be understood that in each of the above embodiments, the methods and / or steps implemented by the intent directory can also be implemented by components (such as chips or circuits) that can be used for the intent directory; the methods and / or steps implemented by the intent requester can also be implemented by components (such as chips or circuits) that can be used for the intent requester; the methods and / or steps implemented by the target intent producer of the network layer can also be implemented by components (such as chips or circuits) that can be used for the target intent producer of the network layer; the methods and / or steps implemented by the target intent producer of the network element layer can also be implemented by components (such as chips or circuits) that can be used for the target intent producer of the network element layer.

[0204] The above mainly introduces the solutions provided by the embodiments of the present application from the perspective of the interaction between various entities. Accordingly, the embodiments of the present application also provide an intent capability management device, which is used to implement the various methods described above. The intent capability management device can be the intent directory in the above method embodiments, or a component that can be used for the intent directory; or, the intent capability management device can be the intent requester in the above method embodiments, or a component that can be used for the intent requester; or, the intent capability management device can be the target intent producer of the network layer in the above method embodiments, or a component that can be used for the target intent producer of the network layer; or, the intent capability management device can be the target intent producer of the network element layer in the above method embodiments, or a component that can be used for the target intent producer of the network element layer. It can be understood that in order to implement the above functions, the intent capability management device includes hardware structures and / or software modules corresponding to the execution of each function. It should be readily appreciated by those skilled in the art that, in combination with the various exemplary units and algorithm steps described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a computer software-driven hardware manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0205] The embodiment of the present application can divide the functional modules of the intent capability management device according to the above method embodiment. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing unit. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation.

[0206] Based on the same concept of the above-mentioned intent capability management method, this application also provides the following intent capability management device:

[0207] As shown in FIG9 , a schematic diagram of the structure of an intent capability management device provided in an embodiment of the present application is shown. The intent capability management device 9000 includes a transceiver unit 901 and a processing unit 902 ; wherein:

[0208] When the intent capability management device is used to implement the function of the intent directory in the above method embodiment, the transceiver unit 901 is used to execute the function of the intent directory in steps S502, S503, S505 and S506 in the embodiment as shown in Figure 5; or, the transceiver unit 901 is used to execute the function of the intent target in steps S601-S607, S609, S610, S614-S617 in the embodiment as shown in Figure 6.

[0209] When the intent capability management device is used to implement the functions of the intent requester in the above-mentioned method embodiment, the transceiver unit 901 is used to execute the functions of the intent requester in steps S501-S504 in the embodiment as shown in Figure 5; or, the transceiver unit 901 is used to execute the functions of the intent requester in steps S605-S608 and S616 in the embodiment as shown in Figure 6.

[0210] When the intent capability management device is used to implement the function of the target intent producer of the network layer in the above-mentioned method embodiment, the transceiver unit 901 is used to execute the function of the target intent producer of the network layer in steps S504-S507 in the embodiment as shown in Figure 5; or, the transceiver unit 901 is used to execute the function of the target intent producer of the network layer in steps S601, S602, S608-S611, and S617 in the embodiment as shown in Figure 6.

[0211] When the intent capability management device is used to implement the function of the target intent producer at the network element layer in the above-mentioned method embodiment, the transceiver unit 901 is used to execute the function of the target intent producer at the network element layer in step S507 in the embodiment as shown in Figure 5, and the processing unit 902 is used to execute step S508 in the embodiment as shown in Figure 5; or, the transceiver unit 901 is used to execute the function of the target intent producer at the network element layer in steps S603, S604, S611, S614, and S615 in the embodiment as shown in Figure 6, and the processing unit 902 is used to execute steps S612 and S613 in the embodiment as shown in Figure 6.

[0212] For the specific implementation of the above-mentioned transceiver unit 901 and the processing unit 902, reference may be made to the description in the above-mentioned method embodiment, which will not be repeated here.

[0213] As shown in Figure 10, it is a structural diagram of another intention capability management device provided in an embodiment of the present application. The intention capability management device 10000 includes a processor 1001, and may also include an interface circuit 1002 and a memory 1003 (represented by dotted lines in the figure). The processor 1001 and the interface circuit 1002 are coupled to each other. It will be understood that the interface circuit 1002 can be a transceiver or an input and output interface. The memory 1003 is used to store instructions executed by the processor 1001, or to store input data required for the processor 1001 to run instructions, or to store data generated after the processor 1001 runs instructions. Among them, the processor 1001 is used to implement the functions of the processing unit 902 in the embodiment shown in Figure 9 above; and the interface circuit 1002 is used to implement the functions of the transceiver unit 901 in the embodiment shown in Figure 9 above.

[0214] When the above-mentioned intent capability management device is a chip applied to the intent directory, the chip implements the function of the intent directory in the above-mentioned method embodiment. The chip receives information from other modules in the intent directory (such as a radio frequency module or an antenna), and the information is sent to the intent directory by the intent requester, the target intent producer of the network layer, or the target intent producer of the network element layer; or the chip sends information to other modules in the intent directory (such as a radio frequency module or an antenna), and the information is sent by the intent directory to the intent requester, the target intent producer of the network layer, or the target intent producer of the network element layer.

[0215] When the above-mentioned intent capability management device is a chip applied to the intent requester, the chip implements the function of the intent requester in the above-mentioned method embodiment. The chip receives information from other modules in the intent requester (such as a radio frequency module or an antenna), and the information is sent to the intent requester by the intent directory, the target intent producer of the network layer, or the target intent producer of the network element layer; or the chip sends information to other modules in the intent requester (such as a radio frequency module or an antenna), and the information is sent by the intent requester to the intent directory, the target intent producer of the network layer, or the target intent producer of the network element layer.

[0216] When the above-mentioned intent capability management device is a chip applied to the target intent producer of the network layer, the chip implements the function of the target intent producer of the network layer in the above-mentioned method embodiment. The chip receives information from other modules (such as a radio frequency module or an antenna) in the target intent producer of the network layer, and the information is sent by the intent directory, the intent requester or the target intent producer of the network element layer to the target intent producer of the network layer; or, the chip sends information to other modules (such as a radio frequency module or an antenna) in the target intent producer of the network layer, and the information is sent by the target intent producer of the network layer to the intent directory, the intent requester or the target intent producer of the network element layer.

[0217] When the above-mentioned intent capability management device is a chip applied to the target intent producer of the network element layer, the chip implements the function of the target intent producer of the network element layer in the above-mentioned method embodiment. The chip receives information from other modules (such as a radio frequency module or an antenna) in the target intent producer of the network element layer, and the information is sent to the target intent producer of the network element layer by the intent directory, the intent requester or the target intent producer of the network layer; or, the chip sends information to other modules (such as a radio frequency module or an antenna) in the target intent producer of the network element layer, and the information is sent to the target intent producer of the network element layer by the intent directory, the intent requester or the target intent producer of the network layer.

[0218] In addition, it should be noted that the aforementioned transceiver unit and / or processing unit may be implemented through virtual modules, for example, the processing unit may be implemented through a software function unit or a virtual device, and the transceiver unit may be implemented through a software function or a virtual device. Alternatively, the processing unit or transceiver unit may also be implemented through a physical device, for example, if the device is implemented using a chip / chip circuit, the transceiver unit may be an input / output circuit and / or a communication interface, performing input operations (corresponding to the aforementioned receiving operations) and output operations (corresponding to the aforementioned sending operations); the processing unit is an integrated processor or microprocessor or integrated circuit.

[0219] The division of modules in this application is illustrative and represents only a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in the examples of this application may be integrated into a single processor, exist physically as separate modules, or two or more modules may be integrated into a single module. The aforementioned integrated modules may be implemented in either hardware or software functional modules.

[0220] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0221] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction is executed, the method in the above embodiment is implemented.

[0222] An embodiment of the present application further provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method in the above embodiment.

[0223] An embodiment of the present application also provides an intent capability management system, including the above-mentioned intent capability management device.

[0224] The present application also provides a circuit, which is coupled to a memory and is used to execute the method shown in the above embodiment. The circuit may include a chip circuit.

[0225] It should be noted that the above units or one or more of the units can be implemented by software, hardware, or a combination of the two. When any of the above units or units is implemented by software, the software exists in the form of computer program instructions and is stored in a memory, and a processor can be used to execute the program instructions and implement the above method flow.

[0226] In this application, a processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic block diagrams disclosed in this application. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in this application may be directly executed by a hardware processor, or by a combination of hardware and software modules within the processor.

[0227] The processor can be built into a system on chip (SoC) or ASIC, or it can be a standalone semiconductor chip. In addition to the core that executes software instructions to perform calculations or processing, the processor can also include necessary hardware accelerators, such as field programmable gate arrays (FPGAs), programmable logic devices (PLDs), or logic circuits that implement specialized logic operations.

[0228] When the above units or units are implemented in hardware, the hardware can be any one or any combination of a CPU, a microprocessor, a digital signal processing (DSP) chip, a microcontroller unit (MCU), an artificial intelligence processor, an ASIC, a SoC, an FPGA, a PLD, a dedicated digital circuit, a hardware accelerator or a non-integrated discrete device, which can run the necessary software or not rely on the software to execute the above method flow.

[0229] Optionally, an embodiment of the present application further provides a chip system, comprising: at least one processor and an interface, wherein the at least one processor is coupled to a memory via the interface, and when the at least one processor executes a computer program or instruction in the memory, the chip system executes the method in any of the above method embodiments. Optionally, the chip system may be composed of a chip, or may include a chip and other discrete devices, which is not specifically limited in the embodiments of the present application.

[0230] In the present application, the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or a volatile memory, such as a random-access memory (RAM). The memory is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory in the present application may also be a circuit or any other device that can implement a storage function, for storing program instructions and / or data.

[0231] It should be understood that in the description of this application, unless otherwise specified, " / " indicates that the objects associated with each other are in an "or" relationship. For example, A / B can mean A or B; where A and B can be singular or plural. Also, in the description of this application, unless otherwise specified, "multiple" means two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or plural. In addition, to facilitate the clear description of the technical solutions of the embodiments of this application, in the embodiments of this application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity or execution order, and words such as "first" and "second" do not necessarily mean different. At the same time, in the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.

[0232] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using a software program, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in 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. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. 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 a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0233] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art can understand and implement other changes to the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple situations. A single processor or other unit can implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0234] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.

[0235] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0236] The components in the device of the embodiment of the present application can be merged, divided, or deleted according to actual needs. Those skilled in the art can combine or combine the different embodiments and features of the different embodiments described in this specification.

[0237] The above embodiments are intended only to illustrate the technical solutions of the present application and are not intended to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they may still modify the technical solutions described in the aforementioned embodiments or replace some of the technical features therein with equivalents; and such modifications or replacements do not deviate from the essence of the corresponding technical solutions within the scope of the technical solutions of the embodiments of the present application.

[0238] In this application, under the premise of no logical contradiction, the examples can reference each other, for example, the methods and / or terms between method embodiments can reference each other, for example, the functions and / or terms between device embodiments can reference each other, for example, the functions and / or terms between device examples and method examples can reference each other.

[0239] Obviously, those skilled in the art may make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include these modifications and variations.

Claims

1. A method for managing intent capabilities, characterized in that: The method comprises: Receiving a subscription request from an intent requester or an intent producer of the network layer, wherein the subscription request is used to subscribe to intent capability description information of a target intent producer of the network layer or the network element layer related to the first service; A subscription response is sent to the intent requester or the intent producer of the network layer, wherein the subscription response includes intent capability description information of the target intent producer of the network layer or network element layer.

2. The method according to claim 1, characterized in that The method further comprises: Receiving an intent registration request from at least one intent producer of the network layer or the network element layer, the intent registration request including intent capability description information of at least one intent producer of the network layer or the network element layer; An intent registration response is sent to at least one intent producer of the network layer or the network element layer.

3. The method according to claim 1 or 2, characterized in that The method further comprises: Receiving an update request from the target intent producer of the network element layer, the update request being used to request an update of the intent capability description information of the target intent producer of the network layer or the network element layer; Send an update response to the target intended producer of the network element layer.

4. The method according to claim 3, characterized in that The method further comprises: A subscription update notification is sent to the intent requester or the intent producer of the network layer, wherein the subscription update notification includes updated intent capability description information of the target intent producer of the network layer or the network element layer.

5. The method according to any one of claims 1 to 4, characterized in that The intent capability description information includes at least one of the following: the role of the intent handler, the processing capability of the intent function, the status of the intent function module, the transmission format of the intent information model, the format of the intent information model, the intent interface type, the access address of the intent function module, the level of the intent function, the supported domains, the name of the intent function, the metadata of the intent function, the intent information model, the intent input, and the intent output.

6. A method for managing intent capabilities, characterized in that: The method comprises: receiving an intention request, the intention request including a first intention, wherein the first intention is a request for performing a first service; Sending a subscription request to the intent directory, where the subscription request is used to subscribe to the intent capability description information of the target intent producer of the network layer related to the first service; receiving a subscription response, wherein the subscription response includes the intent capability description information of the target intent producer of the network layer; A first call indication is sent to a target intent producer of the network layer, where the first call indication is used to indicate calling the target intent producer of the network layer.

7. The method according to claim 6, characterized in that The intent capability description information includes at least one of the following: the role of the intent handler, the processing capability of the intent function, the status of the intent function module, the transmission format of the intent information model, the format of the intent information model, the intent interface type, the access address of the intent function module, the level of the intent function, the supported domains, the name of the intent function, the metadata of the intent function, the intent information model, the intent input, and the intent output.

8. An intention capability management method, characterized in that: The method comprises: Receiving a first call indication from an intent requester, wherein the first call indication is used to indicate calling a target intent producer of a network layer related to a first service; Sending a subscription request to an intent directory according to the first call indication, where the subscription request is used to subscribe to intent capability description information of at least one target intent producer of a network element layer related to the first service; receiving a subscription response from the intent directory, the subscription response including intent capability description information of at least one target intent producer of the network element layer; A second call indication is sent to at least one target intended producer of the network element layer, where the second call indication is used to indicate the call of at least one target intended producer of the network element layer.

9. The method according to claim 8, characterized in that The method further comprises: Sending an intent registration request to the intent directory, the intent registration request including intent capability description information of a target intent producer of the network layer; An intent registration response is received from the intent catalog.

10. The method according to claim 8 or 9, characterized in that The method further comprises: Receive a subscription update notification from the intent directory, wherein the subscription update notification includes updated intent capability description information of the target intent producer of the network element layer.

11. The method according to any one of claims 8 to 10, characterized in that: The intent capability description information includes at least one of the following: the role of the intent handler, the processing capability of the intent function, the status of the intent function module, the transmission format of the intent information model, the format of the intent information model, the intent interface type, the access address of the intent function module, the level of the intent function, the supported domains, the name of the intent function, the metadata of the intent function, the intent information model, the intent input, and the intent output.

12. An intention capability management method, characterized in that: The method comprises: Receiving a second call indication from an intent producer of the network layer, wherein the second call indication is used to indicate calling at least one target intent producer of the network element layer; According to the second calling indication, a network element related to the first service is configured.

13. The method according to claim 12, characterized in that The method further comprises: Sending an intent registration request to the intent directory, the intent registration request including intent capability description information of the target intent producer of the network element layer; An intent registration response is received from the intent catalog.

14. The method according to claim 13, characterized in that The method further comprises: Determine that the intent capability description information of the network element is updated; Sending an update request to the intent directory, wherein the update request is used to request updating the intent capability description information of the target intent producer of the network element layer; Receive an update response from the intent catalog.

15. The method according to any one of claims 12 to 14, characterized in that The intent capability description information includes at least one of the following: the role of the intent handler, the processing capability of the intent function, the status of the intent function module, the transmission format of the intent information model, the format of the intent information model, the intent interface type, the access address of the intent function module, the level of the intent function, the supported domains, the name of the intent function, the metadata of the intent function, the intent information model, the intent input, and the intent output.

16. An intention capability management method, characterized in that: The method comprises: The intention requester receives an intention request, where the intention request includes a first intention, where the first intention is a request for performing a first service; The intent requester sends a first subscription request to the intent directory, where the first subscription request is used to subscribe to the intent capability description information of the target intent producer of the network layer related to the first service; The intent directory sends a first subscription response to the intent requester, wherein the first subscription response includes intent capability description information of a target intent producer of the network layer; The intent requester sends a first call indication to the target intent producer of the network layer, where the first call indication is used to indicate calling the target intent producer of the network layer; The target intent producer of the network layer sends a second subscription request to the intent directory according to the first call indication, where the second subscription request is used to subscribe to intent capability description information of at least one target intent producer of the network element layer related to the first service; The intent directory sends a second subscription response to the intent producer of the network layer, where the second subscription response includes intent capability description information of at least one target intent producer of the network element layer; The intention producer of the network layer sends a second call indication to at least one target intention producer of the network element layer, where the second call indication is used to indicate calling at least one target intention producer of the network element layer; At least one target intended producer of the network element layer configures the network elements related to the first service according to the second call indication.

17. An intention capability management device, characterized in that: The apparatus comprises means for performing the method as claimed in any one of claims 1-15.

18. An intention capability management system, characterized in that: It includes an intent requester, an intent directory, a target intent producer of the network layer and at least one target intent producer of the network element layer, the intent requester is used to execute the method as described in any one of claims 1-5, the intent directory is used to execute the method as described in claim 6 or 7, the target intent producer of the network layer is used to execute the method as described in any one of claims 8-11, and the at least one target intent producer of the network element layer is used to execute the method as described in any one of claims 12-15.

19. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or an instruction. When the computer program or the instruction is executed by the communication device, the method according to any one of claims 1 to 15 is implemented.

20. A computer program product, characterized in that The computer program product comprises program instructions, and when the program instructions are executed, the method according to any one of claims 1 to 15 is implemented.

Images