JP6323288B2 - Data acquisition apparatus, data acquisition method, and program - Google Patents

Description

  The present invention relates to a data acquisition device, a data acquisition method, and a program.

  M2M (Machine-to-for social infrastructure) that automatically collects environmental information such as temperature or disaster prevention information such as river water level or building distortion, and raises an alert when the collected information shows abnormal values (Machine) service is attracting attention. In such a service, a large number of sensors installed to measure data indicating environmental information, disaster prevention information, and the like are used. Therefore, in order to reduce the service operating cost, a power saving technique for reducing the replacement frequency of the battery of each sensor is important.

JP 2011-186903 A JP 2002-304201 A JP 2004-272506 A JP 2010-148027 A

  For example, it is possible to expect power saving by starting the sensor in accordance with the information collection time by the service and putting the sensor to sleep between the collection times.

  However, when a certain sensor is shared by a plurality of services having different data collection cycles, access to the sensor occurs frequently, and it may be difficult to secure an effective sleep period for power saving. . Also, considering the possibility of newly adding a service that uses the sensor, it is difficult to set the sensor activation time in advance.

  Therefore, an object of one aspect is to reduce power consumption of a device that is a continuous data acquisition source.

  In one plan, the data acquisition device receives data measured by the device and the remaining battery level of the device, and stores the data in a storage unit and information connected via a network. In response to the data acquisition request from the processing device, based on the reply unit that returns the data stored in the storage unit, the remaining battery level received by the receiving unit, and the history of the acquisition request, A calculation unit that calculates the next reception time of the data, and a transmission unit that transmits the data from the device at the reception time by transmitting the reception time calculated by the calculation unit to the device. .

  According to one aspect, it is possible to reduce the power consumption of a device that is a continuous data acquisition source.

It is a figure which shows the structural example of the data acquisition system in 1st embodiment. It is a figure which shows the hardware structural example of the data acquisition apparatus in 1st embodiment. It is a figure which shows the function structural example of the data acquisition apparatus and sensor in 1st embodiment. It is a flowchart for demonstrating an example of the process sequence which a data acquisition apparatus performs in 1st embodiment. It is a flowchart for demonstrating an example of the process sequence which a data acquisition apparatus performs in 1st embodiment. It is a figure which shows the structural example of an access log | history memory | storage part. It is a figure which shows the structural example of a data storage part. It is a flowchart for demonstrating an example of the process sequence of the calculation process of the next communication time. It is a figure for demonstrating aggregation of access timing. It is a figure which shows the function structural example of the data acquisition apparatus and sensor in 2nd embodiment. It is a flowchart for demonstrating an example of the process sequence which a data acquisition apparatus performs in 2nd embodiment. It is a figure for demonstrating the communication schedule with respect to a device group. It is a flowchart for demonstrating an example of the process sequence of the production | generation process of the communication schedule with respect to a device group. It is a figure for demonstrating aggregation of the access timing for the production | generation of the communication schedule with respect to a device group.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating a configuration example of a data acquisition system according to the first embodiment. In FIG. 1, a data acquisition device 10 is connected to a data use device 20a and a data use device 20b through a network such as a LAN (Local Area Network) or the Internet. The data acquisition device 10 is also communicably connected to the sensors 30a and 30b via a network such as a LAN or the Internet.

  The sensors 30 such as the sensor 30a and the sensor 30b are sensors 30 that measure data indicating environmental information and disaster prevention information, for example. In the present embodiment, the sensor 30a is assumed to be a temperature sensor that measures the temperature of the installation location of the sensor 30a. The sensor 30b is assumed to be a CO2 sensor that measures the amount of CO2 in the atmosphere where the sensor 30b is installed. However, a sensor other than the temperature sensor and the CO 2 sensor may be used as the sensor 30. Further, the number of sensors 30 connected to the data acquisition device 10 may be one, or three or more.

  The data acquisition device 10 is a computer that receives data measured by each sensor 30 from each sensor 30. For example, the data acquisition device 10 receives temperature data indicating the temperature from the sensor 30a, and receives CO2 data indicating the amount of CO2 from the sensor 30b. In the present embodiment, the data acquisition device 10 controls the reception timing of data from each sensor 30 so that the power consumption of each sensor 30 decreases.

  The data utilization device 20a and the data utilization device 20b (hereinafter referred to as “data utilization device 20” when not distinguished from each other) are computers that provide services using data acquired by the data acquisition device 10. Services provided by each data utilization device 20 may be different from each other. An example of such a service is a service in which the event is notified to a pre-registered notification destination when the temperature or the CO2 amount exceeds a predetermined value. However, the form of service provision by the data utilization device 20 is arbitrary for each data utilization device 20. Note that three or more data utilization devices 20 may be connected to the data acquisition device 10 via a network.

  FIG. 2 is a diagram illustrating a hardware configuration example of the data acquisition apparatus according to the first embodiment. The data acquisition device 10 in FIG. 2 includes a drive device 100, an auxiliary storage device 102, a memory device 103, a CPU 104, an interface device 105, and the like that are mutually connected by a bus B.

  A program for realizing processing in the data acquisition apparatus 10 is provided by the recording medium 101. When the recording medium 101 on which the program is recorded is set in the drive device 100, the program is installed from the recording medium 101 to the auxiliary storage device 102 via the drive device 100. However, the program need not be installed from the recording medium 101 and may be downloaded from another computer via a network. The auxiliary storage device 102 stores the installed program and also stores necessary files and data.

  The memory device 103 reads the program from the auxiliary storage device 102 and stores it when there is an instruction to start the program. The CPU 104 executes functions related to the data acquisition device 10 in accordance with a program stored in the memory device 103. The interface device 105 is used as an interface for connecting to a network.

  An example of the recording medium 101 is a portable recording medium such as a CD-ROM, a DVD disk, or a USB memory. An example of the auxiliary storage device 102 is an HDD (Hard Disk Drive) or a flash memory. Both the recording medium 101 and the auxiliary storage device 102 correspond to computer-readable recording media.

  FIG. 3 is a diagram illustrating a functional configuration example of the data acquisition device and the sensor according to the first embodiment. In FIG. 3, the data acquisition device 10 includes an acquisition request receiving unit 11, a data acquiring unit 12, a data receiving unit 13, a communication time calculating unit 14, a communication time transmitting unit 15, and the like. Each of these units is realized by processing executed by the CPU 104 by a program (for example, middleware) installed in the data acquisition apparatus 10. The data acquisition apparatus 10 also uses a data storage unit 121, an access history storage unit 122, and the like. Each of these storage units can be realized using the memory device 103 or the auxiliary storage device 102, or a storage device connected to the data acquisition device 10 via a network.

  The acquisition request receiving unit 11 receives a sensor data acquisition request transmitted from the data utilization device 20. The sensor data refers to data indicating measurement values (for example, temperature or CO2 amount) measured by the sensor 30. When the target sensor data is stored in the data storage unit 121, the acquisition request receiving unit 11 returns the sensor data. If the target sensor data is not stored in the data storage unit 121, the acquisition request receiving unit 11 requests the data acquisition unit 12 to acquire sensor data. The acquisition request receiving unit 11 also stores information related to the received acquisition request in the access history storage unit 122. Accordingly, the access history storage unit 122 stores a history of sensor data acquisition requests.

  The data acquisition unit 12 transmits a data acquisition command to the sensor 30 in response to a request from the acquisition request reception unit 11. The data receiving unit 13 receives sensor data and information related to the power supply of the sensor 30 (hereinafter referred to as “power supply information”) returned from the sensor 30 in response to the data acquisition command. The sensor data received by the data receiving unit 13 is stored (cached) in the data storage unit 121. The sensor data received by the data receiving unit 13 in response to the data acquisition command is returned to the data utilization device 20 by the acquisition request receiving unit 11. The power supply information received by the data receiving unit 13 is input to the communication time calculating unit 14. The power supply information is information including, for example, the remaining battery level of the sensor 30 and the battery consumption due to the operation of the sensor 30.

  The communication time calculation unit 14 determines the sensor 30 related to the sensor data acquisition request when the access history storage unit 122 stores a history of the data acquisition requests of a predetermined number or more with respect to the sensor 30 related to the data acquisition request. The next communication time (communication time) with the sensor 30 is calculated based on the power supply information and the history. For example, when the consumption rate of the remaining battery level of the sensor 30 is faster than planned, the communication time calculation unit 14 lengthens the period until the next communication time so that the consumption of the remaining battery level of the sensor 30 is suppressed. To. The communication time transmission unit 15 notifies the sensor 30 of a communication command including the communication time calculated by the communication time calculation unit 14. Sensor data transmitted from the sensor 30 in response to the arrival of the communication time is received by the data receiving unit 13.

  The sensor 30 includes a communication control unit 31, a data measurement unit 32, an operation state control unit 33, and the like. Each of these units may be realized by processing that a program installed in the sensor 30 causes the CPU of the sensor 30 to execute, or may be realized by hardware such as a circuit. The sensor 30 also has a profile storage unit 34. The profile storage unit 34 can be realized using a storage device included in the sensor 30.

  The communication control unit 31 receives a data acquisition command and a communication command from the data acquisition device 10. The communication control unit 31 also transmits sensor data and power supply information to the data acquisition device 10. The data measuring unit 32 measures sensor data. The operating state control unit 33 shifts the operating state of the sensor 30 to a startup state or a sleep state. The activated state refers to a state in which the sensor 30 is activated and sensor data can be measured. The sleep state refers to a state in which power consumption by the sensor 30 is suppressed as compared to the start state, and measurement of sensor data, communication with the data acquisition device 10, and the like cannot be performed. For example, in the sleep state, the power supply range is limited to a portion where the next communication time of the sensor 30 can be detected and the sensor 30 can be activated at the communication time. The profile storage unit 34 stores, for example, information (hereinafter referred to as “power profile”) indicating power consumption required for one sensor data communication. The power consumption required for one sensor data communication may include the power required for one sensor data measurement.

  Hereinafter, a processing procedure executed by the data acquisition apparatus 10 will be described. 4 and 5 are flowcharts for explaining an example of a processing procedure executed by the data acquisition device in the first embodiment.

  In the steady state, the data acquisition device 10 waits for an event to occur (S101). The event is, for example, reception of a sensor data acquisition request from any one of the data utilization devices 20, or reception of sensor data from the sensor 30 in response to arrival of the communication time.

  When the acquisition request reception unit 11 receives an acquisition request for sensor data (S102), the acquisition request reception unit 11 includes the service ID and device ID included in the received acquisition request, and the reception time of the acquisition request. Are stored in the access history storage unit 122 in association with each other (S103).

  FIG. 6 is a diagram illustrating a configuration example of the access history storage unit. As illustrated in FIG. 6, the access history storage unit 122 stores a device ID, a service ID, and a reception time for each sensor data acquisition request. The device ID is identification information of the sensor 30 that is the target of the acquisition request. The service ID is service identification information provided by the data use device 20 that is the transmission source of the acquisition request. The reception time is the reception time (reception date / time) of the acquisition request.

  “Thermo1-1” is the device ID of the sensor 30a. “Service1” is the service ID of the data utilization device 20a. “Co2-1” is the device ID of the sensor 30b. “Service2” is the service ID of the data utilization device 20b.

  Hereinafter, the acquisition request received in step S102 is referred to as “target acquisition request”, the device ID included in the target acquisition request is referred to as “target device ID”, and the service ID included in the target request acquisition request is , Referred to as “target service ID”.

  Subsequently, the acquisition request receiving unit 11 determines whether or not the schedule setting flag for the sensor 30 (hereinafter referred to as “target sensor”) related to the target device ID is TRUE (S104). The schedule setting flag is, for example, a parameter stored in the memory device 103 for each device ID, and a value of TRUE or FALSE is substituted. TRUE indicates that the next communication time is set. FALSE indicates that the next communication time is not set. The initial value of the schedule setting flag is FALSE. Therefore, in step S104, it is determined whether or not the next communication time has been set for the target sensor.

  When the schedule setting flag for the target sensor is FALSE (No in S104), the data acquisition device 10 acquires sensor data, power supply information, and the like from the target sensor (S105). More specifically, the data acquisition unit 12 transmits a data acquisition command to the target sensor. The data measurement unit 32 of the target sensor measures sensor data in response to receiving the data acquisition command. The communication control unit 31 of the target sensor returns a device ID of the target sensor, measured sensor data, and power supply information. The data receiving unit 13 of the data acquisition device 10 receives the sensor data and power supply information. The power supply information includes the current battery level of the target sensor, the power profile stored in the profile storage unit 34 of the target sensor, and the like. Communication between the data acquisition device 10 and the sensor 30 is performed using an interface and a communication protocol provided by the communication control unit 31 of the sensor 30. The communication protocol may be, for example, HTTP (HyperText Transfer Protocol), ECHONET Lite protocol, or the like.

  Note that the power profile of each sensor 30 may be stored in the data acquisition device 10 in association with the device ID of each sensor 30, for example. In this case, the power profile may be included in the power supply information and not transmitted from the target sensor.

  Subsequently, the data receiving unit 13 stores the received sensor data in the data storage unit 121 (S106). The data receiving unit 13 inputs the received power supply information to the communication time calculating unit 14.

  FIG. 7 is a diagram illustrating a configuration example of the data storage unit. In FIG. 7, the data storage unit 121 stores, for each device ID, the sensor data last received from the sensor 30 related to the device ID and the update time. The update time is the time (date and time) when the sensor data was last received.

  Subsequently, the communication time calculation unit 14 determines whether or not the history related to the target sensor is greater than or equal to a predetermined number among the history stored in the access history storage unit 122 (S107). That is, it is determined whether or not a sufficient history has been accumulated to derive an access pattern for the target sensor. The access pattern refers to information indicating a timing pattern at which a sensor data acquisition request is generated. The history related to the target sensor refers to a history (record) in which the value of the device ID is the target device ID. Further, in step S107, the number of histories may be counted for each data utilization device 20 with respect to the history of the past predetermined period, not just the total number of histories related to the target sensor. That is, it may be determined whether or not a sufficient history has been accumulated for each data use device 20 that uses the sensor data of the target sensor.

  When the number of histories related to the target sensor is less than the predetermined number (No in S107), the acquisition request receiving unit 11 uses the sensor data stored in the data storage unit 121 regarding the target sensor as the data utilization device 20 related to the target service ID. (S112). That is, in this case, steps S108 to S111 are not executed.

  In this way, until a sufficient history is accumulated for the target sensor and the next communication time is notified to the target sensor, sensor data is received from the target sensor every time an acquisition request is received from the data utilization device 20. To be acquired.

  On the other hand, when the number of histories related to the target sensor is equal to or greater than the predetermined number (Yes in S107), the communication time calculation unit 14 determines the access pattern derived from the history and the power of the target sensor received by the data reception unit 13. Based on the information and the like, the next communication time for the target sensor is calculated (S108). Details of the calculation process of the next communication time will be described later.

  When the next communication time is not calculated (No in S109), the data acquisition device 10 does not execute Steps S110 and S111. When the next communication time is calculated (Yes in S109), the communication time transmission unit 15 sets TRUE to the schedule setting flag associated with the device ID of the target sensor (S110). Subsequently, the communication time transmission unit 15 transmits the next communication time to the target sensor (S111). At this time, the address information of the data acquisition device 10 may be transmitted together with the communication time. This is because the target sensor can specify the transmission destination of the sensor data at the communication time based on the address information.

  At this point, the target sensor is always activated. Therefore, the communication time is received by the communication control unit 31 of the target sensor unless there are special circumstances such as a communication abnormality or a failure of the target sensor. The operation state control unit 33 of the target sensor sets the received communication time in the activation timer, and shifts the target sensor to the sleep state. The activation timer is a timer for activating the sensor 30 at a set time. Therefore, the target sensor can sleep until the next communication time, and can suppress power consumption.

  If a sensor data acquisition request regarding the target sensor is received after the next communication time is notified to the target sensor, the determination in step S104 is Yes, and steps S113 to S116 are executed.

  In step S113, the acquisition request receiving unit 11 acquires sensor data cached in association with the device ID of the target sensor from the data storage unit 121 (S113). Subsequently, the acquisition request receiving unit 11 returns the acquired sensor data to the data utilization device 20 related to the target service ID (S114). Subsequently, the acquisition request receiving unit 11 determines whether or not the target service ID is different from all the service IDs included in the past acquisition requests (S115). That is, it is determined whether or not the transmission source of the acquisition request is the new data utilization device 20. The determination may be performed by referring to the access history storage unit 122, for example. That is, when the target service ID is not stored in any record of the access history storage unit 122, it may be determined that the acquisition request is from the new data use device 20.

  When the target service ID matches the service ID included in the past acquisition request (No in S115), step S116 and subsequent steps are repeated without executing step S116. When the target service ID is not included in any past acquisition requests (Yes in S115), the acquisition request reception unit 11 sets FALSE to the schedule setting flag of the target sensor (S116). The effect of step S116 is clarified in FIG.

  Thereafter, when the next communication time comes, the operation state control unit 33 of the target sensor activates the target sensor. In response to the activation, the data measurement unit 32 of the target sensor performs sensor data measurement. The communication control unit 31 of the target sensor transmits the device ID (target device ID) of the target sensor, the sensor data, and the power supply information of the target sensor to the data acquisition device 10. At this time, the transmission destination of the sensor data may be specified based on the address information notified together with the next communication time. Alternatively, the address information may be stored in advance in the target sensor in a fixed manner. Note that the power information of the target sensor includes information similar to the information transmitted in step S105. However, the remaining battery level included in the power supply information is the remaining battery level at the present time (communication time).

  When the data receiving unit 13 of the data acquisition device 10 receives the sensor data or the like (Yes in step S120 in FIG. 5), the data receiving unit 13 selects the received target device ID from the records in the data storage unit 121. The sensor data of the record to be included is updated with the received sensor data (S130). At this time, the data receiving unit 13 updates the update time of the record with the current date and time. The data receiving unit 13 also inputs the received power supply information to the communication time calculating unit 14.

  Subsequently, the communication time calculation unit 14 determines whether or not the schedule setting flag for the target device ID is TRUE (S140). Here, regarding the target sensor, if step S116 of FIG. 4 is not executed, the schedule setting flag is TRUE, and if step S116 is executed, the schedule setting flag is FALSE.

  When the schedule setting flag for the target device ID is TRUE (Yes in S140), the communication time calculation unit 14 performs the same process as step S108 and calculates the next communication time of the target sensor (S150). When the next communication time is calculated (Yes in S160), the communication time transmission unit 15 performs the same processing as Step S111 in FIG. 4 to notify the target sensor of the next communication time (S170). As a result, the target sensor can sleep until the next communication time.

  On the other hand, when the schedule setting flag for the target device ID is FALSE (No in S140), steps S150 to S170 are not executed. If the next communication time is not calculated (No in S160), step S170 is not executed. Therefore, in this case, the target sensor remains activated.

  That is, in step S116 of FIG. 4, when a new data utilization device 20 is added, the acquisition request history from the new data utilization device 20 is sufficiently accumulated in consideration of the possibility that the access pattern changes. Until this time, the processing is aimed at avoiding the execution of step S108 (calculation of the next communication time). By doing so, it is possible to calculate the next communication time for the target sensor based on the access pattern including the access pattern from the new data utilization device 20.

  Next, details of steps S108 and S150 will be described. FIG. 8 is a flowchart for explaining an example of the processing procedure of the calculation process of the next communication time.

  In step S201, the communication time calculation unit 14 acquires the number of times of communication with the target sensor per hour. The number of times of communication is the sum of the number of times that step S105 has been executed for the target sensor and the number of times that the target sensor has become Yes in step S120. These times may be stored for each sensor 30. Note that the history in the access history storage unit 122 is a history of acquisition requests from the data utilization device 20, and therefore does not necessarily match the number of communications with the target sensor. This is because the sensor data cached in the data storage unit 121 may be returned in response to the acquisition request.

  Subsequently, the communication time calculation unit 14 determines the remaining battery level (R) of the target sensor, the power consumption (C) in one sensor data communication indicated by the power profile of the target sensor, and the number of communications per hour ( N) and the like, the operable time (T) of the target sensor is calculated (S202). Here, T may be calculated by the following equation (1), for example.

T = R ÷ (C × N)
The power consumption by each sensor 30 in one communication of sensor data may be regarded as the same.

  Next, the communication time calculation unit 14 calculates an access interval (acquisition request period) for each service ID with reference to the access history storage unit 122 (S203). Subsequently, the communication time calculation unit 14 determines whether the operable time (T) is equal to or longer than a predetermined time (S204). The predetermined time may be calculated based on, for example, a scheduled battery replacement time for the target sensor. The period from the present time to the replacement time may be the predetermined period. The replacement time may be included in the power profile of the target sensor. Alternatively, the predetermined time may be a fixed value set in advance.

  When the operable time (T) is less than the predetermined time (No in S204), the communication time calculation unit 14 collects each access timing related to the target sensor (S205).

  FIG. 9 is a diagram for explaining aggregation of access timings. In FIG. 9, (1) indicates an access interval for each service ID related to the target sensor. Specifically, Ta indicates an access interval related to the service ID of the data utilization device 20a. Tb indicates an access interval related to the service ID of the data utilization device 20b. The access timing is the reception time of the acquisition request. In FIG. 9, each time that forms an access interval is an access timing.

  (2) shows a state after aggregation of access timings. Aggregation of access timings refers to aggregating (or integrating) access timing groups within a predetermined time into one access timing. Alternatively, the aggregation of access timings means that access timings other than one access timing are removed or deleted from a group of access timings within a predetermined time. For example, in (2) of FIG. 9, the interval between the first access timing a1 from the service of the data utilization device 20a and the first access timing b1 from the service of the data utilization device 20b is within a predetermined time. Therefore, the access timing a1 and the access timing b1 are integrated into the access timing b1 (the access timing a1 is deleted). Similarly, access timing a3 and access timing b2 are aggregated at access timing a3, and access timing b3 and access timing a6 are aggregated at access timing b3.

  FIG. 9 (2) shows an example in which access timing groups within a predetermined time are aggregated to the top access timing of the access timings. However, the access timing group is an access other than the top access timing. You may make it aggregate to a timing.

  In the case of Yes in step S204 or following step S205, the communication time calculation unit 14 determines whether or not each access interval for each service ID is constant for the target sensor (S206). For example, it is determined whether or not the cycle of the acquisition request from the data acquisition device 10a is constant, and whether or not the cycle of the acquisition request from the data acquisition device 10b is constant. Here, “constant” does not require that the access interval (access cycle) be completely constant. The access interval may be approximately constant. Therefore, the “constant” here may be constant with a certain degree (prescribed error) allowed. When step S205 is executed, it is determined whether or not the access interval for each service ID based on the access timing after aggregation is constant.

  When each access interval for each service ID is constant (Yes in S206), the communication time calculation unit 14 obtains a period until two accesses (acquisition requests) are generated for all service IDs (S207). .

  For example, when the access interval for each service ID is in the state shown in (1) of FIG. 9, the access interval Ta is a period until two accesses occur for all service IDs. On the other hand, when the access interval for each service ID is in the state shown in (2) of FIG. 9, that is, when step S205 is executed, the access interval Tb ′ is set to twice for all service IDs. This is the period until access occurs.

  Subsequently, the communication time calculation unit 14 calculates the next communication time based on the period (eg, access interval Ta or Tb ′) obtained in step S207 (S208). For example, the time after the elapse of the period from the current time is set as the next communication time. Therefore, the next communication time is delayed when the operable time of the target sensor is relatively short (the battery is relatively low).

  On the other hand, when there is a non-constant access interval among the access intervals for each service ID (No in S206), the communication time calculation unit 14 does not calculate the next communication time (S209).

  The next communication time calculation process may be executed by a procedure other than that shown in FIG. That is, when it is predicted that the battery level of the sensor 30 is insufficient, the communication interval with the sensor 30 is relatively long, and the battery level of the sensor 30 is expected to be sufficient. In this case, the next communication time may be calculated by various processing procedures as long as the communication interval with the sensor 30 is relatively short. For example, if the sensor 30 includes a photovoltaic power generation mechanism, the next communication time may be calculated in consideration of the amount of power generated by the photovoltaic power generation.

  Further, when the change amount of the value indicated by the sensor data for a certain period is less than the predetermined value, the period until the next communication time may be longer than the period obtained in step S207. This is because the need for frequently acquiring sensor data from the sensor 30 is low. In addition, when the amount of change of the value indicated by the sensor data for a certain period exceeds a predetermined value, the next data communication time may not be set and the sensor 30 may not be put to sleep. This is because there is a high need to frequently acquire sensor data from the sensor 30.

  Further, for a certain sensor 30, the next communication time may be calculated based on the value of sensor data of another sensor 30. For example, when the sensor 30a which is a temperature sensor measures the temperature of the space where the air conditioner is installed, it is considered that the temperature change is small during the operation of the air conditioner. In such a case, when the data acquisition device 10 acquires sensor data from the sensor 30 that monitors the operating state of the air conditioner, and the air conditioner is in the operating state, the period until the next communication time is determined in step S207. It may be longer than the required period. For example, if the calculation result according to FIG. 8 is 30 minutes later, the communication time may be set one hour after double. Doubled is just an example. The other sensor 30 (here, the sensor 30 that monitors the operating state of the air conditioner) may be designated by the user.

  As described above, according to the first embodiment, in addition to the access pattern to the sensor 30 from each data utilization device 20, the power state (battery remaining amount, consumption, etc.) of the sensor 30 is also taken into consideration. The reception timing of sensor data from the sensor 30 is calculated. Therefore, for example, when the remaining battery level of the sensor 30 is low, it is possible to perform control such as extending the sleep time of the sensor 30. As a result, it is possible to reduce the power consumption of a device that is a continuous data acquisition source.

  Each sensor 30 is notified of the communication time, and each sensor 30 may transmit the sensor data at the notified communication time. Therefore, the necessity for each sensor 30 to wait for a sensor data acquisition request from the data acquisition device 10 can be reduced. That is, the sleep time of each sensor 30 can be lengthened.

  Next, a second embodiment will be described. In the second embodiment, differences from the first embodiment will be described. Accordingly, points not particularly mentioned may be the same as those in the first embodiment.

  FIG. 10 is a diagram illustrating a functional configuration example of the data acquisition device and the sensor according to the second embodiment. In FIG. 10, the data acquisition apparatus 10 further includes a group management unit 16. The group management unit 16 groups the sensor 30 groups in which the acquired sensor data has a correlation with each other. For example, when the sensor X, the sensor Y, and the sensor Z belong to the same group, the data acquisition device 10 not only uses the sensor data acquired from the sensor X as the sensor data of the sensor X but also the sensor Y and the sensor Z. It is also cached as sensor data. By doing so, the acquisition frequency of sensor data is reduced for the sensors 30 belonging to the same group. As a result, the sleep time of each sensor 30 can be extended. Hereinafter, a group of sensors 30 formed based on the correlation of sensor data is referred to as a “device group”.

  FIG. 11 is a flowchart for explaining an example of a processing procedure executed by the data acquisition device in the second embodiment. In the second embodiment, FIG. 5 in the first embodiment is replaced with FIG. In FIG. 11, the same steps as those in FIG. 5 are denoted by the same step numbers, and the description thereof is omitted as appropriate.

  After the sensor data stored in the data storage unit 121 is updated with the sensor data transmitted from the sensor 30 in response to the arrival of the communication time (S130), the group management unit 16 sets the group setting flag for the target sensor. It is determined whether or not it is other than 0 (zero) (S131). For example, the group setting flag is stored in the memory device 103 in association with the device ID of each sensor 30. The value of the group setting flag indicates identification information of a group to which the sensor 30 related to the device ID belongs (hereinafter referred to as “group number”). However, 0 (zero) as the value of the group setting flag indicates that the sensor 30 corresponding to the group setting flag does not belong to any group. The initial value of the group setting flag for each sensor 30 is 0 (zero).

  When the value of the group setting flag for the target sensor is 0 (No in S131), the group management unit 16 acquires the sensor data acquired from the target sensor in the past predetermined period from the other sensors 30 for the predetermined period. A correlation coefficient with the sensor data acquired in step S132 is calculated (S132). That is, the degree of similarity between the sensor data of the target sensor and the sensor data of the other sensors 30 is calculated. In the second embodiment, the history of sensor data acquired from each sensor data may be stored in the auxiliary storage device 102, for example. Note that the correlation coefficient calculation method may be a known method. For example, an existing algorithm in the field of pattern recognition or the like may be used to calculate the correlation coefficient.

  If there is no sensor data whose correlation coefficient with the sensor data of the target sensor is greater than or equal to a preset threshold value (No in S133), Step S140 and subsequent steps are executed as in the first embodiment. When there is sensor data whose correlation coefficient with the sensor data of the target sensor is equal to or greater than the threshold (Yes in S133), the group management unit 16 makes the target sensor the same as the one or more sensors 30 related to the sensor data. Belonging to the device group (S134). For example, the same group number is set for the group setting flag for the sensor 30 and the group setting flag for the target sensor, and group numbers that are not assigned to other device groups are set.

  Subsequently, the communication time calculation unit 14 generates a communication schedule for the device group (hereinafter referred to as “target group”) (S137). The communication schedule for the device group refers to a set of communication times of the sensors 30 belonging to the device group after the next time.

  FIG. 12 is a diagram for explaining a communication schedule for a device group. In FIG. 12, (1) shows an example of communication time when each of the sensor X, the sensor Y, and the sensor Z does not belong to the device group. In (1), it is indicated that the sensor X transmits sensor data and the like at timings such as time tx1, time tx2, and time tx3. Strictly speaking, the time tx2 is determined at the time tx1, and the time tx3 is determined at the time tx2. The sensor Y transmits sensor data and the like at timings such as time ty1, time ty2, and time ty3, and the sensor Y transmits sensor data and the like at timings such as time tz1, time tz2, and time tz3. It is shown.

  On the other hand, (2) shows an example of communication time when the sensor X, the sensor Y, and the sensor Z belong to the same device group. In (2), it is indicated that the sensor X transmits sensor data and the like at time tx1, the sensor Y transmits sensor data and the like at time ty2, and the sensor Z transmits sensor data and the like at time tz3. ing. That is, the number of communications of each sensor 30 is reduced to one third. If the total number of sensors 30 belonging to the device group increases, the number of communications of each sensor 30 is further reduced. That is, the communication time of each sensor 30 is calculated so that the number of receptions of sensor data from each sensor 30 is reduced according to the total number of sensors 30 belonging to the same device group.

  A period from when a certain sensor 30 to which the same device group belongs communicates until all other sensors 30 perform at least one communication is referred to as one cycle. In step S137, schedule information for one cycle is generated. In the present embodiment, the number of communications within one cycle is distributed based on the operable time of each sensor 30 and the like. Therefore, the number of communications of each sensor 30 within one cycle is not necessarily equal. Note that the communication time calculation unit 14 stores the schedule information generated for the target group in the memory device 103 or the auxiliary storage device 102 in association with the group number of the target group.

  Subsequently, the communication time transmission unit 15 transmits, for each sensor 30 belonging to the target group, the first communication time regarding the sensor 30 in the generated communication schedule to the sensor 30 (S138). If the schedule information as shown in FIG. 12B is generated, the time tx1 is transmitted to the sensor X, the time ty2 is transmitted to the sensor Y, and the time tz3 is transmitted to the sensor Z.

  On the other hand, in step S131, when the group setting flag for the target sensor is other than 0 (Yes in S131), the data reception unit 13 uses the same device group as the target sensor (hereinafter, referred to as the target sensor) based on the sensor data received from the target sensor. The sensor data stored in the data storage unit 121 for each sensor 30 belonging to “target group” is updated (S135). At this time, for the sensor data stored in the data storage unit 121 regarding the sensors 30 other than the target sensor among the group of sensors 30 belonging to the target group, a flag or the like indicating a measured value by the other sensor 30 is added. May be.

  Subsequently, the communication time calculation unit 14 determines whether or not reception of sensor data for one cycle regarding the schedule information generated last for the target group is completed (S136). That is, based on the schedule information, it is determined whether or not sensor data has been transmitted from all the sensors 30 belonging to the target group at least once. Such determination includes, for example, storing a transmission history of sensor data from each sensor 30 and determining whether or not all communication scheduled in the schedule information has been performed based on the transmission history. It may be done at.

  When reception of sensor data for one cycle is completed (Yes in S136), Step S137 and subsequent steps are executed. If reception of sensor data for one cycle is not completed (Yes in S136), the communication time transmission unit 15 is identified based on schedule information stored in association with the group number of the target group. The next communication time of the sensor is transmitted to the target sensor (S138). That is, when step S137 is not executed, the next communication time is notified to the target sensor in step S138.

  Next, details of step S137 will be described. FIG. 13 is a flowchart for explaining an example of a processing procedure for generating a communication schedule for a device group.

  In step S301, the communication time calculation unit 14 aggregates access timings related to the sensors 30 belonging to the target group for each service.

  FIG. 14 is a diagram for explaining aggregation of access timings for generating a communication schedule for a device group. In the description of FIG. 14, there are two services that access the sensor data of the sensors 30 that belong to the target group, that is, service A and service B. The sensors 30 that belong to the target group are sensors X, Y, and Z. Assume that there are three.

  In (1) to (4) of FIG. 14, the horizontal axis is time. The vertical line indicates the access timing (acquisition request timing) to the sensor data. A short vertical line indicates an access timing by the service A, and a long vertical line indicates an access timing by the service B.

  (1) shows a state where access timing is not aggregated. In (1), for each of service A and service B, three consecutive access timings indicate access timings for sensor X, sensor Y, and sensor Z once. In step S301, access timings to the sensors 30 belonging to the target group are aggregated for each of the service A and the service B. For example, access timings in a period in which at least one access is made to all the sensors 30 of the sensor X, the sensor Y, and the sensor Z are aggregated into one access timing. An example of such an aggregation result is shown in (2). (2) shows an example in which the access timing by service A in (1) is aggregated to access timings tA1, tA2, tA3, and tA4, and the access timing by service B is aggregated to access timings tB1, tB2, and tB3. Has been.

  As an aggregation destination, any access timing may be selected from the access timings to be aggregated. Or, the difference from the top access timing among the access timings to be aggregated is calculated for each other access timing, and the average value of the differences is added to the top access timing to indicate the access timing of the aggregation destination It may be said.

  Subsequently, the communication time calculation unit 14 aggregates access timings whose mutual intervals are within a predetermined time among access timings aggregated for each service into one access timing (S302). Here, access timing is aggregated across services. An example of such an aggregation result is shown in (3) of FIG. (3) shows an example in which the access timing tB2 is aggregated to the access timing tA3 because the interval between the access timing tB2 and the access timing tA3 is within a predetermined time. The access timing tA3 may be aggregated at the access timing tB2, or two access timings may be aggregated at any time between the access timing tB2 and the access timing tA3.

  Subsequently, the communication time calculation unit 14 obtains a period including at least two access timings for all services (S303). In the example of FIG. 14, the period Tc shown in (4) is the corresponding period. The period obtained in step S303 is one cycle period.

  Subsequently, the communication time calculation unit 14 acquires the number of communications per hour for each sensor 30 belonging to the target group (S304). The number of times of communication may be acquired similarly to step S201 in FIG. Subsequently, the communication time calculation unit 14 calculates the operable time for each sensor 30 belonging to the target group (S305). The operable time may be calculated in the same manner as in step S202 in FIG. For the sensors 30 other than the target sensor, the power supply information received last may be used to calculate the operable time.

  Subsequently, the communication time calculation unit 14 calculates the communication schedule of the target group based on the ratio of the operable time (S306). That is, the communication time within one cycle period is calculated for each sensor 30 belonging to the target group. At this time, the communication time of each sensor 30 is calculated so that the communication frequency (communication frequency) of the sensor 30 with a relatively long operation time is greater than the communication frequency of the sensor 30 with a relatively short operation time. Is done.

  For example, it is assumed that the operable time of the sensor X, the sensor Y, and the sensor Z is 2 hours, 1 hour, and 3 hours, respectively. That is, it is assumed that the ratio of operable time is 2: 1: 3. In this case, the communication time of each sensor 30 may be calculated so that the communication frequency (number of communication times) is 2: 1: 3.

  In (4) of FIG. 14, there are six access timings within a period Tc that is a period of one cycle. Therefore, 6 × 2/6 = 2 times for sensor X, 6 × 1/6 = 1 times for sensor Y, and 6 × 3/6 = 3 times for sensor Z. Also good.

  For example, each of the access timings tA1, tB1, tA2, tA3, tA4, and tB3 may be sequentially assigned to the sensor Z, the sensor X, the sensor Y, the sensor Z, the sensor X, and the sensor Z. The timing allocation order is not limited to a predetermined one. Further, the interval from the current time to the access timing tA1 may be specified based on the time calculated by executing the processing described in FIG. 8 for the target sensor.

  In addition, the ratio of the remaining battery capacity may be used instead of the ratio of the operable time. In other words, the access timing may be assigned so that the sensor 30 having the remaining battery level has a higher communication frequency.

  As described above, according to the second embodiment, a plurality of sensors 30 having correlation with respect to sensor data can be handled as one virtual sensor 30. As a result, the sleep time of each sensor 30 can be extended. Therefore, the power consumption of each sensor 30 can be reduced.

  Further, the communication time of each sensor 30 belonging to the same device group is calculated based on the operable time of each sensor 30. As a result, it is possible to reduce the variation in the operable time of each sensor 30.

  In the above, an example in which a device group is automatically formed based on the correlation of sensor data has been described. However, the device group may be set by, for example, an administrator of the data acquisition apparatus 10 or the like. .

  In each of the above embodiments, the data receiving unit 13 is an example of a receiving unit. The acquisition request receiving unit 11 is an example of a reply unit. The communication time calculation unit 14 is an example of a calculation unit. The communication time transmission unit 15 is an example of a transmission unit. The sensor 30 is an example of a device.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to such specific embodiment, In the range of the summary of this invention described in the claim, various deformation | transformation・ Change is possible.

Regarding the above description, the following items are further disclosed.
(Appendix 1)
A receiving unit that receives data measured by the device and the remaining battery level of the device and stores the data in a storage unit;
In response to the data acquisition request from the information processing apparatus connected via the network, a reply unit that returns the data stored in the storage unit;
A calculation unit that calculates a next reception time of the data based on the remaining battery level and the history of the acquisition request received by the reception unit;
A transmission unit for transmitting the data from the device at the reception time by transmitting the reception time calculated by the calculation unit to the device;
A data acquisition device comprising:
(Appendix 2)
The calculation unit calculates the reception time so that the reception time is later when the battery remaining amount is relatively smaller than when the battery remaining amount is relatively large.
The data acquisition device according to supplementary note 1, wherein:
(Appendix 3)
The calculation unit delays the reception time calculated based on the remaining battery level and the history of the acquisition request when the change amount of the data received in a certain period is equal to or less than a threshold value.
The data acquisition device according to appendix 1 or 2, characterized in that.
(Appendix 4)
The storage unit stores data received from the device for each of a plurality of devices,
The receiving unit measures data having a correlation with data received from any one of the plurality of devices and data measured by the first device and the first device. Memorize | store in the said memory | storage part regarding one or more 2nd apparatuses,
The calculation unit is configured to reduce the number of times data is received from each of the first device and the second device according to the total number of the first device and the second device. Calculating a reception time of data from each of the first device and the second device;
The data acquisition device according to any one of appendices 1 to 3, characterized in that:
(Appendix 5)
Computer
Receives data measured by the device and the remaining battery level of the device, stores the data in the storage unit,
In response to the data acquisition request from the information processing apparatus connected via the network, the data stored in the storage unit is returned,
Based on the remaining battery level received in the storing process and the history of the acquisition request, the next reception time of the data is calculated,
Transmitting the data received from the device at the reception time by transmitting the reception time calculated in the calculation process to the device;
A data acquisition method characterized by executing processing.
(Appendix 6)
The calculation process calculates the reception time so that the reception time is later when the remaining battery level is relatively lower than when the remaining battery level is relatively high.
The data acquisition method according to appendix 5, characterized in that:
(Appendix 7)
The calculating process delays the reception time calculated based on the remaining battery level and the history of the acquisition request when the amount of change in the data received in a certain period is equal to or less than a threshold value.
The data acquisition method according to appendix 5 or 6, characterized in that:
(Appendix 8)
The storage unit stores data received from the device for each of a plurality of devices,
The storing process measures data received from any one of a plurality of devices and data having a correlation with the first device and data measured by the first device. Storing in the storage unit with respect to one or more second devices
The calculation process is performed so that the number of data receptions from each of the first device and the second device is reduced according to the total number of the first device and the second device. Calculating a reception time of data from each of the first device and the second device;
The data acquisition method according to any one of appendices 5 to 7, characterized in that:
(Appendix 9)
On the computer,
Receives data measured by the device and the remaining battery level of the device, stores the data in the storage unit,
In response to the data acquisition request from the information processing apparatus connected via the network, the data stored in the storage unit is returned,
Based on the remaining battery level received in the storing process and the history of the acquisition request, the next reception time of the data is calculated,
Transmitting the data received from the device at the reception time by transmitting the reception time calculated in the calculation process to the device;
A program that executes processing.
(Appendix 10)
The calculation process calculates the reception time so that the reception time is later when the remaining battery level is relatively lower than when the remaining battery level is relatively high.
The program according to appendix 9, which is characterized by the above.
(Appendix 11)
The calculating process delays the reception time calculated based on the remaining battery level and the history of the acquisition request when the amount of change in the data received in a certain period is equal to or less than a threshold value.
The program according to appendix 9 or 10, characterized by the above.
(Appendix 12)
The storage unit stores data received from the device for each of a plurality of devices,
The storing process measures data received from any one of a plurality of devices and data having a correlation with the first device and data measured by the first device. Storing in the storage unit with respect to one or more second devices
The calculation process is performed so that the number of data receptions from each of the first device and the second device is reduced according to the total number of the first device and the second device. Calculating a reception time of data from each of the first device and the second device;
The program according to any one of appendices 9 to 11, characterized in that:

DESCRIPTION OF SYMBOLS 10 Data acquisition apparatus 11 Acquisition request reception part 12 Data acquisition part 13 Data reception part 14 Communication time calculation part 15 Communication time transmission part 16 Group management part 20 Data utilization apparatus 30a Sensor 30b Sensor 31 Communication control part 32 Data measurement part 33 Operating state Control unit 34 Profile storage unit 100 Drive device 101 Recording medium 102 Auxiliary storage device 103 Memory device 104 CPU
105 Interface Device 121 Data Storage Unit 122 Access History Storage Unit B Bus

Claims (6)

A receiving unit that receives data measured by the device and the remaining battery level of the device and stores the data in a storage unit;
In response to the data acquisition request from the information processing apparatus connected via the network, a reply unit that returns the data stored in the storage unit;
A calculation unit that calculates a next reception time of the data based on the remaining battery level and the history of the acquisition request received by the reception unit;
A transmission unit for transmitting the data from the device at the reception time by transmitting the reception time calculated by the calculation unit to the device;
A data acquisition device comprising: The calculation unit calculates the reception time so that the reception time is later when the battery remaining amount is relatively smaller than when the battery remaining amount is relatively large.
The data acquisition apparatus according to claim 1. The calculation unit delays the reception time calculated based on the remaining battery level and the history of the acquisition request when the change amount of the data received in a certain period is equal to or less than a threshold value.
The data acquisition device according to claim 1, wherein the data acquisition device is a data acquisition device. The storage unit stores data received from the device for each of a plurality of devices,
The receiving unit measures data having a correlation with data received from any one of the plurality of devices and data measured by the first device and the first device. Memorize | store in the said memory | storage part regarding one or more 2nd apparatuses,
The calculation unit is configured to reduce the number of times data is received from each of the first device and the second device according to the total number of the first device and the second device. Calculating a reception time of data from each of the first device and the second device;
The data acquisition device according to claim 1, wherein the data acquisition device is a data acquisition device. Computer
Receives data measured by the device and the remaining battery level of the device, stores the data in the storage unit,
In response to the data acquisition request from the information processing apparatus connected via the network, the data stored in the storage unit is returned,
Based on the remaining battery level received in the storing process and the history of the acquisition request, the next reception time of the data is calculated,
Transmitting the data received from the device at the reception time by transmitting the reception time calculated in the calculation process to the device;
A data acquisition method characterized by executing processing. On the computer,
Receives data measured by the device and the remaining battery level of the device, stores the data in the storage unit,
In response to the data acquisition request from the information processing apparatus connected via the network, the data stored in the storage unit is returned,
Based on the remaining battery level received in the storing process and the history of the acquisition request, the next reception time of the data is calculated,
Transmitting the data received from the device at the reception time by transmitting the reception time calculated in the calculation process to the device;
A program that executes processing.

Images