System and Method for Mobile Data Synchronization

• US 20160330279A1
• Filed: 05/06/2016
• Published: 11/10/2016
• Est. Priority Date: 05/07/2015
• Status: Active Grant

• Current Assignee: Kodiak Networks (Motorola Solutions, Inc.)
• Original Assignee: Kodiak Networks (Motorola Solutions, Inc.)
• Inventors: Setti Nagaswamy Srinivasan, Bharat Ram, Patel, Krishnakant M., Kandula, Ramu, Vempati, Brahmananda R., Negalaguli, Harisha Mahabaleshwara, Ayyasamy, Ravi
• Granted Patent: US 10,609,138 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: H04L 51/224 providing notification on incoming messages, e.g. pushed notifications of received messages
• CPC Class Codes: H04L 51/42 Mailbox-related aspects, e.g. synchronisation of mailboxes
• 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/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04W 4/08 User group management

Abstract

An embodiment includes receiving, by a client on a client device, a data change notification. The data change notification indicates a change in data relating to the client at a client data store. The method further includes determining, by the client, a type of the data relating to the client changed at the client data store and determining, by the client, a data synchronization mechanism in accordance with the type of the data relating to the client changed at the client data store. Determining the data synchronization mechanism includes determining when to attempt, by the client, a data synchronization to synchronize data on the client device with the data relating to the client changed at the client data store.

Claims

1. A method comprising:

receiving, by a client on a client device, a data change notification, wherein the data change notification indicates a change in data relating to the client at a client data store;

determining, by the client, a type of the data relating to the client changed at the client data store; and

determining, by the client, a data synchronization mechanism in accordance with the type of the data relating to the client changed at the client data store, wherein determining the data synchronization mechanism comprises determining when to attempt, by the client, a data synchronization to synchronize data on the client device with the data relating to the client changed at the client data store.

2. The method of claim 1, wherein the data synchronization mechanism is a non-real-time data synchronization mechanism, and wherein the non-real-time data synchronization mechanism comprises:

determining, by the client, whether the client is running in a foreground of the client device or running in a background of the client device; and

attempting, by the client, to synchronize the data on the client device with the data relating to the client changed at the client data store when the client device is running in the foreground of the client device.

3. The method of claim 2, wherein the non-real-time data synchronization mechanism further comprises waiting, by the client, until the client is running in the foreground to attempt to synchronize the data on the client device with the data relating to the client changed at the client data store when the client device is running in the background of the client device.

4. The method of claim 1, wherein the type of the data relating to the client changed at the client data store is presence data, contact data, group management data, a push-to-X text message notification, a push-to-X multimedia message service notification, a push-to-talk (PTT) over cellular (PoC) instant personal alert, location tracking data, changes to PTT call in progress notification, a PTT call completed notification, or a combination thereof.

5. The method of claim 1, wherein the data synchronization mechanism is a real-time data synchronization mechanism, and wherein the real-time data synchronization mechanism comprises attempting, by the client, to synchronize the data on the client device with the data relating to the client changed at the client data store after the data change notification is received regardless of whether the client is running in a foreground of the client device or running in a background of the client device.

6. The method of claim 1, wherein different types of data synchronization mechanisms are selected for different types of data by a user operating the client device, a group administrator, a network administrator, a service operator, a standard, or a combination thereof.

7. The method of claim 1 further comprising:

determining, by the client device, whether the data change notification was received after a most recent successful data synchronization on the client device when the client transitions from running in a background of the client device to running in a foreground of the client device; and

attempting, by the client, to synchronize the data on the client device with the data relating to the client changed at the client data store when the data change notification was received after the most recent successful data synchronization on the client device.

8. The method of claim 7 further comprising not attempting, by the client, to synchronize the data on the client device with the data relating to the client changed at the client data store when the data change notification was not received after the most recent successful data synchronization on the client device and the client did not lose network connectivity after the most recent successful data synchronization on the client device.

9. The method of claim 1 further comprising:

losing, by the client, network connectivity for at least an interval of time; and

attempting, by the client, to synchronize data on the client device with data at the client data store when the client regains network connectivity after losing network connectivity for at least the interval of time.

10. The method of claim 1, wherein the client does not poll the client data store for changes in data relating to the client, and wherein the client is not required to maintain an active connection with the client data store for receiving changes in data relating to the client.

11. The method of claim 1, wherein the data change notification includes at least a portion of the data relating to the client changed at the client data store, wherein the client maintains a first archive of data for the type of the data relating to the client changed at the client data store, wherein the client data store maintains a second archive of data for the type of the data relating to the client changed at the client data store, and wherein the data synchronization mechanism is used, by the client, to synchronize the first archive of data with the second archive of data.

12. A method comprising:

receiving, by a notification server in a telecommunications services platform, a data change notification, wherein the data change notification indicates a change to data relating to a client at a client data store by one or more services provided by the telecommunications services platform;

maintaining, by the notification server, a data change notification queue for the client;

determining, by the notification server, a state of the data change notification queue; and

determining, by the notification server, whether to transmit the data change notification to the client in accordance with the state of the data change notification queue.

13. The method of claim 12 further comprising, transmitting, by the notification server, the data change notification to the client when the data change notification queue is in a no-data-pending state, wherein the data change notification queue transitions into the no-data-pending state when the client successfully synchronizes data with the client data store.

14. The method of claim 13 further comprising after transmitting the data change notification, transitioning the data change notification queue to a data-pending state.

15. The method of claim 14 further comprising:

receiving, by the notification server, one or more additional data change notifications while the data change notification queue is in a data-pending state, wherein the one or more additional data change notifications indicates one or more additional changes to data relating to the client at the client data store by the one or more services; and

enquequing, by the notification server, the one or more additional data change notifications until the client successfully synchronizes data with the client data store.

16. The method of claim 15 further comprising not transmitting, by the notification server, the one or more additional data change notifications while the data change notification queue is in the data-pending state.

17. The method of claim 12 further comprising:

ignoring, by the notification server, the data change notification when the data change notification queue is in a closed state, wherein the data change notification queue is in the closed state when the client loses network connectivity; and

transmitting, by the notification server, an initial data change notification to the client when the client regains network connectivity.

18. The method of claim 12 further comprising throttling, by the notification server, the data change notification in accordance with a location of the client and a network resource utilization map.

19. The method of claim 12, wherein determining, by the notification server, whether to transmit the data change notification to the client in accordance with the state of the data change notification queue comprises:

transmitting the data change notification to the client when the notification server determines no data change notifications have been transmitted to the client since a most recent time the client successfully synchronized data with the client data store; and

not transmitting the data change notification to the client when the notification server determines a previous data change notification has been transmitted to the client since the most recent time the client successfully synchronized data with the client data store.

20. A telecommunications services platform comprising:

a client data store storing data relating to a push-to-talk (PTT) client on a client device;

one or more processors; and

a computer readable storage medium storing programming for execution by the one or more processors, the programming including instructions to;

provide one or more PTT services to the PTT client; and

provide a notification server, wherein the notification server is configured to;

receive a data change notification indicating a change to the data relating to the PTT client by the one or more PTT services;

transmit the data change notification to the PTT client when the notification server determines no data change notifications have been transmitted to the PTT client since a most recent time the PTT client successfully synchronized data with the client data store; and

not transmit the data change notification to the PTT client when the notification server determines a previous data change notification has been transmitted to the PTT client since the most recent time the PTT client successfully synchronized data with the client data store.

21. The telecommunications services platform of claim 20 further comprising a location server tracking a geographic location of the PTT client, wherein the notification server is further configured to throttle the data change notification in accordance with the geographic location of the PTT client.

22. The telecommunications services platform of claim 20, wherein the programming includes further instructions to provide an analytics system, wherein the analytics system is configured to:

receive user activity reports from the one or more PTT services; and

maintain a network resources utilization map in accordance with the user activity reports, wherein the notification server is further configured to throttle the data change notification in accordance with the network resources utilization map.

23. The telecommunications services platform of claim 20 further comprising a mobile datasync gateway configured to provide access to the client data store by the PTT client.