Systems and methods for recognizing a device

• US 10,334,062 B2
• Filed: 02/25/2016
• Issued: 06/25/2019
• Est. Priority Date: 02/25/2016
• Status: Active Grant

• Current Assignee: Accertify, Inc. (American Express Company)
• Original Assignee: InAuth, Inc. (American Express Company)
• Inventors: Benson, Glenn S., Marsolan, Paul, Moos, Christopher Guenther
• Primary Examiner(s): Le, Khoi V
• Application Number:
  US15/053,362
• Publication Number:
  US 20170250979A1
• Time in Patent Office: 1,216 Days
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34

Abstract

A system for detecting whether a device seeking communication with a server is a returning device that previously communicated with the server includes a database that stores groups of device attributes based on observable device characteristics and unique identifiers. The database is generally not accessible to the devices. Each attribute group and the associated device identifier (DID) can uniquely identify a particular device, and the associated DID is generally not derivable from the attributes. The database may satisfy a uniqueness property so that each attribute value in the database may also uniquely identify a device.

Claims

1. A method for categorizing a device by a server over a network, the method comprising the steps of:

receiving, at the server, device data from the device comprising a plurality of device attributes including a first device attribute and a second device attribute;

using information accessible to the server, wherein the information comprises a plurality of attribute groups, each group corresponding to a respective previously identified device, to designate the device as a risky device in response to;

(a) a determination that the first device attribute is included in a first attribute group within the plurality of attribute groups, the first attribute group being associated with a first device identifier (DID); and

(b) a determination that the second device attribute is included in a second attribute group within the plurality of attribute groups, the second attribute group being different from the first attribute group; and

otherwise;

designating the device as a new device in response to determining that none of the plurality of device attributes is included in any of the plurality of attribute groups; and

otherwise designating the device as a returning device in response to;

(c) a determination that the first device attribute is included in a first attribute group within the plurality of attribute groups; and

(d) a determination that the second device attribute is either (1) included in the first attribute group or (2) not included in any of the plurality of attribute groups.

2. The method of claim 1, wherein the device is designated as a returning device, and the method further comprises identifying the device using the first DID.

3. The method of claim 1, wherein the device is designated as a risky device, and the method further comprises:

associating a designated low confidence score or a designated high risk score with a first DID associated with the first attribute group or a second DID associated with the second attribute group.

4. The method of claim 1, wherein the first device attribute is determined to be included in a first attribute group within the plurality of attribute groups, and wherein the second device attribute is determined to be not included in any of the plurality of attribute groups.

5. The method of claim 1, wherein the device is designed as a new device, and the method further comprises:

generating by the server a new DID;

storing the plurality of device attributes as a new attribute group in the plurality of attribute groups; and

associating the new DID with the new attribute group.

6. The method of claim 5, the method further comprising:

associating a designated high confidence score or a designated low risk score with the new DID if no data element corresponding to the plurality of device attributes is inconsistent with any other data element corresponding to the plurality of device attributes; and

otherwise;

(i) associating a designated low confidence score or a designated high risk score with the new DID, and (ii) re-designating the device as an attempted anonymized device.

7. The method of claim 1, wherein the first device attribute is based on:

a phone number, a mobile equipment identifier, a parameter of an operating system installed on the device, a model number of the device, a serial number of the device, a device characteristic, a public key allocated to the device, or a public key installed on the device.

8. The method of claim 1, wherein the receiving step comprises receiving the first device attribute via a digitally signed message.

9. The method of claim 2, wherein the first device attribute and the second device attribute are determined to be included in the first attribute group, and the method further comprises associating one of a designated high confidence score or a designated low risk score with the first DID.

10. The method of claim 4, wherein the second device attribute represents a user-authorized change to a device property, and the method further comprises:

storing the second device attribute in the first attribute group.

11. The method of claim 4, further comprising associating a designated low confidence score or a designated high risk score with a first DID associated with the first attribute group.

12. The method of claim 10, further comprising associating a designated high confidence score or a designated low risk score with a first DID associated with the first attribute group.

13. The method of claim 5, wherein generating the new DID comprises generating the new DID using a random number generator or a pseudo-random number generator.

14. The method of claim 13, wherein the new DID is generated independently of any of the plurality of device attributes.

15. The method of claim 8, wherein the message comprises:

(i) a first information object comprising the first device attribute, (ii) a header object comprising an anti-replay header or an anti-tamper header, and (iii) an integrity object comprising a digital signature associated with the first information object, and the method further comprises;

validating the message based on the digital signature.

16. The method of claim 15, wherein the plurality of device attributes comprises a public key used for validating the digital signature.

17. The method of claim 15, the method further comprising:

performing by the server;

(i) an anti-replay check, or (ii) an anti-tamper check; and

validating the message according to a result of;

(i) the anti-replay check, or (ii) the anti-tamper check.

18. A method for identifying a device by a server over a network, the method comprising the steps of:

maintaining by the server a stored sequence of functions, each function in the sequence mapping a domain comprising a plurality of stored tuples of attribute values of devices to a plurality of pseudo-randomly generated identifier values in a respective co-domain, each tuple corresponding to a previously recognized device;

receiving, at the server, a device tuple from the device comprising a first attribute value and a second attribute value;

boolean testing the device tuple by the server to produce a failed result and to designate the device as a risky device in response to;

(a) a determination that the first attribute value is included in a first stored tuple, the first tuple being associated with a first device identifier (DID), and (b) a determination that the second attribute value is included in a second stored tuple different from the first tuple; and

otherwise, producing a successful result;

to designate the device as a new device in response to determining that none of the plurality of device attributes is included in any of the plurality of attribute groups; and

to otherwise designate the device as a returning device in response to;

(c) a determination that the first device attribute is included in a first attribute group within the plurality of attribute groups; and

(d) a determination that the second device attribute is either (1) included in the first attribute group or (2) not included in any of the plurality of attribute groups.

19. The method of claim 18, wherein the failed result is produced, and the method further comprises designating the device tuple as a risky tuple.

20. The method of claim 18, wherein:

(c) it is determined that both the first and second attribute values belong to the first stored tuple, a first function in the sequence of functions maps the first tuple to the first device identifier (DID), and the successful result is produced, and the method further comprises;

designating the device associated with the device tuple as a returning device; and

identifying the returning device using the first DID.

21. The method of claim 18, wherein:

(c) the first attribute value is determined to belong to the first stored tuple, and (d) the second attribute value is determined not to belong to any stored tuple in the plurality of stored tuples, and the successful result is produced, and the method further comprises;

designating the device associated with the device tuple a returning device; and

updating the first stored tuple with the second attribute value.

22. The method of claim 18, wherein:

(c) both the first and the second attribute values are determined not to belong to any stored tuple in the plurality of stored tuples, and the successful result is produced, and the method further comprises;

designating the device associated with the device tuple as a new device;

updating the domain by adding the device tuple;

generating a new function mapping the updated domain to an updated plurality of pseudo-randomly generated identifier values in a second co-domain comprising an identifier value that is not in the first co-domain; and

adding the new function to the sequence.

23. The method of claim 18, wherein each identifier value is unique.

24. The method of claim 19, wherein the risky tuple is associated with a designated low confidence score or a designated high risk score.

25. The method of claim 22, wherein:

the new function represents a new set of mappings comprising a first set of mappings according to the first function; and

a number of mappings in the new set of mappings is one greater than a number of mappings in the first set.

26. A system for facilitating categorization of a device by a server over a network, the system comprising:

a first processor; and

a first memory in electrical communication with the first processor, the first memory comprising instructions which, when executed by a processing unit comprising the first processor, and in electronic communication with a memory module comprising the first memory, cause the processing unit to;

receive, at the server, device data from the device comprising a plurality of device attributes including a first device attribute and a second device attribute;

using information accessible to the server, wherein the information comprises a plurality of attribute groups, each group corresponding to a respective previously identified device, to designate the device as a risky device in response to;

(a) a determination that the first device attribute is included in a first attribute group within the plurality of attribute groups, the first attribute group being associated with a first device identifier (DID); and

(b) a determination that the second device attribute is included in a second attribute group within the plurality of attribute groups, the second attribute group being different from the first attribute group; and

otherwise;

designate the device as a new device if it is determined that none of the plurality of device attributes is included any of the plurality of attribute groups; and

otherwise, designate the device as a returning device when;

(c) the first device attribute is determined to be included in a first attribute group within the plurality of attribute groups; and

(d) the second device attribute is determined to be either (1) included in the first attribute group or (2) not included in any of the plurality of attribute groups.

27. The system of claim 26, wherein the processing unit designates the device as a returning device, and wherein the first attribute group is associated with a first device identifier (DID), the instructions further programming the processing unit to identify the device using the first DID.

28. The system of claim 26, wherein the device is designated as a risky device, the instructions further programming the processing unit to associate a designated low confidence score or a designated high risk score with a first DID associated with the first attribute group or a second DID associated with the second attribute group.

29. The system of claim 26, wherein the first device attribute is determined to be included in a first attribute group within the plurality of attribute groups, and wherein the second device attribute is determined to be not included in any of the plurality of attribute groups.

30. The system of claim 26, wherein the device is designated a new device, the instructions further programming the processing unit to:

generate by the server a new DID;

store the plurality of device attributes as a new attribute group; and

associate the new DID with the new attribute group.

31. The system of claim 26, wherein the first device attribute is based on:

a phone number, a mobile equipment identifier, a parameter of an operating system installed on the device, a model number of the device, a serial number of the device, a device characteristic, a public key allocated to the device, or a public key installed on the device.

32. The system of claim 26, wherein the processing unit is programmed to receive the first device attribute via a digitally signed message.

33. The system of claim 27, wherein the first device attribute and the second device attribute are determined to be included in the first attribute group, the instructions further programming the processing unit to associate a designated high confidence score or a designated low risk score with the first DID.

34. The system of claim 29, wherein the second device attribute represents a user-authorized change to a device property, the instructions further programming the processing unit to store the second device attribute in the first attribute group.

35. The system of claim 29, the instructions further programming the processing unit to associate a designated low confidence score or a designated high risk score with a first DID associated with the first attribute group.

36. The system of claim 34, the instructions further programming the processing unit to associate one of a designated high confidence score and a designated low risk score with a first DID associated with the first attribute group.

37. The system of claim 30, wherein to generate the new DID, the instructions further program the processing unit to generate the new DID using a random number generator or a pseudo-random number generator.

38. The system of claim 30, wherein the instructions further program the processing unit to:

associate a designated high confidence score or a designated low risk score with the new DID if no data element corresponding to the plurality of device attributes is inconsistent with any other data element corresponding to the plurality of device attributes; and

otherwise;

(i) associate a designated low confidence score or a designated high risk score with the new DID, and (ii) re-designate the device as an attempted anonymized device.

39. The system of claim 37, wherein the processing unit is programmed to generate the new DID independently of any of the plurality of device attributes.

40. The system of claim 32, wherein the message comprises:

(i) a first information object comprising the first device attribute, (ii) a header object comprising an anti-replay header or an anti-tamper header, and (iii) an integrity object comprising a digital signature associated with the first information object, the instructions further program the processing unit to;

validate the message based on the digital signature.

41. The system of claim 32, wherein the instructions further program the processing unit to:

perform by the server;

(i) an anti-replay check, or (ii) an anti-tamper check; and

validate the message according to a result of;

(i) the anti-replay check, or (ii) the anti-tamper check.

42. The system of claim 40, wherein the plurality of device attributes comprises a public key used for validating the digital signature.

43. A system for facilitating identification of a device by a server over a network, the system comprising:

a first processor; and

a first memory in electrical communication with the first processor, the first memory comprising instructions which, when executed by a processing unit comprising the first processor, and in electronic communication with a memory module comprising the first memory, cause the processing unit to;

maintain by the server a stored sequence of functions, each function in the sequence mapping a domain comprising a plurality of stored tuples of attribute values of devices to a plurality of pseudo-randomly generated identifier values in a respective co-domain, each tuple corresponding to a previously recognized device;

receive, at the server, a device tuple from the device comprising a first attribute value and a second attribute value;

boolean test the device tuple by the server to produce a failed result and to designate the device as a risky device in response to;

(a) a determination that the first attribute value is included in a first stored tuple, the first tuple being associated with a first device identifier (DID), and (b) a determination that the second attribute value is included in a second stored tuple different from the first tuple; and

otherwise, to produce a successful result, and;

designate the device as a new device in response to determining that none of the plurality of device attributes is included in any of the plurality of attribute groups; and

otherwise designate the device as a returning device in response to;

(c) a determination that the first device attribute is included in a first attribute group within the plurality of attribute groups; and

(d) a determination that the second device attribute is either (1) included in the first attribute group or (2) not included in any of the plurality of attribute groups.

44. The system of claim 43, wherein the failed result is produced, and wherein the instructions further cause the processing unit to designate the device tuple as a risky tuple.

45. The system of claim 43, wherein the instructions cause the processing unit to produce a successful result in response to:

(c) a determination that both the first attribute value and the second attribute value belong to the first stored tuple, and wherein a first function in the sequence of functions maps the first tuple to the first device identifier (DID), and wherein the instructions further cause the processing to;

designate the device associated with the device tuple as a returning device; and

identify the returning device using the first DID.

46. The system of claim 43, wherein the instructions cause the processing unit to produce a successful result in response to:

(c) a determination that the first attribute value is included in the first stored tuple, and (d) a determination that the second attribute value is not included in any stored tuple in the plurality of stored tuples, and wherein the instructions further cause the processing unit to;

designate the device associated with the device tuple as a returning device; and

update the first stored tuple with the second attribute value.

47. The system of claim 43, wherein the instructions further cause the processing unit to produce a successful result in response to:

(c) a determination that both the first attribute value and the second attribute value do not to belong to any stored tuple in the plurality of stored tuples, and wherein the instructions further cause the processing unit to;

designate the device associated with the device tuple as a new device;

update the domain by adding the device tuple;

generate a new function mapping the updated domain to an updated plurality of pseudo-randomly generated identifier values in a second co-domain comprising an identifier value that is not in the first co-domain; and

add the new function to the sequence.

48. The system of claim 44, wherein the risky tuple is associated with a designated low confidence score or a designated high risk score.