Systems and methods for location-based automated authentication

• US 9,922,473 B1
• Filed: 01/23/2017
• Issued: 03/20/2018
• Est. Priority Date: 01/23/2017
• Status: Active Grant

• Current Assignee: UScontracting, Inc.
• Original Assignee: UScontracting, Inc.
• Inventors: Haworth, William Frederick, Maynard, Kevin Austin, Kidwell, Jeffrey Brader
• Primary Examiner(s): Pendleton, Dionne H
• Application Number:
  US15/412,321
• Time in Patent Office: 421 Days
• CPC Class Codes: G06F 21/35 communicating wirelessly
• CPC Class Codes: G06F 21/44 Program or device authentication
• CPC Class Codes: G06F 2221/2151 Time stamp
• CPC Class Codes: G06Q 20/3224 Transactions dependent on location of M-devices
• CPC Class Codes: G06Q 20/327 Short range or proximity payments by means of M-devices
• CPC Class Codes: G06Q 20/363 with the personal data of a user
• CPC Class Codes: G06Q 20/38215 Use of certificates or encrypted proofs of transaction rights
• CPC Class Codes: G06Q 20/4015 using location information
• CPC Class Codes: G07B 15/063 using wireless information transmission between the vehicle and a fixed station identification of vehicles G08G
• CPC Class Codes: G07C 2009/00317 keyless data carrier having only one limited data transmission range
• CPC Class Codes: G07C 2009/00412 the transmitted data signal being encrypted
• CPC Class Codes: G07C 9/00309 operated with bidirectional data transmission between data carrier and locks
• CPC Class Codes: G07C 9/21 having a variable access code
• CPC Class Codes: G07C 9/215 the system having a variable access-code, e.g. varied as a function of time
• CPC Class Codes: G07C 9/27 with central registration
• CPC Class Codes: H04H 60/91 Mobile communication networks for accessing the Internet H04H60/85
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• 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/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/0861 using biometrical features, e.g. fingerprint, retina-scan cryptographic mechanisms or cryptographic arrangements for entity authentication using biological data H04L9/3231
• CPC Class Codes: H04L 67/53 : using third party service providers
• CPC Class Codes: H04W 12/037 : of the control plane, e.g. signalling traffic
• CPC Class Codes: H04W 12/068 : using credential vaults, e.g. password manager applications or one time password [OTP] applications
• CPC Class Codes: H04W 4/80 : Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
• CPC Class Codes: H04W 92/045 : between access point and backbone network device
• CPC Class Codes: H04W 92/10 : between terminal device and access point, i.e. wireless air interface

Abstract

Systems and methods for location-based automated authentication are disclosed. A system comprises a mobile device, a sensor and a backend platform. The sensor and the backend platform is in network communication. The mobile device is operable to continuously transmit Bluetooth Low Energy (BLE) signals comprising encrypted transitory identifiers. The sensor is operable to receive a BLE signal from the mobile device when the mobile device is within a predetermined range, and communicate over a network connection the encrypted transitory identifier comprised in the BLE signal to the backend platform. The backend platform is operable to extract a unique identifier and a changing encrypted identifier from the received encrypted transitory identifier, generate a changing encrypted identifier, and validate a user identification by comparing the generated changing encrypted identifier and the extracted encrypted transitory identifier.

Claims

1. A system for location-based automated authentication, comprising:

a user device, a sensor and a backend platform;

wherein the sensor and the backend platform are in network communication;

wherein the user device is operable to construct a Bluetooth Low Energy (BLE) signal through;

constructing a unique value based on an original account timestamp, a changing time interval, and a current timestamp;

encrypting the unique value with a unique encryption key and compressing the encrypted unique value to derive a changing encrypted identifier, wherein the changing encrypted identifier changes based on the changing time interval;

combining the changing encrypted identifier with a unique identifier to form an encrypted transitory identifier;

packaging the encrypted transitory identifier into the BLE signal;

wherein the user device is operable to continuously transmit the BLE signal comprising the encrypted transitory identifier;

wherein the sensor is operable to receive the BLE signal from the user device when the user device is within a predetermined range, and transmit the encrypted transitory identifier comprised in the BLE signal to the backend platform;

wherein the backend platform is operable to;

extract the unique identifier and the changing encrypted identifier from the received encrypted transitory identifier;

retrieve user identification parameters based on the unique identifier, wherein the user identification parameters include the original account timestamp, the changing time interval, the current timestamp, and the unique encryption key;

construct a second unique value based on the user identification parameters;

encrypt the second unique value with the unique encryption key and compress the encrypted second unique value to derive a second changing encrypted identifier;

validate a user identification by comparing the second changing encrypted identifier and the extracted changing encrypted identifier;

charge a user account according to a predefined amount upon validating the user identification; and

generate and store a log of charges and send a charge notification to the user device.

2. The system of claim 1, wherein the user device is further operable to download and activate an application program and send the user identification parameters to the backend platform through the application program.

3. The system of claim 2, wherein the backend platform is further operable to store the user identification parameters in the user account.

4. The system of claim 2, wherein the user identification parameters further comprise at least one from the group consisting of user names, phone numbers, work identification numbers, member identification numbers, financial account information, billing information and other personal information.

5. The system of claim 1, wherein the predetermined range is defined based on a signal strength threshold.

6. The system of claim 1, wherein the user device and the backend platform have the same algorithm for generating the changing encrypted identifier and the second changing encrypted identifier.

7. The system of claim 1, wherein the user identification is validated when the second changing encrypted identifier and the extracted changing encrypted identifier match.

8. The system of claim 7, wherein the backend platform is further operable to execute an action when the user identification is validated.

9. The system of claim 1, wherein the backend platform is further operable to send a notification to the sensor regarding a validation result.

10. The system of claim 9, wherein the user device is further operable to receive the notification from the backend platform.

11. A method for location-based automated authentication, comprising:

a user device constructing a unique value based on an original account timestamp, a changing time interval, and a current timestamp;

the user device encrypting the unique value with a unique encryption key and compressing the encrypted unique value to derive a changing encrypted identifier, wherein the changing encrypted identifier changes based on the changing time interval;

the user device combining the changing encrypted identifier with a unique identifier to form an encrypted transitory identifier;

the user device packaging the encrypted transitory identifier into a Bluetooth Low Energy (BLE) signal;

the user device continuously transmitting the BLE signal;

a sensor receiving the BLE signal when the user device is within a predetermined range;

the sensor communicating the encrypted transitory identifier comprised in the BLE signal to a backend platform via network communication;

the backend platform receiving the encrypted transitory identifier;

the backend platform extracting the unique identifier and the changing encrypted identifier from the received encrypted transitory identifier;

the backend platform retrieving user identification parameters based on the unique identifier, including the original account timestamp, the changing time interval, the current timestamp, and the unique encryption key and constructing a second unique value based on the user identification parameters;

the backend platform encrypting the second unique value with the unique encryption key and compressing the encrypted second unique value to derive a second changing encrypted identifier;

the backend platform validating a user identification by comparing the second changing encrypted identifier and the extracted changing encrypted identifier; and

the backend platform providing a visual indication of a successful validation or an unsuccessful validation.

12. The method of claim 11, further comprising the user device downloading and activating an application program and sending the user identification parameters to the backend platform through the application program.

13. The method of claim 12, further comprising the backend platform storing the user identification parameters in a user account.

14. The method of claim 11, further comprising the backend platform executing an action when the second changing encrypted identifier and the extracted changing encrypted identifier match.

15. The method of claim 11, further comprising the backend platform sending a notification to the sensor regarding a result of the validation, and the user device receiving the notification from the backend platform.