RFID mutual authentication verification session

• US 7,450,010 B1
• Filed: 04/17/2006
• Issued: 11/11/2008
• Est. Priority Date: 04/17/2006
• Status: Active Grant

• Current Assignee: Amtech Systems LLC (Roper Technologies, Inc.)
• Original Assignee: TC License Limited
• Inventors: Gravelle, Kelly, Scott, Dale L., Tan, Zhenping
• Primary Examiner(s): Swarthout; Brent
• Application Number:
  US11/405,011
• Time in Patent Office: 939 Days
• Field of Search: 340/505, 340/572.1, 340/572.4, 340/5.2, 340/5.26, 340/5.21, 340/5.8, 340/5.85, 340/10.1, 340/10.3, 340/728, 340/5.61, 702/182, 455/67.7, 380/270, 235/436
• US Class Current: 340/572.1
• CPC Class Codes: G06F 21/606 by securing the transmission between two devices or processes
• CPC Class Codes: G06K 7/0008 General problems related to the reading of electronic memory record carriers, independent of its reading method, e.g. power transfer
• CPC Class Codes: H04L 63/0442 wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 63/0492 by using a location-limited connection, e.g. near-field communication or limited proximity of entities
• CPC Class Codes: H04L 63/0869 for achieving mutual authentication cryptographic mechanisms or cryptographic arrangements for mutual authentication H04L9/3273
• CPC Class Codes: H04L 9/3271 using challenge-response
• CPC Class Codes: H04L 9/3273 for mutual authentication network architectures or network communication protocols for achieving mutual authentication in a packet data network H04L63/0869

Abstract

In a protocol for preserving the privacy of communications between a RFID reader and a RFID tag, two distinct actions are taken. First, the reader and the tag must be mutually authenticated as being authorized participants in the communications. After that process is successfully completed, the authenticity of each authorized participant must be validated prior to each subsequent communication between reader and tag.

Claims

1. A communications system comprising:

a radio frequency identification (RFID) tag comprising

a tag memory storing a private key and a tag identification (ID),

a tag random number generator for generating a first random number,

a tag authentication code generator, and

a tag processor for causing the tag ID to be transmitted; and

,

a RFID reader comprising

a reader random number generator for generating a second random number,

a reader memory storing private keys for tags and tag IDs, each private key associated with one of the tag IDs,

a reader processor for receiving the tag ID transmitted from the RFID tag and retrieving from said reader memory the tag private key associated with the received tag ID,

a reader authentication code generator for receiving the first random number, the second random number, and the retrieved tag private key, said reader authentication code generator generating a reader authentication code based on the private key, the first random number, and the second random number,

wherein said reader processor causes said reader authentication code to be transmitted to said tag;

wherein said tag authentication code generator further generates a reader authentication code based on the private key, the first random number, and the second random number, and said tag processor determines whether the reader is authentic based on a comparison of the reader authentication code transmitted by the reader and the reader authentication code generated by the tag authentication code generator.

2. The system according to claim 1, wherein said tag accepts communications from said reader if said tag processor determines that the reader is authentic.

3. The system according to claim 1, wherein said tag processor determines that the reader is authentic if the reader authentication code transmitted by the reader matches the reader authentication code generated by the tag authentication code generator.

4. The system according to claim 1, wherein said tag authentication code generator further generates a tag authentication code based on the private key, the first random number, and the second random number, and said tag processor causes said tag authentication code to be transmitted to said reader, and further wherein said reader authentication code generator generates a tag authentication code based on the private key, the first random number, and the second random number, and said reader processor determines whether the tag is authentic based on a comparison of the tag authentication code transmitted by the tag and the tag authentication code generated by the reader.

5. The system according to claim 4, wherein said reader accepts communications from said reader if said tag processor determines that the reader is authentic and said tag accepts communications from said reader if said reader processor determines that the tag is authentic.