Processing device, request device, and communication method

Abstract

This processing device comprises: a control unit that, if a conflict related to an intent in intent-driven management services is detected, derives a plurality of solutions for resolving the conflict; and a transmission unit that transmits, to a request device, a message requesting a determination about the plurality of solutions.

Description

Processing device, requesting device, and communication method

[0001] The present invention relates to intent-driven management services in mobile networks.

[0002] 3GPP (registered trademark) (3rd Generation Partnership Project) has introduced a wireless communication system called 5G or NR (New Radio) (hereinafter, the wireless communication system will be referred to as "5G" or "NR") in order to achieve a larger system capacity, a higher data transmission speed, and a lower latency in wireless sections. 5G introduces various wireless technologies to meet the requirement of achieving a throughput of 10 Gbps or more while reducing latency in wireless sections to 1 ms or less. Furthermore, 6G, a future communication system, is also being studied.

[0003] Furthermore, 3GPP (registered trademark) is studying intent-driven management services for mobile networks (see, for example, Non-Patent Documents 1 and 2). Intent-driven management refers to autonomous operation of a mobile network in accordance with an intent.

[0004] 3GPP TS 28.312 V18.1.1 (2023-09)3GPP TR 28.912 V18.0.1 (2023-06)

[0005] Intent-driven management services are expected to encounter conflicts regarding intent (Non-Patent Documents 1 and 2).

[0006] However, in the conventional technology, when there are multiple solutions for resolving a conflict, it is not possible to appropriately determine which of the multiple solutions to use.

[0007] The present invention has been made in consideration of the above points, and aims to provide a technology that enables appropriate determination of which of multiple solutions to use when there are multiple solutions to resolve a conflict in an intent-driven management service in a mobile network.

[0008] According to the disclosed technology, a processing device is provided that includes: a control unit that, when a conflict related to an intent in an intent-driven management service is detected, derives multiple solutions to resolve the conflict; and a transmission unit that transmits a message to a requesting device requesting a decision on the multiple solutions.

[0009] The disclosed technology provides a technology that enables appropriate determination of which of multiple solutions to use when there are multiple solutions to resolve a conflict in an intent-driven management service in a mobile network.

[0010] FIG. 1 is a diagram for explaining an example of a communication system. FIG. 2 is a diagram for explaining an example of a communication system in a roaming environment. FIG. 3 is a diagram for explaining an example of a system configuration of an OSS architecture. FIG. 4 is a diagram for explaining an intent generation procedure. FIG. 5 is a diagram for explaining an intent generation procedure. FIG. 6 is a diagram for explaining an example of a procedure when a conflict occurs. FIG. 7 is a diagram for explaining an example of a conflict resolution procedure. FIG. 8 is a diagram for explaining a first embodiment. FIG. 9 is a diagram for explaining a second embodiment. FIG. 10 is a diagram for explaining an example of the functional configuration of a processing device 10 in an embodiment of the present invention. FIG. 11 is a diagram for explaining an example of the functional configuration of a requesting device 20 in an embodiment of the present invention. FIG. 12 is a diagram for explaining an example of the hardware configuration of a processing device 10 and a requesting device 20 in an embodiment of the present invention. FIG. 13 is a diagram for explaining an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0012] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies are used as appropriate. However, the existing technologies include, but are not limited to, the existing LTE or the existing NR.

[0013] In the following, we will first explain an example of the configuration of a mobile network, which is an example of a target to which the intent-driven management service is applied, and then explain the configuration and operation related to the intent-driven management service.

[0014] Fig. 1 is a diagram illustrating an example of a communication system corresponding to a mobile network. As shown in Fig. 1, this communication system is composed of a UE and multiple network nodes. Hereinafter, it is assumed that one network node corresponds to each function, but multiple functions may be realized by one network node, or multiple network nodes may realize one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0015] A Radio Access Network (RAN) is a network node having a radio access function, which may include a base station, and is connected to a UE, an Access and Mobility Management Function (AMF), and a User plane function (UPF). The AMF is a network node having functions such as terminating the RAN interface, terminating the Non-Access Stratum (NAS), registration management, connection management, reachability management, and mobility management. The UPF is a network node having functions such as a Protocol Data Unit (PDU) session point to the outside that interconnects with a Data Network (DN), packet routing and forwarding, and user plane Quality of Service (QoS) handling. The UPF and the DN constitute a network slice.

[0016] The AMF is connected to the UE, RAN, SMF (Session Management function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), UDM (Unified Data Management), AUSF (Authentication Server Function), PCF (Policy Control Function), and AF (Application Function). The AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes interconnected via interfaces based on their respective services: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0017] The SMF is a network node that has functions such as session management, UE IP (Internet Protocol) address allocation and management, DHCP (Dynamic Host Configuration Protocol) function, ARP (Address Resolution Protocol) proxy, and roaming function. The NEF is a network node that has the function of notifying other NFs (Network Functions) of capabilities and events. The NSSF is a network node that has functions such as selecting a network slice to which a UE connects, determining the allowed NSSAI (Network Slice Selection Assistance Information), determining the NSSAI to be configured, and determining the AMF set to which the UE connects. The PCF is a network node that has the function of controlling network policies. The AF is a network node that has the function of controlling application servers. The NRF is a network node that has the function of discovering NF instances that provide services. The UDM is a network node that manages subscriber data and authentication data. The UDM is connected to a UDR (User Data Repository) that stores the data.

[0018] 2 is a diagram illustrating an example of a communication system in a roaming environment. As shown in FIG. 2, the network is made up of a UE and a plurality of network nodes.

[0019] The SEPP is a non-transparent proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). The vSEPP shown in Figure 2 is a SEPP in a visited network, and the hSEPP is a SEPP in a home network.

[0020] As shown in Figure 2, a UE is in a roaming environment connected to a RAN and an AMF in a Visited PLMN (VPLMN). The VPLMN and a Home PLMN (HPLMN) are connected via a vSEPP and an hSEPP. The UE can communicate with a UDM in the HPLMN via the AMF in the VPLMN, for example.

[0021] (Intent-driven management services) As mentioned above, 3GPP (registered trademark) is studying intent-driven management services for mobile networks (for example, Non-Patent Documents 1 and 2). Intent-driven management refers to autonomous operation of a mobile network in accordance with an intent.

[0022] As described in Non-Patent Document 1, an intent indicates expectations, including requirements, goals, and constraints, for a specific service, etc. Furthermore, an intent places more emphasis on "what" needs to be achieved than on "how" to achieve the result. "Intent" may also be rephrased as "intention" or "request."

[0023] As described in Non-Patent Document 1, in an intent-driven management service (Intent-driven MnS), an MnS Consumer presents an intent to an MnS Producer, and the MnS Producer interprets the intent and executes an action. Note that MnS is an abbreviation for "management service."

[0024] Hereinafter, an entity corresponding to an MnS Consumer will be referred to as a requesting device, and an entity corresponding to an MnS Producer will be referred to as a processing device. The requesting device may also be referred to as an Intent requesting device, and the processing device may also be referred to as an Intent processing device.

[0025] Both the requesting device and the processing device may be a single device (such as a terminal, a base station, a server, or a network node) or a system consisting of multiple devices. Furthermore, both the requesting device and the processing device may be devices located anywhere on the network.

[0026] A system to which a requesting device and a processing device are applied may have a system configuration of an OSS architecture as shown in Fig. 3. In the configuration of Fig. 3, for example, the BSS or an orchestrator in the OSS may include the function of the requesting device. Also, in the configuration of Fig. 3, for example, the orchestrator of each MD (Management Domain) may include the function of the processing device.

[0027] Alternatively, the BSS may include the functionality of a requesting device, and the orchestrator of the OSS may include the functionality of a processing device.

[0028] (Example of Use Case) As an example, a use case relating to an intent containing an expectation on radio network performance to be assured will be described. This use case is also applicable to the first and second embodiments described below.

[0029] In this case, the requesting device submits an intent to the processing device, including expectations for ensuring performance (e.g., throughput) of the wireless network. The information in the submitted intent may include, for example, area information, RAT information, performance targets, etc.

[0030] A processing device that receives intent information including expectations for ensuring wireless network performance collects data on the relevant wireless network based on the intent information, identifies problems with wireless network performance (e.g., low throughput in a certain area), determines configuration parameters to improve the performance, and adjusts the configuration parameters.

[0031] The processing device continuously monitors the performance of the wireless network to determine whether performance goals for the wireless network are being met, and notifies the requesting device of intent fulfillment information indicating whether the intent has been fulfilled.

[0032] (Intent Creation Procedure (Create an intent)) When performing processing based on an intent, the requesting device requests the processing device to create an intent instance, and the processing device creates the intent instance and performs processing to achieve the intent based on the request.

[0033] 4, an outline of an intent generation procedure performed by the requesting device 20 and the processing device 10 will be described. In S1, the requesting device 20 requests the processing device 10 to generate an intent instance. This request includes information indicating what is desired to be achieved (the above-mentioned expectation).

[0034] In S2, the processing device 10 interprets the request received in S1 and generates an intent instance. When the generation is complete, the processing device 10 returns a response to the requesting device 20 in S3.

[0035] In S4, the processing device 10 executes processing to achieve the intent requested by the requesting device 20, and in S5, transmits a report indicating the processing results to the requesting device 20.

[0036] Fig. 5 is a diagram showing the intent generation procedure in more detail. Fig. 5 is "Figure 6.3.2-1: Procedure for creating an intent" in Non-Patent Document 1. In Fig. 5, the MnS Consumer corresponds to the requesting device 20, and the MnS Producer corresponds to the processing device 10.

[0037] A Managed Entity is an object managed by an MnS Producer. For example, in the wireless network performance example mentioned above, the Managed Entity is the wireless network (or the operation system of the wireless network). A detailed explanation of the procedure is as described in Non-Patent Document 1, so an outline will be given here.

[0038] 5 corresponds to S1 in FIG. 4, 2 corresponds to S2, 3 corresponds to S3, 4 to 7 correspond to S4, and 8 corresponds to S5.

[0039] In step S1, the MnS Consumer requests the MnS Producer to generate an intent instance by sending intent information, and in step S2, the MnS Producer generates an intent MOI (managed object instance) and sets the received intent information in the intent MOI. In step S3, the MnS Producer returns a response to the MnS Consumer.

[0040] In S4, the MnS Producer checks the feasibility of the intent instance. If it is feasible, steps 5a to 8 are performed.

[0041] In 5a, the MnS Producer identifies the MOI of the managed entities, derives executable management tasks (deployment, setting parameters, etc.) for the managed entities, and deploys or sets parameters for the managed entities to satisfy the intent instance.

[0042] In step 6, the MnS Producer continuously monitors the intent fulfillment information while the intent is being executed. In step 7, the MnS Producer analyzes and adjusts the managed entities so that the intent is continuously satisfied. In step 8, the MnS Producer notifies the MnS Consumer of the intent fulfillment information.

[0043] If the implementation check in 4. determines that the request is not implementable, the MnS Producer notifies the MnS Consumer of the impossibility of implementation in 5b. The notification may include the reason for the impossibility (e.g., intent conflict).

[0044] (Regarding Conflicts) As described above, a conflict may occur between multiple intents. For example, suppose that intent #1 is an intent to achieve power saving and intent #2 is an intent to achieve a high communication speed. Since a high communication speed often requires a large amount of power, a conflict may occur between these two intents.

[0045] An example of the procedure when a conflict occurs is shown in Fig. 6. In the example of Fig. 6, there are requesting devices 20-1 and 20-2.

[0046] In S11, the requesting device 20-1 requests the generation of an instance of Intent #1 by transmitting information of Intent #1 to the processing device 10. The processing device 10 generates an instance of Intent #1 in S12 and returns a response in S13.

[0047] In S14, the requesting device 20-2 requests the generation of an instance of Intent #2 by transmitting information about Intent #2 to the processing device 10. The processing device 10 generates an instance of Intent #2 in S15 and returns a response in S16.

[0048] In S17, the processing device 10 detects a conflict between Intent #1 and Intent #2 while executing the processes for achieving Intent #1 and Intent #2. For example, the processing device 10 detects that the power saving goal of Intent #1 and the communication speed increase goal of Intent #2 cannot be achieved simultaneously.

[0049] In S18 and S19, the processing device 10 transmits a report including the intent conflict information to each of the requesting devices 20-1 and 20-2.

[0050] (About the Judge Operation in Intent) Services using Intent are also being studied by organizations other than 3GPP. For example, TMF IG1253 and TMF921A define various operations for Intent, one of which is "Judge." In addition, an operation called Preference is performed in response to Judge.

[0051] (Regarding the Problem) Non-Patent Document 1 discloses a procedure for resolving an intent conflict when a conflict occurs between intents (Intent Conflict Resolution). A sequence based on this procedure is shown in FIG.

[0052] In S21, Intent #1 and Intent #2 are generated. In S22, the processing device 10 detects a conflict between the intents. In S23, the processing device 10 determines a solution (a method of dealing with) for the conflict. The solution to the conflict may be, for example, deleting either Intent #1 or Intent #2, or modifying either or both of Intent #1 and Intent #2.

[0053] In S24 and S25, the processing device 10 transmits an Intent Report to each of the requesting device 20-1 and the requesting device 20-2. The Intent Report includes a solution to the conflict. Transmission of the Intent Report means that the processing device 10 is requesting the requesting device 20 to confirm whether the solution is acceptable.

[0054] In S26-S27, each requesting device 20 returns a response indicating whether or not it accepts the solution to the processing device 10. If the solution is accepted, the determined solution is implemented in S28.

[0055] In the above procedure, the processing device 10 determines a solution. However, there is a possibility that the processing device 10 cannot determine (judge) a solution. For example, after determining which of two conflicting intents to address, the processing device 10 may not be able to determine whether deletion or modification is the appropriate process for that intent.

[0056] However, the conventional procedure as shown in FIG. 7 cannot deal with a situation in which the processing device 10 cannot determine a solution.

[0057] The following describes a technique according to the present embodiment for solving the above problems.

[0058] (Outline of the embodiment) In this embodiment, when the processing device 10 detects that a conflict has occurred and derives multiple solutions, but is unable to determine a solution, it uses the judge operation described above to ask the requesting device 20 to decide which solution to use.

[0059] That is, when the processing device 10 cannot determine by itself which of a plurality of solutions is best, it uses a judge message to ask the requesting device 20 for a judgment. Furthermore, upon receiving the judge message, the requesting device 20 transmits to the processing device 10 a preference message including information indicating, for example, a desired solution.

[0060] In this embodiment, the names "judge" and "preference" used in TMF are used, but these are examples. A message (or operation) that requests a decision from the requesting device 20 may be called by a name other than "judge." Also, a message (or operation) that conveys a desire (taste) from the requesting device 20 may be called by a name other than "preference."

[0061] A first embodiment and a second embodiment, which are examples of specific processing procedures, will be described below. The first embodiment is an embodiment in which a conflict occurs between intents, and the second embodiment is an embodiment in which a conflict occurs within an intent.

[0062] First Embodiment First, a first embodiment will be described. Fig. 8 is a sequence diagram showing a processing procedure in the first embodiment. The processing procedure in the first embodiment will be described with reference to Fig. 8.

[0063] <S101> In S101, Intent #1 is generated based on a request from requesting device 20-1, and Intent #2 is generated based on a request from requesting device 20-2.

[0064] <S102> In S102, the processing device 10 detects a conflict between the intents. The processing device 10 may detect the conflict based on the content of Intent #1 and the content of Intent #2 (Case 1), or may detect the conflict while executing Intent #1 and Intent #2 (Case 2).

[0065] In Case 1, for example, if the content of Intent #1 (specifically, for example, the expectation target) is "communication speed > threshold A" and the content of Intent #2 is "communication speed < threshold A" (for power saving), the processing device 10 can detect a conflict from the content of the intent alone.

[0066] In Case 2, for example, assume that the content of Intent #1 is "communication speed > threshold A" and the content of Intent #2 is "server CPU usage rate < threshold B." In this case, while executing Intent # and Intent #2, the processing device 10 detects that "communication speed > threshold A" and "server CPU usage rate < threshold B" cannot be satisfied, and determines that a conflict has occurred.

[0067] <S103> In S103, the processing device 10 first determines an intent to be dealt with in order to resolve the conflict. In this example, it is assumed that Intent #1 is determined as the intent to be dealt with. Furthermore, in S103, the processing device 10 derives a solution (a method of dealing with) for Intent #1. Here, it is assumed that multiple solutions are derived.

[0068] The method by which the processing device 10 derives a solution is not limited to a specific method. For example, the processing device 10 may derive a solution based on a predetermined rule.

[0069] Note that, in order to resolve a conflict, the target of the action to be taken is one example, as in this example. In order to resolve a conflict, the action to be taken may be taken for multiple conflicting intents.

[0070] It is assumed that the processing device 10 cannot determine which of the multiple solutions derived in S102 to use. In this example, the multiple solutions are deleting Intent #1 and modifying Intent #1.

[0071] The modification of Intent #1 may include multiple types of modifications. For example, if there are three types of modifications, Modification 1, Modification 2, and Modification 3, the multiple solutions for Intent #1 are "Delete, Modification 1, Modification 2, and Modification 3."

[0072] <S104> In S104, the processing device 10 requests the request device 20-1 to judge which solution is better by transmitting a judgement message to the request device 20-1.

[0073] The judge message includes an intent report, which may include, for example, information indicating that "intent #1 and intent #2 are in conflict, and possible solutions include deleting intent #1 and modifying intent #1."

[0074] In addition to the above information, the intent report may also include "results when intent #1 is deleted (e.g., achieved communication quality, etc.) and results when intent #1 is modified (e.g., achieved communication quality, etc.)." Here, if there are modifications 1, 2, and 3, the above information includes the results for each modification.

[0075] <S105> Upon receiving the judge message, the requesting device 20-1 judges the preference (or wish) of the requesting device 20-1 for the multiple solutions, and transmits a preference message including information indicating the preference to the processing device 10.

[0076] The information indicating the preference for the solution may be, for example, a selected solution (e.g., deleting Intent #1) or a priority of multiple solutions, such as Fix 1 being the highest priority, Fix 2 being the second highest priority, Fix 3 being the third highest priority, and Delete being used as little as possible.

[0077] <S106> The processing device 10 that has received the preference message determines one solution from among the multiple solutions based on the "preference information" included in the preference message. For example, if the requesting device 20-1 specifies one solution in the preference message, the processing device 10 determines that solution as the solution to be used.

[0078] Also, for example, if the requesting device 20-1 specifies the priorities of a plurality of solutions, the processing device 10 determines the solution with the highest priority as the solution to be used.

[0079] Note that there may be cases where one solution is not determined in S106. In such cases, one solution may be determined in S107 and S108 based on information indicating preferences.

[0080] <S107> In S107, the processing device 10 transmits an MOICreation message to the requesting device 20-1. This message includes, for example, information indicating the solution determined in S106 (e.g., deleting Intent #1 or modifying Intent #1).

[0081] <S108> In S108, the requesting device 20-1 returns a response message to the message received in S107 to the processing device 10. This response message includes, for example, information indicating that the solution received in S107 is accepted.

[0082] <S109> In S109, the requesting device 20-1 and the processing device 10 execute a conflict resolution process in accordance with the resolution determined based on the preference information (ie, preferences).

[0083] For example, if the solution is to delete Intent #1, the processing device 10 deletes Intent #1 and notifies the requesting device 20-1 that Intent #1 has been deleted.

[0084] Also, if the solution is to modify Intent #1, the processing device 10 modifies Intent #1 and notifies the requesting device 20-1 that Intent #1 has been modified.

[0085] First Embodiment: Examples of Modifications As examples of modifying an intent to resolve a conflict, the following modification examples 1 and 2 will be described.

[0086] <Modification Example 1: Use of an Alternative Target> An alternative target is a target that substitutes for the target of an Intent. For example, if the target of Intent #1 is "communication speed > threshold A," and threshold A is set to be greater than threshold B, the alternative target is, for example, "communication speed > threshold B."

[0087] For example, if the conflict resolution solution for Intent #1 is to change the goal in Intent #1 from "communication speed > threshold A" to "communication speed > threshold B," and the processing device 10 decides to implement this solution, the processing device 10 will perform parameter settings, etc., for the target wireless network according to "communication speed > threshold B."

[0088] <Modification Example 2: Changing the Recommended Context> For example, assume that Intent #1 is "Keep the Radio Link Failure rate (RLF) below 2% even when the Load is 80% or more." Here, "Load ≧ 80%" is an example of a context. In this example, the recommended context as a solution is, for example, "Load ≧ 50%."

[0089] In the above example, if it is decided that the conflict resolution method is to change the context in Intent #1 from "Load ≧ 80%" to "Load ≧ 50%", the processing device 10 performs parameter settings etc. corresponding to "Load ≧ 50%" on the target wireless network.

[0090] The technology according to the first embodiment described above makes it possible to appropriately determine which of the multiple solutions to use when there are multiple solutions for resolving a conflict in an intent-driven management service in a mobile network.

[0091] Second Embodiment Next, a second embodiment will be described. Fig. 9 is a sequence diagram showing a processing procedure in the second embodiment. The processing procedure in the second embodiment will be described with reference to Fig. 9.

[0092] <S201> In S201, an intent #1 is generated based on a request from the requesting device 20.

[0093] <S202> In S202, the processing device 10 detects a conflict within Intent #1. For example, if Intent #1 has goals of "Throughput > Threshold 1" (Goal 1) and "Interference < Threshold 2" (Goal 2), the processing device 10 detects that both "Throughput > Threshold 1" and "Interference < Threshold 2" cannot be satisfied.

[0094] <S203> In S203, the processing device 10 derives a method of dealing with (solution to) the conflict.

[0095] For example, the processing device 10 derives multiple solutions, such as deleting either "Throughput > Threshold 1" or "Interference < Threshold 2", and modifying either or both of "Throughput > Threshold 1" and "Interference < Threshold 2".

[0096] For example, the above-mentioned "alternate goal" can be used as the above correction. Specifically, if the alternative goal is to change Threshold 1 of Goal 1 to Threshold 3 (< Threshold 1), the solution is to change Intent #1 to ("Throughput > Threshold 3" (Goal 1) and "Interference < Threshold 2" (Goal 2)).

[0097] The method by which the processing device 10 derives a solution is not limited to a specific method. For example, the processing device 10 may derive a solution based on a predetermined rule.

[0098] It is assumed that the processing device 10 cannot determine which of the multiple solutions derived in S203 to use. In this example, it is assumed that the multiple solutions are deleting Goal 2 from Intent #1 and modifying Intent #1.

[0099] The modification of Intent #1 may include multiple types of modifications. For example, if there are three types of modifications, Modification 1, Modification 2, and Modification 3, the multiple solutions for Intent #1 are "Delete, Modification 1, Modification 2, and Modification 3."

[0100] <S204> In S204, the processing device 10 transmits a judge message to the requesting device 20, thereby requesting the requesting device 20 to judge which solution is better.

[0101] The judge message includes an intent report, which may include information indicating, for example, that "a conflict has occurred within Intent #1, and potential solutions include deleting Goal 2 from Intent #1 and modifying Intent #1."

[0102] In addition to the above information, the intent report may also include "the result when Goal 2 in Intent #1 is deleted (e.g., the communication quality achieved, etc.) and the result when Intent #1 is modified (e.g., the communication quality achieved, etc.)." Here, if there are Modifications 1, 2, and 3 as modifications, the above information includes the results for each modification.

[0103] <S205> The requesting device 20 that has received the judge message transmits to the processing device 10 a preference message that includes information indicating the requesting device 20's preference (or wish) for the solution.

[0104] The information indicating the preference for the solution may be, for example, a selected solution (e.g., deleting Goal 2 in Intent #1) or the priority of multiple solutions, such as information indicating that deleting Goal 2 is the highest priority, followed by modifying it.

[0105] <S206> The processing device 10 that has received the preference message determines one solution from among the multiple solutions based on the "preference information" included in the preference message. For example, if the requesting device 20 specifies one solution in the preference message, the processing device 10 determines that solution as the solution to be used.

[0106] Furthermore, for example, if the requesting device 20 specifies the priorities of a plurality of solutions, the processing device 10 determines the solution with the highest priority as the solution to be used.

[0107] Note that there may be cases where one solution is not determined in S206. In such cases, one solution may be determined in S207 and S208 based on information indicating preferences.

[0108] <S207> In S207, the processing device 10 transmits an MOICreation message to the requesting device 20. This message includes, for example, information indicating the solution determined in S206 (e.g., deleting Goal 2 from Intent #1, or modifying Intent #1).

[0109] <S208> In S208, the requesting device 20 returns a response message to the message received in S207 to the processing device 10. This response message includes, for example, information indicating that the solution received in S207 is accepted.

[0110] <S209> In S209, the requesting device 20 and the processing device 10 execute a conflict resolution process according to the resolution determined based on the preference information (i.e., preferences).

[0111] For example, if the solution is to delete Goal 2 in Intent #1, the processing device 10 deletes Goal 2 in Intent #1 and notifies the requesting device 20 that Goal 2 has been deleted.

[0112] Alternatively, if the solution is to modify Intent #1, the processing device 10 modifies Intent #1 and notifies the requesting device 20 that Intent #1 has been modified.

[0113] The technology according to the second embodiment described above makes it possible to appropriately determine which of the multiple solutions to use when there are multiple solutions to resolve a conflict in an intent-driven management service in a mobile network.

[0114] (Device Configuration) Next, an example of the functional configuration of the processing device 10 and the requesting device 20 that perform the processes and operations described above will be described.

[0115] <Processing device 10> Fig. 10 is a diagram showing an example of the functional configuration of the processing device 10. As shown in Fig. 10, the processing device 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 10 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations related to the embodiment of the present invention.

[0116] The transmitter 110 has a function of generating a signal to be transmitted to another device and transmitting the signal via a wired or wireless connection. The receiver 120 has a function of receiving various signals transmitted from other devices and acquiring, for example, information of a higher layer from the received signal. A communication unit including the transmitter 110 and the receiver 120 may be configured.

[0117] The setting unit 130 stores preset setting information and various setting information to be transmitted to other devices in a storage device, and reads the information from the storage device as needed. The content of the setting information is, for example, information for configuring settings for managed objects (wireless networks, etc.).

[0118] The control unit 140 controls the processing device 10. The control unit 140 also manages, for example, information indicating solutions for resolving conflicts. The control unit 140 also derives solutions to detected conflicts based on the information, for example. Managing the information indicating solutions means storing the information indicating solutions in a storage device such as a memory, and adding, deleting, or modifying the information indicating solutions in response to external instructions, etc. A functional unit in the control unit 140 related to signal transmission may be included in the transmitting unit 110, and a functional unit in the control unit 140 related to signal reception may be included in the receiving unit 120.

[0119] <Requesting Device 20> Fig. 11 is a diagram showing an example of the functional configuration of the requesting device 20. As shown in Fig. 11, the requesting device 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 11 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations related to the embodiment of the present invention.

[0120] The transmitter 210 has a function of generating a signal to be transmitted to another device and transmitting the signal via a wired or wireless connection. The receiver 220 has a function of receiving various signals transmitted from other devices and acquiring, for example, information of a higher layer from the received signals. A communication unit including the transmitter 210 and the receiver 220 may be configured.

[0121] The setting unit 230 stores preset setting information and various setting information to be transmitted to other devices in a storage device, and reads out the information from the storage device as needed.

[0122] The control unit 240 controls the requesting device 20. The control unit 240 can also determine a preference for a solution among multiple solutions for resolving a conflict. The signal transmission-related functional unit of the control unit 240 may be included in the transmitting unit 210, and the signal reception-related functional unit of the control unit 240 may be included in the receiving unit 120.

[0123] (Hardware Configuration) The block diagrams (FIGS. 10 and 11) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.

[0124] Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0125] For example, the processing device 10 and the request device 20 according to an embodiment of the present disclosure may function as a computer that performs processing of the communication method of the present disclosure. Fig. 12 is a diagram illustrating an example of the hardware configuration of the processing device 10 and the request device 20 according to an embodiment of the present disclosure. The processing device 10 and the request device 20 described above may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0126] In the following description, the term "device" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the processing device 10 and the requesting device 20 may be configured to include one or more of the devices shown in the figure, or may be configured to exclude some of the devices.

[0127] Each function of the processing device 10 and the requesting device 20 is realized by loading specified software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication via the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0128] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0129] The processor 1001 also loads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002 and executes various processes in accordance with the programs. The programs used may be programs that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the processing device 10 shown in FIG. 10 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. For example, the control unit 240 of the requesting device 20 shown in FIG. 11 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by a single processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

[0130] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

[0131] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0132] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0133] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0134] Furthermore, each device such as the processor 1001 and the storage device 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0135] Furthermore, the processing device 10 and the requesting device 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0136] 13 shows an example configuration of a vehicle 2001. As shown in FIG. 13, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example. For example, the processing device 10 or the requesting device 20 may be included in the communication module 2013.

[0137] The drive unit 2002 is configured, for example, by an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

[0138] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0139] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0140] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013 or the like to provide various types of multimedia information and multimedia services to the occupants of the vehicle 2001. The information service unit 2012 may include input devices (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accept input from the outside, and may also include output devices (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that output information to the outside.

[0141] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

[0142] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 29, which are provided in the vehicle 2001.

[0143] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

[0144] The communication module 2013 may transmit, via wireless communication, to an external device at least one of signals from the various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc. may be referred to as input units that accept input.

[0145] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021 to 2029, etc. provided in the vehicle 2001.

[0146] This specification discloses at least the configurations described in the appendices below.

[0147] <Additional Notes> (Additional Item 1) A processing device comprising: a control unit that, when detecting an intent-related conflict in an intent-driven management service, derives multiple solutions for resolving the conflict; and a transmission unit that transmits a message to a requesting device requesting a judgment on the multiple solutions. (Additional Item 2) The processing device according to Additional Item 1, wherein the message is a judge message that requests the requesting device to judge which of the multiple solutions is preferred. (Additional Item 3) A requesting device comprising: a reception unit that receives, from a processing device that has detected an intent-related conflict in an intent-driven management service, a first message that requests a judgment on multiple solutions for resolving the conflict; and a transmission unit that transmits to the processing device a second message presenting a preference for the multiple solutions. (Additional Item 4) The requesting device according to Additional Item 3, wherein the second message is a solution selected by the requesting device from the multiple solutions, or a preference message including priorities for the multiple solutions. (Supplementary Item 5) A communication method executed by a processing device, comprising: when a conflict regarding an intent in an intent-driven management service is detected, deriving a plurality of solutions for resolving the conflict, and sending a message to a requesting device requesting a decision on the plurality of solutions. (Supplementary Item 6) A communication method executed by a requesting device, comprising: receiving, from a processing device that has detected a conflict regarding an intent in an intent-driven management service, a first message requesting a decision on a plurality of solutions for resolving the conflict, and sending, to the processing device, a second message presenting a preference regarding the plurality of solutions.

[0148] Any of Supplementary Items 1 to 6 provides a technique that enables an appropriate decision to be made as to which of multiple solutions to use when there are multiple solutions for resolving a conflict in an intent-driven management service in a mobile network. According to Supplementary Item 2, a judgment message can be used to request a decision from a requesting device. According to Supplementary Item 4, a preference message can be used to notify a processing device of a preference.

[0149] (Supplementary Notes on the Embodiments) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters described in another item (unless inconsistent). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to physical component boundaries. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the processing device 10 and requesting device 20 have been described using functional block diagrams. However, such devices may be implemented using hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

[0150] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling), broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0151] Each aspect / embodiment described in the present disclosure may be implemented using any of the following standards: LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal number)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 ( The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of LTE and / or LTE-A with 5G).

[0152] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be rearranged unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

[0153] The information, signals, etc. described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0154] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be transmitted to another device.

[0155] In the present disclosure, the determination may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0156] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0157] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0158] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0159] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0160] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0161] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0162] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0163] In the present disclosure, terms such as "base station (BS)," "radio base station," "base station device," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. A base station may also be referred to by terms such as a macrocell, a small cell, a femtocell, and a picocell.

[0164] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage.

[0165] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

[0166] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," and the like may be used interchangeably.

[0167] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0168] At least one of the processing device 10 and the requesting device 20 may be referred to as a transmitting device, a receiving device, a communication device, or the like. At least one of the processing device 10 and the requesting device 20 may be a device mounted on a mobile object, the mobile object itself, or the like. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that travels autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the processing device 10 and the requesting device 20 may be a device that does not necessarily move during communication operations. For example, at least one of the processing device 10 and the requesting device 20 may be an IoT (Internet of Things) device such as a sensor.

[0169] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0170] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0171] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

[0172] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0173] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0174] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0175] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0176] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0177] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0178] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0179] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0180] 10 Processing device 110 Transmission unit 120 Reception unit 130 Setting unit 140 Control unit 20 Request device 210 Transmission unit 220 Reception unit 230 Setting unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device

Claims

1. A processing device comprising: a control unit that derives a plurality of solutions for resolving a conflict when detecting a conflict regarding an intent in an intent-driven management service; and a transmission unit that transmits a message for soliciting a determination regarding the plurality of solutions to a requesting device.

2. The processing device according to claim 1, wherein the message is a judge message that solicits a determination from the requesting device regarding which solution among the plurality of solutions is preferable.

3. A requesting device comprising: a receiving unit that receives a first message for soliciting a determination regarding a plurality of solutions for resolving a conflict from a processing device that has detected a conflict regarding an intent in an intent-driven management service; and a transmission unit that transmits a second message presenting a preference regarding the plurality of solutions to the processing device.

4. The requesting device according to claim 3, wherein the second message is a preference message including one solution selected by the requesting device from among the plurality of solutions or a priority order regarding the plurality of solutions.

5. A communication method executed by a processing device, comprising: a step of deriving a plurality of solutions for resolving a conflict when detecting a conflict regarding an intent in an intent-driven management service; and a step of transmitting a message for soliciting a determination regarding the plurality of solutions to a requesting device.

6. A communication method executed by a requesting device, comprising: a step of receiving a first message for soliciting a determination regarding a plurality of solutions for resolving a conflict from a processing device that has detected a conflict regarding an intent in an intent-driven management service; and a step of transmitting a second message presenting a preference regarding the plurality of solutions to the processing device.

Images