WO2019024643A1 - Procédé de gestion de synchronisation de données, dispositif, et équipement électronique - Google Patents

Procédé de gestion de synchronisation de données, dispositif, et équipement électronique 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)
Chinese (zh)
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/fr

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)
  • Stored Programmes (AREA)
  • Power Sources (AREA)
  • Telephone Function (AREA)

Abstract

La présente invention concerne un procédé de gestion de synchronisation de données, un dispositif, et un équipement électronique. Le procédé de gestion de synchronisation de données consiste à : obtenir une application devant être synchronisée dans le dispositif électronique et des paramètres de synchronisation de l'application devant être synchronisée, l'application devant être synchronisée étant une application en attente de synchronisation de données; filtrer une application cible à partir de l'application devant être synchronisée d'après le paramètre de synchronisation; mettre l'application cible en correspondance avec des applications dans une liste blanche prédéfinie; lorsqu'une concordance existe avec une application cible, autoriser l'application cible qui présente une concordance à exécuter la synchronisation de données; et lorsqu'il n'existe pas de concordance avec une application cible, empêcher l'application cible qui ne présente pas de concordance à exécuter la synchronisation de données.
PCT/CN2018/094253 2017-07-31 2018-07-03 Procédé de gestion de synchronisation de données, dispositif, et équipement électronique WO2019024643A1 (fr)

Applications Claiming Priority (2)

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

Publications (1)

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

Family

ID=59989807

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/094253 WO2019024643A1 (fr) 2017-07-31 2018-07-03 Procédé de gestion de synchronisation de données, dispositif, et équipement électronique

Country Status (2)

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

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
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 (fr) Procédé de planification de tâche et dispositif électronique pour mettre en œuvre ce dernier
WO2019024641A1 (fr) Procédé et appareil de synchronisation de données, support de stockage, et appareil électronique
WO2019024646A1 (fr) Procédé, appareil et dispositif électronique de gestion et de commande d'application
CN109992364B (zh) 应用冻结方法、装置、计算机设备和计算机可读存储介质
US20100211680A1 (en) Apparatus and method to allocate limited resources
KR20160145116A (ko) 토큰 버킷을 사용하는 통신들의 배터리 효율적 동기화
EP3699760A1 (fr) Procédé et dispositif de traitement d'informations, dispositif informatique et support d'informations lisible par ordinateur
WO2019024643A1 (fr) Procédé de gestion de synchronisation de données, dispositif, et équipement électronique
CN110853644A (zh) 语音唤醒方法、装置、设备及存储介质
CN116578422A (zh) 资源分配方法和电子设备
CN111144845B (zh) 一种移动终端会议提醒方法和装置
CN112997150B (zh) 应用程序的管理方法、装置、存储介质及电子设备
CN109426572B (zh) 任务处理方法、装置及电子设备
CN110007968B (zh) 信息处理方法、装置、计算机设备和计算机可读存储介质
CN110688344A (zh) 一种文件扫描方法、装置、计算机可读存储介质及终端
CN114416234B (zh) 一种页面切换方法、装置、计算机设备及存储介质
CN112783860B (zh) 构造镜像数据库的方法、装置、存储介质及计算机设备
CN107797645A (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