Validation method and system for use in securing nomadic electronic transactions

• US 9,930,020 B2
• Filed: 04/25/2017
• Issued: 03/27/2018
• Est. Priority Date: 12/18/2008
• Status: Active Grant

• Current Assignee: BCE Incorporated
• Original Assignee: BCE Incorporated
• Inventors: Yeap, Tet Hin, O'Brien, William G, Murray, Sean MacLean
• Primary Examiner(s): HOLDER, BRADLEY W
• Application Number:
  US15/496,370
• Publication Number:
  US 20170228729A1
• Time in Patent Office: 336 Days
• CPC Class Codes: G06K 7/10366 the interrogation device being adapted for miscellaneous applications
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 20/3829 involving key management
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/4015 using location information
• CPC Class Codes: G06Q 20/4016 involving fraud or risk level assessment in transaction processing
• CPC Class Codes: G06Q 20/425 using two different networks, one for transaction and one for security confirmation
• CPC Class Codes: G06Q 2220/00 Business processing using cryptography postage metering system using cryptography G06Q2250/05
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 2209/805 Lightweight hardware, e.g. radio-frequency identification [RFID] or sensor
• 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 63/18 using different networks or channels, e.g. using out of band channels cryptographic mechanisms or cryptographic arrangements for key distribution involving distinctive intermediate devices or communication paths H04L9/0827; cryptographic mechanisms or cryptographic arrangements for authentication using a plurality of channels H04L9/3215
• CPC Class Codes: H04L 9/3215 using a plurality of channels network architectures or network communication protocols using different networks H04L63/18
• CPC Class Codes: H04L 9/3247 involving digital signatures
• CPC Class Codes: H04L 9/3271 using challenge-response

Abstract

A method involving a communication device, which comprises sending a request to a communication device; receiving a response from the communication device over a local communication path; deriving a received data set from said response; determining at least one data set that had been previously transmitted to the communication device over a wireless portion of a second communication path different from the local communication path; and validating the response based on the received data set and the at least one previously transmitted data set.

Claims

1. A method for bulk reading of a plurality of tags each associated with a respective item of a plurality of similar items, comprising:

by a tag reader with a hardware processor;

receiving a plurality of encrypted signatures, each of the received signatures comprising a common identifier common to the plurality of tags and a scrambling code unique to each tag;

receiving an index associated with each of the plurality of signatures indicative of how the respective scrambling codes were generated;

accessing a key database;

determining a decryption key for each of the plurality of signatures based on the index;

decrypting each of the plurality of signatures using the signature'"'"'s decryption key to obtain the encrypted signature'"'"'s common identifier and the scrambling code; and

validating each of the plurality of tags based on one or more of the common identifier and the scrambling code of the encrypted signature of a tag being validated,

wherein validating each of the plurality of tags comprises;

accessing a database to identify a record associated with the common identifier of the tag being validated, the database having one or more records stored thereon each associated with a respective common identifier and comprising zero or more previously determined scrambling codes for the respective common identifier; and

determining that the tag being validated is valid if the scrambling code for the tag has not been previously determined for the common identifier of the tag being validated, or

wherein validating each of the plurality of tags comprises;

accessing a database to identify a record associated with the common identifier of the tag being validated, the database having one or more records stored thereon each associated with a respective common identifier and comprising at least one valid scrambling code for the respective common identifier; and

determining that the tag being validated is valid if the scrambling code for the tag matches one of the at least one valid scrambling code for the common identifier of the tag being validated.

2. The method of claim 1, further comprising for each of the plurality of tags that are determined to be valid, performing an action associated with the tag determined to be valid.

3. The method of claim 1, wherein the signature'"'"'s determined decryption key is known in advance to receiving the plurality of encrypted signatures.

4. The method of claim 1, wherein the scrambling codes of the plurality of signatures dynamically change.

5. The method of claim 4, further comprising:

in response to an event at one of the plurality of tags, generating a second unique scrambling code;

augmenting the common identifier with the second unique scrambling code; and

encrypting the common identifier augmented with the second unique scrambling code using an encryption key to generate an updated encrypted signature.

6. The method of claim 5, wherein the event is any one or more of a read request, a completion of a pre-selected time period, or a received trigger.

7. The method of claim 5, wherein the second unique scrambling code is generated using one of an output of a pseudo-random generator, an output of a geo-location module, or a value measured by a clock module.

8. The method of claim 1, wherein the determined decryption key for each of the plurality of signatures based on the index is common to each of the plurality of signatures comprising the common identifier.

9. A tag reader for bulk reading of a plurality of tags each associated with a respective item of a plurality of similar items, comprising:

a hardware processor for executing instructions that configure the tag reader to;

receive a plurality of encrypted signatures, each of the received signatures comprising a common identifier common to the plurality of tags and a scrambling code unique to each tag;

receive an index associated with each of the plurality of signatures indicative of how the respective scrambling codes were generated;

access a key database;

determine a decryption key for each of the plurality of signatures based on the index;

decrypt each of the plurality of signatures using the signature'"'"'s decryption key to obtain the encrypted signature'"'"'s common identifier and the scrambling code; and

validate each of the plurality of tags based on one or more of the common identifier and the scrambling code of the encrypted signature of a tag being validated,

wherein, when validating each of the plurality of tags, the tag reader is further configured to;

access a database to identify a record associated with the common identifier of the tag being validated, the database having one or more records stored thereon each associated with a respective common identifier and comprising zero or more previously determined scrambling codes for the respective common identifier; and

determine that the tag being validated is valid if the scrambling code for the tag has not been previously determined for the common identifier of the tag being validated, or

wherein, when validating each of the plurality of tags, the tag reader is further configured to;

access a database to identify a record associated with the common identifier of the tag being validated, the database having one or more records stored thereon each associated with a respective common identifier and comprising at least one valid scrambling code for the respective common identifier; and

determine that the tag being validated is valid if the scrambling code for the tag matches one of the at least one valid scrambling code for the common identifier of the tag being validated.

10. The tag reader of claim 9, further configured to perform an action associated with the tag determined to be valid.

11. The tag reader of claim 9, wherein the signature'"'"'s determined decryption key is known in advance to receiving the plurality of encrypted signatures.

12. The tag reader of claim 9, wherein the determined decryption key for each of the plurality of signatures based on the index is common to each of the plurality of signatures comprising the common identifier.