MOBILE BODY DETECTION METHOD AND MOBILE BODY DETECTION SYSTEM

Abstract

To make it possible to suppress an unauthorized use of an ID read from an electronic tag held by a moving object.SOLUTION: A reader 2 and a reader / writer 3 installed at an observation point store an ID list in which an ID of an electronic tag held by a target moving object are registered; and when the reader and the reader / writer detect an electronic tag whose ID is registered in the ID list based on an ID read from a peripheral electronic tag, they report the detection of the registered electronic tag to a tag management server 4. Specifically, when the reader / writer detects the electronic tag whose ID is registered in the ID list, the reader / writer instructs the electronic tag to rewrite the ID into a new ID; and when the reader / writer confirms that the rewriting of the ID to the new ID has succeeded by reading the new ID from the electronic tag, the reader / writer reports to the tag management server that the registered electronic tag has been detected and that the electronic tag has been rewritten with the new ID.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a mobile object detection method and a mobile object detection system that detects a mobile object by using a reader to detect an electronic tag carried by the mobile object. [Background technology]

[0002] There is a demand for specifying a moving object such as a person, vehicle, luggage, or animal (pet) to confirm the location of the specified moving object or to investigate the behavior of the specified moving object.

[0003] In response to such demands, a technology is known in which an electronic tag using RFID (Radio Frequency Identification) or the like is attached to a mobile object, and the electronic tag is detected by a reader to detect the target mobile object and determine the position and behavior of the target mobile object (see Patent Document 1). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2006-099189 [Patent Document 2] Japanese Patent Publication No. 2020-035397 Summary of the Invention [Problem to be solved by the invention]

[0005] Now, with electronic tags, for example, if the UHF band used in RFID is used, a communication distance of several meters to about 10 meters can be achieved. Therefore, for example, by installing a reader on a structure (such as a utility pole) along a road, it is possible to grasp the situation of a moving object moving along the road. Also, by installing a reader at a gate (such as a school gate), it is possible to grasp the situation of a moving object passing through the gate.

[0006] However, with electronic tags, anyone with a reader can easily obtain the ID. This makes it possible for IDs read from electronic tags carried by mobile objects to be used fraudulently. For example, a stalker could obtain the ID of an electronic tag carried by a target and compare it with the detection results from readers installed in various locations to monitor the target's behavior. Furthermore, by obtaining the ID of an electronic tag carried by a target and writing that ID to another electronic tag, the stalker could duplicate the electronic tag and then carry that electronic tag himself, thereby impersonating the target.

[0007] Therefore, a main object of the present invention is to provide a mobile body detection method and a mobile body detection system that can prevent the unauthorized use of IDs read from electronic tags held by mobile bodies. [Means for solving the problem]

[0008] The mobile object detection method of the present invention is a mobile object detection method that detects a target mobile object by reading the ID of an electronic tag held by the mobile object and reports the detection status of the mobile object to an observer, in which a reading device installed at an observation point stores an ID list in which the IDs of the electronic tags held by the target mobile object are registered, and when it detects an electronic tag whose ID is registered in the ID list based on IDs read from surrounding electronic tags, it instructs the electronic tag to rewrite it to a new ID, and when it confirms that the rewriting to the new ID has been successful by reading the new ID from the electronic tag, it reports to a management device that it has detected the registered electronic tag and that it has rewritten the electronic tag to the new ID. If the old ID is read from the electronic tag and it is confirmed that the rewriting to the new ID has failed, the electronic tag is instructed to rewrite to the new ID again. The configuration will be as follows.

[0009] Furthermore, the mobile object detection system of the present invention is a mobile object detection system that detects a target mobile object by reading the ID of an electronic tag held by the mobile object and reports the detection status of the mobile object to an observer, in which a reading device installed at an observation point stores an ID list in which the IDs of the electronic tags held by the target mobile object are registered, and when it detects an electronic tag whose ID is registered in the ID list based on IDs read from surrounding electronic tags, it instructs the electronic tag to rewrite it with a new ID, and when it confirms that the rewriting to the new ID has been successful by reading the new ID from the electronic tag, it reports to a management device that it has detected the registered electronic tag and that it has rewritten the electronic tag with the new ID. If the old ID is read from the electronic tag and it is confirmed that the rewriting to the new ID has failed, the electronic tag is instructed to rewrite to the new ID again. The configuration will be as follows. [Effects of the Invention]

[0010] According to the present invention, the IDs of the electronic tags held by the mobile objects are frequently rewritten, thereby preventing the IDs read from the electronic tags held by the mobile objects from being used fraudulently. [Brief explanation of the drawings]

[0011] [Figure 1] Overall configuration diagram of a moving object detection system according to a first embodiment [Figure 2] FIG. 1 is a block diagram showing a schematic configuration of a reader, a reader / writer, and a tag management server according to a first embodiment; [Figure 3] FIG. 1 is a sequence diagram showing the procedure of operations of an electronic tag, a reader, a reader / writer, and a tag management server when the ID of an electronic tag according to the first embodiment is successfully rewritten. [Figure 4] FIG. 1 is a sequence diagram showing the procedure of operations of an electronic tag, a reader, a reader / writer, and a tag management server when it is unclear whether the ID of an electronic tag has been rewritten successfully according to the first embodiment. [Figure 5] FIG. 1 is an explanatory diagram showing an installation location of a reader / writer according to a first embodiment; [Figure 6] FIG. 10 is an explanatory diagram illustrating a processing unit of a virtual IoT system according to a second embodiment. [Figure 7]FIG. 10 is an explanatory diagram showing an ID rewrite state of an electronic tag according to a third embodiment; [Figure 8] FIG. 10 is a sequence diagram showing the procedure of operations of the electronic tag, reader / writer, and tag management server when ID rewriting according to the third embodiment is successful. [Figure 9] FIG. 10 is a sequence diagram showing the procedure of operations of an electronic tag, a reader / writer, and a tag management server when ID rewriting according to the third embodiment fails and rewriting is attempted again. [Figure 10] FIG. 10 is an explanatory diagram showing an ID rewrite state of an electronic tag according to a modification of the third embodiment; [Figure 11] FIG. 10 is a sequence diagram showing the procedure of the operation of the electronic tag and the reader / writer according to a modification of the third embodiment. [Figure 12] FIG. 10 is an explanatory diagram showing a detection state of spoofing of an electronic tag according to the fourth embodiment; [Figure 13] FIG. 13 is an explanatory diagram showing a detection state of loss of an electronic tag according to the fifth embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] The first invention made to solve the above problem is a mobile object detection method that detects a target mobile object by reading the ID of an electronic tag held by the mobile object and reports the detection status of the mobile object to an observer, in which a reading device installed at an observation point stores an ID list in which the IDs of the electronic tags held by the target mobile object are registered, and when it detects an electronic tag whose ID is registered in the ID list based on IDs read from surrounding electronic tags, it instructs the electronic tag to rewrite it to a new ID, and when it confirms that the rewriting to the new ID has been successful by reading the new ID from the electronic tag, it reports to a management device that it has detected the registered electronic tag and that it has rewritten the electronic tag to the new ID. If the old ID is read from the electronic tag and it is confirmed that the rewriting to the new ID has failed, the electronic tag is instructed to rewrite to the new ID again. The configuration will be as follows.

[0013] This allows the IDs of electronic tags held by mobile objects to be frequently rewritten, which can prevent the IDs read from electronic tags held by mobile objects from being used fraudulently. Furthermore, the ID of the electronic tag can be rewritten reliably.

[0016] Also, 2 In the invention, if the reading device is unable to read either the old ID or the new ID from the electronic tag and it is unclear whether the rewriting to the new ID was successful, it reports this to the management device, and when the management device receives a report from the reading device that it is unclear whether the rewriting to the new ID was successful, it instructs the reading device to detect the electronic tag with both the new ID and the old ID, and if the reading device is able to read either the new ID or the old ID, it reports this to the management device.

[0017] This allows the reader to detect the target electronic tag whether the rewriting to the new ID has been successful or whether the rewriting to the new ID has failed and the old ID remains. Also, the management device can take appropriate action when the rewriting of the ID of the electronic tag has failed.

[0018] In addition, if the reading device is unable to receive a report from the reading device that it has read either the new ID or the old ID, the management device may determine that an error may have occurred in the ID rewrite and may contact the user of the electronic tag, for example, to urge them to perform a reset procedure.

[0019] Also, 3 The invention is configured such that the mobile object holds a plurality of the electronic tags, and a plurality of the reading devices share the task of rewriting the IDs of the plurality of electronic tags to new IDs.

[0020] With this system, even if rewriting to a new ID fails, the ID that is read at almost the same time as the ID of the unrewritten electronic tag can be recognized as that of the electronic tag for which rewriting failed, so the electronic tag for which rewriting failed can be rewritten to a new ID again. This ensures that rewriting to a new ID can be performed.

[0021] Also, 4 The invention is configured such that the mobile object holds a plurality of the electronic tags, and one reader sequentially rewrites the IDs of the plurality of electronic tags to new IDs.

[0022] This ensures that the IDs can be rewritten to new ones without fail. Furthermore, it is possible to prevent some RFID tags from remaining in a state where they have not been rewritten to new IDs for a long period of time, thereby preventing unauthorized detection of moving objects.

[0023] Also, 5 The invention of before A processing unit provided on a network interposed between the reading device and the management device is configured to execute at least one of a data format conversion process, an ID matching process, and a data blocking process.

[0024] This allows a system to be constructed inexpensively by utilizing existing reading devices installed by others for different purposes, even if the existing reading devices have various configurations (specifications).

[0025] Also, 6 In the invention, the processing unit is configured as a virtual device that manages and processes data from the reading device as a physical device in a virtual IoT system.

[0026] This allows the processing units that perform data format conversion processing, ID matching processing, and data blocking processing to be appropriately provided using the virtual IoT system.

[0027] Also, 7 The invention of before The management device is configured to determine the possibility of the electronic tag being spoofed based on the attributes of the mobile object holding the detected electronic tag, the location where the electronic tag was detected, and the time when the electronic tag was detected.

[0028] This makes it possible to accurately detect spoofing of electronic tags.

[0029] Also, 8 In the invention, when electronic tags with the same ID are detected in sequence by the reading devices installed at multiple locations, the management device determines the possibility that any of the electronic tags detected by each of the reading devices is a counterfeit, based on the distance between the locations at which each was detected and the time interval between the times at which the electronic tags were detected in sequence.

[0030] This allows for more accurate detection of spoofed electronic tags.

[0031] Also, 9 The invention of before The management device is configured to determine that the electronic tag is lost when the detection status of the electronic tag is contrary to the behavior pattern of the mobile object that carries the electronic tag.

[0032] This allows accurate detection of the loss of an electronic tag.

[0033] Also, 10 The invention is a mobile object detection system that detects a target mobile object by reading the ID of an electronic tag held by the mobile object and reports the detection status of the mobile object to an observer. A reading device installed at an observation point stores an ID list in which the IDs of the electronic tags held by the target mobile object are registered, and when it detects an electronic tag whose ID is registered in the ID list based on the IDs read from the surrounding electronic tags, it instructs the electronic tag to rewrite it to a new ID, and when it confirms that the rewriting to the new ID has been successful by reading the new ID from the electronic tag, it reports to a management device that it has detected the registered electronic tag and that it has rewritten the electronic tag to the new ID. If the old ID is read from the electronic tag and it is confirmed that the rewriting to the new ID has failed, the electronic tag is instructed to rewrite to the new ID again. The configuration will be as follows.

[0034] According to this, as in the first invention, it is possible to prevent the ID read from the electronic tag held by the mobile body from being used fraudulently. Furthermore, the ID of the electronic tag can be rewritten reliably.

[0035] Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[0036] (First embodiment) FIG. 1 is a diagram showing the overall configuration of a moving body detection system according to the first embodiment.

[0037] The mobile object detection system detects a target mobile object by reading the ID of an electronic tag 1 held by the mobile object, and reports the detection status of the mobile object to an observer. The mobile object detection system comprises an electronic tag 1, a reader 2 (reading device), a reader / writer 3 (a rewritable reading device), a tag management server 4 (management device), a user terminal 6, and a mobile object management server 5. The reader 2, reader / writer 3, tag management server 4, mobile object management server 5, and user terminal 6 are connected via a network.

[0038] The electronic tag 1 is held by a moving object. The moving object may be, for example, a person, a vehicle, luggage, or an animal (pet). The electronic tag 1 stores a unique ID. The electronic tag 1 transmits and receives signals between the reader 2 and the reader / writer 3 by short-range wireless communication such as RFID. The ID can be any information that can identify the electronic tag 1, and the type and format of the information are not important.

[0039] The reader 2 transmits and receives signals to and from the electronic tag 1 via short-range wireless communication such as RFID. The reader 2 reads the ID of the electronic tag 1. The reader 2 stores an ID list. The ID list registers the ID of each electronic tag 1 held by the mobile object to be detected. Based on the ID read from the electronic tag 1, the reader 2 detects the electronic tag 1 whose ID is registered in the ID list, and reports the detection result of the electronic tag 1 to the tag management server 4.

[0040] Like the reader 2, the reader / writer 3 transmits and receives signals to and from the electronic tag 1 via short-range wireless communication such as RFID. The reader / writer 3 reads the ID of the electronic tag 1 and rewrites the ID of the electronic tag 1. Like the reader 2, the reader / writer 3 stores an ID list. Like the reader 2, the reader / writer 3 detects electronic tags 1 whose IDs are registered in the ID list based on the IDs read from the electronic tags 1, and reports the detection results of the electronic tags 1 to the tag management server 4. When the reader / writer 3 detects electronic tags 1 whose IDs are registered in the ID list, it rewrites the ID of the electronic tags 1.

[0041] The tag management server 4 manages the electronic tags 1. The tag management server 4 manages the ID list and distributes the ID list to the reader 2 and the reader / writer 3. The tag management server 4 collects the detection results of the electronic tags 1 by the reader 2 and the reader / writer 3, and reports the detection results of the electronic tags 1 to the mobile object management server 5 either directly or after appropriate processing.

[0042] The mobile object management server 5 manages mobile objects that hold the electronic tags 1. The mobile object management server 5 obtains the detection results of the electronic tags 1, i.e., the IDs of the electronic tags 1 detected by the reader 2 and reader / writer 3, from the tag management server 4, and generates information about the detection status of the mobile objects, i.e., information indicating which mobile objects were detected and where, based on the detection results of the electronic tags 1 and information linking the IDs of the electronic tags 1 with the mobile objects, and reports the information about the detection status of the mobile objects to an observer.

[0043] The user terminal 6 is operated by an observer. In the user terminal 6, the observer inputs conditions for moving object detection to be requested to the mobile object management server 5, specifically, identification information of the moving object to be detected, the period of time for detection, etc. The mobile object management server 5 performs processing for moving object detection based on the conditions input by the observer.

[0044] In this embodiment, the tag management server 4 and the mobile object management server 5 are provided, but a server having the functions of both the tag management server 4 and the mobile object management server 5 may be provided. Furthermore, the information obtained after the processing related to mobile object detection by the mobile object management server 5 may be notified to the user terminal 6 from the mobile object management server 5 in response to an observer inputting the detection target into the user terminal 6, or may be pushed from the mobile object management server 5 to the user terminal 6 at the timing when the detection target is detected or periodically.

[0045] Next, a description will be given of the schematic configuration of the reader 2, reader / writer 3, and tag management server 4 according to the first embodiment. FIG.

[0046] The reader 2 includes a wireless unit 21, a communication unit 22, a memory 23, and a processor 24.

[0047] The radio unit 21 emits radio waves from the antenna and receives, using the energy of the radio waves, an ID signal transmitted from the electronic tag 1. The ID signal includes the ID held by the electronic tag 1 itself.

[0048] The communication unit 22 communicates with the tag management server 4 via the network.

[0049] The memory 23 stores programs to be executed by the processor 24. The memory 23 also stores an ID list. In the ID list, the ID of each electronic tag 1 held by a moving object to be detected is registered.

[0050] The processor 24 performs various processes by executing programs stored in the memory 23. In this embodiment, the processor 24 performs an electronic tag detection process and the like.

[0051] In the electronic tag detection process, the processor 24 detects an electronic tag 1 whose ID is registered in the ID list. At this time, the ID of the electronic tag 1 is read and the ID of the electronic tag 1 is compared with the ID registered in the ID list, and if the ID comparison is successful, it is determined to be a registered electronic tag 1 and a report is made to the tag management server 4 that an electronic tag 1 with an ID registered in the ID list has been detected.

[0052] The reader / writer 3 includes a wireless unit 31, a communication unit 32, a memory 33, and a processor 34. The wireless unit 31 is similar to the wireless unit 21 of the reader 2, and the communication unit 32 is similar to the communication unit 22 of the reader 2.

[0053] The memory 33 stores programs to be executed by the processor 34. The memory 33 also stores an ID list. The ID list registers the ID of each electronic tag 1 held by a mobile object to be detected. The ID list also includes, in addition to the ID of the electronic tag 1, a password required to rewrite the ID.

[0054] The processor 34 performs various processes by executing programs stored in the memory 33. In this embodiment, the processor 34 performs an electronic tag detection process, a new ID issuance process, an ID rewrite process, etc. The electronic tag detection process is the same as that of the reader 2.

[0055] In the new ID issuance process, when the processor 34 detects an electronic tag 1 with an ID registered in the ID list through the electronic tag detection process, it issues a new ID to be written to the target electronic tag 1. At this time, the new ID may be issued randomly or may be generated based on a predetermined rule. The tag management server 4 may also issue a new ID and notify the reader / writer 3.

[0056] In the ID rewrite process, the processor 34 performs a process of rewriting the ID of the electronic tag 1 whose ID is registered in the ID list to the new ID issued in the new ID issuance process. At this time, the processor 34 instructs the target electronic tag 1 to write the new ID by specifying the current ID.

[0057] Furthermore, in the ID rewrite process, the processor 34 checks whether the ID rewrite was successful by reading the rewritten ID. That is, if the new ID is read, it is determined that the ID rewrite was successful. On the other hand, if the old ID is read, it is determined that the ID rewrite was unsuccessful. In this case, the processor 34 rewrites the ID again and checks again whether the ID rewrite was successful. Furthermore, if the rewritten ID cannot be read or if only an ID that is neither the old ID nor the new ID can be read, the processor 34 reports to the tag management server 4 that it is unclear whether the ID rewrite was successful.

[0058] In addition, a password is set in advance in the electronic tag 1 to prevent the ID from being rewritten illegally or the write mode from being changed illegally. As a result, if the password is not notified to the electronic tag 1 when the ID is rewritten, writing of a new ID will be rejected. In other words, only authorized reader / writers 3 are permitted to rewrite the ID, and unauthorized reader / writers 3 are prevented from rewriting the ID. Furthermore, the ID can only be rewritten by electronic tags 1 that are registered in the ID list and whose password is known. Furthermore, the ID cannot be rewritten by electronic tags 1 that are not registered in the ID list, i.e., electronic tags 1 that are not related to the requesting user.

[0059] The tag management server 4 includes a communication unit 41, a memory 42, and a processor 43.

[0060] The communication unit 41 communicates with the reader 2, the reader / writer 3, and the mobile unit management server 5 via the network.

[0061] The memory 42 stores programs to be executed by the processor 43, etc. The memory 42 also stores an ID list in which the ID of each electronic tag 1 held by the mobile object is registered. The memory 42 also stores information relating to the results of detecting the electronic tag 1 by the reader 2 and reader / writer 3, such as the ID of the reader 2 and reader / writer 3 that detected the electronic tag 1, the ID of the detected electronic tag 1, the detection location (the installation location of the reader 2 and reader / writer 3 that detected the electronic tag 1), and the detection time (the time when the reader 2 and reader / writer 3 detected the electronic tag 1).

[0062] The processor 43 performs various processes by executing programs stored in the memory 42. In this embodiment, the processor 43 performs ID list management processing, ID rewrite management processing, and the like.

[0063] In the ID list management process, the processor 43 manages the ID list and distributes it to the reader 2 and the reader / writer 3. The ID list contains the ID of each electronic tag 1 held by the mobile object to be detected. When the processor 43 receives a report from the reader / writer 3 that the ID has been successfully rewritten, it updates the ID list of its own device to change the old ID to the new ID.

[0064] In the ID rewrite management process, the processor 43 manages the rewriting of the ID of the electronic tag 1 performed by the reader / writer 3. Specifically, when the processor 43 receives a report from the reader / writer 3 that the ID rewrite was successful, or receives a report from the reader / writer 3 that the success or failure of the ID rewrite is unknown, the processor 43 issues the necessary notifications and instructions to the reader 2 and other reader / writers 3.

[0065] Next, a case where the ID of the electronic tag 1 according to the first embodiment has been successfully rewritten will be described. Fig. 3 is a sequence diagram showing the procedure of the operations of the electronic tag 1, the reader 2, the reader / writer 3, and the tag management server 4.

[0066] First, the tag management server 4 distributes the ID list (12234 to 12238) to the readers 2 and reader / writers 3 of #1 and #2.

[0067] Next, the #1 reader 2 reads the ID (12234) of the nearby electronic tag 1 and performs ID matching to determine whether the ID is registered in the ID list. If the ID matching is successful, the #1 reader 2 reports to the tag management server 4 that it has detected an electronic tag 1 whose ID (12234) is registered in the ID list.

[0068] Furthermore, when the #2 reader 2 reads the ID (12235) of the nearby electronic tag 1, it performs ID matching to determine whether the ID is registered in the ID list. If the ID matching is successful, the #2 reader 2 reports to the tag management server 4 that it has detected an electronic tag 1 whose ID (12235) is registered in the ID list.

[0069] Meanwhile, when the reader / writer 3 reads the ID (12237) of a nearby electronic tag 1, it performs ID verification to determine whether that ID is registered in the ID list. If the ID verification is successful, the reader / writer 3 issues a new ID (98776). Next, the reader / writer 3 specifies the detected ID (12237) and instructs the target electronic tag 1 to write the new ID (98776). Next, when the reader / writer 3 confirms that the ID rewrite was successful by being able to read the new ID (98776), it reports to the tag management server 4 that it has detected the electronic tag 1 with ID (12237) and that the rewrite to the new ID (98776) was successful.

[0070] When the tag management server 4 receives a report from the reader / writer 3 that the ID rewrite was successful, it notifies the readers 2 of #1 and #2 that the old ID (12237) in the ID list has been changed to the new ID (98776), and instructs them to detect the electronic tag 1 using the new ID (98776).

[0071] It should be noted that the example shown in FIG. 3 is a configuration including two readers 2, #1 and #2, and one reader / writer 3, but the configuration of the reader 2 and reader / writer 3 is not limited to this.

[0072] As described above, in this embodiment, when the reader / writer 3 detects an electronic tag 1 whose ID is registered in the ID list, it rewrites the ID of the target electronic tag 1. Specifically, it instructs the target electronic tag 1 to write a new ID. Next, when the reader / writer 3 confirms that the ID rewrite was successful by being able to read the new ID, it reports to the tag management server 4 that the ID rewrite was successful.

[0073] When the tag management server 4 receives a report from the reader / writer 3 that the ID rewrite was successful, it instructs the reader 2 and other reader / writers 3 to detect the electronic tag 1 with the new ID as an ID rewrite management process. Specifically, the tag management server 4 notifies that the ID of the electronic tag 1 has been rewritten from the old ID to the new ID, and instructs them to add the new ID to the ID list and delete the old ID.

[0074] Next, a case where it is unclear whether the ID rewriting of the electronic tag 1 according to the first embodiment has been successful or not will be described. Fig. 4 is a sequence diagram showing the procedure of the operations of the electronic tag 1, the reader 2, the reader / writer 3, and the tag management server 4.

[0075] 3 until the reader / writer 3 writes the new ID (98776) to the electronic tag 1. However, in this example, the reader / writer 3 is unable to read the new ID (98776) and is unable to confirm that the ID rewrite was successful, so it reports to the tag management server 4 that it has detected an electronic tag 1 with ID (12237) and that it is unclear whether the rewrite to the new ID (98776) was successful. When the reader / writer 3 reads the old ID (12237), it determines that the ID rewrite has failed and performs the ID rewrite again, repeating this process until it is no longer possible to read the old ID (12237).

[0076] When the tag management server 4 receives a report from the reader / writer 3 that the success or failure of the ID rewrite is unknown, it instructs the readers 2 of #1 and #2 and other reader / writers 3 to detect the electronic tag 1 with both the old ID (12237) and the new ID (98776). Specifically, since it is possible that the electronic tag 1 with the old ID (12237) has been rewritten to the new ID (98776) or that the rewrite has not been completed and it still has the old ID (12237), it instructs them to add the new ID (98776) to the ID list without deleting the old ID (12237) from the ID list.

[0077] After instructing the readers 2 of #1 and #2 and other reader / writers 3 to detect the electronic tag 1 using both the old ID (12237) and the new ID (98776), if the tag management server 4 does not receive a report from the readers 2, reader / writers 3 of #1 and #2, or other reader / writers 3 that they have read the new ID (98776) or the old ID (12237) after a predetermined time has elapsed, it determines that an error may have occurred in the ID rewrite. The tag management server 4 then contacts the user of the electronic tag 1 to urge them to perform a reset procedure because an error may have occurred in the ID rewrite. An appropriate communication method (such as telephone, SMS, or email) may be used for this notification. Note that if a mobile object carrying the electronic tag 1 moves back and forth, the electronic tag 1 may leave the detection area of ​​the reader / writer 3 and then return to the detection area, causing the reader / writer 3 to detect the electronic tag 1 again.

[0078] Meanwhile, when the tag management server 4 receives reports from the readers 2 and reader / writers 3 of #1 and #2 and other reader / writers 3 that the new ID (98776) has been read, it recognizes that the rewriting to the new ID has been successful and instructs them to detect the electronic tag 1 using the new ID.

[0079] In this embodiment, when the reader / writer 3 detects an electronic tag 1 whose ID is registered in the ID list and performs an ID rewrite on that electronic tag 1, if the reader / writer 3 is unable to read the new ID and is unable to confirm that the ID rewrite was successful, it reports to the tag management server 4 that it is unclear whether the ID rewrite was successful or not.

[0080] When the tag management server 4 receives a report from the reader / writer 3 that the success or failure of the ID rewrite is unknown, it instructs the reader 2 and other reader / writers 3 to detect the electronic tag 1 with both the old ID and the new ID as an ID rewrite management process. Specifically, it notifies the reader 2 and other reader / writers 3 of the new ID, notifies them that the rewrite is incomplete and the old ID may still remain, and instructs them to add the new ID to the ID list without deleting the old ID from the ID list.

[0081] Furthermore, after instructing the reader 2 and other reader / writers 3 to detect the electronic tag 1 with both the old ID and the new ID, if the tag management server 4 receives a report from the reader 2 or the reader / writer 3 or the other reader / writer 3 that the new ID has been read, it recognizes that the rewrite to the new ID has been successful and instructs them to detect the electronic tag 1 with the new ID. On the other hand, if it receives a report from the reader 2 or the reader / writer 3 or the other reader / writer 3 that the old ID has been read, it recognizes that the ID rewrite is incomplete. As part of the ID rewrite management process, the tag management server 4 instructs the reader 2 or the reader / writer 3 or the other reader / writer 3 to stop detecting the electronic tag 1 with the new ID. Specifically, it notifies them that the ID of the electronic tag 1 has not been rewritten from the old ID to the new ID and instructs them to delete the new ID from the ID list.

[0082] Furthermore, if the tag management server 4 instructs the reader 2 and other reader / writers 3 to detect the electronic tag 1 using both the old ID and the new ID, and then does not receive a report from the reader 2 or the reader / writer 3 or the other reader / writers 3 that the new ID or the old ID has been read after a specified time has elapsed, it determines, as an ID rewrite management process, that an error occurred while writing the new ID in the electronic tag 1, and that the ID has been changed to an invalid ID that is neither the old ID nor the new ID.

[0083] Furthermore, if the tag management server 4 is unable to receive a report from the reader 2 or reader / writer 3 that the new ID or old ID has been read, this is contrary to the normal behavioral pattern of the mobile object, i.e., if the mobile object were to move in a normal behavioral pattern, the electronic tag 1 carried by the mobile object would naturally be detected, then the tag management server 4 determines that an error has occurred in the ID rewriting. At this time, a time period is set during which it is assumed that the mobile object will naturally pass by the installation location of the reader 2 or reader / writer 3. For example, if the mobile object is a student, a time period is set during which it is assumed that the student will naturally pass by the school gate. Then, if the tag management server 4 is unable to receive a report from the reader 2 or reader / writer 3 that the new ID or old ID has been read during the set time period, it is determined that an error has occurred in the ID rewriting.

[0084] In addition, when an ID rewrite error is detected, the tag management server 4 notifies the user of the electronic tag 1 that there is a possibility of an ID rewrite error, and also provides guidance to encourage the user to take the electronic tag 1 to a location responsible for maintenance of the electronic tag 1 and request a procedure to reset the ID of the electronic tag 1, for example.

[0085] Next, an explanation will be given of the installation location of the reader / writer 3 according to the first embodiment. Fig. 5 is an explanatory diagram showing the installation location of the reader / writer 3.

[0086] When the reader / writer 3 detects an electronic tag 1 whose ID is registered in the ID list by reading the ID of the electronic tag 1 and performing ID verification, it instructs the electronic tag 1 to rewrite the ID to a new ID, and then reads the new ID to confirm that the ID rewrite was successful. At this time, if the electronic tag 1 does not stay within the communication area of ​​the reader / writer 3 for a short time, the rewrite process or the process of reading the new ID may fail after the instruction to rewrite to a new ID is given, and it becomes unclear whether the ID rewrite was successful or not.

[0087] Therefore, it is preferable to install the reader / writer 3 at a location where there is a high possibility of ensuring communication time with the electronic tag 1. Specifically, it is preferable to install the reader / writer 3 at a location where a moving object carrying the electronic tag 1 is likely to stop, where the moving object is likely to stay for a long time, or where the moving object's passing speed is slow. This ensures communication time between the reader / writer 3 and the electronic tag 1, thereby reducing the possibility of failure in rewriting the ID.

[0088] In the example shown in Fig. 5(A), the reader / writer 3 is installed at an intersection without traffic lights. At intersections without traffic lights, pedestrians as moving objects stop to check for safety before crossing. Also, vehicles as moving objects slow down when entering the intersection. This ensures a long communication time between the reader / writer 3 and the electronic tag 1.

[0089] In the example shown in Fig. 5(B), the reader / writer 3 is installed at a point where a stop (temporary stop) sign is installed. In this case, the vehicle as a moving body stops reliably, so that a long period of time during which communication is possible between the reader / writer 3 and the electronic tag 1 can be secured. Note that the reader / writer 3 may also be installed at other points where a stop is mandatory, such as at a railroad crossing.

[0090] In the example shown in Fig. 5(C), the reader / writer 3 is installed near a narrow gate. If the moving object is a child, the reader / writer 3 is installed near the school gate. The reader / writer 3 may also be installed near a narrow passageway. At such a location, the speed at which pedestrians pass through as moving objects is slow, so the communication time between the reader / writer 3 and the electronic tag 1 can be extended.

[0091] 5(D), the communication area (area where radio waves can reach) of the reader / writer 3 is enlarged to ensure a long communication time between the reader / writer 3 and the electronic tag 1. Specifically, multiple antennas connected to the reader / writer 3 are arranged side by side along the direction of travel of the moving object. Note that an antenna that is long in one direction may also be used.

[0092] In the example shown in FIG. 5(E), multiple reader / writers 3 work together to instruct the electronic tag 1 to rewrite the ID to a new one and to confirm the success of the ID rewrite by reading the new ID. Specifically, one reader / writer 3 instructs the electronic tag 1 to rewrite the ID to a new one, and the other reader / writer 3 confirms the success of the ID rewrite by reading the new ID. In this case, the multiple reader / writers 3 may work together via the tag management server 4. Alternatively, the multiple reader / writers 3 may work together by directly communicating with each other via a wired or wireless connection. Furthermore, the multiple reader / writers 3 may be installed along the direction of travel of the moving object, and the multiple reader / writers 3 may be spaced apart from each other. The reader / writer 3 and the reader 2 may work together.

[0093] (Second embodiment) Next, a second embodiment will be described. Note that the points not specifically mentioned here are the same as those in the previous embodiment. Fig. 6 is an explanatory diagram showing a processing unit 7 of a virtual IoT system according to the second embodiment.

[0094] When a user (observer) requests the mobile object management server 5 to detect a new moving object, it increases costs for the user to install a new reader 2 and reader / writer 3 required for that moving object detection. Therefore, it is conceivable to use an existing reader 2 and reader / writer 3 installed by another person for a different purpose. However, since the existing readers 2 and reader / writers 3 installed by other people have a variety of configurations (specifications), it may be difficult to connect the existing reader 2 to the tag management server 4 as is.

[0095] Therefore, in this embodiment, the processing unit 7 of the virtual IoT system performs necessary processing on the report data output to the network from the reader 2. The processing unit 7 is a virtual device (single visor) that manages and processes data of the reader 2 as a physical device in the virtual IoT system.

[0096] In the example shown in Fig. 6(A), an ID list is distributed to the reader 2, and the reader 2 checks the ID read from the electronic tag 1 against the ID list to detect the electronic tag 1 registered in the ID list. In this case, the reader 2 is authenticated to prevent the ID list distributed to the reader 2 from being used fraudulently.

[0097] In the example shown in FIG. 6(B), similar to the example shown in FIG. 6(A), an ID list is distributed to the reader 2, and the reader 2 compares the ID of the electronic tag 1 read by the reader 2 with the ID list to detect the electronic tag 1 registered in the ID list. For this reason, authentication is performed on the reader 2. Also, in this example, the processing unit 7 of the virtual IoT system processes the data collected from the reader 2. Specifically, if the output data of an existing reader 2 installed by another person differs from the data format of the tag management server 4, a process (data format conversion process) is performed to convert the output data of the reader 2 into a data format of the electronic tag detection report that can be interpreted by the tag management server 4. This allows the tag management server 4 to process the report data (electronic tag detection report) from the reader 2 in the same way, even for readers 2 with various configurations (specifications).

[0098] In the example shown in Fig. 6(C), the processing unit 7 of the virtual IoT system checks the ID of the electronic tag 1 read by the reader 2 against the ID list (ID checking process) and detects the electronic tag 1 registered in the ID list. In this case, the reader 2 simply outputs the ID read from the electronic tag 1 to the network as is. Therefore, the ID list is not provided to the reader 2, and therefore authentication of the reader 2 is not required.

[0099] The example shown in Figure 6(D) is a case where the existing readers 2 in use include a reader 2 that has a negative impact on the network. For example, an existing reader 2 installed by another person may output data (fake data) that deceives users onto the network, or may output a huge amount of data onto the network intentionally or due to a malfunction. Therefore, if a reader 2 has a negative impact on the network, the processing unit 7 of the virtual IoT system blocks the output data of that reader 2 (data blocking process).

[0100] In this way, in this embodiment, it is possible to appropriately use existing readers 2 installed by others. This reduces the cost of using the mobile object detection service. Also, mobile object detection can be performed over a wide area.

[0101] 6, a reader 2 is shown, but a reader / writer 3 may be used. However, since the reader / writer 3 not only reads but also rewrites data, only Fig. 6(A) or Fig. 6(B) is possible.

[0102] (Third embodiment) Next, a third embodiment will be described. Note that points not particularly mentioned here are the same as those of the previous embodiments. Fig. 7 is an explanatory diagram showing the ID rewrite status of an electronic tag 1 according to the third embodiment. Fig. 8 is a sequence diagram showing the procedure of operation of the electronic tag 1, reader / writer 3, and tag management server 4 when ID rewrite is successful. Fig. 9 is a sequence diagram showing the procedure of operation of the electronic tag 1, reader / writer 3, and tag management server 4 when ID rewrite fails and rewrite is performed again.

[0103] When the reader / writer 3 detects an electronic tag 1 whose ID is registered in the ID list and attempts to rewrite the ID of that electronic tag 1, the ID rewrite may fail. For example, if the electronic tag 1 moves out of the reader / writer 3's radio wave coverage area while the reader / writer 3 is instructing the electronic tag 1 to write a new ID, the ID rewrite will fail. In this case, the contents stored in the electronic tag 1 may become corrupted, and the ID may change to an invalid ID that is neither the old ID nor the new ID. In this case, the reader / writer 3 will not be able to recognize the electronic tag 1 whose ID it previously attempted to rewrite, and will not be able to retry the ID rewrite.

[0104] Therefore, in this embodiment, a mobile object holds a plurality of electronic tags 1, and a reader / writer 3 issues an ID rewrite instruction and verifies the success of the ID rewrite to each of the electronic tags 1 held by the mobile object. Also, here, the ID rewrite of the electronic tags 1 held by the mobile object is shared among the plurality of reader / writers 3.

[0105] The examples shown in Figures 7(A) and 8 are for cases where the ID rewrite was successful. In this case, first, the #1 reader / writer 3 installed at the rewrite location (point A) reads the ID (12345) of the #1 electronic tag 1, and at almost the same time, reads the ID (12346) of the #2 electronic tag 1. The reader / writer 3 compares the read ID (12345) and ID (12346) with the ID list, and if the ID comparison is successful, the reader / writer 3 recognizes that the target moving object holds the electronic tag 1 with ID (12345) and the electronic tag 1 with ID (12346).

[0106] Next, the #1 reader / writer 3 proceeds to the process of rewriting the ID (12345) of the #1 electronic tag 1 to the new ID (33398). That is, it specifies the ID (12345) and instructs the #1 electronic tag 1 to write the new ID (33398). The reader / writer 3 then reads the ID (33398) of the #1 electronic tag 1, and almost simultaneously reads the ID (12346) of the #2 electronic tag 1. This allows the reader / writer 3 to confirm that the ID rewrite for the #1 electronic tag 1 was successful, and reports to the tag management server 4 that the rewrite from the old ID (12345) to the new ID (33398) was successful.

[0107] When two electronic tags 1 are detected with the combination of ID (33398) and ID (12345), the tag management server 4 instructs the reader / writer 3 other than the reader / writer 3 #1 (including the reader / writer 3 #2) to rewrite the electronic tag 1 with ID (12345), one of which has not yet been rewritten.

[0108] Next, the #2 reader / writer 3 installed at the next rewriting location (point B) reads the ID (33398) of the #1 electronic tag 1, and at almost the same time, reads the ID (12346) of the #2 electronic tag 1. At this time, the #2 reader / writer 3 recognizes, based on instructions from the tag management server 4, that the #2 electronic tag 1 with ID (12346) needs to be rewritten.

[0109] As a result, the reader / writer 3 of #2 proceeds to the process of rewriting the ID (12346) of the electronic tag 1 of #2 to the new ID (67679). In other words, it specifies the ID (12346) and instructs the electronic tag 1 of #2 to write the new ID (67679). Next, the reader / writer 3 reads the ID (33398) of the electronic tag 1 of #1, and almost simultaneously reads the ID (67679) of the electronic tag 1 of #2. As a result, the reader / writer 3 confirms that the ID rewrite for the electronic tag 1 of #2 was successful, and reports to the server that the rewrite from the old ID (12346) to the new ID (67679) was successful.

[0110] The examples shown in Figures 7(B) and 9 are for cases where the ID rewrite has failed. In this case, the process is the same as the example shown in Figure 8 until the #1 reader / writer 3 writes the new ID (33398) to the #1 electronic tag 1. However, in this example, the ID rewrite fails in the #1 electronic tag 1, and it changes to an invalid ID (77777) that is neither the old ID (12345) nor the new ID (33398).

[0111] Next, the reader / writer 3 of #1 is able to read the ID (12346) of the electronic tag 1 of #2, but is unable to read either the old ID (12345) or the new ID (33398) of the electronic tag 1 of #1. However, since the reader / writer 3 of #1 was able to read the unknown ID (77777) at almost the same time as the ID (12346), it is presumed that this ID (77777) is from an electronic tag 1 held by the same mobile object as the electronic tag 1 with ID (12346), i.e., an electronic tag 1 whose ID rewrite failed.

[0112] Therefore, the reader / writer 3 of #1 specifies the ID (77777) and instructs it to write a new ID (33398) to the electronic tag 1 of #1. Next, the reader / writer 3 of #1 reads the ID (33398) of the electronic tag 1 of #1, and at almost the same time, reads the ID (12346) of the electronic tag 1 of #2. This allows the reader / writer 3 of #1 to confirm that the ID rewrite for the electronic tag 1 of #1 has been successful, and reports to the tag management server 4 that the rewrite from the old ID (12345) to the new ID (33398) has been successful.

[0113] The subsequent steps are the same as in the example shown in FIG. 8, and the #2 reader / writer 3 performs processing to rewrite the ID (12346) of the #2 electronic tag 1 to the new ID (67679).

[0114] In this embodiment, when a mobile object holds two electronic tags 1, the reader / writer 3 located at the first rewrite location rewrites the ID of the first electronic tag 1, and when it confirms that the ID rewrite for that first electronic tag 1 has been successful, it rewrites the ID of the second electronic tag 1 located at the next rewrite location and confirms that the ID rewrite for that second electronic tag 1 has been successful.

[0115] Here, there may be cases where the ID rewrite for one of the electronic tags 1 fails and is changed to an illegal ID that is neither the old ID nor the new ID, but if the ID of the other electronic tag 1 can be read successfully and there is an ID that is read at almost the same time as the successfully read ID, that ID is presumed to be the ID of the electronic tag 1 whose ID rewrite failed. For this reason, by specifying that ID and issuing an instruction to write a new ID, it is possible to rewrite the ID of the electronic tag 1 whose ID rewrite failed.

[0116] In the example shown in Figure 9, the reader / writer 3 #1 re-attempted the ID rewrite on the electronic tag 1 #1 whose ID rewrite had failed, but the reader / writer 3 #2 may re-attempt the ID rewrite on the electronic tag 1 #1, and another reader / writer 3 may perform the ID rewrite on the electronic tag 1 #2.

[0117] In the examples shown in FIGS. 8 and 9, the mobile object holds two electronic tags 1, but the mobile object may hold three or more electronic tags 1.

[0118] (Modification of the third embodiment) Next, a modified example of the third embodiment will be described. Note that points not particularly mentioned here are the same as those of the above embodiment. Fig. 10 is an explanatory diagram showing the ID rewriting status of the electronic tag 1 according to the modified example of the third embodiment. Fig. 11 is a sequence diagram showing the procedure of the operation of the electronic tag 1 and the reader / writer 3 according to the modified example of the third embodiment.

[0119] As in the third embodiment, by having a mobile object hold multiple electronic tags 1, even if an ID rewrite fails, the ID can be rewritten again. On the other hand, even if the ID rewrite is successful for the electronic tags 1 held by the mobile object, if the ID rewrite is incomplete for some of the remaining electronic tags 1, the mobile object can be identified using the IDs of the incomplete electronic tags 1, and it can be determined that the IDs of the electronic tags 1 held by the mobile object are a combination of the incomplete ID and the successfully rewritten new ID. This makes rewriting the IDs of the electronic tags 1 meaningless, making it possible to detect fraudulent mobile objects.

[0120] On the other hand, in the third embodiment, the ID rewriting of the multiple electronic tags 1 held by the mobile object is shared and carried out by multiple reader / writers 3. For this reason, it is conceivable that the state in which the ID rewriting is incomplete may continue for a long time for some of the electronic tags 1. However, it is necessary to avoid a state in which the ID rewriting is incomplete for some of the electronic tags 1 continuing for a long time, and it is desirable to complete the ID rewriting for all of the electronic tags 1 held by the mobile object in as short a time as possible.

[0121] Therefore, in this modification, the same reader / writer 3 sequentially rewrites the IDs of a plurality of electronic tags 1 held by a moving object.

[0122] In the example shown in FIG. 11, the reader / writer 3 first reads the ID (12345) of the electronic tag 1 #1, and almost simultaneously reads the ID (12346) of the electronic tag 1 #2.

[0123] Next, the reader / writer 3 proceeds to the process of rewriting the ID (12345) of the #1 electronic tag 1 to the new ID (33398). That is, the reader / writer 3 specifies the ID (12345) and instructs the #1 electronic tag 1 to write the new ID (33398).

[0124] Next, when the reader / writer 3 confirms that the ID rewrite for the #1 electronic tag 1 has been successful, it proceeds to the process of rewriting the ID (12346) of the #2 electronic tag 1 to the new ID (67679). That is, it specifies the ID (12346) and instructs the #2 electronic tag 1 to write the new ID (67679).

[0125] In this modified example, when a mobile object holds two electronic tags 1, if the reader / writer 3 fails to rewrite the ID of one of the electronic tags 1, the same reader / writer 3 will rewrite the ID again, and if the ID rewrite is successful, the same reader / writer 3 will then rewrite the ID of the other electronic tag 1.

[0126] Here, when the ID for electronic tag 1 #1 is rewritten, the two electronic tags 1 held by the moving object change from a combination of ID(12345) and ID(12346) to a combination of ID(33398) and ID(12346), but there is a risk that the moving object may be identified using the ID(12346) that has not yet been rewritten, and further, since ID(33398) and ID(12346) are read almost simultaneously, the combination of ID(33398) and ID(12346) is also known, so there is a risk that the moving object may be identified using the ID(33398) that has already been rewritten. However, in this modified example, the IDs of two electronic tags 1 are rewritten in a short period of time by the same reader / writer 3, making it difficult to identify the moving object.

[0127] (Fourth embodiment) Next, a fourth embodiment will be described. Note that points not particularly mentioned here are the same as those in the above-described embodiments. Fig. 12 is an explanatory diagram showing a state in which spoofing of an electronic tag 1 according to the fourth embodiment is detected.

[0128] When the reader 2 and reader / writer 3 read an ID registered in the ID list, they report to the tag management server 4 that they have detected the electronic tag 1 with that ID, and the mobile object management server 5 then detects the mobile object based on the detection result of the electronic tag 1. At this point, if someone steals the ID of the electronic tag 1 held by the mobile object, copies the electronic tag 1 by writing that ID to another electronic tag 1, and has that electronic tag 1 held by another mobile object, they can spoof the electronic tag 1.

[0129] On the other hand, once the ID of an electronic tag 1 is rewritten, it will no longer be possible to spoof it using an electronic tag 1 with the old ID written to it. However, if there is no opportunity to rewrite the ID, i.e., if a moving object does not pass through a location where a reader / writer 3 that rewrites the ID is installed, the ID will not be rewritten, and spoofing of the electronic tag 1 will still be permitted. For example, if a person is located outside their usual range of activities due to a business trip or vacation, or if they do not move from a specific location due to hospitalization or a restricted outing caused by an infectious disease outbreak, it will be impossible to rewrite the ID for an extended period of time. In this case, the risk of someone stealing their ID may be reduced, but conversely, the risk of prolonged spoofing may increase.

[0130] Therefore, in this embodiment, the tag management server 4 determines the possibility of spoofing the electronic tag 1, and if there is a possibility that the electronic tag 1 has been spoofed, notifies the user of the electronic tag 1. At this time, an appropriate communication means (telephone, SMS, email, etc.) may be used. Furthermore, if it is certain that the electronic tag 1 has been spoofed, the tag management server 4 may notify the user of the electronic tag 1 to urge them to perform the ID rewrite procedure.

[0131] Here, in this embodiment, the tag management server 4 determines the possibility of the electronic tag 1 being impersonated based on the attributes of the mobile object holding the detected electronic tag 1, the detection location of the electronic tag 1, i.e., the location where the reader 2 that detected the electronic tag 1 is installed, and the detection time of the electronic tag 1, i.e., the time when the reader 2 detected the electronic tag 1.

[0132] In particular, in this embodiment, when electronic tags 1 with the same ID are detected in sequence by readers 2 installed at multiple locations, the tag management server 4 determines the possibility that any of the electronic tags 1 detected by each reader 2 is a counterfeit, based on the distance between the locations at which each was detected and the time interval between the times at which the electronic tags 1 were detected in sequence.

[0133] Specifically, when electronic tags 1 with the same ID are detected in sequence by readers 2 installed at two locations, the tag management server 4 determines the possibility that the electronic tags 1 detected by the readers 2 at the two locations are held on the same moving object, depending on the possibility of movement between the two locations, based on the distance between the two locations and the time interval between when the electronic tags 1 were detected by the readers 2 at the two locations. If the electronic tags 1 detected by the readers 2 at the two locations are unlikely to be held on the same moving object, the tag management server 4 determines that one of the electronic tags 1 detected by the readers 2 at the two locations is likely to be a spoofed tag.

[0134] In the example shown in FIG. 12, first, a reader 2 installed at point A in Tokyo reads the ID (12345) to detect an electronic tag 1 having the ID (12345) registered in its ID list, and reports the detection result to the tag management server 4. Next, a reader 2 installed at point B in Tokyo reads the ID (12345) to detect an electronic tag 1 having the ID (12345) registered in its ID list, and reports the detection result to the tag management server 4. Next, a reader 2 installed at point C in Okinawa reads the ID (12345) to detect an electronic tag 1 having the ID (12345) registered in its ID list, and reports the detection result to the tag management server 4.

[0135] In this case, the interval between the detection times of the electronic tag 1 at points A and B in Tokyo is sufficiently longer than the time it takes to move from point A to point B in Tokyo. Therefore, the tag management server 4 presumes that the electronic tag 1 detected by the reader 2 at point A in Tokyo and the electronic tag 1 detected by the reader 2 at point B are held on the same moving object, and determines that they are genuine electronic tags 1.

[0136] On the other hand, the interval between the detection times of the electronic tag 1 at point A in Tokyo and point C in Okinawa is shorter than the time it takes to travel from point A in Tokyo to point C in Okinawa. Therefore, the tag management server 4 presumes that the electronic tag 1 detected by reader 2 at point A in Tokyo and the electronic tag 1 detected by reader 2 at point C in Okinawa are not held on the same moving object, and if the electronic tag 1 detected by reader 2 at point A in Tokyo is genuine, it determines that the electronic tag 1 detected by reader 2 at point C in Okinawa is a spoof.

[0137] Furthermore, in this embodiment, when an electronic tag 1 is detected by a reader 2 installed at a certain location, the tag management server 4 determines the possibility that a mobile object holding the genuine electronic tag 1 will pass through the detection location at the time the electronic tag 1 is detected, based on the attributes of the mobile object holding the electronic tag 1, the detection location of the electronic tag 1 (i.e., the location where the reader 2 that detected the electronic tag 1 is installed), and the detection time of the electronic tag 1 (i.e., the time when the reader 2 detected the electronic tag 1). Then, if there is a low possibility that a mobile object holding the genuine electronic tag 1 will pass through the detection location at the time the electronic tag 1 is detected, the tag management server 4 determines that there is a possibility that the electronic tag 1 is a spoofed tag.

[0138] For example, if an electronic tag 1 carried by a person as a mobile entity is detected by a reader 2 located at a point away from the person's home during a time when the person is likely to be at home, it is determined that there is a possibility that the electronic tag 1 has been spoofed. Also, if an electronic tag 1 carried by a child as a mobile entity is detected by a reader 2 installed at the school gate, confirming that the person has arrived at school, and then, before the child leaves school, the electronic tag 1 carried by the child is detected by a reader 2 located at a point away from the school, it is determined that there is a possibility that the electronic tag 1 has been spoofed.

[0139] In the example shown in FIG. 12, the reader 2 reads the ID of the electronic tag 1, but the reader / writer 3 may read the ID of the electronic tag 1.

[0140] 12, the possibility that one of the electronic tags 1 detected by the two readers 2 is a spoofed tag is determined based on the detection results of the readers 2 installed at two locations, but this is not limiting. That is, the possibility that any of the electronic tags 1 detected by the readers 2 is a spoofed tag may be determined based on the detection results of the readers 2 installed at multiple locations (including three or more).

[0141] (Fifth embodiment) Next, a fifth embodiment will be described. Note that points not particularly mentioned here are the same as those in the previous embodiments. Fig. 13 is an explanatory diagram showing a situation in which loss of an electronic tag 1 according to the fifth embodiment is detected.

[0142] If an electronic tag 1 held in a mobile object is lost, various problems can arise. For example, if a person picks up another person's electronic tag 1, they can masquerade as that person by holding that electronic tag 1. Furthermore, if a mobile object holds multiple electronic tags 1 (see the third embodiment), if one of the electronic tags 1 held in the mobile object is lost, this will no longer be a countermeasure for when the ID rewrite fails, and the ID rewrite will remain unsuccessful. Furthermore, if a person picks up another person's electronic tag 1, they can read the ID of that electronic tag 1 and write that ID to another electronic tag 1, thereby duplicating the other person's electronic tag 1 and masquerading as that person. In this case, if the user of the electronic tag 1 can later retrieve the lost electronic tag 1, there is a possibility that they will not notice that the spoofing using the duplicated electronic tag 1 has occurred.

[0143] Therefore, in this embodiment, the tag management server 4 determines that the electronic tag 1 is lost when the detection status of the electronic tag 1 by the reader 2 and reader / writer 3 contradicts the behavior pattern of the mobile object that holds the electronic tag 1. Specifically, when the reader 2 and reader / writer 3 installed at a location where the mobile object is likely to be present based on the behavior pattern of the mobile object do not detect the electronic tag 1 during a time period when the mobile object is likely to be present, that is, when the reader 2 and reader / writer 3 do not detect the electronic tag 1 that was detected regularly at a predetermined location and during a predetermined time period. When the loss of the electronic tag 1 is detected, an alarm is issued to notify the user of the electronic tag 1 that the electronic tag 1 has been lost. This allows the user of the electronic tag 1 to notice the loss of the electronic tag 1 at an early stage.

[0144] 13(A), for example, if the moving object is a person, attention is focused on a reader 2 installed at or near the person's home, and the tag management server 4 monitors the ID read by the focused reader 2 during the time periods when the person is at home, out, or upon returning home. If the targeted ID is not read by the focused reader 2 during the time periods when the person is at home, out, or upon returning home, that is, during the time periods when the targeted ID should be read, the tag management server 4 presumes that the electronic tag 1 carried by the person has been lost.

[0145] For example, it is determined whether the ID reading at midnight, when the person is always at home, is the last reading of the day. In other words, if the ID can be read by a reader 2 installed at another location during the day, but cannot be read by a reader 2 installed at the person's home or a nearby location at midnight, it is presumed that the RFID tag 1 carried by the person has been lost. Note that, for example, if the owner of the RFID tag 1 does not return home on a business trip or vacation, and an alarm is sent to the owner indicating a possible loss, there is no problem because the owner knows the reason and it is clear that the RFID tag 1 has not been lost.

[0146] Also, as shown in Figure 13(B), when a mobile body holds multiple electronic tags 1 (see the third embodiment), if it is not possible to read all of the IDs of the multiple electronic tags held by one mobile body, that is, if the number of electronic tags 1 whose IDs have been read almost simultaneously is less than the number of electronic tags 1 held by the mobile body corresponding to that electronic tag 1, the electronic tag is determined to be lost and an alarm is issued.

[0147] In the example shown in FIG. 13, the reader 2 reads the ID of the electronic tag 1, but the reader / writer 3 may read the ID of the electronic tag 1.

[0148] As described above, the embodiments have been described as examples of the technology disclosed in this application. However, the technology in this disclosure is not limited to these, and can be applied to embodiments in which modifications, substitutions, additions, omissions, etc. are made. Furthermore, it is also possible to combine the components described in the above embodiments to create new embodiments. [Industrial Applicability]

[0149] The mobile body detection method and mobile body detection system of the present invention have the effect of preventing the unauthorized use of IDs read from electronic tags held by mobile bodies, and are useful as mobile body detection methods and mobile body detection systems that detect mobile bodies by detecting electronic tags held by the mobile bodies with a reading device. [Explanation of symbols]

[0150] 1. Electronic tags 2. Reader (reading device) 3. Reader / writer (reading device that can also be rewritten) 4. Tag management server (management device) 5. Mobile Management Server 6 User terminals 7 Processing section

Claims

1. A mobile object detection method for detecting a target mobile object by reading an ID of an electronic tag held by the mobile object and reporting the detection status of the mobile object to an observer, comprising: The reading device installed at the observation point storing an ID list in which the IDs of the electronic tags held by the target mobile object are registered; When the electronic tag whose ID is registered in the ID list is detected based on the IDs read from the surrounding electronic tags, The electronic tag is instructed to be rewritten with a new ID, By reading the new ID from the electronic tag, it is confirmed that the rewriting to the new ID has been successful. Report to the management device that the registered electronic tag has been detected and that the electronic tag has been rewritten with a new ID; By reading the old ID from the electronic tag, it is confirmed that the rewriting to the new ID has failed. A mobile object detection method characterized in that the electronic tag is instructed again to rewrite the ID to a new one.

2. The reading device is If neither the old ID nor the new ID can be read from the electronic tag and it is unclear whether the rewriting to the new ID has been successful, the management device is notified of this fact. The management device When a report is received from the reader that the success or failure of the rewriting to the new ID is unknown, instructing the reader to detect the electronic tag with both the new ID and the old ID; The reading device is 2. The mobile unit detection method according to claim 1, wherein if either the new ID or the old ID can be read, the fact is reported to said management device.

3. The mobile object holds a plurality of the electronic tags, A plurality of said reading devices 2. The mobile body detection method according to claim 1, wherein the rewriting of the IDs to the plurality of electronic tags is shared and carried out.

4. The mobile object holds a plurality of the electronic tags, One of the reading devices is 2. The mobile body detection method according to claim 1, wherein the IDs of the plurality of electronic tags are rewritten to new IDs in sequence.

5. A mobile object detection method as described in claim 1, characterized in that a processing unit provided on a network interposed between the reading device and the management device performs at least one of data format conversion processing, ID matching processing, and data blocking processing.

6. The processing unit The mobile object detection method according to claim 5, characterized in that in a virtual IoT system, the mobile object detection method is a virtual device that manages and processes data from the reading device as a physical device.

7. The management device The mobile object detection method described in claim 1, characterized in that the possibility of the electronic tag being spoofed is determined based on the attributes of the mobile object holding the detected electronic tag, the location where the electronic tag was detected, and the time when the electronic tag was detected.

8. The management device The mobile object detection method described in claim 7, characterized in that when electronic tags with the same ID are detected in sequence by reading devices installed at multiple locations, the possibility that any of the electronic tags detected by each reading device is a counterfeit is determined based on the distance between the locations at which each was detected and the time interval between the times at which the electronic tags were detected in sequence.

9. The management device:

2. The mobile object detection method according to claim 1, wherein the electronic tag is determined to be lost if the detection status of the electronic tag is contrary to the behavior pattern of the mobile object carrying the electronic tag.

10. A mobile object detection system that detects a target mobile object by reading the ID of an electronic tag held by the mobile object and reports the detection status of the mobile object to an observer, The reading device installed at the observation point storing an ID list in which the IDs of the electronic tags held by the target mobile object are registered; When the electronic tag whose ID is registered in the ID list is detected based on the IDs read from the surrounding electronic tags, The electronic tag is instructed to be rewritten with a new ID, By reading the new ID from the electronic tag, it is confirmed that the rewriting to the new ID has been successful. Report to the management device that the registered electronic tag has been detected and that the electronic tag has been rewritten with a new ID; By reading the old ID from the electronic tag, it is confirmed that the rewriting to the new ID has failed. A mobile object detection system characterized in that the electronic tag is instructed again to rewrite the ID to a new one.

Images