JPWO2018167967A1 - Apparatus for verifying identity of operation rules of sensor device - Google Patents

Abstract

The first server device 12 transmits the detection result data received from the sensor devices 11-1 to 11-n in response to a request from the analysis device 13. Terminal devices 15-1 to 15-n are connected to the sensor devices 11-1 to 11-n, respectively. The terminal devices 15-1 to 15-n transmit to the third server device 16 a message digest of rule data such as programs and parameters stored in the connected sensor devices 11-1 to 11-n every time a predetermined time elapses. The third server device 16 determines the consistency of the detection result data generated in each of the sensor devices 11-1 to 11-n based on the message digests received from the terminal devices 15-1 to 15-n. When using the detection result data received from the first server device 12, the analysis device 13 receives, from the third server device 16, the determination result data indicating the determination result of the consistency of the detection result data, The analysis is performed by using the detection result data having the data.

Description

  The present invention relates to a technique for increasing the utility value of data generated by a sensor device.

  Currently, devices called IoT (Internet of Things) devices have become widespread. An IoT device is a type of device including a sensor (hereinafter, referred to as a “sensor device”), and a result detected by the sensor, that is, data indicating an attribute or the like of a detection target (hereinafter, “detection result data”), For example, when an event such as the lapse of a predetermined time has occurred, the data is transmitted to the server device via the Internet.

  The server accumulates detection result data (including secondary data generated based on the detection result data) continuously transmitted from the IoT device. An analyzer that wants to use the attribute of the detection target detected by the IoT device or the like acquires the detection result data that the user wants to use from the server device and uses it for analysis.

  Many IoT devices acquire parameters used for operation via the Internet, control programs called firmware, and the like, and operate according to the rules indicated by the acquired data. Therefore, when a parameter or a program used in the IoT device changes, the operation rule of the IoT device changes.

  As a patent document that discloses a technique for managing parameters and programs used in a device connected to the Internet, for example, there is Patent Document 1. Patent Literature 1 discloses a system that notifies information of software applicable to a device in response to a request from a device to be managed connected to a network.

  The system described in Patent Literature 1 specifies in advance software applicable to a device whose software has been updated by regular update within a certain period in the past, and stores information on the specified applicable software. In advance, in response to a request from the device, information of software applicable to the device and stored in advance is notified. According to the system described in Patent Literature 1, information on applicable software is promptly notified in response to a request from a device.

JP-A-2006-110222

  As described above, when data indicating parameters and programs indicating the operation rules of the IoT device (hereinafter, referred to as “rule data”) is updated, the operation rule of the IoT device changes. Therefore, even if the detection result is represented by the detection result data generated by the same IoT device, the consistency of the detection result may be lost due to the update of the rule data.

  For example, when an IoT device includes an image sensor, the function of removing noise from an image captured by the image sensor may be enhanced with the update of firmware. In this case, the image represented by the image data generated by the IoT device becomes clearer than before the update of the firmware. Therefore, in the case of this example, image data having inconsistency before and after updating the firmware is generated. As described above, when the image data having the inconsistency is misidentified as the consistent image data and is used by the analyzer, there is a risk that the analyzer may derive an incorrect analysis result.

  In view of the above circumstances, an object of the present invention is to provide a unit that enables an apparatus using detection result data generated by a sensor device to easily recognize whether or not the detection result data is consistent.

  According to the present invention, the rule data stored at a first time in a device that outputs detection result data indicating a result of detection by a sensor according to a rule indicated by rule data, and a second value different from the first time in the device. An obtaining unit that obtains the rule data stored at the time of, the rule data stored at the first time obtained by the obtaining unit, and the rule data that is stored at the second time For each of the rule data, an apparatus comprising: a transmission unit that transmits identity verification data, which is uniquely determined from the rule data itself or the rule data and indicates the identity of the rule data, to an external apparatus. Is proposed.

  According to the device according to the first aspect, the external device determines whether or not the sensor device has operated according to the same rule at the first time and the second time based on the identity verification data. can do.

  Further, according to the present invention, the rule data stored at a first time in a device that outputs detection result data indicating a result of detection by a sensor in accordance with a rule indicated by rule data and the device is different from the first time in the device An obtaining unit that obtains the rule data stored at a second time, and the rule data stored at the first time and the rule data stored at the second time obtained by the obtaining unit; As a second aspect, an apparatus including a determination unit that determines whether the rule data is the same or not and a transmission unit that transmits determination result data indicating a result of the determination by the determination unit to an external device is proposed as a second aspect. I do.

  According to the device according to the second aspect, the external device determines whether the sensor device has operated according to the same rule at the first time and the second time based on the determination result data. Can be.

  Further, according to the present invention, an acquisition unit that acquires the rule data and the detection result data from a device that outputs detection result data indicating a result of detection by a sensor according to a rule indicated by rule data, The identification data, which is uniquely determined from the rule data itself or the rule data and indicates the identity of the rule data, and the detection result data acquired by the acquisition unit are associated with each other, and an external A device including a transmission unit that transmits the data to the device is proposed as a third aspect.

  According to the device according to the third aspect, the external device determines whether or not the detection result indicated by the detection result data is a result detected by the sensor device according to the same rule based on the identity verification data. Can be determined.

  Further, the present invention provides a device that outputs detection result data indicating a result of detection by a sensor according to a rule indicated by rule data, wherein the rule data stored at a first time and a second time different from the first time are stored. For each of the rule data stored at the time, reception of receiving, from an external device, identity verification data which is uniquely determined from the rule data itself or the rule data and indicates the identity of the rule data Based on the identity verification data related to the first time and the identity verification data related to the second time, received by the receiver, and stored in the device at the first time. A device comprising a ruler for determining whether or not the rule data stored and the rule data stored at the second time are the same is proposed as a fourth mode.

  According to the apparatus according to the fourth aspect, it is determined whether the sensor device has operated according to the same rule at the first time and the second time.

  According to the present invention, an apparatus that uses detection result data generated by a sensor device can easily recognize whether or not the detection result data is consistent.

FIG. 1 is a diagram showing a configuration of a system according to a first embodiment. FIG. 2 is a diagram illustrating a configuration of a sensor device and a terminal device according to the first embodiment. FIG. 2 is a diagram showing a functional configuration of the terminal device according to the first embodiment. FIG. 2 is an exemplary view showing a configuration of a computer used to realize each of a first server device, an analysis device, a second server device, and a third server device according to the first embodiment. FIG. 3 is a diagram showing a functional configuration of a third server device according to the first embodiment. FIG. 4 is a diagram showing a configuration of a first table stored in a third server device according to the first embodiment. FIG. 4 is a diagram showing a configuration of a second table stored in a third server device according to the first embodiment. FIG. 4 is a diagram showing a configuration of a third table stored in a third server device according to the first embodiment. FIG. 6 is a diagram showing a sequence of processing performed by the terminal device and the third server device according to the first embodiment. FIG. 5 is a diagram showing a configuration of a fourth table stored in the analyzer according to the first embodiment. The figure showing the functional composition of the terminal unit concerning a 2nd embodiment. The figure showing the functional composition of the 3rd server device concerning a 2nd embodiment. FIG. 13 is a diagram showing a configuration of a third table stored in a third server device according to the second embodiment. The figure which showed the sequence of the process which the terminal device and 3rd server apparatus which concern on 2nd Embodiment perform. The figure showing the composition of the system concerning a 3rd embodiment. The figure showing the functional composition of the terminal unit concerning a 3rd embodiment.

[First Embodiment]
FIG. 1 is a diagram showing a configuration of a system 1 according to the first embodiment of the present invention. The system 1 includes n sensor devices 11-1, 11-2,..., 11-n (where n is an arbitrary natural number), a first server device 12, an analysis device 13, and an n number of , 14-n, n terminal devices 15-1, 15-2, ..., 15-n, and a third server device 16.

  Each of the sensor devices 11-1, 11-2,..., 11-n performs detection of an attribute or the like of a detection target by a sensor, and outputs a detection result (a result detected by the sensor or generated using the result. This is a device that outputs detection result data indicating “information”. The types of sensors provided in each of the sensor devices 11-1, 11-2,..., 11-n and the types of detection targets of the sensors may be any of an image sensor, a temperature sensor, an acceleration sensor, and the like. Also, the types of sensors included in each of the sensor devices 11-1, 11-2,..., 11-n and the types of detection targets of the sensors may be the same or different. Hereinafter, the sensor devices 11-1, 11-2,..., 11-n are collectively referred to as the sensor device 11. Each of the sensor devices 11 performs data communication with the first server device 12.

  The first server device 12 is a server device that accumulates detection result data output from each of the sensor devices 11 and provides the data to the analyzer 13. The number of the first server devices 12 included in the system 1 is not limited to one, and may be two or more. When the number of the first server devices 12 included in the system 1 is two or more, each of the sensor devices 11 may perform data communication with any of the two or more first server devices 12. When the number of the first server devices 12 included in the system 1 is two or more, the two or more first server devices 12 may transmit and receive the detection result data stored in each other.

  The analysis device 13 receives the detection result data from the first server device 12 and performs various data analysis using the received detection result data. The number of analyzers 13 provided in the system 1 is not limited to one, and may be two or more.

  Each of the second server devices 14-1, 14-2,..., 14-n indicates an operation rule for each of the sensor devices 11-1, 11-2,. This is a server device that transmits rule data. The rule data indicates, for example, a program such as firmware, parameters used in data processing according to the program, and the like. Hereinafter, the second server devices 14-1, 14-2,..., 14-n are collectively referred to as a second server device 14. Two or more of the second server devices 14 may be realized by one server device. That is, one server device serving as the second server device 14 corresponding to the two or more sensor devices 11 may transmit the rule data to the two or more sensor devices 11.

  In the present embodiment, when transmitting the rule data, the second server device 14 also transmits metadata indicating the attribute of the rule data. The metadata indicates, for example, the specifications of the sensor device 11 that operates according to the rule indicated by the rule data.

  Each of the terminal devices 15-1, 15-2, ..., 15-n is connected to each of the sensor devices 11-1, 11-2, ..., 11-n, and the connected sensor device. 11 is a device for monitoring the rule data stored in the storage device 11. Hereinafter, the terminal devices 15-1, 15-2,..., 15-n are collectively referred to as the terminal device 15. In the present embodiment, the sensor device 11 and the terminal device 15 connected to each other are housed in the same housing. Each of the terminal devices 15 transmits, to the third server device 16, identity verification data that is data indicating the identity of the rule data to be monitored.

  The identity verification data may be any data indicating whether or not two pieces of rule data stored at different times (for example, a first time and a second time) in the sensor device 11 are the same. Types of data. That is, the identity verification data is rule data itself or data uniquely determined from the rule data and indicating the identity of the rule data. The data uniquely determined from the rule data and indicating the identity of the rule data may be either data obtained by reversibly encoding the rule data or data obtained by irreversibly encoding the rule data. A typical example of data obtained by reversibly encoding rule data is data obtained by encrypting rule data. A typical example of data obtained by irreversibly encoding rule data is a message digest of the rule data.

  In the present embodiment, it is assumed that the terminal device 15 transmits a message digest of the rule data to be monitored stored in the sensor device 11 to the third server device 16 as data for verifying identity.

  The third server device 16 has the same rule data stored at different times (for example, the first time and the second time) in the sensor device 11 based on the identity verification data received from the terminal device 15. This is a server device that determines whether or not the determination result is satisfied, and transmits determination result data indicating a result of the determination to the analyzer 13.

  Based on the determination result data received from the third server device 16, the analysis device 13 has consistency in the detection result data received from the first server device 12 and indicating the results detected at different times by the same sensor device 11. Can be determined. If the two detection result data are the detection result data generated by the sensor device 11 according to the same operation rule, the detection result data is consistent, and the two detection result data are different according to the different operation rule. In the case of the detection result data generated by No. 11, those detection result data are not consistent.

  FIG. 2 is a diagram illustrating a configuration of the sensor device 11 and the terminal device 15 housed in the same housing and connected to each other. The connection method between the sensor device 11 and the terminal device 15 may be any of a method of sharing a bus, a method of connecting via an interface conforming to a standard such as USB (Universal Serial Bus) and UART (Universal Asynchronous Receiver Transmitter). You may. Further, two or more of these connection methods may be used in combination.

  The sensor device 11 includes a communication interface 111, a processor 112, a memory 113, and a sensor 114. The communication interface 111 performs data communication with an external device via a communication network such as the Internet. In the present embodiment, the communication interface 111 performs data communication with the first server device 12 and the second server device 14. The processor 112 performs various data processing including control of the sensor 114 in accordance with the rules indicated by the rule data stored in the memory 113. The memory 113 stores various data including rule data and metadata.

  The sensor 114 detects the attribute of the detection target under the control of the processor 112, and generates detection result data indicating the result of the detection. The detection result data generated by the sensor 114 is temporarily stored in the memory 113, for example, and then transmitted to the first server device 12 via the communication interface 111.

  The rule data stored in the memory 113 may be overwritten with the rule data received from the second server device 14. For example, when the firmware and parameters stored in the memory 113 are updated, the sensor device 11 receives new firmware and parameters from the second server device 14, and newly receives old firmware and parameters stored in the memory 113. Replace with the updated firmware and parameters.

  The terminal device 15 includes a communication interface 151, a processor 152, and a memory 153. The communication interface 151 performs data communication with an external device via a communication network such as a mobile communication network. In the present embodiment, the communication interface 151 performs data communication with the third server device 16. The processor 152 performs various data processing according to a program stored in the memory 153. The memory 153 stores a program indicating an operation rule of the processor 152 and various data such as data generated by the processor 152.

  FIG. 3 is a diagram illustrating a functional configuration of the terminal device 15. The terminal device 15 having the functional configuration shown in FIG. 3 is realized by the processor 152 performing data processing according to the program stored in the memory 153.

  The terminal device 15 includes an acquisition unit 501, a generation unit 502, and a transmission unit 503 as functional configurations. The acquisition unit 501 acquires by reading a device ID (Identifier) for identifying the sensor device 11, rule data to be monitored stored in the memory 113 of the sensor device 11, and metadata. The generation unit 502 generates a message digest (an example of the identity verification data) of the rule data acquired by the acquisition unit 501. The transmitting unit 503 transmits the message digest generated by the generating unit 502 and the device ID and metadata acquired by the acquiring unit 501 to the third server device 16.

  Note that at least a part of the acquisition unit 501, the generation unit 502, and the transmission unit 503 included in the terminal device 15 may be realized by dedicated hardware instead of being realized by data processing by the processor 152.

  Each of the first server device 12, the analysis device 13, the second server device 14, and the third server device 16 is realized by, for example, a general server computer. FIG. 4 is a diagram showing a configuration of a computer 10 used to realize each of the first server device 12, the analysis device 13, the second server device 14, and the third server device 16. The computer 10 includes a communication interface 101, a processor 102, and a memory 103.

  The communication interface 101 performs data communication with an external device via a communication network such as the Internet or a mobile communication network. In the present embodiment, the communication interface 101 performs data communication between each of the terminal devices 15 and the analyzer 13. The processor 102 performs various data processing according to a program stored in the memory 103. The memory 103 stores a program indicating an operation rule of the processor 102 and various data such as data generated by the processor 102.

  FIG. 5 is a diagram illustrating a functional configuration of the third server device 16. When the processor 102 of the computer 10 used in the third server device 16 performs data processing according to the program stored in the memory 103, the third server device 16 having the functional configuration shown in FIG. 5 is realized.

  The third server device 16 includes a reception unit 601, a storage unit 602, a determination unit 603, and a transmission unit 604 as functional configurations. The receiving unit 601 receives a device ID, a message digest, and metadata from each of the terminal devices 15. The storage unit 602 stores the device ID, the message digest, and the metadata received by the receiving unit 601.

  The determining unit 603 includes a message digest (an example of the identity verification data related to the first time) previously received by the receiving unit 601 and stored in the storage unit 602, and a message newly received by the receiving unit 601. Based on the digest (an example of the identity verification data related to the second time), it is determined whether or not the rule data used to generate those message digests is the same. The determination result data indicating the result of the determination by the determination unit 603 is stored in the storage unit 602.

  The transmission unit 604 transmits the determination result data and the metadata stored in the storage unit 602 to the analysis device 13.

  Note that at least a part of the receiving unit 601, the storing unit 602, the determining unit 603, and the transmitting unit 604 included in the third server device 16 are realized by dedicated hardware instead of being realized by data processing by the processor 102. Is also good.

  The storage unit 602 of the third server device 16 includes a first table that stores determination result data and a table that stores message digests and metadata according to each of the sensor devices 11 identified by the device ID. And a third table storing period data indicating a period during which the rule data is kept identical.

  FIG. 6 is a diagram showing the configuration of the first table. The first table includes fields [judgment time] and [judgment result]. In the field [judgment time], data indicating the time at which the judgment unit 603 has judged the same of rule data based on the message digest is stored. In the field [judgment result], judgment result data indicating the result of the judgment of the identity of the rule data performed by the judgment unit 603 is stored. The records of the first table are sorted, for example, in descending order of the determination time.

  FIG. 7 is a diagram showing the configuration of the second table. The second table includes fields [message digest ID], [reception time], [message digest], and [metadata]. The field [message digest ID] stores a message digest ID for identifying the message digest.

  The field [reception time] stores data indicating the time when the third server device 16 last received the message digest identified by the message digest ID. In the field [reception time], data indicating the time when the third server device 16 first receives the message digest identified by the message digest ID may be stored. The records in the second table are sorted, for example, in descending order of reception time.

  The field [message digest] stores the message digest identified by the message digest ID. The field [metadata] stores metadata indicating the attribute of the rule data used for generating the message digest.

  FIG. 8 is a diagram showing the configuration of the third table. The third table includes fields [Period] and [Message Digest ID]. In the field [period], the third server device 16 receives the message digest from the terminal device 15 due to the period during which the rule data is kept identical or the operation of the sensor device 11 has stopped. It is not possible to store data indicating a period during which it is unclear whether or not the identity of the rule data has been maintained. The records in the third table are sorted, for example, in the order of newest period.

  The field [message digest ID] stores a message digest ID that identifies the message digest received from the terminal device 15 by the third server device 16 during the period indicated by the data stored in the field [period]. However, a Null value is stored in the field [message digest ID] of the record according to the period during which it is unknown whether or not the identity of the rule data has been maintained.

  The terminal device 15 and the third server device 16 perform processing according to the sequence shown in FIG. 9 in response to occurrence of an event such as the elapse of a predetermined time.

  First, the acquiring unit 501 acquires by reading out a device ID, rule data, and metadata from the memory 113 of the sensor device 11 (Step S101). Subsequently, the generation unit 502 generates a message digest of the rule data acquired by the acquisition unit 501 (Step S102). Subsequently, the transmission unit 503 transmits the message digest generated by the generation unit 502 in step S102, and the device ID and the metadata acquired by the acquisition unit 501 in step S101 to the third server device 16 (step S103). ).

  The receiving unit 601 of the third server device 16 receives the device ID, the message digest, and the metadata transmitted by the terminal device 15 in Step S103 (Step S104). Subsequently, the determination unit 603 determines that the message digest received by the reception unit 601 is the same as the message digest stored in the latest record of the reception time of the second table corresponding to the device ID received by the reception unit 601. Is determined (step S105).

  Subsequently, the determining unit 603 stores the determination result data indicating the result of the determination in the first table corresponding to the device ID received by the receiving unit 601 (Step S106). Specifically, the determination unit 603 adds a new record to the first table corresponding to the device ID received by the reception unit 601 and stores data indicating the current time in a field [determination time] of the new record. , And stores the judgment result data in the field [judgment result].

  Subsequently, the determining unit 603 updates the second table and the third table corresponding to the device ID received by the receiving unit 601 according to the result of the determination (Step S107). Specifically, first, regarding the second table, if the two message digests compared in step S105 are the same, the determination unit 603 converts the data of the field [reception time] of the latest record into data indicating the current time. change. On the other hand, if the two message digests compared in step S105 are different, the determination unit 603 adds a new record to the second table, and adds a new message digest unique to the field [message digest ID] of the new record. The ID, the data indicating the current time in the field [reception time], the message digest received in step S104 in the field [message digest], and the metadata received in step S104 in the field [metadata] are stored. .

  Next, with respect to the third table, if the end of the latest record period is a predetermined time or more before the current time, the determination unit 603 determines that the message digest has not been transmitted until that time due to the suspension of operation of the sensor device 11 or the like. It is determined that the rule data has not been obtained, a new record is added to the third table, data indicating a period during which the rule data cannot be identified is stored in a field [period] of the new record, and a field [message Null value is stored in [Digest ID]. Then, a new record is further added to the third table, data indicating a period starting from the current time and ending undetermined is stored in a field [period] of the new record, and a field [message digest ID] is stored in a field [message digest ID]. The message digest ID stored in the latest record of the third table is stored.

  The determination unit 603 determines that if less than a predetermined time has elapsed from the end of the period of the latest record in the third table to the current time and the two message digests compared in step S105 are the same, the third table Is changed so that the end of the period indicated by the data in the field [period] of the latest record is the current time.

  Further, the determination unit 603 determines that if less than a predetermined time has elapsed from the end of the latest record period of the third table to the current time and the two message digests compared in step S105 are different, the third table , A new record is added to the new record, data indicating a period starting from the current time and ending to be determined is stored in a field [period] of the new record, and a field [message digest ID] is stored in the latest record of the third table. Stores the stored message digest ID.

  The above is the description of the processing performed by the terminal device 15 and the third server device 16 according to the sequence shown in FIG.

  The analysis device 13 receives detection result data necessary for analysis from the first server device 12 in response to, for example, a user instruction or the like. The detection result data received by the analysis device 13 from the first server device 12 includes a device ID for identifying the sensor device 11 that has generated the detection result data, and detection time data indicating a time at which the detection result data was generated. Accompanied. The analysis device 13 temporarily stores data received from the first server device 12 for use in analysis.

  FIG. 10 is a diagram illustrating a configuration of a fourth table used by the analyzer 13 to store data received from the first server device 12. The fourth table includes fields [device ID], [detection time], [detection result], [message digest ID], and [metadata]. The field [device ID] stores a device ID accompanying the detection result data. The field [detection time] stores detection time data accompanying the detection result data. The field [detection result] stores detection result data.

  Upon receiving the detection result data from the first server device 12, the analysis device 13 transmits to the third server device 16 a request including a table in which a pair of the device ID and the detection time data accompanying the received detection result data is a record. . For each record stored in the table included in the request from the first server device 12, the third server device 16 determines, based on the period including the time indicated by the detection time data, from the third table corresponding to the device ID. The searched record is searched, and the field [message digest ID] of the searched record is specified.

  Subsequently, the third server device 16 searches the second table corresponding to the device ID for a record corresponding to the message digest ID specified as described above, and stores the record in the field [metadata] of the searched record. Read the data that is stored.

  The third server device 16 generates a table in which the message digest ID and the metadata searched as described above are added for each of the records of the table included in the request from the analysis device 13, and generates the generated table using the analysis device 13. Send to

  The analysis device 13 converts the message digest ID and the metadata included in the table transmitted from the third server device 16 in response to the request into the fields [message digest ID] and [metadata] of the corresponding record in the fourth table. To be stored.

  Among the detection result data stored in the fourth table, the detection result data associated with the same message digest ID is consistent with each other. Therefore, the analysis device 13 can easily recognize the presence or absence of consistency between the detection result data received from the first server device 12. The analysis device 13 divides records in the fourth table into message detection IDs that are consistent with each other, for example, by grouping the records in the message digest ID, and performs analysis using the detection result data that are consistent with each other. As a result, the analysis is performed with high accuracy by the analyzer 13.

  In the related art, in order to recognize whether or not the detection result data received from the first server device 12 is consistent, the analyzer 13 needs to be configured by the administrator of the sensor device 11 that generated the detection result data. It is necessary to acquire information on updating of rule data such as firmware and parameters from a Web page managed by. In that case, the analyzer 13 needs to visit a number of Web pages to obtain information on each of the different sensor devices 11. Therefore, analysis processing cannot be performed at high speed. According to the system 1, the analyzer 13 can quickly determine whether there is consistency between the detection result data.

  Further, in the related art, the reliability of the information provided by the administrator of each sensor device 11 regarding the update of the rule data such as firmware and parameters is not guaranteed. According to the system 1, the presence or absence of the identity of the rule data actually stored in the sensor device 11 is frequently confirmed. Therefore, there is no danger that the analysis device 13 will perform an incorrect analysis in accordance with erroneous information regarding the update of the rule data.

[Second embodiment]
Hereinafter, a system according to the second embodiment of the present invention will be described. In the system according to the first embodiment, the third server device 16 determines the identity of the rule data. On the other hand, in the system according to the second embodiment, the determination of the identity of the rule data is performed in the terminal device 15.

  The system according to the second embodiment is common in many respects to the system 1 according to the first embodiment. Therefore, the points of the system according to the second embodiment that are different from the system 1 according to the first embodiment will be described below, and the common points will not be described.

  The overall configuration of the system according to the second embodiment is the same as the system 1 according to the first embodiment shown in FIG. The configurations of the sensor device and the terminal device included in the system according to the second embodiment are the same as the configurations of the sensor device 11 and the terminal device 15 according to the first embodiment illustrated in FIG. The configuration of a computer used as hardware such as the third server device 16 included in the system according to the second embodiment is the same as the configuration of the computer 10 according to the first embodiment illustrated in FIG. Therefore, in the following description, the reference numerals used in the first embodiment are used for the system and its components according to the second embodiment.

  Further, the functional configuration of the terminal device 15 according to the second embodiment is similar to the functional configuration of the terminal device 15 according to the first embodiment shown in FIG. Therefore, among the functional components of the terminal device 15 according to the second embodiment, the components used in common with or corresponding to the functional components of the terminal device 15 according to the first embodiment use the reference numerals used in the first embodiment. . The functional configuration of the third server device 16 according to the second embodiment is similar to the functional configuration of the third server device 16 according to the first embodiment shown in FIG. Therefore, among the functional components of the third server device 16 according to the second embodiment, those that are common to or correspond to the functional components of the third server device 16 according to the first embodiment are used in the first embodiment. Use the existing code.

  FIG. 11 is a diagram illustrating a functional configuration of the terminal device 15 according to the second embodiment. The terminal device 15 according to the second embodiment includes, as functional components, an acquisition unit 501, a storage unit 511, a determination unit 512, and a transmission unit 503. The acquiring unit 501 acquires by reading the device ID stored in the memory 113 of the sensor device 11 and the rule data to be monitored. The storage unit 511 stores the rule data obtained last by the obtaining unit 501.

  In the second embodiment, the sensor device 11 does not receive metadata from the second server device 14. Therefore, in the second embodiment, the terminal device 15 does not read the metadata from the memory 113 and does not transmit the metadata to the third server device 16. Further, in the second embodiment, it is assumed that the third server device 16 does not store the metadata and transmit it to the analysis device 13. However, in the second embodiment, similarly to the first embodiment, even if the sensor device 11 receives the metadata from the second server device 14 and the metadata is transmitted to the third server device 16 via the terminal device 15, Good. Further, the third server device 16 may transmit the metadata to the analysis device 13.

  The determination unit 512 compares the rule data (an example of the identity verification data related to the first time) acquired by the acquisition unit 501 in the past and stored in the storage unit 511 with the rule newly acquired by the acquisition unit 501. It is determined whether or not the data (an example of the identity verification data relating to the second time) is the same. The transmission unit 503 transmits the determination result data indicating the result of the determination by the determination unit 512, the determination time data indicating the determination time (current time), and the device ID acquired by the acquisition unit 501 to the third server device 16. Send.

  FIG. 12 is a diagram illustrating a functional configuration of the third server device 16 according to the second embodiment. The third server device 16 according to the second embodiment includes, as functional components, a receiving unit 601, a storage unit 602, a period specifying unit 611, and a transmitting unit 604. The receiving unit 601 receives a device ID, determination result data, and determination time data from each of the terminal devices 15. The storage unit 602 stores the determination result data and the determination time data received by the receiving unit 601.

  The period specifying unit 611 specifies a period in which the rule data is kept identical based on the determination result data and the determination time data stored in the storage unit 602. Period data indicating the period specified by the period specifying unit 611 is stored in the storage unit 602. The transmission unit 604 transmits the period data stored in the storage unit 602 to the analyzer 13.

  The storage unit 602 of the third server device 16 according to the second embodiment stores a first table having the configuration shown in FIG. The third server device 16 sequentially stores the determination time data and the determination result data received from the terminal device 15 in the first table corresponding to the device ID received together with the data.

  Further, in the storage unit 602 of the third server device 16 according to the second embodiment, a third table having a configuration shown in FIG. 13 is stored instead of the third table having a configuration shown in FIG. The third table according to the second embodiment includes fields [Period] and [Identity].

  In the field [period] of the third table according to the second embodiment, data indicating a period in which the rule data is kept identical or a period in which it is unknown whether or not the rule data is kept is stored. Further, in the field [identity] of the third table according to the second embodiment, it is unknown whether or not the rule data has the same identity, or whether the identity has been maintained. "Unknown" is stored. Note that, in the second embodiment, the second table (see FIG. 7) is not used.

  FIG. 14 is a diagram illustrating a sequence of processing performed by the terminal device 15 and the third server device 16 in response to occurrence of an event such as the lapse of a predetermined time in the second embodiment. First, the acquiring unit 501 acquires by reading the device ID and the rule data from the memory 113 of the sensor device 11 (Step S201). Subsequently, the determination unit 512 determines whether or not the rule data acquired by the acquisition unit 501 and the rule data stored in the storage unit 511 are the same, and determination result data indicating a determination result and determination time Is generated (step S202). The determination time data indicates, for example, the current time when the determination is made.

  Subsequently, the determination unit 512 rewrites the rule data stored in the storage unit 511 with the rule data acquired by the acquisition unit 501 (Step S203). Note that if the two pieces of rule data to be compared match in step S202, the processing in step S203 may not be performed.

  Subsequently, the transmission unit 503 transmits the device ID acquired by the acquisition unit 501, the determination time data and the determination result data generated by the determination unit 512 to the third server device 16 (Step S204).

  The receiving unit 601 of the third server device 16 receives the device ID, the determination time data, and the determination result data transmitted by the terminal device 15 in Step S204 (Step S205). The storage unit 602 adds a new record to the first table corresponding to the device ID received by the receiving unit 601 and stores the determination time data and the determination result data received by the receiving unit 601 in the new record. (Step S206).

  Subsequently, based on the data stored in the first table corresponding to the device ID received by the receiving unit 601, the period specifying unit 611 maintains the same period and the same rule data as the rule data. A period during which it is unknown whether or not the user has been identified is specified (step S207). The period specifying unit 611 determines whether the period data indicating the specified period is the same as the rule data during the specified period, or whether it is unknown whether the rule data is the same or not. Then, the third table is updated using the generated data (step S208).

  The above is the description of the processing performed by the terminal device 15 and the third server device 16 according to the second embodiment in accordance with the sequence shown in FIG.

  In the second embodiment, the analysis device 13 receives detection result data necessary for analysis from the first server device 12 in response to, for example, a user instruction or the like. The detection result data received by the analysis device 13 from the first server device 12 includes a device ID for identifying the sensor device 11 that has generated the detection result data, and detection time data indicating a time at which the detection result data was generated. Accompanied. The analysis device 13 temporarily stores data received from the first server device 12 for use in analysis.

  Subsequently, the analysis device 13 transmits a request including a list of device IDs accompanying the detection result data used for analysis to the third server device 16. The third server device 16 reads a third table corresponding to the device ID from the storage unit 602 for each of the device IDs included in the request transmitted from the analyzer 13 and transmits the third table to the analyzer 13.

  The analysis device 13 receives the third table transmitted from the third server device 16 in response to the request. The analyzer 13 can recognize the consistency between the detection result data used for the analysis, based on the data stored in the third table received from the third server 16.

[Third embodiment]
Hereinafter, a system 2 according to the third embodiment of the present invention will be described. In the system 1 according to the first embodiment, the detection result data generated by the sensor device 11 is transmitted to the first server device 12, and is stored in the sensor device 11 when the sensor device 11 generates the detection result data. The identity verification data relating to the rule data that has been sent is transmitted to a third server device 16 different from the first server device 12.

  On the other hand, in the system 2 according to the third embodiment, the identity verification data is associated in the terminal device 15 with the detection result data generated by the sensor device 11. Then, the detection result data to which the identity verification data is added is transmitted from the terminal device 15 to the first server device 12.

  The system 2 has many points in common with the system 1 according to the first embodiment. Therefore, only the differences between the system 2 and the system 1 according to the first embodiment will be described below, and the common points will not be described.

  In addition, among components included in the system 2, components that are common to or correspond to components included in the system 1 according to the first embodiment are denoted by the same reference numerals used in the first embodiment.

  FIG. 15 is a diagram showing a configuration of the system 2. The system 2 does not include the third server device 16 included in the system 1. The sensor device 11 included in the system 2 does not perform data communication with the first server device 12, and the terminal device 15 performs data communication with the first server device 12.

  FIG. 16 is a diagram illustrating a functional configuration of the terminal device 15 included in the system 2. The terminal device 15 includes an acquisition unit 501, a generation unit 502, an electronic signature unit 521, and a transmission unit 503 as functional configurations. The acquisition unit 501 acquires detection result data output from the sensor device 11. Further, the acquisition unit 501 acquires by reading the device ID stored in the memory 113 of the sensor device 11 and the rule data to be monitored.

  The generation unit 502 generates a message digest (an example of the identity verification data) of the rule data acquired by the acquisition unit 501. The electronic signature unit 521 stores a secret key SK in a public key cryptosystem unique to an administrator of the terminal device 15, and uses the secret key SK to obtain a device ID and detection result data obtained by the obtaining unit 501; The electronic signature is performed on the detection time data indicating the detection time and the data in which the message digest generated by the generation unit 502 is associated with each other.

  The transmitting unit 503 transmits, to the first server device 12, data in which a message digest of the device ID, the detection result data, the detection time data, and the rule data, for which the digital signature is performed by the digital signature unit 521, is associated with each other. .

  In the system 2, when the sensor device 11 performs detection using the sensor 114 and generates detection result data, the sensor device 11 outputs the detection result data to the terminal device 15. The acquisition unit 501 of the terminal device 15 acquires the detection result data output from the sensor device 11 and delivers the data to the electronic signature unit 521. Upon acquiring the detection result data from the sensor device 11, the acquiring unit 501 reads the device ID and the rule data from the memory 113 of the sensor device 11, and passes the device ID to the electronic signature unit 521 and the rule data to the generating unit 502.

  Upon receiving the rule data from the acquisition unit 501, the generation unit 502 generates a message digest of the received rule data. Further, the generation unit 502 generates data indicating the current time at that time as detection time data. The generation unit 502 passes the generated message digest and detection time data to the electronic signature unit 521.

  When the electronic signature unit 521 receives the device ID and the detection result data from the acquisition unit 501 and the message digest of the detection time data and the rule data from the generation unit 502, respectively, the electronic signature unit 521 applies an electronic signature to data in which these data are associated with each other. After performing, it is delivered to the transmission unit 503. The transmission unit 503 transmits the data delivered from the electronic signature unit 521 to the first server device 12.

  In the system 2, the first server device 12 and the analysis device 13 acquire and store a public key PK paired with the secret key SK. When the first server device 12 receives the device ID, the detection result data, the detection time data, and the message digest of the rule data with the electronic signature from the terminal device 15, the first server device 12 falsifies the data using the public key PK. After confirming that it has not been performed, accumulate it.

  In the system 2, the analysis device 13 receives, from the first server device 12, a message digest of the device ID, the detection result data, the detection time data, and the rule data, which has been digitally signed with the secret key SK. When the analyzer 13 receives the device ID, the detection result data, the detection time data, and the message digest of the rule data, for which the electronic signature has been performed, from the first server device 12, the data is tampered with the public key PK. After confirming that this has not been done, use those data for analysis.

  In the system 2, the detection result data received by the analyzer 13 from the first server device 12 includes, in addition to the device ID and the detection time data, the sensor device that generated the detection result data at the time when the detection result data was generated. 11 is associated with the message digest of the rule data stored in FIG. The detection result data associated with the same message digest is detection result data generated by the sensor device 11 that operates according to the same rule data. Therefore, the analyzer 13 can recognize the detection result data associated with the same message digest as consistent detection result data.

[Modification]
The embodiments described above may be variously modified. Hereinafter, examples of those modifications will be described. Note that two or more of the above-described embodiment and the following modified examples may be combined.

(1) In the first embodiment or the second embodiment, the first server device 12 and the third server device 16 may be integrated into one server device.

(2) The sensor device 11 and the terminal device 15 connected to each other may be integrated into one device. In that case, one or more of the combinations of the communication interface 111 and the communication interface 151, the processor 112 and the processor 152, and the memory 113 and the memory 153 may be integrated into one component.

(3) Information security techniques such as encryption and electronic signature may be used for data communication between devices as necessary. Further, as a communication connection used for data communication between the devices, a communication connection with high information security such as a closed communication connection capable of communicating only with a specific partner may be used.

(4) The analysis device 13 receives the data used for the analysis directly from the first server device 12, but receives the necessary data from the first server device 12 in advance and stores the data required for the analysis via the storage server device. Data may be received. In that case, the storage server device may recognize the consistency of the detection result data received from the first server device 12.

(5) In the third embodiment, the electronic signature in the terminal device 15 may not be performed. For example, when there is a low risk that data communicated between the terminal device 15 and the first server device 12 is falsified, the electronic signature in the terminal device 15 is unnecessary.

(6) In the third embodiment, instead of the terminal device 15 transmitting data to the first server device 12, the sensor device 11 may transmit data to the first server device 12. In this case, the sensor device 11 receives the identity verification data generated by the terminal device 15, and transmits the received identity verification data to the first server device 12 in association with the detection result data. Further, the sensor device 11 may transmit the rule data itself to the first server device 12 in association with the detection result data as the data for identity verification. In this case, the sensor device 11 also functions as the terminal device 15.

(7) The sensor device 11 may receive rule data such as firmware and parameters from the second server device 14 via the terminal device 15.

(8) The range of the rule data to be monitored by the terminal device 15 may be changed according to an instruction or the like transmitted from an external device such as the third server device 16 to the terminal device 15.

(9) The terminal device 15 may individually handle each of two or more pieces of rule data stored in the memory 113 of the sensor device 11. For example, in the first embodiment, the terminal device 15 may generate a message digest of a program and a message digest of a parameter, and transmit them to the third server device 16. In this case, the identity of the program and the parameters stored in the sensor device 11 is individually managed.

(10) The sensor device 11 and the terminal device 15 connected to each other may be housed in different housings.

(11) In the above-described embodiment, the terminal device 15 acquires the rule data stored in the sensor device 11 by reading from the memory 113. When the terminal device 15 reads the rule data from the memory 113, there is an advantage that the rule data is not easily falsified with respect to the terminal device 15. However, when the risk that the rule data is tampered with is low, the sensor device 11 may transmit the rule data, and the terminal device 15 may acquire the rule data by receiving the rule data transmitted from the sensor device 11. In that case, the terminal device 15 may receive the rule data transmitted from the sensor device 11 via another device that transfers data. Further, the sensor device 11 may transmit the rule data by wireless communication (including short-range wireless communication). Further, the terminal device 15 may receive the rule data by wireless communication (including short-range wireless communication).

  DESCRIPTION OF SYMBOLS 1 ... System, 2 ... System, 10 ... Computer, 11 ... Sensor device, 12 ... First server device, 13 ... Analysis device, 14 ... Second server device, 15 ... Terminal device, 16 ... Third server device, 101 ... Communication interface, 102, processor, 103, memory, 111, communication interface, 112, processor, 113, memory, 114, sensor, 151, communication interface, 152, processor, 153, memory, 501, acquisition unit, 502, generation unit , 503: transmission unit, 511: storage unit, 512: determination unit, 521: electronic signature unit, 601: reception unit, 602: storage unit, 603: determination unit, 604: transmission unit, 611: period identification unit

Claims (4)

The rule data stored at the first time in the device that outputs the detection result data indicating the result of the detection by the sensor according to the rule indicated by the rule data, and the rule data stored in the device at the second time different from the first time An acquiring unit for acquiring the rule data that has been performed,
For each of the rule data stored at the first time and the rule data stored at the second time acquired by the acquisition unit, the rule data is uniquely determined from the rule data itself or the rule data. A transmitting unit that transmits identity verification data, which is data indicating the identity of the rule data, to an external device. The rule data stored at the first time in the device that outputs the detection result data indicating the result of the detection by the sensor according to the rule indicated by the rule data, and the rule data stored in the device at the second time different from the first time An acquiring unit for acquiring the rule data that has been performed,
A determining unit that determines whether the rule data stored at the first time and the rule data stored at the second time acquired by the acquiring unit are the same,
A transmission unit that transmits determination result data indicating a result of the determination by the determination unit to an external device. An acquisition unit that acquires the rule data and the detection result data from a device that outputs detection result data indicating a result of detection by the sensor according to the rule indicated by the rule data,
The rule data itself acquired by the acquisition unit or the identity verification data that is uniquely determined from the rule data and indicates the identity of the rule data, and the detection result data acquired by the acquisition unit And a transmitting unit that transmits to an external device in association with each other. The rule data stored at the first time and the second time different from the first time are stored in the device that outputs detection result data indicating the result of detection by the sensor according to the rule indicated by the rule data. For each of the rule data, the identification data that is uniquely determined from the rule data itself or the rule data and indicates the identity of the rule data, a receiving unit that receives from an external device,
Based on the identity verification data for the first time and the identity verification data for the second time received by the receiving unit, the device was stored at the first time in the device A determination unit that determines whether or not the rule data and the rule data stored at the second time are the same.

Images