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

Abstract

This application discloses an intent negotiation method, apparatus, device, readable storage medium, and program product, relating to the field of communication technology, to ensure the reliability and robustness of intent-driven networks. The method includes: a first device sending a first request to a second device while ensuring the implementation of a first intent, wherein the first request is used to request intent negotiation; and receiving a first response sent by the second device, wherein the first response is used to indicate whether the second device accepts the first request. Embodiments of this application can ensure the reliability and robustness of intent-driven networks.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and in particular to an intention negotiation method and device, equipment, readable storage medium and program product. BACKGROUND

[0002] In an intention-driven network, information interaction between autonomous domains and different levels is "intention-driven". An intention is all desired formal specifications, including requirements, goals and constraints for a technical system. It describes the desired state of the network without specifying how to achieve this state. An intention-driven management service producer (MnS producer) allows an intention-driven management service consumer (MnS consumer) to express service and network resource management through an intention.

[0003] Among them, the intention-driven management service consumer provides an intention description to the intention-driven management service producer and receives intention execution satisfaction information; the intention-driven management service producer receives the intention of the intention-driven management service consumer, verifies, translates and executes the intention, and then feeds back the intention execution satisfaction information to the intention-driven management service consumer. By introducing an intention, the expectations of the system are decoupled from the specific implementation details, leaving room for exploring alternative solutions and finding the best solution.

[0004] In the intention negotiation process, negotiation can be triggered by the intention-driven management service consumer. However, this approach may not be able to obtain a fair and reasonable negotiation result, thereby affecting the reliability and robustness of the intention-driven network. SUMMARY

[0005] Embodiments of the present application provide an intention negotiation method, device, equipment, readable storage medium and program product to ensure the reliability and robustness of the intention-driven network.

[0006] In a first aspect, embodiments of the present application provide an intention negotiation method applied to a first device, the method comprising:

[0007] In the case of ensuring the implementation of the first intention, a first request is sent to a 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] An intention negotiation identifier, used to identify an intention to be negotiated;

[0011] A suggested modified intention expectation combination;

[0012] The intention expectation included in the suggested modified intention expectation combination;

[0013] A desired object of the intention expectation;

[0014] A desired target of the intention expectation;

[0015] A desired context of the intention expectation.

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

[0017] A suggested modified intention context;

[0018] A desired object context of the intention expectation;

[0019] A desired target context of the intention expectation;

[0020] An impact of intention change;

[0021] A reason for intention negotiation.

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

[0023] According to intention priorities of each candidate intention, the candidate intentions are sorted to obtain a first sorting result;

[0024] According to a gap size between resources reserved for desired targets of intention expectations of each candidate intention and actual intention consumption resources of each candidate intention, the candidate intentions are sorted to obtain a second sorting result;

[0025] According to an impact size of a negotiation result of intention negotiation with each candidate intention on the network, the candidate intentions are sorted 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 intention to be negotiated is determined from the candidate intentions.

[0027] Optionally, the method further includes:

[0028] In a case where the first response indicates that the second device accepts the first request, an updated first intention in the first response is obtained, and implementation of the updated first intention is ensured;

[0029] In a case where the first response indicates that the second device does not accept the first request, continuing to guarantee implementation of the first intent.

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

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

[0032] A second intent is received, wherein the second intent conflicts with the first intent;

[0033] A network resource changes.

[0034] Optionally, the first request is sent in a case where a second intent of the second device or a third device is received; the method further comprises:

[0035] In a case where 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 intent is feasible;

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

[0037] Optionally, the method further comprises:

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

[0039] Sending a second response to the second device, wherein the second response is used to indicate whether the first intent is feasible.

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

[0041] An intent expectation combination;

[0042] An intent expectation included in the intent expectation combination;

[0043] An expectation object of the intent expectation;

[0044] An expectation target of the intent expectation;

[0045] An expectation context of the intent expectation.

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

[0047] An intent context;

[0048] a desired object context of the intention expectation;

[0049] a desired target context of the intention expectation.

[0050] In a second aspect, an intention negotiation method is provided, and is applied to a second device. The method comprises:

[0051] receiving a first request sent by a first device, wherein the first request is used to request to perform intention negotiation, and is sent by the first device under the condition of guaranteeing implementation of a first intention;

[0052] sending a first response to the first device, wherein the first response is used to indicate whether the second device accepts the first request.

[0053] Optionally, the method further comprises:

[0054] sending a second request to the first device, wherein the second request is used to request to perform intention negotiation;

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

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

[0057] an intention expectation combination;

[0058] an intention expectation included in the intention expectation combination;

[0059] a desired object of the intention expectation;

[0060] a desired target of the intention expectation;

[0061] a desired context of the intention expectation.

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

[0063] an intention context;

[0064] a desired object of the intention expectation

[0065] a desired target context of the intention expectation.

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

[0067] receiving the first request sent by the first device under the condition of satisfying one or more of the following:

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

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

[0070] The network resource changes.

[0071] In a third aspect, an intent negotiation apparatus is provided, applied to a first device, and the apparatus comprises:

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

[0073] A 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 comprises one or more of the following information:

[0075] An intent negotiation identifier, used to identify an intent to be negotiated;

[0076] A suggested modified intent expectation combination;

[0077] The suggested modified intent expectation combination comprises an intent expectation;

[0078] An expectation object of the intent expectation;

[0079] An expectation target of the intent expectation;

[0080] An expectation context of the intent expectation.

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

[0082] A suggested modified intent context;

[0083] An expectation object context of the intent expectation;

[0084] An expectation target context of the intent expectation;

[0085] An impact after the intent is changed;

[0086] A reason for the intent negotiation.

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

[0088] According to an intent priority of each candidate intent, the each candidate intent is sorted to obtain a first sorting result;

[0089] According to a gap between resources reserved according to an expected target of guaranteeing an intention expectation of each candidate intention and actual intention consumption resources of each candidate intention, the candidate intentions are sorted to obtain a second sorting result;

[0090] According to an influence size of a negotiation result of intention negotiation with each candidate intention on a network, the candidate intentions are sorted 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 intention to be negotiated is determined from the candidate intentions.

[0092] Optionally, the apparatus further includes:

[0093] The first processing module is configured to, in a case where the first response indicates that the second device accepts the first request, acquire an updated first intention in the first response and guarantee implementation of the updated first intention.

[0094] The second processing module is configured to, in a case where the first response indicates that the second device does not accept the first request, continue to guarantee implementation of the first intention.

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

[0096] The first request is sent to the second device when one or more of the following conditions is met:

[0097] The first instruction is received, where the first instruction is used to instruct to send the first request to the second device.

[0098] The second intention is received, where the second intention conflicts with the first intention.

[0099] The network resource changes.

[0100] Optionally, the first request is sent in a case where the second intention of the second device or the third device is received; and the apparatus further includes:

[0101] The second sending module is configured to, in a case where the first response indicates that the second device accepts the first request, send first information to the second device or the third device, where the first information is used to indicate that the second intention is feasible.

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

[0103] Optionally, the apparatus further comprises:

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

[0105] a fourth sending module, configured 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 comprises one or more of the following:

[0107] an intention expectation combination;

[0108] an intention expectation contained in the intention expectation combination;

[0109] an expectation object of the intention expectation;

[0110] an expectation target of the intention expectation;

[0111] an expectation context of the intention expectation.

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

[0113] an intention context;

[0114] an expectation object context of the intention expectation;

[0115] an expectation target context of the intention expectation.

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

[0117] a first receiving module, configured to receive a first request sent by a first device, wherein the first request is used to request to perform intention negotiation and is sent by the first device under the condition of guaranteeing implementation of a first intention;

[0118] a first sending module, 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 apparatus further comprises:

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

[0121] a second receiving module, configured 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 comprises one or more of the following:

[0123] the intent expectation combination;

[0124] the intent expectation contained in the intent expectation combination;

[0125] the expected object of the intent expectation;

[0126] the expected target of the intent expectation;

[0127] the expected context of the intent expectation.

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

[0129] the intent context;

[0130] the expected object context of the intent expectation;

[0131] the expected target context of the intent expectation.

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

[0133] receive the first request sent by the first device under the condition that one or more of the following conditions are met:

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

[0135] a second intent is received, wherein the second intent conflicts with the first intent;

[0136] a network resource changes.

[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 configured to send a first request to a second device under the condition that a first intent is implemented, wherein the first request is used to request to perform intent 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 comprises one or more of the following information:

[0140] an intent negotiation identifier, used to identify an intent to be negotiated;

[0141] a suggested modified intent expectation combination;

[0142] The intention expectation of the proposed modification comprises an intention expectation;

[0143] The expected object of the intention expectation;

[0144] The expected target of the intention expectation;

[0145] The expected context of the intention expectation.

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

[0147] The intention context of the proposed modification;

[0148] The expected object context of the intention expectation;

[0149] The expected target context of the intention expectation;

[0150] The impact of the intention change;

[0151] The reason of the intention negotiation.

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

[0153] The candidate intentions are sorted according to the intention priorities of the candidate intentions, to obtain a first sorting result;

[0154] The candidate intentions are sorted according to the size of the gap between the resources reserved for the expected target of the intention expectation of each candidate intention and the actual intention consumption resources of each candidate intention, to obtain a second sorting result;

[0155] The candidate intentions are sorted according to the size of the impact of the negotiation result of the intention negotiation with the candidate intentions on the network, to obtain a third sorting result;

[0156] The intention to be negotiated is determined from the candidate intentions based on one or more of the first sorting result, the second sorting result and the third sorting result.

[0157] Optionally, the processor is configured to:

[0158] In a case where the first response indicates that the second device accepts the first request, an updated first intention in the first response is obtained, and implementation of the updated first intention is ensured;

[0159] In a case where the first response indicates that the second device does not accept the first request, implementation of the first intention is continued to be ensured.

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

[0161] The first request is sent to the second device when one or more of the following conditions is met:

[0162] The first instruction is received, wherein the first instruction is used to instruct to send the first request to the second device;

[0163] The second intention is received, wherein the second intention conflicts with the first intention;

[0164] The network resource changes.

[0165] Optionally, the first request is sent in the case that the second intention of the second device or the third device is received; and the transceiver is further configured to:

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

[0167] In the case that 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] The second request sent by the second device is received, wherein the second request is used to request to perform intention negotiation;

[0170] The 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 comprises one or more of the following:

[0172] An intention expectation combination;

[0173] An intention expectation included in the intention expectation combination;

[0174] An expectation object of the intention expectation;

[0175] An expectation target of the intention expectation;

[0176] An expectation context of the intention expectation.

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

[0178] An intention context;

[0179] An expectation object context of the intention expectation;

[0180] a desired target context of the intention expectation.

[0181] In a sixth aspect, an intention negotiation apparatus is provided, which is applied to a second device and includes a processor and a transceiver.

[0182] The transceiver is configured to receive a first request sent by a first device, where the first request is used to request to perform intention negotiation and is sent by the first device under the condition of guaranteeing implementation of a first intention; and send a first response to the first device, where the first response is used to indicate whether the second device accepts the first request.

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

[0184] send a second request to the first device, where the second request is used to request to perform intention negotiation;

[0185] receive a second response sent by the first device, where 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] an intention expectation combination;

[0188] an intention expectation included in the intention expectation combination;

[0189] a desired object of the intention expectation;

[0190] a desired target of the intention expectation;

[0191] a desired context of the intention expectation.

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

[0193] an intention context;

[0194] a desired object context of the intention expectation;

[0195] a desired target context of the intention expectation.

[0196] Optionally, the transceiver is further configured to receive the first request sent by the first device under the condition of satisfying one or more of the following:

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

[0198] receiving a second intention, where the second intention conflicts with the first intention;

[0199] The network resource changes.

[0200] In a seventh aspect, an embodiment of the present application further provides a communication device, comprising a memory, a processor, and a program stored in the memory and capable of running on the processor, and the processor implements the steps in the intention negotiation method when executing the program.

[0201] In an eighth aspect, an embodiment of the present application further provides a readable storage medium, and the readable storage medium stores a program, and the program is executed by a processor to implement the steps in the intention negotiation method.

[0202] In a ninth aspect, an embodiment of the present application further provides a computer program product, comprising computer instructions, and the computer instructions are executed by a processor to implement the steps in the intention negotiation method.

[0203] In the embodiment of the present application, the first device can send a first request to the second device for intention negotiation while ensuring implementation of the first intention. By the active intention negotiation of the first device in the implementation process of the first intention, a more fair and reasonable negotiation result can be obtained, thereby ensuring the reliability and robustness of the intention-driven network. BRIEF DESCRIPTION OF DRAWINGS

[0204] Figure 1 FIG. 1 is one of flowcharts of the intention negotiation method provided by an embodiment of the present application;

[0205] Figure 2 FIG. 2 is another of flowcharts of the intention negotiation method provided by an embodiment of the present application;

[0206] Figure 3 FIG. 3 is a third of flowcharts of the intention negotiation method provided by an embodiment of the present application;

[0207] Figure 4 FIG. 4 is a fourth of flowcharts of the intention negotiation method provided by an embodiment of the present application;

[0208] Figure 5 FIG. 5 is one of structural diagrams of the intention negotiation apparatus provided by an embodiment of the present application;

[0209] Figure 6 FIG. 6 is another of structural diagrams of the intention negotiation apparatus provided by an embodiment of the present application;

[0210] Figure 7 FIG. 7 is a third of structural diagrams of the intention negotiation apparatus provided by an embodiment of the present application;

[0211] Figure 8 FIG. 8 is a fourth of structural diagrams of the intention negotiation apparatus provided by an embodiment of the present application. DETAILED DESCRIPTION

[0212] The term "and / or" in the embodiments of the present application describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent the following three cases: A exists alone, A and B exist together, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after it.

[0213] The term "multiple" in the embodiments of the present application means two or more, and other quantifiers are similar.

[0214] The technical solutions in the embodiments of the present application will be described clearly and completely in combination with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present application.

[0215] Referring to Figure 1 , Figure 1 is a flowchart of the intent negotiation method provided by the embodiments of the present application, applied to a first device. As shown in Figure 1 , the following steps are included:

[0216] Step 101: In the case of ensuring implementation of a first intent, a first request is sent to a second device, wherein the first request is used to request intent negotiation.

[0217] The first intent can be any intent after the second device and the first device negotiate, for example, the first device and the second device can negotiate in the intent creation, intent update, intent activation or intent restart stage. Meanwhile, the first intent can be one or more intents.

[0218] The first device has an intent management function. In the embodiments, the first device has an intent management function, for example, can be an intent-driven management service producer, or also can be called an intent handler. The second device has an intent management function, for example, can be an intent-driven management service consumer, or also can be called an intent owner. The first device and the second device interact based on an intent management interface to 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, core network service, network slice, or end-to-end communication service.

[0219] The first device sends the first request to the second device in the case of meeting one or more of the following conditions:

[0220] (1) receiving a first instruction, wherein the first instruction is used to instruct sending the first request to the second device. The first instruction can come from some network management device or the like.

[0221] (2) receiving a second intent, which conflicts with the first intent. That is, when the first device receives a new intent, it can request intent negotiation with the second device for the ongoing guaranteed intent. Here, the conflict may refer to, for example, the resources required by the second intent conflict with the resources required for implementation of the first intent.

[0222] (3) network resources change.

[0223] For example, the first device monitors that the network resources change, such as the current network resources cannot guarantee the execution of the first intent; the current network resources are relatively sufficient and can guarantee the execution of multiple intents at the same time, and the like. For example, the first device monitors that a device failure occurs, which can also trigger sending of the first request.

[0224] Of course, in the embodiments of the present application, the first request can also be sent to the second device in other manners, such as sending at a certain period, and the like.

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

[0226] an intent negotiation identifier;

[0227] a proposed modified intent expectation combination;

[0228] an intent expectation included in the proposed modified intent expectation combination;

[0229] an expectation object of the intent expectation;

[0230] an expectation target of the intent expectation;

[0231] an expectation context of the intent expectation.

[0232] The intent negotiation identifier is used to identify the intent to be negotiated, to indicate which intent or intents are negotiated. The intent to be negotiated can be one or more of the candidate intents.

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

[0234] (1) According to the intent priorities of each candidate intent, the candidate intents are sorted to obtain a first sorting result. Each candidate intent has a corresponding intent priority. For example, the candidate intents can be sorted in order of high to low or low to high intent priority, thereby obtaining the first sorting result. When the intent negotiation is performed, the intent with a low priority can be negotiated first.

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

[0236] (3) According to the influence size of the negotiation result of the intention negotiation with each candidate intention on the network, the candidate intentions are sorted to obtain a third sorting result. The first device can evaluate the influence according to the information such as its own resources and implementation of the intention, so as to determine the size of the influence. When intention negotiation is performed, the candidate intention with a smaller influence is negotiated first.

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

[0238] After the above sorting results are obtained, the intention to be negotiated can be determined based on one or more of one or more sorting results.

[0239] For example, the intention to be negotiated can be determined from the candidate intentions directly based on the first sorting result or the second sorting result or the third sorting result. For example, one or more candidate intentions with a lower priority can be determined as the intention to be negotiated according to the first sorting result; one or more candidate intentions with a larger gap can be determined as the intention to be negotiated according to the second sorting result; and one or more candidate intentions with a smaller influence can be determined as the intention to be negotiated according to the third sorting result.

[0240] For another example, if the intention to be negotiated is determined according to multiple sorting results, each candidate intention can be decomposed according to a preset condition expression (for example, a multi-objective optimization algorithm), and then the intention to be negotiated is determined.

[0241] The suggested modification intention expectation combination can be the best intention expectation combination within the capability of the first device, which is determined by the first device according to its own resource condition, satisfaction information of historical intentions, and the like (it is necessary to ensure that the second intention can be satisfied). The best intention expectation combination can be understood as an intention expectation combination that can adapt to new information or changes while satisfying the execution of the first intention. The intention expectation combination can include one or more intention expectations. The expected object of the intention expectation can be, for example, a certain system, network, device, node, and the like. The expected target of the intention expectation can be, for example, bandwidth, latency, and the like. The expected context of the intention expectation can be information related to the intention expectation, and the like.

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

[0243] The suggested modification intention context: describes the constraints and conditions applied to the entire intention, which is a three-tuple combination of attributes, conditions, and value ranges;

[0244] The expected object context of the intention expectation: describes a list of constraints and conditions applied to a specific expected object;

[0245] The expected target context of the intention expectation: describes a list of constraints and conditions applied to a specific expected target;

[0246] The impact of the intention change;

[0247] The reason for the intention negotiation.

[0248] The impact of the intention change refers to the impact of the change of a certain intention, for example, the change of delay, the change of bandwidth, and the like. For example, the impact can refer to the impact on the implementation of the intention after accepting the intention negotiation, and these impacts can not be explicitly expressed in the intention, and the like. The reason for the intention negotiation can include, for example, satisfying the hope of other intentions to coordinate part of the resources.

[0249] By carrying the above information in the first request, the first device and the second device can explicitly negotiate the content, the impact brought by the negotiation, and the like, thereby improving the accuracy of intention identification and improving the efficiency of intention negotiation.

[0250] In actual application, the first request can be sent in various ways. For example, an intention negotiation report can be introduced in the intention report to carry the intention negotiation information of the intention-driven management service producer to the intention-driven management service consumer, that is, the first request. Alternatively, a new message can be directly sent to the second device, and the new message serves as the first request.

[0251] In the first request, an exemplary portable intention negotiation identifier, a reason for intention negotiation, an impact of intention change, and a suggested modified intention expectation combination are carried.

[0252] In step 102, a first response sent by the second device is received, 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 can determine whether to accept the first request according to the first request and its own needs and other factors, and indicate this to the first device through the first response. If the first request is accepted, the second device can also send the updated first intention to the first device through the first response.

[0254] In a case where the first response indicates that the second device accepts the first request, the first device acquires the updated first intention in the first response and guarantees implementation of the updated first intention. Meanwhile, if the first request is sent in a case where a second intention of the second device or a third device is received, the first device can also send first information to the third device, where the first information is used to indicate that the second intention is feasible, so as to start an intention new creation process.

[0255] In a case where the first response indicates that the second device does not accept the first request, implementation of the first intention is continued. Meanwhile, if the first request is sent in a case where a second intention of the second device or a third device is received, the first device can also send second information to the second device or the third device, where the second information is used to indicate that the second intention is not feasible, and optionally, the second information can also carry a rejection reason and a conflict target. For example, the rejection reason can be that current resources cannot satisfy implementation of the intention, and the conflict target can be bandwidth conflict.

[0256] In the embodiments of the present application, the first device can send the first request to the second device to perform intention negotiation while guaranteeing implementation of the first intention. Therefore, by actively performing intention negotiation in the process of guaranteeing implementation of the first intention, the first device can respond to newly appeared information or changes to make timely adjustment, so as to obtain a more fair and reasonable negotiation result, thereby guaranteeing reliability and robustness of the intention-driven network.

[0257] The intention negotiation process described above is performed in the case of intention execution. In the embodiments of the present application, intention negotiation can also be performed in the intention creation, intention update, intention activation or intention restart phase, so as to avoid potential conflicts caused by intention new creation or change through feasibility check, intention exploration and intention negotiation. The negotiation in this phase is initiated by the intention driven management service consumer. Correspondingly, for the first device, the second request sent by the second device can be received, wherein the second request is used to request intention negotiation. Then, the first device can perform feasibility check and send 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 whether there is potential conflict between the satisfaction degree of intention implementation and one or more intentions (or intention instances). If the result of the feasibility check is feasible, the intention driven management service producer performs service or network management task to satisfy the intention, otherwise the intention is rejected.

[0258] For the first device and the second device, interaction is performed based on the intention (corresponding to the second request), which is composed of a specific intention information model and contains intention expectation, constraint and other information. The intention expectation contains expected object, expected target, target value, context and other information.

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

[0260] Intention expectation combination;

[0261] Intention expectation contained in the intention expectation combination;

[0262] Expected object of the intention expectation;

[0263] Expected target of the intention expectation;

[0264] Expected context of the intention expectation.

[0265] The intention expectation combination can include one or more intention expectations, which can be determined by the second device according to its own needs. The expected object of the intention expectation can be, for example, a certain system, network, device, node, etc. The expected target of the intention expectation can be, for example, bandwidth, latency, etc. The expected context of the intention expectation can be information related to the intention expectation, etc.

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

[0267] Intention context: describes the constraints and conditions applied to the entire intention, which is a three-tuple combination of attributes, conditions and value ranges;

[0268] Expected object context of the intention expectation: describes a list of constraints and conditions applied to a specific expected object;

[0269] The expected target context expected by the intention describes a list of constraints and conditions applied to a specific expected target.

[0270] Therefore, in combination with intention negotiation in different stages, the initiative of the intention-driven management service producer in a multi-intention satisfaction scenario can be ensured without affecting the global state of the network, active negotiation between the intention-driven management service producer and the intention-driven management service consumer is supported, timely adjustment is allowed according to new information or changes in the intention guarantee process, the intention implementation is more in line with the real expectations of the intention-driven management service consumer, and thus the satisfaction of the intention-driven management service consumer can be improved, and the reliability and flexibility of the intention-driven network system can be improved.

[0271] Referring to Figure 2 , Figure 2 is a flowchart of an intention negotiation method provided by an embodiment of the present application, applied to a second device. As shown in Figure 2 , the following steps are included:

[0272] Step 201: 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 in a case of guaranteeing implementation of a first intention, the first device and the second device have an intention management function, for example, in this embodiment, the first device can be an intention-driven management service producer, and the second device can be an intention-driven management service consumer.

[0273] Specifically, the second device can receive the first request sent by the first device in a case of meeting one or more of the following conditions:

[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 intention, wherein the second intention conflicts with the first intention;

[0276] a network resource changes.

[0277] The explanations of the above conditions can refer to the descriptions of the foregoing embodiments.

[0278] The explanation of the first request can refer to the descriptions of the foregoing method embodiments.

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

[0280] The second device, after receiving the first request, can determine whether to accept the first request according to the first request and its own needs and other factors, and indicate the first device through the first response. If the first request is accepted, the second device can also send the updated first intent to the first device through the first response.

[0281] In the embodiments of the present application, the first device can send the first request to the second device to perform intent negotiation while ensuring the implementation of the first intent. Therefore, through the active intent negotiation of the first device in the process of ensuring the implementation of the first intent, the newly emerging information or changes can be adjusted in time, and a more fair and reasonable negotiation result can be obtained, so as to ensure the reliability and robustness of the intent-driven network.

[0282] The above-described intent negotiation process is performed while ensuring the implementation of the intent. In the embodiments of the present application, intent negotiation can also be performed in the intent creation, intent update, intent activation or intent restart phase, so as to avoid potential conflicts caused by new intent creation or changes through feasibility check, intent exploration and intent negotiation. The negotiation in this phase is initiated by the intent-driven management service consumer.

[0283] Specifically, the second device can 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 to perform intent negotiation, and the second response is used to indicate whether the first intent is feasible.

[0284] The explanation of the second request can refer to the description of the foregoing method embodiments.

[0285] Therefore, in combination with intent negotiation in different phases, the initiative of the intent-driven management service producer in the multi-intent satisfaction scenario can be ensured without affecting the global state of the network, active negotiation between the intent-driven management service producer and the intent-driven management service consumer is supported, timely adjustment according to newly emerging information or changes in the intent guarantee process is allowed, the implementation of the intent meets the real expectations of the intent-driven management service consumer more, and therefore the satisfaction of the intent-driven management service consumer can be improved, and the reliability and flexibility of the intent-driven network system can be improved.

[0286] Referring to Figure 3 , Figure 3is a flow chart of the intention negotiation method of the embodiments of the present application. In this flow chart, two stages of intention negotiation are shown. Among them, the intention negotiation of the first stage occurs in the intention creation, intention update, intention activation or intention restart stage, through the feasibility check, intention exploration, intention negotiation, to avoid potential conflicts caused by intention new creation or change; the intention negotiation of the second stage occurs in the intention execution or implementation stage, in which the intention-driven management service producer actively triggers the ability of intention change, improves the system flexibility, and guarantees the resource utilization rate.

[0287] The process of the above intention negotiation occurs between two devices with intention management function, which are respectively the intention-driven management service consumer and the intention-driven management service producer.

[0288] Among them, the intention-driven management service producer allows the intention-driven management service consumer to manage services and network resources through intention expression. Among them, the intention-driven management service consumer provides intention description to the intention-driven management service producer, and receives intention execution satisfaction information; the intention-driven management service producer receives the intention of the intention-driven management service consumer, verifies, translates and executes the intention, and then feeds back the intention execution satisfaction information to the intention-driven management service consumer.

[0289] The processing flow of intention can be roughly divided into five stages of detection, investigation, definition, distribution, and implementation. In the detection stage, the intention-driven management service consumer determines whether a new intention needs to be defined or an existing intention needs to be changed by detecting the demand satisfaction situation. In the investigation stage, the intention-driven management service consumer finds the correct intention-driven management service producer, and the intention-driven management service producer and the intention-driven management service producer determine the feasibility of the intention through investigation negotiation. In the definition stage, the intention-driven management service consumer formulates the intention and related expectations by combining the investigation information with the demand determined in the detection stage. In the distribution stage, the intention-driven management service consumer creates a new intention object or modifies or changes an existing intention object to include the intention expectations obtained in the definition stage. If the intention-driven management service producer accepts the intention, the intention object enters the implementation stage; otherwise, it will send a report to the intention-driven management service consumer containing the reason for rejection, and the intention object life cycle ends (at this time, the intention-driven management service consumer can start creating a new intention through detection). In the implementation stage, the intention-driven management service producer operates its responsibility domain according to the accepted intention object, to guarantee that the expectations corresponding to the intention object are satisfied. In addition, the intention-driven management service producer needs to report to the intention-driven management service consumer the intention satisfaction situation, the execution state and the unmet reason, etc.

[0290] In Figure 3In the flow, the first device is an intent-driven management service producer, and the second device is an intent-driven management service consumer. Generally, the intent-driven management service consumer sends an intent to the intent-driven management service producer, and the intent-driven management service producer feeds back an intent report to the intent-driven management service consumer, both of which interact based on an agreed information model to ensure consistent understanding between the two parties.

[0291] The elements in the intent template include:

[0292] The intent expectation combination, the intent expectation contained in the intent expectation combination, the expectation object of the intent expectation, the expectation target of the intent expectation, and the expectation context of the intent expectation. In some embodiments, the intent context, the expectation object context of the intent expectation, and the expectation target context of the intent expectation can also be included. The intent report includes an intent satisfaction report, an intent feasibility check report, an intent exploration report, and various forms, which appear at different links in the life cycle of the intent.

[0293] As shown in Figure 3 The intent negotiation process can specifically include:

[0294] I. First-stage intent negotiation:

[0295] Step 301, the second device sends an intent request (i.e., a second request) to the first device for 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 (i.e., a second response) to the second device, including intent check results, recommendation information, and negotiation results.

[0298] After that, if the notification feedback of the first device indicates that the intent is feasible, the second device can send an intent implementation request to the first device, and the first device performs intent and evaluation and reports intent satisfaction information to the second device.

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

[0300] Step 305, the first device performs intent and evaluation.

[0301] Step 306, the first device reports intent satisfaction information to the first device.

[0302] II. Second-stage intent negotiation:

[0303] Step 307, the first device sends an intent negotiation request (i.e., a first request) to the second device, including negotiation reasons, recommended expectations, and the impact of intent modification.

[0304] Step 308, if the request is accepted, the second device sends an intent update request (i.e., a first response) to the first device, carrying the updated intent. If the request is not accepted, a response can be sent indicating that the request is not accepted (not shown).

[0305] Referring to Figure 4 , Figure 4 is a flowchart of the intent negotiation method of the embodiments of the present application. In the flowchart, the following processes can be included:

[0306] Step 401, the intent-driven management service consumer defines a new intent or changes an existing intent, and performs first intent distribution.

[0307] In this step, the intent-driven management service consumer performs first intent distribution, 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, which can have the following possibilities:

[0309] (1) The intent-driven management service producer is not a target intent producer and does not understand the semantics of the intent. The intent-driven management service producer directly rejects the intent and feeds back the unfeasible reason (as shown in 4021 in the figure).

[0310] (2) The intent-driven management service producer determines that the first intent itself or the first intent and historical intents have conflicts, such as conflicts between intents, expectations, targets, or the intent cannot be implemented. The intent-driven management service producer directly rejects the intent and feeds back the unfeasible reason (as shown in 4021 in the figure).

[0311] (3) The intent-driven management service producer determines that all or part of the expectations and targets of the first intent are feasible, and then starts negotiation for the first intent, jumping to step 403.

[0312] Step 403, the intent-driven management service producer synthesizes resource conditions and historical satisfaction information, and feeds back to the intent-driven management service consumer a best intent suggestion combination within the capability range of the intent-driven management service producer and potential impacts.

[0313] Step 404, the intent-driven management service consumer receives the negotiated intent, confirms the intent expectations and corresponding target values (here, the best intent combination provided by the intent-driven management service producer is the upper limit of system capability, and the intent-driven management service consumer can adjust to a lower capability without the need for repeated negotiation), and sends to the intent-driven management service producer.

[0314] Step 405, the intent-driven management service producer generates or changes the intent instance according to the received information.

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

[0316] Step 407, during the implementation of the intent, the intent-driven management service producer monitors network state changes or receives new intent requests.

[0317] Step 408, if the network state change is monitored or the new intent request is received, the intent-driven management service producer actively triggers negotiation with the intent-driven management service consumer. Otherwise, it can continue to step 406.

[0318] According to the foregoing embodiment, the intent-driven management service producer models and sends the intent negotiation information to the intent-driven management service consumer.

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

[0320] intent negotiation identifier, proposed modified intent expectation combination, intent expectation contained in the intent expectation combination, expectation object of the intent expectation, expectation target of the intent expectation, expectation context of the intent expectation. In some embodiments, it can also include proposed modified intent context, expectation object context of the intent expectation, expectation target context of the intent expectation, impact of intent change, intent negotiation reason.

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

[0322] Taking the wireless network scenario as an example, the bandwidth demand of business traffic varies according to user business type, time period, etc. Through intent negotiation, adaptive high-reliability service operation guarantee can be achieved.

[0323] Suppose that the current intent-driven management service producer is ensuring the fulfillment of intent A for 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 video live streaming and gaming experiences in the same time period. Under the condition of insufficient available bandwidth resources, the two intents are in competition. In traditional intent solutions, intent A is prioritized. When intent B requests bandwidth resources, it will receive an intent report indicating that system resources are not met during the intent detection phase, and thus refuse to establish the intent object, making it impossible to fulfill the intent. Therefore, a dynamic guarantee and state balance based on intent-driven self-intelligent network cannot be achieved. In this embodiment, when the intent-driven management service producer receives a new intent request, it determines whether the new intent can be fulfilled and its impact on the current management domain. Suppose that at this time, it is determined that there is a potential conflict with the running intent instance. If the intent-driven management service producer detects that the expected target value of the intent expectation set by the intent-driven management service consumer is higher than the actual demand, it can negotiate with intent-driven management service consumer 1 to adjust intent A.

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

[0325] Intent to Negotiate: Negotiation type;

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

[0327] Recommended modification to the intended combination: reduce the desired bandwidth value to 300M; impact: latency and other metrics remain unchanged.

[0328] After receiving the consultation information, consumers of the intent-driven management service determine whether to adjust their intent A according to the suggestion.

[0329] If the intent-driven management service consumer accepts the negotiation, it updates intent A and sends it to the intent-driven management service producer. The intent-driven management service producer updates the instance of intent A and continues to ensure the implementation of intent A. Simultaneously, the intent-driven management service producer determines feasibility and sends feasibility check information to the intent-driven management service consumer to which intent B belongs, initiating the intent creation process.

[0330] If the consumer of the intent-driven management service does not accept the negotiation and replies to the producer with a rejection message, the producer will maintain the original implementation guarantee for intent A. Simultaneously, if the producer determines that intent A is infeasible, it will provide feasibility check information to the consumer of intent B, indicating the reasons for rejection and conflicting objectives.

[0331] As can be seen from the above embodiments, by combining intent negotiation at different stages, the initiative of intent-driven management service producers in multi-intent fulfillment scenarios can be guaranteed without affecting the overall network state. It supports proactive negotiation between intent-driven management service producers and intent-driven management service consumers, and allows timely adjustments based on newly emerging information or changes during the intent guarantee process. This makes intent fulfillment more in line with the true expectations of intent-driven management service consumers, thereby improving their satisfaction and enhancing the reliability and flexibility of the intent-driven network system.

[0332] See Figure 5 , Figure 5 This is a structural diagram of the intent negotiation device provided in an embodiment of this application, applied to a first device, the first device having intent management function. Figure 5 As shown, the intent 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 intent, wherein the first request is used to request intent negotiation, and the second device has 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] Intent to Negotiate identifier, used to identify the intent to negotiate;

[0336] Suggested modifications to the combination of intended expectations;

[0337] The proposed modified combination of intent expectations includes the intent expectations;

[0338] The intended object is the object of expectation;

[0339] The intended goal is as follows;

[0340] The expected context of the intent.

[0341] Optionally, the first request may also include one or more of the following information:

[0342] Suggested modifications to the intent context;

[0343] The intended object context is expected;

[0344] The intended target context;

[0345] The impact of the change of intent;

[0346] The reason for the intention to negotiate.

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

[0348] Based on the intent priority of each candidate intent, the candidate intents are sorted to obtain a first sorting result;

[0349] Based on the difference between the resources reserved for the expected goals of each candidate intention and the actual resources consumed by each candidate intention, the candidate intentions are sorted to obtain a second sorting result.

[0350] Based on the magnitude of the impact of the negotiation results with each candidate intent on the network, the candidate intents are ranked to obtain a third ranking result;

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

[0352] Optionally, the device further includes:

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

[0354] The second processing module is configured to continue to ensure the implementation of the first intent even if the first response indicates that the second device does not accept the first request.

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

[0356] The second sending module is 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] A third sending module is configured to send a second message 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 message is used to indicate that the second intention is not feasible.

[0358] Optionally, the device further includes:

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

[0360] The 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] Intentional expectation combination;

[0363] The intent expectations included in the intent expectation combination;

[0364] The intended object is the object of expectation;

[0365] The intended goal is as follows;

[0366] The expected context of the intent.

[0367] Optionally, the second request may also include one or more of the following:

[0368] Intent context;

[0369] The intended object context is expected;

[0370] The intended target context.

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

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

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

[0374] A second intent is received, which conflicts with the first intent;

[0375] Network resources have changed.

[0376] The apparatus provided in this application embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.

[0377] See Figure 6 , Figure 6 This is a structural diagram of the intent negotiation device provided in an embodiment of this application, applied to a second device, the second device having intent management functions. For example... Figure 6 As shown, the intent negotiation device includes:

[0378] The first receiving module 601 is used to receive a first request sent by the first device, wherein the first request is used to request intent negotiation and is sent by the first device to ensure the implementation of the first intent, and the first device has 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] The second sending module is used to send a second request to the first device, wherein the second request is used to request intent negotiation;

[0381] The second receiving module is configured 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] Intentional expectation combination;

[0384] The intent expectations included in the intent expectation combination;

[0385] The intended object is the object of expectation;

[0386] The intended goal is as follows;

[0387] The expected context of the intent.

[0388] Optionally, the second request may also include one or more of the following:

[0389] Intent context;

[0390] The expected object context of the intent.

[0391] The intended target context.

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

[0393] Receive the first request sent by the first device under one or more of the following conditions:

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

[0395] A second intent is received, which conflicts with the first intent;

[0396] Network resources have changed.

[0397] The apparatus provided in this application embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.

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

[0399] The transceiver 702 is configured to send a first request to a second device while ensuring the implementation of the first intent, wherein the first request is used to request intent negotiation and the second device has intent management function; and 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.

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

[0401] Intent to Negotiate identifier, used to identify the intent to negotiate;

[0402] Suggested modifications to the combination of intended expectations;

[0403] The proposed modified combination of intent expectations includes the intent expectations;

[0404] The intended object is the object of expectation;

[0405] The intended goal is as follows;

[0406] The expected context of the intent.

[0407] Optionally, the first request may also include one or more of the following information:

[0408] Suggested modifications to the intent context;

[0409] The intended object context is expected;

[0410] The intended target context;

[0411] The impact of the change of intent;

[0412] The reason for the intention to negotiate.

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

[0414] Based on the intent priority of each candidate intent, the candidate intents are sorted to obtain a first sorting result;

[0415] Based on the difference between the resources reserved for the expected goals of each candidate intention and the actual resources consumed by each candidate intention, the candidate intentions are sorted to obtain a second sorting result.

[0416] Based on the magnitude of the impact of the negotiation results with each candidate intent on the network, the candidate intents are ranked to obtain a third ranking result;

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

[0418] Optionally, the processor 701 is used for:

[0419] If the first response indicates that the second device accepts the first request, the updated first intent in the first response is obtained, and the implementation of the updated first intent is guaranteed;

[0420] Even if the first response indicates that the second device does not accept the first request, the implementation of the first intention will continue.

[0421] Optionally, the first request is sent upon receiving a second intent from the second or third device; the transceiver 702 is further configured to:

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

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

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

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

[0426] Send a second response 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] Intentional expectation combination;

[0429] The intent expectations included in the intent expectation combination;

[0430] The intended object is the object of expectation;

[0431] The intended goal is as follows;

[0432] The expected context of the intent.

[0433] Optionally, the second request may also include one or more of the following:

[0434] Intent context;

[0435] The intended object context is expected;

[0436] The intended target context.

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

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

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

[0440] A second intent is received, which conflicts with the first intent;

[0441] Network resources have changed.

[0442] The apparatus provided in this application embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.

[0443] See Figure 8 , Figure 8 This is a structural diagram of the intent negotiation device provided in an embodiment of this application, applied to a second device, the second device having intent management functions. For example... Figure 8 As shown, the intent negotiation device includes: a processor 801 and a transceiver 802;

[0444] The transceiver 802 is configured to receive a first request sent by a first device, wherein the first request is for requesting intent negotiation and is sent by the first device to ensure the implementation of a first intent, and the first device has intent management function; and to send a first response to the first device, wherein the first response is for indicating whether the second device accepts the first request.

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

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

[0447] Receive a second response sent by the first device, 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] Intentional expectation combination;

[0450] The intent expectations included in the intent expectation combination;

[0451] The intended object is the object of expectation;

[0452] The intended goal is as follows;

[0453] The expected context of the intent.

[0454] Optionally, the second request may also include one or more of the following:

[0455] Intent context;

[0456] The intended object context is expected;

[0457] The intended target context.

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

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

[0460] A second intent is received, which conflicts with the first intent;

[0461] Network resources have changed.

[0462] The apparatus provided in this application embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.

[0463] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0464] If the integrated unit is implemented as 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 this application, in essence, 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. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0465] This application provides a communication device, including: 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 intent negotiation method as described above.

[0466] This application also provides a readable storage medium storing a program. When executed by a processor, this program implements the various processes of the above-described intent negotiation method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here. The readable storage medium can be any available medium or data storage device accessible to the processor, including but not limited to magnetic storage (e.g., floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND flash), solid-state drives (SSDs), etc.).

[0467] This application also provides a computer program product, including computer instructions. When executed by a processor, these computer instructions implement the various processes of the above-described intent negotiation method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0468] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0469] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0470] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. An intent negotiation method, characterized by, The method applied to a first device comprises: sending a first request to a second device in a case where implementation of a first intention is ensured, wherein the first request is used for requesting intention negotiation; receiving a first response sent by the second device, wherein the first response is used for indicating whether the second device accepts the first request; wherein the first request is sent to the second device when one or more of the following conditions is met: receiving a first instruction, wherein the first instruction is used for indicating that the first request is sent to the second device; receiving a second intention, wherein the second intention conflicts with the first intention; network resources change; wherein the method further comprises: in a case where the first response indicates that the second device accepts the first request, obtaining an updated first intention in the first response, and ensuring implementation of the updated first intention; in a case where the first response indicates that the second device does not accept the first request, continuing to ensure implementation of the first intention; wherein the method further comprises: receiving a second request sent by the second device, wherein the second request is used for requesting intention negotiation; sending a second response to the second device, wherein the second response is used for indicating whether the first intention is feasible.

2. The method of claim 1, wherein, The first request comprises one or more of the following information: an intention negotiation identifier, used for identifying an intention to be negotiated; a proposed modified intention expectation combination; an intention expectation included in the proposed modified intention expectation combination; an expectation object of the intention expectation; an expectation target of the intention expectation; an expectation context of the intention expectation.

3. The method of claim 2, wherein, The first request further comprises one or more of the following information: a proposed modified intention context; an expectation object context of the intention expectation; an expectation target context of the intention expectation; an impact after intention change; a reason for intention negotiation.

4. The method of claim 2, wherein, The intention to be negotiated is determined in the following manner: sorting each candidate intention according to an intention priority of the candidate intention, to obtain a first sorting result; sorting each candidate intention according to a gap size between resources reserved for ensuring an expectation target of an intention expectation of each candidate intention and actual intention consumption resources of each candidate intention, to obtain a second sorting result; sorting each candidate intention according to an impact size on a network caused by a negotiation result of intention negotiation of each candidate intention, to obtain a third sorting result; determining 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.

5. The method of claim 1, wherein, The first request is sent in a case where a second intention of the second device or a third device is received; the method further comprises: in a case where 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 for indicating that the second intention is feasible; In a case where the first response indicates that the second device does not accept the first request, a second information is sent to the second device or the third device, where the second information is used to indicate that the second intent is not feasible.

6. The method of claim 1, wherein, The second request comprises one or more of: an intent expectation combination; an intent expectation included in the intent expectation combination; an expectation object of the intent expectation; an expectation target of the intent expectation; an expectation context of the intent expectation.

7. The method of claim 6, wherein, The second request further comprises one or more of: an intent context; an expectation object context of the intent expectation; an expectation target context of the intent expectation.

8. An intent negotiation method, characterized by, The method applied to a second device comprises: receiving a first request sent by a first device, where the first request is used to request intent negotiation and is sent by the first device in a case where a first intent is implemented; sending a first response to the first device, where the first response is used to indicate whether the second device accepts the first request; wherein the receiving the first request sent by the first device comprises: receiving the first request sent by the first device in a case where one or more of the following conditions is met: receiving a first instruction, where the first instruction is used to indicate that the first request is sent to the second device; receiving a second intent, where the second intent conflicts with the first intent; a network resource changes; wherein in a case where the first response indicates that the second device accepts the first request, the first response is further used to indicate that the first device acquires an updated first intent in the first response and guarantees implementation of the updated first intent; in a case where the first response indicates that the second device does not accept the first request, the first response is further used to indicate that the first device continues to guarantee implementation of the first intent; wherein the method further comprises: sending a second request to the first device, where the second request is used to request intent negotiation; receiving a second response sent by the first device, where the second response is used to indicate whether the first intent is feasible.

9. The method of claim 8, wherein, The second request comprises one or more of: an intent expectation combination; an intent expectation included in the intent expectation combination; an expectation object of the intent expectation; an expectation target of the intent expectation; an expectation context of the intent expectation.

10. The method of claim 9, wherein, The second request further comprises one or more of: an intent context; an expectation object context of the intent expectation; an expectation target context of the intent expectation.

11. An intent negotiation apparatus characterized by comprising: The apparatus applied to a first device comprises: a first sending module configured to send a first request to a second device in a case where a first intent is implemented, where the first request is used to request intent negotiation; a first receiving module configured to 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; wherein the first sending module is further configured to send the first request to the second device in a case where one or more of the following conditions is met: receive a first instruction, wherein the first instruction is used to instruct to send the first request to the second device; receive a second intent, the second intent conflicts with the first intent; network resource changes; the apparatus further comprises: a first processing module, configured to acquire an updated first intent in the first response in a case that the first response indicates that the second device accepts the first request, and guarantee implementation of the updated first intent; a second processing module, configured to continue to guarantee implementation of the first intent in a case that the first response indicates that the second device does not accept the first request; a second receiving module, configured to receive a second request sent by the second device, wherein the second request is used to request to perform intent negotiation; a fourth sending module, configured to send a second response to the second device, wherein the second response is used to indicate whether the first intent is feasible.

12. An intent negotiation apparatus characterized by comprising: 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 to perform intent negotiation, and is sent by the first device in a case that implementation of a first intent is guaranteed; a first sending module, 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; wherein the first receiving module is further configured to receive the first request sent by the first device in a case that one or more of the following conditions is met: receive a first instruction, wherein the first instruction is used to instruct to send the first request to the second device; receive a second intent, the second intent conflicts with the first intent; network resource changes; wherein in a case that the first response indicates that the second device accepts the first request, the first response is further used to instruct the first device to acquire an updated first intent in the first response, and guarantee implementation of the updated first intent; in a case that the first response indicates that the second device does not accept the first request, the first response is further used to instruct the first device to continue to guarantee implementation of the first intent; wherein the apparatus further comprises: a second sending module, configured to send a second request to the first device, wherein the second request is used to request to perform intent negotiation; a second receiving module, configured to receive a second response sent by the first device, wherein the second response is used to indicate whether the first intent is feasible.

13. An intent negotiation apparatus characterized by comprising: applied to a first device, the apparatus comprises a processor and a transceiver; wherein the transceiver is configured to send a first request to a second device in a case that implementation of a first intent is guaranteed, wherein the first request is used to request to perform intent 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; wherein the transceiver is further configured to: send the first request to the second device in a case that one or more of the following conditions is met: receive a first instruction, wherein the first instruction is used to instruct to send the first request to the second device; receive a second intention, the second intention conflicting with the first intention; network resource changes; wherein the processor is further configured to: in a case where the first response indicates that the second device accepts the first request, acquire an updated first intention in the first response and guarantee implementation of the updated first intention; in a case where the first response indicates that the second device does not accept the first request, continue to guarantee implementation of the first intention; wherein the transceiver is further configured to: receive a second request sent by the second device, wherein the second request is used to request intention negotiation; send a second response to the second device, wherein the second response is used to indicate whether the first intention is feasible.

14. An intent negotiation apparatus characterized by comprising: The apparatus applied to a second device comprises a processor and a transceiver. wherein the transceiver is configured 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 in a case where implementation of a first intention is guaranteed; 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. wherein the transceiver is further configured to: receive the first request sent by the first device in a case where one or more of the following conditions is met: receive a first instruction, wherein the first instruction is used to instruct to send the first request to the second device; receive a second intention, the second intention conflicting with the first intention; network resource changes; wherein in a case where the first response indicates that the second device accepts the first request, the first response is further used to instruct the first device to acquire an updated first intention in the first response and guarantee implementation of the updated first intention; and in a case where the first response indicates that the second device does not accept the first request, the first response is further used to instruct the first device to continue to guarantee implementation of the first intention; wherein the transceiver is further configured to: send a second request to the first device, wherein the second request is used to request intention negotiation; receive a second response sent by the first device, wherein the second response is used to indicate whether the first intention is feasible.

15. A communication device comprising: The memory, the 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 intention negotiation method according to any one of claims 1 to 10.

16. A computer readable storage medium for storing a program, characterized in that, The program is executed by the processor to implement the steps in the intention negotiation method according to any one of claims 1 to 10.

17. A computer program product, characterised in that, The program comprises computer instructions, which are executed by the processor to implement the steps in the intention negotiation method according to any one of claims 1 to 10.

Images