System and method for synchronizing multiple calendars over wide area network

• US 6,457,062 B1
• Filed: 04/08/1999
• Issued: 09/24/2002
• Est. Priority Date: 04/08/1999
• Status: Expired due to Term

• Current Assignee: Access Company Limited
• Original Assignee: Palm, Inc. (TCL Technology Group Corp.)
• Inventors: Grillo, Peter, Pivowar, Alvin, Hanrahan, Steve
• Primary Examiner(s): Barot, Bharat
• Application Number:
  US09/289,764
• Time in Patent Office: 1,265 Days
• Field of Search: 709/200-203, 709/204-205, 709/213-214, 709/217-219, 709/248, 713/400
• US Class Current: 709/248
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: G06Q 10/109 Time management, e.g. calendars, reminders, meetings or time accounting

Abstract

A system and method are provided for sharing calendar data sets among a plurality of users. Included are a plurality of personal digital assistants, or PDA'"'"'s, each suitable for storing personal calendar data sets thereon. Further provided is a server for synchronizing server calendar data sets stored thereon with the personal calendar data sets stored on the PDA'"'"'s upon establishing communication therebetween. At least one communication link is adapted for establishing communication between the PDA'"'"'s and the server. By establishing such communication between the PDA'"'"'s and the server, the personal calendar data sets of different PDA'"'"'s may be synchronized.

Claims

1. A system for sharing calendars among a plurality of users comprising:

a plurality of portable data storage modules suitable for storing a plurality of personal calendar data sets thereon;

a server including calendar data sets stored thereon; and

a communication link between the portable data storage modules and the server for synchronizing the server calendar data sets with the personal calendar data sets in order to obtain the personal calendar data set of one portable data storage module on another portable data storage module, thereby synchronizing the personal calendar data sets between different portable data storage modules;

wherein the personal calendar data sets of each of the portable data storage modules has personal identification codes and the server calendar data sets of the server has server identification codes, wherein a map correlating between the personal identification codes and the server identification codes is stored on at least one of the portable data storage module, the server, and a computer in which the communication link is resident for identification purposes during synchronization of the personal calendar data sets and the server calendar data sets.

2. The system as recited in claim 1, wherein the communication link is resident in a client computer and is connected to the server via a network.

3. The system as recited in claim 2, wherein the network is at least one of the Internet and an intranet.

4. The system as recited in claim 1, wherein the communication link includes a link controller suitable for interfacing the portable data storage modules, and a client messenger in communication with the link controller and suitable for interfacing the server.

5. The system as recited in claim 4, wherein the client messenger is further suitable for interfacing local memory for synchronizing local calendar data sets stored thereon with the personal calendar data sets and the server calendar data sets.

6. The system as recited in claim 1, wherein the personal calendar data sets and the server calendar data sets each has three fields of information stored therewith including a name field, an identification field, and an index field for facilitating synchronization.

7. The system as recited in claim 1, wherein the map is stored on the portable data storage modules.

8. The system as recited in claim 1, wherein the synchronization of the personal calendar data sets of different portable data storage modules only occurs on personal calendar data sets specifically marked to be shared by including the server identification codes of the personal calendar data sets of other portable data storage modules.

9. The system as recited in claim 1, wherein the synchronization of the personal calendar data sets between different portable data storage modules only occurs on personal calendar data sets specifically marked to be shared.

10. The system as recited in claim 9, wherein a conflict occurs when a particular personal calendar data set of a first one of the portable data storage modules is synchronized with the server calendar data set before the particular personal calendar data set of a second one of the portable data storage modules is synchronized with the server calendar data set, and the particular personal calendar data sets of the first and second portable data storage modules are marked to be shared.

11. The system as recited in claim 10, wherein the conflict is resolved by replicating the particular personal calendar data set.

12. The system as recited in claim 10, wherein the conflict is resolved by synchronizing the particular personal calendar data set of the second portable data storage module with the server calendar data set.

13. The system as recited in claim 10, wherein the conflict is resolved by not synchronizing the particular personal calendar data set of the second portable data storage module with the server calendar data set.

14. The system as recited in claim 10, wherein the conflict is resolved by marking the particular personal calendar data set of the second portable data storage module and alerting a user of the conflict via a user interface.

15. A method for sharing calendars among a plurality of users comprising the operations of

storing a plurality of personal calendar data sets on a plurality of portable data storage modules;

establishing a communication link between the portable data storage modules and a server including calendar data sets stored thereon;

obtaining the personal calendar data set of one portable data storage module on another portable data storage module, thereby synchronizing the personal calendar data sets of different portable data storage modules via the server;

wherein the personal calendar data sets of each of the portable data storage modules has personal identification codes and the server calendar data sets of the server has server identification codes, wherein a map correlating between the personal identification codes and the server identification codes is stored on at least one of the portable data storage module, the server, and a computer in which the communication link is resident for identification purposes during synchronization of the personal calendar data sets and the server calendar data sets.

16. The method as recited in claim 15, wherein the data sets further include contact information.

17. The method as recited in claim 15, further comprising the operations of:

synchronizing the personal calendar data sets of the portable data storage modules with server calendar data sets stored on the server, whereby the personal calendar data set of one portable data storage module obtained on another portable data storage module.

18. The method as recited in claim 17, wherein the communication link is resident in a client computer and is connected to the server via a network.

19. The method as recited in claim 18, wherein the network is at least one of the Internet and an intranet.

20. The method as recited in claim 17, wherein the communication link includes a link controller suitable for interfacing the portable data storage modules, and a client messenger in communication with the link controller and suitable for interfacing the server.

21. The method as recited in claim 20, wherein the client messenger is further suitable for interfacing local memory for synchronizing local calendar data sets stored thereon with the personal calendar data sets and the server calendar data sets.

22. The method as recited in claim 17, wherein the personal calendar data sets and the server calendar data sets each has three fields of information stored therewith including a name field, an identification field, and an index field for facilitating synchronization.

23. The method as recited in claim 15, wherein the map is stored on the portable data storage modules.

24. The method as recited in claim 15, wherein the synchronization of the personal calendar data sets of different portable data storage modules only occurs on personal calendar data sets specifically marked to be shared by including the server identification codes of the personal calendar data sets of other portable data storage modules.

25. The method as recited in claim 17, wherein the synchronization of the personal calendar data sets between different portable data storage modules only occurs on personal calendar data sets specifically marked to be shared.

26. The method as recited in claim 25, wherein a conflict occurs when a particular personal calendar data set of a first one of the portable data storage modules is synchronized with the server calendar data set before the particular personal calendar data set of a second one of the portable data storage modules is synchronized with the server calendar data set, and the particular personal calendar data sets of the first and second portable data storage modules are marked to be shared.

27. The method as recited in claim 26, wherein the conflict is resolved by replicating the particular personal calendar data set.

28. The method as recited in claim 26, wherein the conflict is resolved by synchronizing the particular personal calendar data set of the second portable data storage module with the server calendar data set.

29. The method as recited in claim 26, wherein the conflict is resolved by not synchronizing the particular personal calendar data set of the second portable data storage module with the server calendar data set.

30. The method as recited in claim 26, wherein the conflict is resolved by marking the particular personal calendar data set of the second portable data storage module and alerting a user of the conflict via a user interface.

31. A computer program embodied on a computer readable medium for providing a communication link between a server and a portable data storage module which is capable of sharing calendars among a plurality of users comprising:

a code segment for synchronizing personal calendar data sets on a portable data storage module with server calendar data sets on a server; and

a code segment for sharing the personal calendar data sets on the portable data storage module with another portable data storage module via the server;

wherein the personal calendar data sets of each of the portable data storage modules has personal identification codes and the server calendar data sets of the server has server identification codes, wherein a map correlating between the personal identification codes and the server identification codes is stored on at least one of the portable data storage module, the server, and a computer in which the communication link is resident for identification purposes during synchronization of the personal calendar data sets and the server calendar data sets.

32. The computer program as recited in claim 31, wherein the data sets further include contact information.

33. The computer program as recited in claim 31, wherein the communication link is resident in a client computer and is connected to the server via a network.

34. The computer program as recited in claim 33, wherein the network is at least one of the Internet and an intranet.

35. The computer program as recited in claim 31, wherein the communication link includes a link controller suitable for interfacing the portable data storage modules, and a client messenger in communication with the link controller and suitable for interfacing the server.

36. The computer program as recited in claim 35, wherein the client messenger is further suitable for interfacing local memory for synchronizing local calendar data sets stored thereon with the personal calendar data sets and the server calendar data sets.

37. The computer program as recited in claim 31, wherein the personal calendar data sets and the server calendar data sets each has three fields of information stored therewith including a name field, an identification field, and an index field for facilitating synchronization.

38. The computer program as recited in claim 31, wherein the map is stored on the portable data storage modules.

39. The computer program as recited in claim 38, wherein the synchronization of the personal calendar data sets of different portable data storage modules only occurs on personal calendar data sets specifically marked to be shared by including the server identification codes of the personal calendar data sets of other portable data storage modules.

40. The computer program as recited in claim 31, wherein the synchronization of the personal calendar data sets between different portable data storage modules only occurs on personal calendar data sets specifically marked to be shared.

41. The computer program as recited in claim 40, wherein a conflict occurs when a particular personal calendar data set of a first one of the portable data storage modules is synchronized with the server calendar data set before the particular personal calendar data set of a second one of the portable data storage modules is synchronized with the server calendar data set, and the particular personal calendar data sets of the first and second portable data storage modules are marked to be shared.

42. The computer program as recited in claim 41, wherein the conflict is resolved by replicating the particular personal calendar data set.

43. The computer program as recited in claim 41, wherein the conflict is resolved by synchronizing the particular personal calendar data set of the second portable data storage module with the server calendar data set.

44. The computer program as recited in claim 41, wherein the conflict is resolved by not synchronizing the particular personal calendar data set of the second portable data storage module with the server calendar data set.

45. The computer program as recited in claim 41, wherein the conflict is resolved by marking the particular personal calendar data set of the second portable data storage module and alerting a user of the conflict via a user interface.