Reader, writer and method for programmable tags

• US 10,152,618 B2
• Filed: 12/14/2016
• Issued: 12/11/2018
• Est. Priority Date: 09/30/2013
• Status: Active Grant

• Current Assignee: Bibliotheca Limited (Bibliotheca Group GmbH)
• Original Assignee: Bibliotheca Limited (Bibliotheca Group GmbH)
• Inventors: Chadbourne, Andrew
• Primary Examiner(s): HOLLOWAY III, EDWIN C
• Application Number:
  US15/378,496
• Publication Number:
  US 20170103238A1
• Time in Patent Office: 727 Days
• Field of Search: 340 1051
• CPC Class Codes: G06K 19/073 Special arrangements for circuits, e.g. for protecting identification code in memory protection against unauthorised use of computer memory G06F12/14
• CPC Class Codes: G06K 7/10257 arrangements for protecting the interrogation against piracy attacks computer security in general G06F21/00; jamming of communication, countermeasures H04K3/00; secret communication H04K1/00
• CPC Class Codes: G06K 7/10297 arrangements for handling protocols designed for non-contact record carriers such as RFIDs NFCs, e.g. ISO/IEC 14443 and 18092 cryptographic protocols H04L9/00; network security protocols H04L63/00; real-time communication protocols in data switching networks H04L65/00; network protocols for data switching network services H04L67/00
• CPC Class Codes: G06K 7/10366 the interrogation device being adapted for miscellaneous applications

Abstract

A tag writer, reader and method are disclosed. The tag writer is operable to generate a security identifier during writing of data to the tag, the security identifier being dependent on one or more of the data written, data already on the tag, metadata associated with the data, the tag and/or the writing of the data.

Claims

1. A tag security system comprising:

a tag writer, a tag reader, a programmable tag and a remote data repository, the programmable tag having a unique identifier, the tag writer being configured to generate a security identifier during writing of data to the tag, the security identifier being dependent on one or more of the data written, data already on the tag, metadata associated with the data, the tag and/or the writing of the data, wherein the tag writer is further configured to write the security identifier to the remote data repository, the tag writer being configured to link the security identifier in the remote data repository to the unique identifier, the tag reader being configured to recreate the security identifier during reading of data from the tag, wherein the tag reader is configured to use the unique identifier to verify the security identifier against the security identifier in the remote data repository, the security identifier further being non-recreatable upon changing of predetermined portions of data in the tag.

2. The tag security system of claim 1, wherein the security identifier is a selected one of a checksum, hash or encrypted digest.

3. The tag security system of claim 1, wherein the security identifier is derived from security status data held by the tag and/or content of a user memory area of the tag.

4. The tag security system of claim 1, wherein at least a part of the security identifier is written integrally to the data on the tag, wherein reprogramming of the tag changes or deletes the security identifier.

5. The tag security system of claim 1, wherein the unique identifier is physically written on one or more of the tag and its packaging and is obtained from the tag and/or packaging for writing of the security identifier to the remote repository.

6. The tag security system of claim 1, wherein the tag writer is further arranged to write data to a backup data repository, the data being data on the tag from which the security identifier is derived.

7. The tag security system of claim 6, wherein upon the recreated security identifier not matching the security identifier in the remote data repository, the tag security system being configured to overwrite data in the tag from data in the backup data repository.

8. The tag security system of claim 1, wherein the tag writer is configured to use a subset of data on the tag to generate the security identifier.

9. The tag security system of claim 8, wherein a pattern to determine the subset is encoded for the tag in a remote data repository, the tag writer being configured to retrieve the pattern and use it to determine the subset.

10. The tag security system of claim 1, wherein the tag is an RFID tag.

11. The tag security system of claim 1, wherein the tag reader is configured to use the unique identifier to retrieve the previously calculated security identifier from a remote data repository.

12. The tag security system of claim 1, wherein the tag reader is configured to communicate the recreated security identifier and the unique identifier to the remote data repository, the remote data repository being configured to compare the security identifier in the remote data repository with the recreated security identifier and return a verification result.

13. The tag security system of claim 1, wherein the tag reader is configured to recreate the security identifier by communicating data read from the tag to the remote data repository with the unique identifier, the remote data repository being configured to recreate the security identifier from the received data, compare the security identifier in the remote data repository with the recreated security identifier and return a verification result.

14. The tag security system of claim 1, wherein upon the recreated security identifier not matching the security identifier in the remote data repository, the tag security system being configured to overwrite data in the tag with default values in a backup data repository.

15. A method for securing a programmable tag, the programmable tag having a unique identifier, the method comprising:

generating a security identifier during writing of data to the tag, the security identifier being dependent on one or more of the data written, data already on the tag, metadata associated with the data, the tag and/or the writing of the data;

storing the security identifier in a remote data repository for future authentication of the tag and security identifier;

linking the security identifier in the remote data repository to the unique identifier of the tag; and

subsequently authenticating the data on the tag by recreating the security identifier from data on the tag and comparing the recreated security identifier to the stored security identifier in the remote data repository using the unique identifier, wherein the security identifier is non-recreatable upon changing of predetermined portions of the data in the tag.

16. The method of claim 15, further comprising deriving the security identifier from security status data held by the tag and/or content of a user memory area of the tag.

17. The method of claim 15, further comprising writing at least a part of the security identifier integrally to the data on the tag, whereby reprogramming of the tag changes or deletes the security identifier.

18. The method of claim 15, wherein the unique identifier is physically written on one or more of the tag and its packaging, the method further comprising obtaining the unique identifier from the tag and/or packaging for writing of the security identifier to the remote repository.