Data collection system
The data collection system addresses the challenge of excessive metadata transmission by using a control device to regulate terminal metadata transmission, reducing load and power consumption while ensuring efficient data collection and management in IoT systems.
Patent Information
- Application Number
- PCT/JP2023/017691
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-11
- Publication Date
- 2024-11-14
AI Technical Summary
In IoT data collection systems, there is a challenge in controlling excessive metadata transmission from terminals to management servers, which can lead to increased load and power consumption, especially when multiple metadata sources are present.
A data collection system that includes a control device and terminal, where the control device transmits control details to the terminal using a communication protocol, allowing the terminal to control its metadata transmission based on predefined control information, thereby regulating the amount and frequency of metadata sent to the management server.
This solution enables controlled metadata transmission, reducing the load and power consumption of terminals while ensuring efficient data collection and management, allowing for optimized network configuration and device information acquisition.
Smart Images

Figure JP2023017691_14112024_PF_FP_ABST
Abstract
Description
Data Collection System
[0001] The present disclosure relates to a control technique for an IoT terminal.
[0002] Network configuration information and device information of terminals and devices are acquired using a standardized, lightweight communication protocol that does not require high performance. For example, Non-Patent Document 1 reports a method using LLDP (Link Layer Discovery Protocol; see Non-Patent Document 3, for example).
[0003] In the Internet of Things (IoT), it is necessary to connect numerous sensor terminals to a network and collect the data (sensing data) they generate. Furthermore, in data utilization in the IoT, it has been reported that not only the sensing data itself generated by the sensor terminals but also data related to the sensing data, known as metadata, is important (see, for example, Non-Patent Document 2). It is expected that users will be able to safely and easily utilize the sensing data by acquiring and distributing both the sensing data and the metadata. For example, by using the LLDP disclosed in Non-Patent Document 1, it is possible to collect metadata (device information) related to the sensing data, such as manufacturer name and model number, with an economical system configuration.
[0004] The more metadata sources that provide metadata, the more metadata can be collected. However, if the transmission of metadata is not controlled for each terminal, there is a possibility that a terminal may transmit an excessive amount of metadata at an excessive frequency. Therefore, it is desirable to be able to control the data transmission from terminals to the management server.
[0005] Yoshiyuki Mihara, Takefumi Yamazaki, Manabu Okamoto, and Atsushi Sato, "Design of Home Network Mapping Protocol HTIP and Its Application to Diagnostic Tools," Transactions of the Information Processing Society of Japan, Consumer Devices & Systems, Vol. 2, No. 3, pp. 34-45, December 2012. Toshihiko Oda, Hiroshi Imai, Takeshi Naito, and Hajime Takebayashi, "A Method for Defining, Generating, and Utilizing Metadata in the Sensing Data Distribution Market," 2018 Annual Conference of the Japanese Society for Artificial Intelligence (32nd), June 2012. IEEE 802.1AB-2016 (LLDP) "Revised Third Edition 802.11 High-Speed Wireless LAN Textbook," Impress Publishing.
[0006] The present disclosure aims to enable control of data transmission from a terminal in a data collection system that collects metadata obtained by the terminal in a management server.
[0007] A data information system according to the present disclosure is a data collection system that collects metadata obtained by a terminal into a management server, and includes a control device, the control device including a signal transmission unit that transmits control content to the terminal using a region defined by a communication protocol that can be received by the terminal.
[0008] The terminal of the present disclosure includes a signal receiving unit that receives a signal of a predetermined communication protocol, and a control unit that controls the terminal itself in accordance with the control content described in the field defined by the communication protocol. This allows the terminal to receive the signal of the communication protocol transmitted from the control device and control the terminal itself in accordance with the control content described in the field defined by the communication protocol.
[0009] Here, the predetermined area can be any area that can be processed by the terminal. For example, the predetermined area is an extended area defined in Layer 2. The control device may be provided in the management server, or in a network device connected between the terminal and the management server.
[0010] The management server may generate control information for controlling at least one of the plurality of terminals based on metadata from the plurality of terminals, and in this case, the control device may transmit control content to the terminal based on the control information generated by the management server.
[0011] The control device and terminal of the present disclosure each execute the method of the present disclosure. For example, the control device executes a signal transmission procedure for transmitting control content to the terminal using a field defined by a communication protocol that the terminal can receive. The terminal also executes a signal reception procedure for receiving a signal of a predetermined communication protocol and a control procedure for controlling the terminal in accordance with the control content described in the field defined by the communication protocol.
[0012] The device of the present invention can also be realized by a computer and a program, and the program can be recorded on a recording medium or provided via a network. The program of the present disclosure is a program for causing a computer to realize each function of the device according to the present disclosure, and a program for causing a computer to execute each procedure of the method executed by the device according to the present disclosure.
[0013] The above disclosures can be combined as much as possible.
[0014] According to the present disclosure, in a data collection system that collects metadata obtained by a terminal in a management server, it is possible to control data transmission from the terminal.
[0015] 1 is an example of a system configuration of the present disclosure; FIG. 2 is an example of a terminal configuration; FIG. 3 is an example of a management server configuration; FIG. 4 is a diagram illustrating a frame transmitted from a terminal to a management server; FIG. 5 is a diagram illustrating an example of a metadata collection sequence when n BLE beacons are arranged around a terminal; FIG. 6 is an example of a system configuration of the present disclosure; FIG. 7 is an example of a control device configuration; FIG. 8 is an example of a terminal configuration; FIG. 9 is an example of a control sequence to a terminal; FIG. 10 is an example of a control sequence to a terminal;
[0016] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. Note that the present disclosure is not limited to the embodiments shown below. These implementation examples are merely illustrative, and the present disclosure can be implemented in various forms with various modifications and improvements based on the knowledge of those skilled in the art. Note that components with the same reference numerals in this specification and drawings indicate the same components.
[0017] First Embodiment In this embodiment, the basic configuration of a data collection system will be described. Fig. 1 is a diagram illustrating a data collection system 301 of this embodiment. The data collection system 301 is a data collection system that performs communication from a terminal 11 to a network device 12 by utilizing an extended area of a standardized communication protocol (such as LLDP, HTIP, or IEEE 802.11), and is characterized in that the terminal 11 stores sensing data detected by a sensor device in an area within a frame defined by the communication protocol that is different from an area for storing metadata, and transmits the data to the network device 12, the network device 12 transfers the frame to a management server 13, and the management server 13 associates the sensing data with the metadata and stores them based on information identifying the terminal 11 written in the frame.
[0018] The data collection network 15 is a network that connects the terminals 11 located within a specific range to the management server 13. The data collection network 15 is, for example, a local area network (LAN), a field area network (FAN), an IoT area network, etc. There are cases where multiple terminals 11 of the same type exist within the same data collection network 15, and cases where multiple types of terminals 11 exist within the same data collection network 15.
[0019] FIG. 2 is a diagram illustrating the terminal 11. The terminal 11 is, for example, an IoT sensor terminal, which senses an observation target and generates sensing data. The terminal 11 includes a sensor device 11a, a sensing data storage processing unit 11b, a device information storage processing unit 11c, a communication protocol operation unit 11d, a metadata detection unit (11e), and a 1 , 11e 2 , 11e3 , ...), and a metadata processing unit 11f.
[0020] The sensor device 11a senses the observation target and acquires sensing data (main data). The sensing data may be, for example, temperature, images, acceleration, sound, light, CO2, etc. The device information storage processing unit 11c collects device information about the observation target (for example, the device manufacturer name, model name, model number, etc.) and stores the information in a predetermined position in the frame (an area that can be used for unique purposes, such as an "extension area" or "optional area" specified by the communication protocol).
[0021] The sensing data storage processing unit 11b stores the sensing data from the sensor device 11a in a predetermined position of the frame (such as the payload portion defined by the communication protocol). The sensing data storage processing unit 11b may process the sensing data before storing it in the frame, for example, by converting it into a certain shortened code or by dividing it into multiple frames and storing them (fragmentation), so that the data conforms to the format / restrictions of the unique extension area of the frame.
[0022] The sensing data storage processing unit 11b can arbitrarily set the timing for storing the sensing data in the frame. For example, the storage timing can be set each time the sensing data is updated, or the sensing data can be stored not sequentially but after it has been accumulated for a certain period of time. Furthermore, when the sensing data has been accumulated for a certain period of time, the sensing data storage processing unit 11b can store a record (log) of the sensing data or the results of specific calculations / statistical processing in the frame.
[0023] The type of sensing data stored in the frame and the storage timing may be fixed or variable. The type of sensing data and the storage timing may be dynamically changed at the discretion of the terminal 11 itself or in response to an instruction from the management server 13. The frame transmission cycle may also be fixed or variable. The frame transmission cycle may be dynamically changed at the discretion of the terminal 11 itself or in response to an instruction from the management server 13.
[0024] The metadata detection unit 11e acquires information (metadata) other than device information. The information other than device information includes, for example, location information of the detection target, time information, information about people, things, or events, and other information. However, the information other than device information in the present invention is not limited to these. In order to acquire this information, the metadata detection unit 11e uses the location information detection unit 11e 1 , time detection unit 11e 2 , person, object, and event detection unit 11e 3 , and other detection units.
[0025] Position information detection unit 11e 1 is, for example, a GPS, an acceleration sensor, a gyro sensor, or an RSSI receiver for a Wi-Fi signal or a BLE (Bluetooth Low Energy) beacon signal. 1 The location metadata detected by is information about location obtained from GPS signals, BLE beacon signals, wireless communication radio wave information, non-communication radio wave information (television, radio, radio clock, other noise, etc.), power information, visible light information, sound wave information, vibration information, acceleration information, and other location metadata sources.
[0026] Time detection unit 11e 2 is an information receiver from, for example, GPS and NTP (Network Time Protocol). 2 The time metadata detected by is information about time obtained from GPS signals, information from NTP, and other time metadata sources.
[0027] Person, object, and event detection unit 11e 3 is a receiver that receives information from, for example, a BLE beacon (carried by a person), a smartphone carried by a person, or information from image analysis results. 3 The person, object, or event metadata detected by the is information about the person, object, or event obtained from a BLE beacon carried by the person, information from a smartphone carried by the person, information from image analysis results, and other current event metadata sources.
[0028] Other metadata detected by the detection unit includes information about the network configuration of the data collection network 15 .
[0029] The metadata detection unit 11e may detect all of the multiple detection targets, or may detect any one of them.
[0030] The metadata processing unit 11f stores the data detected by the metadata detection unit 11e as metadata in an extension area or an optional area within the frame set by the communication protocol. For example, the metadata processing unit 11f can store metadata in a control frame of an IEEE 804.11 wireless LAN. Specifically, the metadata processing unit 11f stores various types of metadata in a "Vendor Specific" area, which is an extension area of a Probe Request frame. Alternatively, the metadata processing unit 11f stores various types of metadata in a "Vendor Specific" area, which is an extension area of a Probe Response frame.
[0031] The metadata processing unit 11f may process the metadata and then store it in the frame, such as by converting it into a shortened code and storing it, or by dividing it and storing it in multiple frames (fragmentation), so that it conforms to the format / restrictions of the frame's unique extension area.
[0032] The metadata processing unit 11f can arbitrarily set the timing for storing metadata in a frame. For example, the storage timing can be set each time the metadata is updated, or the metadata can be stored after it has been accumulated for a certain period of time rather than sequentially. Furthermore, when the metadata processing unit 11f has accumulated metadata for a certain period of time, it can store a record (log) of the metadata or the results of specific calculations or statistical processing in the frame.
[0033] The type of metadata stored in a frame and the timing of storage may be fixed or variable. The type of metadata and the timing of storage may be dynamically changed at the discretion of the terminal 11 itself or in response to an instruction from the management server 13.
[0034] The communication protocol operation unit 11d transmits a frame, in which sensing data and device information are stored in a predetermined area and metadata is stored in an extension area or an optional area, to the network device 12 using a lightweight, standardized communication protocol such as LLDP or HTIP (Home Network Topology Identifying Protocol). Note that the communication protocol of the frame in which the sensing data is stored and the communication protocol of the frame in which the device information is stored may be the same or different. In the latter case, the metadata processing unit 11f may store the metadata in a frame of one of the communication protocols (the frame in which the sensing data is stored or the frame in which the device information is stored) or in frames of both communication protocols (the frame in which the sensing data is stored and the frame in which the device information is stored).
[0035] Furthermore, the terminal 11 also has a function of operating in accordance with instructions from the management server 13, etc. Specifically, when the terminal 11 changes the BLE beacon signal or metadata information (information to be transmitted, radio wave intensity, transmission frequency, etc.) transmitted by the terminal itself in accordance with instructions from the management server 13, the terminal 11 transmits the information to the outside. When transmitting information using the same communication protocol as that for communication with the network device 12, the terminal 11 operates the communication protocol operation unit 11d.
[0036] The terminal 11 may also be a beacon signal source for other terminals to grasp metadata. For example, the terminal 11 may be a beacon signal source for identifying location metadata, or may be a beacon terminal carried by a worker to identify nearby people.
[0037] The network device 12 is, for example, a network switch, a wireless access point, a wireless repeater, or the like. The network device 12 transmits frames uploaded from the lower-level data collection network 15 to the management server 13 as they are. The network device 12 may also have a metadata processing unit (metadata detection unit 11e and metadata processing unit 11f) that the terminal 11 has. Even if the network device 12 does not have the sensor device 11a, it can add metadata, such as its own unique information (e.g., MAC address) and connection port, to frames sent from the terminal 11 and forward them to the management server 13. If the network device 12 has a metadata processing unit, it can grasp the logical connection from the management server 13 to the terminal 11, thereby creating a more accurate logical / physical network management map. In other words, even if the network device 12 is a network switch (switching hub) or a wireless repeater that does not have layer 3 or higher functionality, the present technology operates at layer 2, making it possible to manage and grasp the connections between network devices, including the network device 12.
[0038] 3 is a diagram illustrating the management server 13. The management server 13 has a communication protocol operation unit 13a, an information processing unit 13b, and an information storage unit 13c. The management server 13 extracts information from frames passed from the network device 12, stores the information, and provides it for analysis. In particular, the management server 13 is characterized by having a function to store a combination of two or more pieces of collected information in the information storage unit 13c.
[0039] The communication protocol operation unit 13a receives frames containing sensing data and metadata from the terminal 11 or the network device 12. The information processing unit 12b extracts the following sensing data, device information, and metadata from the received frames and organizes them in the information storage unit 13c based on information identifying the individual terminal 11 (e.g., MAC address): (1) Physical information of the terminal (such as characteristics of the housing, image information, information on attached labels, what the worker is pointing at, and what the worker is looking at), (2) Identifiers of terminals on the logical network (such as MAC address and UUID), (3) Primary data (sensing data such as temperature, image, acceleration, sound, light, and CO2), and (4) Various metadata (such as data on location, time, people, objects, and events). For example, the management server 13 references metadata related to a location and stores primary data acquired at the same location or within a certain area in the format of [location metadata, primary data].
[0040] A supplementary note on location metadata: Like GPS information, there are cases where the information is directly set as location metadata at the time of sensing by the terminal 11. On the other hand, there are also cases where, like signals from BLE beacons, visible light, or sound information, it is not determined whether the information is location information at the time of sensing by the terminal 11 and transmitting it as metadata, and the management server 13 recognizes / understands the metadata as location metadata.
[0041] FIG. 4 is a diagram illustrating a frame 41 transmitted from the terminal 11 to the management server 13. The network device 12 is not shown in FIG. 4. The frame 41 is a Layer 2 communication frame such as an Ethernet (registered trademark) frame or a Wi-Fi communication frame. The frame 41 is composed of a logical identifier 41a of the communication device such as a MAC address, a source or destination identifier 41b such as an IP address, an area 41c in which sensing data such as temperature and images is stored, and an extension area 41d in which metadata is stored. Of these, the identifier 41b and area 41c form a Layer 3 communication packet.
[0042] For example, the management server 13 combines the MAC address of the logical identifier 41a with the location metadata of the extension area 41d to form [MAC address, location metadata], and combines the MAC address of the logical identifier 41a with the installer metadata of the extension area 41d to form [MAC address, installer metadata], and organizes them in the information storage unit 13c.
[0043] In this way, the data collection system 301 can acquire network configuration information, device information, sensing data, and metadata of terminals and devices using a communication protocol that does not require high performance.
[0044] Second Embodiment The terminal 11 is provided with a plurality of metadata detection units 11e, and a large amount of metadata is collected in the terminal 11. Fig. 5 shows an example of a metadata collection sequence when n BLE beacons 16 are arranged around the terminal 11. The metadata detection unit 11e provided in the terminal 11 receives n BLE advertisement signals by scanning BLE beacon signals (S111). The metadata processing unit 11f stores the metadata obtained from the BLE advertisement signals in an extension area of a Probe Request frame (S112). The communication protocol operation unit 11d 1 The access point 12A receives the Probe Request frame (S121) and updates the database that lists the identification information of the BLE beacons 16 that the terminal 11 can detect (S122).
[0045] The access point 12A transmits the metadata information received from the terminal 11 to the management server 13 (S123). For example, the access point 12A transmits the metadata information received from the terminal 11 using an extension area in a Layer 2 communication frame.
[0046] The more metadata sources there are around the terminal 11, the more diverse metadata the management server 13 can collect. On the other hand, if n BLE beacons 16 are arranged around the terminal 11, the terminal 11 may transmit metadata from n BLE beacons 16. The BLE beacons 16 are not the only metadata source around the terminal 11. Therefore, unless metadata transmission is controlled for each terminal 11, the terminal 11 may transmit an excessive amount of metadata to the management server 13 at an excessive frequency.
[0047] Therefore, the data collection system of this embodiment controls the terminal 11 so that the data amount and transmission frequency of the metadata are appropriate, thereby making it possible to reduce the load and power consumption of the terminal 11.
[0048] 6 shows an example of a system configuration of this embodiment. In a data collection system 301 of this embodiment, the network device 12 is an access point 12A, and the system includes a control device 14 that controls the terminal 11. The control device 14 may be integrated with the management server 13 and the access point 12A, or may be an independent device. For example, the access point 12A, control device 14, and management server 13 may be physically located in the same device.
[0049] 7 shows an example configuration of the control device 14. The control device 14 includes an information processing unit 42, a communication protocol operation unit 43, and an information storage unit 44. The communication protocol operation unit 43 receives control information from the management server 13 and stores it in the information storage unit 44. The information processing unit 42 generates control content for each terminal 11 based on the control information stored in the information storage unit 44. The communication protocol operation unit 43 transmits a frame to the terminal 11 that describes the control content for the terminal 11. Here, any communication protocol can be used when transmitting control information from the management server 13 to the control device 14.
[0050] The communication protocol operation unit 43 functions as the "signal transmission unit" of the present disclosure, and transmits control content to the terminal 11 using a predetermined area in a frame of a communication protocol that can be received by the terminal 11. Specifically, the communication protocol operation unit 43 reads out control information stored in the information storage unit 44, stores the control content to the terminal 11 in an extension area 41d of a Layer 2 communication frame defined by the communication protocol as shown in Fig. 4, and transmits a Probe Response frame to the terminal 11. For example, if the communication protocol is IEEE802.11, the extension area 41d is an extension area for the Probe Response.
[0051] Here, the control device 14 may store information indicating the destination in a predetermined area of the extension area of the Probe Response frame so that the destination of the control content can be determined in the terminal 11. For example, if the control signal is a BLE advertisement signal, a logical identifier such as the MAC address of the destination device may be stored in the first 6 bytes of the extension area 41d.
[0052] FIG. 8 shows a configuration example of the terminal 11 of this embodiment. In this embodiment, the communication protocol operation unit 11d functions as the "signal receiving unit" of the present disclosure. The communication protocol operation unit 11d receives a signal of a predetermined communication protocol. The predetermined communication protocol can be any communication protocol that can be received by the terminal 11. In this embodiment, an example will be described in which the communication protocol operation unit 11d receives a Probe Response frame defined by IEEE 802.11.
[0053] The terminal 11 of this embodiment includes a downstream signal information processing unit 11g that functions as the "control unit" of the present disclosure. The downstream signal information processing unit 11g is a functional unit that processes information received by the communication protocol operation unit 11d. In this embodiment, the downstream signal information processing unit 11g controls its own device in accordance with the control content described in the extension field defined in the Probe Response frame.
[0054] 9 shows an example of a control sequence for the terminal 11. At startup or the like, the terminal 11 notifies the management server 13 of information on metadata that can be acquired by the terminal 11. For example, when transmitting a Probe Request frame to the access point 12A, the terminal 11 stores information on n BLE beacons 16 in an extension area of the Probe Request frame (S211). The access point 12A transmits the information on the BLE beacons 16 stored in the extension area of the Probe Request frame to the management server 13 as metadata for the terminal 11 (S221). As a result, the management server 13 obtains information that the terminal 11 can acquire metadata from n BLE beacons 16.
[0055] Here, the terminal 11 may acquire the identification information of the BLE beacon 16 in step S211 and include the identification information of the BLE beacon 16 in the metadata. This allows the management server 13 to collect the identification information of the BLE beacon 16 together with the metadata.
[0056] The management server 13 generates control information for controlling at least one of the plurality of terminals 11 based on the metadata obtained from the plurality of terminals 11, and transmits the control information to the control device 14 (S231). For example, when the number of pieces of metadata of BLE beacons transmitted from the terminal 11 exceeds a certain value, the management server 13 generates, as control information, a transmission stop instruction for part of the metadata of the BLE beacons so that the number of pieces of metadata of BLE beacons transmitted from the terminal 11 becomes equal to or less than the certain value. Instead of the transmission stop instruction, the management server 13 may generate, as control information, a transmission frequency change instruction so that the metadata transmission frequency per hour becomes equal to or less than a certain value.
[0057] The control device 14 transmits control information to the terminal 11 in accordance with the control information from the management server 13 (S241), whereby the communication protocol operation unit 11d in the terminal 11 receives the frame (S212).
[0058] The communication protocol operation unit 11d of the terminal 11 reads the identifier of the terminal 11 written in a predetermined area of the extension area 41d, determines whether the identifier of the terminal 11 is included, and if the identifier of the terminal 11 is included, outputs information of the data storage area of the extension area 41d to the downstream signal information processing unit 11g (S213). The downstream signal information processing unit 11g performs an operation in accordance with the control content acquired from the communication protocol operation unit 11d (S214).
[0059] The information indicating the destination is not limited to the identifier of the terminal 11, but may be identification information of the control target such as the sensor device 11a, the metadata detection unit 11e, the metadata processing unit 11f, and the communication protocol operation unit 11d. This allows simultaneous control of all terminals 11 that have control targets.
[0060] The control content is control to adjust the data amount or transmission frequency of the metadata, and can be exemplified as follows: An instruction to start or stop transmission of specific metadata An instruction to set the transmission cycle or transmission time of specific metadata An instruction to start or put to sleep the specific metadata detection unit 11e Here, the specific metadata and the metadata detection unit 11e can be one or more arbitrary metadata selected from the metadata acquired by the management server 13.
[0061] The control contents may include the control of sensing data, and examples thereof include the following: Parameters used in the sensor device 11a Start-up instruction or sleep instruction for the sensor device 11a Instruction to start or stop transmission of sensing data Setting of the transmission cycle or transmission time of sensing data
[0062] The control contents may include settings of the communication protocol operation unit 11d, and examples thereof include the following: Settings of the destination of the metadata or sensing data (such as the identifier (MAC address, IP address), or port number of the management server 13) Settings used in the communication protocol (such as the SSID and passphrase for Wi-Fi) Settings of encryption keys (public key, private key)
[0063] (Metadata Transmission Period) Specifically, when the metadata transmission period is described in the control content, the downstream signal information processing unit 11g instructs the communication protocol operation unit 11d to transmit the metadata at the transmission period defined in the control content. The communication protocol operation unit 11d follows the instruction and transmits the metadata at the transmission period defined in the control content.
[0064] (Setting of Metadata Detector 11e) Specifically, when a sleep instruction for a specific metadata detector 11e is written in the control content, the downstream signal information processor 11g controls the specific metadata detector 11e to be in a sleep state. Upon receiving the instruction from the downstream signal information processor 11g, the metadata detector 11e transitions to the sleep state.
[0065] (Network connection setting) Specifically, when the control content specifies the specification of authentication information (ID / passphrase) when transmitting sensing data, the downstream signal information processing unit 11g sets the communication protocol operation unit 11d to use the specified authentication information as the authentication information to be used. This can be applied not only to authentication information in network connection setting, but also to any network connection setting such as a connection request destination, communication protocol specification, etc.
[0066] (Third embodiment) In order for the terminal 11 to interpret a large-sized extension area, a mode change is required. In addition, since the amount of data that can be stored in the extension area 41d is limited by the communication protocol, the control device 14 may not be able to transmit all the necessary control information at once. Therefore, in this embodiment, an example will be described in which a large amount of control information is transmitted from the management server 13 to the terminal 11.
[0067] 10 shows an example of a control sequence for the terminal 11. The control device 14 transmits a Probe Response frame including a notification of downstream data transmission as a control content (S241). When the downstream signal information processing unit 11g of the terminal 11 determines that the destination is the terminal itself and that the control content is a notification of downstream data transmission (S213), it switches the communication protocol operation unit 11d to a downstream communication reception mode (S311).
[0068] The downstream communication reception mode can be set to any setting that can interpret a large-sized extension area. For example, the communication protocol operation unit 11d can switch from an STA mode, in which the unit functions as a wireless LAN terminal, to an access point mode.
[0069] The communication protocol operation unit 43 of the control device 14 divides the control content into multiple parts and transmits them using the extension fields 41d of the individual probe responses (S341). The communication protocol operation unit 11d of the terminal 11 reads the extension fields 41d of each received probe response, restores the control content #1 to #n read from the multiple probe responses #1 to #n, and outputs them to the downstream signal information processing unit 11g (S312). The downstream signal information processing unit 11g performs an operation in accordance with the control content acquired from the communication protocol operation unit 11d (S214).
[0070] When the communication protocol operation unit 11d of the terminal 11 has completed receiving all the control contents stored in the probe responses from the control device 14, it returns from the downstream communication reception mode to the normal mode (S313). This timing may be before step S312.
[0071] As described above, according to this embodiment, a large amount of control information can be transmitted from the management server 13 to the terminal 11 to control the terminal 11. Therefore, even if the terminal 11 is installed in a remote location, it can be set to an optimal state according to the location and situation of the terminal 11.
[0072] Fourth Embodiment In this embodiment, an example of application of the present disclosure to exchange of a public key and an encryption key will be described with reference to Fig. 11. In this embodiment, a public key and an encryption key are exchanged by using the downstream communication reception mode shown in Fig. 10, and encrypted communication is thereby established.
[0073] If the first public key is described in the control content, the downstream signal information processing unit 11g determines that the destination is its own device (S213) and updates the first public key in the network connection setting information (S411). The first public key is periodically issued by the management server 13 and is broadcast, for example, using the extension field 41d of the Probe Response frame.
[0074] The communication protocol operation unit 11d reads the first public key from the network connection setting information in the memory, calculates a new second public key linked to the identifier of the terminal 11, etc., encrypts the connection request and the second public key with the first public key, and stores the encrypted connection request and second public key in the extension area 41d of the Probe Request frame and transmits them (S412).
[0075] Furthermore, the communication protocol operation unit 11d outputs the second public key to the downstream signal information processing unit 11g, which then changes the communication protocol operation unit 11d to a downstream communication reception mode (S311).
[0076] The information stored in the Probe Request frame transmitted from the communication protocol operation unit 11d is transmitted as a piece of metadata from the access point 12A to the management server 13. The management server 13 decrypts the metadata using the first public key and confirms its authenticity (S431). If the confirmation of authenticity is successful, the management server 13 encrypts a new, unique third private key with the second public key for communication between the two parties and transmits the encrypted third private key as control information to the terminal 11 (S432). The control device 14 transmits a Probe Response frame to the terminal 11, the control content of which includes the third private key encrypted with the second public key (S442).
[0077] When the control content written in the extension field 41d of the Probe Response frame is encrypted, the downstream signal information processing unit 11g of the terminal 11 decrypts the third secret key using the second public key (S412) and outputs the decrypted third secret key to the communication protocol operation unit 11d. The communication protocol operation unit 11d then verifies the authenticity of the third secret key obtained from the downstream signal information processing unit 11g (S413). If the authenticity verification is successful, the communication protocol operation unit 11d establishes communication with the management server 13 encrypted using the third secret key.
[0078] In the above embodiment, an example was shown in which the Layer 2 communication frame transmitted from the terminal 11 to the control device 14 was a Probe Request frame, and the Layer 2 communication frame transmitted from the control device 14 to the terminal 11 was a Probe Response frame, but these may be reversed. Also, in this embodiment, an example was shown in which the communication protocol was IEEE 802.11, but one or more arbitrary communication protocols that can be processed by the terminal 11 can be used.
[0079] As described above, the management server 13 of this embodiment can set the terminal 11 to an optimal state according to the location and situation of the terminal 11 based on the metadata collected from the terminal 11. This makes it possible for the data collection system of this embodiment to appropriately adjust the amount of data and transmission frequency of the metadata, thereby reducing the load and power consumption of the terminal 11.
[0080] Here, after the IP connection is established, downstream communication from the management server 13 to the terminal 11 can be performed by exchanging data using a common method such as JSON over HTTP. However, this requires a mechanism for constantly running a web server on the terminal 11 side, which is not suitable for application to terminals with low resources. Furthermore, it is practically impossible to grant connection permission to the terminal 11 or to set connection settings such as connection destination information, ID / password, etc. before the IP connection is established.
[0081] In contrast to these, the present disclosure can control the terminal 11 simply by extending the write function to the extended area of Layer 2, which the terminal 11 uses to transmit metadata, to a read function, and therefore can be applied to low-resource terminals and does not require special settings on the terminal 11 side. Therefore, the present disclosure makes it possible to realize control of the terminal 11 in a data collection system that collects metadata of the terminal 11 in the management server 13.
[0082] The management server 13, the control device 14, and the terminal 11 can also be realized by a computer and a program, and the program can be recorded on a recording medium or provided via a network.
[0083] 11: Terminal 11a: Sensor device 11b: Sensing data storage processing unit 11c: Device information storage processing unit 11d: Communication protocol operation unit 11e, 11e1, 11e2, 11e3, ...: Metadata detection unit 11f: Metadata storage processing unit 11g: Downstream signal information processing unit 12: Network device 12A: Access point 13: Management server 13a, 43: Communication protocol operation unit 13b, 42: Information processing unit 13c, 44: Information storage unit 14: Control device 45: Signal transmission unit 15: Data collection network 21: Data processing unit 41: Frame 41a: Logical identifier 41b: Source / destination identifier 41c: Main data area 41d: Extension area 93: Management server 301: Data collection system
Claims
1. A control device having a signal transmission unit that transmits control information to a terminal using an area defined by a communication protocol that the terminal can receive.
2. The control device according to claim 1, wherein the predetermined area is an extension area defined in layer 2.
3. A terminal comprising: a signal receiving unit that receives signals of a predetermined communication protocol; and a control unit that controls the terminal itself in accordance with the control content described in an area determined by the communication protocol.
4. A data collection system that collects metadata obtained at multiple terminals into a management server, comprising the control device according to claim 1 or 2, and at least one of the multiple terminals functions as the terminal according to claim 3.
5. The data collection system of claim 4, wherein the management server generates control information for controlling at least one of the plurality of terminals based on metadata obtained from the plurality of terminals, and the control device transmits control content to the terminal based on the control information generated by the management server.
6. A method in which a control device executes a signal transmission procedure for transmitting control contents to a terminal using a region defined by a communication protocol that can be received by the terminal.
7. A method comprising: a signal reception procedure in which a terminal receives a signal of a predetermined communication protocol; and a control procedure in which the terminal controls the device itself in accordance with the control content described in an area determined by the communication protocol.
8. A program for causing a computer to function as a signal transmission unit provided in the control device according to claim 1 or 2.
Citation Information
Patent Citations
Network management system, management device, relay device, method, and program
WO2019240034A1
Data collection system, terminal, data collection method, and program
WO2022003964A1
Data collection device, sensor terminal, metadata collection system, metadata collection method, and program
WO2022149250A1
System, method, device, and program for collecting data
WO2022269906A1
