JP6930276B2 - Sensor management unit, sensor device, sensing data management method, and sensing data management program - Google Patents

Description

The present invention relates to a technique for distributing sensing data between a provider and a user.

Conventionally, a sensor network system for distributing sensing data sensed by a sensing device between a provider side and a user side has been studied (see, for example, Patent Document 1). The sensing device referred to here is a sensor or a device to which a plurality of sensors are connected. The sensing data is obtained by sensing the observation characteristics of the observation target with a sensing device. The object of observation here is an abstraction of phenomena in the real world (people, things, events, etc.). The observation characteristics are the characteristics of the observation target observed by the actual sensor. Observation targets are, for example, adults, homes, and automobiles. Observational characteristics of adults are, for example, systolic blood pressure, diastolic blood pressure, and heart rate. Household observation characteristics are, for example, electricity consumption, gas consumption, and water usage. The observed characteristics of the vehicle are, for example, position, speed, and fuel consumption rate (fuel consumption).

The provider registers the sensing device and the sensor-side metadata related to the sensing data sensed and provided by the sensing device in the network server. In addition, the user side registers the application that uses the sensing data and the application-side metadata related to the sensing data used in this application in the network server. The sensor-side metadata is information about the sensor and the attributes of the sensing data obtained by the sensor. The application-side metadata is information about the application itself and the attributes of the sensing data required by the application.

The network server matches the sensor-side metadata with the application-side metadata to extract a sensing device that can provide sensing data that meets the requirements of the application. The network server transmits a data flow control command to the sensor management device that manages the extracted sensing device. This data flow control command commands the distribution of sensing data from the data provider (sensing device) to the data usage destination (application).

Japanese Patent No. 5445722

However, the user side may have doubts as to whether the sensing data provided by the provider is appropriate when the sensing data provided by the provider changes rapidly. The sudden change in the sensing data may be due to a sudden change in the observation characteristics (sensing data is appropriate) or due to noise or a change in the installation state of the sensing device (sensing data is inappropriate). ) Is also available. When confirming whether the sensing data is appropriate, the user side inquires about it to the provider side.

In addition, on the provider side, in response to inquiries from the user side, the person in charge of management goes to the installation location of the sensing device and confirms whether the sensing data is inappropriate due to noise or changes in the installation status of the sensing device. , The confirmation result was responded to the user side.

Therefore, on the provider side, a lot of labor and cost are required for inquiries from the user side as to whether or not the sensing data is appropriate. In addition, even if the sensing data is appropriate, the user has to stop providing the service using the sensing data until there is a response from the provider.

An object of the present invention is to provide a technique for easily confirming whether or not the sensing data is appropriate.

The sensor management device of the present invention is configured as follows in order to achieve the above object.

The sensing data acquisition unit acquires the sensing data sensed by the sensing device. The first output control unit outputs the sensing data acquired by the sensing data acquisition unit at a predetermined timing to the user side. The storage unit stores the fluctuation confirmation data used for confirming the fluctuation of the sensing data acquired by the sensing data acquisition unit. The second output control unit outputs the fluctuation confirmation data stored in the storage unit corresponding to the detailed request to the user side in response to the detailed request from the user side.

According to this configuration, the user side makes a detailed request for sensing data to the sensor management device, so that the fluctuation confirmation data used for confirming the fluctuation of the sensing data acquired in the time zone corresponding to this request can be obtained. Can be obtained. The fluctuation confirmation data referred to here may be any data that can confirm the fluctuation of the sensing data. For example, the fluctuation confirmation data includes raw data of sensing data having a dense sensing cycle, work data generated in the process of generating sensing data having a dense sensing cycle, sensing data having a dense sensing cycle, and the like. Further, the fluctuation confirmation data to be output to the user side is not limited to one type, and may be a plurality of types.

Therefore, when the user has doubts about whether the sensed data is appropriate due to the sudden change in the provided sensing data, the time zone changed suddenly by making this detailed request. It is possible to confirm the fluctuation of the sensing data in. As a result, the user can easily confirm whether or not the sensing data is appropriate. In addition, since the provider side does not need to manually respond to the detailed request from the user side, the cost can be reduced.

Further, it is preferable that the second output control unit is configured to output the fluctuation confirmation data of the time zone corresponding to the detailed request to the user side. With this configuration, the user side can efficiently acquire the fluctuation confirmation data corresponding to the detailed request.

Further, the first output control unit controls the first output unit to output sensing data, and the second output control unit controls a second output unit different from the first output unit to fluctuate. It may be configured to output confirmation data. With this configuration, the first output unit and the second output unit can be switched according to the amount of data to be output to the user side.

Further, the second output control unit may be configured to prohibit the output of the fluctuation confirmation data if the user side code included in the detailed request is not appropriate, or the user side included in the detailed request. If the code and the authentication code are not appropriate, the output of the fluctuation confirmation data may be prohibited. In this case, the use of the sensing data can be appropriately restricted based on the usage contract or the like (it can be prevented from providing the fluctuation confirmation data to a person who does not have a usage contract).

The authentication code may be, for example, a one-time password that is set to be valid only for a certain period of time for each usage contract.

If the sensing device is configured to include a cache memory for storing the sensing data, the processing load on the input / output of the sensing data between the sensing device and the sensor management device can be suppressed. As a result, the power consumption of the sensing device can be suppressed. In particular, if the sensing device is battery-powered, the frequency of battery replacement can be reduced.

According to the present invention, it is possible to easily confirm whether or not the sensing data is appropriate.

It is a schematic diagram which shows the sensing data distribution system. It is a block diagram which shows the structure of the main part of a sensor management device. It is a block diagram which shows the structure of the main part of a sensing device. It is a flowchart which shows the operation of a sensor management device. It is a figure which shows the fluctuation of the sensing data which the sensor management apparatus transmitted to the user side system in s2. It is a figure which shows the fluctuation of the sensing data which can be confirmed in a user-side system according to a detailed request. It is a figure which shows the fluctuation of the sensing data which can be confirmed in a user-side system according to a detailed request.

Hereinafter, embodiments of the present invention will be described.

FIG. 1 is a schematic view showing a sensing data distribution system using the sensing information management system according to this example. The sensing data distribution system according to this example includes a network server 1, a sensor management device 2, a user-side system 3, and a sensing device 4.

This sensing data distribution system is a system that distributes sensing data traded between a provider side and a user side. The sensing device 4 is a sensor or a device to which a plurality of sensors are connected. The sensor management device 2 and the sensing device 4 are configurations on the provider side that provide sensing data. The sensor management device 2 corresponds to the sensor management unit referred to in the present invention. Further, the sensor management device 2 and the sensing device 4 which are the configurations of the provider correspond to the sensor device referred to in the present invention.

The user-side system 3 is a user-side configuration that uses sensing data. The network server 1 is configured to realize a sensing data distribution market, that is, a Sensing Data Trading Market (SDTM), which is a marketplace on the Internet for trading sensing data. The network server 1, the sensor management device 2, and the user-side system 3 are connected via the network 5 so as to be capable of data communication. In SDTM, sensing data in which the sensing device 4 senses the observation characteristics of the observation target is traded.

In this example, it is assumed that the contract for trading the sensing data with the SDTM described above is concluded between the provider side and the user side.

The provider side transmits the provided data catalog 100 (provided DC100) related to the sensing data to be traded (sold) by SDTM to the network server 1 and registers it. The provided data catalog 100 describes attribute information related to the provided sensing data. The user side transmits the usage data catalog 101 (utilization DC101) related to the sensing data to be traded (purchased) by SDTM to the network server 1. The usage data catalog 101 describes attribute information related to the sensing data to be used. The network server 1 performs a matching process for extracting a provider who can provide sensing data satisfying the usage data catalog 101 based on the registered provided data catalog 100 and the usage data catalog 101, and a user side with respect to the extracted provider. Performs data flow control processing to transmit a transmission command (data flow control command) of sensing data to. The provider side transmits the sensing data to the user side in response to the data flow control command.

As shown in FIG. 1, the sensor management device 2 on the providing side may transmit the sensing data to the user side system 3 via the network server 1, or the sensing data may be transmitted without going through the network server 1. It may be transmitted to the user side system 3.

The sensor management device 2 usually transmits the sensing data acquired at a predetermined timing to the user system 3. This predetermined timing is based on the sensing data provision contract between the provider and the user. This timing may be a timing that is periodically repeated, such as every 30 minutes or every hour, or may be an irregularly determined timing.

Further, when the sensor management device 2 receives the detailed request from the user side system 3, the sensor management device 2 acquires the detailed request in the time zone specified in the detailed request (the length of this time zone is, for example, 10 minutes or 20 minutes). The sensing data is collectively transmitted to the user system 3. As shown in FIG. 1, the user-side system 3 may transmit the detailed request to the sensor management device 2 via the network server 1, or transmit the detailed request to the sensor management device 2 without going through the network server 1. You may. The user-side system 3 can confirm the fluctuation of the sensing data in this time zone by the sensing data in the time zone received as a response to the detailed request.

The network server 1 has a configuration in which a plurality of providing systems (sensor management device 2 and sensing device 4) can be connected via the network 5. Further, the network server 1 has a configuration in which a plurality of user-side systems 3 can be connected via the network 5. In FIG. 1, the provider side and the user side are illustrated one by one.

Here, the configuration of the sensor management device 2 will be described. FIG. 2 is a block diagram showing a configuration of a main part of the sensor management device.

The sensor management device 2 includes a control unit 11, a sensing device connection unit 12, a communication unit 13, a data catalog storage database 14 (data catalog storage DB 14), an operation unit 15, and a user management database 16 (user management). It includes a DB 16), a device information storage unit 17, and a sensing data storage unit 18.

The control unit 11 controls the operation of each unit of the sensor management device 2 main body. Further, the control unit 11 includes a sensing device registration function unit 11a, a sensing data acquisition function unit 11b, a first communication control function unit 11c, a second communication control function unit 11d, a device information acquisition function unit 11e, and a data catalog generation function unit 11f. It has a user information acquisition function unit 11g and a user identification function unit 11h.

The control unit 11 of the sensor management device 2 is composed of a hardware CPU, a memory, and other electronic circuits. The hardware CPU has the above-mentioned sensing device registration function unit 11a, sensing data acquisition function unit 11b, first communication control function unit 11c, second communication control function unit 11d, device information acquisition function unit 11e, and data catalog generation function unit. It functions as 11f, a user information acquisition function unit 11g, and a user identification function unit 11h. Further, the memory has an area for developing the sensing data management program according to the present invention and an area for temporarily storing data and the like generated when the sensing data management program is executed. The control unit 11 may be an LSI in which a hardware CPU, a memory, and the like are integrated.

The sensing device connection unit 12 is configured to connect the sensing device 4 by wire or wirelessly. The sensing device connection unit 12 functions as an interface for controlling the input / output of data to / from the sensing device 4.

The communication unit 13 controls data communication with the network server 1 and the user system 3 via the network 5. The communication unit 13 includes a first communication unit 13a and a second communication unit 13b.

The first communication unit 13a communicates with the user-side system 3 by a communication method (for example, LPWA: Low Power Wide Area) that can cover a wide area with low power consumption. The second communication unit 13b communicates with the user-side system 3 by a communication method (for example, LTE (Long Term Evolution)) capable of high-speed communication. When the amount of data for data communication with the network server 1 and the user-side system 3 is small, the sensor management device 2 communicates with the first communication unit 13a. Further, the sensor management device 2 communicates with the second communication unit 13b when the amount of data in the data communication with the network server 1 and the user side system 3 is large. The sensor management device 2 can reduce power consumption and communication costs by properly using the first communication unit 13a and the second communication unit 13b. In particular, when the sensor management device 2 is battery-powered, the battery lasts a long time, so that there is an advantage that the time and effort required for battery replacement can be reduced.

The data catalog storage DB 14 stores the provided data catalog 100. At least all the provided data catalogs 100 registered in the network server 1 are stored in the data catalog storage DB 14. In other words, the data catalog storage DB 14 may store the provided data catalog 100 that is not registered in the network server 1.

Here, the provided data catalog 100 describes attribute information related to sensing data traded by SDTM. The provided data catalog 100 includes a sensing data provider, a sensing data provision period, a sensing data measurement location, a sensing data target, an event data specification, reference information, and data sales contract conditions.

The attribute information related to the sensing data provider is related to the organization (individual or business operator) that provides the sensing data, and the name of the organization (organization name), the katakana notation of the name of the organization (organization name kana), and the organization. It is composed of the contact information (contact information) of.

The attribute information related to the sensing data provision period is related to the sensing data provision period, and is composed of the date when the sensing data provision starts (start), the date when the sensing data provision ends (end), and the like. ..

The operation unit 15 receives an operator's input operation to the sensor management device 2 main body. The operation unit 15 has a display and a touch panel attached on the screen of the display. The operation unit 15 also controls the screen display on the display.

The user management DB 16 has an identification code (identification code) of each user-side system 3 contracted to provide the sensing data described in the provided data catalog 100 for each provided data catalog 100 stored in the data catalog storage DB 14. A so-called ID (identification) and an authentication code (so-called password) are associated and stored. That is, the user management DB 16 stores information (hereinafter, referred to as user information) of the user side system 3 contracted to provide sensing data.

For the user-side system 3 whose contract for providing sensing data has been canceled, the corresponding identification code (so-called ID (identification)) and authentication code (so-called password) are deleted from the user management DB 16.

The device information storage unit 17 stores the device information of the sensing device 4 registered in the sensor management device 2. The device information is information about the sensing device 4 (device model, device identifier, setting value in the device, etc.). The device model indicates the model of the sensing device 4. The device identifier is a code that is uniquely set for each sensing device 4 at the time of shipment from the factory, and is an identification code that identifies the sensing device 4.

The sensing data storage unit 18 stores the sensing data sensed by the sensing device 4 connected to the sensing device connection unit 12. Specifically, the sensing data storage unit 18 stores the sensing data sensed by the sensor and the measurement time in association with each other for each sensor. Further, the sensing data storage unit 18 stores fluctuation confirmation data used for confirming fluctuations in the sensing data. The fluctuation confirmation data referred to here may be any kind of data as long as the fluctuation of the sensing data can be confirmed. For example, the fluctuation confirmation data includes raw data of sensing data having a dense sensing cycle, work data generated in the process of generating sensing data having a dense sensing cycle, sensing data having a dense sensing cycle, and the like. Further, the fluctuation confirmation data stored in the sensing data storage unit 18 is not limited to one type, and may be a plurality of types. The sensing data storage unit 18 corresponds to the storage unit referred to in the present invention.

Next, the sensing device registration function unit 11a, the sensing data acquisition function unit 11b, the first communication control function unit 11c, the second communication control function unit 11d, the device information acquisition function unit 11e, and the data catalog generation function unit of the control unit 11 11f, the user information acquisition function unit 11g, and the user identification function unit 11h will be described.

The sensing device registration function unit 11a registers the sensing device 4 connected to the sensing device connection unit 12 in the sensor management device 2. The device information of the sensing device 4 registered by the sensing device registration function unit 11a is stored in the device information storage unit 17.

The sensing data acquisition function unit 11b acquires the sensing data sensed by the sensing device 4 from the sensing device 4 connected in the sensing device connection unit 12. The sensing data acquisition function unit 11b corresponds to the sensing data acquisition unit referred to in the present invention.

The first communication control function unit 11c controls the communication in the first communication unit 13a. Further, the second communication control function unit 11d controls the communication in the second communication unit 13b. The first communication control function unit 11c corresponds to the first output control unit referred to in the present invention, and the second communication control function unit 11d corresponds to the second output control unit referred to in the present invention. Further, the first communication unit 13a corresponds to the first output unit referred to in the present invention, and the second communication unit 13b corresponds to the second output unit referred to in the present invention.

The device information acquisition function unit 11e acquires device information from the sensing device 4 connected in the sensing device connection unit 12. The sensing device 4 stores device information.

The data catalog generation function unit 11f generates the provided data catalog 100 by using the device information acquired from the sensing device 4 by the device information acquisition function unit 11e and the template of the data catalog.

The user information acquisition function unit 11g extracts and acquires the user information included in the transmission data transmitted from the user side system 3 in the communication with the user side system 3 in the communication unit 13. The user identification function unit 11h searches the user management DB 16 based on the user information acquired by the user information acquisition function unit 11g.

FIG. 3 is a diagram showing a configuration of a main part of the sensing device. The sensing device 4 includes a sensor management device connection unit 41, a control unit 42, a cache memory 43, and a sensing unit 44.

The sensing device 4 may be an environment sensor that senses temperature, humidity, atmospheric pressure, noise, illuminance, ultraviolet rays, etc., or a biological sensor that senses systolic blood pressure, diastolic blood pressure, pulse, body movement flag, weight, and the like. It may be present, or it may be a sensor of a type other than these. Further, the sensing device 4 may have a configuration in which the observation target capable of sensing has one observation characteristic, or may have a configuration in which there are a plurality of observation characteristics.

The control unit 42 controls the operation of each unit of the sensing device 4 main body.

The sensing unit 44 has a sensor for sensing the observation characteristics of the observation target. The number of sensors included in the sensing unit 44 may be one or a plurality.

The sensor management device connection unit 41 is connected to the sensing device connection unit 12 by wire or wirelessly.

The control unit 42 temporarily stores the sensing data as a result of measurement by the sensing unit 44 and the fluctuation confirmation data in the cache memory 43. The control unit 42 inputs the data extracted from the data (sensing data and fluctuation confirmation data) stored in the cache memory 43 to the sensor management device 2 at a predetermined timing. The control unit 42 may delete the data transmitted to the sensor management device 2 from the cache memory 43. The timing for erasing the data stored in the cache memory 43 may be determined according to the storage capacity of the cache memory 43.

Instead of the cache memory 43, another type of storage element such as a ring buffer may be used.

The same applies when there are a plurality of sensing devices 4, and in that case, the device identifier of the sensing device 4 and the sensing data are associated with each other and stored in the sensing data storage unit 18.

As a result, the sensing data related to the plurality of sensing devices 4 can be stored for a certain period of time.

Next, the operation of the sensor management device 2 according to this example will be described. FIG. 4 is a flowchart showing the operation of the sensor management device. The sensor management device 2 determines whether or not data has been input from the sensing device 4 (s1). If the data is input from the sensing device 4, the sensor management device 2 stores the data input this time in the sensing data storage unit 18 (s2), and returns to s1. As described above, the sensing device 4 inputs the data extracted from the data (sensing data and fluctuation confirmation data) stored in the cache memory 43 to the sensor management device 2 at a predetermined timing. .. Therefore, the sensing device 4 can suppress the processing load on the data input to the sensor management device 2. As a result, the power consumption of the sensing device 4 can be suppressed. In particular, if the sensing device 4 is battery-powered, the frequency of battery replacement can be suppressed.

If no data has been input from the sensing device 4, the sensor management device 2 determines whether or not it is time to transmit the sensing data to the user-side system 3 (s3). When the sensor management device 2 determines that it is time to transmit the sensing data in s3, it transmits the sensing data to the user system 3 (s4) and returns to s1. In s4, the first communication control function unit 11c controls the first communication unit 13a and transmits the sensing data to the user side system 3. Since the sensing data transmitted to the user-side system 3 in s4 is the sensing data obtained by sensing the observation characteristics of the observation target at a certain timing, the amount of data is relatively small.

Further, when the sensor management device 2 determines that it is not the timing to transmit the sensing data in s3, the communication unit 13 determines whether or not the detailed request transmitted from the user side system 3 has been received (s5).

FIG. 5 is a diagram showing fluctuations in sensing data transmitted by the sensor management device to the user-side system 3 in s4. In the example shown in FIG. 5, the user-side system 3 receives the sensing data sensed at the times t1, t2, t3, and t4 from the sensor management device 2. The sensing data at time t3 has a large difference from the sensing data sensed at other timings (t1, t2, t4).

In this example, the time interval for the user system 3 to acquire the sensing data from the sensor management device 2 by s2 is 30 minutes or 1 hour.

In this case, the administrator of the user-side system 3 has doubts as to whether the sensing data at time t3 is appropriate. Specifically, is the sensing data at time t3 due to a change in the observation characteristics of the observation target (whether it is appropriate sensing data), noise, or a change in the installation state of the sensing device (whether it is due to changes in the installation state of the sensing device, etc.) Is it inappropriate sensing data?). The administrator of the user-side system 3 operates the user-side system 3 to confirm this suspicion, and sends a detailed request to the sensor management device 2. The sensor management device 2 receives the detailed request transmitted in this way at the communication unit 13.

When the sensor management device 2 determines in s5 that the detailed request transmitted from the user system 3 has not been received, the sensor management device 2 returns to s1.

When the sensor management device 2 determines in s5 that the detailed request transmitted from the user side system 3 is received, the user information acquisition function unit 11g determines that the user side system 3 included in the detailed request is received. The identification code and the authentication code of the above are extracted and obtained (s6). The sensor management device 2 determines whether or not the request is a detailed request from the user-side system 3 that has a contract for providing sensing data (s7). The determination related to s7 is performed by the user identification function unit 11h.

When the sensor management device 2 determines that the detailed request is not from the user-side system 3 that has a contract for providing sensing data in s7, the sensor management device 2 returns to s1. Therefore, the sensor management device 2 does not transmit the fluctuation confirmation data to the user-side system 3 that does not have a contract for providing sensing data.

When the sensor management device 2 determines that the request is a detailed request from the user-side system 3 that has a contract for providing sensing data in s7, the sensor management device 2 specifies the time zone of the sensing data requested by the user-side system 3 (s8). ). In s8, for example, in the case of a detailed request for the sensing data at time t3, the time zone from time t2 to time t3 is specified as the time zone of the sensing data requested by the user system 3.

In the sensor management device 2, the sensing data acquisition function unit 11b searches the sensing data storage unit 18, and the sensing data storage unit obtains the fluctuation confirmation data capable of confirming the fluctuation of the sensing data sensed in the time zone specified in s8. Read from 18 (s9). The sensor management device 2 transmits the fluctuation confirmation data read in s9 to the user system 3 (s10), and returns to s1. In s10, the second communication control function unit 11d is, by controlling the second communication section 13 b, and transmits the change confirmation data to the user side system 3. The fluctuation confirmation data transmitted to the user-side system 3 in s10 is data that can confirm the fluctuation of the sensing data sensed in the time zone specified in s8, so that the amount of data is relatively large.

As described above, the fluctuation confirmation data includes raw data of sensing data having a dense sensing cycle, work data generated in the process of generating sensing data having a dense sensing cycle, and sensing having a dense sensing cycle. Data etc. Further, the fluctuation confirmation data stored in the sensing data storage unit 18 may be one type or a plurality of types. Therefore, the fluctuation confirmation data transmitted to the user-side system 3 in s10 is not always one type.

Further, the fluctuation confirmation data read from the sensing data storage unit 18 by the sensing data acquisition function unit 11b in s9 is not necessarily the fluctuation confirmation data acquired in the time zone specified in s8. As described above, the fluctuation confirmation data read from the sensing data storage unit 18 by the sensing data acquisition function unit 11b in s9 is the fluctuation confirmation data capable of confirming the fluctuation of the sensing data sensed in the time zone specified in s8. If this is the case, fluctuation confirmation data may be included in which the acquired time zone is not included in the time zone specified in s8.

However, it is preferable that the amount of fluctuation confirmation data that is not particularly necessary for confirming the fluctuation of the sensing data sensed in the time zone specified in s8 is as small as possible.

In the user-side system 3, by confirming the fluctuation confirmation data transmitted by the sensor management device 2 in s8, it is possible to confirm whether or not the sensing data for which the detailed request has been made is appropriate. Specifically, as shown in FIG. 6, if the administrator of the user-side system can confirm that the sensing data in the time zone in which the detailed request is made fluctuates gently, the sensing data in which the detailed request is made will be released. It can be confirmed that it is appropriate. On the other hand, as shown in FIG. 7, if the administrator of the user-side system can confirm that the sensing data in the time zone in which the detailed request is made fluctuates rapidly, the sensing data in which the detailed request is made is not appropriate. You can check it.

Note that FIGS. 6 and 7 only show the fluctuation of the sensing data in the time zone of time t1 to t4 in order to make the fluctuation of the sensing data easy to understand.

As described above, the sensor management device 2 according to this example can easily and promptly confirm whether or not the sensing data is appropriate on the user side. In addition, the provider does not need to manually respond to inquiries from the user.

In the above example, the sensor management device 2 uses the identification code and the authentication code of the user side system 3 to determine whether or not the sensor management device 2 is the user side system 3 having a contract for providing sensing data. , The configuration may be such that it is determined whether or not the user side system 3 has a contract for providing sensing data only by the identification code of the user side system 3.

Further, in this example, in order to reduce the cost of data communication between the sensor management device 2 and the user side system 3, s4 communicates with the first communication unit 13a, and s10 communicates with the second communication unit 13b. I have to. The sensor management device 2 may be configured such that data communication with the user side system 3 is always performed by the second communication unit 13b (the first communication control function unit 11c and the first communication unit 13a are unnecessary. can.).

Further, the sensing device 4 may be configured in the same housing as the sensor management device 2, or may be configured separately. However, when the sensing device 4 is configured in the same housing as the sensor management device 2, the function of the cache memory 43 of the sensing device 4 is absorbed by the sensing data storage unit 18.

Further, in the above example, the sensing device 4 is configured to generate fluctuation confirmation data, but the sensor management device 2 may be configured to generate fluctuation confirmation data.

The present invention is not limited to the above-described embodiment as it is, and at the implementation stage, the components can be modified and embodied within a range that does not deviate from the gist thereof. In addition, various inventions can be formed by an appropriate combination of the plurality of components disclosed in the above-described embodiment. For example, some components may be removed from all the components shown in the embodiments. In addition, components from different embodiments may be combined as appropriate.

In addition, some or all of the above embodiments may be described as in the following appendix, but are not limited to the following.

(Appendix 1)
Have at least one hardware processor
The hardware processor
The fluctuation confirmation data used for confirming the fluctuation of the sensing data sensed by the sensing device is stored in the storage unit.
The sensing data acquired at a predetermined timing is output to the user side, and the data is output to the user side.
In response to the detailed request from the user side, the fluctuation confirmation data corresponding to the detailed request stored in the storage unit is output to the user side.
Sensor management device.

(Appendix 2)
With at least one hardware processor,
The fluctuation confirmation data used for confirming the fluctuation of the sensing data sensed by the sensing device is stored in the storage unit.
The sensing data acquired at a predetermined timing is output to the user side, and the data is output to the user side.
In response to the detailed request from the user side, the fluctuation confirmation data corresponding to the detailed request stored in the storage unit is output to the user side.
Sensing data provision method.

1 ... Network server 2 ... Sensor management device 3 ... User system 4 ... Sensing device 5 ... Network 11 ... Control unit 11a ... Sensing device registration function unit 11b ... Sensing data acquisition function unit 11c ... First communication control function unit 11d ... First 2 Communication control function unit 11e ... Device information acquisition function unit 11f ... Data catalog generation function unit 11g ... User information acquisition function unit 11h ... User identification function unit 12 ... Sensing device connection unit 13 ... Communication unit 13a ... First communication unit 13b ... Second communication unit 14 ... Data catalog storage database 15 ... Operation unit 16 ... User management database 17 ... Device information storage unit 18 ... Sensing data storage unit 41 ... Sensor management device connection unit 42 ... Control unit 43 ... Cache memory 44 ... Sensing unit 100 ... Provided data catalog 101 ... Usage data catalog

Claims (8)

A sensing data acquisition unit that acquires sensing data sensed by a sensing device,
A first output control unit that outputs the sensing data acquired by the sensing data acquisition unit at a predetermined timing to the user side, and a first output control unit.
A storage unit that stores fluctuation confirmation data used for confirming whether the sensing data acquired by the sensing data acquisition unit is appropriate, and a storage unit.
A sensor management unit including a second output control unit that is stored in the storage unit and outputs the fluctuation confirmation data corresponding to the detailed request to the user side in response to the detailed request from the user side. .. The first output control unit controls the first output unit and outputs the sensing data.
The sensor management unit according to claim 1, wherein the second output control unit controls a second output unit different from the first output unit to output the fluctuation confirmation data. The second output control unit
The sensor management unit according to claim 1 or 2, which prohibits the output of the fluctuation confirmation data if the user-side code included in the detailed request is not appropriate. The second output control unit
The sensor management unit according to claim 1 or 2, which prohibits the output of the fluctuation confirmation data if the user-side code and the authentication code included in the detailed request are not appropriate. The sensor management unit according to any one of claims 1 to 4, wherein the second output control unit outputs the fluctuation confirmation data in a time zone corresponding to the detailed request to the user side. A sensor device comprising the sensor management unit according to any one of claims 1 to 5 and a sensing device connected to the sensor management unit.
The sensing device is a sensor device including a cache memory for storing the sensing data. The computer
A storage step that accumulates the sensing data sensed by the sensing device in the storage unit,
A first output control step that outputs the sensing data acquired at a predetermined timing to the user side, and
In response to the detailed request from the user side, the fluctuation confirmation data corresponding to the detailed request is selected from the fluctuation confirmation data used for confirming whether the sensing data stored in the storage unit is appropriate. A sensing data management method for executing a second output control step of extracting and outputting to the user side. A storage step that accumulates the sensing data sensed by the sensing device in the storage unit,
A first output control step that outputs the sensing data acquired at a predetermined timing to the user side, and
In response to the detailed request from the user side, the fluctuation confirmation data corresponding to the detailed request is selected from the fluctuation confirmation data used for confirming whether the sensing data stored in the storage unit is appropriate. A sensing data management program that causes a computer to execute a second output control step that extracts and outputs to the user side.

Images