Exchanging a contact profile between client devices during a communication session

• US 9,497,287 B2
• Filed: 08/21/2015
• Issued: 11/15/2016
• Est. Priority Date: 03/11/2013
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Jain, Nikhil, Krishnan, Ram, Menendez, Jose Roberto, Joyce, Gerald Patrick III, Deshpande, Manoj
• Primary Examiner(s): Chery, Dady
• Application Number:
  US14/832,198
• Publication Number:
  US 20150358808A1
• Time in Patent Office: 452 Days
• Field of Search: 370/229, 370/331, 370/328, 455/415, 455/461, 455/458, 455/456.1, 455/456.3, 455/418
• US Class Current: 1/1
• CPC Class Codes: H04L 2101/38 Telephone uniform resource identifier [URI]
• CPC Class Codes: H04L 2101/65 Telephone numbers
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1083 In-session procedures
• CPC Class Codes: H04L 65/1094 Inter-user-equipment sessions transfer or sharing
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04W 8/20 Transfer of user or subscriber data

Abstract

In an embodiment, a client device (CD) maintains a contact profile for a user of the CD, the contact profile including a universal identifier (UID) for the user and a list of devices and addresses at which the user of the CD can be contacted. The CD establishes a communication session with a remote CD (RCD) via a given contact address from the set of contact addresses for the RCD. The CD shares, in response to the communication session establishment, at least a portion of the contact profile to the RCD. The RCD generates and/or updates a given contact profile for the user of the CD that is maintained on the RCD based on the shared contact profile. The RCD can also share its profile with the CD in response to the communication session establishment, causing the CD to generate and/or update a contact profile for the RCD.

Claims

1. A method of operating a server, comprising:

maintaining a contact profile for a user, the contact profile including a universal identifier (UID) for the user and a list of devices through which to contact the user, each device in the list of devices being maintained in association with a device identifier, a device location descriptor and a set of contact addresses through which to contact the device;

receiving a request from a remote client device to send the contact profile to the remote client device;

determining a portion of the contact profile to send to the remote client device; and

sending the portion of the contact profile to the remote client device.

2. The method of claim 1, wherein the UID corresponds to an email address, or a cellular phone number associated with a cellular phone from the list of devices.

3. The method of claim 1, wherein the device location descriptor includes home, work or mobile.

4. The method of claim 1, wherein maintaining a contact profile for a user comprises:

registering an email address as the UID for the contact profile of the user;

receiving, for a new device to be added to the contact profile, an indication of the UID and new device information that includes a given device identifier of the new device, a given device location descriptor of the new device and a given set of contact addresses through which to contact the new device; and

updating the contact profile of the user to include the new device information in response to the new device information being received in association with the UID.

5. The method of claim 1, wherein maintaining a contact profile for a user includes:

registering an email address as the UID for the contact profile of the user;

receiving, for a new contact address to be added to the contact profile for an existing device that is already listed in the list of devices, an indication of the UID and new contact address information that includes a given device identifier of the existing device, wherein the new contact address corresponds to a given type of contact mechanism that is different from the registered email address; and

updating the contact profile of the user to include the new contact address for the existing device in response to the new contact address being received in association with the UID.

6. The method of claim 1, wherein the portion of the contact profile that is sent to the remote client device includes each of the set of contact addresses for each of the list of devices of the user.

7. The method of claim 1, wherein the portion of the contact profile that is sent to the remote client device includes less than all contact addresses from the set of contact addresses for one or more of the list of devices of the user.

8. The method of claim 1, wherein the request includes a token that indicates privileges of the remote client device with respect to the contact profile and determining the portion of the contact profile to send to the remote client device comprises determining the portion of the contact profile based on the token.

9. The method of claim 1, wherein determining the portion of the contact profile to send to the remote client device comprises determining the portion of the contact profile based upon one or more privacy rules associated with the user.

10. The method of claim 1, further comprising:

retrieving data messages associated with two or more different contact addresses from the contact profile, the two or more different contact addresses associated with different communication services; and

sending an aggregated version of the retrieved data messages associated with the two or more different contact addresses via a unified interface.

11. The method of claim 10,

wherein the retrieved data messages include a set of cellular phone voicemail messages and a set of Voice over Internet Protocol (VoIP) voicemail messages, and

wherein the two or more different contact addresses include a cellular phone number and a VoIP identifier.

12. The method of claim 10,

wherein the retrieved data messages include a set of email messages, and

wherein the two or more different contact addresses include two or more different email addresses.

13. The method of claim 1, wherein one or more contact addresses in the portion of the contact profile that is sent to the remote client device are masked so that the one or more contact addresses (i) can be recognized by software residing on the remote client device for communication session initiation attempts to the one or more contact addresses by the remote client device, and (ii) cannot be recognized by a given user of the remote client device.

14. The method of claim 1, wherein, for each device in the list of devices, the set of contact addresses includes either (i) a single contact address through which to contact the device, or (ii) multiple contact addresses through which to contact the device.

15. A server, comprising:

a processor configured with processor-executable instructions to perform operations comprising;

maintaining a contact profile for a user, the contact profile including a universal identifier (UID) for the user and a list of devices through which to contact the user, each device in the list of devices being maintained in association with a device identifier, a device location descriptor and a set of contact addresses through which to contact the device;

receiving a request from a remote client device to send the contact profile to the remote client device;

determining a portion of the contact profile to send to the remote client device; and

sending the portion of the contact profile to the remote client device.

16. The server of claim 15, wherein the UID corresponds to an email address, or a cellular phone number associated with a cellular phone from the list of devices.

17. The server of claim 15, wherein the device location descriptor includes home, work or mobile.

18. The server of claim 15, wherein the processor is further configured with processor-executable instructions to perform operations such that maintaining the contact profile comprises:

registering an email address as the UID for the contact profile of the user;

receiving, for a new device to be added to the contact profile, an indication of the UID and new device information that includes a given device identifier of the new device, a given device location descriptor of the new device and a given set of contact addresses through which to contact the new device; and

updating the contact profile of the user to include the new device information in response to the new device information being received in association with the UID.

19. The server of claim 15, wherein the processor is further configured with processor-executable instructions to perform operations such that maintaining the contact profile comprises:

registering an email address as the UID for the contact profile of the user;

receiving, for a new contact address to be added to the contact profile for an existing device that is already listed in the list of devices, an indication of the UID and new contact address information that includes a given device identifier of the existing device, wherein the new contact address corresponds to a given type of contact mechanism that is different from the registered email address; and

updating the contact profile of the user to include the new contact address for the existing device in response to the new contact address being received in association with the UID.

20. The server of claim 15, wherein the processor is further configured with processor-executable instructions to perform operations such that the portion of the contact profile that is sent to the remote client device includes each of the set of contact addresses for each of the list of devices of the user.

21. The server of claim 15, wherein the processor is further configured with processor-executable instructions to perform operations such that the portion of the contact profile that is sent to the remote client device includes less than all contact addresses from the set of contact addresses for one or more of the list of devices of the user.

22. The server of claim 15, wherein the request includes a token that indicates privileges of the remote client device with respect to the contact profile, and wherein the processor is further configured with processor-executable instructions to perform operations such that determining the portion of the contact profile to send to the remote client device comprises determining the portion of the contact profile based on the token.

23. The server of claim 15, wherein the processor is further configured with processor-executable instructions to perform operations such that determining the portion of the contact profile to send to the remote client device comprises determining the portion of the contact profile based upon one or more privacy rules associated with the user.

24. The server of claim 15, wherein the processor is further configured with processor-executable instructions to perform operations comprising:

retrieving data messages associated with two or more different contact addresses from the contact profile, the two or more different contact addresses associated with different communication services; and

sending an aggregated version of the retrieved data messages associated with the two or more different contact addresses to the user.

25. The server of claim 24,

wherein the retrieved data messages include a set of cellular phone voicemail messages and a set of Voice over Internet Protocol (VoIP) voicemail messages, and

wherein the two or more different contact addresses include a cellular phone number and a VoIP identifier.

26. The server of claim 24,

wherein the retrieved data messages include a set of email messages, and

wherein the two or more different contact addresses include two or more different email addresses.

27. The server of claim 15, wherein the processor is further configured with processor-executable instructions to perform operations such that one or more contact addresses in the portion of the contact profile that is sent to the remote client device are masked so that the one or more contact addresses (i) can be recognized by software residing on the remote client device for communication session initiation attempts to the one or more contact addresses by the remote client device, and (ii) cannot be recognized by a given user of the remote client device.

28. The server of claim 15, wherein the processor is further configured with processor-executable instructions to perform operations such that, for each device in the list of devices, the set of contact addresses includes either (i) a single contact address through which to contact the device, or (ii) multiple contact addresses through which to contact the device.

29. A server, comprising:

means for maintaining a contact profile for a user, the contact profile including a universal identifier (UID) for the user and a list of devices through which to contact the user, each device in the list of devices being maintained in association with a device identifier, a device location descriptor and a set of contact addresses through which to contact the device;

means for receiving a request from a remote client device to send the contact profile to the remote client device;

means for determining a portion of the contact profile to send to the remote client device; and

means for sending the portion of the contact profile to the remote client device.

30. A non-transitory computer-readable medium containing instructions stored thereon, which, when executed by a server, cause the server to perform operations, the instructions comprising:

at least one instruction to cause the server to maintain a contact profile for a user, the contact profile including a universal identifier (UID) for the user and a list of devices through which to contact the user, each device in the list of devices being maintained in association with a device identifier, a device location descriptor and a set of contact addresses through which to contact the device;

at least one instruction to cause the server to receive a request from a remote client device to send the contact profile to the remote client device;

at least one instruction to cause the server to determine a portion of the contact profile to send to the remote client device; and

at least one instruction to cause the server to send the portion of the contact profile to the remote client device.