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

Abstract

The present application relates to the technical field of communications. Disclosed are an intent negotiation method and apparatus, and a device, a readable storage medium and a program product, which aim to ensure the reliability and robustness of an intent-driven network. The method comprises: when the implementation of a first intent is ensured, a first device sending a first request to a second device, wherein the first request is used for requesting intent negotiation; and 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.

Description

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

[0001] Cross-reference to Related Applications

[0002] The present application is based on the Chinese patent application No. 202411377221.0, filed on September 30, 2024, and claims priority to the above Chinese patent application, the whole content of which is incorporated herein by reference. TECHNICAL FIELD

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

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

[0005] Among them, the intention-driven management service consumer provides the intention description to the intention-driven management service producer, and receives the 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 the intention, the expectations of the system are decoupled from the specific implementation details, leaving room for exploring alternative solutions and finding the best solution.

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

[0007] The 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.

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

[0009] In a case of guaranteeing implementation of the first intention, a first request is sent to the second device, wherein the first request is used for requesting intention negotiation;

[0010] A first response sent by the second device is received, wherein the first response is used for indicating whether the second device accepts the first request.

[0011] Embodiments of the present application further provide an intention negotiation method, applied to a second device, and the method comprises:

[0012] A first request sent by a first device is received, wherein the first request is used for requesting intention negotiation and is sent by the first device in a case of guaranteeing implementation of a first intention;

[0013] A first response is sent to the first device, wherein the first response is used for indicating whether the second device accepts the first request.

[0014] Embodiments of the present application further provide an intention negotiation device, applied to a first device, and the device comprises:

[0015] A first sending module is configured to send a first request to a second device in a case of guaranteeing implementation of a first intention, wherein the first request is used for requesting intention negotiation;

[0016] A first receiving module is configured to receive a first response sent by the second device, wherein the first response is used for indicating whether the second device accepts the first request.

[0017] Embodiments of the present application further provide an intention negotiation device, applied to a second device, and the device comprises:

[0018] A first receiving module is configured to receive a first request sent by a first device, wherein the first request is used for requesting intention negotiation and is sent by the first device in a case of guaranteeing implementation of a first intention;

[0019] A first sending module is configured to send a first response to the first device, wherein the first response is used for indicating whether the second device accepts the first request.

[0020] Embodiments of the present application further provide an intention negotiation device, applied to a first device, and the device comprises a processor and a transceiver;

[0021] The transceiver is configured to send a first request to a second device in a case of guaranteeing implementation of a first intention, wherein the first request is used for requesting intention negotiation; and receive a first response sent by the second device, wherein the first response is used for indicating whether the second device accepts the first request.

[0022] The embodiment of the present application further provides an intention negotiation device, applied to a second device, the device comprising a processor and a transceiver;

[0023] The transceiver is configured to receive a first request sent by a first device, wherein the first request is used for requesting 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, wherein the first response is used for indicating whether the second device accepts the first request.

[0024] The embodiment of the present application further provides a communication device, comprising a memory, a processor and a program stored in the memory and executable on the processor, wherein the processor implements the steps in the intention negotiation method as described above when executing the program.

[0025] The embodiment of the present application further provides a readable storage medium, wherein the readable storage medium stores a program, and the program is executed by a processor to implement the steps in the intention negotiation method as described above.

[0026] The 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 as described above.

[0027] In the embodiment of the present application, the first device can send a first request to the second device under the condition of guaranteeing implementation of a first intention to perform intention negotiation. By means of the scheme of the embodiment of the present application, a more fair and reasonable negotiation result can be obtained through the active intention negotiation of the first device in the implementation process of the first intention, so as to guarantee the reliability and robustness of the intention-driven network. BRIEF DESCRIPTION OF DRAWINGS

[0028] FIG. 1 is a flowchart of an intention negotiation method according to an embodiment of the present application;

[0029] FIG. 2 is a flowchart of an intention negotiation method according to another embodiment of the present application;

[0030] FIG. 3 is a flowchart of an intention negotiation method according to an embodiment of the present application;

[0031] FIG. 4 is a flowchart of an intention negotiation method according to another embodiment of the present application;

[0032] FIG. 5 is a structural diagram of an intention negotiation device according to an embodiment of the present application;

[0033] FIG. 6 is a structural diagram of an intention negotiation device according to another embodiment of the present application;

[0034] FIG. 7 is a structural diagram of an intention negotiation device according to another embodiment of the present application;

[0035] FIG. 8 is a fourth structural diagram of the intention negotiation apparatus provided in the embodiments of the present application. DETAILED DESCRIPTION

[0036] In the embodiments of the present application, the term "and / or" is used to describe an association relationship of associated objects, which means that there can be three relationships, for example, A and / or B can mean that 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.

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

[0038] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some 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 fall within the scope of protection of the present application.

[0039] Referring to FIG. 1, FIG. 1 is a flowchart of an intention negotiation method provided in the embodiments of the present application, applied to a first device. As shown in FIG. 1, the method includes the following steps:

[0040] Step 101: sending a first request to a second device under the condition of guaranteeing implementation of a first intention, wherein the first request is used to request intention negotiation.

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

[0042] The first device has an intention management function. In the embodiments, the first device has an intention management function, for example, can be an intention drive management service producer, or can also be called an intention handler. The second device has an intention management function, for example, can be an intention drive management service consumer, or can also be called an intention owner. The first device and the second device interact based on an intention management interface to perform centralized management operations including but not limited to the following: intention creation, intention deletion, intention update, intention negotiation, intention activation / deactivation, intention 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.

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

[0044] (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 a network management device or the like.

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

[0046] (3) network resources change.

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

[0048] 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.

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

[0050] An intention negotiation identifier;

[0051] A suggested modified intention expectation combination;

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

[0053] An expectation object of the intention expectation;

[0054] An expectation target of the intention expectation;

[0055] An expectation context of the intention expectation.

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

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

[0058] (1) According to the intention priority of each candidate intention, the candidate intentions are sorted to obtain a first sorting result. Each candidate intention has a corresponding intention priority. For example, the candidate intentions can be sorted according to the intention priority from high to low or from low to high, thereby obtaining the first sorting result. When intention negotiation is performed, the intention with a low priority can be negotiated first.

[0059] (2) According to the gap size 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, the candidate intentions are sorted to obtain a second sorting result. The first device can compare the resources reserved for 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, thereby obtaining the gap size. For example, the candidate intentions can be sorted according to the gap size from high to low or from low to high, thereby obtaining the second sorting result. When intention negotiation is performed, the intention with a large gap can be negotiated first.

[0060] (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 the resources of itself and the implementation of the intention, thereby determining the size of the influence. When intention negotiation is performed, the candidate intention with a smaller influence is negotiated first.

[0061] (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.

[0062] 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.

[0063] 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 low priority can be determined as the intention to be negotiated according to the first sorting result; one or more candidate intentions with a large gap can be determined as the intention to be negotiated according to the second sorting result; and one or more candidate intentions with a small influence can be determined as the intention to be negotiated according to the third sorting result.

[0064] For another example, if the intention to be negotiated is determined according to multiple sorting results, the candidate intentions 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.

[0065] 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.

[0066] In an embodiment, the first request further includes one or more of the following information:

[0067] 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;

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

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

[0070] The impact of the intention change;

[0071] The reason for the intention negotiation.

[0072] 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.

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

[0074] In actual applications, the first request can be sent in various ways. For example, an intention negotiation report can be introduced in an 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.

[0075] 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.

[0076] 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.

[0077] 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.

[0078] 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.

[0079] 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, for example, the second information can also carry a rejection reason and a conflict target. The rejection reason can be, for example, that current resources cannot meet implementation of the intention, and the conflict target can be, for example, bandwidth conflict.

[0080] 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, through active intention negotiation of the first device in the process of guaranteeing implementation of the first intention, timely adjustment can be performed in response to newly appeared information or changes, and a more fair and reasonable negotiation result can be obtained, so that reliability and robustness of the intention-driven network can be guaranteed.

[0081] The intention negotiation process described above is performed in the case of intention execution. In the embodiment 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.

[0082] 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.

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

[0084] Intention expectation combination;

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

[0086] Expected object of the intention expectation;

[0087] Expected target of the intention expectation;

[0088] Expected context of the intention expectation.

[0089] 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, delay, etc. The expected context of the intention expectation can be information related to the intention expectation, etc.

[0090] In an embodiment, the second request further includes one or more of the following:

[0091] Intention context, describing the constraints and conditions applied to the entire intention, which is a three-tuple combination of attribute, condition and value range;

[0092] the intent expectation desired target context, which describes a list of constraints and conditions applied to a specific desired target.

[0093] the intent expectation desired target context, which describes a list of constraints and conditions applied to a specific desired target.

[0094] Therefore, in combination with the intent negotiation in different stages, the initiative of the intent-driven management service producer in a 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 is allowed according to new information or changes in the intent guarantee process, 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.

[0095] Referring to FIG. 2, FIG. 2 is a flowchart of an intent negotiation method provided by an embodiment of the present application, applied to a second device. As shown in FIG. 2, the method includes the following steps:

[0096] In step 201, a first request sent by a first device is received, wherein the first request is used to request to perform intent negotiation, and is sent by the first device in a case of guaranteeing implementation of a first intent, the first device and the second device have an intent management function, for example, in this embodiment, the first device can be an intent-driven management service producer, and the second device can be an intent-driven management service consumer.

[0097] 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:

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

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

[0100] a network resource changes.

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

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

[0103] In step 202, a first response is sent to the first device, wherein the first response is used to indicate whether the second device accepts the first request.

[0104] The second device, after receiving the first request, can determine whether the first request can be accepted 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 intention to the first device through the first response.

[0105] In the embodiments of the present application, the first device can send the first request to the second device to perform intention negotiation while ensuring implementation of the first intention. Therefore, through the active intention negotiation of the first device in the process of ensuring the implementation of the first intention, timely adjustment can be made to the newly appeared information or changes, a more fair and reasonable negotiation result can be obtained, and thus the reliability and robustness of the intention-driven network can be ensured.

[0106] The intention negotiation process described above is performed while ensuring implementation of the intention. 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 new intention creation or changes through feasibility check, intention exploration and intention negotiation. The negotiation in this phase is initiated by the intention-driven management service consumer.

[0107] 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 intention negotiation, and the second response is used to indicate whether the first intention is feasible.

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

[0109] Therefore, in combination with intention negotiation in different phases, 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 of the intention-driven management service producer and the intention-driven management service consumer is supported, timely adjustment according to newly appeared information or changes is allowed in the intention guarantee process, the intention implementation can better meet the real expectations of the intention-driven management service consumer, 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.

[0110] Referring to FIG. 3, FIG. 3 is a flowchart of an intention negotiation method according to an embodiment of the present application. In the flowchart, two-phase intention negotiation is shown. The first phase of intention negotiation occurs in the intention creation, intention update, intention activation or intention restart phase, and through feasibility check, intention exploration and intention negotiation, potential conflicts caused by new intention creation or changes are avoided. The second phase of intention negotiation occurs in the intention execution or implementation phase, in which the intention-driven management service producer actively triggers the ability of intention change, improves the flexibility of the system, and ensures resource utilization.

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

[0112] The intention driven management service producer allows the intention driven management service consumer to manage service and network resources through intention expression. 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 intention of the intention driven management service consumer, verifies, translates and executes the intention, and then feeds back intention execution satisfaction information to the intention driven management service consumer.

[0113] The processing flow of intention can be roughly divided into five stages: detection, investigation, definition, distribution and implementation. In the detection stage, the intention driven management service consumer determines whether to define a new or change an existing intention by detecting demand satisfaction. 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 intention and related expectations by combining 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 ensure that the expectations corresponding to the intention object are met. In addition, the intention driven management service producer needs to report intention satisfaction, execution status and unmet reasons to the intention driven management service consumer.

[0114] In the flow of FIG. 3, the first device is the intention driven management service producer, and the second device is the intention driven management service consumer. Generally, the intention driven management service consumer sends an intention to the intention driven management service producer, and the intention driven management service producer feeds back an intention report to the intention driven management service consumer. They interact based on the agreed information model to ensure consistent understanding between the two parties.

[0115] The elements in the intention template include:

[0116] Intention expectation combination, intention expectation contained in intention expectation combination, expected object of intention expectation, expected target of intention expectation, expected context of intention expectation. In some embodiments, intention context, expected object context of intention expectation, expected target context of intention expectation, etc. information can also be included. Intention report includes: intention satisfaction report, intention feasibility check report, intention exploration report, etc. various forms, which respectively appear at different links of intention full life cycle.

[0117] As shown in FIG. 3, the intention negotiation process can specifically include:

[0118] I. First stage of intention negotiation:

[0119] Step 301, the second device sends an intention request (i.e. second request) to the first device for intention feasibility check exploration and negotiation.

[0120] Step 302, the first device performs evaluation verification according to the intention request.

[0121] Step 303, the first device sends a notification feedback (i.e. second response) to the second device, including intention check result, recommendation information and negotiation result.

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

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

[0124] Step 305, the first device performs intention and evaluation.

[0125] Step 306, the first device reports intention satisfaction information to the first device.

[0126] II. Second stage of intention negotiation:

[0127] Step 307, the first device sends an intention negotiation request (i.e. first request) to the second device, including negotiation reason, recommended expectation, impact of intention modification, etc.

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

[0129] Referring to FIG. 4, FIG. 4 is a flowchart of an intention negotiation method according to an embodiment of the present application. In this flowchart, the following processes can be included:

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

[0131] 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.

[0132] Step 402, when the intent-driven management service producer receives the first intent, it judges whether the intent is feasible, which has the following possibilities:

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

[0134] (2) The intent-driven management service producer judges that the first intent itself or the first intent and historical intents exist contradictions, such as conflicts between intents, expectations, and targets, and 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).

[0135] (3) The intent-driven management service producer judges 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.

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

[0137] 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 it to the intent-driven management service producer.

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

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

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

[0141] Step 408, if a network state change is monitored or a new intent request is received, the intent-driven management service producer initiatively triggers negotiation with the intent-driven management service consumer. Otherwise, step 406 can be continuously executed.

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

[0143] In the embodiments 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:

[0144] intent negotiation identifier, suggested modified intent expectation combination, intent expectation contained in the intent expectation combination, expected object of the intent expectation, expected target of the intent expectation, expected context of the intent expectation. In some embodiments, suggested modified intent context, expected object context of the intent expectation, expected target context of the intent expectation, impact of the intent change, and intent negotiation reason can also be included.

[0145] Step 409, the intent-driven management service consumer receives the negotiation information, can reject the change and return to step 406 (not shown in the figure); or, proposes adjustment suggestions, gets modified intent, and instructs the intent-driven management service producer to change the intent instance, and returns to step 406.

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

[0147] Assuming that the current intent-driven management service producer is guaranteeing the implementation of intent A of the intent-driven management service consumer 1, during which the intent-driven management service producer receives intent B (may come from the intent-driven management service consumer 1 or other intent-driven management service consumers), intent A and intent B need to guarantee respective video live streaming and game experience in the same period, and under the condition of insufficient available bandwidth resources, the two intents have a competitive relationship. In the traditional intent solution, intent A will be prioritized; when intent B applies for bandwidth resources, it will receive an intent report that the system resources do not meet in the intent detection stage, and then refuse to establish an intent object, which cannot achieve intent satisfaction, so that a dynamic guarantee and state balance based on intent-driven self-intelligent network cannot be achieved. In the embodiment of the present application, the intent-driven management service producer receives a new intent request, determines whether the new intent can be implemented, and the impact on the current management domain. Assuming that it is determined that there is a potential conflict with the running intent instance, the intent-driven management service producer monitors that the intent expectation set by the intent-driven management service consumer expects a higher target value than the actual demand, and can negotiate the intent-driven management service consumer 1 to adjust intent A.

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

[0149] The intent negotiation identifier: negotiation type;

[0150] The negotiation reason: to satisfy the hope of other intents to coordinate part of the resources;

[0151] The suggested modified intent expectation combination: reduce the expected bandwidth value to 300M; impact: keep the indicators such as delay unchanged.

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

[0153] If the intent-driven management service consumer accepts the negotiation, the intent-driven management service consumer updates the intent A and sends it to the intent-driven management service producer. The intent-driven management service producer updates the instance of the intent A and continues the implementation guarantee of the intent A. Meanwhile, the intent-driven management service producer judges that it is feasible, feeds back the feasibility check information to the intent-driven management service consumer to which the intent B belongs, and starts the intent new creation process.

[0154] If the intent-driven management service consumer does not accept the negotiation, the intent-driven management service consumer replies to the intent-driven management service producer with rejection information, and the intent-driven management service producer maintains the original implementation guarantee of the intent A. Meanwhile, the intent-driven management service producer judges that it is not feasible, feeds back the feasibility check information to the intent-driven management service consumer to which the intent B belongs, and indicates the rejection reason and the conflict target.

[0155] As can be seen from the above embodiments, in combination with the intent negotiation in different stages, the initiative of the intent-driven management service producer in the multi-intent satisfaction scenario can be guaranteed without affecting the global state of the network, the active negotiation between the intent-driven management service producer and the intent-driven management service consumer is supported, timely adjustment is allowed according to new information or changes in the intent guarantee process, the implementation of the intent can better meet the real expectations of the intent-driven management service consumer, and thus 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.

[0156] Referring to FIG. 5, FIG. 5 is a structural diagram of an intent negotiation apparatus provided by an embodiment of the present application, which is applied to a first device having an intent management function. As shown in FIG. 5, the intent negotiation apparatus includes:

[0157] A first sending module 501 configured to send a first request to a second device in a case of guaranteeing implementation of a first intent, wherein the first request is used to request to perform intent negotiation, and the second device has an intent management function; and a first receiving module 502 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.

[0158] In an embodiment, the first request includes one or more of the following information:

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

[0160] A suggested modified intent expectation combination;

[0161] An intent expectation included in the suggested modified intent expectation combination;

[0162] An expectation object of the intent expectation;

[0163] the expected target of the intention expectation;

[0164] the expected context of the intention expectation.

[0165] In an embodiment, the first request further comprises one or more of the following information:

[0166] the suggested modified intention context;

[0167] the expected object context of the intention expectation;

[0168] the expected target context of the intention expectation;

[0169] the impact of the intention change;

[0170] the reason of the intention negotiation.

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

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

[0173] 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;

[0174] 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;

[0175] 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.

[0176] In an embodiment, the apparatus further comprises:

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

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

[0179] In an embodiment, the first request is sent in the case that a second intention of the second device or a third device is received; the apparatus further comprises:

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

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

[0182] In an embodiment, the apparatus further includes:

[0183] 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;

[0184] The fourth sending module is configured to send a second response to the second device, wherein the second response is used to indicate whether the first intent is feasible.

[0185] In an embodiment, the second request includes one or more of the following:

[0186] an intent expectation combination;

[0187] an intent expectation included in the intent expectation combination;

[0188] an expectation object of the intent expectation;

[0189] an expectation target of the intent expectation;

[0190] an expectation context of the intent expectation.

[0191] In an embodiment, the second request further includes one or more of the following:

[0192] an intent context;

[0193] an expectation object context of the intent expectation;

[0194] an expectation target context of the intent expectation.

[0195] In an embodiment, the first sending module 501 is further configured to:

[0196] send the first request to the second device when one or more of the following conditions is met:

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

[0198] receive a second intent, which conflicts with the first intent;

[0199] The network resource changes.

[0200] The apparatus provided by the embodiments of the present application can execute the method embodiments, and the implementation principles and technical effects are similar, and the embodiments will not be described here.

[0201] Referring to FIG. 6, FIG. 6 is a structural diagram of an intention negotiation apparatus provided by an embodiment of the present application, which is applied to a second device having an intention management function. As shown in FIG. 6, the intention negotiation apparatus includes:

[0202] The first receiving module 601 is configured to receive a first request sent by a first device, wherein the first request is used for requesting to perform intention negotiation, and is sent by the first device in a case of guaranteeing implementation of a first intention; and the first sending module 602 is configured to send a first response to the first device, wherein the first response is used for indicating whether the second device accepts the first request.

[0203] In an embodiment, the apparatus further includes:

[0204] The second sending module is configured to send a second request to the first device, wherein the second request is used for requesting to perform intention negotiation.

[0205] The second receiving module is configured to receive a second response sent by the first device, wherein the second response is used for indicating whether the first intention is feasible.

[0206] In an embodiment, the second request includes one or more of the following:

[0207] An intention expectation combination;

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

[0209] An expectation object of the intention expectation;

[0210] An expectation target of the intention expectation;

[0211] An expectation context of the intention expectation.

[0212] In an embodiment, the second request further includes one or more of the following:

[0213] An intention context;

[0214] An expectation object context of the intention expectation

[0215] An expectation target context of the intention expectation.

[0216] In an embodiment, the first receiving module 601 is further configured to:

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

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

[0219] receive a second intention, wherein the second intention conflicts with the first intention;

[0220] the network resource changes.

[0221] The apparatus provided in the embodiments of the present application can execute the method embodiments described above, and has similar implementation principles and technical effects. Therefore, the apparatus will not be described here again.

[0222] Referring to FIG. 7, FIG. 7 is a structural diagram of an intention negotiation apparatus provided in the embodiments of the present application, which is applied to a first device having an intention management function. As shown in FIG. 7, the intention negotiation apparatus includes a processor 701 and a transceiver 702.

[0223] The transceiver 702 is configured to send a first request to a second device under the condition that a first intention is implemented, wherein the first request is used to request to negotiate the intention, and the second device has an intention management function; and receive a first response sent by the second device, wherein the first response is used to indicate whether the first request is accepted by the second device.

[0224] In an embodiment, the first request includes one or more of the following information:

[0225] an intention negotiation identifier, used to identify an intention to be negotiated;

[0226] a suggested modified intention expectation combination;

[0227] the intention expectation included in the suggested modified intention expectation combination;

[0228] a desired object of the intention expectation;

[0229] a desired target of the intention expectation;

[0230] a desired context of the intention expectation.

[0231] In an embodiment, the first request further includes one or more of the following information:

[0232] a suggested modified intention context;

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

[0234] the expected target context expected by the intention;

[0235] the impact after the intention is changed;

[0236] the reason for the intention negotiation.

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

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

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

[0240] The candidate intentions are sorted according to the influence sizes of the negotiation results of the intention negotiation with the candidate intentions on the network, to obtain a third sorting result;

[0241] 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.

[0242] In an embodiment, the processor 701 is configured to:

[0243] 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 acquired, and implementation of the updated first intention is guaranteed;

[0244] In a case where the first response indicates that the second device does not accept the first request, implementation of the first intention is continuously guaranteed.

[0245] In an embodiment, the first request is sent in a case where a second intention of the second device or a third device is received; the transceiver 702 is further configured to:

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

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

[0248] In an embodiment, the transceiver 702 is further configured to:

[0249] receiving a second request sent by the second device, wherein the second request is used to request intention negotiation;

[0250] sending a second response to the second device, wherein the second response is used to indicate whether the first intention is feasible.

[0251] In an embodiment, the second request comprises one or more of the following:

[0252] intention expectation combination;

[0253] intention expectation contained in the intention expectation combination;

[0254] expectation object of the intention expectation;

[0255] expectation target of the intention expectation;

[0256] expectation context of the intention expectation.

[0257] In an embodiment, the second request further comprises one or more of the following:

[0258] intention context;

[0259] expectation object context of the intention expectation;

[0260] expectation target context of the intention expectation.

[0261] In an embodiment, the transceiver 702 is further configured to:

[0262] sending the first request to the second device when one or more of the following conditions is met:

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

[0264] receiving a second intention, wherein the second intention conflicts with the first intention;

[0265] network resource changes.

[0266] The apparatus provided by the embodiments of the present application can execute the above-mentioned method embodiments, and the implementation principles and technical effects are similar, and the present embodiment will not be described here.

[0267] Referring to FIG. 8, FIG. 8 is a structure diagram of an intention negotiation apparatus provided by an embodiment of the present application, which is applied to a second device having an intention management function. As shown in FIG. 8, the intention negotiation apparatus comprises a processor 801 and a transceiver 802;

[0268] The transceiver 802 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 a first intention is implemented, and the first device has an intention management function; and send a first response to the first device, wherein the first response is used to indicate whether the second device accepts the first request.

[0269] In an embodiment, the transceiver 802 is further configured to:

[0270] send a second request to the first device, wherein the second request is used to request intention negotiation;

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

[0272] In an embodiment, the second request comprises one or more of the following:

[0273] an intention expectation combination;

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

[0275] an expectation object of the intention expectation;

[0276] an expectation target of the intention expectation;

[0277] an expectation context of the intention expectation.

[0278] In an embodiment, the second request further comprises one or more of the following:

[0279] an intention context;

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

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

[0282] In an embodiment, the transceiver 802 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:

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

[0284] receiving a second intention, wherein the second intention conflicts with the first intention;

[0285] a network resource changes.

[0286] The device provided by the embodiments of the present application can execute the method embodiments described above, and has similar implementation principles and technical effects. The embodiments will not be described here again.

[0287] It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division. In actual implementation, another division manner can be used. In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0288] When the integrated unit is realized in the form of a software functional unit and sold or used as an independent product, the integrated unit can be stored in a processor-readable storage medium. Based on this understanding, the technical solutions of the present application or all or part of the technical solutions that make contributions to the related art can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The foregoing storage medium includes a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0289] The embodiments of the present application provide 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 intention negotiation method described above.

[0290] The embodiments of the present application also provide a readable storage medium, and the readable storage medium stores a program. The program is executed by a processor to implement each process of the intention negotiation method embodiments described above, and can achieve the same technical effects. To avoid repetition, the embodiments will not be described here again. The readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to a magnetic memory (such as a floppy disk, a hard disk, a magnetic tape, a magneto-optical disk (MO), etc.), an optical memory (such as a CD, a DVD, a BD, a HVD, etc.), and a semiconductor memory (such as a ROM, an EPROM, an EEPROM, a non-volatile memory (NAND FLASH), a solid-state disk (SSD), etc.).

[0291] The embodiment of the present application further provides a computer program product, comprising computer instructions, which, when executed by a processor, implement each process of the above-mentioned intention negotiation method embodiment and can achieve the same technical effects. To avoid repetition, details are not described herein.

[0292] It should be noted that, in this document, the terms "comprising", "including", or any other variant thereof are intended to cover a non-exclusive inclusion, so that a process, method, article, or apparatus that comprises a list of elements does not only include those elements, but also includes other elements not expressly listed or inherent to such process, method, article, or apparatus. Without more limitations, an element defined by the statement "comprising a" does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0293] From the above description of the embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be realized by means of software and a general hardware platform as required, and of course can also be realized by hardware, but in many cases the former is a better embodiment. According to such understanding, the technical solutions of the present application or the part that contributes to the related art can be embodied in the form of a computer software product, which is stored in a storage medium (such as a ROM / RAM, a magnetic disk, an optical disk), and includes a plurality of instructions for making a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in each embodiment of the present application.

[0294] The embodiments of the present application are described above in combination with the drawings, but the present application is not limited to the above-mentioned specific embodiments, and the above-mentioned specific embodiments are only illustrative and not restrictive. Those skilled in the art can make many forms under the inspiration of the present application without departing from the scope of the present application and the scope of protection of the claims.

Claims

1. A method for intent negotiation, applied to a first device, the method comprising: sending a first request to a second device in a case where implementation of a first intent is ensured, wherein the first request is used to request to perform intent negotiation; 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.

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

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

4. The method of claim 2, wherein, The intent to be negotiated is determined in the following manner: sorting each candidate intent according to an intent priority of each candidate intent to obtain a first sorting result; sorting each candidate intent according to a gap size between resources reserved for an expectation target of an intent expectation of each candidate intent and actual intent consumption resources of each candidate intent to obtain a second sorting result; sorting each candidate intent according to an impact size on a network caused by a negotiation result of each candidate intent to obtain a third sorting result; determining the intent to be negotiated from the candidate intents 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 method further comprises: in a case where the first response indicates that the second device accepts the first request, obtaining an updated first intent in the first response and ensuring implementation of the updated first intent; 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 intent.

6. The method of claim 1, wherein, The first request is sent to the second device when one or more of the following conditions are met: receiving a first instruction, wherein the first instruction is used to instruct to send the first request to the second device; receiving a second intent, wherein the second intent conflicts with the first intent; network resources change.

7. The method of claim 6, wherein, 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: 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; 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.

8. The method of claim 1, wherein, The method further comprises: receiving a second request sent by the second device, wherein the second request is used to request to perform intent negotiation; sending a second response to the second device, wherein the second response is used to indicate whether the first intention is feasible.

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

10. The method of claim 9, wherein, The second request further comprises one or more of: an intention context; an expectation object context of the intention expectation; an expectation target context of the intention expectation. 11.An intention negotiation method applied to a second device, the method comprising: receiving a first request sent by a first device, wherein the first request is used to request to conduct intention negotiation and is sent by the first device under the condition of guaranteeing implementation of a first intention; sending a first response to the first device, wherein the first response is used to indicate whether the second device accepts the first request.

12. The method of claim 11, wherein, The method further comprises: sending a second request to the first device, wherein the second request is used to request to conduct intention negotiation; receiving a second response sent by the first device, wherein the second response is used to indicate whether the first intention is feasible.

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

14. The method of claim 13, wherein, The second request further comprises one or more of: an intention context; an expectation object context of the intention expectation; an expectation target context of the intention expectation.

15. The method of claim 13, wherein, The receiving of the first request sent by the first device comprises: receiving the first request sent by the first device under the condition of satisfying one or more of: receiving a first instruction, wherein the first instruction is used to instruct to send the first request to the second device; receiving a second intention, wherein the second intention conflicts with the first intention; a change in network resources. 16.An intention negotiation apparatus applied to a first device, the apparatus comprising: a first sending module configured to send a first request to a second device under the condition of guaranteeing implementation of a first intention, wherein the first request is used to request to conduct intention negotiation; a first receiving module 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. 17.An intention negotiation apparatus applied to a second device, the apparatus comprising: a first receiving module configured to receive a first request sent by a first device, wherein the first request is used to request to conduct intention negotiation and is sent by the first device under the condition of guaranteeing implementation of a first intention; 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.

18. An intent negotiation apparatus applied to a first device, the apparatus comprising: a processor and a transceiver; The transceiver is configured to send a first request to the second device in a case where implementation of the first intention is guaranteed, where the first request is used to request intention negotiation; and 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.

19. An intent negotiation apparatus applied to a second device, the apparatus comprising: a processor and a transceiver; The transceiver is configured to receive a first request sent by a first device, where 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, where the first response is used to indicate whether the second device accepts the first request.

20. A communication device comprising: a memory, a processor, and a program stored in the memory and executable on the processor; 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 15. 21.A computer readable storage medium, having a program stored thereon, which, when executed by a processor, implements the steps in the intention negotiation method according to any one of claims 1 to 15. 22.A computer program product, comprising computer instructions, which, when executed by a processor, implement the steps in the intention negotiation method according to any one of claims 1 to 15.

Images