WO2023109594A1 - 一种意图合法性检查方法及装置 - Google Patents

一种意图合法性检查方法及装置 Download PDF

Info

Publication number
WO2023109594A1
WO2023109594A1 PCT/CN2022/137016 CN2022137016W WO2023109594A1 WO 2023109594 A1 WO2023109594 A1 WO 2023109594A1 CN 2022137016 W CN2022137016 W CN 2022137016W WO 2023109594 A1 WO2023109594 A1 WO 2023109594A1
Authority
WO
WIPO (PCT)
Prior art keywords
intent
attribute
expression
template
range
Prior art date
Application number
PCT/CN2022/137016
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 EP22906344.1A priority Critical patent/EP4432065A1/en
Priority to KR1020247023216A priority patent/KR20240113612A/ko
Publication of WO2023109594A1 publication Critical patent/WO2023109594A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/04845—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range for image manipulation, e.g. dragging, rotation, expansion or change of colour
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/20—Natural language analysis
    • G06F40/253—Grammatical analysis; Style critique
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/166—Editing, e.g. inserting or deleting
    • G06F40/186—Templates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/30—Semantic analysis

Definitions

  • the present application relates to the technical field of communications, and in particular to a method and device for checking the validity of intentions.
  • SA5 3rd generation partnership project (3GPP) service and system aspect work group 5 (SA5) adopts the full-scale construction of network resources in the definition of the traditional northbound interface (itf-N).
  • 3GPP 3rd generation partnership project
  • SA5 system aspect work group 5
  • the network management system (NMS) directly manages all southbound management objects through operations such as configuration management (CM), performance management (PM), and fault management (FM).
  • CM configuration management
  • PM performance management
  • FM fault management
  • 3GPP SA5 launched the research on intent-driven management service (IDMS): NMS as
  • IDMS intent-driven management service
  • NMS NMS
  • the intention is expressed in a declarative manner, and the operation and maintenance personnel only need to declare what effect to achieve through the intention expression, without having to determine how to achieve it, which helps to reduce the threshold for operation and maintenance.
  • the intent producer that is, the equipment management system (EMS) receives the intent expression, it needs to create an intent instance according to the intent expression.
  • the EMS can translate the intent expression into a pair of network
  • the needs and specific implementation operations are implemented to achieve the intention.
  • the EMS may fail to create the intent instance, so the EMS will indicate to the NMS that the creation of the intent instance failed.
  • the NMS does not know the reason for the current creation failure, so that the NMS cannot reasonably modify it based on the failure reason. intent expression.
  • the present application provides a method and device for checking the validity of an intent, which is used to solve the problem in the prior art that intent consumers cannot reasonably modify intent expressions because they cannot know the cause of intent instance creation failure.
  • the present application provides a method for checking the validity of an intention, which can be executed by a first device, and the first device can be an intention producer, where the intention producer can specifically be an EMS, an IDMS producer, or a management service producer ( management service producer, MnS producer).
  • the method includes: the first device receives a first intent expression of the second device, and the first intent expression is used to create an intent instance; The device sends failure information, and the failure information is used to indicate the failure reason for creating the intent instance; wherein, the first intent expression includes multiple attributes, and the failure reason includes conflicting attributes in the first intent expression, and the attribute is a goal or a constraint condition.
  • the first device can send failure information to the second device according to the first intent expression, so as to inform the second device of the reason why the first intent expression cannot be successfully created.
  • the second device sends an intent expression that can be used to successfully create an intent instance to the first device, so that the success rate of intent creation can be improved.
  • the first device sends failure information to the second device according to the first intent expression, including: the first device checks the validity of the first intent expression; After the intent expression fails the legality check, a failure message is generated according to the reason for the failed legality check.
  • the first device can perform a legality check on the first intent expression, and when it is determined that the first intent expression fails the legality check, it does not need to create an intent instance based on the first intent expression, thereby facilitating Prevent the first device from performing unnecessary operations.
  • the first device may also generate failure information according to the reason for failing the legality check, which helps to inform the second device of the reason why the intent instance cannot be successfully created.
  • the failure reason includes conflicting first attribute and second attribute in the first intent expression, the first attribute includes the first attribute name and the first attribute range, and the second attribute includes the second Attribute name and second attribute range;
  • the type of conflict includes one or more of the following: a syntax conflict indicating that the first attribute name is the same as the second attribute name, and the intersection of the first attribute range and the second attribute range is empty ;Operation conflict, used to indicate that the operation indicated by the first attribute name and the first attribute range is mutually exclusive with the operation indicated by the second attribute name and the second attribute range, for example, operation one is "open symbol close switch", operation 2 is "close the symbol to turn off the switch", then operation 1 and operation 2 are mutually exclusive operations; the effect conflict is used to indicate the operation indicated by the first attribute name and the first attribute range, and the second attribute When the operations indicated by the name and the second attribute range are executed at the same time, the effects they can achieve are mutually exclusive. For example, “turning on the symbol shutdown switch" can achieve the purpose of energy saving,
  • the failure information includes the first attribute, the second attribute, and a conflict type between the first attribute and the second attribute.
  • the types of conflicts may be syntax conflicts, operation conflicts and effect conflicts
  • the first device may determine from the first intent expression that there are conflicting first attributes and second attributes based on the three types of conflicts, It helps to improve the correct rate of identifying conflicting attributes. Further, the first device notifies the second device of the attribute conflict through the failure information, so that the second device can obtain the reason why the first intent expression cannot be successfully created an intent instance based on the failure information, so as to target the intention expression Modifications can help improve the success rate of intent creation.
  • the failure reason further includes that the third attribute in the first intent expression does not conform to the intent template in the first device; the intent template includes multiple template attribute names and the multiple template attribute names correspond to The template attribute range of the third attribute; the third attribute includes the third attribute name and the third attribute range; the third attribute in the first intent expression does not conform to the intent template in the first device, including: the third attribute name is not included in the intent template in multiple template attribute names; or, the scope of the third attribute is outside the scope of the template attribute corresponding to the third attribute in the intent template.
  • the failure information further includes a third attribute.
  • the first device can determine the third attribute included in the first intent expression that does not conform to the intent template, and notify the second device through failure information, which helps to improve the success rate of intent creation.
  • the method further includes: the first device sends a recommendation intention expression to the second device according to the first intention expression; after the first device determines that the second device accepts the recommendation intention expression, according to the recommendation Intent expressions create Intent instances.
  • the first device can also send the recommended intention expression to the second device to recommend an intention expression that can pass the legality check to the second device.
  • the second device accepts the recommended intention expression
  • the first The device can create an intent instance based on the recommended intent expression, which helps to improve the efficiency and success rate of intent instance creation.
  • the method further includes: the first device receives a second intent expression of the second device, and the second intent expression is obtained by the second device after modifying the first intent expression according to the failure reason .
  • the first device can also receive the second intent expression obtained by modifying the first intent expression based on the failure information of the second device, so that the first device can further legalize the second intent expression.
  • the success rate of the intent expression passing the legality check can be improved, and the second device can choose whether to adopt the recommended intent expression, thereby improving the flexibility of creating an intent instance.
  • the first intent expression is included in the intent creation request, and the failure information is included in the intent creation response; the second intent expression is included in the intent modification request or the intent creation request.
  • the intent creation request further includes a check indication, where the check indication is used to instruct the first device to check the validity of the first intent expression.
  • a check instruction is added in the intent creation request, and the check instruction may be used to instruct the first device to check the validity of the first intent expression in the intent creation request.
  • the first intent expression is included in the intent legitimacy check request, and the failure information is included in the intent legitimacy check response; the second intent expression is included in the intent legitimacy check request or the intent creation request middle.
  • the first device may receive an intention legality check request from the second device, and the intention legality check request may be used to instruct the first device to perform a legality check on the first intention expression in the intention legality check request .
  • the failure information includes one or more of the following: there are conflicting attributes, there are conflicting types between conflicting attributes; attribute names and/or attribute ranges are not included in the intent attributes in the template.
  • the failure information indicates the failure reason for creating the intent instance, so that the second device can be instructed to modify the first intent expression based on the failure information, thereby helping the first device receive the first intent expression that meets the legality check. 2. Intent expression, to improve the success rate of creating an intent instance.
  • the present application provides a method for checking the validity of an intent, which can be executed by a second device, and the second device can be an intent consumer, where the intent consumer can specifically be an NMS, an IDMS consumer, or a management service consumer ( management service consumer, MnS consumer).
  • the method includes: the second device sends a first intent expression to the first device, and the first intent expression is used to create an intent instance; the second device receives failure information of the first device, and the failure information It is used to indicate a failure reason for creating an intent instance; wherein, the first intent expression includes multiple attributes, the failure reason includes conflicting attributes in the first intent expression, and the attribute is a target or a constraint condition.
  • the failure reason includes conflicting first attribute and second attribute in the first intent expression, the first attribute includes the first attribute name and the first attribute range, and the second attribute includes the second Attribute name and second attribute range;
  • the type of conflict includes one or more of the following: a syntax conflict indicating that the first attribute name is the same as the second attribute name, and the intersection of the first attribute range and the second attribute range is empty ;Operation conflict, used to indicate that the operation indicated by the first attribute name and the first attribute range is mutually exclusive with the operation indicated by the second attribute name and the second attribute range;Effect conflict, used to indicate the first attribute name When the operation indicated by the name of the first attribute and the operation indicated by the second attribute name and the second attribute range are executed at the same time, the effects that can be achieved by the two are mutually exclusive.
  • the failure information includes the first attribute, the second attribute, and a conflict type between the first attribute and the second attribute.
  • the failure reason further includes that the third attribute in the first intent expression does not conform to the intent template in the first device; the intent template includes multiple template attribute names and the multiple template attribute names correspond to The template attribute range of the third attribute; the third attribute includes the third attribute name and the third attribute range; the third attribute in the first intent expression does not conform to the intent template in the first device, including: the third attribute name is not included in the intent template in multiple template attribute names; or, the scope of the third attribute is outside the scope of the template attribute corresponding to the third attribute in the intent template.
  • the failure information further includes a third attribute.
  • the method further includes: the second device receives the recommended intention expression from the first device; the second device sends an indication of accepting the recommended intention expression to the first device, and the recommended intention expression is used to create Intent instance.
  • the method further includes: the second device sends the second intent expression to the first device through a second intent expression obtained by modifying the first intent expression according to the failure reason.
  • the first intent expression is included in the intent creation request, and the failure information is included in the intent creation response; the second intent expression is included in the intent modification request.
  • the intent creation request further includes a check indication, where the check indication is used to instruct the first device to check the validity of the first intent expression.
  • the first intent expression is included in the intent validity check request, and the failure information is included in the intent validity check response; the second intent expression is included in the intent creation request.
  • the failure information includes one or more of the following: there are conflicting attributes, there are conflicting types between conflicting attributes; attribute names and/or attribute ranges are not included in the intent attributes in the template.
  • the embodiment of the present application provides a communication device, which has the function of implementing the first device in the above-mentioned first aspect or any possible implementation of the first aspect, and the first device may be an intended producer , the apparatus may be the first device or a chip in the first device.
  • the communication device may also have the function of implementing the second aspect or the second device in any possible implementation manner of the second aspect.
  • the second device may be the intended consumer, and the device may be the second device or the second device. Two chips in the device.
  • the above-mentioned functions of the communication device may be realized by hardware, or may be realized by executing corresponding software by hardware, and the hardware or software includes one or more modules or units or means (means) corresponding to the above-mentioned functions.
  • the structure of the apparatus includes a processing module and a transceiver module, where the processing module is configured to support the apparatus to execute the first aspect or the first device in any implementation manner of the first aspect corresponding functions, or perform corresponding functions of the second device in the second aspect or any implementation manner of the second aspect.
  • the transceiver module is used to support communication between the device and other communication devices, for example, when the device is the first device, it can receive the first intent expression from the second device.
  • the communication device may also include a storage module, which is coupled to the processing module and stores necessary program instructions and data of the device.
  • the processing module may be a processor
  • the communication module may be a transceiver
  • the storage module may be a memory
  • the memory may be integrated with the processor or configured separately from the processor.
  • the structure of the apparatus includes a processor, and may further include a memory.
  • the processor is coupled with the memory, and can be used to execute the computer program instructions stored in the memory, so that the device executes the method in the above-mentioned first aspect or any possible implementation manner of the first aspect, or executes the above-mentioned second aspect or the second aspect.
  • the device further includes a communication interface, and the processor is coupled to the communication interface.
  • the communication interface may be a transceiver or an input/output interface; when the device is a chip contained in the second device or a chip contained in the first device, the communication interface may be It is the input/output interface of the chip.
  • the transceiver may be a transceiver circuit, and the input/output interface may be an input/output circuit.
  • an embodiment of the present application provides a chip system, including: a processor and a memory, the processor and the memory are coupled, and the memory is used to store programs or instructions, and when the programs or instructions are executed by the processor, the chip system realizes The first aspect or the method in any possible implementation manner of the first aspect, or the second aspect or the method in any possible implementation manner of the second aspect.
  • the chip system further includes an interface circuit for exchanging code instructions to the processor.
  • processors in the chip system, and the processors may be implemented by hardware or by software.
  • the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor may be a general-purpose processor implemented by reading software codes stored in a memory.
  • the memory can be integrated with the processor, or can be set separately from the processor.
  • the memory may be a non-transitory processor, such as a read-only memory ROM, which may be integrated with the processor on the same chip, or may be respectively disposed on different chips.
  • the embodiment of the present application provides a communication device, including a processor, the processor is connected to the memory, the memory is used to store the computer program, and the processor is used to execute the computer program stored in the memory, so that the device realizes the above first aspect Or a method in any possible implementation manner of the first aspect, or a method in any possible implementation manner of realizing the above-mentioned second aspect or the second aspect.
  • the embodiments of the present application provide a computer-readable storage medium, in which computer programs or instructions are stored, and when the computer programs or instructions are executed by the communication device, the above-mentioned first aspect or the first aspect is realized A method in any possible implementation manner of the above-mentioned second aspect or a method in any possible implementation manner of the second aspect.
  • the embodiment of the present application provides a computer program product.
  • the computer program product includes computer programs or instructions.
  • the computer programs or instructions are executed by the communication device, any possible possibility of the above-mentioned first aspect or the first aspect can be realized.
  • the present application provides a communication system, where the communication system includes a first device and a second device.
  • the first device may be used to execute the method in the above first aspect or any possible implementation of the first aspect
  • the second device may be used to execute the above second aspect or any possible implementation of the second aspect method in method.
  • FIG. 1 is a schematic diagram of a communication system architecture provided by the present application.
  • Fig. 2 is a schematic flow chart of intention creation provided by this application.
  • FIG. 3 is a schematic flow diagram of a method for checking the validity of intentions provided by the present application.
  • FIG. 4 is a flow chart of the method for checking the validity of intentions in the first specific scenario provided by the present application.
  • FIG. 5 is a flow chart of the method for checking the validity of intentions in the second specific scenario provided by the present application.
  • FIG. 6 is a flowchart of a method for checking the validity of an intention in a third specific scenario provided by the present application.
  • FIG. 7 is a flow chart of the method for checking the validity of intentions in the fourth specific scenario provided by the present application.
  • FIG. 8 is a schematic structural diagram of a communication device provided by the present application.
  • FIG. 9 is a schematic structural diagram of another communication device provided by the present application.
  • Intent The expectation of the functioning system, including requirements, goals and constraints, but without specifying how to achieve it.
  • Actions and objects can be included in intent expressions.
  • an action refers to an abstract and simplified network operation based on an intent, and may include an intent driven action (IDA) name (name) and a series of related attributes (for example, IDA attributes, IDA properties); an object refers to an action based on an intent
  • the management object information provided may include an intent driven object (intent driven object, IDO) name (name) and a series of attributes used to identify the object (for example, IDO attribute, IDO properties).
  • the target value of an intent can be contained in an action or an object; alternatively, an intent expression includes an action, an object, and a target value.
  • the intention is to optimize the downlink rate of a cell, wherein the action is "optimize", the object is "cell”, and the target value is a specific value of the downlink rate of the cell.
  • the intent expression only contains the description of the target, and the specific implementation method of the intent is obtained by parsing and translating the intent expression by the intent producer.
  • the intention producer can determine which scheme to use to meet the expectation, that is, the intention producer can determine which scheme to use to satisfy the intention.
  • Intent conflicts may include one or more of syntax conflicts, operational conflicts, and effect conflicts.
  • the grammatical conflict refers to the conflict between the intent expressions of two intents.
  • the intent expressions of two intents describe mutually exclusive goals of the same object (eg, cell, base station, etc.) under the same valid condition.
  • the intent expression of one intent expresses the goal of increasing the downlink rate of the cell
  • the intent expression of the other intent embodies the goal of reducing the downlink rate of the cell, and there is a grammatical conflict between the two intents.
  • Operational conflict refers to the conflict between two intents in the translated execution operation (intent operation), that is, the operations of two intents cannot be executed at the same time.
  • the schemes corresponding to two intents include mutually exclusive operations on the same parameter and/or attribute of the same network element.
  • An example is that there is an operational conflict between Intent 1 and Intent 2 when the scheme of Intent 1 requires the network configuration parameter A to be adjusted up, while the scheme of Intent 2 requires the network configuration parameter A to be adjusted down.
  • a conflict of effects means that the translated execution of two intents is mutually exclusive in effect.
  • Intent creation Create a new intent instance in the intent system and create a corresponding intent context.
  • the intent consumer is a device that manages the intent. Specifically, the intent consumer can generate an intent, and send an intent expression for carrying the intent to the intent generator.
  • the intent may be the intended consumer's demand on the network where the device executing the intent solution resides, for example, the intent may reflect the intended consumer's demand for at least one key performance indicator (key performance indicator, KPI) in the network where the device executing the intent solution resides demand.
  • KPI key performance indicator
  • the intent producer is a device that processes the intent. Specifically, after receiving the intent expression from the intent consumer, the intent producer can generate multiple solutions that can satisfy the intent, and select one of them for execution. Then, the intent producer can send the selected solution to the device executing the intent, so that the device executing the intent executes the selected solution.
  • the intent consumer and/or the intent producer may be AN equipment or CN equipment.
  • the intent consumer may be a network management service (network management service, NMS), an IDMS consumer (IDMS consumer), or a management service consumer (management service consumer, MnS consumer).
  • the intent producer can be an element management service (element management service, EMS), an IDMS producer (IDMS producer), or a management service producer (management service producer, MnS producer).
  • Fig. 1 shows the architecture of a possible communication system provided by the present application, which includes IDMS consumers and IDMS producers, IDMS consumers can realize the functions of intent consumers, and IDMS producers can realize intent producers
  • IDMS consumers can realize the functions of intent consumers
  • IDMS producers can realize intent producers
  • IDMS producers may include: intent translation (intent translation, IT) module, intent evaluation (intent evaluation, IEv) module, intent conflict resolution (intent conflict resolution, ICR) module, intent decision (intent decision, ID) module.
  • intent translation module, the intent evaluation module, the intent conflict resolution module, and the intent decision module may be independent entities, or virtual modules in one or more entities.
  • the intent translation module can be used to perform intent translation and generate a solution that can satisfy the intent.
  • the intent translation module can acquire the information needed for intent translation, which can be the correspondence between intentions and strategies; the intention translation module can determine the strategy of the intention according to the correspondence and the intention obtained from the IDMS consumer; then, The intent translation module can generate at least one solution that can satisfy the intent according to the strategy of the intent.
  • the intent evaluation module can evaluate the realization of the intent.
  • the intent conflict resolution module can handle intent conflicts. For example, an intent conflict resolution module can determine whether an intent conflict exists between two intents.
  • the intent decision module can decide which solution of the intent to execute. For example, when the intention translation module generates at least one scheme that can satisfy the intention, the intention decision module can randomly select a scheme that does not conflict with other intentions from the at least one scheme for execution, or select a scheme that is consistent with the intention according to a predetermined strategy. Other schemes that do not intend to conflict with each other are executed (for example, the scheme with the smallest delay or the scheme with the least energy consumption is selected).
  • FIG. 2 is a schematic flow diagram of an intentional creation provided by this application:
  • step 201 the IDMS consumer sends an intent creation request to the IDMS producer.
  • the intent creation request can be used to indicate the intent instance to be created.
  • the intent creation request can include an intent expression, and the intent expression can further include multiple attributes.
  • An attribute can be represented by a key-value pair, for example, the key-value pair is [attribute, vlaue], where attribute represents the attribute name, and vlaue represents the attribute range. This key-value pair can be used to indicate the created attribute name and the attribute range corresponding to the attribute name.
  • step 202 the IDMS producer creates an intent instance according to the intent expression in the intent creation request.
  • step 203 the IDMS producer sends an intent creation response to the IDMS consumer.
  • the intent creation response sent to the IDMS consumer may be used to indicate that the intent instance is successfully created.
  • the intent creation response sent to the IDMS consumer may be used to indicate the intent instance creation failure.
  • IDMS consumers can only know whether the current intent instance is successfully created, but in the case of creation failure, they cannot know the cause of the creation failure, so they cannot reasonably modify the intent expression in the intent creation request.
  • this application provides a method for checking the validity of the intention.
  • the first device can check the intention expression, and determine the reason why the intention expression fails the legality check, and inform the second device of the reason for failing the legality check.
  • the second device may modify the intent expression in a targeted manner based on the reason for failing the legality check, and request the first device to create an intent based on the modified intent expression.
  • the first device may be an intended producer, such as an EMS, IDMS producer, or MnS producer.
  • the second device may be an intended consumer, such as an NMS, IDMS consumer, or MnS consumer.
  • Step 301 the second device sends a first intention expression to the first device.
  • the first intent expression is used to create an intent instance.
  • the first intent expression includes multiple attributes, and the attributes may be targets or constraints.
  • an attribute may include the attribute name and the attribute range corresponding to the attribute name.
  • the target may be "throughput rate>5kbps", wherein the attribute name is “throughput rate”, and the attribute range corresponding to the attribute name is ">5kbps”.
  • the constraint condition may be "user>80%”, wherein the attribute name is "user”, and the attribute range corresponding to the attribute name is ">80%”.
  • the constraint condition and the target may have a corresponding relationship, and the constraint condition is used to constrain the effective condition of its corresponding target.
  • the constraint condition "users > 80%” has a corresponding relationship with the target "throughput rate > 5kbps”, it may mean "the throughput rate corresponding to more than 80% of users needs to be above 5kbps".
  • Step 302 the first device checks the legality of the first intent expression.
  • the legality check may be used to indicate whether the first device further creates a corresponding intent instance according to the first intent expression.
  • the first device may create an intent instance according to the first intent expression, and the intent instance may be created successfully.
  • the first intent expression fails the legality check, the first device does not need to create an intent instance according to the first intent expression.
  • the legality check may at least include one or more of attribute conflict checks and grammar and lexical checks. Firstly, the attribute conflict checking and grammar and lexical checking are explained as follows.
  • the types of conflicts between attributes may include one or more of grammatical conflicts, operational conflicts, and semantic conflicts, as explained below using two attributes as examples.
  • a syntax conflict is when two attributes have the same attribute name and the intersection of the attribute range of one attribute with the attribute range of the other attribute is empty. For example, if one attribute is "throughput rate>5kbps" and the other attribute is "throughput rate ⁇ 5kbps", then the attribute names corresponding to the two attributes are both "throughput rate", and there is no intersection between the corresponding attribute ranges. There is a grammatical conflict between the two.
  • Operation conflict means that the operation indicated by the attribute name and attribute range of one attribute is mutually exclusive with the operation indicated by the attribute name and attribute range of another attribute (or the two operations cannot be executed at the same time). For example, if an attribute is "Energy Efficiency Level 2", the attribute name of this attribute is “Energy Efficiency Level”, and the attribute range is "Level 2". is "throughput rate ⁇ 10kbps", where the attribute name of the attribute is “throughput rate” and the attribute range is " ⁇ 10kbps”. The operation indicated by both is to close the symbol off switch, and the two operations cannot be executed at the same time , that is, there is an operation conflict.
  • Semantic conflict means that when the operation indicated by the attribute name and attribute range of one attribute is executed simultaneously with the operation indicated by the attribute name and attribute range of another attribute, the effects that the two can achieve are mutually exclusive (or two operations cannot simultaneously achieve the desired effect).
  • one attribute is "Energy Efficiency Level 2", where the attribute name is “Energy Efficiency Level”, and the attribute range is "Level 2”; while another attribute is "Throughput ⁇ 10kbps", where the attribute name is "Throughput Rate ", the attribute range is " ⁇ 10kbps”. It is estimated that when the energy efficiency level is 2, the corresponding throughput rate needs to be less than 10 kbps, so the expected effects corresponding to the two attributes cannot be achieved at the same time.
  • conflict may be a conflict between two attributes, or a conflict between multiple attributes.
  • attribute 1 is "throughput rate ⁇ 5kbps”
  • attribute 2 is “5kbps ⁇ throughput rate ⁇ 10kbps”
  • attribute 3 is "10kbps ⁇ throughput rate”
  • the three attributes have the same attribute name, the attribute range between is disjoint, that is, there is a grammatical conflict among attribute 1, attribute 2, and attribute 3.
  • the present application may also include other examples of conflicts among multiple attributes, and no more examples will be given here.
  • syntax conflicts, operation conflicts and semantic conflicts correspond to syntax conflict checking, operation conflict checking and semantic conflict checking respectively.
  • the first device checks attribute conflicts, it may specifically perform one or more of syntax conflict checks, operation conflict checks, and semantic conflict checks.
  • the first device performs syntax conflict checking, operation conflict checking and semantic conflict checking on the first intent expression. If the first device determines that the first intent expression passes the three conflict checks, it may determine that the first intent expression passes the attribute conflict check; if the first device determines that the first intent expression fails one of the three conflict checks item, it can be determined that the first intent expression fails the attribute conflict check.
  • the first device may also perform a conflict check among syntax conflict check, operation conflict check and semantic conflict check on the first intent expression, and determine the first intent expression when the first intent expression passes the conflict check.
  • the intent expression passes the attribute conflict check; and when the first intent expression fails the one conflict check, determining that the first intent expression fails the attribute conflict check.
  • the first device may also perform two conflict checks among syntax conflict check, operation conflict check, and semantic conflict check on the first intention expression. For details, reference may be made to the above description, and details are not repeated here.
  • the first device may check whether, among the multiple attributes included in the first intent expression, there is an attribute that does not meet the grammar and lexical check, wherein the grammar and lexical check may be performed based on the intent template in the first device.
  • the intent template may include multiple template attribute names and template attribute ranges corresponding to the multiple template attribute names.
  • the intent template includes N template attribute names, N is a positive integer, and the N template attribute names can respectively correspond to their own template attribute ranges. It can also be understood that the intent template includes template attribute names 1 and template Template attribute range 1 corresponding to attribute name 1, template attribute name 2 and template attribute range 2 corresponding to template attribute name 2, ..., template attribute name N and template attribute range N corresponding to template attribute name N.
  • the intent template may be pre-configured in the first device, or dynamically loaded by the first device from the intent system management device. In the latter case, the intent template may be updated periodically, or when required Updates are initiated by the system administrator.
  • the first device may execute for an attribute in the first intent expression: judge whether the attribute name of the attribute is in the intent template; after determining that the attribute name of the attribute is in the intent template, judge whether the attribute range of the attribute exceeds the intent
  • the first device determines that in the attribute, the attribute name is in the intent template, and the attribute range does not exceed the template attribute range corresponding to the attribute name in the intent template, it can determine that the attribute has passed the grammar and lexical check, that is, the attribute is grammatically correct. If the first device determines that the attribute name is not in the intent template, or if it is determined that the attribute name is in the intent template, but the attribute range exceeds the corresponding template attribute range in the intent template, it may determine that the attribute fails Grammar and lexical checking, that is, the grammatical and lexical errors of this attribute.
  • the first device may consider the error type to be a syntax error, and if the first device determines that the attribute range in the attribute exceeds the corresponding template attribute range in the intent template , the error type can be considered a lexical error.
  • the first device can determine that the syntax and lexical correctness of the attribute.
  • the first device may determine that the attribute name is in the intent template, but The scope of this attribute exceeds the scope of the template attribute corresponding to this attribute in the intent template, that is, there is a grammatical and lexical error in this attribute, and the error type is specifically a lexical error.
  • the first device may perform attribute conflict checking and grammar and lexical checking, and when it is determined that the first intent expression fails one of the checks, it determines that the first intent expression fails the legality check. When it is determined that the first intent expression passes the attribute conflict check and the grammar and lexical check, it is determined that the first intent expression passes the legality check.
  • the first intent expression includes conflicting first attributes and second attributes, and it can also be understood that the first device cannot be based on the first attribute name and the first attribute range in the first attribute, and The second attribute name and the second attribute scope in the second attribute generate an intent instance.
  • both the first attribute and the second attribute may be targets, that is, the first intent expression includes conflicting first and second targets; the first attribute and the second attribute may both be constraints, that is, the first The intention expression includes conflicting first constraint conditions and second constraint conditions.
  • the goal refers to the goal that the intention wants to achieve
  • the constraint refers to the constraints to achieve the goal, such as “increase the average throughput of the terminal by 30% when the energy consumption is not increased by more than 30%", where "the average terminal Throughput rate increased by 30%” is the intended goal, and "energy consumption is not increased by more than 30%” is the constraint condition.
  • the first device when it performs attribute conflict check on the first intent expression, it may determine that there is a conflict between the first attribute and the second attribute in the first intent expression, wherein the first attribute and the second attribute
  • the mutually conflicting conflict types may be one or more of syntax conflicts, operational conflicts, and semantic conflicts.
  • the first intent expression may include a third attribute
  • the third attribute may include a third attribute name and a third attribute range
  • the third attribute does not conform to the intent template in the first device.
  • the first device checks the syntax and grammar of the first intent expression, specifically, the first device may determine that the third attribute name is not included in the template attribute names of the intent template; or the first device determines that the third attribute After the name is included in multiple template attribute names of the intent template, it is determined that the range of the third attribute exceeds the range of template attributes corresponding to the third attribute in the intent template.
  • Step 303 if the first device determines that the first intent expression fails the legality check, it may send failure information to the second device, where the failure information may be used to indicate that the first intent expression cannot be used to successfully create an intent instance.
  • the failure information may be creation failure information
  • the creation failure information may be used to indicate the reason why the first intent expression cannot successfully create the intent instance, or in other words, the reason why the intent instance fails to be created.
  • the failure information may also be check failure information, and the check failure information may be used to indicate a failure reason that the first intent expression fails the legality check, or in other words, a reason why the first device fails the legality check on the first intent expression.
  • the failure information is used as an example in the following.
  • the failure information may include one or more of the following fields: attribute conflict field, syntax and lexical error field.
  • the attribute conflict field may be used to indicate that the failure reason of the first intent expression failing the legality check includes conflicting attributes existing in the first intent expression.
  • the attribute conflict field may include conflicting attributes and conflicting types between conflicting attributes.
  • the first intent expression includes a first attribute and a second attribute that conflict with each other, and correspondingly, the attribute conflict field may include the first attribute, the second attribute, and the relationship between the first attribute and the second attribute type of conflict.
  • the first attribute is "throughput rate ⁇ 5kbps”
  • the second attribute is "throughput rate > 5kbps”
  • the attribute conflict field can include these two attributes, namely "throughput rate ⁇ 5kbps", “throughput rate > 5kbps”, and the conflict type "syntax conflict”.
  • the grammatical and lexical error field may be used to indicate that the failure reason for the first intent expression failing the legality check includes an attribute with a grammatical lexical error existing in the first intent expression.
  • the grammatical and lexical error field may include attributes whose attribute names and/or attribute ranges are not included in the intent template.
  • the first intent expression includes a third attribute with grammatical and lexical errors
  • the grammatical and lexical error field may include the third attribute and an error type of the third attribute. For example, if the third attribute is "10kbps ⁇ throughput rate", and the attribute range in the third attribute exceeds the template attribute range corresponding to "throughput rate" in the intent template, then the grammar and lexical error field is "10kbps ⁇ throughput rate", and the error type is a lexical error.
  • the failure information may also include a failure indication field, which may be used to indicate to the second device that the first intent expression fails the legality check, or indicate to the second device that the first device expresses the The formula could not successfully create an intent instance.
  • a failure indication field which may be used to indicate to the second device that the first intent expression fails the legality check, or indicate to the second device that the first device expresses the The formula could not successfully create an intent instance.
  • the second device may modify the first intention expression according to the failure information to obtain the second intention expression, and then send the second intention expression to the first device.
  • the first device receives the second intent expression, and the first device checks the validity of the second intent expression.
  • the first device determines that the second intention expression fails the legality verification, it continues to send failure information to the second device, and the first device continues to modify the intention expression. In this way, the actions of the first device and the second device in the above steps are repeated until the first device determines that the intention expression of the second device passes the legality verification.
  • the second device sends the first intent expression to the first device, and the first device can perform a legality check on the first intent expression, and when it is determined that the first intent expression fails the legality check, send the The second device sends failure information, that is, informs the second device of the reason why the first intent expression fails the legality verification. Therefore, the second device can make targeted modifications to the first intent expression based on the cause of the error, which helps the second device to send an intent expression that can pass the legality check to the first device.
  • the first device A corresponding intent instance can be created based on the intent expression that passes the legality check, which can improve the success rate of intent creation.
  • the first device sends a recommendation intent expression to the second device according to the first intent expression, where the recommendation intent expression can pass a legality check.
  • the first device may generate a recommended intent expression according to attributes with conflicts in the first intent expression, and/or attributes with grammatical and lexical errors.
  • attributes with conflicts in the first intent expression and/or attributes with grammatical and lexical errors.
  • the first device adjusts one of the attribute ranges or two attribute ranges according to the first attribute name and the first attribute range in the first attribute, and the second attribute name and the second attribute range in the second attribute , or delete one of the attributes so that there is no attribute conflict between the first attribute and the second attribute.
  • the third attribute in the intent template A device can adjust the third attribute range to be included in the template attribute range corresponding to the third attribute.
  • the first device may delete the attribute from the first intent expression.
  • the second device receives the recommendation intention expression from the first device, determines whether to accept the recommendation intention expression, and then sends an acceptance indication or a rejection indication to the first device, wherein the acceptance indication can be used to instruct the second device to accept the recommendation intention expression In this way, the rejection indication may be used to instruct the second device to refuse to adopt the recommendation intention expression.
  • the first device may receive the acceptance indication from the second device.
  • the first device may also generate an intent instance according to the recommended intent expression, and send creation success information of the intent instance to the first device.
  • the second device may also generate a second intent expression according to the failure information and the first intent expression, and then send the second intent expression to the first device, specifically Reference may be made to the above first implementation manner, which will not be repeated here.
  • the second device may include the rejection indication and the second intention expression in the same message, or may further include the rejection indication and the second intention expression in two messages respectively.
  • the second intent expression may be understood as a rejection indication, and when the second device refuses to adopt the recommended intent expression, it may directly send the second intent expression to the first device to indicate to the first device that the recommended intent expression The second device refuses to use the recommended intent expression, and instructs the first device to continue to check the validity of the second intent expression.
  • the second device sends the first intent expression to the first device, and the first device can perform a legality check on the first intent expression, and when it is determined that the first intent expression fails the legality check, send the The second device sends a recommended intent expression, that is, recommends an intent expression that can pass legality verification to the second device.
  • the first device can Creating an intent instance helps to improve the efficiency and success rate of intent instance creation.
  • the first device may also send a failure reason to the second device, and when the second device refuses to accept the recommended intent expression, the second device may make targeted modifications to the first intent expression based on the error reason, In this way, the second device can send the intent expression that can pass the legality check to the first device, which helps to improve the flexibility of creating an intent instance.
  • the above information can be transmitted through different messages between the first device and the second device, two examples are provided as follows:
  • Example 1 intent creation request and intent creation response.
  • the first intent expression sent by the second device to the first device may be included in the intent creation request, and the intent creation request instructs the first device to create an intent instance according to the first intent expression in the intent creation request. Further, the intent creation request further includes a check indication (flag), which may be used to instruct the first device to check the validity of the first intent expression before creating the intent instance.
  • a check indication flag
  • the first device can create an intent instance according to the first intent expression, and send an intent creation response to the second device after the intent instance is successfully created, and the intent creation response includes creating Success information, to indicate that the intent instance corresponding to the first intent expression is created successfully.
  • the first device may send to the second device information indicating that the first intent expression has passed the legality check; and after creating the intent instance, send to the second device a message containing An intent creation response with creation success information, which can be used to indicate that the instance was successfully created.
  • the first device may send failure information to the second device, where the failure information is included in the intent creation response.
  • the second device may send the intent creation request containing the second intent expression to the first device again, and the first device further checks whether the second intent expression in the intent creation request Pass the legality check.
  • the second device may send an intent modification request including the second intent expression to the first device, and the first device performs a legality check according to the second intent expression in the intent modification request.
  • the first device may not send an intent creation response including creation success information to the second device.
  • the second device may determine the intent instance corresponding to the first intent expression if it does not receive an intent creation response containing failure information from the first device after the preset time period has elapsed. has been created successfully.
  • this application will not give examples one by one.
  • the first device may not perform a legality check, but directly create an intent instance according to the first intent expression. If the creation of the intent instance fails, then Creation failure information (distinguished from check failure information here) may be sent to the second device, and the creation failure information may include reasons why the first intent expression cannot be successfully created as an intent instance.
  • Example 2 the intent legality check request and the intent legality check response.
  • the first intention expression sent by the second device to the first device may be included in the intention validity checking request, and the intention validity checking request may be used to instruct the first device to check the validity of the first intention expression.
  • the first device may send an intent legality check response including check success information to the second device, and the intent legality check response may be used to indicate that the first intent expression passes the legality check. sex check.
  • the second device may further send an intent creation request to the first device, and the first device creates an intent instance according to the intent creation request.
  • the intent creation request may include a first intent expression.
  • the first device after determining that the first intention expression fails the legality check, the first device sends an intention validity check response including failure information to the second device, and the intention validity check response may be used to indicate that the first intention expression has not passed the validity check. Pass the legality check.
  • the second device may further send an intent validity check request including the second intent expression to the first device, for instructing the first device to check the validity of the second intent expression again.
  • the first device may not send the intent legality check response including the check success information to the second device.
  • the second device sends the intent legality check request, if it determines that the preset time period has elapsed and does not receive an intent legality check response containing failure information from the first device, it can determine the first intent expression Having passed the legality check, the intent creation request may continue to be sent to the first device.
  • this application will not give examples one by one.
  • the first intent expression can also be included in other messages, such as an intent expression error checking request, an intent error checking request, and an intent attribute conflict checking request.
  • the checking result corresponding to the first intent expression can be included in in the corresponding response.
  • the first device is an IDMS producer
  • the second device is an IDMS consumer
  • Embodiment 1 The IDMS consumer sends an intent creation request to the IDMS producer, and the IDMS producer checks the validity of the first intent expression in the intent creation request. For details, refer to the flowchart in FIG. 4 .
  • step 401 the IDMS consumer sends an intent creation request to the IDMS producer.
  • the intent creation request includes the first intent expression and a check indication (flag), and the check indication is used to instruct the IDMS producer to check the validity of the first intent expression.
  • a check indication for the specific implementation, refer to the description in step 301 above.
  • step 402 the IDMS producer checks the validity of the first intent expression.
  • the IDMS producer can perform lexical grammar check and attribute conflict check on the first intention expression, and the specific implementation method can refer to the description in step 302 above.
  • the IDMS producer sends an intent creation response to the IDMS consumer, wherein the intent creation response includes failure information to indicate that the first intent expression fails the legality check and the reason for failing the legality check.
  • the failure information includes at least the following fields: a failure indication field, a grammatical and lexical error field, and an attribute conflict field.
  • a failure indication field For a specific implementation, refer to the description in step 303 above.
  • step 404 the IDMS consumer modifies the first intent expression according to the failure information included in the intent creation response to obtain a second intent expression.
  • the IDMS consumer modifies the first intent expression according to the failure information included in the intent creation response to obtain a second intent expression.
  • the failure information included in the intent creation response For specific implementation, refer to the description in step 303 above.
  • Step 405 the IDMS consumer sends an intent creation request or an intent modification request to the IDMS producer, wherein the intent creation request or the intent modification request includes a second intent expression.
  • the intent creation request or the intent modification request may further include a check indication (flag).
  • step 406 the IDMS producer creates an intent instance according to the intent creation request.
  • the IDMS producer sends an intent creation response to the IDMS consumer, wherein the intent creation response includes creation success information to indicate to the IDMS consumer that the intent instance is successfully created.
  • Embodiment 2 The IDMS consumer sends an intent validity check request to the IDMS producer, and the IDMS producer checks the validity of the first intent expression in the intent validity check request. For details, refer to the flowchart in FIG. 5 .
  • step 501 the IDMS consumer sends an intent legality check request to the IDMS producer, and the intent legality check request instructs the IDMS producer to perform a legality check on the first intent expression included in the intent legality check request.
  • the intent legality check request instructs the IDMS producer to perform a legality check on the first intent expression included in the intent legality check request.
  • step 502 the IDMS producer checks the validity of the first intent expression.
  • the IDMS producer can perform lexical grammar check and attribute conflict check on the first intention expression, and the specific implementation method can refer to the description in step 302 above.
  • the IDMS producer sends an intent validity check response to the IDMS consumer, wherein the intent validity check response includes failure information (specifically, check failure information) to indicate that the first intent expression fails the validity check, and The reason for failing the legality check.
  • failure information specifically, check failure information
  • the failure information includes at least the following fields: a failure indication field, a grammatical and lexical error field, and an attribute conflict field.
  • a failure indication field For a specific implementation, refer to the description in step 303 above.
  • step 504 the IDMS consumer modifies the first intent expression according to the failure information included in the intent validity check response to obtain a second intent expression.
  • the IDMS consumer modifies the first intent expression according to the failure information included in the intent validity check response to obtain a second intent expression.
  • Step 505 the IDMS consumer sends an intent creation request to the IDMS producer, wherein the intent creation request includes a second intent expression.
  • the IDMS consumer may also send the intent validity check request to the IDMS producer again, so as to instruct the IDMS producer to check the validity of the second intent expression included in the intent validity check request.
  • step 506 the IDMS producer sends an intent validity check response to the IDMS consumer, wherein the intent validity check response includes check success information to indicate that the first intent expression passes the validity check.
  • the IDMS consumer sends an intent creation request to the IDMS producer to instruct the IDMS producer to create an intent instance according to the first intent expression.
  • the intent creation request includes the first intent expression.
  • step 508 the IDMS consumer creates an intent instance according to the intent creation request.
  • the IDMS consumer sends an intent creation response to the IDMS producer, wherein the intent creation response includes creation success information to indicate to the IDMS consumer that the intent instance is successfully created.
  • step 505 to step 509 refer to the description in the related embodiment in FIG. 3 .
  • Embodiment 3 The IDMS consumer sends an intent creation request to the IDMS producer, and the IDMS producer performs a legality check on the first intent expression in the intent creation request, and after determining that the first intent expression fails the legality check,
  • the recommendation intention expression is sent to the IDMS consumer, for details, refer to the flowchart in FIG. 6 .
  • Step 601 the IDMS consumer sends an intent creation request to the IDMS producer, the intent creation request includes the first intent expression and a check indication (flag), and the check indication is used to instruct the IDMS producer to check the validity of the first intent expression , for a specific implementation manner, refer to the description in step 301 above.
  • step 602 the IDMS producer checks the validity of the first intent expression.
  • the IDMS producer can perform lexical grammar check and attribute conflict check on the first intention expression, and the specific implementation method can refer to the description in step 302 above.
  • the IDMS producer sends an intent creation response to the IDMS consumer, wherein the intent creation response includes failure information to indicate that the first intent expression fails the legality check and the reason for failing the legality check.
  • the failure information includes at least the following fields: a failure indication field, a grammatical and lexical error field, and an attribute conflict field.
  • a failure indication field For a specific implementation, refer to the description in step 303 above.
  • Step 604 the IDMS producer generates a recommended intention expression according to the first intention expression, and sends the recommended intention expression to the second device, wherein the recommended intention expression can pass a legality check.
  • the IDMS consumer can determine whether to receive the recommended intent expression according to the recommended intent expression from the IDMS producer, as follows:
  • step 605 the IDMS consumer sends an acceptance indication to the IDMS producer to instruct the IDMS consumer to accept the recommendation intention expression.
  • step 606 the IDMS producer creates an intent instance according to the recommended intent expression.
  • the IDMS producer sends an intent creation response to the IDMS consumer, wherein the intent creation response includes creation success information to indicate to the IDMS consumer that the intent instance is successfully created.
  • step 608 the IDMS consumer sends a rejection indication to the IDMS producer, for instructing the IDMS consumer to refuse to accept the recommendation intention expression.
  • Step 609 the IDMS consumer modifies the first intent expression according to the failure information included in the intent creation response to obtain the second intent expression.
  • Step 610 the IDMS consumer sends an intent creation request or an intent modification request to the IDMS producer, wherein the intent creation request or the intent modification request includes a second intent expression.
  • the intent creation request or the intent modification request may further include a check indication (flag).
  • step 611 the IDMS producer creates an intent instance according to the intent creation request.
  • the IDMS producer sends an intent creation response to the IDMS consumer, wherein the intent creation response includes creation success information to indicate to the IDMS consumer that the intent instance is successfully created.
  • step 603 is an optional step, and step 604 may also be directly performed after step 602 .
  • the order in which the IDMS producer sends the intent creation response containing the failure information to the IDMS consumer and sends the recommended intent expression to the IDMS consumer may not be limited.
  • the intent creation response including the failure information may also include a recommended intent expression, or in other ways.
  • step 604 to step 612 For the implementation manners not described in detail in step 604 to step 612, refer to the description in the related embodiment in FIG. 3 .
  • Embodiment 4 The IDMS consumer sends an intent validity check request to the IDMS producer, and the IDMS producer performs a legality check on the first intent expression in the intent legitimacy check request, and determines that the first intent expression fails to pass the legality check request. After the validity check, the intent expression is recommended to the IDMS consumer, for details, refer to the flow chart in Fig. 7 .
  • step 701 the IDMS consumer sends an intent legality check request to the IDMS producer, and the intent legality check request is used to instruct the IDMS producer to perform a legality check on the first intent expression in the intent legality check request.
  • the specific implementation method can be Refer to the description in step 301 above.
  • step 702 the IDMS producer checks the validity of the first intent expression.
  • the IDMS producer can perform lexical grammar check and attribute conflict check on the first intention expression, and the specific implementation method can refer to the description in step 302 above.
  • step 703 the IDMS producer sends an intent validity check response to the IDMS consumer.
  • the intent validity check response includes failure information (specifically, check failure information) to indicate that the first intent expression fails the legality check and a reason for failing the legality check.
  • failure information specifically, check failure information
  • the failure information includes at least the following fields: a failure indication field, a grammatical and lexical error field, and an attribute conflict field.
  • a failure indication field For a specific implementation, refer to the description in step 303 above.
  • step 704 the IDMS producer generates a recommendation intent expression according to the first intent expression, and sends the recommendation intent expression to the second device, wherein the recommendation intent expression can pass a legality check.
  • the IDMS consumer can determine whether to receive the recommended intent expression according to the recommended intent expression from the IDMS producer, as follows:
  • Step 705 The IDMS consumer sends an intent creation request to the IDMS producer, wherein the intent creation request includes an acceptance indication to instruct the IDMS consumer to accept the recommended intent expression and instruct the IDMS producer to create Intent instance.
  • step 706 the IDMS producer creates an intent instance according to the recommended intent expression.
  • the IDMS producer sends an intent creation response to the IDMS consumer, wherein the intent creation response includes creation success information to indicate that the IDMS producer has successfully created the intent instance.
  • Step 708 the IDMS consumer sends a rejection indication to the IDMS producer, for instructing the IDMS consumer to refuse to accept the recommendation intention expression.
  • step 709 the IDMS consumer modifies the first intent expression according to the failure information contained in the intent validity check response to obtain the second intent expression.
  • Step 710 the IDMS consumer sends an intent validity check request to the IDMS producer, for instructing the IDMS producer to check the validity of the second intent expression included in the intent validity check request.
  • step 711 the IDMS producer sends an intent validity check response to the IDMS consumer, wherein the intent validity check response includes check success information to indicate that the first intent expression passes the validity check.
  • the IDMS consumer sends an intent creation request to the IDMS producer to instruct the IDMS producer to create an intent instance according to the first intent expression.
  • the intent creation request includes the first intent expression.
  • step 713 the IDMS producer creates an intent instance according to the intent creation request.
  • the IDMS producer sends an intent creation response to the IDMS consumer, wherein the intent creation response includes creation success information to indicate that the IDMS producer has successfully created the intent instance.
  • step 704 to step 714 For the implementation manners not described in detail in step 704 to step 714, refer to the description in the related embodiment in FIG. 3 .
  • FIG. 8 and FIG. 9 are schematic structural diagrams of possible communication devices provided by the present application. These communication devices can be used to realize the functions in the foregoing method embodiments, and therefore can also realize the beneficial effects possessed by the foregoing method embodiments.
  • the communication device 800 includes a processing module 801 and a transceiver module 802 .
  • the communication device 800 When the communication device 800 is used to realize the function of the first device in the method embodiment shown in FIG. 3 above, or to realize the function of the IDMS producer in FIG. 4 to FIG. 7 above:
  • the processing module 801 is configured to control the transceiver module 802 to receive a first intent expression of the second device, and the first intent expression is used to create an intent instance; the processing module 801 is also configured to An intent expression, controlling the transceiver module 802 to send failure information to the second device, the failure information is used to indicate the failure reason for creating the intent instance; wherein, the first intent expression includes multiple attributes, and the failure reason includes the first intent expression There are conflicting attributes in , which are goals or constraints.
  • the processing module 801 controls the transceiver module 802 to send failure information to the second device according to the first intent expression, it is specifically used to: check the validity of the first intent expression; After the intent expression fails the legality check, a failure message is generated according to the reason for failing the legality check.
  • the failure reason includes conflicting first attribute and second attribute in the first intent expression, the first attribute includes the first attribute name and the first attribute range, and the second attribute includes the second Attribute name and second attribute range;
  • the type of conflict includes one or more of the following: a syntax conflict indicating that the first attribute name is the same as the second attribute name, and the intersection of the first attribute range and the second attribute range is empty ;Operation conflict, used to indicate that the operation indicated by the first attribute name and the first attribute range is mutually exclusive with the operation indicated by the second attribute name and the second attribute range;Effect conflict, used to indicate the first attribute name When the operation indicated by the name of the first attribute and the operation indicated by the second attribute name and the second attribute range are executed at the same time, the effects that can be achieved by the two are mutually exclusive.
  • the failure information includes the first attribute, the second attribute, and a conflict type between the first attribute and the second attribute.
  • the reason for the failure also includes that the third attribute in the first intent expression does not conform to the intent template in the communication device 800; the intent template includes multiple template attribute names and the multiple template attribute names correspond to The template attribute range; the third attribute includes the third attribute name and the third attribute range; the third attribute in the first intent expression does not conform to the intent template in the communication device 800, including: the third attribute name is not included in the intent template in multiple template attribute names; or, the scope of the third attribute is outside the scope of the template attribute corresponding to the third attribute in the intent template.
  • the failure information further includes a third attribute.
  • the processing module 801 is further configured to: according to the first intention expression, control the transceiving module 802 to send the recommended intention expression to the second device; after determining that the second device accepts the recommended intention expression, according to It is recommended that intent expressions create intent instances.
  • the processing module 801 is further configured to: control the transceiving module 802 to receive the second intention expression of the second device, the second intention expression is the second device performing an operation on the first intention expression according to the failure reason obtained after modification.
  • the first intent expression is included in the intent creation request, and the failure information is included in the intent creation response; the second intent expression is included in the intent modification request.
  • the intent creation request includes a check indication, where the check indication is used to instruct the communications apparatus 800 to check the validity of the first intent expression.
  • the first intent expression is included in the intent validity check request, and the failure information is included in the intent validity check response; the second intent expression is included in the intent creation request.
  • the failure information includes one or more of the following: there are conflicting attributes, there are conflicting types between conflicting attributes; attribute names and/or attribute ranges are not included in the intent attributes in the template.
  • the communication device 800 is used to realize the function of the second device in the method embodiment shown in FIG. 3 above, or to realize the function of the IDMS consumer in FIG. 4 to FIG. 7 above:
  • the processing module 801 is configured to control the transceiving module 802 to send a first intent expression to the first device, and the first intent expression is used to create an intent instance; the processing module 801 is also configured to control the transceiving Module 802 receives failure information of the first device, where the failure information is used to indicate a failure reason for creating an intent instance; wherein, the first intent expression includes multiple attributes, and the failure reason includes conflicting attributes in the first intent expression, Attributes are goals or constraints.
  • the processing module 801 is further configured to: control the transceiver module 802 to receive the recommended intention expression from the first device, and send an indication of accepting the recommended intention expression to the first device, and the recommended intention expression uses for creating intent instances.
  • the processing module 801 is further configured to: control the transceiver module 802 to send the second intent expression to the first device by modifying the first intent expression according to the failure reason Mode.
  • FIG. 9 shows an apparatus 900 provided in the embodiment of the present application.
  • the apparatus shown in FIG. 9 may be a hardware circuit implementation manner of the apparatus shown in FIG. 8 .
  • the apparatus may be applicable to the flow chart shown above to execute the functions in the foregoing method embodiments. For ease of illustration, only the main components of the device are shown in FIG. 9 .
  • the device 900 shown in FIG. 9 includes a communication interface 910, a processor 920, and a memory 930, wherein the memory 930 is used for storing program instructions and/or data.
  • Processor 920 may cooperate with memory 930 .
  • Processor 920 may execute program instructions stored in memory 930 .
  • the processor 920 is used to perform the operations performed by the processing module 801 in the above embodiments
  • the communication interface 910 is used to perform the operations performed by the transceiver module 802 in the above embodiments.
  • the memory 930 is coupled to the processor 920 .
  • the coupling in the embodiments of the present application is an indirect coupling or a communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • At least one of the memories 930 may be included in the processor 920 .
  • the communication interface may be a transceiver, a circuit, a bus, a module, or other types of communication interfaces.
  • the transceiver when the communication interface is a transceiver, the transceiver may include an independent receiver and an independent transmitter; it may also be a transceiver integrated with a transceiver function, or be a communication interface.
  • Apparatus 900 may also include a communication link 940 .
  • the communication interface 910, the processor 920 and the memory 930 can be connected to each other through a communication line 940;
  • the communication line 940 can be a peripheral component interconnect (PCI for short) bus or an extended industry standard architecture (extended industry standard architecture , referred to as EISA) bus and so on.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the communication line 940 can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used in FIG. 9 , but it does not mean that there is only one bus or one type of bus.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Artificial Intelligence (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Computational Linguistics (AREA)
  • General Health & Medical Sciences (AREA)
  • Human Computer Interaction (AREA)
  • Machine Translation (AREA)

Abstract

一种意图合法性检查方法及装置，用于解决现有技术中意图消费者因无法得知意图实例创建失败的原因、而无法合理修改意图表达式的问题。在本申请中，方法包括: 第一设备接收来自第二设备的第一意图表达式，第一意图表达式用于创建意图实例; 第一设备根据第一意图表达式，向第二设备发送失败信息，失败信息用于指示创建意图实例的失败原因; 其中，第一意图表达式中包括多个属性，失败原因包括第一意图表达式中存在相互冲突的属性，属性是目标或者约束条件。

Description

一种意图合法性检查方法及装置
相关申请的交叉引用
本申请要求在2021年12月17日提交中国专利局、申请号为202111548435.6、申请名称为“一种意图合法性检查方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种意图合法性检查方法及装置。
背景技术
当前第三代伙伴计划(the 3rd generation partnership project，3GPP)业务与系统第五工作组(service and system aspect work group 5，SA5)在传统北向接口(itf-N)的定义上采用网络资源全量建模和网络对象全量管理的方式。网络管理系统(network management system，NMS)通过配置管理(configuration management，CM)、性能管理(performance management，PM)、故障管理(fault management，FM)等类型的操作直接对南向所有的管理对象进行增删改查。
进一步的，为了降低网络基础设施的管理复杂度、提高多运营商(Multi-vendor)场景下的运维效率，3GPP SA5启动了意图驱动管理服务(intent driven management service，IDMS)的研究：NMS作为意图消费者，其中只保留意图模型，北向接口上只传递意图表达式，从而屏蔽了设备厂商实现上的差异化细节。其中，意图采用声明式表达，运维人员只需要通过意图表达式，声明实现什么效果，而无需确定如何去实现，从而有助于降低运维门槛。当意图生产者，即设备管理系统(equipment management system，EMS)收到意图表达式之后，需根据意图表达式创建意图实例，具体的，EMS可根据网络状态，将意图表达式转译成对网络的需求和具体的执行操作并执行来达成意图。
在该过程中，EMS可能存在创建意图实例失败的情况，于是EMS会向NMS指示创建意图实例失败，但是对于NMS来说，NMS并不知道当前创建失败的原因，导致NMS无法基于失败原因合理修改意图表达式。
发明内容
本申请提供一种意图合法性检查方法及装置，用于解决现有技术中意图消费者因无法得知意图实例创建失败的原因、而无法合理修改意图表达式的问题。
第一方面，本申请提供一种意图合法性检查方法，该方法可由第一设备执行，第一设备可以是意图生产者，其中意图生产者具体可以是EMS、IDMS生产者或管理服务生产者(management service producer，MnS producer)。
在一种可能的实现方式中，方法包括：第一设备接收第二设备的第一意图表达式，第一意图表达式用于创建意图实例；第一设备根据第一意图表达式，向第二设备发送失败信息，失败信息用于指示创建意图实例的失败原因；其中，第一意图表达式中包括多个属性， 失败原因包括第一意图表达式中存在相互冲突的属性，属性是目标或者约束条件。
上述技术方案中，第一设备可根据第一意图表达式，向第二设备发送失败信息，以用于告知第二设备第一意图表达式不能被成功创建意图实例的原因，如此，有助于第二设备向第一设备发送可用于成功创建意图实例的意图表达式，如此可提高意图创建成功率。
在一种可能的实现方式中，第一设备根据第一意图表达式，向第二设备发送失败信息，包括：第一设备对第一意图表达式进行合法性检查；第一设备在确定第一意图表达式未通过合法性检查之后，根据未通过合法性检查的原因，生成失败信息。
上述技术方案中，第一设备可对第一意图表达式进行合法性检查，在确定第一意图表达式未通过合法性检查时，即无需根据第一意图表达式创建意图实例，从而有助于避免第一设备执行不必要的操作。且第一设备还可根据未通过合法性检查的原因，生成失败信息，有助于将不能成功创建意图实例的原因告知第二设备。
在一种可能的实现方式中，失败原因包括第一意图表达式中存在相互冲突的第一属性与第二属性，第一属性包括第一属性名称和第一属性范围，第二属性包括第二属性名称和第二属性范围；冲突的类型包括如下中一个或多个：语法冲突，用于指示第一属性名称与第二属性名称相同，且第一属性范围与第二属性范围的交集为空；操作冲突，用于指示第一属性名称和第一属性范围所指示的操作，与第二属性名称和第二属性范围所指示的操作之间互斥，比如，操作一为“打开符号关断开关”，操作二为“关闭符号关断开关”，那么操作一与操作二为互斥的操作；效果冲突，用于指示第一属性名称和第一属性范围所指示的操作，与第二属性名称和第二属性范围所指示的操作被同时执行时，二者能够达到的效果互斥，比如，“打开符号关断开关”，能够达到节能的目的，却会降低网络的吞吐率。
在一种可能的实现方式中，失败信息中包括第一属性、第二属性，以及第一属性与第二属性的冲突的类型。
上述技术方案中，冲突类型可以是语法冲突、操作冲突和效果冲突，第一设备可基于该三个冲突的类型从第一意图表达式中确定出存在相互冲突的第一属性和第二属性，有助于提高识别出冲突属性的正确率。进一步的，第一设备通过失败信息将该属性冲突告知第二设备，以使得第二设备可基于失败信息获得第一意图表达式不能被成功创建意图实例的原因，从而有针对性的对意图表达式进行修改，有助于提高意图创建成功率。
在一种可能的实现方式中，失败原因还包括第一意图表达式中的第三属性不符合第一设备中的意图模板；意图模板中包括多个模板属性名称和多个模板属性名称分别对应的模板属性范围；第三属性包括第三属性名称和第三属性范围；第一意图表达式中的第三属性不符合第一设备中的意图模板，包括：第三属性名称未包含于意图模板的多个模板属性名称中；或者，第三属性范围超出意图模板中第三属性对应的模板属性范围。
在一种可能的实现方式中，失败信息中还包括第三属性。
上述技术方案中，第一设备可确定出第一意图表达式中包括的不符合意图模板的第三属性，并通过失败信息告知第二设备，有助于可提高意图创建成功率。
在一种可能的实现方式中，方法还包括：第一设备根据第一意图表达式，向第二设备发送推荐意图表达式；第一设备在确定第二设备接受推荐意图表达式之后，根据推荐意图表达式创建意图实例。
上述技术方案中，第一设备还可向第二设备发送推荐意图表达式，以向第二设备推荐可通过合法性检查的意图表达式，在第二设备接受该推荐意图表达式时，第一设备可以基 于该推荐意图表达式创建意图实例，有助于提高意图实例创建的效率以及成功率。
在一种可能的实现方式中，方法还包括：第一设备接收第二设备的第二意图表达式，第二意图表达式是第二设备根据失败原因对第一意图表达式进行修改后得到的。
上述技术方案中，第一设备还可接收到第二设备的基于失败信息对第一意图表达式进行修改后得的第二意图表达式，从而第一设备可进一步对第二意图表达式进行合法性检查，如此，可提高意图表达式通过合法性检查的成功率，且第二设备可以自己选择是否采用推荐意图表达式，提高意图实例创建的灵活性。
在一种可能的实现方式中，第一意图表达式包含于意图创建请求中，失败信息包含于意图创建响应中；第二意图表达式包含于意图修改请求或者意图创建请求中。在一种可能的实现方式中，意图创建请求中还包括检查指示，检查指示用于指示第一设备对第一意图表达式进行合法性检查。上述技术方案中，在意图创建请求中新增检查指示，该检查指示可用于指示第一设备对意图创建请求中的第一意图表达式进行合法性检查。
在一种可能的实现方式中，第一意图表达式包含于意图合法性检查请求中，失败信息包含于意图合法性检查响应中；第二意图表达式包含于意图合法性检查请求或者意图创建请求中。上述技术方案中，第一设备可接收来自第二设备的意图合法性检查请求，该意图合法性检查请求可用于指示第一设备对意图合法性检查请求中的第一意图表达式进行合法性检查。
在一种可能的实现方式中，失败信息中包括如下的一项或多项：具有相互冲突的属性、具有相互冲突的属性之间存在冲突的类型；属性名称和/或属性范围未包含于意图模板中的属性。上述技术方案中，通过失败信息指示创建意图实例的失败原因，从而可指示第二设备基于该失败信息对第一意图表达式进行修改，从而有助于第一设备接收到符合合法性检查的第二意图表达式，提高意图实例的创建成功率。
第二方面，本申请提供一种意图合法性检查方法，该方法可由第二设备执行，第二设备可以是意图消费者，其中意图消费者具体可以是NMS、IDMS消费者或管理服务消费者(management service consumer，MnS consumer)。
在一种可能的实现方式中，方法包括：第二设备向第一设备发送第一意图表达式，第一意图表达式用于创建意图实例；第二设备接收第一设备的失败信息，失败信息用于指示创建意图实例的失败原因；其中，第一意图表达式中包括多个属性，失败原因包括第一意图表达式中存在相互冲突的属性，属性是目标或者约束条件。
在一种可能的实现方式中，失败原因包括第一意图表达式中存在相互冲突的第一属性与第二属性，第一属性包括第一属性名称和第一属性范围，第二属性包括第二属性名称和第二属性范围；冲突的类型包括如下中一个或多个：语法冲突，用于指示第一属性名称与第二属性名称相同，且第一属性范围与第二属性范围的交集为空；操作冲突，用于指示第一属性名称和第一属性范围所指示的操作，与第二属性名称和第二属性范围所指示的操作之间互斥；效果冲突，用于指示第一属性名称和第一属性范围所指示的操作，与第二属性名称和第二属性范围所指示的操作被同时执行时，二者能够达到的效果互斥。
在一种可能的实现方式中，失败信息中包括第一属性、第二属性，以及第一属性与第二属性的冲突的类型。
在一种可能的实现方式中，失败原因还包括第一意图表达式中的第三属性不符合第一 设备中的意图模板；意图模板中包括多个模板属性名称和多个模板属性名称分别对应的模板属性范围；第三属性包括第三属性名称和第三属性范围；第一意图表达式中的第三属性不符合第一设备中的意图模板，包括：第三属性名称未包含于意图模板的多个模板属性名称中；或者，第三属性范围超出意图模板中第三属性对应的模板属性范围。
在一种可能的实现方式中，失败信息中还包括第三属性。
在一种可能的实现方式中，方法还包括：第二设备接收来自第一设备的推荐意图表达式；第二设备向第一设备发送接受推荐意图表达式的指示，推荐意图表达式用于创建意图实例。
在一种可能的实现方式中，方法还包括：第二设备根据失败原因，对第一意图表达式进行修改后得到的第二意图表达式，向第一设备发送第二意图表达式。
在一种可能的实现方式中，第一意图表达式包含于意图创建请求中，失败信息包含于意图创建响应中；第二意图表达式包含于意图修改请求中。
在一种可能的实现方式中，意图创建请求中还包括检查指示，检查指示用于指示第一设备对第一意图表达式进行合法性检查。
在一种可能的实现方式中，第一意图表达式包含于意图合法性检查请求中，失败信息包含于意图合法性检查响应中；第二意图表达式包含于意图创建请求中。
在一种可能的实现方式中，失败信息中包括如下的一项或多项：具有相互冲突的属性、具有相互冲突的属性之间存在冲突的类型；属性名称和/或属性范围未包含于意图模板中的属性。
第三方面，本申请实施例提供一种通信装置，该装置具有实现上述第一方面或第一方面的任一种可能的实现方式中第一设备的功能，该第一设备可以是意图生产者，该装置可以是第一设备或者是第一设备中的芯片。该通信装置也可以具有实现上述第二方面或第二方面的任一种可能的实现方式中第二设备的功能，该第二设备可以是意图消费者，该装置可以是第二设备或者是第二设备中的芯片。
上述通信装置的功能可以通过硬件实现，也可以通过硬件执行相应的软件实现，硬件或软件包括一个或多个与上述功能相对应的模块或单元或手段(means)。
在一种可能的实现方式中，该装置的结构中包括处理模块和收发模块，其中，处理模块被配置为支持该装置执行上述第一方面或第一方面的任一种实现方式中第一设备相应的功能，或者执行上述第二方面或第二方面的任一种实现方式中第二设备相应的功能。收发模块用于支持该装置与其他通信设备之间的通信，例如该装置为第一设备时，可接收来自第二设备的第一意图表达式。该通信装置还可以包括存储模块，存储模块与处理模块耦合，其保存有装置必要的程序指令和数据。作为一种示例，处理模块可以为处理器，通信模块可以为收发器，存储模块可以为存储器，存储器可以和处理器集成在一起，也可以和处理器分离设置。
在另一种可能的实现方式中，该装置的结构中包括处理器，还可以包括存储器。处理器与存储器耦合，可用于执行存储器中存储的计算机程序指令，以使装置执行上述第一方面或第一方面的任一种可能的实现方式中的方法，或者执行上述第二方面或第二方面的任一种可能的实现方式中的方法。可选地，该装置还包括通信接口，处理器与通信接口耦合。当装置为第二设备或第一设备时，该通信接口可以是收发器或输入/输出接口；当该装置为 第二设备中包含的芯片或第一设备中包含的芯片时，该通信接口可以是芯片的输入/输出接口。可选地，收发器可以为收发电路，输入/输出接口可以是输入/输出电路。
第四方面，本申请实施例提供一种芯片系统，包括：处理器和存储器，处理器与存储器耦合，存储器用于存储程序或指令，当程序或指令被处理器执行时，使得该芯片系统实现上述第一方面或第一方面的任一种可能的实现方式中的方法，或实现上述第二方面或第二方面的任一种可能的实现方式中的方法。
可选地，该芯片系统还包括接口电路，该接口电路用于交互代码指令至处理器。
可选地，该芯片系统中的处理器可以为一个或多个，该处理器可以通过硬件实现也可以通过软件实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等。当通过软件实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现。
可选地，该芯片系统中的存储器也可以为一个或多个。该存储器可以与处理器集成在一起，也可以和处理器分离设置。示例性的，存储器可以是非瞬时性处理器，例如只读存储器ROM，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上。
第五方面，本申请实施例提供一种通信装置，包括处理器，处理器与存储器相连，存储器用于存储计算机程序，处理器用于执行存储器中存储的计算机程序，以使得装置实现上述第一方面或第一方面的任一种可能的实现方式中方法，或实现上述第二方面或第二方面的任一种可能的实现方式中方法。
第六方面，本申请实施例提供一种计算机可读存储介质，计算机可读存储介质中存储有计算机程序或指令，当计算机程序或指令被通信装置执行时，实现上述第一方面或第一方面的任一种可能的实现方式中方法，或实现上述第二方面或第二方面的任一种可能的实现方式中方法。
第七方面，本申请实施例提供一种计算机程序产品，计算机程序产品包括计算机程序或指令，当计算机程序或指令被通信装置执行时，实现上述第一方面或第一方面的任一种可能的实现方式中方法，或实现上述第二方面或第二方面的任一种可能的实现方式中方法。
第八方面，本申请提供一种通信系统，该通信系统包括第一设备和第二设备。其中，第一设备可以用于执行上述第一方面或第一方面的任一种可能的实现方式中方法，第二设备可以用于执行上述第二方面或第二方面的任一种可能的实现方式中方法。
上述第二方面至第八方面中任一方面可以达到的技术效果可以参照上述第一方面中有益效果的描述，此处不再重复赘述。
附图说明
图1为本申请提供的一种通信系统架构示意图；
图2为本申请提供的一种意图创建的流程示意图；
图3为本申请提供的一种意图合法性检查的方法的流程示意图；
图4为本申请提供的第一种具体场景中的意图合法性检查的方法的流程图；
图5为本申请提供的第二种具体场景中的意图合法性检查的方法的流程图；
图6为本申请提供的第三种具体场景中的意图合法性检查的方法的流程图；
图7为本申请提供的第四种具体场景中的意图合法性检查的方法的流程图；
图8为本申请提供的一种通信装置的结构示意图；
图9为本申请提供的再一种通信装置的结构示意图。
具体实施方式
为了更好的解释本申请实施例，先对本申请中的相关术语或技术解释：
1、意图：对作用系统的期望，包括要求、目标和约束条件，但不用说明如何实现。
2、意图表达式：用来承载意图的表达式。
意图表达式中可以包括动作和对象。其中，动作是指根据意图抽象和简化的网络操作，可以包含意图驱动动作(intent driven action，IDA)名(name)和一系列相关属性(例如，IDA属性，IDA properties)；对象是指根据意图提供的管理对象信息，可以包含意图驱动对象(intent driven object，IDO)名(name)和一系列用于标识对象的属性(例如，IDO属性，IDO properties)。意图的目标值可以包含在动作或者对象中；或者，意图表达式包括动作、对象和目标值。例如，意图为优化小区下行速率，其中，动作是“优化”，对象是“小区”，目标值是小区下行速率的具体数值。
意图表达式中只包含对目标的描述，意图的具体实施方法由意图生产者对意图表达式进行解析、转译得到。意图生产者自己可以确定使用何种方案来满足期望，即意图生产者自己可以确定使用何种方案满足意图。
3、意图冲突：当两个意图因为互斥而无法同时满足时，这两个意图存在意图冲突。意图冲突可以包括语法冲突、操作冲突、效果冲突中的一个或多个。
其中，语法冲突是指两个意图的意图表达式存在冲突。例如，两个意图的意图表达式描述了同一个对象(例如，小区、基站等)在同一生效条件下互斥的目标。一个示例是，一个意图的意图表达式体现的目标为提高小区下行速率，另一个意图的意图表达式体现的目标为降低小区下行速率，则这两个意图之间存在语法冲突。
操作冲突是指两个意图在转译后的执行操作(intent operation)上存在的冲突，即两个意图的操作无法同时执行。例如，两个意图分别对应的方案中包含对同一个网元的同一个参数和/或属性的互斥操作。一个示例是，当意图1的方案要求将网络配置参数A调高，而意图2的方案要求将网络配置参数A调低时，意图1与意图2之间存在操作冲突。
效果冲突是指两个意图在转译后的执行操作在效果上互斥。
4、意图创建：在意图系统中新建一个意图实例，并创建相应意图上下文。
5、意图消费者和意图生产者。
其中，意图消费者，是对意图进行管理的设备。具体的，意图消费者可以生成意图，并向意图生成者发送用于承载该意图的意图表达式。其中，该意图可以是意图消费者对执行意图方案的设备所在网络的需求，例如，该意图可以体现意图消费者对执行意图方案的设备所在网络中至少一个关键绩效指标(key performance indicator，KPI)的需求。
意图生产者，是对意图进行处理的设备。具体的，意图生产者可以在接收到来自意图消费者的意图表达式之后，生成多个能够满足该意图的方案，并从中选择一个用于执行的方案。然后，意图生产者可以将选择的方案发送给执行该意图的设备，以便执行该意图的设备执行选择的方案。
其中，意图消费者和/或意图生产者可以为AN设备，也可以为CN设备。例如，意图消费者可以为网络管理服务(network management service，NMS)、IDMS消费者(IDMS  consumer)或管理服务消费者(management service consumer，MnS consumer)。意图生产者可以为网元管理服务(element management service，EMS)、IDMS生产者(IDMS producer)或管理服务生产者(management service producer，MnS producer)。
应理解，意图消费者和意图生产者也可以采用其他名称，只要具有相同的功能即可，本申请对此不做限定。
下面将结合附图，对本申请实施例应用的通信系统进行描述。
图1示出了本申请示例性提供的一种可能的通信系统的架构，其中，包括IDMS消费者和IDMS生产者，IDMS消费者可实现意图消费者的功能，IDMS生产者可以实现意图生产者的功能，具体内容可参考名词解释部分，此处不再赘述。
IDMS生产者中可包括：意图转译(intent translation，IT)模块、意图评估(intent evaluation，IEv)模块、意图冲突解决(intent conflict resolution，ICR)模块、意图决策(intent decision，ID)模块。其中，意图转译模块、意图评估模块、意图冲突解决模块、意图决策模块可以是独立的实体，也可以是一个或多个实体中的虚拟模块。
具体的，意图转译模块，可以用于进行意图转译，以及生成能够满足意图的方案。例如，意图转译模块可获取意图转译所需要的信息，该信息可以为意图和策略的对应关系；意图转译模块可以根据该对应关系以及从IDMS消费者获取的意图，确定该意图的策略；然后，意图转译模块可以根据该意图的策略，生成能够满足该意图的至少一个方案。
意图评估模块，可以对意图的实现情况进行评估。
意图冲突解决模块，可以对意图冲突进行处理。例如，意图冲突解决模块可以确定两个意图之间是否存在意图冲突。
意图决策模块，可以决定执行该意图的哪个方案。例如，当意图转译模块生成能够满足意图的至少一个方案时，意图决策模块可以从该至少一个方案中，随机选择一个与其他意图不存在意图冲突的方案来执行，或者，根据预定策略选择一个与其他意图不存在意图冲突的方案来执行(例如，选择时延最小的方案或能耗最小的方案)。
如图2为本申请提供的一种意图创建的流程示意图：
步骤201，IDMS消费者向IDMS生产者发送意图创建请求。
意图创建请求可用于指示待创建的意图实例，具体的，意图创建请求中可包括意图表达式，意图表达式可进一步包括多个属性，一个属性可通过键值对来表示，比如键值对为[attribute，vlaue]，其中，attribute表示属性名称，vlaue表示属性范围，该键值对可用于指示创建的属性名称以及该属性名称对应的属性范围。
步骤202，IDMS生产者根据意图创建请求中意图表达式，创建意图实例。
步骤203，IDMS生产者向IDMS消费者发送意图创建响应。
其中，IDMS生产者在确定意图实例创建成功的情况下，向IDMS消费者发送的意图创建响应可用于指示意图实例创建成功。IDMS生产者在确定意图实例创建失败的情况下，向IDMS消费者发送的意图创建响应可用于指示意图实例创建失败。
在上述方案中，IDMS消费者只能知道当前的意图实例是否创建成功，但是在创建失败的情况下，并不能知道创建失败的原因，从而无法合理修改意图创建请求中意图表达式。
基于上述问题，本申请提供一种意图合法性检查的方法，第一设备可检查意图表达式， 并确定出意图表达式未通过合法性检查的原因，将该未通过合法性检查的原因告知第二设备。相应的，第二设备可基于未通过合法性检查的原因，对意图表达式进行有针对性的修改，并基于修改之后的意图表达式向第一设备请求创建意图。
其中，第一设备可以是意图生产者，比如是EMS、IDMS生产者或MnS生产者等。第二设备可以是意图消费者，比如是NMS、IDMS消费者或MnS消费者等。
参照图3示出的一种意图合法性检查的方法的流程图：
步骤301，第二设备向第一设备发送第一意图表达式。
其中，第一意图表达式用于创建意图实例。第一意图表达式中包括多个属性，属性可以是目标，也可以是约束条件。
进一步的，一个属性中可包括有属性名称和属性名称对应的属性范围。举例来说，当属性具体是目标时，该目标可以是“吞吐率>5kbps”，其中属性名称是“吞吐率”，属性名称对应的属性范围是“>5kbps”。又或者，当属性具体是约束条件时，该约束条件可以是“用户>80％”，其中属性名称是“用户”，属性名称对应的属性范围是“>80％”。
可选的，约束条件与目标可以是对应关系，约束条件用于约束其对应目标的生效条件。比如约束条件“用户>80％”，与目标“吞吐率>5kbps”二者具有对应关系，则可表示“需要实现80％以上的用户对应的吞吐率在5kbps以上”。
步骤302，第一设备对第一意图表达式进行合法性检查。
合法性检查可用于指示第一设备是否进一步根据第一意图表达式创建对应的意图实例。示例性的，在第一意图表达式通过合法性检查时，第一设备可根据该第一意图表达式创建意图实例，且可成功创建该意图实例。在第一意图表达式未通过合法性检查时，第一设备无需根据该第一意图表达式创建意图实例。
其中合法性检查可至少包括属性冲突检查和语法词法检查中的一项或多项。如下先对属性冲突检查和语法词法检查解释。
一、属性冲突检查
属性之间存在冲突的冲突类型可以包括语法冲突、操作冲突和语义冲突中的一项或多项，如下以两个属性为例解释。
语法冲突指的是，两个属性的属性名称相同，且其中一个属性的属性范围与另一个属性的属性范围的交集为空。比如，一个属性是“吞吐率>5kbps”，另一个属性是“吞吐率≤5kbps”，那么该两个属性对应的属性名称均是“吞吐率”，且对应的属性范围之间无交集，二者之间是存在语法冲突的。
操作冲突指的是，一个属性的属性名称和属性范围所指示的操作，与另一个属性的属性名称和属性范围所指示的操作之间互斥(或者说两个操作无法同时被执行)。比如，一个属性是“能效等级2级”，其中，该属性的属性名称是“能效等级”，属性范围是“2级”，二者共同指示的操作是打开符号关断开关；而另一个属性是“吞吐率≥10kbps”，其中，该属性的属性名称是“吞吐率”，属性范围是“≥10kbps”，二者共同指示的操作是关闭符号关断开关，则两个操作不能同时被执行，即存在操作冲突。
语义冲突指的是，一个属性的属性名称和属性范围所指示的操作，与另一个属性的属性名称和属性范围所指示的操作被同时执行时，二者能够达到的效果互斥(或者说两个操作无法同时达到预期的效果)。比如，一个属性是“能效等级2级”，其中，属性名称是“能 效等级”，属性范围是“2级”；而另一个属性是“吞吐率≥10kbps”，其中，属性名称是“吞吐率”，属性范围是“≥10kbps”。通过预估，在能效等级为2级时对应的吞吐率需要小于10kbps，如此，该两个属性对应的预期效果是不能同时被达到的。
需要指出的是，上述冲突可以是两个属性之间存在冲突，还可以是多个属性之间存在冲突。比如属性1是“吞吐率≤5kbps”，属性2是“5kbps＜吞吐率＜10kbps”，属性3是“10kbps≤吞吐率”，那么该三个属性在属性名称相同的情况下，属性范围之间是无交集，也即，属性1、属性2和属性3三者之间存在语法冲突。当然，本申请还可包括其他的多个属性之间存在冲突的例子，不再一一举例。
上述语法冲突、操作冲突和语义冲突分别对应于语法冲突检查、操作冲突检查和语义冲突检查。第一设备在进行属性冲突检查时，具体可以执行语法冲突检查、操作冲突检查、语义冲突检查中的一项或多项。
在一个具体示例中，第一设备对第一意图表达式执行语法冲突检查、操作冲突检查和语义冲突检查。第一设备若确定第一意图表达式通过该三项冲突检查，则可确定第一意图表达式通过属性冲突检查；第一设备若确定第一意图表达式未通过该三项冲突检查中的一项，则可确定该第一意图表达式未通过属性冲突检查。
或者，第一设备还可对第一意图表达式执行语法冲突检查、操作冲突检查和语义冲突检查中的一项冲突检查，并在第一意图表达式通过该一项冲突检查时，确定第一意图表达式通过属性冲突检查；以及在第一意图表达式未通过该一项冲突检查时，确定第一意图表达式未通过属性冲突检查。又或者，第一设备还可对第一意图表达式执行语法冲突检查、操作冲突检查和语义冲突检查中的两项冲突检查，具体可参照上述描述，不再赘述。
二、语法词法检查
第一设备可检查第一意图表达式包括的多个属性中，是否存在不符合语法词法检查的属性，其中，语法词法检查可以基于第一设备中的意图模板执行。
其中，意图模板中可包括多个模板属性名称和多个模板属性名称对应的模板属性范围。示例性的，意图模板中包括N个模板属性名称，N为正整数，且该N个模板属性名称可分别对应于自己的模板属性范围，也可以理解，意图模板中包括模板属性名称1和模板属性名称1对应的模板属性范围1，模板属性名称2和模板属性名称2对应的模板属性范围2，……，模板属性名称N和模板属性名称N对应的模板属性范围N。
其中，意图模板可以是在第一设备中预先配置的，或者是第一设备从意图系统管理设备中动态加载的，在后一种情况中，该意图模板可以实现定周期更新，或者在需要时由系统管理员发起更新。
第一设备可以针对第一意图表达式中的一个属性执行：判断该属性的属性名称是否在意图模板中；在确定该属性的属性名称在意图模板中之后，判断该属性的属性范围是否超出意图模板中该属性的属性名称对应的模板属性范围。
具体的，第一设备若确定该属性中，属性名称在意图模板中，且属性范围未超出意图模板中该属性名称对应的模板属性范围，则可确定该属性的通过语法词法检查，即该属性的语法词法正确。第一设备若确定该属性中，属性名称未在意图模板中，或者，若确定该属性名称在意图模板中，但是属性范围超出了意图模板中对应的模板属性范围，则可确定该属性未通过语法词法检查，即该属性的语法词法错误。
进一步的，第一设备若确定该属性中的属性名称未在意图模板中，则可认为错误类型是语法错误，第一设备若确定该属性中的属性范围超出了意图模板中对应的模板属性范围，则可认为错误类型是词法错误。
比如，第一意图表达式中包括属性“5kbps＜吞吐率＜8kbps”，第一设备的意图模板中包括“5kbps＜吞吐率＜10kbps”，那么第一设备可确定该属性的语法词法正确。
再比如，第一意图表达式中包括属性“10kbps≤吞吐率”，第一设备的意图模板中包括“5kbps＜吞吐率＜10kbps”，那么第一设备可确定该属性名称在意图模板中，但是该属性范围超出了意图模板中该属性对应的模板属性范围，即该属性存在语法词法错误，且错误类型具体是词法错误。
在一种可能方式中，第一设备可执行属性冲突检查和语法词法检查，在确定第一意图表达式未通过其中一个检查时，确定第一意图表达式未通过合法性检查。在确定第一意图表达式通过属性冲突检查和语法词法检查时，确定第一意图表达式通过合法性检查。
一个示例中，该第一意图表达式中包括相互冲突的第一属性和第二属性，也可理解为，第一设备不能基于该第一属性中的第一属性名称和第一属性范围，以及第二属性中的第二属性名称和第二属性范围生成意图实例。其中，第一属性和第二属性可以均是目标，即第一意图表达式中包括相互冲突的第一目标和第二目标；第一属性和第二属性也可以均是约束条件，即第一意图表达式中包括相互冲突的第一约束条件和第二约束条件。其中，目标是指意图想要达到的目的，而约束是指达到目标的约束条件，比如“在能耗增加不高于30％的情况下使终端平均吞吐率提高30％”，其中“终端平均吞吐率提高30％”为意图目标，而“能耗增加不高于30％”为约束条件。
进一步的，第一设备在对第一意图表达式进行属性冲突检查时，可确定出第一意图表达式中的第一属性和第二属性之间存在冲突，其中，第一属性和第二属性相互冲突的冲突类型可以是语法冲突、操作冲突和语义冲突中的一项或多项。
再一个示例中，第一意图表达式中可包括第三属性，该第三属性中可包括第三属性名称和第三属性范围，该第三属性不符合第一设备中的意图模板。第一设备在对第一意图表达式进行语法词法检查时，具体可以是第一设备确定第三属性名称未包含于意图模板的多个模板属性名称中；或者是，第一设备确定第三属性名称包含于意图模板的多个模板属性名称中之后，确定第三属性范围超出意图模板中第三属性对应的模板属性范围。
步骤303，第一设备若确定第一意图表达式未通过合法性检查，则可向第二设备发送失败信息，该失败信息可用于指示第一意图表达式不能用于成功创建意图实例。
其中，失败信息可以是创建失败信息，该创建失败信息可用于指示第一意图表达式不能成功创建意图实例的原因，或者说，创建意图实例失败的原因。
失败信息还可以是检查失败信息，该检查失败信息可用于指示第一意图表达式未通过合法性检查的失败原因，或者说，第一设备对第一意图表达式进行合法性检查失败的原因。
需要指出的是，在第一意图表达式未通过合法性检查情况下，该第一意图表达式不能被成功创建意图实例，也可以理解，创建失败信息与检查失败信息为相同信息。对于第二设备来说，第二设备接收来自第一设备的失败信息之后，即可知道当前的第一意图表达式不能用于成功创建意图实例。为方便说明，如下均以失败信息为例。
失败信息中可包括如下字段中的一个或多个：属性冲突字段、语法词法错误字段。
属性冲突字段可用于指示第一意图表达式未通过合法性检查的失败原因包括第一意图表达式中存在的具有相互冲突的属性。其中，属性冲突字段中可包括具有相互冲突的属性、具有相互冲突的属性之间存在冲突的类型。
示例性的，第一意图表达式中包括具有相互冲突的第一属性和第二属性，相应的，属性冲突字段中可包括第一属性、第二属性，以及第一属性、第二属性之间的冲突类型。比如，第一属性是“吞吐率≤5kbps”，第二属性是“吞吐率＞5kbps”，属性冲突字段中可包括该两个属性，即“吞吐率≤5kbps”、“吞吐率＞5kbps”，以及冲突类型“语法冲突”。
语法词法错误字段可用于指示第一意图表达式未通过合法性检查的失败原因包括第一意图表达式中存在的具有语法词法错误的属性。其中，语法词法错误字段中可包括属性名称和/或属性范围未包含于意图模板中的属性。
示例性的，第一意图表达式中包括具有语法词法错误的第三属性，语法词法错误字段中可包括第三属性，以及第三属性的错误类型。比如，第三属性为“10kbps≤吞吐率”，且第三属性中的属性范围超出了意图模板中的“吞吐率”对应的模板属性范围，则语法词法错误字段为“10kbps≤吞吐率”，以及错误类型是词法错误。
可选的，失败信息中还可包括失败指示字段，该失败指示字段可用于向第二设备指示第一意图表达式未通过合法性检查，或者向第二设备指示第一设备根据第一意图表达式不能成功创建意图实例。
在第一意图表达式未通过合法性检查的情况下，本申请提供如下两种实现方式：
实现方式1，第二设备可根据失败信息，对第一意图表达式进行修改以得到第二意图表达式，然后向第一设备发送第二意图表达式。
相应的，第一设备接收到第二意图表达式，第一设备对第二意图表达式进行合法性检查。具体实现方式参见上述步骤301至302，把“第一意图表达式”替换成“第二意图表达式”即可。进一步的，若第一设备确定第二意图表达式未通过合法性验证，则继续向第二设备发送失败信息，第一设备继续修改意图表达式。如此，循环上述步骤中第一设备和第二设备的动作，直至第一设备确定第二设备的意图表达式通过合法性验证。
上述技术方案中，第二设备向第一设备发送第一意图表达式，第一设备可对第一意图表达式进行合法性检查，在确定第一意图表达式未通过合法性检查时，向第二设备发送失败信息，即告知第二设备第一意图表达式未通过合法性验证的原因。从而第二设备可以基于该错误原因对第一意图表达式进行有针对性的修改，如此有助于第二设备向第一设备发送可通过合法性检查的意图表达式，相应的，第一设备可以基于该通过合法性检查的意图表达式来创建对应的意图实例，如此可提高意图创建成功率。
实现方式2，第一设备根据第一意图表达式，向第二设备发送推荐意图表达式，其中该推荐意图表达式是可通过合法性检查的。
具体的，第一设备可以根据第一意图表达式中具有冲突的属性，和/或，具有语法词法错误的属性，生成推荐意图表达式。如下，以相互冲突的第一属性和第二属性，以及具有语法词法错误的第三属性为例说明：
(1)第一设备根据第一属性中的第一属性名称和第一属性范围，以及第二属性中的第二属性名称和第二属性范围，调整其中一个属性范围，或者调整两个属性范围，或者删 除其中一个属性，以使得第一属性和第二属性二者不存在属性冲突。
(2)若第一意图表达式中第三属性中的第三属性名称包含于意图模板中，而第三属性中的第三属性范围超出意图模板中第三属性对应的模板属性范围，则第一设备可调整第三属性范围至包含于第三属性对应的模板属性范围中。
(3)若第一意图表达式中第三属性中的第三属性名称未包含于意图模板中，则第一设备可将该属性从第一意图表达式中删除。
第二设备接收来自第一设备的推荐意图表达式，确定是否接受该推荐意图表达式，进而向第一设备发送接受指示或拒绝指示，其中，接受指示可用于指示第二设备接受该推荐意图表达式，拒绝指示可用于指示第二设备拒绝采用该推荐意图表达式。
在第二设备向第一设备发送接受指示的情况下，第一设备可接收来自第二设备的接受指示。可选的，第一设备还可根据推荐意图表达式，生成意图实例，并将创建意图实例的创建成功信息发送至第一设备。
在第二设备向第一设备发送拒绝指示的情况下，第二设备还可根据失败信息和第一意图表达式，生成第二意图表达式，然后向第一设备发送第二意图表达式，具体可参见上述第一种实现方式，此处不再赘述。
其中，第二设备可将拒绝指示和第二意图表达式包含于同一条消息中，或者还可以将拒绝指示和第二意图表达式分别包含于两条消息中。
又或者，可以将第二意图表达式理解为一种拒绝指示，当第二设备拒绝采用该推荐意图表达式时，可以直接向第一设备发送第二意图表达式，以向第一设备指示第二设备拒绝使用推荐意图表达式，以及指示第一设备对第二意图表达式继续进行合法性检查。
上述技术方案中，第二设备向第一设备发送第一意图表达式，第一设备可对第一意图表达式进行合法性检查，在确定第一意图表达式未通过合法性检查时，向第二设备发送推荐意图表达式，即向第二设备推荐可通过合法性验证的意图表达式，相应的，在第二设备可接受该推荐的意图表达式，第一设备可基于该推荐意图表达式创建意图实例，有助于提高意图实例创建的效率以及成功率。进一步的，第一设备还可以向第二设备发送失败原因，第二设备在拒绝接受该推荐意图表达式时，第二设备可基于该错误原因对第一意图表达式进行有针对性的修改，如此，第二设备可向第一设备发送可通过合法性检查的意图表达式，有助于提高意图实例创建的灵活性。
上述各信息可以通过第一设备和第二设备之间的不同消息传递，如下提供两个示例：
示例1，意图创建请求和意图创建响应。
第二设备向第一设备发送的第一意图表达式，可包含于意图创建请求中，该意图创建请求指示第一设备根据意图创建请求中该第一意图表达式创建意图实例。进一步的，该意图创建请求中还包括检查指示(flag)，该检查指示可用于指示第一设备在创建意图实例之前，对该第一意图表达式进行合法性检查。
第一设备在确定第一意图表达式通过合法性检查之后，可根据第一意图表达式创建意图实例，在将意图实例创建成功之后向第二设备发送意图创建响应，该意图创建响应中包括创建成功信息，以指示第一意图表达式对应的意图实例被创建成功。
又或者，第一设备可在确定第一意图表达式通过合法性检查之后，向第二设备发送用于指示通过合法性检查的检查成功信息；以及在创建意图实例之后，向第二设备发送包含 有创建成功信息的意图创建响应，该意图创建响应可用于指示意图实例被创建成功。
第一设备在确定第一意图表达式未通过合法性检查之后，则可向第二设备发送失败信息，该失败信息包含于意图创建响应中。相应的，第二设备接收到该意图创建响应之后，可再次向第一设备发送包含有第二意图表达式的意图创建请求，第一设备进而检查该意图创建请求中的第二意图表达式是否通过合法性检查。
或者另外的示例中，第二设备可向第一设备发送包含有第二意图表达式的意图修改请求，第一设备根据该意图修改请求中的第二意图表达式进行合法性检查。
此外，第一设备在创建意图实例之后，还可以不向第二设备发送包含有创建成功信息的意图创建响应。相应的，第二设备在发送意图创建请求之后，若确定预设时长到达之后，未接收到来自第一设备的包含有失败信息的意图创建响应，则可确定第一意图表达式对应的意图实例已被成功创建。当然还可以有其他的实现方式，本申请不再一一举例。
还需要补充的是，本申请中第一设备在接收到第一意图表达式之后，还可以不执行合法性检查，而是直接根据第一意图表达式创建意图实例，若创建意图实例失败，则可向第二设备发送创建失败信息(此处与检查失败信息相区分)，创建失败信息中可包括有第一意图表达式不能被成功创建意图实例的原因。
示例2，意图合法性检查请求和意图合法性检查响应。
第二设备向第一设备发送的第一意图表达式，可包含于意图合法性检查请求中，该意图合法性检查请求可用于指示第一设备对该第一意图表达式进行合法性检查。
第一设备在确定第一意图表达式通过合法性检查之后，可向第二设备发送包含有检查成功信息的意图合法性检查响应，该意图合法性检查响应可用于指示第一意图表达式通过合法性检查。第二设备可进一步向第一设备发送意图创建请求，第一设备根据意图创建请求，创建意图实例。可选的，该意图创建请求中可包括第一意图表达式。
或者，第一设备在确定第一意图表达式未通过合法性检查之后，向第二设备发送包含有失败信息的意图合法性检查响应，该意图合法性检查响应可用于指示第一意图表达式未通过合法性检查。第二设备可进一步向第一设备发送包含有第二意图表达式的意图合法性检查请求，用于指示第一设备再次对第二意图表达式进行合法性检查。
此外，第一设备在确定第一意图表达式通过合法性检查之后，还可以不向第二设备发送包含有检查成功信息的意图合法性检查响应。相应的，第二设备在发送意图合法性检查请求之后，若确定预设时长到达之后，未接收到来自第一设备的包含有失败信息的意图合法性检查响应，则可确定第一意图表达式已通过合法性检查，可继续向第一设备发送意图创建请求。当然还可以有其他的实现方式，本申请不再一一举例。
此外，第一意图表达式还可以包含于其他消息中，比如意图表达式错误检查请求，意图错误检查请求，意图属性冲突检查请求中，相应的，第一意图表达式对应的检查结果可包含于对应的响应中。
基于上述相同的发明构思，如下提供四种具体实施例，其中第一设备是IDMS生产者，第二设备是IDMS消费者。
实施例1、IDMS消费者向IDMS生产者发送意图创建请求，IDMS生产者对意图创建请求中的第一意图表达式进行合法性检查，具体可参见图4的流程示意图。
步骤401，IDMS消费者向IDMS生产者发送意图创建请求。
意图创建请求中包括第一意图表达式和检查指示(flag)，检查指示用于指示IDMS生产者对第一意图表达式进行合法性检查，具体实现方式可参见上述步骤301中描述。
步骤402，IDMS生产者对第一意图表达式进行合法性检查。
IDMS生产者可对第一意图表达式进行词法语法检查，以及属性冲突检查，具体实现方式可参见上述步骤302中描述。
其中，在第一意图表达式未通过合法性检查情况下，执行下述步骤403至步骤405，在第一意图表达式通过合法性检查情况下，执行下述步骤406和步骤407。
步骤403，IDMS生产者向IDMS消费者发送意图创建响应，其中意图创建响应中包括失败信息，以指示第一意图表达式未通过合法性检查，以及未通过合法性检查的原因。
示例性的，该失败信息中至少有如下字段：失败指示字段、语法词法错误字段和属性冲突字段，具体实现方式可参见上述步骤303中描述。
步骤404，IDMS消费者根据意图创建响应中包括的失败信息，修改第一意图表达式，得到第二意图表达式，具体实现方式可参见上述步骤303中描述。
步骤405，IDMS消费者向IDMS生产者发送意图创建请求或意图修改请求，其中，意图创建请求或意图修改请求中包括第二意图表达式。可选的，意图创建请求或意图修改请求中还可包括检查指示(flag)。
步骤406，IDMS生产者根据意图创建请求，创建意图实例。
步骤407，IDMS生产者向IDMS消费者发送意图创建响应，其中意图创建响应中包括创建成功信息，以用于向IDMS消费者指示成功创建意图实例。
实施例2、IDMS消费者向IDMS生产者发送意图合法性检查请求，IDMS生产者对意图合法性检查请求中的第一意图表达式进行合法性检查，具体可参见图5的流程示意图。
步骤501，IDMS消费者向IDMS生产者发送意图合法性检查请求，意图合法性检查请求指示IDMS生产者对意图合法性检查请求中包括的第一意图表达式进行合法性检查，具体实现方式可参见上述步骤301中描述。
步骤502，IDMS生产者对第一意图表达式进行合法性检查。
IDMS生产者可对第一意图表达式进行词法语法检查，以及属性冲突检查，具体实现方式可参见上述步骤302中描述。
其中，在第一意图表达式未通过合法性检查情况下，执行下述步骤503至步骤505，在第一意图表达式通过合法性检查情况下，执行下述步骤506和步骤509。
步骤503，IDMS生产者向IDMS消费者发送意图合法性检查响应，其中意图合法性检查响应中包括失败信息(具体可以是检查失败信息)，以指示第一意图表达式未通过合法性检查，以及未通过合法性检查的原因。
示例性的，该失败信息中至少有如下字段：失败指示字段、语法词法错误字段和属性冲突字段，具体实现方式可参见上述步骤303中描述。
步骤504，IDMS消费者根据意图合法性检查响应中包括的失败信息，修改第一意图表达式，得到第二意图表达式，具体实现方式可参见上述步骤303中描述。
步骤505，IDMS消费者向IDMS生产者发送意图创建请求，其中，意图创建请求中包括第二意图表达式。
在另外的实施例中，IDMS消费者还可向IDMS生产者再次发送意图合法性检查请求，以指示IDMS生产者对意图合法性检查请求中包括的第二意图表达式进行合法性检查。
步骤506，IDMS生产者向IDMS消费者发送意图合法性检查响应，其中意图合法性检查响应中包括检查成功信息，以指示第一意图表达式通过合法性检查。
步骤507，IDMS消费者向IDMS生产者发送意图创建请求，以指示IDMS生产者根据第一意图表达式创建意图实例。可选的，该意图创建请求中包括第一意图表达式。
步骤508，IDMS消费者根据意图创建请求，创建意图实例。
步骤509，IDMS消费者向IDMS生产者发送意图创建响应，其中意图创建响应中包括创建成功信息，以用于向IDMS消费者指示成功创建意图实例。
其中，步骤505至步骤509中未详细描述的实现方式均可参见图3相关实施例中描述。
实施例3、IDMS消费者向IDMS生产者发送意图创建请求，IDMS生产者对意图创建请求中的第一意图表达式进行合法性检查，且在确定第一意图表达式未通过合法性检查之后，向IDMS消费者发送推荐意图表达式，具体可参见图6的流程示意图。
步骤601，IDMS消费者向IDMS生产者发送意图创建请求，意图创建请求中包括第一意图表达式和检查指示(flag)，检查指示用于指示IDMS生产者对第一意图表达式进行合法性检查，具体实现方式可参见上述步骤301中描述。
步骤602，IDMS生产者对第一意图表达式进行合法性检查。
IDMS生产者可对第一意图表达式进行词法语法检查，以及属性冲突检查，具体实现方式可参见上述步骤302中描述。
其中，在第一意图表达式未通过合法性检查情况下，执行下述步骤603至步骤610，在第一意图表达式通过合法性检查情况下，执行下述步骤611和步骤612。
步骤603，IDMS生产者向IDMS消费者发送意图创建响应，其中意图创建响应中包括失败信息，以指示第一意图表达式未通过合法性检查，以及未通过合法性检查的原因。
示例性的，该失败信息中至少有如下字段：失败指示字段、语法词法错误字段和属性冲突字段，具体实现方式可参见上述步骤303中描述。
步骤604，IDMS生产者根据第一意图表达式，生成推荐意图表达式，向第二设备发送推荐意图表达式，其中该推荐意图表达式是可通过合法性检查的。
相应的，IDMS消费者可根据来自IDMS生产者的推荐意图表达式，确定是否接收该推荐意图表达式，如下分两种情况：
在IDMS消费者接受推荐意图表达式的情况下：
步骤605，IDMS消费者向IDMS生产者发送接受指示，以用于指示IDMS消费者接受该推荐意图表达式。
步骤606，IDMS生产者根据该推荐意图表达式，创建意图实例。
步骤607，IDMS生产者向IDMS消费者发送意图创建响应，其中意图创建响应中包括创建成功信息，以用于向IDMS消费者指示成功创建意图实例。
在IDMS消费者拒绝接受推荐意图表达式的情况下：
步骤608，IDMS消费者向IDMS生产者发送拒绝指示，以用于指示IDMS消费者拒绝接受该推荐意图表达式。
步骤609，IDMS消费者根据意图创建响应中包括失败信息，修改第一意图表达式， 以得到第二意图表达式。
步骤610，IDMS消费者向IDMS生产者发送意图创建请求或意图修改请求，其中，意图创建请求或意图修改请求中包括第二意图表达式。可选的，意图创建请求或意图修改请求中还可包括检查指示(flag)。
步骤611，IDMS生产者根据意图创建请求，创建意图实例。
步骤612，IDMS生产者向IDMS消费者发送意图创建响应，其中意图创建响应中包括创建成功信息，以用于向IDMS消费者指示成功创建意图实例。
需要补充的是，步骤603为可选步骤，也可以在步骤602之后直接执行步骤604。或者可不限定IDMS生产者向IDMS消费者发送该包含有失败信息的意图创建响应，以及向IDMS消费者发送推荐意图表达式的先后顺序。此外，该包含有失败信息的意图创建响应中，还可同时包括有推荐意图表达式，或者其他方式。
其中，步骤604至步骤612中未详细描述的实现方式均可参见图3相关实施例中描述。
实施例4、IDMS消费者向IDMS生产者发送意图合法性检查请求，IDMS生产者对意图合法性检查请求中的第一意图表达式进行合法性检查，且在确定第一意图表达式未通过合法性检查之后，向IDMS消费者推荐意图表达式，具体可参见图7的流程示意图。
步骤701，IDMS消费者向IDMS生产者发送意图合法性检查请求，意图合法性检查请求用于指示IDMS生产者对意图合法性检查请求中的第一意图表达式进行合法性检查，具体实现方式可参见上述步骤301中描述。
步骤702，IDMS生产者对第一意图表达式进行合法性检查。
IDMS生产者可对第一意图表达式进行词法语法检查，以及属性冲突检查，具体实现方式可参见上述步骤302中描述。
其中，在第一意图表达式未通过合法性检查情况下，执行下述步骤703至步骤710，在第一意图表达式通过合法性检查情况下，执行下述步骤711至步骤714。
步骤703，IDMS生产者向IDMS消费者发送意图合法性检查响应。
其中意图合法性检查响应中包括失败信息(具体可以是检查失败信息)，以指示第一意图表达式未通过合法性检查，以及未通过合法性检查的原因。
示例性的，该失败信息中至少有如下字段：失败指示字段、语法词法错误字段和属性冲突字段，具体实现方式可参见上述步骤303中描述。
步骤704，IDMS生产者根据第一意图表达式，生成推荐意图表达式，向第二设备发送推荐意图表达式，其中该推荐意图表达式是可通过合法性检查的。
相应的，IDMS消费者可根据来自IDMS生产者的推荐意图表达式，确定是否接收该推荐意图表达式，如下分两种情况：
在IDMS消费者接受推荐意图表达式的情况下：
步骤705，IDMS消费者向IDMS生产者发送意图创建请求，其中意图创建请求中包括接受指示，以用于指示IDMS消费者接受该推荐意图表达式，并指示IDMS生产者根据该推荐意图表达式创建意图实例。
步骤706，IDMS生产者根据该推荐意图表达式，创建意图实例。
步骤707，IDMS生产者向IDMS消费者发送意图创建响应，其中意图创建响应中包括创建成功信息，以用于指示IDMS生产者已成功创建意图实例。
在IDMS消费者拒绝接受推荐意图表达式的情况下：
步骤708，IDMS消费者向IDMS生产者发送拒绝指示，以用于指示IDMS消费者拒绝接受该推荐意图表达式。
步骤709，IDMS消费者根据意图合法性检查响应中包括失败信息，修改第一意图表达式，以得到第二意图表达式。
步骤710，IDMS消费者向IDMS生产者发送意图合法性检查请求，以用于指示IDMS生产者对意图合法性检查请求中包括的第二意图表达式进行合法性检查。
步骤711，IDMS生产者向IDMS消费者发送意图合法性检查响应，其中意图合法性检查响应中包括检查成功信息，以指示第一意图表达式通过合法性检查。
步骤712，IDMS消费者向IDMS生产者发送意图创建请求，以指示IDMS生产者根据第一意图表达式创建意图实例。可选的，该意图创建请求中包括第一意图表达式。
步骤713，IDMS生产者根据意图创建请求，创建意图实例。
步骤714，IDMS生产者向IDMS消费者发送意图创建响应，其中意图创建响应中包括创建成功信息，以用于指示IDMS生产者已成功创建意图实例。
其中，步骤704至步骤714中未详细描述的实现方式均可参见图3相关实施例中描述。
基于上述内容和相同构思，图8和图9为本申请提供的可能的通信装置的结构示意图。这些通信装置可以用于实现上述方法实施例中功能，因此也能实现上述方法实施例所具备的有益效果。如图8所示，该通信装置800包括处理模块801和收发模块802。
通信装置800用于实现上述图3中所示的方法实施例中第一设备的功能，或者用于实现上述图4至图7中的IDMS生产者的功能时：
在一种可能的实现方式中，处理模块801，用于控制收发模块802接收第二设备的第一意图表达式，第一意图表达式用于创建意图实例；处理模块801，还用于根据第一意图表达式，控制收发模块802向第二设备发送失败信息，失败信息用于指示创建意图实例的失败原因；其中，第一意图表达式中包括多个属性，失败原因包括第一意图表达式中存在相互冲突的属性，属性是目标或者约束条件。
在一种可能的实现方式中，处理模块801根据第一意图表达式，控制收发模块802向第二设备发送失败信息时，具体用于：对第一意图表达式进行合法性检查；在确定第一意图表达式未通过合法性检查之后，根据未通过合法性检查的原因，生成失败信息。
在一种可能的实现方式中，失败原因包括第一意图表达式中存在相互冲突的第一属性与第二属性，第一属性包括第一属性名称和第一属性范围，第二属性包括第二属性名称和第二属性范围；冲突的类型包括如下中一个或多个：语法冲突，用于指示第一属性名称与第二属性名称相同，且第一属性范围与第二属性范围的交集为空；操作冲突，用于指示第一属性名称和第一属性范围所指示的操作，与第二属性名称和第二属性范围所指示的操作之间互斥；效果冲突，用于指示第一属性名称和第一属性范围所指示的操作，与第二属性名称和第二属性范围所指示的操作被同时执行时，二者能够达到的效果互斥。
在一种可能的实现方式中，失败信息中包括第一属性、第二属性，以及第一属性与第二属性的冲突的类型。
在一种可能的实现方式中，失败原因还包括第一意图表达式中的第三属性不符合通信装置800中的意图模板；意图模板中包括多个模板属性名称和多个模板属性名称分别对应 的模板属性范围；第三属性包括第三属性名称和第三属性范围；第一意图表达式中的第三属性不符合通信装置800中的意图模板，包括：第三属性名称未包含于意图模板的多个模板属性名称中；或者，第三属性范围超出意图模板中第三属性对应的模板属性范围。
在一种可能的实现方式中，失败信息中还包括第三属性。
在一种可能的实现方式中，处理模块801还用于：根据第一意图表达式，控制收发模块802向第二设备发送推荐意图表达式；在确定第二设备接受推荐意图表达式之后，根据推荐意图表达式创建意图实例。
在一种可能的实现方式中，处理模块801还用于：控制收发模块802接收第二设备的第二意图表达式，第二意图表达式是第二设备根据失败原因对第一意图表达式进行修改后得到的。
在一种可能的实现方式中，第一意图表达式包含于意图创建请求中，失败信息包含于意图创建响应中；第二意图表达式包含于意图修改请求中。
在一种可能的实现方式中，意图创建请求中包括还检查指示，检查指示用于指示通信装置800对第一意图表达式进行合法性检查。
在一种可能的实现方式中，第一意图表达式包含于意图合法性检查请求中，失败信息包含于意图合法性检查响应中；第二意图表达式包含于意图创建请求中。
在一种可能的实现方式中，失败信息中包括如下的一项或多项：具有相互冲突的属性、具有相互冲突的属性之间存在冲突的类型；属性名称和/或属性范围未包含于意图模板中的属性。
通信装置800用于实现上述图3中所示的方法实施例中第二设备的功能，或者用于实现上述图4至图7中的IDMS消费者的功能：
在一种可能的实现方式中，处理模块801，用于控制收发模块802向第一设备发送第一意图表达式，第一意图表达式用于创建意图实例；处理模块801，还用于控制收发模块802接收第一设备的失败信息，失败信息用于指示创建意图实例的失败原因；其中，第一意图表达式中包括多个属性，失败原因包括第一意图表达式中存在相互冲突的属性，属性是目标或者约束条件。
在一种可能的实现方式中，处理模块801还用于：控制收发模块802接收来自第一设备的推荐意图表达式，以及向第一设备发送接受推荐意图表达式的指示，推荐意图表达式用于创建意图实例。
在一种可能的实现方式中，处理模块801还用于：根据失败原因，对第一意图表达式进行修改后得到的第二意图表达式，控制收发模块802向第一设备发送第二意图表达式。
如图9所示为本申请实施例提供的装置900，图9所示的装置可以为图8所示的装置的一种硬件电路的实现方式。该装置可适用于前面所示出的流程图中，执行上述方法实施例中的功能。为了便于说明，图9仅示出了该装置的主要部件。
图9所示的装置900包括通信接口910、处理器920和存储器930，其中存储器930用于存储程序指令和/或数据。处理器920可能和存储器930协同操作。处理器920可能执行存储器930中存储的程序指令。存储器930中存储的指令或程序被执行时，该处理器920用于执行上述实施例中处理模块801执行的操作，通信接口910用于执行上述实施例中收发模块802执行的操作。
存储器930和处理器920耦合。本申请实施例中的耦合是装置、单元或模块之间的间 接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。所述存储器930中的至少一个可以包括于处理器920中。
在本申请实施例中，通信接口可以是收发器、电路、总线、模块或其它类型的通信接口。在本申请实施例中，通信接口为收发器时，收发器可以包括独立的接收器、独立的发射器；也可以集成收发功能的收发器、或者是通信接口。
装置900还可以包括通信线路940。其中，通信接口910、处理器920以及存储器930可以通过通信线路940相互连接；通信线路940可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，简称EISA)总线等。所述通信线路940可以分为地址总线、数据总线、控制总线等。为便于表示，图9中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的保护范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (29)

  1. 一种意图合法性检查的方法，其特征在于，包括：
    第一设备接收第二设备的第一意图表达式，所述第一意图表达式用于创建意图实例；
    所述第一设备根据所述第一意图表达式，向所述第二设备发送失败信息，所述失败信息用于指示创建所述意图实例的失败原因；
    其中，所述第一意图表达式中包括多个属性，所述失败原因包括所述第一意图表达式中存在相互冲突的属性，属性是目标或者约束条件。
  2. 如权利要求1所述的方法，其特征在于，所述第一设备根据所述第一意图表达式，向所述第二设备发送失败信息，包括：
    所述第一设备对所述第一意图表达式进行合法性检查；
    所述第一设备在确定所述第一意图表达式未通过所述合法性检查之后，根据未通过所述合法性检查的原因，生成所述失败信息。
  3. 如权利要求1或2所述的方法，其特征在于，所述失败原因包括所述第一意图表达式中存在相互冲突的第一属性与第二属性，所述第一属性包括第一属性名称和第一属性范围，所述第二属性包括第二属性名称和第二属性范围；
    所述冲突的类型包括如下中一个或多个：
    语法冲突，用于指示所述第一属性名称与所述第二属性名称相同，且所述第一属性范围与所述第二属性范围的交集为空；
    操作冲突，用于指示所述第一属性名称和所述第一属性范围所指示的操作，与所述第二属性名称和所述第二属性范围所指示的操作之间互斥；
    效果冲突，用于指示所述第一属性名称和所述第一属性范围所指示的操作，与所述第二属性名称和所述第二属性范围所指示的操作被同时执行时，二者能够达到的效果互斥；
    所述失败信息中包括所述第一属性、所述第二属性，以及所述第一属性与所述第二属性的冲突的类型。
  4. 如权利要求1至3任一项所述的方法，其特征在于，所述失败原因还包括所述第一意图表达式中的第三属性不符合所述第一设备中的意图模板；
    所述意图模板中包括多个模板属性名称和所述多个模板属性名称分别对应的模板属性范围；所述第三属性包括第三属性名称和第三属性范围；
    所述第一意图表达式中的第三属性不符合所述第一设备中的意图模板，包括：
    所述第三属性名称未包含于所述意图模板的多个模板属性名称中；
    或者，所述第三属性范围超出所述意图模板中所述第三属性对应的模板属性范围；
    所述失败信息中还包括所述第三属性。
  5. 如权利要求1至4任一项所述的方法，其特征在于，还包括：
    所述第一设备根据所述第一意图表达式，向所述第二设备发送推荐意图表达式；
    所述第一设备在确定所述第二设备接受所述推荐意图表达式之后，根据所述推荐意图表达式创建所述意图实例。
  6. 如权利要求1至4任一项所述的方法，其特征在于，还包括：
    所述第一设备接收所述第二设备的第二意图表达式，所述第二意图表达式是所述第二设备根据所述失败原因对所述第一意图表达式进行修改后得到的。
  7. 如权利要求1至6任一项所述的方法，其特征在于，所述第一意图表达式包含于意图创建请求中，所述失败信息包含于意图创建响应中；所述意图创建请求中还包括检查指示，所述检查指示用于指示所述第一设备对所述第一意图表达式进行合法性检查；
    或者，所述第一意图表达式包含于意图合法性检查请求中，所述失败信息包含于意图合法性检查响应中。
  8. 一种意图合法性检查的方法，其特征在于，包括：
    第二设备向第一设备发送第一意图表达式，所述第一意图表达式用于创建意图实例；
    所述第二设备接收所述第一设备的失败信息，所述失败信息用于指示创建所述意图实例的失败原因；
    其中，所述第一意图表达式中包括多个属性，所述失败原因包括所述第一意图表达式中存在相互冲突的属性，属性是目标或者约束条件。
  9. 如权利要求8所述的方法，其特征在于，所述失败原因包括所述第一意图表达式中存在相互冲突的第一属性与第二属性，所述第一属性包括第一属性名称和第一属性范围，所述第二属性包括第二属性名称和第二属性范围；
    所述冲突的类型包括如下中一个或多个：
    语法冲突，用于指示所述第一属性名称与所述第二属性名称相同，且所述第一属性范围与所述第二属性范围的交集为空；
    操作冲突，用于指示所述第一属性名称和所述第一属性范围所指示的操作，与所述第二属性名称和所述第二属性范围所指示的操作之间互斥；
    效果冲突，用于指示所述第一属性名称和所述第一属性范围所指示的操作，与所述第二属性名称和所述第二属性范围所指示的操作被同时执行时，二者能够达到的效果互斥；
    所述失败信息中包括所述第一属性、所述第二属性，以及所述第一属性与所述第二属性的冲突的类型。
  10. 如权利要求8或9所述的方法，其特征在于，所述失败原因还包括所述第一意图表达式中的第三属性不符合所述第一设备中的意图模板；
    所述意图模板中包括多个模板属性名称和所述多个模板属性名称分别对应的模板属性范围；所述第三属性包括第三属性名称和第三属性范围；
    所述第一意图表达式中的第三属性不符合所述第一设备中的意图模板，包括：
    所述第三属性名称未包含于所述意图模板的多个模板属性名称中；
    或者，所述第三属性范围超出所述意图模板中所述第三属性对应的模板属性范围；
    所述失败信息中还包括所述第三属性。
  11. 如权利要求8至10任一项所述的方法，其特征在于，还包括：
    所述第二设备接收来自所述第一设备的推荐意图表达式；
    所述第二设备向所述第一设备发送接受所述推荐意图表达式的指示，所述推荐意图表达式用于创建所述意图实例。
  12. 如权利要求8至10任一项所述的方法，其特征在于，还包括：
    所述第二设备根据所述失败原因，对所述第一意图表达式进行修改后得到的第二意图表达式，向所述第一设备发送所述第二意图表达式。
  13. 如权利要求8至12任一项所述的方法，其特征在于，所述第一意图表达式包含于意图创建请求中，所述失败信息包含于意图创建响应中；所述意图创建请求中还包括检查 指示，所述检查指示用于指示所述第一设备对所述第一意图表达式进行合法性检查；
    或者，所述第一意图表达式包含于意图合法性检查请求中，所述失败信息包含于意图合法性检查响应中。
  14. 一种通信装置，其特征在于，包括：
    处理模块，用于控制收发模块接收第二设备的第一意图表达式，所述第一意图表达式用于创建意图实例；
    所述处理模块，还用于根据所述第一意图表达式，控制所述收发模块向所述第二设备发送失败信息，所述失败信息用于指示创建所述意图实例的失败原因；
    其中，所述第一意图表达式中包括多个属性，所述失败原因包括所述第一意图表达式中存在相互冲突的属性，属性是目标或者约束条件。
  15. 如权利要求14所述的装置，其特征在于，所述处理模块根据所述第一意图表达式，控制所述收发模块向所述第二设备发送失败信息时，具体用于：
    对所述第一意图表达式进行合法性检查；
    在确定所述第一意图表达式未通过所述合法性检查之后，根据未通过所述合法性检查的原因，生成所述失败信息。
  16. 如权利要求14或15所述的装置，其特征在于，所述失败原因包括所述第一意图表达式中存在相互冲突的第一属性与第二属性，所述第一属性包括第一属性名称和第一属性范围，所述第二属性包括第二属性名称和第二属性范围；
    所述冲突的类型包括如下中一个或多个：
    语法冲突，用于指示所述第一属性名称与所述第二属性名称相同，且所述第一属性范围与所述第二属性范围的交集为空；
    操作冲突，用于指示所述第一属性名称和所述第一属性范围所指示的操作，与所述第二属性名称和所述第二属性范围所指示的操作之间互斥；
    效果冲突，用于指示所述第一属性名称和所述第一属性范围所指示的操作，与所述第二属性名称和所述第二属性范围所指示的操作被同时执行时，二者能够达到的效果互斥；
    所述失败信息中包括所述第一属性、所述第二属性，以及所述第一属性与所述第二属性的冲突的类型。
  17. 如权利要求14至16任一项所述的装置，其特征在于，所述失败原因还包括所述第一意图表达式中的第三属性不符合所述装置中的意图模板；
    所述意图模板中包括多个模板属性名称和所述多个模板属性名称分别对应的模板属性范围；所述第三属性包括第三属性名称和第三属性范围；
    所述第一意图表达式中的第三属性不符合所述装置中的意图模板，包括：
    所述第三属性名称未包含于所述意图模板的多个模板属性名称中；
    或者，所述第三属性范围超出所述意图模板中所述第三属性对应的模板属性范围；
    所述失败信息中还包括所述第三属性。
  18. 如权利要求14至17任一项所述的装置，其特征在于，所述处理模块还用于：
    根据所述第一意图表达式，控制所述收发模块向所述第二设备发送推荐意图表达式；
    在确定所述第二设备接受所述推荐意图表达式之后，根据所述推荐意图表达式创建所述意图实例。
  19. 如权利要求14至17任一项所述的装置，其特征在于，所述处理模块还用于：
    控制所述收发模块接收所述第二设备的第二意图表达式，所述第二意图表达式是所述第二设备根据所述失败原因对所述第一意图表达式进行修改后得到的。
  20. 如权利要求14至19任一项所述的装置，其特征在于，所述第一意图表达式包含于意图创建请求中，所述失败信息包含于意图创建响应中；所述意图创建请求中还包括检查指示，所述检查指示用于指示所述装置对所述第一意图表达式进行合法性检查；
    或者，所述第一意图表达式包含于意图合法性检查请求中，所述失败信息包含于意图合法性检查响应中。
  21. 一种通信装置，其特征在于，包括：
    处理模块，用于控制收发模块向第一设备发送第一意图表达式，所述第一意图表达式用于创建意图实例；
    所述处理模块，还用于控制所述收发模块接收所述第一设备的失败信息，所述失败信息用于指示创建所述意图实例的失败原因；
    其中，所述第一意图表达式中包括多个属性，所述失败原因包括所述第一意图表达式中存在相互冲突的属性，属性是目标或者约束条件。
  22. 如权利要求21所述的装置，其特征在于，所述失败原因包括所述第一意图表达式中存在相互冲突的第一属性与第二属性，所述第一属性包括第一属性名称和第一属性范围，所述第二属性包括第二属性名称和第二属性范围；
    所述冲突的类型包括如下中一个或多个：
    语法冲突，用于指示所述第一属性名称与所述第二属性名称相同，且所述第一属性范围与所述第二属性范围的交集为空；
    操作冲突，用于指示所述第一属性名称和所述第一属性范围所指示的操作，与所述第二属性名称和所述第二属性范围所指示的操作之间互斥；
    效果冲突，用于指示所述第一属性名称和所述第一属性范围所指示的操作，与所述第二属性名称和所述第二属性范围所指示的操作被同时执行时，二者能够达到的效果互斥；
    所述失败信息中包括所述第一属性、所述第二属性，以及所述第一属性与所述第二属性的冲突的类型。
  23. 如权利要求21或22所述的装置，其特征在于，所述失败原因还包括所述第一意图表达式中的第三属性不符合所述第一设备中的意图模板；
    所述意图模板中包括多个模板属性名称和所述多个模板属性名称分别对应的模板属性范围；所述第三属性包括第三属性名称和第三属性范围；
    所述第一意图表达式中的第三属性不符合所述第一设备中的意图模板，包括：
    所述第三属性名称未包含于所述意图模板的多个模板属性名称中；
    或者，所述第三属性范围超出所述意图模板中所述第三属性对应的模板属性范围；
    所述失败信息中还包括所述第三属性。
  24. 如权利要求21至23任一项所述的装置，其特征在于，所述处理模块还用于：
    控制所述收发模块接收来自所述第一设备的推荐意图表达式，以及向所述第一设备发送接受所述推荐意图表达式的指示，所述推荐意图表达式用于创建所述意图实例。
  25. 如权利要求21至23任一项所述的装置，其特征在于，所述处理模块还用于：
    根据所述失败原因，对所述第一意图表达式进行修改后得到的第二意图表达式，控制所述收发模块向所述第一设备发送所述第二意图表达式。
  26. 如权利要求21至25任一项所述的装置，其特征在于，所述第一意图表达式包含于意图创建请求中，所述失败信息包含于意图创建响应中；所述意图创建请求中还包括检查指示，所述检查指示用于指示所述第一设备对所述第一意图表达式进行合法性检查；
    或者，所述第一意图表达式包含于意图合法性检查请求中，所述失败信息包含于意图合法性检查响应中。
  27. 一种通信装置，其特征在于，包括处理器，所述处理器与存储器相连，所述存储器用于存储计算机程序，所述处理器用于执行所述存储器中存储的计算机程序，以使得所述装置执行如权利要求1至7任一项，或者8至13任一项所述的方法。
  28. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机程序或指令，当所述计算机程序或指令被通信装置执行时，实现如权利要求1至7任一项，或者8至13任一项所述的方法。
  29. 一种计算机程序产品，其特征在于，所述计算机程序产品包括计算机程序或指令，当所述计算机程序或指令被通信装置执行时，实现如权利要求1至7任一项，或者8至13任一项所述的方法。
PCT/CN2022/137016 2021-12-17 2022-12-06 一种意图合法性检查方法及装置 WO2023109594A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP22906344.1A EP4432065A1 (en) 2021-12-17 2022-12-06 Intent legitimacy checking method and apparatus
KR1020247023216A KR20240113612A (ko) 2021-12-17 2022-12-06 의도 타당성 체크 방법 및 장치

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111548435.6A CN116266267A (zh) 2021-12-17 2021-12-17 一种意图合法性检查方法及装置
CN202111548435.6 2021-12-17

Publications (1)

Publication Number Publication Date
WO2023109594A1 true WO2023109594A1 (zh) 2023-06-22

Family

ID=86743465

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/137016 WO2023109594A1 (zh) 2021-12-17 2022-12-06 一种意图合法性检查方法及装置

Country Status (4)

Country Link
EP (1) EP4432065A1 (zh)
KR (1) KR20240113612A (zh)
CN (1) CN116266267A (zh)
WO (1) WO2023109594A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109376847A (zh) * 2018-08-31 2019-02-22 深圳壹账通智能科技有限公司 用户意图识别方法、装置、终端及计算机可读存储介质
CN111565114A (zh) * 2019-02-14 2020-08-21 华为技术有限公司 一种意图处理方法、装置及系统
CN112822699A (zh) * 2019-11-15 2021-05-18 华为技术有限公司 执行意图的方法及装置
WO2021213632A1 (en) * 2020-04-21 2021-10-28 Nokia Solutions And Networks Oy Intent fulfillment for automated control of communication networks

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109376847A (zh) * 2018-08-31 2019-02-22 深圳壹账通智能科技有限公司 用户意图识别方法、装置、终端及计算机可读存储介质
CN111565114A (zh) * 2019-02-14 2020-08-21 华为技术有限公司 一种意图处理方法、装置及系统
CN112822699A (zh) * 2019-11-15 2021-05-18 华为技术有限公司 执行意图的方法及装置
WO2021213632A1 (en) * 2020-04-21 2021-10-28 Nokia Solutions And Networks Oy Intent fulfillment for automated control of communication networks

Also Published As

Publication number Publication date
CN116266267A (zh) 2023-06-20
KR20240113612A (ko) 2024-07-22
EP4432065A1 (en) 2024-09-18

Similar Documents

Publication Publication Date Title
CN108011935B (zh) 一种nb-iot设备的程序升级方法、服务器及nb-iot设备
US20190274117A1 (en) Downlink Data Packet Transmission Method and Device
US11979825B2 (en) Method and system for controlling gateway, and electronic device
CN112672440A (zh) 指令执行方法、系统、网络设备及存储介质
CN101626352A (zh) 带有恒定误比特率的高速链路的可调整发射器功率
WO2021063254A1 (zh) 一种信息处理方法、相关设备及计算机存储介质
US12015486B2 (en) Data retransmission decoding method, apparatus and system, and communication device
WO2022267874A1 (zh) 排障方法、系统、电子设备和计算机可读存储介质
WO2023109594A1 (zh) 一种意图合法性检查方法及装置
EP2439881A1 (en) Cluster system and request message distribution method for processing multi-node transaction
CN102955801A (zh) 基于分布式数据库系统的数据控制方法及系统
CN107391630B (zh) 处理并行网络请求的方法、装置及终端设备
CN111246427B (zh) 辅链路的传输控制方法、系统、设备、介质及辅链路终端
WO2021036621A1 (zh) 信息交互方法及相关设备
CN111554291B (zh) 设备控制方法、语音输入终端、语音平台及存储介质
CN111459514B (zh) 一种终端升级的处理方法、服务器及基站
CN110928828A (zh) 处理器间业务处理系统
CN113133066A (zh) 一种切换方法和网络设备
CN100548002C (zh) 永久虚电路状态查询系统
CN115996404B (zh) 节点链路动态调整方法及装置
CN116996450B (zh) 一种管理数据处理方法、装置及系统
CN108769260A (zh) 一种集群升级过程中事件处理方法及其装置
WO2020258264A1 (zh) 上行链路信道调度方法和装置、介质、基站和用户终端
CN102571927B (zh) 一种多终端集中控制方法与系统
CN114679755B (zh) 一种工作模式切换方法、装置、设备和存储介质

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: 22906344

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022906344

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022906344

Country of ref document: EP

Effective date: 20240611

ENP Entry into the national phase

Ref document number: 20247023216

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE