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.
Legal claims defining the scope of protection, as filed with the USPTO.
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, wherein the type of the data relating to the client changed at the client data store is Push-to-talk (PTT) over cellular (PoC) presence data, PTT contact data, PTT group management data, a push-to-X text message notification, a push-to-X multimedia message service notification, a PTT instant personal alert, PTT location tracking data, changes to PTT call in progress notification, a PTT call completed notification, or a combination thereof; 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, wherein when the data synchronization mechanism is a non-real-time data synchronization mechanism, 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, 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.
2. The method of claim 1 , wherein when the data synchronization mechanism is a real-time data synchronization mechanism 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.
3. 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.
4. 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.
5. The method of claim 4 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.
6. 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.
7. 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.
8. 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.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
May 6, 2016
March 31, 2020
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.