WO2022099626A1 - 意图系统间意图知识的关联方法及装置、系统 - Google Patents

意图系统间意图知识的关联方法及装置、系统 Download PDF

Info

Publication number
WO2022099626A1
WO2022099626A1 PCT/CN2020/128754 CN2020128754W WO2022099626A1 WO 2022099626 A1 WO2022099626 A1 WO 2022099626A1 CN 2020128754 W CN2020128754 W CN 2020128754W WO 2022099626 A1 WO2022099626 A1 WO 2022099626A1
Authority
WO
WIPO (PCT)
Prior art keywords
intent
knowledge
driven
update
keyword
Prior art date
Application number
PCT/CN2020/128754
Other languages
English (en)
French (fr)
Inventor
巨敏
李贤明
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2020/128754 priority Critical patent/WO2022099626A1/zh
Priority to CN202080103879.6A priority patent/CN116113958A/zh
Priority to EP20961182.1A priority patent/EP4227822A4/en
Publication of WO2022099626A1 publication Critical patent/WO2022099626A1/zh
Priority to US18/313,546 priority patent/US20230281469A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2455—Query execution
    • G06F16/24568—Data stream processing; Continuous queries
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/542—Event management; Broadcasting; Multicasting; Notifications
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
    • G06N5/00—Computing arrangements using knowledge-based models
    • G06N5/02—Knowledge representation; Symbolic representation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14—Network analysis or design
    • H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/16—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using machine learning or artificial intelligence

Definitions

  • the present application relates to the technical field of network intelligence management, and in particular, to a method, device, and system for associating intent knowledge between intent systems.
  • the intent knowledge stored in the intent knowledge repository (knowledge repository) of the intent system has a one-to-one corresponding intent keyword (Intentkeyword) to identify the intent knowledge.
  • the intent knowledge includes an execution constraint (constraint), and a set of operations (intentOperations): intentOperations [executionConditon, operationType, operation].
  • the operationType of the intent knowledge base is an enumeration type, where a 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 base of the low-level intent system.
  • 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 intent knowledge of the low-level intent system.
  • the high-level intent system implements the premise of sub-intent delivery.
  • Figure 1 shows a schematic diagram of a hierarchically deployed multi-level intent system. After the high-level intent system receives an intent and issues a command, the operation objects (eg, network elements) corresponding to the intent are managed by different low-level intent systems. , the high-level intent system will decompose the intent and send the decomposed sub-intents to these low-level intent systems, and the low-level intent system will feed back the intent achievement to the high-level intent system.
  • the operation objects eg, network elements
  • the external system can update the intent knowledge in the intent knowledge base of the intent system, such as adding, modifying and deleting.
  • the intent systems at different levels are layered and divided into domains, and the intent systems implement domain autonomy, and external systems cannot perform intent knowledge management operations on the intent systems at different levels. Therefore, when the external system performs the intention knowledge update operation, it can only update the intention knowledge in the intention knowledge base of the current intention system, and cannot update the intention knowledge of the upper and lower level intention systems related to the current intention system. This will lead to inefficient delivery of intent system sub-intents after the intent knowledge is updated, or even invalid or missing intent knowledge.
  • Embodiments of the present application provide a method, device, and system for associating intent knowledge between intent systems, so as to realize the association of intent knowledge between intent systems when the intent knowledge is updated.
  • a method for associating intent knowledge between intent systems comprising: when the intent knowledge of the first intent of the first intent system is updated, the second intent system receives the information sent by the first intent system. an intent knowledge update notification, wherein the intent knowledge update notification includes an update type and an intent keyword of the first intent; and the second intent system updates the intent of the first intent according to the intent knowledge update notification
  • the intent knowledge of the first intent corresponding to the keyword is associated with the intent knowledge of the second intent in the second intent system, where the first intent is a sub-intent of the second intent.
  • the association of intent knowledge between intent systems can be implemented, so as to prevent the intent knowledge update of the first intent from causing the intent of the first intent in the second intent system Lack or failure of knowledge.
  • the method 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 the intent knowledge update to the first intent system a subscription request, the intent knowledge update subscription request includes the identification and update type of the second intent system; and the second intent system receives an intent knowledge update subscription response sent by the first intent system, the intent knowledge updates
  • the subscription response includes at least one of the following information: a subscription identifier and a subscription status; wherein the intent knowledge update notification further includes the subscription identifier.
  • the first intent system adds new intent knowledge, and can notify the second intent system in a subscription-notification manner.
  • the intent knowledge update notification further includes an identifier of the first intent system, and after the second intent system receives the intent knowledge update notification sent by the first intent system, the method It also includes: the second intent system sending an intent knowledge update response to the first intent system.
  • the first intent system adds new intent knowledge, and informs the second intent system through direct reporting.
  • the update type is adding intent knowledge of the first intent
  • the intent knowledge update notification further includes an intent-driven object and an intent-driven operation of the first intent
  • the first intent The two-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 intent system queries the second intent system for the intent knowledge of the second intent according to the intent-driven object and intent-driven operation of the first intent, wherein the intent of the first intent a drive object is contained within an intent-driven object of the second intent, and/or an intent-driven operation of the first intent is contained within an intent-driven operation of the second intent; and the second intent system converts the The intent keyword of the first intent, the intent-driven object, and the intent-driven operation are associated with intent knowledge of the second intent.
  • the update type is to delete the intent knowledge of the first intent
  • the second intent system updates the notification according to the intent knowledge, and updates the intent keyword corresponding to the first intent
  • the intent knowledge of the first intent is associated with the intent knowledge of the second intent in the second intent system, including: the second intent system, according to the intent keyword of the first intent, in the second intent
  • the intent system searches for the intent knowledge of the first intent corresponding to the intent keyword of the first intent; and the second intent system deletes the found intent knowledge of the first intent.
  • the update type is to modify the intent knowledge of the first intent
  • the intent knowledge update notification further includes at least one of the following information: keywords of the first intent before modification, The intent-driven object of the first intent before modification, the intent-driven operation of the first intent before modification, the keyword of the modified first intent, the intent-driven object of the modified first intent , the modified intent-driven operation of the first intent;
  • the second intent system updates the notification according to the intent knowledge, and compares the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the to associate the intent knowledge of the second intent in the second intent system, including at least one of the following operations: after the first intent system modifies the intent keywords of the first intent, the second intent system the intent keyword of the first intent, look up the intent knowledge of the first intent corresponding to the intent keyword of the first intent before the modification in the second intent system, and the second intent The intent system replaces the intent keyword of the modified first intent with the intent keyword of the first intent before the modification in the intent knowledge of the first intent; the first intent system modifies the intent
  • the method further includes: the second intent system drives an object and/or an intent-driven operation according to the intent of the first intent before the modification, in the second intent system Query the intent knowledge of the third intent, 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 object of the first intent before the modification
  • the intent-driven operation of an intent is included in the intent-driven operation of the third intent
  • the second intent system compares the intent-driven object and/or intent-driven operation of the first intent before the modification with the intent-driven operation of the third intent. Intention-knowledge disassociation of three intentions.
  • the method further includes: 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 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, an intent-driven object, and an intent-driven operation, wherein the first intent system is one of the intent systems in the at least one third intent system; the second intent system receives an intent knowledge capability query response that is intended to be sent by the at least one third system, and the intent knowledge capability query response includes at least one of the following Item information: the identifier of the second intent system, the identifier of the at least one third intent system, and at least one item associated with the updated intent keyword of the second intent, an intent-driven object, and an intent-driven operation The intent knowledge of the first intent; and the second intent system compares the intent knowledge of the first intent with the updated intent keyword of the second intent, an intent-driven object, and an intent-driven operation.
  • the update type is to modify the intent knowledge of the second intent
  • the second intent system compares the intent knowledge of the first intent with the updated intent keywords of the second intent , an intent-driven object, and an intent-driven operation to associate at least one of the following operations: after the second intent system modifies the intent keyword of the second intent, the second intent system modifies the The intent keyword of the second intent is associated with the intent keyword of the first intent; after the second intent system modifies the intent-driven object and/or intent-driven operation of the second intent, the The two-intent system associates the modified intent-driven object and/or intent-driven operation of the second intent with the intent-driven object and/or intent-driven operation of the first intent.
  • the method further includes: the second intent system querying the second intent system according to the intent-driven object and/or intent-driven operation of the second intent before modification Intent knowledge to a fourth intent in the at least one third intent system, wherein the intent-driven object of the second intent before the modification comprises an intent-driven object of the fourth intent, and/or the The intent-driven operation of the second intent before modification includes the intent-driven operation of the fourth intent; and the second intent system converts the intent-driven object and/or intent-driven operation of the second intent before the modification Actions are disassociated from intent knowledge of the fourth intent.
  • the method before the second intent system sends an intent knowledge capability query request to at least one third intent system, the method further includes: the second intent system according to the updated second intent system the intent-driven object of the intent, determining the at least one third intent system, wherein the intent-driven object of the first intent in the at least one third intent system is included in the updated second intent's Intent driven objects.
  • a method for associating intent knowledge among intent systems comprising: determining that the intent knowledge of the first intent of the first intent system is updated; and sending the first intent system to the second intent system an intent knowledge update notification, so that the second intent system updates the notification according to the intent knowledge, and the intent knowledge of the first intent corresponding to the intent keyword of the first intent and the second intent in the second intent system
  • the intent knowledge of the intent is associated, wherein the first intent is a sub-intent of the second intent, and the intent knowledge update notification includes an update type and an intent keyword of the first intent.
  • the method before the first intent system sends an intent knowledge update notification to the second intent system, the method further includes: the first intent system receiving the intent knowledge update sent by the second intent system a subscription request, the intent knowledge update subscription request including the identification and update type of the second intent system; and the first intent system sending an intent knowledge update subscription response to the second intent system, the intent knowledge update subscription
  • the response includes at least one of the following information: subscription identifier, subscription status; wherein, the intent knowledge update notification further includes the subscription identifier.
  • the method further includes: the first intent system receiving the intent knowledge sent by the second intent system Update response.
  • the update type includes at least one of the following: adding the intent knowledge of the first intent, deleting the intent knowledge of the first intent, and modifying the intent knowledge of the first intent; If the update type is to add the intent knowledge of the first intent, the intent knowledge update notification further includes an intent-driven object and an intent-driven operation of the first intent; if the update type is to modify the first intent The intent knowledge of the intent, the intent knowledge notification further includes at least one of the following information: the keyword of the first intent before modification, the intent-driven object of the first intent before modification, the first intent before modification The intent-driven operation of the intent, the modified keyword of the first intent, the modified intent-driven object of the first intent, and the modified intent-driven operation of the first intent.
  • the method further includes: the intent knowledge of the second intent is updated, the first intent system receives an intent knowledge capability query request sent by the second intent system, the intent The 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 the One of the at least one third intent system; the first intent system finds all the intents associated with at least one of the updated second intent's intent keyword, intent-driven object, and intent-driven operation; the intent knowledge of the first intent; and the first intent system sends an intent knowledge capability query response to the second intent system, the intent knowledge capability query response including at least one of the following information: Identification, identification of the at least one third intent system, intent knowledge of the first intent.
  • a communication apparatus for performing the first aspect or the method in any possible implementation of the first aspect.
  • the communication device may be the second-intent system in the first aspect or any possible implementation of the first aspect, or a module applied in the second-intent system, such as a chip or a chip system.
  • this communication device comprises the corresponding module, unit or means (means) that realizes the above-mentioned method, and this module, unit or means can be realized by hardware, software realization, or by hardware executing corresponding software realization.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • the communication device includes: a transceiver unit and a processing unit; wherein:
  • a transceiver unit configured to receive an intent knowledge update notification sent by the 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 the first intent knowledge update notification. an intent keyword of an intent; and a processing unit configured to update the notification according to the intent knowledge, and associate the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the second intent in the second intent system , where the first intent is a sub-intent of the second intent.
  • the transceiver unit is further configured to send an intent knowledge update subscription request to the first intent system, where the intent knowledge update subscription request includes the identifier and update type of the second intent system; and The unit is further configured to receive an 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: subscription identifier, subscription status; wherein the intent knowledge update notification further includes the subscription identifier.
  • the intent knowledge update notification further includes an identifier of the first intent system, and a transceiver unit is further configured to send an intent knowledge update response to the first intent system.
  • the update type is to add intent knowledge of the first intent
  • the intent knowledge update notification further includes an intent-driven object and an intent-driven operation of the first intent
  • the processing unit It is used to query the intent knowledge of the second intent in the second intent system according to the intent-driven object and intent-driven operation of the first intent, wherein the intent-driven object of the first intent is included in the 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
  • a processing unit further configured to convert the intent of the first intent A keyword, the intent-driven object, and the intent-driven operation are associated with intent knowledge of the second intent.
  • the update type is to delete the intent knowledge of the first intent
  • the processing unit is configured to, according to the intent keyword of the first intent, search the second intent system for a The intent knowledge of the first intent corresponding to the intent keyword of the first intent; and a processing unit, further configured to delete the found intent knowledge of the first intent.
  • the update type is to modify the intent knowledge of the first intent
  • the intent knowledge update notification further includes at least one of the following information: keywords of the first intent before modification, The intent-driven object of the first intent before modification, the intent-driven operation of the first intent before modification, the keyword of the modified first intent, the intent-driven object of the modified first intent , the modified intent-driven operation of the first intent; a processing unit, configured to perform at least one of the following operations: after the first intent system modifies the intent keyword of the first intent, The intent keyword of the first intent, searching for the intent knowledge of the first intent corresponding to the intent keyword of the first intent before the modification in the second intent system, and converting the modified all intent
  • the intent keyword of the first intent replaces the intent keyword of the first intent before the modification in the intent knowledge of the first intent; the first intent system modifies the intent-driven object of the first intent and/or after the intent-driven operation, according to the modified intent-driven object of the first intent and/or the intent-driven operation, the intent knowledge of the second intent is
  • the processing unit is further configured to query the second intent system for a third intent according to the intent-driven object and/or intent-driven operation of the first intent before the modification knowledge of the intent, wherein the intent-driven object of the first intent before the modification is contained within the intent-driven object of the third intent, and/or the intent-driven operation of the first intent before the modification It is included in the intent-driven operation of the third intent; the processing unit is further configured to separate the intent-driven object and/or intent-driven operation of the first intent before the modification from the intent knowledge of the third intent. association.
  • the transceiver unit is further configured to update the intent knowledge of the second intent, and send an intent knowledge capability query request to at least one third intent system, where the intent knowledge capability query request includes At least one piece of information: the identifier of the second intent system, the updated intent keyword of the second intent, an intent-driven object, and an intent-driven operation, wherein the first intent system is the at least one first intent system.
  • the transceiver unit is further configured to receive an intent knowledge capability query response that is intended to be sent by the at least one third system, where the intent knowledge capability query response includes at least one of the following information: the first The identifier of the second intent system, the identifier of the at least one third intent system, the intent of the first intent associated with at least one of the updated intent keyword of the second intent, an intent-driven object, and an intent-driven operation knowledge; and a processing unit, further configured to associate 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.
  • the update type is to modify the intent knowledge of the second intent
  • the processing unit is further configured to perform at least one of the following operations: the second intent system modifies the intent key of the second intent the modified intent keyword of the second intent is associated with the intent keyword of the first intent; or the second intent system modifies the intent-driven object and/or intent of the second intent After the driving operation, the modified intent-driven object and/or the intent-driven operation of the second intent is associated with the intent-driven object and/or the intent-driven operation of the first intent.
  • the processing unit is further configured to query the second intent system for the at least one first intent-driven object according to the intent-driven object and/or intent-driven operation of the second intent before modification.
  • the intent knowledge of the fourth intent in the three-intent system wherein the intent-driven object of the second intent before the modification includes the intent-driven object of the fourth intent, and/or the intent-driven object of the second intent before the modification
  • the intent-driven operation of the second intent includes the intent-driven operation of the fourth intent
  • a processing unit is further configured to compare the intent-driven object and/or intent-driven operation of the second intent before the modification with the fourth intent. Intent-knowledge disassociation.
  • the processing unit is further configured to determine the at least one third intent system according to the updated intent-driven object of the second intent, wherein the at least one third intent The intent-driven object of the first intent in the system is contained within the updated intent-driven object of the second intent.
  • the communication device includes: an input interface, an output interface and a processing circuit; wherein:
  • the input interface is used to receive an intent knowledge update notification sent by the 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 the first intent. an intent keyword of the intent; and a processing circuit configured to update the notification according to the intent knowledge, and associate the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the second intent in the second intent system , where the first intent is a sub-intent of the second intent.
  • the output interface is further configured to send an intent knowledge update subscription request to the first intent system, where the intent knowledge update subscription request includes the identifier and update type of the second intent system; and the input The interface is further configured to receive an 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: subscription identifier, subscription status; wherein the intent knowledge update notification further includes the subscription identifier.
  • the intent knowledge update notification further includes an identifier of the first intent system, an output interface, and is further configured to send an intent knowledge update response to the first intent system.
  • the update type is to add intent knowledge of the first intent
  • the intent knowledge update notification further includes an intent-driven object and an intent-driven operation of the first intent
  • a processing circuit It is used to query the intent knowledge of the second intent in the second intent system according to the intent-driven object and intent-driven operation of the first intent, wherein the intent-driven object of the first intent is included in the 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; and a processing circuit, further configured to convert the intent of the first intent A keyword, the intent-driven object, and the intent-driven operation are associated with intent knowledge of the second intent.
  • the update type is to delete the intent knowledge of the first intent
  • the processing circuit is configured to search the second intent system according to the intent keyword of the first intent to search for and match with the second intent system.
  • the intent knowledge of the first intent corresponding to the intent keyword of the first intent; and a processing circuit, further configured to delete the found intent knowledge of the first intent.
  • the processing circuit is further configured to query a third intent in the second intent system according to the intent-driven object and/or intent-driven operation of the first intent before the modification knowledge of the intent, wherein the intent-driven object of the first intent before the modification is contained within the intent-driven object of the third intent, and/or the intent-driven operation of the first intent before the modification It is included in the intent-driven operation of the third intent; the processing circuit is further configured to separate the intent-driven object and/or intent-driven operation of the first intent before the modification from the intent knowledge of the third intent. association.
  • the output interface is further configured to update the intent knowledge of the second intent, and send an intent knowledge capability query request to at least one third intent system, where the intent knowledge capability query request includes At least one piece of information: the identifier of the second intent system, the updated intent keyword of the second intent, an intent-driven object, and an intent-driven operation, wherein the first intent system is the at least one first intent system.
  • One of the intent systems in the three-intent systems an input interface, further configured to receive an intent knowledge capability query response intended to be sent by the at least one third system, where the intent knowledge capability query response includes at least one of the following information: the first The identifier of the second intent system, the identifier of the at least one third intent system, the intent of the first intent associated with at least one of the updated intent keyword of the second intent, an intent-driven object, and an intent-driven operation knowledge; and a processing circuit, further configured to associate the intent knowledge of the first intent with the updated intent keyword of the second intent, an intent-driven object, and an intent-driven operation.
  • the update type is to modify the intent knowledge of the second intent
  • the processing circuit is further configured to perform at least one of the following operations: the second intent system modifies the intent key of the second intent the modified intent keyword of the second intent is associated with the intent keyword of the first intent; or the second intent system modifies the intent-driven object and/or intent of the second intent After the driving operation, the modified intent-driven object and/or the intent-driven operation of the second intent is associated with the intent-driven object and/or the intent-driven operation of the first intent.
  • the processing circuit is further configured to query the second intention system to find the at least one first object according to the intention-driven object and/or the intention-driven operation of the second intention before modification.
  • the intent knowledge of the fourth intent in the three-intent system wherein the intent-driven object of the second intent before the modification includes the intent-driven object of the fourth intent, and/or the intent-driven object of the second intent before the modification
  • the intent-driven operation of the second intent includes the intent-driven operation of the fourth intent
  • a processing circuit is further configured to associate the intent-driven object and/or intent-driven operation of the second intent before the modification with the fourth intent-driven operation Intent-knowledge disassociation.
  • the processing circuit is further configured to determine the at least one third intent system according to the updated intent-driven object of the second intent, wherein the at least one third intent The intent-driven object of the first intent in the system is contained within the updated intent-driven object of the second intent.
  • the communication device further includes a memory coupled to the at least one processor for executing program instructions stored in the memory to cause the communication device to perform the above-mentioned first aspect or the first aspect method in any possible implementation of .
  • 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 invoke and execute program instructions stored in the memory to cause the communication device to perform the above-mentioned first aspect or any possible implementation of the first aspect. method.
  • the communication apparatus further includes a communication interface for the communication apparatus to communicate with other devices.
  • the communication interface is a transceiver, an input/output interface, a circuit, or the like.
  • the communication device includes: at least one processor and a communication interface for executing the method in the first aspect or any possible implementation of the first aspect, specifically including: the at least one processor
  • the communication device communicates with the outside using the communication interface; the at least one processor is configured to run a computer program, so that the communication device executes the method in the first aspect or any possible implementation of the first aspect.
  • the external may be an object other than the processor, or an object other than the communication device.
  • the communication device is a chip or a system of chips.
  • the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, etc. on the chip or the chip system.
  • the processor may also be embodied as processing circuitry or logic circuitry.
  • a communication apparatus for performing the second aspect or the method in any possible implementation of the second aspect.
  • the communication device may be the first-intent system in the second aspect or any possible implementation of the second aspect, or a module applied in the first-intent system, such as a chip or a chip system.
  • the communication device includes corresponding modules, units, or means for implementing the above method, and the modules, units, or means may be implemented by hardware, software, or by executing corresponding software in hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • the communication device includes: a processing unit and a transceiver unit; wherein:
  • a processing unit configured to determine that the intent knowledge of the first intent of the first intent system is updated; and a transceiver unit, configured to send an intent knowledge update notification to the second intent system, so that the second intent system updates the notification according to the intent knowledge , 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 intent system, where the first intent is the first intent A sub-intent of the second intent, the intent knowledge update notification includes an update type and an intent keyword of the first intent.
  • the transceiver unit is further configured to receive an intent knowledge update subscription request sent by the second intent system, where the intent knowledge update subscription request includes the identifier and update type of the second intent system; and The transceiver unit is further configured to send 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: subscription identifier, subscription status; wherein the intent knowledge update notification further includes the subscription identifier.
  • the transceiver unit is further configured to receive an intent knowledge update response sent by the second intent system.
  • the update type includes at least one of the following: adding the intent knowledge of the first intent, deleting the intent knowledge of the first intent, and modifying the intent knowledge of the first intent; If the update type is to add the intent knowledge of the first intent, the intent knowledge update notification further includes an intent-driven object and an intent-driven operation of the first intent; if the update type is to modify the first intent The intent knowledge of the intent, the intent knowledge notification further includes at least one of the following information: the keyword of the first intent before modification, the intent-driven object of the first intent before modification, the first intent before modification The intent-driven operation of the intent, the modified keyword of the first intent, the modified intent-driven object of the first intent, and the modified intent-driven operation of the first intent.
  • the transceiver unit is further configured to update the intent knowledge of the second intent, and receive an intent knowledge capability query request sent by the second intent system, where the intent knowledge capability query request includes the following At least one piece of information: the identifier of the second intent system, the updated intent keyword of the second intent, an intent-driven object, and an intent-driven operation, wherein the first intent system is the at least one third intent system One of the intent systems in the; processing unit, configured to find the intent knowledge of the first intent associated with at least one of the updated intent keywords, intent-driven objects, and intent-driven operations of the updated second intent and a transceiver unit, further configured to send an intent knowledge capability query response to the second intent system, where the intent knowledge capability query response includes at least one of the following information: an identifier of the second intent system, the at least one first The identification of the three-intent system, the intent knowledge of the first intent.
  • the communication device includes: an input interface, an output interface and a processing circuit; wherein:
  • a processing circuit for determining that the intent knowledge of the first intent of the first intent system is updated; and an output interface for sending an intent knowledge update notification to the second intent system, so that the second intent system updates the notification according to the intent knowledge , 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 intent system, where the first intent is the first intent A sub-intent of the second intent, the intent knowledge update notification includes an update type and an intent keyword of the first intent.
  • the input interface is further configured to receive an intent knowledge update subscription request sent by the second intent system, where the intent knowledge update subscription request includes the identifier and update type of the second intent system; and
  • the output interface is further configured to send 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: subscription identifier, subscription status; wherein the intent knowledge update notification further includes the subscription identifier.
  • the input interface is further configured to receive an intent knowledge update response sent by the second intent system.
  • the update type includes at least one of the following: adding the intent knowledge of the first intent, deleting the intent knowledge of the first intent, and modifying the intent knowledge of the first intent; If the update type is to add the intent knowledge of the first intent, the intent knowledge update notification further includes an intent-driven object and an intent-driven operation of the first intent; if the update type is to modify the first intent The intent knowledge of the intent, the intent knowledge notification further includes at least one of the following information: the keyword of the first intent before modification, the intent-driven object of the first intent before modification, the first intent before modification The intent-driven operation of the intent, the modified keyword of the first intent, the modified intent-driven object of the first intent, and the modified intent-driven operation of the first intent.
  • the input interface is further used for updating the intent knowledge of the second intent, and receiving an intent knowledge capability query request sent by the second intent system, where the intent knowledge capability query request includes the following At least one piece of information: the identifier of the second intent system, the updated intent keyword of the second intent, an intent-driven object, and an intent-driven operation, wherein the first intent system is the at least one third intent system One of the intent systems in the; processing circuit for finding the intent knowledge of the first intent associated with at least one of the updated intent keywords, intent-driven objects, and intent-driven operations of the updated second intent and an input interface, further configured to send an intent knowledge capability query response to the second intent system, where the intent knowledge capability query response includes at least one of the following information: an identifier of the second intent system, the at least one first The identification of the three-intent system, the intent knowledge of the first intent.
  • the communication device further includes a memory coupled to the at least one processor for executing program instructions stored in the memory to cause the communication device to perform the above-mentioned second aspect or the second aspect method in any possible implementation of .
  • 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 invoke and execute program instructions stored in the memory to cause the communication device to perform the above-mentioned second aspect or any possible implementation of the second aspect. method.
  • the communication apparatus further includes a communication interface for the communication apparatus to communicate with other devices.
  • the communication interface is a transceiver, an input/output interface, a circuit, or the like.
  • the communication device includes: at least one processor and a communication interface for executing the method in the second aspect or any possible implementation of the second aspect, specifically including: the at least one processor
  • the communication device communicates with the outside using the communication interface; the at least one processor is used for running a computer program, so that the communication device executes the method in the second aspect or any possible implementation of the second aspect.
  • the external may be an object other than the processor, or an object other than the communication device.
  • the communication device is a chip or a system of chips.
  • the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, etc. on the chip or the chip system.
  • the processor may also be embodied as processing circuitry or logic circuitry.
  • a communication system including the communication apparatus according to the third aspect or any one of the implementations of the third aspect, and the communication apparatus according to the fourth aspect.
  • a computer-readable storage medium is provided, and instructions are stored in the computer-readable storage medium, which, when executed on a computer, cause the computer to perform the methods described in the above aspects.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods of the above aspects.
  • a chip is provided, the chip is coupled with a memory, and implements the communication method in the first aspect or any one of the first aspects of the embodiments of the present application.
  • a chip is provided, the chip is coupled with a memory, and implements the communication method in the second aspect or any one of the second aspects of the embodiments of the present application.
  • Coupled in the embodiments of the present application means that two components are directly or indirectly combined with each other.
  • Figure 1 is a schematic diagram of a multi-level intent system for hierarchical deployment
  • Fig. 2 is a schematic diagram of IDM
  • Fig. 3 is the schematic diagram of the intention classification of IDMS definition
  • Fig. 4 is a schematic diagram of a knowledge management function module
  • FIG. 5 is a schematic diagram of an ENI architecture based on an intent policy
  • FIG. 6 is a schematic diagram of the intent knowledge management architecture in the ENI fusion system based on intent policy
  • FIG. 7 is a schematic diagram of an intent knowledge management architecture in an intent policy-based ENI fusion system provided by an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of a method for associating intent knowledge between intent systems according to an embodiment of the present application
  • FIG. 9 is a schematic flowchart of yet another method for associating intent knowledge between intent systems according to an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of yet another method for associating intent knowledge between intent systems according to an embodiment of the present application
  • 11 is a schematic flowchart of another method for associating intent knowledge between intent systems according to an embodiment of the present application.
  • FIG. 12 is a schematic flowchart of yet another method for associating intent knowledge between intent systems according to an embodiment of the present application
  • FIG. 13 is a schematic flowchart of yet another method for associating intent knowledge between intent systems according to an embodiment of the present application
  • FIG. 14 is a schematic flowchart of yet another method for associating intent knowledge between intent systems according to an embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 16 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • FIG. 17 is a schematic structural diagram of still another communication apparatus provided by an embodiment of the present application.
  • 3GPP SA5 launched the research on intent-driven management (IDM), which uses a service-oriented interface to deliver intent.
  • IDM intent-driven management
  • the intent-driven management service consumer sends the intent to the intent-driven management service provider (IDM service producer) by calling the intent-driven management service (IDMS) interface.
  • IDMS intent-driven management service
  • the IDM service provider translates the intent into a specific execution strategy and sends it to the network infrastructure.
  • the network infrastructure may be physical and/or virtual.
  • the intent model is used to model the information that should be included in the intent expression (intentExpression), at least including "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:
  • FIG. 3 is a schematic diagram of the intent hierarchy defined by IDMS.
  • IDMS provides the communication service customer (CSC), communication service provider (communication service provider), end-to-end (end-to-end) intent expression. , CSP) and network operator (network operator, NOP) three levels.
  • CSC includes end users, small and medium-sized enterprises, large enterprises, vertical industries, and other CSPs. in:
  • intent of the communication service consumer (intent-CSC): It only expresses the management requirements of the service level, and does not involve the implementation details of the service and network.
  • intent of the communication service provider (intent-CSP): It only expresses the management requirements at the network level, and does not involve the professional knowledge of network operation.
  • tent-NOP Network operator's intent
  • Experiential networked intelligence is a perceptual network management system architecture defined by an industry normative working group, which uses artificial intelligence and context-awareness to optimize and adjust network operations. It includes input processing and normalization function module (data ingestion&normalization FB), output generation and denormalization function module (output generation&denormalisation FB), knowledge management function module (knowledge management FB), context awareness function module (context awareness FB), cognitive management There are eight functional modules: cognition management FB, situational awareness FB, policy management FB and model driven engineering FB. This application focuses on the knowledge management FB.
  • data ingestion&normalization FB data ingestion&normalization FB
  • output generation and denormalization function module output generation&denormalisation FB
  • knowledge management function module knowledge management function module
  • context awareness function module context awareness function module
  • cognitive management There are eight functional modules: cognition management FB, situational awareness FB, policy management FB and model driven engineering FB. This application focuses on the knowledge management FB.
  • the knowledge management FB is used to manage at least four kinds of data and knowledge repository (data and knowledge repository), namely database (data repository), knowledge repository (knowledge repository), model repository ( 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 context awareness FB, cognition management FB, situation awareness FB, model-driven engineering FB, and policy management FB.
  • the schematic diagram of the ENI architecture based on the intent policy proposes the ENI architecture based on the intent policy, promotes the standardization of the intent-driven network architecture, and enhances the original ENI architecture:
  • Added intent translation function module used to process intent policy, including intent policy intent translation, intent guarantee and life cycle management.
  • Enhance knowledge management FB Store the intent knowledge model and intent knowledge data in the model repository and knowledge repository respectively.
  • Figure 6 is a schematic diagram of the intent knowledge management architecture in the intent policy-based ENI fusion system.
  • the current intent system or the low-level intent system has the intent knowledge management function and interface, and supports external systems such as user (user)/application ( application, APP) / operation support system (operation support system, OSS) / operation and maintenance support system-like system (business support system-like, BSS-like) functional entities (Functionality) through the following interfaces: E 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 intent system's knowledge repository.
  • the intent knowledge stored in the knowledge repository of the intent system has a one-to-one corresponding intent keyword to identify the intent knowledge.
  • This intent knowledge includes execution constraints, and intentOperations[executionConditon, operationType, operation].
  • the operationType of the intent knowledge base is an enumeration type, where a 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 this sub-intent exists in the intent knowledge base of the low-level intent system.
  • the intent knowledge base of the high-level intent system will store the intent keywords, IDO and IDA of the intent knowledge of the low-level intent system, which is the premise for the high-level intent system to deliver sub-intents.
  • Figure 1 shows a schematic diagram of a hierarchically deployed multi-level intent system. After the high-level intent system receives an intent and issues a command, the operation objects (eg, network elements) corresponding to the intent are managed by different low-level intent systems. , the high-level intent system will decompose the intent and send the decomposed sub-intents to these low-level intent systems, and the low-level intent system will feed back the intent achievement to the high-level intent system.
  • the operation objects eg, network elements
  • the intent systems at different levels are layered and divided into domains, and the intent systems implement domain autonomy, and external systems cannot perform intent knowledge management operations on the intent systems at different levels. Therefore, when the external system performs the intention knowledge update operation, it can only update the intention knowledge in the knowledge repository of the current intention system, and cannot update the intention knowledge of the upper and lower level intention systems related to the current intention system. This will cause the updated intent knowledge to affect the delivery of sub-intents, because the intent knowledge in the knowledge repository of the upper and lower intent systems is not associated and updated after the intent knowledge is updated, so the intent system after the intent knowledge is updated Sub-intent delivery is inefficient, and even intention knowledge is invalid or missing. Specifically,
  • the low-level intent system adds intent knowledge, but this intent does not exist in the high-level intent system, and the high-level intent system cannot decompose and issue the intent as a sub-intent in the high-level.
  • the new intent knowledge of the low-level intent system means that the intent does not exist in the knowledge base of the low-level intent system, that is, there is no Intentkeyword, IDA, IDO, constraint and intentOperations.
  • the newly added intent knowledge includes the newly added Intentkeyword, IDA and IDO and corresponding constraints and intentOperations. If the intent keyword already exists in the knowledge base, only adding constraints and intentOperations does not belong to the scope of the new intent knowledge of the low-level intent system here.
  • the low-level intent system modifies the intent knowledge.
  • the intent can also be used as a sub-intent in the high-level, but it will lead to a bias in the decomposition of the intent in the high-level.
  • the low-level intent system modifies the intent knowledge means that the intent already exists in the low-level intent system knowledge base, including Intentkeyword, IDA, IDO, constraint and intentOperations, but Intentkeyword/IDA/IDO is modified.
  • the original IntentDrivenObjectProperties is JinQiao
  • the modified IntentDrivenObjectProperties is MinHang.
  • the low-level intent system deletes the intent knowledge, and the intent is still used as a sub-intent in the high-level, resulting in failure to deliver the high-level neutron intent.
  • the low-level intent system deletes the intent knowledge means that the intent exists in the low-level intent system knowledge base, that is, there are Intentkeyword, IDA, IDO, constraint and intentOperations, deleting the intent knowledge means deleting the Intentkeyword, IDA, IDO, All knowledge of constraints and intentOperations.
  • the high-level intent system adds or modifies intent knowledge, it can only exist in the high-level knowledge repository as intent knowledge, and cannot be associated with the intent knowledge of the low-level intent system, resulting in the inability to implement intent decomposition and delivery.
  • the present application provides a method, device, and system for associating intent knowledge between intent systems.
  • the second intent system receives an 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 compares the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the intent keyword in the second intent system according to the intent knowledge update notification.
  • the intent knowledge of the second intent is associated, where the first intent is a sub-intent of the second intent.
  • the association of intent knowledge between intent systems can be realized, so as to avoid the update of the intent knowledge of the first intent resulting in the lack of the intent knowledge of the first intent in the second intent system or invalid.
  • ⁇ knowledge management FB manage all knowledge within the scope of ENI, and complete 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 in this application.
  • Data ingestion and normalization FB operations such as acquisition and normalization of input data from external systems, in this application, the intent knowledge update notification and intent knowledge query operations between intent systems are enhanced.
  • ⁇ output generation and demoralization FB It is responsible for converting the internal commands of the system 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.
  • FIG. 7 a schematic diagram of the intent knowledge management architecture in the intent policy-based ENI fusion system provided by the embodiment of the present application, the ENI system interface of the intent policy is newly added to support knowledge between multi-level intent systems Management external interface E eni-eni-kno .
  • the intent policy-based ENI fusion system 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 element management system EMS of the network equipment manufacturer, or Deployed on the network element NE.
  • the network elements that deploy the intent-based ENI fusion system support the query, update and storage functions of intent knowledge, and support the notification and query functions of updated intent knowledge among multi-level network elements.
  • a schematic flowchart 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:
  • the first intent system determines that the intent knowledge of its first intent is updated.
  • the first intent system may be a low-level intent system
  • the second intent system may be a high-level intent system.
  • the first-intent system may be CSP, and the second-intent system may be CSC; or the first-intent system may be CSC, and the second-intent system may be NOP.
  • An external system can update the intent knowledge of the first intent of the first intent system.
  • the intent knowledge of the first intent of the first intent system is updated, which may be that the first intent system adds, modifies, or deletes the intent knowledge of the first intent.
  • the intent knowledge of the first intent is the intent knowledge of any intent that already exists or is about to be stored in the first intent system.
  • the first intent system sends an intent knowledge update notification to the second intent system, where the intent knowledge update notification includes the update type and intent keywords of the first intent.
  • the second intent system receives the intent knowledge update notification sent by the first intent system.
  • the update of the intent knowledge of the first intent system may cause the sub-intent knowledge of the second intent system to be missing or invalid.
  • the second intent system cannot perform sub-intent decomposition and distribution, resulting in insufficient use of intent knowledge; modifying the intent knowledge for the first intent system, the second intent system can perform sub-intent decomposition and distribution , but there may be a decomposition deviation, which requires multiple intent negotiation, resulting in low efficiency; deleting the intent knowledge from the first intent system, the second intent system can perform sub-intent decomposition and delivery, but the first intent system cannot implement the sub-intent.
  • the first intent system when it determines that its intent knowledge of the first intent is updated, it sends an intent knowledge update notification to the second intent system to notify the second intent system: the intent knowledge of the first intent system of the first intent An update has occurred.
  • the intent knowledge update notification includes the update type and the intent keyword of the first intent.
  • the intent knowledge update notification may further include the IDO and IDA of the first intent; if it is to modify at least one of the intent keywords/IDO/IDA of the first intent, Then, the intent knowledge update notification may further include at least one of the intent keyword of the first intent before modification and the intent keyword/IDO/IDA of the modified 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, where the first intent is A sub-intent of the second intent.
  • the second intent system cannot use the first intent as a child of the second intent system. Intentions are decomposed and issued. Therefore, when the first intent system adds the intent knowledge of the first intent, it is necessary to associate the newly added intent knowledge of the first intent with the intent knowledge of the second intent in the second intent system.
  • the first intent system modifies the intent knowledge of the first intent
  • the first intent can also be used as a sub-intent in the second intent system, but it will lead to a deviation in the intent decomposition in the second intent system. Therefore, when the first intent system modifies the intent knowledge of the first intent, it is necessary to re-associate with the intent knowledge of the second intent in the second intent system according to the modified intent knowledge of the first intent.
  • the first intent system deletes the intent knowledge of the first intent, the first intent is still used as a sub-intent in the second intent system, resulting in failure to deliver the sub-intent in the second intent system. Therefore, when the first intent system deletes the intent knowledge of the first intent, the intent knowledge of the first intent needs to be disassociated from the intent knowledge of the second intent in the second intent system.
  • the second intent system can prevent the update of the intent knowledge of the first intent from causing the second intent Absence or failure of intent knowledge of the first intent in the system.
  • the intent knowledge of the second intent in the second intent system is updated, and the second intent system sends an intent knowledge capability query request to at least one third intent system, where 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 system.
  • the first intent system receives the intent knowledge capability query request sent by the second intent system.
  • the external system can also update the intent knowledge of the second intent in the second intent system.
  • the external system updates the intent knowledge of the intent in the second intent system independently of updating the intent knowledge of the intent in the first intent system.
  • the intention knowledge of the second intention of the second intention system is updated, which may be that the second intention system adds or modifies the intention knowledge of the second intention.
  • the intent knowledge of the second intent is the intent knowledge of any intent that already exists or is about to be stored in the second intent system.
  • the second intent system adds or modifies the intent knowledge of the second intent, it can only exist in the knowledge repository of the second intent system as intent knowledge, and cannot be associated with the intent knowledge of the first intent system, resulting in the inability to Realize intent decomposition and delivery.
  • the second intent system when the second intent system updates the intent knowledge of the second intent, the second intent system sends an intent knowledge capability query request to at least one third intent system to request to query at least one third intent system related to the updated intent.
  • the intent knowledge of the second intent is associated with the intent knowledge of the first intent.
  • the first intent system finds the intent knowledge of the first intent associated with at least one of the updated intent keywords, intent-driven objects, and intent-driven operations of the second intent.
  • the first intent system searches for and updates the intent key of the second intent according to at least one of the updated intent keyword, intent-driven object, and intent-driven operation carried in the received intent knowledge capability query request.
  • the intent knowledge of the first intent associated with at least one of a word, an intent-driven object, and an intent-driven action.
  • the first intent system sends an intent knowledge capability query response to the second intent system, where the intent knowledge capability query response includes at least one of the following information: an identifier of the second intent system, an identifier of at least one third intent system, at least one third intent system Intention knowledge of the first intent in the intent system.
  • the second intent system receives at least one intent knowledge capability query response that is intended to be sent by the third system.
  • the first intent system feeds back the queried intent knowledge of the associated first intent to the second intent system.
  • 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.
  • the above-mentioned intent knowledge capability query request includes the Intentkeyword, IDA and IDO of the newly added second intent; the first intent system according to the second intent added in the second intent system Intentkeyword, IDA and IDO, query the relevant first intent intent knowledge in the first intent system; the second intent system compares the first intent intent knowledge with the newly added second intent intentkeyword, at least one of IDA and IDO one to associate.
  • the above-mentioned intent knowledge capability query request includes the modified Intentkeyword of the second intent; Intentkeyword; Second Intent
  • the system associates the modified Intentkeyword of the second intent with the Intentkeyword of the first intent.
  • the above intent knowledge capability query request includes the modified IDO/IDA of the second intent; the first intent system queries the IDO/IDA of the second intent according to the modified IDO/IDA of the second intent.
  • the intent knowledge of the second intent can be avoided
  • the update cannot be associated with the intent knowledge of the first intent in the second intent system, and cannot implement intent decomposition and delivery.
  • the association of intent knowledge between intent systems avoids that the update of the intent knowledge of the first intent causes the loss or invalidation of the intent knowledge of the first intent in the second intent system, or that the update of the intent knowledge of the second intent cannot be compared with the first intent knowledge in the second intent system.
  • the intent knowledge of an intent is correlated, and the intent decomposition and distribution cannot be realized.
  • FIGS 9 to 12 below correspond to the scenarios in which the low-level intent system updates the intent knowledge and informs the high-level intent system knowledge base.
  • FIG. 9 it is a schematic flowchart of yet another method for associating intent knowledge between intent systems according to an embodiment of the present application.
  • the low-level intent system adds intent knowledge, and informs the high-level intent system through subscription-notification.
  • the method may include the following steps:
  • 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, filter (that is, the update type ) is the filter constraint for subscription notifications, including [add (add), modify (modify), delete (delete)].
  • Step 203 the data ingestion and normalization FB of the low-level intent system performs format conversion on the received message and sends updateKnowledgeSubscription to the knowledge management FB.
  • step 204 the knowledge management FB of the low-level intent system starts a subscription according to updateKnowledgeSubscription and assigns a subscription identifier (SubscriptionID).
  • the knowledge management FB of the low-level intent system sends an intent knowledge update subscription response updateKnowledgeSubscription Response(SubscriptionID, status) to the high-level intent system, carrying the SubscriptionID and status.
  • SubscriptionID is the subscription identifier of the low-level intent system
  • status is the status of whether the subscription is successfully started (referred to as subscription status).
  • the external system (user/APP/OSS-/BSS-like) adds intent knowledge to the low-level intent system. It carries the update type (new addition), intent keywords, and intent knowledge.
  • 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 low-level intent system
  • SubscriptionID is the low-level intent system
  • the subscription identifier of , 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.
  • 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 the sub-intent knowledge as a sub-intent and its own intent knowledge.
  • the high-level intent system queries the high-level intent system to obtain the intent knowledge of the second intent (the second intent is the high-level intent) according to the IDO and IDA in the newly added intent knowledge (first intent knowledge).
  • system intent where the IDO of the first intent is contained within the IDO of the second intent, and/or the IDA of the first intent is contained in the IDA of the second intent, i.e. the first intent is included in the high-level intent system as Sub-intent forms exist.
  • the high-level intent system associates the intentkeyword, IDO and IDA of the first intent with the intent knowledge of the second intent.
  • the low-level intent system can notify the high-level intent system after adding intent knowledge, so that the newly added intent knowledge can exist in the knowledge repository of the high-level intent system as a sub-intent, which can enhance the high-level intent knowledge.
  • -level intent system's intent decomposition delivery capability can notify the high-level intent system after adding intent knowledge, so that the newly added intent knowledge can exist in the knowledge repository of the high-level intent system as a sub-intent, which can enhance the high-level intent knowledge.
  • An intent knowledge update subscription operation is added on the interface between the fusion system and the intent system. After the low-level intent system adds intent knowledge, the intent knowledge update notification feeds back the newly added intent knowledge.
  • the sub-intent knowledge association function is newly added in the fusion system, which associates the new intention knowledge of the low-level intention system with the intention knowledge of the high-level intention system as a sub-intent.
  • FIG. 10 it is a schematic flowchart of another method for associating intent knowledge between intent systems according to an embodiment of the present application.
  • the low-level intent system modifies/deletes intent knowledge, and informs the high-level intent system knowledge base through subscription-notification.
  • the method may include the following steps:
  • Steps 301 to 307 refer to steps S201 to S207 of the embodiment shown in FIG. 9 .
  • the external system instructs the low-level intent system to update the intent knowledge. It carries the update type (modification/deletion), intent keywords, and intent knowledge.
  • 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 allocated by the low-level intent system , delete is the intent knowledge deleted by the low-level intent system, and intentkeyword represents the intent knowledge deleted by the low-level intent system.
  • SubscriptionID is the subscription identifier allocated by the low-level intent system
  • delete is the intent knowledge deleted by the low-level intent system
  • intentkeyword represents the intent knowledge deleted by the low-level intent system.
  • step S316 the high-level intent system deletes the intent knowledge deleted from the low-level intent system in the knowledge repository.
  • the high-level intent system searches the high-level intent system for the intent knowledge of the first intent corresponding to the intent keyword according to the intent keyword of the intent knowledge (the intent knowledge of the first intent) deleted in the low-level intent system.
  • the high-level intent system removes the found intent knowledge of the first intent.
  • 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 low-level intent system to change intent knowledge Identification, if it is to modify the intent keyword, intentkeywordbefore is the intent intentkeyword before the change, intentkeywordafter is the intentkeyword after the change; if it is to modify the IDO/IDA, the intent knowledge update notification includes the intent keyword, intentkeywordbefore is the IDO/ before the change IDA, intentkeywordafter is the changed IDO/IDA.
  • step S320 the high-level intention system changes the changed intention knowledge in the low-level intention system into the knowledge repository, and associates the sub-intent knowledge with its own intention knowledge.
  • 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 the intent keywords in the intent knowledge of the first intent , one or more of IDO, IDA. Therefore, the high-level intent system performs at least one of the following actions depending on the specific modification:
  • the low-level intent system modifies the intent keywords of the original intent knowledge, and 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, and the high-level intent system is based on the modification.
  • the intent keyword of the previous first intent look up the intent knowledge of the first intent corresponding to the intent keyword of the first intent before the modification in the intent knowledge base of the high-level intent system, and the first intent is in the high-level intent knowledge base.
  • the level intent system exists as a sub-intent.
  • the high-level intent system replaces the intent keyword before the modification in the intent knowledge of the first intent with the modified intent keyword of the first intent;
  • 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 modified first intent
  • the high-level intent system finds the intent knowledge of the second intent of the high-level intent system in the intent knowledge base of the high-level intent system according to the modified IDO/IDA of the first intent, and the modified first intent
  • the IDO of the second intent is included in the IDO of the second intent, and/or the modified IDA of the first intent is included 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 modified IDO/IDA of the first intent with the intent knowledge of the second intent.
  • the IntentDrivenObjectProperties in the IDO before the modification of the first intent is Lujiazui
  • the IntentDrivenObjectProperties in the IDO after the modification of the first intent is Xujiahui
  • the IntentDrivenObjectProperties in the IDO of the second intent is Xuhui, that is, the IDO of the modified first intent Included in the IDO of the second intent, associate the modified IDO of the first intent with the intent knowledge of the second intent.
  • the high-level intent system queries the high-level intent system for the intent knowledge of the third intent according to the IDO/IDA of the first intent before modification, wherein the IDO of the first intent before modification is included in the third intent.
  • the high-level intent system disassociates the IDO/IDA of the first intent before modification with the intent knowledge of the third intent. For example, in the above example, the IntentDrivenObjectProperties in the IDO of the third intent is Pudong, the IDO before the modification of the first intent is included in the IDO of the third intent, then the IDO before the modification of the first intent and the IDO of the third intent are combined. Intent knowledge disassociation.
  • the low-level intent system can notify the high-level intent system after modifying/deleting intent knowledge. Therefore, the modified intent knowledge is also modified and associated with sub-intents in the knowledge repository of the high-level intent system, avoiding the failure of sub-intent knowledge or the low efficiency of intent decomposition when the intent is decomposed and issued in the high-level intent system; The deleted intent knowledge is also deleted in the knowledge repository of the high-level intent system to avoid the failure of intent delivery when the intent of the high-level intent system is decomposed.
  • An intent knowledge update subscription operation is added on the interface between the fusion system and the fusion system. After the low-level intent system modifies/deletes the intent knowledge, the intent knowledge update notification feeds back the modified/deleted intent knowledge.
  • the sub-intent knowledge modification, deletion and association functions are newly added in the fusion system. Modification, disassociation and re-association of intention knowledge of high-level intention system before and after modification of intention knowledge modified by low-level intention system; high-level intention system intention after deletion of intention knowledge deleted by low-level intention system Deletion and disassociation of knowledge.
  • FIG. 11 it is a schematic flowchart of yet another method for associating intent knowledge between intent systems according to an embodiment of the present application.
  • the low-level intent system adds new intent knowledge, and informs the high-level intent system knowledge base through direct reporting.
  • the method may include the following steps:
  • the external system (user/APP/OSS-/BSS-like) adds intent knowledge to the low-level intent system. It carries the update type (new addition), intent keywords, and intent knowledge.
  • 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 the sub-intent knowledge with its own intent knowledge as a sub-intent.
  • step S216 in the embodiment shown in FIG. 9 .
  • the high-level intent system sends an intent knowledge reporting response updateKnowledgeReport Response(status) (also called an intent knowledge update response) to the low-level intent system, where status indicates whether the knowledge repository of the high-level intent system has been carried out add operation.
  • updateKnowledgeReport Response also called an intent knowledge update response
  • the low-level intent system can directly report the new intent knowledge to the high-level intent system, so that the newly added intent knowledge can exist as a sub-intent in the knowledge repository of the high-level intent system, which can enhance the The intent decomposition and delivery capability of the high-level intent system.
  • a new intent knowledge update reporting operation is added on the interface between the fusion system and the fusion system. After the low-level intent system adds intent knowledge, the newly added intent knowledge is directly reported to the high-level intent system, without the need for the high-level intent system in advance. Send subscription notifications.
  • the sub-intent knowledge association function is added in the fusion system, and the new intention knowledge of the low-level intention system is associated with the intention knowledge of the high-level intention system as a sub-intent.
  • FIG. 12 it is a schematic flowchart of yet another method for associating intent knowledge between intent systems according to an embodiment of the present application.
  • the low-level intent system modifies/deletes the intent knowledge, and informs the high-level intent system knowledge base through direct reporting.
  • the method may include the following steps:
  • the external system instructs the low-level intent system to update the intent knowledge. It carries the update type (modification/deletion), intent keywords, and intent knowledge.
  • Steps S506-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, and delete is The low-level intent system deletes the intent knowledge, and the intentkeyword represents the intent knowledge deleted by the low-level intent system.
  • step S509 the high-level intent system deletes the intent knowledge deleted in the low-level intent system from the knowledge repository.
  • step S316 in the embodiment shown in FIG. 10 .
  • 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 performed a delete operation.
  • Steps S513 to S515 the knowledge management FB of the low-level intent system sends the knowledge management FB of the high-level intent system to update the intent knowledge and report updateKnowledgeReport(producerReference, modify, intentkeywordbefore, intentkeywordafter), where modify is the low-level intent system to change the intent knowledge Identity, intentkeywordbefore is the intent before the change intentkeyword, IDO and IDA, intentkeywordafter is the intent after the change intentkeyword, IDO and IDA.
  • step S516 the high-level intention system changes the changed intention knowledge in the low-level intention system into the knowledge repository, and associates the sub-intent knowledge with its own intention knowledge.
  • step S320 in the embodiment shown in FIG. 10 .
  • 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 undergone a modify operation.
  • the low-level intent system can directly report the intent knowledge to the high-level intent system after modifying/deleting the intent knowledge. Therefore, the modified intent knowledge is also modified and associated with sub-intents in the knowledge repository of the high-level intent system, avoiding the failure of sub-intent knowledge or the low efficiency of intent decomposition when the intent is decomposed and issued in the high-level intent system; The deleted intent knowledge is also deleted in the knowledge repository of the high-level intent system to avoid the failure of intent delivery when the intent of the high-level intent system is decomposed.
  • the interface between the fusion system and the fusion system has added an intent knowledge update reporting operation. After the low-level intent system modifies/deletes the intent knowledge, it is directly reported to the high-level intent system.
  • the high-level intent system does not need to send a subscription notification in advance.
  • the sub-intent knowledge modification, deletion and association functions are newly added in the fusion system. Modification, disassociation and re-association of intention knowledge of high-level intention system before and after modification of intention knowledge modified by low-level intention system; high-level intention system intention after deletion of intention knowledge deleted by low-level intention system Deletion and disassociation of knowledge.
  • FIG. 13 and FIG. 14 below correspond to the scenarios in which the high-level intent system updates the intent knowledge and queries the knowledge base of the low-level intent system.
  • FIG. 13 it is a schematic flowchart of yet another method for associating intent knowledge between intent systems according to an embodiment of the present application.
  • the high-level intent system adds intent knowledge, and queries all low-level intent system knowledge bases.
  • the method may include the following steps:
  • steps S601-S605 the external system (user/APP/OSS-/BSS-like) instructs the high-level intent system to add/modify intent knowledge.
  • the high-level intent system sends an intent knowledge capability query request queryKnowledgeCapacity(consumerReference, Intentkeyword, IDO, IDA) to all low-level intent systems below it (referred to as the third intent system).
  • queryKnowledgeCapacity consistumerReference, Intentkeyword, IDO, IDA
  • Intentkeyword, IDO, and IDA are intent knowledge added/modified in step S603 according to the content of step S601.
  • Step S608 the knowledge management module of each low-level intent system queries the related/associated intent knowledge RelatedIntentknowledge according to 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.
  • the high-level intent system sends an intent knowledge capability query response queryKnowledgeCapacity Response(consumerReference, Intentkeyword, RelatedInten--tknowledge) to the low-level intent system.
  • Intentkeyword is high-level intent system knowledge
  • RelatedIntentknowledge is low-level intent system knowledge.
  • step S612 the high-level intent system updates the RelatedIntentknowledge into the knowledge repository, and associates the sub-intent knowledge with its own intent knowledge.
  • the above-mentioned intent knowledge capability query request includes the newly added Intentkeyword, IDA and IDO of the second intent; the low-level intent system uses the newly added second intent in the high-level intent system The Intentkeyword of the second intent, IDA and IDO, query the relevant intent knowledge of the first intent in the low-level intent system; the high-level intent system combines the intent knowledge of the first intent with the newly added Intentkeyword of the second intent, IDA Associate with at least one item in IDO.
  • the above-mentioned intent knowledge capability query request includes the modified Intentkeyword of the second intent; the low-level intent system queries the first intent according to the modified Intentkeyword of the second intent Intentkeyword of the intent; the high-level intent system associates the modified Intentkeyword of the second intent with the Intentkeyword of the first intent.
  • the above-mentioned intent knowledge capability query request includes the modified IDO/IDA of the second intent; the low-level intent system queries according to the modified IDO/IDA of the second intent To the IDO/IDA of the first intent; the high-level intent system associates the modified IDO/IDA of the second intent with the IDO/IDA of the first intent.
  • the high-level intent system adds/modifies the intent knowledge and then queries the related intent knowledge of the low-level intent system, 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.
  • An intent knowledge capability query operation is added on the interface between the fusion system and the fusion system. After the high-level intent system adds intent knowledge, this operation is used to query the intent knowledge of the low-level intent system.
  • the sub-intent knowledge association function is added in the fusion system, and the intent knowledge of the low-level intent system obtained by the query is associated with the new intent knowledge of the high-level intent system as a sub-intent.
  • FIG. 14 it is a schematic flowchart of yet another method for associating intent knowledge between intent systems according to an embodiment of the present application.
  • the high-level intent system adds intent knowledge, and queries part of the low-level intent system knowledge base (it needs to decide which low-level intent system knowledge base to query).
  • the high-level intent system needs to determine which low-level intent systems to query based on sub-intent knowledge and determine the list.
  • the sub-intent knowledge in the high-level intention system includes Intentkeyword, IDO and IDA, and the general form of IDO and IDA is as follows, including the "action" and "object” of the intention function:
  • the low-level intent system is filtered according to the IDO of the new intent knowledge added by the high-level intent system and the IDO of the existing sub-intent knowledge.
  • the methods and steps of the list list of the low-level intent system are as follows:
  • the high-level intent system searches IntentDrivenObjectName2 and IntentDrivenObjectProperties2 of the existing sub-intent knowledge according to IntentDrivenObjectName1 and IntentDrivenObjectProperties1 in IDO1. If IntentDrivenObjectName2 and IntentDrivenObjectProperties2 are within the range of IntentDrivenObjectName1 and IntentDrivenObjectProperties1, the IntentDrivenObjectName2 and IntentDrivenObjectProperties2 of IntentDrivenObjectName2 correspond to the low-level intent. The system is placed in the list.
  • IntentDrivenObjectProperties1 is Pudong, if IntentDrivenObjectProperties2 is Jinqiao, the low-level intent system corresponding to IntentDrivenObjectProperties2 is placed in the list; if IntentDrivenObjectProperties2 is Minhang, the low-level intent system corresponding to IntentDrivenObjectProperties2 does not need to be placed in the list.
  • the low-level intent system is also screened according to the IDA of the newly added intent knowledge of the high-level intent system and the IDA of the existing sub-intent knowledge.
  • the method may include the following steps:
  • Steps S701 to S705 refer to steps S601 to S605 of the embodiment shown in FIG. 13 .
  • Step S706 the high-level intent system determines a list of low-level intent systems to be queried according to the intent keyword, IDO and IDA of the newly added/modified intent knowledge.
  • the high-level intent system sends an intent knowledge capability query request queryKnowledgeCapacity(consumerReference, Intentkeyword, IDO, IDA) to the low-level intent system in the list.
  • Intentkeyword, IDO, and IDA are intent knowledge added/modified by the high-level intent system according to the content of step S701 in step S703.
  • step S710 the knowledge management module of the low-level intent system queries the related intent knowledge RelatedIntentknowledge according to 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.
  • Steps S711 to S713 the low-level intent system sends an intent knowledge capability response queryKnowledgeCapacity Response(consumerReference, Intentkeyword, RelatedInten--tknowledge) to the high-level intent system.
  • Intentkeyword is the intent knowledge added/modified by the high-level intent system
  • RelatedIntentknowledge is the intent knowledge queried by the low-level intent system.
  • step S714 the high-level intent system updates the RelatedIntentknowledge to the knowledge repository, and associates the sub-intent knowledge with its own intent knowledge.
  • the high-level intent system after the high-level intent system adds/modifies intent knowledge, the related intent knowledge of the low-level intent system is queried according to the low-level intent system list, so that the intent knowledge in the low-level intent system is used as a sub-intent Knowledge addition/modification
  • the high-level intent system can decompose and distribute the newly added/modified intent knowledge.
  • An intent knowledge capability query operation is added on the interface between the fusion system and the fusion system. After the high-level intent system adds intent knowledge, this operation is used to query the intent knowledge of the low-level intent system.
  • the low-level intent system query list determination function has been added to the fusion system.
  • the sub-intent knowledge association function is added in the fusion system, and the intent knowledge of the low-level intent system obtained by the query is associated with the new intent knowledge of the high-level intent system as a sub-intent.
  • the present application also provides the following communication devices:
  • the communication apparatus may be the above-mentioned 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:
  • the transceiver unit 11 is configured to receive an intent knowledge update notification sent by the 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 the first intent knowledge update notification. an intent keyword of an intent; and a processing unit 12, configured to update the notification according to the intent knowledge, and compare the intent knowledge of the first intent corresponding to the intent keyword of the first intent with the first intent in the second intent system Two intents are associated with intent knowledge, wherein the first intent is a sub-intent of the second intent.
  • the transceiver unit 11 is further configured to send an intent knowledge update subscription request to the first intent system, where the intent knowledge update subscription request includes the identifier and update type of the second intent system; and The transceiver unit 11 is further configured to receive an 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: subscription identifier, subscription status; wherein, the intent knowledge update notification Also includes the subscription identifier.
  • the intent knowledge update notification further includes an identifier of the first intent system
  • the transceiver unit 11 is further configured to send an intent knowledge update response to the first intent system.
  • the update type is adding the intent knowledge of the first intent
  • the intent knowledge update notification further includes an intent-driven object and an intent-driven operation of the first intent
  • the processing unit 12 for querying the intent knowledge of the second intent in the second intent system according to the intent-driven object and intent-driven operation of the first intent, wherein the intent-driven object of the first intent is included in the 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 12 is further configured to convert the first intent
  • the intent keyword, the intent-driven object, and the intent-driven operation are associated with intent knowledge of the second intent.
  • the update type is to delete the intent knowledge of the first intent
  • the processing unit 12 is configured to search in the second intent system according to the intent keyword of the first intent The intent knowledge of the first intent corresponding to the intent keyword of the first intent; and the processing unit 12, further configured to delete the found intent knowledge of the first intent.
  • the update type is to modify the intent knowledge of the first intent
  • the intent knowledge update notification further includes at least one of the following information: keywords of the first intent before modification, The intent-driven object of the first intent before modification, the intent-driven operation of the first intent before modification, the keyword of the modified first intent, the intent-driven object of the modified first intent , the modified intent-driven operation of the first intent;
  • the processing unit 12 is configured to perform at least one of the following operations: after the first intent system modifies the intent keyword of the first intent, The intent keyword of the first intent is searched in the second intent system for the intent knowledge of the first intent corresponding to the intent keyword of the first intent before the modification, and the modified intent keyword is The intent keyword of the first intent replaces the intent keyword of the first intent before the modification in the intent knowledge of the first intent; the first intent system modifies the intent driving of the first intent After the object and/or the intent-driven operation, according to the modified intent-driven object and/or the intent-driven operation of the first intent, the intent knowledge of the second intent is que
  • the processing unit 12 is further configured to query the second intent system for a third intent-driven object and/or an intent-driven operation according to the first intent before the modification.
  • Intent knowledge of intents wherein the intent-driven object of the first intent before the modification is contained within the intent-driven object of the third intent, and/or the intent-driven object of the first intent before the modification The operation is included in the intent-driven operation of the third intent; the processing unit 12 is further configured to associate the intent-driven object and/or intent-driven operation of the first intent before the modification with the intent of the third intent knowledge to associate.
  • the transceiver unit 11 is further configured to update the intent knowledge of the second intent, and send an intent knowledge capability query request to at least one third intent system, wherein the intent knowledge capability query request It includes at least one piece of information: the identifier of the second intent system, the updated intent keyword of the second intent, an intent-driven object, and an intent-driven operation, wherein the first intent system is the at least one One of the intent systems in the third intent system; the transceiver unit 11 is further configured to receive an intent knowledge capability query response that is intended to be sent by the at least one third system, where 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 first intent associated with the updated intent keyword of the second intent, the intent-driven object, the intent-driven action and the processing unit 12, further configured to associate 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.
  • the update type is to modify the intent knowledge of the second intent
  • the processing unit 12 is further configured to perform at least one of the following operations: the second intent system modifies the intent of the second intent After selecting the keyword, associate the modified intent keyword of the second intent with the intent keyword of the first intent; or the second intent system modifies the intent-driven object and/or the intent-driven object of the second intent After the intent-driven operation, the modified intent-driven object and/or the intent-driven operation of the second intent is associated with the intent-driven object and/or the intent-driven operation of the first intent.
  • the processing unit 12 is further configured to query the second intent system according to the intent-driven object and/or intent-driven operation of the second intent before modification to find the at least one The intent knowledge of the fourth intent in the third intent system, wherein the intent-driven object of the second intent before the modification includes the intent-driven object of the fourth intent, and/or the intent-driven object of the second intent before the modification
  • the intent-driven operation of the second intent includes the intent-driven operation of the fourth intent
  • the processing unit 12 is further configured to compare the intent-driven object and/or intent-driven operation of the second intent before the modification with the intent-driven operation of the second intent. Intention-knowledge disassociation of the fourth intent.
  • the processing unit 12 is further configured to determine the at least one third intent system according to the updated intent-driven object of the second intent, wherein the at least one third intent The intent-driven object of the first intent in the intent system is contained within the updated intent-driven object of the second intent.
  • the communication of intent knowledge between intent systems can be realized.
  • association to avoid the intention knowledge update of the first intention leading to the lack or invalidation of the intention knowledge of the first intention in the second intention system, or to avoid that the intention knowledge update of the second intention cannot be performed with the intention knowledge of the first intention in the second intention system.
  • Associative unable to achieve intention decomposition and delivery.
  • the communication apparatus may be the above-mentioned first-intent system or a module in the first-intent system.
  • the communication device 200 includes: a processing unit 21 and a transceiver unit 22; wherein:
  • the processing unit 21 is configured to determine that the intent knowledge of the first intent of the first intent system has been updated; and the transceiver unit 22 is configured to send an intent knowledge update notification to the second intent system, so that the second intent system can update the intent knowledge according to the intent knowledge.
  • Update the notification 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 intent system, where the first intent is all the sub-intent of the second intent, and the intent knowledge update notification includes an update type and an intent keyword of the first intent.
  • the transceiver unit 22 is further configured to receive an intent knowledge update subscription request sent by the second intent system, where the intent knowledge update subscription request includes the identifier and update type of the second intent system; and the transceiver unit 22, further configured to send 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: subscription identifier, subscription status; wherein, the intent knowledge update notification Also includes the subscription identifier.
  • the transceiver unit 22 is further configured to receive an intent knowledge update response sent by the second intent system.
  • the update type includes at least one of the following: adding the intent knowledge of the first intent, deleting the intent knowledge of the first intent, and modifying the intent knowledge of the first intent; If the update type is to add the intent knowledge of the first intent, the intent knowledge update notification further includes an intent-driven object and an intent-driven operation of the first intent; if the update type is to modify the first intent The intent knowledge of the intent, the intent knowledge notification further includes at least one of the following information: the keyword of the first intent before modification, the intent-driven object of the first intent before modification, the first intent before modification The intent-driven operation of the intent, the modified keyword of the first intent, the modified intent-driven object of the first intent, and the modified intent-driven operation of the first intent.
  • the transceiver unit 22 is further configured to update the intent knowledge of the second intent, and receive an intent knowledge capability query request sent by the second intent system, where the intent knowledge capability query request includes At least one piece 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 the at least one third intent One of the intent systems in the system; the processing unit 21 is configured to find the first intent associated with at least one of the updated intent keyword, intent-driven object, and intent-driven operation of the updated second intent.
  • Intention knowledge and a transceiver unit 22, further configured to send an intention knowledge capability query response to the second intention system, where the intention knowledge capability query response includes at least one of the following information: an identifier of the second intention system, the Identification of at least one third intent system, intent knowledge of the first intent.
  • the communication of intent knowledge between intent systems can be realized.
  • association to avoid the intention knowledge update of the first intention leading to the lack or invalidation of the intention knowledge of the first intention in the second intention system, or to avoid that the intention knowledge update of the second intention cannot be performed with the intention knowledge of the first intention in the second intention system.
  • Associative unable to achieve intention decomposition and delivery.
  • FIG. 17 a schematic structural diagram of a communication apparatus is also provided, and the communication apparatus is configured to execute the above communication method.
  • the communication apparatus is configured to execute the above communication method.
  • Part or all of the above methods may be implemented by hardware, and may also be implemented by software or firmware.
  • the communication device may be a chip or an integrated circuit during specific implementation.
  • the communication device 300 may include:
  • the memory 33 and the processor 34 may be one or more, and one processor is taken as an example in FIG. 17 ), and may also include an input device 31 and an output device 32 .
  • the input device 31, the output device 32, the memory 33, and the processor 34 may be connected by a bus or other means, wherein the connection by a bus is taken as an example in FIG. 17 .
  • the processor 34 is configured to perform the method steps performed by the first intention system in FIGS. 8 to 14 .
  • the processor 34 is configured to perform the method steps performed by the second intent system in FIGS. 8-14 .
  • the program of the above communication method may be stored in the memory 33 .
  • the memory 33 may be a physically independent unit, or may be integrated with the processor 34 .
  • the memory 33 can also be used to store data.
  • the communication apparatus may also only include a processor.
  • the memory for storing the program is located outside the communication device, and the processor is connected to the memory through a circuit or wire for reading and executing the program stored in the memory.
  • the processor may be a central processing unit (CPU), a network processor (NP), or a WLAN device.
  • CPU central processing unit
  • NP network processor
  • WLAN device a WLAN device
  • the processor may further include a hardware chip.
  • the above-mentioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above-mentioned PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general-purpose array logic (generic array logic, GAL) or any combination thereof.
  • CPLD complex programmable logic device
  • FPGA field-programmable gate array
  • GAL general-purpose array logic
  • the memory may include volatile memory (volatile memory), such as random-access memory (RAM); the memory may also include non-volatile memory (non-volatile memory), such as flash memory (flash memory) , a hard disk drive (HDD) or a solid-state drive (SSD); the memory may also include a combination of the above-mentioned types of memory.
  • volatile memory such as random-access memory (RAM)
  • non-volatile memory such as flash memory (flash memory) , a hard disk drive (HDD) or a solid-state drive (SSD)
  • flash memory flash memory
  • HDD hard disk drive
  • SSD solid-state drive
  • the memory may also include a combination of the above-mentioned types of memory.
  • one or more embodiments of the present disclosure may be provided as a method, system or computer program product. Accordingly, one or more embodiments of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of the present disclosure may employ a computer program implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein form of the product.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • An embodiment of the present application further provides a chip system, including: at least one processor and an interface, the at least one processor is coupled to a memory through the interface, and when the at least one processor executes a computer program or instruction in the memory, the above-mentioned The method of any method embodiment is performed.
  • the chip system may be composed of chips, or may include chips and other discrete devices, which are not specifically limited in this embodiment of the present application.
  • Embodiments of the present application further provide a computer-readable storage medium, where a computer program may be stored thereon, and when the program is executed by a processor, the steps of the method described in any embodiment of the present disclosure are implemented.
  • the embodiments of the present application also provide a computer program product containing instructions, which, when executed on a computer, cause the computer to execute the steps of the method described in any of the embodiments of the present disclosure.
  • An embodiment of the present application further provides a communication system, where the communication system includes the above-mentioned communication device.
  • At least one (a) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c may be single or multiple .
  • words such as “first” and “second” are used to distinguish the same or similar items with basically the same function and effect. Those skilled in the art can understand that the words “first”, “second” and the like do not limit the quantity and execution order, and the words “first”, “second” and the like are not necessarily different.
  • words such as “exemplary” or “for example” are used to represent examples, illustrations or illustrations. Any embodiments or designs described in the embodiments of the present application as “exemplary” or “such as” should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as “exemplary” or “such as” is intended to present the related concepts in a specific manner to facilitate understanding.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the division of the unit is only a logical function division, and there may be other division methods in actual implementation, for example, multiple units or components may be combined or integrated into another system, or some features may be ignored, or not implement.
  • the shown or discussed mutual coupling, or direct coupling, or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • Units described as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the procedures or functions according to the embodiments of the present application are generated in whole or in part.
  • 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 or transmitted over a computer-readable storage medium.
  • the computer instructions can be sent from one website site, computer, server, or data center to another by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.)
  • wire e.g. coaxial cable, fiber optic, digital subscriber line (DSL)
  • wireless e.g., infrared, wireless, microwave, etc.
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes one or more available media integrated.
  • the available media may be read-only memory (ROM), or random access memory (RAM), or magnetic media, such as floppy disks, hard disks, magnetic tapes, magnetic disks, or optical media, such as , digital versatile disc (digital versatile disc, DVD), or semiconductor media, for example, solid state disk (solid state disk, SSD) and the like.
  • ROM read-only memory
  • RAM random access memory
  • magnetic media such as floppy disks, hard disks, magnetic tapes, magnetic disks, or optical media, such as , digital versatile disc (digital versatile disc, DVD), or semiconductor media, for example, solid state disk (solid state disk, SSD) and the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computational Linguistics (AREA)
  • Data Mining & Analysis (AREA)
  • Computing Systems (AREA)
  • Artificial Intelligence (AREA)
  • Evolutionary Computation (AREA)
  • Mathematical Physics (AREA)
  • Multimedia (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

一种意图系统间意图知识的关联方法及装置、系统，第一意图系统的第一意图的意图知识发生更新时(S101)，第二意图系统接收第一意图系统发送的意图知识更新通知(S102)，其中，意图知识更新通知包括更新类型和第一意图的意图关键词；第二意图系统根据意图知识更新通知，将第一意图的意图关键词对应的第一意图的意图知识与第二意图系统中的第二意图的意图知识进行关联(S103)，其中，第一意图是第二意图的子意图。从而可以在第一意图系统的第一意图的意图知识发生更新时，实现意图系统间意图知识的关联，避免第一意图的意图知识更新导致第二意图系统中第一意图的意图知识的缺失或者失效。

Description

意图系统间意图知识的关联方法及装置、系统 技术领域
本申请涉及网络智能管理技术领域，尤其涉及一种意图系统间意图知识的关联方法及装置、系统。
背景技术
意图系统的意图知识库(knowledge repository)中存放的意图知识都有一个一一对应的意图关键词(Intentkeyword)，用于标识该意图知识。该意图知识包括执行约束(constraint)，以及操作集合(intentOperations)：intentOperations[执行条件(executionConditon)，操作类型(operationType)，操作(operation)]。意图知识库的operationType是一个枚举类型，其中，operationType的一个取值为“subintent”，表示对应的操作描述的是一个子意图下发的脚本，包括子意图的意图关键词。该子意图对应的意图知识在下级(low-level)意图系统的意图知识库中存在。
同时，上级(high-level)意图系统的意图知识库中会存放low-level意图系统的意图知识的意图关键词、意图驱动对象(IntentDrivenObject，IDO)和意图驱动操作(IntentDrivenAction，IDA)，这是high-level意图系统实现子意图下发的前提。如图1所示的分层部署的多级意图系统示意图，high-level意图系统收到意图下发命令后，由于意图对应的操作对象(如：网元)被不同的low-level意图系统管理，high-level意图系统会将意图进行分解，并向这些low-level意图系统发送分解后的子意图，同时low-level意图系统将意图达成情况反馈给high-level意图系统。
外部系统可以对意图系统的意图知识库中的意图知识进行更新，例如新增、修改和删除。然而，在分层部署的多级意图系统中，不同层级的意图系统分层、分域，意图系统实行分域自治，外部系统无法对不同层级的意图系统都进行意图知识管理操作。所以，外部系统进行意图知识更新操作，只能对当前意图系统的意图知识库中的意图知识进行更新，并不能对与当前意图系统相关的上下级意图系统进行意图知识更新。这会导致意图知识更新后意图系统子意图下发效率低下，甚至意图知识失效或者缺失。
有鉴于此，如何进行意图系统间意图知识的关联，使得意图知识的更新不会影响上级意图系统的意图分解和下发，是本申请亟待解决的问题。
发明内容
本申请实施例提供一种意图系统间意图知识的关联方法及装置、系统，以在意图知识发生更新时，实现意图系统间意图知识的关联。
第一方面，提供了一种意图系统间意图知识的关联方法，所述方法包括：第一意图系统的第一意图的意图知识发生更新时，第二意图系统接收所述第一意图系统发送的意图知识更新通知，其中，所述意图知识更新通知包括更新类型和所述第一意图的意图关键词；以及所述第二意图系统根据所述意图知识更新通知，将所述第一意图的意图关键词对应的所述第一意图的意图知识与所述第二意图系统中的第二意图的意图知识进行关联，其中，所述第一意图是所述第二意图的子意图。在该方面中，可以在第一意图系统的第一意图的 意图知识发生更新时，实现意图系统间意图知识的关联，避免第一意图的意图知识更新导致第二意图系统中第一意图的意图知识的缺失或者失效。
在一种可能的实现中，第二意图系统接收所述第一意图系统发送的意图知识更新通知之前，所述方法还包括：所述第二意图系统向所述第一意图系统发送意图知识更新订阅请求，所述意图知识更新订阅请求包括所述第二意图系统的标识和更新类型；以及所述第二意图系统接收所述第一意图系统发送的意图知识更新订阅响应，所述意图知识更新订阅响应包括以下至少一项信息：订阅标识，订阅状态；其中，所述意图知识更新通知还包括所述订阅标识。在该实现中，第一意图系统新增意图知识，可以通过订阅-通知的方式告知第二意图系统。
在又一种可能的实现中，所述意图知识更新通知还包括所述第一意图系统的标识，所述第二意图系统接收所述第一意图系统发送的意图知识更新通知之后，所述方法还包括：所述第二意图系统向所述第一意图系统发送意图知识更新响应。在该实现中，第一意图系统新增意图知识，通过直接上报的方式告知第二意图系统。
在又一种可能的实现中，所述更新类型为新增所述第一意图的意图知识，所述意图知识更新通知还包括所述第一意图的意图驱动对象和意图驱动操作；所述第二意图系统根据所述意图知识更新通知，将所述第一意图的意图关键词对应的所述第一意图的意图知识与所述第二意图系统中的第二意图的意图知识进行关联，包括：所述第二意图系统根据所述第一意图的意图驱动对象和意图驱动操作，在所述第二意图系统中查询到所述第二意图的意图知识，其中，所述第一意图的意图驱动对象包含在所述第二意图的意图驱动对象内，和/或所述第一意图的意图驱动操作包含在所述第二意图的意图驱动操作中；以及所述第二意图系统将所述第一意图的意图关键词、所述意图驱动对象和所述意图驱动操作与所述第二意图的意图知识进行关联。
在又一种可能的实现中，所述更新类型为删除所述第一意图的意图知识，所述第二意图系统根据所述意图知识更新通知，将所述第一意图的意图关键词对应的所述第一意图的意图知识与所述第二意图系统中的第二意图的意图知识进行关联，包括：所述第二意图系统根据所述第一意图的意图关键词，在所述第二意图系统中查找与所述第一意图的意图关键词对应的所述第一意图的意图知识；以及所述第二意图系统删除查找到的所述第一意图的意图知识。
在又一种可能的实现中，所述更新类型为修改所述第一意图的意图知识，所述意图知识更新通知还包括以下至少一项信息：修改前的所述第一意图的关键词、修改前的所述第一意图的意图驱动对象、修改前的所述第一意图的意图驱动操作、修改后的所述第一意图的关键词、修改后的所述第一意图的意图驱动对象、修改后的所述第一意图的意图驱动操作；所述第二意图系统根据所述意图知识更新通知，将所述第一意图的意图关键词对应的所述第一意图的意图知识与所述第二意图系统中的第二意图的意图知识进行关联，包括以下至少一种操作：所述第一意图系统修改所述第一意图的意图关键词后，所述第二意图系统根据修改前的所述第一意图的意图关键词，在所述第二意图系统中查找与所述修改前的所述第一意图的意图关键词对应的所述第一意图的意图知识，所述第二意图系统将所述修改后的所述第一意图的意图关键词替换所述第一意图的意图知识中的所述修改前的所述第 一意图的意图关键词；所述第一意图系统修改所述第一意图的意图驱动对象和/或意图驱动操作后，所述第二意图系统根据所述修改后的所述第一意图的意图驱动对象和/或意图驱动操作，在所述第二意图系统中查询到所述第二意图的意图知识，其中，所述修改后的所述第一意图的意图驱动对象包含在所述第二意图的意图驱动对象内，和/或所述修改后的所述第一意图的意图驱动操作包含在所述第二意图的意图驱动操作中；所述第二意图系统将所述修改后的所述第一意图的意图驱动对象和/或意图驱动操作与所述第二意图的意图知识关联。
在又一种可能的实现中，所述方法还包括：所述第二意图系统根据所述修改前的所述第一意图的意图驱动对象和/或意图驱动操作，在所述第二意图系统中查询到第三意图的意图知识，其中，所述修改前的所述第一意图的意图驱动对象包含在所述第三意图的意图驱动对象内，和/或所述修改前的所述第一意图的意图驱动操作包含在所述第三意图的意图驱动操作中；所述第二意图系统将所述修改前的所述第一意图的意图驱动对象和/或意图驱动操作与所述第三意图的意图知识去关联。
在又一种可能的实现中，所述方法还包括：所述第二意图的意图知识发生更新，所述第二意图系统向至少一个第三意图系统发送意图知识能力查询请求，其中，所述意图知识能力查询请求包括以下至少一项信息：所述第二意图系统的标识、更新后的所述第二意图的意图关键词、意图驱动对象、意图驱动操作，其中，所述第一意图系统为所述至少一个第三意图系统中的其中一个意图系统；所述第二意图系统接收所述至少一个第三系统意图发送的意图知识能力查询响应，所述意图知识能力查询响应包括以下至少一项信息：所述第二意图系统的标识、所述至少一个第三意图系统的标识、与更新后的所述第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项关联的第一意图的意图知识；以及所述第二意图系统将所述第一意图的意图知识与更新后的所述第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项进行关联。在该实现中，第二意图系统的第二意图的意图知识发生更新时，实现意图系统间意图知识的关联，可以避免第二意图的意图知识更新无法与第二意图系统中第一意图的意图知识进行关联，无法实现意图分解和下发。
在又一种可能的实现中，更新类型为修改所述第二意图的意图知识，所述第二意图系统将所述第一意图的意图知识与更新后的所述第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项进行关联，包括以下至少一种操作：所述第二意图系统修改所述第二意图的意图关键词后，所述第二意图系统将修改后的所述第二意图的意图关键词与所述第一意图的意图关键词进行关联；所述第二意图系统修改所述第二意图的意图驱动对象和/或意图驱动操作后，所述第二意图系统将修改后的所述第二意图的意图驱动对象和/或意图驱动操作与所述第一意图的意图驱动对象和/或意图驱动操作进行关联。
在又一种可能的实现中，所述方法还包括：所述第二意图系统根据修改前的所述第二意图的意图驱动对象和/或意图驱动操作，在所述第二意图系统中查询到所述至少一个第三意图系统中的第四意图的意图知识，其中，所述修改前的所述第二意图的意图驱动对象包含所述第四意图的意图驱动对象，和/或所述修改前的所述第二意图的意图驱动操作包含所述第四意图的意图驱动操作；以及所述第二意图系统将所述修改前的所述第二意图的意图驱动对象和/或意图驱动操作与所述第四意图的意图知识去关联。
在又一种可能的实现中，所述第二意图系统向至少一个第三意图系统发送意图知识能力查询请求之前，所述方法还包括：所述第二意图系统根据更新后的所述第二意图的所述意图驱动对象，确定所述至少一个第三意图系统，其中，所述至少一个第三意图系统中的所述第一意图的意图驱动对象包含在更新后的所述第二意图的意图驱动对象内。
第二方面，提供了一种意图系统间意图知识的关联方法，所述方法包括：确定第一意图系统的第一意图的意图知识发生更新；以及所述第一意图系统向第二意图系统发送意图知识更新通知，以使第二意图系统根据所述意图知识更新通知，将所述第一意图的意图关键词对应的所述第一意图的意图知识与所述第二意图系统中的第二意图的意图知识进行关联，其中，所述第一意图是所述第二意图的子意图，所述意图知识更新通知包括更新类型和所述第一意图的意图关键词。
在一种可能的实现中，所述第一意图系统向第二意图系统发送意图知识更新通知之前，所述方法还包括：所述第一意图系统接收所述第二意图系统发送的意图知识更新订阅请求，所述意图知识更新订阅请求包括所述第二意图系统的标识和更新类型；以及所述第一意图系统向所述第二意图系统发送意图知识更新订阅响应，所述意图知识更新订阅响应包括以下至少一项信息：订阅标识，订阅状态；其中，所述意图知识更新通知还包括所述订阅标识。
在又一种可能的实现中，所述第一意图系统向第二意图系统发送意图知识更新通知之后，所述方法还包括：所述第一意图系统接收所述第二意图系统发送的意图知识更新响应。
在又一种可能的实现中，所述更新类型包括以下至少一种：新增所述第一意图的意图知识、删除所述第一意图的意图知识、修改所述第一意图的意图知识；若所述更新类型为新增所述第一意图的意图知识，所述意图知识更新通知还包括所述第一意图的意图驱动对象和意图驱动操作；若所述更新类型为修改所述第一意图的意图知识，所述意图知识通知还包括以下至少一项信息：修改前的所述第一意图的关键词、修改前的所述第一意图的意图驱动对象、修改前的所述第一意图的意图驱动操作、修改后的所述第一意图的关键词、修改后的所述第一意图的意图驱动对象、修改后的所述第一意图的意图驱动操作。
在又一种可能的实现中，所述方法还包括：所述第二意图的意图知识发生更新，所述第一意图系统接收所述第二意图系统发送的意图知识能力查询请求，所述意图知识能力查询请求包括以下至少一项信息：所述第二意图系统的标识、更新后的第二意图的意图关键词、意图驱动对象、意图驱动操作，其中，所述第一意图系统为所述至少一个第三意图系统中的其中一个意图系统；所述第一意图系统查找到与所述更新后的第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项关联的所述第一意图的意图知识；以及所述第一意图系统向所述第二意图系统发送意图知识能力查询响应，所述意图知识能力查询响应包括以下至少一项信息：所述第二意图系统的标识、所述至少一个第三意图系统的标识、所述第一意图的意图知识。
第三方面，提供了一种通信装置用于执行上述第一方面或第一方面的任一可能的实现中的方法。该通信装置可以为上述第一方面或第一方面的任一可能的实现中的第二意图系统，或者应用于第二意图系统中的模块，例如芯片或芯片系统。其中，该通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件 实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
结合上述第三方面，在一种可能的实现中，通信装置包括：收发单元和处理单元；其中：
收发单元，用于第一意图系统的第一意图的意图知识发生更新时，接收所述第一意图系统发送的意图知识更新通知，其中，所述意图知识更新通知包括更新类型和所述第一意图的意图关键词；以及处理单元，用于根据所述意图知识更新通知，将所述第一意图的意图关键词对应的所述第一意图的意图知识与第二意图系统中的第二意图的意图知识进行关联，其中，所述第一意图是所述第二意图的子意图。
在一种可能的实现中，收发单元，还用于向所述第一意图系统发送意图知识更新订阅请求，所述意图知识更新订阅请求包括所述第二意图系统的标识和更新类型；以及收发单元，还用于接收所述第一意图系统发送的意图知识更新订阅响应，所述意图知识更新订阅响应包括以下至少一项信息：订阅标识，订阅状态；其中，所述意图知识更新通知还包括所述订阅标识。
在又一种可能的实现中，所述意图知识更新通知还包括所述第一意图系统的标识，收发单元，还用于向所述第一意图系统发送意图知识更新响应。
在又一种可能的实现中，所述更新类型为新增所述第一意图的意图知识，所述意图知识更新通知还包括所述第一意图的意图驱动对象和意图驱动操作；处理单元，用于根据所述第一意图的意图驱动对象和意图驱动操作，在所述第二意图系统中查询到所述第二意图的意图知识，其中，所述第一意图的意图驱动对象包含在所述第二意图的意图驱动对象内，和/或所述第一意图的意图驱动操作包含在所述第二意图的意图驱动操作中；以及处理单元，还用于将所述第一意图的意图关键词、所述意图驱动对象和所述意图驱动操作与所述第二意图的意图知识进行关联。
在又一种可能的实现中，所述更新类型为删除所述第一意图的意图知识，处理单元，用于根据所述第一意图的意图关键词，在所述第二意图系统中查找与所述第一意图的意图关键词对应的所述第一意图的意图知识；以及处理单元，还用于删除查找到的所述第一意图的意图知识。
在又一种可能的实现中，所述更新类型为修改所述第一意图的意图知识，所述意图知识更新通知还包括以下至少一项信息：修改前的所述第一意图的关键词、修改前的所述第一意图的意图驱动对象、修改前的所述第一意图的意图驱动操作、修改后的所述第一意图的关键词、修改后的所述第一意图的意图驱动对象、修改后的所述第一意图的意图驱动操作；处理单元，用于执行以下至少一种操作：所述第一意图系统修改所述第一意图的意图关键词后，根据修改前的所述第一意图的意图关键词，在所述第二意图系统中查找与所述修改前的所述第一意图的意图关键词对应的所述第一意图的意图知识，将所述修改后的所述第一意图的意图关键词替换所述第一意图的意图知识中的所述修改前的所述第一意图的意图关键词；所述第一意图系统修改所述第一意图的意图驱动对象和/或意图驱动操作后，根据所述修改后的所述第一意图的意图驱动对象和/或意图驱动操作，在所述第二意图系统中查询到所述第二意图的意图知识，其中，所述修改后的所述第一意图的意图驱动对象包 含在所述第二意图的意图驱动对象内，和/或所述修改后的所述第一意图的意图驱动操作包含在所述第二意图的意图驱动操作中；将所述修改后的所述第一意图的意图驱动对象和/或意图驱动操作与所述第二意图的意图知识关联。
在又一种可能的实现中，处理单元，还用于根据所述修改前的所述第一意图的意图驱动对象和/或意图驱动操作，在所述第二意图系统中查询到第三意图的意图知识，其中，所述修改前的所述第一意图的意图驱动对象包含在所述第三意图的意图驱动对象内，和/或所述修改前的所述第一意图的意图驱动操作包含在所述第三意图的意图驱动操作中；处理单元，还用于将所述修改前的所述第一意图的意图驱动对象和/或意图驱动操作与所述第三意图的意图知识去关联。
在又一种可能的实现中，收发单元，还用于所述第二意图的意图知识发生更新，向至少一个第三意图系统发送意图知识能力查询请求，其中，所述意图知识能力查询请求包括以下至少一项信息：所述第二意图系统的标识、更新后的所述第二意图的意图关键词、意图驱动对象、意图驱动操作，其中，所述第一意图系统为所述至少一个第三意图系统中的其中一个意图系统；收发单元，还用于接收所述至少一个第三系统意图发送的意图知识能力查询响应，所述意图知识能力查询响应包括以下至少一项信息：所述第二意图系统的标识、所述至少一个第三意图系统的标识、与更新后的所述第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项关联的第一意图的意图知识；以及处理单元，还用于将所述第一意图的意图知识与更新后的所述第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项进行关联。
在又一种可能的实现中，更新类型为修改所述第二意图的意图知识，处理单元，还用于执行以下至少一种操作：所述第二意图系统修改所述第二意图的意图关键词后，将修改后的所述第二意图的意图关键词与所述第一意图的意图关键词进行关联；或所述第二意图系统修改所述第二意图的意图驱动对象和/或意图驱动操作后，将修改后的所述第二意图的意图驱动对象和/或意图驱动操作与所述第一意图的意图驱动对象和/或意图驱动操作进行关联。
在又一种可能的实现中，处理单元，还用于根据修改前的所述第二意图的意图驱动对象和/或意图驱动操作，在所述第二意图系统中查询到所述至少一个第三意图系统中的第四意图的意图知识，其中，所述修改前的所述第二意图的意图驱动对象包含所述第四意图的意图驱动对象，和/或所述修改前的所述第二意图的意图驱动操作包含所述第四意图的意图驱动操作；以及处理单元，还用于将所述修改前的所述第二意图的意图驱动对象和/或意图驱动操作与所述第四意图的意图知识去关联。
在又一种可能的实现中，处理单元，还用于根据更新后的所述第二意图的所述意图驱动对象，确定所述至少一个第三意图系统，其中，所述至少一个第三意图系统中的所述第一意图的意图驱动对象包含在更新后的所述第二意图的意图驱动对象内。
结合上述第三方面，在又一种可能的实现中，通信装置包括：输入接口、输出接口和处理电路；其中：
输入接口，用于第一意图系统的第一意图的意图知识发生更新时，接收所述第一意图系统发送的意图知识更新通知，其中，所述意图知识更新通知包括更新类型和所述第一意 图的意图关键词；以及处理电路，用于根据所述意图知识更新通知，将所述第一意图的意图关键词对应的所述第一意图的意图知识与第二意图系统中的第二意图的意图知识进行关联，其中，所述第一意图是所述第二意图的子意图。
在一种可能的实现中，输出接口，还用于向所述第一意图系统发送意图知识更新订阅请求，所述意图知识更新订阅请求包括所述第二意图系统的标识和更新类型；以及输入接口，还用于接收所述第一意图系统发送的意图知识更新订阅响应，所述意图知识更新订阅响应包括以下至少一项信息：订阅标识，订阅状态；其中，所述意图知识更新通知还包括所述订阅标识。
在又一种可能的实现中，所述意图知识更新通知还包括所述第一意图系统的标识，输出接口，还用于向所述第一意图系统发送意图知识更新响应。
在又一种可能的实现中，所述更新类型为新增所述第一意图的意图知识，所述意图知识更新通知还包括所述第一意图的意图驱动对象和意图驱动操作；处理电路，用于根据所述第一意图的意图驱动对象和意图驱动操作，在所述第二意图系统中查询到所述第二意图的意图知识，其中，所述第一意图的意图驱动对象包含在所述第二意图的意图驱动对象内，和/或所述第一意图的意图驱动操作包含在所述第二意图的意图驱动操作中；以及处理电路，还用于将所述第一意图的意图关键词、所述意图驱动对象和所述意图驱动操作与所述第二意图的意图知识进行关联。
在又一种可能的实现中，所述更新类型为删除所述第一意图的意图知识，处理电路，用于根据所述第一意图的意图关键词，在所述第二意图系统中查找与所述第一意图的意图关键词对应的所述第一意图的意图知识；以及处理电路，还用于删除查找到的所述第一意图的意图知识。
在又一种可能的实现中，所述更新类型为修改所述第一意图的意图知识，所述意图知识更新通知还包括以下至少一项信息：修改前的所述第一意图的关键词、修改前的所述第一意图的意图驱动对象、修改前的所述第一意图的意图驱动操作、修改后的所述第一意图的关键词、修改后的所述第一意图的意图驱动对象、修改后的所述第一意图的意图驱动操作；处理电路，用于执行以下至少一种操作：所述第一意图系统修改所述第一意图的意图关键词后，根据修改前的所述第一意图的意图关键词，在所述第二意图系统中查找与所述修改前的所述第一意图的意图关键词对应的所述第一意图的意图知识，将所述修改后的所述第一意图的意图关键词替换所述第一意图的意图知识中的所述修改前的所述第一意图的意图关键词；所述第一意图系统修改所述第一意图的意图驱动对象和/或意图驱动操作后，根据所述修改后的所述第一意图的意图驱动对象和/或意图驱动操作，在所述第二意图系统中查询到所述第二意图的意图知识，其中，所述修改后的所述第一意图的意图驱动对象包含在所述第二意图的意图驱动对象内，和/或所述修改后的所述第一意图的意图驱动操作包含在所述第二意图的意图驱动操作中；将所述修改后的所述第一意图的意图驱动对象和/或意图驱动操作与所述第二意图的意图知识关联。
在又一种可能的实现中，处理电路，还用于根据所述修改前的所述第一意图的意图驱动对象和/或意图驱动操作，在所述第二意图系统中查询到第三意图的意图知识，其中，所述修改前的所述第一意图的意图驱动对象包含在所述第三意图的意图驱动对象内，和/或所 述修改前的所述第一意图的意图驱动操作包含在所述第三意图的意图驱动操作中；处理电路，还用于将所述修改前的所述第一意图的意图驱动对象和/或意图驱动操作与所述第三意图的意图知识去关联。
在又一种可能的实现中，输出接口，还用于所述第二意图的意图知识发生更新，向至少一个第三意图系统发送意图知识能力查询请求，其中，所述意图知识能力查询请求包括以下至少一项信息：所述第二意图系统的标识、更新后的所述第二意图的意图关键词、意图驱动对象、意图驱动操作，其中，所述第一意图系统为所述至少一个第三意图系统中的其中一个意图系统；输入接口，还用于接收所述至少一个第三系统意图发送的意图知识能力查询响应，所述意图知识能力查询响应包括以下至少一项信息：所述第二意图系统的标识、所述至少一个第三意图系统的标识、与更新后的所述第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项关联的第一意图的意图知识；以及处理电路，还用于将所述第一意图的意图知识与更新后的所述第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项进行关联。
在又一种可能的实现中，更新类型为修改所述第二意图的意图知识，处理电路，还用于执行以下至少一种操作：所述第二意图系统修改所述第二意图的意图关键词后，将修改后的所述第二意图的意图关键词与所述第一意图的意图关键词进行关联；或所述第二意图系统修改所述第二意图的意图驱动对象和/或意图驱动操作后，将修改后的所述第二意图的意图驱动对象和/或意图驱动操作与所述第一意图的意图驱动对象和/或意图驱动操作进行关联。
在又一种可能的实现中，处理电路，还用于根据修改前的所述第二意图的意图驱动对象和/或意图驱动操作，在所述第二意图系统中查询到所述至少一个第三意图系统中的第四意图的意图知识，其中，所述修改前的所述第二意图的意图驱动对象包含所述第四意图的意图驱动对象，和/或所述修改前的所述第二意图的意图驱动操作包含所述第四意图的意图驱动操作；以及处理电路，还用于将所述修改前的所述第二意图的意图驱动对象和/或意图驱动操作与所述第四意图的意图知识去关联。
在又一种可能的实现中，处理电路，还用于根据更新后的所述第二意图的所述意图驱动对象，确定所述至少一个第三意图系统，其中，所述至少一个第三意图系统中的所述第一意图的意图驱动对象包含在更新后的所述第二意图的意图驱动对象内。
示例性地，该通信装置还包括存储器，该存储器与该至少一个处理器耦合，该至少一个处理器用于运行存储器中存储的程序指令，以使得所述通信装置执行上述第一方面或第一方面的任一可能的实现中的方法。
在一种可能的实现中，该存储器用于存储程序指令和数据。该存储器与该至少一个处理器耦合，该至少一个处理器可以调用并执行该存储器中存储的程序指令，以使得所述通信装置执行上述第一方面或第一方面的任一可能的实现中的方法。
示例性地，该通信装置还包括通信接口，该通信接口用于该通信装置与其它设备进行通信。当该通信装置为第二意图系统时，该通信接口为收发器、输入/输出接口、或电路等。
在一种可能的设计中，该通信装置包括：至少一个处理器和通信接口，用于执行上述第一方面或第一方面的任一可能的实现中的方法，具体地包括：该至少一个处理器利用该 通信接口与外部通信；该至少一个处理器用于运行计算机程序，使得该通信装置执行上述第一方面或第一方面的任一可能的实现中的方法。可以理解，该外部可以是处理器以外的对象，或者是该通信装置以外的对象。
在另一种可能的设计中，该通信装置为芯片或芯片系统。该通信接口可以是该芯片或芯片系统上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。该处理器也可以体现为处理电路或逻辑电路。
其中，第三方面中任一种设计方式所带来的技术效果可参见上述第一方面中不同设计方式所带来的技术效果，此处不再赘述。
第四方面，提供了一种通信装置用于执行上述第二方面或第二方面的任一可能的实现中的方法。该通信装置可以为上述第二方面或第二方面的任一可能的实现中的第一意图系统，或者应用于第一意图系统中的模块，例如芯片或芯片系统。其中，该通信装置包括实现上述方法相应的模块、单元、或means，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
结合上述第四方面，在一种可能的实现中，通信装置包括：处理单元和收发单元；其中：
处理单元，用于确定第一意图系统的第一意图的意图知识发生更新；以及收发单元，用于向第二意图系统发送意图知识更新通知，以使第二意图系统根据所述意图知识更新通知，将所述第一意图的意图关键词对应的所述第一意图的意图知识与所述第二意图系统中的第二意图的意图知识进行关联，其中，所述第一意图是所述第二意图的子意图，所述意图知识更新通知包括更新类型和所述第一意图的意图关键词。
在一种可能的实现中，收发单元，还用于接收所述第二意图系统发送的意图知识更新订阅请求，所述意图知识更新订阅请求包括所述第二意图系统的标识和更新类型；以及收发单元，还用于向所述第二意图系统发送意图知识更新订阅响应，所述意图知识更新订阅响应包括以下至少一项信息：订阅标识，订阅状态；其中，所述意图知识更新通知还包括所述订阅标识。
在又一种可能的实现中，收发单元，还用于接收所述第二意图系统发送的意图知识更新响应。
在又一种可能的实现中，所述更新类型包括以下至少一种：新增所述第一意图的意图知识、删除所述第一意图的意图知识、修改所述第一意图的意图知识；若所述更新类型为新增所述第一意图的意图知识，所述意图知识更新通知还包括所述第一意图的意图驱动对象和意图驱动操作；若所述更新类型为修改所述第一意图的意图知识，所述意图知识通知还包括以下至少一项信息：修改前的所述第一意图的关键词、修改前的所述第一意图的意图驱动对象、修改前的所述第一意图的意图驱动操作、修改后的所述第一意图的关键词、修改后的所述第一意图的意图驱动对象、修改后的所述第一意图的意图驱动操作。
在又一种可能的实现中，收发单元，还用于所述第二意图的意图知识发生更新，接收所述第二意图系统发送的意图知识能力查询请求，所述意图知识能力查询请求包括以下至少一项信息：所述第二意图系统的标识、更新后的第二意图的意图关键词、意图驱动对象、 意图驱动操作，其中，所述第一意图系统为所述至少一个第三意图系统中的其中一个意图系统；处理单元，用于查找到与所述更新后的第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项关联的所述第一意图的意图知识；以及收发单元，还用于向所述第二意图系统发送意图知识能力查询响应，所述意图知识能力查询响应包括以下至少一项信息：所述第二意图系统的标识、所述至少一个第三意图系统的标识、所述第一意图的意图知识。
结合上述第四方面，在又一种可能的实现中，通信装置包括：输入接口、输出接口和处理电路；其中：
处理电路，用于确定第一意图系统的第一意图的意图知识发生更新；以及输出接口，用于向第二意图系统发送意图知识更新通知，以使第二意图系统根据所述意图知识更新通知，将所述第一意图的意图关键词对应的所述第一意图的意图知识与所述第二意图系统中的第二意图的意图知识进行关联，其中，所述第一意图是所述第二意图的子意图，所述意图知识更新通知包括更新类型和所述第一意图的意图关键词。
在一种可能的实现中，输入接口，还用于接收所述第二意图系统发送的意图知识更新订阅请求，所述意图知识更新订阅请求包括所述第二意图系统的标识和更新类型；以及输出接口，还用于向所述第二意图系统发送意图知识更新订阅响应，所述意图知识更新订阅响应包括以下至少一项信息：订阅标识，订阅状态；其中，所述意图知识更新通知还包括所述订阅标识。
在又一种可能的实现中，输入接口，还用于接收所述第二意图系统发送的意图知识更新响应。
在又一种可能的实现中，所述更新类型包括以下至少一种：新增所述第一意图的意图知识、删除所述第一意图的意图知识、修改所述第一意图的意图知识；若所述更新类型为新增所述第一意图的意图知识，所述意图知识更新通知还包括所述第一意图的意图驱动对象和意图驱动操作；若所述更新类型为修改所述第一意图的意图知识，所述意图知识通知还包括以下至少一项信息：修改前的所述第一意图的关键词、修改前的所述第一意图的意图驱动对象、修改前的所述第一意图的意图驱动操作、修改后的所述第一意图的关键词、修改后的所述第一意图的意图驱动对象、修改后的所述第一意图的意图驱动操作。
在又一种可能的实现中，输入接口，还用于所述第二意图的意图知识发生更新，接收所述第二意图系统发送的意图知识能力查询请求，所述意图知识能力查询请求包括以下至少一项信息：所述第二意图系统的标识、更新后的第二意图的意图关键词、意图驱动对象、意图驱动操作，其中，所述第一意图系统为所述至少一个第三意图系统中的其中一个意图系统；处理电路，用于查找到与所述更新后的第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项关联的所述第一意图的意图知识；以及输入接口，还用于向所述第二意图系统发送意图知识能力查询响应，所述意图知识能力查询响应包括以下至少一项信息：所述第二意图系统的标识、所述至少一个第三意图系统的标识、所述第一意图的意图知识。
示例性地，该通信装置还包括存储器，该存储器与该至少一个处理器耦合，该至少一个处理器用于运行存储器中存储的程序指令，以使得所述通信装置执行上述第二方面或第 二方面的任一可能的实现中的方法。
在一种可能的实现中，该存储器用于存储程序指令和数据。该存储器与该至少一个处理器耦合，该至少一个处理器可以调用并执行该存储器中存储的程序指令，以使得所述通信装置执行上述第二方面或第二方面的任一可能的实现中的方法。
示例性地，该通信装置还包括通信接口，该通信接口用于该通信装置与其它设备进行通信。当该通信装置为第一意图系统时，该通信接口为收发器、输入/输出接口、或电路等。
在一种可能的设计中，该通信装置包括：至少一个处理器和通信接口，用于执行上述第二方面或第二方面的任一可能的实现中的方法，具体地包括：该至少一个处理器利用该通信接口与外部通信；该至少一个处理器用于运行计算机程序，使得该通信装置执行上述第二方面或第二方面的任一可能的实现中的方法。可以理解，该外部可以是处理器以外的对象，或者是该通信装置以外的对象。
在另一种可能的设计中，该通信装置为芯片或芯片系统。该通信接口可以是该芯片或芯片系统上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。该处理器也可以体现为处理电路或逻辑电路。
其中，第四方面中任一种设计方式所带来的技术效果可参见上述第二方面中不同设计方式所带来的技术效果，此处不再赘述。
第五方面，提供了一种通信系统，包括如第三方面或第三方面的任一个实现所述的通信装置，以及如第四方面所述的通信装置。
第六方面，提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第七方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第八方面，提供了一种芯片，所述芯片与存储器耦合，执行本申请实施例第一方面或第一方面中任一实现所述的通信方法。
第九方面，提供了一种芯片，所述芯片与存储器耦合，执行本申请实施例第二方面或第二方面中任一实现所述的通信方法。
需要说明的是，本申请实施例中“耦合”是指两个部件彼此直接或间接地结合。
附图说明
图1为分层部署的多级意图系统示意图；
图2为IDM示意图；
图3为IDMS定义的意图分级示意图；
图4为知识管理功能模块示意图；
图5为基于意图策略的ENI架构示意图；
图6为基于意图策略的ENI融合系统中的意图知识管理架构示意图；
图7为本申请实施例提供的基于意图策略的ENI融合系统中的意图知识管理架构示意图；
图8为本申请实施例提供的一种意图系统间意图知识的关联方法的流程示意图；
图9为本申请实施例提供的又一种意图系统间意图知识的关联方法的流程示意图；
图10为本申请实施例提供的又一种意图系统间意图知识的关联方法的流程示意图；
图11为本申请实施例提供的又一种意图系统间意图知识的关联方法的流程示意图；
图12为本申请实施例提供的又一种意图系统间意图知识的关联方法的流程示意图；
图13为本申请实施例提供的又一种意图系统间意图知识的关联方法的流程示意图；
图14为本申请实施例提供的又一种意图系统间意图知识的关联方法的流程示意图；
图15为本申请实施例提供的一种通信装置的结构示意图；
图16为本申请实施例提供的又一种通信装置的结构示意图；
图17为本申请实施例提供的又一种通信装置的结构示意图。
具体实施方式
为了降低网络基础设施的管理复杂度，3GPP SA5启动了意图驱动管理(intent driven management，IDM)的研究，IDM采用服务化的接口来实现意图的下发。如图2所示的IDM示意图，意图驱动管理服务消费者(IDM service consumer)通过调用意图驱动管理服务(intent driven management service，IDMS)接口将意图下发至意图驱动管理服务提供者(IDM service producer)，IDM业务提供者将意图转译为具体的执行策略下发给网络基础设施(network infrastructure)。该网络基础设施可以是物理的(physical)和/或虚拟的(virtual)。意图模型用于对意图表达(intentExpression)中应包含的信息进行建模，至少应包含“意图驱动动作(IntentDrivenAction，IDA)”和“意图驱动对象(IntentDrivenObject，IDO)”。IDA由一个动作名(IntentDrivenActionName)和完成该动作所需的一系列属性(IntentDrivenActionProperties)组成；IDO则由一个对象名(IntentDrivenObjectName)和一系列用于标识具体对象实例的属性(IntentDrivenObjectProperties)组成。因此，意图模型的形式化表达如下：
<intentExpression>:＝<IntentDrivenAction><IntentDrivenObject>
<IntentDrivenAction>:＝<IntentDrivenActionName><IntentDrivenActionProperties>
<IntentDrivenObject>:＝<IntentDrivenObjectName><IntentDrivenObjectProperties>
如图3所示的IDMS定义的意图分级示意图，IDMS给出了端到端(end-to-end)意图表达的通信业务消费者(communication service customer，CSC)、通信业务提供商(communication service provider，CSP)和网络运营商(network operator，NOP)三个层级。其中，CSC包括终端用户(end user)、中小企业、大型企业、垂直行业、其他CSP等。其中：
通信业务消费者的意图(intent-CSC)：只表达业务级的管理需求，不涉及业务和网络的实现细节。
通信业务提供商的意图(intent-CSP)：只表达网络级的管理需求，不涉及网络运营的专业知识。
网络运营商的意图(intent-NOP)：只表达网络资源级的管理需求，不涉及物理网络设备和虚拟化基础设施的操作细节，即EMS北向接口上传递的意图。
体验式网络智能(experiential networked intelligence，ENI)是行业规范工作组定义的 一种感知网络管理系统架构，运用人工智能和上下文感知等技术手段优化和调整网络运营。其包括输入处理和标准化功能模块(data ingestion&normalization FB)、输出生成和去标准化功能模块(output generation&denormalisation FB)、知识管理功能模块(knowledge management FB)、上下文感知功能模块(context awareness FB)、认知管理功能模块(cognition management FB)、状态感知功能模块(situational awareness FB)、策略管理功能模块(policy management FB)和模型驱动工程功能模块(model driven engineering FB)八个功能模块。本申请重点描述knowledge management FB。如图4所示的知识管理功能模块示意图，knowledge management FB用来管理至少四种数据和知识库(data and knowledge repository)，分别是数据库(data repository)、知识库(knowledge repository)、模型库(model repository)和黑板库(blackboard repository)。knowledge repository用来存储、操作、编辑和检索知识和智慧，knowledge repository会和context awareness FB、cognition management FB、situation awareness FB、model-driven engineering FB以及policy management FB进行交互。
如图5所示的基于意图策略(intent policy)的ENI架构示意图，提出基于intent policy的ENI架构，推动意图驱动网络架构标准化，对ENI原有架构进行了增强：
新增意图转译功能模块(intent translation FB):用来处理intent policy，包括intent policy意图转译、意图保障和生命周期管理。
增强knowledge management FB:将意图知识模型和意图知识数据分别存放在model repository和knowledge repository之中。
如图6所示的基于意图策略的ENI融合系统中的意图知识管理架构示意图，当前意图系统或者low-level意图系统具备意图知识管理功能和接口，支持外部系统如用户(user)/应用程序(application，APP)/运营支撑系统(operation support system，OSS)/运维支撑系统类似的系统(business support system-like，BSS-like)功能实体(Functionality)通过以下接口：E user-eni-kno、E app-eni-kno和E oss-eni-kno进行意图知识更新操作。外部系统可以对意图系统的knowledge repository中的意图知识进行新增、修改和删除。
意图系统的knowledge repository中存放的意图知识都有一个一一对应的意图关键词，用于标识该意图知识。该意图知识包括执行约束，以及intentOperations[executionConditon，operationType，operation]。意图知识库的operationType是一个枚举类型，其中，operationType的一个取值为“subintent”，表示对应的操作描述的是一个子意图下发的脚本，包括子意图的意图关键词。该子意图对应的意图知识在low-level意图系统的意图知识库中存在。
同时，high-level意图系统的意图知识库中会存放low-level意图系统的意图知识的意图关键词、IDO和IDA，这是high-level意图系统实现子意图下发的前提。如图1所示的分层部署的多级意图系统示意图，high-level意图系统收到意图下发命令后，由于意图对应的操作对象(如：网元)被不同的low-level意图系统管理，high-level意图系统会将意图进行分解，并向这些low-level意图系统发送分解后的子意图，同时low-level意图系统将意图达成情况反馈给high-level意图系统。
然而，在分层部署的多级意图系统中，不同层级的意图系统分层、分域，意图系统实行分域自治，外部系统无法对不同层级的意图系统都进行意图知识管理操作。所以，外部系统进行意图知识更新操作，只能对当前意图系统的knowledge repository中的意图知识进 行更新，并不能对与当前意图系统相关的上下级意图系统进行意图知识更新。这会导致更新后的意图知识可能会影响子意图的下发，是因为在意图知识更新后并没有对上下级意图系统的knowledge repository中的意图知识进行关联和更新，所以意图知识更新后意图系统子意图下发效率低下，甚至意图知识失效或者缺失。具体来讲，
low-level意图系统更新意图知识对high-level意图系统的影响：
1)low-level意图系统新增意图知识，而high-level意图系统中不存在这个意图，high-level意图系统无法将该意图作为high-level中的子意图进行意图分解和下发。
其中，low-level意图系统新增意图知识是指low-level意图系统的知识库中不存在该条意图，即没有Intentkeyword,IDA，IDO，constraint和intentOperations，新增意图知识包括新增的Intentkeyword,IDA和IDO及相应的constraint和intentOperations。如果知识库已存在意图关键词，而仅是新增constraint和intentOperations不属于此处low-level意图系统新增意图知识所指的范围。
2)low-level意图系统修改意图知识，该意图还可以作为high-level中的子意图，但会导致high-level中意图分解有偏差。
其中，low-level意图系统修改意图知识是指low-level意图系统知识库已存在该条意图，有Intentkeyword,IDA,IDO,constraint和intentOperations，但是修改了Intentkeyword/IDA/IDO。
例如，修改了IDO中的IntentDrivenObjectProperties的知识，原IntentDrivenObjectProperties为JinQiao，修改后的IntentDrivenObjectProperties为MinHang。
3)low-level意图系统删除意图知识，该意图仍然作为high-level中的子意图，导致high-level中子意图下发失败。
其中，low-level意图系统删除意图知识是指low-level意图系统知识库中存在该条意图，即有Intentkeyword,IDA，IDO，constraint和intentOperations，删除意图知识是指删除了Intentkeyword,IDA，IDO，constraint和intentOperations所有的知识。
high-level意图系统更新意图知识的影响：
high-level意图系统新增或者修改意图知识后，只能作为意图知识存在于high-level的knowledge repository中，不能与low-level意图系统的意图知识关联，导致不能实现意图分解和下发。
本申请提供一种意图系统间意图知识的关联方法及装置、系统，第一意图系统的第一意图的意图知识发生更新时，第二意图系统接收第一意图系统发送的意图知识更新通知，其中，意图知识更新通知包括更新类型和第一意图的意图关键词；第二意图系统根据意图知识更新通知，将第一意图的意图关键词对应的第一意图的意图知识与第二意图系统中的第二意图的意图知识进行关联，其中，第一意图是第二意图的子意图。从而可以在第一意图系统的第一意图的意图知识发生更新时，实现意图系统间意图知识的关联，避免第一意图的意图知识更新导致第二意图系统中第一意图的意图知识的缺失或者失效。
本申请涉及的功能模块描述如下：
·knowledge management FB：管理ENI范围内的所有知识，在本申请中完成intent knowledge repository FB中意图知识的查询、更新和存储。在本申请中增强了意图知识的关联功能。
·data ingestion and normalization FB：对外部系统的输入数据的获取和标准化等操作，在本申请中增强了意图系统之间的意图知识更新通知以及意图知识查询操作。
·output generation and demoralization FB：负责将系统内部命令转化为外部系统能够处理的格式并发送给外部系统，在本申请中增强了意图知识更新结果和意图知识查询结果的命令转化。
为此，如图7所示的本申请实施例提供的基于意图策略的ENI融合系统中的意图知识管理架构示意图，intent policy的ENI系统接口中新增了为了支持多级意图系统之间的知识管理的外部接口E eni-eni-kno。
本申请中的基于intent policy的ENI融合系统可以部署在运维支撑系统BSS上，或者部署在运营商的网络管理系统NMS的上，或者部署在网络设备商的网元管理系统EMS上，还可以部署在网元NE上。
部署了基于intent的ENI融合系统的网元支持对意图知识的查询、更新和存储功能，并且多级网元之间支持对更新意图知识的通知和查询功能。
下面对本申请实施例提供的意图系统间意图知识的关联方法进行详细描述：
如图8所示，为本申请实施例提供的一种意图系统间意图知识的关联方法的流程示意图，该方法可以包括以下步骤：
S101、第一意图系统确定其第一意图的意图知识发生更新。
在本实施例中，第一意图系统可以是low-level意图系统，第二意图系统可以是high-level意图系统。具体地，例如图3中，第一意图系统可以是CSP，第二意图系统可以是CSC；或者第一意图系统可以是CSC，第二意图系统可以是NOP。
外部系统(user/APP/OSS-/BSS-like)可以更新第一意图系统的第一意图的意图知识。具体地，第一意图系统的第一意图的意图知识发生更新，可以是第一意图系统新增、修改或删除第一意图的意图知识。该第一意图的意图知识是已经存在于或即将存储到第一意图系统的任一意图的意图知识。
S102、第一意图系统向第二意图系统发送意图知识更新通知，其中，意图知识更新通知包括更新类型和第一意图的意图关键词。相应地，第二意图系统接收第一意图系统发送的意图知识更新通知。
第一意图系统的意图知识的更新可能导致第二意图系统子意图知识缺失或者失效。对第一意图系统新增意图知识，第二意图系统无法进行子意图分解和下发，导致意图知识利用不够；对第一意图系统修改意图知识，第二意图系统可以进行子意图分解和下发，但是可能存在分解偏差，需要多次意图协商，导致效率低下；对第一意图系统删除意图知识，第二意图系统可以进行子意图分解和下发，但是第一意图系统无法实施该子意图。
本实施例中，当第一意图系统确定其第一意图的意图知识发生更新，向第二意图系统发送意图知识更新通知，以通知第二意图系统：第一意图系统的第一意图的意图知识发生了更新。该意图知识更新通知包括更新类型和第一意图的意图关键词。此外，如果是新增第一意图的意图知识，则该意图知识更新通知还可以包括第一意图的IDO和IDA；如果是修改第一意图的意图关键词/IDO/IDA中的至少一项，则该意图知识更新通知还可以包括修改前的第一意图的意图关键词和修改后的第一意图的意图关键词/IDO/IDA中的至少一项。
S103、第二意图系统根据意图知识更新通知，将第一意图的意图关键词对应的第一意图的意图知识与第二意图系统中的第二意图的意图知识进行关联，其中，第一意图是第二意图的子意图。
如前所述，如果第一意图系统新增第一意图的意图知识，而第二意图系统中不存在这个第一意图，第二意图系统无法将该第一意图作为第二意图系统中的子意图进行意图分解和下发。因此，当第一意图系统新增第一意图的意图知识，需要将该新增的第一意图的意图知识关联到第二意图系统中的第二意图的意图知识。
如果第一意图系统修改第一意图的意图知识，该第一意图还可以作为第二意图系统中的子意图，但会导致第二意图系统中的意图分解有偏差。因此，当第一意图系统修改第一意图的意图知识，需要根据修改的第一意图的意图知识重新与第二意图系统中的第二意图的意图知识进行关联。
如果第一意图系统删除第一意图的意图知识，该第一意图仍然作为第二意图系统中的子意图，导致第二意图系统中的子意图下发失败。因此，当第一意图系统删除第一意图的意图知识，需要将第一意图的意图知识与第二意图系统中的第二意图的意图知识去关联。
第二意图系统通过将第一意图的意图关键词对应的第一意图的意图知识与第二意图系统中的第二意图的意图知识进行关联，可以避免第一意图的意图知识更新导致第二意图系统中第一意图的意图知识的缺失或者失效。
可选地，还可以包括以下步骤：
S104、第二意图系统中的第二意图的意图知识发生更新，第二意图系统向至少一个第三意图系统发送意图知识能力查询请求，其中，意图知识能力查询请求包括以下至少一项信息：第二意图系统的标识、更新后的第二意图的意图关键词、意图驱动对象、意图驱动操作，其中，第一意图系统为至少一个第三意图系统中的其中一个意图系统。相应地，第一意图系统接收第二意图系统发送的意图知识能力查询请求。
外部系统(user/APP/OSS-/BSS-like)也可以更新第二意图系统中的第二意图的意图知识。外部系统更新第二意图系统中的意图的意图知识与更新第一意图系统中的意图的意图知识是独立的。具体地，第二意图系统的第二意图的意图知识发生更新，可以是第二意图系统新增或修改第二意图的意图知识。该第二意图的意图知识是已经存在于或即将存储到第二意图系统的任一意图的意图知识。
如前所述，第二意图系统新增或者修改第二意图的意图知识后，只能作为意图知识存在于第二意图系统的knowledge repository中，不能与第一意图系统的意图知识关联，导致不能实现意图分解和下发。
本实施例中，当第二意图系统更新第二意图的意图知识，第二意图系统向至少一个第三意图系统发送意图知识能力查询请求，以请求查询至少一个第三意图系统中与该更新的第二意图的意图知识关联的第一意图的意图知识。
S105、第一意图系统查找到与更新后的第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项关联的第一意图的意图知识。
第一意图系统根据接收到的意图知识能力查询请求携带的更新后的第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项，查找与更新后的第二意图的意图关键 词、意图驱动对象、意图驱动操作中的至少一项关联的第一意图的意图知识。
S106、第一意图系统向第二意图系统发送意图知识能力查询响应，意图知识能力查询响应包括以下至少一项信息：第二意图系统的标识、至少一个第三意图系统的标识、至少一个第三意图系统中的第一意图的意图知识。相应地，第二意图系统接收至少一个第三系统意图发送的意图知识能力查询响应。
第一意图系统将查询到的关联的第一意图的意图知识反馈给第二意图系统。
S107、第二意图系统将至少一个第三意图系统中的第一意图的意图知识与更新后的第二意图的意图关键词、意图驱动对象、意图驱动操作进行关联。
具体地，若第二意图系统新增意图知识，上述意图知识能力查询请求包括新增的第二意图的Intentkeyword，IDA和IDO；第一意图系统根据第二意图系统中新增的第二意图的Intentkeyword，IDA和IDO，在第一意图系统中查询到相关的第一意图的意图知识；第二意图系统将第一意图的意图知识与新增的第二意图的Intentkeyword，IDA和IDO中的至少一项进行关联。
具体地，若第二意图系统修改第二意图的Intentkeyword，上述意图知识能力查询请求包括修改后的第二意图的Intentkeyword；第一意图系统根据修改后的第二意图的Intentkeyword查询到第一意图的Intentkeyword；第二意图系统将修改后的第二意图的Intentkeyword与第一意图的Intentkeyword进行关联。
若第二意图系统修改第二意图的IDO/IDA，上述意图知识能力查询请求包括修改后的第二意图的IDO/IDA；第一意图系统根据修改后的第二意图的IDO/IDA查询到第一意图的IDO/IDA；第二意图系统将修改后的第二意图的IDO/IDA第一意图的IDO/IDA进行关联。
通过第二意图系统将至少一个第三意图系统中的第一意图的意图知识与更新后的第二意图的意图关键词、意图驱动对象、意图驱动操作进行关联，可以避免第二意图的意图知识更新无法与第二意图系统中第一意图的意图知识进行关联，无法实现意图分解和下发。
根据本申请实施例提供的一种意图系统间意图知识的关联方法，可以在第一意图系统的第一意图的意图知识发生更新或者第二意图系统的第二意图的意图知识发生更新时，实现意图系统间意图知识的关联，避免第一意图的意图知识更新导致第二意图系统中第一意图的意图知识的缺失或者失效，或者避免第二意图的意图知识更新无法与第二意图系统中第一意图的意图知识进行关联，无法实现意图分解和下发。
下面图9～图12对应low-level意图系统进行意图知识更新，告知high-level意图系统知识库的场景。
如图9所示，为本申请实施例提供的又一种意图系统间意图知识的关联方法的流程示意图。在该实施例中，low-level意图系统新增意图知识，通过订阅—通知的方式告知high-level意图系统。具体地，该方法可以包括以下步骤：
步骤S201～S202、high-level意图系统的knowledge management FB向low-level意图系统向发送意图知识更新订阅请求updateKnowledgeSubscription(consumerReference,filter)，其中consumerReference是high-level意图系统的标识，filter(即更新类型)是订阅通知的过滤条件(filter constraint)，包含[增加(add)，修改(modify)，删除(delete)]。
步骤203、low-level意图系统的data ingestion and normalization FB对接收到的消息进 行格式转换并发送updateKnowledgeSubscription到knowledge management FB。
步骤204、low-level意图系统的knowledge management FB根据updateKnowledgeSubscription启动订阅并分配订阅标识(SubscriptionID)。
步骤S205～S207、low-level意图系统的knowledge management FB向high-level意图系统发送意图知识更新订阅响应updateKnowledgeSubscription Response(SubscriptionID,status)，携带SubscriptionID和status。其中，SubscriptionID是low-level意图系统的订阅标识，status是否成功启动订阅的状态(简称订阅状态)。
步骤S208～S212、外部系统(user/APP/OSS-/BSS-like)向low-level意图系统新增意图知识。其中携带更新类型(新增)、意图关键词、意图知识。
如果low-level意图系统新增意图知识成功：
步骤S213～S215、low-level意图系统的knowledge management FB向high-level意图系统的knowledge management FB发送意图知识更新通知updateKnowledgeNotification(SubscriptionID,add,intentkeyword,IDO,IDA)，其中SubscriptionID是low-level意图系统的订阅标识，add是low-level意图系统新增意图知识标识，intentkeyword,IDO和IDA表示low-level意图系统新增的意图知识。
步骤S216、high-level意图系统的knowledge management FB将low-level意图系统中新增的意图知识增加到knowledge repository中，并将其作为子意图和自身意图知识进行子意图知识关联。
具体地，high-level意图系统根据新增的意图知识(第一意图知识)中的IDO和IDA，在high-level意图系统中查询到第二意图的意图知识(第二意图是high-level意图系统的意图)，其中，第一意图的IDO包含在第二意图的IDO内，和/或第一意图的IDA包含在第二意图的IDA中，即第一意图在high-level意图系统中以子意图形式存在。high-level意图系统将第一意图的intentkeyword，IDO和IDA与第二意图的意图知识进行关联。
在该实施例中，low-level意图系统新增意图知识后可以通知high-level意图系统，从而使得新增的意图知识能够作为子意图存在于high-level意图系统的knowledge repository中，可以增强high-level意图系统的意图分解下发能力。
融合系统与意图系统间接口上新增意图知识更新订阅操作，在low-level意图系统新增意图知识后通过意图知识更新通知反馈新增的意图知识。
融合系统内部新增子意图知识关联功能，将low-level意图系统新增的意图知识关联到high-level意图系统的意图知识上作为子意图存在。
如图10所示，为本申请实施例提供的又一种意图系统间意图知识的关联方法的流程示意图。在该实施例中，low-level意图系统修改/删除意图知识，通过订阅—通知的方式告知high-level意图系统知识库。具体地，该方法可以包括以下步骤：
步骤301～307、参考图9所示实施例的步骤S201～S207。
步骤S308～S312、外部系统(user/APP/OSS-/BSS-like)指示low-level意图系统更新意图知识。其中携带更新类型(修改/删除)、意图关键词、意图知识。
如果low-level意图系统更新意图知识成功：
如果low-level意图系统对原有意图知识进行删除：
步骤S313～S315、low-level意图系统的knowledge management FB向high-level意图系统的knowledge management FB发送意图知识更新通知updateKnowledgeNotification(SubscriptionID,delete,intentkeyword),其中SubscriptionID是low-level意图系统分配的订阅标识，delete是low-level意图系统删除意图知识，intentkeyword表示low-level意图系统删除的意图知识。
步骤S316、high-level意图系统将low-level意图系统中删除的意图知识也在knowledge repository中删除。
具体地，high-level意图系统根据low-level意图系统中删除的意图知识(第一意图的意图知识)的intentkeyword，在high-level意图系统中查找与该intentkeyword对应的第一意图的意图知识。high-level意图系统删除查找到的第一意图的意图知识。
如果low-level意图系统对原有意图知识进行修改：
步骤S317～S319、low-level意图系统的knowledge management FB向high-level意图系统的knowledge management FB发送意图知识更新通知updateKnowledgeNotification(SubscriptionID,modify,intentkeywordbefore,intentkeywordafter)，modify是low-level意图系统更改意图知识标识，如果是修改意图关键词，则intentkeywordbefore是更改前的意图intentkeyword，intentkeywordafter是更改后的意图intentkeyword；如果是修改IDO/IDA，则意图知识更新通知包括意图关键词，intentkeywordbefore是更改前的IDO/IDA，intentkeywordafter是更改后的IDO/IDA。
步骤S320、high-level意图系统将low-level意图系统中更改的意图知识更改到knowledge repository中，并和自身意图知识进行子意图知识关联。
具体地，若意图知识更新通知中包括的更新类型为修改low-level意图系统中的原有意图知识(第一意图的意图知识)，该修改包括修改第一意图的意图知识中的意图关键词、IDO、IDA中的一项或多项。因此，high-level意图系统根据具体的修改内容执行以下至少一种操作：
low-level意图系统修改原有意图知识的意图关键词，则意图知识更新通知包括修改前第一意图的意图关键词和修改后的第一意图的意图关键词，high-level意图系统根据该修改前的第一意图的意图关键词，在high-level意图系统的意图知识库中查找与该修改前的第一意图的意图关键词对应的第一意图的意图知识，该第一意图在high-level意图系统中作为子意图存在。high-level意图系统将修改后的第一意图的意图关键词替换第一意图的意图知识中的该修改前的意图关键词；
low-level意图系统修改原有意图知识的IDO/IDA，则意图知识更新通知包括第一意图的意图关键词、修改前的第一意图的IDO/IDA和修改后的第一意图的IDO/IDA，high-level意图系统根据修改后的第一意图的IDO/IDA，在high-level意图系统的意图知识库中查找到high-level意图系统的第二意图的意图知识，修改后的第一意图的IDO包含在第二意图的IDO内，和/或修改后的第一意图的IDA包含在第二意图的IDA内，即第一意图在high-level意图系统以子意图形式存在。high-level意图系统将修改后的第一意图的IDO/IDA与第二意图的意图知识关联。例如，第一意图的修改前的IDO中的IntentDrivenObjectProperties是Lujiazui，第一意图的修改后的IDO中的IntentDrivenObjectProperties是Xujiahui，第二意图 的IDO中的IntentDrivenObjectProperties是Xuhui，即修改后的第一意图的IDO包含在第二意图的IDO中，将第一意图的修改后的IDO与第二意图的意图知识关联。
进一步地，high-level意图系统根据修改前的第一意图的IDO/IDA，在high-level意图系统中查询到第三意图的意图知识，其中，修改前的第一意图的IDO包含在第三意图的IDO内，和/或修改前的第一意图的IDA包含在第三意图的IDA中。high-level意图系统将修改前的第一意图的IDO/IDA与第三意图的意图知识去关联。例如，在上述示例中，第三意图的IDO中的IntentDrivenObjectProperties是Pudong，第一意图的修改前的IDO包含在第三意图的IDO中，则将第一意图的修改前的IDO与第三意图的意图知识去关联。
在本实施例中，low-level意图系统修改/删除意图知识后可以通知high-level意图系统。从而使得修改后的意图知识在high-level意图系统的knowledge repository中也进行子意图修改并关联，避免在high-level意图系统意图分解和下发时候的子意图知识失效或者意图分解效率低下；使得删除后的意图知识在high-level意图系统的knowledge repository中也进行子意图删除，避免在high-level意图系统意图分解时候的意图下发失败。
融合系统与融合系统间接口上新增意图知识更新订阅操作，在low-level意图系统修改/删除意图知识后通过意图知识更新通知反馈修改/删除的意图知识。
融合系统内部新增子意图知识修改和删除、关联功能。对low-level意图系统修改的意图知识进行修改前后的high-level意图系统意图知识的修改、去关联和重新关联；对low-level意图系统删除的意图知识进行删除后的high-level意图系统意图知识的删除和去关联。
如图11所示，为本申请实施例提供的又一种意图系统间意图知识的关联方法的流程示意图。在该实施例中，low-level意图系统新增意图知识，通过直接上报的方式告知high-level意图系统知识库。具体地，该方法可以包括以下步骤：
步骤S401～S405、外部系统(user/APP/OSS-/BSS-like)向low-level意图系统新增意图知识。其中携带更新类型(新增)、意图关键词、意图知识。
如果low-level意图系统新增意图知识成功：
步骤S406～S408、low-level意图系统的knowledge management FB向high-level意图系统的knowledge management FB发送意图知识更新上报updateKnowledgeReport(producerReference,add,intentkeyword,IDO,IDA)(也可以称为意图知识更新通知)，其中producerReference是low-level意图系统的标识，add是low-level意图系统新增意图知识，intentkeyword,IDO和IDA表示low-level意图系统新增的意图知识。
S409、high-level意图系统的knowledge management FB将low-level意图系统中新增的意图知识增加到自身的knowledge repository中，并作为子意图和自身意图知识进行子意图知识关联。
具体的实现过程可参考图9所示实施例的步骤S216。
S410～S412、high-level意图系统向low-level意图系统发送意图知识上报响应updateKnowledgeReport Response(status)(也可以称为意图知识更新响应)，其中status表示high-level意图系统的knowledge repository是否进行了add操作。
在本实施例中，low-level意图系统新增意图知识后可以直接上报high-level意图系统，从而使得新增的意图知识能够作为子意图存在于high-level意图系统的knowledge repository 中，可以增强high-level意图系统的意图分解和下发能力。
融合系统与融合系统间接口上新增意图知识更新上报操作，在low-level意图系统新增意图知识后将新增的意图知识直接上报给high-level意图系统，不需要high-level意图系统事先发送订阅通知。
融合系统内部新增子意图知识关联功能，将low-level意图系统新增意图知识关联到high-level意图系统的意图知识上作为子意图存在。
如图12所示，为本申请实施例提供的又一种意图系统间意图知识的关联方法的流程示意图。在该实施例中，low-level意图系统修改/删除意图知识，通过直接上报的方式告知high-level意图系统知识库。具体地，该方法可以包括以下步骤：
步骤S501～S505、外部系统(user/APP/OSS-/BSS-like)指示low-level意图系统更新意图知识。其中携带更新类型(修改/删除)、意图关键词、意图知识。
如果low-level意图系统更新意图知识成功：
如果low-level意图系统对原有意图知识进行删除：
步骤S506～508、low-level意图系统的knowledge management FB向high-level意图系统的knowledge management FB发送意图知识更新上报updateKnowledgeReport(producerReference,delete,intentkeyword),其中producerReference是low-level意图系统标识，delete是low-level意图系统删除意图知识，intentkeyword表示low-level意图系统删除的意图知识。
步骤S509、high-level意图系统将low-level意图系统中删除的意图知识也在knowledge repository中删除。
具体实现可参考图10所示实施例的步骤S316。
步骤S510～S512、high-level意图系统向low-level意图系统发送updateKnowledgeReport Response(delete,status)，其中status表示high-level意图系统的knowledge repository是否进行了delete操作。
如果low-level意图系统对原有意图知识进行修改：
步骤S513～S515、low-level意图系统的knowledge management FB向high-level意图系统的knowledge management FB发送意图知识更新上报updateKnowledgeReport(producerReference,modify,intentkeywordbefore,intentkeywordafter)，modify是low-level意图系统更改意图知识标识，intentkeywordbefore是更改前的意图intentkeyword,IDO和IDA，intentkeywordafter是更改后的意图intentkeyword,IDO和IDA。
步骤S516、high-level意图系统将low-level意图系统中更改的意图知识更改到knowledge repository中，并和自身意图知识进行子意图知识关联。
具体实现可参考图10所示实施例的步骤S320。
步骤S517～S519、high-level意图系统向low-level意图系统发送updateKnowledgeReport Response(modify,status)，其中status表示high-level意图系统的knowledge repository是否进行了modify操作。
在本实施例中，low-level意图系统修改/删除意图知识后可以直接上报给high-level意图系统。从而使得修改后的意图知识在high-level意图系统的knowledge repository中也进 行子意图修改并关联，避免在high-level意图系统意图分解和下发时候的子意图知识失效或者意图分解效率低下；使得删除后的意图知识在high-level意图系统的knowledge repository中也进行子意图删除，避免在high-level意图系统意图分解时候的意图下发失败。
融合系统与融合系统间接口新增意图知识更新上报操作，在low-level意图系统修改/删除意图知识后直接上报给high-level意图系统，不需要high-level意图系统事先发送订阅通知。
融合系统内部新增子意图知识修改和删除、关联功能。对low-level意图系统修改的意图知识进行修改前后的high-level意图系统意图知识的修改、去关联和重新关联；对low-level意图系统删除的意图知识进行删除后的high-level意图系统意图知识的删除和去关联。
下面图13和图14所示实施例对应high-level意图系统进行意图知识更新，查询low-level意图系统知识库的场景。
如图13所示，为本申请实施例提供的又一种意图系统间意图知识的关联方法的流程示意图。在该实施例中，high-level意图系统新增意图知识，查询所有low-level意图系统知识库。具体地，该方法可以包括以下步骤：
步骤S601～S605、外部系统(user/APP/OSS-/BSS-like)指示high-level意图系统新增/修改意图知识。
如果high-level意图系统新增/修改意图知识成功：
步骤S606～S607、high-level意图系统向其下面的所有的low-level意图系统(称为第三意图系统)发送意图知识能力查询请求queryKnowledgeCapacity(consumerReference,Intentkeyword,IDO,IDA)。其中，Intentkeyword，IDO,IDA为步骤S603根据步骤S601内容新增/修改的意图知识。
步骤S608、每个low-level意图系统的知识管理模块根据Intentkeyword,IDO,IDA查询相关/关联的意图知识RelatedIntentknowledge。RelatedIntentknowledge为low-level意图系统中根据high-level意图系统中新增/修改的Intentkeyword,IDO和IDA查询得到的相关子意图知识，包含子意图知识的intentkeyword,IDO,IDA。
步骤S609～S611、high-level意图系统向low-level意图系统发送意图知识能力查询回应queryKnowledgeCapacity Response(consumerReference,Intentkeyword,RelatedInten--tknowledge)。Intentkeyword是high-level意图系统知识，RelatedIntentknowledge是low-level意图系统知识。
步骤S612、high-level意图系统将RelatedIntentknowledge更新到knowledge repository中，并和自身意图知识进行子意图知识关联。
具体地，若high-level意图系统新增意图知识，上述意图知识能力查询请求包括新增的第二意图的Intentkeyword，IDA和IDO；low-level意图系统根据high-level意图系统中新增的第二意图的Intentkeyword，IDA和IDO，在low-level意图系统中查询到相关的第一意图的意图知识；high-level意图系统将第一意图的意图知识与新增的第二意图的Intentkeyword，IDA和IDO中的至少一项进行关联。
具体地，若high-level意图系统修改第二意图的Intentkeyword，上述意图知识能力查询请求包括修改后的第二意图的Intentkeyword；low-level意图系统根据修改后的第二意图的 Intentkeyword查询到第一意图的Intentkeyword；high-level意图系统将修改后的第二意图的Intentkeyword与第一意图的Intentkeyword进行关联。
若high-level意图系统修改第二意图的IDO/IDA，上述意图知识能力查询请求包括修改后的第二意图的IDO/IDA；low-level意图系统根据修改后的第二意图的IDO/IDA查询到第一意图的IDO/IDA；high-level意图系统将修改后的第二意图的IDO/IDA第一意图的IDO/IDA进行关联。
在该实施例中，high-level意图系统新增/修改意图知识后查询low-level意图系统相关意图知识，从而使得low-level意图系统中的意图知识作为子意图知识新增/修改在high-level意图系统中，high-level意图系统可以对新增/修改的意图知识进行意图分解和下发。
融合系统与融合系统间接口上新增意图知识能力查询操作，在high-level意图系统新增意图知识后通过该操作查询low-level意图系统的意图知识。
融合系统内部新增子意图知识关联功能，将查询得到的low-level意图系统的意图知识作为子意图关联到high-level意图系统新增的意图知识上。
如图14所示，为本申请实施例提供的又一种意图系统间意图知识的关联方法的流程示意图。在该实施例中，high-level意图系统新增意图知识，查询部分low-level意图系统知识库(需要决定对哪些low-level意图系统知识库进行查询)。
high-level意图系统需要根据子意图知识确定对哪些low-level意图系统进行查询，确定list。high-level意图系统中的子意图知识(low-level意图系统的意图知识)包括Intentkeyword,IDO和IDA，而IDO和IDA的总称形式如下，包括意图作用的“动作”和“对象”：
<IntentDrivenAction>:＝<IntentDrivenActionName><IntentDrivenActionProperties>
<IntentDrivenObject>:＝<IntentDrivenObjectName><IntentDrivenObjectProperties>
从而根据high-level意图系统新增的意图知识的IDO以及已存在的子意图知识的IDO进行low-level意图系统的筛选，只查询符合新增意图知识IDO范围内的low-level意图系统，确定low-level意图系统的列表list的方法和步骤如下：
1.high-level意图系统中新增意图知识，包括Intentkeyword1，IDO1，IDA1，constraint1和intentOperations1[executionConditon,operationType,operation]。
2.high-level意图系统根据IDO1中的IntentDrivenObjectName1和IntentDrivenObjectProperties1查找已有的子意图知识的IntentDrivenObjectName2和IntentDrivenObjectProperties2，如果IntentDrivenObjectName2和IntentDrivenObjectProperties2在IntentDrivenObjectName1和IntentDrivenObjectProperties1的范围内，则将该IntentDrivenObjectName2和IntentDrivenObjectProperties2对应的low-level意图系统放入list中。
例如：IntentDrivenObjectProperties1中是Pudong,若IntentDrivenObjectProperties2是Jinqiao，则IntentDrivenObjectProperties2对应的low-level意图系统放入list中；若IntentDrivenObjectProperties2是Minhang，则IntentDrivenObjectProperties2对应的low-level意图系统不需要放入list中。
当然，也根据high-level意图系统新增的意图知识的IDA以及已存在的子意图知识的IDA进行low-level意图系统的筛选。
具体地，该方法可以包括以下步骤：
步骤S701～S705、参考图13所示的实施例的步骤S601～S605。
如果high-level意图系统新增/修改意图知识成功：
步骤S706、high-level意图系统根据新增/修改意图知识的Intentkeyword,IDO和IDA确定需要查询的low-level意图系统的列表list。
步骤S707～S709、high-level意图系统向在list内的low-level意图系统发送意图知识能力查询请求queryKnowledgeCapacity(consumerReference,Intentkeyword,IDO,IDA)。Intentkeyword，IDO,IDA为步骤S703根据步骤S701的内容high-level意图系统新增/修改的意图知识。
步骤S710、low-level意图系统的知识管理模块根据Intentkeyword,IDO,IDA查询相关的意图知识RelatedIntentknowledge。RelatedIntentknowledge为low-level意图系统中根据high-level意图系统中新增/修改的Intentkeyword,IDO和IDA查询得到的相关子意图知识，包含子意图知识的intentkeyword,IDO,IDA。
步骤S711～S713、low-level意图系统向high-level意图系统发送意图知识能力回应queryKnowledgeCapacity Response(consumerReference,Intentkeyword,RelatedInten--tknowledge)。Intentkeyword是high-level意图系统新增/修改的意图知识，RelatedIntentknowledge是low-level意图系统查询的意图知识。
步骤S714、high-level意图系统将RelatedIntentknowledge更新到knowledge repository中，并和自身意图知识进行子意图知识关联。
在该实施例中，high-level意图系统新增/修改意图知识后，根据low-level意图系统list查询low-level意图系统相关意图知识，从而使得low-level意图系统中的意图知识作为子意图知识新增/修改在high-level意图系统中，high-level意图系统可以对新增/修改的意图知识进行意图分解和下发。
融合系统与融合系统间接口上新增意图知识能力查询操作，在high-level意图系统新增意图知识后通过该操作查询low-level意图系统的意图知识。
融合系统内部新增low-level意图系统查询list确定功能。
融合系统内部新增子意图知识关联功能，将查询得到的low-level意图系统的意图知识作为子意图关联到high-level意图系统新增的意图知识上。
基于上述意图系统间意图知识的关联方法的同一构思，本申请还提供了以下通信装置：
如图15所示，为本申请实施例提供的一种通信装置的结构示意图，该通信装置可以是上述第二意图系统，或第二意图系统中的一个模块。该通信装置100包括：收发单元11和处理单元12；其中：
收发单元11，用于第一意图系统的第一意图的意图知识发生更新时，接收所述第一意图系统发送的意图知识更新通知，其中，所述意图知识更新通知包括更新类型和所述第一意图的意图关键词；以及处理单元12，用于根据所述意图知识更新通知，将所述第一意图的意图关键词对应的所述第一意图的意图知识与第二意图系统中的第二意图的意图知识进行关联，其中，所述第一意图是所述第二意图的子意图。
在一种可能的实现中，收发单元11，还用于向所述第一意图系统发送意图知识更新订 阅请求，所述意图知识更新订阅请求包括所述第二意图系统的标识和更新类型；以及收发单元11，还用于接收所述第一意图系统发送的意图知识更新订阅响应，所述意图知识更新订阅响应包括以下至少一项信息：订阅标识，订阅状态；其中，所述意图知识更新通知还包括所述订阅标识。
在又一种可能的实现中，所述意图知识更新通知还包括所述第一意图系统的标识，收发单元11，还用于向所述第一意图系统发送意图知识更新响应。
在又一种可能的实现中，所述更新类型为新增所述第一意图的意图知识，所述意图知识更新通知还包括所述第一意图的意图驱动对象和意图驱动操作；处理单元12，用于根据所述第一意图的意图驱动对象和意图驱动操作，在所述第二意图系统中查询到所述第二意图的意图知识，其中，所述第一意图的意图驱动对象包含在所述第二意图的意图驱动对象内，和/或所述第一意图的意图驱动操作包含在所述第二意图的意图驱动操作中；以及处理单元12，还用于将所述第一意图的意图关键词、所述意图驱动对象和所述意图驱动操作与所述第二意图的意图知识进行关联。
在又一种可能的实现中，所述更新类型为删除所述第一意图的意图知识，处理单元12，用于根据所述第一意图的意图关键词，在所述第二意图系统中查找与所述第一意图的意图关键词对应的所述第一意图的意图知识；以及处理单元12，还用于删除查找到的所述第一意图的意图知识。
在又一种可能的实现中，所述更新类型为修改所述第一意图的意图知识，所述意图知识更新通知还包括以下至少一项信息：修改前的所述第一意图的关键词、修改前的所述第一意图的意图驱动对象、修改前的所述第一意图的意图驱动操作、修改后的所述第一意图的关键词、修改后的所述第一意图的意图驱动对象、修改后的所述第一意图的意图驱动操作；处理单元12，用于执行以下至少一种操作：所述第一意图系统修改所述第一意图的意图关键词后，根据修改前的所述第一意图的意图关键词，在所述第二意图系统中查找与所述修改前的所述第一意图的意图关键词对应的所述第一意图的意图知识，将所述修改后的所述第一意图的意图关键词替换所述第一意图的意图知识中的所述修改前的所述第一意图的意图关键词；所述第一意图系统修改所述第一意图的意图驱动对象和/或意图驱动操作后，根据所述修改后的所述第一意图的意图驱动对象和/或意图驱动操作，在所述第二意图系统中查询到所述第二意图的意图知识，其中，所述修改后的所述第一意图的意图驱动对象包含在所述第二意图的意图驱动对象内，和/或所述修改后的所述第一意图的意图驱动操作包含在所述第二意图的意图驱动操作中；将所述修改后的所述第一意图的意图驱动对象和/或意图驱动操作与所述第二意图的意图知识关联。
在又一种可能的实现中，处理单元12，还用于根据所述修改前的所述第一意图的意图驱动对象和/或意图驱动操作，在所述第二意图系统中查询到第三意图的意图知识，其中，所述修改前的所述第一意图的意图驱动对象包含在所述第三意图的意图驱动对象内，和/或所述修改前的所述第一意图的意图驱动操作包含在所述第三意图的意图驱动操作中；处理单元12，还用于将所述修改前的所述第一意图的意图驱动对象和/或意图驱动操作与所述第三意图的意图知识去关联。
在又一种可能的实现中，收发单元11，还用于所述第二意图的意图知识发生更新，向 至少一个第三意图系统发送意图知识能力查询请求，其中，所述意图知识能力查询请求包括以下至少一项信息：所述第二意图系统的标识、更新后的所述第二意图的意图关键词、意图驱动对象、意图驱动操作，其中，所述第一意图系统为所述至少一个第三意图系统中的其中一个意图系统；收发单元11，还用于接收所述至少一个第三系统意图发送的意图知识能力查询响应，所述意图知识能力查询响应包括以下至少一项信息：所述第二意图系统的标识、所述至少一个第三意图系统的标识、与更新后的所述第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项关联的第一意图的意图知识；以及处理单元12，还用于将所述第一意图的意图知识与更新后的所述第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项进行关联。
在又一种可能的实现中，更新类型为修改所述第二意图的意图知识，处理单元12，还用于执行以下至少一种操作：所述第二意图系统修改所述第二意图的意图关键词后，将修改后的所述第二意图的意图关键词与所述第一意图的意图关键词进行关联；或所述第二意图系统修改所述第二意图的意图驱动对象和/或意图驱动操作后，将修改后的所述第二意图的意图驱动对象和/或意图驱动操作与所述第一意图的意图驱动对象和/或意图驱动操作进行关联。
在又一种可能的实现中，处理单元12，还用于根据修改前的所述第二意图的意图驱动对象和/或意图驱动操作，在所述第二意图系统中查询到所述至少一个第三意图系统中的第四意图的意图知识，其中，所述修改前的所述第二意图的意图驱动对象包含所述第四意图的意图驱动对象，和/或所述修改前的所述第二意图的意图驱动操作包含所述第四意图的意图驱动操作；以及处理单元12，还用于将所述修改前的所述第二意图的意图驱动对象和/或意图驱动操作与所述第四意图的意图知识去关联。
在又一种可能的实现中，处理单元12，还用于根据更新后的所述第二意图的所述意图驱动对象，确定所述至少一个第三意图系统，其中，所述至少一个第三意图系统中的所述第一意图的意图驱动对象包含在更新后的所述第二意图的意图驱动对象内。
有关上述收发单元11和处理单元12的具体实现可参考图8～图14中第二意图系统的相关描述。
根据本申请实施例提供的一种通信装置，可以在第一意图系统的第一意图的意图知识发生更新或者第二意图系统的第二意图的意图知识发生更新时，实现意图系统间意图知识的关联，避免第一意图的意图知识更新导致第二意图系统中第一意图的意图知识的缺失或者失效，或者避免第二意图的意图知识更新无法与第二意图系统中第一意图的意图知识进行关联，无法实现意图分解和下发。
如图16所示，为本申请实施例提供的又一种通信装置的结构示意图，该通信装置可以是上述第一意图系统，或第一意图系统中的一个模块。该通信装置200包括：处理单元21和收发单元22；其中：
处理单元21，用于确定第一意图系统的第一意图的意图知识发生更新；以及收发单元22，用于向第二意图系统发送意图知识更新通知，以使第二意图系统根据所述意图知识更新通知，将所述第一意图的意图关键词对应的所述第一意图的意图知识与所述第二意图系统中的第二意图的意图知识进行关联，其中，所述第一意图是所述第二意图的子意图，所 述意图知识更新通知包括更新类型和所述第一意图的意图关键词。
在一种可能的实现中，收发单元22，还用于接收所述第二意图系统发送的意图知识更新订阅请求，所述意图知识更新订阅请求包括所述第二意图系统的标识和更新类型；以及收发单元22，还用于向所述第二意图系统发送意图知识更新订阅响应，所述意图知识更新订阅响应包括以下至少一项信息：订阅标识，订阅状态；其中，所述意图知识更新通知还包括所述订阅标识。
在又一种可能的实现中，收发单元22，还用于接收所述第二意图系统发送的意图知识更新响应。
在又一种可能的实现中，所述更新类型包括以下至少一种：新增所述第一意图的意图知识、删除所述第一意图的意图知识、修改所述第一意图的意图知识；若所述更新类型为新增所述第一意图的意图知识，所述意图知识更新通知还包括所述第一意图的意图驱动对象和意图驱动操作；若所述更新类型为修改所述第一意图的意图知识，所述意图知识通知还包括以下至少一项信息：修改前的所述第一意图的关键词、修改前的所述第一意图的意图驱动对象、修改前的所述第一意图的意图驱动操作、修改后的所述第一意图的关键词、修改后的所述第一意图的意图驱动对象、修改后的所述第一意图的意图驱动操作。
在又一种可能的实现中，收发单元22，还用于所述第二意图的意图知识发生更新，接收所述第二意图系统发送的意图知识能力查询请求，所述意图知识能力查询请求包括以下至少一项信息：所述第二意图系统的标识、更新后的第二意图的意图关键词、意图驱动对象、意图驱动操作，其中，所述第一意图系统为所述至少一个第三意图系统中的其中一个意图系统；处理单元21，用于查找到与所述更新后的第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项关联的所述第一意图的意图知识；以及收发单元22，还用于向所述第二意图系统发送意图知识能力查询响应，所述意图知识能力查询响应包括以下至少一项信息：所述第二意图系统的标识、所述至少一个第三意图系统的标识、所述第一意图的意图知识。
有关上述处理单元21和收发单元22的具体实现可参考图8～图14中第一意图系统的相关描述。
根据本申请实施例提供的一种通信装置，可以在第一意图系统的第一意图的意图知识发生更新或者第二意图系统的第二意图的意图知识发生更新时，实现意图系统间意图知识的关联，避免第一意图的意图知识更新导致第二意图系统中第一意图的意图知识的缺失或者失效，或者避免第二意图的意图知识更新无法与第二意图系统中第一意图的意图知识进行关联，无法实现意图分解和下发。
如图17所示，还提供了一种通信装置的结构示意图，该通信装置用于执行上述通信方法。上述方法中的部分或全部可以通过硬件来实现，也可以通过软件或固件来实现。
可选的，该通信装置在具体实现时可以是芯片或者集成电路。
可选的，当上述实施例的通信方法中的部分或全部通过软件或固件来实现时，可以通过图17提供的一种通信装置300来实现。如图17所示，该通信装置300可包括：
存储器33和处理器34(装置中的处理器34可以是一个或多个，图17中以一个处理器为例)，还可以包括输入装置31、输出装置32。在本实施例中，输入装置31、输出装置 32、存储器33和处理器34可通过总线或其它方式连接，其中，图17中以通过总线连接为例。
其中，在一个实施例中，处理器34用于执行图8～图14中第一意图系统所执行的方法步骤。
在另一个实施例中，处理器34用于执行图8～图14中第二意图系统所执行的方法步骤。
可选的，上述通信方法的程序可以存储在存储器33中。该存储器33可以是物理上独立的单元，也可以与处理器34集成在一起。该存储器33也可以用于存储数据。
可选的，当上述实施例的通信方法中的部分或全部通过软件实现时，该通信装置也可以只包括处理器。用于存储程序的存储器位于该通信装置之外，处理器通过电路或电线与存储器连接，用于读取并执行存储器中存储的程序。
处理器可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)，或WLAN设备。
处理器还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。
存储器可以包括易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)；存储器也可以包括非易失性存储器(non-volatile memory)，例如快闪存储器(flash memory)，硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)；存储器还可以包括上述种类的存储器的组合。
本领域技术人员应明白，本公开一个或多个实施例可提供为方法、系统或计算机程序产品。因此，本公开一个或多个实施例可采用完全硬件实施例、完全软件实施例或结合软件和硬件方面的实施例的形式。而且，本公开一个或多个实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请实施例还提供了一种芯片系统，包括：至少一个处理器和接口，该至少一个处理器通过接口与存储器耦合，当该至少一个处理器执行存储器中的计算机程序或指令时，使得上述任一方法实施例中的方法被执行。可选的，该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
本申请实施例还提供一种计算机可读存储介质，该存储介质上可以存储有计算机程序，所述程序被处理器执行时实现本公开任一实施例描述的方法的步骤。
本申请实施例还提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行本公开任一实施例描述的方法的步骤。
本申请实施例还提供一种通信系统，该通信系统包括上述的通信装置。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
应理解，在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关 系，例如，A/B可以表示A或B；其中A，B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。同时，在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，该单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如，多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。所显示或讨论的相互之间的耦合、或直接耦合、或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行该计算机程序指令时，全部或部分地产生按照本申请实施例的流程或功能。该计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。该计算机指令可以存储在计算机可读存储介质中，或者通过该计算机可读存储介质进行传输。该计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。该计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。该可用介质可以是只读存储器(read-only memory，ROM)，或随机存取存储器(random access memory，RAM)，或磁性介质，例如，软盘、硬盘、磁带、磁碟、或光介质，例如，数字通用光盘(digital versatile disc，DVD)、或者半导体介质，例如，固态硬盘(solid state disk，SSD)等。

Claims (35)

  1. 一种意图系统间意图知识的关联方法，其特征在于，所述方法包括：
    第一意图系统的第一意图的意图知识发生更新时，第二意图系统接收所述第一意图系统发送的意图知识更新通知，其中，所述意图知识更新通知包括更新类型和所述第一意图的意图关键词；
    所述第二意图系统根据所述意图知识更新通知，将所述第一意图的意图关键词对应的所述第一意图的意图知识与所述第二意图系统中的第二意图的意图知识进行关联，其中，所述第一意图是所述第二意图的子意图。
  2. 根据权利要求1所述的方法，其特征在于，第二意图系统接收所述第一意图系统发送的意图知识更新通知之前，所述方法还包括：
    所述第二意图系统向所述第一意图系统发送意图知识更新订阅请求，所述意图知识更新订阅请求包括所述第二意图系统的标识和更新类型；
    所述第二意图系统接收所述第一意图系统发送的意图知识更新订阅响应，所述意图知识更新订阅响应包括以下至少一项信息：订阅标识，订阅状态；
    其中，所述意图知识更新通知还包括所述订阅标识。
  3. 根据权利要求1所述的方法，其特征在于，所述意图知识更新通知还包括所述第一意图系统的标识，所述第二意图系统接收所述第一意图系统发送的意图知识更新通知之后，所述方法还包括：
    所述第二意图系统向所述第一意图系统发送意图知识更新响应。
  4. 根据权利要求1～3任一项所述的方法，其特征在于，所述更新类型为新增所述第一意图的意图知识，所述意图知识更新通知还包括所述第一意图的意图驱动对象和意图驱动操作；
    所述第二意图系统根据所述意图知识更新通知，将所述第一意图的意图关键词对应的所述第一意图的意图知识与所述第二意图系统中的第二意图的意图知识进行关联，包括：
    所述第二意图系统根据所述第一意图的意图驱动对象和意图驱动操作，在所述第二意图系统中查询到所述第二意图的意图知识，其中，所述第一意图的意图驱动对象包含在所述第二意图的意图驱动对象内，和/或所述第一意图的意图驱动操作包含在所述第二意图的意图驱动操作中；
    所述第二意图系统将所述第一意图的意图关键词、所述意图驱动对象和所述意图驱动操作与所述第二意图的意图知识进行关联。
  5. 根据权利要求1～4任一项所述的方法，其特征在于，所述更新类型为删除所述第一意图的意图知识，所述第二意图系统根据所述意图知识更新通知，将所述第一意图的意图 关键词对应的所述第一意图的意图知识与所述第二意图系统中的第二意图的意图知识进行关联，包括：
    所述第二意图系统根据所述第一意图的意图关键词，在所述第二意图系统中查找与所述第一意图的意图关键词对应的所述第一意图的意图知识；
    所述第二意图系统删除查找到的所述第一意图的意图知识。
  6. 根据权利要求1～5任一项所述的方法，其特征在于，所述更新类型为修改所述第一意图的意图知识，所述意图知识更新通知还包括以下至少一项信息：修改前的所述第一意图的关键词、修改前的所述第一意图的意图驱动对象、修改前的所述第一意图的意图驱动操作、修改后的所述第一意图的关键词、修改后的所述第一意图的意图驱动对象、修改后的所述第一意图的意图驱动操作；
    所述第二意图系统根据所述意图知识更新通知，将所述第一意图的意图关键词对应的所述第一意图的意图知识与所述第二意图系统中的第二意图的意图知识进行关联，包括以下至少一种操作：
    所述第一意图系统修改所述第一意图的意图关键词后，所述第二意图系统根据修改前的所述第一意图的意图关键词，在所述第二意图系统中查找与所述修改前的所述第一意图的意图关键词对应的所述第一意图的意图知识，所述第二意图系统将所述修改后的所述第一意图的意图关键词替换所述第一意图的意图知识中的所述修改前的所述第一意图的意图关键词；
    所述第一意图系统修改所述第一意图的意图驱动对象和/或意图驱动操作后，所述第二意图系统根据所述修改后的所述第一意图的意图驱动对象和/或意图驱动操作，在所述第二意图系统中查询到所述第二意图的意图知识，其中，所述修改后的所述第一意图的意图驱动对象包含在所述第二意图的意图驱动对象内，和/或所述修改后的所述第一意图的意图驱动操作包含在所述第二意图的意图驱动操作中；
    所述第二意图系统将所述修改后的所述第一意图的意图驱动对象和/或意图驱动操作与所述第二意图的意图知识关联。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：所述第二意图系统根据所述修改前的所述第一意图的意图驱动对象和/或意图驱动操作，在所述第二意图系统中查询到第三意图的意图知识，其中，所述修改前的所述第一意图的意图驱动对象包含在所述第三意图的意图驱动对象内，和/或所述修改前的所述第一意图的意图驱动操作包含在所述第三意图的意图驱动操作中；
    所述第二意图系统将所述修改前的所述第一意图的意图驱动对象和/或意图驱动操作与所述第三意图的意图知识去关联。
  8. 根据权利要求1～7中任一项所述的方法，其特征在于，所述方法还包括：
    所述第二意图的意图知识发生更新，所述第二意图系统向至少一个第三意图系统发送意图知识能力查询请求，其中，所述意图知识能力查询请求包括以下至少一项信息：所述 第二意图系统的标识、更新后的所述第二意图的意图关键词、意图驱动对象、意图驱动操作，其中，所述第一意图系统为所述至少一个第三意图系统中的其中一个意图系统；
    所述第二意图系统接收所述至少一个第三系统意图系统发送的意图知识能力查询响应，所述意图知识能力查询响应包括以下至少一项信息：所述第二意图系统的标识、所述至少一个第三意图系统的标识、与更新后的所述第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项关联的第一意图的意图知识；
    所述第二意图系统将所述第一意图的意图知识与更新后的所述第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项进行关联。
  9. 根据权利要求8所述的方法，其特征在于，更新类型为修改所述第二意图的意图知识，所述第二意图系统将所述第一意图的意图知识与更新后的所述第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项进行关联，包括以下至少一种操作：
    所述第二意图系统修改所述第二意图的意图关键词后，所述第二意图系统将修改后的所述第二意图的意图关键词与所述第一意图的意图关键词进行关联；
    所述第二意图系统修改所述第二意图的意图驱动对象和/或意图驱动操作后，所述第二意图系统将修改后的所述第二意图的意图驱动对象和/或意图驱动操作与所述第一意图的意图驱动对象和/或意图驱动操作进行关联。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：所述第二意图系统根据修改前的所述第二意图的意图驱动对象和/或意图驱动操作，在所述第二意图系统中查询到所述至少一个第三意图系统中的第四意图的意图知识，其中，所述修改前的所述第二意图的意图驱动对象包含所述第四意图的意图驱动对象，和/或所述修改前的所述第二意图的意图驱动操作包含所述第四意图的意图驱动操作；
    所述第二意图系统将所述修改前的所述第二意图的意图驱动对象和/或意图驱动操作与所述第四意图的意图知识去关联。
  11. 根据权利要求8～10中任一项所述的方法，其特征在于，所述第二意图系统向至少一个第三意图系统发送意图知识能力查询请求之前，所述方法还包括：
    所述第二意图系统根据更新后的所述第二意图的所述意图驱动对象，确定所述至少一个第三意图系统，其中，所述至少一个第三意图系统中的所述第一意图的意图驱动对象包含在更新后的所述第二意图的意图驱动对象内。
  12. 一种意图系统间意图知识的关联方法，其特征在于，所述方法包括：
    确定第一意图系统的第一意图的意图知识发生更新；
    所述第一意图系统向第二意图系统发送意图知识更新通知，以使第二意图系统根据所述意图知识更新通知，将所述第一意图的意图关键词对应的所述第一意图的意图知识与所述第二意图系统中的第二意图的意图知识进行关联，其中，所述第一意图是所述第二意图的子意图，所述意图知识更新通知包括更新类型和所述第一意图的意图关键词。
  13. 根据权利要求12所述的方法，其特征在于，所述第一意图系统向第二意图系统发送意图知识更新通知之前，所述方法还包括：
    所述第一意图系统接收所述第二意图系统发送的意图知识更新订阅请求，所述意图知识更新订阅请求包括所述第二意图系统的标识和更新类型；
    所述第一意图系统向所述第二意图系统发送意图知识更新订阅响应，所述意图知识更新订阅响应包括以下至少一项信息：订阅标识，订阅状态；
    其中，所述意图知识更新通知还包括所述订阅标识。
  14. 根据权利要求12所述的方法，其特征在于，所述第一意图系统向第二意图系统发送意图知识更新通知之后，所述方法还包括：
    所述第一意图系统接收所述第二意图系统发送的意图知识更新响应。
  15. 根据权利要求12～14任一项所述的方法，其特征在于，所述更新类型包括以下至少一种：新增所述第一意图的意图知识、删除所述第一意图的意图知识、修改所述第一意图的意图知识；
    若所述更新类型为新增所述第一意图的意图知识，所述意图知识更新通知还包括所述第一意图的意图驱动对象和意图驱动操作；
    若所述更新类型为修改所述第一意图的意图知识，所述意图知识通知还包括以下至少一项信息：修改前的所述第一意图的关键词、修改前的所述第一意图的意图驱动对象、修改前的所述第一意图的意图驱动操作、修改后的所述第一意图的关键词、修改后的所述第一意图的意图驱动对象、修改后的所述第一意图的意图驱动操作。
  16. 根据权利要求12～15任一项所述的方法，其特征在于，所述方法还包括：
    所述第二意图的意图知识发生更新，所述第一意图系统接收所述第二意图系统发送的意图知识能力查询请求，所述意图知识能力查询请求包括以下至少一项信息：所述第二意图系统的标识、更新后的第二意图的意图关键词、意图驱动对象、意图驱动操作，其中，所述第一意图系统为所述至少一个第三意图系统中的其中一个意图系统；
    所述第一意图系统查找到与所述更新后的第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项关联的所述第一意图的意图知识；
    所述第一意图系统向所述第二意图系统发送意图知识能力查询响应，所述意图知识能力查询响应包括以下至少一项信息：所述第二意图系统的标识、所述至少一个第三意图系统的标识、所述第一意图的意图知识。
  17. 一种通信装置，其特征在于，所述装置包括：
    收发单元，用于第一意图系统的第一意图的意图知识发生更新时，接收所述第一意图系统发送的意图知识更新通知，其中，所述意图知识更新通知包括更新类型和所述第一意图的意图关键词；
    处理单元，用于根据所述意图知识更新通知，将所述第一意图的意图关键词对应的所述第一意图的意图知识与所述第二意图系统中的第二意图的意图知识进行关联，其中，所述第一意图是所述第二意图的子意图。
  18. 根据权利要求17所述的装置，其特征在于：
    所述收发单元，还用于向所述第一意图系统发送意图知识更新订阅请求，所述意图知识更新订阅请求包括所述第二意图系统的标识和更新类型；
    所述收发单元，还用于接收所述第一意图系统发送的意图知识更新订阅响应，所述意图知识更新订阅响应包括以下至少一项信息：订阅标识，订阅状态；
    其中，所述意图知识更新通知还包括所述订阅标识。
  19. 根据权利要求17所述的装置，其特征在于，所述意图知识更新通知还包括所述第一意图系统的标识；
    所述收发单元，还用于向所述第一意图系统发送意图知识更新响应。
  20. 根据权利要求17～19任一项所述的装置，其特征在于，所述更新类型为新增所述第一意图的意图知识，所述意图知识更新通知还包括所述第一意图的意图驱动对象和意图驱动操作；
    所述处理单元，用于根据所述第一意图的意图驱动对象和意图驱动操作，在所述第二意图系统中查询到所述第二意图的意图知识，其中，所述第一意图的意图驱动对象包含在所述第二意图的意图驱动对象内，和/或所述第一意图的意图驱动操作包含在所述第二意图的意图驱动操作中；
    所述处理单元，还用于将所述第一意图的意图关键词、所述意图驱动对象和所述意图驱动操作与所述第二意图的意图知识进行关联。
  21. 根据权利要求17～20任一项所述的装置，其特征在于，所述更新类型为删除所述第一意图的意图知识；
    所述处理单元，还用于根据所述第一意图的意图关键词，在所述第二意图系统中查找与所述第一意图的意图关键词对应的所述第一意图的意图知识；
    所述处理单元，还用于删除查找到的所述第一意图的意图知识。
  22. 根据权利要求17～21任一项所述的装置，其特征在于，所述更新类型为修改所述第一意图的意图知识，所述意图知识更新通知还包括以下至少一项信息：修改前的所述第一意图的关键词、修改前的所述第一意图的意图驱动对象、修改前的所述第一意图的意图驱动操作、修改后的所述第一意图的关键词、修改后的所述第一意图的意图驱动对象、修改后的所述第一意图的意图驱动操作；
    所述处理单元，还用于执行以下至少一种操作：
    所述第一意图系统修改所述第一意图的意图关键词后，根据修改前的所述第一意图的 意图关键词，在所述第二意图系统中查找与所述修改前的所述第一意图的意图关键词对应的所述第一意图的意图知识，所述第二意图系统将所述修改后的所述第一意图的意图关键词替换所述第一意图的意图知识中的所述修改前的所述第一意图的意图关键词；
    所述第一意图系统修改所述第一意图的意图驱动对象和/或意图驱动操作后，根据所述修改后的所述第一意图的意图驱动对象和/或意图驱动操作，在所述第二意图系统中查询到所述第二意图的意图知识，其中，所述修改后的所述第一意图的意图驱动对象包含在所述第二意图的意图驱动对象内，和/或所述修改后的所述第一意图的意图驱动操作包含在所述第二意图的意图驱动操作中；
    将所述修改后的所述第一意图的意图驱动对象和/或意图驱动操作与所述第二意图的意图知识关联。
  23. 根据权利要求22所述的装置，其特征在于，所述处理单元，还用于根据所述修改前的所述第一意图的意图驱动对象和/或意图驱动操作，在所述第二意图系统中查询到第三意图的意图知识，其中，所述修改前的所述第一意图的意图驱动对象包含在所述第三意图的意图驱动对象内，和/或所述修改前的所述第一意图的意图驱动操作包含在所述第三意图的意图驱动操作中；
    所述处理单元，还用于将所述修改前的所述第一意图的意图驱动对象和/或意图驱动操作与所述第三意图的意图知识去关联。
  24. 根据权利要求17～23中任一项所述的装置，其特征在于：
    所述收发单元，还用于所述第二意图的意图知识发生更新，向至少一个第三意图系统发送意图知识能力查询请求，其中，所述意图知识能力查询请求包括以下至少一项信息：所述第二意图系统的标识、更新后的所述第二意图的意图关键词、意图驱动对象、意图驱动操作，其中，所述第一意图系统为所述至少一个第三意图系统中的其中一个意图系统；
    所述收发单元，还用于接收所述至少一个第三系统意图系统发送的意图知识能力查询响应，所述意图知识能力查询响应包括以下至少一项信息：所述第二意图系统的标识、所述至少一个第三意图系统的标识、与更新后的所述第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项关联的第一意图的意图知识；
    所述处理单元，还用于将所述第一意图的意图知识与更新后的所述第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项进行关联。
  25. 根据权利要求24所述的装置，其特征在于，更新类型为修改所述第二意图的意图知识，所述处理单元，还用于执行以下至少一种操作：
    修改所述第二意图的意图关键词后，所述第二意图系统将修改后的所述第二意图的意图关键词与所述第一意图的意图关键词进行关联；
    修改所述第二意图的意图驱动对象和/或意图驱动操作后，将修改后的所述第二意图的意图驱动对象和/或意图驱动操作与所述第一意图的意图驱动对象和/或意图驱动操作进行关联。
  26. 根据权利要求25所述的装置，其特征在于，所述处理单元，还用于根据修改前的所述第二意图的意图驱动对象和/或意图驱动操作，在所述第二意图系统中查询到所述至少一个第三意图系统中的第四意图的意图知识，其中，所述修改前的所述第二意图的意图驱动对象包含所述第四意图的意图驱动对象，和/或所述修改前的所述第二意图的意图驱动操作包含所述第四意图的意图驱动操作；
    所述处理单元，还用于将所述修改前的所述第二意图的意图驱动对象和/或意图驱动操作与所述第四意图的意图知识去关联。
  27. 根据权利要求24～26中任一项所述的装置，其特征在于，所述处理单元，还用于根据更新后的所述第二意图的所述意图驱动对象，确定所述至少一个第三意图系统，其中，所述至少一个第三意图系统中的所述第一意图的意图驱动对象包含在更新后的所述第二意图的意图驱动对象内。
  28. 一种通信装置，其特征在于，所述装置包括：
    处理单元，用于确定第一意图系统的第一意图的意图知识发生更新；
    收发单元，用于向第二意图系统发送意图知识更新通知，以使第二意图系统根据所述意图知识更新通知，将所述第一意图的意图关键词对应的所述第一意图的意图知识与所述第二意图系统中的第二意图的意图知识进行关联，其中，所述第一意图是所述第二意图的子意图，所述意图知识更新通知包括更新类型和所述第一意图的意图关键词。
  29. 根据权利要求28所述的装置，其特征在于：
    所述收发单元，还用于接收所述第二意图系统发送的意图知识更新订阅请求，所述意图知识更新订阅请求包括所述第二意图系统的标识和更新类型；
    所述收发单元，还用于向所述第二意图系统发送意图知识更新订阅响应，所述意图知识更新订阅响应包括以下至少一项信息：订阅标识，订阅状态；
    其中，所述意图知识更新通知还包括所述订阅标识。
  30. 根据权利要求28所述的装置，其特征在于，所述收发单元，还用于接收所述第二意图系统发送的意图知识更新响应。
  31. 根据权利要求28～30任一项所述的装置，其特征在于，所述更新类型包括以下至少一种：新增所述第一意图的意图知识、删除所述第一意图的意图知识、修改所述第一意图的意图知识；
    若所述更新类型为新增所述第一意图的意图知识，所述意图知识更新通知还包括所述第一意图的意图驱动对象和意图驱动操作；
    若所述更新类型为修改所述第一意图的意图知识，所述意图知识通知还包括以下至少一项信息：修改前的所述第一意图的关键词、修改前的所述第一意图的意图驱动对象、修 改前的所述第一意图的意图驱动操作、修改后的所述第一意图的关键词、修改后的所述第一意图的意图驱动对象、修改后的所述第一意图的意图驱动操作。
  32. 根据权利要求28～31任一项所述的装置，其特征在于：
    所述收发单元，还用于所述第二意图的意图知识发生更新，接收所述第二意图系统发送的意图知识能力查询请求，所述意图知识能力查询请求包括以下至少一项信息：所述第二意图系统的标识、更新后的第二意图的意图关键词、意图驱动对象、意图驱动操作，其中，所述第一意图系统为所述至少一个第三意图系统中的其中一个意图系统；
    所述处理单元，还用于查找到与所述更新后的第二意图的意图关键词、意图驱动对象、意图驱动操作中的至少一项关联的所述第一意图的意图知识；
    所述收发单元，还用于向所述第二意图系统发送意图知识能力查询响应，所述意图知识能力查询响应包括以下至少一项信息：所述第二意图系统的标识、所述至少一个第三意图系统的标识、所述第一意图的意图知识。
  33. 一种通信装置，其特征在于，包括处理器、存储器以及存储在所述存储器上并可在处理器上运行的指令，当所述指令被运行时，使得所述通信装置执行如权利要求1～11任一项所述的方法。
  34. 一种通信装置，其特征在于，包括处理器、存储器以及存储在所述存储器上并可在处理器上运行的指令，当所述指令被运行时，使得所述通信装置执行如权利要求12～16任一项所述的方法。
  35. 一种计算机可读存储介质，包括指令，其特征在于，当其在计算机运行时，如权利要求1～16任一项所述的方法被执行。
PCT/CN2020/128754 2020-11-13 2020-11-13 意图系统间意图知识的关联方法及装置、系统 WO2022099626A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2020/128754 WO2022099626A1 (zh) 2020-11-13 2020-11-13 意图系统间意图知识的关联方法及装置、系统
CN202080103879.6A CN116113958A (zh) 2020-11-13 2020-11-13 意图系统间意图知识的关联方法及装置、系统
EP20961182.1A EP4227822A4 (en) 2020-11-13 2020-11-13 METHOD AND DEVICE FOR INTENTION-KNOWLEDGE ASSOCIATION BETWEEN INTENTION SYSTEMS AND SYSTEM
US18/313,546 US20230281469A1 (en) 2020-11-13 2023-05-08 Method for associating intent knowledge between intent systems, apparatus, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/128754 WO2022099626A1 (zh) 2020-11-13 2020-11-13 意图系统间意图知识的关联方法及装置、系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/313,546 Continuation US20230281469A1 (en) 2020-11-13 2023-05-08 Method for associating intent knowledge between intent systems, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2022099626A1 true WO2022099626A1 (zh) 2022-05-19

Family

ID=81602002

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/128754 WO2022099626A1 (zh) 2020-11-13 2020-11-13 意图系统间意图知识的关联方法及装置、系统

Country Status (4)

Country Link
US (1) US20230281469A1 (zh)
EP (1) EP4227822A4 (zh)
CN (1) CN116113958A (zh)
WO (1) WO2022099626A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108475506A (zh) * 2015-12-21 2018-08-31 谷歌有限责任公司 动态意图注册
US20190317994A1 (en) * 2018-04-16 2019-10-17 Tata Consultancy Services Limited Deep learning techniques based multi-purpose conversational agents for processing natural language queries
CN110427415A (zh) * 2019-08-02 2019-11-08 泰康保险集团股份有限公司 知识库共享方法、装置、系统介质及电子设备
CN111565114A (zh) * 2019-02-14 2020-08-21 华为技术有限公司 一种意图处理方法、装置及系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10841182B2 (en) * 2019-03-29 2020-11-17 Juniper Networks, Inc. Supporting near real time service level agreements
US20200344293A1 (en) * 2019-04-23 2020-10-29 Google Llc Distributed robotic controllers

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108475506A (zh) * 2015-12-21 2018-08-31 谷歌有限责任公司 动态意图注册
US20190317994A1 (en) * 2018-04-16 2019-10-17 Tata Consultancy Services Limited Deep learning techniques based multi-purpose conversational agents for processing natural language queries
CN111565114A (zh) * 2019-02-14 2020-08-21 华为技术有限公司 一种意图处理方法、装置及系统
CN110427415A (zh) * 2019-08-02 2019-11-08 泰康保险集团股份有限公司 知识库共享方法、装置、系统介质及电子设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Study on scenarios for Intent driven management services for mobile networks (Release 17)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 28.812, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V17.0.0, 25 September 2020 (2020-09-25), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 46, XP051961046 *
See also references of EP4227822A4 *

Also Published As

Publication number Publication date
EP4227822A4 (en) 2023-11-29
US20230281469A1 (en) 2023-09-07
EP4227822A1 (en) 2023-08-16
CN116113958A (zh) 2023-05-12

Similar Documents

Publication Publication Date Title
US20210405629A1 (en) System and method for interoperable communication of an automation system component with multiple information sources
US11646940B2 (en) Intent driven network policy platform
EP2477355B1 (en) Method and device for managing association of network resources
CN102084623B (zh) 控制自优化开关的方法、装置和系统
US8209440B2 (en) Device-configuration-information optimum arrangement method and device-configuration-information optimum arrangement system
US20240037001A1 (en) Large-scale k8s cluster monitoring method, apparatus, device, and readable medium
CN101730099A (zh) 基于权限控制的终端管理方法及装置
WO2016107397A1 (en) System and method for model-based search and retrieval of networked data
CN114077602B (zh) 数据迁移方法和装置、电子设备、存储介质
CN108733727A (zh) 一种查询处理方法、数据源注册方法及查询引擎
US20180278481A1 (en) Distributed Policy Store
US9015204B2 (en) Onboarding resources to an identity management system
CN107277120B (zh) 配置文件管理方法、装置以及服务配置方法与系统
US20180205790A1 (en) Distributed data structure in a software defined networking environment
WO2022099626A1 (zh) 意图系统间意图知识的关联方法及装置、系统
US9501548B2 (en) Data updating method, system and device
US10439897B1 (en) Method and apparatus for enabling customized control to applications and users using smart tags
CN103139806B (zh) 网管与基站配置数据解耦的方法及基站
US10764152B1 (en) Methods and apparatus for centralized configuration management of heterogenous network devices through software-based node unification
CN113986545A (zh) 用户与角色关联方法及装置
WO2022048444A1 (zh) 通信方法及装置、系统
CN111723036A (zh) 数据处理方法、相关设备及计算机存储介质
WO2023050815A1 (zh) 切片业务配置方法、网络设备、网络系统及存储介质
WO2023125260A1 (zh) 一种意图管理的方法和通信装置
EP4325791A1 (en) Configuration updating method and apparatus, and system and computer-readable storage medium

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20961182

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020961182

Country of ref document: EP

Effective date: 20230510

NENP Non-entry into the national phase

Ref country code: DE