Methods and systems for creating and exchanging a device specific blockchain for device authentication

Patent metadata

Field	Value
Publication number	US-10212145-B2
Application number	US-201615284103-A
Country	US
Kind code	B2
Filing date	Oct 3, 2016
Priority date	Apr 6, 2016
Publication date	Feb 19, 2019
Grant date	Feb 19, 2019

Abstract

Mobile devices and other devices used in transactions or interactions with other computer systems can be identified by an abstract composite of information unique to the device. For example, the device can record and store when a user first started the device (a date and time of first use), how the device is configured (including any hardware/software identifications, versions, install dates, time when configurations or installations occurred, etc.), etc. All of the information can be collected for a specified period of time (e.g., 30 minutes, 1 hour, etc.), periodically, or continually. This process yields a large collection of data, which can be condensed (a record before condensing the data may be approximately 10 to 50 MB). The data may then be encapsulated in a blockchain. At least a portion of the blockchain may then be exchanged to identify the device.

First claim

What is claimed is:

1. A method for authenticating a service, the method comprising:
activating a device;
in response to activating the device, generating a blockchain;
the device executing a first event;
in response to activating the device and executing the first event, storing a first block in the blockchain, wherein the first block describes the first event associated with activating the device;
the device executing a second event;
storing a second block associated with the second event occurring with the device;
the device executing a third event;
storing a third block associated with the third event occurring with the device, wherein the first, second, and third blocks in the blockchain are associated with events that occur only on the device, wherein the blockchain is an abstract composite of information unique to the device;
the device identifying a user using the device;
the device establishing a binding is active and associated with the user;
establishing an interaction with a second computer system;
the device sending an indication of the binding to the second computer system; and
with the binding active, providing at least a portion of the blockchain during the interaction to secure the interaction, wherein the portion of the blockchain uniquely identifies the device to the second computer system.

2. The method according to claim 1 , wherein the portion of the blockchain is a tuple.

3. The method according to claim 2 , wherein each block includes an identifier, data, and a timestamp.

4. The method according to claim 3 , wherein the second and third event occur after the first event.

5. The method according to claim 4 , wherein the second block includes a reference to the first block.

6. The method according to claim 5 , wherein the blockchain is periodically updated.

7. The method according to claim 5 , wherein the activating of the device is a first activation of the device.

8. The method according to claim 1 , wherein, when the user is no longer using the device, the device deactivates the binding with the user that was using the device.

9. The method according to claim 8 , wherein the portion of the blockchain is provided to the second computer system only if the binding is active.

10. The method according to claim 1 , wherein the second computer system:
storing the blockchain;
verifying the portion of the blockchain provided by the device with the stored blockchain;
generating a second blockchain; and
providing at least a second portion of the second blockchain during the interaction to secure the interaction, wherein the second portion of the second blockchain uniquely identifies the second computer system to the device.

11. A device in communication with a second computer system, the device comprising:
a memory;
a processor in communication with the memory, the processor adapted to:
identify a user using the device;
establish that a binding is active while the user is using the device;
establish an interaction with the second computer system;
send an indication of the binding to the second computer system;
while the binding is active, send a tuple, formed from at least a portion of a blockchain, to the second computer system, wherein the at least a portion of the blockchain uniquely identifies the device to the second computer system, wherein all blocks in the blockchain are associated with events that occur only on the device and created from events occurring with the device, wherein the second computer system verifies that the tuple is associated with the blockchain, wherein the interaction is secured when the tuple is verified; and
conducting the secure interaction.

12. The system of claim 11 , wherein the secure interaction continues while the binding is active.

13. The system of claim 11 , wherein the binding is discontinued, and wherein the processor sends a second indication to the second computer system that the binding is inactive.

14. The system according to claim 13 , wherein the secure interaction is stopped based on the second indication.

15. The system according to claim 11 , wherein the processor provides an instance of the blockchain to a third party computer system, wherein the second computer system provides the tuple to the third party computer system to verify the tuple.

16. A non-transitory computer readable medium having stored thereon instructions that cause a processor to execute a method, the method comprising:
communicating with a device;
receiving an indication of a binding between the device and a user is active;
while the binding is active, receiving a tuple formed from at least a first portion of a blockchain and at least a second portion of a sidechain, wherein the at least a first and at least a second portions uniquely identify the device wherein all blocks in the blockchain are associated with events that occur only on the device;
verifying that the tuple is associated with the blockchain and the sidechain, wherein the interaction is secured when the tuple is verified; and
conducting the secure interaction.

17. The computer readable medium of claim 16 , wherein the sidechain describes events associated with previous interactions with the user.

18. The computer readable medium of claim 16 , the method further comprising:
receiving the blockchain;
generating the sidechain; and
providing the blockchain and the sidechain to a third party computer system.

19. The computer readable medium according to claim 18 , the method further comprising: providing the tuple to the third party computer system to verify the tuple.

20. The computer readable medium according to claim 19 , wherein the binding is discontinued, and wherein the method further comprising:
receiving a second indication that the binding is inactive; and
stopping the secure interaction based on the second indication.

Assignees

• Avaya Inc

Inventors

• Chavez David
• Philonenko Laurent

Classifications

• H04L63/08 Primary

  for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title

• H04L63/1466

  Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks · CPC title

• H04L9/3239

  involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD · CPC title

• H04L63/123

  received data contents, e.g. message integrity · CPC title

• H04W12/10

  Integrity · CPC title