A data synchronization management method, system and electronic device

By introducing device management interfaces and data synchronization management interfaces into electronic devices, the problems of complex data synchronization operations and privacy and security between electronic devices are solved, achieving simple and efficient data synchronization management and privacy protection.

CN116166740BActive Publication Date: 2026-02-13HUAWEI TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202111412184.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-11-25
Publication Date
2026-02-13
Estimated Expiration
2041-11-25

AI Technical Summary

Technical Problem

In existing technologies, data synchronization between electronic devices is complex, affects user experience, and poses data privacy and security issues.

Method used

By implementing device management and data synchronization management interfaces in electronic devices, users can manage data synchronization through simple and natural interactive operations, supporting application-level data synchronization control and privacy protection.

Benefits of technology

It simplifies data synchronization, improves user experience, and enhances data privacy and security.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116166740B_ABST
    Figure CN116166740B_ABST
Patent Text Reader

Abstract

The application discloses a data synchronization management method, which is applied to a first electronic device. The method comprises the following steps: receiving a first operation of a user; displaying a device management interface in response to the first operation, wherein the device management interface comprises identification information of at least one second electronic device; receiving a second operation of the user on the identification information of the second electronic device; displaying a first data synchronization management interface corresponding to the second electronic device in response to the second operation, wherein the first data synchronization management interface comprises identification information of at least one application in the second electronic device, and a first management control corresponding to the identification information of the application; receiving a third operation of the user on the first management control; and if the application is a first type of application, performing a data synchronization management process in response to the third operation, wherein the data synchronization management process corresponds to all data of the application. The data synchronization management operation can be simplified, and the user experience is improved. The application further discloses a data synchronization management system and an electronic device.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, in particular to a data synchronization management method and system and electronic device. BACKGROUND

[0002] In the past, the data of electronic devices such as mobile phones, tablets, televisions and the like are respectively stored in the local electronic devices, and the data synchronization between electronic devices (the data synchronization can also be referred to as data sharing, data flow, etc.) is not convenient. The emergence of cloud services (the cloud services can also be referred to as cloud synchronization services) has accelerated the development of electronic device interconnection, and under the condition that multiple electronic devices log in to the same cloud account, the multiple electronic devices can realize the function of data synchronization between electronic devices through the cloud services. For example, a mobile phone logs in to a cloud account and enables the cloud services, and after the user selects an application (Application, APP) for data synchronization, the mobile phone uploads all the data of the application to the cloud corresponding to the cloud services (the cloud can also be referred to as a cloud server). Then, if a tablet logs in to the same cloud account and enables the cloud services, after the user selects the same application for data synchronization, the tablet can directly synchronize all the data of the application synchronized to the cloud by the mobile phone from the cloud to the local tablet, thereby realizing the data synchronization between the mobile phone and the tablet.

[0003] As described above, the current mobile phone and tablet can only perform data synchronization management on their respective local data, and in the process of realizing the data synchronization between the mobile phone and the tablet, the user needs to perform multiple data synchronization operations on the mobile phone and the tablet respectively, which exists the problems of complex operation and affecting user experience. In addition, the current synchronization of all the data of the application between the mobile phone and the tablet may also exist the problem of affecting the data privacy security. SUMMARY

[0004] The present application provides a data synchronization management method and system and electronic device, which can solve the problems of complex operation, affecting user experience and affecting data privacy security in the process of the user performing data synchronization operation between electronic devices, that is, can realize simplifying the operation of the user performing data synchronization between electronic devices, can effectively improve the user experience, and can improve the data privacy security.

[0005] To solve the above technical problems, in a first aspect, embodiments of the present application provide a data synchronization management method applied to a first electronic device, the method comprising: receiving a first operation of a user; in response to the first operation, displaying a device management interface, the device management interface comprising identification information of at least one second electronic device, the second electronic device being an electronic device using a same preset account as the first electronic device; receiving a second operation of the user on the identification information of the second electronic device; in response to the second operation, displaying a first data synchronization management interface corresponding to the second electronic device, the first data synchronization management interface comprising identification information of at least one application in the second electronic device and a first management control corresponding to the identification information of the application; receiving a third operation of the user on the first management control; if the application is a first type of application, in response to the third operation, performing a data synchronization management process corresponding to all data of the application.

[0006] The first electronic device can display the identification information of the second electronic device and the identification information of the application through the device management interface and the first data synchronization management interface, respectively. In this way, the user only needs to operate the first electronic device, and through the device management interface and the first data synchronization management interface, the user can conveniently and simply perform data synchronization management between the first electronic device and the second electronic device based on a simple natural interaction operation mode, thereby simplifying the data synchronization management operation and improving the user experience.

[0007] In a possible implementation of the first aspect, if the application is a second type of application, the method comprises: in response to the third operation, displaying a second data synchronization management interface corresponding to the application, the second data synchronization management interface comprising identification information of at least one type of application sub-data corresponding to the application and a second management control corresponding to the identification information of the application sub-data; receiving a fourth operation of the user on the second management control; and in response to the fourth operation, performing a data synchronization management process corresponding to the application sub-data corresponding to the second management control.

[0008] The first electronic device can display the identification information of the application sub-data of the application in the second electronic device through the second data synchronization management interface. In this way, the user only needs to operate the first electronic device, and through the second data synchronization management interface, the user can conveniently and simply perform data synchronization management between the first electronic device and the second electronic device based on a simple natural interaction operation mode, thereby simplifying the data synchronization management operation and improving the user experience.

[0009] In a possible implementation of the first aspect, the second data synchronization management interface further includes a third management control corresponding to an application, and the method further includes: receiving a fifth operation of the third management control by the user; and in response to the fifth operation, performing a data synchronization management process corresponding to all application sub-data included in the second data synchronization management interface.

[0010] By setting the third management control in the second data synchronization management interface, the user can conveniently perform data synchronization management on all application sub-data included in the second data synchronization management interface, and the user experience can be effectively improved.

[0011] In a possible implementation of the first aspect, the data synchronization management process includes starting data synchronization between the first electronic device and the second electronic device, or stopping data synchronization between the first electronic device and the second electronic device. In this way, the user experience of data synchronization management can be improved.

[0012] In a possible implementation of the first aspect, the device management interface further includes a data synchronization region and a data independent region, the data synchronization region is configured to display identification information of an electronic device that has logged in the preset account and has performed data synchronization with the first electronic device, and the data independent region is configured to display identification information of an electronic device that has not performed data synchronization with the first electronic device; and the method further includes: displaying the identification information of the second electronic device in the data synchronization region or the data independent region according to at least one of the following information: information about whether the second electronic device is currently logged in the preset account, information about the number of times that the second electronic device has logged in the preset account, information about whether the second electronic device is currently performing data synchronization with the first electronic device, and information about whether the identification information of the second electronic device has been deleted from the device management interface.

[0013] The user can determine information about whether the second electronic device is logged in the preset account, information about whether the second electronic device is performing data synchronization with the first electronic device, and the like according to the region in which the identification information of the second electronic device is located, thereby facilitating the user to perform corresponding data synchronization management, and effectively improving the user experience.

[0014] In a possible implementation of the first aspect, the method further includes: receiving a sixth operation of the identification information of the second electronic device by the user; if the sixth operation is an operation of moving the identification information of the second electronic device from the data synchronization region to the data independent region, in response to the sixth operation, stopping data synchronization between the first electronic device and the second electronic device; and if the sixth operation is an operation of moving the identification information of the second electronic device from the data independent region to the data synchronization region, in response to the sixth operation, starting data synchronization of preset data between the first electronic device and the second electronic device, or displaying a first data synchronization management interface corresponding to the second electronic device.

[0015] In this way, the user only needs to drag the identification information of the second electronic device on the device management interface displayed by the first electronic device through simple and natural interaction, so as to conveniently and concisely perform data synchronization management between the first electronic device and the second electronic device, simplify the data synchronization management operation, and improve the user experience.

[0016] In a possible implementation of the first aspect, if the sixth operation is an operation of moving the identification information of the second electronic device from the data synchronization area to the data independent area, the method further includes: in response to the sixth operation, displaying stop data synchronization prompt information; and stopping the data synchronization between the first electronic device and the second electronic device, including: receiving a seventh operation of the user corresponding to the stop data synchronization prompt information; and in response to the seventh operation, stopping the data synchronization between the first electronic device and the second electronic device.

[0017] By displaying the stop data synchronization prompt information, the user can be prompted to confirm whether to stop the data synchronization between the first electronic device and the second electronic device, so as to avoid user misoperation and effectively improve the user experience.

[0018] In a possible implementation of the first aspect, the method further includes: receiving an eighth operation of the user corresponding to the stop data synchronization prompt information; and in response to the eighth operation, displaying the identification information of the second electronic device in the data synchronization area.

[0019] In this way, if the user chooses not to stop the data synchronization between the first electronic device and the second electronic device, the identification information of the second electronic device can be directly displayed in the data synchronization area, so as to improve the user experience of data synchronization management.

[0020] In a possible implementation of the first aspect, the method further includes: receiving a ninth operation of the user on the identification information of the second electronic device; in response to the ninth operation, deleting the identification information of the second electronic device from the first data synchronization management interface; or in response to the ninth operation, displaying a deletion control; receiving a tenth operation of the user corresponding to the deletion control; and in response to the tenth operation, deleting the identification information of the second electronic device from the first data synchronization management interface.

[0021] In this way, the user can delete the identification information of the second electronic device according to needs during the data synchronization management, so as to effectively improve the user experience.

[0022] In a possible implementation of the first aspect, the method further includes: in response to the ninth operation or the tenth operation, stopping the data synchronization between the first electronic device and the second electronic device.

[0023] In this way, the first electronic device can also perform corresponding data synchronization management according to the deletion operation of the user, and the user experience can be effectively improved.

[0024] In a possible implementation of the first aspect, the method further includes: receiving a data synchronization request sent by the second electronic device; in response to the data synchronization request, displaying an opening data synchronization prompt information; receiving an eleventh operation of the user corresponding to the opening data synchronization prompt information; and in response to the eleventh operation, opening data synchronization of data corresponding to the data synchronization request between the first electronic device and the second electronic device.

[0025] The first electronic device can also display corresponding opening data synchronization prompt information according to the data synchronization request sent by the second electronic device, so as to facilitate the user to perform data synchronization management processing, and the user experience can be effectively improved.

[0026] In a possible implementation of the first aspect, the method further includes: if it is determined that a preset data synchronization stop condition is met, stopping data synchronization of data corresponding to the data synchronization request between the first electronic device and the second electronic device.

[0027] The first electronic device can also perform data synchronization management according to the preset data synchronization stop condition, and the data synchronization management efficiency and the user experience can be effectively improved.

[0028] In a possible implementation of the first aspect, the data synchronization stop condition includes any one of the following: the time of opening data synchronization reaches a preset opening time; a preset operation of the user on data corresponding to the data synchronization request is received.

[0029] In a possible implementation of the first aspect, the method further includes: displaying data synchronization has stopped prompt information; and / or sending data synchronization has stopped prompt information to the second electronic device, so that the second electronic device displays the data synchronization has stopped prompt information.

[0030] By displaying the data synchronization has stopped prompt information, the user can be facilitated to understand the current data synchronization situation, and the user experience can be effectively improved.

[0031] In a possible implementation of the first aspect, the method further includes: receiving a twelfth operation of the user corresponding to the opening data synchronization prompt information; in response to the twelfth operation, sending notification information of refusing data synchronization to the second electronic device; or in response to the twelfth operation, displaying data synchronization refusal prompt information; receiving a thirteenth operation of the user corresponding to the data synchronization refusal prompt information; and in response to the thirteenth operation, sending notification information of refusing data synchronization to the second electronic device.

[0032] The first electronic device can perform corresponding data synchronization management processing according to the data synchronization management operation of the user by opening the data synchronization prompt information, can conveniently perform data synchronization management, and can effectively improve the user experience.

[0033] In a possible implementation of the first aspect, the method further includes determining the display state of the management control according to information about whether data synchronization between the first electronic device and the second electronic device is enabled or disabled.

[0034] In this way, the user can conveniently understand the current data synchronization situation through the display state of the management control, and the user experience can be effectively improved.

[0035] In a possible implementation of the first aspect, the method further includes determining the data synchronization management interface according to at least one of the following information: application data of an application installed in the first electronic device; application data of an application installed in the second electronic device; device information of the second electronic device, wherein the data synchronization management interface includes a first data synchronization management interface and a second data synchronization management interface.

[0036] In this way, the data used by the user for data synchronization management in the second electronic device can be conveniently and accurately determined, and the data security of data synchronization management can be improved.

[0037] In a possible implementation of the first aspect, determining the data synchronization management interface according to the application data and the device information includes: classifying the application data, determining a data risk level and a data use scenario of each type of application data, and determining a device security level, a device sharing degree, and a device use scenario of the second electronic device according to the device information; determining first data in the application data according to at least one of the data risk level, the data use scenario, the device security level, the device sharing degree, and the device use scenario, wherein the first data is data in the application data used by the user for data synchronization management; and displaying the data synchronization management interface according to the first data.

[0038] The first data determined according to at least one of the data risk level, the data use scenario, the device security level, the device sharing degree, and the device use scenario is used to display the data synchronization management interface. In this way, the data security of data synchronization management can be effectively improved.

[0039] In a possible implementation of the first aspect, the method further includes: determining second data and third data in the application data according to at least one of the data risk level, the data use scenario, the device security level, the device sharing degree, and the device use scenario, the second data being data in the application data for which data synchronization is enabled by default, and the third data being data in the application data for which data synchronization is not enabled by default; enabling data synchronization of the second data between the first electronic device and the second electronic device; not enabling data synchronization of the third data between the first electronic device and the second electronic device; and not displaying, in the data synchronization management interface, identification information of the second data and the third data or identification information of application sub-data corresponding to the second data and the third data.

[0040] In this way, data synchronization management of the second data and the third data can be conveniently implemented, data synchronization of the second data is enabled by default, which can improve data synchronization management efficiency, data synchronization of the third data is not displayed and not enabled by default, which can also improve data synchronization management efficiency, and data security of data synchronization management can be improved.

[0041] In a possible implementation of the first aspect, enabling data synchronization between the first electronic device and the second electronic device includes: sending a data synchronization enabling instruction to the cloud end, so that the cloud end enables, according to the data synchronization enabling instruction, data synchronization access permission of the second electronic device for data synchronization with the first electronic device through the cloud end; and stopping data synchronization between the first electronic device and the second electronic device includes: sending a data synchronization stopping instruction to the cloud end, so that the cloud end closes, according to the data synchronization stopping instruction, data synchronization access permission of the second electronic device for data synchronization with the first electronic device through the cloud end.

[0042] The first electronic device manages, through the cloud end, data synchronization access permission of the second electronic device for data synchronization with the first electronic device through the cloud end, which can facilitate and accurately implement data synchronization management, and can effectively improve data synchronization management efficiency.

[0043] Secondly, embodiments of this application provide a data synchronization management system, which includes a first electronic device and at least one second electronic device. The first electronic device receives a first operation from a user; in response to the first operation, displays a device management interface including identification information of at least one second electronic device, wherein the second electronic device uses the same preset account as the first electronic device; receives a second operation from the user on the identification information of the second electronic device; in response to the second operation, displays a first data synchronization management interface corresponding to the second electronic device, the first data synchronization management interface including identification information of at least one application in the second electronic device and a first management control corresponding to the application's identification information; receives a third operation from the user on the first management control; if the application is a first type of application, in response to the third operation, performs data synchronization management processing, the data synchronization management processing corresponding to all data of the application; the second electronic device performs data processing corresponding to the data synchronization management processing.

[0044] In one possible implementation of the second aspect above, if the application is a second type of application, the first electronic device is further configured to respond to a third operation by displaying a second data synchronization management interface corresponding to the application, the second data synchronization management interface including identification information of at least one type of application sub-data corresponding to the application, and a second management control corresponding to the identification information of the application sub-data; and receiving a fourth operation from the user on the second management control; and in response to the fourth operation, performing data synchronization management processing, the data synchronization management processing corresponding to the application sub-data corresponding to the second management control; the second electronic device is configured to perform data processing corresponding to the data synchronization management processing.

[0045] In one possible implementation of the second aspect described above, the data synchronization management system further includes a cloud, which is used to store data synchronized from the first electronic device and the second electronic device, as well as to perform data synchronization access permission processing corresponding to the data synchronization management processing.

[0046] The data synchronization management system provided in this application is used to execute the data synchronization management method provided by the first aspect and / or any possible implementation of the first aspect, and thus can also achieve the beneficial effects (or advantages) of the data synchronization management method provided by the first aspect.

[0047] Thirdly, embodiments of this application provide an electronic device, including: a memory for storing a computer program, the computer program including program instructions; and a controller for executing the program instructions to cause the electronic device to perform the data synchronization management method provided by the first aspect and / or any possible implementation of the first aspect.

[0048] In a fourth aspect, embodiments of the present application provide a computer readable storage medium storing a computer program, the computer program comprising program instructions, which, when executed by an electronic device, cause the electronic device to perform the data synchronization management method according to the first aspect and / or any possible implementation of the first aspect.

[0049] It can be understood that the beneficial effects of the second aspect to the fourth aspect described above can also be referred to the related description in the first aspect, which will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0050] In order to more clearly illustrate the technical solutions of the present application, the drawings used in the embodiments will be briefly introduced as follows.

[0051] Figure 1 Fig. 1 shows a structural schematic diagram of a data synchronization management system according to some embodiments of the present application;

[0052] Figures 2A-2H Fig. 2 shows some display interface schematic diagrams of a mobile phone 10 according to some embodiments of the present application;

[0053] Figure 3 Fig. 3 shows a structural schematic diagram of a data synchronization management system according to some embodiments of the present application;

[0054] Figure 4 Fig. 4 shows a structural schematic diagram of a mobile phone 100 according to some embodiments of the present application;

[0055] Figures 5A-5R Fig. 5 shows some display interface schematic diagrams of the mobile phone 100 according to some embodiments of the present application;

[0056] Figures 6A-6G Fig. 6 shows some display interface schematic diagrams of the mobile phone 100 and a television 220 according to some embodiments of the present application;

[0057] Figure 7 Fig. 7 shows a flowchart of a data synchronization management method according to some embodiments of the present application;

[0058] Figure 8 Fig. 8 shows a flowchart of another data synchronization management method according to some embodiments of the present application;

[0059] Figure 9 Fig. 9 shows a flowchart of yet another data synchronization management method according to some embodiments of the present application;

[0060] Figure 10 Fig. 10 shows a structural schematic diagram of an electronic device according to some embodiments of the present application;

[0061] Figure 11 According to some implementations of the present application, a structural diagram of a system on chip (SoC) is shown. DETAILED DESCRIPTION

[0062] The technical solutions of the present application will be described in further detail below with reference to the accompanying drawings.

[0063] As mentioned above, under the condition that multiple electronic devices are logged in the same cloud account, the multiple electronic devices can realize the capability of data synchronization between electronic devices through cloud services.

[0064] Referring to Figure 1 , Figure 1 A structural diagram of a data synchronization management system is shown, which includes a mobile phone 10, a tablet computer 20 and a cloud 30.

[0065] The process of logging in the cloud account by the mobile phone 10 and realizing data synchronization between the mobile phone 10, the tablet computer 20 and the cloud 30 will be described below taking the mobile phone 10 as an example.

[0066] Referring to Figure 2A , the mobile phone 10 displays a main desktop, which includes a “settings” control and other controls such as “clock”, “calendar” and the like. If the mobile phone 10 receives a click operation of the “settings” control by a user, the mobile phone displays a display interface as shown in Figure 2B , which includes a “log in ** account” control, the “** account” being the cloud account. If the mobile phone 10 receives a click operation of the “log in ** account” control by a user, the mobile phone 10 displays a display interface as shown in Figure 2C , which includes a cloud account “1234567” that has been logged in by the user in the past and an “immediately log in / register” control. If the mobile phone 10 receives a click operation of the “immediately log in / register” control by a user, the mobile phone 10 logs in the cloud account “1234567” and displays a display interface as shown in Figure 2D , which includes a “cloud space” control. If the mobile phone 10 receives a click operation of the “cloud space” control by a user, the mobile phone 10 starts the cloud service and displays a display interface as shown in Figure 2E .

[0067] Referring to Figure 2EThe display interface includes application icons of a plurality of applications installed in the mobile phone 10, such as "Gallery", "Contacts", "Calendar", "Memo", "Browser", "WLAN", and the like, which can use the cloud service, and management controls M corresponding to the application icons. The user can manage the applications using the cloud service through the management controls M in the display interface, for example, start data synchronization of a certain application, or stop data synchronization of a certain application. Moreover, after the mobile phone 10 receives the operation of the user starting data synchronization of a certain application, the mobile phone 10 uploads all data corresponding to the application to the cloud 30 corresponding to the cloud service, thereby realizing synchronization of data from the mobile phone 10 to the cloud 30. The all data can be, for example, application data such as usage data, user behavior data, and the like generated in the process of the user using the application.

[0068] For example, as shown in Figure 2E , it can be seen that the mobile phone 10 has currently started data synchronization of the "Gallery" application by default, and has started data synchronization of the "Calendar" application and the "Browser" application by default, that is, the mobile phone 10 can upload all data of the "Gallery" application, the "Calendar" application, and the "Browser" application to the cloud 30. In addition, it can also be seen that the mobile phone 10 has not currently started data synchronization of the "Contacts" application, the "Memo" application, and the "WLAN" application, that is, the mobile phone 10 cannot currently upload data of the "Contacts" application, the "Memo" application, and the "WLAN" application to the cloud 30. It should be noted that Figure 2E The display interface shown in

[0069] In addition, the user can further view the data synchronization situation of the application through the display interface shown in Figure 2E . For example, please continue to refer to Figure 2E , if the mobile phone 10 receives a click operation of the user on the management control M (that is, the "started" control) corresponding to the "Gallery" application, the mobile phone 10 displays the display interface shown in Figure 2F , through which it can be seen that the mobile phone 10 is currently uploading all data such as photos and videos in the "Gallery" application to the cloud 30.

[0070] Further, after the mobile phone 10 has logged in the aforementioned cloud account "1234567" and started the cloud service, if the mobile phone 10 receives a click operation of the user on the "Settings" control as shown in the aforementioned Figure 2A , the mobile phone 10 displays the display interface shown in Figure 2G , through which it can be seen that the mobile phone 10 has currently logged in the cloud account "1234567". If the mobile phone 10 receives a click operation of the user on the "My Device" control, the mobile phone 10 displays the display interface shown in Figure 2HThe displayed display interface (equivalent to the device management interface) can show that the electronic devices currently logged in the same cloud account as the mobile phone 10 include the mobile phone "**P40 Pro", the PC "Match", the "Matebook PC" and other electronic devices.

[0071] Taking the PC "Match" as the aforementioned tablet computer 20 as an example, if the user needs to synchronize the data in the mobile phone 10 through the tablet computer 20, the user needs to operate the tablet computer 20 to log in the same cloud account "1234567" through the same or similar display interface and operation as the aforementioned, and enable the data synchronization of the corresponding application. In this way, the tablet computer 20 can directly synchronize all the data of the application in the mobile phone 10 from the cloud 30 to the cloud 30, and synchronize the data from the cloud 30 to the local of the tablet computer 20, thereby realizing the data synchronization between the mobile phone 10 and the tablet computer 20. Figures 2A-2E

[0072] As described above, the current mobile phone 10 and the tablet computer 20 can only manage the local data synchronization of each other, and therefore, in the process of realizing the data synchronization between the mobile phone 10 and the tablet computer 20, the user needs to perform multiple data synchronization operations on the mobile phone 10 and the tablet computer 20 respectively, and the user needs to check and manage the local data synchronization situation through the mobile phone 10 and the tablet computer 20 respectively, which causes the user operation to be complex and affects the user experience.

[0073] In addition, in this way, for an application, the user can only choose between not enabling the data synchronization or enabling the data synchronization, that is, the user can only choose between not synchronizing the application data and completely synchronizing all the data of the application. If the user chooses to enable the data synchronization of the application, the mobile phone 10 will completely synchronize all the data of the application to the cloud 30 without distinction; if the user chooses not to enable the data synchronization of the application, the mobile phone 10 will not synchronize any data of the application to the cloud 30, that is, the current method cannot realize the synchronization of part of the data of the application. However, for some sensitive data of the application and other data, the user may want to synchronize the data to other electronic devices in some scenarios, and the user may not want to synchronize the data to other electronic devices in other scenarios. Therefore, the current data synchronization method cannot realize the synchronization of part of the data of the application, which may cause the data privacy and security problem of the data synchronization, that is, the user may accidentally leak the private data when using multiple devices.

[0074] The implementation manner of the present application provides a data synchronization management method applied to a mobile phone to realize the data synchronization between the mobile phone and other electronic devices, and a data synchronization management system for realizing the data synchronization management method. Please refer to Figure 3 ​The data synchronization management system includes a mobile phone 100, a synchronization device 200, and a cloud 300. The synchronization device 200 can be an electronic device such as a tablet computer 210, a television 220, a large-screen device 230, and a notebook computer 240. In this implementation, the user can realize data synchronization management between the mobile phone 100 and the synchronization device 200 through the mobile phone 100.

[0075] In an implementation of the present application, the data synchronization management method includes the following steps. After the mobile phone 100 and the synchronization device 200 log in to the same cloud account, if the mobile phone 100 receives a click operation of a user on a control displayed on the mobile phone 100, such as the aforementioned "my device", the mobile phone 100 can display device icons of the synchronization device 200 discovered by the mobile phone 100 and using the same cloud account as the mobile phone 100. If the mobile phone 100 receives a click operation of a user on a device icon of the synchronization device 200, the mobile phone 100 can display a data synchronization management interface corresponding to the synchronization device 200. The data synchronization management interface includes application icons of at least one application in the synchronization device 200 and management controls (also referred to as synchronization control options) corresponding to the application icons. The user can manage whether the application performs data synchronization through the management controls. For example, if the mobile phone 100 receives a click operation of a user on a management control corresponding to an application, the mobile phone 100 can directly start or stop data synchronization of all data of the application between the mobile phone 100 and the synchronization device 200 according to the click operation, or the mobile phone 100 can display a data management sub-interface corresponding to the application. The data management sub-interface includes data icons of at least one type of application sub-data corresponding to the application and management controls corresponding to the data icons. Further, if the mobile phone 100 receives a click operation of a user on a management control corresponding to a data icon, the mobile phone 100 can directly start or stop data synchronization of the application sub-data corresponding to the data icon between the mobile phone 100 and the synchronization device 200 according to the click operation.

[0076] In this implementation, the mobile phone 100 can display device icons, application icons, data icons of application sub-data, and other information of the synchronization device 200 through the device management interface, the data synchronization management interface, and the data synchronization management sub-interface. In this way, the user only needs to operate the mobile phone 100 to perform data synchronization management between the mobile phone 100 and the synchronization device 200 through the device management interface, the data synchronization management interface, and the data synchronization management sub-interface based on natural interaction modes such as a simple click operation, which simplifies the data synchronization management operation and improves the user experience.

[0077] And, in the present embodiment, the mobile phone 100 displays application sub-data and management controls corresponding to the application sub-data through the data synchronization management sub-interface, so that the user can perform data synchronization management on the application sub-data as needed, that is, can perform single data synchronization management on part of the data of the application as needed, thereby realizing partial data synchronization management. This data synchronization management by data category realizes fine-grained control or minimal control of synchronized data, enhances the user's control over personal data, and can effectively avoid privacy data leakage and other problems in a multi-device scenario, thereby effectively improving the data privacy security of the device and improving the user experience. In addition, the amount of data synchronization can be reduced, thereby effectively reducing the power consumption of the electronic device, etc.

[0078] Further, in the present embodiment, the mobile phone 100 can determine different display states of the management controls according to the user's click operation on the management controls, that is, according to information that the data corresponding to the management controls between the mobile phone 100 and the synchronization device 200 is in open data synchronization or closed data synchronization. Thus, the user can conveniently check the data synchronization situation between the mobile phone 100 and the synchronization device 200 through the display state of the management controls in the mobile phone 100, and the user experience is effectively improved.

[0079] Further, in the present embodiment, the device management interface further includes a data synchronization area and a data independent area. The data synchronization area is used to display device icons of electronic devices that have logged in the aforementioned cloud account and are in data synchronization with the mobile phone 100. The data independent area is used to display device icons of electronic devices that are not in data synchronization with the mobile phone 100. In the present embodiment, the mobile phone 100 displays the device icons of the synchronization device 200 in the data synchronization area or the data independent area according to information such as whether the synchronization device 200 is in data synchronization with the mobile phone 100. If the mobile phone 100 receives an operation of the user dragging (or also referred to as moving) the device icon of the synchronization device 200 from the data synchronization area to the data independent area, the mobile phone 100 stops data synchronization of all data between the mobile phone 100 and the synchronization device 200. If the mobile phone 100 receives an operation of the user dragging the device icon of the synchronization device 200 from the data independent area to the data synchronization area, the mobile phone 100 starts data synchronization of preset data between the mobile phone 100 and the synchronization device 200, or displays a data synchronization management interface corresponding to the synchronization device 200 for the user to perform data synchronization management.

[0080] In this way, the user only needs to perform simple interactions such as dragging the device icon of the synchronization device 200 on the device management interface displayed by the mobile phone 100, to conveniently and simply perform data synchronization management between the mobile phone 100 and the synchronization device 200, thereby simplifying the data synchronization management operation and improving the user experience.

[0081] Further, in the present implementation, only the data of the applications installed in both the mobile phone 100 and the synchronization device 200 can be synchronized between the mobile phone 100 and the synchronization device 200. Therefore, in the present implementation, the mobile phone 100 can classify the application data in the mobile phone 100 and / or the application data in the synchronization device 200, and determine the data risk level and the data usage scenario of each type of application data, and the device security level, the device sharing degree, and the device usage scenario of the synchronization device 200 according to the product serial number and other device information of the synchronization device 200. Then, the mobile phone 100 determines the first data displayed on the data synchronization management interface and the data synchronization management sub-interface according to at least one of the data risk level, the data usage scenario, the device security level, the device sharing degree, and the device usage scenario, for the user to perform data synchronization management (e.g., to select whether to enable data synchronization).

[0082] In addition, the mobile phone 100 can also determine the second data in the application data that is enabled by default for data synchronization, and / or the third data in the application data that is not enabled by default for data synchronization, according to at least one of the data risk level, the data usage scenario, the device security level, the device sharing degree, and the device usage scenario.

[0083] In addition, in the present implementation, the mobile phone 100 displays the application icon and the data icon corresponding to the first data on the data synchronization management interface and the data synchronization management sub-interface, so that the user can select whether to enable data synchronization of the first data through the application icon and the data icon. In addition, the mobile phone 100 generally enables data synchronization between the mobile phone 100 and the synchronization device 200 for the second data by default, and generally does not enable data synchronization between the mobile phone 100 and the synchronization device 200 for the third data by default. In addition, the mobile phone 100 can display or not display the application icon of the application corresponding to the second data or the data icon of the application sub-data on the data synchronization management interface and the data synchronization management sub-interface, and the mobile phone 100 does not display the application icon of the application corresponding to the third data or the data icon of the application sub-data on the data synchronization management interface and the data synchronization management sub-interface. In this way, the data synchronization management between the mobile phone 100 and the synchronization device 200 can be more convenient.

[0084] In summary, in the present implementation, the mobile phone 100 can facilitate and simplify the data synchronization management between the mobile phone 100 and the synchronization device 200 based on the user operation, and the application data in the mobile phone 100 and / or the synchronization device 200, and the device information of the synchronization device 200, without the need for the user to perform data synchronization management operations on the mobile phone 100 and the synchronization device 200 respectively, thereby simplifying the user operation and effectively improving the user experience.

[0085] The functions of each electronic device in the data synchronization management system provided by the implementation of the present application will be described below.

[0086] The mobile phone 100 is a private electronic device with high privacy, and is used frequently by the user. The mobile phone 100 has a system-level cloud account, and can discover the synchronization device 200 that has logged in the cloud account currently or historically. In addition, the mobile phone 100 has installed multiple applications, and the user generates application data such as user usage data and user behavior data in the process of using the applications. Taking the user usage data as an example, if the data synchronization of an application is enabled, the user usage data corresponding to the application can be uploaded to the cloud 300 by the mobile phone 100. In addition, the mobile phone 100 can access the user usage data corresponding to the application synchronized to the cloud 300 by the synchronization device 200 through the cloud 300, and display the user usage data on the mobile phone 100.

[0087] In addition, in the implementation, the mobile phone 100 can synchronize the user usage data corresponding to all the applications in the mobile phone 100 to the cloud 300. In addition, the mobile phone 100 can control the access right (i.e., the data synchronization access right) of the synchronization device 200 to the user usage data synchronized to the cloud 300 by the mobile phone 100 through the cloud 300. For example, the mobile phone 100 can control whether the synchronization device 200 accesses or receives the user usage data synchronized to the cloud 300 by the mobile phone 100, and control the type of the user usage data that the synchronization device 200 can access or receive from the cloud 300, and so on, so as to realize the data synchronization between the mobile phone 100 and the synchronization device 200.

[0088] The synchronization device 200 is a private electronic device with low privacy, and can log in to the system-level cloud account. In addition, the synchronization device 200 has installed multiple applications, and the user generates user usage data in the process of using the applications. If the data synchronization of an application is enabled, the user usage data corresponding to the application can be synchronized to the cloud 300 by the synchronization device 200.

[0089] The cloud 300 is a storage station of user usage data and the like, and is configured to receive user usage data on the device from the mobile phone 100 and the synchronization device 200 and store the user usage data. The synchronization manner between the electronic device such as the mobile phone 100 and the synchronization device 200 and the cloud 300 is as follows: the cloud 300 provides data synchronization access permission, after the electronic device is connected to the cloud 300, if the data synchronization access permission of an application of the electronic device is turned on, the electronic device can access the user usage data corresponding to the application stored in the cloud 300 and display the user usage data on the electronic device. When the data synchronization access permission of an application of the electronic device to the cloud 300 is turned off, the electronic device no longer displays the user usage data corresponding to the application synchronized from the cloud 300. In addition, when some user usage data is deleted from the cloud 300, the mobile phone 100 and the synchronization device 200 also synchronously delete the corresponding user usage data synchronized from the cloud 300.

[0090] The structure of the mobile phone 100 provided by the implementation manner of the present application will be described below.

[0091] Please refer to Figure 4 , Figure 4 A structure schematic diagram of the mobile phone 100 is shown. The mobile phone 100 includes a processor 110, an input detection unit 120, a display 130, and a communication unit 140.

[0092] The processor 110 can include one or more processing units, for example: the processor 110 can include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units can be independent devices or integrated in one or more processors. The processor 110 can generate operation control signals according to instruction operation codes and timing signals, and complete the control of fetching and executing instructions. The processor 110 can be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory can save instructions or data that have just been used or are repeatedly used by the processor 110. If the processor 110 needs to use the instructions or data again, the instructions or data can be directly called from the memory, avoiding repeated access and reducing the waiting time of the processor 110, thereby improving the efficiency of the system. The processor 110 executes various processes related to data synchronization management of the mobile phone 100 by running stored instructions.

[0093] For example, processor 110 is used to perform corresponding calculations based on user input during the data synchronization management process, generate corresponding calculation results, and send the calculation results to display 130, causing display 130 to refresh the visual interface. Additionally, processor 110 is also used to manage the data synchronization access permissions of cloud 300 to synchronization device 200, i.e., to control the data sent from cloud 300 to synchronization device 200. Furthermore, it performs granular decomposition on data from mobile phone 100, synchronization device 200, or data synchronized from cloud 300 to obtain application sub-data (also called categorized data), and performs risk rating and usage scenario analysis on each application sub-data to obtain data risk level and data usage scenario. Moreover, processor 110 is also used to assess the device security level and device sharing degree of synchronization device 200, obtaining device security level, device sharing degree, and device usage scenario, etc. The processor 110 is also used to determine the risk level range of data that the synchronization device 200 can receive and store based on at least one of the following: data risk level, data usage scenario, device security level, device sharing information, and device usage scenario, and to provide corresponding data protection measures. For example, it determines the first data displayed on the aforementioned data synchronization management interface and data synchronization management sub-interface between the mobile phone 100 and the synchronization device 200 for the user to select whether to enable data synchronization, and determines the second data that is enabled by default, the third data that is not enabled by default, and performs different data management on each data.

[0094] The input detection unit 120 is used to receive user input, such as touch operations like clicking on the mobile phone 100. This can be implemented using components such as a pressure sensor. In some implementations, the pressure sensor can be located on the display 130. When a touch operation is applied to the display 130, the mobile phone 100 detects the intensity of the touch operation based on the pressure sensor to determine the type of user-triggered operation. In some embodiments, the mobile phone 100 can also calculate the touch position based on the detection signal from the pressure sensor, for example, determining operations such as clicking or dragging the device icon of an electronic device, clicking other controls, and determining the location where the user performs the touch operation.

[0095] In some embodiments, the pressure sensor can also be a touch sensor, also referred to as a "touch device" or a "touch chipset". The touch sensor can be disposed on the display screen, and the display 130 can be formed by the touch sensor and the display screen, also referred to as a "touch screen". The touch sensor is configured to detect a touch operation applied thereto or in the vicinity thereof. The touch sensor can transmit the detected touch operation to the processor 110 to determine a touch event type and a location where the touch event occurs, and the mobile phone 100 can provide visual output related to the touch operation through the display 130.

[0096] The display 130 provides a visual output interface for displaying various image information, and for feeding back the execution result of the input of the user. After the user performs the input operation, the interface of the display 130 will change correspondingly, for example, the device management interface, the data synchronization management interface, and the data synchronization management sub-interface described above, and the like. In some embodiments, the mobile phone 100 can include one or N displays 130, where N is a positive integer greater than 1.

[0097] The communication unit 140 is configured to realize the communication between the mobile phone 100 and the synchronization device 200, such as the cloud 300, the tablet computer 210, the television 220, the large-screen device 230, and the notebook computer 240, so as to realize the data synchronization. The communication unit 140 can be realized by a mobile communication module and a wireless communication module. The mobile communication module can provide a solution for wireless communication, such as 2G / 3G / 4G / 5G, applied to the mobile phone 100. The wireless communication module can provide a solution for wireless communication, such as wireless local area networks (WLAN) (for example, wireless fidelity (Wi-Fi) network), Bluetooth (BT), near field communication (NFC), infrared (IR) technology, and the like, applied to the mobile phone 100.

[0098] It can be understood that the structure shown in the embodiments of the present application does not constitute a specific limitation on the mobile phone 100. In other embodiments of the present application, the mobile phone 100 can include more or fewer components than those shown, or combine certain components, or split certain components, or different arrangement of components. The components shown can be realized by hardware, software, or a combination of software and hardware.

[0099] The structure of the cloud 300, the tablet computer 210, the television 220, the large-screen device 230, and the notebook computer 240 will not be described in detail in the implementation manner of the present application, and can be selected and set as needed.

[0100] The data synchronization management method provided by the implementation manner of the present application will be described below in combination with some display interface diagrams of the mobile phone 100.

[0101] First, in the implementation manner, the mobile phone 100 logs in the cloud account "1234567" as described above, and displays the display interface as shown in Figure 5A . Please continue to refer to Figure 5A . If the mobile phone 100 receives a click operation of the user on "My Devices", the mobile phone 100 displays a device management interface, and the device management interface can display the device icons of the electronic devices that have logged in the cloud account currently, and the device icons of the electronic devices that have logged in the cloud account historically.

[0102] It should be noted that since one cloud account can be logged in on multiple electronic devices, as long as an electronic device logs in the cloud account, the cloud end 300 can discover the electronic device that logs in the cloud account. For example, the electronic devices that have logged in the cloud account historically, and the online electronic devices that log in the cloud account currently, etc. In addition, the online electronic devices that have logged in the cloud account currently can include the electronic devices that log in the cloud account frequently, and the electronic devices that log in the cloud account temporarily. Therefore, when the user uses the mobile phone 100, after logging in the cloud account on the mobile phone 100, the mobile phone 100 can discover the electronic devices that log in the cloud account through the cloud end 300, and display the device icons of the electronic devices in the device management interface.

[0103] For example, please refer to Figure 5B . The device management interface displayed by the mobile phone 100 can be as shown in Figure 5B . The device management interface includes the cloud account "1234567", and the nickname "Abc" of the user corresponding to the cloud account. In addition, the device management interface also includes a data synchronization area and a data independent area, the device icon of the mobile phone 100, and the device icons of the tablet computer 210, the television 220 and the large-screen device 230 discovered by the mobile phone 100, which log in the same cloud account "1234567" as the mobile phone 100 currently.

[0104] In this implementation, the mobile phone 100 displays the device icons of each electronic device in either the data synchronization area or the data independence area, depending on whether data synchronization is currently occurring between the mobile phone 100 and the tablet computer 210, TV 220, and large-screen device 230. When the device icon is in the data synchronization area, it indicates that the electronic device and the mobile phone 100 have achieved at least partial data synchronization at the current time, and this data synchronization is long-term, with synchronized data being updated over time until the user removes the electronic device from the data synchronization area via the mobile phone 100, or the user stops the data synchronization between the mobile phone 100 and the electronic device. When the device icon is in the data independence area, it indicates that the electronic device and the mobile phone 100 are used independently at the current time, and all application data of the electronic device is stored locally and will not be uploaded to the cloud 300 for data synchronization with other electronic devices. Therefore, the data of an electronic device in the data independence area is isolated from the data of other electronic devices, and the electronic device will not synchronize data with other electronic devices to share data.

[0105] For example, such as Figure 5B As shown, mobile phone 100 determines that tablet computer 210 and large-screen device 230 are synchronizing data with mobile phone 100. Therefore, mobile phone 100 displays the device icons of tablet computer 210 and large-screen device 230 in the data synchronization area. It can be seen that tablet computer 210 is currently synchronizing two items of data with mobile phone 100, and large-screen device 230 is synchronizing three items of data with mobile phone 100. Additionally, mobile phone 100 determines that TV 220 is not currently synchronizing data with mobile phone 100, so mobile phone 100 displays the device icon of TV 220 in a separate data area. Furthermore, mobile phone 100, as the master device (i.e., the current device), has already enabled data synchronization, so mobile phone 100 also displays its device icon in the data synchronization area.

[0106] In this way, users can easily view the electronic devices currently logged into the same cloud account as the mobile phone through the device management interface displayed on the mobile phone 100, and can also check whether each electronic device is syncing data with the mobile phone 100, as well as the number of data items that are synced, which can effectively improve the user experience.

[0107] Further, in the present implementation, the mobile phone 100 can also determine whether the tablet 210, the television 220 and the large-screen device 230 are electronic devices that frequently log in the cloud account or electronic devices that temporarily log in the cloud account according to information such as the number of times the tablet 210, the television 220 and the large-screen device 230 log in the cloud account, and display the device icons of the electronic devices in different manners. For example, if the mobile phone 100 determines that the tablet 210 and the television 220 log in the cloud account for more than or equal to 3 times, the mobile phone 100 determines that the tablet 210 and the television 220 are electronic devices that frequently log in the cloud account, please refer to Figure 5C , and the mobile phone 100 displays the border lines of the device icons of the tablet 210 and the television 220 as solid lines. If the mobile phone 100 determines that the large-screen device 230 logs in the cloud account less than 3 times, the mobile phone 100 determines that the large-screen device 230 is an electronic device that temporarily logs in the cloud account, please refer to Figure 5C , and the mobile phone 100 displays the border line of the device icon of the large-screen device 230 as a dashed line.

[0108] In this way, the user can conveniently know the number of times the electronic devices log in the cloud account through the different display manners of the device icons on the device management interface, so that the user can perform corresponding data synchronization management on the electronic devices, and the user experience can be effectively improved.

[0109] Of course, in other implementations of the present application, the mobile phone 100 can also display the device icons of the electronic devices that frequently log in the cloud account and the electronic devices that temporarily log in the cloud account in other manners, so as to facilitate the user to view, which can be specifically selected and set according to the needs.

[0110] Further, in the present implementation, the mobile phone 100 can also display the device icons of the electronic devices (hereinafter referred to as “historical login electronic devices”) that have not logged in the cloud account at present but have logged in the cloud account in the past, and display the device icons of the electronic devices that have logged in the cloud account at present and the historical login electronic devices in different manners. Please refer to Figure 5D , for example, if the mobile phone 100 determines that the tablet 210, the television 220 and the large-screen device 230 are electronic devices that have logged in the cloud account at present, the mobile phone 100 displays the border lines of the device icons as solid lines. If the mobile phone 100 determines that the notebook computer 240 is a historical login electronic device, the mobile phone 100 displays the device icon of the notebook computer 240 and the border line thereof as dashed lines. And since the notebook computer 240 has not started the cloud service at present, the mobile phone 100 displays the device icon of the notebook computer 240 in the data independent area.

[0111] In this way, the mobile phone 100 can display device icons of all electronic devices that have logged in the cloud account, and the user can conveniently know the current login status of the cloud account of each electronic device through different display manners of the device icons on the device management interface, so that the user can perform corresponding data synchronization management on each electronic device, and the user experience can be effectively improved.

[0112] Of course, in another implementation of the present application, the mobile phone 100 can also display device icons of electronic devices that have logged in the cloud account and electronic devices that have historically logged in the cloud account in other manners, so as to facilitate the user to view, which can be specifically selected and set according to the needs of the user.

[0113] In the data synchronization management method provided by the implementation of the present application, the user can perform data synchronization management between the corresponding electronic device and the mobile phone 100 by clicking the device icon in the data synchronization area or the data independent area on the device management interface. Figures 5B-5D The user can click the device icon in the data synchronization area or the data independent area on the device management interface shown in any one of the figures to perform data synchronization management between the corresponding electronic device and the mobile phone 100. Hereinafter, the process of the user managing data synchronization between the mobile phone 100 and the tablet computer 210 through the mobile phone 100 will be described by taking the tablet computer 210 as an example.

[0114] Please continue to refer to Figure 5D If the mobile phone 100 receives a click operation of the user on the device icon of the tablet computer 210, the mobile phone 100 displays a data synchronization management interface as shown in Figure 5E The data synchronization management interface includes application icons of a part of applications installed in the tablet computer 210. These applications are usually system-level applications, or other applications that support cloud account login or cloud services. For example, these applications are all applications in the tablet computer 210 that support cloud services, and these applications are usually installed in the tablet computer 210 and the mobile phone 100 at the same time. Of course, the mobile phone 100 can also display applications that have been installed in the tablet computer 210 but have not been installed in the mobile phone 100. It should be noted that in this case, the mobile phone 100 and the tablet computer 210 cannot perform data synchronization of the corresponding applications before the mobile phone 100 installs the same applications.

[0115] In addition, in the implementation of the present application, management controls for the user to perform data synchronization start and stop operations are displayed behind each application icon, so that the user can manage data synchronization of each application through the management controls, and view the data synchronization status. In the implementation of the present application, the mobile phone 100 can display different management controls behind the application icons according to application data in the mobile phone 100 and / or the tablet computer 210.

[0116] For example, if an application's data is relatively simple, the phone 100 will not perform data categorization. For instance, the "WLAN" application might only store WiFi account and password data, and the "Contacts" application might only store contact data. In this case, the phone 100 can display a management control M1 next to these applications, allowing users to directly control data synchronization on and off within the data synchronization management interface. Conversely, if an application's data is diverse, the phone 100 will categorize the application's data, identifying multiple application sub-data sets. The phone 100 will then display a management control M2 next to these applications, allowing users to access the corresponding data synchronization management sub-interface. This sub-interface displays the application sub-data set, along with the corresponding data synchronization on / off control, enabling users to manage data synchronization by category.

[0117] Additionally, if an application includes multiple application sub-data sets, after enabling data synchronization, the following will be displayed after its application icon: Figure 5E The management control M3 shown can also include information on the number of application sub-data items for which data synchronization has been enabled. For example, as... Figure 5E As shown, it can be seen that data synchronization of two application sub-data in the "Video" application has been enabled between mobile phone 100 and tablet computer 210.

[0118] In this implementation, users can manage data synchronization across applications and view data synchronization status through management controls M1, M2, and M3. For example, through... Figure 5E The data synchronization management interface shown indicates that data synchronization for the two application sub-data items included in the "Video" application is currently enabled between mobile phone 100 and tablet computer 210. However, data synchronization for other applications such as "WLAN" and "Calendar" is not enabled between tablet computer 210 and mobile phone 100.

[0119] Please see Figure 5F ,like Figure 5F As shown in the data synchronization management interface on the left, if mobile phone 100 receives a user's click operation on the management control M3 corresponding to the "Video" application, mobile phone 100 will display as follows: Figure 5F The data synchronization management sub-interface shown on the right. This data synchronization management sub-interface includes multiple application sub-data corresponding to the "Video" application. For example, as can be seen from this data synchronization management sub-interface, the "Video" application includes four categories of application sub-data: "My Favorites", "Playback History", "My Schedules", and "Watching Reminders". That is, for the "Video" application, Mobile 100 provides data synchronization functions for these four categories.

[0120] In addition, each application sub-data is displayed with a management control n1 behind it. According to the management control n1, the user can check whether the data synchronization of each application sub-data is enabled or not. For example, it can be seen from the data synchronization management sub-interface that the application sub-data whose data synchronization is enabled includes the "My Collection" and "TV Show Reminder" data, while the data synchronization of the "Play History" and "My Reservation" application sub-data is not enabled. It should be noted that at this time, the tablet computer 210 can synchronize the "My Collection" and "TV Show Reminder" data in the mobile phone 100 from the cloud 300.

[0121] Further, the user can enable and disable the data synchronization of the corresponding application sub-data through the management control n1, that is, manage the data synchronization.

[0122] For example, if the mobile phone 100 receives a user's click operation on the management control n1 corresponding to the "Play History" control (at this time, it is an operation of enabling data synchronization), the mobile phone 100 sends a data synchronization enabling instruction to the cloud 300, so that the cloud 300 enables the permission of the tablet computer 210 to access the "Play History" data of the "Video" application in the mobile phone 100 according to the data synchronization enabling instruction, that is, enables the tablet computer 210 to synchronize the "Play History" data of the "Video" application in the mobile phone 100 through the cloud 300. In addition, the cloud 300 can also send a data synchronization enabling instruction to the tablet computer 210, so that the tablet computer 210 enables the data synchronization of the "Play History" data of the "Video" application according to the data synchronization enabling instruction, synchronizes the corresponding data to the cloud 300, and facilitates the mobile phone 100 to synchronize the "Play History" data of the "Video" application in the tablet computer 210 from the cloud 300.

[0123] In addition, if the mobile phone 100 receives a user's click operation on the management control n1 corresponding to the "My Collection" control (at this time, it is an operation of disabling data synchronization), the mobile phone 100 sends a data synchronization disabling instruction to the cloud 300, so that the cloud 300 disables the permission of the tablet computer 210 to access the "My Collection" data of the "Video" application in the mobile phone 100 according to the data synchronization disabling instruction, that is, disables the tablet computer 210 to synchronize the "My Collection" data of the "Video" application in the mobile phone 100 through the cloud 300. In addition, the cloud 300 can also send a data synchronization disabling instruction to the tablet computer 210, so that the tablet computer 210 stops synchronizing the "My Collection" data of the "Video" application to the cloud 300 according to the data synchronization disabling instruction. In addition, the cloud 300 can also delete the "My Collection" data of the "Video" application previously synchronized by the tablet computer 210.

[0124] Furthermore, the data synchronization management sub-interface also includes a "Synchronize All" data identifier and a corresponding management control n2. Users can use management control n2 to manage the synchronization of all application sub-data for the "Video" application displayed on the interface. This "All Application Sub-Data" includes "My Favorites" data, "Playback History" data, "My Schedule" data, and "Watching Reminders" data. For example, if mobile phone 100 receives a user's click on management control n2 (which is an operation to enable data synchronization), mobile phone 100 sends a data synchronization enable command to cloud 300. This allows cloud 300 to grant tablet computer 210 permission to access all application sub-data in the "Video" application interface on mobile phone 100, enabling tablet computer 210 to synchronize all application sub-data in the "Video" application interface on mobile phone 100 via cloud 300. In addition, the cloud 300 can also send a data synchronization start command to the tablet computer 210, so that the tablet computer 210 can start the synchronization of all application sub-data in the interface of its "Video" application according to the data synchronization start command, so as to synchronize the corresponding data to the cloud 300, so that the mobile phone 100 can synchronize all application sub-data in the interface of the "Video" application in the tablet computer 210 from the cloud 300.

[0125] Furthermore, if the mobile phone 100 receives another click operation from the user on the management control n2 (this is an operation to stop data synchronization), the mobile phone 100 sends a data synchronization stop command to the cloud 300. This causes the cloud 300 to, according to the data synchronization stop command, close the tablet computer 210's access permission to all application sub-data in the "Video" application interface on the mobile phone 100, thus preventing the tablet computer 210 from synchronizing all application sub-data in the "Video" application interface on the mobile phone 100 through the cloud 300. Additionally, the cloud 300 can also send a data synchronization stop command to the tablet computer 210, causing the tablet computer 210 to stop synchronizing all application sub-data in its "Video" application interface to the cloud 300. Furthermore, the cloud 300 can also delete all application sub-data in the "Video" application interface previously synchronized from the tablet computer 210.

[0126] Please see Figure 5G ,like Figure 5G As shown in the data synchronization management interface on the left, if mobile phone 100 receives a click operation from the user on the management control M1 corresponding to the "WLAN" application, mobile phone 100 will start data synchronization for the "WLAN" application and display the following: Figure 5G The display interface shown on the right.

[0127] It should be noted that after the mobile phone 100 opens the data synchronization of the "WLAN" application, the mobile phone 100 sends a data synchronization opening instruction to the cloud 300, so that the cloud 300 opens the permission of the tablet computer 210 to access the "WLAN" application data in the mobile phone 100 according to the data synchronization opening instruction, that is, so that the tablet computer 210 can synchronize all the data of the "WLAN" application in the mobile phone 100 through the cloud 300. In addition, the cloud 300 can also send a data synchronization opening instruction to the tablet computer 210, so that the tablet computer 210 opens the data synchronization of the "WLAN" application according to the data synchronization opening instruction, so as to synchronize all the data of the "WLAN" application in the tablet computer 210 to the cloud 300, and facilitate the mobile phone 100 to synchronize all the data of the "WLAN" application in the tablet computer 210 from the cloud 300.

[0128] Please refer to Figure 5H For example Figure 5H As shown in the data synchronization management interface on the left, if the mobile phone 100 receives a click operation of the user on the management control M2 corresponding to the "gallery" application, the mobile phone 100 displays Figure 5H the data synchronization management sub-interface shown on the right. The data synchronization management sub-interface includes "photo", "collection", and "screenshot" three types of application sub-data corresponding to the "gallery" application. It can be seen that the current "photo", "collection", and "screenshot" three types of application sub-data do not open data synchronization.

[0129] In addition, as shown in the data synchronization management sub-interface on the right Figure 5H , the "photo", "collection", and "screenshot" three types of application sub-data also display corresponding management controls n1 behind them, and the "all synchronization" data identifier also displays a corresponding management control n2 behind it. The user can manage the synchronization of the corresponding data through the management control n1 and the management control n2, and the process is the same as or similar to the management process of the "video" application shown in the foregoing Figure 5F . Here, details are not repeated.

[0130] In summary, in the implementation manner of the present application, the mobile phone 100 can open or close the data synchronization between the mobile phone 100 and the tablet computer 210 according to the click operation of the user on the management control corresponding to each application and each type of application sub-data in the tablet computer 210 displayed through the foregoing data synchronization management interface and data synchronization management sub-interface, so as to conveniently realize the data synchronization management of the tablet computer 210. In this way, the data synchronization operation is simplified, and the user experience is improved. Moreover, the user can conveniently check the data synchronization situation of the tablet computer 210 through the display state of each management control through the mobile phone 100, which also effectively improves the user experience.

[0131] Furthermore, in the implementation of this application, if the applications displayed on the data synchronization management interface corresponding to the tablet computer 210 include applications installed on the tablet computer 210 but not installed on the mobile phone 100 (e.g., the "Music" application), then, if Figure 5I As shown in the data synchronization management interface on the left, if mobile phone 100 receives a user's click operation on the management control M2 corresponding to the "Music" application, mobile phone 100 can display as follows: Figure 5I The data synchronization management interface on the right displays a reminder message: "The [Music] app is not currently installed on mobile phone 100. Please confirm whether to install the [Music] app and enable data synchronization?", along with "OK" and "Cancel" controls. If mobile phone 100 receives a click on the "OK" control, it downloads and installs the "Music" app and enables data synchronization between mobile phone 100 and tablet computer 210. If mobile phone 100 receives a click on the "Cancel" control, it does not download and install the "Music" app, nor does it enable data synchronization between mobile phone 100 and tablet computer 210.

[0132] In addition, in this implementation, the mobile phone 100 can also display the border of the "Music" application icon as a dotted line, so that users can easily see that the "Music" application is not currently installed on the mobile phone 100. Of course, in other implementations of this application, the mobile phone 100 can also display the application icons of installed and uninstalled applications in other ways for users to view, and they can choose and set them as needed.

[0133] It should be noted that in this implementation, if mobile phone 100 receives the user's request for the aforementioned... Figure 5E After clicking the "Back" control indicated by the middle arrow, the mobile phone 100 exits the data synchronization management interface corresponding to the tablet computer 210. Furthermore, if the mobile phone 100 determines that there is an application or application sub-data on the tablet computer 210 with data synchronization enabled, the mobile phone 100 will automatically display the device icon of the tablet computer 210 in the data synchronization area, as shown below. Figures 5B-5D The device management interface shown. If the mobile phone 100 determines that there are no applications or application sub-data with data synchronization enabled on the tablet computer 210, the mobile phone 100 will automatically display the device icon of the tablet computer 210 in the data-independent area.

[0134] In another implementation of the present application, after the mobile phone 100 receives a click operation of a user on the device icon of the television 220 displayed in the data independent area, the mobile phone 100 can also display the data synchronization management interface corresponding to the television 220, so as to be used by the user to perform data synchronization management on the television 220. In addition, after the mobile phone 100 further receives an operation of the user to start data synchronization of any application or application sub in the television 220 through the data synchronization management interface, and receives an operation of the user to exit the data synchronization management interface, the mobile phone 100 automatically displays the device icon of the television 220 in the data synchronization area. Of course, if the mobile phone 100 determines that the user does not start data synchronization of any application or application sub, the mobile phone 100 still displays the device icon of the television 220 in the data independent area.

[0135] It should be noted that the mobile phone 100 is the most commonly used electronic device by the user, and the scenario of the mobile phone 100 cooperating with other electronic devices becomes very frequent. In this case, although the technical capability of device interconnection and data synchronization can be greatly improved, thereby improving the user experience. However, since the mobile phone 100 interacts with multiple other electronic devices, it also brings privacy security problems. Moreover, because the use frequency and use scenario of the electronic device are different, the order of magnitude of the privacy data carried by the electronic device is also different, and the degree of influence of different types of data on the privacy security of the user is also different. Therefore, when the user synchronizes the data in the mobile phone 100 to other electronic devices through a cloud account synchronization manner, or synchronizes the data of other electronic devices using the mobile phone 100, there may be a huge privacy security risk.

[0136] The data synchronization management method provided by the implementation of the present application classifies the application data in the mobile phone 100 or the application data in the tablet computer 210, can determine the application sub data displayed in the data synchronization management sub interface, so that the user can control the data synchronization according to different data categories, and realizes the synchronization management of part of the application data, that is, the user can autonomously select the data to be synchronized, instead of only choosing between the two options of different data and completely synchronized data. In the implementation of the present application, the data synchronization mode based on the data category realizes the minimum control of the synchronized data, enhances the control degree of the user on the personal data, and can effectively avoid the problem of privacy data leakage, and can effectively improve the user experience.

[0137] Further, in the implementation of the present application, the user can also perform the data synchronization management on the data in the mobile phone 100 through the data synchronization management interface displayed in the data independent area. Figures 5B-5DThe device management interface shown in any one of the figures, through the device icon in the data synchronization area and the data independent area between drag (or also known as the movement), to achieve the phone 100 and the synchronization device 200 between the data synchronization management, that is, to achieve the opening of the phone 100 and the synchronization device 200 between the data synchronization, or stop the phone 100 and the synchronization device 200 between the data synchronization management.

[0138] For example, please see Figure 5J , if the phone 100 receives the user to drag the device icon of the tablet 210 from the data synchronization area to the data independent area operation, the phone 100 determines that the user needs to stop the data synchronization between the phone 100 and the tablet 210, the phone 100 displays the device icon of the tablet 210 in the data independent area. And, the phone 100 sends a data synchronization stop instruction to the cloud 300, so that the cloud 300 closes the data synchronization access permission of the tablet 210 to synchronize all data in the phone 100 through the cloud 300 according to the data synchronization stop instruction. That is, the cloud 300 stops synchronizing the tablet 210 to the phone 100 to the cloud 300, and also stops synchronizing the phone 100 to the tablet 210 to the cloud 300.

[0139] Further, if the phone 100 receives the user to drag the device icon of the tablet 210 back to the data synchronization area operation again, the phone 100 defaults to restore the data synchronization type preference option set by the tablet 210 last time, that is, the default opening of the phone 100 and the tablet 210 between the previous data synchronization task, can not be called out as shown in the data synchronization management interface of the tablet 210 as described above Figure 5E . Of course, if the phone 100 receives the user to drag the device icon of the tablet 210 back to the data synchronization area operation again, the phone 100 can also call out the data synchronization management interface of the tablet 210 as shown in the data synchronization management interface of the tablet 210 as described above Figure 5E . It can be selected and set according to.

[0140] In another implementation of the present application, please see Figure 5K , after receiving the user to drag the device icon of the tablet 210 from the data synchronization area to the data independent area operation, the phone 100 can also display the data synchronization management interface of the tablet 210 as shown in Figure 5KThe stop data synchronization prompt information "whether to close the data synchronization function of the tablet computer 210" is displayed on the right side of the data synchronization management interface, and the "cancel" control and the "confirm" control are displayed. If the mobile phone 100 receives a click operation of the "confirm" control by the user, the mobile phone 100 determines that the user needs to close the data synchronization between the mobile phone 100 and the tablet computer 210, and the mobile phone 100 continues to display the device icon of the tablet computer 210 in the data independent area, and the mobile phone 100 sends a data synchronization stop instruction to the cloud 300, so that the cloud 300 closes the data synchronization access permission of the tablet computer 210 to the aforementioned two data in the mobile phone 100 through the cloud 300 according to the data synchronization stop instruction. If the mobile phone 100 receives a click operation of the "cancel" control by the user, the mobile phone 100 determines that the user does not need to close the data synchronization between the mobile phone 100 and the tablet computer 210, and the mobile phone 100 displays the device icon of the tablet computer 210 in the data synchronization area again, and at this time, the tablet computer 210 can continue to synchronize the aforementioned two data in the mobile phone 100 through the cloud 300.

[0141] Please refer to Figure 5L , if the notebook computer 240 is also currently logged in the aforementioned cloud account, after the mobile phone 100 receives the operation of dragging the device icon of the notebook computer 240 from the data independent area to the data synchronization area by the user, the mobile phone 100 determines that the user needs to start the data synchronization between the mobile phone 100 and the notebook computer 240, and as Figure 5L indicated, the mobile phone 100 displays the device icon of the notebook computer 240 in the data synchronization area. Furthermore, if the mobile phone 100 further receives a click operation of the device icon of the notebook computer 240 by the user, the mobile phone 100 can display Figure 5M indicated, a data synchronization management interface, so that the user selects the application between the mobile phone 100 and the notebook computer 240 which needs to start the data synchronization function through the data synchronization management interface.

[0142] In another implementation manner of the present application, as Figure 5L indicated, after the mobile phone 100 receives the operation of dragging the device icon of the notebook computer 240 from the data independent area to the data synchronization area by the user, the mobile phone 100 can also directly display Figure 5M indicated, a data synchronization management interface, so that the user selects the application between the mobile phone 100 and the notebook computer 240 which needs to start the data synchronization function through the data synchronization management interface.

[0143] In another implementation of this application, after receiving a user's operation of dragging the laptop 240 from the independent data area to the data synchronization area, if the mobile phone 100 determines that the user has previously enabled data synchronization in the laptop 240's data synchronization management interface, the mobile phone 100 can directly enable data synchronization for some applications or application sub-data that the user has previously preset (as an example of preset data), such as enabling data synchronization for applications like the aforementioned gallery, without needing to re-set the data synchronization. Alternatively, the mobile phone 100 can also display the aforementioned data synchronization management interface, allowing the user to reselect and set the applications or application sub-data to be synchronized as needed.

[0144] In another implementation of this application, if the laptop 240 is an electronic device that is not currently logged into a cloud account, when the mobile phone 100 receives an operation from the user dragging the device icon of the laptop 240 from the data-independent area to the data-synchronized area, the mobile phone 100 displays a reminder message: "The current device is not logged into a cloud account. Please log in to your cloud account first." Then, the mobile phone 100 will by default display the device icon of the laptop 240 again in the data-independent area.

[0145] In summary, users can [do something] in the aforementioned [context]. Figures 5B-5D The data synchronization management interface shown allows users to drag device icons between the data synchronization area and the independent data area to control data synchronization between the corresponding electronic device and the mobile phone 100. This simple and convenient drag-and-drop interface enables users to easily manage data synchronization between their electronic devices, effectively improving the user experience.

[0146] Furthermore, in this implementation, mobile phone 100 can also provide a device deletion function through the device management interface, and the user can delete the device through the aforementioned... Figures 5B-5D On any of the device management interfaces shown in the images, you can delete electronic devices by long-pressing the device icon.

[0147] For example, see Figure 5N If mobile phone 100 confirms that the current device management interface displays a laptop 240 that has previously logged into a cloud account, and if... Figure 5N As shown in the device management interface on the left, if the mobile phone 100 receives a long press operation from the user on the device icon of the laptop 240 for a certain period of time (e.g., a long press for 5 seconds), the mobile phone 100 displays a "Delete" control. If the mobile phone 100 further receives a click operation from the user on the "Delete" control, the mobile phone 100 directly deletes the device icon of the laptop 240 and displays... Figure 5N The device management interface shown on the right.

[0148] Alternatively, if the mobile phone 100 receives a user's click operation on the "delete" control, the mobile phone 100 displays a "cancel" control and a "confirm" control. If the mobile phone 100 receives a user's click operation on the "confirm" control, the mobile phone 100 determines that the user needs to delete the notebook computer 240, and then the mobile phone 100 removes the device icon of the notebook computer 240 from the current device management interface, i.e., deletes the device icon of the notebook computer 240, and displays the device management interface shown on the right side. Meanwhile, the data synchronization between the cloud 300 and the notebook computer 240 is stopped. If the mobile phone 100 receives a user's click operation on the "cancel" control, the mobile phone 100 determines that the user does not need to delete the notebook computer 240, and then the mobile phone 100 keeps the device icon of the notebook computer 240 in the current device management interface and displays it in the original position. Figure 5N

[0149] In addition, if the mobile phone 100 receives a user's long press operation on the device icon of the large-screen device 230 which logs in the cloud account temporarily, or receives a user's long press operation on the device icon of the electronic device such as the tablet computer 210 which logs in the cloud account frequently, the mobile phone 100 can also display a "delete" control for the user to delete the corresponding electronic device.

[0150] In another implementation manner of the present application, the mobile phone 100 can also delete a device icon based on other user interaction manners. For example, if the mobile phone 100 receives a user's operation of dragging the device icon out of the edge of the display interface of the mobile phone 100, the mobile phone 100 deletes the corresponding device icon.

[0151] Further, in another implementation manner of the present application, the mobile phone 100 can also simultaneously stop the data synchronization between the electronic device corresponding to the deleted device icon and the mobile phone 100, which can be selected and set as needed.

[0152] It should be noted that in the present implementation manner, after the device icon is deleted, it means that the mobile phone 100 will not display the device icon any more, i.e., it can be understood that the electronic device corresponding to the device icon will not be discovered by the mobile phone 100 and cannot be managed for device synchronization any more. Meanwhile, if the mobile phone 100 determines that the deleted device logs in the same cloud account as the mobile phone 100, the mobile phone 100 re-adds the device icon to the device management interface and displays it in the data independent area by default, and the mobile phone 100 can re-manage the device for data synchronization.

[0153] ​Further, in the implementation of the present application, the mobile phone 100 can classify the application data in the mobile phone 100 or the application data in the tablet computer 210, the television 220, the large-screen device 230 and the notebook computer 240, and determine the data risk level and the data usage scenario of each type of application data. In addition, the mobile phone 100 can also determine the device security level, the device sharing degree and the device usage scenario of different electronic devices according to the device information of the tablet computer 210, the television 220, the large-screen device 230 and the notebook computer 240. The mobile phone 100 can determine the device synchronization management interface and the device synchronization management sub-interface according to at least one of the data risk level, the data usage scenario, the device security level, the device sharing degree and the device usage scenario.

[0154] That is, in the implementation of the present application, the mobile phone 100 displays different data synchronization management interfaces and / or data synchronization management sub-interfaces for the electronic devices with different device security levels, device sharing degrees, device usage scenarios, data risk levels and data usage scenarios.

[0155] The following takes the tablet computer 210 and the television 220 as examples to illustrate how the mobile phone 100 displays the data synchronization management interface and the data synchronization management sub-interface of the tablet computer 210 and the television 220 according to the data risk level and the device sharing degree.

[0156] Please refer to Figure 5O , if the mobile phone 100 determines that the tablet computer 210 is a low-sharing device (i.e., a low-sharing device means that the device is a private-use device and has no usage scenario of sharing the device with others). Therefore, the mobile phone 100 can display the "wallet" application on the data synchronization management interface of the tablet computer 210, so that the user can perform data synchronization management of the "wallet" application between the mobile phone 100 and the tablet computer 210. If the mobile phone 100 determines that the television 220 is a high-sharing device (i.e., a high-sharing device means that the device is a shared device and will be used with others in a public place). Therefore, the mobile phone 100 does not display the "wallet" application on the data synchronization management interface of the television 220, so that the user cannot perform data synchronization management of the "wallet" application between the mobile phone 100 and the television 220. In this way, for the high-sharing television 220, the mobile phone 100 does not display the "wallet" application including sensitive data (i.e., the data risk level of the "wallet" application is high), so that the mobile phone 100 cannot synchronize the data of the "wallet" application to the television 220, i.e., the television 220 cannot synchronize the data of the "wallet" application in the mobile phone 100, which can effectively ensure the security of the user data.

[0157] Further, please refer to Figure 5PFor the same application in the tablet 210 and the television 220, for example, the "video" application, since the tablet 210 is a low sharing degree device, the mobile phone 100 can display the "recent search" data in the "video" application on the data synchronization management interface of the tablet 210, so that the user can perform the data synchronization management of the "recent search" data between the mobile phone 100 and the tablet 210. Since the television 220 is a high sharing degree device, the mobile phone 100 does not display the "recent search" data in the "video" application on the data synchronization management interface of the television 220, so that the user cannot perform the data synchronization management of the "recent search" data between the mobile phone 100 and the tablet 210. Thus, for the high sharing degree television 220, the mobile phone 100 does not display the "recent search" data including sensitive data (i.e., the data risk level of the "recent search" data is higher), so that the mobile phone 100 cannot synchronize the "recent search" data to the television 220, and the security of the user data can be effectively ensured even if the television 220 cannot synchronize the "recent search" data in the mobile phone 100.

[0158] Thus, the mobile phone 100 can classify data, display different data synchronization management interfaces and data synchronization management sub-interfaces for different data risk levels and different device sharing degrees of electronic devices, so that the user can perform data synchronization control by category, the synchronization needs of part of the data between the mobile phone 100 and the synchronization device 200 are realized, and the differentiated display and synchronization control of the data between the mobile phone 100 and different electronic devices can be realized. Thus, while meeting the data synchronization management needs of the user, the leakage of sensitive data can be avoided, the security of the user data can be effectively ensured, and the user experience can be improved.

[0159] Further, in some other implementations of the present application, the mobile phone 100 can also provide a display interface for the user to operate to display the device management interface in other positions by other applications, trigger controls, etc., which can be selected as needed. For example, referring to FIG. 13, after the mobile phone 100 logs in the cloud account, the mobile phone 100 can also display the display interface shown in FIG. 14, which includes a "my account" control. Figure 5Q Figure 5Q If the mobile phone 100 receives a click operation of the user on the "my account" control, the mobile phone 100 displays the display interface shown in FIG. 15, which includes a "my device" control. If the mobile phone 100 further receives a click operation of the user on the "my device" control, the mobile phone 100 displays the device management interface shown in FIG. 16. Figure 5R Figure 5E

[0160] ​​​It should be noted that when an application is used on different devices, some functions of the application can be common, but the use data of the user is generally recorded only on the device side, and the mobile phone 100 can not synchronize the use data on other devices logged in the same cloud account. Taking the television 220 as an example, the user of the television 220 can view the data synchronized to the cloud 300 by the mobile phone 100 during use of the television 220. However, there is a case that the user of the mobile phone 100 wants to view the data synchronization function of the data, and the unsynchronized data includes: data that the user refuses to synchronize in the data synchronization management sub-interface, and data that is not synchronized by default (this part of data can be the third data described above, and the synchronization of this part of data cannot be controlled by the user in the data synchronization management sub-interface). The user of the television 220 cannot view the corresponding data content, at this time, if the data synchronization setting is switched to the mobile phone 100, there is an obvious pause in the task flow. And if the user does not want to continue to keep the data synchronization, he still needs to go back to the mobile phone 100 and stop the data synchronization through the mobile phone 100. This requires the user to perform two data synchronization processes on the mobile phone 100, and the setting process is relatively cumbersome. At the same time, it may also cause the user to forget to stop the data synchronization, and the data that the user does not want to synchronize will continue to be synchronized to the electronic device that the user does not want to synchronize, which affects the user experience.

[0161] Based on this, in another implementation manner of the present application, the mobile phone 100 can also perform data synchronization management on the corresponding data for the data content that the user of the television 220 wants to view, and the implementation process will be described below.

[0162] Please refer to Figure 6A , the television 220 displays the "video" application "my collection" data display interface, and it can be seen that the synchronization of the "video" application "my collection" data is not started between the mobile phone 100 and the television 220. If the television 220 receives a click operation of the user on the "data synchronization" control (i.e., the synchronization control) in the mobile phone 100 icon, the television 220 determines that the user wants to access the "video" application "my collection" data in the mobile phone 100, and the television 220 displays the display interface shown in Figure 6B . The display interface includes a prompt information "is applying to access the video and audio data of ** account 1234567 [video-my collection]", and includes a "authorize through the mobile phone 100" control.

[0163] Please continue to refer to Figure 6B , if the television 220 receives a click operation of the user on the "authorize through the mobile phone 100" control, the television 220 sends a data synchronization request to the mobile phone 100 through the cloud 300. After receiving the data synchronization request, the mobile phone 100 displays, for example, Figure 6BThe display interface shown in the figure. The display interface includes the data synchronization prompt information "whether to allow the device to access the content of your phone 100 [video-my collection]?", and displays the "reject" control and the "allow" control. The user can choose whether to open the television 220 to synchronize the "video" application "my collection" data in the phone 100 according to the need.

[0164] Please refer to Figure 6C If the phone 100 receives the user's click operation on the "allow" control, the phone 100 opens the data synchronization access permission of the "video" application "my collection" data through the cloud 300 by the television 220, that is, opens the data synchronization of the "video" application "my collection" data between the phone 100 and the television 220, so that the television 220 can access the "video" application "my collection" data synchronized by the phone 100 to the cloud 300. And the television 220 can display Figure 6C The display interface after data synchronization shown in the figure, it can be seen that the "video" application "my collection" data in the phone 100 has been synchronized to the television 220. The user of the television 220 can view the corresponding data content by clicking the corresponding icon of the phone 100.

[0165] In the present embodiment, if the phone 100 determines that the user has clicked the "allow" control, the phone 100 determines that the user wants to permanently allow the television 220 to maintain data synchronization of the "video" application "my collection" data with the phone 100. Then, after the phone 100 determines that the user has clicked the "allow" control, the phone 100 will change the data type synchronized by the data synchronization sub-interface of the "video" application, and the display state of the "my collection" management control will change from the original stop to open. If the user does not want to synchronize the "my collection" data later, the user needs to stop the data synchronization of this type of data in the phone 100. That is, in the present embodiment, the final interaction result is that the phone 100 and the television 220 maintain the data synchronization of the "my collection" data for a long time, until the user stops the data synchronization of the "my collection" in the phone 100.

[0166] In this implementation, the mobile phone 100 can also close the data synchronization access permission of the television 220 to the "My Collection" data of the "Video" application in the mobile phone 100 when the following data synchronization stop condition is met. For example, the mobile phone 100 is pre-set with an access duration (i.e., a preset opening time of the data synchronization), which can be set to, for example, a single time, one day, three days, or different time intervals, and when the data synchronization is opened to reach the access duration, the mobile phone 100 closes the data synchronization access permission of the television 220 to the "My Collection" data of the "Video" application in the mobile phone 100. Alternatively, if the mobile phone 100 determines that the user has performed at least one operation on the "My Collection" bar of the mobile phone 100, the mobile phone 100 closes the data synchronization access permission of the television 220 to the "My Collection" data of the "Video" application in the mobile phone 100. Alternatively, if the mobile phone 100 determines that the television 220 exits the "My Collection" display interface, the mobile phone 100 closes the data synchronization access permission of the television 220 to the "My Collection" data of the "Video" application in the mobile phone 100.

[0167] Please refer to Figure 6D If the mobile phone 100 receives a click operation of the user on the "Reject" control, the mobile phone 100 does not open the data synchronization access permission of the television 220 to the "My Collection" data of the "Video" application, and the mobile phone 100 sends a notification information of rejecting the data synchronization to the television 220 through the cloud 300 to notify the television 220 that the mobile phone 100 does not open the data synchronization of the "My Collection" data of the "Video" application. After receiving the notification information, the television 220 displays a prompt information "The other device has rejected your request" as shown in Figure 6D Of course, the television 220 can also display other content or form of prompt information, which can be selected and set as needed.

[0168] Further, in order to prevent misoperation, if the mobile phone 100 receives a click operation of the user on the "Reject" control, the mobile phone 100 can also display a prompt information "Please confirm again whether to reject the access of the device to the content of your mobile phone 100 [Video-My Collection]" as shown in Figure 6E , and display a "Confirm" control and a "Cancel" control, so that the user can confirm again on the mobile phone 100. That is, if the mobile phone 100 receives a click operation of the user on the "Confirm" control, the mobile phone 100 determines not to open the data synchronization access permission of the television 220 to the "My Collection" data of the "Video" application. If the mobile phone 100 receives a click operation of the user on the "Cancel" control, the mobile phone 100 can display the display interface as shown in Figure 6D again to determine whether to open the data synchronization access permission of the television 220 to the "My Collection" data of the "Video" application.

[0169] Furthermore, in some other implementations of this application, after receiving a data synchronization request from the television 220, the mobile phone 100 may also display, as shown below. Figure 6F The display interface shown includes multiple time settings for when mobile phone 100 can enable data synchronization, i.e., the time during which TV 220 is allowed to access the "My Favorites" data in the "Video" application, allowing the user to select the appropriate time. Examples include "1 time," "24 hours," "3 days," "7 days," and "Permanent," allowing the user to choose the corresponding time as needed.

[0170] For example, if mobile phone 100 sequentially receives user clicks on "3 days" and "Allow" controls, mobile phone 100 initiates data synchronization between mobile phone 100 and TV 220 regarding the "My Favorites" data in the "Video" application. This allows TV 220 to access and synchronize data from cloud 300 with the "My Favorites" data in the "Video" application synchronized from mobile phone 100 to cloud 300. Furthermore, TV 220 can display the aforementioned... Figure 6C The displayed interface after data synchronization is shown so that users can view the corresponding data content. Furthermore, after the "3 days" period is confirmed, mobile phone 100 automatically stops data synchronization between mobile phone 100 and TV 220 for the "Video" application's "My Favorites" data, preventing TV 220 from accessing and synchronizing the "Video" application's "My Favorites" data synchronized from mobile phone 100 to cloud 300.

[0171] Furthermore, in this implementation, after mobile phone 100 automatically stops data synchronization of the "My Favorites" data in the "Video" application between mobile phone 100 and TV 220, mobile phone 100 can also display as follows: Figure 6G The displayed message "Data synchronization has stopped sharing audio and video data from [Videos - My Favorites] with TV 220" is to inform users of the relevant operation.

[0172] Furthermore, in this implementation, after mobile phone 100 automatically stops data synchronization of the "My Favorites" data in the "Video" application between mobile phone 100 and TV 220, it can also send a data synchronization stopped notification message to TV 220 via cloud 300 to notify TV 220 that mobile phone 100 has currently stopped data synchronization of the "My Favorites" data in the "Video" application. After receiving the data synchronization stopped notification message, TV 220 displays as follows: Figure 6G The displayed message "The other device has stopped sharing audio and video data in [Videos - My Favorites]" indicates that data synchronization has stopped, so that users are aware of the relevant operation.

[0173] It should be noted that in the present embodiment, the cloud 300 provides data synchronization access permission, the "my collection" display interface on the television 220 includes a "local" collection column and a "mobile phone 100" collection column, and the "mobile phone 100" collection column is the data in the mobile phone 100 synchronized from the cloud 300 to the television 220. When the television 220 opens the data synchronization access permission of the cloud 300, the "mobile phone 100" collection column displays the program data in the mobile phone 100 collected by the cloud 300 in real time or at a regular time. At this time, for the "mobile phone 100" collection column, the data is stored in the cloud 300 instead of the television 220, and the television 220 is only used as a display. After that, if the user closes the data synchronization access permission of the cloud 300 through the mobile phone 100, the "mobile phone 100" collection column on the television 220 is emptied and no longer displays the corresponding content, and the specific display is empty.

[0174] In the present embodiment, for the data type that the user does not want to keep data synchronization for a long time, when the user temporarily wants to use or synchronize, the mobile phone 100 provides temporary synchronization service through the temporary application mode of the electronic device such as the television 220, which meets the user's temporary use demand and the use intention of continuously protecting privacy. For example, for the device that does not start data synchronization, in the use situation that the user needs to access specific data, the user can apply for authorization to the mobile phone 100 through the television 220, and the mobile phone 100 automatically prompts the data authorization reminder information. The user only needs to perform the final confirmation process on the mobile phone 100, without complex data synchronization settings, which reduces the user's interactive operation burden and can effectively improve the user experience.

[0175] In addition, in the present embodiment, the mobile phone 100 can also provide an effective access time limit for data synchronization, and automatically restore the previous data synchronization state of the mobile phone 100 when the time limit expires, so as to avoid the user forgetting to stop the data synchronization authorization, meet the actual privacy protection demand of the user, and effectively improve the user experience.

[0176] In summary, in the present embodiment, a synchronization control can be set on the synchronization device 200 such as the television 220, and after receiving the operation of the user interacting with the synchronization control, the television 220 performs the specified operation and sends a temporary synchronization application to the mobile phone 100 to apply for data synchronization of the specified data type. The user can realize the data synchronization management of other electronic devices logged in the same cloud account through the mobile phone 100, and effectively improve the user experience.

[0177] Please refer to Figure 7 , and the following will be further described with the method flowchart shown in Figure 7 as an example of data synchronization management between the mobile phone 100 and the tablet computer 210.

[0178] Please refer to Figure 7 , the mobile phone 100 displays Figures 5B-5D The process of displaying the device management interface shown in any one of the figures includes the following steps:

[0179] S101, the mobile phone 100 receives a click operation of a user on the “My Device” control shown in Figure 5A , and determines a device information acquisition request. The device information acquisition request includes account information “1234567” of a cloud account to which the mobile phone 100 is currently logged in, and cloud account identification information, and includes product serial number of the mobile phone 100 and device identification information.

[0180] S102, the mobile phone 100 sends the device information acquisition request to the cloud 300.

[0181] S103, after the cloud 300 receives the device information acquisition request, the cloud 300 determines electronic devices that are currently logged in the cloud account according to the cloud account in the device information acquisition request, and determines device information of the electronic devices, which includes device type information such as device name and product serial number, and information such as whether the cloud account is logged in, whether data synchronization between the mobile phone 100 and the electronic devices is enabled, the number of times the cloud account is logged in, and whether the corresponding device icon is deleted from the device management interface. It should be noted that the device type information is, for example, the name of the device and the unique identification code such as the product serial number, and the device type information indicates the type of the device, such as a tablet computer, a television, a large-screen device, a notebook computer, etc.

[0182] In addition, the cloud 300 can also determine the device information of the aforementioned historical login electronic devices, and send the device information to the mobile phone 100.

[0183] S104, the cloud 300 sends the device information to the mobile phone 100.

[0184] S105, the mobile phone 100 receives the device information, determines the current login situation of the cloud account of each electronic device, the current data synchronization situation, and the number of times the data synchronization is logged in by the electronic device, and displays Figures 5B-5D The device management interface shown in any one of the figures.

[0185] For example, the mobile phone 100 displays the device icon of the electronic device in the data synchronization area or the data independent area according to whether the data synchronization between the mobile phone 100 and the electronic device is enabled, and determines the display mode of the device icon according to the number of times the data synchronization is logged in by the electronic device, the current login situation of the cloud account, etc.

[0186] In this way, the mobile phone 100 can conveniently display the device icon of the synchronization device 200 that is logged into the same cloud account as the mobile phone 100, so as to facilitate the user to view, and effectively improve the user experience.

[0187] The process of the user managing data synchronization through the device management interface will be described below.

[0188] Please continue to refer to Figure 7 The user managing data synchronization through the device management interface includes the following steps:

[0189] S111, the mobile phone 100 receives a click operation of the user on the device icon of the tablet computer 210 as shown in the figure, determines the application data in the mobile phone 100, or obtains the application data of the tablet computer 210 from the cloud 300. Figure 5D

[0190] S112, the mobile phone 100 determines the data synchronization management interface and the data synchronization management sub-interface according to at least one of the application data of the mobile phone 100 and / or the tablet computer 210 and the device information.

[0191] It should be noted that the mobile phone 100 is the data synchronization management center of the mobile phone 100 and all synchronization devices such as the tablet computer 210, and all synchronization devices 200 are connected with the mobile phone 100 to realize data synchronization, and the two synchronization devices 200 cannot directly synchronize data without the mobile phone 100. Therefore, in the present implementation mode, it is emphasized that the mobile phone 100 transmits synchronization data to the tablet computer 210 and other synchronization devices 200. Therefore, the data on the mobile phone 100 can be generated by the user using the mobile phone 100, or can be synchronized from other synchronization devices 200. In addition, the mobile phone 100 can obtain the application data of the tablet computer 210 through the cloud 300.

[0192] The specific process of the mobile phone 100 determining the corresponding data synchronization management interface and the data synchronization management interface and the data synchronization management sub-interface of the tablet computer 210 will be described below.

[0193] In the present implementation mode, the mobile phone 100 classifies the application data in the mobile phone 100 and / or the tablet computer 210. For example, based on the data minimization principle, the application data is granularly decomposed according to the application's home sub-menu information, the application sub-data of multiple types corresponding to the application is determined, and the data risk level of each type of application sub-data is determined.

[0194] ​For example, for the data of a certain application, the mobile phone 100 can classify the degree of influence on individuals, organizations or the public according to the legal risks caused by the leakage or damage, and the data risk level is divided into five levels: serious S4, high risk S3, medium risk S2, low risk S1 and no risk S0.

[0195] The specific classification criteria / rules refer to the following Table 1:

[0196] Table 1

[0197]

[0198]

[0199] In addition, the mobile phone 100 can also determine the device security level and device sharing degree of the tablet computer 210 according to the device information of the tablet computer 210. And electronic devices with different device security levels and device sharing degrees correspond to different data receiving levels, which can be considered as the data risk level of the data received or synchronized by the synchronization device 200 from the mobile phone 100.

[0200] The device security level can be divided as shown in the following Table 2:

[0201] Table 2

[0202]

[0203] That is, the device security level is divided into four levels SL0-SL3, wherein the data receiving level corresponding to SL0 is S0-S1, the data receiving level corresponding to SL1 is S0-S2, the data receiving level corresponding to SL3 is S0-S3, and the data receiving level corresponding to SL4 is S0-S4.

[0204] The level division of the device sharing degree can refer to the following Table 3:

[0205] Table 3

[0206]

[0207]

[0208] That is, the device sharing degree is divided into three levels: no sharing, weak sharing and strong sharing, and among the electronic devices with no sharing, the data receiving level corresponding to the electronic device with security level SL3 is S0-S4, the data receiving level corresponding to the electronic device with security level SL2 is S0-S3, and the data receiving level corresponding to the electronic device with security level SL0 is S0-S1. Among other weak sharing electronic devices and strong sharing devices, the data receiving level corresponding to the electronic device of each security level is shown in the above Table 3, which will not be expanded here.

[0209] For example, the mobile phone 100 can determine the data type of the data synchronization between the mobile phone 100 and the synchronization device 200 such as the tablet computer 210 according to the data risk level, and the device security level and the device sharing degree of the synchronization device 200 such as the tablet computer 210, which indicates the data risk level of the synchronization data that the synchronization device 200 can receive from the mobile phone 100. The synchronization device 200 such as the tablet computer 210 cannot receive the synchronization data higher than the data risk level at will. The data type within the normal data risk level range can be automatically synchronized, and for the data type higher than the data risk level that the device can receive, certain protection measures should be provided, for example, in the data synchronization management interface of the application, the application icon or data icon corresponding to the filtered high-risk data type is displayed, so that the user can perform synchronization authorization control on the filtered high-risk data type. Therefore, the synchronizable application on different devices and the data in the application will be different when the data synchronization control is performed according to the security level and the device sharing degree of the device.

[0210] For example, as shown in the foregoing Figure 5M The data synchronization management interfaces of the tablet computer 210 and the television 220 displayed by the mobile phone 100 are not the same. That is, the mobile phone 100 determines that the tablet computer 210 is a low sharing degree device, and the data receiving level is S0-S3. The mobile phone 100 determines that the television 220 is a high sharing degree device, and the data receiving level is S0-S2. Assuming that the data risk level of the wallet application belongs to S3-S4 as a whole, the mobile phone 100 can display the "wallet" application of the tablet computer 210 on the data synchronization management interface of the tablet computer 210, and does not display the "wallet" application of the television 220 on the data synchronization management interface of the television 220. That is, the television 220 as a strong sharing device cannot synchronize the data of the wallet application, so there is no synchronization setting option of the "wallet" application on the data synchronization management interface of the television 220. The tablet computer 210 belongs to a weak sharing device, and allows to synchronize part of the data of the "wallet" application, so the synchronization setting of the "wallet" application can be performed on the data synchronization management interface of the tablet computer 210.

[0211] Similarly, for the same application on different electronic devices, the data types of data synchronization are also different due to different data receiving levels of different electronic devices. For example, the data synchronization management sub-interfaces corresponding to the "video" application of the tablet computer 210 and the television 220 displayed by the mobile phone 100 are also different. That is, since the tablet computer 210 is a low sharing degree device, the mobile phone 100 can display the "recent search" data of the "video" application on the data synchronization management interface of the tablet computer 210, so that the user can perform data synchronization management on the "recent search" data. The television 220 is a high sharing degree device, and the mobile phone 100 does not display the "recent search" data of the "video" application on the data synchronization management interface of the television 220, so that the user cannot perform data synchronization management on the "recent search" data.

[0212] In the present implementation, the mobile phone 100 determines the data types of data synchronization according to the data risk level and the device sharing degree, so that the data types of data synchronization on different devices change with the change of the device sharing degree (i.e., the device attribute), thereby realizing fine-grained control of data.

[0213] In some other implementations of the present application, the mobile phone 100 can also determine the data types of synchronization according to the use scenario of the device or the use scenario of the data.

[0214] When determining the data types of synchronization according to the use scenario of the device, the device sharing degree is mainly determined. Different device sharing degrees have different corresponding data synchronization ranges, for example, the device sharing degrees of the private mobile phone 100, the tablet computer 210, and the television 220 increase in turn. For application data of the same data risk level, the user's willingness to present on devices of different device sharing degrees is also different. Some data that the user intends to present on a weak sharing device, but does not want to present on a strong sharing device. For example, for the aforementioned "play history" data, the user may intend to synchronize on the private tablet computer 210, but does not want to synchronize on the publicly used television 220. Therefore, the control options of the data types are provided, and the user can decide whether to display the play history on different devices according to personal willingness. In addition, the same application can also be provided with different types of data synchronization control on the synchronization devices of different device sharing degrees according to such user willingness. For example, the data synchronization management sub-interface corresponding to the "video" application of the television 220 does not display the management control of the "play history" data, and the synchronization sub-interface of the video application of the tablet computer displays the synchronization control option of the play history.

[0215] In addition, when determining the data type to be synchronized based on the usage context of application data, besides assessing the data risk level, it is also necessary to comprehensively consider the scenarios in which users use this type of application data on the synchronization device 200, such as the tablet 210 (e.g., the frequency of use of this type of data when operating the application). For example, the "Video" application includes several types of application sub-data such as "Video Resources (S0), My Messages (S3), Recent Searches (S3), Tag Profiles (S3), Purchase History (S2), Recently Played (S3), My Favorites (S3), My Appointments (S2), and Series Reminders (S2)". Combining this with the daily usage context of the tablet 210, three types of data synchronization mechanisms can be derived:

[0216] 1. Data with low data risk level and data in high-frequency usage scenarios (as an example of the aforementioned second type of data) are synchronized by default (e.g., video resources (S0)).

[0217] 2. Data with medium to low risk level and data in medium to low frequency of use (as an example of the aforementioned third type of data) will not be synchronized by default (e.g., in video applications, My Messages (S3), Recent Searches (S3), Tag Profiles (S3), Purchase Records (S2)).

[0218] 3. Data with high data risk level and data in high-frequency usage scenarios (as an example of the first type of data mentioned above) will be displayed in the data synchronization management sub-interface of the "Video" application, and the user can decide whether to perform data synchronization.

[0219] In actual use, the usage context of application data can be collected during user device usage and used as a label for that category of data when classifying data. The usage context of the same type of application data may differ on different electronic devices.

[0220] Furthermore, in some other implementations of this application, the mobile phone 100 determines the data synchronization mechanism for different types of data in different electronic devices based on at least one of the above-mentioned information such as data risk level, data usage scenario, device security level, device security degree, and device usage scenario. That is, it determines the data synchronization management interface and data synchronization management sub-interface displayed by the mobile phone 100 for different electronic devices, which can be specifically selected and set as needed.

[0221] In this implementation, the mobile phone 100 determines the data type to be synchronized based on the usage context of the electronic device or application data, which not only protects privacy but also reduces the amount of data to be synchronized.

[0222] It should be noted that in this implementation, the mobile phone 100 can also determine the application that has started data synchronization or the application sub-data according to the case of starting data synchronization included in the foregoing device information, and adjust the state display of the management control corresponding to the application that has started data synchronization or the application sub-data to the corresponding state, or display the number of items of the application sub-data that are started.

[0223] Further, as mentioned above, the user can manage the synchronization of the plurality of applications in the tablet computer 210 through the data synchronization management interface, please continue to refer to Figure 7 , the process in which the user manages the synchronization of the plurality of applications in the tablet computer 210 through the data synchronization management interface includes the following steps:

[0224] S121, the mobile phone 100 receives the click operation of the user on the "Sync 2 items" control corresponding to the "video" application as shown on the left, and the mobile phone 100 displays the data synchronization management sub-interface corresponding to the "video" application as shown on the right. Figure 5F Figure 5F

[0225] S122, the mobile phone 100 receives the click operation of the management control on the data synchronization management sub-interface, and determines the data synchronization management instruction. For example, if the mobile phone 100 receives the click operation of the user on the management control n2 corresponding to the "all synchronization" control, the data synchronization management instruction is a data synchronization start instruction. If the mobile phone 100 receives the click operation of the user on the management control n1 corresponding to the "my collection" data, the data synchronization management instruction is a data synchronization stop instruction.

[0226] S123, the mobile phone 100 sends the data synchronization management instruction to the cloud 300.

[0227] S124, the cloud 300 receives the data synchronization management instruction, determines the type of the data synchronization management instruction, i.e., whether the data synchronization management instruction is a data synchronization start instruction or a data synchronization stop instruction. Then, the cloud 300 manages the data synchronization access permission of the corresponding data in the tablet computer 210 to the mobile phone 100 according to the instruction type.

[0228] Further, if the data synchronization management instruction is a data synchronization stop instruction, the cloud 300 closes the data synchronization access permission of the corresponding data in the tablet computer 210 to the mobile phone 100, and can also perform step S125a. If the data synchronization management instruction is a data synchronization start instruction, the cloud 300 opens the data synchronization access permission of the corresponding data in the tablet computer 210 to the mobile phone 100, and can also perform step S126a.

[0229] S125a, the cloud 300 sends the data synchronization management instruction to the tablet computer 210. ​​

[0230] S125b, the tablet 210 stops synchronizing the "my collection" data to the cloud 300 according to the data synchronization management instruction.

[0231] S126a, the cloud 300 sends the data synchronization management instruction to the tablet 210.

[0232] S126b, the tablet 210 starts synchronizing all data of the "video" application according to the data synchronization management instruction.

[0233] S126c, the tablet 210 synchronizes all data of the "video" application to the cloud 300, so that the mobile phone 100 synchronizes all data of the "video" application from the cloud 300.

[0234] Further, if the mobile phone 100 receives the user's click operation on the management control n2 corresponding to the "gallery" application and the click operation on the management control n1 corresponding to the "photo", "collection" and "screenshot" data, the mobile phone 100, the cloud 300 and the tablet 210 perform the same or similar data synchronization management process as the foregoing steps S121-S126c, which will not be described here. Figure 5H

[0235] Please continue to see Figure 7 In some implementations of the present application, the process of the user synchronizing and managing multiple applications in the tablet 210 through data synchronization management can further include the following steps:

[0236] S131, the mobile phone 100 receives the user's click operation on the management control M1 corresponding to the "WLAN" application as shown on the left, and the mobile phone 100 displays the display interface as shown on the right, and the mobile phone 100 determines the data synchronization management instruction, which is a data synchronization start instruction. Figure 5G Figure 5G

[0237] S132, the mobile phone 100 sends the data synchronization management instruction to the cloud 300.

[0238] S133, the cloud 300 receives the data synchronization management instruction and determines the type of the data synchronization management instruction, i.e. determines that the data synchronization management instruction is a data synchronization start instruction. Then, the cloud 300 starts the data synchronization access permission of the tablet 210 to synchronize all data of the "WLAN" application in the mobile phone 100, and the cloud 300 performs step S134.

[0239] S134, the cloud 300 sends the data synchronization management instruction to the tablet 210.

[0240] ​​​S135, the tablet 210 starts data synchronization of all data of the "WLAN" application according to the data synchronization management instruction.

[0241] S136, the tablet 210 synchronizes all data of the "WLAN" application to the cloud 300, so as to facilitate other electronic devices to synchronize all data of the "WLAN" application from the cloud 300.

[0242] Further, in the present implementation, if the mobile phone 100 further receives a click operation of the user on the management control M corresponding to the "WLAN" application, the mobile phone 100 determines a data synchronization management instruction, which is a data synchronization stop instruction. The mobile phone 100, the cloud 300 and the tablet 210 perform the same or similar processing of stopping data synchronization as the foregoing steps S125-S126b, which will not be described herein again.

[0243] In this way, the mobile phone 100 can manage data synchronization of the tablet 210 according to the operation of the user on the data synchronization management interface and the data synchronization management sub-interface, which can effectively improve user experience.

[0244] Please continue to see Figure 7 In some other implementations of the present application, the process of the user synchronizing and managing multiple applications in the tablet 210 through the data synchronization management can further include the following steps:

[0245] S141, the mobile phone 100 receives a drag operation of the user on the device icon, and if the drag operation is an operation of the user dragging the tablet 210 from the data synchronization area to the data independent area as shown in FIG. 5K, the mobile phone 100 determines a data synchronization management instruction, which is a data synchronization stop instruction. If the operation is an operation of the user dragging the notebook computer 240 from the data independent area to the data synchronization area as shown in FIG. 5L, the mobile phone 100 determines a data synchronization management instruction, which is a data synchronization start instruction. Figure 5J Figure 5L

[0246] S142, the mobile phone 100 sends the data synchronization management instruction to the cloud 300.

[0247] S143, the cloud 300 receives the data synchronization management instruction, determines the type of the data synchronization management instruction, i.e., determines that the data synchronization management instruction is a data synchronization stop instruction. Then, the cloud 300 manages the data synchronization access permission of the tablet 210 to synchronize the corresponding data in the mobile phone 100 according to the data synchronization management instruction.

[0248] ​​If the data synchronization management instruction is a data synchronization stop instruction, the cloud 300 closes the data synchronization access permission of the corresponding data in the tablet 210 to the mobile phone 100, and the step S144a can also be performed. If the data synchronization management instruction is a data synchronization start instruction, the cloud 300 opens the data synchronization access permission of the corresponding data in the tablet 210 to the mobile phone 100, and the step S145a can also be performed.

[0249] S144a, the cloud 300 sends the data synchronization management instruction to the tablet 210.

[0250] S144b, the tablet 210 stops synchronizing all data in the tablet 210 to the cloud 300 according to the data synchronization management instruction.

[0251] S145a, the cloud 300 sends the data synchronization management instruction to the tablet 210.

[0252] S145b, the tablet 210 starts the data synchronization of the preset data in the tablet 210 according to the data synchronization management instruction.

[0253] S145c, the tablet 210 synchronizes the preset data to the cloud 300, so that the mobile phone 100 synchronizes the data from the cloud 300.

[0254] In this way, the mobile phone 100 can manage the data synchronization of the tablet 210 according to the operation of the user on the data synchronization management interface, and the user experience can be effectively improved.

[0255] In some implementations of the present application, the mobile phone 100 can also perform data synchronization management on the corresponding data according to the data content that the user of the television 220 wants to view, and the implementation process will be described below.

[0256] Please refer to Figure 8 , the mobile phone 100 performs data synchronization management on the corresponding data according to the data content that the user of the television 220 wants to view, including the following process:

[0257] S201, the television 220 receives the click operation of the user on the "authorized by the mobile phone 100" control shown in the foregoing Figure 6B , determines a data synchronization request, and the data synchronization request includes the identification information of the application data requested to be accessed by the user.

[0258] S202, the television 220 sends the data synchronization request to the cloud 300.

[0259] S203, the cloud 300 receives the data synchronization request and sends the data synchronization request to the mobile phone 100.

[0260] S204, the mobile phone 100 receives the data synchronization request, displays the open data synchronization prompt information as shown in Figure 6B , and the "reject" control and the "allow" control.

[0261] S205, if the mobile phone 100 receives the user's click operation on the "allow" control as shown in Figure 6C , the mobile phone 100 determines to open the data synchronization of the "my collection" data of the "video" application between the mobile phone 100 and the television 220, and executes step S206. If the mobile phone 100 receives the user's click operation on the "reject" control as shown in Figure 6D , the mobile phone 100 determines to reject the data synchronization notification information, and executes step S210.

[0262] S206, the mobile phone 100 sends the data synchronization open instruction of allowing the television 220 to synchronize the "my collection" data to the cloud 300.

[0263] S207, the cloud 300 opens the data synchronization access permission of the television 220 to synchronize the "my collection" data of the mobile phone 100 on the cloud 300 according to the data synchronization open instruction, that is, allows the television 220 to access the "my collection" data.

[0264] S208, the cloud 300 synchronizes the "my collection" data to the television 220.

[0265] S209, the television 220 receives the "my collection" data, and displays the display interface as shown in Figure 6C .

[0266] S210, the mobile phone 100 sends the data synchronization rejection notification information to the cloud 300.

[0267] S211, the cloud 300 receives the notification information, and sends the notification information to the television 220.

[0268] S212, the television 220 displays the prompt information as shown in Figure 6D .

[0269] After the mobile phone 100 executes step S206, the mobile phone 100 can further execute steps S213 and S214:

[0270] S213, after the mobile phone 100 determines that the synchronization time (for example, "3 days") of opening the data synchronization arrives, the mobile phone 100 automatically determines to stop the data synchronization of the "my collection" data of the "video" application between the mobile phone 100 and the television 220, and displays the data synchronization stop prompt information as shown in Figure 6G .

[0271] S214, the mobile phone 100 sends the data synchronization stop prompt information to the cloud 300.

[0272] S215, the cloud 300 receives the data synchronization has stopped prompt information, and closes the data synchronization access permission of the tablet 210 to the "my collection" data in the mobile phone 100 according to the data synchronization has stopped prompt information.

[0273] Further, the cloud 300 can also send the data synchronization has stopped prompt information to the television 220, so that the television 220 displays the data synchronization has stopped prompt information as shown in Figure 6G

[0274] In this way, the mobile phone 100 can conveniently realize the data synchronization management between the mobile phone 100 and the television 220, and the user experience can be effectively improved.

[0275] It should be noted that, in an implementation manner of the present application, for the synchronization control of the synchronization device 200, the synchronization device 200 can use a traditional control manner, as long as the data synchronization function of the synchronization device 200 is turned on, and the corresponding application synchronization is turned on, the mobile phone 100 can perform the data synchronization of the application according to the synchronization preference setting of the mobile phone 100 through the cloud 300.

[0276] In another implementation manner of the present application, the synchronization device 200 can only provide the start / stop data synchronization function, and temporarily does not perform the synchronization setting of the data category of the application, so as to simplify the task flow of the initial setting. After the data synchronization is started, the mobile phone 100 can perform the data synchronization of the application according to the synchronization preference setting of the mobile phone 100 through the cloud 300.

[0277] In another implementation manner of the present application, the synchronization device 200 can only open part of the functions to the user for setting, and the other functions need to be selected by the user. That is, the synchronization device 200 can send a data synchronization request to the user, and if the mobile phone 100 detects the confirmation operation of the user, the corresponding synchronization processing is started.

[0278] The above two manners are mainly based on the data synchronization preference setting of the mobile phone 100. For the first manner, the synchronization device 200 (non-main device) can select to receive / reject the synchronization at the device level and the application level. The second manner can only receive the setting manner of the mobile phone 100 (main device), and has stronger control on the synchronization device 200 (non-main device).

[0279] In summary, the data synchronization management method provided by the present application is a method for realizing the data synchronization between different devices, and please refer to Figure 9 The method comprises the following steps:

[0280] S301, a user operates a first electronic device as a main device to display a device management interface; ​

[0281] S302, receiving an operation of selecting a second electronic device to be managed by a user on a device management interface, displaying a data synchronization management interface of the selected second electronic device;

[0282] S303, receiving an operation of the user on the data synchronization management interface, and performing a synchronization data management process.

[0283] The device management interface and the data synchronization management interface displayed by the first electronic device, and the operation of selecting a second electronic device to be managed by the user on the device management interface, the operation of the user on the data synchronization management interface, etc. can be as described above, and will not be repeated here.

[0284] It should be noted that the foregoing mobile phone 100 is an example of the first electronic device, and in other implementations of the present application, the first electronic device can also be a tablet computer or other non-public device.

[0285] The foregoing synchronization device 200 such as the tablet computer 210, the television 220, the large-screen device 230, and the notebook computer 240 is an example of the second electronic device. In other implementations of the present application, the second electronic device can also be a sound box, a vehicle-mounted device, or other public device.

[0286] The foregoing cloud account is an example of a same preset account used by the first electronic device and the second electronic device. In other implementations of the present application, the preset account can also be a system account based on a same development system, or other types of accounts, which can be selected and set as needed.

[0287] The foregoing device icon is an example of identification information of the electronic device. In other implementations of the present application, the identification information of the electronic device can also be other text, graphics, or other forms of content, which can be selected and set as needed.

[0288] The foregoing application icon is an example of identification information of the application. In other implementations of the present application, the identification information of the application can also be other text, graphics, or other forms of content, which can be selected and set as needed.

[0289] The foregoing data icon is an example of identification information of the application sub-data. In other implementations of the present application, the identification information of the application sub-data can also be other text, graphics, or other forms of content, which can be selected and set as needed.

[0290] The aforementioned management control M1, management control M2 and management control M3 are as an example of the first management control, the management control n1 is as an example of the second management control, and the management control n2 is as an example of the third management control. In other implementations of the present application, the first management control, the second management control and the third management control can also be other forms of controls, which can all be selected and set as needed.

[0291] The aforementioned clicking operation of the "My Device" control by the user is as an example of the first operation of the user. The aforementioned clicking operation of the device icon by the user is as an example of the second operation of the user. The aforementioned clicking operation of the management control M1, management control M2 and management control M3 by the user is as an example of the third operation of the user. The aforementioned clicking operation of the management control n1 by the user is as an example of the fourth operation of the user. The aforementioned clicking operation of the management control n2 by the user is as an example of the fifth operation of the user. The aforementioned dragging operation of the device icon by the user is as an example of the sixth operation of the user. The aforementioned clicking operation of the "OK" control by the user is as an example of the seventh operation of the user. The aforementioned clicking operation of the "Cancel" control by the user is as an example of the eighth operation of the user. The aforementioned long-pressing operation of the device icon by the user is as an example of the ninth operation of the user. The aforementioned clicking operation of the "Delete" control by the user is as an example of the tenth operation of the user. The aforementioned clicking operation of the "Allow" control by the user is as an example of the eleventh operation of the user. The aforementioned clicking operation of the "Deny" control by the user is as an example of the twelfth operation of the user. The aforementioned clicking operation of the "OK" control by the user is as an example of the thirteenth operation of the user. Figure 5A Figure 5D Figure 5E Figure 5F 5H Figure 5F 5H Figures 5J to 5L Figure 5K Figure 5K Figure 5N Figure 5N Figure 6C Figure 6D Figure 6E

[0292] ​​​​​​​​​​​​​​​In other implementations of this application, the aforementioned user click operation on the device icon can be a single click, a double click, or a long press or other operation; the aforementioned user drag operation on the device icon can be a triple click or other touch operation; and the aforementioned user long press operation on the device icon can be a knuckle tap or other touch operation. Furthermore, the aforementioned user click operations on each control can be single clicks, double clicks, or other touch operations, all of which can be selected and set as needed.

[0293] Of course, in other implementations of this application, the aforementioned user touch operation can also be a gesture-triggered operation, a voice-triggered operation, an iris-triggered operation, or other trigger operations, which can be selected and set as needed.

[0294] The aforementioned "WLAN" application, "Calendar" application, "Contacts" application, and "Memo" application are some examples of the first type of application. In other implementations of this application, the first type of application can also be selected or set as other types of applications as needed.

[0295] The aforementioned "Gallery" application, "Browser" application, "Music" application, and "Wallet" application are some examples of the second type of application. In other implementations of this application, the second type of application can also be selected or set as other types of applications as needed.

[0296] The foregoing Figure 5K The displayed stop data synchronization notification message is an example of such a message. Figure 6B , Figure 6C and Figure 6D The displayed data synchronization notification message is an example of what is meant to be a notification message for enabling data synchronization. Figure 6E The data synchronization rejection reminder displayed on mobile phone 100 is an example of a data synchronization rejection reminder message, and the reminder message displayed on TV 220 is an example of a data synchronization rejection notification message. Figure 6G The data synchronization stopped notification message shown is one example of such a notification message. In other implementations of this application, these notification messages and information can also be set to other displays or content as needed and optional.

[0297] The aforementioned user actions on the "Mobile 100" favorites bar serve as examples of some preset actions for users to request corresponding data for data synchronization. These preset actions can also be other actions that users can perform on the data, which can be selected and set as needed.

[0298] The data synchronization management interface is an example of the first data synchronization management interface, and the data synchronization management sub-interface is an example of the second data synchronization management interface. In other implementations of the present application, the data synchronization management interface and the data synchronization management sub-interface can also be selected or set as other display forms as needed.

[0299] In other implementations of the present application, the device management interface can also be selected or set as other display forms as needed.

[0300] In other implementations of the present application, the phone 100 can also not synchronize all data in the phone 100 to the cloud 300. If the phone 100 determines that the data of an application or the sub-data of an application needs to be synchronized to the synchronization device 200, the phone 100 opens the data synchronization of the corresponding data, synchronizes the data to the cloud 300, and opens the data synchronization access permission of the synchronization device 200 to access the data, so that the synchronization device 200 can synchronize the data from the cloud 300.

[0301] For example, in the implementation of the present application, the device management interface simultaneously displays the device icon of the phone 100. In other implementations of the present application, the user can also manage the data synchronization of the phone 100 through the device management interface to achieve the same or similar process of managing the data synchronization of the tablet computer 210. Details are not described herein.

[0302] That is, in the implementation of the present application, the user can not only manage the data synchronization of the phone 100 itself through the phone 100, but also manage the data synchronization of other electronic devices using the same cloud account as the phone 100. In the process of synchronizing data among multiple electronic devices, the user only needs to operate on the phone 100 to uniformly manage and view the data synchronization of multiple electronic devices, which simplifies the user's data synchronization management operation and effectively improves the user experience.

[0303] Please refer to Figure 10 , Figure 10A structural diagram of an electronic device 900 is shown in accordance with an implementation of the present application. The electronic device 900 can include one or more processors 901 coupled to a controller hub 904. For at least one embodiment, the controller hub 904 communicates with the processor(s) 901 via a multi -branch bus, such as a Front Side Bus (FSB), a point-to-point interface such as QuickPath Interconnect (QPI), or similar connection. The processor(s) 901 execute instructions to perform data processing operations of a general type. In one embodiment, the controller hub 904 includes, but is not limited to, a Graphics Memory Controller Hub (GMCH) (not shown in diagram) that includes memory and graphics controllers, and an Input / Output Hub (IOH) (which can be on a separate chip) (not shown in diagram).

[0304] The electronic device 900 can also include a coprocessor 906 and a memory 902 coupled to the controller hub 904. Alternatively, one or both of the memory 902 and the GMCH can be integrated within the processor 901 (as described in the present application), the memory 902 and the coprocessor 906 are directly coupled to the processor 901 and the controller hub 904, with the controller hub 904 in a single chip with the IOH.

[0305] The memory 902 can be, for example, a Dynamic Random Access Memory (DRAM), a Phase Change Memory (PCM), or a combination of both.

[0306] In one embodiment, the coprocessor 906 is a special-purpose processor, such as, for example, a high-throughput Many Integrated Core (MIC) processor, a network or communication processor, compression engine, a Figure 10 co-processor 906 is shown in dashed lined in

[0307] In one embodiment, the electronic device 900 can further include a network interface (NIC) 903. The network interface 903 can include a transceiver to provide a radio interface for the electronic device 900 to communicate with any other suitable device (e.g., a front-end module, an antenna, etc.). In various embodiments, the network interface 903 can be integrated with other components of the electronic device 900. The network interface 903 can implement the functionality of the communication unit in the above-described embodiments.

[0308] The electronic device 900 can further include input / output (I / O) devices 905. The input / output (I / O) devices 905 can include a user interface designed to enable a user to interact with the electronic device 900, a peripheral component interface designed to enable a peripheral component to also interact with the electronic device 900, and / or a sensor designed to determine environmental conditions and / or location information related to the electronic device 900.

[0309] Notably, Figure 10 are merely exemplary. That is, although Figure 10 Although the electronic device 900 is shown in FIG. 10 to include a processor 901, a controller hub 904, a memory 902, and so on, in actual applications, a device using the methods of the present application can include only a portion of the components of the electronic device 900, e.g., only the processor 901 and the NIC 903. Figure 10 The optional nature of the components of the electronic device 900 is denoted in FIG. 10 by the dashed lines.

[0310] The memory of the electronic device 900 can include one or more tangible, non-transitory computer-readable media for storage of data and / or instructions. The computer-readable storage media can store instructions, specifically, transient and permanent copies of the instructions.

[0311] In the present application, the electronic device 900 can be specifically a terminal device such as a mobile phone, a tablet computer, a personal digital assistant (PDA), or a desktop computer. The instructions stored in the memory of the electronic device can include instructions that, when executed by at least one unit of the processor, cause the electronic device to implement the data synchronization management method as mentioned above.

[0312] See Figure 11 , Figure 11 FIG. 11 shows a structure diagram of a SoC (System on Chip) 1000 according to an implementation of the present application. In Figure 11In the following description, like-named components have like reference numbers. Additionally, the SoC 1000 can be used in any of the electronic devices described in accordance with the present disclosure, and can implement corresponding functionality depending on the device in which it is embodied and the instructions it is instructed to execute.

[0313] In Figure 11 In the following description, like-named components have like reference numbers. Additionally, the SoC 1000 can be used in any of the electronic devices described in accordance with the present disclosure, and can implement corresponding functionality depending on the device in which it is embodied and the instructions it is instructed to execute.

[0314] The SRAM unit 1008 can include one or more computer-readable media for storage of data and / or instructions, for example. The computer-readable storage medium can store instructions which, when executed by the processor 1001, cause the electronic device to perform the data synchronization management method as mentioned above.

[0315] It should be noted that the terms "first", "second", and so on are merely used to distinguish different descriptions, and cannot be understood as indicating or implying relative importance.

[0316] It should be noted that in the drawings, some structural or method features can be shown in a particular arrangement and / or order. However, it should be understood that such a particular arrangement and / or order can not be required. Rather, in some embodiments, the features can be arranged in a different manner and / or order than shown in the illustrative figures. Additionally, the inclusion of a structural or method feature in a particular figure is not meant to imply that such a feature is needed in all embodiments, and in some embodiments, the feature can not be included or can be combined with other features in a combination.

[0317] While the application has been illustrated and described in connection with certain preferred implementations thereof, it will be readily apparent to those of ordinary skill in the art that changes and modifications in the illustrated implementation can be made without departing from the spirit and scope of the application. It is intended in the following claims to cover all such changes and modifications that fall within the spirit and scope of the application.

Claims

1. A data synchronization management method, applied to a first electronic device, characterized in that, The method includes: Receive the user's first action; In response to the first operation, a device management interface is displayed, which includes identification information of at least one second electronic device, which is an electronic device that uses the same preset account as the first electronic device. A second operation to receive the user's identification information for the second electronic device; In response to the second operation, a first data synchronization management interface corresponding to the second electronic device is displayed. The first data synchronization management interface includes identification information of at least one application in the second electronic device, and a first management control corresponding to the identification information of the application. The at least one application is related to the security level and device sharing degree of the second electronic device. Receive a third operation from the user on the first management control; If the application is a first type of application, then in response to the third operation, a data synchronization management process is performed, the data synchronization management process corresponding to all data of the application.

2. The data synchronization management method according to claim 1, characterized in that, If the application is a second type of application, then the method includes: In response to the third operation, a second data synchronization management interface corresponding to the application is displayed. The second data synchronization management interface includes identification information of at least one type of application sub-data corresponding to the application, and a second management control corresponding to the identification information of the application sub-data. Receive the user's fourth operation on the second management control; In response to the fourth operation, a data synchronization management process is performed, the data synchronization management process corresponding to the application sub-data corresponding to the second management control.

3. The data synchronization management method according to claim 2, characterized in that, The second data synchronization management interface also includes a third management control corresponding to the application, then the method further includes: Receive the user's fifth operation on the third management control; In response to the fifth operation, a data synchronization management process is performed, which corresponds to all the application sub-data included in the second data synchronization management interface.

4. The data synchronization management method according to claim 1, characterized in that, The data synchronization management process includes enabling data synchronization between the first electronic device and the second electronic device, or stopping data synchronization between the first electronic device and the second electronic device.

5. The data synchronization management method according to claim 1, characterized in that, The device management interface further includes a data synchronization area and a data independence area. The data synchronization area is used to display the identification information of electronic devices that are currently logged into the preset account and have synchronized data with the first electronic device. The data independence area is used to display the identification information of electronic devices that are not currently synchronized data with the first electronic device. The method further includes displaying the identification information of the second electronic device in the data synchronization area or the data independence area based on at least one of the following: Whether the second electronic device is currently logged into the preset account; Information on the number of times the second electronic device has logged into the preset account; Information on whether the second electronic device is currently synchronizing data with the first electronic device; Whether the identification information of the second electronic device has been deleted from the device management interface.

6. The data synchronization management method according to claim 5, characterized in that, The method further includes: The sixth operation is to receive the user's identification information for the second electronic device; If the sixth operation is to move the identification information of the second electronic device from the data synchronization area to the data independent area, then in response to the sixth operation, the data synchronization between the first electronic device and the second electronic device is stopped. If the sixth operation is to move the identification information of the second electronic device from the data independent area to the data synchronization area, then in response to the sixth operation, data synchronization of preset data between the first electronic device and the second electronic device is started, or the first data synchronization management interface corresponding to the second electronic device is displayed.

7. The data synchronization management method according to claim 6, characterized in that, If the sixth operation is to move the identification information of the second electronic device from the data synchronization area to the data independent area, the method further includes: in response to the sixth operation, displaying a stop data synchronization reminder message; Then stop the data synchronization between the first electronic device and the second electronic device, including: The seventh operation is to receive the user's notification message for stopping data synchronization. In response to the seventh operation, data synchronization between the first electronic device and the second electronic device is stopped.

8. The data synchronization management method according to claim 7, characterized in that, The method further includes: The eighth operation received by the user in response to the stop data synchronization reminder message; In response to the eighth operation, the identification information of the second electronic device is displayed in the data synchronization area.

9. The data synchronization management method according to claim 1, characterized in that, The method further includes: The ninth operation is to receive the user's identification information for the second electronic device; In response to the ninth operation, the identification information of the second electronic device is deleted from the first data synchronization management interface; or In response to the ninth operation, the delete control is displayed; Receive the user's tenth operation corresponding to the delete control; In response to the tenth operation, the identification information of the second electronic device is deleted from the first data synchronization management interface.

10. The data synchronization management method according to claim 9, characterized in that, The method further includes: In response to the ninth or tenth operation, data synchronization between the first electronic device and the second electronic device is stopped.

11. The data synchronization management method according to claim 1, characterized in that, The method further includes: Receive a data synchronization request sent by the second electronic device; In response to the data synchronization request, a reminder message to enable data synchronization is displayed; Receive the eleventh operation from the user corresponding to the activation of the data synchronization reminder message; In response to the eleventh operation, data synchronization of the corresponding data in the data synchronization request is initiated between the first electronic device and the second electronic device.

12. The data synchronization management method according to claim 11, characterized in that, The method further includes: If the preset data synchronization stop condition is met, then the data synchronization between the first electronic device and the second electronic device, and the corresponding data of the data synchronization request, is stopped.

13. The data synchronization management method according to claim 12, characterized in that, The data synchronization stop condition includes any one of the following: Data synchronization is initiated at the preset start time. The system receives a preset operation for the data corresponding to the user's data synchronization request.

14. The data synchronization management method according to claim 12, characterized in that, The method further includes: Display a notification message indicating that data synchronization has stopped; and / or Send a notification message that data synchronization has stopped to the second electronic device, so that the second electronic device displays the notification message.

15. The data synchronization management method according to claim 11, characterized in that, The method further includes: Receive the twelfth operation from the user corresponding to the data synchronization reminder message; In response to the twelfth operation, a notification message of refusal to synchronize data is sent to the second electronic device; or In response to the twelfth operation, a data synchronization rejection reminder message is displayed; The thirteenth operation received by the user in response to the data synchronization rejection reminder message; In response to the thirteenth operation, a notification message of refusal to synchronize data is sent to the second electronic device.

16. The data synchronization management method according to claim 1, characterized in that, The method further includes: The display status of the management control is determined based on the information that data synchronization between the first electronic device and the second electronic device is turned on or off.

17. The data synchronization management method according to any one of claims 1-16, characterized in that, The method further includes determining a data synchronization management interface based on at least one of the following information, wherein the data synchronization management interface includes a first data synchronization management interface and a second data synchronization management interface: Application data of the applications installed in the first electronic device; Application data of the applications installed in the second electronic device; Device information of the second electronic device.

18. The data synchronization management method according to claim 17, characterized in that, The data synchronization management interface is determined based on the application data and the device information, including: The application data is classified, and the data risk level and data usage scenario of each type of application data are determined. The device security level, device sharing degree and device usage scenario of the second electronic device are determined based on the device information. Based on at least one of the following information: data risk level, data usage scenario, device security level, device sharing degree, and device usage scenario, a first data in the application data is determined, wherein the first data is the data in the application data used by the user for data synchronization management. The data synchronization management interface is shown based on the first data display.

19. The data synchronization management method according to claim 18, characterized in that, The method further includes: Based on at least one of the following information: data risk level, data usage scenario, device security level, device sharing degree, and device usage scenario, determine the second data and the third data in the application data. The second data is the data in the application data for which data synchronization is enabled by default, and the third data is the data in the application data for which data synchronization is not enabled by default. Enable data synchronization between the first electronic device and the second electronic device for the second data; Data synchronization of the third data is not enabled between the first electronic device and the second electronic device; and The identification information of the application corresponding to the second data and the third data, or the identification information of the application sub-data, will not be displayed in the data synchronization management interface.

20. The data synchronization management method according to claim 4, characterized in that, Enabling data synchronization between the first electronic device and the second electronic device includes: sending a data synchronization enable command to the cloud, so that the cloud enables data synchronization access permissions for the second electronic device to synchronize data with the first electronic device through the cloud, according to the data synchronization enable command; Stopping data synchronization between the first electronic device and the second electronic device includes: sending a data synchronization stop instruction to the cloud, so that the cloud, according to the data synchronization stop instruction, closes the data synchronization access permission of the second electronic device to synchronize data with the first electronic device through the cloud.

21. A data synchronization management system, characterized in that, It includes a first electronic device and at least one second electronic device, wherein, The first electronic device is used to receive a first operation from the user; In response to the first operation, a device management interface is displayed, which includes identification information of at least one second electronic device, which is an electronic device that uses the same preset account as the first electronic device. A second operation to receive the user's identification information for the second electronic device; In response to the second operation, a first data synchronization management interface corresponding to the second electronic device is displayed. The first data synchronization management interface includes identification information of at least one application in the second electronic device, and a first management control corresponding to the identification information of the application. The at least one application is related to the security level and device sharing degree of the second electronic device. Receive a third operation from the user on the first management control; If the application is a first type of application, then in response to the third operation, a data synchronization management process is performed, the data synchronization management process corresponding to all data of the application; The second electronic device is used to perform data processing corresponding to the data synchronization management process.

22. The data synchronization management system according to claim 21, characterized in that, If the application is a second type of application. The first electronic device is further configured to respond to the third operation by displaying a second data synchronization management interface corresponding to the application. The second data synchronization management interface includes identification information of at least one type of application sub-data corresponding to the application, and a second management control corresponding to the identification information of the application sub-data. as well as Receive the user's fourth operation on the second management control; In response to the fourth operation, a data synchronization management process is performed, the data synchronization management process corresponding to the application sub-data corresponding to the second management control; The second electronic device is used to perform data processing corresponding to the data synchronization management process.

23. The data synchronization management system according to claim 21 or 22, characterized in that, It also includes a cloud, which is used to store data synchronized from the first electronic device and the second electronic device, and to perform data synchronization access permission processing corresponding to the data synchronization management processing.

24. An electronic device, characterized in that, include: A memory for storing computer programs, the computer programs including program instructions; A processor is configured to execute the program instructions to cause the electronic device to perform the data synchronization management method according to any one of claims 1-20.

25. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, the computer program including program instructions, which are executed by the electronic device to cause the electronic device to perform the data synchronization management method according to any one of claims 1-20.

Citation Information

Patent Citations

  • Data synchronization method, client end, server, terminal and system

    CN103873519A

  • Application synchornization

    CN105940397A