WO2008065482A1

WO2008065482A1 - System and method for synchronization

Info

Publication number: WO2008065482A1
Application number: PCT/IB2007/001853
Authority: WO
Original assignee: Lai, Josephine, Suk, Ying
Priority date: 2006-01-24
Filing date: 2007-01-18
Publication date: 2008-06-05

Abstract

A system and method for synchronizing data between users specified data in a mobile device and a centralized data storage server located remotely. The mobile device is linked to such data storage server using an embedded application. This synchronizing process can be performed automatically or manually executed by user each time. The application compares the data on mobile device with data on the centralized database server. It then determines which data is most recent and initiates an 'update data' command that updates the less recent data with the most recent data. When one device provides updated information to the database, information on all other user-registered devices will then be updated accordingly and promptly. The embedded application also scans and setup for other available network signals in the surrounding area such as Wi-Fi, cellular networks to extend the coverage area and to provide most efficient method for data transferring.

Description

SYSTEM AND METHOD FOR SYNCHRONIZATION

INVENTOR

QUACH₅ Robert Chi-Thanh, C-57 Cameron Street Toronto, Ontario M5T 2Hl Citizen of Canada

CLAIM OF PRIORITY

This patent application claims priority from provisional patent application, Ser. No. 60/761,354. filed on 1/24/06.

BACKGROUND

At present, mobile devices such as cell phones, smartphones, PDAs (personal

digital assistant), laptops are capable of wired/wirelessly transferring data between one

another.

For example, a calendar with schedules or document file on a laptop can be transferred to a smartphone or PDA.

However, if a user has two or more of these devices, they would need to synchronize the data (calendar or document file) for each separate device whenever there is a change or new file added. This is because the information is usually stored on local

memory of the mobile device or portable memory device. These devices can cause a significant limitation when transferring files due to non-compatible portable memory

devices among mobile units. Also, to exchange information via these devices, the user must be physically present with the devices. For example, if the mobile unit with the portable memory devices is lost, the information contained within is also lost. Thus, the user has no other option/methods to retrieve the require information.

Hence, the inventors have identified several end-user needs. There is a need to be

able to provide the most up-to-date information to all of the user's mobile devices utilizing the most efficient type of network signals. There is also a need to provide information transfer from a first mobile device to a second mobile device, for example, when changing devices. Furthermore, there is a need to retrieve information without having physical access to the mobile device.

SUMMARY OF THE INVENTION

In the preferred embodiment, the registered user ("the user") may be adding a new contact, updating or removing data on one of their computing devices such as a desktop personal computer, laptop, personal digital assistant (PDA), mobile phone, etc. that contains a program that manages contacts, appointments, notes, photos, music, etc. The data is not restricted to contacts; it can be any type of data on the mobile device (appointments, notes, photo, music, etc.)

The program on the device recognizes that a new contact has been added. The program initiates synchronization wirelessly over the carrier's network via the Internet gateway through the Internet to the company's synchronization server ("sync server"). Latest changes from the device are propagated to the sync server. The sync server then initiates synchronization with other registered devices in the user's profile. The sync server contacts the mobile devices using SMS gateway; SMS gateway is one of the possible mechanism to communicate withy the mobile device, other possible mechanism can be employed such as TCP/IP networks. The contacted device(s) then synchronizes with the sync server containing the latest update.

Another possible method to induce synchronization of registered device(s) is to log on to the company's website with the user's credentials. The user can then make changes to his/her profile, add/delete/modify contacts, appointment, photo, music, etc. using the web application. The web application notifies the sync server of the change(s). The sync server initiates the synchronization with all devices in the registered user's profiles. The sync server contacts the mobile device(s) using the SMS gateway. The contacted device(s) then synchronizes with the sync server containing the latest update.

Another possible is when the user, for example, buys a new device. The user obtains the company software from the user website and installs it onto the device. The user enters his/her credentials into the program on the devices and initiates a manual synchronization with the sync server. The sync server authenticates against the credential and recognizes a new device, and the device is added to the user's profile. The synchronization pushes all data (contact, appointment, photos, etc.) to the new device. The device is now up-to- date and ready to use.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1: Block diagram of a typical communication system for data synchronization between a mobile device and a remote data server.

Figure 2: Flowchart for network signal detection and connection

Figure 3 : Flowchart for synchronization details

Figure 4: Flowchart for scheduled synchronization

Figure 5: Flowchart for triggered synchronization

Figure 6: Flowchart for server record updated and trigger signal push to device DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS OF THE INVENTION

Figure 1 is a block diagram of an exemplary embodiment of the synchronizing system. The synchronizing system comprises a three-tier information system. The three- tier information system comprises database server(s) and an application server(s) (13) and distributed terminal workstations (10). In an embodiment, each terminal workstation (10) is a mobile computing device, which may be but is not limited to a personal digital assistant (PDA), a laptop computer, or a smart phone. The system may contain at least one application server. Each application server may comprise core and business logic of the communication system, including database management. The application server (13) processes what is input by users, and returns results of processing to users. The database server controls processing of data stored in a database located in the database server (13). Such processing may include reading, writing, deleting, modifying, and backup.

A communication base (11) provides a communication path (21) to each mobile computing device. The mobile computing device communicates with the communication base. The communication base (11) is also connected to the application servers (13) through a communication path (22). The communication path (22) may be either private or public. In addition, the communication path may or may not be wireless; that is, employ wireless communication. Each application server (13) is coupled to a local area network (LAN), which itself also connects with the database server. The LAN provides access to the Internet for the application servers and the computing devices. The mobile device therefore also has access to the Internet via the LAN, to any of the application servers, thru the communication path 21, and to the communication path 22. An alternative communication system could be used between the mobile computing device (10) and the base station (11). The alternative communication system is similar to the above-described typical communication system. However, in the alternative communication system, the mobile computing device is connected to the base station (11) using but not limited to a Ethernet card, a phone line, a coaxial cable, an electric wire or a combination of any of the above media. Through the LAN, the mobile computing device can access the application and database server (13).

The above-described typical and alternative communication systems are used as examples only. Many variations of the systems described, and even different types of systems, can also be employed to incorporate the data synchronizing system and to practice the claimed method of the present invention. For example, the claimed subject matter can be employed in a LAN-based data server configuration. It should also be apparent to one with skill in the art that the disclosed method can be advantageously deployed within almost any communication or another type of system ih which either bandwidth and/or device memory is an issue. Furthermore, the application is not limited to systems that employ wireless communication links, but the disclosed methods provide significant advantages in a wireless context.

Figure 2 is a flowchart showing an exemplary embodiment of a method for detecting and connecting to preferred available network. In an embodiment, a user predefines his preference for network connection methods. The connection module checks for available connection interfaces in the device. Based on user predefined prefer communication method list, the device searches for available network signals in the surrounding area. A connection module selects the type of connection method based on user's pre-defined preferences or default settings.

Figure 3 is a flowchart showing an exemplary embodiment of a synchronization sequence. The application tries to establish the connection using a method such as the method illustrated in Figure 2. After the network connection is established, the device record ID with check flag and user ID are packaged into a dataset and send to the host system. The host system will compare the data store in the device and the host system database. If there is any data not in sync, the synchronize process will start and process in a secure encrypted channel. The sequence will be complete after all the date between the mobile computing device and the host system is identical.

Figure 4 is a flowchart showing an exemplary embodiment of a scheduled synchronization process. User predefine a prefer schedule (e.g. date and/or time) to perform the synchronization function. The schedule is stored in the user device memory. The application may contain a monitoring module. The monitoring module may run as a background process. The monitoring module may check whether the current date and time matches the user predefined schedule. When the current date and time matches the user predefined schedule, the application then initializes a synchronization sequence, such as the sequence illustrated in Figure 3.

Figure 5 is a flowchart showing an exemplary embodiment of a method for synchronizing data between mobile computing device and the host system when data is changed in the mobile computing device. The application may contain a monitoring module. The monitoring module may run as a background process. The monitoring module may check continuously to see if any data being changed on the mobile computing device. The data changes could be a result of new data entry, modify existing data or deleting existing data. This kind of changes could be triggered manually or

automatically. When any data is changed, the application will initialize a synchronization

sequence, such as the sequence illustrated in Figure 3.

Figure 6 is a flowchart showing an exemplary embodiment of a method for host system date records updates and triggering a signal push to the mobile computing device. A data record in the host system may be changed by the user. When a data record is

changed in the host system, the host system will retrieve the list of registered device(s) based on the user ID. For each device on the list, the host system will send a "Triggered- sync" command to the device. This command may be captured by the monitoring

module running on the mobile computing device described in Figure 5. The sequence will stop after a command send to all registered devices.

While the above invention has been described with reference to certain preferred embodiments, the scope of the present invention is not limited to these embodiments. One skilled in the art may find variations of these preferred embodiments which, nevertheless, fall within the spirit of the present invention, whose scope is defined by the claims set forth below

Claims

We claim:

1. A method of synchronizing data between mobile device(s) and a remote data storage unit comprising: a. Accessing a network with the mobile device(s); and b. Transferring data to and from at least one remote data storage device to said mobile device(s).

2. A method as in claim 1 , whereas the mobile device(s) is wireless.

3. A method as in claim 1, whereas the accessing the network is through a docking port.

4. A method as in claim 1 , whereas the accessing the network requires a secure logon.

5. A method as in claim 1 , whereas the network is a secure connection.

6. A method as in claim 1 , whereas the network is Internet.

7. A method as in claim 1 , whereas the network connection is wireless.

8. A method as in claim 1 , whereas the network connection is facilitated through wifi.

9. A method as in claim 1 , whereas the network connection is facilitated through a cellular network.

10. A method as in claim 1 , whereas the mobile device is a PDA, cellular phone, or wireless portable computer.

11. A method as in claim 1, whereas the remote data storage device is at least one centralized data repository server.

12. A method as in claim 1, whereas the remote data storage device is at least one remote personal computer.

13. A method as in claim 1, whereas the synchronization can include uploading or downloading of data.

14. A method as in claim 1, whereas the synchronization is automatically initiated periodically.

15. A method as in claim 1, whereas the synchronization is predetermined by the user.

16. A method as in claim 1, whereas the synchronization is manually initiated by the user.

17. A method as in claim I₅ whereas the synchronization may be accomplished onto a new device.

18. A method as in claim 1, whereas the synchronization may be accomplished onto a new device once an existing device is lost.

19. A method as in claim 1, whereas the synchronization intervals can be adjusted by the user.

20. A method as in claim 1, whereas said user is prompted to select device(s) to be synchronized with said data.

21. A method as in claim 1, whereas said user is prompted to transfer data to other device(s) to be synchronized.

22. A method of synchronizing data between mobile device(s) and a repository server comprising: a. Utilizing at least one application server to facilitate the transfer of data from the mobile device(s) to at least one remote centralized data repository server; b. Utilizing a wired/wireless connection to via a wide area network or local area network; c. Transferring data between the mobile device(s) to the remote data repository server; d. Receiving data from the remote data storage; e. Continuously updating the data within the mobile device(s).

23. A method of synchronizing data between mobile device(s) and a repository server comprising: a. Utilizing at least one application server to facilitate the transfer of data from the mobile device(s) to at least one remote centralized data repository server; b. Transferring data between the mobile device to the remote data repository server; c. Ensuring security utilizing encrypted data packets in the transmission; d. Receiving data between the remote data storage; and e. Continuously updating the data within the mobile device(s).

24. A method of synchronizing data between mobile device(s) and a repository server comprising: a. Utilizing an application server to facilitate the transfer of data from the mobile device(s) to the remote centralized data repository server; b. Transferring data between the mobile device to the remote data repository server; c. Ensuring security utilizing encrypted data packets in the transmission; d. Receiving data between the remote data storage; and e. Continuously updating the data within designated mobile device(s) validated by an embedded encryption key within said target mobile device(s).

25. A method of synchronizing data between at least one mobile device and a repository server comprising: a. Utilizing at least one application server to facilitate the transfer of data from a primary mobile device to at least one remote centralized data repository server; b. Utilizing a wired/wireless connection to via a wide area network or local area network; c. Transferring data between the mobile device to the remote data repository server; d. Receiving data between the remote data storage; e. Continuously updating the data within the selected data receiving slave mobile device(s).

26. A method as in claim 25, whereas the user may interchange the designated primary mobile device.

27. An apparatus to facilitate the synchronization data between mobile device(s) and a remote data storage unit comprising: a. a network to facilitate connectivity with the mobile device(s) and at least one remote data storage device; and b. Transferring data to and from at least one remote data storage device.

28. An apparatus as in claim 27, whereas the mobile device(s) is wireless.

29. An apparatus as in claim 27, whereas the accessing the network is through a docking port.

30. An apparatus as in claim 27, whereas the accessing the network requires a secure logon.

31. An apparatus as in claim 27, whereas the network is a secure connection.

32. An apparatus as in claim 27, whereas the network is internet.

33. An apparatus as in claim 27, whereas the network connection is wireless

34. An apparatus as in claim 27, whereas the network connection is facilitated through wifi.

35. An apparatus as in claim 27, whereas the network connection is facilitated through a cellular network.

36. An apparatus as in claim 27, whereas the mobile device is a PDA, cellular phone, or wireless portable computer.

37. An apparatus as in claim 27, whereas the remote data storage device is at least one centralized data repository server.

38. An apparatus as in claim 27, whereas the remote data storage device is at least one remote personal computer.

39. An apparatus as in claim 27, whereas the synchronization can include uploading or downloading of data.

40. An apparatus as in claim 27, whereas the synchronization is automatically initiated periodically.

41. An apparatus as in claim 27, whereas the synchronization is predetermined by the user.

42. An apparatus as in claim 27, whereas the synchronization is manually initiated by the user.

43. An apparatus as in claim 27, whereas the synchronization may be accomplished onto a new device.

44. A method as in claim 27, whereas the synchronization may be accomplished onto a new device once an existing device is lost.

45. An apparatus as in claim 27, whereas the synchronization intervals can be adjusted by the user.

46. An apparatus as in claim 27, whereas said user is prompted to select device(s) to be synchronized with said data.

47. An apparatus as in claim 27, whereas said user is prompted to transfer data to other device(s) to be synchronized.

48. An apparatus to facilitate the synchronization data between mobile device(s) and a remote data storage unit comprising: a. At least one application server to facilitate the transfer of data from the mobile device(s) to the remote centralized data repository server; b. a wired connection to via a wide area network or local area network; c. data is transferred between the mobile device(s) to the remote data repository server; d. said data is received by at least one remote data storage; e. data is continuously updated on said mobile device(s).

49. An apparatus to facilitate the synchronization data between mobile device(s) and a remote data storage unit comprising: a. At least one application server to facilitate the transfer of data from the mobile device(s) to the remote centralized data repository server; b. Data is transferred wirelessly between the mobile device to the remote data repository server; c. Security is added to said data utilizing encrypted data packets in the transmission; d. Data is received between at least one remote data storage; and e. data is continuously updated on said mobile device(s).

50. An apparatus to facilitate the synchronization data between mobile device(s) and a remote data storage unit comprising: a. At least one application server to facilitate the transfer of data from the mobile device(s) to the remote centralized data repository server; • b. Data is transferred wirelessly between the mobile device to the remote data repository server; c. Security is added to said data utilizing encrypted data packets in the transmission; d. Data is received between at least one remote data storage; and e. data is continuously updated on said mobile device(s) validated by an embedded encryption key within said target mobile device(s).

51. An apparatus to facilitate the synchronization data between mobile device(s) and a remote data storage unit comprising: a. At least one application server to facilitate the transfer of data from the primary mobile device(s) to the remote centralized data repository server; b. Data is transferred wirelessly between the mobile device to the remote data repository server; c. Security is added to said data utilizing encrypted data packets in the transmission; d. Data is received between at least one remote data storage; and e. data is continuously updated on said slave mobile device(s).

52. An apparatus as in claim 51, whereas the user may interchange the designated primary mobile device.