WO2019024643A1 - 数据同步管控方法、装置及电子设备 - Google Patents

数据同步管控方法、装置及电子设备 Download PDF

Info

Publication number
WO2019024643A1
WO2019024643A1 PCT/CN2018/094253 CN2018094253W WO2019024643A1 WO 2019024643 A1 WO2019024643 A1 WO 2019024643A1 CN 2018094253 W CN2018094253 W CN 2018094253W WO 2019024643 A1 WO2019024643 A1 WO 2019024643A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
preset
data
data synchronization
synchronization
Prior art date
Application number
PCT/CN2018/094253
Other languages
English (en)
French (fr)
Inventor
杜冰
林志泳
张俊
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Publication of WO2019024643A1 publication Critical patent/WO2019024643A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to the field of mobile device technologies, and in particular, to a data synchronization management method, device, and electronic device.
  • the electronic device side realizes communication, watching video, listening to music, and the like through various applications. For example, use instant messaging software for video chat.
  • the application of the electronic device side performs data synchronization during the running process, especially the application of data cycle synchronization, and the data in the application is periodically synchronized.
  • the embodiment of the present application provides a data synchronization management method, device, and electronic device, which can save power of an electronic device and improve the running speed of the electronic device.
  • the embodiment of the present application provides a data synchronization management method, which is applied to an electronic device, where the data synchronization management method includes:
  • the target application that is successfully matched When there is a target application that is successfully matched, the target application that is successfully matched is allowed to perform data synchronization; when there is a target application that fails to match, the target application that fails to match is prohibited from performing data synchronization.
  • the embodiment of the present application further provides a data synchronization management device, where the data synchronization control device includes:
  • a first acquiring module configured to acquire a synchronization parameter of the to-be-synchronized application and the to-be-synchronized application in the electronic device, where the to-be-synchronized application is an application waiting for data synchronization;
  • a screening module configured to filter a target application from the to-be-synchronized application according to the synchronization parameter
  • a matching module configured to apply the target to an application in a preset whitelist for matching
  • control module configured to allow the successfully matched target application to perform data synchronization when there is a target application with a successful match
  • the control module is further configured to prevent the target application that fails the matching from performing data synchronization when there is a target application that fails to match.
  • an embodiment of the present application further provides an electronic device, where the electronic device includes a processor and a memory, the processor and the memory are electrically connected, and the memory is used to store instructions and data, and the processing The device is configured to execute the data synchronization management method as described above.
  • FIG. 1 is a schematic diagram of a scenario of a data synchronization management method according to an embodiment of the present disclosure.
  • FIG. 2 is another schematic diagram of a data synchronization management method according to an embodiment of the present disclosure.
  • FIG. 3 is a schematic flowchart of a data synchronization management method according to an embodiment of the present application.
  • FIG. 4 is another schematic flowchart of a data synchronization management method according to an embodiment of the present application.
  • FIG. 5 is a priority row list of preset whitelists according to an embodiment of the present application.
  • FIG. 6 is another priority row list of a preset white list according to an embodiment of the present application.
  • FIG. 7 is another priority ranking list of a preset whitelist according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a data synchronization management device according to an embodiment of the present disclosure.
  • FIG. 9 is another schematic structural diagram of a data synchronization management device according to an embodiment of the present application.
  • FIG. 10 is another schematic structural diagram of a data synchronization management device according to an embodiment of the present application.
  • FIG. 11 is another schematic structural diagram of a data synchronization management device according to an embodiment of the present application.
  • FIG. 12 is another schematic structural diagram of a data synchronization management device according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
  • FIG. 14 is another schematic structural diagram of an electronic device according to an embodiment of the present application.
  • the embodiment of the present application provides a data synchronization management method, device, and electronic device.
  • FIG. 1 is a schematic diagram of a scenario of a data synchronization management method according to an embodiment of the present disclosure.
  • the scenario may include an electronic device 10 , which may include a tablet, a PC (Personal Computer), a mobile phone, and the like.
  • the electronic device 10 is provided with a storage unit and has a microprocessor mounted thereon and has computing power.
  • the electronic device 10 is described by taking a mobile phone as an example.
  • the mobile phone 10 obtains a white list 11 from the local area.
  • the mobile phone 10 may store a white list 11 in advance.
  • the white list 11 stored in the mobile phone 10 may be manually set by the user, or may be based on a preset.
  • the rules set up may be performed by the user, or may be based on a preset.
  • the white list 11 can also be downloaded from the server side in advance.
  • the application in the whitelist 11 is matched with the data cycle synchronization application.
  • the successfully matched application is allowed to be synchronized; and when there is an application that fails to match, the application is prohibited.
  • the scenario may include a data synchronization management device 300, which may be specifically integrated in the electronic device 10.
  • the data synchronization control device 300 is mainly configured to acquire a synchronization parameter of an application to be synchronized and an application to be synchronized in an electronic device, where the application to be synchronized is an application that waits for data to be synchronized; and the target application is filtered from the application to be synchronized according to the synchronization parameter.
  • the target application is matched with the application in the preset whitelist; when there is a target application with a successful match, the target application that matches the success is allowed to perform data synchronization; when there is a target application that fails to match, the target application that fails the matching is prohibited from being performed. data synchronization.
  • the target application is filtered out in the application to be synchronized, and the target application is also an application waiting for data synchronization, or the target application can perform data synchronization.
  • FIG. 2 is another schematic diagram of a data synchronization management method according to an embodiment of the present disclosure.
  • the scenario may include an electronic device 10 and a server 20. The difference between the scenario and FIG. 1 is that the electronic device 10 can directly The whitelist 11 is obtained from the server 20. After the electronic device 10 obtains the white list 11, please refer to the above content, and details are not described herein again.
  • the scenario may further include a data synchronization control device 300.
  • the data synchronization control device 300 may be integrated into the electronic device 10. For details, refer to the data synchronization control device in FIG.
  • a data synchronization control device which may be integrated into an electronic device having a storage unit and a microprocessor installed with a computing capability, such as a tablet, a PC, or a mobile phone.
  • a data synchronization management method is applied to an electronic device, which includes:
  • the target application that is successfully matched is allowed to perform data synchronization
  • the target application whose matching fails is prohibited from performing data synchronization.
  • the data synchronization management method before the step of matching the target application with a preset whitelist, the data synchronization management method further includes:
  • the original whitelist is determined as a preset whitelist.
  • the data synchronization management method before the step of matching the target application with a preset whitelist, the data synchronization management method further includes:
  • a preset whitelist is generated according to the application of the data cycle synchronization.
  • the step of generating a preset whitelist according to the data period synchronization application includes:
  • the application whose synchronization period is greater than the preset period is written into the preset white list to generate the preset white list.
  • the generating a preset whitelist according to the data period synchronization application includes:
  • the application whose historical running time is longer than the preset duration is written into the preset white list to generate the preset white list.
  • the generating a preset whitelist according to the data period synchronization application includes:
  • the application whose history running times is greater than the preset number of times is written into the preset white list to generate the preset white list.
  • the data synchronization management method further includes:
  • All applications in the preset whitelist are set to different priorities according to a preset rule.
  • the data synchronization management method further includes:
  • the application whose priority is higher than the preset priority is allowed to perform data synchronization, and the application whose priority is lower than the preset priority is prohibited from performing data synchronization. And storing the data to be synchronized in the application whose priority is lower than the preset priority in a buffer, and allowing the storage to be stored in the buffer until the current running condition of the electronic device meets the preset operating condition.
  • the data to be synchronized is synchronized.
  • the step of setting different priorities of all the applications in the preset whitelist according to the preset rule includes:
  • FIG. 3 is a schematic flowchart of a data synchronization management method according to an embodiment of the present disclosure.
  • the data synchronization management method can include:
  • step S101 the synchronization parameters of the application to be synchronized and the application to be synchronized in the electronic device are acquired.
  • the synchronization manner of data in an application mainly includes the following three methods: a method of periodically synchronizing, a method of manually controlling synchronization by a user, and a method of setting synchronization according to a synchronization switch.
  • Each synchronization mode application has different synchronization parameters, and different synchronization modes have different synchronization parameters carried in the synchronization process.
  • the application of the data cycle synchronization carries the synchronization parameter 1 when the data cycle is synchronized;
  • the application that is synchronized according to the synchronization switch carries the synchronization parameter 2 when performing data synchronization;
  • the application that the user manually controls the synchronization carries when the data is synchronized.
  • the data synchronization mechanism (Syncmanager) determines different synchronization modes according to different synchronization parameters while controlling the application.
  • the application to be synchronized is an application waiting for data synchronization.
  • the WeChat application in the electronic device needs to perform data synchronization, and the WeChat application sends a data synchronization request, and the WeChat application is the application to be synchronized.
  • the synchronization parameter to be synchronized is a parameter carried by the application to be synchronized.
  • the application to be synchronized when the application to be synchronized needs to perform data synchronization, the application to be synchronized is acquired, and the synchronization parameters carried by the application to be synchronized are acquired to determine a synchronization manner of data in the application to be synchronized.
  • step S102 the target application is filtered out from the application to be synchronized according to the synchronization parameter.
  • the synchronization manner of the data in the application to be synchronized may be determined according to the synchronization parameter carried by the application to be synchronized, or the synchronization type of the data in the application to be synchronized may be determined according to the synchronization parameter carried by the application to be synchronized.
  • the target application of the data cycle synchronization can be filtered according to the synchronization parameters carried by the application to be synchronized.
  • step S103 the target application is matched with the application in the preset whitelist.
  • the preset whitelist includes an application that has at least one data cycle synchronization, and the application can perform data cycle synchronization, or the application has a cycle synchronization function.
  • the applications in the preset whitelist can perform data cycle synchronization.
  • the preset whitelist can be obtained from the server. Specifically, the manner in which the preset whitelist is obtained from the server includes the following steps:
  • the original white list is determined as a preset white list.
  • the preset whitelist may also be directly obtained from the electronic device, and the preset whitelist of the electronic device may be downloaded from the server in advance, or may be formed according to manual control of the user, or may be Set rules to form.
  • the manner in which the preset whitelist is obtained from the electronic device includes the following steps:
  • acquiring an application for synchronizing all data periods in the electronic device and synchronizing the data into a preset white list specifically includes the following steps:
  • the application of the data cycle synchronization in the embodiment of the present application may be the same as the target application.
  • the application or the target application of the data cycle synchronization may be referred to as an application, and the synchronization period of the application is the time interval for applying the synchronization. It should be noted that, when the application performs data synchronization over a time interval, for example, the time interval is 24 hours, the synchronization period is synchronized once every 24 hours. If the time interval is 1 hour, the synchronization period is synchronized once every 1 hour.
  • the preset period can be set according to the user's needs, for example, the preset period is synchronized once every 12 hours.
  • the application whose synchronization period is greater than the preset period is written into the preset white list to generate a preset white list.
  • the synchronization period is synchronized once every 24 hours, and the preset period is 12 hours synchronization, the synchronization period of the application is greater than the preset period, and the application of the data period synchronization is written. Go to the default whitelist.
  • the synchronization period is less than the preset period, the corresponding application is not written into the white list.
  • acquiring an application for synchronizing all data periods in the electronic device and generating a preset whitelist according to the application of the data cycle synchronization further includes the following steps:
  • the historical running time of the application in which the data period is synchronized may be acquired, or the historical running time of the application in which the data period is synchronized may be acquired in a period of time. For example, in one month, the historical running time of the application for synchronizing data cycles can be obtained, and the historical running time can be 1 hour, 10 hours, 20 hours, 50 hours, and the like.
  • the preset duration can be set according to the user's needs, for example, the preset duration is set to 25 hours.
  • the historical running time of the application in which the data period is synchronized is compared with the preset duration.
  • the application running longer than the preset duration is written.
  • the historical running time is less than the preset duration, the application less than the preset duration is not written into the preset whitelist.
  • acquiring an application for synchronizing all data periods in the electronic device and generating a preset whitelist according to the application of the data cycle synchronization further includes the following steps:
  • the historical running times of the application in which the data period is synchronized may be acquired, or the historical running times of the target application may be acquired in a period of time. For example, in one month, the number of historical operations of the application in which the data cycle is synchronized may be acquired, and the number of historical operations may be 1, 10, 30, 50, 60, and the like.
  • the preset number of times can be set according to the user's needs, for example, the preset number of times is set to 15 times.
  • comparing the historical running times of the application of the data cycle synchronization with the preset number of times when the historical running times of the application of the data cycle synchronization is greater than the preset number of times, the historical running times are greater than the preset number of times.
  • the application is written in the preset whitelist to generate a preset whitelist. For example, if the number of historical runs is 30, and the preset number is 15 times, the number of historical runs is greater than the preset number, and the corresponding application is written into the preset white list. When the number of historical running times is less than the preset number of times, the application that is less than the preset number of data periods is not written into the preset white list.
  • step S104 when there is a target application with a successful match, the target application that successfully matches is allowed to perform data synchronization.
  • the target application matches the application in the preset whitelist
  • the target application matches the corresponding application in the preset whitelist, that is, when there is a target application with a successful match
  • the Matching the successful target application for data synchronization thereby invoking and starting the data synchronization mechanism, and controlling the target program for data synchronization through the data synchronization mechanism.
  • step S105 when there is a target application whose matching fails, the target application whose matching fails is prohibited from performing data synchronization.
  • the prohibition is prohibited.
  • the target application that fails to match performs data synchronization, so that the data synchronization mechanism is not invoked or started, so that the target application that fails the matching does not perform data synchronization, and some applications that are too frequently synchronized are prohibited from performing data synchronization, and the data cycle synchronization is effectively controlled.
  • Applications reduce the power consumption of electronic devices and increase the speed of electronic devices.
  • the prompt information is sent to prompt the target application to be an abnormal application, so that the user can understand that the data period is too frequent in the electronic device. Synchronized apps that prevent apps from being maliciously synced.
  • the prompt information may be a prompt message, a prompt voice, or the like.
  • FIG. 4 is another schematic flowchart of a data synchronization management method according to an embodiment of the present application.
  • the data synchronization management method includes the following steps:
  • step S201 the synchronization parameters of the application to be synchronized and the application to be synchronized in the electronic device are acquired.
  • step S101 the synchronization parameters of the application to be synchronized and the application to be synchronized in the electronic device are acquired.
  • step S202 the target application is filtered out from the application to be synchronized according to the synchronization parameter.
  • step S102 the target application is filtered out from the application to be synchronized according to the synchronization parameter.
  • step S203 the target is applied to the application in the preset whitelist for matching.
  • the target is applied to the application in the preset whitelist for matching.
  • step S204 when there is a target application with a successful match, the target application that successfully matches is allowed to perform data synchronization.
  • the target application that successfully matches is allowed to perform data synchronization.
  • step S205 all applications in the preset whitelist are set to different priorities according to a preset rule.
  • the preset rule may be a historical running time of all applications, and further, may be a historical running time of all applications over a period of time.
  • the applications that synchronize all the data cycles are sorted according to their respective historical running times, sorted according to the length of the historical running time, and the application with a long historical running time is set to a high priority.
  • FIG. 5 is a priority row list of preset whitelists according to an embodiment of the present application.
  • the longest setting of the historical running time has the highest priority, and then the priority level is set in turn.
  • the historical running time of application A is 50 hours, and the specific one can be the running time of one month.
  • the historical running time of application B is 45 hours
  • the historical running time of application C is 40 hours
  • the historical running time of application D is 35 hours
  • the historical running time of application E is 30 hours
  • the historical running time of application F is 25 hours.
  • the priorities of the application A, the application B, the application C, the application D, the application E, and the application F in the preset whitelist 12 are, in descending order, application A, application B, application C, application D, application E, and application F. . It should be noted that FIG. 5 only shows a part of the application, and does not limit the number of applications in the preset white list 12.
  • the preset rule may be a synchronization period of all applications, and all applications that synchronize data periods are sorted according to respective synchronization periods, and are sorted according to the length of the synchronization period, and the synchronization period is long.
  • the application settings have a high priority.
  • FIG. 6 is another priority ranking list of a preset whitelist according to an embodiment of the present application.
  • the setting with the longest synchronization period has the highest priority, and then the priority level is set in turn.
  • the synchronization period of application A is 12 hours
  • the synchronization period of application B is 10 hours
  • the synchronization period of application C is 8 hours
  • the synchronization period of application D is 6 hours
  • the synchronization period of application E is 5 hours.
  • the synchronization period is 4 hours
  • the priorities of the application A, the application B, the application C, the application D, the application E, and the application F in the preset whitelist 13 are the application A, the application B, the application C, and the application D in descending order.
  • application E and application F is another priority ranking list of a preset whitelist according to an embodiment of the present application.
  • FIG. 6 only shows a part of the application, and does not limit the number of applications in the preset white list 13.
  • the preset rule may also be the running times of all applications, and the applications that synchronize all the data cycles are sorted according to the respective running times, and are sorted according to at least the running times, and the running times are more.
  • the application settings have a high priority.
  • the application embodiment has the highest priority setting, and then sets the priority level in sequence. For details, please refer to FIG. 5 and FIG. 6, which are not illustrated here.
  • setting different priorities of all applications in the preset whitelist according to the preset rule may specifically include the following steps:
  • FIG. 7 is another priority row list of a preset whitelist according to an embodiment of the present application.
  • Different levels 141 are set according to different types of applications in the preset whitelist 14 , for example, the application type in one level 141 is a bank type application, and the bank type application includes application A, application B, and application C, and the bank class The priority of the app is set to the highest.
  • the application type in one level 142 is an instant messaging application, which includes application D and application E, even if the priority of the communication application is lower than the application priority in level 141.
  • the applications in other levels are not illustrated one by one, and can be set according to user requirements.
  • the arrangement of the hierarchical priorities in the preset whitelist 14 from high to low is hierarchical 141, hierarchical 142, hierarchical 143, hierarchical 144, hierarchical 145, hierarchical 146, and hierarchical 147. It should be noted that FIG. 7 only shows a partial application, and does not limit the number of applications in the preset whitelist 14.
  • step S206 when the running status of the electronic device does not meet the preset operating condition, the application with the priority higher than the preset priority is allowed to perform data synchronization, and the application whose priority is lower than the preset priority is prohibited from performing data synchronization, and
  • the data to be synchronized in the application whose priority is lower than the preset priority is stored in a buffer, and the data to be synchronized stored in the buffer is allowed to be synchronized when the current running condition of the electronic device meets the preset operating condition.
  • the operating status of the electronic device may include multiple applications in the electronic device at a certain time for data synchronization, low battery power, slow running speed, and the like.
  • the preset condition corresponds to the operating condition of the electronic device. For example, when the operating condition of the electronic device is that the battery is low, the preset condition is a preset battery power. Specifically, when the electronic device has a battery power of 5%. The preset battery power can be set to eight percent, and the electronic device has less than eight percent of the battery power. If the preset condition is not met, the data with the priority lower than the preset priority is synchronized. It is forbidden to synchronize data with applications whose priority is lower than the preset priority. Therefore, priority can be given to prioritizing applications with high priority to ensure that important applications can prioritize data synchronization; unimportant applications do not affect users' use of electronic devices, staggering the peak usage period of electronic devices, and improving data synchronization efficiency.
  • the preset priority may be set according to user requirements. For example, the preset priority is located in the middle of all priorities, and the preset priority may also limit only a few applications with the highest priority.
  • step S207 when there is a target application whose matching fails, the target application whose matching fails is prohibited from performing data synchronization.
  • the target application whose matching fails is prohibited from performing data synchronization.
  • the embodiment of the present application further provides an apparatus based on the data synchronization management method.
  • the meaning of the noun is the same as that in the above data synchronization management method.
  • a data synchronization control device is applied to an electronic device, which includes:
  • a first acquiring module configured to acquire an application to be synchronized and a synchronization parameter of the to-be-synchronized application in the electronic device, where the application to be synchronized is an application waiting for data synchronization;
  • a screening module configured to filter a target application from the to-be-synchronized application according to the synchronization parameter
  • a matching module configured to apply the target to an application in a preset whitelist for matching
  • control module configured to allow the successfully matched target application to perform data synchronization when there is a target application with a successful match
  • the control module is further configured to prevent the target application that fails the matching from performing data synchronization when there is a target application that fails to match.
  • the data synchronization management device further includes a second acquisition module and a determination module;
  • the second obtaining module is configured to obtain an original whitelist from a server
  • the determining module is configured to determine the original whitelist as a preset whitelist.
  • the data synchronization management device further includes a third acquisition module and a generation module;
  • the third acquiring module is configured to acquire an application for synchronizing all data periods in the electronic device
  • the generating module is configured to generate a preset whitelist according to the application that is synchronized by the data period.
  • the generating module comprises:
  • a fourth acquiring module configured to acquire a synchronization period of an application synchronized with each of the data periods
  • the first writing module is configured to write an application whose synchronization period is greater than a preset period into a preset whitelist to generate the preset whitelist.
  • the generating module further includes:
  • a fifth obtaining module configured to acquire a historical running time of an application synchronized for each data period
  • the second writing module is configured to write the application whose historical running time is longer than the preset duration to the preset whitelist to generate the preset whitelist.
  • the data synchronization control device further includes a first setting module
  • the first setting module is configured to set different priorities of all applications in the preset whitelist according to a preset rule
  • the control module is further configured to allow the application with the priority higher than the preset priority to perform data synchronization when the operating condition of the electronic device does not meet the preset operating condition, and prohibit the priority from being lower than the preset.
  • the priority application performs data synchronization, and the data to be synchronized in the application whose priority is lower than the preset priority is stored in a buffer until the current running condition of the electronic device meets the preset operating condition. And allowing data stored in the buffer to be synchronized to be synchronized.
  • the first setting module includes:
  • the second setting module is configured to set different levels according to the type of the application in the preset white list, and allocate the applications in the preset white list to the corresponding levels respectively;
  • the third setting module is configured to set different priorities for the different levels according to types of applications in the preset white list.
  • FIG. 8 is a schematic structural diagram of a data synchronization management device according to an embodiment of the present disclosure.
  • the data synchronization management device 300 of the embodiment of the present application includes a first obtaining module 301, a screening module 302 matching module 303, and a management module 304.
  • the first obtaining module 301 is configured to acquire synchronization parameters of the application to be synchronized and the application to be synchronized in the electronic device.
  • the synchronization manner of data in an application mainly includes the following three methods: a method of periodically synchronizing, a method of manually controlling synchronization by a user, and a method of setting synchronization according to a synchronization switch.
  • Each synchronization mode application has different synchronization parameters, and different synchronization modes have different synchronization parameters carried in the synchronization process.
  • the application of the data cycle synchronization carries the synchronization parameter 1 when performing periodic synchronization
  • the application that is synchronized according to the synchronization switch carries the synchronization parameter 2 when performing synchronization
  • the application that the user manually controls the synchronization carries the synchronization parameter when performing synchronization.
  • the data synchronization mechanism (Syncmanager) determines different synchronization modes according to different synchronization parameters while controlling the application.
  • the application to be synchronized is an application waiting for data synchronization.
  • a WeChat application in an electronic device needs to perform data synchronization, and a WeChat application sends a data synchronization request, and the WeChat application is an application to be synchronized.
  • the synchronization parameter to be synchronized is a parameter carried by the application to be synchronized.
  • the first obtaining module 301 acquires the to-be-synchronized application, and acquires synchronization parameters carried by the to-be-synchronized application, so as to determine a synchronization manner of the application to be synchronized.
  • the screening module 302 is configured to filter the target application from the to-be-synchronized application according to the synchronization parameter.
  • the synchronization mode with the application to be synchronized may be determined according to the synchronization parameter carried by the application to be synchronized, or the synchronization type of the application to be synchronized may be determined according to the synchronization parameter carried by the application to be synchronized.
  • only the target application is filtered according to the synchronization parameter screening module 302 carried by the application to be synchronized.
  • the matching module 303 is configured to match the target application with an application in the preset whitelist. Please refer to the above for the specific matching method and process of the target application and the preset whitelist, and will not be described here.
  • the control module 304 is configured to allow the successfully matched target application to perform data synchronization when there is a target application with a successful match.
  • the control module 304 is configured to allow the successfully matched target application to perform data synchronization when there is a target application with a successful match.
  • the control module 304 is further configured to prevent the target application that fails the matching from performing data synchronization when there is a target application that fails to match. After the target application and the preset whitelist match fail, please refer to the above content, and details are not described herein.
  • FIG. 9 is another schematic structural diagram of a data synchronization control device according to an embodiment of the present application.
  • the data synchronization management device 300 can also include a second acquisition module 305 and a determination module 306.
  • the second obtaining module 305 is configured to obtain an original whitelist from the server. Specifically, please refer to the above content, and will not be described here.
  • the determining module 306 is configured to determine the original whitelist as the preset whitelist. Specifically, please refer to the above content, and will not be described here.
  • FIG. 10 is another schematic structural diagram of a data synchronization management device according to an embodiment of the present disclosure.
  • the data synchronization management device 300 can also include a third acquisition module 307 and a generation module 308.
  • the third obtaining module 307 is configured to acquire an application for synchronizing all data periods in the electronic device. Please refer to the above for details, and I will not repeat them here.
  • the generating module 308 is configured to generate a preset whitelist according to the application of the data cycle synchronization. Please refer to the above for details, and I will not repeat them here.
  • the generation module 308 includes a fourth acquisition module 3081 and a first write module 3082.
  • the fourth obtaining module 3081 is configured to acquire a synchronization period of an application synchronized for each data period. Please refer to the above for details, and I will not repeat them here.
  • the first writing module 3082 is configured to write an application whose synchronization period is greater than the preset period into the preset whitelist to generate a preset whitelist. Please refer to the above for details, and I will not repeat them here.
  • FIG. 11 is another schematic structural diagram of a data synchronization management device according to an embodiment of the present application.
  • the generation module 308 can also include a fifth acquisition module 3083 and a second write module 3084.
  • the fifth obtaining module 3083 is configured to acquire a historical running duration of an application synchronized for each data period. Please refer to the above for details, and I will not repeat them here.
  • the second writing module 3084 is configured to write an application whose historical running time is longer than the preset duration to the preset whitelist to generate a preset whitelist. Please refer to the above for details, and I will not repeat them here.
  • FIG. 12 is another schematic structural diagram of a data synchronization management device according to an embodiment of the present disclosure.
  • the data synchronization control device 300 can also include a first setting module 309.
  • the first setting module 309 is configured to set different priorities of all applications in the preset whitelist according to a preset rule. Please refer to the above for details, and I will not repeat them here.
  • control module 304 is further configured to: when the running status of the electronic device does not meet the preset operating condition, allow the application with the priority higher than the preset priority to perform data synchronization, and the prohibition priority is lower than the preset priority.
  • the level of the application is used for data synchronization, and the data to be synchronized in the application with the lower priority than the preset priority is stored in a buffer, and is allowed to be stored in the buffer when the current running condition of the electronic device meets the preset operating condition.
  • the data to be synchronized is synchronized. Please refer to the above for details, and I will not repeat them here.
  • the first setting module 309 includes a second setting module 3091 and a third setting module 3092.
  • the second setting module 3091 is configured to set different levels according to the type of the application in the preset white list, and allocate the applications in the preset white list to the corresponding levels. Please refer to the above for details, so I will not repeat them here.
  • the third setting module 3092 is configured to set different priorities for the different levels according to types of applications in the preset white list. Please refer to the above for details, so I will not repeat them here.
  • FIG. 13 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
  • the electronic device 400 includes a processor 401 and a memory 402.
  • the processor 401 is electrically connected to the memory 402.
  • the processor 401 is a control center of the electronic device 400, and connects various parts of the entire electronic device 400 using various interfaces and lines, by running or loading an application stored in the memory 402, and calling data stored in the memory 402, executing The various functions and processing data of the electronic device 400 enable overall monitoring of the electronic device 400.
  • the processor 401 in the electronic device 400 loads the instructions corresponding to the process of one or more applications into the memory 402 according to the following steps, and is executed by the processor 401 to be stored in the memory 402.
  • the application thus implementing various functions:
  • the target application that matches the success is allowed to perform data synchronization
  • the target application that failed to match is prohibited from performing data synchronization.
  • Memory 402 can be used to store applications and data.
  • the application stored in the memory 402 contains instructions executable in the processor 401.
  • Applications can form various functional modules.
  • the processor 401 executes various functional applications and data processing by running an application stored in the memory 402.
  • FIG. 14 is another schematic structural diagram of an electronic device.
  • the electronic device 400 further includes: a radio frequency circuit 403, a display screen 404, a control circuit 405, an input unit 406, and an audio circuit 407. Sensor 408 and power supply 409.
  • the processor 401 is electrically connected to the radio frequency circuit 403, the display screen 404, the control circuit 405, the input unit 406, the audio circuit 407, the sensor 408, and the power source 409, respectively.
  • the radio frequency circuit 403 is configured to transceive radio frequency signals to communicate with a server or other electronic device through a wireless communication network.
  • the display screen 404 can be used to display information entered by the user or information provided to the user as well as various graphical user interfaces of the terminal, which can be composed of images, text, icons, video, and any combination thereof.
  • the control circuit 405 is electrically connected to the display screen 404 for controlling the display screen 404 to display information.
  • the input unit 406 can be configured to receive input digits, character information, or user characteristic information (eg, fingerprints), and to generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function controls.
  • user characteristic information eg, fingerprints
  • the audio circuit 407 can provide an audio interface between the user and the terminal through a speaker and a microphone.
  • Sensor 408 is used to collect external environmental information.
  • Sensor 408 can include one or more of ambient brightness sensors, acceleration sensors, gyroscopes, and the like.
  • Power source 409 is used to power various components of electronic device 400.
  • the power supply 409 can be logically coupled to the processor 401 through a power management system to enable functions such as managing charging, discharging, and power management through the power management system.
  • the electronic device 400 may further include a camera, a Bluetooth module, and the like, and details are not described herein.
  • the application of the electronic device side will perform data synchronization during the running process, especially the application of the data cycle synchronization, and the synchronization will be performed periodically. If the cycle synchronization of the application is too frequent, it will increase the battery power consumption and reduce the running speed of the electronic device.
  • the electronic device in the embodiment of the present application can prohibit some applications that do not need synchronization to perform cycle synchronization, in particular, prohibit applications with high synchronization frequency from performing data synchronization, effectively control applications, reduce power consumption of electronic devices, and improve operating speed of electronic devices.
  • the embodiment of the present application further provides a storage medium, where the storage medium stores a plurality of instructions, and the instruction is adapted to be loaded by a processor to execute the data synchronization management method described in any of the foregoing embodiments.
  • the medium may include, but is not limited to, a read only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Human Computer Interaction (AREA)
  • Power Sources (AREA)
  • Telephone Function (AREA)
  • Stored Programmes (AREA)

Abstract

本申请公开了一种数据同步管控方法、装置及电子设备，数据同步管控方法包括：获取电子设备中的待同步应用以及待同步应用的同步参数，待同步应用为等待进行数据同步的应用；根据同步参数从待同步应用中筛选出目标应用；将目标应用与预设白名单中的应用进行匹配；当存在匹配成功的目标应用时，允许匹配成功的目标应用进行数据同步；当存在匹配失败的目标应用时，禁止匹配失败的目标应用进行数据同步。

Description

数据同步管控方法、装置及电子设备
本申请要求于2017年7月31日提交中国专利局、申请号为201710646418.3、申请名称为“数据同步管控方法、装置、存储介质及电子设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及移动设备技术领域，具体涉及一种数据同步管控方法、装置及电子设备。
背景技术
随着电子设备技术的快速发展，电子设备的功能越来越多。比如，电子设备端通过各种应用实现通信、观看视频、听音乐等。具体比如，使用即时通讯软件进行视频聊天。通常，电子设备端的应用在运行过程中，会进行数据同步，尤其是数据周期同步的应用，应用中的数据会定时进行同步。
发明内容
本申请实施例提供一种数据同步管控方法、装置及电子设备，可以节省电子设备电量、提升电子设备的运行速度。
第一方面，本申请实施例提供一种数据同步管控方法，应用于电子设备中，所述数据同步管控方法包括：
获取所述电子设备中的待同步应用以及所述待同步应用的同步参数，所述待同步应用为等待进行数据同步的应用；
根据所述同步参数从所述待同步应用中筛选出目标应用；
将所述目标应用于预设白名单中的应用进行匹配；
当存在匹配成功的目标应用时，允许所述匹配成功的目标应用进行数据同步；当存在匹配失败的目标应用时，禁止所述匹配失败的目标应用进行数据同步。
第二方面，本申请实施例还提供一种数据同步管控装置，所述数据同步管控装置包括：
第一获取模块，用于获取所述电子设备中的待同步应用以及所述待同步应用的同步参数，所述待同步应用为等待进行数据同步的应用；
筛选模块，用于根据所述同步参数从所述待同步应用中筛选出目标应用；
匹配模块，用于将所述目标应用于预设白名单中的应用进行匹配；
管控模块，用于当存在匹配成功的目标应用时，允许所述匹配成功的目标应用进行数据同步；
所述管控模块，还用于当存在匹配失败的目标应用时，禁止所述匹配失败的目标应用进行数据同步。
第三方面，本申请实施例还提供一种电子设备，所述电子设备包括处理器和存储器，所述处理器和所述存储器电性连接，所述存储器用于存储指令和数据，所述处理器用于执行如上所述的数据同步管控方法。
附图说明
下面结合附图，通过对本申请的具体实施方式详细描述，将使本申请的技术方案及其它有益效果显而易见。
图1为本申请实施例提供的数据同步管控方法的场景示意图。
图2为本申请实施例提供的数据同步管控方法的另一场景示意图。
图3为本申请实施例提供的数据同步管控方法的流程示意图。
图4为本申请实施例提供的数据同步管控方法的另一流程示意图。
图5为本申请实施例提供的预设白名单的优先级排列表。
图6为本申请实施例提供的预设白名单的另一优先级排列表。
图7为本申请实施例提供的预设白名单的另一优先级排列表。
图8为本申请实施例提供的数据同步管控装置的结构示意图。
图9为本申请实施例提供的数据同步管控装置的另一结构示意图。
图10为本申请实施例提供的数据同步管控装置的另一结构示意图。
图11为本申请实施例提供的数据同步管控装置的另一结构示意图。
图12为本申请实施例提供的数据同步管控装置的另一结构示意图。
图13为本申请实施例提供的电子设备的结构示意图。
图14为本申请实施例提供的电子设备的另一结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。
本申请中的术语“第一”和“第二”等是用于区别不同对象，而不是用于描述特定顺序。
本申请实施例提供了一种数据同步管控方法、装置及电子设备。
请参阅图1，该图1为本申请实施例提供的数据同步管控方法的场景示意图，该场景可以包括电子设备10，该电子设备10可以包括平板、PC(个人计算机，Personal Computer)、手机等，该电子设备10具备储存单元并安装有微处理器而具有运算能力。该电子设备10以手机为例进行说明，手机10从本地获取白名单11，手机10可以预先存储有白名单11，手机10中存储的白名单11可以是用户手动设置形成的，也可以根据预设的规则形成的。当然，该白名单11也可以是提前从服务器端下载得到的。手机10获取到白名单11后，将白名单11中的应用与数据周期同步应用进行匹配，当存储匹配成功的应用，则允许该匹配成功的应用同步；而当存在匹配失败的应用，则禁止该匹配失败的应用同步。从而，可以禁止一些无需同步的应用进行周期同步，尤其是禁止同步频率较高的应用进行数据同步，有效管控数据周期同步的应用，减少电子设备的耗电量，提升电子设备的运行速度。
该场景可以包括数据同步管控装置300，该数据同步管控装置300具体可以集成在电子设备10中。该数据同步管控装置300主要用于获取电子设备中的待同步应用以及待同步应用的同步参数，其中，待同步应用为等待数据进行同步的应用；根据同步参数从待同步应用中筛选出目标应用；将目标应用与预设白名单中的应用进行匹配；当存在匹配成功的目标应用时，允许匹配成功的目标应用进行数据同步；当存在匹配失败的目标应用时，禁止匹配失败的目标应用进行数据同步。
可以理解的是，目标应用在待同步应用中筛选出，目标应用也为等待数据进行同步的应用，或者说目标应用可以进行数据同步。
请参阅图2，该图2为本申请实施例提供的数据同步管控方法的另一场景示意图，该场景可以包括电子设备10和服务器20，该场景与图1的区别在于：电子设备10可以直接从服务器20获取白名单11。电子设备10获取到白名单11后请参阅以上内容，在此不再赘述。该场景还可以包括数据同步管控装置300，该数据同步管控装置300可以集成于电子设备10中，具体可以参阅图1中的数据同步管控装置，在此不再赘述。
在本申请实施例中，将从数据同步管控装置的角度进行描述，该数据同步管控装置具体可以集成在平板、PC、手机等具备储存单元并安装有微处理器而具有运算能力的电子设备中。
一种数据同步管控方法，应用于电子设备中，其包括：
获取所述电子设备中的待同步应用以及所述待同步应用的同步参数，所述待同步应用为等待数据进行同步的应用；
根据所述同步参数从所述待同步应用中筛选出目标应用；
将所述目标应用与预设白名单中的应用进行匹配；
当存在匹配成功的目标应用时，允许所述匹配成功的目标应用进行数据同步；
当存在匹配失败的目标应用时，禁止所述匹配失败的目标应用进行数据同步。
在一些实施例中，所述将所述目标应用与预设白名单进行匹配的步骤之前，所述数据同步管控方法还包括：
从服务器获取原始白名单；
将所述原始白名单确定为预设白名单。
在一些实施例中，所述将所述目标应用与预设白名单进行匹配的步骤之前，所述数据同步管控方法还包括：
获取所述电子设备中所有数据周期同步的应用；
根据所述数据周期同步的应用生成预设白名单。
在一些实施例中，所述根据所述数据周期同步的应用生成预设白名单的步骤，具体包括：
获取每一所述数据周期同步的应用的同步周期；
将所述同步周期大于预设周期的应用写入预设白名单中，以生成所述预设白名单。
在一些实施例中，所述根据所述数据周期同步的应用生成预设白名单，包括：
获取每一数据周期同步的应用的历史运行时长；
将所述历史运行时长大于预设时长的应用写入预设白名单中，以生成所述预设白名单。
在一些实施例中，所述根据所述数据周期同步的应用生成预设白名单，包括：
获取每一所述数据周期同步的应用的历史运行次数；
将所述历史运行次数大于预设次数的应用写入预设白名单中，以生成所述预设白名单。
在一些实施例中，所述当存在匹配成功的目标应用时，允许所述匹配成功的目标应用进行数据同步的步骤之后，所述数据同步管控方法还包括：
根据预设规则将所述预设白名单中所有应用设置不同的优先级。
在一些实施例中，所述根据预设规则将预设白名单中的所有应用设置不同的优先级的步骤之后，所述数据同步管控方法还包括：
当所述电子设备的运行状况未满足预设运行状况时，允许所述优先级高于预设优先级的应用进行数据同步，禁止所述优先级低于预设优先级的应用进行数据同步，并将所述优先级低于预设优先级的应用中待同步的数据存储于一缓存器中，直至所述电子设备当前运行状况满足所述预设运行状况时，允许存储于所述缓存器中待同步的数据进行同步。
在一些实施例中，所述根据预设规则将所述预设白名单中所有应用设置不同的优先级的步骤，具体包括：
根据所述预设白名单中应用的类型设置不同的层级，并将所述预设白名单中的应用分别分配到对应的层级中；
根据所述预设白名单中应用的类型对所述不同层级设置不同的优先级。
请参阅图3，图3为本申请实施例提供的数据同步管控方法的流程示意图。该数据同步管控方法可以包括：
在步骤S101中，获取电子设备中的待同步应用以及待同步应用的同步参数。
需要说明的是，应用中数据的同步方式具有多种，应用中数据的同步方式主要包括以下三种方式：周期同步的方式、用户手动控制同步的方式、根据同步开关设置同步的方式。每一种同步方式的应用均具有不同的同步参数，不同的同步方式在同步过程中所携带的同步参数不同。比如，数据周期同步的应用在进行数据周期同步时携带有同步参数1；根据同步开关设置同步的应用在进行数据同步时携带有同步参数2；用户手动控制同步的应用在进 行数据同步时携带有同步参数3。数据同步机制(Syncmanager)在控制应用进行同时根据不同的同步参数判断出不同的同步方式。
其中，待同步应用为等待进行数据同步的应用。比如，电子设备中的微信应用需要进行数据同步，微信应用发送数据同步请求，则该微信应用为待同步应用。其中，待同步应用的同步参数为该待同步应用若携带的参数。
在一些实施例中，当有待同步应用需要进行数据同步时，获取该待同步应用，同时获取该待同步应用所携带的同步参数，以便确定出待同步应用中数据的同步方式。
在步骤S102中，根据同步参数从待同步应用中筛选出目标应用。
在一些实施例中，根据待同步应用所携带的同步参数可以确定出待同步应用中数据的同步方式，或者说根据待同步应用所携带的同步参数可以确定出待同步应用中数据的同步类型。根据待同步应用所携带的同步参数可以筛选出数据周期同步的目标应用。
在步骤S103中，将目标应用与预设白名单中的应用进行匹配。
其中，该预设白名单包括有至少一个数据周期同步的应用，该应用可以进行数据周期同步，或者说该应用具有周期同步功能。本申请实施例预设白名单中的应用均可以进行数据周期同步。在一些实施例中，该预设白名单可以从服务器中获取，具体的，该预设白名单从服务器端获取的方式包括以下步骤：
(1)从服务器获取原始白名单；
(2)将原始白名单确定为预设白名单。
需要说明的是，在一些实施例中，预设白名单也可以直接从电子设备中获取，电子设备端的预设白名单可以预先从服务器端下载，也可以根据用户手动控制形成，还可以根据预设规则形成。具体的，该预设白名单从电子设备端获取的方式包括以下步骤：
(11)获取电子设备中所有数据周期同步的应用；
(12)根据数据周期同步的生成预设白名单。
在一些实施例中，获取电子设备中所有数据周期同步的应用，并根据数据周期同步的成预设白名单具体包括以下步骤：
(13)获取每一数据周期同步的同步周期；
(14)将同步周期大于预设周期的应用写入预设白名单中，以生成预设白名单。
其中，本申请实施例数据周期同步的应用可以与目标应用相同，在此可以将数据周期同步的应用或目标应用简称为应用，应用的同步周期即为应用两次同步的时间间隔。需要说明的是，应用在经过时间间隔进行数据同步，比如时间间隔为24小时，则该同步周期为24小时同步1次。若时间间隔为1小时，则该同步周期为1小时同步1次。
其中，预设周期可以根据用户的需求进行设定，比如该预设周期为12小时同步1次。
在一些实施例，当有数据周期同步的应用的同步周期大于预设周期时，将该同步周期大于预设周期的应用写入预设白名单中，以生成预设白名单。比如，某一数据周期同步的应用，其同步周期为24小时同步1次，该预设周期为12小时同步1次，则该应用的同步周期大于预设周期，将该数据周期同步的应用写入到预设白名单中。而当同步周期小于预设周期时，则不将对应的应用写入到白名单中。
在一些实施例中，获取电子设备中所有数据周期同步的应用，并根据数据周期同步的应用生成预设白名单具体还包括以下步骤：
(15)获取每一数据周期同步的应用的历史运行时长；
(16)将历史运行时长大于预设时长的数据周期同步的应用写入预设白名单中，以生成预设白名单。
具体的，可以获取数据周期同步的应用的历史运行时长，也可以在一段时间内获取数据周期同步的应用的历史运行时长。比如，在一个月内，获取数据周期同步的应用的历史 运行时长，该历史运行时长可以为1小时、10小时、20小时、50小时等。
其中，该预设时长可以根据用户的需求进行设置，比如该预设时长设置为25小时。
在一些实施例中，将数据周期同步的应用的历史运行时长和预设时长进行比对，当数据周期同步的历史运行时长大于预设时长时，将该历史运行时长大于预设时长的应用写入预设白名单中，以生成预设白名单。比如，历史运行时长为41小时，预设时长为25小时，则历史运行时长大于预设时长，进而将对应的应用写入到预设白名单中。而当历史运行时长小于预设时长时，则不将小于预设时长的应用写入预设白名单中。
在一些实施例中，获取电子设备中所有数据周期同步的应用，并根据数据周期同步的应用生成预设白名单具体还包括以下步骤：
(17)获取每一数据周期同步的应用的历史运行次数；
(18)将历史运行次数大于预设次数的应用写入预设白名单中，以生成预设白名单。
具体的，可以获取数据周期同步的应用的历史运行次数，也可以在一段时间内获取目标应用的历史运行次数。比如，在一个月内，获取数据周期同步的应用的历史运行次数，该历史运行次数可以为1次、10次、30次、50次、60次等。
其中，该预设次数可以根据用户的需求进行设置，比如该预设次数设置为15次。
在一些实施例中，将数据周期同步的应用的历史运行次数和预设次数进行比对，当数据周期同步的应用的历史运行次数大于预设次数时，将该历史运行次数大于预设次数的应用写入预设白名单中，以生成预设白名单。比如，历史运行次数为30次，预设次数为15次，则历史运行次数大于预设次数，进而将对应的应用写入到预设白名单中。而当历史运行次数小于预设次数时，则不将小于预设次数的数据周期同步的应用写入预设白名单中。
在步骤S104中，当存在匹配成功的目标应用时，允许匹配成功的目标应用进行数据同步。
在一些实施例中，将目标应用和预设白名单中的应用匹配过程中，当目标应用在预设白名单中匹配到对应的应用时，也就是存在匹配成功的目标应用时，则允许该匹配成功的目标应用进行数据同步，从而调用、并启动数据同步机制，通过该数据同步机制控制目标程序进行数据同步。
在步骤S105中，当存在匹配失败的目标应用时，禁止匹配失败的目标应用进行数据同步。
在一些实施例中，将目标应用和预设白名单中的应用匹配过程中，当目标应用在预设白名单中未匹配到对应的应用时，也就是存在匹配失败的目标应用时，则禁止该匹配失败的目标应用进行数据同步，从而不调用、也不启动数据同步机制，使得该匹配失败的目标应用不进行数据同步，禁止一些同步过于频繁的应用进行数据同步，有效管控数据周期同步的应用，减少电子设备的耗电量，提升电子设备的运行速度。
在实际检测过程中，经过大数据统计得出超过百分之二十的电子设备日均拦截同步次数在500次以上，导致电子设备的电量在12小时的待机过程中被消耗百分之四，甚至有些应用进行恶意同步，给用户的使用带来威胁，导致安全性降低。而本申请实施例，在预设白名单中未匹配到对应的数据周期同步的应用时，禁止未匹配到的应用进行数据同步，在节省电子设备电量的前提下，可以提升电子设备的运行速度，提高电子设备的安全性，提升用户的使用体验。
在一些实施例中，当在预设白名单中未匹配到对应的数据周期同步的应用，则发出提示信息以提示目标应用为异常应用，从而便于用户了解到电子设备中存在过于频繁进行数据周期同步的应用，有效防止应用进行恶意同步。该提示信息可以为提示消息、提示语音等等。
请参阅图4，图4为本申请实施例提供的数据同步管控方法的另一流程示意图。该数据 同步管控方法包括以下步骤：
在步骤S201中，获取电子设备中的待同步应用以及待同步应用的同步参数。详情请参阅步骤S101，在此不再赘述。
在步骤S202中，根据同步参数从待同步应用中筛选出目标应用。详情请参阅步骤S102，在此不再赘述。
在步骤S203中，将目标应用于预设白名单中的应用进行匹配。详情请参阅步骤S103，在此不再赘述。
在步骤S204中，当存在匹配成功的目标应用时，允许匹配成功的目标应用进行数据同步。详情请参阅步骤S104，在此不再赘述。
在步骤S205中，根据预设规则将预设白名单中的所有应用设置不同的优先级。
。在一些实施例中，该预设规则，可以是所有应用的历史运行时长，进一步的，可以是在一段时间内所有应用的历史运行时长。将所有数据周期同步的应用根据各自的历史运行时长进行排序，按照历史运行时长的长至短进行排序，将历史运行时长较长的应用设置优先级高。
请参阅图5，图5为本申请实施例提供的预设白名单的优先级排列表。本申请实施例将历史运行时长最长的设置优先级最高，然后依次设置优先级级别。比如，应用A的历史运行时长为50小时，具体的可以是在一个月的运行时长。应用B的历史运行时长为45小时，应用C的历史运行时长为40小时，应用D的历史运行时长为35小时，应用E的历史运行时长为30小时，应用F的历史运行时长为25小时，则预设白名单12中应用A、应用B、应用C、应用D、应用E和应用F的优先级从高到低依次为应用A、应用B、应用C、应用D、应用E和应用F。需要说明的是，图5仅示出部分应用，并未对预设白名单12中的应用个数进行限制。
在一些实施例中，该预设规则，可以是所有应用的同步周期，将所有数据周期同步的应用根据各自的同步周期进行排序，按照同步周期的长至短进行排序，将同步周期较长的应用设置优先级高。
请参阅图6，图6为本申请实施例提供的预设白名单的另一优先级排列表。本申请实施例将同步周期最长的设置优先级最高，然后依次设置优先级级别。比如，应用A的同步周期为12小时，应用B的同步周期为10小时，应用C的同步周期为8小时，应用D的同步周期为6小时，应用E的同步周期为5小时，应用F的同步周期为4小时，则预设白名单13中应用A、应用B、应用C、应用D、应用E和应用F的优先级从高到低依次为应用A、应用B、应用C、应用D、应用E和应用F。需要说明的是，图6仅示出部分应用，并未对预设白名单13中的应用个数进行限制。
在一些实施例中，该预设规则，还可以是所有应用的运行次数，将所有数据周期同步的应用根据各自的运行次数进行排序，按照运行次数的多至少进行排序，将运行次数较多的应用设置优先级高。申请实施例将运行次数最多的设置优先级最高，然后依次设置优先级级别，具体请参阅图5和图6，在此不再一一举例说明。
在一些实施例中，根据预设规则将预设白名单中的所有应用设置不同的优先级具体可以包括以下步骤：
(21)根据预设白名单中应用的类型设置不同的层级，并将预设白名单中的应用分别分配到对应的层级中；
(22)根据预设白名单中应用的类型对不同层级设置不同的优先级。
请参阅图7，图7为本申请实施例提供的预设白名单的另一优先级排列表。根据预设白名单14中应用的类型不同而设置不同的层级141，比如：一个层级141中的应用类型为银行类型应用，该银行类型应用包括应用A、应用B、应用C，将该银行类应用的优先级设置为最高。一个层级142中的应用类型为即时通讯应用，该即时通讯应用包括应用D和应用E，该即 使通讯应用的优先级次于层级141中的应用优先级。其它层级中的应用不再一一举例说明，可以根据用户需求进行设置。该预设白名单14中的层级优先级从高到低的排列方式为层级141、层级142、层级143、层级144、层级145、层级146和层级147。需要说明的是，图7仅示出部分应用，并未对预设白名单14中的应用个数进行限制。
在步骤S206中，当电子设备的运行状况未满足预设运行状况时，允许优先级高于预设优先级的应用进行数据同步，禁止优先级低于预设优先级的应用进行数据同步，并将优先级低于预设优先级的应用中待同步的数据存储于一缓存器中，直至电子设备当前运行状况满足预设运行状况时，允许存储于缓存器中待同步的数据进行同步。
其中，该电子设备的运行状况可以包括电子设备中在某一时间具有多个应用进行数据同步、电池电量低、运行速度慢等。该预设状况与电子设备的运行状况相对应，比如当电子设备的运行状况为电池电量低时，该预设状况为预设电池电量，具体的，当电子设备的电池电量为百分之五时，该预设电池电量可以设定为百分之八，则电子设备的电池电量不足百分之八，未满足预设状况，则将优先级低于预设优先级的应用进行数据同步，而禁止优先级低于预设优先级的应用进行数据同步。从而，可以优先同步优先级高的应用，确保重要的应用能优先数据同步；不重要的应用不影响用户使用电子设备，错开电子设备的使用高峰期，提高了数据同步的效率。
其中，该预设优先级可以根据用户需求进行设置，比如预设优先级位于所有优先级的中间位置，该预设优先级也可以仅限定几个优先级靠前的应用。
在步骤S207中，当存在匹配失败的目标应用时，禁止匹配失败的目标应用进行数据同步。详情请参阅步骤S105，在此不再赘述。
为便于更好的实施本申请实施例提供的数据同步管控方法，本申请实施例还提供一种基于数据同步管控方法的装置。其中名词的含义与上述数据同步管控方法中的相同，具体实现细节可以参考方法实施例中的说明。
一种数据同步管控装置，应用于电子设备中，其包括：
第一获取模块，用于获取所述电子设备中的待同步应用以及所述待同步应用的同步参数，待同步应用为等待进行数据同步的应用；
筛选模块，用于根据所述同步参数从所述待同步应用中筛选出目标应用；
匹配模块，用于将所述目标应用于预设白名单中的应用进行匹配；
管控模块，用于当存在匹配成功的目标应用时，允许所述匹配成功的目标应用进行数据同步；
所述管控模块，还用于当存在匹配失败的目标应用时，禁止所述匹配失败的目标应用进行数据同步。
在一些实施例中，所述数据同步管控装置还包括第二获取模块和确定模块；
所述第二获取模块，用于从服务器获取原始白名单；
所述确定模块，用于将所述原始白名单确定为预设白名单。
在一些实施例中，所述数据同步管控装置还包括第三获取模块和生成模块；
所述第三获取模块，用于获取所述电子设备中所有数据周期同步的应用；
所述生成模块，用于根据所述数据周期同步的应用生成预设白名单。
在一些实施例中，所述生成模块包括：
第四获取模块，用于获取每一所述数据周期同步的应用的同步周期；
第一写入模块，用于将所述同步周期大于预设周期的应用写入预设白名单中，以生成所述预设白名单。
在一些实施例中，所述生成模块还包括：
第五获取模块，用于获取每一数据周期同步的应用的历史运行时长；
第二写入模块，用于将所述历史运行时长大于预设时长的应用写入预设白名单中，以生成所述预设白名单。
在一些实施例中，所述数据同步管控装置还包括第一设置模块；
所述第一设置模块，用于根据预设规则将所述预设白名单中所有的应用设置不同的优先级；
所述管控模块，还用于当所述电子设备的运行状况未满足预设运行状况时，允许所述优先级高于预设优先级的应用进行数据同步，禁止所述优先级低于预设优先级的应用进行数据同步，并将所述优先级低于预设优先级的应用中待同步的数据存储于一缓存器中，直至所述电子设备当前运行状况满足所述预设运行状况时，允许存储于所述缓存器中待同步的数据进行同步。
在一些实施例中，所述第一设置模块包括：
第二设置模块，用于根据所述预设白名单中应用的类型设置不同的层级，并将所述预设白名单中的应用分别分配到对应的层级中；
第三设置模块，用于根据所述预设白名单中应用的类型对所述不同层级设置不同的优先级。
请参阅图8，图8为本申请实施例提供的数据同步管控装置的结构示意图。本申请实施例数据同步管控装置300包括有第一获取模块301、筛选模块302匹配模块303和管控模块304。
其中，第一获取模块301，用于获取电子设备中的待同步应用以及待同步应用的同步参数。
需要说明的是，应用中数据的同步方式具有多种，应用中数据的同步方式主要包括以下三种方式：周期同步的方式、用户手动控制同步的方式、根据同步开关设置同步的方式。每一种同步方式的应用均具有不同的同步参数，不同的同步方式在同步过程中所携带的同步参数不同。比如，数据周期同步的应用在进行周期同步时携带有同步参数1；根据同步开关设置同步的应用在进行同步时携带有同步参数2；用户手动控制同步的应用在进行同步时携带有同步参数3。数据同步机制(Syncmanager)在控制应用进行同时根据不同的同步参数判断出不同的同步方式。
其中，待同步应用为等待进行数据同步的应用。比如，电子设备中的微信应用需要进行数据同步，微信应用发送数据同步请求，该微信应用为待同步应用。其中，待同步应用的同步参数为该待同步应用若携带的参数。
在一些实施例中，当有待同步应用需要进行同步时，第一获取模块301获取该待同步应用，同时获取该待同步应用所携带的同步参数，以便确定出该待同步应用的同步方式。
其中，筛选模块302，用于根据同步参数从待同步应用中筛选出目标应用。
在一些实施例中，根据带待同步应用所携带的同步参数可以确定出带待同步应用的同步方式，或者说根据待同步应用所携带的同步参数可以确定出带待同步应用的同步类型。本申请实施例根据待同步应用所携带的同步参数筛选模块302仅筛选出目标应用。
其中，匹配模块303，用于将目标应用与预设白名单中的应用进行匹配。目标应用和预设白名单的具体匹配方式及过程请参阅以上内容，在此不再赘述。
其中，管控模块304，用于当存在匹配成功的目标应用时，允许匹配成功的目标应用进行数据同步。目标应用和预设白名单匹配成功后具体进行数据同步请参阅以上内容，在此不再赘述。
其中，管控模块304，还用于当存在匹配失败的目标应用时，禁止匹配失败的目标应用进行数据同步。目标应用和预设白名单匹配失败后具体请参阅以上内容，在此不再赘述。
请参阅图9，图9为本申请实施例提供的数据同步管控装置的另一结构示意图。该数据同步管控装置300还可以包括第二获取模块305和确定模块306。
其中，第二获取模块305，用于从服务器获取原始白名单。具体的，请参阅以上内容，在此不再赘述。
其中，确定模块306，用于将原始白名单确定为预设白名单。具体的，请参阅以上内容，在此不再赘述。
请参阅图10，图10为本申请实施例提供的数据同步管控装置的另一结构示意图。该数据同步管控装置300还可以包括第三获取模块307和生成模块308。
其中，第三获取模块307，用于获取电子设备中所有数据周期同步的应用。具体请参阅以上内容，在此不再赘述。
其中，生成模块308，用于根据数据周期同步的应用生成预设白名单。具体请参阅以上内容，在此不再赘述。
在一些实施例中，生成模块308包括第四获取模块3081和第一写入模块3082。
其中，第四获取模块3081，用于获取每一数据周期同步的应用的同步周期。具体请参阅以上内容，在此不再赘述。
其中，第一写入模块3082，用于将同步周期大于预设周期的应用写入预设白名单中，以生成预设白名单。具体请参阅以上内容，在此不再赘述。
请参阅图11，图11为本申请实施例提供的数据同步管控装置的另一结构示意图。在一些实施例中，生成模块308还可以包括第五获取模块3083和第二写入模块3084。
其中，第五获取模块3083，用于获取每一数据周期同步的应用的历史运行时长。具体请参阅以上内容，在此不再赘述。
其中，第二写入模块3084，用于将历史运行时长大于预设时长的应用写入预设白名单中，以生成预设白名单。具体请参阅以上内容，在此不再赘述。
请参阅图12，图12为本申请实施例提供的数据同步管控装置的另一结构示意图。该数据同步管控装置300还可以包括第一设置模块309。
其中，第一设置模块309，用于根据预设规则将预设白名单中所有的应用设置不同的优先级。具体请参阅以上内容，在此不再赘述。
在一些实施例中，管控模块304，还用于当电子设备的运行状况未满足预设运行状况时，允许优先级高于预设优先级的应用进行数据同步，禁止优先级低于预设优先级的应用进行数据同步，并将优先级低于预设优先级的应用中待同步的数据存储于一缓存器中，直至电子设备当前运行状况满足预设运行状况时，允许存储于缓存器中待同步的数据进行同步。具体请参阅以上内容，在此不再赘述。
在一些实施例中，第一设置模块309包括第二设置模块3091和第三设置模块3092。
其中，第二设置模块3091，用于根据所述预设白名单中应用的类型设置不同的层级，并将所述预设白名单中的应用分别分配到对应的层级中。详情请参阅以上内容，在此不再赘述。
其中，第三设置模块3092，用于根据所述预设白名单中应用的类型对所述不同层级设置不同的优先级。详情请参阅以上内容，在此不再赘述。
本申请实施例还提供一种电子设备400。该电子设备400可以是智能手机、平板电脑等设备。如图13所示，图13为本申请实施例提供的电子设备的结构示意图，电子设备400包括：处理器401和存储器402。其中，处理器401与存储器402电性连接。
处理器401是电子设备400的控制中心，利用各种接口和线路连接整个电子设备400的各个部分，通过运行或加载存储在存储器402内的应用程序，以及调用存储在存储器402内的数据，执行电子设备400的各种功能和处理数据，从而对电子设备400进行整体监控。
在一些实施例中，电子设备400中的处理器401会按照如下的步骤，将一个或一个以上的应用程序的进程对应的指令加载到存储器402中，并由处理器401来运行存储在存储器402 中的应用程序，从而实现各种功能：
获取电子设备中的待同步应用以及待同步应用的同步参数，所述待同步应用为等待进行数据同步的应用；
根据同步参数从待同步应用中筛选出目标应用；
将目标应用与预设白名单中的应用进行匹配；
当存在匹配成功的目标应用时，允许匹配成功的目标应用进行数据同步；
当存在匹配失败的目标应用时，禁止匹配失败的目标应用进行数据同步。
存储器402可用于存储应用程序和数据。存储器402存储的应用程序中包含有可在处理器401中执行的指令。应用程序可以组成各种功能模块。处理器401通过运行存储在存储器402的应用程序，从而执行各种功能应用以及数据处理。
在一些实施例中，请一并参阅图14，图14为电子设备的另一结构示意图，电子设备400还包括：射频电路403、显示屏404、控制电路405、输入单元406、音频电路407、传感器408以及电源409。其中，处理器401分别与射频电路403、显示屏404、控制电路405、输入单元406、音频电路407、传感器408以及电源409电性连接。
射频电路403用于收发射频信号，以通过无线通信网络与服务器或其他电子设备进行通信。
显示屏404可用于显示由用户输入的信息或提供给用户的信息以及终端的各种图形用户接口，这些图形用户接口可以由图像、文本、图标、视频和其任意组合来构成。
控制电路405与显示屏404电性连接，用于控制显示屏404显示信息。
输入单元406可用于接收输入的数字、字符信息或用户特征信息(例如指纹)，以及产生与用户设置以及功能控制有关的键盘、鼠标、操作杆、光学或者轨迹球信号输入。
音频电路407可通过扬声器、传声器提供用户与终端之间的音频接口。
传感器408用于采集外部环境信息。传感器408可以包括环境亮度传感器、加速度传感器、陀螺仪等传感器中的一种或多种。
电源409用于给电子设备400的各个部件供电。在一些实施例中，电源409可以通过电源管理系统与处理器401逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。
尽管图14中未示出，电子设备400还可以包括摄像头、蓝牙模块等，在此不再赘述。
可以理解的是，电子设备端的应用在运行过程中，会进行数据同步，尤其是数据周期同步的应用，会定时进行同步。若应用的周期同步过于频繁，会增加电池耗电量，降低电子设备端的运行速度。本申请实施例的电子设备可以禁止一些无需同步的应用进行周期同步，尤其是禁止同步频率较高的应用进行数据同步，有效管控应用，减少电子设备的耗电量，提升电子设备的运行速度。
本申请实施例还提供一种存储介质，该存储介质中存储有多条指令，该指令适于由处理器加载以执行上述任一实施例所述的数据同步管控方法。
需要说明的是，本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序可以存储于计算机可读的介质中，该介质可以包括但不限于：只读存储器(ROM，Read Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁盘或光盘等。
以上对本申请实施例所提供的数据同步管控方法、装置及电子设备进行了详细介绍，本文中应用了具体个例对本申请的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本申请的方法及其核心思想；同时，对于本领域的技术人员，依据本申请的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本申请的限制。

Claims (19)

  1. 一种数据同步管控方法，应用于电子设备中，其包括：
    获取所述电子设备中的待同步应用以及所述待同步应用的同步参数，所述待同步应用为等待进行数据同步的应用；
    根据所述同步参数从所述待同步应用中筛选出目标应用；
    将所述目标应用与预设白名单中的应用进行匹配；
    当存在匹配成功的目标应用时，允许所述匹配成功的目标应用进行数据同步；
    当存在匹配失败的目标应用时，禁止所述匹配失败的目标应用进行数据同步。
  2. 根据权利要求1所述的数据同步管控方法，其中，所述将所述目标应用与预设白名单进行匹配的步骤之前，所述数据同步管控方法还包括：
    从服务器获取原始白名单；
    将所述原始白名单确定为预设白名单。
  3. 根据权利要求1所述的数据同步管控方法，其中，所述将所述目标应用与预设白名单进行匹配的步骤之前，所述数据同步管控方法还包括：
    获取所述电子设备中所有数据周期同步的应用；
    根据所述数据周期同步的应用生成预设白名单。
  4. 根据权利要求3所述的数据同步管控方法，其中，所述根据所述数据周期同步的应用生成预设白名单的步骤，具体包括：
    获取每一所述数据周期同步的应用的同步周期；
    将所述同步周期大于预设周期的应用写入预设白名单中，以生成所述预设白名单。
  5. 根据权利要求3所述的数据同步管控方法，其中，所述根据所述数据周期同步的应用生成预设白名单，包括：
    获取每一数据周期同步的应用的历史运行时长；
    将所述历史运行时长大于预设时长的应用写入预设白名单中，以生成所述预设白名单。
  6. 根据权利要求3所述的数据同步管控方法，其特征在于，所述根据所述数据周期同步的应用生成预设白名单，包括：
    获取每一所述数据周期同步的应用的历史运行次数；
    将所述历史运行次数大于预设次数的应用写入预设白名单中，以生成所述预设白名单。
  7. 根据权利要求3所述的数据同步管控方法，其中，所述当存在匹配成功的目标应用时，允许所述匹配成功的目标应用进行数据同步的步骤之后，所述数据同步管控方法还包括：
    根据预设规则将所述预设白名单中所有应用设置不同的优先级。
  8. 根据权利要求7所述的数据同步管控方法，其中，所述根据预设规则将预设白名单中的所有应用设置不同的优先级的步骤之后，所述数据同步管控方法还包括：
    当所述电子设备的运行状况未满足预设运行状况时，允许所述优先级高于预设优先级的应用进行数据同步，禁止所述优先级低于预设优先级的应用进行数据同步，并将所述优先级低于预设优先级的应用中待同步的数据存储于一缓存器中，直至所述电子设备当前运行状况满足所述预设运行状况时，允许存储于所述缓存器中待同步的数据进行同步。
  9. 根据权利要求8所述的数据同步管控方法，其中，所述根据预设规则将所述预设白名单中所有应用设置不同的优先级的步骤，具体包括：
    根据所述预设白名单中应用的类型设置不同的层级，并将所述预设白名单中的应用分别分配到对应的层级中；
    根据所述预设白名单中应用的类型对所述不同层级设置不同的优先级。
  10. 根据权利要求1所述的数据同步管控方法，其中，所述当存在匹配成功的目标应 用时，允许所述匹配成功的目标应用进行数据同步的步骤之后，所述数据同步管控方法还包括：
    根据预设规则将所述预设白名单中所有应用设置不同的优先级；
    当所述电子设备的运行状况未满足预设运行状况时，允许所述优先级高于预设优先级的应用进行数据同步，禁止所述优先级低于预设优先级的应用进行数据同步，并将所述优先级低于预设优先级的应用中待同步的数据存储于一缓存器中，直至所述电子设备当前运行状况满足所述预设运行状况时，允许存储于所述缓存器中待同步的数据进行同步。
  11. 根据权利要求10所述的数据同步管控方法，其中，所述根据预设规则将所述预设白名单中所有应用设置不同的优先级的步骤，具体包括：
    根据所述预设白名单中应用的类型设置不同的层级，并将所述预设白名单中的应用分别分配到对应的层级中；
    根据所述预设白名单中应用的类型对所述不同层级设置不同的优先级。
  12. 一种数据同步管控装置，应用于电子设备中，其包括：
    第一获取模块，用于获取所述电子设备中的待同步应用以及所述待同步应用的同步参数，所述待同步应用为等待进行数据同步的应用；
    筛选模块，用于根据所述同步参数从所述待同步应用中筛选出目标应用；
    匹配模块，用于将所述目标应用于预设白名单中的应用进行匹配；
    管控模块，用于当存在匹配成功的目标应用时，允许所述匹配成功的目标应用进行数据同步；
    所述管控模块，还用于当存在匹配失败的目标应用时，禁止所述匹配失败的目标应用进行数据同步。
  13. 根据权利要求12所述的数据同步管控装置，其中，所述数据同步管控装置还包括第二获取模块和确定模块；
    所述第二获取模块，用于从服务器获取原始白名单；
    所述确定模块，用于将所述原始白名单确定为预设白名单。
  14. 根据权利要求12所述的数据同步管控装置，其中，所述数据同步管控装置还包括第三获取模块和生成模块；
    所述第三获取模块，用于获取所述电子设备中所有数据周期同步的应用；
    所述生成模块，用于根据所述数据周期同步的应用生成预设白名单。
  15. 根据权利要求14所述的数据同步管控装置，其中，所述生成模块包括：
    第四获取模块，用于获取每一所述数据周期同步的应用的同步周期；
    第一写入模块，用于将所述同步周期大于预设周期的应用写入预设白名单中，以生成所述预设白名单。
  16. 根据权利要求14所述的数据同步管控装置，其中，所述生成模块还包括：
    第五获取模块，用于获取每一数据周期同步的应用的历史运行时长；
    第二写入模块，用于将所述历史运行时长大于预设时长的应用写入预设白名单中，以生成所述预设白名单。
  17. 根据权利要求14所述的数据同步管控装置，其中，所述数据同步管控装置还包括第一设置模块；
    所述第一设置模块，用于根据预设规则将所述预设白名单中所有的应用设置不同的优先级；
    所述管控模块，还用于当所述电子设备的运行状况未满足预设运行状况时，允许所述优先级高于预设优先级的应用进行数据同步，禁止所述优先级低于预设优先级的应用进行数据同步，并将所述优先级低于预设优先级的应用中待同步的数据存储于一缓存器中，直 至所述电子设备当前运行状况满足所述预设运行状况时，允许存储于所述缓存器中待同步的数据进行同步。
  18. 根据权利要求17所述的数据同步管控装置，其中，所述第一设置模块包括：
    第二设置模块，用于根据所述预设白名单中应用的类型设置不同的层级，并将所述预设白名单中的应用分别分配到对应的层级中；
    第三设置模块，用于根据所述预设白名单中应用的类型对所述不同层级设置不同的优先级。19、一种电子设备，其包括处理器和存储器，所述处理器和所述存储器电性连接，所述存储器用于存储指令和数据，所述处理器用于执行以下步骤：
    获取所述电子设备中的待同步应用以及所述待同步应用的同步参数；
    根据所述同步参数从所述待同步应用中筛选出目标应用，所述目标应用为周期同步的应用；
    将所述目标应用与预设白名单中的应用进行匹配；
    当存在匹配成功的目标应用时，允许所述匹配成功的目标应用进行数据同步；
    当存在匹配失败的目标应用时，禁止所述匹配失败的目标应用进行数据同步。。
  19. 根据权利要求19所述的电子设备，其中，所述将所述目标应用与预设白名单进行匹配的步骤之前，所述数据同步管控方法还包括：
    获取所述电子设备中所有周期同步的应用；
    根据所述周期同步的应用生成预设白名单。
PCT/CN2018/094253 2017-07-31 2018-07-03 数据同步管控方法、装置及电子设备 WO2019024643A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710646418.3 2017-07-31
CN201710646418.3A CN107241447B (zh) 2017-07-31 2017-07-31 数据同步管控方法、装置、存储介质及电子设备

Publications (1)

Publication Number Publication Date
WO2019024643A1 true WO2019024643A1 (zh) 2019-02-07

Family

ID=59989807

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/094253 WO2019024643A1 (zh) 2017-07-31 2018-07-03 数据同步管控方法、装置及电子设备

Country Status (2)

Country Link
CN (1) CN107241447B (zh)
WO (1) WO2019024643A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107241447B (zh) * 2017-07-31 2019-09-13 Oppo广东移动通信有限公司 数据同步管控方法、装置、存储介质及电子设备
CN110018806A (zh) * 2018-11-22 2019-07-16 阿里巴巴集团控股有限公司 一种语音处理方法和装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105324749A (zh) * 2013-06-14 2016-02-10 三星电子株式会社 终端及用于其的应用同步方法
JP2016062311A (ja) * 2014-09-18 2016-04-25 株式会社日立製作所 更新装置及び情報処理方法
CN106201596A (zh) * 2016-06-29 2016-12-07 宇龙计算机通信科技(深圳)有限公司 一种禁止第三方应用自动更新的方法、装置以及终端
CN106993096A (zh) * 2017-03-31 2017-07-28 宇龙计算机通信科技(深圳)有限公司 一种终端应用管理方法及系统
CN107241447A (zh) * 2017-07-31 2017-10-10 广东欧珀移动通信有限公司 数据同步管控方法、装置、存储介质及电子设备

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009163423A (ja) * 2007-12-28 2009-07-23 Canon Inc プログラム連携システム及びそのシミュレーション制御方法
KR101828295B1 (ko) * 2011-08-30 2018-02-13 삼성전자 주식회사 단말 및 그 단말에서 애플리케이션 관리 방법
US9477678B2 (en) * 2013-01-23 2016-10-25 Htc Corporation Data synchronization management methods and systems
CN104917844B (zh) * 2015-06-17 2016-10-26 深圳市腾讯计算机系统有限公司 一种数据同步方法、装置及系统
CN106022108B (zh) * 2016-05-17 2019-07-02 Oppo广东移动通信有限公司 一种同步管理方法及终端设备
CN106209974B (zh) * 2016-06-21 2019-03-12 浪潮电子信息产业股份有限公司 一种数据同步方法、设备及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105324749A (zh) * 2013-06-14 2016-02-10 三星电子株式会社 终端及用于其的应用同步方法
JP2016062311A (ja) * 2014-09-18 2016-04-25 株式会社日立製作所 更新装置及び情報処理方法
CN106201596A (zh) * 2016-06-29 2016-12-07 宇龙计算机通信科技(深圳)有限公司 一种禁止第三方应用自动更新的方法、装置以及终端
CN106993096A (zh) * 2017-03-31 2017-07-28 宇龙计算机通信科技(深圳)有限公司 一种终端应用管理方法及系统
CN107241447A (zh) * 2017-07-31 2017-10-10 广东欧珀移动通信有限公司 数据同步管控方法、装置、存储介质及电子设备

Also Published As

Publication number Publication date
CN107241447A (zh) 2017-10-10
CN107241447B (zh) 2019-09-13

Similar Documents

Publication Publication Date Title
US10958850B2 (en) Electronic device and method for capturing image by using display
KR102148948B1 (ko) 전자 장치의 멀티 태스킹 방법 및 그 전자 장치
US10631361B2 (en) Method and apparatus for providing user with information received by electronic device
US20210389973A1 (en) Electronic device and method for operating the same
US10491535B2 (en) Adaptive data synchronization
US20190369700A1 (en) Electronic Device Control Method and Apparatus, and Electronic Device
US10402222B2 (en) Task migration method and apparatus
US10712798B2 (en) Sensor processing method of mobile terminal, storage medium, and electronic device
WO2017160003A1 (ko) 태스크 스케줄링 방법 및 이를 구현한 전자 장치
WO2019024641A1 (zh) 数据同步方法、装置、存储介质以及电子设备
WO2019024646A1 (zh) 应用管控方法、装置及电子设备
CN109992364B (zh) 应用冻结方法、装置、计算机设备和计算机可读存储介质
US20100211680A1 (en) Apparatus and method to allocate limited resources
KR20160145116A (ko) 토큰 버킷을 사용하는 통신들의 배터리 효율적 동기화
EP3699760A1 (en) Information processing method and device, computer device and computer readable storage medium
WO2019024643A1 (zh) 数据同步管控方法、装置及电子设备
CN114327087A (zh) 输入事件处理方法、装置、电子设备和存储介质
CN116578422A (zh) 资源分配方法和电子设备
CN111144845B (zh) 一种移动终端会议提醒方法和装置
CN112997150B (zh) 应用程序的管理方法、装置、存储介质及电子设备
CN112860352A (zh) 一种应用程序的加载方法、装置、存储介质及终端
CN109426572B (zh) 任务处理方法、装置及电子设备
CN110007968B (zh) 信息处理方法、装置、计算机设备和计算机可读存储介质
CN110688344A (zh) 一种文件扫描方法、装置、计算机可读存储介质及终端
CN114416234B (zh) 一种页面切换方法、装置、计算机设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18840802

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18840802

Country of ref document: EP

Kind code of ref document: A1