Intention negotiation method, apparatus and device, readable storage medium and program product

Abstract

The invention discloses an intention negotiation method, device and equipment, a readable storage medium and a program product, relates to the technical field of communication, and aims to ensure the reliability and robustness of an intention-driven network. The method comprises the steps that first equipment sends a first request to second equipment under the condition that implementation of a first intention is guaranteed, and the first request is used for requesting intention negotiation; and receiving a first response sent by the second device, the first response being used for indicating whether the second device accepts the first request. According to the embodiment of the invention, the reliability and robustness of the intention-driven network can be ensured.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to an intention negotiation method, apparatus, device, readable storage medium, and program product. Background Art

[0002] In intent-driven networking, information exchange between autonomous domains and different layers is "intent-driven." An intent is a formal specification of all desired expectations, including requirements, goals, and constraints for technical systems. It describes the desired network state without specifying how to achieve it. Intent-driven management service producers (MnS producers) allow intent-driven management service consumers (MnS consumers) to manage services and network resources through intent expressions.

[0003] In this approach, the IDM service consumer provides an intent description to the IDM service producer and receives information about the intent's fulfillment. The IDM service producer receives the intent from the IDM service consumer, verifies, translates, and executes the intent, and then provides feedback on the intent's fulfillment to the IDM service consumer. By introducing intents, system expectations are decoupled from specific implementation details, leaving room for exploring alternatives and finding optimal solutions.

[0004] In the intent-driven negotiation process, the intent-driven management service consumer can trigger the negotiation. However, this approach may not produce fair and reasonable negotiation results, thus affecting the reliability and robustness of the intent-driven network. Summary of the Invention

[0005] The embodiments of the present application provide an intent negotiation method, apparatus, device, readable storage medium, and program product to ensure the reliability and robustness of an intent-driven network.

[0006] In a first aspect, an embodiment of the present application provides an intent negotiation method, applied to a first device, the method comprising:

[0007] When ensuring the implementation of the first intention, sending a first request to the second device, wherein the first request is used to request intention negotiation;

[0008] A first response sent by the second device is received, wherein the first response is used to indicate whether the second device accepts the first request.

[0009] Optionally, the first request includes one or more of the following information:

[0010] Intended negotiation identifier, used to identify the intention to be negotiated;

[0011] the intended expected combination of proposed modifications;

[0012] The proposed modified intention expectation combination includes the intention expectations;

[0013] the desired object desired by the said intention;

[0014] the desired goal desired by the stated intention;

[0015] The desired context expected by the intent.

[0016] Optionally, the first request further includes one or more of the following information:

[0017] the intended context of the proposed modification;

[0018] The desired object context expected by the intent;

[0019] the desired target context desired by the intent;

[0020] the impact of a change of intention;

[0021] Reasons for intending to negotiate.

[0022] The intention to be negotiated is determined in the following manner:

[0023] Sorting the candidate intents according to their intent priorities to obtain a first sorting result;

[0024] Sorting the candidate intentions according to the difference between the resources reserved for ensuring the desired target of the intention of each candidate intention and the actual intention consumption resources of each candidate intention to obtain a second sorting result;

[0025] sorting the candidate intents according to the impact of the negotiation results of the intent negotiation with the candidate intents on the network to obtain a third sorting result;

[0026] Based on one or more of the first sorting result, the second sorting result and the third sorting result, the intent to be negotiated is determined from the candidate intents.

[0027] Optionally, the method further includes:

[0028] When the first response indicates that the second device accepts the first request, obtaining the updated first intent in the first response and ensuring implementation of the updated first intent;

[0029] When the first response indicates that the second device does not accept the first request, continue to ensure the implementation of the first intention.

[0030] Optionally, the first request is sent to the second device when one or more of the following conditions are met:

[0031] receiving a first instruction, wherein the first instruction is used to instruct sending the first request to the second device;

[0032] receiving a second intent, the second intent conflicting with the first intent;

[0033] Network resources have changed.

[0034] Optionally, the first request is sent when a second intent from the second device or the third device is received; and the method further includes:

[0035] If the first response indicates that the second device accepts the first request, sending first information to the second device or the third device, wherein the first information is used to indicate that the second intention is feasible;

[0036] In a case where the first response indicates that the second device does not accept the first request, second information is sent to the second device or the third device, wherein the second information is used to indicate that the second intention is not feasible.

[0037] Optionally, the method further includes:

[0038] receiving a second request sent by the second device, wherein the second request is used to request an intent negotiation;

[0039] A second response is sent to the second device, wherein the second response is used to indicate whether the first intention is feasible.

[0040] Optionally, the second request includes one or more of the following:

[0041] Intention-expectation combination;

[0042] The intention expectations contained in the intention expectation combination;

[0043] the desired object desired by the said intention;

[0044] the desired goal desired by the stated intention;

[0045] The desired context expected by the intent.

[0046] Optionally, the second request further includes one or more of the following:

[0047] Intent context;

[0048] The desired object context expected by the intent;

[0049] The desired target context expected by the intent.

[0050] In a second aspect, an embodiment of the present application provides an intent negotiation method, applied to a second device, the method comprising:

[0051] receiving a first request sent by a first device, wherein the first request is used to request intention negotiation and is sent by the first device while ensuring the implementation of the first intention;

[0052] A first response is sent to the first device, where the first response is used to indicate whether the second device accepts the first request.

[0053] Optionally, the method further includes:

[0054] Sending a second request to the first device, wherein the second request is used to request intent negotiation;

[0055] A second response sent by the first device is received, wherein the second response is used to indicate whether the first intention is feasible.

[0056] Optionally, the second request includes one or more of the following:

[0057] Intention-expectation combination;

[0058] The intention expectations contained in the intention expectation combination;

[0059] the desired object desired by the said intention;

[0060] the desired goal desired by the stated intention;

[0061] The desired context expected by the intent.

[0062] Optionally, the second request further includes one or more of the following:

[0063] Intent context;

[0064] The intended expectation

[0065] The desired target context expected by the intent.

[0066] Optionally, the receiving a first request sent by the first device includes:

[0067] Receiving the first request sent by the first device when one or more of the following conditions are met:

[0068] receiving a first instruction, wherein the first instruction is used to instruct sending the first request to the second device;

[0069] receiving a second intent, the second intent conflicting with the first intent;

[0070] Network resources have changed.

[0071] In a third aspect, an embodiment of the present application provides an intent negotiation apparatus, applied to a first device, the apparatus comprising:

[0072] A first sending module is configured to send a first request to the second device while ensuring the implementation of the first intention, wherein the first request is used to request intention negotiation;

[0073] The first receiving module is configured to receive a first response sent by the second device, wherein the first response is used to indicate whether the second device accepts the first request.

[0074] Optionally, the first request includes one or more of the following information:

[0075] Intended negotiation identifier, used to identify the intention to be negotiated;

[0076] the intended expected combination of proposed modifications;

[0077] The proposed modified intention expectation combination includes the intention expectations;

[0078] the desired object desired by the said intention;

[0079] the desired goal desired by the stated intention;

[0080] The desired context expected by the intent.

[0081] Optionally, the first request further includes one or more of the following information:

[0082] the intended context of the proposed modification;

[0083] The desired object context expected by the intent;

[0084] the desired target context desired by the intent;

[0085] the impact of a change of intention;

[0086] Reasons for intending to negotiate.

[0087] The intention to be negotiated is determined in the following manner:

[0088] Sorting the candidate intents according to their intent priorities to obtain a first sorting result;

[0089] Sorting the candidate intentions according to the difference between the resources reserved for ensuring the desired target of the intention of each candidate intention and the actual intention consumption resources of each candidate intention to obtain a second sorting result;

[0090] sorting the candidate intents according to the impact of the negotiation results of the intent negotiation with the candidate intents on the network to obtain a third sorting result;

[0091] Based on one or more of the first sorting result, the second sorting result and the third sorting result, the intent to be negotiated is determined from the candidate intents.

[0092] Optionally, the device further includes:

[0093] a first processing module, configured to, when the first response indicates that the second device accepts the first request, obtain the updated first intent in the first response and ensure implementation of the updated first intent;

[0094] The second processing module is configured to continue ensuring the implementation of the first intention when the first response indicates that the second device does not accept the first request.

[0095] Optionally, the first sending module is further configured to:

[0096] When one or more of the following conditions are met, the first request is sent to the second device:

[0097] receiving a first instruction, wherein the first instruction is used to instruct sending the first request to the second device;

[0098] receiving a second intent, the second intent conflicting with the first intent;

[0099] Network resources have changed.

[0100] Optionally, the first request is sent when a second intent from the second device or the third device is received; and the apparatus further includes:

[0101] a second sending module, configured to send first information to the second device or the third device when the first response indicates that the second device accepts the first request, wherein the first information is used to indicate that the second intention is feasible;

[0102] The third sending module is used to send second information to the second device or the third device when the first response indicates that the second device does not accept the first request, wherein the second information is used to indicate that the second intention is not feasible.

[0103] Optionally, the device further includes:

[0104] A second receiving module is configured to receive a second request sent by the second device, wherein the second request is used to request an intent negotiation;

[0105] A fourth sending module is used to send a second response to the second device, wherein the second response is used to indicate whether the first intention is feasible.

[0106] Optionally, the second request includes one or more of the following:

[0107] Intention-expectation combination;

[0108] The intention expectations contained in the intention expectation combination;

[0109] the desired object desired by the said intention;

[0110] the desired goal desired by the stated intention;

[0111] The desired context expected by the intent.

[0112] Optionally, the second request further includes one or more of the following:

[0113] Intent context;

[0114] The desired object context expected by the intent;

[0115] The desired target context expected by the intent.

[0116] In a fourth aspect, an embodiment of the present application provides an intent negotiation apparatus, applied to a second device, the apparatus comprising:

[0117] A first receiving module is configured to receive a first request sent by a first device, wherein the first request is used to request an intention negotiation and is sent by the first device while ensuring the implementation of the first intention;

[0118] The first sending module is configured to send a first response to the first device, wherein the first response is used to indicate whether the second device accepts the first request.

[0119] Optionally, the device further includes:

[0120] A second sending module is configured to send a second request to the first device, wherein the second request is used to request an intent negotiation;

[0121] The second receiving module is used to receive a second response sent by the first device, wherein the second response is used to indicate whether the first intention is feasible.

[0122] Optionally, the second request includes one or more of the following:

[0123] Intention-expectation combination;

[0124] The intention expectations contained in the intention expectation combination;

[0125] the desired object desired by the said intention;

[0126] the desired goal desired by the stated intention;

[0127] The desired context expected by the intent.

[0128] Optionally, the second request further includes one or more of the following:

[0129] Intent context;

[0130] The desired object context expected by the intent;

[0131] The desired target context expected by the intent.

[0132] Optionally, the first receiving module is further configured to:

[0133] Receiving the first request sent by the first device when one or more of the following conditions are met:

[0134] receiving a first instruction, wherein the first instruction is used to instruct sending the first request to the second device;

[0135] receiving a second intent, the second intent conflicting with the first intent;

[0136] Network resources have changed.

[0137] In a fifth aspect, an embodiment of the present application provides an intent negotiation apparatus, applied to a first device, the apparatus comprising: a processor and a transceiver;

[0138] The transceiver is used to send a first request to the second device while ensuring the implementation of the first intention, wherein the first request is used to request intention negotiation; and receive a first response sent by the second device, wherein the first response is used to indicate whether the second device accepts the first request.

[0139] Optionally, the first request includes one or more of the following information:

[0140] Intended negotiation identifier, used to identify the intention to be negotiated;

[0141] the intended expected combination of proposed modifications;

[0142] The proposed modified intention expectation combination includes the intention expectations;

[0143] the desired object desired by the said intention;

[0144] the desired goal desired by the stated intention;

[0145] The desired context expected by the intent.

[0146] Optionally, the first request further includes one or more of the following information:

[0147] the intended context of the proposed modification;

[0148] The desired object context expected by the intent;

[0149] the desired target context desired by the intent;

[0150] the impact of a change of intention;

[0151] Reasons for intending to negotiate.

[0152] The intention to be negotiated is determined in the following manner:

[0153] Sorting the candidate intents according to their intent priorities to obtain a first sorting result;

[0154] Sorting the candidate intentions according to the difference between the resources reserved for ensuring the desired target of the intention of each candidate intention and the actual intention consumption resources of each candidate intention to obtain a second sorting result;

[0155] sorting the candidate intents according to the impact of the negotiation results of the intent negotiation with the candidate intents on the network to obtain a third sorting result;

[0156] Based on one or more of the first sorting result, the second sorting result and the third sorting result, the intent to be negotiated is determined from the candidate intents.

[0157] Optionally, the processor is configured to:

[0158] When the first response indicates that the second device accepts the first request, obtaining the updated first intent in the first response and ensuring implementation of the updated first intent;

[0159] When the first response indicates that the second device does not accept the first request, continue to ensure the implementation of the first intention.

[0160] Optionally, the transceiver is further configured to:

[0161] When one or more of the following conditions are met, the first request is sent to the second device:

[0162] receiving a first instruction, wherein the first instruction is used to instruct sending the first request to the second device;

[0163] receiving a second intent, the second intent conflicting with the first intent;

[0164] Network resources have changed.

[0165] Optionally, the first request is sent when a second intention from the second device or the third device is received; and the transceiver is further configured to:

[0166] If the first response indicates that the second device accepts the first request, sending first information to the second device or the third device, wherein the first information is used to indicate that the second intention is feasible;

[0167] In a case where the first response indicates that the second device does not accept the first request, second information is sent to the second device or the third device, wherein the second information is used to indicate that the second intention is not feasible.

[0168] Optionally, the transceiver is further configured to:

[0169] receiving a second request sent by the second device, wherein the second request is used to request an intent negotiation;

[0170] A second response is sent to the second device, wherein the second response is used to indicate whether the first intention is feasible.

[0171] Optionally, the second request includes one or more of the following:

[0172] Intention-expectation combination;

[0173] The intention expectations contained in the intention expectation combination;

[0174] the desired object desired by the said intention;

[0175] the desired goal desired by the stated intention;

[0176] The desired context expected by the intent.

[0177] Optionally, the second request further includes one or more of the following:

[0178] Intent context;

[0179] The desired object context expected by the intent;

[0180] The desired target context expected by the intent.

[0181] In a sixth aspect, an embodiment of the present application provides an intention negotiation apparatus, applied to a second device, the apparatus comprising: a processor and a transceiver;

[0182] The transceiver is used to receive a first request sent by a first device, wherein the first request is used to request intention negotiation and is sent by the first device while ensuring the implementation of the first intention; and send a first response to the first device, wherein the first response is used to indicate whether the second device accepts the first request.

[0183] Optionally, the transceiver is further configured to:

[0184] Sending a second request to the first device, wherein the second request is used to request intent negotiation;

[0185] A second response sent by the first device is received, wherein the second response is used to indicate whether the first intention is feasible.

[0186] Optionally, the second request includes one or more of the following:

[0187] Intention-expectation combination;

[0188] The intention expectations contained in the intention expectation combination;

[0189] the desired object desired by the said intention;

[0190] the desired goal desired by the stated intention;

[0191] The desired context expected by the intent.

[0192] Optionally, the second request further includes one or more of the following:

[0193] Intent context;

[0194] The desired object context expected by the intent;

[0195] The desired target context expected by the intent.

[0196] Optionally, the transceiver is further configured to receive the first request sent by the first device when one or more of the following conditions are met:

[0197] receiving a first instruction, wherein the first instruction is used to instruct sending the first request to the second device;

[0198] receiving a second intent, the second intent conflicting with the first intent;

[0199] Network resources have changed.

[0200] In the seventh aspect, an embodiment of the present application also provides a communication device, including: a memory, a processor, and a program stored in the memory and executable on the processor, wherein the processor implements the steps in the intention negotiation method as described above when executing the program.

[0201] In an eighth aspect, an embodiment of the present application further provides a readable storage medium, on which a program is stored, and when the program is executed by a processor, the steps in the intention negotiation method as described above are implemented.

[0202] In a ninth aspect, an embodiment of the present application further provides a computer program product, comprising computer instructions, which, when executed by a processor, implement the steps in the intention negotiation method as described above.

[0203] In the embodiment of the present application, the first device can send a first request to the second device to conduct intent negotiation while ensuring the implementation of the first intent. Utilizing the solution of the embodiment of the present application, through the first device's proactive intent negotiation while ensuring the implementation of the first intent, a more fair and reasonable negotiation result can be obtained, thereby ensuring the reliability and robustness of the intent-driven network. BRIEF DESCRIPTION OF THE DRAWINGS

[0204] Figure 1 This is one of the flow charts of the intention negotiation method provided in the embodiment of the present application;

[0205] Figure 2 This is the second flowchart of the intention negotiation method provided in the embodiment of the present application;

[0206] Figure 3 This is the third flowchart of the intention negotiation method provided in the embodiment of the present application;

[0207] Figure 4 This is the fourth flowchart of the intention negotiation method provided in the embodiment of the present application;

[0208] Figure 5 This is one of the structural diagrams of the intention negotiation device provided in the embodiment of the present application;

[0209] Figure 6 This is the second structural diagram of the intention negotiation device provided in the embodiment of the present application;

[0210] Figure 7 This is the third structural diagram of the intention negotiation device provided in the embodiment of the present application;

[0211] Figure 8 This is the fourth structural diagram of the intention negotiation device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0212] In the embodiments of this application, the term "and / or" describes the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0213] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0214] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0215] See also Figure 1 , Figure 1 This is a flow chart of the intention negotiation method provided in the embodiment of the present application, which is applied to the first device. Figure 1 As shown, the following steps are included:

[0216] Step 101: While ensuring the implementation of the first intention, send a first request to the second device, wherein the first request is used to request intention negotiation.

[0217] The first intent can be any intent after the second device and the first device have negotiated intents. For example, the first device and the second device can negotiate intents during the intent creation, intent update, intent activation, or intent restart phases. Furthermore, the first intent can be one or more intents.

[0218] The first device has an intent management function. Here, in an embodiment, the first device has an intent management function, for example, it can be an intent-driven management service producer, or it can also be called an intent processor. The second device has an intent management function, for example, it can be an intent-driven management service consumer, or it can also be called an intent owner. The first device and the second device interact based on the intent management interface, and perform centralized management operations including but not limited to the following: intent creation, intent deletion, intent update, intent negotiation, intent activation / deactivation, intent management capability query, etc. The embodiments of the present application can be applied to one or more of the following scenarios: wireless network, wireless service, core network network, core network service, network slicing, or end-to-end communication service.

[0219] The first device sends the first request to the second device when one or more of the following conditions are met:

[0220] (1) A first instruction is received, wherein the first instruction is used to instruct the sending of the first request to the second device. The first instruction may come from a network management device, etc.

[0221] (2) A second intent is received that conflicts with the first intent. That is, when the first device receives a new intent, it may request intent negotiation with the second device regarding the intent being secured. Here, the conflict may, for example, refer to a conflict between the resources required for the second intent and the resources required for the first intent.

[0222] (3) Network resources change.

[0223] For example, the first device detects a change in network resources, such as that the current network resources cannot guarantee the execution of the first intention; the current network resources are relatively sufficient to guarantee the execution of multiple intentions at the same time, etc. For example, when the first device detects a device failure, it can also trigger the sending of the first request.

[0224] Of course, in the embodiment of the present application, the first request may be sent to the second device in other ways, for example, according to a certain period.

[0225] In this embodiment of the present application, the first request includes one or more of the following information:

[0226] Intent to negotiate identification;

[0227] the intended expected combination of proposed modifications;

[0228] The proposed modified intention expectation combination includes the intention expectations;

[0229] the desired object desired by the said intention;

[0230] the desired goal desired by the stated intention;

[0231] The desired context expected by the intent.

[0232] The intention negotiation identifier is used to identify the intention to be negotiated, so as to indicate which intention or intentions are to be negotiated. The intention to be negotiated may be one or more of the candidate intentions.

[0233] The intention to be negotiated is determined in the following manner:

[0234] (1) Sort the candidate intents according to their intent priorities to obtain a first sorting result. Each candidate intent has a corresponding intent priority. For example, the candidate intents may be sorted from high to low or from low to high in order of intent priority to obtain a first sorting result. When negotiating intents, the intents with the lowest priority may be negotiated first.

[0235] (2) Sort the candidate intentions according to the size of the gap between the resources reserved for guaranteeing the expected target of the intention of each candidate intention and the actual intention consumption resources of each candidate intention, and obtain a second sorting result. The first device can compare the resources reserved for guaranteeing the expected target of the intention of each candidate intention with the actual intention consumption resources during the implementation of each candidate intention, so as to obtain the size of the gap. For example, the candidate intentions can be sorted in order from high to low or from low to high according to the size of the gap, so as to obtain the second sorting result. When negotiating intentions, the intention with the largest gap can be negotiated first.

[0236] (3) The candidate intents are ranked according to the impact of the negotiation results with the candidate intents on the network, thereby obtaining a third ranking result. The first device may evaluate the impact based on its own resources, the implementation of the intent, and other information to determine the magnitude of the impact. When negotiating intents, the candidate intents with the least impact are negotiated first.

[0237] (4) Determine the intention to be negotiated from the candidate intentions based on one or more of the first sorting result, the second sorting result, and the third sorting result.

[0238] After obtaining the above ranking results, the intention to be negotiated may be determined based on one or more items of one or more ranking results.

[0239] For example, the intent to be negotiated can be determined from the candidate intents directly based on the first sorting result, the second sorting result, or the third sorting result. For example, based on the first sorting result, one or more candidate intents with lower priorities can be selected as intents to be negotiated; based on the second sorting result, one or more candidate intents with larger differences can be selected as intents to be negotiated; and based on the third sorting result, one or more candidate intents with smaller impact can be selected as intents to be negotiated.

[0240] For another example, if the intention to be negotiated is determined based on multiple ranking results, each candidate intention can be decomposed according to a preset conditional expression (such as a multi-objective optimization algorithm) to determine the intention to be negotiated.

[0241] The proposed modified intention expectation combination can be the best intention expectation combination within the capabilities of the first device, determined by the first device based on its own resource conditions, information on satisfaction of historical intentions, etc. (the feasibility of satisfying the second intention needs to be guaranteed). The best intention expectation combination can be understood as an intention expectation combination that can adapt to newly emerging information or changes while satisfying the execution of the first intention. The intention expectation combination may include one or more intention expectations. The expected object of the intention expectation may be, for example, a system, network, device, node, etc. The expected target of the intention expectation may be, for example, bandwidth, latency, etc. The expected context of the intention expectation may be information related to the intention expectation, etc.

[0242] Optionally, in this embodiment of the present application, the first request further includes one or more of the following information:

[0243] Suggested modified intent context: describes the constraints and conditions that apply to the entire intent, which is a triple combination of attribute, condition, and value range;

[0244] The desired object context of the intent: describes a list of constraints and conditions that apply to the specific desired object;

[0245] The desired goal context of the intent: a list of constraints and conditions that apply to the specific desired goal;

[0246] the impact of a change of intention;

[0247] Reasons for intending to negotiate.

[0248] The impact of an intent change refers to the effect of a change in an intent, such as a change in latency or bandwidth. For example, this impact can refer to the effect on the implementation of the intent after accepting the intent negotiation, which may not be explicitly expressed in the intent. The reason for the intent negotiation may include, for example, the need to coordinate some resources to satisfy other intents.

[0249] By carrying the above information in the first request, the first device and the second device can clearly understand the content of the negotiation, the impact of the negotiation, etc., thereby improving the accuracy of intent recognition and the efficiency of intent negotiation.

[0250] In practical applications, the first request can be sent in a variety of ways. For example, an intent negotiation report can be included in the intent report to carry the intent negotiation information of the intent-driven management service producer to the intent-driven management service consumer, i.e., the first request. Alternatively, a new message can be sent directly to the second device, and this new message serves as the first request.

[0251] In the first request, an exemplary combination of the intended negotiation identifier, the reason for the intended negotiation, the impact of the intended change, and the intended modification suggestion may be carried out.

[0252] Step 102: Receive a first response sent by the second device, where the first response is used to indicate whether the second device accepts the first request.

[0253] After receiving the first request, the second device may determine whether to accept the first request based on the first request and its own needs, and indicate this to the first device through a first response. If the first request is accepted, the second device may also send the updated first intent to the first device through the first response.

[0254] If the first response indicates that the second device accepts the first request, the first device obtains the updated first intent in the first response and ensures the implementation of the updated first intent. Furthermore, if the first request is sent after receiving a second intent from the second or third device, the first device may also send a first message to the third device, where the first message indicates that the second intent is feasible, thereby initiating the intent creation process.

[0255] If the first response indicates that the second device does not accept the first request, the implementation of the first intention is continued. At the same time, if the first request is sent after receiving the second intention from the second or third device, the first device may also send a second message to the second or third device, where the second message indicates that the second intention is not feasible. Optionally, the second message may also carry a rejection reason and a conflict target. The rejection reason may be, for example, that current resources cannot meet the implementation of the intention, and the conflict target may be, for example, a bandwidth conflict.

[0256] In the embodiment of the present application, the first device can send a first request to the second device to negotiate intent while ensuring the implementation of the first intent. Therefore, through the first device's proactive intent negotiation while ensuring the implementation of the first intent, timely adjustments can be made in response to new information or changes, resulting in a more fair and reasonable negotiation result, thereby ensuring the reliability and robustness of the intent-driven network.

[0257] The intent negotiation process described above is performed under the condition of intent execution. In an embodiment of the present application, intent negotiation can also be performed during the intent creation, intent update, intent activation or intent restart phase, so as to avoid potential conflicts caused by the creation or change of intent through feasibility check, intent exploration and intent negotiation. The negotiation at this stage is initiated by the intent-driven management service consumer. Accordingly, for the first device, a second request sent by the second device can be received, wherein the second request is used to request intent negotiation. Afterwards, the first device performs a feasibility check and sends a second response to the second device, wherein the second response is used to indicate whether the first intention is feasible. The feasibility check includes checking the degree of satisfaction of the intention implementation and whether there is a potential conflict between one or more intentions (or intent instances). If the feasibility check result is feasible, the intent-driven management service producer performs the service or network management task to satisfy the intention, otherwise the intention will be rejected.

[0258] For the first device and the second device, interaction is based on intent (corresponding to the second request). The intent is composed of a specific intent information model, which includes information such as intent expectations and constraints. Among them, the intent expectation includes information such as the expected object, expected target, target value, and context.

[0259] Specifically, the second request may include one or more of the following:

[0260] Intention-expectation combination;

[0261] The intention expectations contained in the intention expectation combination;

[0262] the desired object desired by the said intention;

[0263] the desired goal desired by the stated intention;

[0264] The desired context expected by the intent.

[0265] The intent expectation combination may include one or more intent expectations, which may be determined by the second device based on its own needs. The desired object of the intent expectation may be, for example, a system, network, device, node, etc. The desired target of the intent expectation may be, for example, bandwidth, latency, etc. The desired context of the intent expectation may be information related to the intent expectation, etc.

[0266] Optionally, the second request further includes one or more of the following:

[0267] Intent context, which describes the constraints and conditions applied to the entire intent and is a triple combination of attributes, conditions, and value ranges;

[0268] The desired object context of the intent: describes a list of constraints and conditions that apply to the specific desired object;

[0269] The intent expects a desired target context, which describes a list of constraints and conditions that apply to a specific desired target.

[0270] Therefore, by combining the intent negotiation at different stages, the initiative of the intent-driven management service producer in multi-intent satisfaction scenarios can be guaranteed without affecting the global state of the network. It supports the active negotiation between the intent-driven management service producer and the intent-driven management service consumer, and allows timely adjustments based on new information or changes during the intent assurance process, so that the intent realization can better meet the real expectations of the intent-driven management service consumers, thereby improving the satisfaction of the intent-driven management service consumers and improving the reliability and flexibility of the intent-driven network system.

[0271] See also Figure 2 , Figure 2 This is a flow chart of the intention negotiation method provided in the embodiment of the present application, which is applied to the second device. Figure 2 As shown, the following steps are included:

[0272] Step 201: Receive a first request sent by a first device, wherein the first request is used to request intent negotiation and is sent by the first device while ensuring the implementation of the first intent. The first device and the second device have intent management functions. For example, in this embodiment, the first device may be an intent-driven management service producer, and the second device may be an intent-driven management service consumer.

[0273] Specifically, the second device may receive the first request sent by the first device when one or more of the following conditions are met:

[0274] receiving a first instruction, wherein the first instruction is used to instruct sending the first request to the second device;

[0275] receiving a second intent, the second intent conflicting with the first intent;

[0276] Network resources have changed.

[0277] For explanation of the above conditions, please refer to the description of the above embodiments.

[0278] For an explanation of the first request, please refer to the description of the aforementioned method embodiment.

[0279] Step 202: Send a first response to the first device, where the first response is used to indicate whether the second device accepts the first request.

[0280] After receiving the first request, the second device may determine whether to accept the first request based on the first request and its own needs, and indicate this to the first device through a first response. If the first request is accepted, the second device may also send the updated first intent to the first device through the first response.

[0281] In the embodiment of the present application, the first device can send a first request to the second device to negotiate intent while ensuring the implementation of the first intent. Therefore, through the first device's proactive intent negotiation while ensuring the implementation of the first intent, it can make timely adjustments to new information or changes, obtaining a more fair and reasonable negotiation result, thereby ensuring the reliability and robustness of the intent-driven network.

[0282] The intent negotiation process described above is executed while ensuring the implementation of intent. In an embodiment of the present application, intent negotiation can also be performed during the intent creation, intent update, intent activation, or intent restart phase, thereby avoiding potential conflicts caused by the creation or modification of intent through feasibility checks, intent exploration, and intent negotiation. Negotiation at this stage is initiated by the intent-driven management service consumer.

[0283] Specifically, the second device may send a second request to the first device and receive a second response sent by the second device, wherein the second request is used to request intent negotiation, and the second response is used to indicate whether the first intent is feasible.

[0284] For explanation of the second request, reference may be made to the description of the aforementioned method embodiment.

[0285] Therefore, by combining the intent negotiation at different stages, the initiative of the intent-driven management service producer in multi-intent satisfaction scenarios can be guaranteed without affecting the global state of the network. It supports the active negotiation between the intent-driven management service producer and the intent-driven management service consumer, and allows timely adjustments based on new information or changes during the intent assurance process, so that the intent realization can better meet the real expectations of the intent-driven management service consumers, thereby improving the satisfaction of the intent-driven management service consumers and improving the reliability and flexibility of the intent-driven network system.

[0286] See also Figure 3 , Figure 3This is a flow chart of the intent negotiation method of an embodiment of the present application. In this flow chart, two stages of intent negotiation are shown. Among them, the first stage of intent negotiation occurs at the stage of intent creation, intent update, intent activation or intent restart. Through feasibility check, intent exploration, and intent negotiation, potential conflicts caused by the creation or change of intent are avoided; the second stage of intent negotiation occurs at the stage of intent execution or implementation. In this stage, the intent drives the management service producer to actively trigger the ability of intent changes, improve system flexibility, and ensure resource utilization.

[0287] The above intent negotiation process occurs between two devices with intent management capabilities, which act as intent-driven management service consumers and intent-driven management service producers respectively.

[0288] The intent-driven management service producer allows the intent-driven management service consumer to manage services and network resources through intent expression. The intent-driven management service consumer provides an intent description to the intent-driven management service producer and receives intent fulfillment information. The intent-driven management service producer receives the intent from the intent-driven management service consumer, verifies, translates, and executes the intent, and then feeds back the intent fulfillment information to the intent-driven management service consumer.

[0289] The intent processing process can be broadly divided into five phases: detection, investigation, definition, distribution, and implementation. In the detection phase, the intent-driven management service consumer determines whether to define a new intent or modify an existing one by testing whether requirements are met. In the investigation phase, the intent-driven management service consumer finds the appropriate intent-driven management service producer and, through investigation and negotiation, determines the feasibility of the intent. In the definition phase, the intent-driven management service consumer formulates the intent and associated expectations by combining the investigation information with the requirements determined in the detection phase. In the distribution phase, the intent-driven management service consumer creates a new intent object or modifies or changes an existing intent object to incorporate the intent expectations obtained in the definition phase. If the intent-driven management service producer accepts the intent, the intent object enters the implementation phase; otherwise, it sends a report to the intent-driven management service consumer with the reason for rejection, and the intent object lifecycle ends (at which point the intent-driven management service consumer can restart the process by detecting a new intent). In the implementation phase, the intent-driven management service producer operates its responsibility domain based on the accepted intent object to ensure that the corresponding expectations of the intent object are met. Furthermore, the intent-driven management service producer reports to the intent-driven management service consumer on the intent's fulfillment status, execution status, and reasons for non-fulfillment.

[0290] exist Figure 3In this process, the first device is the IDM producer, and the second device is the IDM consumer. Typically, the IDM consumer sends an intent to the IDM producer, and the IDM producer reports back to the IDM consumer. The two interact based on an agreed-upon information model to ensure mutual understanding.

[0291] The elements in the intent template include:

[0292] Intent expectation combination, the intent expectation contained in the intent expectation combination, the expected object of the intent expectation, the expected target of the intent expectation, and the expected context of the intent expectation. In some embodiments, the intent context, the expected object context of the intent expectation, the expected target context of the intent expectation, and other information may also be included. Intent reports include: intent satisfaction reports, intent feasibility check reports, intent exploration reports, and other forms, which appear in different stages of the intent life cycle.

[0293] like Figure 3 As shown, the intention negotiation process may specifically include:

[0294] 1. The first stage of intention negotiation:

[0295] Step 301: The second device sends an intent request (ie, a second request) to the first device for performing an intent feasibility check, exploration, and negotiation.

[0296] Step 302: The first device performs evaluation and verification according to the intent request.

[0297] Step 303: The first device sends a notification feedback (ie, a second response) to the second device, including the intention check result, recommendation information, and negotiation result.

[0298] Afterwards, if the notification feedback from the first device indicates that the intention is feasible, the second device can send an intention realization request to the first device, the first device executes the intention and evaluation, and reports the intention satisfaction information to the second device.

[0299] For example, in step 304, the second device sends an intent realization request to the first device.

[0300] Step 305: The first device executes the intention and evaluation.

[0301] Step 306: The first device reports the intent satisfaction information to the second device.

[0302] 2. Second stage of intention negotiation:

[0303] Step 307: The first device sends a negotiation intention request (ie, a first request) to the second device, including negotiation reasons, suggested expectations, and the impact of the intended modification.

[0304] Step 308: If the request is accepted, the second device sends an update intention request (ie, a first response) to the first device, carrying the update intention. If the request is not accepted, a response may be sent to indicate that the request is not accepted (not shown).

[0305] See also Figure 4 , Figure 4 This is a flow chart of the intention negotiation method according to an embodiment of the present application. This flow chart may include the following processes:

[0306] Step 401: The intent-driven management service consumer defines a new intent or modifies an existing intent and distributes the first intent.

[0307] In this step, the intent-driven management service consumer distributes the first intent, which can also be understood as requesting the intent-driven management service producer to perform intent negotiation.

[0308] Step 402: When the intent-driven management service producer receives the first intent, it determines whether the intent is feasible. There are several possibilities:

[0309] (1) The intent-driven management service producer is not the target intent producer and does not understand the intent semantics. The intent-driven management service producer directly rejects the intent and provides feedback on the reason why it is not feasible (as shown in 4021 in the figure).

[0310] (2) The intent-driven management service producer determines that there is a contradiction between the first intention itself or between the first intention and the historical intention, such as a conflict between intentions, expectations, or goals, and the intention cannot be realized. The intent-driven management service producer directly rejects the intention and provides feedback on the reason for its infeasibility (as shown in 4021 in the figure).

[0311] (3) If the intent-driven management service producer determines that all or part of the expectations and goals of the first intent are feasible, it initiates negotiation for the first intent and jumps to step 403.

[0312] Step 403: The intent-driven management service producer integrates resource conditions and historical satisfaction information, and feeds back to the intent-driven management service consumer the best intent suggestion combination and potential impact within the capability of the intent-driven management service producer.

[0313] Step 404: The intent-driven management service consumer receives the negotiation intent, confirms the intent expectation and corresponding target value (here the best intent combination that the intent-driven management service producer can provide is the upper limit of the system capability. The default intent-driven management service consumer can adjust to a low capability option without repeated negotiation), and sends it to the intent-driven management service producer.

[0314] Step 405: The intent-driven management service producer generates or modifies an intent instance based on the received information.

[0315] Step 406: The intent-driven management service producer operates its responsibility domain to ensure that the expectations corresponding to the intent object are met, and regularly reports intent satisfaction information.

[0316] Step 407: During the intent implementation, the intent-driven management service producer monitors changes in network status or receives new intent requests.

[0317] Step 408: If a network status change is detected or a new intent request is received, the intent-driven management service producer proactively triggers a negotiation with the intent-driven management service consumer. Otherwise, the process continues with step 406.

[0318] With reference to the description of the aforementioned embodiment, the intent-driven management service producer models the intent negotiation information and sends it to the intent-driven management service consumer.

[0319] In the embodiment of the present application, the intent negotiation initiated by the intent-driven management service producer can be implemented through the intent negotiation information template. Among them, the elements in the intent negotiation information template include:

[0320] Intent negotiation identifier; the proposed modified intent expectation combination, the intent expectation contained in the intent expectation combination, the expected object of the intent expectation, the expected target of the intent expectation, and the expected context of the intent expectation. In some embodiments, the proposed modified intent context, the expected object context of the intent expectation, the expected target context of the intent expectation, the impact of the intent change, and the reason for the intent negotiation may also be included.

[0321] Step 409: The intent-driven management service consumer receives the negotiation information and may reject the change and return to step 406 (not shown in the figure); or, make adjustment suggestions, obtain the modified intent, and instruct the intent-driven management service producer to change the intent instance and return to step 406.

[0322] Taking wireless network scenarios as an example, the bandwidth requirements of business traffic vary depending on the user's business type, time period, etc. Through intent negotiation, adaptive and highly reliable service operation guarantees can be achieved.

[0323] Assume that the current intent-driven management service producer is ensuring the realization of intent A of intent-driven management service consumer 1. During this period, the intent-driven management service producer receives intent B (which may come from intent-driven management service consumer 1 or other intent-driven management service consumers). Intent A and intent B need to ensure their respective live video broadcast and gaming experiences during the same period. Under the condition of insufficient available bandwidth resources, the two intentions are in a competitive relationship. In traditional intent solutions, intent A will be met first; when intent B applies for bandwidth resources, it will receive an intent report that system resources are not met during the intent detection phase, and then refuse to establish an intent object, making it impossible to achieve intent satisfaction, and thus unable to achieve a dynamic guarantee and state balance of an intent-driven self-intelligent network. In an embodiment of the present application, the intent-driven management service producer receives a new intent request, determines whether the new intent can be realized, and the impact on the current management domain. Assuming that it is judged at this time that there is a potential conflict with the running intent instance, the intent-driven management service producer detects that the expected target value of the intent expectation part set by the intent-driven management service consumer is higher than the actual demand, and can negotiate with the intent-driven management service consumer 1 to adjust intent A.

[0324] The intent-driven management service producer sends an intent negotiation report (i.e., the first request) to the intent-driven management service consumer. The intent negotiation report can be modeled through the intent negotiation information template information, including the intent negotiation identifier; the proposed modified intent expectation combination, the intent expectation contained in the intent expectation combination, the intended object of the intent expectation, the intended target of the intent expectation, and the intended context of the intent expectation. In some embodiments, it can also include the proposed modified intent context, the intended object context of the intended expectation, the intended target context of the intended expectation, the impact after the intent change, and the negotiation reason. For example, the negotiation information includes:

[0325] Intended negotiation identifier: negotiation type;

[0326] Reason for negotiation: to meet other intentions and to coordinate some resources;

[0327] Suggested modification of the expected bandwidth: Lower the expected bandwidth to 300M; Impact: Indicators such as latency remain unchanged.

[0328] After receiving the negotiation information, the intent-driven management service consumer determines whether to adjust intent A according to the suggestion.

[0329] If the IDM consumer accepts the negotiation, it updates Intent A and sends it to the IDM producer. The IDM producer updates the instance of Intent A and continues to guarantee Intent A. At the same time, the IDM producer determines that Intent B is feasible and sends a feasibility check message to the IDM consumer to which Intent B belongs, initiating the intent creation process.

[0330] If the intent-driven management service consumer does not accept the negotiation and replies to the intent-driven management service producer with a rejection message, the intent-driven management service producer will maintain the implementation guarantee of the original intent A. At the same time, the intent-driven management service producer will determine that it is not feasible and will feedback feasibility check information to the intent-driven management service consumer to which intent B belongs, indicating the rejection reason and conflicting goals, etc.

[0331] It can be seen from the above embodiments that, by combining intent negotiation at different stages, the initiative of intent-driven management service producers in multi-intent satisfaction scenarios can be guaranteed without affecting the global state of the network, and active negotiation between intent-driven management service producers and intent-driven management service consumers can be supported. Timely adjustments can be made according to new information or changes during the intent assurance process, so that the intent realization can better meet the real expectations of intent-driven management service consumers, thereby improving the satisfaction of intent-driven management service consumers and improving the reliability and flexibility of the intent-driven network system.

[0332] See also Figure 5 , Figure 5 This is a structural diagram of the intent negotiation device provided in an embodiment of the present application, which is applied to a first device having an intent management function. Figure 5 As shown, the intention negotiation device includes:

[0333] The first sending module 501 is used to send a first request to the second device while ensuring the implementation of the first intention, wherein the first request is used to request intent negotiation, and the second device has an intent management function; the first receiving module 502 is used to receive a first response sent by the second device, wherein the first response is used to indicate whether the second device accepts the first request.

[0334] Optionally, the first request includes one or more of the following information:

[0335] Intended negotiation identifier, used to identify the intention to be negotiated;

[0336] the intended expected combination of proposed modifications;

[0337] The proposed modified intention expectation combination includes the intention expectations;

[0338] the desired object desired by the said intention;

[0339] the desired goal desired by the stated intention;

[0340] The desired context expected by the intent.

[0341] Optionally, the first request further includes one or more of the following information:

[0342] the intended context of the proposed modification;

[0343] The desired object context expected by the intent;

[0344] the desired target context desired by the intent;

[0345] the impact of a change of intention;

[0346] Reasons for intending to negotiate.

[0347] The intention to be negotiated is determined in the following manner:

[0348] Sorting the candidate intents according to their intent priorities to obtain a first sorting result;

[0349] Sorting the candidate intentions according to the difference between the resources reserved for ensuring the desired target of the intention of each candidate intention and the actual intention consumption resources of each candidate intention to obtain a second sorting result;

[0350] sorting the candidate intents according to the impact of the negotiation results of the intent negotiation with the candidate intents on the network to obtain a third sorting result;

[0351] Based on one or more of the first sorting result, the second sorting result and the third sorting result, the intent to be negotiated is determined from the candidate intents.

[0352] Optionally, the device further includes:

[0353] a first processing module, configured to, when the first response indicates that the second device accepts the first request, obtain the updated first intent in the first response and ensure implementation of the updated first intent;

[0354] The second processing module is configured to continue ensuring the implementation of the first intention when the first response indicates that the second device does not accept the first request.

[0355] Optionally, the first request is sent when a second intent from the second device or the third device is received; and the apparatus further includes:

[0356] a second sending module, configured to send first information to the second device or the third device when the first response indicates that the second device accepts the first request, wherein the first information is used to indicate that the second intention is feasible;

[0357] The third sending module is used to send second information to the second device or the third device when the first response indicates that the second device does not accept the first request, wherein the second information is used to indicate that the second intention is not feasible.

[0358] Optionally, the device further includes:

[0359] A second receiving module is configured to receive a second request sent by the second device, wherein the second request is used to request an intent negotiation;

[0360] A fourth sending module is used to send a second response to the second device, wherein the second response is used to indicate whether the first intention is feasible.

[0361] Optionally, the second request includes one or more of the following:

[0362] Intention-expectation combination;

[0363] The intention expectations contained in the intention expectation combination;

[0364] the desired object desired by the said intention;

[0365] the desired goal desired by the stated intention;

[0366] The desired context expected by the intent.

[0367] Optionally, the second request further includes one or more of the following:

[0368] Intent context;

[0369] The desired object context expected by the intent;

[0370] The desired target context expected by the intent.

[0371] Optionally, the first sending module 501 is further configured to:

[0372] When one or more of the following conditions are met, the first request is sent to the second device:

[0373] receiving a first instruction, wherein the first instruction is used to instruct sending the first request to the second device;

[0374] receiving a second intent, the second intent conflicting with the first intent;

[0375] Network resources have changed.

[0376] The device provided in the embodiment of the present application can execute the above method embodiment, and its implementation principle and technical effects are similar, so this embodiment will not be repeated here.

[0377] See also Figure 6 , Figure 6 This is a structural diagram of the intention negotiation device provided in an embodiment of the present application, which is applied to a second device having an intention management function. Figure 6 As shown, the intention negotiation device includes:

[0378] The first receiving module 601 is used to receive a first request sent by a first device, wherein the first request is used to request intent negotiation and is sent by the first device while ensuring the implementation of the first intent, and the first device has an intent management function; the first sending module 602 is used to send a first response to the first device, wherein the first response is used to indicate whether the second device accepts the first request.

[0379] Optionally, the device further includes:

[0380] A second sending module is configured to send a second request to the first device, wherein the second request is used to request an intent negotiation;

[0381] The second receiving module is used to receive a second response sent by the first device, wherein the second response is used to indicate whether the first intention is feasible.

[0382] Optionally, the second request includes one or more of the following:

[0383] Intention-expectation combination;

[0384] The intention expectations contained in the intention expectation combination;

[0385] the desired object desired by the said intention;

[0386] the desired goal desired by the stated intention;

[0387] The desired context expected by the intent.

[0388] Optionally, the second request further includes one or more of the following:

[0389] Intent context;

[0390] The desired object context expected by the intent

[0391] The desired target context expected by the intent.

[0392] Optionally, the first receiving module 601 is further configured to:

[0393] Receiving the first request sent by the first device when one or more of the following conditions are met:

[0394] receiving a first instruction, wherein the first instruction is used to instruct sending the first request to the second device;

[0395] receiving a second intent, the second intent conflicting with the first intent;

[0396] Network resources have changed.

[0397] The device provided in the embodiment of the present application can execute the above method embodiment, and its implementation principle and technical effects are similar, so this embodiment will not be repeated here.

[0398] See also Figure 7 , Figure 7 This is a structural diagram of the intent negotiation device provided in an embodiment of the present application, which is applied to a first device having an intent management function. Figure 7 As shown, the intention negotiation device includes: a processor 701 and a transceiver 702;

[0399] In which, the transceiver 702 is used to send a first request to the second device while ensuring the implementation of the first intention, wherein the first request is used to request intent negotiation, and the second device has an intent management function; and receive a first response sent by the second device, wherein the first response is used to indicate whether the second device accepts the first request.

[0400] Optionally, the first request includes one or more of the following information:

[0401] Intended negotiation identifier, used to identify the intention to be negotiated;

[0402] the intended expected combination of proposed modifications;

[0403] The proposed modified intention expectation combination includes the intention expectations;

[0404] the desired object desired by the said intention;

[0405] the desired goal desired by the stated intention;

[0406] The desired context expected by the intent.

[0407] Optionally, the first request further includes one or more of the following information:

[0408] the intended context of the proposed modification;

[0409] The desired object context expected by the intent;

[0410] the desired target context desired by the intent;

[0411] the impact of a change of intention;

[0412] Reasons for intending to negotiate.

[0413] The intention to be negotiated is determined in the following manner:

[0414] Sorting the candidate intents according to their intent priorities to obtain a first sorting result;

[0415] Sorting the candidate intentions according to the difference between the resources reserved for ensuring the desired target of the intention of each candidate intention and the actual intention consumption resources of each candidate intention to obtain a second sorting result;

[0416] sorting the candidate intents according to the impact of the negotiation results of the intent negotiation with the candidate intents on the network to obtain a third sorting result;

[0417] Based on one or more of the first sorting result, the second sorting result and the third sorting result, the intent to be negotiated is determined from the candidate intents.

[0418] Optionally, the processor 701 is configured to:

[0419] When the first response indicates that the second device accepts the first request, obtaining the updated first intent in the first response and ensuring implementation of the updated first intent;

[0420] When the first response indicates that the second device does not accept the first request, continue to ensure the implementation of the first intention.

[0421] Optionally, the first request is sent when a second intention from the second device or the third device is received; the transceiver 702 is further configured to:

[0422] If the first response indicates that the second device accepts the first request, sending first information to the second device or the third device, wherein the first information is used to indicate that the second intention is feasible;

[0423] In a case where the first response indicates that the second device does not accept the first request, second information is sent to the second device or the third device, wherein the second information is used to indicate that the second intention is not feasible.

[0424] Optionally, the transceiver 702 is further configured to:

[0425] receiving a second request sent by the second device, wherein the second request is used to request an intent negotiation;

[0426] A second response is sent to the second device, wherein the second response is used to indicate whether the first intention is feasible.

[0427] Optionally, the second request includes one or more of the following:

[0428] Intention-expectation combination;

[0429] The intention expectations contained in the intention expectation combination;

[0430] the desired object desired by the said intention;

[0431] the desired goal desired by the stated intention;

[0432] The desired context expected by the intent.

[0433] Optionally, the second request further includes one or more of the following:

[0434] Intent context;

[0435] The desired object context expected by the intent;

[0436] The desired target context expected by the intent.

[0437] Optionally, the transceiver 702 is further configured to:

[0438] When one or more of the following conditions are met, the first request is sent to the second device:

[0439] receiving a first instruction, wherein the first instruction is used to instruct sending the first request to the second device;

[0440] receiving a second intent, the second intent conflicting with the first intent;

[0441] Network resources have changed.

[0442] The device provided in the embodiment of the present application can execute the above method embodiment, and its implementation principle and technical effects are similar, so this embodiment will not be repeated here.

[0443] See also Figure 8 , Figure 8 This is a structural diagram of the intention negotiation device provided in an embodiment of the present application, which is applied to a second device having an intention management function. Figure 8 As shown, the intention negotiation device includes: a processor 801 and a transceiver 802;

[0444] In which, the transceiver 802 is used to receive a first request sent by a first device, wherein the first request is used to request intent negotiation and is sent by the first device while ensuring the implementation of the first intention, and the first device has an intent management function; and send a first response to the first device, wherein the first response is used to indicate whether the second device accepts the first request.

[0445] Optionally, the transceiver 802 is further configured to:

[0446] Sending a second request to the first device, wherein the second request is used to request intent negotiation;

[0447] A second response sent by the first device is received, wherein the second response is used to indicate whether the first intention is feasible.

[0448] Optionally, the second request includes one or more of the following:

[0449] Intention-expectation combination;

[0450] The intention expectations contained in the intention expectation combination;

[0451] the desired object desired by the said intention;

[0452] the desired goal desired by the stated intention;

[0453] The desired context expected by the intent.

[0454] Optionally, the second request further includes one or more of the following:

[0455] Intent context;

[0456] The desired object context expected by the intent;

[0457] The desired target context expected by the intent.

[0458] Optionally, the transceiver 802 is further configured to receive the first request sent by the first device when one or more of the following conditions are met:

[0459] receiving a first instruction, wherein the first instruction is used to instruct sending the first request to the second device;

[0460] receiving a second intent, the second intent conflicting with the first intent;

[0461] Network resources have changed.

[0462] The device provided in the embodiment of the present application can execute the above method embodiment, and its implementation principle and technical effects are similar, so this embodiment will not be repeated here.

[0463] It should be noted that the division of units in the embodiments of the present application is schematic and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0464] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0465] An embodiment of the present application provides a communication device, comprising: a memory, a processor, and a program stored in the memory and executable on the processor; the processor is configured to read the program in the memory to implement the steps in the aforementioned intention negotiation method.

[0466] The embodiment of the present application also provides a readable storage medium, on which a program is stored. When the program is executed by the processor, the various processes of the above-mentioned intention negotiation method embodiment are implemented, and the same technical effect is achieved. To avoid repetition, it is not repeated here. The readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disk, hard disk, tape, magneto-optical disk (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)), etc.

[0467] An embodiment of the present application also provides a computer program product, including computer instructions. When the computer instructions are executed by a processor, the various processes of the above-mentioned intention negotiation method embodiment are implemented and can achieve the same technical effect. To avoid repetition, they will not be repeated here.

[0468] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0469] Through the description of the above embodiments, those skilled in the art can clearly understand that the above embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better embodiment. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, disk, CD), and includes a number of instructions for enabling a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0470] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms without departing from the purpose of this application and the scope of protection of the claims, all of which are within the protection of this application.

Claims

1. An intention negotiation method, characterized in that: Applied to a first device, the method includes: In a case where the first intention is implemented, sending a first request to the second device, wherein the first request is used to request intention negotiation; A first response sent by the second device is received, wherein the first response is used to indicate whether the second device accepts the first request.

2. The method according to claim 1, characterized in that The first request includes one or more of the following information: Intended negotiation identifier, used to identify the intention to be negotiated; The intended expected combination of proposed modifications; The proposed modified intention expectation combination includes the intention expectations; the desired object desired by the said intention; the desired goal desired by the stated intention; The desired context expected by the intent.

3. The method according to claim 2, characterized in that The first request also includes one or more of the following information: the intended context of the proposed modification; The desired object context expected by the intent; the desired target context desired by the intent; the impact of a change of intention; The reason for the intention to negotiate.

4. The method according to claim 2, characterized in that: The intention to be negotiated is determined as follows: Sorting the candidate intents according to their intent priorities to obtain a first sorting result; According to the difference between the resources reserved for the expected target of each candidate intention and the actual intention consumption resources of each candidate intention, the candidate intentions are sorted to obtain a second sorting result; sorting the candidate intents according to the influence of the negotiation results of the intent negotiation with the candidate intents on the network to obtain a third sorting result; Based on one or more of the first sorting result, the second sorting result and the third sorting result, the intent to be negotiated is determined from the candidate intents.

5. The method according to claim 1, characterized in that The method further comprises: When the first response indicates that the second device accepts the first request, obtaining the updated first intent in the first response, and ensuring the implementation of the updated first intent; When the first response indicates that the second device does not accept the first request, continue to ensure the implementation of the first intention.

6. The method according to claim 1, characterized in that When one or more of the following conditions are met, a first request is sent to the second device: receiving a first instruction, wherein the first instruction is used to instruct sending the first request to the second device; receiving a second intent, the second intent conflicting with the first intent; Network resources have changed.

7. The method according to claim 6, characterized in that The first request is sent when a second intention of the second device or the third device is received; and the method further includes: When the first response indicates that the second device accepts the first request, sending first information to the second device or the third device, wherein the first information is used to indicate that the second intention is feasible; In a case where the first response indicates that the second device does not accept the first request, second information is sent to the second device or the third device, wherein the second information is used to indicate that the second intention is not feasible.

8. The method according to claim 1, characterized in that The method further comprises: receiving a second request sent by the second device, wherein the second request is used to request an intent negotiation; A second response is sent to the second device, wherein the second response is used to indicate whether the first intention is feasible.

9. The method according to claim 8, characterized in that The second request includes one or more of the following: Intention-expectation combination; The intention expectations included in the intention expectation combination; the desired object desired by the said intention; the desired goal desired by the stated intention; The desired context expected by the intent.

10. The method according to claim 9, characterized in that The second request also includes one or more of the following: Intent context; The desired object context expected by the intent; The desired target context desired by the intent.

11. An intention negotiation method, characterized in that: Applied to the second device, the method includes: receiving a first request sent by a first device, wherein the first request is used to request an intent negotiation and is sent by the first device while ensuring the implementation of the first intent; A first response is sent to the first device, wherein the first response is used to indicate whether the second device accepts the first request.

12. The method according to claim 11, characterized in that The method further comprises: Sending a second request to the first device, wherein the second request is used to request an intent negotiation; A second response sent by the first device is received, wherein the second response is used to indicate whether the first intention is feasible.

13. The method according to claim 12, characterized in that The second request includes one or more of the following: Intention-expectation combination; The intention expectations included in the intention expectation combination; the desired object desired by the said intention; the desired goal desired by the stated intention; The desired context expected by the intent.

14. The method according to claim 13, characterized in that The second request also includes one or more of the following: Intent context; The desired object context expected by the intent; The desired target context desired by the intent.

15. The method according to claim 13, characterized in that The receiving a first request sent by a first device includes: Receiving the first request sent by the first device when one or more of the following conditions are met: receiving a first instruction, wherein the first instruction is used to instruct sending the first request to the second device; receiving a second intent, the second intent conflicting with the first intent; Network resources have changed.

16. An intention negotiation device, characterized in that: Applied to a first device, the apparatus comprises: A first sending module, configured to send a first request to a second device while ensuring the implementation of the first intention, wherein the first request is used to request an intention negotiation; The first receiving module is used to receive a first response sent by the second device, wherein the first response is used to indicate whether the second device accepts the first request.

17. An intention negotiation device, characterized in that: Applied to a second device, the apparatus comprises: A first receiving module, configured to receive a first request sent by a first device, wherein the first request is used to request an intent negotiation and is sent by the first device under the condition of ensuring the implementation of the first intent; The first sending module is used to send a first response to the first device, wherein the first response is used to indicate whether the second device accepts the first request.

18. An intention negotiation device, characterized in that: Applied to a first device, the apparatus comprises: a processor and a transceiver; The transceiver is used to send a first request to the second device while ensuring the implementation of the first intention, wherein the first request is used to request intention negotiation; and receive a first response sent by the second device, wherein the first response is used to indicate whether the second device accepts the first request.

19. An intention negotiation device, characterized in that: Applied to a second device, the apparatus comprises: a processor and a transceiver; The transceiver is used to receive a first request sent by a first device, wherein the first request is used to request an intent negotiation and is sent by the first device while ensuring the implementation of the first intention; and send a first response to the first device, wherein the first response is used to indicate whether the second device accepts the first request.

20. A communication device comprising: A memory, a processor, and a program stored in the memory and executable on the processor; wherein the processor is used to read the program in the memory to implement the steps in the intention negotiation method as described in any one of claims 1 to 15.

21. A computer-readable storage medium for storing a program, characterized in that: When the program is executed by a processor, the steps in the intention negotiation method according to any one of claims 1 to 15 are implemented.

22. A computer program product, characterized in that The method comprises computer instructions, which, when executed by a processor, implement the steps in the intention negotiation method according to any one of claims 1 to 15.

Images