METHOD AND SYSTEMS FOR SYNCHRONIZING CONTACT INFORMATION

• US 20150339368A1
• Filed: 05/20/2014
• Published: 11/26/2015
• Est. Priority Date: 05/20/2014
• Status: Abandoned Application

• Current Assignee: Vonage Business Inc (Telefonaktiebolaget LM Ericsson)
• Original Assignee: Vonage Network LLC (Telefonaktiebolaget LM Ericsson)
• Inventors: Gruber, Alexander
• Application Number:
  US14/282,427
• Publication Number:
  US 20150339368A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Methods and systems for synchronizing contact information from multiple sources across multiple devices associated with a user are provided herein. In some embodiments, a method for synchronizing contact information from multiple sources across multiple devices associated with a user may include receiving a contact modification message from a first device to modify a contact in a cloud contact address book, where the cloud contact address book includes contact information for a plurality of contacts from one or more devices associated with a user; modifying the contact in the cloud contact address book based on modification information included in the contact modification message; identifying at least one device of the plurality of devices in which the contact is a native contact; and pushing the modified contact to the identified at least one device.

Claims

1. A computer implemented method for synchronizing contact information across multiple devices associated with a user, comprising:

receiving a contact modification message from a first device to modify a contact in a cloud contact address book, where the cloud contact address book includes contact information for a plurality of contacts from one or more devices associated with a user;

modifying the contact in the cloud address book based on modification information included in the contact modification message;

identifying at least one device of the one or more devices in which the contact is a native contact; and

pushing the modified contact to the identified at least one device.

2. The method of claim 1, wherein some of the plurality of contacts from a first device in the one or more devices are unique from some of the plurality of contacts from a second device in the one or more devices.

3. The method of claim 1, wherein at least some of the plurality of contacts stored in the cloud contact address book is owned by a third party application.

4. The method of claim 1, wherein identifying at least one device comprises:

determining, from metadata associated with the contact in the cloud contact address book, at least one source device identifier that uniquely identifies the at least one device on which the contact is a native contact.

5. The method of claim 1, wherein pushing the modified contact comprises:

determining, from metadata associated with the contact in the cloud address book, a contact identifier that uniquely identifies the modified contact; and

sending a message to the at least one identified device including the at least the contact identifier and the modification information.

6. The method of claim 1, wherein a native contact is a contact that is stored locally on a device of the one or more devices associated with the user.

7. A computer implemented method for updating a native contact on a device, wherein contact information associated with the native contact was modified in a cloud contact address book, comprising:

receiving a message indicating a change to the contact information associated with the native contact in the cloud contact address book, wherein the message includes a contact identifier that identifies the native contact;

requesting, using the contact identifier, modified contact information associated with the native contact from the cloud address book;

receiving the modified contact information; and

updating the native contact in a native address book on the device using the modified contact information.

8. The method of claim 7, wherein the native contact is owned by a third party application.

9. The method of claim 8, further comprising synchronizing the updated native contact with the third party application that owns the native contact.

10. A system for synchronizing contact information across multiple devices associated with a user, comprising a contact storage device that stores a cloud contact address book, wherein the cloud contact address book includes contact information for a plurality of contacts from one or more devices associated with the user;

and

a contact modification module configured to;

receive a contact modification message from a first device to modify a contact in the cloud contact address book;

modify the contact in the cloud contact address book based on modification information included in the contact modification message;

identify at least one device of the one or more devices in which the contact is a native contact; and

push the modified contact to the identified at least one device.

11. The system of claim 10 further comprising a contacts module configured to:

receive a message to update the native contact;

identify a contact identifier from the message;

request, using the contact identifier, contact information for the native contact from the cloud contact address book; and

update the native contact in a native address book on the at least one device.

12. The system of claim 10, wherein at least some of the plurality of contacts stored in the cloud contact address book are owned by a third party application.

13. The system of claim 10, wherein identifying at least one device comprises:

determining, from metadata associated with the contact in the cloud contact address book, at least one source device identifier that uniquely identifies the at least one device on which the contact is a native contact.

14. The system of claim 10, wherein pushing the modified contact comprises:

determining, from metadata associated with the contact in the cloud address book, a contact identifier that uniquely identifies the modified contact; and

sending a message to the at least one identified device including at least the contact identifier and the modification information.

15. A non-transitory computer readable medium for storing computer instructions that, when executed by at least one processor causes the at least one processor to perform a method for synchronizing contact information across multiple devices associated with a user, comprising:

receiving a contact modification message from a first device to modify a contact in a cloud contact address book, where the cloud contact address book includes contact information for a plurality of contacts from one or more devices associated with a user;

modifying the contact in the cloud contact address book based on modification information included in the contact modification message;

identifying at least one device of the one or more devices in which the contact is a native contact; and

pushing the modified contact to the identified at least one device.

16. The computer readable medium of claim 15, wherein one or more of the plurality of contacts from a first device in the one or more devices are unique from one or more of plurality of contacts from a second device in the one or more devices.

17. The computer readable medium of claim 15, wherein at least some the plurality of contacts stored in the cloud contact address book is owned by a third party application.

18. The computer readable medium of claim 15, wherein identifying at least one device comprises:

determining, from metadata associated with the contact in the cloud contact address book, at least one source device identifier that uniquely identifies the at least one device on which the contact is a native contact.

19. The computer readable medium of claim 15, wherein pushing the modified contact comprises:

determining, from metadata associated with the contact in the cloud address book, a contact identifier that uniquely identifies the modified contact; and

sending a message to the at least one identified device including at least the contact identifier and the modification information.

20. The computer readable medium of claim 15, wherein a native contact is a contact that is stored locally on a device of the one or more devices associated with the user.