Processing device and processing method

Abstract

This processing device comprises: a reception unit that receives, from a requesting device, a request for processing relating to an intent in an intent-driven management service; and a control unit that increments a receive counter on the basis of the reception of the request.

Description

Processing device and processing 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.2.1 (2023-12)3GPP TR 28.912 V18.0.1 (2023-06)3GPP TS 28.622 V18.5.0 (2023-12)

[0005] Intent-driven management services introduce intent-related processes such as Create, Modify, Delete, Query, and Intent conflict resolution (see Non-Patent Document 1). However, the conventional technology has a problem in that a processing device that performs intent-related processes (the MnS Producer in Non-Patent Document 1) cannot appropriately count events related to intent processing (e.g., request reception, processing success / failure, conflict detection).

[0006] The present invention has been made in view of the above points, and aims to provide a technique for appropriately counting events related to intent processing in an intent-driven management service.

[0007] According to the disclosed technology, a processing device is provided that includes: a receiving unit that receives a request for processing related to an intent in an intent-driven management service from a requesting device; and a control unit that increments a reception counter based on the reception of the request.

[0008] The disclosed technology provides a technology for appropriately counting events related to intent processing in an intent-driven management service.

[0009] FIG. 1 is a diagram for explaining an example of a communication system. FIG. 1 is a diagram for explaining an example of a communication system in a roaming environment. FIG. 2 is a diagram for explaining an example of a system configuration of an OSS architecture. FIG. 3 is a diagram for explaining a Create procedure. FIG. 4 is a diagram for explaining a Modify procedure. FIG. 5 is a diagram for explaining a Delete procedure. FIG. 6 is a diagram for explaining a Query procedure. FIG. 7 is a diagram for explaining an Intent conflict resolution procedure. FIG. 8 is a diagram for explaining an example of the functional configuration of a processing device 10 in an embodiment of the present invention. FIG. 9 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. 10 is a diagram for explaining an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

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

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

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

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

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

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

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

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

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

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

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

[0021] 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."

[0022] 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."

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

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

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

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

[0027] (Example of Use Case) As an example, a use case related to an intent containing an expectation on radio network performance to be assured will be described. This use case is applicable to any of the embodiments.

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

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

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

[0031] (Regarding procedures for intent management) Intent-driven management defines the procedures Create, Modify, Delete, Query, and Intent conflict resolution (Non-Patent Document 1). All intent-related procedures start with the issuance of a request from an MnS Consumer (requesting device) to an Mns Producer (processing device). Note that "intent-related procedures" may also be called "intent-related processing."

[0032] 4 to 8 show the procedures for Create (FIG. 4), Modify (FIG. 5), Delete (FIG. 6), Query (FIG. 7), and Intent conflict resolution (FIG. 8), which are excerpted from Non-Patent Document 1.

[0033] Details of the processing procedure are as described in Non-Patent Document 1. Here, as an example, Create (intent generation procedure) shown in Fig. 4 will be described. In Fig. 4, the MnS Consumer corresponds to the request device 20, and the MnS Producer corresponds to the processing device 10.

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

[0035] In step 1, the MnS Consumer requests the creation of an intent instance by sending intent information to the MnS Producer, in step 2 the MnS Producer creates an intent MOI (managed object instance) and sets the received intent information in the intent MOI, and in step 3 the MnS Producer returns a response to the MnS Consumer.

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

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

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

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

[0040] (Problem) In an autonomous network operation based on intent, failure of an intent-related operation can have a significant impact on service provision. However, the conventional technology does not provide a method for a processing device (MnS producer) that processes intents to acquire the number of intent-related operations processed, the number of successes, the number of failures, etc.

[0041] Furthermore, in an autonomous network operation based on intent, the occurrence of intent conflicts may have a significant impact on service provision. However, in the prior art, there is no method for acquiring the number of intent conflicts that have occurred.

[0042] The following describes a technique according to the present embodiment for solving the above-mentioned problems. In the first to fourth embodiments, an occurrence counter and a counting method for each intent-related process (which may also be called an operation) are described. In the fifth embodiment, an intent conflict occurrence counter and a counting method are described.

[0043] (Outline of First to Fifth Embodiments) The processing device 10 holds a reception counter, a success counter, and a failure counter for each operation. The processing device 10 also holds a failure counter for each reason for failure. The processing device 10 increments the corresponding counter for each reception, success, and failure.

[0044] The operations are CREATE, MODIFY, DELETE, and QUERY, and CREATE, MODIFY, DELETE, and QUERY will be described below in the first to fourth embodiments. The processing device 10 also counts the number of intent conflicts that occur, which will be described in the fifth embodiment.

[0045] The counter is, for example, a variable in the processing device 10. When an event that increments the counter is detected, the variable (i.e., the counter) is incremented.

[0046] The first to fifth embodiments can be combined in any manner. The technology according to the present invention can also be applied to intent-related processes other than "CREATE, MODIFY, DELETE, QUERY, and Intent conflict." While multiple counters are described in each embodiment, the processing device 10 may have only some of the multiple counters, rather than all of them.

[0047] (First Embodiment: CREATE) In the first embodiment, a counter and a counting method in CREATE will be described.

[0048] <First embodiment: types of counters> The processing device 10 holds the following counters (1) to (6): (6) is more specifically divided into (6-1) to (6-3).

[0049] (1) CREATE reception counter (2) CREATE success counter (3) CREATE failure counter (4) CREATE feasibility check notify counter (feasible) (5) CREATE feasibility check notify counter (infeasible) (6) CREATE internal logic failure counter (6-1) CREATE failure (invalid parameter) counter (6-2) CREATE failure (infeasible) counter (6-3) CREATE failure (insufficient resources) counter <First embodiment: Counting method> Next, an example of the counting method for each counter will be described.

[0050] When the processing device 10 receives a CREATE request from the requesting device 20, the processing device 10 increments the CREATE reception counter by one.

[0051] If the CREATE operation is successful, the processing device 10 increments the CREATE success counter by 1. A successful CREATE operation occurs, for example, when the status of the createMOI response returned to the requesting device 20 in step 3 of FIG. 4 is OperationSucceeded.

[0052] If the CREATE operation fails, the processing device 10 increments the CREATE failure counter by 1. If the CREATE operation fails, for example, the status of the createMOI response is OperationFailed.

[0053] If the feasibility check determines that the request is feasible, the processing device 10 increments the CREATE feasibility check notify counter (feasible) by 1. If the feasibility check determines that the request is feasible, for example, the feasibilityCheckResult in the intentFeasibilityCheckReport of notifyMOIAttributeValueChanges notified to the requesting device 20 in step 8 of FIG.

[0054] If the feasibility check is determined to be infeasible, the processing device 10 increments the CREATE feasibility check notify counter (infeasible) by 1. If the feasibility check is determined to be infeasible, for example, the feasibilityCheckResult in the intentFeasibilityCheckReport of notifyMOIAttributeValueChanges notified to the requesting device 20 in step 5b of FIG.

[0055] When the operation of the CREATE request fails, the processing device 10 increments the CREATE failure counter by 1 according to the reason for the failure. Specifically, the reason is as follows.

[0056] If the processing device 10 fails to execute the CREATE request due to an incorrect parameter, it increments the CREATE failure (incorrect parameter) counter by one.

[0057] If the feasibility check results in infeasible, the processing device 10 increments the CREATE failure (infeasible) counter by one.

[0058] If the processing device 10 fails to execute the CREATE request due to a lack of resources, it increments the CREATE failure (lack of resources) counter by one.

[0059] <Effects of the First Embodiment> According to the first embodiment, it is possible to appropriately count events related to the CREATE process.

[0060] (Second Embodiment: MODIFY) In the second embodiment, a counter and a counting method in MODIFY will be described.

[0061] Second Embodiment: Types of Counters The processing device 10 holds the following counters (1) to (7): (7) is more specifically divided into (7-1) to (7-4).

[0062] (1) MODIFY reception counter (2) MODIFY success counter (3) MODIFY partial success counter (4) MODIFY failure counter (5) MODIFY feasibility check notify counter (feasible) (6) MODIFY feasibility check notify counter (infeasible) (7) MODIFY internal logic failure counter (7-1) MODIFY failure (invalid parameter) counter (7-2) MODIFY failure (infeasible) counter (7-3) MODIFY failure (target Intent object does not exist) counter (7-4) MODIFY failure (another operation is in progress) counter <Second embodiment: Counting method> Next, an example of a counting method for each counter will be described.

[0063] When the processing device 10 receives a MODIFY request from the requesting device 20, the processing device 10 increments the MODIFY reception counter by one.

[0064] If the MODIFY operation is successful, the processing device 10 increments the MODIFY success counter by 1. A successful MODIFY operation occurs, for example, when the status of the modifyMOIAttributes response returned to the requesting device 20 in step 3 of FIG. 5 is OperationSucceeded.

[0065] If the MODIFY operation is partially successful, the processing device 10 increments the MODIFY partial success counter by 1. If the MODIFY operation is partially successful, for example, the status of the modifyMOIAttributes response is OperationPartiallySucceeded.

[0066] If the MODIFY operation fails, the processing device 10 increments the MODIFY failure counter by 1. If the MODIFY operation fails, for example, the status of the modifyMOIAttributes response is OperationFailed.

[0067] If the feasibility check determines that the request is feasible, the processing device 10 increments the MODIFY feasibility check notify counter (feasible) by 1. If the feasibility check determines that the request is feasible, for example, the feasibilityCheckResult in the intentFeasibilityCheckReport of notifyMOIAttributeValueChanges notified to the requesting device 20 in step 8 of FIG.

[0068] If the feasibility check results in infeasible, the processing device 10 increments the MODIFY feasibility check notify counter (infeasible) by 1. If the feasibility check results in infeasible, for example, the feasibilityCheckResult in the intentFeasibilityCheckReport of notifyMOIAttributeValueChanges notified to the requesting device 20 in step 5b of FIG.

[0069] When the operation of the MODIFY request fails, the processor 10 increments the MODIFY failure counter by 1 according to the reason for the failure. Specifically, the reason is as follows.

[0070] If the processing unit 10 fails to execute the MODIFY request due to an incorrect parameter, it increments the MODIFY failure (incorrect parameter) counter by one.

[0071] If the feasibility check results in infeasible, the processing device 10 increments the MODIFY failure (infeasible) counter by one.

[0072] If the operation of the MODIFY request fails because the target Intent object of the MODIFY request does not exist, the processing device 10 increments the MODIFY failure (target Intent object does not exist) counter by one.

[0073] If the processing unit 10 cannot execute MODIFY because another operation is in progress, it increments the MODIFY failure (another operation is in progress) counter by one.

[0074] <Effects of the Second Embodiment> According to the second embodiment, it is possible to appropriately count events related to the MODIFY process.

[0075] (Third Embodiment: DELETE) In the third embodiment, a counter and a counting method in DELETE will be described.

[0076] <Third embodiment: types of counters> The processing device 10 holds the following counters (1) to (5): (5) is more specifically (5-1).

[0077] (1) DELETE reception counter (2) DELETE partial success counter (3) DELETE success counter (4) DELETE failure counter (5) DELETE internal logic failure counter (5-1) DELETE failure (target Intent object does not exist) counter <Third embodiment: Counting method> Next, an example of a counting method for each counter will be described.

[0078] When the processing device 10 receives a DELETE request from the requesting device 20, the processing device 10 increments the DELETE reception counter by one.

[0079] If the DELETE operation is successful, the processing device 10 increments the DELETE success counter by 1. A successful DELETE operation occurs, for example, when the status of the deleteMOI response sent to the requesting device 20 in step 3 of FIG. 6 is OperationSucceeded.

[0080] If the DELETE operation is partially successful, the processing device 10 increments the DELETE partial success counter by 1. If the DELETE operation is partially successful, for example, the status of the deleteMOI response is OperationPartiallySucceeded.

[0081] If the operation of the DELETE request fails, i.e., if the status of the deleteMOI response is OperationFailed, the processing device 10 increments the DELETE failure counter according to the reason for the failure by 1. For example, if the target Intent object does not exist, the processing device 10 increments the DELETE failure counter (target Intent object does not exist) by 1.

[0082] <Effects of the Third Embodiment> According to the third embodiment, it is possible to appropriately count events related to DELETE processing.

[0083] (Fourth Embodiment: QUERY) In the fourth embodiment, a counter and a counting method for a QUERY will be described.

[0084] <Fourth embodiment: types of counters> The processing device 10 holds the following counters (1) to (4): (4) is more specifically (4-1).

[0085] (1) QUERY reception counter (2) QUERY success counter (3) QUERY failure counter (4) QUERY internal logic failure counter (4-1) QUERY failure counter (target Intent object does not exist) <Fourth embodiment: Counting method> Next, an example of the counting method for each counter will be described.

[0086] When the processing device 10 receives a QUERY request from the requesting device 20, the processing device 10 increments the QUERY reception counter by one.

[0087] If the QUERY operation is successful, the processing device 10 increments the QUERY success counter by 1. A successful QUERY operation is, for example, when the status of the getMOIAttributes response sent to the requesting device 20 in step 3 of Figure 7 is OperationSucceeded.

[0088] If the operation of a QUERY request fails, i.e., if the status of the getMOIAttributes response is OperationFailed, the processing device 10 increments the QUERY failure counter corresponding to the reason for the failure by 1. For example, if the target Intent object does not exist, the processing device 10 increments the counter corresponding to the reason for the failure by 1.

[0089] <Effects of the Fourth Embodiment> According to the fourth embodiment, it is possible to appropriately count events related to query processing.

[0090] Fifth Embodiment: Intent Conflict Resolution In the fifth embodiment, a counter and a counting method for Intent conflict resolution will be described.

[0091] Fifth Embodiment: Types of Counters The processing device 10 holds an intent conflict occurrence counter.

[0092] 8, the processing device 10 increments the intent conflict counter by 1 when an intent conflict is detected. Here, an example of detecting an intent conflict will be described. For example, assume that the processing device 10 receives a request to generate intent #1 from the requesting device 20-1 and a request to generate intent #2 from the requesting device 20-2.

[0093] Assume 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 requires a large amount of power, the processing device 10 detects the occurrence of a conflict between these two intents and increments the counter by one.

[0094] Furthermore, a conflict may be detected within a single intent. For example, suppose the processing device 10 receives a request to generate a certain intent. For example, if the intent has goals of "throughput > threshold 1" (goal 1) and "interference < threshold 2" (goal 2), when the processing device 10 detects that both "throughput > threshold 1" and "interference < threshold 2" cannot be satisfied, it detects that a conflict has occurred within the intent.

[0095] <Effects of Fifth Embodiment> According to the fifth embodiment, it is possible to appropriately count the occurrence of an intent conflict.

[0096] (Variation of operation common to the first to fifth embodiments) In the examples described so far, when the conditions for incrementing the counter are met, the counter is incremented by 1. However, depending on the settings, etc., when the conditions are met, the counter may be incremented by N (N is an integer of 2 or more).

[0097] In addition, when the processing device 10 detects that the count value of a specific counter (e.g., a failure counter) has exceeded a preset threshold, it may output a signal (e.g., an alert) indicating this.

[0098] Furthermore, when the processing device 10 detects that a predetermined condition for a counter has been satisfied, the processing device 10 may decrement the counter by 1 (or by N). For example, after the failure counter is incremented by 1 due to the detection of a failure event, the failure counter may be decremented by 1 if the failure event is resolved and the processing is successful.

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

[0100] <Processing device 10> Fig. 9 is a diagram showing an example of the functional configuration of the processing device 10. As shown in Fig. 9, 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. 9 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.

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

[0102] The setting unit 130 stores preset setting information and various setting information to be transmitted to other devices in a storage device, and reads it from the storage device as needed. The setting information is, for example, information for configuring settings for a management target (such as a wireless network). The control unit 140 controls the processing device 10. The control unit 140 holds the counter described above and can perform counting using the method described above. The signal transmission functional unit in the control unit 140 may be included in the transmitting unit 110, and the signal reception functional unit in the control unit 140 may be included in the receiving unit 120.

[0103] <Requesting Device 20> Fig. 10 is a diagram showing an example of the functional configuration of the requesting device 20. As shown in Fig. 10, 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. 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.

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

[0105] The setting unit 230 stores preset setting information and various setting information to be transmitted to other devices in a storage device, and reads them from the storage device as needed. The control unit 240 controls the requesting device 20. The function unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the function unit related to signal reception in the control unit 240 may be included in the receiving unit 120.

[0106] (Hardware Configuration) The block diagrams (FIGS. 9 and 10) 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.

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

[0108] 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 processing method of the present disclosure. Fig. 11 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.

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

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

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

[0112] The processor 1001 also reads 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. 9 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. 10 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.

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

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

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

[0116] 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).

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

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

[0119] 12 shows an example configuration of a vehicle 2001. As shown in FIG. 12, 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.

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

[0121] 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).

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

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

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

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

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

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

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

[0129] This specification discloses at least the configurations described in the following supplementary notes. <Supplementary Notes> (Supplementary Item 1) A processing device comprising: a receiving unit that receives, from a requesting device, a request for processing related to an intent in an intent-driven management service; and a control unit that increments a reception counter based on the reception of the request. (Supplementary Item 2) The processing device according to Supplementary Item 1, wherein the control unit increments a success counter if the processing is successful, and increments a failure counter if the processing fails. (Supplementary Item 3) The processing device according to Supplementary Item 2, wherein the failure counter is a counter corresponding to a reason for failure. (Supplementary Item 4) The processing device according to any one of Supplementary Items 1 to 3, wherein the control unit increments a counter indicating that the processing is executable if it determines that the processing is executable, and increments a counter indicating that the processing is not executable if it determines that the processing is not executable. (Supplementary Item 5) The processing device according to any one of Supplementary Items 1 to 4, wherein the control unit increments an intent conflict counter if it detects an intent conflict. (Supplementary Item 6) A processing method executed by a processing device, comprising: receiving a request for processing related to an intent in an intent-driven management service from a requesting device; and incrementing a reception counter based on the reception of the request.

[0130] Any of Supplementary Items 1 to 6 makes it possible to appropriately count events related to intent processing in an intent-driven management service. Supplementary Item 2 makes it possible to count failures and successes. Supplementary Item 3 makes it possible to count according to the reason for failure. Supplementary Item 4 makes it possible to count executable and inexecutable events. Supplementary Item 5 makes it possible to count the number of intent conflicts that occur.

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

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

[0133] 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0150] 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, handcarts, 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 operational commands. The moving object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that 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.

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

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

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

[0154] 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."

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

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

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

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

[0159] 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."

[0160] 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).

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

[0162] 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 receiving unit that receives a request for processing related to an intent in an intent-driven management service from a requesting device; and a control unit that increments a reception counter based on the reception of the request.

2. The processing device according to claim 1, wherein the control unit increments a success counter when the processing is successful, and increments a failure counter when the processing is unsuccessful.

3. The processing device according to claim 2, wherein the failure counter is a counter corresponding to the reason for failure.

4. The processing device according to claim 1, wherein the control unit increments a counter indicating that the processing is executable when it determines that the processing is executable, and increments a counter indicating that the processing is not executable when it determines that the processing is not executable.

5. The processing device according to claim 1, wherein the control unit increments an intent conflict counter when an intent conflict is detected.

6. A processing method executed by a processing device, comprising: receiving a request for processing related to an intent in an intent-driven management service from a requesting device; and incrementing a reception counter based on the reception of the request.

Images