COMMUNICATION CONTROL DEVICE, COMMUNICATION SYSTEM, COMMUNICATION CONTROL METHOD, AND PROGRAM

JPWO2025004379A1Active Publication Date: 2025-01-02MITSUBISHI ELECTRIC CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2023561787
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-06-30
Publication Date
2025-01-02
Estimated Expiration
2043-06-30

AI Technical Summary

Technical Problem

In a network environment where multiple ECHONET devices are connected to the same LAN, simultaneous responses to individual identification information acquisition requests can lead to missed responses if the in-home device management device does not process them quickly enough, resulting in unmanaged devices.

Method used

A communication control device that prioritizes message acquisition processes based on multicast or broadcast transmission requests, ensuring all device messages are acquired without omission by executing them ahead of other processes.

Benefits of technology

This approach allows for complete management of devices connected to the local network by ensuring all device messages are obtained, preventing the loss of critical information and enabling effective device management.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader

Abstract

The communication control device (1) includes a message acquisition unit (111) that acquires a device message generated by the device (3) via a local network based on the UDP protocol, a transmission request determination unit (118) that determines whether transmission request information requesting the device (3) to transmit a device message is to be multicast or broadcast to the device (3), and a processing order management unit (119) that, when it is determined that the transmission request information is to be multicast or broadcast to the device (3), causes a message acquisition process for acquiring the device message to be executed in priority over other processes among a plurality of processes that are executed sequentially to relay information transmitted and received between the device (3) and the cloud server (2).
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a communication control device, a communication system, a communication control method, and a program. [Background technology]

[0002] A home device management device has been proposed that manages ECHONET devices, which are devices compliant with the ECHONET (registered trademark) standard, via a network (see, for example, Patent Document 1). This home device management device periodically multicasts a request to acquire predetermined individual identification information that identifies the ECHONET device to the ECHONET devices connected to the network, receives individual identification information acquisition responses from each ECHONET device connected to the network, and manages the individual identification information included in the received individual identification information acquisition responses in association with the ECHONET addresses set in the ECHONET devices. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2008-172462 A Summary of the Invention [Problem to be solved by the invention]

[0004] Incidentally, when a home appliance management apparatus as described in Patent Document 1 is connected to the same LAN (Local Area Network) as an ECHONET device, a connectionless communication protocol such as UDP (User Datagram Protocol) may be adopted as a communication protocol between the home appliance management apparatus and ECHONET, prioritizing communication speed. In this case, when multiple ECHONET devices are connected to the LAN, it is assumed that when the multiple ECHONET devices receive an individual identification information acquisition request at the same time, they transmit individual identification information acquisition responses to the home appliance management apparatus at the same timing. In this case, if the home appliance management apparatus does not have a sufficient speed for processing the individual identification information acquisition response, there is a risk that the individual identification information acquisition response will be missed. In addition, when a connectionless communication protocol is adopted, the home appliance management apparatus does not confirm the acquisition of the individual identification information acquisition response from the ECHONET device that is the sender of the individual identification information acquisition response, so that the ECHONET device that is the target of the missed acquisition may be left unmanaged without managing the individual identification information.

[0005] The present disclosure has been made in consideration of the above-mentioned reasons, and aims to provide a communication control device, a communication system, a communication control method, and a program that can appropriately manage devices connected to a network. [Means for solving the problem]

[0006] In order to achieve the above object, a communication control device according to the present disclosure includes: A communication control device that is connected to a local network to which devices are connected and is connected to a server via a wide area network, and that sequentially executes a plurality of processes for relaying information transmitted and received between the devices and the server, a message acquisition unit that acquires a device message generated by the device via the local network based on a connectionless communication protocol; a transmission request determination unit that determines whether or not transmission request information requesting the device to transmit the device message is to be multicast or broadcast to the device; and a processing order management unit that, when it is determined that the transmission request information is to be multicast or broadcast to the device, causes a message acquisition process for acquiring the device message among the plurality of processes to be executed in priority over other processes. Effect of the Invention

[0007] According to the present disclosure, the transmission request determination unit determines whether the transmission request information is multicast or broadcast to the devices, and when the processing order management unit determines that the transmission request information is multicast or broadcast to the devices, causes the message acquisition unit to execute a message acquisition process for acquiring device messages with priority. This allows the message acquisition process for acquiring device messages transmitted from the devices in response to the transmission request information multicast or broadcast to the devices to be executed with priority over other processes without waiting until the other processes are completed, so that all device messages can be acquired. This allows the devices connected to the local network to be properly managed. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a schematic configuration diagram of a communication system according to an embodiment of the present disclosure. [Diagram 2] FIG. 1 is a block diagram showing a hardware configuration of a communication system according to an embodiment. [Diagram 3] FIG. 1 is a block diagram showing a functional configuration of a communication system according to an embodiment. [Figure 4] FIG. 1 is a diagram showing an example of information stored in a device information storage unit of a cloud server according to an embodiment; [Figure 5A] FIG. 2 is an explanatory diagram of the operation of a thread processing unit according to an embodiment; [Figure 5B] An explanatory diagram of the operation of a transmission information generating unit according to an embodiment. [Figure 6] An explanatory diagram of the operation of a processing order management unit according to an embodiment [Figure 7] FIG. 1 is a sequence diagram showing an operation of a communication system according to an embodiment. [Figure 8] FIG. 1 is a sequence diagram showing an operation of a communication system according to an embodiment. [Figure 9] FIG. 1 is a sequence diagram showing an operation of a communication system according to an embodiment. [Figure 10] FIG. 1 is a sequence diagram showing an operation of a communication system according to an embodiment. [Figure 11] 1 is a flowchart showing an example of a flow of a communication control process executed by a communication control device according to an embodiment. [Figure 12] 1 is a flowchart showing an example of a flow of a communication control process executed by a communication control device according to an embodiment. [Figure 13] 1 is a flowchart showing an example of the flow of a device control process executed by a cloud server according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] A communication control device according to an embodiment of the present disclosure will be described below with reference to the accompanying drawings. The communication control device according to the present embodiment is connected to a local network to which devices are connected, and is connected to a server via a wide area network, and sequentially executes a plurality of processes for relaying information transmitted and received between the device and the server. The communication control device includes a message acquisition unit that acquires a device message generated by the device via the local network based on a connectionless communication protocol, a transmission request determination unit that determines whether transmission request information requesting the device to transmit the device message is to be multicast or broadcast to the device, and a processing order management unit that, when it is determined that the transmission request information is to be multicast or broadcast to the device, causes a message acquisition process for acquiring the device message among the plurality of processes to be executed in priority over other processes.

[0010] As shown in Fig. 1, the communication system according to the present embodiment includes a cloud server 2, a device 3 installed in a house, a communication control device 1 that transmits device messages generated by the device 3 to the cloud server 2, and a terminal device 4. The device 3, the communication control device 1, and the terminal device 4 are capable of communicating with each other via a local network NW2 such as a wireless LAN (Local Area Network). The cloud server 2 is also capable of communicating with a wide area network NW1 such as the Internet and a broadband router (hereinafter referred to as "BBR") 8. The device 3 is, for example, an air conditioner equipped with a wireless module, and communicates with the BBR 8, the communication control device 1, and the terminal device 4 via the local network NW2.

[0011] The device 3 is, for example, an air conditioner equipped with a wireless module, and communicates with the communication control device 1 or the terminal device 4 via the local network NW2 using communication middleware such as ECHONETLite (registered trademark). Here, the device 3 communicates with the communication control device 1 and the terminal device 4 based on a connectionless communication protocol, for example, by a communication protocol that employs UDP as a transport layer. When the device 3 acquires device status request information that requests the cloud server 2 to transmit device status information indicating the device's status transmitted from the communication control device 1, the device 3 generates device status information including status parameter information indicating the device 3's status and transmits it to the communication control device 1. When the device 3 acquires device identification information request information from the communication control device 1 or the terminal device 4 that requests the device 3 to transmit device identification information that identifies the device, the device 3 generates device identification information response information including the device identification information described above in response to the request and transmits it to the communication control device 1. Here, the device identification information request information is information including identification number information that identifies the device 3 in the application layer, and is, for example, an instance list request message that requests the device 3 to transmit an instance list notification message in the communication protocol of the ECHONETLite standard, or a Get message. Furthermore, the identification number information is, for example, information indicating a 16-byte identification number assigned to each device 3 in the ECHONET Lite standard. The device identification information response information is information including the MAC address information and IP address information of the device 3, and is, for example, an instance list notification message transmitted by multicast from the device 3 in the communications protocol of the ECHONET Lite standard. Furthermore, the device 3 operates based on control information transmitted from the communications control device 1.

[0012] In response to an operation by a user, the terminal device 4 generates device table update request information for requesting an update of device table information (described later) managed by the cloud server 2, and transmits the device table update request information to the cloud server 2 via the wide area network NW1. This device table update request information includes preset subnet information for identifying the local network NW2 to which the device 3 used by the user is connected. Assume that the user newly connects the device 3 to the local network NW2, and then performs a network initial connection operation on the terminal device 4 to register a combination of device identification information, IP address information, and MAC address information of the newly connected device 3 in the device table information managed by the cloud server 2. In this case, the terminal device 4 accepts the network initial connection operation, generates device table update request information for requesting an update of the device table information, and transmits the device table update request information to the cloud server 2.

[0013] The communication control device 1 sequentially executes a number of processes for relaying information transmitted and received between the device 3 and the cloud server 2. As shown in FIG. 2, the communication control device 1 includes a CPU (Central Processing Unit) 101, a main memory unit 102, an auxiliary memory unit 103, a communication unit 106, and a bus 109 connecting the various units. The main memory unit 102 is a volatile memory such as a RAM (Random Access Memory) and is used as a working area for the CPU 101. The auxiliary memory unit 103 has a non-volatile memory such as a semiconductor memory, functions as a ROM (Read Only Memory) and storage, and stores programs for implementing various functions of the communication control device 1. The communication unit 106 has, for example, a wireless module, and performs wireless communication with the device 3 and the BBR 8.

[0014] The CPU 101 loads the program stored in the auxiliary storage unit 103 into the main storage unit 102 and executes it, thereby functioning as a message acquisition unit 111, a transmission information generation unit 112, a thread processing unit 113, a format conversion unit 114, an information transmission unit 115, an information acquisition unit 116, a message transmission unit 117, a transmission request determination unit 118, and a processing order management unit 119, as shown in FIG. 3. Here, the format conversion unit 114, the information transmission unit 115, and the information acquisition unit 116 correspond to a transmission / reception task execution function unit APT in which the CPU 101 executes processing based on a communication protocol in an application layer such as MQTT (Message Queuing Telemetry Transport) and a transport layer such as TCP (Transmission Control Protocol). The thread processing unit 113 and the transmission information generation unit 112 execute processing based on a communication protocol in a transport layer such as UDP. The message acquisition unit 111 and the message transmission unit 117 execute processing based on a communication protocol below the data link layer. The CPU 101 executes these processes sequentially. 2 includes a received message buffer 121 for temporarily storing device messages transmitted from the device 3, a transmission information buffer 122 for temporarily storing transmission information to be transmitted to the cloud server 2, and a transmission message buffer 123, as shown in FIG. 3. The transmission message buffer 123 temporarily stores device messages to be transmitted to the device 3 connected to the local network NW2. The received message buffer 121 is configured as a ring buffer, and stores device messages that are not encrypted in the network layer. The auxiliary memory unit 103 includes an ARP table storage unit 131 for storing ARP table information indicating the correspondence between the MAC address information and the IP address information of the device 3 and the communication control device 1 connected to the local network NW2, as shown in FIG. 3.

[0015] The message acquisition unit 111 executes a message acquisition process to acquire, via the local network NW2, a device message based on UDP (User Datagram Protocol), a connectionless communication protocol, which is generated by the device 3 and transmitted from the device 3. This message acquisition process includes only processes based on protocols below the data link layer. Examples of the device message include the above-mentioned device identification information response information or the above-mentioned device status information. The message acquisition unit 111 then stores the acquired device message in the received message buffer 121. After storing the device message in the received message buffer 121, the message acquisition unit 111 notifies the thread processing unit 113 of pointer information indicating the storage position in the received message buffer 121.

[0016] The thread processing unit 113 executes a plurality of threads based on protocols belonging to the transport layer and network layer in the OSI basic reference model. The thread processing unit 113 executes a thread for identifying the processing in the application layer for each device message stored in the received message buffer 121 based on, for example, UDP, and a thread for checking the integrity of the device message by using a checksum. The thread processing unit 113 also executes a thread for transmitting and receiving a management packet for managing the connection state of the device 3 in the local network NW2 based on ICMP (Internet Control Message Protocol) and IGMP (Internet Group Management Protocol).

[0017] Furthermore, the thread processing unit 113 executes a thread for routing when transmitting the device message stored in the received message buffer 121 based on a communication protocol of the network layer in the OSI basic reference model, such as IPv4 (Internet Protocol version 4) or IPv6 (Internet Protocol version 6), or the Internet layer in the Internet Protocol Suite. Here, when the IP address information of the destination of the device message stored in the received message buffer 121 indicates an IP address assigned to the device 3 connected to the local network NW2, the thread processing unit 113 executes a thread for specifying a MAC address corresponding to the IP address by referring to the ARP table information stored in the ARP table storage unit 131. Then, the thread processing unit 113 executes a thread for adding the specified MAC address information to the device message stored in the received message buffer 121 and then storing the device message in the transmitted message buffer 123. Furthermore, when the IP address information of the destination of the device message stored in the received message buffer 121 indicates a multicast address or a broadcast address, the thread processing unit 113 executes a thread for identifying the MAC addresses corresponding to the respective IP addresses of all the devices 3 connected to the local network NW2, with reference to the APR table information stored in the ARP table storage unit 131. Then, the thread processing unit 113 executes a thread for generating a device message in which the identified MAC address information is added to the device message stored in the received message buffer 121, and for storing the generated device message in the transmitted message buffer 123. Furthermore, when the IP address information of the destination of the device message stored in the received message buffer 121 indicates an IP address assigned to the communication control device 1, the thread processing unit 113 executes a thread for identifying the IP address corresponding to the MAC address of the sender, with reference to the APR table information stored in the ARP table storage unit 131, and then generates various information in which the MAC address information and IP address information of the sender are added to the device message, and stores the information in the transmitted information buffer 122.5A, when the thread processing unit 113 executes the process of generating various types of information from the device message and storing it in the transmission information buffer 122, it usually generates various types of information to be transmitted to the cloud server 2 by executing multiple threads Th[0], Th[1], . . . , Th[i] (i is a positive integer) while accessing the device message stored in the received message buffer 121 based on the pointer information notified from the message acquisition unit 111. Then, the thread processing unit 113 stores the generated various types of information in the transmission information buffer 122.

[0018] Returning to FIG. 3, the transmission information generating unit 112 selects a device telegram including device identification information to be transmitted to the cloud server 2 from among the device telegrams stored in the received telegram buffer 121, based on the port number information included in the device telegram. Then, the transmission information generating unit 112 generates device information notification information including device identification information to be transmitted to the cloud server 2 using the selected device telegram, and stores the generated device information notification information in the transmission information buffer 122. This device information notification information is, for example, information having a format conforming to the ECHONET Lite standard. Here, as shown in FIG. 5B, the transmission information generating unit 112 selects a device telegram including port number information indicating a preset port number and device identification information from among the device telegrams stored in the received telegram buffer 121. Then, the transmission information generating unit 112 generates device information notification information in which source MAC address information and IP address information are added to the device telegram including the selected device identification information, and stores the generated device information notification information in the transmission information buffer 122. Here, the port number information is included in the UDP header and indicates a number assigned to execute a transmission process in the application layer to transmit various information to the cloud server 2. This port number information may indicate, for example, "3610" assigned to a process based on the ECHONETLite standard.

[0019] Returning to Fig. 3, the format conversion unit 114 converts the format of various information stored in the transmission information buffer 122. The format conversion unit 114 converts the format of the various information into, for example, a JSON format. The information transmission unit 115 performs an encapsulation process of adding header information for specifying the cloud server 2 as the transmission destination to the various information whose format has been converted by the format conversion unit 114. Then, the information transmission unit 115 transmits the encapsulated transmission information to the cloud server 2 based on the header information included in the transmission information.

[0020] When the information acquisition unit 116 acquires various information destined for the communication control device 1 and transmitted from the cloud server 2, it removes header information from the acquired information and then decapsulates it. The various information includes device status request information that requests the device 3 to transmit device status information indicating the status of the device 3, and control information for controlling the device 3. The information acquisition unit 116 then stores the extracted various information in the transmission message buffer 123. The message transmission unit 117 transmits the notified various information to the device 3 based on the MAC address information of the device 3 included in the various information stored in the transmission message buffer 123. Furthermore, when the information to be transmitted is device identification information request information, the message transmission unit 117 notifies the transmission request determination unit 118 of the device identification information request information.

[0021] The transmission request determination unit 118 determines whether the device identification information request information notified from the message transmitting unit 117 is to be multicast or broadcast to the device 3. If the destination IP address of the generated device identification information request information is set to a multicast address or broadcast address, the transmission request determination unit 118 determines that the device identification information request information is to be multicast or broadcast to the device 3. When the transmission request determination unit 118 determines that the device identification information request information is to be multicast or broadcast to the device 3, it notifies the processing order management unit 119 to that effect.

[0022] When the transmission request determination unit 118 determines that the device identification information request information is to be multicast or broadcast to the device 3, the processing order management unit 119 executes a message acquisition process for acquiring a device message in preference to other processes among a plurality of processes executed by the communication control device 1 to relay information transmitted and received between the device 3 and the cloud server 2. Specifically, when the transmission request determination unit 118 determines that the device identification information request information is to be multicast or broadcast to the device 3, the processing order management unit 119 prohibits the processing of the transmission and reception task execution function unit APT described above until a preset processing prohibition period ends. Specifically, when the transmission request determination unit 118 determines that the device identification information request information is to be multicast or broadcast to the device 3, the processing order management unit 119 prohibits the dispatch of the CPU 101 to the processing executed by the transmission and reception task execution function unit APT described above until a preset processing prohibition period ends. Here, the length of the processing prohibition period is set to, for example, 3 sec. Then, when the processing prohibition period has elapsed, the processing order management unit 119 again permits the processing of the transmission and reception task execution function unit APT. As shown in FIG. 6, the processing order management unit 119 normally dispatches the message acquisition process TA1, the transmission information generation process TA2 by the thread processing unit 113, and the transmission process TA3 to the CPU 101 in that order. Here, the transmission process TA3 corresponds to the process executed by the transmission and reception task execution function unit APT described above. Then, when the processing order management unit 119 acquires device identification information request information to be multicast or broadcast to the device 3, it prohibits the dispatch of the transmission information generation process TA2 and the transmission process TA3 to the CPU 101, and repeatedly dispatches the message acquisition process TA1 and the transmission information generation process TA4 by the transmission information generation unit 112 to the CPU 101. After that, when the processing prohibition period dT1 ends, the processing order management unit 119 dispatches the transmission process TA3 to the CPU 101. After that, the processing order management unit 119 again dispatches the message acquisition process TA1, the transmission information generation process TA2 by the thread processing unit 113, and the transmission process TA3 to the CPU 101 in that order.

[0023] Returning to FIG. 2, the cloud server 2 includes a CPU 201, a main memory unit 202, an auxiliary memory unit 203, a communication unit 206, a clock unit 207, and a bus 209 connecting the various units. The CPU 201 is, for example, a multi-core processor. The main memory unit 202 is a volatile memory and is used as a working area for the CPU 201. The auxiliary memory unit 203 has a non-volatile memory, functions as a ROM and storage, and stores programs for realizing various functions of the cloud server 2. The communication unit 206 communicates with the communication control device 1 via the wide area network NW1 and BBR8, and also communicates with the terminal device 4 via the wide area network NW1. The clock unit 207 has, for example, a real-time clock.

[0024] In the cloud server 2, the CPU 201 loads the program stored in the auxiliary storage unit 203 into the main storage unit 202 and executes it, thereby functioning as an information acquisition unit 211, a type determination unit 212, a device information update unit 213, a status acquisition unit 214, a control information generation unit 215, a transmission request unit 216, and an information transmission unit 217, as shown in FIG. 3. The auxiliary storage unit 203 shown in FIG. 2 also has a device information storage unit 231 and a status storage unit 232, as shown in FIG. 3. The device information storage unit 231 stores at least a combination of identification number information, MAC address information, and IP address information for identifying the device 3 in the application layer, in association with the IP address information of the communication control device 1. For example, as shown in FIG. 4, the device information storage unit 231 stores device table information consisting of identification number information, MAC address information, and IP address information of each device 3 connected to the local network NW2, in association with the IP address information of the communication control device 1 connected to the local network NW2. Here, the device table information is information that associates the identification number information of each device 3 with a combination of the MAC address information and IP address information of the device 3. The example shown in Fig. 4 indicates that a communication control device 1 with an IP address "192.168.32.x0" is connected to a local network NW2 indicated by subnet information "192.168.32.0 / 24". Returning to Fig. 3, the status storage unit 232 stores device status information indicating the status of the device 3 in association with the identification number information, MAC address information, and IP address information of the device 3.

[0025] When the information acquisition unit 211 acquires various information transmitted from the communication control device 1 or the terminal device 4, it notifies the type determination unit 212 of the acquired various information. The type determination unit 212 judges whether the information notified from the information acquisition unit 211 is device table information, device status information, or the above-mentioned device table update request information. Here, when the type determination unit 212 judges that the information notified from the information acquisition unit 211 is device table information, it notifies the device information update unit 213 of the device table information. Furthermore, when the type determination unit 212 judges that the information notified from the information acquisition unit 211 is the above-mentioned device status information, it notifies the status acquisition unit 214 of the device status information. Furthermore, when the type determination unit 212 judges that the information notified from the information acquisition unit 211 is device table update request information, it notifies the transmission request unit 216 of the device table update request information.

[0026] The device information update unit 213 updates the device table information stored in the device information storage unit 231 using the device table information notified from the type determination unit 212. The status acquisition unit 214 acquires device status information transmitted from the device 3 by transmitting, to the device 3, device status request information requesting the device 3 to transmit device status information. Specifically, the status acquisition unit 214 generates device status request information every time a preset device status acquisition time arrives, and notifies the information transmission unit 217 of the generated device status request information. Then, when the status acquisition unit 214 is notified of the device status information from the type determination unit 212, it updates the device status information stored in the status storage unit 232 using the notified device status information.

[0027] The control information generating unit 215 refers to the device status information stored in the status storage unit 232, and determines whether or not a control event has occurred that requires a change in the control content of the device 3, based on the state of the device 3 indicated by the device status information. Then, when the control information generating unit 215 determines that a control event has occurred, it generates control information for changing the control content of the device 3, and notifies the information transmitting unit 217 of the generated control information.

[0028] When the transmission request unit 216 is notified of the device table update request information by the type determination unit 212, it generates device identification information request information that requests the device 3 to transmit device identification information, and notifies the information transmission unit 217 of the generated device identification information request information. The IP address information included in this device identification information request information is set to a multicast address or a broadcast address. Here, the transmission request unit 216 also notifies the information transmission unit 217 of the subnet information included in the device table update request information. The transmission request unit 216 also determines whether or not a preset device identification information acquisition time has arrived based on the time measured by the clock unit 207, and when it is determined that the device identification information acquisition time has arrived, it also generates the above-mentioned device identification information request information and notifies the information transmission unit 217 of it.

[0029] When the information transmitting unit 217 is notified of various information from the status acquiring unit 214 and the control information generating unit 215, the information transmitting unit 217 specifies the communication control device 1 as the destination according to the notified various information. Here, the information transmitting unit 217 specifies the IP address information of the communication control device 1 associated with the combination of the device status request information, the MAC address information of the device 3 as the destination of the control information, and the IP address information stored in the device information storing unit 231. Then, the information transmitting unit 217 executes an encapsulation process of adding header information including the specified IP address information to the notified various information. Then, the information transmitting unit 217 transmits the encapsulated various information to the destination indicated by the specified IP address information. Also, when the information transmitting unit 217 is notified of the device identification information request information and the subnetwork information from the transmission request unit 216, the information transmitting unit 217 specifies the IP address information of the communication control device 1 associated with the notified subnetwork information stored in the device information storing unit 231. Then, the information transmitting unit 217 performs an encapsulation process of adding header information including the specified IP address information to the notified device identification information request information, and transmits it to the communication control device 1.

[0030] Next, the operation of the communication system according to the present embodiment will be described with reference to FIG. 7 to FIG. 10. Here, it is assumed that a process for establishing a connection has already been performed between the communication control device 1 and the cloud server 2, and that the communication control device 1 and the cloud server 2 have acquired each other's IP address information. First, as shown in FIG. 7, it is assumed that the user performs the above-mentioned network initial connection operation on the terminal device 4. In this case, the terminal device 4 generates device table update request information including subnet information of the local network NW2 to which the device 3 used by the user is connected (step S1), and the generated device table update request information is transmitted from the terminal device 4 to the cloud server 2 (step S2). On the other hand, when the cloud server 2 acquires the device table update request information, it generates device identification information request information in which the destination IP address is set to a multicast address or a broadcast address in response to the device table update request information (step S3). Next, the cloud server 2 executes an encapsulation process of adding header information including IP address information of the destination communication control device 1 to the generated device identification information request information (step S4), and the encapsulated device identification information request information is transmitted from the cloud server 2 to the communication control device 1 (step S5).

[0031] On the other hand, when the communication control device 1 acquires the device identification information request information, it executes a decapsulation process to remove the header information from the acquired device identification information request information (step S6). Next, it is assumed that the communication control device 1 determines that the destination IP address of the device identification information request information is a multicast address or a broadcast address (step S7). In this case, the communication control device 1 prohibits the CPU 101 from dispatching to the process executed by the transmission and reception task execution function unit APT described above (step S8). After that, the device identification information request information is transmitted by multicast transmission or broadcast transmission from the communication control device 1 to the device 3 (step S9).

[0032] On the other hand, when the device 3 acquires the device identification information request information, it generates device identification information response information including its own identification number information in response to the request (step S10). Next, the generated device identification information response information is transmitted from the device 3 to the communication control device 1 (step S11). On the other hand, when the communication control device 1 acquires the device identification information response information, it stores the acquired device identification information response information in the received message buffer 121 (step S12). Next, the communication control device 1 selects a device message to be transmitted to the cloud server 2 from the device messages stored in the received message buffer 121 based on the port number information included in the device message (step S13). After that, the communication control device 1 generates device information notification information including the device identification information included in the device message to be transmitted to the cloud server 2 using the selected device message, and stores the generated device information notification information in the transmission information buffer 122 (step S14). Thereafter, the communication control device 1 repeatedly executes a series of processes from steps S9 to S14 during the aforementioned processing prohibition period.

[0033] Next, as shown in FIG. 8, it is assumed that the communication control device 1 determines that the above-mentioned process inhibition period has ended (step S15). In this case, the communication control device 1 releases the inhibition of dispatching to the process executed by the transmission / reception task execution function unit APT for the CPU 101 (step S16). Next, the communication control device 1 converts the format of the device information notification information stored in the transmission information buffer 122 into, for example, a JSON format (step S17), and then performs an encapsulation process of adding header information for setting the destination to the cloud server 2 to the device information notification information (step S18). After that, the encapsulated device information notification information is transmitted from the communication control device 1 to the cloud server 2 (step S19). On the other hand, when the cloud server 2 acquires the device information notification information transmitted from the communication control device 1, the cloud server 2 stores the device information included in the acquired device information notification information in the device information storage unit 231 in association with the IP address information of the communication control device 1 that is the transmission source of the device information notification information (step S20).

[0034] Furthermore, when a preset time for obtaining device identification information arrives, the cloud server 2 generates device identification information request information (step S21), and the generated device identification information request information is transmitted from the cloud server 2 to the communication control device 1 based on preset subnet information (step S22). On the other hand, when the communication control device 1 obtains the device identification information request information, it executes a decapsulation process for removing header information from the obtained device identification information request information (step S6). Next, a series of processes from steps S7 to S20 are executed.

[0035] Also, as shown in FIG. 9, it is assumed that the time for acquiring the device status indicating the device status of a preset device 3 has arrived. In this case, the cloud server 2 generates device status request information requesting one preset device 3 to transmit device status information (step S23). Next, the cloud server 2 identifies the IP address information of the communication control device 1 associated with the IP address information of the device 3 to which the device status request information is to be transmitted, which is stored in the device information storage unit 231. Then, the cloud server 2 executes an encapsulation process for adding header information including the identified IP address information to the device status request information (step S24). After that, the encapsulated device status request information is transmitted from the cloud server 2 to the communication control device 1 (step S25). On the other hand, when the communication control device 1 acquires the device status request information transmitted from the cloud server 2, it executes a decapsulation process for removing the header information from the acquired device status request information (step S26). Next, the device status request information is transmitted by unicast from the communication control device 1 to the device 3 based on the MAC address information and IP address information of the device 3 included in the device status request information from which the header information has been removed (step S27).

[0036] On the other hand, when the device 3 acquires the device status request information, it generates device status information indicating its own status in response to the request (step S28). Next, the generated device status information is transmitted from the device 3 to the communication control device 1 (step S29). On the other hand, when the communication control device 1 acquires the device status information, it generates device status notification information including the acquired device status information (step S30) and executes an encapsulation process of adding header information for specifying the cloud server 2 as the destination to the generated device status notification information (step S31). Next, the encapsulated device status notification information is transmitted from the communication control device 1 to the cloud server 2 (step S32). On the other hand, when the cloud server 2 acquires the device status notification information transmitted from the communication control device 1, it extracts the device status information included in the acquired device status notification information and updates the device status information stored in the status storage unit 232 using the extracted device status information (step S33).

[0037] Furthermore, when the above-mentioned control event occurs, the cloud server 2 generates control information for changing the control content of the device 3 (step S34). After that, the cloud server 2 identifies the IP address information of the communication control device 1 associated with the IP address information of the device 3 to which the control information is to be transmitted, which is stored in the device information storage unit 231. Then, the cloud server 2 executes an encapsulation process for adding header information including the identified IP address information to the device status request information (step S35). Then, as shown in FIG. 10, the encapsulated control information is transmitted from the cloud server 2 to the communication control device 1 (step S36). On the other hand, when the communication control device 1 acquires the control information transmitted from the cloud server 2, it executes a decapsulation process for removing the header information from the acquired control information (step S37). After that, the control information is transmitted from the communication control device 1 to the device 3 based on the MAC address information and IP address information of the device 3 included in the control information (step S38). On the other hand, when the device 3 acquires the control information, it operates based on the acquired control information (step S39).

[0038] After that, it is assumed that an IP address update event occurs in which the IP address of the device 3 is updated. This IP address update event corresponds to, for example, a case where the DHCP function unit of the BBR 8 sets a lease time for the IP address assigned to each device 3, and the IP address assigned to each device 3 is released after the set lease time has elapsed. In this case, the cloud server 2 determines that the device table information stored in the device information storage unit 231 needs to be updated (step S40). Here, the cloud server 2 determines that the device table information needs to be updated if, after transmitting device status request information to the communication control device 1, the cloud server 2 does not acquire device status information transmitted from the communication control device 1 within a preset allowable response time, or if, after transmitting control information to the communication control device 1, the status of the corresponding device 3 stored in the status storage unit 232 does not reflect the transmitted control information after the elapse of the overhead time of the corresponding device 3, the cloud server 2 generates device identification information request information (step S41), and the generated device identification information request information is transmitted from the cloud server 2 to the communication control device 1 based on preset subnet information (step S42). On the other hand, when the communication control device 1 acquires the device identification information request information, it executes a decapsulation process to remove the header information from the acquired device identification information request information (step S6). Next, a series of processes from steps S7 to S20 are executed.

[0039] Next, the communication control process executed by the communication control device 1 according to the present embodiment will be described with reference to FIG. 11 and FIG. 12. This communication control process is started, for example, when the communication control device 1 is powered on and the communication control device 1 is placed in a location where it can be connected to the local network NW2. First, as shown in FIG. 11, the information acquisition unit 116 judges whether or not the above-mentioned device identification information request information has been acquired (step S101). Here, the information acquisition unit 116 acquires information transmitted from the cloud server 2, performs a decapsulation process on the acquired information, and then judges whether or not the acquired information is device identification information request information. Here, if the information acquisition unit 116 judges that the device identification information request information has not been acquired (step S101: No), the process of step S116 described later is executed. On the other hand, if the information acquisition unit 116 judges that the device identification information request information has been acquired (step S101: Yes), the transmission request judgment unit 118 judges whether or not the destination IP address of the acquired device identification information request information is set to a multicast address or a broadcast address (step S102). Here, when the transmission request determination unit 118 determines that the destination IP address is an IP address assigned to one device 3 (step S102: No), the message transmission unit 117 unicasts the acquired device identification information request information to the device 3 assigned with the IP address indicated by the destination IP address information included in the device identification information request information (step S103). As a result, the message acquisition unit 111 acquires device identification information response information transmitted from the device 3 to which the device identification information request information is transmitted, and stores the acquired device identification information response information in the received message buffer 121 (step S104). Next, the thread processing unit 113 executes various threads for routing when transmitting the device identification information response information stored in the received message buffer 121, based on the communication protocol of the network layer in the OSI basic reference model. As a result, the thread processing unit 113 generates device information notification information including the device identification information included in the device identification information response information and the MAC address information and IP address information of the transmission source, and stores the information in the transmission information buffer 122 (step S105).

[0040] Next, the format conversion unit 114 converts the format of the device information notification information stored in the transmission information buffer 122, and the information transmission unit 115 performs an encapsulation process of adding header information for specifying the cloud server 2 as the destination to the device information notification information whose format has been converted. Then, the information transmission unit 115 transmits the encapsulated transmission information to the cloud server 2 based on the header information included in the transmission information (step S106). Thereafter, the process of step S116 described below is executed.

[0041] On the other hand, it is assumed that the transmission request determination unit 118 determines in step S102 that the destination IP address of the acquired device identification information request information is set to a multicast address or a broadcast address (step S102: Yes). In this case, the processing order management unit 119 prohibits the CPU 101 from dispatching the acquired device identification information request information to be executed by the transmission and reception task execution function unit APT (step S107). Next, the message transmission unit 117 transmits the acquired device identification information request information by multicast or broadcast to all devices 3 connected to the local network NW2 (step S108). Next, the message acquisition unit 111 determines whether or not the device identification information response information transmitted from any of the devices 3 connected to the local network NW2 has been acquired (step S109). Here, if the message acquisition unit 111 determines that the device identification information response information has not been acquired (step S109: No), the processing of step S113 described later is executed. On the other hand, when the message acquisition unit 111 determines that it has acquired device identification information response information (step S109: Yes), it stores the acquired device identification information response information in the received message buffer 121 (step S110). After that, the transmission information generation unit 112 selects a device message including device identification information to be transmitted to the cloud server 2 from the device messages stored in the received message buffer 121 based on the port number information included in the device message (step S111). Next, the transmission information generation unit 112 generates device information notification information including device identification information to be transmitted to the cloud server 2 using the selected device message, and stores the generated device information notification information in the transmission information buffer 122 (step S112).

[0042] Next, the processing order management unit 119 judges whether or not a preset processing end period has ended (step S113). If the processing order management unit 119 judges that the processing end period has not yet ended (step S113: No), the processing of step S109 is executed again. On the other hand, if the processing order management unit 119 judges that the processing end period has ended (step S113: Yes), the processing order management unit 119 cancels the prohibition of dispatching to the CPU 101 to the processing executed by the transmission / reception task execution function unit APT (step S114). After that, the format conversion unit 114 converts the format of the device information notification information stored in the transmission information buffer 122, and the information transmission unit 115 performs an encapsulation process in which the format-converted device information notification information is added with header information for specifying the cloud server 2 as the transmission destination. Then, the information transmission unit 115 transmits the encapsulated transmission information to the cloud server 2 based on the header information included in the transmission information (step S115).

[0043] Next, as shown in FIG. 12, the message acquisition unit 111 judges whether or not the device status information transmitted from the device 3 has been acquired (step S116). If the message acquisition unit 111 judges that the device status information has not been acquired (step S116: No), the process of step S119 described later is executed. On the other hand, if the message acquisition unit 111 judges that the device status information has been acquired (step S116: Yes), the message acquisition unit 111 stores the acquired device status information in the received message buffer 121. Then, the thread processing unit 113 executes various threads for routing when transmitting the device status information stored in the received message buffer 121 based on the communication protocol of the network layer in the OSI basic reference model. As a result, the thread processing unit 113 generates device status notification information including the device status information and the MAC address information and IP address information of the transmission source of the device status information, and stores the information in the transmission information buffer 122 (step S117). Thereafter, format conversion unit 114 converts the format of the device status notification information stored in transmission information buffer 122, and information transmission unit 115 performs an encapsulation process in which the format-converted device status notification information is added with header information for specifying cloud server 2 as the destination. Then, information transmission unit 115 transmits the encapsulated transmission information to cloud server 2 based on the header information included in the transmission information (step S118).

[0044] Next, the information acquisition unit 116 judges whether or not the device status request information or the control information transmitted from the cloud server 2 has been acquired (step S119). If the information acquisition unit 116 judges that the device status request information and the control information have not been acquired (step S119: No), the process of step S101 is executed again. On the other hand, if the information acquisition unit 116 judges that the device status request information or the control information has been acquired (step S119: Yes), the information acquisition unit 116 performs a decapsulation process to remove header information from the acquired device status request information or the control information, and then stores the information in the transmission message buffer 123 (step S120). Next, the message transmission unit 117 transmits the device status request information or the control information stored in the transmission message buffer 123 to the device 3 (step S121). After that, the process of step S101 is executed again.

[0045] Next, the device control process executed by the cloud server 2 according to the present embodiment will be described with reference to FIG. 13. This device control process is started, for example, when a program for executing the device control process is started in the cloud server 2. First, the transmission request unit 216 determines whether or not the above-mentioned device identification information acquisition time has arrived based on time information indicating the time measured by the clock unit 207 (step S301). If the transmission request unit 216 determines that the device identification information acquisition time has arrived (step S301: Yes), the process of step S303 described below is executed. On the other hand, if the transmission request unit 216 determines that the device identification information acquisition time has not yet arrived (step S301: No), it determines whether or not the device table information needs to be updated (step S302). If the transmission request unit 216 determines that the device table information does not need to be updated (step S302: No), the process of step S305 described below is executed. On the other hand, when the transmission request unit 216 determines that the device table information needs to be updated (step S302: Yes), it generates the above-mentioned device identification information request information (step S303) and notifies the generated device identification information request information and subnet information to the information transmitting unit 217. Next, the information transmitting unit 217 identifies the IP address information of the communication control device 1 that is stored in the device information storage unit 231 and that is associated with the subnet information notified by the transmission request unit 216, and performs an encapsulation process of adding header information including the identified IP address information to the notified device identification information request information, and then transmits it to the communication control device 1 (step S304).

[0046] Next, the control information generating unit 215 refers to the device status information stored in the status storage unit 232, and judges whether or not a control event that requires a change in the control content of the device 3 has occurred based on the state of the device 3 indicated by the device status information (step S305). If the control information generating unit 215 judges that a control event has not occurred (step S305: No), the process of step S308 described later is executed. On the other hand, if the control information generating unit 215 judges that a control event has occurred (step S305: Yes), it generates control information for changing the control content of the device 3 (step S306). Thereafter, the information transmitting unit 217 identifies the IP address information of the communication control device 1 associated with the IP address information of the device 3 that is the destination of the device status request information stored in the device information storage unit 231, executes an encapsulation process of adding header information including the identified IP address information to the control information, and transmits the encapsulated control information to the communication control device 1 (step S307).

[0047] Next, the status acquisition unit 214 judges whether the above-mentioned device status acquisition time has arrived (step S308). If the status acquisition unit 214 judges that the device status acquisition time has not yet arrived (step S308: No), the process of step S311 described later is executed. On the other hand, if the status acquisition unit 214 judges that the device status acquisition time has arrived (step S308: Yes), the status acquisition unit 214 generates the above-mentioned device status request information (step S309). Next, the information transmission unit 217 identifies the IP address information of the communication control device 1 associated with the IP address information of the device 3 to which the device status request information is to be transmitted, which is stored in the device information storage unit 231, performs an encapsulation process of adding header information including the identified IP address information to the device status request information, and transmits the encapsulated device status request information to the communication control device 1 (step S310).

[0048] Next, the information acquisition unit 211 judges whether or not various information transmitted from the communication control device 1 has been acquired (step S311). Here, if the information acquisition unit 211 judges that various information transmitted from the communication control device 1 has not been acquired (step S311: No), the process of step S301 is executed again. On the other hand, if the information acquisition unit 211 judges that various information transmitted from the communication control device 1 has been acquired (step S311: Yes), it judges whether or not the acquired information is device information notification information (step S312). Here, if the type determination unit 212 judges that the information is device information notification information (step S312: Yes), it notifies the device information update unit 213 of the device information notification information. Then, the device information update unit 213 extracts the device information included in the notified device information notification information, and updates the device table information stored in the device information storage unit 231 using the extracted device information (step S313). Then, the process of step S301 is executed again.

[0049] On the other hand, if the type determination unit 212 determines that the acquired information is not device information notification information (step S312: No), it determines whether or not the acquired information is device status information (step S314). Here, if the type determination unit 212 determines that the acquired information is not device status information (step S314: No), the process of step S301 is executed again. On the other hand, if the type determination unit 212 determines that the acquired information is device status information (step S314: Yes), the status acquisition unit 214 uses the device status information to update the device status information of the device 3 stored in the status storage unit 232 (step S315). Thereafter, the process of step S301 is executed again.

[0050] As described above, according to the communication control device 1 of this embodiment, the transmission request determination unit 118 determines whether the transmission request information is multicast or broadcast to the device 3. Then, when the processing order management unit 119 determines that the transmission request information is multicast or broadcast to the device 3, it causes the message acquisition unit 111 to execute a message acquisition process for acquiring a device message with priority. As a result, the message acquisition for acquiring a device message transmitted from the device 3 in response to the transmission request information multicast or broadcast to the device 3 is executed with priority over other processes without waiting until the other processes are completed, so that the device identification information response information can be acquired without omission. Therefore, the devices 3 connected to the local network NW2 can be appropriately managed.

[0051] However, when the multicast-transmitted device identification information request information is acquired at the same time by a plurality of devices 3 connected to the local network NW2, the plurality of devices 3 may transmit device identification information response information at the same timing. In this case, if the communication control device 1 has insufficient capability for message acquisition processing, there is a risk that the device identification information response information may be missed. For this reason, there is a risk that the number of devices 3 connected to the local network NW2 may have to be limited. In contrast, in the communication system according to the present embodiment, the message acquisition processing for acquiring the device message transmitted from the device 3 is executed in priority to other processing without waiting until the completion of other processing, so that the device identification information response information transmitted from the device 3 can be stored without omission in the received message buffer 121, and thus the occurrence of problems due to the missed acquisition of the device identification information response information can be suppressed.

[0052] In addition, in the communication control device 1 according to the present embodiment, the transmission information generating unit 112 selects a device message to be transmitted to the cloud server 2 from the device messages stored in the received message buffer 121 based on the port number information included in the device message, and generates various information to be transmitted to the cloud server 2 using the selected device message. As a result, the transmission information generating unit 112 can generate device information notification information to be transmitted to the cloud server 2 from the device messages stored in the received message buffer 121 more quickly than the thread processing unit 113, and can generate device information notification information corresponding to the device identification information response information before the device identification information response information stored in the received message buffer 121 is overwritten by the newly acquired device identification information response information. Therefore, it is possible to generate device information notification information corresponding to all of the device identification information response information stored in the received message buffer 121. Therefore, it is possible to suppress the occurrence of a malfunction caused by some of the device information notification information to be transmitted to the cloud server 2 not being transmitted to the cloud server 2.

[0053] Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above-described embodiments. For example, the local network NW2 may be configured as a wired LAN.

[0054] In the embodiment, an example has been described in which the device information storage unit 231 stores the IP address information and MAC address information of the device 3 in association with the identification number information unique to the device 3. However, this is not limiting, and the device information storage unit 231 may store the IP address information and MAC address information of the device 3 in association with model name information indicating the model name of the device 3, serial number information indicating the serial number of the device 3, and the like.

[0055] In addition, the various functions of the communication control device 1 and the cloud server 2 according to the present disclosure may be realized by software, firmware, or a combination of software and firmware. In this case, the software or firmware may be written as a program, and the program may be stored and distributed in a computer-readable recording medium such as a flexible disk, a CD-ROM (Compact Disc Read Only Memory), a DVD (Digital Versatile Disc), an MO (Magneto-Optical Disc), or a flash memory, and the program may be read and installed in a computer to configure a computer capable of realizing each of the above-mentioned functions. In addition, when each function is realized by sharing the work between an OS (Operating System) and an application, or by cooperation between the OS and an application, only the parts other than the OS may be stored in the recording medium.

[0056] Furthermore, each program may be superimposed on a carrier wave and distributed via a communication network. For example, the program may be posted on a bulletin board (BBS, Bulletin Board System) on the communication network and distributed via the network. These programs may then be started and executed under the control of the OS in the same way as other application programs, thereby enabling the above-mentioned processing to be performed.

[0057] Various embodiments and modifications of the present disclosure are possible without departing from the broad spirit and scope of the present disclosure. The above-described embodiments are for explaining the present disclosure and do not limit the scope of the present disclosure. In other words, the scope of the present disclosure is indicated by the claims, not the embodiments. Various modifications made within the scope of the claims and within the scope of the disclosure equivalent thereto are considered to be within the scope of the present disclosure. [Industrial Applicability]

[0058] The present disclosure is suitable as a system for managing multiple devices installed in a home. [Explanation of symbols]

[0059] 1 Communication control device, 2 Cloud server, 3 Device, 4 Terminal device, 8 BBR, 101, 201 CPU, 102, 202 Main memory, 103, 203 Auxiliary memory, 106, 206 Communication unit, 109, 209 Bus, 111 Message acquisition unit, 112 Transmission information generation unit, 113 Thread processing unit, 114 Format conversion unit, 115, 217 Information transmission unit, 116, 211 Information acquisition unit, 117 Message transmission unit, 118 Transmission request determination unit, 119 Processing order management unit, 121 Received message buffer, 122 Transmission information buffer, 123 Transmitted message buffer, 131 ARP table storage unit, 207 Timer, 212 Type determination unit, 213 Device information update unit, 214 Status acquisition unit, 215 Control information generation unit, 216 Transmission request unit, 231 device information storage unit, 232 status storage unit, NW1 wide area network, NW2 local network

Claims

1. A communication control device that is connected to a local network to which devices are connected and is connected to a server via a wide area network, and that sequentially executes a plurality of processes for relaying information transmitted and received between the devices and the server, a message acquisition unit that acquires a device message generated by the device via the local network based on a connectionless communication protocol; a transmission request determination unit that determines whether or not transmission request information requesting the device to transmit the device message is to be multicast or broadcast to the device; a process order management unit that, when it is determined that the transmission request information is to be multicast or broadcast to the device, causes a process of acquiring the device message among the plurality of processes to be executed in priority over other processes. Communications control device.

2. The message acquisition process includes a plurality of threads based on a protocol belonging to a transport layer or lower in the OSI Reference Model. The communication control device according to claim 1 .

3. a received message buffer for temporarily storing the device message acquired via the local network and not encrypted at a network layer; a transmission information generating unit that selects the device telegram to be transmitted to the server from the device telegrams stored in the received telegram buffer based on port number information included in the device telegram, and generates transmission information to be transmitted to the server using the selected device telegram. The communication control device according to claim 1 or 2.

4. The message acquisition process includes only processes based on protocols belonging to the data link layer or lower. The communication control device according to claim 3.

5. The device message includes a User Datagram Protocol (UDP) header, The port number information included in the UDP header indicates a number assigned to execute a transmission process for transmitting the transmission information to the server in an application layer. The communication control device according to claim 3.

6. A server; a communication control device connected to a local network to which devices are connected and connected to the server via a wide area network, the communication control device sequentially executing a plurality of processes for relaying information transmitted and received between the devices and the server; The server, a transmission request unit that transmits, to the communication control device, transmission request information that requests the device to transmit a device message generated by the device; The communication control device includes: a message acquisition unit that acquires a device message generated by the device via the local network based on a connectionless communication protocol; a transmission request determination unit that determines whether the transmission request information is to be multicast or broadcast to the device; a processing order management unit that, when it is determined that the transmission request information is to be multicast or broadcast to the device, causes a message acquisition process for acquiring the device message among the plurality of processes to be executed in priority over other processes. Communication systems.

7. A communication control method executed by a communication control device that is connected to a local network to which devices are connected and is connected to a server via a wide area network, and that sequentially executes a plurality of processes for relaying information transmitted and received between the devices and the server, comprising: acquiring a device message generated by the device via the local network based on a connectionless communication protocol; transmitting, to the communication control device, transmission request information for requesting the device to transmit the device message; determining whether the request-to-send information is multicast or broadcast to the devices; and when it is determined that the transmission request information is to be multicast or broadcast to the device, executing a message acquisition process for acquiring the device message among the plurality of processes in preference to other processes. Communications control method.

8. Computer, a message acquisition unit that acquires a device message generated by the device via a local network to which the device is connected based on a connectionless communication protocol; a transmission request determination unit that determines whether or not transmission request information requesting the device to transmit the device message is to be multicast or broadcast to the device; a processing order management unit that, when it is determined that the transmission request information is to be multicast or broadcast to the device, executes a message acquisition process for acquiring the device message among a plurality of processes that are sequentially executed to relay information transmitted and received between the device and a server in priority to other processes; A program to function as a