Method of automatically replicating data objects between a mobile device and a server

• US 8,156,075 B2
• Filed: 12/12/2003
• Issued: 04/10/2012
• Est. Priority Date: 12/19/2002
• Status: Active Grant

• Current Assignee: Synchronoss Software Ireland Limited (Synchronoss Technologies Incorporated)
• Original Assignee: Critical Path Data Centre Limited
• Inventors: Greenwell, Thomas Ralph Edwards, Spence, Stephen Timothy, Stalker, Mark Colin
• Primary Examiner(s): Lu, Kuen S
• Assistant Examiner(s): Rayyan, Susan F
• Application Number:
  US10/539,863
• Publication Number:
  US 20060171523A1
• Time in Patent Office: 3,042 Days
• Field of Search: 707/748, 707/754, 707/653, 707/621
• US Class Current: 707/610
• CPC Class Codes: H04L 12/1485 Tariff-related aspects
• CPC Class Codes: H04L 67/01 Protocols
• 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/62 Establishing a time schedule for servicing the requests
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04W 4/00 Services specially adapted for wireless communication networks; Facilities therefor

Abstract

Network operators can control how data replication services use available bandwidth, in order to make the most efficient usage of that bandwidth, using parameters applied to a data object to be replicated. The parameters may be both time dependent and also relate to how urgently that object needs to be replicated. A change log lists all objects at the device and/or server to be replicated and the parameters then comprise a weight associated with each object that defines how urgently that object needs to be replicated; the weight of each object is then locally compared to a threshold at a given time and the outcome of the comparison determines whether the object is sent for replication or not at that time. This combination of weight and threshold gives a flexible way to control the timing of data replication and hence make the best use of bandwidth.

Claims

1. Method of automatically replicating data objects between a mobile device and a server, connected together via a wireless network, in which the timing of data replication across the network is determined by a network operator applying parameters that make efficient usage of network bandwidth;

comprising;

creating a change log that lists all objects at the device and/or server to be replicated;

applying, via said network operator, as a first of said parameters, a single weight associated with each object that defines how urgently that object needs to be replicated; and

applying, via said network operator, as a second of said parameters, a threshold that is a function of time, with the single weight of each object being locally compared to the threshold at a given time and the outcome of the comparison determining whether the object is sent for replication or not at that time;

wherein all criteria that are relevant to how urgently an object needs to be replicated are represented by the single weight associated with that object.

2. The method of claim 1 in which a connection is established at a given time if the weight of any object exceeds the threshold at that time.

3. The method of claim 1 in which the weight of an object at a given time is a function of one or more of the following:

(a) Direction of data replication (device to serves or server to device)

(b) Shelf life, defining the time or duration after which the object will be automatically deleted if still present in the change log

(c) Whether the object is overwritable

(d) Size in bytes

(e) Time entered into the change log

(f) Priority

(g) Time out interval

(h) Assigned time for replication

(i) User assignment of a non-default priority to a given object

(j) Memory available.

4. The method of claim 1 in which the network operator can cause the weight of an object to be altered at any time.

5. The method of claim 1 in which the network operator can cause the threshold to be altered at any time.

6. The method of claim 1 in which the threshold varies over time in such a way that efficient use is made of available bandwidth.

7. The method of claim 1 in which the threshold can vary over time in a different way for different groups of end-users, individual end-users or applications.

8. The method of claim 1 in which dynamic varying of the threshold can occur as cell or network loadings change.

9. The method of claim 1 in which dynamic varying of the threshold can occur to encourage uptake of a new data replication service.

10. The method of claim 1 in which the threshold can vary depending on one or more of the following:

(a) current time

(b) device roaming status

(c) cell or network loading

(d) time since last replication

(e) user tariff.

11. The method of claim 1 in which, if the weight of no object exceeds the threshold at a given time, the time interval that will elapse before the weight of any object exceeds the threshold is calculated and a timer set for that time interval.

12. The method of claim 11 in which the time interval is re-calculated if:

(a) a new object is added to the change log

(b) a new threshold is deployed

(c) the timer expires

(d) cell or network loading alters

(e) device memory falls below a predefined level

(f) the device detects that its roaming state changes

(g) a new application is activated on the device

(h) a network connection is terminated.

13. The method of claim 1 in which the end-user of the device can override default replication timing in respect of a specific object or type of object.

14. The method of claim 1 in which an object to be replicated is assigned a time limit by which time replication must occur.

15. The method of claim 14 in which the time limit is dynamic.

16. The method of claim 14 in which the time limit alters if memory on the device changes or if the device roams to a new network.

17. The method of claim 1 in which an object to be replicated is assigned a shelf life which defines a time or duration after which the object will be deleted automatically if not replicated.

18. The method of claim 1 in which different parameters enable the network operator to offer end-users different levels of data replication service, each associated with a different tariff.

19. The method of claim 1 in which, once a connection initiating object has been replicated, then further objects in a change log and pending replication are sent as well.

20. The method of claim 19 in which an opportunism threshold function determines the further objects that are sent.

21. The method of claim 20 in which the opportunism threshold changes if the device is on a roaming network.

22. The method of claim 21 in which the opportunism threshold changes depending on whether a cell loading threshold of the cell the device is located in is exceeded.

23. The method of claim 21 in which the opportunism threshold is applied consistently by device and server, with changes to the threshold communicated across the network.

24. The method of claim 21 in, which the network operator can vary the opportunism threshold.

25. The method of claim 1 in which the actual time of replication is a function of the state of the mobile device, the state of the network and the parameters.

26. A mobile device programmed with software that enables the device to replicate data to a server using the method of claim 1.

27. A server programmed with software that enables the server to replicate data to a mobile device using the method of claim 1.