Method and apparatus for personalization and identity management

• US 8,051,472 B2
• Filed: 07/13/2004
• Issued: 11/01/2011
• Est. Priority Date: 12/17/2003
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Maes, Stephane H.
• Primary Examiner(s): Shiferaw; Eleni
• Assistant Examiner(s): FIELDS, COURTNEY D
• Application Number:
  US10/890,786
• Publication Number:
  US 20050137981A1
• Time in Patent Office: 2,667 Days
• Field of Search: 726/8, 705/44, 705/67, 713/153, 455/410, 455/461, 370/329
• US Class Current: 726/8
• CPC Class Codes: G06F 21/6254 by anonymising data, e.g. decorrelating personal data from the owner's identification
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/35 involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
• 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 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

Methods and systems are disclosed for personalization and identity management. In one embodiment, the method comprises receiving, from an access provider, a message for a service provider, the message associated with a first identifier of a user of the access provider. A second identifier is obtained, the first identifier is disassociated from the message, and the second identifier is associated with the message. The message associated with the second identifier is then sent to the service provider.

Claims

1. A method comprising:

receiving into an identity provider, from a first access provider, a first message for a first service provider, the first access provider providing access to a communication network to a device of a user, the first service provider providing one or more services to the user of the communication network, and the first message associated with a first identifier corresponding to a user of the first access provider, the first identifier identifying the user allowing the user to access and communicate with the first access provider; and

in response to receiving the first message from the first access provider;

obtaining by the identity provider a second identifier on behalf of the user;

disassociating by the identity provider the first identifier from the first message;

associating by the identity provider the first message with the second identifier; and

sending from the identity provider the first message associated with the second identifier to the first service provider, the second identifier providing for communication with the first service provider while masking identity information for the user and the device of the user contained within the first identifier;

retrieving by the identity provider personalization information associated with the second identifier, wherein the personalization information comprises one or more of user preferences, user device characteristics, user device capabilities, user device settings, and user device addresses;

sending from the identity provider a first subset of the personalization information to the first service provider;

receiving into the identity provider, from a second access provider, a second message for the first service provider, the second message associated with a third identifier of the user of the second access provider; and

in response to the second message from the second access provider;

determining by the identity provider the third identifier is mapped to the first identifier;

disassociating by the identity provider the third identifier from the second message;

associating by the identity provider the second message with the second identifier;

sending from the identity provider the second message associated with the second identifier to the first service provider; and

sending from the identity provider the first subset of the personalization information to the first service provider.

2. The method of claim 1, wherein sending the personalization information is in response to receiving a request from the first service provider to access the portion of the personalization information.

3. The method of claim 2, wherein receiving the request from the first service provider comprises receiving a request from the first service provider to obtain a cookie, the request associated with the second identifier.

4. The method of claim 1, wherein sending the personalization information comprises receiving authorization from the user to send the personalization information.

5. The method of claim 1, wherein sending the personalization information comprises determining the personalization information may be shared with the service provider.

6. The method of claim 1, wherein the personalization information comprises one or more of user preferences related to the first service provider and generic user preferences.

7. The method of claim 1, wherein the personalization information comprises account information.

8. The method of claim 1, wherein the personalization information comprises payment information.

9. The method of claim 1, wherein the personalization information comprises application settings.

10. The method of claim 1, further comprising:

receiving, from the first access provider, a third message for a second service provider, the third message associated with the first identifier;

disassociating the first identifier from the third message;

associating the third message with the second identifier;

sending the third message associated with the second identifier to the second service provider; and

sending a second subset of the personalization information to the second service provider.

11. The method of claim 1, further comprising:

receiving, from the first access provider a third message for a second service provider, the third message associated with the first identifier;

disassociating the first identifier from the third message;

obtaining a fourth identifier;

associating the third message with the fourth identifier;

sending the third message associated with the fourth identifier to the second service provider; and

sending a second subset of the personalization information to the second service provider.

12. The method of claim 1, further comprising:

receiving personalization information;

associating the personalization information with the second identifier; and

storing the personalization information associated with the second identifier.

13. The method of claim 12, wherein receiving personalization information comprises receiving personalization information from the user.

14. The method of claim 12, wherein receiving personalization information comprises receiving a cookie from the first service provider.

15. The method of claim 12, wherein receiving personalization information comprises receiving one or more of user device characteristics, user device capabilities, user device settings, and user device addresses.

16. The method of claim 12, wherein receiving personalization information comprises receiving at least one user preference.

17. The method of claim 1, further comprising:

associating a session to the second identifier;

associating the first or second message to the session;

evaluating the message for session management information, the session management information including data representing a state of the interaction between the user and the service provider;

receiving one or more additional messages, from the access provider, for the first or second service provider, the one or more additional messages associated with the first identifier;

for each of the additional messages for the first or second service provider, received from the first access provider associating the additional messages to the session, and evaluating each of the additional messages for session management information; and

storing the session management information.

18. The method of claim 17, further comprising:

receiving, from a third access provider, a third message for the first or second service provider, the third message associated with a fourth identifier for the user;

determining the fourth identifier is mapped to the first identifier;

disassociating the fourth identifier from the third message;

associating the third message with the second identifier; and

sending the third message associated with the second identifier to the first or second service provider.

19. The method of claim 18, further comprising:

determining the third identifier is associated with the session;

retrieving the session management information associated with the session; and

sending the session management information to the first or second service provider.

20. The method of claim 1, further comprising:

receiving, from a third access provider, a third message for the first or second service provider, the third message associated with a fourth identifier for a user;

determining the fourth identifier is mapped to the first identifier;

disassociating the fourth identifier from the third message;

associating the third message with the second identifier; and

sending the third message associated with the second identifier to the first or second service provider.

21. The method of claim 20, wherein receiving the first message for the first service provider comprises receiving the first message at a first identity provider, and wherein receiving the second message for the second service comprises receiving the second message at a second identity provider, and wherein determining the third identifier is mapped to the first identifier comprises accessing, from the second identity provider, a data storage including user identification mappings mapping user addresses for the first access provider to user addresses for the second access provider.

22. The method of claim 1, wherein obtaining the second identifier comprises determining the first identifier is mapped to the second identifier.

23. The method of claim 1, wherein obtaining the second identifier comprises obtaining a new identification for the user.

24. The method of claim 1, further comprising:

authenticating the second identifier; and

wherein sending the first message comprises sending the first message with an indication the second identifier has been authenticated.

25. The method of claim 1, wherein receiving the first message comprises receiving the first message from a mobile network operator (MNO).

26. The method of claim 25, wherein first identifier is an MSISDN.

27. The method of claim 1, wherein receiving the first message from the first access provider comprises receiving the first message from a wireless network provider.

28. The method of claim 27, wherein the wireless network provider is one of a provider of General Packet Radio Service (GPRS), WiFi, 2.5G, FOMA, UMTS, CDMA, and EDGE.

29. The method of claim 1, wherein the first service provider is a payment provider, the method further comprising:

receiving a request to authorize a payment amount, the request associated with the second identifier;

providing the authorization to the payment provider.

30. The method of claim 29, further comprising transmitting the payment amount to the first access provider.

31. A system comprising:

a processor; and

a memory coupled with and readable by the processor and having stored therein a sequence of instructions which, when executed by the processor, cause the processor to manage personalization and identity information by;

receiving, from a first access provider, a first message for a first service provider, the first access provider providing access to a communication network to a device of a user, the first service provider providing one or more services to the user of the communication network, and the first message associated with a first identifier corresponding to a user of the first access provider, the first identifier identifying the user allowing the user to access and communicate with the first access provider; and

in response to receiving the first message from the first access provider;

obtaining a second identifier on behalf of the user;

disassociating the first identifier from the first message;

associating the first message with the second identifier; and

sending f the first message associated with the second identifier to the first service provider, the second identifier providing for communication with the first service provider while masking identity information for the user and the device of the user contained within the first identifier;

retrieving personalization information associated with the second identifier, wherein the personalization information comprises one or more of user preferences, user device characteristics, user device capabilities, user device settings, and user device addresses;

sending a first subset of the personalization information to the first service provider;

receiving, from a second access provider, a second message for the first service provider, the second message associated with a third identifier of the user of the second access provider; and

in response to the second message from the second access provider;

determining the third identifier is mapped to the first identifier;

disassociating the third identifier from the second message;

associating the second message with the second identifier;

sending the second message associated with the second identifier to the first service provider; and

sending the first subset of the personalization information to the first service provider.

32. A non-transitory computer-readable memory having stored thereon a sequence of instructions which, when executed by a processor, cause the processor to manage personalization and identity information by:

receiving, from a first access provider, a first message for a first service provider, the first access provider providing access to a communication network to a device of a user, the first service provider providing one or more services to the user of the communication network, and the first message associated with a first identifier corresponding to a user of the first access provider, the first identifier identifying the user allowing the user to access and communicate with the first access provider;

and in response to receiving the first message from the first access provider;

obtaining a second identifier on behalf of the user;

disassociating the first identifier from the first message;

associating the first message with the second identifier;

and sending the first message associated with the second identifier to the first service provider, the second identifier providing for communication with the first service provider while masking identity information for the user and the device of the user contained within the first identifier;

retrieving personalization information associated with the second identifier, wherein the personalization information comprises one or more of user preferences, user device characteristics, user device capabilities, user device settings, and user device addresses;

sending a first subset of the personalization information to the first service provider;

receiving, from a second access provider, a second message for the first service provider, the second message associated with a third identifier of the user of the second access provider;

and in response to the second message from the second access provider;

determining the third identifier is mapped to the first identifier;

disassociating the third identifier from the second message;

associating the second message with the second identifier;

sending the second message associated with the second identifier to the first service provider;

and sending the first subset of the personalization information to the first service provider.