# Patent

## Title
Background synchronization

## Abstract

Systems, methods and computer program products for determining a schedule for synchronizing a server and a client are described herein. The method operates by tracking user usage of the client to develop usage patterns. A sync schedule is generated using the usage patterns, where the sync schedule enhances at least one of sync usefulness and sync transparency. The server and client are synchronized according to the sync schedule. More particularly, a sync fitness measure for an interval t is determined. The sync fitness measure is based on at least one of (a) sync transparency; and (b) sync usefulness. It is determined whether the sync fitness measure satisfies a threshold. If the sync fitness measure satisfies the threshold, then the server and client are synchronized during interval t.

## Background
CROSS REFERENCE TO RELATED APPLICATIONS
This application claims benefit as a continuation to U.S. patent application Ser. No. 11/790,038, filed Apr. 23, 2007, which issued as U.S. Pat. No. 8,060,653 on Nov. 15, 2011, entitled “Background Synchronization,” this application hereby incorporated herein by reference as if fully set forth herein.


BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention is generally directed to synchronization between clients and servers in a computing environment.
2. Background Art
FIG. 1 illustrates a computing environment 102 that includes a server 104 and a client 106 which communication via any known means, such as the Internet 110 (in practice, a plurality of servers 104 and clients 106 may operate in the computing environment 102). From time to time, client 106 synchronizes its state (data, applications, etc.) with server 104.
For example, according to the AVANTGO service (www.avantgo.com) available from iAnywhere Solutions, Inc., a Sybase company, client 106 receives content from one or more web sites 108 when it syncs with server 104. More particularly, server 104 retrieves data from web sites 108 corresponding to channels to which client 106 is subscribed. During a sync operation, server 104 transfers such data to client 106 via the Internet 110. (In an embodiment, as shown in the example of FIG. 1, server 104 and web sites 108 communicate with each other, and the client 106 and the server 104 communicate with each other, but the client 106 does not directly communicate with web sites 108. Instead, client 106 receives content from web sites 108 via server 104.)
In the past, sync operations usually took place when the client 106 was in a cradle connected to a computer via a wired connection, which was in turn connected to the Internet 110 via another wired connection.
Now, a multitude of well known client devices exist with functionality to wirelessly connect to the Internet. With such client devices, synchronizations can occur at any time.
Synchronization operations demand substantial computer and network resources, and often require a non-trivial amount of time to complete. A user's experience is diminished if a sync occurs while the user is trying to use the client device.
Also, by definition, synchronizations are performed to provide the user with up-to-date information when he is using the client device. The usefulness of a sync is diminished if the period between when the sync is performed, and when the user next uses the client device, is great.
Accordingly, what are needed are improved approaches for performing syncs between clients and servers.
BRIEF SUMMARY OF THE INVENTION
The present invention is directed to systems, methods and computer program products for determining a schedule for synchronizing a server and a client.
In an embodiment, the invention operates by tracking user usage of the client to develop usage patterns. A sync schedule is generated using the usage patterns, where the sync schedule enhances at least one of sync usefulness and sync transparency. The server and client are synchronized according to the sync schedule.
More particularly, the invention determines a sync fitness measure for an interval t. The sync fitness measure is based on at least one of (a) sync transparency; and (b) sync usefulness. The invention determines whether the sync fitness measure satisfies a threshold. If the sync fitness measure satisfies the threshold, then the server and client are synchronized during interval t.
Further features and advantages of the present invention, as well as the structure and operation of various embodiments thereof, are described in detail below with reference to the accompanying drawings. It is noted that the invention is not limited to the specific embodiments described herein. Such embodiments are presented herein for illustrative purposes only. Additional embodiments will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein.



BRIEF DESCRIPTION OF THE DRAWINGS/FIGURES
The accompanying drawings, which are incorporated herein and form part of the specification, illustrate the present invention and, together with the description, further serve to explain the principles of the invention and to enable a person skilled in the relevant art(s) to make and use the invention.
FIG. 1 illustrates an example computing environment according to an embodiment of the invention.
FIG. 2 is an example timeline used to illustrate issues associated with synchronizing a client with a server.
FIG. 3 is a flowchart representing a scheduled sync process according to an embodiment of the invention.
FIG. 4 is a flowchart representing an adaptive sync process according to an embodiment of the invention.
FIG. 5 is a flowchart illustrating functional details of the adaptive sync process, according to an embodiment of the invention.
FIGS. 6-9 are expressions for generating a sync fitness measure that is used in the adaptive sync process for determining whether a sync should take place in a given time interval, according to an embodiment of the invention.
FIGS. 10-12 are graphs illustrating advantages in using adaptive algorithms to generate PH(t) (probability that a client will be inactive at time t) and PU(t) (probability that a user will be accessing data in a client at time t), according to an embodiment of the invention.
FIG. 13 illustrates an example computer useful for implementing components of the invention.



The features and advantages of the present invention will become more apparent from the detailed description set forth below when taken in conjunction with the drawings. In the drawings, like reference numbers generally indicate identical, functionally similar, and/or structurally similar elements. Generally, the drawing in which an element first appears is indicated by the leftmost digit(s) in the corresponding reference number.
DETAILED DESCRIPTION OF THE INVENTION
1. Overview of the Invention
The present invention is directed to systems, methods and computer program products for synchronizing a client with a server such that (1) the sync is transparent to the user; and (2) usefulness of the sync is enhanced.
The invention shall be described with reference to the example computing environment 102 shown in FIG. 1, which is provided solely for purposes of illustration, and not limitation. Computing environment 102 includes a server 104 and a client 106, which are connected via any known means, such as but not limited to the Internet 110. Although only a single server 104 and client 106 are shown in FIG. 1, in practice computing environment 102 may include any number of servers 104 and clients 106.
According to an embodiment, client 106 includes a control (or system) module 112, a user interface 114 and a storage module 116. The storage module 116 includes data 118. It is noted that data 118 may represent information, applications, graphics, video, audio or any other object capable of being stored in a computer useable medium.
In an embodiment, during a sync, server 104 transmits information from websites 108 to client 106. Such websites 108 correspond to channels to which client 106 is subscribed. The information is stored in storage module 116 (represented as data 118). Thereafter, a user of client 106 can access data 118 via user interface 114 to surf such channels in an off-line browsing mode. Such functionality is provided by the AVANTGO service (www.avantgo.com) available from iAnywhere Solutions, Inc., a Sybase company. It is noted that the invention is not limited to this example AVANTGO embodiment. Instead, the invention is applicable to any client/server syncing of any type of data from any source.
According to the invention, syncs between client 106 and server 104 are scheduled so as to enhance a user's experience while working with client 106. In particular, syncs are scheduled to enhance either or both of the following factors: (1) sync transparency; and (2) sync usefulness.
Sync transparency is directed to reducing the impact of the sync on the user. Consider the example timeline 202 shown in FIG. 2. Period 204 denotes a period during which the client 106 is inactive. In other words, period 204 is a period during which client 106 is not being used by the user (for example, the client 106 may be holstered). Period 206 denotes a period during which the client 106 is active. In other words, during period 206, the user is using the client 106. Or, more particularly in some embodiments, during period 206, the user is accessing data 118 in client 106 via user interface 114. Other definitions/implementations of active/inactive will be apparent to persons skilled in the relevant art, and are within the scope and spirit of the present invention. For example, in an embodiment, active/inactive may depend on whether a particular application is being used in client 106.
According to embodiments of the invention, it is preferred to perform the sync while the client 106 is inactive (i.e., during period 204). Thus, it is preferred to perform the sync at times t1 or t2. By performing the sync in the background, the sync is not visible to the user. In other words, the sync is transparent to the user. In contrast, if the sync is performed while the client 106 is active, such as at time t4, then the sync will interfere with the user's work as it will negatively impact the performance of client 106.
Sync usefulness is directed to scheduling the sync so as to better ensure that the data 118 is current when the user next wishes to access the data 118 via user interface 114 or some other means. Consider again the example timeline 202 in FIG. 2. According to embodiments of the invention, it is better to perform the sync at time t2, as opposed to time t1. By doing so, the data 118 is more up-to-date when the user next wishes to access the data 118 at time t3.
For the same reason, it might be useful to perform the sync at time t4. In other words, to provide the user with the most up-to-date information, it might be useful to perform the sync during the period 206 that the client 106 is active. However, doing so would make, the sync visible to the user and would, therefore, negatively impact the user's experience while working with client 106. Embodiments of the invention consider these factors when scheduling when syncs should occur.
2. Scheduled Synchronization Embodiment
FIG. 3 illustrates a flowchart 302 representing a scheduled synchronization process according to an embodiment of the invention.
In step 304, the user enters criteria for the sync. Such criteria defines when syncs are to take place. For example, criteria may be “Sync at 8 am every day,” or “Sync when the device has been idle for 1 hour.” Other such criteria will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein.
In step 306, control module 112 of client 106 determines whether the criteria is satisfied. If not, then in step 308 control module 112 waits and, after a predetermined time period (the length of which is implementation dependent), returns to step 306.
Otherwise, if it is determined in step 306 that the criteria is satisfied, then step 310 is performed. In step 310, control module 112 generates a random number.
In step 312, control module 112 waits for a time period equal to t plus or minus the random number. The value of t is implementation dependent, and in embodiments may be set by the user or administrator. Whether the random number is added or subjected from t is also implementation dependent. After the time period elapses, step 314 is performed.
In step 314, control module 112 initiates a sync between the client 106 and the server 104.
It is noted that steps 310 and 312 are optional. The purpose of steps 310 and 312 is to prevent a large number of clients 106 from attempting to sync with server 104 at the same time (this could negatively impact network and server performance). By waiting some time period that is set using a random number, it is possible to stagger in time syncs with a great number of clients 106, thereby enhancing network and server performance.
3. Adaptive Synchronization Embodiment
FIG. 4 illustrates a flowchart 402 representing an adaptive synchronization process according to an embodiment of the invention.
According to the adaptive synchronization process 402, the client 106 automatically and intelligently schedules syncs with the server 104. Benefits include:

    
    
        A simplified user experience which adapts a schedule without requiring user intervention.
        Reduced visibility of synchronizations, meaning the user will not see the length of time associated with synchronizations.
        Enhanced sync usefulness, meaning the data 118 will be more up-to-date when the user next wishes to access the data 118 on the client 106.
    
    


The adaptive synchronization process 402 tracks user actions to develop patterns which can be expected to govern the actions of a user at a later time. Using the patterns that have been observed over time, the best interval for synchronization is chosen. The adaptive synchronization process 402 tracks (1) the probability that the client device 106 will be active or inactive in a given interval; and (2) the probability that the user will access the data 118 in client 106 in a given interval. The two probabilities, when tracked, provide sufficient information to determine a fitness measure for each interval. This measure determines whether synchronization in a given interval would be useful and whether it would be unlikely to be seen by the user.
Referring now to FIG. 4, in step 404 the control module 112 tracks user usage of client 106, and develops usage patterns. In particular, control module 112 tracks when client device 106 is inactive (i.e., not being used at all by user, such as when it is holstered), and active (i.e., when it is being used by user, or might be being used by user, such as when it is not holstered). Also, control module 112 tracks when the user is accessing data 118 via user interface 114 or some other means. Well known client devices, such as but not limited to BLACKBERRIES, PALM devices and POCKETPC devices, provide well known interfaces for tracking such activities.
With such usage information, control module 112 determines the probability PH that the client 106 is holstered (i.e., inactive) in any given interval during the day, and the probability PU that the user will be accessing data 118 in any given interval during the day. In an embodiment, each interval is 15 minutes, and accordingly there are 96 intervals each day. In an embodiment, intervals are numbered from 0 to 95, or 1 to 96. Embodiments for determining PH and PU are described below in Section 5.
In step 408, control module 112 determines a schedule for synchronizing client 106 with server 104 such that (1) the sync is transparent to the user; and (2) usefulness of the sync is enhanced. In embodiments, factor (1) is given more weight than factor (2), or vice versa. In embodiments, only factor (1) is considered. In other embodiments, only factor (2) is considered.
In step 410, syncs are performed according to the schedule developed in step 408.
An embodiment for performing steps 408 and 410 (collectively indicated as 406 in FIG. 4) shall now be described with reference to flowchart 502 in FIG. 5.
In step 504, control module 112 determines the sync fitness measure E(t) for the current time interval. The sync fitness measure E(t) is an indication of whether the sync should be performed in the current time interval. The larger E(t) is, the greater the likelihood that a sync will occur during the current time interval.
An embodiment for generating the sync fitness measure E(t) is described below in Section 4.
In step 510, control module 112 determines whether the sync fitness measure E(t) is greater than or equal to a threshold. The value of the threshold is implementation dependent, and in embodiments may be user or administrator adjustable.
If the sync fitness measure E(t) is not greater than or equal to the threshold, then the control module 112 in step 512 waits for the next time interval, at which time it will return to step 504.
If the sync fitness measure E(t) is greater than or equal to the threshold, then step 514 is performed. In step 514, control module 112 initiates a sync between client 106 and server 104.
4. Embodiments for Generating the Sync Fitness Measure E(t)
In an embodiment, the sync fitness measure E(t) is based on two factors: (1) how useful an update in the current interval will be to the user (sync usefulness; see 508 in FIG. 5); and (2) how likely it is that a sync in the current interval will not disturb the user (sync transparency; see 506 in FIG. 5).
The first factor is represented as E1(t), an embodiment of which is shown in FIG. 6. E1(t) has a first component 604 and a second component 606.
The first component 604 is a representation of how old the data 118 will be when it is next accessed by the user of client 106. In essence, the first component 604 is a measure of the length of time between the current interval and the closest next interval of major usage of the data 118 by the user.
In FIG. 6, t is the current interval, and t1 is the closest (in time) next interval of major usage of the data 118 by the user. MAXtime is equal to the number of intervals in a day. In an embodiment, MAXtime is equal to 96, and the intervals are numbered from 0 to 95 or 1 to 96. Thus, t, t1, etc., are each equal to 0 to 95 or 1 to 96, depending on the numbering scheme used.
If the difference t−t1 is small, then the time period between the current interval and the next interval of major data usage is small. Accordingly, if the difference t−t1 is small, then it would be useful to sync during the current interval, since it is likely that the user will soon be accessing, the data 118 via user interface 114 (thus, the data 118 will be current when it is accessed by the user if the sync took place during the current interval). This is reflected in the first component 604 of FIG. 6, where the absolute value of difference t−t1 is divided by MAXtime, and then this normalized value is subtracted from 1.
In contrast, if the difference t−t1 is large, then the time period between the current interval and the next interval of major data usage is great. Accordingly, if the difference t−t1 is large, then it would not be useful to sync during the current interval, since it is not likely that the user will soon be accessing the data 118 via user interface 114 (thus, the data 118 will be old when it is accessed by the user if the sync took place during the current interval).
FIG. 7 illustrates an embodiment for calculating tj, which as noted above is equal to the closest (in time) next interval of major usage of the data 118 by the user. PU(j) is the probability that data 118 will be accessed by the user via user interface 114 during interval j. According to the expression 702 in FIG. 7, the interval that has a usage probability PU greater than a threshold β, and that is closest in time to the current interval (determined using the minimum, or min, function) is identified and returned as t1.
Referring again to FIG. 6, the second component 606 of E1(t) is a representation of how usefulness is being lost in delaying the sync. Lost usefulness is determined by summing the usage probabilities PU for the intervals from t0 (the last interval where a sync took place) to just before the current interval (i.e., interval t−1). The second component 606 is subtracted from the first component 604 to form E1(t). Thus, the greater the second component 606 (that is, the more usefulness was lost by delaying the sync to the current interval), the less likely the sync will take place in the current interval. The second component 606 acts to balance the first 604 by making it less likely to sync if too much usage has been missed by not syncing earlier. This helps to push syncs forward and away from intervals when the user is actually using the client 106.
As indicated in FIG. 6, α1 and α2 are weights to control the importance of the two components 604 and 606.
FIG. 8 illustrates an expression 802 corresponding to the second factor E2(t) upon which E(t) is based, specifically, how likely it is that a sync in the current interval will not disturb the user's use of the client 106 (sync transparency). This expression 802 acts to ensure that syncs are more likely to occur in the intervals when the user does not need to use the client 106. Accordingly, E2(t) is equal to the probability that the client 106 will be inactive (for example, holstered) during the current interval t.
The sync fitness measure E(t) is represented by expression 902 in FIG. 9, and is the weighted sum of E1(t) and E2(t). The weights enable these factors to be emphasized or deemphasized in an implementation dependent manner.
As noted above, the larger E(t) is, the greater the likelihood that a sync will occur during the current time interval. Specifically, if E(t) of the current interval is greater than or equal to a threshold, then the sync is performed in the current interval (see steps 510 and 514 of FIG. 5).
5. Embodiments for Determining PH(t) and PU(t)
As described above, PH(t) is the probability that the client 106 will be inactive (holstered or otherwise inactive) during interval t. PU(t) is the probability that the user will be accessing the data 118 in the client 106 during interval t.
PH(t) and PU(t) can be determined by control module 112 in a number of ways. For example, an averaging method can be used to determine PH(t) and PU(t). A number of averaging methods exist. According to one approach, the control module 112 collects samples during each interval for a number of days. Assume, for example, that during interval 25, the client 112 was inactive 8 out of 10 days. According to this approach, PH(25) would be equal to 80%. Also assume, for example, that during interval 25 and for those same 10 days, the user had accessed data 118 in client 106 only once. Accordingly, PU(25) would be equal to 10%. PH(t) and PU(t) could be adjusted each day according to that day's samples.
There are many other approaches for determining PH(t) and PU(t), many of which are well known, and the scope of the present invention includes all of those well known approaches.
Additional approaches are also within the scope and spirit of the present invention. A novel and unobvious embodiment of the invention for generating PH(t) and PU(t) shall now be described.
5.1 Probability Estimation
According to an embodiment, an adaptive algorithm is used to generate PH(t) and PU(t).
The goal of many adaptive algorithms is to evolve a specific solution over time. Preferably, any adaptive algorithm used with the present invention should also converge over time. With such adaptive algorithm the same kind of annealing that is commonly used is not directly applicable since usage patterns can change with time and the estimates (PH(t) and PU(t)) are expected to change with them. Annealing is still partially applicable with the invention since it acts to add noise resistance to the data which naturally is highly volatile. For these reasons, the algorithm will preferably employ a kind of partial annealing to harden the estimation when it is undergoing stochastic noise and loosen when it observes changes in patterns which are reinforced over multiple observations. According to an embodiment, a recurrence relation, Δn,t, is used to control the proportion of the observed probability that will be integrated into the estimation. This relation is defined as

Δn,t=ωΔn-1,t+(1−ω)(*(t)+n-1(t)),

where P*(t) represents the observed probability, Pn(t) represents the probability estimation for iteration n and 0≦ω≦1 is a scaling factor. Using this Δ-factor the probability estimate Pn(t) is updated as

n(t)=|Δn,t|*(t)+(1−|Δn,t|)n-1(t).

Using this definition of Δn significantly improves the resistance of the estimation to the noisy data, as can be seen in FIG. 10, while still being able to adapt quickly to the behavioral changes in the data.
The advantages of this adaptive algorithm are apparent when compared with an averaging method over a short interval. Firstly, the adaptive scheduling method needs to store information for two or more intervals per hour to allow it to be effective while an average-based method would need to store more information about the series of previous observations to obtain similar results.
An averaging method also lacks the ability to dampen the noise to the extent demonstrated by the adaptive algorithm. Averaging methods are also slower in adaptation for comparable noise reduction, requiring around ten-times the number of observations required to adapt using the adaptive algorithm.
5.2 Improving Estimation
The Δ-factor described above still contains a high level of variability. This is due in part to the fact that small and large changes are treated linearly. Since small changes can vary the estimation of PH(t) and PU(t) widely, the adaptive algorithm in an alternative embodiment includes a method of exaggerating the differences between small and large changes, to lessen the impact of smaller changes which can accumulate over time and introduce large amounts of noise in the estimate. Using the square of the Δ-factor as the update rate decreases, the impact of small variations has the added problem of making the estimation very slow to respond to legitimate behavioral changes. This new update rate, Δ*n,t is defined as

Δ*n,t=sgn(Δn,t),Δn,t,

where sgn(•) denotes the sign of the term. It is important to note that without the sgn-term variability would compound and the update rate would quickly saturate at the maximum and cause the estimation to fluctuate significantly.
As can be seen in FIG. 11, the quadratic term significantly improves the noise dampening capabilities of this embodiment, but improvement is still possible. By using a combination of the linear and quadratic equations, a better estimator can be created which borrows characteristics from both Δ-factors.
FIG. 12 demonstrates the results of the new Δ-factor definition applied to varying levels of noise using an equal contribution of both original terms. The variability in the third test is significantly reduced compared to the same test that was applied to the linear definition while still maintaining the immediate transition from one behavior to another when such a move is justified. The first and second tests show considerable resistance to large amounts of additional noise which occurs in the datasets.
6. Example Computer Implementation
In an embodiment of the present invention, the system and components of the present invention described herein are implemented using well known computers, such as computer 1302 shown in FIG. 13. For example, server 104, web sites 108 and client 106 can be implemented using computers 1302.
The computer 1302 can be any commercially available and well known computer capable of performing the functions described herein, such as computers, personal data assistants, as well as any other data processing device available from International Business Machines, Apple, Sun, HP, Dell, Compaq, Digital, Cray, etc.
The computer 1302 includes one or more processors (also called central processing units, or CPUs), such as a processor 1306. The processor 1306 is connected to a communication bus 1304.
The computer 1302 also includes a main or primary memory 1308, such as random access memory (RAM). The primary memory 1308 has stored therein control logic 1328A (computer software), and data.
The computer 1302 also includes one or more secondary storage devices 1310. The secondary storage devices 1310 include, for example, a hard disk drive 1312 and/or a removable storage device or drive 1314, as well as other types of storage devices, such as memory cards and memory sticks. The removable storage drive 1314 represents a floppy disk drive, a magnetic tape drive, a compact disk drive, an optical storage device, tape backup, etc.
The removable storage drive 1314 interacts with a removable storage unit 1316. The removable storage unit 1316 includes a computer useable or readable storage medium 1324 having stored therein computer software 1328B (control logic) and/or data. Removable storage unit 1316 represents a floppy disk, magnetic tape, compact disk, DVD, optical storage disk, or any other computer data storage device. The removable storage drive 1314 reads from and/or writes to the removable storage unit 1316 in a well known manner.
The computer 1302 also includes input/output/display devices 1322, such as monitors, keyboards, pointing devices, etc.
The computer 1302 further includes a communication or network interface 1318. The network interface 1318 enables the computer 1302 to communicate with remote devices. For example, the network interface 1318 allows the computer 1302 to communicate over communication networks or mediums 1324B (representing a form of a computer useable or readable medium), such as LANs, WANs, the Internet, etc. The network interface 1318 may interface with remote sites or networks via wired or wireless connections.
Control logic 1328C may be transmitted to and from the computer 1302 via the communication medium 13241. More particularly, the computer 1302 may receive and transmit carrier waves (electromagnetic signals) modulated with control logic 1330 via the communication medium 1324B.
Any apparatus or manufacture comprising a computer useable or readable medium having control logic (software) stored therein is referred to herein as a computer program product or program storage device. This includes, but is not limited to, the computer 1302, the main memory 1308, the secondary storage devices 1310, the removable storage unit 1316 and the carrier waves modulated with control logic 1330. Such computer program products, having control logic stored therein that, when executed by one or more data processing devices, cause such data processing devices to operate as described herein, represent embodiments of the invention.
The invention can work with software, hardware, and/or operating system implementations other than those described herein. Any software, hardware, and operating system implementations suitable for performing the functions described herein can be used.
6. Conclusion
While various embodiments of the present invention have been described above, it should be understood that they have been presented by way of example only, and not limitation. It will be understood by those skilled in the relevant art(s) that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined in the appended claims. Accordingly, the breadth and scope of the present invention should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.

## Claims

1. A method of synchronizing a server and a client, comprising:
determining whether user provided criteria is satisfied for a current time interval, wherein the current time interval corresponds to a sync fitness measure including a probability that the client is inactive in the given interval and a probability that said user accesses data to be synchronized in the current time interval, wherein said sync fitness measure indicates a likelihood that a sync of said server and said client is to be performed in the current time interval, and wherein said user provided criteria indicates a time period to wait before initiating said sync of said server and said client;
generating a random number if said user provided criteria is satisfied and if a sync fitness measure is greater than or equal to said threshold;
waiting said time period plus or minus said random number; and
initiating said sync after said waiting.

2. The method of claim 1, wherein determining whether user provided criteria is satisfied comprises determining whether a period of idle time for the client has passed.

3. The method of claim 1, wherein determining whether user provided criteria is satisfied comprises determining whether a clock time has passed.

4. The method of claim 1 further comprising, after the determining and before the generating stages:
if the user provided criteria is not satisfied, waiting a predetermined period of time, wherein after the waiting is completed, returning to the determining stage.

5. A system for synchronizing a server and a client, comprising:
an interface configured to receive user provided criteria;
a control module configured to:
determine whether the user provided criteria is satisfied for a current time interval, wherein the current time interval corresponds to a sync fitness measure including a probability that the client is inactive in the given time interval and a probability that said user accesses data to be synchronized in the current time interval,
wherein said sync fitness measure indicates a likelihood that a sync of said server and said client is to be performed in said current time interval, and wherein said user provided criteria indicates a time period to wait before initiating said sync of said server and said client; and

if the user provided criteria is satisfied,
generate a random number if said user provided criteria is satisfied and if said sync fitness measure is greater than or equal to a threshold, wait said time period plus or minus said random number, and

initiate said sync after said wait.

6. The system of claim 5, wherein the user provided criteria comprises a period of client idle time.

7. The system of claim 5, wherein the user provided criteria comprises a clock time to initiate a sync of the server and the client.

8. The system of claim 5 wherein the control module is further configured to, after determining whether the user provided criteria is satisfied and before generating the random number:
if the user provided criteria is not satisfied, wait a predetermined period of time, wherein after the waiting is completed, return to determining whether the user defined criteria is satisfied.

9. The system of claim 5, wherein the user provided criteria corresponds to a synchronization schedule adaptive to user experience.

10. The system of claim 9, wherein the synchronization schedule is configured to promote synchronization transparency, and wherein the sync in a current interval minimizes disturbance to usage of the client.

11. The system of claim 9, wherein the synchronization schedule is configured to promote synchronization usefulness, and wherein the sync in a current interval is close in time to next major usage of data.

12. A computer-readable storage device having computer-executable instructions stored thereon that, when executed by a computing device, cause the computing device to perform operations for synchronizing a server and a client, the operations comprising:
determining whether user provided criteria is satisfied for a current time interval, wherein the current time interval corresponds to a sync fitness measure including a probability that the client is inactive in the given time interval and a probability that said user accesses data to be synchronized in the current time interval, wherein said sync fitness measure indicates a likelihood that a sync of said server and said client is to be performed in said current time interval, and wherein said user provided criteria indicates a time period to wait before initiating said sync of said server and said client;
generating a random number if said user provided criteria is satisfied and if said sync fitness measure is greater than or equal to a threshold; waiting said time period plus or minus said random number; and
initiating a sync after said waiting.