JP5416619B2 - RFID platform system, logger device, and management method - Google Patents

Description

  The present invention relates to an RFID platform system for managing the location of an RFID (Radio Freqency IDentification) tag.

  In recent years, development of RFID systems for individually identifying information on articles has been activated. Originally, the RFID system has been developed as a new merchandise identification and management technology that replaces the bar code. However, the RFID system is not limited to this and is now being applied to various technical fields. Management targets are not limited to articles, but are also targeted at people. For example, in public transportation, the use of an admission management card with a built-in RF tag is rapidly progressing instead of a conventional ticket gate or commuter pass. As one of the techniques for managing people using an RF tag, there is an attendance management system for grasping on a computer where a person carrying the RF tag is.

  A conventional RFID system is composed of a single platform and a plurality of tag readers. Tag data transmitted from the RF tag is collected on the platform via any of the tag readers. Tag data collected on the platform is made into a database and provided to various applications such as an attendance management system. Patent Documents 1 to 4 describe an RFID system that manages tag data acquired by a tag reader and provides it to various applications.

  In particular, the event management device described in Patent Document 4 supports communication between various tag readers and various applications in order to reduce the amount of data transmitted from a plurality of different types of tag readers to applications, and tag data acquired from the tag readers. Event generation processing and data filtering processing are performed on In this event management device, communication between the tag reader and the application is supported by compatibility and conversion between different tag reader protocols. Tag data acquired for each tag reader is stored in the data storage unit after filtering and event generation. Stored and provided to various applications.

JP 2009-157779 A (released on July 16, 2009) JP 2009-134722 A (released on June 18, 2009) JP 2008-158651 A (released July 10, 2008) Special Table 2008-524742 (announced July 10, 2008)

  However, in the prior art described in Patent Document 4 described above, information on RF tags and tag readers to be managed by the system is collectively managed by one event management device, and all the acquired tag data is stored in one database. The Therefore, when the number of RF tags to be managed increases, the load on the event management device that manages the tag data increases, and the performance of the system significantly decreases. In other words, in order to keep the system performance above a certain level, it is necessary to keep the number of RF tags to be managed below a certain number. The prior arts described in Patent Documents 1 to 3 also have the same problem because all tag information is collectively managed by one platform.

  The present invention has been made in view of the above problems, and its object is to provide an RFID platform system that does not cause a significant performance degradation even when the number of RF tags to be managed increases, in other words, It is an object of the present invention to provide an RFID platform system that can increase the number of RF tags to be managed without any significant performance degradation.

  In order to solve the above problems, an RFID platform apparatus system according to the present invention includes a plurality of platform apparatuses that manage different RF tag groups, a master platform apparatus that manages addresses of the plurality of platform apparatuses, and the plurality of platforms. A logger device corresponding to one of the devices, and when the RF tag is included in an RF tag group managed by the corresponding platform device, a logger device that transmits tag data read from the RF tag to the corresponding platform device; If the RF tag is not included in the RF tag group managed by the corresponding platform device, the logger device queries the master platform device for the address of the platform device that manages the RF tag, and And the platform device inquires of each of the plurality of platform devices whether the platform device manages the RF tag, and returns the address of the platform device that replied that the platform device manages the RF tag to the logger device. The logger device transmits the tag data read from the RF tag to the address replied from the master platform device.

  In order to solve the above problems, a management method according to the present invention includes a plurality of platform devices that manage different RF tag groups, a master platform device that manages addresses of the plurality of platform devices, and the plurality of platforms. A management method for managing tag data read from an RF tag using a logger device corresponding to any of the devices, and the logger device when the RF tag is included in an RF tag group managed by a corresponding platform device Transmitting the tag data read from the RF tag to the corresponding platform device, and when the RF tag is not included in the RF tag group managed by the corresponding platform device, the logger device The address of the platform device to be managed A platform device that inquires to the platform device, and inquires of each of the plurality of platform devices whether it is a platform device that manages the RF tag, and that it is a platform device that manages the RF tag. Replying to the logger device, and the logger device transmitting the tag data read from the RF tag to the address answered from the master platform device in response to the inquiry. It is characterized by that.

  According to the above configuration, even when the RF tag is not included in the RF tag group managed by the corresponding platform device, the logger device knows the address of the platform device managing the RF tag by making an inquiry to the master platform device. The tag data can be transmitted to the platform device that manages the RF tag. That is, the logger device can correctly transmit the tag data regardless of which platform device is managing the RF tag.

  Moreover, the RFID platform system shares and manages RF tags by a plurality of platform devices. For this reason, even if the number of RF tags to be managed increases, a decrease in system performance can be easily avoided by adding a new platform device. Note that the addition of a new platform device is extremely easy because it is only necessary to register its address in the master platform.

  Further, the master platform device only needs to manage the addresses of a plurality of platform devices, and does not need to manage tag IDs or tag data. For this reason, even if the number of RF tags to be managed increases and the number of platform devices increases, the master platform device does not become a bottleneck, and there is no possibility that the performance of the system will deteriorate.

  In the RFID platform device system according to the present invention, the logger device inquires to the master platform device by transmitting the tag ID of the RF tag to the master platform device. By transmitting the tag ID of the RF tag to each of the plurality of platform devices, each of the plurality of platform devices is inquired, and each of the plurality of platform devices is a tag of the RF tag managed by itself. It has a database storing ID, it is determined whether or not the tag ID of the RF tag transmitted from the master platform device is stored in the database, and the tag ID of the RF tag is stored in the database If it is determined that the address is determined, the platform responds to the master platform device by transmitting its own address to the master platform device, and the master platform device responds that the platform device manages the RF tag. It is preferable to reply to the logger device by sending the address of the device to the logger device.

  According to the above configuration, the inquiry transmitted from the logger device to the master platform device and the inquiry transmitted from the master platform device to each platform device include the tag ID of the RF tag detected by the logger device. . Then, the platform device determines whether or not the tag ID of the RF tag managed by itself stored in the database includes the tag ID of the RF tag included in the inquiry from the master platform device. If it is determined that the platform device is, the platform device transmits its own address to the master platform device. Further, the master platform device answers the logger device by transmitting the address transmitted from the platform device to the logger device.

  In the RFID platform device system according to the present invention, the logger device includes a cache that associates and stores the tag ID of the RF tag and the transmission destination address to which the tag data read from the RF tag is transmitted, When a new RF tag is not included in the RF tag group managed by the corresponding platform device, a transmission destination address for transmitting tag data read from the new RF tag is set to the tag of the new RF tag in the cache. It is preferable to set the destination address associated with the ID.

  According to the above configuration, even if the RF tag is not included in the RF tag group managed by the corresponding platform device, if the tag data of the RF tag is transmitted for the second time or later, it is transmitted to the master platform device. The destination address can be read from the cache without making an inquiry. For this reason, the performance of the system can be further improved.

  Further, a configuration including a plurality of the RFID platform systems described above and further adding a higher-level master platform device for managing the address of the master platform device included in each RFID platform system also falls within the scope of the present invention.

  According to the above configuration, even if the number of RF tags to be managed increases exponentially, it is possible to easily avoid a decrease in system performance by adding a higher-level master platform device.

  In addition, a logger device, a platform device, and a master platform device included in the RFID platform system also fall within the scope of the present invention.

  That is, the logger device of the present invention is a logger device corresponding to the platform device that manages the RF tag group, and when the RF tag is not included in the RF tag group, the address of the platform device that manages the RF tag is set. Inquiry means for inquiring a master platform device that manages addresses of a plurality of platform devices including the platform device, and when the RF tag is included in the RF tag group, tag data read from the RF tag Transmitting means for transmitting to the device, and when the RF tag is not included in the RF tag group, transmitting means for transmitting the tag data read from the RF tag to the address to which the master platform device responded to the inquiry; It is characterized by having.

  The platform device of the present invention is a platform device that manages a group of RF tags, and is an inquiry from a master platform device that manages the addresses of a plurality of platform devices including the platform device. When the specific RF tag is included in the RF tag group in response to an inquiry asking whether it is a platform device to be managed, an answering means for replying that the platform device manages the specific RF tag is provided. It is characterized by having.

  A master platform device that manages addresses of a plurality of platform devices that manage different RF tag groups, and is an inquiry from a logger device corresponding to any of the plurality of platform devices, and a specific RF tag is In response to an inquiry asking for an address of a platform device to be managed, each of the plurality of platform devices is inquired as to whether the platform device manages the specific RF tag, and is a platform device that manages the specific RF tag. An answering means for answering the address of the responding platform device to the logger device is provided.

  As described above, the RFID platform system according to the present invention includes any one of a plurality of platform devices that manage different RF tag groups, a master platform device that manages addresses of the plurality of platform devices, and the plurality of platform devices. And a logger device that transmits tag data read from the RF tag to the corresponding platform device when the RF tag is included in an RF tag group managed by the corresponding platform device. When the RF tag is not included in the RF tag group managed by the corresponding platform device, the device inquires the address of the platform device managing the RF tag to the master platform device, and the master platform device Each of the plurality of platform devices is inquired about whether or not it is a platform device that manages the RF tag, and the address of the platform device that replied that it is a platform device that manages the RF tag is answered to the logger device. The tag data read from the RF tag is transmitted to the address answered from the master platform device.

  Therefore, even if the number of RF tags to be managed increases, it is possible to realize an RFID platform system that does not cause significant performance degradation.

1 is a system configuration diagram showing an overall configuration of an RFID platform system according to a first embodiment of the present invention. It is a block diagram which shows the principal part structure of the logger contained in the RFID platform system of FIG. It is a block diagram which shows the principal part structure of the platform contained in the RFID platform system of FIG. It is a block diagram which shows the principal part structure of the master platform contained in the RFID platform system of FIG. It is a figure which shows the tag management table contained in the database (master database) of the platform shown in FIG. It is a figure which shows the tag reader management table contained in the database (master database) of the platform shown in FIG. It is a figure which shows the abstract data management table contained in the database (master database) of the platform shown in FIG. It is a figure which shows the index data management table of the master platform shown in FIG. It is a figure which shows the cache data management table of the logger shown in FIG. It is a figure which shows the whole structure of the RFID platform system which concerns on the 2nd Embodiment of this invention.

[RFID platform system]
(Embodiment 1)
The following describes the first embodiment of the present invention with reference to FIGS. In the following description, an “RF tag” refers to a tag capable of short-range wireless communication in which an IC chip storing a tag ID is embedded, and it is questionable whether it is a passive tag or an active tag. Absent.

  An RFID platform system 1 according to the present embodiment will be described with reference to FIG. FIG. 1 is a system configuration diagram showing an overall configuration of an RFID platform system 1 according to the present embodiment. As shown in FIG. 1, the RFID platform system 1 includes a master platform (master platform device) 2 (MPLAT), a platform (platform device) 3 (PLAT1-2), and a logger (logger device) 4 (LOG1-4). I have.

  In this embodiment, the RFID platform system 1 includes PLAT1 and PLAT2 that are platforms 3 below the MPLAT that is the master platform 2. Further, LOG1 and LOG2 that are loggers 4 are provided below PLAT1, and LOG3 and LOG4 that are loggers 4 are provided below PLAT2. Thus, the master platform 2, the platform 3, and the logger 4 form a hierarchical structure. Further, two child loggers 5 are provided below each logger 4. The child loggers 5 are connected to the corresponding RF tag readers 6 on a one-to-one basis.

  Two platforms 3 below the master platform 2 are operating on different servers 8. The lower logger 4 and the child logger 5 of each platform 3 operate on the same server 8 as that platform 3. The master platform 2 operates on a server (not shown) different from these two platforms 2. That is, the RFID platform system 1 includes a first server 8 that functions as PLAT1, LOG1, LOG2, LOG11, LOG12, LOG21, and LOG22, and a second server that functions as PLAT2, LOG3, LOG4, LOG31, LOG32, LOG41, and LOG42. This is realized by the server 8 and a third server functioning as MPLAT.

  The RFID platform system 1 is a system for managing the location of each RF tag 7. Here, managing which RFID reader 6 the RF tag 7 exists in the vicinity is between the tag ID of each RF tag 7 and the reader ID of the RF tag reader 6 that detected the RF tag 7. Refers to giving a dynamic association.

  The RFID platform system 1 according to the present embodiment is characterized in that the location of the RF tag 7 to be managed is shared and managed by the two platforms 3. That is, the RF tag 7 to be managed is divided into a first RF tag group and a second RF tag group, the location of the first RF tag group is managed by the first platform 3 (PLAT1), and the second The location of the RF tag group is managed by the second platform 3 (PLAT2).

  In the RDID platform system 1, the location of each RF tag 7 is managed as follows.

  That is, when short-range wireless communication is possible with the RF tag 7, the RF tag reader 6 detects the RF tag 7 by obtaining the tag ID from the RF tag 7. When the RF tag reader 6 detects the RF tag 7, the tag data acquired from the RF tag 7 is transmitted to the upper logger 4 via the child logger 5. Here, the tag data transmitted from the RF tag reader 6 includes at least the tag ID of the detected RF tag 7 and the reader ID of the detected RF tag reader 6.

  The logger 4 stores the tag IDs of all the RF tags 7 that should be managed by the platform 3 that is higher than the logger 4, and the tag IDs included in the received tag data should be managed by the platform 3 that is higher than itself. It can be determined whether or not the RF tag 7 is used. When the tag ID included in the received tag data is that of the RF tag 7 that should be managed by the platform 3 that is higher than itself, the logger 4 stores the received tag data in the database of the platform 3 that is higher than itself. To store. This is the same processing as the conventional RFID platform system. On the other hand, if the tag ID included in the received tag data is not that of the RF tag 7 that should be managed by the platform 3 that is higher than the tag ID, which platform 3 should be managed by this platform 3 Is unknown to the logger 4 for the time being.

  Therefore, if the tag ID included in the received tag data is not that of the RF tag 7 that should be managed by the platform 3 that is higher than the logger 4, the logger 4 inquires of the master platform 2 about the platform 3 that should store the tag data. Here, the inquiry transmitted by the logger 4 includes a tag ID (a tag ID included in the tag data received by the logger 4). The master platform 2 that has received the inquiry from the logger 4 refers to the index data, and broadcasts the inquiry to all the platforms 3 existing under it (other than the platform 3 related to the logger 4 that has made the inquiry). . Here, the inquiry transmitted by the master platform 2 also includes the tag ID (the tag ID included in the tag data received by the logger 4). The inquiry that the logger 4 sends to the master platform 3 and the inquiry that the master platform 3 sends to each platform 2 can be realized as a query in an inquiry language (including a database language), for example.

  Each platform 3 that has received an inquiry from the master platform 2 compares the tag ID included in the inquiry with the tag ID of the RF tag 7 to be managed by itself, and if they match, the IP address is transferred to the master platform 2. Answer by sending. The master platform 2 that has received the reply responds by transmitting the IP address transmitted from the platform 3 to the logger 4 that made the inquiry. The logger 4 that has received the answer stores the tag data in the platform 3 based on the answer.

  As described above, the RFID platform system 1 shares and manages the tag data of the plurality of RF tags 7 by the plurality of platforms 3, and provides a database for storing the tag data of the RF tag 7 in each platform 3. . For this reason, access is not concentrated on one server, and performance degradation can be avoided. Therefore, even when the number of RF tags 7 and RF tag readers 6 to be managed is increased, if the number of platforms 3 to be managed is increased accordingly, the burden on one server can be reduced. .

  In addition, since the master platform 2 that manages each platform 3 has only the index data of the subordinate platform 3, even when the number of subordinate platforms 3 increases, only the IP address is added to the index data. It's okay. Therefore, it is not necessary to use a large-capacity database, and it is excellent in expandability.

  In this embodiment, the RFID platform system 1 operates the platform 3 and the lower-level logger 4 on the same server. However, in order to further improve the server performance, the RFID platform system 1 is operated on different servers. May be. The master platform 2 may be operated on a server different from the platform 3 and the logger 4, or may be operated on the same server as any platform 3. In other words, as long as a plurality of platforms 3 are operated on different servers, the operation locations of other blocks are not particularly limited.

  Further, the number of platforms 3, loggers 4 and child loggers 5 is not particularly limited, and may be appropriately increased according to the number of RF tag readers 6 and RF tags 7 to be managed. In particular, in order to distribute the load applied to the platform 3, a plurality of loggers 4 are operated per one platform 3, or other lower loggers 4 are applied to a platform 3 having a higher processing frequency than the other platforms 3. It is possible to cope with various operation modes such as operating more than the lower loggers 4 of the platform 3.

(Configuration of Logger 4)
The principal part structure of the logger 4 is demonstrated with reference to FIG. FIG. 2 is a block diagram showing a main configuration of the logger 4. As shown in FIG. 2, the logger 4 includes a master data acquisition unit 11, a master data memory 12, a cache memory 13, a tag data reception unit 14, a tag ID determination unit 15, a tag ID inquiry unit (inquiry means) 16, A tag memory 17 and a tag data transmission unit (transmission means) 18 are provided.

  Hereinafter, each part of the logger 4 will be described. In the present embodiment, LOG1 managed by PLAT1 will be described as an example of the logger 4.

  The master data acquisition unit 11 is a means for acquiring the tag ID of the RF tag 7 managed by the upper platform 3 (PLAT 1 in this embodiment). The master data acquisition unit 11 stores the acquired tag ID as master data in the master data memory 12. The tag ID stored in the master data memory 12 is hereinafter referred to as “master tag ID”.

  The tag data receiving unit 14 is means for receiving tag data acquired from the RF tag 7 by the RF tag reader 6 (R1 or R2 in the present embodiment). The tag data received by the tag data receiving unit 14 is transmitted from the RF tag reader 6 when the RF tag 7 is detected. At least the tag ID of the RF tag 7 and the reader ID of the RF tag reader 6 Is included. The tag data receiving unit 14 stores the received tag data in the tag memory 17 and provides the tag ID included in the received tag data to the tag ID determining unit 15. The tag memory 17 stores in advance the IP address (PLAT address) of the platform 3 that manages itself.

  The tag ID determination unit 15 is a means for determining whether or not the received tag data is related to the RF tag 7 to be managed by the upper platform 3 (PLAT 1 in the present embodiment). Specifically, (1) the tag ID acquired from the tag data receiving unit 14 is compared with each master tag ID stored in the master data memory 12, and (2-1) if there is a matching master tag ID, When it is determined that the tag data is related to the RF tag 7 to be managed by the upper platform 3 and (2-2) there is no matching master tag ID, the tag data is the RF tag to be managed by the upper platform 3 7 is determined not to be related. The tag ID determination unit 15 provides the determination result to the tag data transmission unit 18. If it is determined that the tag data is not related to the RF tag 7 to be managed by the upper platform 3, the tag ID acquired from the tag data receiving unit 14 is provided to the tag ID inquiry unit 16.

  If the received tag data is not related to the RF tag 7 that should be managed by the upper platform 3 (PLAT 1 in this embodiment), the tag ID inquiry unit 16 manages the platform 3 (this book) that manages the tag data. In the embodiment, it is a means for inquiring the master platform 2 for the IP address of PLAT2). Specifically, the tag ID acquired from the tag ID determination unit 15 is transmitted to the master platform 2 and, as a response, the IP address of the platform 3 that should manage the received tag data is received from the master platform 2. Then, the tag ID inquiry unit 16 provides the received IP address to the tag data transmission unit 18. In this embodiment, the IP address of PLAT 2 is received from the master platform 2.

  In the present embodiment, a configuration using a cache is employed to speed up the IP address inquiry process in the tag ID inquiry unit. That is, when the tag ID is acquired, the tag ID inquiry unit 16 first reads cache data (cache information) from the cache memory 13. This cache data includes data relating to the RF tag 7 detected previously. That is, the cache data stores the tag ID of the RF tag 7 managed by the platform 3 other than PLAT1 among the previously detected RF tags 7 in association with the IP address of the platform 3 that manages the RF tag 7. ing. In the present embodiment, the cache data includes the tag ID of the RF tag 7 managed by PLAT2 and the IP address of PLAT2 that manages this.

  The tag ID inquiry unit 16 compares the tag ID acquired from the tag ID determination unit 15 with the tag ID included in the cache data, and determines whether there is a matching tag ID. If a tag ID that matches the cache data exists, the IP address associated with the tag ID included in the cache data is provided to the tag data transmission unit 18 without making an inquiry to the master platform 2.

  When the IP address of the platform 3 is received from the master platform 2, the detected tag ID of the RF tag 7 is stored in the cache memory in association with the IP address received from the master platform 2. The cache data updated in this way is used the next time the same RF tag 7 is detected. In addition, cache data that has not been used for a certain period is deleted.

  When the tag data received by the tag data receiving unit 14 is tag data related to the RF tag 7 to be managed by the upper platform 3, the tag data transmitting unit 18 uses the tag data as the IP address of the upper platform 3 (this embodiment) In this mode, the tag data is transmitted to the IP address (PLAT1 IP address). Otherwise, the tag data is transmitted to the IP address acquired from the master platform 2 (in this embodiment, the IP address of PLAT2).

  Specifically, when the determination result that the received tag data is related to the RF tag 7 managed by the upper platform 3 is acquired from the tag ID determination unit 15, the tag data transmission unit 18 The tag data and the IP address of the upper platform 3 are read from 17. Then, the tag data transmission unit 18 transmits the tag data read from the tag memory 17 to the IP address read from the tag memory 17. When the determination result that the received tag data is not related to the RF tag 7 to be managed by the upper platform 3 is acquired from the tag ID determination unit 15, the tag data transmission unit 18 reads the tag data from the tag memory 17, An IP address is acquired from the tag ID inquiry unit 16. Then, the tag data transmission unit 18 transmits the tag data read from the tag memory 17 to the IP address acquired from the tag ID inquiry unit 16.

  As described above, when the logger 4 receives the tag data of the detected RF tag 7 from the RF tag reader 6, the logger 4 detects based on the master data of the platform 3 that manages the tag data or the cache data related to the tag data detected before. The platform 3 that stores the tag data of the RF tag 7 is determined. When the master data or the cache data does not include information on the platform 3 that stores the detected tag data of the RF tag 7, the tag data of the RF tag 7 is transmitted to the master platform 2 that manages the platform 3. Is inquired about the platform 3 for storing.

  Thereby, even if the database which stores tag data is distributed to a plurality of servers, tag data can be stored accurately. Further, the tag data storage processing time can be shortened by acquiring the tag data storage destination by combining the master data reference, the cache data reference, and the inquiry to the master platform 2.

(Configuration of platform 3)
The configuration of the main part of the platform 3 will be described with reference to FIG. FIG. 3 is a block diagram showing a main configuration of the platform 3. As shown in FIG. 3, the platform 3 includes a tag data receiving unit 21, an abstract database 22, a master database 23, a tag data query determination unit (answer means) 24, and a tag ID query unit 25.

  Hereinafter, an outline of tag data storage processing by the platform 3 will be described. In the present embodiment, the PLAT1 tag data storage process will be described as an example of the platform 3 process.

  The tag data receiving unit 21 receives tag data transmitted from the logger 4 and stores it in the abstract database 22. The abstract database associates identification information (reader ID) unique to the RF tag reader 6 that transmits tag data to the logger 4 via the child logger 5 and the tag ID of the RF tag 7 detected by the RF tag reader 6. Thus, tag data representing the detection history of the RF tag 7 is stored.

  The master database 23 transmits master data including information on the RF tag 7 to be managed by PLAT1 to the master data acquisition unit 11 of LOG1. Further, the master database 23 transmits the master ID included in the master data to the tag data inquiry determination unit 24. The master database 23 stores a tag management table and a tag reader management table described later.

  The tag ID inquiry unit 25 receives an inquiry from the master platform 2 as to whether or not the detected tag ID of the RF tag 7 is included in the master data, and transmits the received tag ID to the tag data inquiry determination unit 24. The tag data inquiry determination unit 24 that has received the tag ID acquires the master ID from the master database 23, determines whether the tag ID is included in the master ID, and sends the determination result to the tag ID inquiry unit 25. Send. The tag ID inquiry unit 25 transmits the received determination result to the master platform 2.

  Thus, the platform 3 needs to store the tag data only when the RF tag 7 managed by the platform 3 is detected, and needs to store the tag data when another RF tag 7 is detected. There is no. Therefore, access is not concentrated on one platform 3, and a performance degradation can be avoided.

(Configuration of master platform 2)
The principal part structure of the master platform 2 is demonstrated with reference to FIG. FIG. 4 is a block diagram showing a main configuration of the master platform 2. As shown in FIG. 4, the master platform 2 includes a tag ID inquiry unit (answering means) 31, a PLAT address database 32, and a PLAT inquiry unit 33.

  Hereinafter, an outline of response processing in the master platform 2 in response to an inquiry from the platform 3 will be described. In the present embodiment, a response process to an inquiry from LOG 1 will be described as a process example of the master platform 2.

  When the tag ID inquiry unit 31 receives an inquiry from the platform 3 that stores the tag data of the detected RF tag 7 from the LOG 1, the tag ID inquiry unit 31 provides the tag ID of the RF tag 7 included in the inquiry to the PLAT inquiry unit 33. To do. The PLAT inquiry unit 33 that has acquired the tag ID acquires the IP addresses of all platforms 3 managed by the master platform 2 from the PLAT address database 32. The PLAT address database 32 stores an index data table including IP addresses of all platforms 3 managed by the master platform 2.

  The PLAT inquiry unit 33 transmits the tag ID included in the inquiry from the LOG 1 to all the IP addresses acquired from the PLAT address database 32, and inquires whether the tag ID is included in the master data. However, it is not necessary to make an inquiry to PLAT1 that manages the inquired LOG1. Each platform 3 that has received the inquiry has the tag ID received from the master platform 2 as long as the tag ID of the RF tag 7 managed by its own device (if the received tag ID is a tag ID included in the master data). The IP address of the own device is returned to the master platform 2. When the PLAT inquiry unit 33 receives an answer from the platform 3 that manages the RF tag 7 being inquired, the PLAT inquiry unit 33 provides the tag ID inquiry unit 31 with the IP address of the platform 3 as the PLAT address. To do. The tag ID inquiry unit 31 transmits the acquired PLAT address to LOG1.

  In this way, the master platform 2 only transfers the inquiry from the logger 4 to the platform 3 under its control, and does not perform the tag data storage process or the storage destination search process by itself. That is, only the IP address of the platform 3 managed by itself is managed as index data, and does not have other master data. Therefore, even if the number of subordinate platforms 3, loggers 4 and RF tag readers 6 increases, it is only necessary to add the IP address of the platform 3, a large-capacity database is not required, and the scalability is excellent.

(Example of table in master database 23)
The master database 23 provided in the platform 3 stores master data of the RF tag 7 and the RF tag reader 6 managed by the platform 3 itself. That is, master data relating to the RF tag 7 that stores tag data and the RF tag reader 6 that detects the tag is stored in its own abstract database 22. This master data is extracted by the master data acquisition unit 11 of the logger 4 or the tag data inquiry determination unit 24 of the platform 3 and used for managing tag data.

  Examples of tables stored in the master database 23 are shown in FIGS. FIG. 5 is a diagram illustrating a tag management table, and FIG. 6 is a diagram illustrating a tag reader management table. The master database 23 can store not only these tables but also various tables required when each block in the RFID platform system 1 executes a predetermined process.

(Tag management table)
The tag management table shown in FIG. 5 stores identification information (tag ID) unique to the RF tag 7 and name information of the user who owns the RF tag 7 in association with each other. The tag ID is identification information (an integer in this embodiment) uniquely assigned to each RF tag 7. That is, each user has an RF tag 7 to which a unique tag ID is assigned.

  Therefore, the logger 4 refers to the master data acquired from the tag management table using the tag ID value included in the radio signal transmitted from the RF tag reader 6, and the tag of the RF tag 7 detected by the RF tag reader 6. It can be determined whether or not the data is stored in the platform 3 that manages the data.

(Tag reader management table)
The tag reader management table shown in FIG. 6 stores identification information (reader ID) unique to the RF tag reader 6 and information indicating the installation location of the RF tag reader 6 in association with each other. This reader ID is identification information (an integer in this embodiment) uniquely assigned to each RF tag reader 6. Further, when the RF tag reader 6 transmits a signal including the detection result of the RF tag 7 to the logger 4, the RF tag reader 6 includes a unique reader ID assigned to the RF tag reader 6 in the signal.

  That is, in the signal output from the RF tag reader 6, the detected tag ID of the RF tag 7 and the reader ID of the RF tag reader 6 are associated with each other. The logger 4 stores the detection result of the RF tag 7 detected by the RF tag reader 6 in the platform 3 in association with the reader ID of the detected RF tag reader 6.

(Example of table in the abstract database 22)
The abstract database 22 provided in the platform 3 stores history data (abstract data) representing detection information or non-detection information of the RF tag 7 by the RF tag reader 6. The abstract data is transmitted as tag data from the tag data transmission unit 18 of the logger 4 to the tag data reception unit 21 of the platform 3 and stored in the abstract database 22 by the tag data reception unit 21.

  An example of the abstract data management table stored in the abstract database 22 is shown in FIG. FIG. 7 shows an abstract data management table. The abstract database 22 can store not only this table but also various tables required when each block in the RFID platform system 1 executes a predetermined process.

  The abstract data management table shown in FIG. 7 includes the tag ID of the RF tag 7, the reader ID of the RF tag reader 6 that detected the RF tag 7, the detection start time of the RF tag 7, and the detection end of the RF tag 7. Time and information indicating the detection state of the RF tag 7 are stored in association with each other.

  Each RF tag reader 6 transmits a signal including the detection result of the RF tag 7 to the RFID platform system 1 via the child logger 5 every time a predetermined time elapses. The signal received by the child logger 5 is sent to the logger 4 that manages the child logger 5. The logger 4 analyzes the received signal, generates record information indicating whether or not the RF tag 7 is detected by the RF tag reader 6 at a certain time, and stores it in the platform 3. Therefore, the platform 3 stores data indicating whether or not the RF tag 7 has been detected at a certain time for all the RF tags 7 managed in the platform 3 every time a certain time elapses. To go.

  In the present embodiment, the RF tag reader 6 counts the time itself, and the detection process of the RF tag 7 is started when a predetermined time has elapsed. Then, after the detection process is completed, a radio signal including the detection result of the RF tag 7 is transmitted to the logger 4 via the child logger 5. On the other hand, the logger 4 passively processes a signal sent from the RF tag reader 6 to accumulate tag data every time the specified time elapses.

  On the contrary, the tag data receiving unit 14 of the logger 4 actively counts the time itself, and when the specified time has elapsed, a signal instructing the RF tag reader 6 to detect the RF tag 7 may be transmitted. Good. In this case, each RF tag reader 6 starts detection processing of the RF tag 7 immediately after receiving the instruction signal.

(Data accumulation in the abstract data management table)
The logger 4 stores the detection history of the RF tag 7 in the platform 3 by analyzing the tag data representing the detection history of the detected RF tag 7. Specifically, in the abstract data management table in the abstract database 22 of the platform 3, if the RF tag 7 is detected when the RF tag 7 is in a non-detection state, the detection history of the RF tag 7 is detected. Is generated and stored in the abstract data management table.

  In the present embodiment, the logger 4 performs detection history accumulation processing every time new tag data is detected. It should be noted that when a certain number of tag data is detected, the detection history storage processing can be performed collectively.

  Using FIG. 7 as an example, the flow in which records are accumulated in the abstract data management table will be described. First, since no record is stored in the abstract data management table in the initial state, the detection state of any RF tag 7 is “non-detection”. Here, at time “11:11:10”, the logger 4 has detected the RF tag 7 assigned the tag ID “0001” from the RF tag reader 6 assigned the reader ID “0001”. Assume that raw data is received.

  At this time, the logger 4 determines that the RF tag 7 has changed from the non-detection state to the detection state by processing the raw data. As a result, the record on the first line is generated in the abstract data management table. Specifically, the tag ID of the detected RF tag 7, the reader ID of the RF tag reader 6 that detected the RF tag 7, the time when the RF tag 7 was detected (tag detection start time), and the detection state are shown. A record in which information (here “detection”) is associated with each other is generated. Since the detection of the RF tag 7 has not ended yet, the tag detection end time is blank (no data).

  Thereafter, the logger 4 periodically receives a signal indicating that the RF tag 7 assigned the tag ID “0001” is detected from the RF tag reader 6 assigned the reader ID “0001”. ing. That is, the detection of the RF tag 7 continues without ending. Therefore, the record in the first line of the abstract data management table is not changed as it is.

  Here, it is detected that the logger 4 has detected the RF tag 7 to which the tag ID “0002” is assigned from the RF tag reader 6 to which the reader ID “0002” is assigned at the time “01:01:00”. Assume that raw data is received. The logger 4 determines that the RF tag 7 has changed from the non-detection state to the detection state by processing the raw data. As a result, the record on the second line is generated in the abstract data management table. At this time, the tag ID of the detected RF tag 7, the reader ID of the RF tag reader 6 that detected the RF tag 7, the time when the RF tag 7 was detected (tag detection start time), and information indicating the detection state ( Here, a record in which “detection”) is associated with each other is generated. Since the detection of the RF tag 7 has not ended yet, the tag detection end time is blank (no data).

  The logger 4 still periodically receives a signal indicating that the RF tag 7 assigned the tag ID “0001” is detected from the RF tag reader 6 assigned the reader ID “0001”. doing. That is, the detection of the RF tag 7 is continued without ending. Therefore, the record in the first row of the extracted data management table is not changed as it is.

  Next, when the logger 4 detects the RF tag 7 to which the tag ID “0002” is assigned from the RF tag reader 6 to which the reader ID “0002” is assigned at the time “01:01:01”. Suppose that no signal is received. At this time, the logger 4 stores raw data indicating that the RF tag 7 has not been detected at the time in the abstract data management table. The logger 4 determines that the detection of the RF tag 7 is completed by processing the raw data, and sets the time “01:01:01” in the tag detection end time column in the record of the second row. In addition, the detection status column of the record is changed from “detected” to “not detected”. By these processes, data (record) indicating the detection history of the RF tag 7 is closed. In other words, the record in the second row remains as a history in the abstract data management table, and the content does not change any more.

  Next, when the logger 4 detects the RF tag 7 to which the tag ID “0002” is assigned from the RF tag reader 6 to which the reader ID “0002” is assigned at the time “01:01:10”. Assume that raw data is received. At this time, the logger 4 specifies the tag ID of the detected RF tag 7 by processing the raw data. Then, the latest record in which the identified tag ID “0002” is stored is retrieved from the records recorded in the extracted data management table. Then, the value of the detection state column in the retrieved record is acquired.

  In the example of FIG. 7, at this time, the logger 4 detects the record in the second row and acquires “non-detection” as the value in the detection state column. Therefore, the logger 4 determines that the RF tag 7 to which the tag ID “0002” is assigned has newly changed from the non-detection state to the detection state. Thereby, the record in the third row is generated as a new record in the extracted data management table. Specifically, the tag ID of the detected RF tag 7, the reader ID of the RF tag reader 6 that detected the RF tag 7, the time when the RF tag 7 was detected (tag detection start time), and the detection state are shown. A record in which information (here “detection”) is associated with each other is generated. Since the detection of the RF tag 7 has not ended yet, the tag detection end time is blank (no data).

  By repeating the above procedure, the logger 4 accumulates records in the abstract data management table. In the example of FIG. 7, records up to the third line are accumulated, and each record indicates a detection history of any RF tag 7. That is, in the example of FIG. 7, the RF tag 7 assigned the tag ID “0001” and the RF tag 7 assigned the tag ID “0002” 4 until the latest point in time when 4 refers to the tag abstract data management table). Note that since the RF tag 7 to which the tag ID “0002” is assigned has been detected once before, its history remains in the abstract data management table (record in the second row).

(Example of table in PLAT address database 32)
The PLAT address database 32 of the master platform 2 stores index data including the IP addresses of all platforms 3 managed by the master platform 2. This index data is extracted by the PLAT inquiry unit 33 and used for an inquiry of the platform 3 that manages the detected RF tag 7.

  An example of an index data management table stored in the PLAT address database 32 is shown in FIG. FIG. 8 shows an index data management table. The PLAT address database 32 can store not only these tables but also various tables required when each block in the RFID platform system 1 executes a predetermined process.

  The index data management table shown in FIG. 8 stores the IP addresses of all platforms 3 managed by the master platform 2. Therefore, when the master platform 2 receives an inquiry from the logger 4, the tag ID value of the RF tag 7 detected by the RF tag reader 6 is sent to all platforms 3 whose IP addresses are included in the index data management table. The platform 3 including the tag ID in the master data can be inquired by transmitting.

(Example of table in cache memory 13)
The cache memory 13 of the logger 4 stores information on the platform 3 that manages the RF tag 7 that the logger 4 has recently received from the RF tag reader 6. That is, the cache memory 13 stores the IP address of the platform 3 that stores the recently detected detection data of the RF tag 7 as cache data in association with the tag ID of the RF tag 7. This cache data is used in the tag ID inquiry unit 16.

  An example of a cache data table stored in the cache memory 13 is shown in FIG. FIG. 9 is a diagram illustrating a cache data table. The cache data table shown in FIG. 9 stores the tag ID of the recently detected RF tag 7 in the RF tag reader 6 under the logger 4 in association with the IP address of the platform 3 in which the detected data of the RF tag 7 is accumulated. doing.

  When the tag ID inquiry unit 16 of the logger 4 obtains the IP address of the platform 3 that stores the tag data of the RF tag 7 from the master platform 2, the tag ID of the RF tag 7 and the RF tag are updated. 7 adds new cache data in association with the IP address of the platform 3 that manages. The added data is used when the same RF tag 7 is detected next time. Also, cache data that has not been used for a certain period is deleted.

(Embodiment 2)
The following describes the second embodiment of the present invention with reference to FIG. An RFID platform system 100 according to the present embodiment will be described with reference to FIG. FIG. 10 is a diagram showing an overall configuration of the RFID platform system 100 according to the present embodiment. As shown in FIG. 10, the RFID platform system 100 includes two master platforms 102, and is provided with an upper master platform 101 that manages the master platform 102 above the master platform 102. 1 RFID platform system 1 is different. In the present embodiment, differences from the first embodiment will be described, and other details will be omitted.

  In the present embodiment, the RFID platform system 100 includes two master platforms (MPLAT11 and MPLAT12) 102 below the upper master platform (MPLAT1) 101. Then, two platforms (PLAT1 and PLAT2) 103 are provided below MPLAT11, and a platform (PLAT3) 103 is provided below MPLAT12. The subordinate structure of PLAT1 is the same as that of the RFID platform system 1 of the first embodiment.

  PLAT2 has two loggers (LOG3 and LOG4) 104 in the lower layer, LOG3 has two child loggers (LOG31 and LOG32) 105, LOG4 has one child logger (LOG41) 105 in each lower layer. I have. PLAT3 includes three loggers (LOG5, LOG6, and LOG7) 104 at the lower level. LOG5 includes two child loggers (LOG51 and LOG52) 105, LOG6 includes one child logger (LOG61) 105, and LOG7 includes one child logger (LOG71) 105 at a lower level.

  Each child logger 105 is connected to the corresponding RF tag reader 106 on a one-to-one basis. Each of the three platforms 103 subordinate to the master platform 102 operates on a different server 108. The lower-level logger 104 and the child logger 105 of each platform 103 operate on the same server 108 as the platform 103 that manages itself. In addition, the two master platforms 102 operate on the same server 108 as any one of the lower platforms 103 or a server different from these servers 108.

  The upper master platform 101 has IP addresses of all the master platforms 102 managed by itself as index data (master platform identification information) for identifying the master platform 102. When the master platform 102 that has received an inquiry about the platform 103 that stores the tag data of the RF tag 107 from the logger 104 does not find the tag ID of the RF tag 107 in the master data of all the platforms 3 that it manages, The host master platform 101 is inquired about the platform 103 that stores the tag data of the RF tag 107.

  The upper master platform 101 that has received the inquiry refers to the index data and inquires of all the master platforms 102 other than the inquired master platform 102 about the platform 103 that stores the detection data of the RF tag 107. The master platform 102 that has received the inquiry inquires of the platform 103 managed by itself whether the tag ID of the RF tag 107 is included in the master data. By repeating such an inquiry, the storage location of the detected tag data of the RF tag 107 can be acquired.

  As described above, the RFID platform system 100 includes the master platform 102 that increases the number of master platforms 102 and manages the master platform 102 above these master platforms 102. Therefore, the RF tag reader 106 and the RF tag that manage them are provided. Even if the number of 107 further increases, the processing is not concentrated on one master platform 102, and the performance degradation can be avoided. In addition, even if the number of RF tag readers 106 and RF tags 107 to be managed further increases, it is possible to increase the number of platforms 103 for managing these, and further increase the number of master platforms 102 and upper master platforms 101 to increase the number of layers. can do.

[Program and recording medium]
Each block included in the RFID platform system 1 may be configured by hardware logic. Alternatively, it may be realized by software using a CPU (Central Processing Unit) as follows.

  That is, each device constituting the RFID platform system 1 includes a CPU that executes instructions of a program that realizes each function, a ROM (Read Only Memory) that stores the program, and a RAM (RAM that expands the program into an executable format). Random Access Memory) and a storage device (recording medium) such as a memory for storing the program and various data. With this configuration, the object of the present invention can be achieved by a predetermined recording medium.

  This recording medium only needs to record the program code (execution format program, intermediate code program, source program) of the program of the RFID platform system 1 which is software for realizing the above-described functions so as to be readable by a computer. This recording medium is supplied to the RFID platform system 1. Thus, the RFID platform system 1 (or CPU or MPU) as a computer may read and execute the program code recorded on the supplied recording medium.

  The recording medium for supplying the program code to each device constituting the RFID platform system 1 is not limited to a specific structure or type. That is, the recording medium includes, for example, a tape system such as a magnetic tape and a cassette tape, a magnetic disk such as a floppy (registered trademark) disk / hard disk, and an optical disk such as a CD-ROM / MO / MD / DVD / CD-R. System, a card system such as an IC card (including a memory card) / optical card, or a semiconductor memory system such as a mask ROM / EPROM / EEPROM / flash ROM.

  Further, even if each device constituting the RFID platform system 1 is configured to be connectable to a communication network, the object of the present invention can be achieved. In this case, the program code is supplied to each device constituting the RFID platform system 1 via a communication network. This communication network is not limited to a specific type or form as long as it can supply a program code to each device constituting the RFID platform system 1. For example, it may be the Internet, intranet, extranet, LAN, ISDN, VAN, CATV communication network, virtual private network, telephone line network, mobile communication network, satellite communication network, and the like.

  The transmission medium constituting the communication network may be any medium that can transmit the program code, and is not limited to a specific configuration or type. For example, wired communication such as IEEE 1394, USB (Universal Serial Bus), power line carrier, cable TV line, telephone line, ADSL (Asymmetric Digital Subscriber Line) line, infrared rays such as IrDA and remote control, Bluetooth (registered trademark), 802.11 It can also be used by radio such as radio, HDR, mobile phone network, satellite line, terrestrial digital network. The present invention can also be realized in the form of a computer data signal embedded in a carrier wave in which the program code is embodied by electronic transmission.

  The present invention is not limited to the above-described embodiments, and various modifications are possible within the scope shown in the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments. Is also included in the technical scope of the present invention.

  The present invention can be widely used as an RFID system.

1 RFID platform system 2 Master platform 3 Platform 4 Logger 5 Child logger 6 RF tag reader 7 RF tag

Claims (6)

A plurality of platform devices for managing different RF tag groups;
A master platform device for managing addresses of the plurality of platform devices;
When the logger device corresponds to any one of the plurality of platform devices and the RF tag is included in an RF tag group managed by the corresponding platform device, tag data read from the RF tag is transmitted to the corresponding platform device. A logger device,
If the RF tag is not included in the RF tag group managed by the corresponding platform device, the logger device queries the address of the platform device managing the RF tag to the master platform device,
The master platform device inquires of each of the plurality of platform devices whether it is a platform device that manages the RF tag, and the address of the platform device that replied that the platform device manages the RF tag is sent to the logger device. Answer
When the RF tag is not included in the RF tag group managed by the corresponding platform device, the logger device transmits the tag data read from the RF tag to the address answered from the master platform device. RFID Platform insects stem characterized by. The logger device inquires to the master platform device by transmitting the tag ID of the RF tag to the master platform device,
The master platform device inquires each of the plurality of platform devices by transmitting a tag ID of the RF tag to each of the plurality of platform devices.
Each of the plurality of platform devices has a database storing tag IDs of RF tags managed by itself, and whether the tag ID of the RF tag transmitted from the master platform device is stored in the database. If it is determined that the tag ID of the RF tag is stored in the database, the master platform device is answered by sending its own address to the master platform device,
The master platform device replies to the logger device by transmitting the address of the platform device that has replied that the platform device manages the RF tag to the logger device.
RFID Platform Musi stem according to claim 1, characterized in that. The logger device includes a cache that associates and stores the tag ID of the RF tag and the transmission destination address to which the tag data read from the RF tag is transmitted, and the new RF tag manages the corresponding platform device. When not included in the RF tag group, the transmission destination address for transmitting the tag data read from the new RF tag is set to the transmission destination address associated with the tag ID of the new RF tag in the cache.
RFID Platform Musi stem according to claim 1 or 2, characterized in that. It includes a plurality of RFID platform Musi stem according to any one of claims 1 to 3, further includes an upper master platform apparatus for managing an address of the master platform device included in each RFID Platform Musi stem ,
RFID Platform insects stem, characterized in that. A logger device corresponding to a platform device that manages a group of RF tags,
When the RF tag is not included in the RF tag group, inquiry means for inquiring the address of the platform device that manages the RF tag to the master platform device that manages the addresses of a plurality of platform devices including the platform device;
When the RF tag is included in the RF tag group, tag data read from the RF tag is transmitted to the platform device. When the RF tag is not included in the RF tag group, the tag data is read from the RF tag. Transmitting means for transmitting tag data to an address to which the master platform device responds to the inquiry,
A logger device characterized by that. Reading from the RF tag using a plurality of platform devices that manage different RF tag groups, a master platform device that manages addresses of the plurality of platform devices, and a logger device corresponding to any of the plurality of platform devices A management method for managing tag data,
When the RF tag is included in an RF tag group managed by the corresponding platform device, the logger device transmits tag data read from the RF tag to the corresponding platform device;
If the RF tag is not included in the RF tag group managed by the corresponding platform device, the logger device queries the master platform device for the address of the platform device that manages the RF tag;
The master platform device inquires of each of the plurality of platform devices whether the platform device manages the RF tag, and the address of the platform device that replied that the platform device manages the RF tag is sent to the logger device. Steps to answer,
When the RF tag is not included in the RF tag group managed by the corresponding platform device, the tag data read from the RF tag by the logger device is addressed to the address returned from the master platform device in response to the inquiry. And a step of transmitting to the management method.

Images