WO2017181520A1

WO2017181520A1 - Method and device for data synchronization

Info

Publication number: WO2017181520A1
Application number: PCT/CN2016/087117
Authority: WO
Inventors: 张更
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-04-20
Filing date: 2016-06-24
Publication date: 2017-10-26
Also published as: CN107306283B; CN107306283A

Abstract

A method for data synchronization, comprising: acquiring the frequency factor at which an application program is used during at least one synchronization time period in a current loop cycle, the frequency factor being used for indicating the frequency at which the application program is used by a user during the synchronization time period; setting, according to the frequency factor, the synchronization cycle of the application program during the synchronization time period; performing data synchronization on the application program according to the synchronization cycle during the same synchronization time period of the next loop cycle. By adjusting the synchronization cycle of data in a timely manner according to the frequency at which the application program is used, the described technical solution can adapt to the usage habits of different users. The method for data synchronization solves, to a certain extent, the contradiction between the timeliness of data synchronization and system power consumption, and meanwhile, prevents data from being synchronized during the time period when the application is not used, reducing the accidental disturbance and traffic loss arising from data synchronization.

Description

Data synchronization method and device

Technical field

This document relates to, but is not limited to, the field of mobile communications, and relates to a data synchronization method and apparatus.

Background technique

At present, many applications in mobile phones are designed using C/S (client/server) architecture. The application in the mobile phone synchronizes data between the client (client) and the server (server). It is done in the background with a fixed cycle.

In the case of e-mail, the e-mail in the mobile phone plays the role of the client. The e-mail client actively takes the e-mail to the server to view it. This process is called synchronization. In addition to the user manually synchronizing the e-mail, the synchronization is mainly initiated by the background, and is generally set to be synchronized once every 15 minutes or half an hour, that is, at a fixed period (frequency). Some applications also provide settings for users, and users can set different synchronization cycles according to their needs.

The synchronization period is a fixed value. If the setting is long, the new message cannot be received in time. If the setting is short, the "useless" synchronization is often initiated, which has a great impact on the power consumption of the terminal, and is also a waste of user data traffic.

Every time you sync your phone, you must wake up and then sync, even if the user sleeps late at night, the phone will automatically complete this series of wake-up process. The shorter the synchronization period, the more likely the user will receive new information in a timely manner, and it will mean more wake-ups and more power. In addition, "useless" synchronization can also cause user disruption. For example, many online video applications currently push information, but in fact, users rarely pay attention to these push information, especially when they push information continuously during work, which will cause some disturbance to users and waste user traffic. .

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The embodiment of the invention provides a data synchronization method and device, which can adapt to the usage habits of different users and solve the contradiction between the timeliness of data synchronization and the system power consumption.

The embodiment of the invention provides a data synchronization method, including:

Obtaining a frequency factor of using an application in at least one synchronization time period in a current cycle period, the frequency factor being used to indicate a frequency of how the user uses the application during the synchronization time period;

Setting a synchronization period of the application in the synchronization period according to the frequency factor;

Data synchronization is performed on the application according to the synchronization period during the same synchronization period of the next cycle.

Optionally, the setting, according to the frequency factor, the synchronization period of the application in the synchronization period includes:

A synchronization period of the application in the synchronization period is set according to a relationship in which the magnitude of the frequency factor is negatively correlated with the length of the synchronization period.

Optionally, the method further includes: before the step of acquiring a frequency factor of using an application in at least one synchronization period in the current cycle period,

Dividing the current cycle period into a plurality of time periods;

Obtaining a frequency factor for using an application during each of the time periods;

a time period in which the frequency factor is greater than the first threshold is used as the synchronization time period; a time period in which the frequency factor is less than or equal to the first threshold is used as the non-synchronization time period, and the non-synchronization time period is closed for the application. data synchronization.

Optionally, the obtaining a frequency factor for using an application in each of the time periods includes:

Obtaining an operation operation time for the application to perform different operations in each time period preset for a plurality of historical cycle periods, and assigning a weight value to each operation;

Obtaining a running time of the application in each time period preset by a plurality of historical cycle periods;

The frequency factor of the application during the time period is calculated according to the number of operations of different operations, the weight, and the running time of the application.

Optionally, the method further includes: using, as the time period, the frequency factor is greater than the first threshold a synchronization period; after the time period in which the frequency factor is less than or equal to the first threshold is used as the non-synchronization period,

Combining a plurality of consecutive non-synchronized time periods, and merging a plurality of consecutive synchronization time periods in which the frequency factors do not exceed the second threshold;

Determining a frequency factor of the combined synchronization time period; wherein, the frequency factor of the combined synchronization time period is not greater than a maximum value of the frequency factor in the synchronization time period included therein, and the frequency factor of the combined synchronization time period Not less than the minimum of the frequency factor in the synchronization period it includes.

The embodiment of the invention further provides a data synchronization device, comprising:

An obtaining module, configured to acquire a frequency factor of using an application in at least one synchronization period in a current cycle period, where the frequency factor is used to indicate a frequency of how the user uses the application during the synchronization period;

Setting a module, configured to set a synchronization period of the application in the synchronization period according to the frequency factor;

The synchronization module is configured to perform data synchronization on the application according to the synchronization period within the same synchronization period of the next cycle.

Optionally, the setting module is set to:

Optionally, the device further includes: a pre-processing module, configured to:

Dividing the current cycle period into a plurality of time periods;

Optionally, the preprocessing module includes:

a first processing sub-module, configured to acquire a number of operations of the application performing different operations in each time period of a preset plurality of historical cycle periods, and assign a weight to each operation;

a second processing submodule configured to acquire a running time of the application in each time period preset by a plurality of historical cycle periods;

The third processing submodule is configured to calculate a frequency factor of the application during the time period according to the number of operations of different operations, the weight, and the running time of the application.

Optionally, the device further includes a merge module, configured to:

The embodiment of the invention further provides a computer readable storage medium, wherein the computer readable storage medium stores computer executable instructions, and the computer executable instructions are implemented to implement a data synchronization method.

The data synchronization method of the embodiment of the present invention can adapt to the usage habits of different users by adjusting the synchronization period of the data in time by using the frequency of the application program. The data synchronization method ensures that the synchronization function is turned off during the period when the application is not used, and the synchronization period is set to be shorter when the application is used frequently, which solves the time synchronization of the data synchronization and the system power consumption to some extent. The contradiction; at the same time, it prevents the data from being synchronized during the period when the application is not used, and reduces the accidental interruption and traffic loss caused by data synchronization. Other aspects will be apparent upon reading and understanding the drawings and detailed description.

DRAWINGS

1 is a schematic flowchart of a data synchronization method in Embodiment 1 of the present invention;

2 is a schematic flowchart of dividing a current cycle period according to Embodiment 1 of the present invention;

FIG. 3 is a schematic flowchart of calculating a frequency factor of each divided time period according to Embodiment 1 of the present invention; FIG.

FIG. 4 is a schematic flowchart of combining the current cycle period and combining the current cycle according to the first embodiment of the present invention;

FIG. 5 is a schematic flowchart of synchronizing emails by using a data synchronization method according to Embodiment 2 of the present invention; FIG.

6 is a schematic flowchart of recording time and weight of each operation of an email according to Embodiment 2 of the present invention;

7 is a schematic flowchart of pushing a video application by using a data synchronization method according to Embodiment 3 of the present invention;

FIG. 8 is a schematic flowchart of recording time and weight of each operation of a video screen application according to Embodiment 3 of the present invention; FIG.

FIG. 9 is a schematic structural diagram of a data synchronization apparatus according to Embodiment 4 of the present invention.

detailed description

The present application will be described in detail below with reference to the accompanying drawings and specific embodiments.

Embodiment 1

Referring to FIG. 1, an embodiment of the present invention provides a data synchronization method, including:

Step 1: Obtain a frequency factor of using an application in at least one synchronization time period in the current cycle period, where the frequency factor is used to indicate how frequently the user uses the application during the synchronization time period;

When users use the application, they often use the 24 hours a day as a cycle and repeat it. In the embodiment of the present invention, the cycle period is not limited to one day, and may be adjusted according to actual use. In the current cycle, the frequency factor of using an application in at least one synchronization period is obtained to obtain how frequently the user uses the application in the different time period. During the synchronization period, the frequency with which the application is used is directly related to the user's need for the synchronization cycle of the application.

Step 2, according to the frequency factor, setting a synchronization period of the application in the synchronization period;

The synchronization period is set according to the frequency factor, which fully satisfies the user's usage habits. The method of setting the synchronization period is different from the method of setting the synchronization period to a fixed value in the related art, fully considering the habit of the user, and setting different synchronization periods for the time periods of different usage frequencies.

Step 3: in the same synchronization period of the next cycle, according to the synchronization period The application performs data synchronization.

When the application runs the next cycle of the current cycle, it runs to the same synchronization time period, and synchronizes the application with the synchronization cycle set for the synchronization time period to achieve the purpose of running a new synchronization cycle.

The data synchronization method in the embodiment of the present invention can adapt to the usage habits of different users by adjusting the synchronization period of the data in time by using the frequency of the application.

Optionally, in step 2, setting a synchronization period of the application in the synchronization period according to the frequency factor, including:

In other words, if the frequency factor of an application in the synchronization period in the current loop period is large, the synchronization period of the application is adjusted to be shorter; if an acquired application is in the synchronization period in the current cycle period, If the frequency factor of the program is small, the synchronization period of the application is adjusted to be longer. The data synchronization method ensures that the synchronization setting is shorter in a period in which the application is used more frequently, and the synchronization period is longer in a period in which the application is used less, thereby solving the timeliness and system of the data synchronization to some extent. The contradiction between power consumption; at the same time, it prevents the data from being synchronized during the time period when the application is not used, and reduces the accidental interruption and traffic loss caused by data synchronization.

In the present embodiment, depending on the particular operation and usage of the application, there is a case where the size of the frequency factor is positively correlated with the length of the synchronization period, and the synchronization period of the application within the synchronization period is set.

Optionally, referring to FIG. 2, the method further includes:

Step 10: Before the step of acquiring a frequency factor of using an application in at least one synchronization period in the current cycle period, dividing the current cycle period into multiple time segments;

For example, taking one day as a cycle, the day is divided equally into four time periods, that is, from 0 o'clock, every 6 hours as a time period.

Step 20: Obtain a frequency factor of using an application in each of the time periods;

For example, get the frequency factor of the application from 0 to 6, 6 to 12, 12 to 18, and 18 to 24.

Step 30: The time period in which the frequency factor is greater than the first threshold is used as the synchronization time period; the time period in which the frequency factor is less than or equal to the first threshold is used as the non-synchronization time period, and the application is closed in the non-synchronization time period. The data synchronization performed by the program.

For example, if the frequency factor from 0 o'clock to 6 o'clock is less than the first threshold, and the frequency factor from 6 o'clock to 12 o'clock is greater than the first threshold, then 0 o'clock to 6 o'clock is the non-synchronization time period, and 6 o'clock to 12 o'clock is the synchronization time period. . The step is to determine that the time period factor is less than the first threshold time period as the non-synchronization time period, and the synchronization is not performed during the non-synchronization time period, preventing data synchronization from being performed during the time period when the application is not used, and reducing the data synchronization band. Unexpected interruptions and traffic losses.

Optionally, referring to FIG. 3, in step 20, obtaining a frequency factor of each of the time segments, including:

Step 201: Acquire a number of operations in which the application performs different operations in each time period preset for a plurality of historical cycle periods, and assign a weight to each operation;

In this embodiment, the number of times each operation is performed on the application in each time period of the previous cycle of the current cycle is obtained. Generally, each time period of the week before the current day is taken. The number of times the application performs various operations is collected. For example, the number of times an application is opened, the number of times the first function of the application is clicked, or the number of times the second function of the application is clicked. Because each operation of the application has a different weight for determining the frequency factor, a weight is assigned to each operation.

Step 202: Acquire a running time of the application in each time period preset by a plurality of historical cycle periods;

For example, determine the total time to use the application from 0:00 to 6:00 on the day of the previous day of the day, the total time to use the program from 6 to 12, and so on. It is thus possible to determine the length of time the application is running in each time period.

Step 203: Calculate a frequency factor of the application in the time period according to the number of operations of different operations, the weight, and the running time of the application.

The number of operations, weights, and application runtime of different operations can determine the frequency factor by which the user uses the application. The user's habit data, such as the number of operations of an application, the weight, and the application, are stored in the user's habit database. Frequency factor in different time periods Refers to the ratio of all users' habitual data samples in a cycle of the user's habits of data samples during this time period.

In this embodiment, step 10, step 20, and step 30 are capable of distinguishing the divided time segments from which time period the data of the application is synchronized, and which time period the application data is not synchronized, thereby avoiding Synchronizing the application's data during periods of low user manipulation frequency causes an interruption to the user.

Optionally, referring to FIG. 4, the method further includes:

Step 40: The time period in which the frequency factor is greater than the first threshold is used as the synchronization time period; after the time period in which the frequency factor is less than or equal to the first threshold is used as the non-synchronization time period, multiple consecutive non-synchronization time segments are used. Merging, and combining a plurality of consecutive synchronization time periods in which the frequency factors differ by no more than the second threshold;

Step 50: Determine a frequency factor of the combined synchronization time period.

A plurality of consecutive synchronization periods in which the frequency factors differ by no more than the second threshold are combined, or a plurality of consecutive non-synchronization periods are combined. After the current cycle period is divided into multiple time segments, the frequency factor of each time segment can be determined by the number of operations of different operations, the weight, and the running time of the application. If the difference between the frequency factors in the plurality of consecutive synchronization periods does not exceed the second threshold, the plurality of time segments are combined, and the synchronized time period after the synchronization uses the same synchronization period to synchronize the application, thereby reducing the synchronization time period. The number of non-synchronized time periods reduces the amount of control resources that are occupied.

The frequency factor of the merged synchronization period is not greater than a maximum of a plurality of consecutive frequency factors in the synchronization period, and is not less than a minimum of a plurality of consecutive frequency factors in the synchronization period. For example, if the frequency factors of the combined time periods are 0.02, 0.03, 0.01, 0.04, and 0.02, the frequency factor of the combined time period may be between 0.01 and 0.04. Setting the frequency factor of the combined time period can reduce the excessive processing frequency factor data and reduce the load on the system.

Optionally, the method further includes: after step 3, after data synchronization of the application in a synchronization period of the next cycle period, determining the next time after the synchronization time period according to the merge situation of the divided multiple time segments The time of the synchronization period generally refers to the start time of the next synchronization period. Determine the start time of each synchronization time period in turn, so that the system can enter a cycle Planning for line synchronization.

Embodiment 2

The following is a detailed description of the data synchronization method of the embodiment of the present invention by taking a day as a cycle and a method of intelligently synchronizing emails.

Referring to FIG. 5, the method for intelligently synchronizing emails includes:

Step S1, dividing each day equally into a plurality of time periods;

Step S2: Counting user habit data such as the number of operations, the weight, and the running time of the application for different operations of the e-mail in each time period of the plurality of historical loop periods, and acquiring the users in different time periods according to the user habit data. Frequency factor of the email;

Step S3, setting a synchronization period of the email in each time period according to the frequency factor of each time period;

Step S4: performing data synchronization on the email according to the set synchronization period in a certain period of the next cycle period;

In step S5, it is determined the time when the email is synchronized next time.

In this embodiment, in step S1, 24 hours a day can be divided into 12 time segments, each time period is two hours, and is defined as T0 to T11, T0 represents 0:00 to 2:00, and T1 represents 2 :00～4:00...T11 stands for 22:00～24:00.

Referring to FIG. 6, in step S2, the user habit data such as the number of operations, the weight, and the running time of the application for different operations of the e-mail in each time period of the preset plurality of historical loop periods are statistically included:

S201: When receiving a new mail, record the time and weight P of receiving the new mail;

S202: When opening the mail application, record the time and weight M of opening the mail application;

S203: When exiting the mail application, record the time of exiting the mail application and the duration of using the mail application;

S204: When manually synchronizing the mail, record the time and weight N of manually synchronizing the mail.

In step S2, user habit data such as the number of operations of different operations of the e-mail, the weight and the running time of the application in each time period of the plurality of historical loop periods are saved in the habit number. According to the database, the correspondence between user habit data is shown in Table 1.

时间time	类型Types of	权值Weight
时间1Time 1	新邮件New mail	PP

时间2Time 2	打开邮件应用Open the mail app	MM

时间3Time 3	退出邮件应用Exit the mail app	使用时长Length of use
时间4Time 4	手动同步邮件Manually sync mail	NN

Table 1

In step S2, the user presets the user habit data for operating the e-mail in each time period of the plurality of historical cycle periods, and takes the user data of the past week as a statistical sample, and firstly clears the record in the user habit database earlier than one week. And then calculate the frequency factor for the user to use the email for different time periods according to the following formula:

For example, the correspondence between the frequency factors for calculating the e-mail used by the user for each time period of the day is as shown in Table 2.

时间段period	T0T0	T1T1	T2T2	T3T3	T4T4	T5T5	T6T6	T7T7	T8T8	T9T9	T10T10	T11T11
频率因子Frequency factor	00	00	00	0.020.02	0.130.13	0.260.26	0.080.08	0.220.22	0.180.18	0.070.07	0.020.02	00

Table 2

In step S3, according to the frequency factor of each time period, the synchronization period of the email in each time period is set, including the following cases:

1) When the frequency factor is small, set the synchronization period to be longer; for example, the T4 time period synchronization factor is 0.13, and the T4 time period synchronization period is set to 30 minutes;

2) When the frequency factor is large, set the synchronization period to be shorter; for example, the T5 time period synchronization factor is 0.26, and the T5 time period synchronization period is set to 5 minutes;

3) When the frequency factor is less than a certain fixed threshold (for example, 0.05), the email synchronization is turned off; for example, the T0, T1, T2, T3, T10, and T11 time periods, and the email synchronization function is turned off;

Step S3, according to the frequency factor of each time period, before setting the synchronization period of the email in each time period, the method further comprises: combining several time periods into one when the frequency factors of the consecutive time periods are the same or similar Longer time period. Wherein, when a plurality of consecutive time period frequency factors do not exceed a certain threshold (for example, 0.02), the time periods are combined. For example, T0 to T3 and T10 to T11 are combined into the same time period. If the frequency factors of several consecutive time segments are less than a set threshold, the consecutive time segments are regarded as non-synchronized time segments, and the application is not synchronized during the combined time period. Reduce the use of traffic and avoid the impact on users.

In step S5, after the email client synchronizes the mail with the new synchronization week, it determines the time for adjusting the email synchronization period for the next time, which generally refers to the start time of the next time period. For example, when T0 is set to turn off e-mail synchronization, the next adjustment of the e-mail synchronization period is the start time of T4, and the synchronization period is set to 30 minutes in sequence at T4.

Embodiment 3

The data synchronization method of the embodiment of the present invention is described in detail below by taking a day as a cycle and applying an intelligent synchronization (pushing) method to an online video.

Referring to Figure 7, the following steps are included:

Step S10, dividing each day equally into a plurality of time periods;

Step S20: Counting user habit data such as the number of operations, the weight, and the running time of the application for different operations of the video in each time period of the plurality of historical loop periods, and acquiring the users in different time periods according to the user habit data. Frequency factor of the video application;

Step S30, setting a push period of the video application in each time period according to a frequency factor of each time period;

Step S40: Perform data push on the video application according to the set push period in a certain period of the next cycle period;

In step S50, the time for pushing the video application next time is determined.

In step S10, six time periods are divided each day, each time period is 4 hours, and is defined as T0 to T5.

Referring to FIG. 8, in step S20, statistics are preset for each time period of a plurality of historical cycle periods. User habits such as the number of operations, weights, and application runtime of different operations on the video, including:

S2001, when opening the online video application, recording the time and weight M of opening the video software;

S2002, when exiting the online video application, record the time of exiting the online video application and the duration of using the online video.

Then the frequency factor of the online video application used by the user during a certain period of time is:

For example, the frequency factor correspondence of the user using the online video application in each time period of the day is calculated as shown in Table 3.

时间段period	T0T0	T1T1	T2T2	T3T3	T4T4	T5T5
频率因子Frequency factor	00	00	00	0.020.02	0.130.13	0.850.85

table 3

In step S30;

1) Turn off data push when the frequency factor is small, for example, turn off the data push of the video application during the time period of T0, T1, T2, T3, and T4;

2) When the frequency factor is large, the data push is turned on, and the push cycle is set to a default value, such as a T5 time period.

In this embodiment, the method further includes, before step S30, combining the several time periods into one longer time period when the frequency factors of the consecutive time periods are the same or similar. Wherein, when the frequency factors of the plurality of consecutive time periods do not exceed a certain threshold (for example, 0.02), the time periods T0 to T4 are combined. If the frequency factors of several consecutive time segments are less than a set threshold, the consecutive time segments are regarded as non-synchronized time segments, and the application is not synchronized during the combined time period. Reduce the use of traffic and avoid the impact on users.

In step S50, after the video application pushes with the new push week, the push time of the next screen application is determined, which is generally the start time of the next time period for pushing. For example, the data push is turned off during the T0 period, and the start time of the next time period T5 of pushing is determined, and Turn on data push at T5 and set the push cycle to the default value.

Embodiment 4

Referring to FIG. 9, an embodiment of the present invention further provides a data synchronization apparatus, including:

The obtaining module 100 is configured to acquire a frequency factor of using an application in at least one synchronization period in the current cycle period, where the frequency factor is used to indicate how frequently the user uses the application during the synchronization period;

The setting module 200 is configured to set a synchronization period of the application in the synchronization period according to the frequency factor;

The synchronization module 300 is configured to perform data synchronization on the application according to the synchronization period within the same synchronization period of the next cycle.

Optionally, the data synchronization device further includes: a pre-processing module 400, configured to:

Dividing the current cycle period into a plurality of time periods;

Optionally, the pre-processing module 400 includes:

The first processing sub-module 401 is configured to acquire, for a preset number of operations, that the application performs different operations in each time period of the plurality of historical cycle periods, and assign a weight to each operation;

The second processing sub-module 402 is configured to acquire a running time of the application in each time period preset by a plurality of historical cycle periods;

The third processing sub-module 403 is configured to calculate a frequency factor of the application in the time period according to the number of operations of different operations, the weight, and the running time of the application.

Optionally, the setting module 200 is configured to:

Optionally, the data synchronization device further includes a merge module 500,

Set to: combine a plurality of consecutive non-synchronized time periods, and combine a plurality of consecutive synchronization time periods whose frequency factors do not exceed a second threshold;

Determining a frequency factor of the combined synchronization time period; wherein, the frequency factor of the combined synchronization time period is not greater than a maximum value of the frequency factor in the synchronization time period included therein, and the frequency of the combined synchronization time period The factor is not less than the minimum of the frequency factor in the synchronization period it includes.

In an embodiment of the invention, the modules may be implemented in software for execution by a plurality of types of processors. For example, an acquisition module can include one or more physical or logical blocks of computer instructions, which can be constructed, for example, as an object, procedure, or function. Nevertheless, the executable code of the acquisition module need not be physically located together, but may comprise different instructions stored in different bits, and when these instructions are logically combined, they constitute a module and achieve the specified purpose of the module. .

In fact, the acquisition module can be a single instruction or a number of instructions, and can even be distributed over multiple different code segments, distributed among different programs, and distributed across multiple memory devices. As such, operational data may be identified within the modules and may be implemented in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed at different locations (including on different storage devices), and may at least partially exist as an electronic signal on a system or network.

When the module can be implemented by software, considering the level of the related hardware process, the module can be implemented in software, and the technician can construct the corresponding hardware circuit to realize the corresponding function without considering the cost. The hardware circuits include conventional Very Large Scale Integration (VLSI) circuits or gate arrays and existing semiconductors such as logic chips, transistors, or other discrete components. The modules can also be implemented with programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, and the like.

One of ordinary skill in the art will appreciate that all or a portion of the above steps may be performed by a program to instruct related hardware, such as a processor, which may be stored in a computer readable storage medium, such as a read only memory, disk or optical disk. Wait. Optionally, all or part of the above embodiment The steps can also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the above embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, executing a program stored in the memory by a processor. / instruction to achieve its corresponding function. This application is not limited to any specific combination of hardware and software. A person skilled in the art should understand that the technical solutions of the present application can be modified or equivalent, without departing from the spirit and scope of the technical solutions of the present application, and should be included in the scope of the claims of the present application.

Industrial applicability

The above technical solution can adapt to the usage habits of different users, and solves the contradiction between the timeliness of data synchronization and the system power consumption to some extent, and reduces the accidental interruption and traffic loss caused by data synchronization.

Claims

A data synchronization method includes:

Obtaining a frequency factor of using an application in at least one synchronization time period in a current cycle period, the frequency factor being used to indicate a frequency of how the user uses the application during the synchronization time period;

Setting a synchronization period of the application in the synchronization period according to the frequency factor;

Data synchronization is performed on the application according to the synchronization period during the same synchronization period of the next cycle.
The data synchronization method according to claim 1, wherein said setting a synchronization period of said application within said synchronization period according to said frequency factor comprises:

A synchronization period of the application in the synchronization period is set according to a relationship in which the magnitude of the frequency factor is negatively correlated with the length of the synchronization period.
The data synchronization method according to claim 1, further comprising: said step of: obtaining a frequency factor of using an application during at least one synchronization period in the current cycle period,

Dividing the current cycle period into a plurality of time periods;

Obtaining a frequency factor for using an application during each of the time periods;

a time period in which the frequency factor is greater than the first threshold is used as the synchronization time period; a time period in which the frequency factor is less than or equal to the first threshold is used as the non-synchronization time period, and the non-synchronization time period is closed for the application. data synchronization.
The data synchronization method according to claim 3, wherein said obtaining a frequency factor for using an application in each of said time periods comprises:

Obtaining an operation operation time for the application to perform different operations in each time period preset for a plurality of historical cycle periods, and assigning a weight value to each operation;

Obtaining a running time of the application in each time period preset by a plurality of historical cycle periods;

The frequency factor of the application during the time period is calculated according to the number of operations of different operations, the weight, and the running time of the application.
The data synchronization method according to claim 3, further comprising: said frequency factor a period in which the sub-threshold is greater than the first threshold is used as the synchronization period; after the period in which the frequency factor is less than or equal to the first threshold is used as the non-synchronization period,

Combining a plurality of consecutive non-synchronized time periods, and merging a plurality of consecutive synchronization time periods in which the frequency factors do not exceed the second threshold;

Determining a frequency factor of the combined synchronization time period; wherein, the frequency factor of the combined synchronization time period is not greater than a maximum value of the frequency factor in the synchronization time period included therein, and the frequency factor of the combined synchronization time period Not less than the minimum of the frequency factor in the synchronization period it includes.
A data synchronization device comprising:

An obtaining module, configured to acquire a frequency factor of using an application in at least one synchronization period in a current cycle period, where the frequency factor is used to indicate a frequency of how the user uses the application during the synchronization period;

Setting a module, configured to set a synchronization period of the application in the synchronization period according to the frequency factor;

The synchronization module is configured to perform data synchronization on the application according to the synchronization period within the same synchronization period of the next cycle.
The data synchronization device of claim 6, wherein said setting module is configured to:

A synchronization period of the application in the synchronization period is set according to a relationship in which the magnitude of the frequency factor is negatively correlated with the length of the synchronization period.
The data synchronization device of claim 6, further comprising: a preprocessing module, configured to:

Dividing the current cycle period into a plurality of time periods;

Obtaining a frequency factor for using an application during each of the time periods;

a time period in which the frequency factor is greater than the first threshold is used as the synchronization time period; a time period in which the frequency factor is less than or equal to the first threshold is used as the non-synchronization time period, and the non-synchronization time period is closed for the application. data synchronization.
The data synchronization device of claim 8 wherein said pre-processing module comprises:

a first processing sub-module configured to acquire a preset plurality of historical cycle periods, each of the time periods The number of operations the application performs for different operations, and assigns weights to each operation;

a second processing submodule configured to acquire a running time of the application in each time period preset by a plurality of historical cycle periods;

The third processing submodule is configured to calculate a frequency factor of the application during the time period according to the number of operations of different operations, the weight, and the running time of the application.
The data synchronization device of claim 8 further comprising a merge module configured to:

Combining a plurality of consecutive non-synchronized time periods, and merging a plurality of consecutive synchronization time periods in which the frequency factors do not exceed the second threshold;

Determining a frequency factor of the combined synchronization time period; wherein, the frequency factor of the combined synchronization time period is not greater than a maximum value of the frequency factor in the synchronization time period included therein, and the frequency factor of the combined synchronization time period Not less than the minimum of the frequency factor in the synchronization period it includes.