JP2021190781A - Method for confirming correspondence between sensing target and sensor and correspondence confirmation system - Google Patents

Abstract

To provide a method for confirming correspondence between a sensing target and a sensor without paring sensors.SOLUTION: A correspondence confirmation method for confirming quality of correspondence between a sensor attached to a sensing target and the sensing target includes the steps of: acquiring positional information on a first sensor fixed and attached to the sensing target; acquiring positional information on a second sensor removably attached to the sensing target; and comparing the positional information on the first sensor with the positional information on the second sensor to calculate a distance and, when the distance is equal to or larger than a threshold, determining that correspondence between the sensing target and the second sensor is inconsistent.SELECTED DRAWING: Figure 14

Description

The present invention relates to a technique for confirming the correspondence between a sensing object and a sensor attached to the sensing object.

There is a mechanism called IoT (Internet of Things) in which "things" such as sensors and devices are connected to the cloud and servers via the Internet and are mutually controlled by exchanging information. In the IoT system, device operation management such as life / death monitoring and status monitoring of sensors and devices, setting changes and firmware updates is required.

On the other hand, if there is a discrepancy in the relationship between the sensor and the object to be sensed, there arises a problem that the sensor data does not sense the object to be sensed correctly. Therefore, there is a need to grasp the correspondence relationship between the sensor and the object to be sensed by device management as well as the conventional device management. For example, in livestock IoT, a cattle management system that manages the health condition of cattle by attaching a wearable sensor to the cattle is adopted. Here, if a mistake occurs when the wearable sensor is attached, the sensor data obtained by measuring different cows will be managed, and the health condition of the cows cannot be managed correctly.

On the other hand, in Patent Document 1, "a terminal positioning system that estimates the position of a positioning target terminal in a facility, and is a beacon radio wave that is arranged at a plurality of predetermined locations in the facility and represents different beacon identification information. A plurality of beacons to be transmitted, a receiving unit provided in the positioning target terminal to receive the beacon radio waves, a storage unit for storing storage information in which the installation position of each beacon and the beacon identification information are associated with each other, and the above. A terminal positioning system including a calculation processing unit that estimates and calculates the position of the positioning target terminal based on the received information of the beacon radio wave and the stored information. ”(Claim 1) is disclosed.

Further, in Patent Document 2, "a pairing method in an in-vehicle terminal for pairing a short-range wireless communication with a mobile terminal, wherein the in-vehicle terminal detects a trigger for starting a pairing process. When the trigger for starting the pairing process is detected, the step of starting the search mode for searching the mobile terminal and the search from the mobile terminal when the mobile terminal cannot be detected in the search mode are performed. A step of shifting to the standby mode and a pairing method in an in-vehicle terminal having the standby mode. ”(Claim 2) are disclosed.

Japanese Unexamined Patent Publication No. 2019-100708 Japanese Unexamined Patent Publication No. 2012-29027

Patent Document 1 discloses a technique of confirming the position of a sensor by a beacon. However, when the sensing target dynamically changes its position, the correspondence between the sensing target and the sensor cannot be determined only by the position of the sensor.

Further, Patent Document 2 discloses a technique for pairing two devices. If this is applied, the relationship between the sensing target and the sensor can be confirmed by pairing the individual identification tag fixed to the sensing target with the sensor and assigning the ID of the individual identification tag when the sensor transmits data. .. However, the sensor is often battery-powered, and it is often difficult to implement extra processing other than sensing due to the problem of power consumption.

An object of the present invention is to provide a method for confirming the correspondence between a sensing target and a sensor without pairing the sensors with each other.

In the present invention, a plurality of sensors such as an individual identification sensor and a state confirmation sensor attached to a sensing target are associated with each other. Then, when the position information of the various sensors associated with the sensing target deviates by a certain distance or more, it is determined that a mismatch has occurred in the correspondence between the sensing target and the sensor.

To give an example of the "method for confirming the correspondence between the sensing target and the sensor" of the present invention, it is a correspondence confirmation method for confirming the quality of the correspondence between the sensor attached to the sensing target and the sensing target. A step of acquiring the position information of the first sensor fixedly attached to the sensing target, a step of acquiring the position information of the second sensor detachably attached to the sensing target, and the first sensor. The step of comparing the position information of the second sensor with the position information of the second sensor to obtain the distance, and if the distance is equal to or greater than the threshold value, the step of determining that the correspondence between the sensing target and the second sensor does not match. It is a method of confirming the correspondence between the sensing target and the sensor.

According to the present invention, it is possible to avoid a mismatch in the correspondence between the sensing target and the sensor, and it is possible to prevent the sensor data from being mixed up.

Issues, configurations and effects other than those described above will be clarified by the following description of the embodiments.

It is a figure which showed the whole structure of the cattle management system of Example 1. FIG. It is a figure which showed the structure of the cattle management server of Example 1. FIG. It is a figure which showed the structure of the cattle management collection held by the cattle management server of Example 1. FIG. It is a figure which showed the structure of the wearable sensor management collection held by the cow management server of Example 1. FIG. It is a figure which showed the flow of the cattle registration processing in the cattle information management part held by the cattle management server of Example 1. FIG. It is a figure which showed the flow of the input process of the cattle management information in the cattle information management part held by the cattle management server of Example 1. FIG. It is a figure which showed the flow of the output processing of the cattle management information in the cattle information management part held by the cattle management server of Example 1. FIG. It is a figure which showed the flow of the registration process of the wearable sensor in the wearable sensor management part held by the cow management server of Example 1. FIG. It is a figure which showed the flow of the input process of the sensor data of the wearable sensor in the wearable sensor management part held by the cow management server of Example 1. FIG. It is a figure which showed the configuration of the device management server of Example 1. FIG. It is a figure which showed the structure of the device management collection held by the device management server of Example 1. FIG. It is a figure which showed the structure of the gateway management collection held by the device management server of Example 1. FIG. It is a figure which showed the flow of the specific process of the wearable sensor corresponding to a cow in the mapping management part held by the device management server of Example 1. FIG. It is a figure which showed the flow of the correspondence relationship confirmation process of a cow and a wearable sensor in the mapping management part held by the device management server of Example 1. FIG. It is a figure which showed the device state display GUI displayed by the device management server of Example 1. FIG. It is a figure which showed the whole structure of the IoT system of Example 2. FIG. It is a figure which showed the structure of the sensing management server of Example 2. FIG. It is a figure which showed the flow of the identification process of the sensor which is related to the sensing target in the mapping management part held by the device management server of Example 2. FIG. It is a figure which showed the flow of the correspondence relationship confirmation process of a sensing target and a sensor in the mapping management part held by the device management server of Example 2. FIG. It is a figure which showed the configuration of the device management server of Example 3. FIG. It is a figure which showed the structure of the tag management collection held by the device management server of Example 3. FIG. It is a figure which showed the flow of the identification process of the sensor which is related to the sensing target in the mapping management part held by the device management server of Example 3. FIG. It is a figure which showed the flow of the correspondence relationship confirmation process of a sensing target and a sensor in the mapping management part held by the device management server of Example 4. FIG. It is a figure which showed the flow of the process of the sensing management server of Example 5. It is a figure which showed the flow of the process of the sensing management server of Example 6.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. In addition, in each figure for demonstrating an embodiment, the same constituent elements are given the same name and reference numeral, and the repeated description thereof will be omitted.

FIG. 1 is a schematic diagram of a cattle management system for managing cattle in a ranch or the like to which the first embodiment of the present invention is applied. As shown in the figure, the cow management system of this embodiment includes at least one cow 101, an ear tag 102 fixed to the cow 101, a wearable sensor 103 attached to the cow, a cow management server 104, and device management. It is composed of a server 105, at least one tag reading terminal 106, and at least one gateway 107. The ear tag 102 and the tag reading terminal 106 are connected via the tag network 108, and the wearable sensor 103 and the gateway 107 are connected by the sensor network 109. The cow management server 104, the device management server 105, the tag reading terminal 106, and the gateway 107 are connected by the management network 110.

The tag reading terminal 106 is equipped with a GPS function and can acquire its own position information. The tag reading terminal 106 reads the individual identification number held by the ear tag 102, transmits the position information and the individual identification number to the cattle management server 104, and acquires the cattle management information held by the cattle management server 104. indicate. The tag reading terminal 106 reads the ear tag 102 at a short distance of, for example, within 10 cm.

The wearable sensor 103 attached to the cow is a state confirmation sensor, measures the activity amount of the cow 101, and periodically transmits it to the gateway 107. When the gateway 107 acquires data from the wearable sensor 103, it transfers the data to the cow management server 104. Further, the gateway 107 can position the position of the wearable sensor 103 by the radio wave strength of the wearable sensor 103, and responds with the position information of the wearable sensor 103 in response to a request.

In this embodiment, the wearable sensor 103 transmits data to the cow management server 104 via the gateway 107, but in addition, for example, the wearable sensor 103 directly transmits data to the cow management server 104 using a mobile line. There may be. At that time, the position information of the wearable sensor 103 (such as the position information of the SIM) shall be acquired from the mobile line provider.

FIG. 2 is a diagram showing the configuration of the cow management server 104. The cow management server 104 includes a CPU 201, a memory 202, a storage device 203, an input device 204, an output device 205, and a communication port 206.

The storage device 203 holds a database 210, a program constituting the cow information management unit 221 and a program constituting the wearable sensor information management unit 222, and these programs are loaded into the memory 202 and executed at the time of execution.
The database 210 holds a cow management collection 211 that holds information for managing cows and a wearable sensor management collection 212 for managing wearable sensors.

The cattle management collection 211 will be described with reference to FIG.
The cow management collection 211 is composed of one or more documents 300.
Document 300 includes a thing_id 310 that stores an individual identification number that identifies a cow, a static 320 that stores static information of the cow such as date of birth and gender, and a state 330 that stores management information of the cow that occurs daily such as milk yield. , Consists of a sensor 340 that stores wearable sensor information.

The wearable sensor management collection 212 will be described with reference to FIG.
The wearable sensor management collection 212 is composed of one or more documents 400.
The document 400 is composed of a sensor_id 410 that stores an ID that identifies the wearable sensor, and a mapped_thing 420 that stores the individual identification number of the cow to which the wearable sensor is attached.

FIG. 5 is a flowchart showing the processing performed at the time of cattle registration in the cattle information management unit 221.
When the cow information management unit 221 receives the individual identification number of the newly registered cow 101 (S501), the cow information management unit 221 creates a new document in which the received individual identification number is stored in the thing_id 310 in the cow management collection 211. At this time, if information other than individual information is included, it is stored in the static 320 of the new document (S502). Finally, a response of registration completion is returned (S503).
The above is the description of the processing performed at the time of cattle registration in the cattle information management unit 221.

FIG. 6 is a flowchart showing the processing performed at the time of inputting the cattle management information that occurs every day in the cattle information management unit 221.
When the cattle information management unit 221 receives the cattle management information (S601), the cattle management collection 211 searches for the document 300 whose thing_id 310 matches the individual identification number, and stores the received cattle management information in the state 330 (S602). ). Finally, the input completion is replied (S603).
The above is the description of the process performed when the cattle management information is input in the cattle information management unit 221.

FIG. 7 is a flowchart showing the processing performed when the cow information is output in the cow information management unit 221.
Upon receiving the cow information request (S701), the cow information management unit 221 searches the cow management collection 211 for the document 300 whose thing_id 310 matches the individual identification number included in the request (S702), and searches for the contents of the matched document 300. Respond (S703).
Next, the cow information management unit 221 confirms whether the document 400 in which the individual identification number included in the request is stored exists in the mapped_thing 420 from the wearable sensor management collection 212 (S704). If it exists, the device management server 105 is requested to confirm the correspondence between the cow and the sensor (S705). If it does not exist, the device management server 105 is requested to confirm whether the sensor corresponding to the cow exists (S706).
The above is a description of the processing performed when the cow information is output in the cow information management unit 221.

FIG. 8 is a flowchart showing a process performed at the time of registration of the wearable sensor in the wearable sensor information management unit 222.
When the wearable sensor information management unit 222 receives the device ID of the wearable sensor 103 to be newly registered (S801), the wearable sensor information management unit 222 creates a new document in the wearable sensor management collection 212 in which the device ID received in the sensor_id 410 is stored (S802). Finally, the response of registration completion is returned (S803).
The above is a description of the processing performed when the wearable sensor is registered in the wearable sensor information management unit 222.

FIG. 9 is a flowchart showing a process performed at the time of inputting data of the wearable sensor in the wearable sensor information management unit 222.
Upon receiving the sensor data (S901), the wearable sensor information management unit 222 searches the wearable sensor management collection 212 for the document 400 matching the device ID included in the sensor data received by the sensor_id 410, and acquires the value of mapped_thing 420. (S902). Next, the document 300 whose thing_id 310 matches the above mapped_thing 420 is searched from the cow management collection 211, the received sensor data is added to the sensor 340 (S903), and the input completion response is returned (S904).

FIG. 10 is a diagram showing the configuration of the device management server 105.
The device management server 105 includes a CPU 1001, a memory 1002, a storage device 1003, an input device 1004, an output device 1005, and a communication port 1006.
The storage device 1003 holds a database 1010 and a program constituting the mapping management unit 1021, and at the time of execution, this program is loaded into the memory 1002 and executed.
The database 1010 holds a device management collection 1011 that holds information for managing devices, and a gateway management collection 1012 that holds information about the gateway 107 that is the location information acquisition destination of the wearable sensor 103.

The device management collection 1011 will be described with reference to FIG.
The device management collection 1011 is composed of one or more documents 1100. The document 1100 is composed of a sensor_id 1110 that stores an ID that identifies a device, and a url 1120 that stores a destination for collecting sensor position information.

The gateway management collection 1012 will be described with reference to FIG.
The gateway management collection 1012 consists of one or more documents 1200. The document 1200 is composed of a gateway_id1210 that stores an ID that identifies the gateway 107, and a url1220 that stores a destination for collecting sensor position information.

FIG. 13 is a flowchart showing a specific process of the wearable sensor 103 corresponding to the cow 101 in the mapping management unit 1021.
When the mapping management unit 1021 receives the confirmation request of the sensor corresponding to the cow (S1301), the mapping management unit 1021 acquires the position information acquired from the tag reading terminal that has read the cow's ear tag included in the confirmation request as the cow's position information (S1301). S1302).
Next, the position information of the wearable sensor 103 is requested from the url 1220 stored in all the documents 1200 of the gateway management collection 1012, and the position information of all the wearable sensors 103 is acquired (S1303).
Next, the position information of the cow 101 is compared with the position information of all the wearable sensors 103, and the wearable sensor 103 closest to the cow 101 is specified (S1304).
Next, it is confirmed whether the distance between the cow 101 and the specified wearable sensor 103 is within a predetermined threshold value (S1305). If it is within the threshold value, the device ID of the specified wearable sensor is returned (S1306). If not, the answer is not applicable (S1207).
The above is the description of the specific processing of the wearable sensor corresponding to the cow in the mapping management unit 1021.

FIG. 14 is a flowchart showing a process performed when the mapping management unit 1021 confirms the correspondence between the cow 101 and the wearable sensor 103.
When the mapping management unit 1021 receives the correspondence relationship confirmation request (S1401), the mapping management unit 1021 acquires the position information acquired from the tag reading terminal that has read the cow's ear tag included in the confirmation request as the cow's position information (S1402).
Next, the sensor_id 1110 searches the device management collection 1011 for the document 1100 that matches the sensor_id included in the confirmation request, requests the position information of the wearable sensor 103 from the url 1120, and the position information of the corresponding wearable sensor 103 from the gateway 107. (S1403).
Next, the position information of the cow and the position information of the wearable sensor are compared to specify the distance (S1404).
Next, it is confirmed whether the specified distance is within the predetermined threshold value (S1405). If it is within the threshold value, it responds normally (S1406). Otherwise, an alert is generated (S1407). The alert may be sound or display.
The above is a description of the processing performed when the mapping management unit 1021 confirms the correspondence between the cow 101 and the wearable sensor 103.

FIG. 15 is an example of the device status display GUI displayed by the device management server 105.
The device status display GUI consists of sensor_id1501 that identifies the wearable sensor, status1502 that indicates the life or death of the wearable sensor, mapped_thing1503 that indicates the cow to which the wearable sensor is attached, and mapping_status1504 that indicates the status of the correspondence between the cow and the wearable sensor. To. If the correspondence between the cow and the wearable sensor matches, it is displayed as OK, and if it does not match, it is displayed as NG.

Although the cow management server 104 and the device management server 105 are separate servers in FIG. 1, the two servers may be combined into one management server (management device).

In this embodiment, the position information of a plurality of sensors (fixed and attached earmarks and removable wearable sensor) attached to a cow which is the same sensing target is acquired, and the position information of the earmarks and the wearable are acquired. The distance is specified by comparing the position information of the sensors, and if the specified distance is not within the threshold value, it is determined that the correspondence between the cow and the wearable sensor does not match, and an alert is generated.

According to this embodiment, it is possible to prevent the correspondence between the cow and the wearable sensor from becoming inconsistent, and it is possible to manage the cow using the correct sensor data.

FIG. 16 is a schematic diagram of the IoT system according to the second embodiment of the present invention. This embodiment is used for an article as a sensing target. The configuration of the second embodiment is almost the same as the configuration of the first embodiment, but the cow 101 is the object to be sensed 1601, the ear tag 102 is the individual identification tag 1602, the wearable sensor 103 is the sensor 1603, and the cow management server 104. Has been changed to the sensing management server 1604.

The individual identification tag 1602 connects to the management network 110 via a mobile line. The location information of the individual identification tag 1602 is obtained from the mobile line carrier. The individual identification tag 1602 may communicate via the tag reading terminal 106 as in the first embodiment, and the position information of the tag reading terminal 106 may be used as the position information of the individual identification tag.

FIG. 17 shows the configuration of the sensing management server. The storage device 203 of the sensing management server 1604 holds a database 210, a program constituting the sensing target information management unit 1721, and a program constituting the sensor information management unit 1722, and loads these programs into the memory 202 at the time of execution. And execute. Further, the database 210 holds a sensing target management collection 1711 that holds information for managing the sensing target, and a sensor management collection 1712 that holds the sensor management collection 1712 for managing the sensor.

Further, the processing in the mapping management unit 1021 of the device management server 105 is different.

FIG. 18 is a flowchart showing the identification process of the sensor related to the object to be sensed in the mapping management unit 1021.
When the mapping management unit 1021 receives the confirmation request of the sensor related to the object (S1801), the mapping management unit 1021 acquires the position information of the individual identification tag 1602 included in the confirmation request and sets it as the position of the object to be sensed (S1802).
Next, the position information of the sensor 1603 is requested from the url 1220 stored in all the documents 1200 of the gateway management collection 1012, and the position information of all the sensors 1603 is acquired (S1803).
Next, the position information of the object 1601 to be sensed is compared with the position information of all the sensors 1603, and the sensor 1603 closest to the object 1601 to be sensed is specified (S1804).
Next, it is confirmed whether the distance between the object 1601 to be sensed and the specified sensor 1603 is within a predetermined threshold value (S1805). If it is within the threshold value, the device ID of the identified sensor 1603 is returned (1806). If not, the answer is not applicable (S1807).
The above is the description of the specific processing of the sensor 1603 corresponding to the thing 1601 to be sensed in the mapping management unit 1021.

FIG. 19 is a flowchart showing a process performed when the mapping management unit 1021 confirms the correspondence between the object 1601 to be sensed and the sensor 1603.
When the mapping management unit 1021 receives the correspondence relationship confirmation request (S1901), the mapping management unit 1021 acquires the position information of the individual identification tag 1602 included in the confirmation request as the position information of the object to be sensed (S1902).
Next, the sensor_id 1110 searches the device management collection 1011 for the document 1100 that matches the sensor_id included in the confirmation request, requests the position information of the sensor 1603 from the url 1120, and acquires the position information of the sensor 1603 from the gateway 107 (. S1903).
Next, the position information of the object 1601 to be sensed is compared with the position information of the sensor 1603, and the distance is specified (S1904).
Next, it is confirmed whether the specified distance is within the predetermined threshold value (S1905). If it is within the threshold value, it responds normally (S1906). Otherwise, an alert is generated (S1907).
The above is a description of the processing performed when the mapping management unit 1021 confirms the correspondence between the object 1601 to be sensed and the sensor 1603.

According to this embodiment, it is possible to prevent the correspondence between the article to be sensed and the sensor from becoming inconsistent, and it is possible to realize an IoT system using correct sensor data.

Hereinafter, Example 3 of the present invention will be described with reference to figures and tables. The configuration of the third embodiment is almost the same as the configuration of the second embodiment, but the addition of the individual identification tag management collection to the device management server and the processing in the mapping management unit 1021 of the device management server 105 are different.

FIG. 20 shows the configuration of the device management server 105. In addition to the configuration of FIG. 10, the database 1010 includes an individual identification tag management collection 2001.

FIG. 21 shows the configuration of the individual identification tag management collection 2001 held by the device management server 105. The individual identification tag management collection 2001 is composed of one or more documents 2100. The document 2100 is composed of a tag_id2110 that stores an ID that identifies an individual identification tag, and a url2120 that stores a destination for collecting the position information of the individual identification tag.

FIG. 22 is a flowchart showing a process of confirming the sensing target object 1601 related to the sensor 1603 in the mapping management unit 1021.
When the mapping management unit 1021 receives the confirmation request of the object to be sensed related to the sensor (S2201), the mapping management unit 1021 searches the device management collection 1011 for the document 1100 in which the sensor_id 1110 matches the sensor_id included in the confirmation request, and for the url 1120. The position information of the sensor 1603 is requested, and the position information of the sensor 1603 is acquired from the gateway 107 (S2202).
Next, the position information of the individual identification tag 1602 is requested from the url 2120 stored in all the documents of the individual identification tag management collection 2001, the position information of all the individual identification tags 1602 is acquired, and the object to be sensed. It is used as position information (S2203).
Next, the position information of the sensor 1603 and the position information of all the sensing target objects 1601 are compared, and the sensing target object 1601 having the closest distance to the sensor 1603 is specified (S2204).
Next, it is confirmed whether the distance between the sensor 1603 and the object to be sensed 1601 specified is within a predetermined threshold value (S2205). If it is within the threshold value, the thing_id of the specified object 1601 to be sensed is returned (S2206). If not, the answer is not applicable (S2207).
The above is the description of the specific processing of the thing 1601 to be sensed corresponding to the sensor 1603 in the mapping management unit 1021.

According to this embodiment, the correspondence between the sensing target and the sensor can be confirmed from the sensor starting point. As a result, it is possible to prevent the correspondence between the sensing target and the sensor from becoming inconsistent, and it is possible to realize an IoT system using correct sensor data.

Hereinafter, Example 4 of the present invention will be described with reference to figures and tables. The configuration of the fourth embodiment is almost the same as the configuration of the second embodiment, but the processing in the mapping management unit 1021 of the device management server 105 is different.

FIG. 23 is a flowchart showing a process of confirming the sensing target thing 1601 related to the sensor 1603 in the mapping management unit 1021.
When the mapping management unit 1021 receives the correspondence confirmation request (S2301), the mapping management unit 1021 acquires the position information of the individual identification tag 1602 included in the confirmation request as the position information of the object to be sensed (S2302).
Next, the position information of the sensor 1603 is requested from the url 1220 stored in all the documents 1200 of the gateway management collection 1012, and the position information of all the sensors 1603 is acquired (S2303).
Next, the position information of the object 1601 to be sensed is compared with the position information of all the sensors 1603, and the sensor 1603 closest to the object 1601 to be sensed is specified (S2304).
Next, it is confirmed whether the specified sensor 1603 having the shortest distance is the sensor to be confirmed (S2305). If it is a sensor to be confirmed, it responds normally (S2306). Otherwise, an alert is generated (S2307).
The above is a description of the processing performed when the mapping management unit 1021 confirms the correspondence between the object 1601 to be sensed and the sensor 1603.

According to this embodiment, it is possible to prevent the correspondence between the object to be sensed and the sensor from becoming inconsistent, and it is possible to realize an IoT system using correct sensor data.

The configuration of the fifth embodiment is almost the same as the configuration of the second embodiment, but the processing of the sensor information management unit 1722 of the sensing management server 1604 is different.

FIG. 24 shows the processing flow of the sensing management server 1604. When the sensor information management unit 1722 of the sensing management server 1604 receives an alert from the device management server 105 (S2401), it acquires the sensor_id of the alert target sensor included in the alert (S2402).
After the alert, it is determined that the sensor data transmitted from the sensor is not accurate, and the sensor data is not saved and discarded (S2403).

According to this embodiment, it is possible to avoid contamination of the analysis result due to inaccurate sensor data, and it is possible to realize an IoT system using only correct sensor data.

The configuration of the sixth embodiment is almost the same as the configuration of the second embodiment, but the processing of the sensor information management unit 1722 of the sensing management server 16040 is different.

FIG. 25 shows the processing flow of the sensing management server 1604 of the sixth embodiment. When the sensor information management unit 1722 receives an alert from the device management server 105 (S2501), it determines whether there is an unprocessed alert and executes the following processing for each sensor_id included in the alert (S2502).
Acquire the sensor_id of the alert target sensor included in the alert (S2503).
Next, the document 400 in the sensor management collection 1712 (document is shown in FIG. 4) is searched by sensor_id410, and the object to be sensed is identified from the value of mapped_thing420 of the hit document 400 (identify the object having the wrong correspondence). (S2504).
Next, the device management server 105 is requested to identify the sensor related to the sensor to be sensed 1601, and the correspondence between the thing_id 310 of the thing 1601 to be sensed correctly (the document is FIG. 3) and the sensor_id 410 of the sensor 1603 is grasped (S2505). ).
Next, the document 300 in the sensing target management collection 1711 is searched by the thing_id310 of the object to be sensed incorrectly registered, and the content of the sensor 340 of the hit document 300 is searched by the thing_id310 of the thing to be sensed correctly and hit. Move to the sensor 340 of the document 300 (S2506).

According to this embodiment, the sensor data before the discrepancy is noticed can be correctly used, and the IoT system without waste of the sensor data can be realized.

101 ... Cow, 102 ... Earmark, 103 ... Wearable sensor, 104 ... Sensing management server, 105 ... Device management server, 106 ... Tag reading terminal, 107 ... Gateway, 108 ... Tag network, 109 ... Sensor network, 110 ... Management network,
201 ... CPU, 202 ... memory, 203 ... storage device, 204 ... input device, 205 ... output device, 206 ... communication port, 210 ... database, 211 ... cow management collection, 212 ... wearable sensor management collection, 221 ... cow information management Department 222 ... Wearable sensor information management department,
300 ... Document, 400 ... Document,
1001 ... CPU, 1002 ... Memory, 1003 ... Storage device, 1004 ... Input device, 1005 ... Output device, 1006 ... Communication port, 1010 ... Database, 1011 ... Device management collection, 1012 ... Gateway management collection, 1021 ... Mapping management unit,
1100 ... Document, 1200 ... Document,
1601 ... Article to be sensed, 1602 ... Individual identification tag, 1603 ... Sensor, 1604 ... Sensing management server,
1711 ... Sensing target management collection, 1712 ... Sensor management collection, 1721 ... Sensing target information management department, 1722 ... Sensor information management department,
2001 ... Fixed identification tag management collection, 2100 ... Documents.

Claims (15)

It is a correspondence relationship confirmation method for confirming the quality of the correspondence between the sensor attached to the sensing target and the sensing target.
The step of acquiring the position information of the first sensor fixedly attached to the sensing target, and
The step of acquiring the position information of the second sensor detachably attached to the sensing target, and
The distance is obtained by comparing the position information of the first sensor with the position information of the second sensor, and if the distance is equal to or greater than the threshold value, the correspondence between the sensing target and the second sensor does not match. Steps to judge and
How to check the correspondence between the sensing target and the sensor. In the method for confirming the correspondence between the sensing target and the sensor according to claim 1.
A method for confirming the correspondence between the sensing target and the sensor, which comprises a step of issuing an alarm when it is determined that the correspondence between the sensing target and the second sensor does not match. In the method for confirming the correspondence between the sensing target and the sensor according to claim 1.
As the position information of the first or second sensor, the position information of the reading terminal that reads the sensor data, the position information determined from the radio field strength at the time of data transmission, or the position information of the SIM held by the mobile line carrier shall be used. A method for confirming the correspondence between the sensing target and the sensor. In the method for confirming the correspondence between the sensing target and the sensor according to claim 1.
A method for confirming the correspondence between a sensing target and a sensor, which comprises confirming the correspondence between the sensing target and the sensor by using data reception from a specific sensor as a trigger. In the method for confirming the correspondence between the sensing target and the sensor according to claim 1.
A method for confirming the correspondence between a sensing target and a sensor, which comprises searching for another sensor having a short distance from the first sensor or the second sensor as a starting point, and specifying the correspondence between the sensing target and the sensor. In the method for confirming the correspondence between the sensing target and the sensor according to claim 1.
A method for confirming the correspondence between a sensing target and a sensor, which comprises a step of discarding sensor data when a mismatch occurs between the sensing target and the sensor. In the method for confirming the correspondence between the sensing target and the sensor according to claim 1.
When a mismatch occurs in the correspondence between the sensing target and the sensor, the sensor data registered as the sensing data of the wrong sensing target is re-registered as the sensing data of the correct sensing target. How to check the correspondence between the target and the sensor. It is a correspondence relationship confirmation method for confirming the quality of the correspondence between the sensor attached to the sensing target and the sensing target.
The step of acquiring the position information of the first sensor fixedly attached to the sensing target, and
A step to acquire the position information of a plurality of second sensors detachably attached to a plurality of sensing targets, and a step of acquiring the position information.
A step of searching for a sensor having the position information closest to the position information of the first sensor from the plurality of second sensors.
It is determined whether the sensor having the closest position information is a sensor having a correspondence relationship, and if it is not a sensor having a correspondence relationship, it is determined that the correspondence relationship between the sensing target and the second sensor does not match, and an alarm is issued. The steps to be emitted and
How to check the correspondence between the sensing target and the sensor. It is a correspondence relationship confirmation system that confirms the quality of the correspondence between the sensor attached to the sensing target and the sensing target.
The first sensor fixedly attached to the sensing target and
A second sensor detachably attached to the sensing target,
The first position information acquisition means for acquiring the position information of the first sensor, and
A second position information acquisition means for acquiring the position information of the second sensor, and
The position information of the first sensor is compared with the position information of the second sensor to obtain the distance, and if the distance is equal to or greater than the threshold value, the correspondence between the sensing target and the second sensor does not match. The management device to judge that
A system for confirming the correspondence between the sensing target and the sensor. In the correspondence relationship confirmation system between the sensing target and the sensor according to claim 9.
The management device is a system for confirming the correspondence between the sensing target and the sensor, which issues an alarm when it is determined that the correspondence between the sensing target and the second sensor does not match. In the correspondence relationship confirmation system between the sensing target and the sensor according to claim 9.
As the position information of the first or second sensor, the position information of the reading terminal that reads the sensor data, the position information determined from the radio field strength at the time of data transmission, or the position information of the SIM held by the mobile line carrier shall be used. A system for confirming the correspondence between the sensing target and the sensor. In the correspondence relationship confirmation system between the sensing target and the sensor according to claim 9.
The management device searches for other sensors having a short distance from the first sensor or the second sensor as a starting point, and identifies the correspondence between the sensing target and the sensor. Correspondence confirmation system. In the correspondence relationship confirmation system between the sensing target and the sensor according to claim 9.
The first sensor is an individual identification sensor and is an individual identification sensor.
The second sensor is a state confirmation sensor, which is a sensing target and a sensor correspondence confirmation system. In the correspondence relationship confirmation system between the sensing target and the sensor according to claim 9.
The management device is a sensing target-sensor correspondence confirmation system characterized in that sensor data is discarded when a mismatch occurs between the sensing target and the sensor. In the correspondence relationship confirmation system between the sensing target and the sensor according to claim 9.
The management device is characterized in that when a mismatch occurs in the correspondence between the sensing target and the sensor, the sensor data registered as the sensing data of the wrong sensing target is re-registered as the sensing data of the correct sensing target. A system for confirming the correspondence between the sensing target and the sensor.

Images