Intention system inter-intention knowledge association method, device and system

Abstract

A method and device for associating intent knowledge between intent systems, when the intent knowledge of a first intent of a first intent system is updated (S101), a second intent system receives an intent knowledge update notification sent by the first intent system (S102), wherein the intent knowledge update notification includes an update type and an intent keyword of the first intent; the second intent system associates the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the intent knowledge of a second intent in the second intent system according to the intent knowledge update notification (S103), wherein the first intent is a sub-intent of the second intent. Thus, when the intent knowledge of the first intent of the first intent system is updated, the association of the intent knowledge between the intent systems can be realized, and the loss or failure of the intent knowledge of the first intent in the second intent system caused by the update of the intent knowledge of the first intent can be avoided.

Description

Technical Field

[0001] The present application relates to the field of network intelligent management technology, and in particular to a method, device, and system for associating intent knowledge between intent systems. Background Art

[0002] The intent knowledge stored in the intent knowledge repository of the intent system has a one-to-one corresponding intent keyword (Intentkeyword) to identify the intent knowledge. The intent knowledge includes execution constraints (constraints) and operation sets (intentOperations): intentOperations[executionConditon, operation type (operationType), operation (operation)]. The operationType of the intent knowledge repository is an enumeration type, where one value of operationType is "subintent", indicating that the corresponding operation describes a script issued by a sub-intent, including the intent keyword of the sub-intent. The intent knowledge corresponding to the sub-intent exists in the intent knowledge repository of the lower-level intent system.

[0003] At the same time, the intent knowledge base of the high-level intent system will store the intent keywords, intent-driven objects (IntentDrivenObject, IDO) and intent-driven actions (IntentDrivenAction, IDA) of the low-level intent system's intent knowledge. This is the premise for the high-level intent system to implement the sub-intent delivery. Figure 1 As shown in the diagram of a hierarchically deployed multi-level intent system, after the high-level intent system receives the intent issuance command, since the operation objects corresponding to the intent (such as network elements) are managed by different low-level intent systems, the high-level intent system will decompose the intent and send the decomposed sub-intentions to these low-level intent systems. At the same time, the low-level intent system will feedback the intention achievement status to the high-level intent system.

[0004] External systems can update the intent knowledge in the intent knowledge base of the intent system, such as adding, modifying, and deleting. However, in a hierarchically deployed multi-level intent system, intent systems at different levels are layered and domain-specific, and the intent systems implement domain-specific autonomy. External systems cannot perform intent knowledge management operations on intent systems at different levels. Therefore, when an external system performs an intent knowledge update operation, it can only update the intent knowledge in the intent knowledge base of the current intent system, and cannot update the intent knowledge of the upper and lower intent systems related to the current intent system. This will lead to inefficient delivery of sub-intents of the intent system after the intent knowledge is updated, and even invalid or missing intent knowledge.

[0005] In view of this, how to associate intent knowledge between intent systems so that the update of intent knowledge does not affect the intent decomposition and distribution of the superior intent system is an urgent problem to be solved in this application. Summary of the Invention

[0006] The embodiments of the present application provide a method, device, and system for associating intent knowledge between intent systems, so as to achieve the association of intent knowledge between intent systems when the intent knowledge is updated.

[0007] In a first aspect, a method for associating intent knowledge between intent systems is provided, the method comprising: when the intent knowledge of a first intent of a first intent system is updated, a second intent system receives an intent knowledge update notification sent by the first intent system, wherein the intent knowledge update notification includes an update type and an intent keyword of the first intent; and the second intent system associates the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the intent knowledge of the second intent in the second intent system according to the intent knowledge update notification, wherein the first intent is a sub-intention of the second intent. In this aspect, when the intent knowledge of the first intent of the first intent system is updated, the association of intent knowledge between intent systems can be achieved, thereby avoiding the loss or invalidation of the intent knowledge of the first intent in the second intent system caused by the update of the intent knowledge of the first intent.

[0008] In one possible implementation, before the second intent system receives the intent knowledge update notification sent by the first intent system, the method further includes: the second intent system sends an intent knowledge update subscription request to the first intent system, the intent knowledge update subscription request including the identifier of the second intent system and the update type; and the second intent system receives an intent knowledge update subscription response sent by the first intent system, the intent knowledge update subscription response including at least one of the following information: a subscription identifier and a subscription status; wherein the intent knowledge update notification also includes the subscription identifier. In this implementation, the first intent system can notify the second intent system of new intent knowledge through a subscription-notification method.

[0009] In another possible implementation, the intent knowledge update notification also includes an identifier of the first intent system. After the second intent system receives the intent knowledge update notification from the first intent system, the method further includes: the second intent system sending an intent knowledge update response to the first intent system. In this implementation, the first intent system directly notifies the second intent system of the newly added intent knowledge.

[0010] In another possible implementation, the update type is to add the intention knowledge of the first intention, and the intention knowledge update notification also includes the intention-driven object and intention-driven operation of the first intention; the second intention system associates the intention knowledge of the first intention corresponding to the intention keyword of the first intention with the intention knowledge of the second intention in the second intention system according to the intention knowledge update notification, including: the second intention system queries the intention knowledge of the second intention in the second intention system according to the intention-driven object and intention-driven operation of the first intention, wherein the intention-driven object of the first intention is included in the intention-driven object of the second intention, and / or the intention-driven operation of the first intention is included in the intention-driven operation of the second intention; and the second intention system associates the intention keywords, the intention-driven object and the intention-driven operation of the first intention with the intention knowledge of the second intention.

[0011] In another possible implementation, the update type is to delete the intention knowledge of the first intention, and the second intention system associates the intention knowledge of the first intention corresponding to the intention keyword of the first intention with the intention knowledge of the second intention in the second intention system based on the intention knowledge update notification, including: the second intention system searches for the intention knowledge of the first intention corresponding to the intention keyword of the first intention in the second intention system based on the intention keyword of the first intention; and the second intention system deletes the intention knowledge of the first intention found.

[0012] In another possible implementation, the update type is to modify the intention knowledge of the first intention, and the intention knowledge update notification also includes at least one of the following information: the keyword of the first intention before modification, the intention-driven object of the first intention before modification, the intention-driven operation of the first intention before modification, the keyword of the first intention after modification, the intention-driven object of the first intention after modification, and the intention-driven operation of the first intention after modification; the second intention system associates the intention knowledge of the first intention corresponding to the intention keyword of the first intention with the intention knowledge of the second intention in the second intention system according to the intention knowledge update notification, including at least one of the following operations: after the first intention system modifies the intention keyword of the first intention, the second intention system searches for the intention keyword of the first intention before modification in the second intention system. The intention knowledge of the first intention corresponds to the intention keyword of the intention, and the second intention system replaces the intention keyword of the first intention before modification in the intention knowledge of the first intention with the modified intention keyword of the first intention; after the first intention system modifies the intention-driven object and / or intention-driven operation of the first intention, the second intention system queries the intention knowledge of the second intention in the second intention system based on the modified intention-driven object and / or intention-driven operation of the first intention, wherein the modified intention-driven object of the first intention is included in the intention-driven object of the second intention, and / or the modified intention-driven operation of the first intention is included in the intention-driven operation of the second intention; the second intention system associates the modified intention-driven object and / or intention-driven operation of the first intention with the intention knowledge of the second intention.

[0013] In another possible implementation, the method also includes: the second intention system queries the intention knowledge of the third intention in the second intention system based on the intention-driven object and / or intention-driven operation of the first intention before the modification, wherein the intention-driven object of the first intention before the modification is included in the intention-driven object of the third intention, and / or the intention-driven operation of the first intention before the modification is included in the intention-driven operation of the third intention; the second intention system de-associates the intention-driven object and / or intention-driven operation of the first intention before the modification with the intention knowledge of the third intention.

[0014] In another possible implementation, the method further includes: when the intent knowledge of the second intent is updated, the second intent system sends an intent knowledge capability query request to at least one third intent system, wherein the intent knowledge capability query request includes at least one of the following information: the identifier of the second intent system, the updated intent keyword of the second intent, the intent-driven object, and the intent-driven operation, wherein the first intent system is one of the at least one third intent systems; the second intent system receives the intent knowledge capability query response sent by the at least one third system, wherein the intent knowledge capability query response includes at least one of the following information: the identifier of the second intent system, the identifier of the at least one third intent system, the intent knowledge of the first intent associated with at least one of the updated intent keyword, the intent-driven object, and the intent-driven operation of the second intent; and the second intent system associates the intent knowledge of the first intent with at least one of the updated intent keyword, the intent-driven object, and the intent-driven operation of the second intent. In this implementation, when the intent knowledge of the second intent of the second intent system is updated, the association of intent knowledge between the intent systems is realized, which can avoid the failure of the intent knowledge update of the second intent to be associated with the intent knowledge of the first intent in the second intent system, and the failure of intent decomposition and distribution.

[0015] In another possible implementation, the update type is to modify the intention knowledge of the second intention, and the second intention system associates the intention knowledge of the first intention with at least one of the updated intention keywords, intention-driven objects, and intention-driven operations of the second intention, including at least one of the following operations: after the second intention system modifies the intention keywords of the second intention, the second intention system associates the modified intention keywords of the second intention with the intention keywords of the first intention; after the second intention system modifies the intention-driven objects and / or intention-driven operations of the second intention, the second intention system associates the modified intention-driven objects and / or intention-driven operations of the second intention with the intention-driven objects and / or intention-driven operations of the first intention.

[0016] In another possible implementation, the method also includes: the second intention system queries the intention knowledge of the fourth intention in the at least one third intention system in the second intention system based on the intention-driven object and / or intention-driven operation of the second intention before modification, wherein the intention-driven object of the second intention before modification includes the intention-driven object of the fourth intention, and / or the intention-driven operation of the second intention before modification includes the intention-driven operation of the fourth intention; and the second intention system de-associates the intention-driven object and / or intention-driven operation of the second intention before modification with the intention knowledge of the fourth intention.

[0017] In another possible implementation, before the second intention system sends an intent knowledge capability query request to at least one third intention system, the method also includes: the second intention system determines the at least one third intention system based on the updated intention-driven object of the second intention, wherein the intention-driven object of the first intention in the at least one third intention system is included in the updated intention-driven object of the second intention.

[0018] In a second aspect, a method for associating intent knowledge between intent systems is provided, the method comprising: determining that the intent knowledge of a first intent of a first intent system is updated; and the first intent system sends an intent knowledge update notification to a second intent system, so that the second intent system associates the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the intent knowledge of the second intent in the second intent system according to the intent knowledge update notification, wherein the first intent is a sub-intent of the second intent, and the intent knowledge update notification includes an update type and the intent keyword of the first intent.

[0019] In one possible implementation, before the first intent system sends an intent knowledge update notification to the second intent system, the method also includes: the first intent system receives an intent knowledge update subscription request sent by the second intent system, and the intent knowledge update subscription request includes the identifier and update type of the second intent system; and the first intent system sends an intent knowledge update subscription response to the second intent system, and the intent knowledge update subscription response includes at least one of the following information: subscription identifier, subscription status; wherein the intent knowledge update notification also includes the subscription identifier.

[0020] In another possible implementation, after the first intent system sends the intent knowledge update notification to the second intent system, the method further includes: the first intent system receiving the intent knowledge update response sent by the second intent system.

[0021] In another possible implementation, the update type includes at least one of the following: adding the intention knowledge of the first intention, deleting the intention knowledge of the first intention, and modifying the intention knowledge of the first intention; if the update type is adding the intention knowledge of the first intention, the intention knowledge update notification also includes the intention-driven object and intention-driven operation of the first intention; if the update type is modifying the intention knowledge of the first intention, the intention knowledge notification also includes at least one of the following information: the keyword of the first intention before modification, the intention-driven object of the first intention before modification, the intention-driven operation of the first intention before modification, the keyword of the first intention after modification, the intention-driven object of the first intention after modification, and the intention-driven operation of the first intention after modification.

[0022] In another possible implementation, the method also includes: the intention knowledge of the second intention is updated, the first intention system receives the intention knowledge capability query request sent by the second intention system, and the intention knowledge capability query request includes at least one of the following information: the identifier of the second intention system, the intention keywords of the updated second intention, the intention-driven object, and the intention-driven operation, wherein the first intention system is one of the intention systems of the at least one third intention system; the first intention system finds the intention knowledge of the first intention associated with at least one of the intention keywords, intention-driven objects, and intention-driven operations of the updated second intention; and the first intention system sends an intention knowledge capability query response to the second intention system, and the intention knowledge capability query response includes at least one of the following information: the identifier of the second intention system, the identifier of the at least one third intention system, and the intention knowledge of the first intention.

[0023] In a third aspect, a communication device is provided for executing the method in the first aspect or any possible implementation of the first aspect. The communication device can be the second intention system in the first aspect or any possible implementation of the first aspect, or a module applied to the second intention system, such as a chip or a chip system. The communication device includes a module, unit, or means corresponding to the above method, and the module, unit, or means can be implemented by hardware, software, or by executing the corresponding software implementation by hardware. The hardware or software includes one or more modules or units corresponding to the above functions.

[0024] In conjunction with the third aspect above, in one possible implementation, a communication device includes: a transceiver unit and a processing unit; wherein:

[0025] A transceiver unit is used to receive an intent knowledge update notification sent by a first intent system when the intent knowledge of the first intent of the first intent system is updated, wherein the intent knowledge update notification includes an update type and an intent keyword of the first intent; and a processing unit is used to associate the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the intent knowledge of the second intent in a second intention system according to the intent knowledge update notification, wherein the first intent is a sub-intention of the second intent.

[0026] In one possible implementation, the transceiver unit is also used to send an intent knowledge update subscription request to the first intent system, and the intent knowledge update subscription request includes the identifier and update type of the second intent system; and the transceiver unit is also used to receive an intent knowledge update subscription response sent by the first intent system, and the intent knowledge update subscription response includes at least one of the following information: subscription identifier, subscription status; wherein the intent knowledge update notification also includes the subscription identifier.

[0027] In another possible implementation, the intent knowledge update notification further includes an identifier of the first intent system, and the transceiver unit is further configured to send an intent knowledge update response to the first intent system.

[0028] In another possible implementation, the update type is to add the intention knowledge of the first intention, and the intention knowledge update notification also includes the intention-driven object and intention-driven operation of the first intention; the processing unit is used to query the intention knowledge of the second intention in the second intention system based on the intention-driven object and intention-driven operation of the first intention, wherein the intention-driven object of the first intention is included in the intention-driven object of the second intention, and / or the intention-driven operation of the first intention is included in the intention-driven operation of the second intention; and the processing unit is also used to associate the intention keywords of the first intention, the intention-driven object and the intention-driven operation with the intention knowledge of the second intention.

[0029] In another possible implementation, the update type is to delete the intention knowledge of the first intention, and the processing unit is used to search for the intention knowledge of the first intention corresponding to the intention keyword of the first intention in the second intention system based on the intention keyword of the first intention; and the processing unit is also used to delete the intention knowledge of the first intention found.

[0030] In another possible implementation, the update type is to modify the intention knowledge of the first intention, and the intention knowledge update notification also includes at least one of the following information: the keyword of the first intention before modification, the intention-driven object of the first intention before modification, the intention-driven operation of the first intention before modification, the keyword of the first intention after modification, the intention-driven object of the first intention after modification, and the intention-driven operation of the first intention after modification; a processing unit is used to perform at least one of the following operations: after the first intention system modifies the intention keyword of the first intention, according to the intention keyword of the first intention before modification, the intention knowledge of the first intention corresponding to the intention keyword of the first intention before modification is searched in the second intention system, and the The modified intention keywords of the first intention replace the intention keywords of the first intention before modification in the intention knowledge of the first intention; after the first intention system modifies the intention-driven object and / or intention-driven operation of the first intention, the intention knowledge of the second intention is queried in the second intention system based on the modified intention-driven object and / or intention-driven operation of the first intention, wherein the modified intention-driven object of the first intention is included in the intention-driven object of the second intention, and / or the modified intention-driven operation of the first intention is included in the intention-driven operation of the second intention; the modified intention-driven object and / or intention-driven operation of the first intention is associated with the intention knowledge of the second intention.

[0031] In another possible implementation, the processing unit is further used to query the intention knowledge of the third intention in the second intention system based on the intention-driven object and / or intention-driven operation of the first intention before the modification, wherein the intention-driven object of the first intention before the modification is included in the intention-driven object of the third intention, and / or the intention-driven operation of the first intention before the modification is included in the intention-driven operation of the third intention; the processing unit is further used to de-associate the intention-driven object and / or intention-driven operation of the first intention before the modification with the intention knowledge of the third intention.

[0032] In another possible implementation, the transceiver unit is also used to update the intention knowledge of the second intention and send an intention knowledge capability query request to at least one third intention system, wherein the intention knowledge capability query request includes at least one of the following information: the identifier of the second intention system, the updated intention keyword of the second intention, the intention-driven object, and the intention-driven operation, wherein the first intention system is one of the at least one third intention systems; the transceiver unit is also used to receive the intention knowledge capability query response sent by the at least one third system, and the intention knowledge capability query response includes at least one of the following information: the identifier of the second intention system, the identifier of the at least one third intention system, and the intention knowledge of the first intention associated with at least one of the updated intention keywords, intention-driven objects, and intention-driven operations of the second intention; and the processing unit is also used to associate the intention knowledge of the first intention with at least one of the updated intention keywords, intention-driven objects, and intention-driven operations of the second intention.

[0033] In another possible implementation, the update type is to modify the intention knowledge of the second intention, and the processing unit is further used to perform at least one of the following operations: after the second intention system modifies the intention keywords of the second intention, the modified intention keywords of the second intention are associated with the intention keywords of the first intention; or after the second intention system modifies the intention-driven object and / or intention-driven operation of the second intention, the modified intention-driven object and / or intention-driven operation of the second intention is associated with the intention-driven object and / or intention-driven operation of the first intention.

[0034] In another possible implementation, the processing unit is further used to query the intention knowledge of the fourth intention in the at least one third intention system in the second intention system based on the intention-driven object and / or intention-driven operation of the second intention before modification, wherein the intention-driven object of the second intention before modification includes the intention-driven object of the fourth intention, and / or the intention-driven operation of the second intention before modification includes the intention-driven operation of the fourth intention; and the processing unit is further used to de-associate the intention-driven object and / or intention-driven operation of the second intention before modification with the intention knowledge of the fourth intention.

[0035] In another possible implementation, the processing unit is further used to determine the at least one third intention system based on the updated intention-driven object of the second intention, wherein the intention-driven object of the first intention in the at least one third intention system is included in the updated intention-driven object of the second intention.

[0036] In combination with the third aspect above, in another possible implementation, a communication device includes: an input interface, an output interface, and a processing circuit; wherein:

[0037] An input interface for receiving an intent knowledge update notification sent by a first intent system when the intent knowledge of the first intent is updated, wherein the intent knowledge update notification includes an update type and an intent keyword of the first intent; and a processing circuit for associating the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the intent knowledge of the second intent in a second intention system according to the intent knowledge update notification, wherein the first intent is a sub-intention of the second intent.

[0038] In one possible implementation, the output interface is also used to send an intent knowledge update subscription request to the first intent system, and the intent knowledge update subscription request includes the identifier and update type of the second intent system; and the input interface is also used to receive an intent knowledge update subscription response sent by the first intent system, and the intent knowledge update subscription response includes at least one of the following information: subscription identifier, subscription status; wherein the intent knowledge update notification also includes the subscription identifier.

[0039] In another possible implementation, the intent knowledge update notification also includes an identifier of the first intent system, an output interface, and is further used to send an intent knowledge update response to the first intent system.

[0040] In another possible implementation, the update type is to add the intention knowledge of the first intention, and the intention knowledge update notification also includes the intention-driven object and intention-driven operation of the first intention; the processing circuit is used to query the intention knowledge of the second intention in the second intention system based on the intention-driven object and intention-driven operation of the first intention, wherein the intention-driven object of the first intention is included in the intention-driven object of the second intention, and / or the intention-driven operation of the first intention is included in the intention-driven operation of the second intention; and the processing circuit is also used to associate the intention keywords of the first intention, the intention-driven object and the intention-driven operation with the intention knowledge of the second intention.

[0041] In another possible implementation, the update type is to delete the intention knowledge of the first intention, and the processing circuit is used to search for the intention knowledge of the first intention corresponding to the intention keyword of the first intention in the second intention system based on the intention keyword of the first intention; and the processing circuit is also used to delete the intention knowledge of the first intention found.

[0042] In another possible implementation, the update type is to modify the intention knowledge of the first intention, and the intention knowledge update notification also includes at least one of the following information: the keyword of the first intention before modification, the intention-driven object of the first intention before modification, the intention-driven operation of the first intention before modification, the keyword of the first intention after modification, the intention-driven object of the first intention after modification, and the intention-driven operation of the first intention after modification; a processing circuit is used to perform at least one of the following operations: after the first intention system modifies the intention keyword of the first intention, according to the intention keyword of the first intention before modification, the intention knowledge of the first intention corresponding to the intention keyword of the first intention before modification is searched in the second intention system, and the intention knowledge of the first intention corresponding to the intention keyword of the first intention before modification is searched. The modified intention keywords of the first intention replace the intention keywords of the first intention before modification in the intention knowledge of the first intention; after the first intention system modifies the intention-driven object and / or intention-driven operation of the first intention, the intention knowledge of the second intention is queried in the second intention system based on the modified intention-driven object and / or intention-driven operation of the first intention, wherein the modified intention-driven object of the first intention is included in the intention-driven object of the second intention, and / or the modified intention-driven operation of the first intention is included in the intention-driven operation of the second intention; the modified intention-driven object and / or intention-driven operation of the first intention is associated with the intention knowledge of the second intention.

[0043] In another possible implementation, the processing circuit is further used to query the intention knowledge of the third intention in the second intention system based on the intention-driven object and / or intention-driven operation of the first intention before the modification, wherein the intention-driven object of the first intention before the modification is included in the intention-driven object of the third intention, and / or the intention-driven operation of the first intention before the modification is included in the intention-driven operation of the third intention; the processing circuit is further used to de-associate the intention-driven object and / or intention-driven operation of the first intention before the modification with the intention knowledge of the third intention.

[0044] In another possible implementation, the output interface is also used to update the intention knowledge of the second intention and send an intention knowledge capability query request to at least one third intention system, wherein the intention knowledge capability query request includes at least one of the following information: the identifier of the second intention system, the updated intention keyword of the second intention, the intention-driven object, and the intention-driven operation, wherein the first intention system is one of the at least one third intention systems; the input interface is also used to receive the intention knowledge capability query response sent by the at least one third system, and the intention knowledge capability query response includes at least one of the following information: the identifier of the second intention system, the identifier of the at least one third intention system, and the intention knowledge of the first intention associated with at least one of the updated intention keywords, intention-driven objects, and intention-driven operations of the second intention; and the processing circuit is also used to associate the intention knowledge of the first intention with at least one of the updated intention keywords, intention-driven objects, and intention-driven operations of the second intention.

[0045] In another possible implementation, the update type is to modify the intention knowledge of the second intention, and the processing circuit is also used to perform at least one of the following operations: after the second intention system modifies the intention keywords of the second intention, the modified intention keywords of the second intention are associated with the intention keywords of the first intention; or after the second intention system modifies the intention-driven object and / or intention-driven operation of the second intention, the modified intention-driven object and / or intention-driven operation of the second intention is associated with the intention-driven object and / or intention-driven operation of the first intention.

[0046] In another possible implementation, the processing circuit is further used to query the intention knowledge of the fourth intention in the at least one third intention system in the second intention system based on the intention-driven object and / or intention-driven operation of the second intention before modification, wherein the intention-driven object of the second intention before modification includes the intention-driven object of the fourth intention, and / or the intention-driven operation of the second intention before modification includes the intention-driven operation of the fourth intention; and the processing circuit is further used to de-associate the intention-driven object and / or intention-driven operation of the second intention before modification with the intention knowledge of the fourth intention.

[0047] In another possible implementation, the processing circuit is further used to determine the at least one third intention system based on the updated intention-driven object of the second intention, wherein the intention-driven object of the first intention in the at least one third intention system is included in the updated intention-driven object of the second intention.

[0048] Exemplarily, the communication device also includes a memory, which is coupled to the at least one processor, and the at least one processor is used to run program instructions stored in the memory so that the communication device executes the method in the above-mentioned first aspect or any possible implementation of the first aspect.

[0049] In one possible implementation, the memory is used to store program instructions and data. The memory is coupled to the at least one processor, and the at least one processor can call and execute the program instructions stored in the memory to cause the communication device to perform the method of the first aspect or any possible implementation of the first aspect.

[0050] Exemplarily, the communication device further includes a communication interface, which is used for the communication device to communicate with other devices. When the communication device is a second intention system, the communication interface is a transceiver, an input / output interface, or a circuit.

[0051] In one possible design, the communication device includes: at least one processor and a communication interface, configured to execute the method of the first aspect or any possible implementation of the first aspect, specifically including: the at least one processor communicating with an external device using the communication interface; and the at least one processor being configured to execute a computer program so that the communication device executes the method of the first aspect or any possible implementation of the first aspect. It will be understood that the external device may be an object other than the processor or an object other than the communication device.

[0052] In another possible design, the communication device is a chip or a chip system. The communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip or chip system. The processor can also be embodied as a processing circuit or a logic circuit.

[0053] Among them, the technical effects brought about by any design method in the third aspect can refer to the technical effects brought about by different design methods in the above-mentioned first aspect, and will not be repeated here.

[0054] In a fourth aspect, a communication device is provided for executing the method in the second aspect or any possible implementation of the second aspect. The communication device can be the first intention system in the second aspect or any possible implementation of the second aspect, or a module applied to the first intention system, such as a chip or a chip system. The communication device includes a module, unit, or means corresponding to the above method, and the module, unit, or means can be implemented by hardware, software, or by executing the corresponding software implementation through hardware. The hardware or software includes one or more modules or units corresponding to the above functions.

[0055] In conjunction with the fourth aspect above, in one possible implementation, a communication device includes: a processing unit and a transceiver unit; wherein:

[0056] A processing unit for determining that the intent knowledge of the first intent of the first intent system is updated; and a transceiver unit for sending an intent knowledge update notification to the second intent system, so that the second intent system associates the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the intent knowledge of the second intent in the second intention system according to the intent knowledge update notification, wherein the first intent is a sub-intention of the second intent, and the intent knowledge update notification includes the update type and the intent keyword of the first intent.

[0057] In one possible implementation, the transceiver unit is also used to receive an intent knowledge update subscription request sent by the second intent system, and the intent knowledge update subscription request includes the identifier and update type of the second intent system; and the transceiver unit is also used to send an intent knowledge update subscription response to the second intent system, and the intent knowledge update subscription response includes at least one of the following information: subscription identifier, subscription status; wherein the intent knowledge update notification also includes the subscription identifier.

[0058] In another possible implementation, the transceiver unit is further configured to receive an intent knowledge update response sent by the second intent system.

[0059] In another possible implementation, the update type includes at least one of the following: adding the intention knowledge of the first intention, deleting the intention knowledge of the first intention, and modifying the intention knowledge of the first intention; if the update type is adding the intention knowledge of the first intention, the intention knowledge update notification also includes the intention-driven object and intention-driven operation of the first intention; if the update type is modifying the intention knowledge of the first intention, the intention knowledge notification also includes at least one of the following information: the keyword of the first intention before modification, the intention-driven object of the first intention before modification, the intention-driven operation of the first intention before modification, the keyword of the first intention after modification, the intention-driven object of the first intention after modification, and the intention-driven operation of the first intention after modification.

[0060] In another possible implementation, the transceiver unit is also used to update the intention knowledge of the second intention, receive the intention knowledge capability query request sent by the second intention system, and the intention knowledge capability query request includes at least one of the following information: the identifier of the second intention system, the intention keywords of the updated second intention, the intention-driven object, and the intention-driven operation, wherein the first intention system is one of the at least one third intention systems; the processing unit is used to find the intention knowledge of the first intention associated with at least one of the intention keywords, intention-driven objects, and intention-driven operations of the updated second intention; and the transceiver unit is also used to send an intention knowledge capability query response to the second intention system, and the intention knowledge capability query response includes at least one of the following information: the identifier of the second intention system, the identifier of the at least one third intention system, and the intention knowledge of the first intention.

[0061] In combination with the fourth aspect above, in another possible implementation, a communication device includes: an input interface, an output interface, and a processing circuit; wherein:

[0062] A processing circuit for determining that the intent knowledge of the first intent of the first intention system is updated; and an output interface for sending an intent knowledge update notification to the second intention system, so that the second intention system associates the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the intent knowledge of the second intention in the second intention system according to the intent knowledge update notification, wherein the first intent is a sub-intention of the second intention, and the intent knowledge update notification includes the update type and the intent keyword of the first intention.

[0063] In one possible implementation, the input interface is also used to receive an intent knowledge update subscription request sent by the second intent system, wherein the intent knowledge update subscription request includes the identifier and update type of the second intent system; and the output interface is also used to send an intent knowledge update subscription response to the second intent system, wherein the intent knowledge update subscription response includes at least one of the following information: subscription identifier, subscription status; wherein the intent knowledge update notification also includes the subscription identifier.

[0064] In yet another possible implementation, the input interface is further configured to receive an intent knowledge update response sent by the second intent system.

[0065] In another possible implementation, the update type includes at least one of the following: adding the intention knowledge of the first intention, deleting the intention knowledge of the first intention, and modifying the intention knowledge of the first intention; if the update type is adding the intention knowledge of the first intention, the intention knowledge update notification also includes the intention-driven object and intention-driven operation of the first intention; if the update type is modifying the intention knowledge of the first intention, the intention knowledge notification also includes at least one of the following information: the keyword of the first intention before modification, the intention-driven object of the first intention before modification, the intention-driven operation of the first intention before modification, the keyword of the first intention after modification, the intention-driven object of the first intention after modification, and the intention-driven operation of the first intention after modification.

[0066] In another possible implementation, the input interface is also used to update the intention knowledge of the second intention, receive the intention knowledge capability query request sent by the second intention system, and the intention knowledge capability query request includes at least one of the following information: the identification of the second intention system, the intention keywords of the updated second intention, the intention-driven object, and the intention-driven operation, wherein the first intention system is one of the at least one third intention systems; the processing circuit is used to find the intention knowledge of the first intention associated with at least one of the intention keywords, intention-driven objects, and intention-driven operations of the updated second intention; and the input interface is also used to send an intention knowledge capability query response to the second intention system, and the intention knowledge capability query response includes at least one of the following information: the identification of the second intention system, the identification of the at least one third intention system, and the intention knowledge of the first intention.

[0067] Exemplarily, the communication device also includes a memory, which is coupled to the at least one processor, and the at least one processor is used to run program instructions stored in the memory so that the communication device executes the method in the above-mentioned second aspect or any possible implementation of the second aspect.

[0068] In one possible implementation, the memory is used to store program instructions and data. The memory is coupled to the at least one processor, and the at least one processor can call and execute the program instructions stored in the memory to cause the communication device to perform the method of the second aspect or any possible implementation of the second aspect.

[0069] Exemplarily, the communication device further includes a communication interface, which is used for the communication device to communicate with other devices. When the communication device is a first intention system, the communication interface is a transceiver, an input / output interface, or a circuit.

[0070] In one possible design, the communication device includes: at least one processor and a communication interface, configured to execute the method of the second aspect or any possible implementation of the second aspect, specifically including: the at least one processor communicating with an external device using the communication interface; and the at least one processor being configured to execute a computer program so that the communication device executes the method of the second aspect or any possible implementation of the second aspect. It will be understood that the external device may be an object other than the processor or an object other than the communication device.

[0071] In another possible design, the communication device is a chip or a chip system. The communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip or chip system. The processor can also be embodied as a processing circuit or a logic circuit.

[0072] Among them, the technical effects brought about by any design method in the fourth aspect can refer to the technical effects brought about by different design methods in the above-mentioned second aspect, and will not be repeated here.

[0073] In a fifth aspect, a communication system is provided, comprising the communication device as described in the third aspect or any one implementation of the third aspect, and the communication device as described in the fourth aspect.

[0074] In a sixth aspect, a computer-readable storage medium is provided, wherein instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is run on a computer, the computer executes the methods described in the above aspects.

[0075] In a seventh aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the methods described in the above aspects.

[0076] In an eighth aspect, a chip is provided, which is coupled to a memory and executes the communication method described in the first aspect of the embodiment of the present application or any implementation of the first aspect.

[0077] In a ninth aspect, a chip is provided, which is coupled to a memory and executes the communication method described in the second aspect of the embodiment of the present application or any implementation of the second aspect.

[0078] It should be noted that, in the embodiments of the present application, “coupling” refers to two components being directly or indirectly coupled to each other. BRIEF DESCRIPTION OF THE DRAWINGS

[0079] Figure 1 Schematic diagram of a multi-level intent system with hierarchical deployment;

[0080] Figure 2 This is a schematic diagram of IDM;

[0081] Figure 3 Schematic diagram of the intent hierarchy defined for IDMS;

[0082] Figure 4 This is a schematic diagram of the knowledge management function module;

[0083] Figure 5 This is a schematic diagram of the ENI architecture based on intent strategy;

[0084] Figure 6 Schematic diagram of the intent knowledge management architecture in the ENI fusion system based on intent strategy;

[0085] Figure 7 Schematic diagram of the intent knowledge management architecture in the ENI fusion system based on intent strategy provided in the embodiment of this application:

[0086] Figure 8 A flowchart of a method for associating intent knowledge between intent systems provided in an embodiment of the present application;

[0087] Figure 9 A flowchart of another method for associating intent knowledge between intent systems provided in an embodiment of the present application;

[0088] Figure 10 A flowchart of another method for associating intent knowledge between intent systems provided in an embodiment of the present application;

[0089] Figure 11 A flowchart of another method for associating intent knowledge between intent systems provided in an embodiment of the present application;

[0090] Figure 12 A flowchart of another method for associating intent knowledge between intent systems provided in an embodiment of the present application;

[0091] Figure 13 A flowchart of another method for associating intent knowledge between intent systems provided in an embodiment of the present application;

[0092] Figure 14 A flowchart of another method for associating intent knowledge between intent systems provided in an embodiment of the present application;

[0093] Figure 15 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0094] Figure 16 A schematic structural diagram of another communication device provided in an embodiment of the present application;

[0095] Figure 17 A structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0096] In order to reduce the management complexity of network infrastructure, 3GPP SA5 initiated the research of intent-driven management (IDM). IDM uses service-oriented interfaces to implement the delivery of intent. Figure 2 As shown in the IDM diagram, the intent-driven management service consumer (IDM service consumer) sends the intent to the intent-driven management service provider (IDM service producer) by calling the intent-driven management service (IDMS) interface. The IDM service provider translates the intent into a specific execution strategy and sends it to the network infrastructure. The network infrastructure can be physical and / or virtual. The intent model is used to model the information that should be contained in the intent expression (intentExpression), and should at least include "intent-driven action (IntentDrivenAction, IDA)" and "intent-driven object (IntentDrivenObject, IDO)". IDA consists of an action name (IntentDrivenActionName) and a series of properties (IntentDrivenActionProperties) required to complete the action; IDO consists of an object name (IntentDrivenObjectName) and a series of properties (IntentDrivenObjectProperties) used to identify specific object instances. Therefore, the formal expression of the intent model is as follows:

[0097] <intentexpression> ：＝ <intentdrivenaction> <intentdrivenobject>

[0098] <intentdrivenaction> ：＝ <intentdrivenactionname> <intentdrivenactionproperties>

[0099] <intentdrivenobject> ：＝ <intentdrivenobjectname> <intentdrivenobjectproperties>

[0100] like Figure 3 The following is a diagram of the intent hierarchy defined by IDMS. IDMS provides three levels of end-to-end intent expression: communication service customer (CSC), communication service provider (CSP), and network operator (NOP). CSC includes end users, small and medium-sized enterprises, large enterprises, vertical industries, and other CSPs.

[0101] Communication service consumer intent (intent-CSC): only expresses service-level management requirements and does not involve service and network implementation details.

[0102] Communication service provider intent (intent-CSP): only expresses network-level management requirements and does not involve professional knowledge of network operations.

[0103] Network operator intent (intent-NOP): This only expresses management requirements at the network resource level and does not involve the operational details of physical network devices and virtualized infrastructure. This is the intent conveyed on the EMS northbound interface.

[0104] Experiential networked intelligence (ENI) is a perception network management system architecture defined by the industry specification working group, which uses artificial intelligence and context awareness and other technical means to optimize and adjust network operations. It includes eight functional modules: input processing and normalization functional module (data ingestion & normalization FB), output generation and denormalization functional module (output generation & denormalization FB), knowledge management functional module (knowledge management FB), context awareness functional module (context awareness FB), cognition management functional module (cognition management FB), situational awareness functional module (situational awareness FB), policy management functional module (policy management FB) and model driven engineering functional module (model driven engineering FB). This application focuses on describing the knowledge management FB. Figure 4 The schematic diagram of the knowledge management functional module shows that the knowledge management FB is used to manage at least four types of data and knowledge repositories: the data repository, the knowledge repository, the model repository, and the blackboard repository. The knowledge repository is used to store, manipulate, edit, and retrieve knowledge and wisdom. The knowledge repository interacts with the context awareness FB, the cognition management FB, the situation awareness FB, the model-driven engineering FB, and the policy management FB.

[0105] like Figure 5 The following figure shows an ENI architecture diagram based on intent policy. It proposes an ENI architecture based on intent policy, promotes the standardization of intent-driven network architecture, and enhances the original ENI architecture:

[0106] Added a new intent translation function module (intent translation FB): used to process intent policy, including intent policy intent translation, intent protection and lifecycle management.

[0107] Enhance knowledge management FB: Store the intent knowledge model and intent knowledge data in the model repository and knowledge repository respectively.

[0108] like Figure 6 The following is a schematic diagram of the intent knowledge management architecture in the ENI fusion system based on intent strategy. The current intent system or low-level intent system has intent knowledge management functions and interfaces, supporting external systems such as users / applications (APPs) / operation support systems (OSSs) / business support system-like (BSS-like) functional entities through the following interfaces: user-eni-kno 、E app-eni-kno and E oss-eni-kno Perform intent knowledge update operations. External systems can add, modify, and delete intent knowledge in the knowledge repository of the intent system.

[0109] Each intent knowledge stored in the intent system's knowledge repository has a one-to-one correspondence with an intent keyword, which is used to identify the intent knowledge. This intent knowledge includes execution constraints and intentOperations[executionConditon, operationType, operation]. The operationType in the intent knowledge repository is an enumeration type, where a value of "subintent" indicates that the corresponding operation describes a script issued by a subintent, including the subintent's intent keyword. The intent knowledge corresponding to this subintent exists in the low-level intent system's intent knowledge repository.

[0110] At the same time, the high-level intent system's intent knowledge base will store the intent keywords, IDO, and IDA of the low-level intent system's intent knowledge. This is the prerequisite for the high-level intent system to implement the sub-intent delivery. Figure 1 As shown in the diagram of a hierarchically deployed multi-level intent system, after the high-level intent system receives the intent issuance command, since the operation objects corresponding to the intent (such as network elements) are managed by different low-level intent systems, the high-level intent system will decompose the intent and send the decomposed sub-intentions to these low-level intent systems. At the same time, the low-level intent system will feedback the intention achievement status to the high-level intent system.

[0111] However, in a multi-level intent system with hierarchical deployment, intent systems at different levels are layered and domain-based, and the intent systems implement domain-based autonomy. External systems cannot perform intent knowledge management operations on intent systems at different levels. Therefore, when an external system performs intent knowledge update operations, it can only update the intent knowledge in the knowledge repository of the current intent system, and cannot update the intent knowledge of the upper and lower intent systems related to the current intent system. This will cause the updated intent knowledge to affect the delivery of sub-intentions, because after the intent knowledge is updated, the intent knowledge in the knowledge repository of the upper and lower intent systems is not associated and updated, so after the intent knowledge is updated, the efficiency of the intent system's sub-intent delivery is low, and even the intent knowledge is invalid or missing. Specifically,

[0112] The impact of the low-level intent system updating intent knowledge on the high-level intent system:

[0113] 1) The low-level intent system adds new intent knowledge, but this intent does not exist in the high-level intent system. The high-level intent system cannot decompose and distribute this intent as a sub-intent in the high-level intent system.

[0114] New intent knowledge added to the low-level intent system refers to intents that don't exist in the low-level intent system's knowledge base. Specifically, these intents lack the IntentKeyword, IDA, IDO, constraint, and IntentOperations. New intent knowledge includes newly added IntentKeywords, IDAs, and IDOs, along with their corresponding constraints and IntentOperations. If the knowledge base already contains an IntentKeyword but only adds constraints and IntentOperations, these new intent knowledge is not considered new in the low-level intent system.

[0115] 2) The low-level intent system modifies the intent knowledge, and the intent can also be used as a sub-intention in the high-level, but it will lead to deviations in the intent decomposition in the high-level.

[0116] Among them, the low-level intent system modifies the intent knowledge means that the low-level intent system knowledge base already has the intent, including Intentkeyword, IDA, IDO, constraint and intentOperations, but the Intentkeyword / IDA / IDO are modified.

[0117] For example, the knowledge of IntentDrivenObjectProperties in IDO is modified. The original IntentDrivenObjectProperties is JinQiao, and the modified IntentDrivenObjectProperties is MinHang.

[0118] 3) The low-level intent system deletes the intent knowledge, but the intent still exists as a sub-intent in the high-level system, causing the sub-intent in the high-level system to fail to be sent.

[0119] Among them, deleting intent knowledge in the low-level intent system means that the intent exists in the low-level intent system knowledge base, that is, it has Intentkeyword, IDA, IDO, constraint and intentOperations. Deleting intent knowledge means deleting all knowledge of Intentkeyword, IDA, IDO, constraint and intentOperations.

[0120] The impact of updating intent knowledge in the high-level intent system:

[0121] After the high-level intent system adds or modifies intent knowledge, it can only exist as intent knowledge in the high-level knowledge repository and cannot be associated with the intent knowledge of the low-level intent system, resulting in the inability to decompose and distribute intent.

[0122] The present application provides a method, device, and system for associating intent knowledge between intent systems. When the intent knowledge of a first intent in a first intent system is updated, a second intent system receives an intent knowledge update notification sent by the first intent system, wherein the intent knowledge update notification includes an update type and an intent keyword of the first intent; based on the intent knowledge update notification, the second intent system associates the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the intent knowledge of the second intent in the second intent system, wherein the first intent is a sub-intent of the second intent. Thus, when the intent knowledge of the first intent in the first intent system is updated, the intent knowledge between the intent systems can be associated, thereby preventing the intent knowledge update of the first intent from causing the loss or invalidation of the intent knowledge of the first intent in the second intent system.

[0123] The functional modules involved in this application are described as follows:

[0124] Knowledge management FB: manages all knowledge within the ENI scope. In this application, it completes the query, update, and storage of intent knowledge in the intent knowledge repository FB. In this application, the association function of intent knowledge is enhanced.

[0125] ●Data ingestion and normalization FB: Operations such as acquisition and standardization of input data from external systems. In this application, intent knowledge update notifications and intent knowledge query operations between intent systems are enhanced.

[0126] ●Output generation and demoralization FB: Responsible for converting internal system commands into a format that can be processed by the external system and sending it to the external system. In this application, the command conversion of intent knowledge update results and intent knowledge query results is enhanced.

[0127] For this reason, Figure 7 The schematic diagram of the intent knowledge management architecture in the ENI fusion system based on intent policy provided by the embodiment of the present application is shown. The ENI system interface of intent policyv has been newly added with an external interface E to support knowledge management between multi-level intent systems. eni-eni-kno .

[0128] The ENI fusion system based on intent policy in this application can be deployed on the operation and maintenance support system BSS, or on the operator's network management system NMS, or on the network equipment vendor's network element management system EMS, and can also be deployed on the network element NE.

[0129] The network elements that deploy the intent-based ENI fusion system support the query, update and storage functions of intent knowledge, and the notification and query functions of updated intent knowledge are supported between multi-level network elements.

[0130] The following describes in detail the method for associating intent knowledge between intent systems provided in the embodiment of the present application:

[0131] like Figure 8 FIG. 1 is a flow chart of a method for associating intent knowledge between intent systems provided in an embodiment of the present application. The method may include the following steps:

[0132] S101. The first intention system determines that the intention knowledge of its first intention is updated.

[0133] In this embodiment, the first intention system may be a low-level intention system, and the second intention system may be a high-level intention system. Specifically, for example Figure 3 In the embodiment, the first intention system may be CSP and the second intention system may be CSC; or the first intention system may be CSC and the second intention system may be NOP.

[0134] An external system (user / APP / OSS- / BSS-like) can update the intent knowledge of the first intent of the first intent system. Specifically, the intent knowledge of the first intent of the first intent system is updated by adding, modifying, or deleting the intent knowledge of the first intent in the first intent system. The intent knowledge of the first intent is the intent knowledge of any intent that already exists in or will be stored in the first intent system.

[0135] S102: The first intent system sends an intent knowledge update notification to the second intent system, wherein the intent knowledge update notification includes an update type and an intent keyword of the first intent. Correspondingly, the second intent system receives the intent knowledge update notification sent by the first intent system.

[0136] Updating the intent knowledge of the first intent system may cause the sub-intent knowledge of the second intent system to be missing or invalid. If the intent knowledge of the first intent system is added, the second intent system cannot decompose and distribute the sub-intents, resulting in insufficient utilization of the intent knowledge. If the intent knowledge of the first intent system is modified, the second intent system can decompose and distribute the sub-intents, but there may be decomposition deviations, requiring multiple intent negotiations, resulting in low efficiency. If the intent knowledge of the first intent system is deleted, the second intent system can decompose and distribute the sub-intents, but the first intent system cannot implement the sub-intent.

[0137] In this embodiment, when the first intent system determines that the intent knowledge of its first intent has been updated, it sends an intent knowledge update notification to the second intent system to notify the second intent system that the intent knowledge of the first intent of the first intent system has been updated. The intent knowledge update notification includes the update type and the intent keyword of the first intent. In addition, if the intent knowledge of the first intent is newly added, the intent knowledge update notification may also include the IDO and IDA of the first intent; if at least one of the intent keywords / IDO / IDA of the first intent is modified, the intent knowledge update notification may also include the intent keyword of the first intent before the modification and at least one of the intent keywords / IDO / IDA of the first intent after the modification.

[0138] S103. The second intention system associates the intention knowledge of the first intention corresponding to the intention keyword of the first intention with the intention knowledge of the second intention in the second intention system according to the intention knowledge update notification, wherein the first intention is a sub-intention of the second intention.

[0139] As mentioned above, if the first intent system adds intent knowledge for the first intent, but this first intent does not exist in the second intent system, the second intent system cannot decompose and distribute the first intent as a sub-intent in the second intent system. Therefore, when the first intent system adds intent knowledge for the first intent, it needs to associate this newly added first intent knowledge with the intent knowledge for the second intent in the second intent system.

[0140] If the first intent system modifies the intent knowledge of the first intent, the first intent can still be used as a sub-intent in the second intent system, but this will cause deviations in the intent decomposition in the second intent system. Therefore, when the first intent system modifies the intent knowledge of the first intent, it needs to re-associate the modified first intent with the intent knowledge of the second intent in the second intent system.

[0141] If the first intent system deletes the intent knowledge of the first intent, the first intent will still be included as a sub-intent in the second intent system, causing the sub-intent in the second intent system to fail to be delivered. Therefore, when the first intent system deletes the intent knowledge of the first intent, it is necessary to disassociate the intent knowledge of the first intent from the intent knowledge of the second intent in the second intent system.

[0142] The second intention system can avoid the loss or invalidation of the intention knowledge of the first intention in the second intention system due to the update of the intention knowledge of the first intention by associating the intention knowledge of the first intention corresponding to the intention keyword of the first intention with the intention knowledge of the second intention in the second intention system.

[0143] Optionally, the following steps may also be included:

[0144] S104: The intent knowledge of the second intent in the second intent system is updated, and the second intent system sends an intent knowledge and capability query request to at least one third intent system. The intent knowledge and capability query request includes at least one of the following information: an identifier of the second intent system, an intent keyword of the updated second intent, an intent-driven object, and an intent-driven operation. The first intent system is one of the at least one third intent system. Accordingly, the first intent system receives the intent knowledge and capability query request sent by the second intent system.

[0145] An external system (user / APP / OSS- / BSS-like) can also update the intent knowledge of the second intent in the second intent system. The external system updating the intent knowledge of the intent in the second intent system is independent of updating the intent knowledge of the intent in the first intent system. Specifically, the intent knowledge of the second intent of the second intent system is updated, and the second intent system may add or modify the intent knowledge of the second intent. The intent knowledge of the second intent is the intent knowledge of any intent that already exists in or is about to be stored in the second intent system.

[0146] As mentioned above, after the second intent system adds or modifies the intent knowledge of the second intent, it can only exist as intent knowledge in the knowledge repository of the second intent system and cannot be associated with the intent knowledge of the first intent system, resulting in the inability to realize intent decomposition and distribution.

[0147] In this embodiment, when the second intention system updates the intention knowledge of the second intention, the second intention system sends an intention knowledge capability query request to at least one third intention system to request to query the intention knowledge of the first intention associated with the updated intention knowledge of the second intention in at least one third intention system.

[0148] S105. The first intention system finds the intention knowledge of the first intention associated with at least one of the intention keywords, intention-driven objects, and intention-driven operations of the updated second intention.

[0149] The first intention system searches for the intention knowledge of the first intention associated with at least one of the intention keywords, intention-driven objects, and intention-driven operations of the updated second intention carried in the received intention knowledge capability query request.

[0150] S106. The first intent-based system sends an intent-knowledge-capability query response to the second intent-based system. The intent-knowledge-capability query response includes at least one of the following information: an identifier of the second intent-based system, an identifier of at least one third intent-based system, and intent-related knowledge of the first intent in the at least one third intent-based system. Accordingly, the second intent-based system receives the intent-knowledge-capability query response sent by the at least one third intent-based system.

[0151] The first intention system feeds back the queried intent knowledge of the associated first intention to the second intention system.

[0152] S107. The second intent system associates the intent knowledge of the first intent in at least one third intent system with the updated intent keywords, intent-driven objects, and intent-driven operations of the second intent.

[0153] Specifically, if the second intention system adds new intent knowledge, the above-mentioned intent knowledge capability query request includes the newly added second intent's Intentkeyword, IDA and IDO; the first intention system queries the relevant first intent's intent knowledge in the first intention system based on the newly added second intent's Intentkeyword, IDA and IDO in the second intention system; the second intention system associates the intent knowledge of the first intention with at least one of the newly added second intent's Intentkeyword, IDA and IDO.

[0154] Specifically, if the second intent system modifies the Intentkeyword of the second intent, the above-mentioned intent knowledge capability query request includes the modified Intentkeyword of the second intent; the first intent system queries the Intentkeyword of the first intent based on the modified Intentkeyword of the second intent; the second intent system associates the modified Intentkeyword of the second intent with the Intentkeyword of the first intent.

[0155] If the second intention system modifies the IDO / IDA of the second intention, the above-mentioned intention knowledge capability query request includes the modified IDO / IDA of the second intention; the first intention system queries the IDO / IDA of the first intention based on the modified IDO / IDA of the second intention; the second intention system associates the modified IDO / IDA of the second intention with the IDO / IDA of the first intention.

[0156] By associating the intent knowledge of the first intent in at least one third intent system with the updated intent keywords, intent-driven objects, and intent-driven operations of the second intent through the second intent system, it is possible to avoid the situation where the intent knowledge update of the second intent cannot be associated with the intent knowledge of the first intent in the second intention system, and the intent decomposition and distribution cannot be achieved.

[0157] According to a method for associating intent knowledge between intent systems provided in an embodiment of the present application, the association of intent knowledge between intent systems can be achieved when the intent knowledge of the first intent of the first intent system is updated or the intent knowledge of the second intent of the second intent system is updated, thereby avoiding the update of the intent knowledge of the first intent leading to the loss or invalidation of the intent knowledge of the first intent in the second intent system, or avoiding the update of the intent knowledge of the second intent being unable to be associated with the intent knowledge of the first intent in the second intention system, thereby failing to achieve intent decomposition and distribution.

[0158] under Figures 9 to 12 The low-level intent system updates the intent knowledge and informs the high-level intent system of the knowledge base scenario.

[0159] like Figure 9 The figure shows a flow chart of another method for associating intent knowledge between intent systems provided in an embodiment of the present application. In this embodiment, the low-level intent system adds new intent knowledge and notifies the high-level intent system through a subscription-notification method. Specifically, the method may include the following steps:

[0160] In steps S201 to S202, the knowledge management FB of the high-level intent system sends an intent knowledge update subscription request updateKnowledgeSubscription(consumerReference, filter) to the low-level intent system, where consumerReference is the identifier of the high-level intent system, and filter (i.e., update type) is the filter constraint for subscription notifications, including [add, modify, delete].

[0161] Step 203: The data ingestion and normalization FB of the low-level intent system converts the format of the received message and sends updateKnowledgeSubscription to the knowledge management FB.

[0162] Step 204: The knowledge management FB of the low-level intent system starts a subscription according to updateKnowledgeSubscription and allocates a subscription identifier (SubscriptionID).

[0163] In steps S205-S207, the knowledge management FB of the low-level intent system sends an intent knowledge update subscription response (updateKnowledgeSubscriptionResponse(SubscriptionID, status)) to the high-level intent system, carrying SubscriptionID and status. SubscriptionID is the subscription identifier of the low-level intent system, and status indicates whether the subscription was successfully started (referred to as subscription status).

[0164] Steps S208 to S212: The external system (user / APP / OSS- / BSS-like) adds new intent knowledge to the low-level intent system, which carries the update type (new), intent keywords, and intent knowledge.

[0165] If the low-level intent system successfully adds new intent knowledge:

[0166] In steps S213 to S215, the knowledge management FB of the low-level intent system sends an intent knowledge update notification updateKnowledgeNotification(SubscriptionID, add, intentkeyword, IDO, IDA) to the knowledge management FB of the high-level intent system, where SubscriptionID is the subscription identifier of the low-level intent system, add is the newly added intent knowledge identifier of the low-level intent system, intentkeyword, IDO and IDA represent the newly added intent knowledge of the low-level intent system.

[0167] Step S216: The knowledge management FB of the high-level intent system adds the newly added intent knowledge in the low-level intent system to the knowledge repository, and associates it with its own intent knowledge as a sub-intent.

[0168] Specifically, the high-level intent system searches for the intent knowledge of the second intent in the high-level intent system based on the IDO and IDA in the newly added intent knowledge (the first intent knowledge) (the second intent is the intent of the high-level intent system). The IDO of the first intent is contained in the IDO of the second intent, and / or the IDA of the first intent is contained in the IDA of the second intent, that is, the first intent exists as a sub-intent in the high-level intent system. The high-level intent system associates the intentkeyword, IDO, and IDA of the first intent with the intent knowledge of the second intent.

[0169] In this embodiment, the low-level intent system can notify the high-level intent system after adding new intent knowledge, so that the newly added intent knowledge can exist as a sub-intention in the knowledge repository of the high-level intent system, which can enhance the intent decomposition and delivery capabilities of the high-level intent system.

[0170] A new intent knowledge update subscription operation is added to the interface between the fusion system and the intent system. After the low-level intent system adds new intent knowledge, the new intent knowledge is fed back through the intent knowledge update notification.

[0171] A new sub-intention knowledge association function is added within the fusion system, which associates the new intent knowledge of the low-level intent system with the intent knowledge of the high-level intent system as a sub-intention.

[0172] like Figure 10 The figure shows a flow chart of another method for associating intent knowledge between intent systems provided in an embodiment of the present application. In this embodiment, the low-level intent system modifies / deletes intent knowledge and notifies the high-level intent system knowledge base through a subscription-notification method. Specifically, the method may include the following steps:

[0173] Steps 301 to 307, reference Figure 9 Steps S201 to S207 of the illustrated embodiment.

[0174] In steps S308 to S312, the external system (user / APP / OSS- / BSS-like) instructs the low-level intent system to update the intent knowledge, which includes the update type (modify / delete), intent keywords, and intent knowledge.

[0175] If the low-level intent system updates intent knowledge successfully:

[0176] If the low-level intent system deletes the original intent knowledge:

[0177] In steps S313 to S315, the knowledge management FB of the low-level intent system sends an intent knowledge update notification updateKnowledgeNotification(SubscriptionID, delete, intentkeyword) to the knowledge management FB of the high-level intent system, where SubscriptionID is the subscription identifier assigned by the low-level intent system, delete means the low-level intent system deletes the intent knowledge, and intentkeyword indicates the intent knowledge deleted by the low-level intent system.

[0178] Step S316: The high-level intent system deletes the intent knowledge deleted from the low-level intent system in the knowledge repository.

[0179] Specifically, the high-level intent system searches for the intent knowledge of the first intent corresponding to the intent keyword of the intent knowledge deleted from the low-level intent system (the intent knowledge of the first intent). The high-level intent system deletes the intent knowledge of the first intent that it has found.

[0180] If the low-level intent system modifies the original intent knowledge:

[0181] Steps S317 to S319, the knowledge management FB of the low-level intent system sends an intent knowledge update notification updateKnowledgeNotification(SubscriptionID, modify, intentkeywordbefore, intentkeywordafter) to the knowledge management FB of the high-level intent system, where modify is the intent knowledge change identifier of the low-level intent system. If the intent keyword is modified, intentkeywordbefore is the intent before the change, and intentkeywordafter is the intent after the change; if the IDO / IDA is modified, the intent knowledge update notification includes the intent keyword, intentkeywordbefore is the IDO / IDA before the change, and intentkeywordafter is the IDO / IDA after the change.

[0182] Step S320: The high-level intent system changes the modified intent knowledge in the low-level intent system to the knowledge repository, and associates the sub-intent knowledge with its own intent knowledge.

[0183] Specifically, if the update type included in the intent knowledge update notification is to modify the original intent knowledge in the low-level intent system (the intent knowledge of the first intent), the modification includes modifying one or more of the intent keywords, IDO, and IDA in the intent knowledge of the first intent. Therefore, the high-level intent system performs at least one of the following operations based on the specific modification content:

[0184] If the low-level intent system modifies the intent keywords of the original intent knowledge, the intent knowledge update notification includes the intent keywords of the first intent before the modification and the intent keywords of the first intent after the modification. The high-level intent system searches the intent knowledge base of the high-level intent system for the intent knowledge of the first intent corresponding to the intent keywords of the first intent before the modification based on the intent keywords of the first intent before the modification. The first intent exists as a sub-intent in the high-level intent system. The high-level intent system replaces the intent keywords of the first intent before the modification in the intent knowledge of the first intent with the intent keywords of the modified first intent.

[0185] If the low-level intent system modifies the IDO / IDA of the original intent knowledge, the intent knowledge update notification includes the intent keyword of the first intent, the IDO / IDA of the first intent before modification, and the IDO / IDA of the first intent after modification. The high-level intent system searches the intent knowledge of the second intent of the high-level intent system in the intent knowledge base of the high-level intent system based on the IDO / IDA of the modified first intent. The IDO of the modified first intent is included in the IDO of the second intent, and / or the IDA of the modified first intent is included in the IDA of the second intent, that is, the first intent exists in the form of a sub-intent in the high-level intent system. The high-level intent system associates the IDO / IDA of the modified first intent with the intent knowledge of the second intent. For example, the IntentDrivenObjectProperties in the IDO of the first intent before modification is Lujiazui, the IntentDrivenObjectProperties in the IDO of the first intent after modification is Xujiahui, and the IntentDrivenObjectProperties in the IDO of the second intent is Xuhui, that is, the modified IDO of the first intent is included in the IDO of the second intent, and the modified IDO of the first intent is associated with the intent knowledge of the second intent.

[0186] Furthermore, the high-level intent system queries the intent knowledge of the third intent in the high-level intent system based on the IDO / IDA of the first intent before modification, wherein the IDO of the first intent before modification is contained in the IDO of the third intent, and / or the IDA of the first intent before modification is contained in the IDA of the third intent. The high-level intent system disassociates the IDO / IDA of the first intent before modification from the intent knowledge of the third intent. For example, in the above example, the IntentDrivenObjectProperties in the IDO of the third intent is Pudong, and the IDO of the first intent before modification is contained in the lDO of the third intent, then the IDO of the first intent before modification is disassociated from the intent knowledge of the third intent.

[0187] In this embodiment, the low-level intent system can notify the high-level intent system after modifying or deleting intent knowledge. This allows the modified intent knowledge to be modified and associated with sub-intents in the high-level intent system's knowledge repository, preventing sub-intent knowledge from becoming invalid or intent decomposition from being inefficient during intent decomposition and delivery by the high-level intent system. Furthermore, deleted intent knowledge is also deleted from the high-level intent system's knowledge repository, preventing intent delivery failure during intent decomposition by the high-level intent system.

[0188] A new intent knowledge update subscription operation is added on the interface between fusion systems. After the low-level intent system modifies / deletes intent knowledge, the modified / deleted intent knowledge is fed back through the intent knowledge update notification.

[0189] New sub-intent knowledge modification, deletion, and association functions have been added to the fusion system. For intent knowledge modified by the low-level intent system, the high-level intent system's intent knowledge can be modified, disassociated, and reassociated before and after the modification. For intent knowledge deleted by the low-level intent system, the high-level intent system's intent knowledge can be deleted and disassociated after the deletion.

[0190] like Figure 11 The figure shows a flow chart of another method for associating intent knowledge between intent systems provided in an embodiment of the present application. In this embodiment, the low-level intent system adds new intent knowledge and directly reports it to the high-level intent system knowledge base. Specifically, the method may include the following steps:

[0191] In steps S401 to S405, the external system (user / APP / OSS- / BSS-like) adds new intent knowledge to the low-level intent system, which carries the update type (new), intent keywords, and intent knowledge.

[0192] If the low-level intent system successfully adds new intent knowledge:

[0193] In steps S406 to S408, the knowledge management FB of the low-level intent system sends an intent knowledge update report updateKnowledgeReport(producerReference, add, intentkeyword, IDO, IDA) (also called intent knowledge update notification) to the knowledge management FB of the high-level intent system, where producerReference is the identifier of the low-level intent system, add is the newly added intent knowledge of the low-level intent system, intentkeyword, IDO and IDA represent the newly added intent knowledge of the low-level intent system.

[0194] S409. The knowledge management FB of the high-level intent system adds the newly added intent knowledge in the low-level intent system to its own knowledge repository, and associates it with its own intent knowledge as a sub-intent.

[0195] The specific implementation process can be found in Figure 9 Step S216 of the illustrated embodiment.

[0196] S410~S412, the high-level intent system sends an intent knowledge report response updateKnowledgeReport Response(status) (also called intent knowledge update response) to the low-level intent system, where status indicates whether the knowledge repository of the high-level intent system has performed an add operation.

[0197] In this embodiment, the low-level intent system can directly report the newly added intent knowledge to the high-level intent system, so that the newly added intent knowledge can exist as a sub-intention in the knowledge repository of the high-level intent system, which can enhance the intent decomposition and distribution capabilities of the high-level intent system.

[0198] A new intent knowledge update reporting operation is added on the interface between the fusion systems. After the low-level intent system adds new intent knowledge, the new intent knowledge will be directly reported to the high-level intent system without the need for the high-level intent system to send a subscription notification in advance.

[0199] A new sub-intention knowledge association function is added within the fusion system, which associates the new intent knowledge of the low-level intent system with the intent knowledge of the high-level intent system as a sub-intention.

[0200] like Figure 12 The figure shows a flow chart of another method for associating intent knowledge between intent systems provided in an embodiment of the present application. In this embodiment, the low-level intent system modifies / deletes intent knowledge and notifies the high-level intent system knowledge base by directly reporting it. Specifically, the method may include the following steps:

[0201] In steps S501 to S505, the external system (user / APP / OSS- / BSS-like) instructs the low-level intent system to update intent knowledge, which includes the update type (modify / delete), intent keywords, and intent knowledge.

[0202] If the low-level intent system updates intent knowledge successfully:

[0203] If the low-level intent system deletes the original intent knowledge:

[0204] Steps S506 to 508, the knowledge management FB of the low-level intent system sends an intent knowledge update report updateKnowledgeReport(producerReference, delete, intentkeyword) to the knowledge management FB of the high-level intent system, where producerReference is the low-level intent system identifier, delete is the low-level intent system deleting intent knowledge, and intentkeyword represents the intent knowledge deleted by the low-level intent system.

[0205] Step S509: The high-level intent system deletes the intent knowledge deleted from the low-level intent system in the knowledge repository.

[0206] For specific implementation, please refer to Figure 10 Step S316 of the illustrated embodiment.

[0207] In steps S510 to S512 , the high-level intent system sends updateKnowledgeReport Response (delete, status) to the low-level intent system, where status indicates whether the knowledge repository of the high-level intent system has been deleted.

[0208] If the low-level intent system modifies the original intent knowledge:

[0209] In steps S513 to S515, the knowledge management FB of the low-level intent system sends an intent knowledge update report updateKnowledgeReport(producerReference, modify, intentkeywordbefore, intentkeywordafter) to the knowledge management FB of the high-level intent system, where modify is the intent knowledge change identifier of the low-level intent system, intentkeywordbefore is the intent keyword, IDO and IDA before the change, and intentkeywordafter is the intent keyword, IDO and IDA after the change.

[0210] Step S516: The high-level intent system changes the modified intent knowledge in the low-level intent system to the knowledge repository, and associates the sub-intent knowledge with its own intent knowledge.

[0211] For specific implementation, please refer to Figure 10 Step S320 of the illustrated embodiment.

[0212] In steps S517 to S519, the high-level intent system sends updateKnowledgeReport Response (modify, status) to the low-level intent system, where status indicates whether the knowledge repository of the high-level intent system has been modified.

[0213] In this embodiment, the low-level intent system can directly report intent knowledge modifications / deletions to the high-level intent system. This allows the modified intent knowledge to be modified and associated with sub-intents in the high-level intent system's knowledge repository, preventing sub-intent knowledge failure or inefficient intent decomposition during intent decomposition and delivery by the high-level intent system. Furthermore, deleted intent knowledge is also deleted from the high-level intent system's knowledge repository, preventing intent delivery failure during intent decomposition by the high-level intent system.

[0214] A new intent knowledge update reporting operation is added to the interface between fusion systems. After the low-level intent system modifies / deletes the intent knowledge, it is directly reported to the high-level intent system without the need for the high-level intent system to send a subscription notification in advance.

[0215] New sub-intent knowledge modification, deletion, and association functions have been added to the fusion system. For intent knowledge modified by the low-level intent system, the high-level intent system's intent knowledge can be modified, disassociated, and reassociated before and after the modification. For intent knowledge deleted by the low-level intent system, the high-level intent system's intent knowledge can be deleted and disassociated after the deletion.

[0216] under Figure 13 and Figure 14 The illustrated embodiment corresponds to a scenario in which a high-level intent system updates intent knowledge and queries a low-level intent system knowledge base.

[0217] like Figure 13 The figure shows a flow chart of another method for associating intent knowledge between intent systems provided in an embodiment of the present application. In this embodiment, the high-level intent system adds new intent knowledge and queries the knowledge base of all low-level intent systems. Specifically, the method may include the following steps:

[0218] Steps S601 to S605 : The external system (user / APP / OSS- / BSS-like) instructs the high-level intent system to add / modify intent knowledge.

[0219] If the high-level intent system successfully adds / modifies intent knowledge:

[0220] In steps S606-S607, the high-level intent system sends an intent knowledge capability query request queryKnowledgeCapacity(consumerReference, Intentkeyword, IDO, IDA) to all the lower-level intent systems (called third intent systems) below it. Intentkeyword, IDO, and IDA are the intent knowledge newly added / modified in step S603 based on the content of step S601.

[0221] Step S608: The knowledge management module of each low-level intent system queries for related / associated intent knowledge (RelatedIntentknowledge) based on the Intentkeyword, IDO, and IDA. RelatedIntentknowledge is the related sub-intent knowledge obtained by querying the low-level intent system based on the newly added / modified Intentkeyword, IDO, and IDA in the high-level intent system, including the intentkeyword, IDO, and IDA of the sub-intent knowledge.

[0222] Steps S609 to S611: The high-level intent system sends a queryKnowledgeCapacity Response (consumerReference, Intentkeyword, RelatedIntentknowledge) to the low-level intent system. Intentkeyword is the knowledge of the high-level intent system, and RelatedIntentknowledge is the knowledge of the low-level intent system.

[0223] Step S612: The high-level intent system updates the RelatedIntentknowledge to the knowledgerepository and associates the sub-intent knowledge with its own intent knowledge.

[0224] Specifically, if the high-level intent system adds new intent knowledge, the above-mentioned intent knowledge capability query request includes the newly added second intent's Intentkeyword, IDA and IDO; the low-level intent system queries the relevant first intent's intent knowledge in the low-level intent system based on the newly added second intent's Intentkeyword, IDA and IDO in the high-level intent system; the high-level intent system associates the intent knowledge of the first intent with at least one of the newly added second intent's Intentkeyword, IDA and IDO.

[0225] Specifically, if the high-level intent system modifies the Intentkeyword of the second intent, the above-mentioned intent knowledge capability query request includes the modified Intentkeyword of the second intent; the low-level intent system queries the Intentkeyword of the first intent based on the modified Intentkeyword of the second intent; the high-level intent system associates the modified Intentkeyword of the second intent with the Intentkeyword of the first intent.

[0226] If the high-level intent system modifies the IDO / IDA of the second intent, the above-mentioned intent knowledge capability query request includes the modified IDO / IDA of the second intent; the low-level intent system queries the IDO / IDA of the first intent based on the modified IDO / IDA of the second intent; the high-level intent system associates the modified IDO / IDA of the second intent with the IDO / IDA of the first intent.

[0227] In this embodiment, the high-level intent system queries the relevant intent knowledge of the low-level intent system after adding / modifying intent knowledge, so that the intent knowledge in the low-level intent system is added / modified as sub-intention knowledge in the high-level intent system. The high-level intent system can decompose and distribute the newly added / modified intent knowledge.

[0228] A new intent knowledge capability query operation is added to the interface between fusion systems. After intent knowledge is added to the high-level intent system, this operation is used to query the intent knowledge of the low-level intent system.

[0229] A new sub-intention knowledge association function is added within the fusion system, which associates the intent knowledge of the low-level intent system obtained from the query as a sub-intention to the newly added intent knowledge of the high-level intent system.

[0230] like Figure 14 The figure shows a flow chart of another method for associating intent knowledge between intent systems provided in an embodiment of the present application. In this embodiment, the high-level intent system adds new intent knowledge and queries some low-level intent system knowledge bases (it is necessary to decide which low-level intent system knowledge bases to query).

[0231] The high-level intent system needs to determine which low-level intent systems to query based on sub-intent knowledge to determine the list. The sub-intent knowledge in the high-level intent system (the intent knowledge in the low-level intent system) includes Intentkeyword, IDO, and IDA. The general form of IDO and IDA is as follows, including the "action" and "object" of the intent:

[0232] <intentdrivenaction> ：＝ <intentdrivenactionname> <intentdrivenactionproperties>

[0233] <intentdrivenobject> ：＝ <intentdrivenobjectname> <intentdrivenobjectproperties>

[0234] Therefore, the low-level intent systems are screened based on the IDO of the newly added intent knowledge and the IDO of the existing sub-intent knowledge of the high-level intent system. Only the low-level intent systems that meet the scope of the newly added intent knowledge IDO are queried. The method and steps for determining the list of low-level intent systems are as follows:

[0235] 1. New intent knowledge is added to the high-level intent system, including Intentkeyword1, IDO1, IDA1, constraint1 and intentOperations1[execntionConditon, operationType, operation].

[0236] 2. The high-level intent system searches for IntentDrivenObjectName2 and IntentDrivenObjectProperties2 of the existing sub-intent knowledge based on IntentDrivenObjectName1 and IntentDrivenObjectProperties1 in IDO 1. If IntentDrivenObjectName2 and IntentDrivenObjectProperties2 are within the range of IntentDrivenObjectName1 and IntentDrivenObjectProperties1, the low-level intent system corresponding to IntentDrivenObjectName2 and IntentDrivenObjectProperties2 is put into the list.

[0237] For example: If IntentDrivenObjectProperties1 is Pudong and IntentDrivenObjectProperties2 is Jinqiao, the low-level intent system corresponding to IntentDrivenObjectProperties2 is put into the list; if IntentDrivenObjectProperties2 is Minhang, the low-level intent system corresponding to IntentDrivenObjectProperties2 does not need to be put into the list.

[0238] Of course, the low-level intent system is also screened based on the IDA of the newly added intent knowledge of the high-level intent system and the IDA of the existing sub-intent knowledge.

[0239] Specifically, the method may include the following steps:

[0240] Steps S701 to S705, reference Figure 13 Steps S601 to S605 of the embodiment shown.

[0241] If the high-level intent system successfully adds / modifies intent knowledge:

[0242] Step S706: The high-level intent system determines the list of low-level intent systems that need to be queried based on the Intentkeyword, IDO, and IDA of the newly added / modified intent knowledge.

[0243] In steps S707 to S709, the high-level intent system sends an intent knowledge capability query request queryKnowledgeCapacity(consumerReference, Intentkeyword, IDO, IDA) to the low-level intent systems in the list. Intentkeyword, IDO, IDA are the intent knowledge newly added / modified by the high-level intent system in step S703 based on the content of step S701.

[0244] In step S710, the knowledge management module of the low-level intent system queries the related intent knowledge RelatedIntentknowledge based on the Intentkeyword, IDO, and IDA. RelatedIntentknowledge is the related sub-intent knowledge obtained by querying the new / modified Intentkeyword, IDO, and IDA in the high-level intent system in the low-level intent system, including the intentkeyword, IDO, and IDA of the sub-intent knowledge.

[0245] In steps S711 to S713, the low-level intent system sends a queryKnowledgeCapacity Response (consumerReference, Intentkeyword, RelatedIntentknowledge) to the high-level intent system. Intentkeyword is the intent knowledge added / modified by the high-level intent system, and RelatedIntentknowledge is the intent knowledge queried by the low-level intent system.

[0246] Step S714: The high-level intent system updates the RelatedIntentknowledge to the knowledgerepository and associates the sub-intent knowledge with its own intent knowledge.

[0247] In this embodiment, after the high-level intent system adds / modifies intent knowledge, it queries the relevant intent knowledge of the low-level intent system according to the low-level intent system list, so that the intent knowledge in the low-level intent system is added / modified as sub-intent knowledge in the high-level intent system. The high-level intent system can decompose and distribute the newly added / modified intent knowledge.

[0248] A new intent knowledge capability query operation is added to the interface between fusion systems. After intent knowledge is added to the high-level intent system, this operation is used to query the intent knowledge of the low-level intent system.

[0249] A new low-level intent system query list confirmation function has been added within the fusion system.

[0250] A new sub-intention knowledge association function is added within the fusion system, which associates the intent knowledge of the low-level intent system obtained from the query as a sub-intention to the newly added intent knowledge of the high-level intent system.

[0251] Based on the same concept of the above-mentioned method for associating intent knowledge between intent systems, this application also provides the following communication device:

[0252] like Figure 15 FIG. 1 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device may be the aforementioned second intention system or a module in the second intention system. The communication device 100 includes a transceiver unit 11 and a processing unit 12; wherein:

[0253] A transceiver unit 11 is used to receive an intent knowledge update notification sent by a first intent system when the intent knowledge of the first intent of the first intent system is updated, wherein the intent knowledge update notification includes an update type and an intent keyword of the first intent; and a processing unit 12 is used to associate the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the intent knowledge of the second intent in the second intention system according to the intent knowledge update notification, wherein the first intent is a sub-intention of the second intent.

[0254] In one possible implementation, the transceiver unit 11 is also used to send an intent knowledge update subscription request to the first intent system, and the intent knowledge update subscription request includes the identifier and update type of the second intent system; and the transceiver unit 11 is also used to receive an intent knowledge update subscription response sent by the first intent system, and the intent knowledge update subscription response includes at least one of the following information: subscription identifier, subscription status; wherein, the intent knowledge update notification also includes the subscription identifier.

[0255] In another possible implementation, the intent knowledge update notification further includes an identifier of the first intent system, and the transceiver unit 11 is further configured to send an intent knowledge update response to the first intent system.

[0256] In another possible implementation, the update type is to add the intention knowledge of the first intention, and the intention knowledge update notification also includes the intention-driven object and intention-driven operation of the first intention; the processing unit 12 is used to query the intention knowledge of the second intention in the second intention system based on the intention-driven object and intention-driven operation of the first intention, wherein the intention-driven object of the first intention is included in the intention-driven object of the second intention, and / or the intention-driven operation of the first intention is included in the intention-driven operation of the second intention; and the processing unit 12 is also used to associate the intention keywords of the first intention, the intention-driven object and the intention-driven operation with the intention knowledge of the second intention.

[0257] In another possible implementation, the update type is to delete the intention knowledge of the first intention, and the processing unit 12 is used to search for the intention knowledge of the first intention corresponding to the intention keyword of the first intention in the second intention system based on the intention keyword of the first intention; and the processing unit 12 is also used to delete the intention knowledge of the first intention found.

[0258] In another possible implementation, the update type is to modify the intention knowledge of the first intention, and the intention knowledge update notification also includes at least one of the following information: the keyword of the first intention before modification, the intention-driven object of the first intention before modification, the intention-driven operation of the first intention before modification, the keyword of the first intention after modification, the intention-driven object of the first intention after modification, and the intention-driven operation of the first intention after modification; the processing unit 12 is used to perform at least one of the following operations: after the first intention system modifies the intention keyword of the first intention, according to the intention keyword of the first intention before modification, the intention knowledge of the first intention corresponding to the intention keyword of the first intention before modification is searched in the second intention system, and the intention knowledge of the first intention corresponding to the intention keyword of the first intention before modification is searched. The modified intention keywords of the first intention replace the intention keywords of the first intention before modification in the intention knowledge of the first intention; after the first intention system modifies the intention-driven object and / or intention-driven operation of the first intention, the intention knowledge of the second intention is queried in the second intention system based on the modified intention-driven object and / or intention-driven operation of the first intention, wherein the modified intention-driven object of the first intention is included in the intention-driven object of the second intention, and / or the modified intention-driven operation of the first intention is included in the intention-driven operation of the second intention; the modified intention-driven object and / or intention-driven operation of the first intention is associated with the intention knowledge of the second intention.

[0259] In another possible implementation, the processing unit 12 is further used to query the intention knowledge of the third intention in the second intention system based on the intention-driven object and / or intention-driven operation of the first intention before the modification, wherein the intention-driven object of the first intention before the modification is included in the intention-driven object of the third intention, and / or the intention-driven operation of the first intention before the modification is included in the intention-driven operation of the third intention; the processing unit 12 is also used to de-associate the intention-driven object and / or intention-driven operation of the first intention before the modification with the intention knowledge of the third intention.

[0260] In another possible implementation, the transceiver unit 11 is also used to update the intention knowledge of the second intention and send an intention knowledge capability query request to at least one third intention system, wherein the intention knowledge capability query request includes at least one of the following information: the identifier of the second intention system, the updated intention keyword of the second intention, the intention-driven object, and the intention-driven operation, wherein the first intention system is one of the at least one third intention systems; the transceiver unit 11 is also used to receive the intention knowledge capability query response sent by the at least one third system, and the intention knowledge capability query response includes at least one of the following information: the identifier of the second intention system, the identifier of the at least one third intention system, and the intention knowledge of the first intention associated with at least one of the updated intention keywords, intention-driven objects, and intention-driven operations of the second intention; and the processing unit 12 is also used to associate the intention knowledge of the first intention with at least one of the updated intention keywords, intention-driven objects, and intention-driven operations of the second intention.

[0261] In another possible implementation, the update type is to modify the intention knowledge of the second intention, and the processing unit 12 is also used to perform at least one of the following operations: after the second intention system modifies the intention keywords of the second intention, the modified intention keywords of the second intention are associated with the intention keywords of the first intention; or after the second intention system modifies the intention-driven object and / or intention-driven operation of the second intention, the modified intention-driven object and / or intention-driven operation of the second intention is associated with the intention-driven object and / or intention-driven operation of the first intention.

[0262] In another possible implementation, the processing unit 12 is further used to query the intention knowledge of the fourth intention in the at least one third intention system in the second intention system based on the intention-driven object and / or intention-driven operation of the second intention before modification, wherein the intention-driven object of the second intention before modification includes the intention-driven object of the fourth intention, and / or the intention-driven operation of the second intention before modification includes the intention-driven operation of the fourth intention; and the processing unit 12 is further used to de-associate the intention-driven object and / or intention-driven operation of the second intention before modification with the intention knowledge of the fourth intention.

[0263] In another possible implementation, the processing unit 12 is further used to determine the at least one third intention system based on the updated intention-driven object of the second intention, wherein the intention-driven object of the first intention in the at least one third intention system is included in the updated intention-driven object of the second intention.

[0264] For the specific implementation of the above-mentioned transceiver unit 11 and processing unit 12, please refer to Figures 8 to 14 Related description of the second intention system in .

[0265] According to a communication device provided in an embodiment of the present application, when the intent knowledge of the first intent of the first intention system is updated or the intent knowledge of the second intent of the second intention system is updated, the association of intent knowledge between intent systems can be realized, thereby avoiding the situation where the intent knowledge update of the first intention causes the loss or invalidation of the intent knowledge of the first intention in the second intention system, or avoiding the situation where the intent knowledge update of the second intention cannot be associated with the intent knowledge of the first intention in the second intention system, and the intention decomposition and distribution cannot be realized.

[0266] like Figure 16 FIG2 is a schematic diagram of the structure of another communication device provided in an embodiment of the present application. The communication device can be the first intention system described above, or a module in the first intention system. The communication device 200 includes: a processing unit 21 and a transceiver unit 22; wherein:

[0267] A processing unit 21 is used to determine whether the intent knowledge of the first intent of the first intent system is updated; and a transceiver unit 22 is used to send an intent knowledge update notification to the second intent system, so that the second intent system associates the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the intent knowledge of the second intention in the second intention system according to the intent knowledge update notification, wherein the first intent is a sub-intention of the second intent, and the intent knowledge update notification includes the update type and the intent keyword of the first intent.

[0268] In one possible implementation, the transceiver unit 22 is also used to receive an intent knowledge update subscription request sent by the second intent system, and the intent knowledge update subscription request includes the identifier and update type of the second intent system; and the transceiver unit 22 is also used to send an intent knowledge update subscription response to the second intent system, and the intent knowledge update subscription response includes at least one of the following information: subscription identifier, subscription status; wherein the intent knowledge update notification also includes the subscription identifier.

[0269] In another possible implementation, the transceiver unit 22 is further configured to receive an intent knowledge update response sent by the second intent system.

[0270] In another possible implementation, the update type includes at least one of the following: adding the intention knowledge of the first intention, deleting the intention knowledge of the first intention, and modifying the intention knowledge of the first intention; if the update type is adding the intention knowledge of the first intention, the intention knowledge update notification also includes the intention-driven object and intention-driven operation of the first intention; if the update type is modifying the intention knowledge of the first intention, the intention knowledge notification also includes at least one of the following information: the keyword of the first intention before modification, the intention-driven object of the first intention before modification, the intention-driven operation of the first intention before modification, the keyword of the first intention after modification, the intention-driven object of the first intention after modification, and the intention-driven operation of the first intention after modification.

[0271] In another possible implementation, the transceiver unit 22 is also used to update the intention knowledge of the second intention, receive the intention knowledge capability query request sent by the second intention system, and the intention knowledge capability query request includes at least one of the following information: the identifier of the second intention system, the intention keywords of the updated second intention, the intention-driven object, and the intention-driven operation, wherein the first intention system is one of the at least one third intention systems; the processing unit 21 is used to find the intention knowledge of the first intention associated with at least one of the intention keywords, intention-driven objects, and intention-driven operations of the updated second intention; and the transceiver unit 22 is also used to send an intention knowledge capability query response to the second intention system, and the intention knowledge capability query response includes at least one of the following information: the identifier of the second intention system, the identifier of the at least one third intention system, and the intention knowledge of the first intention.

[0272] For the specific implementation of the processing unit 21 and the transceiver unit 22, please refer to Figures 8 to 14 Related description of the first intention system in .

[0273] According to a communication device provided in an embodiment of the present application, when the intent knowledge of the first intent of the first intention system is updated or the intent knowledge of the second intent of the second intention system is updated, the association of intent knowledge between intent systems can be realized, thereby avoiding the situation where the intent knowledge update of the first intention causes the loss or invalidation of the intent knowledge of the first intention in the second intention system, or avoiding the situation where the intent knowledge update of the second intention cannot be associated with the intent knowledge of the first intention in the second intention system, and the intention decomposition and distribution cannot be realized.

[0274] like Figure 17 As shown, a schematic diagram of the structure of a communication device is also provided, which is used to perform the above communication method. Part or all of the above method can be implemented by hardware, or by software or firmware.

[0275] Optionally, the communication device may be a chip or an integrated circuit in specific implementation.

[0276] Optionally, when part or all of the communication methods in the above embodiments are implemented by software or firmware, Figure 17 A communication device 300 is provided to achieve this. Figure 17 As shown, the communication device 300 may include:

[0277] Memory 33 and processor 34 (the processor 34 in the device may be one or more, Figure 17 (taking a processor as an example), it may also include an input device 31 and an output device 32. In this embodiment, the input device 31, the output device 32, the memory 33 and the processor 34 may be connected via a bus or other means, wherein: Figure 17 The bus connection is taken as an example.

[0278] In one embodiment, the processor 34 is used to execute Figures 8 to 14 The method steps performed by the first intention system.

[0279] In another embodiment, the processor 34 is configured to execute Figures 8 to 14 The method steps performed by the second intention system.

[0280] Optionally, the program of the above communication method can be stored in the memory 33. The memory 33 can be a physically independent unit or integrated with the processor 34. The memory 33 can also be used to store data.

[0281] Optionally, when part or all of the communication methods of the above embodiments are implemented via software, the communication device may include only a processor. The memory for storing the program is located outside the communication device, and the processor is connected to the memory via circuits or wires to read and execute the program stored in the memory.

[0282] The processor may be a central processing unit (CPU), a network processor (NP), or a WLAN device.

[0283] The processor may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0284] The memory may include volatile memory, such as random-access memory (RAM); the memory may also include non-volatile memory, such as flash memory, a hard disk drive (HDD) or a solid-state drive (SSD); the memory may also include a combination of the above types of memory.

[0285] It will be understood by those skilled in the art that one or more embodiments of the present disclosure may be provided as a method, system, or computer program product. Therefore, one or more embodiments of the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0286] The present application also provides a chip system, including at least one processor and an interface. 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 method described in any of the above method embodiments is executed. Optionally, the chip system may consist of a chip alone, or may include a chip and other discrete components, which is not specifically limited in the present application.

[0287] An embodiment of the present application further provides a computer-readable storage medium, which may store a computer program. When the program is executed by a processor, the steps of the method described in any embodiment of the present disclosure are implemented.

[0288] An embodiment of the present application also provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the steps of the method described in any embodiment of the present disclosure.

[0289] An embodiment of the present application also provides a communication system, which includes the above-mentioned communication device.

[0290] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0291] 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. Furthermore, 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, the words "first" and "second" are used in the embodiments of this application to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that the words "first" and "second" do not limit the quantity or execution order, and the words "first" and "second" do not necessarily mean different. 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 construed as being preferred or advantageous over 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.

[0292] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the division of the units is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. The mutual coupling, direct coupling, or communication connection shown or discussed can be through some interface, indirect coupling or communication connection of devices or units, and can be electrical, mechanical or other forms.

[0293] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0294] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, 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 according to the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted via the computer-readable storage medium. 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 available media integrated therein. The available medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic medium such as a floppy disk, a hard disk, a tape, a magnetic disk, or an optical medium such as a digital versatile disc (DVD), or a semiconductor medium such as a solid state disk (SSD).< / intentdrivenobjectproperties> < / intentdrivenobjectname> < / intentdrivenobject> < / intentdrivenactionproperties> < / intentdrivenactionname> < / intentdrivenaction> < / intentdrivenobjectproperties> < / intentdrivenobjectname> < / intentdrivenobject> < / intentdrivenactionproperties> < / intentdrivenactionname> < / intentdrivenaction> < / intentdrivenobject> < / intentdrivenaction> < / intentexpression>

Claims

1. A method for associating intention knowledge between intention systems, characterized in that: The method comprises: When the intent knowledge of the first intent of the first intent system is updated, the second intent system receives the intent knowledge update notification sent by the first intent system, wherein the intent knowledge update notification includes the update type and the intent keyword of the first intent; The second intent system associates, according to the intent knowledge update notification, the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the intent knowledge of the second intent in the second intent system, wherein the first intent is a sub-intent of the second intent; The update type is adding intent knowledge of the first intent, and the intent knowledge update notification also includes the intent-driven object and intent-driven operation of the first intent; The second intent system associates, according to the intent knowledge update notification, the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the intent knowledge of the second intent in the second intent system, including: The second intention system queries the second intention system for intent knowledge of the second intention based on the intent-driven object and the intent-driven operation of the first intention, wherein the intent-driven object of the first intention is included in the intent-driven object of the second intention, and / or the intent-driven operation of the first intention is included in the intent-driven operation of the second intention; The second intention system associates the intention keywords of the first intention, the intention-driven object and the intention-driven operation with the intention knowledge of the second intention.

2. The method according to claim 1, characterized in that Before the second intent system receives the intent knowledge update notification sent by the first intent system, the method further includes: The second intent system sends an intent knowledge update subscription request to the first intent system, where the intent knowledge update subscription request includes an identifier and an update type of the second intent system; The second intent system receives the intent knowledge update subscription response sent by the first intent system, where the intent knowledge update subscription response includes at least one of the following information: a subscription identifier and a subscription status; The intent knowledge update notification further includes the subscription identifier.

3. The method according to claim 1, characterized in that The intent knowledge update notification also includes an identifier of the first intent system. After the second intent system receives the intent knowledge update notification sent by the first intent system, the method further includes: The second intent system sends an intent knowledge update response to the first intent system.

4. The method according to any one of claims 1 to 3, characterized in that The update type is to delete the intent knowledge of the first intent, and the second intent system associates the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the intent knowledge of the second intent in the second intent system according to the intent knowledge update notification, including: The second intention system searches, according to the intention keyword of the first intention, for intention knowledge of the first intention corresponding to the intention keyword of the first intention in the second intention system; The second intention system deletes the intention knowledge of the first intention found.

5. The method according to any one of claims 1 to 3, characterized in that The update type is to modify the intent knowledge of the first intent, and the intent knowledge update notification further includes at least one of the following information: a keyword of the first intent before the modification, an intent-driven object of the first intent before the modification, an intent-driven operation of the first intent before the modification, a keyword of the first intent after the modification, an intent-driven object of the first intent after the modification, and an intent-driven operation of the first intent after the modification; The second intent system associates, according to the intent knowledge update notification, the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the intent knowledge of the second intent in the second intent system, including at least one of the following operations: After the first intention system modifies the intention keyword of the first intention, the second intention system searches for the intention knowledge of the first intention corresponding to the intention keyword of the first intention before the modification in the second intention system based on the intention keyword of the first intention before the modification, and the second intention system replaces the intention keyword of the first intention before the modification in the intention knowledge of the first intention with the intention keyword of the first intention after the modification; After the first intention system modifies the intent-driven object and / or intention-driven operation of the first intention, the second intention system queries the intent knowledge of the second intention in the second intention system based on the modified intent-driven object and / or intention-driven operation of the first intention, wherein the modified intent-driven object of the first intention is included in the intent-driven object of the second intention, and / or the modified intent-driven operation of the first intention is included in the intent-driven operation of the second intention; The second intention system associates the modified intention-driven object and / or intention-driven operation of the first intention with the intention knowledge of the second intention.

6. The method according to claim 5, characterized in that The method further includes: the second intention system querying intent knowledge of a third intention in the second intention system based on the intent-driven object and / or the intent-driven operation of the first intention before the modification, wherein the intent-driven object of the first intention before the modification is included in the intent-driven object of the third intention, and / or the intent-driven operation of the first intention before the modification is included in the intent-driven operation of the third intention; The second intention system disassociates the intention-driven object and / or intention-driven operation of the first intention before the modification from the intention knowledge of the third intention.

7. The method according to any one of claims 1 to 3, characterized in that The method further comprises: The intent knowledge of the second intent is updated, and the second intent system sends an intent knowledge capability query request to at least one third intent system, wherein the intent knowledge capability query request includes at least one of the following information: an identifier of the second intent system, an updated intent keyword of the second intent, an intent-driven object, and an intent-driven operation, wherein the first intent system is one of the at least one third intent system; The second intent system receives an intent knowledge capability query response sent by the at least one third intent system, the intent knowledge capability query response including at least one of the following information: an identifier of the second intent system, an identifier of the at least one third intent system, and intent knowledge of the first intent associated with at least one of an intent keyword, an intent-driven object, and an intent-driven operation of the updated second intent; The second intention system associates the intention knowledge of the first intention with at least one of the updated intention keywords, intention-driven objects, and intention-driven operations of the second intention.

8. The method according to claim 7, characterized in that The update type is to modify the intent knowledge of the second intent. The second intent system associates the intent knowledge of the first intent with at least one of the updated intent keywords, intent-driven objects, and intent-driven operations of the second intent, including at least one of the following operations: After the second intent system modifies the intent keyword of the second intent, the second intent system associates the modified intent keyword of the second intent with the intent keyword of the first intent; After the second intention system modifies the intention-driven object and / or intention-driven operation of the second intention, the second intention system associates the modified intention-driven object and / or intention-driven operation of the second intention with the intention-driven object and / or intention-driven operation of the first intention.

9. The method according to claim 8, characterized in that The method further includes: the second intention system querying, in the second intention system, intent knowledge of a fourth intention in the at least one third intention system based on the intent-driven object and / or the intent-driven operation of the second intention before modification, wherein the intent-driven object of the second intention before modification includes the intent-driven object of the fourth intention, and / or the intent-driven operation of the second intention before modification includes the intent-driven operation of the fourth intention; The second intention system disassociates the intention-driven object and / or intention-driven operation of the second intention before modification from the intention knowledge of the fourth intention.

10. The method according to claim 7, characterized in that Before the second intent system sends the intent knowledge capability query request to at least one third intent system, the method further includes: The second intention system determines the at least one third intention system based on the updated intention-driven object of the second intention, wherein the intention-driven object of the first intention in the at least one third intention system is included in the updated intention-driven object of the second intention.

11. A method for associating intention knowledge between intention systems, characterized in that: The method comprises: Determining that the intention knowledge of the first intention of the first intention system is updated; The first intent system sends an intent knowledge update notification to the second intent system, so that the second intent system associates the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the intent knowledge of the second intent in the second intent system according to the intent knowledge update notification, wherein the first intent is a sub-intent of the second intent, and the intent knowledge update notification includes an update type and the intent keyword of the first intent; The update type includes adding intent knowledge of the first intent, and the intent knowledge update notification also includes the intent-driven object and intent-driven operation of the first intent; The second intent system associates the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the intent knowledge of the second intent in the second intent system according to the intent knowledge update notification, including: The second intention system queries the second intention system for intent knowledge of the second intention based on the intent-driven object and the intent-driven operation of the first intention, wherein the intent-driven object of the first intention is included in the intent-driven object of the second intention, and / or the intent-driven operation of the first intention is included in the intent-driven operation of the second intention; The second intention system associates the intention keywords of the first intention, the intention-driven object and the intention-driven operation with the intention knowledge of the second intention.

12. The method according to claim 11, characterized in that Before the first intent system sends the intent knowledge update notification to the second intent system, the method further includes: The first intent system receives an intent knowledge update subscription request sent by the second intent system, where the intent knowledge update subscription request includes an identifier and an update type of the second intent system; The first intent system sends an intent knowledge update subscription response to the second intent system, where the intent knowledge update subscription response includes at least one of the following information: a subscription identifier and a subscription status; The intent knowledge update notification further includes the subscription identifier.

13. The method according to claim 11, characterized in that After the first intent system sends the intent knowledge update notification to the second intent system, the method further includes: The first intent system receives an intent knowledge update response sent by the second intent system.

14. The method according to any one of claims 11 to 13, characterized in that The update type further includes at least one of the following: deleting the intention knowledge of the first intention, modifying the intention knowledge of the first intention; If the update type is to modify the intention knowledge of the first intention, the intention knowledge notification also includes at least one of the following information: keywords of the first intention before modification, the intention-driven object of the first intention before modification, the intention-driven operation of the first intention before modification, keywords of the first intention after modification, the intention-driven object of the first intention after modification, and the intention-driven operation of the first intention after modification.

15. The method according to any one of claims 11 to 13, characterized in that: The method further comprises: The intent knowledge of the second intent is updated, and the first intent system receives an intent knowledge capability query request sent by the second intent system, where the intent knowledge capability query request includes at least one of the following information: an identifier of the second intent system, an intent keyword of the updated second intent, an intent-driven object, and an intent-driven operation, wherein the first intent system is one of the at least one third intent system; The first intention system finds intention knowledge of the first intention associated with at least one of the intention keyword, the intention-driven object, and the intention-driven operation of the updated second intention; The first intent system sends an intent knowledge capability query response to the second intent system, and the intent knowledge capability query response includes at least one of the following information: an identifier of the second intent system, an identifier of the at least one third intent system, and intent knowledge of the first intent.

16. A communication device, characterized in that: The device comprises: a transceiver unit, configured to receive an intent knowledge update notification sent by a first intent system when intent knowledge of a first intent of the first intent system is updated, wherein the intent knowledge update notification includes an update type and intent keywords of the first intent; a processing unit, configured to associate, according to the intent knowledge update notification, the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the intent knowledge of the second intent in the device, wherein the first intent is a sub-intent of the second intent; The update type is adding intent knowledge of the first intent, and the intent knowledge update notification also includes the intent-driven object and intent-driven operation of the first intent; the processing unit being configured to query the device for intent knowledge of the second intent based on the intent-driven object and the intent-driven operation of the first intent, wherein the intent-driven object of the first intent is included in the intent-driven object of the second intent, and / or the intent-driven operation of the first intent is included in the intent-driven operation of the second intent; The processing unit is further used to associate the intention keywords of the first intention, the intention-driven object and the intention-driven operation with the intention knowledge of the second intention.

17. The device according to claim 16, characterized in that: The transceiver unit is further configured to send an intent knowledge update subscription request to the first intent system, wherein the intent knowledge update subscription request includes an identifier of the device and an update type; The transceiver unit is further configured to receive an intent knowledge update subscription response sent by the first intent system, wherein the intent knowledge update subscription response includes at least one of the following information: a subscription identifier and a subscription status; The intent knowledge update notification further includes the subscription identifier.

18. The device according to claim 16, characterized in that The intent knowledge update notification further includes an identifier of the first intent system; The transceiver unit is further configured to send an intent knowledge update response to the first intent system.

19. The device according to any one of claims 16 to 18, characterized in that The update type is to delete the intention knowledge of the first intention; The processing unit is further configured to search, in the device, for intent knowledge of the first intent corresponding to the intent keyword of the first intent, based on the intent keyword of the first intent; The processing unit is further used to delete the intention knowledge of the first intention found.

20. The device according to any one of claims 16 to 18, characterized in that The update type is to modify the intent knowledge of the first intent, and the intent knowledge update notification further includes at least one of the following information: a keyword of the first intent before the modification, an intent-driven object of the first intent before the modification, an intent-driven operation of the first intent before the modification, a keyword of the first intent after the modification, an intent-driven object of the first intent after the modification, and an intent-driven operation of the first intent after the modification; The processing unit is further configured to perform at least one of the following operations: After the first intention system modifies the intention keyword of the first intention, the device searches for the intention knowledge of the first intention corresponding to the intention keyword of the first intention before the modification based on the intention keyword of the first intention before the modification, and the device replaces the intention keyword of the first intention before the modification in the intention knowledge of the first intention with the intention keyword of the first intention after the modification; After the first intention system modifies the intent-driven object and / or intent-driven operation of the first intention, the device is queried for intent knowledge of the second intention based on the modified intent-driven object and / or intent-driven operation of the first intention, wherein the modified intent-driven object of the first intention is included in the intent-driven object of the second intention, and / or the modified intent-driven operation of the first intention is included in the intent-driven operation of the second intention; The modified intention-driven object and / or intention-driven operation of the first intention is associated with the intention knowledge of the second intention.

21. The device according to claim 20, characterized in that The processing unit is further configured to query the device for intent knowledge of a third intent based on the intent-driven object and / or the intent-driven operation of the first intent before the modification, wherein the intent-driven object of the first intent before the modification is included in the intent-driven object of the third intent, and / or the intent-driven operation of the first intent before the modification is included in the intent-driven operation of the third intent; The processing unit is further used to de-associate the intention-driven object and / or intention-driven operation of the first intention before the modification with the intention knowledge of the third intention.

22. The device according to any one of claims 16 to 18, characterized in that: The transceiver unit is further configured to, when the intent knowledge of the second intent is updated, send an intent knowledge capability query request to at least one third intent system, wherein the intent knowledge capability query request includes at least one of the following information: an identifier of the device, an updated intent keyword of the second intent, an intent-driven object, and an intent-driven operation, wherein the first intent system is one of the at least one third intent system; The transceiver unit is further configured to receive an intent knowledge capability query response sent by the at least one third intent system, the intent knowledge capability query response including at least one of the following information: an identifier of the device, an identifier of the at least one third intent system, and intent knowledge of the first intent associated with at least one of an intent keyword, an intent-driven object, and an intent-driven operation of the updated second intent; The processing unit is further used to associate the intention knowledge of the first intention with at least one of the updated intention keywords, intention-driven objects, and intention-driven operations of the second intention.

23. The device according to claim 22, characterized in that The update type is to modify the intent knowledge of the second intent, and the processing unit is further configured to perform at least one of the following operations: After modifying the intent keyword of the second intent, the device associates the modified intent keyword of the second intent with the intent keyword of the first intent; After modifying the intention-driven object and / or intention-driven operation of the second intention, the modified intention-driven object and / or intention-driven operation of the second intention is associated with the intention-driven object and / or intention-driven operation of the first intention.

24. The device according to claim 23, characterized in that The processing unit is further configured to query, in the device, intent knowledge of a fourth intent in the at least one third intention system based on the intent-driven object and / or the intent-driven operation of the second intent before modification, wherein the intent-driven object of the second intent before modification includes the intent-driven object of the fourth intent, and / or the intent-driven operation of the second intent before modification includes the intent-driven operation of the fourth intent; The processing unit is further used to de-associate the intention-driven object and / or intention-driven operation of the second intention before the modification with the intention knowledge of the fourth intention.

25. The device according to claim 22, characterized in that The processing unit is further used to determine the at least one third intention system based on the updated intention-driven object of the second intention, wherein the intention-driven object of the first intention in the at least one third intention system is included in the updated intention-driven object of the second intention.

26. A communication device, characterized in that: The device comprises: a processing unit, configured to determine that intention knowledge of a first intention of the apparatus is updated; a transceiver unit, configured to send an intent knowledge update notification to the second intent system, so that the second intent system associates the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the intent knowledge of the second intent in the second intent system according to the intent knowledge update notification, wherein the first intent is a sub-intent of the second intent, and the intent knowledge update notification includes an update type and the intent keyword of the first intent; The update type includes adding intent knowledge of the first intent, and the intent knowledge update notification also includes the intent-driven object and intent-driven operation of the first intent; The second intent system associates the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the intent knowledge of the second intent in the second intent system according to the intent knowledge update notification, including: The second intention system queries the second intention system for intent knowledge of the second intention based on the intent-driven object and the intent-driven operation of the first intention, wherein the intent-driven object of the first intention is included in the intent-driven object of the second intention, and / or the intent-driven operation of the first intention is included in the intent-driven operation of the second intention; The second intention system associates the intention keywords of the first intention, the intention-driven object and the intention-driven operation with the intention knowledge of the second intention.

27. The device according to claim 26, characterized in that: The transceiver unit is further configured to receive an intent knowledge update subscription request sent by the second intent system, wherein the intent knowledge update subscription request includes an identifier and an update type of the second intent system; The transceiver unit is further configured to send an intent knowledge update subscription response to the second intent system, wherein the intent knowledge update subscription response includes at least one of the following information: a subscription identifier and a subscription status; The intent knowledge update notification further includes the subscription identifier.

28. The device according to claim 26, characterized in that The transceiver unit is further configured to receive an intent knowledge update response sent by the second intent system.

29. The device according to any one of claims 26 to 28, characterized in that The update type further includes at least one of the following: deleting the intention knowledge of the first intention, modifying the intention knowledge of the first intention; If the update type is to add the intent knowledge of the first intent, the intent knowledge update notification also includes the intent-driven object and intent-driven operation of the first intent; If the update type is to modify the intention knowledge of the first intention, the intention knowledge notification also includes at least one of the following information: keywords of the first intention before modification, the intention-driven object of the first intention before modification, the intention-driven operation of the first intention before modification, keywords of the first intention after modification, the intention-driven object of the first intention after modification, and the intention-driven operation of the first intention after modification.

30. The device according to any one of claims 26 to 28, characterized in that: The transceiver unit is further configured to receive, when the intent knowledge of the second intent is updated, an intent knowledge capability query request sent by the second intent system, the intent knowledge capability query request including at least one of the following information: an identifier of the second intent system, an intent keyword of the updated second intent, an intent-driven object, and an intent-driven operation, wherein the device is one of the at least one third intent system; The processing unit is further configured to find intent knowledge of the first intent associated with at least one of an intent keyword, an intent-driven object, and an intent-driven operation of the updated second intent; The transceiver unit is also used to send an intent knowledge capability query response to the second intent system, and the intent knowledge capability query response includes at least one of the following information: the identifier of the second intent system, the identifier of the at least one third intent system, and the intent knowledge of the first intent.

31. A communication device, characterized in that: The communication device comprises a processor, a memory, and instructions stored in the memory and executable on the processor, wherein when the instructions are executed, the communication device executes the method according to any one of claims 1 to 10.

32. A communication device, characterized in that: The communication device comprises a processor, a memory, and instructions stored in the memory and executable on the processor, wherein when the instructions are executed, the communication device executes the method according to any one of claims 11 to 15.

33. A computer-readable storage medium comprising instructions, characterized in that: When the method according to any one of claims 1 to 15 is executed on a computer, the method is executed.

Images