USER AUTHENTICATION USING UNIQUE HIDDEN IDENTIFIERS

• US 20140317699A1
• Filed: 03/11/2014
• Published: 10/23/2014
• Est. Priority Date: 03/15/2013
• Status: Active Grant

• Current Assignee: Brian A. Truong
• Original Assignee: Brian A. Truong
• Inventors: Truong, Brian A.
• Granted Patent: US 9,306,926 B2
• Time in Patent Office: Days
• US Class Current: 726/5
• CPC Class Codes: G06Q 50/01 Social networking
• CPC Class Codes: H04L 63/0407 wherein the identity of one or more communicating identities is hidden cryptographic mechanisms or cryptographic arrangements for anonymous credentials or for identity based cryptographic systems H04L9/00
• CPC Class Codes: H04L 63/0414 during transmission, i.e. party's identity is protected against eavesdropping, e.g. by using temporary identifiers, but is known to the other party or parties involved in the communication
• CPC Class Codes: H04L 63/0421 Anonymous communication, i.e. the party's identifiers are hidden from the other party or parties, e.g. using an anonymizer
• 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 63/104 Grouping of entities
• CPC Class Codes: H04M 2203/6009 Personal information, e.g. profiles or personal directories being only provided to authorised persons
• CPC Class Codes: H04M 3/42008 Systems for anonymous communication between parties, e.g. by use of disposal contact identifiers
• CPC Class Codes: H04M 3/4931 Directory assistance systems
• CPC Class Codes: H04W 12/02 Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
• CPC Class Codes: H04W 12/033 of the user plane, e.g. user's traffic
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 4/08 User group management
• CPC Class Codes: H04W 8/186 Processing of subscriber group data

Abstract

Systems and methods are provided for user authentication using hidden unique identifiers in networks. In some example embodiments these systems and methods only require a single human readable identifier be provided and minimize personal information exposure in the event of a network breach.

Claims

1. A non-transitory computer readable medium including instructions that are configured to cause a computer system to authenticate a user by performing a method comprising:

a user device prompting a user to create a human readable identifier signifying a network account;

the user device creating the network account signified by the human readable identifier, wherein account creation includes a server assigning a unique identifier to the user device;

the user device prompting the user to add contacts directly or indirectly; and

the user device adding contacts directly or indirectly based on user input, where human readable identifiers are used to identify added contacts to the user.

2. The non-transitory computer readable medium including instructions that are configured to cause a computer system to authenticate a user by performing a method according to claim 1, wherein the user device creating the network account using the human readable identifier further comprises:

for a first user using a first device with a first human readable identifier,

1) the first device sending the first human readable identifier signifying the first device to a server;

2) the server assigning a first unique identifier to the first device and sending the first unique identifier to the first device;

3) the server associating the first user identifier with the first human readable identifier in a database, wherein the first unique identifier is unknown to the first user; and

wherein allowing additional users to create user accounts includes following steps

     1),

     2),

     3).

3. The non-transitory computer readable medium including instructions that are configured to cause a computer system to authenticate a user by performing a method according to claim 1, wherein adding contacts directly further comprises:

after a first user account associated with a first device and a second user account associated with a second device have been created, the first device connecting to the server;

the second device to connect to the server;

during a real-time communication, the first device sending a contact add request to the server;

the server forwarding the contact add request to the second device and the second device displaying the first human readable identifier and the contact add request during the real-time communication;

the second device sending a second session identifier to the server upon confirmation of the contact add request;

the server retrieving and adding the first user identifier to a second group and retrieving and adding a second user identifier to a first group; and

the server sending the second human readable identifier to a first group on the first device and sending the first human readable identifier to a second group on the second user device.

4. The non-transitory computer readable medium including instructions that are configured to cause a computer system to authenticate a user by performing a method according to claim 3, further comprising:

wherein the first device connecting to the server further comprises the first device sending the first unique identifier to the server and receiving a first session identifier from the server.

5. The non-transitory computer readable medium including instructions that are configured to cause a computer system to authenticate a user by performing a method according to claim 3, further comprising:

wherein the second user device connecting to the server further comprises the second device sending a second unique identifier to the server and receiving a second session identifier from the server.

6. The non-transitory computer readable medium including instructions that are configured to cause a computer system to authenticate a user by performing a method according to claim 3, further comprising:

wherein the first device sending a contact add request to the server comprises the first device sending a contact add request comprising the first session identifier, the first human readable identifier and an instruction to request the second user'"'"'s approval.

7. The non-transitory computer readable medium including instructions that are configured to cause a computer system to authenticate a user by performing a method according to claim 1, wherein users adding contacts indirectly further comprises:

once a first user account associated with a first device, a second user account associated with a second device, and a third user account associated with a third device have been created, and the first device and second device are contacts, second device and third device are contacts, and the first device and third device are not contacts;

the second device creating a group comprising the first human readable identifier and the third human readable identifier;

wherein the human readable identifiers are visible to all members of the group on their respective devices;

the first device sending a contact add request to the server;

the server forwarding the contact add request to the third device and the third device displaying the first human readable identifier and the contact add request;

the third device sending a third session identifier to the server upon confirmation of the contact add request;

the server retrieving and adding the first user identifier to a third group and retrieving and adding a third user identifier to a first group; and

the server sending the third human readable identifier to a first group on the first device and sending the first human readable identifier to a third group on the second user device.

8. The non-transitory computer readable medium including instructions that are configured to cause a computer system to authenticate a user by performing a method according to claim 1, further comprising:

a third party system authenticating users using the human readable identifier signifying the user network account.

9. The non-transitory computer readable medium including instructions that are configured to cause a computer system to authenticate a user by performing a method according to claim 8, further comprising:

wherein a third party system authenticating users using the human readable identifier signifying the user network account further comprises;

the third party system displaying a barcode signifying a session identifier for the user to scan;

upon scanning the barcode, the user device prompting the user to confirm a login; and

confirmation of a login causing the third party system to have access to or interaction with the user'"'"'s contacts.

10. The non-transitory computer readable medium including instructions that are configured to cause a computer system to authenticate a user by performing a method according to claim 1, further comprising:

wherein a quantity of user contacts is used to provide an additional authentication measure.

11. A process of user authentication comprising:

creating a computer network operable to allow users to create accounts;

wherein the computer network is operable to allow users to become contacts directly or indirectly; and

wherein information required for user authentication comprises a human readable identifier without requiring other personal information.

12. The process of user authentication of claim 11, wherein allowing users to create user accounts further comprises:

for a first user,

1) allowing the first user using a first device to create a first human readable identifier associated with the first device;

2) the first device sending the first human readable identifier associated with the first device to a server;

3) the server assigning a first unique identifier to the first device and sending the first unique identifier to the first device;

4) the server associating the first user identifier with the first human readable identifier in a database, wherein the first unique identifier is unknown to the first user; and

wherein allowing additional users to create user accounts comprises following steps

     1),

     2),

     3),

     4).

13. The process of user authentication of claim 11, wherein allowing users to become contacts directly further comprises:

once a first user account associated with a first device and a second user account associated with a second device have been created, allowing the first device to connect to the server;

the second user device connecting to the server;

during a real-time communication, the first device to send a contact add request to the server;

the server forwarding the contact add request to the second device and the second device displaying the first human readable identifier and the contact add request, during the real-time communication;

the second device sending the second session identifier to the server upon confirmation of the contact add request;

the server retrieving and adding the first user identifier to a second group and retrieving and adding a second user identifier to a first group; and

the server sending the second human readable identifier to a first group on the first device and sending the first human readable identifier to a second group on the second user device.

14. The process of user authentication of claim 13, further comprising:

wherein the first device connecting to the server comprises the first device sending the first unique identifier to the server and receiving a first session identifier from the server.

15. The process of user authentication of claim 13, further comprising:

wherein the second user device connecting to the server comprises the second device sending a second unique identifier to the server and receiving a second session identifier from the server.

16. The process of user authentication of claim 13, further comprising:

wherein the first device sending a contact add request to the server comprises the first device sending a contact add request comprising the first session identifier, the first human readable identifier and an instruction to request the second user'"'"'s approval.

17. The process of user authentication of claim 11, wherein users becoming contacts indirectly further comprises:

once a first user account associated with a first device, a second user account associated with a second device, and a third user account associated with a third device have been created, and the first device and second device are contacts, second device and third device are contacts, and the first device and third device are not contacts;

the second device creating a group containing the first human readable identifier and the third human readable identifier;

the human readable identifiers are visible to all members of the group on their respective devices;

the first device sending a contact add request to the server;

the server forwarding the contact add request to the third device and the third device displaying the first human readable identifier and the contact add request;

the third device sending a third session identifier to the server upon confirmation of the contact add request;

the server retrieving and adding the first user identifier to a third group and retrieving and adding a third user identifier to a first group; and

the server sending the third human readable identifier to a first group on the first device and sending the first human readable identifier to a third group on the second user device.

18. The process of user authentication of claim 11, further comprising:

a third party system authenticating users using the human readable identifier signifying the user network account.

19. The process of user authentication of claim 18, further comprising:

wherein a third party system authenticating users using the human readable identifier signifying the user network account further comprises;

the third party system displaying a barcode signifying a session identifier for the user to scan;

upon scanning the barcode, the user device prompting the user to confirm a login; and

confirmation of a login causing the third party system to have access to or interaction with the user'"'"'s contacts.

20. The process of user authentication of claim 11, further comprising:

wherein a quantity of user contacts is used to provide an additional authentication measure.