System and method to facilitate importation of user profile data over a network

• US 20060095780A1
• Filed: 10/28/2004
• Published: 05/04/2006
• Est. Priority Date: 10/28/2004
• Status: Abandoned Application

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google LLC (Alphabet Inc.)
• Inventors: Hillis, W. Daniel, Ferren, Bran
• Application Number:
  US10/976,696
• Publication Number:
  US 20060095780A1
• Time in Patent Office: Days
• US Class Current: 713/182
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 63/126 the source of the received data

Abstract

A system and method to facilitate importation of user profile data over a network are described. In one preferred embodiment, a request to import the user profile data is received from a user, the user profile data being stored in a source user account within a source entity. Prior to importation of the user profile data, the source user account is authenticated as being associated with the user. Subsequent to the authentication, the user profile data is received from the source entity and is merged within a destination user account associated with the user. Alternatively, the user profile data may be used to create a destination user account associated with the user.

Claims

1. A method to facilitate importation of user profile data over a network, said method comprising the steps of:

receiving a request to import said user profile data from a user, said user profile data being stored in a source user account within a source entity; and

prior to said importation of said user profile data, authenticating said source user account as being associated with said user.

2. The method according to claim 1, further comprising the steps of:

receiving said user profile data from said source entity; and

merging said user profile data within a destination user account associated with said user.

3. The method according to claim 1, further comprising the steps of:

receiving said user profile data from said source entity; and

using said user profile data to create a destination user account associated with said user.

4. The method according to claim 1, wherein said authenticating step further comprises the steps of:

transmitting a request to said user to provide authentication data for said source user account;

receiving said authentication data; and

accessing said source user account within said source entity using said authentication data.

5. The method according to claim 4, wherein said authentication data is a valid password used to access said source user account.

6. The method according to claim 1, wherein said authenticating step further comprises the steps of:

installing a destination client on a client machine associated with said user;

prompting said user to access said source user account within said source entity; and

monitoring said access of said source user account using said destination client to authenticate said source user account as being associated with said user.

7. The method according to claim 1, wherein said authenticating step further comprises the steps of:

installing a destination client on a client machine associated with said user;

prompting said user to access said source entity using a link accessible only with valid authentication data; and

monitoring said access of said source entity using said destination client to authenticate said source user account as being associated with said user.

8. The method according to claim 7, wherein said monitoring step further comprises the steps of:

determining if said user receives information from said link via a Hyper Text Transfer Protocol (HTTP) request.

9. The method according to claim 1, wherein said authenticating step further comprises the steps of:

transmitting a request to said user to modify at least one parameter within said source entity, each parameter being related to the source user account and being outwardly visible via said network; and

connecting to said source entity to verify modification of said at least one parameter.

10. The method according to claim 9, wherein said authenticating step further comprises the steps of:

receiving a communication detailing said modification from said user.

11. The method according to claim 9, wherein said at least one parameter is a password hint in the event that said user forgets a password used to access said source user account.

12. A system to facilitate importation of user profile data over a network, said system comprising:

means for receiving a request to import said user profile data from a user, said user profile data being stored in a source user account within a source entity; and

prior to said importation of said user profile data, means for authenticating said source user account as being associated with said user.

13. The system according to claim 12, further comprising:

means for receiving said user profile data from said source entity; and

means for merging said user profile data within a destination user account associated with said user.

14. The system according to claim 12, further comprising:

means for receiving said user profile data from said source entity; and

means for using said user profile data to create a destination user account associated with said user.

15. The system according to claim 12, further comprising:

means for transmitting a request to said user to provide authentication data for said source user account;

means for receiving said authentication data; and

means for accessing said source user account within said source entity using said authentication data.

16. The system according to claim 15, wherein said authentication data is a valid password used to access said source user account.

17. The system according to claim 12, further comprising:

means for installing a destination client on a client machine associated with said user;

means for prompting said user to access said source user account within said source entity; and

means for monitoring said access of said source user account using said destination client to authenticate said source user account as being associated with said user.

18. The system according to claim 12, further comprising:

means for installing a destination client on a client machine associated with said user;

means for prompting said user to access said source entity using a link accessible only with valid authentication data; and

means for monitoring said access of said source entity using said destination client to authenticate said source user account as being associated with said user.

19. The system according to claim 18, further comprising:

means for determining if said user receives information from said link via a Hyper Text Transfer Protocol (HTTP) request.

20. The system according to claim 12, further comprising:

means for transmitting a request to said user to modify at least one parameter within said source entity, each parameter being related to the source user account and being outwardly visible via said network; and

means for connecting to said source entity to verify modification of said at least one parameter.

21. The system according to claim 20, further comprising:

means for receiving a communication detailing said modification from said user.

22. The system according to claim 20, wherein said at least one parameter is a password hint in the event that said user forgets a password used to access said source user account.

23. A computer readable medium containing executable instructions, which, when executed in a processing system, cause said processing system to perform a method to facilitate importation of user profile data over a network, said method comprising the steps of:

receiving a request to import said user profile data from a user, said user profile data being stored in a source user account within a source entity; and

prior to said importation of said user profile data, authenticating said source user account as being associated with said user.

24. The computer readable medium according to claim 23, wherein said method further comprises the steps of:

receiving said user profile data from said source entity; and

merging said user profile data within a destination user account associated with said user.

25. The computer readable medium according to claim 23, wherein said method further comprises the steps of:

receiving said user profile data from said source entity; and

using said user profile data to create a destination user account associated with said user.

26. The computer readable medium according to claim 23, wherein said authenticating step further comprises the steps of:

transmitting a request to said user to provide authentication data for said source user account;

receiving said authentication data; and

accessing said source user account within said source entity using said authentication data.

27. The computer readable medium according to claim 26, wherein said authentication data is a valid password used to access said source user account.

28. The computer readable medium according to claim 23, wherein said authenticating step further comprises the steps of:

installing a destination client on a client machine associated with said user;

prompting said user to access said source user account within said source entity; and

monitoring said access of said source user account using said destination client to authenticate said source user account as being associated with said user.

29. The computer readable medium according to claim 23, wherein said authenticating step further comprises the steps of:

installing a destination client on a client machine associated with said user;

prompting said user to access said source entity using a link accessible only with valid authentication data; and

monitoring said access of said source entity using said destination client to authenticate said source user account as being associated with said user.

30. The computer readable medium according to claim 29, wherein said monitoring step further comprises the steps of:

determining if said user receives information from said link via a Hyper Text Transfer Protocol (HTTP) request.

31. The computer readable medium according to claim 23, wherein said authenticating step further comprises the steps of:

transmitting a request to said user to modify at least one parameter within said source entity, each parameter being related to the source user account and being outwardly visible via said network; and

connecting to said source entity to verify modification of said at least one parameter.

32. The computer readable medium according to claim 31, wherein said authenticating step further comprises the steps of:

receiving a communication detailing said modification from said user.

33. The computer readable medium according to claim 31, wherein said at least one parameter is a password hint in the event that said user forgets a password used to access said source user account.

34. A system to facilitate importation of user profile data over a network, said system comprising:

a client machine associated with a user; and

a destination entity coupled to said client machine over said network, said destination entity further comprising authentication servers for receiving a request to import said user profile data from said user, said user profile data being stored in a source user account within a source entity coupled to said destination entity over said network, said authentication servers for authenticating said source user account as being associated with said user prior to said importation of said user profile data.

35. The system according to claim 34, wherein said authentication servers further receive said user profile data from said source entity and merge said user profile data within a destination user account associated with said user.

36. The system according to claim 34, wherein said authentication servers further receive said user profile data from said source entity and use said user profile data to create a destination user account associated with said user.

37. The system according to claim 34, wherein said authentication servers further transmit a request to said user to provide authentication data for said source user account, receive said authentication data, and access said source user account within said source entity using said authentication data.

38. The system according to claim 37, wherein said authentication data is a valid password used to access said source user account.

39. The system according to claim 34, wherein said authentication servers further install a destination client on said client machine associated with said user, prompt said user to access said source user account within said source entity, and monitor said access of said source user account using said destination client to authenticate said source user account as being associated with said user.

40. The system according to claim 34, wherein said authentication servers further install a destination client on said client machine associated with said user, prompt said user to access said source entity using a link accessible only with valid authentication data, and monitor said access of said source entity using said destination client to authenticate said source user account as being associated with said user.

41. The system according to claim 40, wherein said authentication servers further determine if said user receives information from said link via a Hyper Text Transfer Protocol (HTTP) request.

42. The system according to claim 34, wherein said authentication servers further transmit a request to said user to modify at least one parameter within said source entity, each parameter being related to the source user account and being outwardly visible via said network, and connect to said source entity to verify modification of said at least one parameter.

43. The system according to claim 42, wherein said authentication servers further receive a communication detailing said modification from said user.

44. The system according to claim 42, wherein said at least one parameter is a password hint in the event that said user forgets a password used to access said source user account.