Anonymous Preservation of a Relationship and Its Application in Account System Management

• US 20110078779A1
• Filed: 09/25/2009
• Published: 03/31/2011
• Est. Priority Date: 09/25/2009
• Status: Abandoned Application

• Current Assignee: Liu Song, Min Guo
• Original Assignee: Liu Song, Min Guo
• Inventors: Liu, Song, Guo, Min
• Application Number:
  US12/567,066
• Publication Number:
  US 20110078779A1
• Time in Patent Office: Days
• US Class Current: 726/9
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 21/34 involving the use of external additional devices, e.g. dongles or smart cards
• CPC Class Codes: G06F 21/6254 by anonymising data, e.g. decorrelating personal data from the owner's identification
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 2209/42 Anonymization, e.g. involving pseudonyms
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 9/3213 using tickets or tokens, e.g. Kerberos network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807
• CPC Class Codes: H04L 9/3236 using cryptographic hash functions

Abstract

Disclosed is a system or method of using hash functions to preserve a relationship. A relationship is anonymously preserved by storing the hash result of a relationship token that comprises a finite set of values of a plurality of objects. Specifically, an account anonymous identifier of an account can be produced by hashing a relationship token that comprises identity information of an owner of said account. A party that has enough knowledge of an account owner can independently produces said account anonymous identifier and therefore, securely communicates with a specific account without prior communication or a password. An account owner can further prove his/her ownership of an account by submitting related documents and a relationship token that comprises his/her identity information to an account system.

Claims

1. A method for anonymously preserving a relationship among a finite set of values of a plurality of objects, comprising:

a. constructing a relationship token by comprising said finite set of values of said plurality of objects

b. providing hash means for generating a relationship identifier by hashing said relationship token so that said relationship identifier is substantially irreversible and its relationship with said relationship token is substantially injective

c. storing said relationship identifier in a storage media so that said relationship among said finite set of values of said plurality of objects is anonymously preserved

whereby said relationship among said finite set of values of said plurality of objects can be anonymously preserved without storing said finite set of values that might contain sensitive information.

2. The method of claim 1, further including a method for verifying whether an anonymously preserved relationship exists among a different set of values of said plurality of objects, comprising:

a. constructing a test relationship token that comprises said different set of values of said plurality of objects

b. hashing said test relationship token using said hash means to produce a test relationship identifier

c. matching a stored relationship identifier with said test relationship identifier by searching stored relationship identifiers

d. confirming a preserved relationship existing among said different set of values of said plurality of objects if a match is found.

3. The method of claim 1 wherein said relationship token comprises a value separator.

4. The method of claim 1, further including formatting a value of said finite set of values to a fixed length string and using said fixed length string to replace said value in constructing said relationship token.

5. The method of claim 1, further including encrypting a value of said finite set of values to get an encryption string and using said encryption string to replace said value in constructing said relationship token.

6. The method of claim 1 wherein adjacent said values in said relationship token belonging to different symbol sets.

7. The method of claim 1 wherein said finite set of values of a plurality of objects comprising a login name object value and a password object value.

8. A method for constructing an account anonymous identifier for an account in an account system by anonymously preserving a relationship among a finite set of values of a plurality of said account related objects, comprising

a. constructing a unique relationship token by comprising a finite set of values of a plurality of said account related objects

b. providing hash means for generating an account anonymous identifier by hashing said unique relationship token so that said account anonymous identifier is substantially irreversible and its relationship with said unique relationship token is substantially injective

c. storing said account anonymous identifier and its association with said account in said account system in a storage media so that said account system can identify an account by a given account anonymous identifier

whereby said account system is able to use said account anonymous identifier to identify said account without storing said relationship token that might contain sensitive information.

9. The method of claim 8 wherein said account anonymous identifier is unique within said account system.

10. The method of claim 8 wherein a value of said finite set of values of a plurality of said account related objects contains a piece of identity information of an owner of said account.

11. The method of claim 8 wherein said account anonymous identifier is generated at a client side.

12. The method of claim 8 wherein said account anonymous identifier is saved at a client side.

13. The method of claim 8 wherein said account anonymous identifier is a login name encryption of said account.

14. The method of claim 8, wherein said account anonymous identifier is an account ID of said account.

15. The method of claim 8 wherein a plurality of said account anonymous identifiers are constructed and stored for said account

whereby said account is able to match more identifiers to accommodate third parties that have different information to construct different account anonymous identifiers.

16. The method of claim 8, further comprising storage means for storing the associations of said account anonymous identifier with its related records within said account.

17. The method of claim 8, further including a method for boosting the security level of a stored account anonymous identifier by storing the hash result of said account anonymous identifier, comprising:

a. providing a hash means to hash said account anonymous identifier so that a new account anonymous identifier can be obtained

b. replacing said account anonymous identifier with said new account anonymous identifier in said storing process so that said new account anonymous identifier and its association with said account in said account system are stored, and said account system can identify an account by using a hash result that is generated by applying said hash means on a given account anonymous identifier

whereby said account system is able to use said new account anonymous identifier, an value cannot be constructed by a party that does not know said hash means, as a stored account anonymous identifier to identify an account, substantially increasing the security level of an account identification process.

18. The method of claim 8, further including a method for an third party to identify an account within said account system, comprising:

a. constructing a relationship token that comprises a finite set of values of a plurality of said account related objects from available data sources of said third party

b. providing hash means for generating an existing account anonymous identifier by hashing said relationship token

c. submitting said existing account anonymous identifier to said account system for identifying said account

d. searching stored account anonymous identifiers within said account system for an account identifier match using an identifier selected from the group consisting of said submitted existing account anonymous identifier and a new identifier that is generated by hashing said submitted existing account anonymous identifier

e. identifying an existing account as an account identified by said third party if a stored account anonymous identifier of said existing account matches with an identifier selected from the group consisting of said submitted existing account anonymous identifier and a new identifier generated by hashing said submitted existing account anonymous identifier.

whereby said third party is able use its own data source and knowledge of the relationship among said account related objects to independently construct an effective existing account anonymous identifier to identify an existing account without prior communication with said account system.

19. The method of claim 10, further including a method for an account owner to recover his/her account ownership of an existing account in said account system, comprising:

a. constructing a relationship token that comprises a finite set of values of a plurality of said account related objects using said owner identity information

b. submitting said relationship token together with related identity documents to said account system

c. verifying whether said submitted relationship token is truly constructed with the identity information from said submitted documents

d. hashing said submitted relationship token to produce an existing account anonymous identifier

e. searching said existing account anonymous identifier among stored account anonymous identifiers for a match

f. granting the account ownership of an existing account to said account owner if said relationship token is constructed with the identity information from said submitted documents and a stored account anonymous identifier associated with said existing account matches with said existing account anonymous identifier.

20. The method of claim 8, further comprising a method for supporting multiple users to share said account by storing the associations of a said account anonymous identifier with its related records, comprising:

a. using a piece of identity information of a said user to construct a unique relationship token for a said user

b. constructing a unique relationship token for each said multiple users

c. hashing each said unique relationship token by said providing hash means for generating an account anonymous identifier for each said multiple users

d. storing each said account anonymous identifier, its association with said account in said account system in a storage media so that said account system can identify an account by a given account anonymous identifier

e. storing the associations of a said account anonymous identifier with its related records so that said account system can classify a record within said account by a given account anonymous identifier.

21. The method of claim 8 wherein said unique relationship token is a login name of said account.