Delay information collection device, delay control system, delay information collection method and program

Abstract

This delay information collection device comprises: a route information acquisition unit that acquires route information relating to a communication route between a controlled device and a control device; a delay information acquisition unit that acquires delay information indicating a communication delay time occurring on the communication path from one or a plurality of communication devices present on the communication path; and a delay information transmission unit that transmits total delay information indicating a total of the delay time, which is based on the delay information acquired by the delay information acquisition unit, to the control device, which controls the controlled device on the basis of the total delay information.

Description

[Technical Field]

[0001] The present invention relates to a delay information collecting device, a delay control system, a delay information collecting method, and a program. [Background technology]

[0002] Communication delays (hereinafter referred to as "network delays") occurring in a network can adversely affect the control performance of real-time control of IoT (Internet of Things) terminals via a network. For example, a decrease in control performance can lengthen the time it takes for control of the IoT terminal to stabilize, or even cause the terminal to become uncontrollable. Generally, the greater the distance between the IoT terminal to be controlled (hereinafter referred to as the "controlled device") and the control device that controls the controlled device, and the greater the number of communication devices through which communication between the controlled device and the control device passes, the greater the magnitude of network delays.

[0003] In recent years, edge computing technologies have been proposed that reduce network latency by installing a server near a controlled device and performing edge processing. Furthermore, a conventional technology has been proposed that sequentially measures latency and controls the controlled device in real time based on the measured latency. In such conventional technologies, a method is generally used in which the latency of communication between a control device and a controlled device is calculated using a measured value of RTT (Round Trip Time) (see, for example, Patent Document 1).

[0004] A conventional delay control system will be briefly described below. FIG. 21 is a schematic diagram showing the control of a controlled device by a conventional delay control system. As shown in FIG. 21, the controlled device includes a sensor node and an actuator node, and the control device includes a controller. First, at the beginning of a control period, the control device sends measurement data to the controlled device using a command such as ping to measure the RTT. When the controlled device receives the measurement data, it sends response data back to the control device. The control device receives the response data sent from the controlled device. The control device can measure the RTT by measuring the time from when it sends the measurement data to when it receives the response data.

[0005] If the control device and the controlled device are time-synchronized, the RTT can also be measured, for example, as follows. First, at the beginning of the control period, data is sent from the sensor node of the controlled device to the controller of the control device. This allows the control device to obtain the value of delay t1, which indicates the magnitude of the network delay in communication from the controlled device to the control device. Next, data is sent from the controller of the control device to the actuator node of the controlled device. This allows the control device to obtain the value of delay t2, which indicates the magnitude of the network delay in communication from the control device to the controlled device. In this case, the RTT is expressed as t1 + t2.

[0006] The control device then incorporates delay information based on this RTT value into the control algorithm executed by the controller. Note that the control algorithm here refers to an algorithm executed by the control device to control the controlled device in real time. The control device measures the RTT at each control cycle, thereby sequentially updating the delay information incorporated into the control algorithm.

[0007] FIG. 22 is a schematic diagram illustrating the basic configuration of a conventional delay control system. As shown in FIG. 22, the delay control system includes a control target device, a control device, and multiple communication devices. The control target device is, for example, an IoT terminal such as a drone, a sensor, or an actuator. The control device is a server device that controls the control target device in real time. Note that, for simplicity of explanation, FIG. 22 illustrates only one control device and one control target device. However, the configuration is not limited to this, and a configuration in which one control device controls multiple control target devices in real time is also possible.

[0008] As shown in FIG. 22, a control target device, multiple communication devices, and a control device are connected in series. The control target device and the control device communicate via multiple communication devices. Note that communication between the control target device and the control device may be via only one communication device. Each of the multiple communication devices sequentially measures the processing time of the communication process executed by its own communication device. Then, each of the multiple communication devices transmits information indicating the measured processing time to the control device. This allows the control device to sequentially acquire information indicating the processing time of the communication process executed by each communication device (hereinafter referred to as "delay information") from all the communication devices. Each time the control device acquires delay information from all the communication devices, it sets the control algorithm to be executed by its own control device. Specifically, the control device updates the delay information incorporated in the control algorithm with new delay information acquired sequentially.

[0009] Note that the network delay occurring in communication between the control target device and the control device is not necessarily limited to delays caused only by the communication processing executed by the communication device. However, for the sake of simplicity, the delay time of the network delay occurring in communication between the control target device and the control device is assumed to be the sum of the processing times of the communication processing executed by each communication device.

[0010] Fig. 23 is a block diagram showing an example of the functional configuration of a conventional delay control system. As shown in Fig. 23, the delay control system includes, for example, a control target device, a control server, a communication server, and a white-box switch. The control target device is, for example, an IoT terminal, and is a device managed by a user. The control server, communication server, and white-box switch are devices managed by a telecommunications carrier (at a central office). The control system is a system for controlling the control target device in real time using edge computing by the telecommunications carrier.

[0011] As shown in FIG. 23, the control server includes a delay information receiving unit and an updating unit. The control server is a device equivalent to the control device of the control system shown in FIG. 22. The communication server includes a processing time measuring unit, a monitoring unit, and a delay information transmitting unit. The white-box switch includes a processing time measuring unit, a monitoring unit, and a delay information transmitting unit. The communication server and the white-box switch are devices equivalent to the communication devices of the control system shown in FIG. 22.

[0012] The control server is a server device that controls a control target device in real time. For ease of explanation, FIG. 23 shows a control system configuration in which one control server controls only one control target device in real time. However, this configuration is not limiting, and one control server may control multiple control target devices in real time. As shown in FIG. 23, the control target device, communication server, white-box switch, and control server are connected in series. The control target device and the control server communicate with each other via the communication server and white-box switch.

[0013] The processing time measurement unit of the communication server sequentially measures the processing time of the communication processing executed by the communication server. The monitoring unit of the communication server determines whether to transmit delay information indicating the processing time to the control server based on the processing time measured by the processing time measurement unit and the measurement cycle of the processing time measurement unit. The delay information transmission unit of the communication server transmits the delay information to the control server when the monitoring unit determines to transmit the delay information.

[0014] The configurations of the processing time measurement unit, monitoring unit, and delay information transmission unit of the white-box switch are the same as the configurations of the processing time measurement unit, monitoring unit, and delay information transmission unit of the communication server, respectively. The processing time measurement unit of the white-box switch sequentially measures the processing time of the communication processing executed by its own white-box switch. The monitoring unit of the white-box switch determines whether to transmit delay information indicating the processing time to the control server based on the processing time measured by the processing time measurement unit and the measurement cycle of the processing time measurement unit. The delay information transmission unit of the white-box switch transmits the delay information to the control server when the monitoring unit determines that the delay information should be transmitted.

[0015] The delay information receiving unit of the control server receives the delay information transmitted from the communication server and the white-box switch. The update unit of the control server sequentially updates the delay information incorporated in the control algorithm executed by the control server with new delay information sequentially acquired by the delay information receiving unit. Then, a controller (not shown) included in the control server controls the controlled device in real time using the control algorithm with the updated delay information. [Prior art documents] [Patent documents]

[0016] [Patent Document 1] Japanese Patent Publication No. 2020-021410 Summary of the Invention [Problem to be solved by the invention]

[0017] As described above, in remote control of a controlled device such as an IoT terminal that takes into account delays in a communication path, a method has been known in the past that considers the processing time of communication processing in a communication device present on the communication path as a delay (for example, Patent Document 1). In such a conventional method, a measured value of RTT is generally used as delay information transmitted from the communication device to the control device. In such a conventional method, delay information indicating delays occurring in communication devices (generally managed by a telecommunications carrier) present on the communication network must be acquired by the control device (generally managed by a user).

[0018] However, since a control device is generally a device managed by a user, it may not have an interface that allows direct communication with a communication device managed by a telecommunications carrier. Therefore, there is a problem that it may be practically difficult for the control device to directly communicate with a communication device that exists on a communication path between the control device and the control target device, acquire delay information from the communication device, and remotely control the control target device using the above-mentioned conventional method.

[0019] In view of the above circumstances, the present invention aims to provide a delay information collection device, a delay control system, a delay information collection method, and a program that can remotely control a controlled device while taking into account delays that occur on the communication path between the control device and the controlled device, even if the control device cannot communicate directly with a communication device that exists on the communication path between the control device and the controlled device. [Means for solving the problem]

[0020] One aspect of the present invention is a delay information collection device that includes a route information acquisition unit that acquires route information regarding a communication route between a control target device and a control device, a delay information acquisition unit that acquires delay information indicating a communication delay time occurring on the communication route from one or more communication devices present on the communication route, and a delay information transmission unit that transmits total delay information indicating the sum of the delay times based on the delay information acquired by the delay information acquisition unit to the control device that controls the control target device based on the total delay information.

[0021] Another aspect of the present invention is a delay control system having a control device and a delay information collecting device, wherein the control device comprises: a route information transmitting unit that transmits route information regarding the communication route between the control target device to be controlled and the control device itself to the delay information collecting device; a total delay information acquiring unit that acquires total delay information indicating the total communication delay time occurring on the communication route from the delay information collecting device; and a control unit that controls the control target device based on the total delay information acquired by the total delay information acquiring unit, and the delay information collecting device comprises: a route information acquiring unit that acquires route information transmitted from the control device; a delay information acquiring unit that acquires delay information indicating the delay time from one or more communication devices present on the communication route; and a total delay information transmitting unit that transmits the total delay information indicating the total of the delay time based on the delay information acquired by the delay information acquiring unit to the control device.

[0022] Another aspect of the present invention is a delay information collection method by a computer of a delay information collection device, which includes a route information acquisition step of acquiring route information regarding a communication route between a control target device and a control device, a delay information acquisition step of acquiring delay information indicating a communication delay time occurring on the communication route from one or more communication devices present on the communication route, and a delay information transmission step of transmitting total delay information indicating the sum of the delay times based on the delay information acquired by the delay information acquisition step to the control device that controls the control target device based on the total delay information.

[0023] Another aspect of the present invention is a program for causing a computer to execute a route information acquisition step of acquiring route information regarding a communication route between a control target device and a control device, a delay information acquisition step of acquiring delay information indicating a communication delay time occurring on the communication route from one or more communication devices present on the communication route, and a delay information transmission step of transmitting total delay information indicating the sum of the delay times based on the delay information acquired by the delay information acquisition step to the control device that controls the control target device based on the total delay information. [Effects of the Invention]

[0024] According to the present invention, even if a control device cannot communicate directly with a communication device that exists on a communication path between the control device and the controlled device, it is possible to remotely control the controlled device while taking into account delays that occur on the communication path. [Brief explanation of the drawings]

[0025] [Figure 1] 1 is an overall configuration diagram of a delay control system 1 according to a first embodiment of the present invention. [Figure 2] 2 is a block diagram showing a functional configuration of a delay information collection App 41 of a delay information collection device 40 according to the first embodiment of the present invention. FIG. [Figure 3] FIG. 1 is a diagram illustrating an example of a configuration of a communication network and a delay control system. [Figure 4] FIG. 2 is a diagram illustrating an example of a route information master stored in a route delay information DB 412 in the first embodiment of the present invention. [Figure 5] FIG. 4 is a diagram showing an example of delay information stored in a route delay information DB 412 in the first embodiment of the present invention. [Figure 6] 3 is a flowchart showing the operation of the delay control system 1 in the first embodiment of the present invention. [Figure 7] 10 is a block diagram showing a functional configuration of a delay information collection App 41a of a delay information collection device 40 according to a second embodiment of the present invention. FIG. [Figure 8] 10 is a flowchart showing the operation of the delay control system 1a according to the second embodiment of the present invention. [Figure 9] FIG. 1 is a diagram illustrating an example of a configuration of a communication network and a delay control system. [Figure 10] FIG. 13 is a diagram illustrating an example of a route information master stored in a route delay information DB 412b in the third exemplary embodiment of the present invention. [Figure 11] FIG. 4 is a diagram illustrating an example of delay information stored in a route delay information DB 412b in the first embodiment of the present invention. [Figure 12] 1 is a block diagram showing an example of a network configuration of a delay control system according to an embodiment of the present invention. [Figure 13] 1 is a block diagram showing an example of a network configuration of a delay control system according to an embodiment of the present invention. [Figure 14] 1 is a block diagram showing an example of a network configuration of a delay control system according to an embodiment of the present invention. [Figure 15] 1 is a block diagram showing an example of a network configuration of a delay control system according to an embodiment of the present invention. [Figure 16] 1 is a block diagram showing an example of a network configuration of a delay control system according to an embodiment of the present invention. [Figure 17] 1 is a block diagram showing an example of a network configuration of a delay control system according to an embodiment of the present invention. [Figure 18] 1 is a block diagram showing an example of a network configuration of a delay control system according to an embodiment of the present invention. [Figure 19] 1 is a block diagram showing an example of a network configuration of a delay control system according to an embodiment of the present invention. [Figure 20] 1 is a block diagram showing an example of a network configuration of a delay control system according to an embodiment of the present invention. [Figure 21] FIG. 1 is a schematic diagram illustrating control of a control target device by a conventional delay control system. [Figure 22]FIG. 1 is a schematic diagram for explaining a basic configuration of a conventional delay control system. [Figure 23] FIG. 1 is a block diagram showing an example of a functional configuration of a conventional delay control system. DETAILED DESCRIPTION OF THE INVENTION

[0026] Hereinafter, a delay information collecting device, a delay control system, a delay information collecting method, and a program according to embodiments will be described with reference to the drawings.

[0027] First Embodiment The delay control system 1 according to the first embodiment of the present invention will be described below.

[0028] [Configuration of delay control system] The following describes the overall configuration of the delay control system 1. Fig. 1 is a diagram showing the overall configuration of the delay control system 1 according to the first embodiment of the present invention. As shown in Fig. 1, the delay control system 1 includes a control target device 10, a control device 20, a plurality of communication devices 30, and a delay information collection device 40.

[0029] The control target device 10 is, for example, an IoT terminal such as a drone, a sensor, or an actuator. The control device 20 is, for example, a server device (information processing device) such as a general-purpose computer that controls the control target device 10 in real time. For simplicity of explanation, FIG. 1 illustrates only one control device 20 and one control target device 10. However, this configuration is not limiting, and for example, a configuration in which one control device 20 controls multiple control target devices 10 in real time is also acceptable.

[0030] 1, a control target device 10, a plurality of communication devices 30, and a control device 20 are connected in series. The control target device 10 and the control device 20 communicate with each other via the plurality of communication devices 30. Note that the number of communication devices 30 (communication devices 30 present on the communication path) via which communication between the control target device 10 and the control device 20 is passed may be one.

[0031] FIG. 1 shows three communication devices 30 as an example, one of which is communication device 30-1 and the other is communication device 30-2. Communication device 30-1 is a wireless base station that is connected to control target device 10 via wireless communication. Communication device 30-2 is a switch that switches wired communication paths. Note that communication device 30 is not limited to wireless base stations and switches, but includes all devices that are present on the communication path between control device 20 and control target device 10 and perform communication processing that may cause delays. Note that in the following description, when there is no need to distinguish between communication device 30-1 and communication device 30-2, they will simply be referred to as "communication device 30."

[0032] Each of the multiple communication devices 30 sequentially measures the processing time of the communication processing executed by its own communication device 30. Then, each of the multiple communication devices 30 transmits delay information indicating the measured processing time to the delay information collecting device 40. Note that the communication device 30 may transmit the delay information in response to a request from the delay information collecting device 40, or may transmit the delay information to the delay information collecting device 40 on its own initiative, for example, periodically.

[0033] The delay information collecting device 40 is an information processing device such as a general-purpose computer. As shown in Fig. 1, a delay information collecting application 41 (hereinafter referred to as "delay information collecting App 41") is installed in the delay information collecting device 40. The delay information collecting App 41 is an application that collects delay information transmitted from each of the communication devices 30 and outputs information based on the collected delay information to the control device 20.

[0034] The delay information collection app 41 acquires delay information transmitted from each of the multiple communication devices 30. The delay information collection app 40 acquires delay information from, for example, all of the communication devices 30. The delay information collection app 41 adds up the acquired delay information and outputs it to the control device 20. This allows the control device 20 to sequentially acquire, via the delay information collection app 41 of the delay information collection app 40, information indicating the total processing time (delay time) of communication processing executed by each of the communication devices 30 present on the communication path.

[0035] The delay information collection App 41 may transmit the delay information to the control device 20 spontaneously, or may transmit the delay information in response to a request from the control device 20. When the delay information collection device 40 spontaneously transmits the delay information to the control device 20, the delay information collection device 40 may transmit the delay information when it has collected the delay information from all of the communication devices 30, or may transmit the delay information periodically.

[0036] The control device 20 is a server device (information processing device) that controls the control target device 10 (IoT terminal) in real time. As shown in Fig. 1, an IoT terminal control application 21 (hereinafter referred to as "IoT terminal control App 21") is installed in the control device 20. The IoT terminal control App 21 is an application that executes a control algorithm that controls the control target device 10 in real time.

[0037] The IoT terminal control app 21 sequentially acquires delay information from all communication devices 30 collected by the delay information collection app 41 from the delay information collection app 40. Each time the IoT terminal control app 21 acquires the delay information, it sets the control algorithm to be executed by the IoT terminal control app 21. Specifically, the IoT terminal control app 21 updates the delay information incorporated in the control algorithm each time new delay information is acquired sequentially.

[0038] With such a configuration, even if the delay time generated in each of the communication devices 30 changes, the IoT terminal control App21 can follow the change in the delay time and perform appropriate control of the control target device 10 in real time.

[0039] Furthermore, when the control device 20 controls, for example, a plurality of control target devices 10 in real time, the control device 20 needs to acquire the delay information incorporated into the control algorithm for each control target device 10 for which the delay information is to be updated. As shown in Fig. 1 , the IoT terminal control App 21 of the control device 20 transmits, to the delay information collection device 40, route information indicating the communication route between the control device 20 and the control target device 10 for which the delay information is to be updated.

[0040] The delay information collection app 41 of the delay information collection device 40 acquires the route information transmitted from the IoT terminal control app 21. The delay information collection app 41 identifies one or more communication devices 30 that exist on the communication route corresponding to the acquired route information. The delay information collection app 41 collects delay information from each of the identified communication devices 30. The delay information collection app 41 adds up delay times based on the collected delay information and outputs the sum to the control device 20.

[0041] The IoT terminal control app 21 of the control device 20 acquires delay information (total delay information) from the delay information collection device 40, which is collected by the delay information collection app 41 and indicates the sum of delay times in all communication devices 30 present on the communication path between the control target device 10 that is the control target and the control device 20. Each time the IoT terminal control app 21 acquires the delay information, it sets the control algorithm to be executed by its own IoT terminal control app 21. Specifically, the IoT terminal control app 21 updates the delay information incorporated in the control algorithm each time new delay information is acquired sequentially.

[0042] With this configuration, even if the delay time generated in each of the communication devices 30 present on the communication path between the control target device 10 to be controlled and the control device 20 changes, the IoT terminal control App 21 can follow the change in the delay time and execute appropriate control in real time for each control target device 10 to be controlled.

[0043] It should be noted that the network delay occurring in the communication path between the control target device 10 and the control device 20 is not necessarily limited to delay occurring solely due to the communication processing executed by the communication device 30. However, for simplicity of explanation, it is assumed here that the delay time of the network delay occurring in the communication path between the control target device 10 and the control device 20 is the sum of the processing times of the communication processing executed by each of the communication devices 30. If necessary, the delay time of other network delays, such as propagation time, may be set in advance as a fixed value, and the delay time of the other network delays may be added to the above-mentioned summation time.

[0044] [Configuration of the delay information collection app] The following describes the configuration of the delay information collection App 41 of the delay information collection device 40. Fig. 2 is a block diagram showing the functional configuration of the delay information collection App 41 of the delay information collection device 40 in the first embodiment of the present invention.

[0045] As shown in Figure 2, the delay information collection App41 is configured to include a delay information acquisition unit 411, a route delay information database 412 (hereinafter referred to as the "route delay information DB412"), a route delay information acquisition control unit 413, a delay information request receiving unit 414, a route information conversion unit 415, a total route delay calculation unit 416, and a delay information transmission unit 417.

[0046] The delay information acquisition unit 411 acquires delay information transmitted from each of the multiple communication devices 30. A route ID (Identifier) ​​is assigned to the delay information transmitted from the communication device 30. The route ID is an identifier that indicates a specific range of the communication route between the control target device 10 and the control device 20. The delay information collection App 41 acquires the delay information and the route ID, thereby being able to recognize the network delay for each specific range of the communication route.

[0047] In the first embodiment, as described above, it is assumed that network delay occurs only in the communication device 30, and therefore the path ID corresponds to an identifier that identifies the communication device 30. Therefore, in the first embodiment, the delay information collection app 41 can recognize network delay for each communication device 30.

[0048] The delay information acquisition unit 411 stores the acquired delay information and route information in association with each other in the route delay information DB 412.

[0049] The delay information request receiving unit 414 (route information acquiring unit) acquires a delay information request transmitted from the IoT terminal control app 21 of the control device 20. The delay information request includes route information for identifying a communication route between the control target device 10, which is the target of control by the IoT terminal control app 21, and the control device 20. The delay information request receiving unit 414 outputs the acquired route information to the route information converting unit 415.

[0050] The path information may be any information as long as it is information that can identify a communication path between the control target device 10 and the control device 20. For example, if it is possible to identify a communication path based on identification information that identifies the control target device 10, such as an IP address or a MAC address, the path information may be identification information that identifies such a control target device 10.

[0051] The route information conversion unit 415 acquires the route information output from the delay information request receiving unit 414. The route information conversion unit 415 identifies a communication route between the control target device 10, which is the target of control by the IoT terminal control App 21, and the control device 20, based on the acquired route information. Then, the route information conversion unit 415 identifies route IDs corresponding to each range (communication devices 30) that constitutes the identified communication route. The route information conversion unit 415 outputs the identified one or more route IDs (hereinafter referred to as a "route ID group") to the route delay information acquisition control unit 413.

[0052] The route delay information acquisition control unit 413 acquires the route ID group output from the route information conversion unit 415. The route delay information acquisition control unit 413 refers to the route delay information DB 412 and acquires delay information associated with each of the route IDs included in the acquired route ID group.

[0053] The delay information acquisition unit 411 may directly output information in which the acquired delay information is associated with the route ID to the route delay information acquisition control unit 413. In this case, the route delay information acquisition control unit 413 acquires delay information associated with each of the route IDs included in the acquired route ID group based on the delay information and route ID acquired from the delay information acquisition unit 411.

[0054] It should be noted that whether the route delay information acquisition control unit 413 acquires the delay information from the route delay information DB 412 or the delay information acquisition unit 411 may be determined, for example, in response to a request from the IoT terminal control App 21 of the control device 20. For example, if the request from the IoT terminal control App 21 requires more real-time performance, it is preferable to acquire the delay information directly from the delay information acquisition unit 411, and otherwise acquire the delay information from the route delay information DB 412.

[0055] If the group of route IDs acquired from the route information conversion unit 415 includes multiple route IDs (i.e., if there are multiple communication devices 30 on the communication path between the control target device 10 that is the target of control by the IoT terminal control App 21 and the control device 20), the route delay information acquisition control unit 413 outputs the delay information associated with each of the route IDs to the total route delay calculation unit 416.

[0056] Furthermore, when the group of route IDs acquired from the route information conversion unit 415 includes only one route ID (i.e., when only one communication device 30 exists on the communication path between the control target device 10, which is the target of control by the IoT terminal control App 21, and the control device 20), the route delay information acquisition control unit 413 outputs the delay information associated with the route ID to the delay information transmission unit 417. Alternatively, when there is a request from the control device 20 to transmit the delay information to the IoT terminal control App 21 of the control device 20 without adding up the delay information, the route delay information acquisition control unit 413 outputs the delay information associated with the route ID to the delay information transmission unit 417.

[0057] The total route delay calculation unit 416 acquires multiple pieces of delay information (associated with each route ID) output from the route delay information acquisition control unit 413. The total route delay calculation unit 416 adds up the delay times indicated by each piece of acquired delay information. The total route delay calculation unit 416 outputs delay information indicating the added up delay time (total delay information) to the delay information transmission unit 417 (total delay information transmission unit).

[0058] The delay information transmission unit 417 acquires the delay information output from the route delay information acquisition control unit 413 or the total route delay calculation unit 416. The delay information transmission unit 417 transmits the acquired delay information to the IoT terminal control App 21 of the control device 20.

[0059] The IoT terminal control application 21 acquires the delay information transmitted from the delay information transmission unit 417. Each time the IoT terminal control application 21 acquires the delay information, it configures the control algorithm executed by the IoT terminal control application 21. Specifically, the IoT terminal control application 21 updates the delay information incorporated into the control algorithm each time new delay information (total delay information) is acquired sequentially. For example, the IoT terminal control application 21 updates the configuration of the control algorithm so that the delay time based on the acquired delay information (total delay information) is taken into account.

[0060] With this configuration, even if the delay time generated in each of the communication devices 30 present on the communication path between the control target device 10 to be controlled and the control device 20 changes, the IoT terminal control App 21 can follow the change in the delay time and execute appropriate control in real time for each control target device 10 to be controlled.

[0061] For ease of understanding, a specific example will be given below to explain the process of collecting delay information by the delay information collection App 41 of the delay information collection device 40. Fig. 3 is a diagram showing an example of the configuration of a communication network and a delay control system.

[0062] As shown in Fig. 3, the IoT terminal control App 21 can control the control target device 10A and the control target device 10B. Also, as shown in Fig. 3, communication devices 30A to 30D exist on the communication paths between the IoT terminal control App 21 (control device 20) and the control target device 10A and the control target device 10B.

[0063] 3, the control target device 10A and the control target device 10B are connected to the communication device 30A. The communication device 30A is connected to the communication device 30B and the communication device 30C. The communication device 30B and the communication device 30C are connected to the communication device 30D. The communication device 30D is connected to the IoT terminal control App 21 (control device 20) and the delay information collection App 41 (delay information collection device 40). The delay information collection App 41 includes a route delay information DB 412.

[0064] The route delay information DB 412 stores in advance information (hereinafter referred to as "route information master") in which identification information for identifying the control target device 10 is associated with identification information for identifying the communication device 30 present on the communication path between the control target device 10 and the control device 20 (i.e., the above-mentioned route ID group). Here, it is assumed that the route information master is acquired in advance by, for example, another system (not shown) and stored in the route delay information DB 412.

[0065] Fig. 4 is a diagram showing an example of a route information master stored in the route delay information DB 412 in the first embodiment of the present invention. As shown in Fig. 4, a group of route IDs indicating a communication route of (control target device 10A)-"communication device 30A"-"communication device 30B"-"communication device 30D" is associated with identification information for identifying the control target device 10A (a character string "control target device 10A" in Fig. 4). In Fig. 4, each of the character strings "communication device 30A", "communication device 30B", and "communication device 30D" is a route ID.

[0066] Furthermore, information in which a route ID is associated with delay information is stored in the route delay information DB 412. This delay information is sequentially acquired from each of the communication devices 30 by the delay information collection App 41 and updated.

[0067] 5 is a diagram showing an example of delay information stored in the route delay information DB 412 in the first embodiment of the present invention. As shown in FIG. 4, the delay information is information in which information indicating delay time is associated with a route ID.

[0068] The information indicating the delay time included in the delay information is, for example, information indicating the delay time of a delay that occurs in a communication process executed by each communication device 30. As shown in FIG. 4, for example, a delay time of "10" is associated with a route ID of "communication device 30A." This indicates that the delay time (at that time) of a delay that occurs in a communication process executed by communication device 30A is 10 (for example, 10 milliseconds). Also, as shown in FIG. 4, for example, a delay time of "5" is associated with a route ID of "communication device 30B." This indicates that the delay time (at that time) of a delay that occurs in a communication process executed by communication device 30B is 5 (for example, 5 milliseconds).

[0069] The flow of the delay information collection process will be described below. First, the IoT terminal control app 21 transmits route information including identification information for identifying the control target device 10 to be controlled to the delay information collection app 41. As an example, it is assumed here that the IoT terminal control app 21 transmits route information including identification information indicating the control target device 10A to the delay information collection app 41.

[0070] The delay information collection app 41 acquires the route information transmitted from the IoT terminal control app 21. The delay information collection app 41 identifies the identification information (that identifies the control target device 10) included in the acquired route information. The delay information collection app 41 refers to the route delay information DB 412, and acquires a group of route IDs corresponding to the identified identification information.

[0071] As described above, here, the identification information included in the route information is identification information that indicates the control target device 10A. The delay information collection App 41 acquires, for example, "(control target device 10A)-communication device 30A-communication device 30B-communication device 30D," which is a route ID group corresponding to the control target device 10A, as shown in FIG.

[0072] Next, the delay information collection App 41 refers to the route delay information DB 412 and acquires delay information corresponding to each of the route IDs included in the acquired route ID group. Specifically, the delay information collection App 41 acquires, for example, "10" which is the delay time value corresponding to "communication device 30A," "5" which is the delay time value corresponding to "communication device 30B," and "8" which is the delay time value corresponding to "communication device 30D" as shown in FIG.

[0073] The delay information collection app 41 sums up the delay time values ​​indicated by the acquired delay information. Specifically, the delay information collection app 41 obtains the value "23" as the sum of the delay time values ​​included in each of the delay information. The delay information collection app 41 transmits delay information indicating the summed delay time (total delay information) to the IoT terminal control app 21.

[0074] The IoT terminal control app 21 acquires the delay information transmitted from the delay information collection app 41. The IoT terminal control app 21 updates the delay information incorporated in the control algorithm each time new delay information is acquired. Specifically, the IoT terminal control app 21 updates the setting of the control algorithm so that the control target device 10A is controlled taking into account the value of "23" (e.g., 23 milliseconds), which is the delay time indicated by the acquired delay information.

[0075] With this configuration, even if the delay time generated in each of the communication devices 30A, 30B, and 30D present on the communication path between the control target device 10A to be controlled and the control device 20 changes, the IoT terminal control App21 can follow the change in the delay time and perform appropriate control of the control target device 10A in real time.

[0076] [Delay control system operation] The following describes an example of the operation of the delay control system 1. Fig. 6 is a flowchart showing the operation of the delay control system 1 in the first embodiment of the present invention. The operation of the delay control system 1 shown in the flowchart of Fig. 6 is started, for example, when the system is started.

[0077] Each of the plurality of communication devices 30 measures the processing time (delay time) of the communication processing executed by the communication device, for example, periodically (for example, every second) (step S001). Each time the plurality of communication devices 30 measures a delay time, it transmits delay information to the delay information collecting device 40 (step S002). As described above, the delay information includes the measured delay time and a route ID, which is identification information for identifying the communication device 30 that measured the delay time.

[0078] The delay information acquisition unit 411 of the delay information collection App 41 acquires delay information transmitted from each of the plurality of communication devices 30 (step S101). The delay information acquisition unit 411 stores the acquired delay information in the route delay information DB 412 (step S102).

[0079] The IoT terminal control app 21 of the control device 20 transmits a delay information request to the delay information collection app 41 of the delay information collection device 40 (step S201). As described above, the delay information request includes route information (e.g., identification information for identifying the control target device 10) for specifying a communication route between the control device 20 and the control target device 10 that is the target of control by the IoT terminal control app 21.

[0080] The delay information request receiving unit 414 of the delay information collection app 41 acquires the delay information request transmitted from the IoT terminal control app 21 of the control device 20 (step S103). The delay information request receiving unit 414 outputs the acquired route information to the route information conversion unit 415.

[0081] The route information conversion unit 415 acquires the route information output from the delay information request receiving unit 414. The route information conversion unit 415 refers to the route delay information DB 412 and identifies a communication route between the control target device 10 to be controlled by the IoT terminal control App 21 and the control device 20, which corresponds to the acquired route information (for example, identification information for identifying the control target device 10) (step S104). Then, the route information conversion unit 415 identifies route IDs corresponding to each range (communication device 30 in this embodiment) constituting the identified communication route (step S105). The route information conversion unit 415 outputs the identified one or more route IDs (route ID group) to the route delay information acquisition control unit 413.

[0082] The route delay information acquisition control unit 413 acquires the route ID group output from the route information conversion unit 415. The route delay information acquisition control unit 413 refers to the route delay information DB 412 and acquires the delay time associated with each of the route IDs included in the acquired route ID group (step S106). The route delay information acquisition control unit 413 outputs information indicating the delay time associated with each of the route IDs to the total route delay calculation unit 416.

[0083] The total route delay calculation unit 416 acquires information indicating multiple delay times (associated with each route ID) output from the route delay information acquisition control unit 413. The total route delay calculation unit 416 adds up the delay times indicated by each of the acquired information (step S107). The total route delay calculation unit 416 outputs delay information indicating the added up delay time (total delay information) to the delay information transmission unit 417.

[0084] The delay information transmission unit 417 acquires the delay information output from the route delay information acquisition control unit 413 or the total route delay calculation unit 416. The delay information transmission unit 417 transmits the acquired delay information to the IoT terminal control App 21 of the control device 20 (step S108).

[0085] The IoT terminal control app 21 of the control device 20 acquires the delay information transmitted from the delay information transmission unit 417 (step S202). Each time the IoT terminal control app 21 acquires the delay information, it configures the control algorithm executed by itself. Specifically, the IoT terminal control app 21 updates the delay information incorporated into the control algorithm each time new delay information is acquired (step S203). For example, the IoT terminal control app 21 updates the configuration of the control algorithm so that the delay time based on the acquired delay information is taken into account.

[0086] The IoT terminal control App 21 controls the control target device 10 according to a control algorithm that uses the updated delay information (step S204). With this, the operation of the delay control system 1 shown in the flowchart of FIG.

[0087] As described above, the delay control system 1 in the first embodiment of the present invention is a system in which the control device 20 remotely controls the control target device 10 such as an IoT terminal, taking into consideration delays that occur in the communication path. Generally, the control device 20 is a device managed by a user, and therefore does not have an interface that can directly communicate with the communication device 30 managed by a telecommunications carrier that exists in the communication path.

[0088] However, the delay control system 1 in the first embodiment of the present invention has a delay information collection device 40 that collects delay information from each communication device 30 instead of a device managed by a user. With this configuration, even if the control device 20 cannot directly communicate with a communication device 30 that exists on a communication path between the control device 20 and the control target device 10, the delay control system 1 in the first embodiment of the present invention can remotely control the control target device 10 while taking into account delays that occur on the communication path.

[0089] <Second embodiment> A delay control system 1a according to the second embodiment of the present invention will now be described.

[0090] In the delay control system 1 in the first embodiment described above, a case has been described in which each of the communication devices 30 is configured to voluntarily transmit delay information to the delay information collection device 40. In contrast, in the delay control system 1a in the second embodiment described below, the delay information collection app 41a first requests each of the communication devices 30 present on a communication path based on the path information specified by the IoT terminal control app 21 to transmit delay information. Then, each of the communication devices 30 transmits delay information to the delay information collection app 41a in response to the delay information transmission request.

[0091] That is, in the delay control system 1 in the first embodiment described above, delay information is transmitted from each of the communication devices 30 to the delay information collection App 41 by a push-type information transmission method. In contrast, in the delay control system 1a in the second embodiment described below, delay information is transmitted from each of the communication devices 30 to the delay information collection App 41a by a pull-type information transmission method in response to a request from the delay information collection App 41a.

[0092] With this configuration, the delay control system 1a in the second embodiment can be configured to, for example, acquire only the delay information of the necessary communication devices 30 at the necessary timing. As a result, the delay control system 1a in the second embodiment can, for example, reduce the storage capacity of the route delay information DB 412 and reduce the amount of communication between each of the communication devices 30 and the delay information collection device 40.

[0093] [Configuration of delay control system] The overall configuration diagram of the delay control system 1a in the second embodiment is similar to the overall configuration diagram of the delay control system 1 in the first embodiment shown in FIG. 1, and therefore a description thereof will be omitted.

[0094] [Configuration of the delay information collection app] The configuration of the delay information collection App 41a of the delay information collection device 40 of the delay control system 1a in the second embodiment will be described below. Fig. 7 is a block diagram showing the functional configuration of the delay information collection App 41a of the delay information collection device 40 in the second embodiment of the present invention.

[0095] As shown in Figure 7, the delay information collection App41a is composed of a delay information acquisition unit 411a, a route delay information DB 412, a route delay information acquisition control unit 413, a delay information request receiving unit 414, a route information conversion unit 415a, a total route delay calculation unit 416, a delay information transmission unit 417, and a delay information request unit 418.

[0096] As shown in FIG. 7, the configuration of the delay information collection App 41a in the second embodiment differs from the configuration of the delay information collection App 41 in the second embodiment described above in that a delay information request unit 418 has been added, and the delay information acquisition unit 411 and the route information conversion unit 415 have been changed to a delay information acquisition unit 411a and a route information conversion unit 415a, respectively.

[0097] The delay information request receiving unit 414 (route information acquiring unit) acquires a delay information request transmitted from the IoT terminal control app 21 of the control device 20. The delay information request includes route information for identifying a communication route between the control target device 10, which is the target of control by the IoT terminal control app 21, and the control device 20. The delay information request receiving unit 414 outputs the acquired route information to the route information converting unit 415a.

[0098] The path information may be any information as long as it is information that can identify a communication path between the control target device 10 and the control device 20. For example, if it is possible to identify a communication path based on identification information that identifies the control target device 10, such as an IP address or a MAC address, the path information may be identification information that identifies such a control target device 10.

[0099] The route information conversion unit 415a acquires the route information output from the delay information request receiving unit 414. Based on the acquired route information, the route information conversion unit 415a identifies a communication route between the control target device 10, which is the target of control by the IoT terminal control App 21, and the control device 20. Then, the route information conversion unit 415a identifies a route ID corresponding to each range constituting the identified communication route. The route ID is an identifier that indicates a specific range of the communication route between the control target device 10 and the control device 20.

[0100] As in the first embodiment, in the second embodiment, as described above, it is assumed that network delays occur only in the communication device 30, and therefore the path ID corresponds to an identifier that identifies the communication device 30. Therefore, in the second embodiment, the delay information collection App 41a can recognize network delays for each communication device 30.

[0101] The delay information collection App 41 acquires delay information in which a route ID is associated with a delay time, thereby being able to recognize network delay for each range of a communication route (for each communication device 30). The route information conversion unit 415a outputs the identified one or more route IDs (route ID group) to the route delay information acquisition control unit 413 and the delay information request unit 418.

[0102] The delay information request unit 418 acquires the group of route IDs output from the route information conversion unit 415a. The delay information request unit 418 identifies one or more route IDs (e.g., identification information for identifying a communication device 30) included in the acquired group of route IDs. The delay information request unit 418 transmits delay information requests to one or more communication devices 30 corresponding to the identified route IDs, respectively.

[0103] The delay information request here refers to control information that requests the communication device 30 to return delay information including the delay time (that is, the time required for the communication process performed by the communication device 30).

[0104] The delay information acquisition unit 411a acquires delay information transmitted from one or more communication devices 30 in response to a delay information request transmitted from the delay information request unit 418. The delay information transmitted from the communication device 30 includes information indicating a delay time and a route ID. The delay information acquisition unit 411a stores the acquired delay information, in which the information indicating the delay time is associated with the route ID, in the route delay information DB 412.

[0105] The route delay information acquisition control unit 413 acquires the route ID group output from the route information conversion unit 415a. The route delay information acquisition control unit 413 refers to the route delay information DB 412 and acquires information indicating the delay time associated with each of the route IDs included in the acquired route ID group.

[0106] The delay information acquisition unit 411a may directly output delay information in which the acquired delay times are associated with the route IDs to the route delay information acquisition control unit 413. In this case, the route delay information acquisition control unit 413 acquires information indicative of delay times associated with each of the route IDs included in the acquired route ID group, based on the information indicative of delay times and the route IDs acquired from the delay information acquisition unit 411a.

[0107] It should be noted that whether the route delay information acquisition control unit 413 acquires the delay information from the route delay information DB 412 or the delay information acquisition unit 411a may be determined, for example, in response to a request from the IoT terminal control App 21 of the control device 20. For example, if the request from the IoT terminal control App 21 requires more real-time performance, it is preferable to acquire the delay information directly from the delay information acquisition unit 411a, and otherwise acquire the delay information from the route delay information DB 412.

[0108] If the group of route IDs acquired from the route information conversion unit 415a includes multiple route IDs (i.e., if there are multiple communication devices 30 on the communication path between the control target device 10 that is the target of control by the IoT terminal control App 21 and the control device 20), the route delay information acquisition control unit 413 outputs information indicating the delay time associated with each of the route IDs to the total route delay calculation unit 416.

[0109] Furthermore, when the group of route IDs acquired from the route information conversion unit 415a includes only one route ID (i.e., when only one communication device 30 exists on the communication path between the control target device 10, which is the target of control by the IoT terminal control App 21, and the control device 20), the route delay information acquisition control unit 413 outputs information indicating the delay time associated with the route ID to the delay information transmission unit 417. Alternatively, when there is a request from the control device 20 to transmit the delay information to the IoT terminal control App 21 of the control device 20 without adding up the delay information, the route delay information acquisition control unit 413 outputs the delay information associated with the route ID to the delay information transmission unit 417.

[0110] The total route delay calculation unit 416 acquires information indicating multiple delay times (associated with each route ID) output from the route delay information acquisition control unit 413. The total route delay calculation unit 416 adds up the delay times indicated by each of the acquired information. The total route delay calculation unit 416 outputs delay information indicating the added up delay time (total delay information) to the delay information transmission unit 417.

[0111] The delay information transmission unit 417 (total delay information transmission unit) acquires information indicating the delay time output from the route delay information acquisition control unit 413 or the total route delay calculation unit 416. The delay information transmission unit 417 transmits the acquired delay information indicating the delay time to the IoT terminal control App 21 of the control device 20.

[0112] The IoT terminal control application 21 acquires the delay information transmitted from the delay information transmission unit 417. Each time the IoT terminal control application 21 acquires the delay information, it configures the control algorithm executed by the IoT terminal control application 21. Specifically, the IoT terminal control application 21 updates the delay information incorporated into the control algorithm each time new delay information is acquired sequentially. For example, the IoT terminal control application 21 updates the configuration of the control algorithm so that the delay time based on the acquired delay information is taken into account.

[0113] With this configuration, even if the delay time generated in each of the communication devices 30 present on the communication path between the control target device 10 to be controlled and the control device 20 changes, the IoT terminal control App 21 can follow the change in the delay time and execute appropriate control in real time for each control target device 10 to be controlled.

[0114] [Delay control system operation] An example of the operation of the delay control system 1a will be described below. Fig. 8 is a flowchart showing the operation of the delay control system 1a in the second embodiment of the present invention. The operation of the delay control system 1a shown in the flowchart of Fig. 8 starts, for example, when the IoT terminal control app 21 of the control device 20 sends a delay information request to the delay information collection app 21a of the delay information collection device 40.

[0115] The IoT terminal control app 21 of the control device 20 transmits a delay information request to the delay information collection app 41 of the delay information collection device 40 (step S501). As described above, the delay information request includes route information (e.g., identification information for identifying the control target device 10) for specifying a communication route between the control device 20 and the control target device 10 that is the target of control by the IoT terminal control app 21.

[0116] The delay information request receiving unit 414 of the delay information collection app 41a acquires a delay information request transmitted from the IoT terminal control app 21 of the control device 20 (step S301). The delay information request receiving unit 414 outputs the acquired route information to the route information conversion unit 415a. The route information conversion unit 415a acquires the route information output from the delay information request receiving unit 414.

[0117] The route information conversion unit 415a acquires the route information output from the delay information request receiving unit 414. The route information conversion unit 415a identifies a communication route between the control target device 10, which is to be controlled by the IoT terminal control App 21, and the control device 20 based on the acquired route information (step S402). Then, the route information conversion unit 415a identifies route IDs corresponding to each range constituting the identified communication route (step S403). As described above, a route ID is an identifier indicating a specific range (communication device 30 in this embodiment) of the communication route between the control target device 10 and the control device 20. The route information conversion unit 415a outputs the identified one or more route IDs (route ID group) to the route delay information acquisition control unit 413 and the delay information requesting unit 418.

[0118] The delay information request unit 418 acquires the group of route IDs output from the route information conversion unit 415a. The delay information request unit 418 identifies one or more route IDs (e.g., identification information for identifying a communication device 30) included in the acquired group of route IDs. The delay information request unit 418 transmits delay information requests to one or more communication devices 30 corresponding to the identified route IDs (step S404).

[0119] Each of the communication devices 30 acquires delay request information transmitted from the delay information collection App 41a of the delay information collection device 40 (step S301). Each of the communication devices 30 measures the processing time (delay time) of the communication processing executed by its own communication device (step S302). Each of the multiple communication devices 30 transmits delay information including the measured delay time to the delay information collection device 40 (step S303). As described above, the delay information includes the measured delay time and a route ID that identifies the communication device 30 that measured the delay time.

[0120] In the present embodiment, the communication device 30 is configured to measure the delay time after acquiring the delay request information transmitted from the delay information collection App 41a of the delay information collection device 40 as described above, but the present invention is not limited to this configuration. For example, the communication device 30 may be configured to periodically measure the delay time and immediately transmit the latest delay time to the delay information collection device 40 in response to acquiring the delay request information.

[0121] The delay information acquisition unit 411a acquires delay information transmitted from one or more communication devices 30 in response to the delay information request transmitted from the delay information request unit 418 (step S405). The delay information transmitted from the communication device 30 includes information indicating a delay time and a route ID. The delay information acquisition unit 411a stores the acquired delay information in association with the route ID in the route delay information DB 412 (step S406).

[0122] The route delay information acquisition control unit 413 acquires the route ID group output from the route information conversion unit 415a. The route delay information acquisition control unit 413 refers to the route delay information DB 412 and acquires information indicating the delay time associated with each of the route IDs included in the acquired route ID group (step S407). The route delay information acquisition control unit 413 outputs the information indicating the delay time associated with each of the route IDs to the total route delay calculation unit 416.

[0123] The total route delay calculation unit 416 acquires information indicating multiple delay times (associated with each route ID) output from the route delay information acquisition control unit 413. The total route delay calculation unit 416 adds up the delay times indicated by each of the acquired information (step S408). The total route delay calculation unit 416 outputs delay information indicating the added up delay time (total delay information) to the delay information transmission unit 417.

[0124] The delay information transmission unit 417 acquires information indicating the delay time output from the route delay information acquisition control unit 413 or the total route delay calculation unit 416. The delay information transmission unit 417 transmits the acquired delay information indicating the delay time to the IoT terminal control App 21 of the control device 20 (step S409).

[0125] The IoT terminal control app 21 of the control device 20 acquires the delay information transmitted from the delay information transmission unit 417 (step S502). Each time the IoT terminal control app 21 acquires the delay information, it configures the control algorithm executed by its own IoT terminal control app 21. Specifically, the IoT terminal control app 21 updates the delay information incorporated into the control algorithm each time new delay information is acquired (step S503). For example, the IoT terminal control app 21 updates the configuration of the control algorithm so that the delay time based on the acquired delay information is taken into account.

[0126] The IoT terminal control App 21 controls the control target device 10 according to a control algorithm that uses the updated delay information (step S504). With this, the operation of the delay control system 1a shown in the flowchart of FIG.

[0127] As described above, the delay control system 1a in the second embodiment of the present invention is a system in which the control device 20 remotely controls the control target device 10 such as an IoT terminal, taking into consideration delays that occur on a communication path. Generally, the control device 20 is a device managed by a user, and therefore does not have an interface that can directly communicate with the communication device 30 managed by a telecommunications carrier that exists on the communication path.

[0128] However, the delay control system 1a in the second embodiment of the present invention has a delay information collection device 40 that collects delay information from each communication device 30 instead of a device managed by a user. With this configuration, even if the control device 20 cannot directly communicate with a communication device 30 that exists on a communication path between the control device 20 and the control target device 10, the delay control system 1a in the second embodiment of the present invention can remotely control the control target device 10 while taking into account delays that occur on the communication path.

[0129] Furthermore, in the delay control system 1a according to the second embodiment of the present invention, delay information is transmitted from each of the communication devices 30 to the delay information collection app 41a by pull-type information transmission in response to a request from the delay information collection app 41a. With this configuration, the delay control system 1a according to the second embodiment of the present invention can be configured to, for example, acquire only the delay information of the necessary communication devices 30 at the necessary timing. As a result, the delay control system 1a according to the second embodiment can, for example, reduce the storage capacity of the route delay information DB 412 and reduce the amount of communication between each of the communication devices 30 and the delay information collection app 40.

[0130] <Third embodiment> The delay control system 1 according to the third embodiment of the present invention will be described below.

[0131] In the delay control system 1 in the first embodiment and the delay control system 1a in the second embodiment described above, the path ID corresponds to identification information that identifies the communication device 30, and therefore it can be said that the delay information is managed in units of devices (communication devices 30). In contrast, the delay control system in the third embodiment described below is configured to manage delay information in units of sections between devices (on the communication path).

[0132] [Configuration of delay control system] The overall configuration diagram of the delay control system in the third embodiment is similar to the overall configuration diagram of the delay control system 1 in the first embodiment shown in FIG. 1, and therefore a description thereof will be omitted.

[0133] [Configuration of the delay information collection app] The configuration of the delay information collection App 41b of the delay information collection device 40 in the third embodiment can be basically the same as the configuration of the delay information collection App 41 in the first embodiment shown in Fig. 2 or the configuration of the delay information collection App 41a in the second embodiment shown in Fig. 7. Therefore, a description of the basic configuration of the third delay information collection App 41b will be omitted, and the following description will focus on the extent to which the configuration differs from the first and second embodiments.

[0134] Hereinafter, a specific example will be given to explain the process of collecting delay information by the delay information collection App 41b of the delay information collection device 40 in the third embodiment. Fig. 9 is a diagram showing an example of the configuration of a communication network and a delay control system.

[0135] As shown in Fig. 9, the IoT terminal control App 21 can control the control target device 10A and the control target device 10B. Also, as shown in Fig. 3, communication devices 30A to 30D exist on the communication paths between the IoT terminal control App 21 (control device 20) and the control target device 10A and the control target device 10B.

[0136] 9, the control target device 10A and the control target device 10B are connected to the communication device 30A. The communication device 30A is connected to the communication device 30B and the communication device 30C. The communication device 30B and the communication device 30C are connected to the communication device 30D. The communication device 30D is connected to the IoT terminal control App 21 (control device 20) and the delay information collection App 41b (delay information collection device 40). The delay information collection App 41b includes a path delay information DB 412b.

[0137] Furthermore, identification information (route ID) is assigned to each section constituting the communication path between the IoT terminal control App 21 (control device 20) and the control target device 10A and the control target device 10B.

[0138] As shown in FIG. 9, the route ID assigned to the section between the control target device 10A and communication device 30A is "route A-1," the route ID assigned to the section between the control target device 10B and communication device 30A is "route A-2," the route ID assigned to the section between communication device 30A and communication device 30B is "route B," the route ID assigned to the section between communication device 30A and communication device 30C is "route C," the route ID assigned to the section between communication device 30B and communication device 30D is "route D-1," the route ID assigned to the section between communication device 30C and communication device 30D is "route D-2," and the route ID assigned to the section between communication device 30D and IoT terminal control App21 is "route D-3."

[0139] The alphabetic characters written following the character string "route" in the route ID indicate the communication device 30 that manages delay information indicating the delay time occurring on the route ID. Specifically, communication device 30A manages delay information indicating the delay time occurring in the "route A-1" section and the "route A-2" section of the communication route, communication device 30B manages delay information indicating the delay time occurring in the "route B" section of the communication route, communication device 30C manages delay information indicating the delay time occurring in the "route C" section of the communication route, and communication device 30D manages delay information indicating the delay time occurring in the "route D-1" section, the "route D-2" section, and the "route D-3" section.

[0140] The route delay information DB 412b stores in advance information (route information master) in which identification information for identifying the control target device 10 is associated with information (route ID group) for identifying each of one or more sections constituting a communication path between the control target device 10 and the control device 20. Here, it is assumed that the route information master is acquired in advance by, for example, another system (not shown) and stored in the route delay information DB 412b.

[0141] Fig. 10 is a diagram showing an example of a route information master stored in the route delay information DB 412b in the third embodiment of the present invention. As shown in Fig. 10, for example, identification information for identifying the control target device 10A (a character string "control target device 10A" in Fig. 10) is associated with a group of route IDs indicating communication routes of (control target device 10A)-"route A-1"-"route B"-"route D-1"-"route D-3". In Fig. 10, each of the character strings "route A-1", "route B", "route D-1", and "route D-3" is a route ID.

[0142] The route delay information DB 412b stores information in which a route ID, identification information of a communication device that manages the delay time of a delay that occurs in a section of a communication route to which the route ID is assigned, and the delay time are associated with each other. This delay information is sequentially acquired from each communication device 30 by the delay information collection App 41b and updated.

[0143] 11 is a diagram showing an example of delay information stored in the route delay information DB 412b in the first embodiment of the present invention. As shown in Fig. 11, for each route ID, identification information of the communication device 30 that manages the delay time and information indicating the delay time are associated with each other.

[0144] The information indicating the delay time is, for example, information indicating the delay time of a delay that occurs in a communication process executed by each communication device 30. As shown in FIG. 11, for example, a delay time of "10" is associated with a route ID of "route A-1." This indicates that the delay time (at that time) of the delay that occurs in the section of "route A-1" of the communication route is 10 (for example, 10 milliseconds). Also, as shown in FIG. 11, for example, a delay time of "3" is associated with a route ID of "communication device B." This indicates that the delay time (at that time) of the delay that occurs in the section of "route B" of the communication route is 3 (for example, 3 milliseconds).

[0145] In addition, delay information including delay times associated with the sections of "Route A-1" and "Route A-2" is transmitted from communication device 30A, which manages the delay times, to delay information collection App 41b and sequentially updated; delay information including delay times associated with the section of "Route B" is transmitted from communication device 30B, which manages the delay time, to delay information collection App 41b and sequentially updated; delay information including delay times associated with the section of "Route C" is transmitted from communication device 30C, which manages the delay time, to delay information collection App 41b and sequentially updated; and delay information including delay times associated with the sections of "Route D-1," "Route D-2," and "Route D-3" is transmitted from communication device 30D, which manages the delay time, to delay information collection App 41b and sequentially updated.

[0146] The flow of the delay information collection process will be described below. First, the IoT terminal control app 21 transmits route information including identification information for identifying the control target device 10 to be controlled to the delay information collection app 41. As an example, it is assumed here that the IoT terminal control app 21 transmits route information including identification information indicating the control target device 10A to the delay information collection app 41.

[0147] The delay information collection app 41b acquires route information transmitted from the IoT terminal control app 21. The delay information collection app 41b identifies identification information (that identifies the control target device 10) included in the acquired route information. The delay information collection app 41b refers to the route delay information DB 412b and acquires a group of route IDs corresponding to the identified identification information.

[0148] As described above, here, the identification information included in the route information is identification information that indicates the control target device 10A. The delay information collection App 41b acquires, for example, "(control target device 10A)-route A-1-route B-route D-1-route D-3," which is a route ID group corresponding to the control target device 10A, as shown in FIG.

[0149] Next, the delay information collection App 41b refers to the route delay information DB 412b and acquires information indicating the delay time corresponding to each of the route IDs included in the acquired route ID group. Specifically, the delay information collection App 41b acquires, for example, "10" which is the delay time value corresponding to "route A-1," "3" which is the delay time value corresponding to "route B," "6" which is the delay time value corresponding to "route D-1," and "9" which is the delay time value corresponding to "route D-3" as shown in FIG.

[0150] The delay information collection app 41b sums up the delay time values ​​included in the acquired delay information. Specifically, the delay information collection app 41b obtains the value "28" as the sum of the delay time values. The delay information collection app 41b transmits delay information indicating the summed delay time (total delay information) to the IoT terminal control app 21.

[0151] The IoT terminal control app 21 acquires the delay information transmitted from the delay information collection app 41b. The IoT terminal control app 21 updates the delay information incorporated in the control algorithm each time new delay information is acquired. Specifically, the IoT terminal control app 21 updates the setting of the control algorithm so that the control target device 10A is controlled taking into account the value of "28" (e.g., 28 milliseconds), which is the delay time indicated by the acquired delay information.

[0152] With this configuration, even if the delay time that occurs in each of the sections "route A-1", "route B", "route D-1", and "route D-3" that constitute the communication path between the control target device 10A to be controlled and the control device 20 changes, the IoT terminal control App21 can follow the change in the delay time and perform appropriate control of the control target device 10A in real time.

[0153] [Delay control system operation] The operation of the delay control system in the third embodiment can be basically the same as the operation of the delay control system 1 in the first embodiment shown in the flowchart of Fig. 6 or the operation of the delay control system 1a in the second embodiment shown in the flowchart of Fig. 8. Therefore, a description of the operation of the third delay control system will be omitted.

[0154] As described above, the delay control system according to the third embodiment of the present invention is a system in which the control device 20 remotely controls the control target device 10, such as an IoT terminal, taking into consideration delays that occur on a communication path. Generally, the control device 20 is a device managed by a user, and therefore does not have an interface that can directly connect and communicate with the communication device 30 managed by a telecommunications carrier that exists on the communication path.

[0155] However, the delay control system according to the third embodiment of the present invention has a delay information collection device 40 that collects delay information from each communication device 30 instead of a device managed by a user. With this configuration, even if the control device 20 cannot directly communicate with a communication device 30 that exists on a communication path between the control device 20 and the control target device 10, the delay control system according to the third embodiment of the present invention can remotely control the control target device 10 while taking into account delays that occur on the communication path.

[0156] Furthermore, the delay control system according to the third embodiment of the present invention is configured to manage delay information in units of sections between devices (on a communication path) rather than in units of communication device 30. With this configuration, the delay control system according to the third embodiment of the present invention can more easily allow the control device 20 to remotely control the control target device 10, such as an IoT terminal, by taking into consideration not only the delay time that occurs in the communication device 30 but also the delay time that occurs on the communication path between devices.

[0157] (Variation) Below, we will explain several variations of the network configuration (connection form) of the control target device 10, the communication device 30, the delay information collection App 41 (delay information collection device 40), and the IoT terminal control App 21 (control device 20). The network configurations explained below are applicable to any of the delay control systems in the first to third embodiments described above.

[0158] 12 to 20 are block diagrams each showing an example of a network configuration of a delay control system according to an embodiment of the present invention. In the following description, the control target device 10 is, for example, an IoT terminal such as a drone, a sensor, or an actuator. The control device 20 is, for example, an information processing device such as a general-purpose computer. The communication device 30 is, for example, communication equipment such as a wireless base station, a switch, an OLT, or an ONU. The delay information collection device 40 is, for example, an IoT terminal such as a sensor or an actuator. The control device 20 is, for example, an information processing device such as a general-purpose computer.

[0159] 12 shows an example of a network configuration in which a main signal and a network control signal (hereinafter referred to as a "NW control signal") transmitted and received between the control target device 10 and the IoT terminal control App 21 (control device 20) are transmitted over the same communication path. The network control signal here refers to, for example, delay information transmitted from the communication device 30 to the delay information collection App 41 (delay information collection device 40), and a delay information request transmitted from the delay information collection App 41 (delay information collection device 40) to the communication device 30.

[0160] 12 also shows a communication path when a delay information collection App 41 (delay information collection device 40) exists on the communication path between the control target device 10 and the IoT terminal control App 21 (control device 20). Therefore, in the network configuration shown in FIG. 12, the main signal transmitted and received between the control target device 10 and the control device 20 is transmitted and received via the delay information collection device 40.

[0161] The IoT terminal control app 21 and the delay information collection app 41 may be applications executed in the same device. That is, the control device 20 and the delay information collection device 40 may be integrated into one device.

[0162] FIG. 12 also shows a network configuration in which only one communication device 30 exists on the communication path between the control target device 10 and the IoT terminal control App 21 (control device 20).

[0163] 13, a plurality of communication devices 30 may exist on the communication path between the control target device 10 and the delay information collection App 41 (delay information collection device 40). When a plurality of communication devices 30 exists on the communication path between the control target device 10 and the delay information collection device 40, for example, the control target device 10 and the delay information collection device 40 may be connected via a core network.

[0164] Furthermore, as in the network configuration shown in FIG. 14, a communication device 30 may be present on the communication path between the IoT terminal control App 21 (control device 20) and the delay information collection App 41 (delay information collection device 40).

[0165] 15, multiple communication devices 30 may exist not only on the communication path between the control target device 10 and the delay information collection App 41 (delay information collection device 40) but also on the communication path between the IoT terminal control App 21 (control device 20) and the delay information collection App 41 (delay information collection device 40). When multiple communication devices 30 exist on the communication path between the control device 20 and the delay information collection device 40, for example, the control device 20 and the delay information collection device 40 may be connected via a core network.

[0166] 16 shows an example of a network configuration in which a main signal and a NW control signal transmitted and received between the control target device 10 and the IoT terminal control App 21 (control device 20) are transmitted over different communication paths. In the network configuration shown in FIG. 16, the delay information collection App 41 (delay information collection device 40) does not exist on the communication path between the control target device 10 and the IoT terminal control App 21 (control device 20). Therefore, in this case, the main signal transmitted and received between the control target device 10 and the control device 20 is transmitted and received without going through the delay information collection device 40.

[0167] FIG. 16 also shows a network configuration in which only one communication device 30 exists on the communication path between the control target device 10 and the IoT terminal control App 21 (control device 20).

[0168] 17, a plurality of communication devices 30 may exist on the communication path between the control target device 10 and the IoT terminal control App 21 (control device 20). When a plurality of communication devices 30 exists on the communication path between the control target device 10 and the control device 20, for example, the control target device 10 and the control device 20 may be connected via a core network.

[0169] 17 also shows a network configuration in which the delay information collection App 41 (delay information collection App 40) is communicatively connected to one communication device 30. Therefore, in the network configuration shown in Fig. 17, NW control signals transmitted from each communication device 30 to the delay information collection App 41 and NW control signals transmitted from the delay information collection App 41 to each communication device 30 are transmitted via one communication device 30 communicatively connected to the delay information collection App 41. Then, between the multiple communication devices 30, the NW control signals are transmitted via the same communication path as the main signal.

[0170] 18, the delay information collection App 41 (delay information collection App 40) and each of the plurality of communication devices 30 may be directly connected for communication. In the network configuration shown in FIG. 18, the NW control signal transmitted from each of the communication devices 30 to the delay information collection App 41 and the NW control signal transmitted from the delay information collection App 41 to each of the communication devices 30 are transmitted directly without passing through other devices. Therefore, in the network configuration shown in FIG. 18, the main signal transmitted between the control target device 10 and the IoT terminal control App 21 (control device 20) and the NW control signal transmitted between the delay information collection App 41 (delay information collection device 40) and each of the communication devices 30 are all transmitted via different communication paths.

[0171] Furthermore, as in the network configuration shown in FIG. 19, a communication device 30 may be present on the communication path between the IoT terminal control App 21 (control device 20) and the delay information collection App 41 (delay information collection device 40).

[0172] 20, multiple communication devices 30 may exist not only on the communication path between the control target device 10 and the IoT terminal control App 21 (control device 20) but also on the communication path between the IoT terminal control App 21 (control device 20) and the delay information collection App 41 (delay information collection device 40). When multiple communication devices 30 exist on the communication path between the control device 20 and the delay information collection device 40, for example, the control device 20 and the delay information collection device 40 may be connected via a core network.

[0173] 18, the network configuration shown in FIG. 20 is configured such that the delay information collection App 41 (delay information collection App 40) and each of the plurality of communication devices 30 are directly connected for communication.

[0174] According to the above-described embodiment, the delay information collecting device includes a route information acquiring unit, a delay information acquiring unit, and a delay information transmitting unit. For example, the delay information collecting device is the delay information collecting device 40 in the embodiment, the route information acquiring unit is the delay information request receiving unit 414 in the embodiment, the delay information acquiring unit is the delay information acquiring unit 411 and the delay information acquiring unit 411a in the embodiment, and the delay information transmitting unit is the delay information transmitting unit 417 in the embodiment.

[0175] The above-mentioned path information acquisition unit acquires path information regarding a communication path between a control target device and a control device. For example, the control target device is control target device 10 in the embodiment, and the control device is control device 20 in the embodiment. The above-mentioned delay information acquisition unit acquires delay information indicating a communication delay time occurring on the communication path from one or more communication devices present on the communication path. For example, the communication device is communication device 30 in the embodiment. The above-mentioned delay information transmission unit transmits total delay information indicating a sum of delay times based on the delay information acquired by the delay information acquisition unit to a control device that controls the control target device based on the total delay information.

[0176] The path information may include identification information for identifying the control target device. In this case, the delay information acquisition unit may acquire delay information from one or more communication devices located between the control target device identified by the identification information and the control device.

[0177] The delay information collecting device may further include a delay information requesting unit. For example, the delay information requesting unit is the delay information requesting unit 418 in the embodiment. In this case, the delay information requesting unit may transmit a request to transmit delay information to the communication device.

[0178] The delay time may include the processing time of the processing executed by the communication device.

[0179] The delay time may be a time indicating a delay occurring in a specific section of a communication path managed by a communication device.

[0180] According to the above-described embodiment, the delay control system includes a control device and a delay information collecting device. For example, the delay control system is the delay control system 1 and the delay control system 1a in the embodiment, the control device is the control device 20 in the embodiment, and the delay information collecting device is the delay information collecting device 40 in the embodiment.

[0181] The control device includes a route information transmitter, a total delay information acquirer, and a controller. The route information transmitter transmits route information relating to a communication route between the control target device to be controlled and the control device itself to the delay information collector. The total delay information acquirer acquires total delay information indicating the total communication delay time occurring on the communication route from the delay information collector. The controller controls the control target device based on the total delay information acquired by the total delay information acquirer.

[0182] The delay information collecting device includes a route information acquiring unit, a delay information acquiring unit, and a total delay information transmitting unit. For example, the route information acquiring unit is the delay information request receiving unit 414 in the embodiment, the delay information acquiring unit is the delay information acquiring unit 411 and the delay information acquiring unit 411a in the embodiment, and the total delay information transmitting unit is the delay information transmitting unit 417 in the embodiment.

[0183] The route information acquisition unit acquires route information transmitted from the control device. The delay information acquisition unit acquires delay information indicating delay times from one or more communication devices present on the communication path. For example, the communication device is communication device 30 in the embodiment. The total delay information transmission unit transmits total delay information indicating the sum of delay times based on the delay information acquired by the delay information acquisition unit to the control device.

[0184] The control target device 10, the control device 20, the communication device 30, and the delay information collecting device 40 in the above-described embodiments may be partially implemented by a computer. In this case, a program for implementing this function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be loaded into a computer system and executed. Note that the term "computer system" here includes hardware such as an OS and peripheral devices. Furthermore, the term "computer-readable recording medium" refers to portable media such as a flexible disk, optical magnetic disk, ROM, CD-ROM, and storage devices such as a hard disk built into a computer system.

[0185] Furthermore, the term "computer-readable recording medium" may include a medium that dynamically stores a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, or a medium that stores a program for a fixed period of time, such as a volatile memory within a computer system that serves as a server or client in such a case. The program may also be one that realizes part of the above-mentioned functions, or one that can realize the above-mentioned functions in combination with a program already stored in the computer system, or one that can be realized using a programmable logic device such as an FPGA (Field Programmable Gate Array).

[0186] Although an embodiment of the present invention has been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and includes designs within the scope of the gist of the present invention. [Explanation of symbols]

[0187] 1, 1a... delay control system, 10, 10A, 10B... control target device, 20... control device, 21... IoT terminal control application, 30, 30-1, 30-2, 30A, 30B, 30C, 30D... communication device, 40... delay information collection device, 41... delay information collection application, 411, 411a... delay information acquisition unit, 412... route delay information database, 413... route delay information acquisition control unit, 414... delay information request receiving unit, 415, 415a... route information conversion unit, 416... total route delay calculation unit, 417... delay information transmission unit, 418... delay information request unit

Claims

1. a route information acquisition unit that acquires route information regarding a communication route between the control target device and the control device; a delay information acquisition unit that acquires delay information indicating a communication delay time occurring on the communication path from one or more communication devices that are present on the communication path and relay communication between the control target device and the control device via a path that is different from the communication path and directly connects to each of the communication devices; a delay information storage unit that stores the delay information acquired by the delay information acquisition unit; a delay information transmitting unit that determines whether to acquire the delay information from the delay information acquiring unit or the delay information storing unit in response to a request from the control device, and transmits total delay information indicating the total of the delay times based on the acquired delay information to the control device that controls the control target device based on the total delay information; A delay information collection device comprising:

2. the path information includes identification information for identifying the control target device, The delay information acquisition unit acquires the delay information from the one or more communication devices present between the control target device identified by the identification information and the control device. The delay information collecting device according to claim 1 .

3. a delay information request unit that transmits a request to transmit the delay information to the communication device; The delay information collecting device according to claim 1 or 2, further comprising:

4. The delay time includes a processing time of a process executed by the communication device. The delay information collecting device according to claim 1 or 2.

5. The delay time is a time indicating a delay occurring in a specific section of the communication path managed by the communication device. The delay information collecting device according to claim 1 or 2.

6. A delay control system having a control device and a delay information collecting device, The control device a route information transmitting unit that transmits route information regarding a communication route between a control target device to be controlled and the control target device itself to the delay information collecting device; a total delay information acquisition unit that acquires total delay information indicating a total delay time of communication occurring on the communication path from the delay information collection device; a control unit that controls the control target device based on the total delay information acquired by the total delay information acquisition unit; Equipped with The delay information collecting device a route information acquisition unit that acquires route information transmitted from the control device; a delay information acquisition unit that acquires delay information indicating the delay time from one or more communication devices that are present on the communication path and relay communication between the control target device and the control device via a path that is different from the communication path and directly connects to each of the communication devices; a delay information storage unit that stores the delay information acquired by the delay information acquisition unit; a total delay information transmission unit that determines whether to acquire the delay information from the delay information acquisition unit or the delay information storage unit in response to a request from the control device, and transmits the total delay information indicating the total of the delay times based on the acquired delay information to the control device; and Equipped with Delay control system.

7. A delay information collection method by a computer of a delay information collection device, a path information acquisition step of acquiring path information regarding a communication path between the control target device and the control device; a delay information acquisition step of acquiring delay information indicating a communication delay time occurring on the communication path from one or more communication devices that are present on the communication path and relay communication between the control target device and the control device via a path that is different from the communication path and directly connects to each of the communication devices; a delay information storage step of storing the delay information acquired by the delay information acquisition step; a delay information transmitting step of determining whether to acquire the delay information acquired by the delay information acquiring step or the delay information stored by the delay information storing step in response to a request from the control device, and transmitting total delay information indicating the total of the delay times based on the acquired delay information to the control device that controls the controlled device based on the total delay information; A delayed information collection method having:

8. On the computer, a path information acquisition step of acquiring path information regarding a communication path between the control target device and the control device; a delay information acquisition step of acquiring delay information indicating a communication delay time occurring on the communication path from one or more communication devices that are present on the communication path and relay communication between the control target device and the control device via a path that is different from the communication path and directly connects to each of the communication devices; a delay information storage step of storing the delay information acquired by the delay information acquisition step; a delay information transmitting step of determining whether to acquire the delay information acquired by the delay information acquiring step or the delay information stored by the delay information storing step in response to a request from the control device, and transmitting total delay information indicating the total of the delay times based on the acquired delay information to the control device that controls the controlled device based on the total delay information; A program to execute.

Images