JP2007122604A - Tag report method, tag report program, tag report device and tag report system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To suppress detection error for reading of an RFID (Radio Frequency Identification) tag attached to a commodity. <P>SOLUTION: A computer executes a tag input procedure for inputting, when a reader 300 reads a tag 400, a tag ID 401 and a reader ID 301; an event determination procedure for transferring the current state of a designation schedule designating states related to the tag ID 401 inputted in the tag input procedure and transfer between the states, when the transfer from the current state is matched with the reader ID 301 inputted in the tag input procedure, and permitting the report of the tag ID 401; and an event report procedure for reporting the tag ID 401 permitted in the event determination procedure. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a tag notification method, a tag notification program, a tag notification device, and a tag notification system.

  In recent years, field trials and practical applications of applications using RFID (Radio Frequency Identification) tags have already begun in the fields of manufacturing, distribution, and services, and preparations for spreading are in progress. In recent cases, in addition to the integrated sales and manufacturing business categories such as the apparel industry, fields with high unit prices such as automobiles and home appliances, etc., verification tests have been conducted up to individual item management at supermarket stores with relatively low unit prices. Yes.

  Examples of tag application technologies include the following. Patent Document 1 discloses a technique for attaching a wireless ID tag to a moving body and generating accurate flow line information of the moving body that moves in a facility. Patent Document 2 discloses a technique for attaching a non-contact IC tag to a software product so that the distribution management of the software product at a lease shop or a rental shop can be accurately and easily performed. Patent Document 3 discloses a technique for improving communication safety in order to store personal information in an IC tag and prevent an authentication code included in the personal information from being stolen.

  Patent Document 1 attaches an RFID tag to a shopping cart or shopping cart, stretches an RFID reader in a store, and when the RFID reader reads the RFID tag, the RFID reader identification information, the RFID tag identification information, Information associated with the time is transmitted and stored in the DB. Then, based on the accumulated information, there has been proposed a system for displaying the flow line information of shopping carts and shopping carts, and eventually the flow line information of people who are shopping using the shopping carts and shopping carts. However, grasping the flow line information of a person by attaching an RFID tag to a shopping cart or a shopping cart may cause a privacy problem.

An application example in which an RFID tag is attached to a product is a smart shelf. The smart shelf is a device in which an RFID tag is attached to a shaver and related products, and an RFID reader is mounted on the product shelf for the purpose of preventing shoplifting, inventory management, and clarifying the person responsible for loss that occurs in the distribution process. An example of installing a smart shelf in a store and reading information from an RFID tag has been reported.
JP 2005-71252 A JP 2002-74501 A JP 2003-317044 A

  However, the conventional smart shelf may erroneously detect that the commodity is displayed on the predetermined smart shelf even though the commodity is moving in the vicinity of the predetermined smart shelf. In other words, during the movement of a product, a tag reader installed in a smart shelf different from the smart shelf on which the product is to be displayed reads the product information from the RFID tag of the moving product, so that the product can be transferred to another smart shelf. I misrecognize that the product is displayed. As a result, an erroneous event notification based on misrecognition is transmitted to a system for managing products, which may hinder business.

  For example, when a supermarket system in which RFID tags are attached to a large number of products and a large number of smart shelves are installed at a storefront is considered, the products with RFID tags attached are displayed from the warehouse to the storefront. When a product is to be delivered to a smart shelf to be sold, and vice versa, when a product is returned from a smart shelf to be displayed to a warehouse, or a consumer places it in a shopping cart to purchase a product with an RFID tag. When you carry it around.

  Therefore, the main object of the present invention is to suppress false detection regarding reading of an RFID tag attached to a product.

  The present invention is a tag notification method for notifying a tag ID read from a tag by a reader identified by a reader ID, wherein the computer specifies a plurality of states related to tag reading and a transition schedule between the states, And a procedure for storing the current state in the specified schedule in the storage means for each tag ID, a tag input procedure for inputting the tag ID of the tag and the reader ID of the reader when the reader reads the tag, and the tag input If the transition from the current state of the specified schedule related to the tag ID input in the procedure matches the reader ID input in the tag input procedure, the event determination procedure for transitioning the current state and permitting notification of the tag ID And an event notification procedure for notifying the tag ID permitted by the event determination procedure, Characterized in that it run. Other means will be described later.

  According to the present invention, by comparing the read tag ID with a specified schedule, it is possible to suppress erroneous detection regarding reading of an RFID tag attached to a product.

  The best mode for carrying out the present invention will be described below with reference to the drawings.

  FIG. 1 is an overall configuration diagram of a system according to the best mode for carrying out the present invention. The system includes a reading reader scheduling device 100, one or more reader control devices 200 connected to the reading reader scheduling device 100, one or more readers 300 connected to the reader control device 200, and one or more tags 400 read by the reader 300. Is composed of.

  The store clerk takes out the product in the warehouse, moves inside the store, and installs the product on the shelf of the sales floor. A tag 400 identified by a tag ID 401 is attached to the product. The shelf of the sales floor is provided with a reader 300 specified by the reader ID 301. The reader 300 reads the tag ID 401 by communicating with the nearby or contacting tag 400. The reader control apparatus 200 notifies the management server of the tag ID 401 read by the reader 300 in response to a request from the management server (not shown). Thereby, the management server can inform the administrator that the product is displayed on the shelf of the sales floor.

  First, in the form of the comparative example, when the reader control device 200 finds a tag 400 that the reader 300 can communicate with, the reader control device 200 unconditionally acquires all tag IDs 401 and notifies the management server. In this method, the product may be erroneously detected as being displayed on the predetermined smart shelf even though the product is moving in the vicinity of the predetermined smart shelf.

  Therefore, the present embodiment is characterized in that two conditions are set in order to select the tag ID 401 to be notified to the management server among all the tag IDs 401 acquired by the reader 300. The first condition is a designated schedule that is set based on the merchandise distribution business. The second condition is a designated condition set based on the product arrangement period. The reader control device 200 may notify the management server of the tag ID 401 that satisfies the first condition. Alternatively, the reader control device 200 may notify the management server of the tag ID 401 that does not satisfy the first condition and satisfies the second condition.

  Regarding the two conditions for selecting the tag ID 401 to be notified to the management server, whether or not the condition is satisfied is determined by the reading reader scheduling device 100 instead of the reader control device 200. The reader control device 200 may be configured as a tag notification device including the reading reader schedule device 100.

  An outline of the first condition will be described. The reading reader schedule device 100 determines whether or not to generate an event for notifying the tag ID 401 based on the designated schedule stored in the reading reader schedule DB 111. The designated schedule is a state transition table (see FIG. 2 for details) that defines the states related to reading of the tag 400 and transitions between the states.

  The outline of the second condition will be described. The reading reader scheduling apparatus 100 determines whether or not to generate an event for notifying the tag ID based on the specified conditions stored in the forced reading event generation condition DB 112 (see FIG. 3 for details).

  The tag 400 is a medium including at least a tag ID 401 that is an ID of the tag 400, such as an RFID tag, an IC card, or a barcode. The reader 300 is a device that reads one or more tag IDs 401 of the tag 400 at the same time, and includes at least a reader ID 301 that is an ID of the reader 300.

  The reader control device 200 is a device that controls one or more readers 300, and includes at least a CPU (Central Processing Unit) 201, a memory 202, a storage device 203, a communication interface 204, and one or more reader interfaces 205. And a clock 206. The reader interface 205 is an interface corresponding to the interface method of the reader 300 and communicates with the reader 300.

  The communication interface 204 is an interface such as a wired LAN (Local Area Network) card or a wireless LAN card, and communicates with at least the reading reader scheduling apparatus 100. The storage device 203 is a device that stores programs and data, such as a hard disk drive and a flash memory, and includes at least a tag reading event generation program 210 as a program.

  The tag reading event generation program 210 reads one or more tag IDs 401 from one or more readers 300, and associates each tag ID 401 with the reader ID 301 of the reader 300. The tag ID 401 -reader ID 301 pair is received.

  Then, the tag reading event generation program 210 inquires of the schedule management program 110 whether the tag 400 of the tag ID 401 is in accordance with the schedule read by the reader 300 of the reader ID 301 at that time for each of the tag ID 401 -reader ID 301 pair. . If it is according to the schedule, the event is generated as a read according to the schedule. On the other hand, if it continues to be read for the time specified by the schedule management program 110 instead of according to the schedule, an event is generated as forced reading.

  When the reader 300 reads the tag 400 by being executed by the CPU 201, the tag reading event generation program 210 is input to the tag input unit that inputs the tag ID 401 of the tag and the reader ID 301 of the reader 300, and the tag input unit If the transition from the current state of the designated schedule related to the tag ID matches the reader ID 301 input to the tag input unit, an event determination unit that transitions the current state and permits notification of the tag ID 401, and an event determination unit And an event notification unit that notifies the tag ID 401 permitted by.

  In addition, if the event notification unit matches the specified condition for the tag ID 401 whose transition from the current state of the specified schedule related to the tag ID 401 input in the tag input procedure does not match the reader ID 301 input to the tag input unit, The notification of the tag ID 401 is permitted.

  The tag reading event generation program 210 is read into the memory 202 and executed by the CPU 201, whereby each processing is executed. The tag reading event generation program 210 generates at least the tag reading buffer 211 as data in the memory 202 at the time of execution.

  The tag reading buffer 211 reads a tag ID 401 -reader ID 301 pair received by the tag reading event generation program 210 that is not in a schedule in which the tag 400 of the tag ID 401 is read by the reader 300 of the reader ID 301 at that time. The data to be buffered until the specified time has passed as long as the reading continues by associating the time when the read started with the specified time to generate an event as a forced read when the read continues for the specified time (See Figure 4 for details).

  Next, the reading reader schedule device 100 is a device such as a PC, and includes at least a CPU 101, a memory 102, a storage device 103, and a communication interface 104. The communication interface 104 is an interface such as a wired LAN card or a wireless LAN card, and communicates with one or more reader control devices 200.

  The storage device 103 is a device that stores programs and data, such as a hard disk and a flash memory, and includes at least a schedule management program 110 as a program, and at least a reading reader schedule DB 111 and a forced reading event generation condition DB 112 as data. Including. The schedule management program 110 is read from the storage device 103 into the memory 102 and executed by the CPU 101, whereby each process is executed.

  The schedule management program 110 receives a reading reader schedule confirmation request including one or more tag ID-reader ID pairs from the tag reading event generation program 210, and reads the reading reader schedule for each tag ID-reader ID pair. In accordance with the contents of the DB 111, it is confirmed whether or not the tag 400 with the tag ID was in accordance with the schedule read by the reader 300 with the reader ID at that time.

  Then, the schedule management program 110 shifts the state of the reader ID of the reader ID to which the tag 400 of the tag ID is read next if the schedule is read. Respond to. On the other hand, if the reading is not performed according to the schedule, according to the content of the forced reading event generation condition DB 112, if the tag 400 of the tag ID has been continuously read by the reader 300 of the reader ID for a specified time, the designation is made to generate an event as forced reading. The time is responded to the tag reading event generation program 210.

  The reading reader schedule DB 111 manages the schedule of which reader ID of each tag ID tag 400 is read by the reader 300. If the reading is performed according to the schedule, the reader ID of the tag ID tag 400 is the next reader ID. This is data for changing the state of reading by the ID reader 300 (see FIG. 2 for details). Note that the reading reader schedule DB 111 is set in advance by, for example, being input to an input device (not shown) of the reading reader schedule device 100 by an operation manager of the system.

  The forced read event generation condition DB 112 generates a specified time for generating an event as a forced read if it continues reading for any tag ID tag 400 that is not read as scheduled for each reader ID of the reader 300. (See FIG. 3 for details). Note that the forced reading event generation condition DB 112 is set in advance by an operation manager of the system or the like by being input to an input device (not shown) in the reading reader scheduling device 100.

  FIG. 2 is a configuration diagram of the reading reader schedule DB 111, which includes at least a tag ID 111a, a reading reader state transition table 111b, and a current state 111c as record fields. The tag ID 111a lists all the tag IDs 401 (T56, T57, T78, ...) of the tag 400 included in the system.

  The reading reader state transition table 111b is a field for managing a schedule of which reader ID of the tag 400 indicated by the tag ID 111a of the record is read by the reader 300. The reader ID of the reader 300 that permits reading in the initial state 0 is listed in the reading permitted reader ID 111b0a, and each of the reader IDs listed in the reading permitted reader ID 111b0a is listed in the reader 300 of the reader ID in the state 0. If it is read, the next state to be shifted is designated as the next state 111b0b.

  In the reading reader state transition table 111b, the reading permission reader ID 111b1a and the next state 111b1b are set in the state 1 and subsequent states as in the state 0. Note that if “any” indicating an arbitrary reader 300 is set in the read permission reader ID, reading by the reader 300 of any reader ID in that state is permitted, and nothing is set in the read permission reader ID. In this state, reading by the reader 300 of any reader ID is not permitted.

  In the current state 111c, the state at that time when the tag 400 indicated by the tag ID 111a of the record is transiting according to the contents of the reading reader state transition table 111b is stored. For example, in the tag ID “T57”, the current state 111c is “state 0”, and in order to transit to “state 1” of the next state 111b0b, “R01” or “R02” indicated by the read permission reader ID 111b0a The tag needs to be read by the reader.

  By utilizing the designated schedule, the tag ID 401 is not registered in the state transition of the designated schedule even if the shelf reader 300 reads the tag ID 401 of the product for the shelf that the store clerk passed while moving the product. Not notified. Thereby, the manager of the store can grasp the position of the displayed product, not the product being moved.

  FIG. 3 is a configuration diagram of the forced read event generation condition DB 112, which includes at least a reader ID 112a and a forced read event generation time 112b as record fields. The reader ID 112a lists all the reader IDs 301 of the reader 300 included in the system.

  During the forced read event generation time 112b, the reader 300 indicated by the reader ID 112a of the record can continue to read the tag 400 of any tag ID that is not read as scheduled during the forced read event generation time 112b. For example, specify the time to generate an event as forced reading.

  If the forced read event generation time 112b is set to 0 seconds, the reader 300 indicated by the reader ID 112a of the record reads the tag 400 of any tag ID that is not read as scheduled, and does not wait for the forced read as it is. Generate an event. If ∞ is set in the forced read event generation time 112b, no event is generated even if the reader 300 indicated by the reader ID 112a of the record reads the tag 400 of any tag ID that is not read as scheduled.

  As described above, the specified condition described in the forced read event generation condition DB 112 is based on the period of the product placed in a predetermined place and the tag of the placed product by comparison with a threshold prepared in advance. Used to determine whether to notify the ID. In FIG. 3, the specified condition is set for each reader ID, but is set for each set of reader ID and tag ID, or for each set of reader ID and tag ID, and for each current state of the specified schedule. It may be. Also, a specified number of times may be set instead of the forced reading event generation time 112b.

  Utilizing the specified conditions, such as when a customer accidentally moves a product to another shelf, the product is displayed on a product shelf that is different from the item to be displayed. State) as an event, the store manager can grasp the exact current position of each product.

  Next, FIG. 4 is a configuration diagram of the tag reading buffer 211, which includes at least a tag ID 211a, a reader ID 211b, a reading start time 211c, and a forced reading event generation time 211d as record fields.

  The tag ID 211a and the reader ID 211b are not in accordance with the schedule in which the tag 400 of the tag ID 401 among the tag ID 401-reader ID 301 pair received by the tag reading event generation program 210 is read by the reader 300 of the reader ID 301 at that time. Remember things. Note that the stored record is a record that is a candidate for notifying the tag ID 211a. On the other hand, since it is determined that the tag ID 211a is notified, it is not necessary to memorize the one according to the read schedule.

  The reading start time 211c is the time when the tag 400 indicated by the tag ID 211a of the record starts to be read by the reader 300 indicated by the reader ID 211b of the record.

  The forced read event generation time 211d generates an event as a forced read if the tag 400 indicated by the record tag ID 211a is continuously read by the reader 300 indicated by the record reader ID 211b for the forced read event generation time 211d. It is time to do.

  Next, FIG. 5 is a flowchart of read reader schedule confirmation processing by the schedule management program 110. The outline of FIG. 5 will be described below.

  The schedule management program 110 receives a reading reader schedule confirmation request including one or more tag ID-reader ID pairs from the tag reading event generation program 210, and reads the reading reader schedule for each tag ID-reader ID pair. In accordance with the contents of the DB 111, it is confirmed whether or not the tag 400 with the tag ID was in accordance with the schedule read by the reader 300 with the reader ID at that time.

  First, if the schedule management program 110 is on schedule, the schedule management program 110 transitions the state of the reader ID of the reader ID to which the tag 400 of that tag ID is read next. Respond to 210.

  On the other hand, if the schedule management program 110 is not according to the schedule, according to the content of the forced read event generation condition DB 112, if the tag 400 of the tag ID is continuously read by the reader 300 of the reader ID for a specified time, an event is detected as forced read. The specified time to be generated is responded to the tag reading event generation program 210. The outline of FIG. 5 has been described above.

  FIG. 6 shows the configuration of the reading reader schedule confirmation request 500. First, the schedule management program 110 starts processing upon receiving a reading reader schedule confirmation request 500 from the tag reading event generation program 210 (S111 in FIG. 5). The reading reader schedule confirmation request 500 is data including one or more tag ID 500a-reader ID 500b pairs.

  Then, the schedule management program 110 performs steps S112, S113, and S114 for each of the tag ID 500a-reader ID 500b pair included in the received reading reader schedule confirmation request 500.

  The schedule management program 110 determines whether or not the tag ID-reader ID pair can be read in the current state (S112). That is, when the tag ID 500a and the tag ID 111a match, the schedule management program 110 sets the read permission reader ID corresponding to the current state 111c of the read reader state transition table 111b for the record including the tag ID 111a in the read reader schedule DB 111. The reader ID 500b is checked.

  When reading is possible (S112, Yes), the schedule management program 110 changes the state of the reading reader so that the next state of the record corresponding to the current state 111c of the reading reader state transition table 111b is stored in the current state 111c. (S113), and the process proceeds to S115.

  When reading is impossible (S112, No), the schedule management program 110 determines the forced read event generation time 112b for the record including the reader ID 112a in the forced read event generation condition DB 112 when the reader ID 500b matches the reader ID 112a. Is acquired (S114), and the process proceeds to S115.

  Then, the schedule management program 110 checks whether all the tag ID 500a-reader ID 500b pairs included in the read reader schedule confirmation request 500 received in S111 have been confirmed (S115). When everything has been confirmed (S115, Yes), the process proceeds to S116, and when all has not been confirmed (S115, No), the process proceeds to S112.

  Further, the schedule management program 110 transmits a reading reader schedule confirmation request response 501 to the tag reading event generation program 210 (S116), and the reading reader schedule confirmation processing is thus completed.

  FIG. 7 shows the configuration of the reading reader schedule confirmation request response 501. The reading reader schedule confirmation request response 501 includes at least a tag ID 501a-schedule confirmation result 501b pair. All the tag IDs 500a included in the reading reader schedule confirmation request 500 received in S111 are set in the tag ID 501a. In the schedule confirmation result 501b, for each tag ID 501a, if the reader ID 500b is included in the check in S112, OK is set. If not included, the forced read event generation time 112b acquired in S114 is set.

  Next, FIG. 8 is a flowchart of tag read event generation processing. The outline of the flowchart of FIG. 8 will be described below. The tag reading event generation program 210 reads one or more tag IDs 401 from one or more readers 300, and associates each tag ID 401 with the reader ID 301 of the reader 300. The tag ID 401 -reader ID 301 pair is received.

  The tag reading event generation program 210 inquires of the schedule management program 110 whether the tag 400 of the tag ID 401 is read by the reader 300 of the reader ID 301 at that time for each of the tag ID 401 -reader ID 301 pairs, and follows the schedule. If there is, the event is generated as a read as scheduled, and the event is generated as a forced read if it is not read as scheduled but continues to be read for the time specified by the schedule management program 110. The outline of the flowchart of FIG. 8 has been described above.

  First, the tag reading event generation program 210 starts processing by receiving one or more tag ID 401-reader ID 301 pairs from one or more readers 300 in association with the time acquired from the clock 206 (S211). To do.

  Then, the tag reading event generation program 210 transmits a reading reader schedule confirmation request 500 to the schedule management program 110 (S212), and the schedule management program 110 that has received the reading reader schedule confirmation request 500 is described in the explanation of FIG. According to the method, each tag ID 500a-reader ID 500b pair included in the read reader schedule confirmation request 500 is confirmed as being read according to the schedule, and a read reader schedule confirmation request response 501 is returned to the tag read event generation program 210.

  The tag reading event generation program 210 receives the reading reader schedule confirmation request response 501, and for each of the tag ID 501a-schedule confirmation result 501b pairs included in the reading reader schedule confirmation request response 501, S213, S214, S215, and S216. Perform step processing. Note that the tag ID 500a-reader ID 500b pair of the reading reader schedule confirmation request 500 is set with all of the tag ID 401-reader ID 301 pairs received in S211.

  In S213, the tag reading event generation program 210 checks whether the schedule confirmation result 501b is OK.

  First, when the schedule confirmation result 501b is OK (S213, Yes), the read event generation program 210 is associated with the tag ID 501a, the tag ID 401-reader ID 301 pair received in S211 corresponding to the tag ID 501a, and the pair. Based on the reader ID 301 of the reader 300 that has read the tag ID 501a and the reading time, which is determined from the time at which the tag is 501a, an event is generated as scheduled reading (S214), and the event is used for business, and the process proceeds to S217.

  On the other hand, when the schedule confirmation result 501b is not OK (S213, No), the tag reading event generation program 210 matches the tag ID 401-reader ID 301 pair received in S211 corresponding to the tag ID 501a in the tag reading buffer 211. It is checked whether the tag ID 211a-reader ID 211b pair can be referenced (S215). When the pair can be referred to (S215, Yes), the process proceeds to S217, and when the pair cannot be referred to (S215, No), the process proceeds to S216.

  Then, the tag reading event generation program 210 stores the tag ID 211a-reader ID 211b pair, the reading start time 211c, and the forced reading event generation time 211d in the tag reading buffer 211 of the tag ID 401-reader ID 301 corresponding to the tag ID 501a. The pair, the time associated with the pair, and the line that is the schedule confirmation result 501b are added (S216), and the process proceeds to S217.

  Further, the tag read event generation program 210 checks whether all the tag ID 501a-schedule confirmation result 501b pairs included in the read reader schedule confirmation request response 501 received in S213 have been confirmed (S217). When everything has been confirmed (S217, Yes), the process proceeds to S218, and when all has not been confirmed (S217, No), the process proceeds to S213.

  Then, the tag reading event generation program 210 performs the processing of steps S213, S214, S215, and S216 for all of the tag ID 501a-schedule confirmation result 501b pairs included in the reading reader schedule confirmation request response 501 received in S213. As a result, the row (record) of the tag reading buffer 211 that has not been referenced or added is deleted (S218). For example, the tag reading event generation program 210 stores an ID (not shown) of a line (record) that has been referenced or added to determine which line in the tag reading buffer 211 has not been referenced or added. Can be determined.

  Further, the tag reading event generation program 210 obtains the current time from the clock 206, and the forced reading event generation time 211d has passed in the tag reading buffer 211, that is, the forced reading event generation occurs at the reading start time 211c. For each row that has passed the time 211d, an event is generated as forced reading based on the tag ID 211a, reader ID 211b, reading start time 211c, etc. of the record (S219) for use in business Connect and delete all of the lines. As described above, the tag reading event generation processing is completed and the process proceeds to reception standby (S220).

  Although the best mode for carrying out the present invention has been specifically described above, the present invention is not limited to this, and various modifications can be made without departing from the scope of the invention. For example, the system configuration of FIG. 1 may be modified as shown below.

  The tag reading event generation program 210 generates one tag reading buffer 211 as data in the memory 202 at the time of execution. The tag reading event generation program 210 has a configuration of the reader control device 200 that generates a plurality for each reader 300 connected to the reader control device 200. May be. In the reader control device 200, the reader ID may be omitted from the data buffered in the tag reading buffer 211.

  The time when the reader 300 reads the tag 400 is based on the clock 206 of the reader control device 200. However, if the reader 300 includes a clock, the time when the reader 300 reads the tag 400 is The timepiece included in 300 may be used. If all of the readers 300 connected to the reader control device 200 include a clock in the system, the clock 206 of the reader control device 200 may be omitted.

  Although the reader ID 301 is included in the reader 300, a system configuration in which the reader ID 301 is not included in the reader 300 may be employed. In the system, an ID is assigned to each of the reader interfaces 205 to which the reader 300 is connected, and the ID included in the storage device 203 as data is set as the reader ID.

  For each tag ID tag 400, the schedule of which reader ID the reader 300 reads is managed. If the system configuration includes one or more antennas connected to the reader 300, which ID antenna You may manage the schedule of whether it will be read by. That is, in the system of FIG. 1, what is managed by the reader ID is managed by the antenna ID that is the ID of the antenna.

  For each reader ID reader 300, any tag ID tag 400 that is not read as scheduled generates an event as a forced read if it continues to be read for a specified time, but continues to read for a specified number of times. In this case, the system may be configured to generate an event as forced reading.

  What the forced read event generation condition DB 112 manages at the specified time will be managed at the specified number of times, and what the tag read buffer 211 also manages at the specified time will be managed at the specified number of times. Of the data buffered in the tag reading buffer 211, the reading start time may be omitted, and the clock 206 may be omitted.

  The reading reader scheduling device 100 and one or more reader control devices 200 connected to the reading reader scheduling device 100 are included, but one integrated device that integrates the reading reader scheduling device 100 and the reader control device 200 is provided. The configuration of the system including the above may be used. In the system of FIG. 1, the reading reader schedule DB 111 and the forced reading event generation condition DB 112 are stored in the storage devices of the integrated devices, mirrored between the integrated devices, and data is duplicated.

  The schedule management program 110 is stored in the storage device 103 of the reading reader scheduling device 100, read into the memory 102, and executed by the CPU 101, so that the processing is executed in the reading reader scheduling device 100. Even if the management program 110 is stored in the storage device 203 of the reader control device 200, read into the memory 202, and executed by the CPU 201, the processing is executed in the reader control device 200. Good.

  The schedule management program 110 includes a system configuration for accessing the reading reader schedule DB 111 and the forced reading event generation condition DB 112 stored in the storage device 103, as well as a reading reader in which the schedule management program 110 is stored in the storage device 103. The schedule DB 111 and the forced reading event generation condition DB 112 may be configured to access a system that is mirrored or cached in the memory 202 or the storage device 203.

  The schedule management program 110 confirms whether the tag 400 of the tag ID is in accordance with the schedule read by the reader 300 of the reader ID at that time according to the contents of the reading reader schedule DB 111. Here, the contents of the reading reader schedule DB 111 can describe the schedule in various expression formats.

  Based on the contents of the reading reader schedule DB 111, a list of tag IDs as scheduled by the reader 300 of the reader ID is distributed in real time to the reader control device 200 connected to each reader 300, so that the list The tag read event generation program 210 of the reader control device 200 to which the message is distributed is not inquiring of the schedule management program 110 whether the tag 400 of the tag ID 401 is in accordance with the schedule read by the reader 300 of the reader ID 301 at that time. The system configuration may be such that confirmation is made by referring to the list, the confirmation result is notified to the schedule management program 110, and the confirmation result is read and reflected in the reader schedule DB.

  Although the forced reading event generation condition DB 112 is stored in the storage device 103 of the reading reader scheduling apparatus 100, each reader control apparatus 200 has a reader connected to the reader control apparatus 200 among the records of the forced reading event generation condition DB 112. The system configuration may be such that a DB consisting only of those that match the reader ID 301 of 300 is stored in the storage device 203 and the tag reading event generation program 210 acquires conditions for generating an event as forced reading from the DB.

  The reading reader schedule DB 111 in FIG. 2 includes the current state 111c as a record field. However, when the tag 400 has an area where data can be read and written, the current state 111c is not held in the reading reader schedule DB 111, but the tag 400 May have a DB configuration in an area where data can be read and written.

  The forced read event generation condition DB 112 in FIG. 3 manages the forced read event generation time 112b for each reader ID 112a, but each reader ID reader 300 has read a tag 400 of each tag ID, That is, a DB configuration that manages the forced read event generation time 112b for each pair of reader ID and tag ID may be used. Alternatively, the forced read event generation time 112b for each combination in which the reader 300 of each reader ID reads the tag 400 of each tag ID in each current state, that is, each combination of the reader ID, the current state, and the tag ID. It may be a DB configuration for managing.

  In the flowchart of FIG. 8, all of the tag ID 401-reader ID 301 pairs received in S211 are set in the read reader schedule confirmation request 500, but among the pairs, those that can be referred to the tag read buffer 211 are read reader schedule confirmation. The request 500 may not be set. In the flowchart of FIG. 8, if the result of S213 is not OK, S215 is omitted and the process proceeds to S216. Further, in the flowchart of FIG. 8, S218 is omitted, and instead, in S212, the rows of the tag reading buffer 211 that are not included in the tag ID 401-reader ID 301 pair received in S211 are deleted.

  In the flowchart of FIG. 8, S219 is performed immediately before S220, but may be performed at any timing in the flowchart. Further, in FIG. 8, in S216, if the forced read event generation time 211d is 0 second, the event is directly generated as forced read without being added to the tag read buffer 211, and this is used for business. Also good.

  FIG. 9 is a state transition diagram showing a part of the state transition table of FIG. 2 (data with tag ID 111a of T56). Each state (current state 111c, next state 111b0b) is indicated by a circled node. The transition between the states is indicated by an arrow between the nodes, and the input for the state transition is the read permission reader ID 111b0a. For example, when the current state 111c is “state 0” and “R12” of the reader permission reader ID 111b0a is input, the state transitions to “state 1” of the next state 111b0b.

  Thus, when the tag ID 111a is input from the read permission reader ID 111b0a whose state changes, an event for notifying the tag ID 111a is generated. On the other hand, when the tag ID 111a is input from the reader ID 301 whose state does not change, an event for notifying the tag ID is not generated.

It is a block diagram which shows the system regarding one Embodiment of this invention. It is a block diagram which shows the reading reader | leader schedule DB regarding one Embodiment of this invention. It is a block diagram which shows forced reading event generation condition DB regarding one Embodiment of this invention. It is a block diagram which shows the tag reading buffer regarding one Embodiment of this invention. It is a flowchart which shows the reading reader | leader schedule confirmation process regarding one Embodiment of this invention. It is a block diagram which shows the reading reader | leader schedule confirmation request regarding one Embodiment of this invention. It is a block diagram which shows the reading reader | leader schedule confirmation request response regarding one Embodiment of this invention. It is a flowchart which shows the tag reading event generation process regarding one Embodiment of this invention. It is a state transition diagram which shows the reading reader schedule DB regarding one Embodiment of this invention.

Explanation of symbols

100 Reading Reader Schedule Device 110 Schedule Management Program 111 Reading Reader Schedule DB
112 Forced read event generation condition DB
200 Reader Control Device 210 Tag Reading Event Generation Program 211 Tag Reading Buffer 300 Reader 301 Reader ID
400 tag 401 tag ID
500 Reading reader schedule confirmation request 501 Reading reader schedule confirmation request response

Claims (10)

A tag notification method for notifying a tag ID read from a tag by a reader identified by a reader ID,
Computer
A specified schedule that defines a plurality of states related to tag reading and transitions between the states, and a procedure for storing the current state in the specified schedule in the storage means for each tag ID;
When the reader reads the tag, a tag input procedure for inputting the tag ID of the tag and the reader ID of the reader;
If the transition from the current state of the specified schedule related to the tag ID input in the tag input procedure matches the reader ID input in the tag input procedure, the current state is transitioned and tag ID notification is permitted. An event determination procedure;
An event notification procedure for notifying the tag ID permitted by the event determination procedure;
The tag notification method characterized by performing.   In the event determination procedure, the transition from the current state of the designated schedule related to the tag ID input in the tag input procedure matches the specified condition for the tag ID that does not match the reader ID input in the tag input procedure. The tag notification method according to claim 1, wherein notification of the tag ID is permitted.   The tag notification method according to claim 2, wherein the event determination procedure applies the specified condition set for each reader ID.   The tag notification method according to claim 2, wherein the event determination procedure applies the specified condition set for each pair of a reader ID and a tag ID.   3. The tag notification method according to claim 2, wherein the event determination procedure applies a combination of a reader ID and a tag ID and the designated condition set for each current state of the designated schedule.   6. The event determination procedure according to claim 2, wherein the specified condition for permitting notification of the tag ID is applied when the number of times the reader reads the tag is equal to or greater than the specified number. The tag notification method according to item 1.   6. The event determination procedure according to claim 2, wherein the specified condition for permitting notification of a tag ID is applied when a time for reading a tag by the reader is equal to or longer than a specified time. The tag notification method according to item 1.   A tag notification program for causing a computer to execute the tag notification method according to any one of claims 1 to 7. A tag notification device that notifies a tag ID read from a tag by a reader identified by a reader ID,
A designated schedule that defines a plurality of states related to tag reading and transitions between the states, and storage means for storing the current state in the designated schedule for each tag ID;
When the reader reads the tag, a tag input unit for inputting the tag ID of the tag and the reader ID of the reader;
If the transition from the current state of the specified schedule related to the tag ID input to the tag input unit matches the reader ID input to the tag input unit, the current state is transitioned and tag ID notification is permitted. An event determination unit;
An event notification unit for notifying the tag ID permitted by the event determination unit;
A tag notification device comprising:   A tag notification system according to claim 9, and a tag notification system comprising the tag and the reader.

Images