JP4550695B2 - RFID tag reader control device and RFID tag reader control program - Google Patents

Description

  The present invention provides an RFID tag reader control device that functions as an interface between a computer that performs business processing using data of a plurality of RFID tags read by an RFID (Radio Frequency Identification) tag reader and the RFID tag reader, and controls the RFID tag reader in the computer. The present invention relates to an RFID tag reader control program for realizing functions as a device.

  For example, in the field of retail distribution, each product is given a barcode with a JAN (Japanese Article Number) code, which is a product identification code, and the barcodes of the products handled at retail stores, store management headquarters, wholesale stores, etc. It is widely practiced to manage product information by reading the information with a bar code reader and inputting it to a computer. On the other hand, in recent years, an IC chip having a unique ID set and stored as a tag identifier and an antenna are used, and contactless communication is performed wirelessly with a reader / writer, thereby enabling ID reading or arbitrary A wireless data carrier capable of writing and reading information, so-called RFID tags, has attracted attention.

  There is a problem that the barcode is inefficient because it cannot be read unless it is scanned one by one with a barcode reader. In contrast, an RFID tag uses an anti-collision (collision prevention) method for communication control with a reader / writer, so that even if a plurality of RFID tags exist within a communicable range of one reader / writer. Since data can be read in a batch, it is efficient. Therefore, each product is attached with an RFID tag in which the JAN code of the product is written, and the data of the RFID tag attached to the product handled at each base is collectively read by an RFID tag reader and input to a computer, It is desired to build a mechanism for managing information on products handled.

  Conventionally, a technology has been known in which both systems are used in combination during a transition from a barcode-based merchandise management system to a RFID tag merchandise management system so that merchandise management can be performed smoothly (see, for example, Patent Document 1).

Note that the RFID tag is also referred to as a non-contact IC card, a wireless tag, an IC tag, a transponder, or the like, but is unified with the RFID tag in this specification. The reader / writer is also unified as an RFID tag reader.
Japanese Patent Laid-Open No. 11-096463

  FIG. 14 is a schematic configuration diagram for realizing a conventional merchandise management system using a barcode. A barcode reader 2 is connected to a computer 1. The computer 1 includes a controller 3 as a main control unit, a storage unit 4 for storing various programs and data processed by the controller 3, a communication interface 5 with external devices or peripheral devices, a bar code reader 2 and a driver 6 as a reader control device for controlling 2. The storage unit 4 is implemented with application programs for processing various operations executed by the computer 1 using a JAN code obtained from a barcode, such as sales product registration business, incoming product inspection business, stock product inventory business, and the like. ing.

  When shifting from such a system using a barcode to a system using an RFID tag, the RFID tag reader is simply connected to the computer 1 instead of the barcode reader 2 in terms of hardware. Change to a compatible one.

  However, in this case, the data of a plurality of RFID tags that are collectively read by the RFID tag reader are sent as a group to the controller 3 from the driver. Therefore, the controller 3 uses the RFID tag data group received from the driver as an RFID tag. It is required to divide every item and repeatedly execute necessary business processing for the divided RFID tag data. That is, the application program developed corresponding to the barcode data is created on the assumption that the data is input to the controller 3 one by one, but in order to develop the application program corresponding to the RFID tag data. Has to be created on the premise that a plurality of data are input to the controller 3 at the same time, and there is a problem that the development cost increases due to a large amount of program modification.

  The present invention has been made based on such circumstances, and the purpose of the present invention is to reduce the amount of modification from an application program corresponding to barcode data to an application program corresponding to RFID tag data. It is an object of the present invention to provide an RFID tag reader control device and an RFID tag reader control program that can reduce such costs.

The RFID tag reader control device of the present invention specifies an RFID tag reader capable of reading data from a plurality of RFID tags at once by using an anti-collision method for communication control with the RFID tag, and a product to which the RFID tag is attached. And a data buffer capable of storing data relating to a plurality of RFID tags, and data of a plurality of RFID tags read together by an RFID tag reader. Tag data dividing means that divides every RFID tag, RFID tag data divided for each RFID tag by the tag data dividing means, a tag identifier preset for the RFID tag, such as an ID, and a product to which the RFID tag is attached Product identification code for identifying And RFID data acquisition means for acquiring a data writing means for writing in the data buffer in association with the tag ID and item identification code obtained by the RFID data acquisition means, associated with the data buffer the tag identifier product identification code storage Then, one of the product identification codes is supplied to the controller, and the data supply means for supplying the next one product identification code to the controller in response to receiving a supply completion instruction for the supplied data from the controller. It is equipped with.

The RFID tag reader control program of the present invention connects an RFID tag reader capable of reading data from a plurality of RFID tags by using an anti-collision method for communication control with an RFID tag, and processes a business using a product identification code. A function that divides the data of a plurality of RFID tags that are collectively read by an RFID tag reader into a computer on which the application program is installed and the RFID tag data that is divided for each RFID tag is preset in the RFID tag. A function for acquiring a tag identifier, for example, an ID, and a product identification code, for example, a JAN code, for specifying a product to which the RFID tag is attached, and the tag identifier of the acquired RFID tag and the product identification code are associated with each other It is stored in the data buffer Te Ability and, when associated with a tag identifier in the data buffer is the product identification code is stored handed one product identification code therein to the application program, subsequently, that it has received a receipt completion instruction Delivered data from the application program Accordingly, the function of delivering the next one product identification code to the application program is realized.

  According to the present invention in which such a measure is taken, it is possible to reduce the amount of remodeling from an application program corresponding to barcode data to an application program corresponding to RFID tag data, thereby reducing the cost of program development.

Hereinafter, the best mode for carrying out the present invention will be described.
In this embodiment, the present invention is applied to a merchandise sales registration apparatus in a retail store.

  FIG. 1 is a schematic configuration diagram showing a merchandise sales registration apparatus according to the present embodiment. An RFID tag reader 12 is connected to a POS terminal 11 mainly composed of a computer. The POS terminal 11 includes a controller 13 as a main control unit, a storage unit 14 for storing various programs and data processed by the controller 13, a communication interface 15 with an external device such as a store controller, an RFID, It comprises a driver 16 as a reader control device for controlling the tag reader 12, a data temporary storage buffer 17 used by the driver 16, and peripheral devices such as a keyboard 18, a touch panel 19, and a printer 20.

  The storage unit 14 is loaded with an application program for realizing various business processes executed by the POS terminal 11 using the RFID tag data. Further, as shown in FIG. 2, in correspondence with the JAN code as a product identification code for identifying each product, a JAN file 21 in which product information such as the product name and sales price of the product is set in advance is stored in the storage unit 14. Is stored in memory.

  The RFID tag reader 12 is connected to a tag communication antenna 22, and communicates with the RFID tags 26, 27, and 28 provided in the respective products 23, 24, and 25 via the tag communication antenna 22 in a contactless manner. To read the data in the IC chip memory of each RFID tag 26, 27, 28.

  More specifically, the RFID tag reader 12 includes an interface unit with the POS terminal 11, a control unit, a modulation unit, and a demodulation unit. When the RFID tag read execution command is input from the POS terminal 11 via the interface unit, the control unit modulates the read execution command by the modulation unit and transmits the modulated radio wave from the tag communication antenna 22.

  Each RFID tag 26, 27, 28 includes a loop coil antenna and an IC chip. A non-volatile memory is mounted on the IC chip. The data structure of this memory is shown in FIG. As shown in the figure, in the memory of each RFID tag 26, 27, 28, an ID as a tag identifier set at the time of RFID tag manufacture is fixedly stored. In addition, a user data area in which data can be arbitrarily written by the user is secured. In the present embodiment, each RFID tag 26, 27, 28 has a JAN, which is an identification code of the product 23, 24, 25 attached thereto. The code is at least written and saved.

  Thus, the RFID tags 26, 27, and 28 existing within the communicable range of the tag communication antenna 22 generate power in response to receiving the modulated radio wave of the read execution command by the loop coil antenna, and the ID in the memory. The user area data is modulated and radio waves are transmitted from the loop coil antenna. When the radio wave is received by the tag communication antenna 22, the control unit of the RFID tag reader 12 demodulates the received radio wave by the demodulation unit, and interfaces the demodulated RFID tag data, that is, ID and user area data. Output to the POS terminal 11 via the unit.

  Here, in the present embodiment, a method called anti-collision (collision prevention) is used for communication control between the RFID tags 26, 27, and 28 and the RFID tag reader 12. As a result, when there are a plurality of RFID tags 26, 27, 28 within the communicable range of one RFID tag reader 12, the data of each RFID tag 26, 27, 28 is collectively collected by the RFID tag reader 12. It is read and output to the POS terminal 11. In the above example, three RFID tags are shown. However, when one, two, or four or more RFID tags exist within the communicable range of the RFID tag reader 12, no reading error occurs. As long as the data of these RFID tags is read at once.

  The RFID tag reader 12 and the controller 13 of the POS terminal 11 are connected via a driver 16. The driver 16 is installed with an RFID tag reader control program as middleware that provides an interface with the RFID tag reader 12. By the action of the RFID tag reader control program, the driver 16 performs an operation of storing data of one or more RFID tags read by the RFID tag reader 12 in the data temporary storage buffer 17. As shown in FIG. 4, the temporary data storage buffer 17 can store the ID of one RFID tag and the JAN code in association with a plurality of tags. In addition, a processed flag f for identifying whether or not the processing has been performed for each RFID tag ID and JAN code data related thereto is stored. The driver 16 sequentially reads JAN codes of unprocessed data from the temporary data storage buffer 17 and supplies them to the controller 13 by the action of the RFID tag reader control program.

  The operation of the driver 16 will be described in more detail with reference to the flowcharts of FIGS. This operation is realized by an RFID tag reader control program.

  That is, the driver 16 waits for a data acquisition instruction from the controller 13 as an initial state (FIG. 5, ST1). When there is a data acquisition instruction, the driver 16 initializes the data temporary storage buffer 17 (FIG. 5, ST2: buffer initialization means). Also, a confirmation loop process described later is started (FIG. 5, ST3).

  Next, the driver 16 transmits a read execution command to the RFID tag reader 12 (FIG. 5, ST4). As a result, the RFID tag reader 12 collectively reads RFID tag data consisting of the ID of the RFID tag and the user area data existing within the communicable range of the tag communication antenna 22. Then, all the RFID tag data read in a batch are input to the driver 16.

  Therefore, when the driver 16 confirms that the RFID tag data has been read and inputted by the RFID tag reader 12 (FIG. 5, ST5), the driver 16 divides all the RFID tag data read in a batch for each RFID tag (FIG. 5, ST6: Data dividing means). Then, an ID and a JAN code are extracted for each divided RFID tag data (FIG. 5, ST7: RFID data acquisition means).

  Next, the data temporary storage buffer 17 is searched with the ID extracted from one RFID tag data (FIG. 5, ST8), and it is determined whether or not the same ID is already stored (FIG. 5, ST9: determining means). ). If the same ID has already been stored, the extracted ID and JAN code are discarded (FIG. 5, ST11). If the same ID is not stored, the extracted ID and JAN code are stored in the data temporary storage buffer 17 together with unprocessed flag information (assuming f = 0) (FIG. 5, ST10: data writing means). ).

  Next, it is determined whether or not the above processing (ST8 to ST11 processing) has been executed for the IDs and JAN codes extracted from all the divided RFID tag data (FIG. 5, ST12). If an unexecuted ID and JAN code remain, the above processing (ST8 to ST11) is executed for the ID and JAN code.

  Thus, when all the RFID tag data collectively read by the RFID tag reader 12 is already stored in the temporary data storage buffer 17, the read RFID tag data is discarded and not stored. In this case, a process of sequentially storing the read RFID tag data ID and JAN code together with unprocessed flag information in the data temporary storage buffer 17 is executed. When this process is completed, the driver 16 determines whether or not there has been a data acquisition end instruction from the controller 13 (FIG. 5, ST13).

  If it is determined that there is no data acquisition end instruction, the driver 16 transmits a read execution command to the RFID tag reader 12 again (FIG. 5, ST4). Then, the subsequent processing (FIG. 5, ST5 to ST13) is executed again.

  On the other hand, if it is determined that there has been a data acquisition end instruction, the driver 16 stops the confirmation loop process (FIG. 5, ST14). Thus, the processing operation for the data acquisition instruction from the controller 13 is completed.

  Further, when the confirmation loop process is activated, the driver 16 searches whether or not the unprocessed (f = 0) ID and the data of the JAN code associated therewith are stored in the data temporary storage buffer 17 (FIG. 6, ST21). When it is detected that unprocessed data is stored (FIG. 6, ST22), the driver 16 takes out the unprocessed data with the earliest storage order from the data temporary storage buffer 17 (FIG. 6, ST23). At this time, the flag f of the RFID tag data is updated to have been processed (f = 1) (FIG. 6, ST24).

  Next, the driver 16 extracts the JAN code of the data taken out from the temporary data storage buffer 17 and supplies this JAN code to the controller 13 (FIG. 6, ST25: data supply means). Thereafter, the driver 16 waits for a receipt confirmation instruction from the controller 13 (FIG. 6, ST26). If the receipt confirmation instruction is received, the driver 16 again searches whether or not unprocessed data is stored in the temporary data storage buffer 17 (FIG. 6, ST21). When it is detected that the data is stored (FIG. 6, ST22), the above processing (FIG. 6, ST23 to ST26) is executed again.

  In this way, the driver 16 does not supply a plurality of RFID tag data collectively read by the RFID tag reader 12 to the controller 13 as it is, but divides the RFID tag data for each RFID tag and further extracts the ID and JAN code to obtain data. Temporary storage is performed in the temporary storage buffer 17. The JAN code stored in the buffer 17 is extracted one by one in order and supplied to the controller 13.

  Therefore, in the POS terminal 11 including the driver 16 having such a function, the JAN code is sequentially supplied from the driver 16 to the controller 13 one by one. Therefore, the structure of the application program using the RFID tag data is as follows. Basically, there is no difference from the structure of a conventional application program that uses barcode data.

As an example of this type of application program, the structure of an application program for realizing the registration work process will be described with reference to the flowchart of FIG.
When the start of registration work is declared by the mode key operation of the keyboard 18 or the menu screen touch operation of the touch panel 19, this application program is activated. Thereby, the controller 13 first displays a product sales registration screen 30 having a layout as shown in FIG. 9 on the touch panel 19 (FIG. 7, ST31). The product sales registration screen 30 includes a detail column 31 for displaying registered product detail information such as JAN code, product name, quantity, and price, a total column 32 for displaying the total amount including tax, and a current key. 33, a batch cancel key 34 and a cancel registration key 35 are displayed. The current total key 33 functions as a closing key for declaring registration closing of one commercial transaction. The batch cancellation key 34 functions as a key for declaring batch cancellation of one commercial transaction. The cancellation registration key 35 functions as a key for declaring designated cancellation of a product registered as one transaction.

  Next, the controller 13 waits for a registration start trigger for one commercial transaction to be input (FIG. 7, ST32). For example, when a registration start trigger is input by operating a registration start declaration key on the keyboard 18, the controller 13 gives an instruction to acquire RFID tag data to the driver 16 (FIG. 7, ST33). As a result, when the RFID tag reader 12 reads the RFID tag data all at once, the driver 16 is supplied with the JAN code of the RFID tag data stored in the data temporary storage buffer 17 first. 13 waits for the JAN code to be input (FIG. 7, ST34).

  When the JAN code is input, the controller 13 executes merchandise sales registration processing using the JAN code. That is, the JAN file 21 is searched with the input JAN code, and product information such as product name and sales price is acquired (FIG. 7, ST35). Next, the JAN code, product information such as product name and sales price, and quantity = 1 are stored in the sales registration memory of the storage unit 14 (FIG. 7, ST36). At this time, if data with the same JAN code has already been stored, the quantity of the data is increased by +1. Next, the JAN code, product name, quantity and price (sales price × quantity) are displayed in the detail column 31 of the product sales registration screen 30 (FIG. 7, ST37).

  Thereafter, the controller 13 gives a receipt confirmation instruction to the driver 16 (FIG. 7, ST38). As a result, the driver 16 is supplied with the JAN code of the RFID tag data stored in the data temporary storage buffer 17 next, so that the controller 13 receives the JAN code and performs the above processing (FIG. 7, FIG. 7). Steps ST35 to ST38) are executed again.

  Further, when the controller 13 detects that any one of the touch keys 33, 34, and 35 on the merchandise sales registration screen 30 has been touched (FIG. 7, ST39), it gives an instruction to end the acquisition of RFID tag data to the driver 16. (FIG. 7, ST40).

  If the touch-operated key is the current key 33 (FIG. 7, NO in ST41 and YES in ST42), the controller 13 performs a transaction based on the product sales data stored in the sales registration memory. A tightening process is executed (FIG. 7, ST43). In this transaction closing process, the merchandise sales data stored in the sales registration memory is subjected to the sales registration process. Further, the print data of the purchase receipt is created, and the purchase receipt is printed and issued by the printer 20. Thereafter, the controller 13 clears the sales registration memory (ST44 in FIG. 7), and ends the registration work process for one commercial transaction.

  If the key is the collective cancellation key 34 (FIG. 7, NO in ST41 and NO in ST42), the controller 13 clears the sales registration memory (ST44 in FIG. 7), and performs registration work processing for one commercial transaction. Cancel.

On the other hand, when the touch-operated key is the cancel registration key 35 (FIG. 7, ST41 YES), the controller 13 executes the cancel registration process specifically shown in FIG.
First, for example, a layout cancellation registration screen 40 as shown in FIG. 10 is displayed on the touch panel 19 (FIG. 8, ST51). The cancellation registration screen 40 displays a detail column 41 for displaying canceled product detail information such as JAN code, product name, quantity, price, etc., and touch keys such as a confirmation key 42 and a cancel key 43. The confirmation key 42 functions as a key for declaring registration confirmation of the canceled product. The cancel key 43 functions as a key for declaring cancellation of registration of a canceled product.

  Next, the controller 13 waits for the cancellation start trigger to be input (FIG. 8, ST52). For example, when a cancel start trigger is input by operating a cancel start declaration key on the keyboard 18, the controller 13 gives an instruction to acquire RFID tag data to the driver 16 (FIG. 8, ST53). Thereby, the data temporary storage buffer 17 is once cleared. Next, when RFID tag data is collectively read by the RFID tag reader 12 from the driver 16, the JAN code of the RFID tag data stored in the data temporary storage buffer 17 is supplied first, so that the controller 13 Waits for a JAN code to be input (FIG. 8, ST54).

  When the JAN code is input, the controller 13 determines whether or not the JAN code is stored in the sales registration memory (FIG. 8, ST55). And when memorize | stored in sales registration memory, the controller 13 performs merchandise registration cancellation processing. That is, the JAN file 21 is searched with the input JAN code, and product information such as product name and sales price is acquired (FIG. 8, ST56). The JAN code, product name, product information such as sales price, and quantity = 1 are stored in the cancellation registration memory of the storage unit 14 (FIG. 8, ST57). At this time, if data with the same JAN code has already been stored, the quantity of the data is increased by +1. Further, the JAN code, product name, quantity and price (sales price × quantity) are displayed in the detail column 41 of the cancellation registration screen 40 (FIG. 8, ST58).

  Thereafter, the controller 13 gives a receipt confirmation instruction to the driver 16 (FIG. 8, ST59). As a result, the driver 16 is supplied with the JAN code of the RFID tag data stored in the data temporary storage buffer 17 next, so that the controller 13 receives the above-described processing (FIG. 8, FIG. 8). Steps ST55 to ST59) are executed again.

  If the input JAN code is not stored in the sales registration memory (FIG. 8, NO in ST55), the input of the JAN code is ignored. Then, the controller 13 gives a receipt confirmation instruction to the driver 16 (FIG. 8, ST59).

  Further, when the controller 13 detects that any one of the touch keys 42 and 43 on the cancellation registration screen G2 is touched (FIG. 8, ST60), it gives an instruction to end the acquisition of RFID tag data to the driver 16 (FIG. 8). , ST61).

  If the touch-operated key is the confirm key 42 (FIG. 8, YES in ST62), the controller 13 deletes the contents of the cancellation registration memory from the sales registration memory (FIG. 8, ST63). Thereafter, the cancellation registration memory is cleared (FIG. 8, ST64). If the screen of the touch panel 19 is returned to the merchandise sales registration screen 30 and the contents of the sales registration memory are displayed in the description column 31 (FIG. 8, ST65), it returns to the input standby state of the JAN code (FIG. 7, ST34).

  On the other hand, when the touched key is the cancel key 43 (FIG. 8, NO in ST62), the controller 13 clears the cancellation registration memory (FIG. 8, ST64). If the screen of the touch panel 19 is returned to the merchandise sales registration screen 30 and the contents of the sales registration memory are displayed in the description column 31 (FIG. 8, ST65), it returns to the input standby state of the JAN code (FIG. 7, ST34).

  In a retail store that uses the POS terminal 11 in which an application program having such a program structure is installed, the registration work process is executed in the following procedure. First, a merchandise sales registration screen 30 is displayed on the touch panel 19 as an initial state. Here, when the shopper comes to the cash register for accounting for the purchased product, the store clerk operating the POS terminal 11 puts the purchased product together on the scanner table in which the tag communication antenna 22 of the RFID tag reader 12 is embedded. . Then, the registration start declaration key on the keyboard 18 is operated.

  Then, the controller 13 gives an instruction to acquire RFID tag data to the driver 16. As a result, first, the temporary data storage buffer 17 is cleared. Next, a read execution command is transmitted to the RFID tag reader 12. As a result, the RFID tag reader 12 collectively reads the RFID tag data attached to each purchased product placed on the scanner base and inputs the data to the driver 16.

  In the driver 16, each RFID tag data is divided for each RFID tag, and its ID and JAN code are stored in the data temporary storage buffer 17. At this time, since the RFID tag data in which the same ID is already stored is discarded, the ID and JAN code of the same product are not stored in the data temporary storage buffer 17 in duplicate. Of course, if the same type of product is a different product, the ID of the attached RFID tag is different, so it is stored in the data temporary storage buffer 17 as separate data.

In the driver 16, only one JAN code stored earliest in the temporary data storage buffer 17 is given to the controller 13. As a result, the merchandise sales registration process using the JAN code is executed in the controller 13. When the merchandise sales registration process is executed, a receipt confirmation instruction is given to the driver 16. Waiting for this receipt confirmation instruction, the driver 16 gives only one JAN code stored next to the controller 13. After that
Each time a receipt confirmation instruction is given from the controller 13, the sequentially stored JAN codes are given to the controller 13 one by one, and merchandise sales registration processing using the JAN codes is executed.

  The store clerk compares the information displayed in the detail column 31 of the product sales registration screen 30 with the purchased product placed on the scanner stand, and confirms the completion of registration of the purchased product, and then touches the current key 33. . As a result, the controller 13 executes transaction closing processing based on the contents of the sales registration memory.

  If the customer offers to return all of the purchased products before that, the collective cancellation key 34 is touched. As a result, the sales registration memory is cleared in the controller 13.

  Further, when the customer offers to return a part of the purchased product, the cancel registration key 35 is touched. As a result, the screen of the touch panel 19 is switched to the cancellation registration screen 40, so that the store clerk once removes all the purchased products from the scanner table and then places the products to be returned on the scanner table again. Then, the cancel start declaration key on the keyboard 18 is operated.

  Then, the controller 13 gives an instruction to acquire RFID tag data to the driver 16. As a result, the data temporary storage buffer 17 is cleared. Next, a read execution command is transmitted to the RFID tag reader 12. As a result, the RFID tag reader 12 collectively reads the RFID tag data attached to each returned product placed on the scanner base and inputs the data to the driver 16.

  In the driver 16, each RFID tag data is divided for each RFID tag, and its ID and JAN code are stored in the data temporary storage buffer 17. At this time, since the RFID tag data in which the same ID is already stored is discarded, the ID and JAN code of the same product are not stored in the data temporary storage buffer 17 in duplicate. Of course, if the same type of product is a different product, the ID of the attached RFID tag is different, so it is stored in the data temporary storage buffer 17 as separate data.

  In the driver 16, only one JAN code stored earliest in the temporary data storage buffer 17 is given to the controller 13. As a result, the product registration cancellation process using the JAN code is executed in the controller 13. When the product registration cancellation process is executed, a receipt confirmation instruction is given to the driver 16. Waiting for this receipt confirmation instruction, the driver 16 gives only one JAN code stored next to the controller 13. Thereafter, each time a receipt confirmation instruction is given from the controller 13, the sequentially stored JAN codes are given to the controller 13 one by one, and the merchandise registration cancellation process using the JAN code is executed.

  The store clerk compares the information displayed in the detail column 41 of the cancellation registration screen 40 with the canceled product placed on the scanner stand, and confirms the registration completion of the canceled product, and then touches the confirmation key 42. As a result, the controller 13 deletes the contents of the cancellation registration memory from the sales registration memory. Thereafter, when the store clerk confirms that the purchase product has been registered, the store clerk touches the current total key 33. As a result, the controller 13 executes transaction closing processing based on the contents of the sales registration memory.

  Thus, according to the present embodiment, the structure of the application program is basically the same as that of an application program that uses existing barcode data. That is, even in an application program that uses existing barcode data, first, the driver 6 is instructed to acquire barcode data, and a JAN code that is one barcode data read by the barcode reader 2 is captured. Handle it. When the processing is completed, a data reception confirmation instruction is given to the driver 6, and when the next JAN code, which is the next bar code data, is fetched accordingly, this is processed.

  Therefore, according to the present embodiment, when an application program corresponding to RFID tag data is developed, one JAN code is stored in the controller 13 one by one as in the application program developed corresponding to barcode data. Since it is sufficient to make it based on the input, it is possible to reduce the amount of modification of the application program accompanying the transition from the barcode to the RFID tag. As a result, the cost associated with the development of the program can be greatly reduced, so that the transition from the barcode to the RFID tag can be performed smoothly.

The present invention is not limited to the above-described embodiment as it is, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage.
For example, in the above-described embodiment, the driver 16 divides a plurality of RFID tag data collectively read by the RFID tag reader 12 for each RFID tag, further extracts an ID and a JAN code, and temporarily stores them in the data temporary storage buffer 17. However, all user area data other than the ID and JAN code may be temporarily stored in the data temporary storage buffer 17.

  Moreover, although the case where the JAN code is included in the user area data of the RFID tag has been described in the above embodiment, the present invention can be implemented even when the JAN code is not included. Therefore, a second embodiment in which the JAN code is not included in the user area data of the RFID tag will be described next.

  FIG. 11 is a schematic configuration diagram showing a merchandise sales registration apparatus according to the second embodiment, and parts common to those in FIG. That is, the second embodiment is different from the first embodiment in that the driver 16 refers to the ID / JAN table 29.

  As shown in FIG. 12, the ID / JAN table 29 corresponds to the IDs of the RFID tags 26, 27, and 28 attached to the products 23, 24, and 25, respectively. A JAN code that is an identification code is preset and stored.

  In this configuration, the RFID tag reader control program is configured so that the driver 16 operates according to the procedure shown in the flowchart of FIG. In FIG. 13, the same processing steps as those in FIG.

  That is, the driver 16 waits for a data acquisition instruction from the controller 13 as an initial state (FIG. 13, ST1). When there is a data acquisition instruction, the driver 16 initializes the data temporary storage buffer 17 (FIG. 13, ST2: buffer initialization means). Moreover, the confirmation loop process shown in FIG. 6 is started (FIG. 13, ST3).

  Next, the driver 16 transmits a read execution command to the RFID tag reader 12 (FIG. 13, ST4). As a result, the RFID tag reader 12 collectively reads RFID tag data consisting of the ID of the RFID tag and the user area data existing within the communicable range of the tag communication antenna 22. Then, all the RFID tag data read in a batch are input to the driver 16.

  Therefore, when the driver 16 confirms that the RFID tag data has been read and input by the RFID tag reader 12 (FIG. 13, ST5), the driver 16 divides all the RFID tag data read in batches for each RFID tag (FIG. 13, ST6: Data dividing means). And ID is extracted for every divided | segmented RFID tag data (FIG. 13, ST70: RFID data acquisition means).

  Next, the data temporary storage buffer 17 is searched with the ID extracted from one RFID tag data (FIG. 13, ST8), and it is determined whether or not the same ID is already stored (FIG. 13, ST9: determining means). ). If the same ID is already stored, the extracted ID and JAN code are discarded (ST11 in FIG. 13). If the same ID is not stored, the ID / JAN table 29 is searched with the extracted ID, and the JAN code set corresponding to the ID is acquired (FIG. 13, ST71). Then, the ID and JAN code are stored in the data temporary storage buffer 17 together with unprocessed flag information (f = 0) (FIG. 13, ST10: data writing means).

  Next, it is determined whether or not the above-described processing (ST8, ST9, ST11 or ST8.ST9.ST71.ST10 processing) has been executed for the IDs extracted from all the divided RFID tag data (FIG. 13, ST12). ). If an unexecuted ID remains, the above process is executed for that ID.

  Thus, when all the RFID tag data collectively read by the RFID tag reader 12 is already stored in the temporary data storage buffer 17, the read RFID tag data is discarded and not stored. In such a case, the ID of the read RFID tag data and the JAN code set in the ID / JAN table 29 corresponding to the ID are sequentially stored in the data temporary storage buffer 17 together with unprocessed flag information. Execute. When this processing is completed, the driver 16 determines whether or not there has been a data acquisition end instruction from the controller 13 (FIG. 13, ST13).

  If it is determined that there is no data acquisition end instruction, the driver 16 transmits a read execution command to the RFID tag reader 12 again (FIG. 13, ST4). Then, the subsequent processing is executed again.

  On the other hand, if it is determined that there has been a data acquisition end instruction, the driver 16 stops the confirmation loop process (FIG. 13, ST14). Thus, the processing operation for the data acquisition instruction from the controller 13 is completed.

  Also in the second embodiment configured as described above, when the RFID tag data attached to each of a plurality of products is collectively read from the RFID tag reader 12, the driver 16 sends the data to the controller 13. Since the JAN code of the product is supplied one by one, the same function and effect as in the first embodiment can be achieved.

Needless to say, the product identification code is not limited to the JAN code.
In addition, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the embodiment. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, the constituent elements over different embodiments may be combined.

The block diagram which shows schematic structure of the goods sales registration apparatus which is the 1st Embodiment of this invention. The schematic diagram which shows the data structure of the JAN file memorize | stored in the memory | storage part of a POS terminal in the embodiment. 4 is a schematic diagram showing a data structure stored in a memory of the RFID tag in the embodiment. FIG. FIG. 3 is a schematic diagram showing a data structure of a temporary data storage buffer used by a driver in the embodiment. 4 is a flowchart showing a main procedure of RFID tag reader control processing executed by a driver in the embodiment. 4 is a flowchart showing the main procedure of confirmation loop processing executed by a driver in the embodiment. 4 is a flowchart showing a main procedure of registration work processing executed by a controller in the embodiment. FIG. 8 is a flowchart specifically illustrating a procedure of cancellation registration processing in FIG. 7. FIG. The top view which shows an example of a goods sales registration screen. The top view which shows an example of a cancellation | release registration screen. The block diagram which shows schematic structure of the merchandise sales registration apparatus which is the 2nd Embodiment of this invention. 4 is a schematic diagram showing a data structure of an ID / JAN table referred to by a driver in the embodiment. FIG. 4 is a flowchart showing a main procedure of RFID tag reader control processing executed by a driver in the embodiment. The schematic block diagram for implement | achieving the merchandise management system using the conventional barcode.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 11 ... POS terminal, 12 ... RFID tag reader, 13 ... Controller, 14 ... Memory | storage part, 15 ... Communication interface, 16 ... Driver, 17 ... Data temporary storage buffer, 18 ... Keyboard, 19 ... Touch panel, 20 ... Printer, 21 ... JAN File, 22 ... tag communication antenna, 26, 27, 28 ... RFID tag, 29 ... ID / JAN table.

Claims (8)

An RFID tag reader that can read data from a plurality of RFID tags by using an anti-collision method for communication control with an RFID (Radio Frequency Identification) tag, and product identification for specifying a product to which the RFID tag is attached In the RFID tag reader control device interposed between the controller for processing the code ,
A data buffer capable of storing data relating to a plurality of RFID tags;
Tag data dividing means for dividing data of a plurality of RFID tags collectively read by the RFID tag reader for each RFID tag;
Acquires said commodity identification code for identifying the commodity tag identifier and said RFID tag that is set in advance from the RFID tag data divided for each RFID tag in the RFID tag is attached by the tag data dividing means RFID data acquisition means for
Data writing means for associating the tag identifier obtained by the RFID data acquisition means with the product identification code and writing to the data buffer;
When a product identification code associated with a tag identifier is stored in the data buffer, one of the product identification codes is supplied to the controller, and thereafter, a received data reception completion instruction is received from the controller. In response, data supply means for supplying the next one product identification code to the controller;
An RFID tag reader control device comprising: 2. The RFID tag reader control device according to claim 1, wherein the data supply means attaches a processed flag to the product identification code supplied to the controller.   The apparatus further comprises a judging means for judging whether or not the tag identifier obtained by the RFID data obtaining means has already been written in the data buffer, and the data only when the tag identifier has not been written in the data buffer. 2. The RFID tag reader control device according to claim 1, wherein the writing means is operated.   4. The RFID tag reader control device according to claim 1, further comprising a buffer initialization unit that initializes the data buffer each time a data acquisition instruction is received from the controller. 5. When the RFID data acquisition unit acquires a tag identifier preset for the RFID tag from the RFID tag data divided for each RFID tag by the tag data division unit, the RFID data acquisition unit corresponds to the tag identifier of each RFID tag. 2. The RFID according to claim 1, wherein a product identification code set corresponding to the acquired tag identifier is acquired from a table in which a product identification code of a product with an RFID tag is set in advance. Tag reader control device. An anti-collision method is used for communication control with an RFID tag, and an RFID tag reader capable of reading data from a plurality of RFID tags at a time is connected, and an application program for processing a business using a product identification code is mounted on a computer. ,
A function of dividing data of a plurality of RFID tags collectively read by the RFID tag reader for each RFID tag;
A function of acquiring a tag identifier set in advance in the RFID tag and a product identification code for specifying a product to which the RFID tag is attached from RFID tag data divided for each RFID tag;
A function of associating the tag identifier of the acquired RFID tag and the product identification code and storing them in a data buffer ;
When a product identification code is stored in the data buffer in association with a tag identifier, one of the product identification codes is delivered to the application program, and thereafter an instruction to complete receipt of supplied data is received from the application program. According to the function of handing over the next one product identification code to the application program,
An RFID tag reader control program characterized by realizing the above. In the computer,
Determining whether a tag identifier acquired from RFID tag data is already stored in the data buffer, and further realizing a function of discarding the tag identifier to be stored when the tag identifier is already stored. The RFID tag reader control program according to claim 5. In the computer,
8. The RFID tag reader control program according to claim 5, further comprising a function of clearing the data buffer every time a data acquisition instruction is generated from the application program.

Images