Device data migration method, electronic device, and system

Abstract

The present application relates to the technical field of terminals, and discloses a device data migration method, an electronic device, and a system, which can achieve convenient and accurate migration of personalized data related to user usage habits and / or preferences in one device to another device, thereby improving user experience. In the present application, an electronic device may decouple a plurality of setting items that are on a shortcut entry interface and used for representing a usage habit and / or a preference of a user, so that the setting items are not associated with each other in terms of a relative location relationship. Finally, after personalized data representing a setting item layout habit and / or preference when the user uses the shortcut entry interface is migrated to the second device, the second device can maintain consistency with the first device to the greatest extent when the shortcut entry interface is laid out, thereby maintaining the usage habit of the user.

Description

Data migration methods for devices, electronic devices and systems

[0001] This application claims priority to Chinese patent application filed on June 19, 2024, with application number 202410798047.0 and entitled "Data Migration Method, Electronic Device and System of Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of terminal technology, and in particular to a data migration method, electronic device and system for a device. Background Technology

[0003] With the rapid pace of technological advancements in mobile phones, tablets, and other electronic devices, and the consumer preference for user-centric experiences, users frequently upgrade their devices. When upgrading, users typically need to migrate data from their old devices to the new ones. To provide a more convenient upgrade experience, electronic devices now offer automatic data migration services. For example, electronic devices can automatically migrate data from old devices to new devices through cross-device transfer methods (such as phone cloning) or cloud synchronization.

[0004] However, current automatic data migration between devices only targets application data such as contacts, text messages, photos, and videos stored on older devices. This alone cannot provide users with a sufficiently good experience when switching to a new device. For example, each user has their own unique usage habits and / or preferences when using electronic devices, such as which shortcuts they prefer, where those shortcuts are located, and which functions or permissions they need to enable. Existing automatic data migration technology cannot migrate this kind of personalized data from old devices to new devices. Summary of the Invention

[0005] This application provides a data migration method, electronic device, and system for devices, which can conveniently and accurately migrate personalized data about user habits and / or preferences from one device to another, thereby improving the user experience.

[0006] To achieve the above objectives, this application adopts the following technical solution:

[0007] Firstly, a data migration method for a device is provided. This method can be applied to an electronic device, such as a first device. The method includes: in response to a data migration request, the first device acquires personalized data of a user, wherein the personalized data represents the layout positions of multiple settings items on a first interface of the first device; the first device sends personalized data to a second device, wherein the personalized data is used by the second device to lay out the corresponding settings items on a second interface. The solution provided in the first aspect allows the first device to decouple multiple settings items on the first interface that represent user habits and / or preferences, making them independent in relative position. Ultimately, after migrating personalized data representing user layout habits and / or preferences when using the first interface, such as layout parameters of the first interface, to the second device, the second device can maintain maximum consistency with the first interface when laying out the second interface related to the first interface, such as ensuring that each setting item maintains the same layout position as the first interface, preserving user habits, and improving user experience.

[0008] As one possible implementation, the layout positions of the aforementioned settings items are represented by row and column numbers. These layout positions are used to place the same settings items in corresponding positions on the second device's second interface. In this way, after personalized data is migrated to the second device, the row and column numbers of each setting item on the second device's second interface remain consistent with the corresponding settings items on the first interface, preserving user habits and improving user experience.

[0009] As one possible implementation, the method further includes: in response to a data migration request, the first device obtains an interface layout strategy; the first device sends the interface layout strategy to the second device, the interface layout strategy being used by the second device to perform corresponding processing based on the interface layout strategy when encountering preset situations. Thus, it can be used as a reference for the second device when handling special situations, improving the flexibility of the second device in performing interface layout based on personalized data.

[0010] As an example, the above-mentioned preset situation includes: the second device does not support the first setting among the above multiple settings.

[0011] As an example, the reason why the second device does not support the first setting item includes at least one of the following: the hardware of the second device does not support the function corresponding to the first setting item; the identifier of the first setting item in the first device is inconsistent with the identifier of the setting item with the same function in the second device; or the function corresponding to the first setting item has not been authorized by the user in the second device.

[0012] As one possible implementation, the aforementioned interface layout strategy includes a first strategy or a second strategy. The first strategy instructs the second device to reserve the position corresponding to the layout position of the first setting item on the second interface. The second strategy instructs the second device to place the second setting item at the position corresponding to the layout position of the first setting item on the second interface. The second setting item does not belong to multiple setting items. In this way, different handling strategies for special cases can be supported by the second device, flexibly meeting the diverse preferences and needs of users.

[0013] As one possible implementation, the second setting could be the setting most frequently used by the user within a preset time period while using the first device; or, the second setting could be the setting most recently used by the user while using the first device; or, the second setting could be a setting supported by the second device but not included in multiple other settings. This would, on the one hand, ensure a seamless second interface on the second device, resulting in a more cohesive and aesthetically pleasing design; on the other hand, it could improve the user experience. For example, if the second setting is a recently used or most frequently used switch, its placement would facilitate future use. Similarly, if the second setting is a new feature added to the second device compared to the first device, its placement would make it easier for the user to access or discover the new functionality, thus enhancing the user experience.

[0014] As one possible implementation, the aforementioned first interface is a control center interface, and the multiple settings items include any one or more of the following: cellular switch, airplane mode switch, eye protection mode switch, do not disturb switch, silent switch, flashlight switch, auto-rotate switch, mobile data switch, Wi-Fi switch, Bluetooth switch, and HyperTerminal switch. This allows the second device to maintain, to the greatest extent possible, consistency with the control center interface layout on the first device after personalized data is migrated to the second device, preserving user habits.

[0015] As one possible implementation, the second interface described above is a control center interface. This allows the second device to maintain, to the greatest extent possible, the layout of its control center interface to match that of the first device after the personalized data has been migrated, thus preserving the user's habits.

[0016] As one possible implementation, the first device acquires the user's personalized data by: generating personalized data based on the layout of multiple settings items on the first interface; or automatically generating personalized data based on the user's custom settings operations on the settings items on the first interface. Thus, the first device can acquire the user's personalized data in multiple different ways, improving the flexibility of the solution.

[0017] As one possible implementation, the aforementioned data migration request is a request to migrate data from a first device to a second device in a device replacement scenario (also known as a device cloning scenario). In this way, personalized data regarding the user's settings layout habits and / or preferences when using the first interface can be conveniently and accurately migrated from the old device to the new device with reduced user operations, fully preserving the user's usage habits and / or preferences on the new device.

[0018] As an example, the first device is the old device in the replacement scenario, and the second device is the new device in the replacement scenario.

[0019] As one possible implementation, the above method also includes: the first device responding to the data migration request by sending application data to the second device. In this way, in a device upgrade scenario, application data such as contacts, SMS messages, photos, and videos from the old device can be automatically migrated to the new device, providing users with a convenient device upgrade experience.

[0020] As one possible implementation, the first device sends personalized data to the second device, including: the first device sending personalized data directly to the second device; or the first device sending personalized data to the second device through a cloud server. This allows for the migration of personalized data across different architectures and based on different data migration methods, such as cross-device transmission or cloud synchronization, improving the compatibility and applicability of the solution.

[0021] Secondly, a data migration method is provided, which can be applied to electronic devices, such as a second device. The method includes: the second device receiving personalized data from a user of a first device, wherein the personalized data represents the layout positions of multiple settings items on a first interface of the first device; and the second device arranging the settings items on a second interface of the second device according to the personalized data.

[0022] The solution provided in the second aspect above allows the first device to decouple multiple settings on the first interface that characterize user habits and / or preferences, making them independent in relative position. Ultimately, after migrating data characterizing user layout habits and / or preferences when using the first interface, such as personalized data including layout parameters of the first interface, to the second device, the second device can maintain consistency with the first interface to the greatest extent when laying out the second interface related to the first interface. For example, it can ensure that each setting item maintains the same layout position as the first interface, thus preserving user habits and improving user experience.

[0023] As one possible implementation, the layout positions of the aforementioned multiple settings items are represented by row and column numbers. The second device lays out the settings items on its second interface based on the personalized data, including: the second device lays out at least one of the multiple settings items at the corresponding positions on the second interface based on the personalized data. In this way, after the personalized data is migrated to the second device, the row and column numbers of each setting item on the second interface of the second device remain consistent with the corresponding settings items on the first interface, maintaining user habits and improving user experience.

[0024] As one possible implementation, the second device supports the aforementioned multiple settings items. The second device arranges at least one of the multiple settings items at corresponding positions on the second interface based on personalized data. This includes: the second device arranging multiple settings items at corresponding positions on the second interface based on personalized data. In this way, the layout of each setting item on the second interface of the second device remains consistent with the corresponding setting item on the first interface, maintaining user habits and improving user experience.

[0025] As one possible implementation, the method further includes: the second device receiving an interface layout strategy from the first device, the interface layout strategy being used by the second device to perform corresponding processing based on the interface layout strategy when encountering a preset situation; and the second device, when laying out settings on its second interface according to personalized data, performing corresponding processing based on the interface layout strategy if a preset situation is encountered. This can be used as a reference for the second device when handling special situations, improving the flexibility of the second device in performing interface layout based on personalized data.

[0026] As one possible implementation, the aforementioned preset scenarios include: the second device does not support the first setting among the multiple settings, and the aforementioned interface layout strategy is the first strategy; the second device lays out the settings on its second interface based on personalized data, including: the second device lays out the other settings besides the first setting at corresponding positions on the second interface based on personalized data; the second device reserves the position corresponding to the layout of the first setting on the second interface as a reserved position according to the first strategy. This not only ensures that the layout positions of each setting on the second interface of the second device are consistent with the corresponding settings on the first interface, preserving user habits, but also improves the flexibility of the second device's interface layout based on personalized data.

[0027] As one possible implementation, the aforementioned preset scenarios include: the second device does not support the first setting among multiple settings, and the aforementioned interface layout strategy is the second strategy; the second device lays out the settings on its second interface based on personalized data, including: the second device lays out the other settings besides the first setting at corresponding positions on the second interface based on personalized data; the second device lays out the second setting at the position corresponding to the first setting's layout position on the second interface according to the second strategy, and the second setting does not belong to the multiple settings. This not only ensures that the settings on the second interface of the second device maintain the same layout position as the corresponding settings on the first interface, preserving user habits, but also ensures that the second interface of the second device has no empty spaces, resulting in greater overall coherence, aesthetics, and improved user experience. For example, if the second setting is a switch recently used or the most frequently used switch, laying out this second setting makes it convenient for the user to use it again; or if the second setting is a new setting added to the second device compared to the first device, laying out this second setting makes it easier for the user to access or discover the new function of the second device, improving the user experience of using the second device.

[0028] As one possible implementation, the second setting could be the setting most frequently used by the user within a preset time period while using the first device; or, the second setting could be the setting most recently used by the user while using the first device; or, the second setting could be a setting supported by the second device but not included in multiple other settings. This would, on the one hand, ensure a seamless second interface on the second device, resulting in a more cohesive and aesthetically pleasing design; on the other hand, it could improve the user experience. For example, if the second setting is a recently used or most frequently used switch, its placement would facilitate future use. Similarly, if the second setting is a new feature added to the second device compared to the first device, its placement would make it easier for the user to access or discover the new functionality, thus enhancing the user experience.

[0029] As an example, the reason why the second device does not support the first setting item includes at least one of the following: the hardware of the second device does not support the function corresponding to the first setting item; the identifier of the first setting item in the first device is inconsistent with the identifier of the setting item with the same function in the second device; or the function corresponding to the first setting item has not been authorized by the user in the second device.

[0030] As one possible implementation, the aforementioned first interface is a control center interface, and the multiple settings items include any one or more of the following: cellular switch, airplane mode switch, eye protection mode switch, do not disturb switch, silent switch, flashlight switch, auto-rotate switch, mobile data switch, Wi-Fi switch, Bluetooth switch, and HyperTerminal switch. This allows the second device to maintain, to the greatest extent possible, consistency with the control center interface layout on the first device after personalized data is migrated to the second device, preserving user habits.

[0031] As one possible implementation, the second interface described above is a control center interface. This allows the second device to maintain, to the greatest extent possible, the layout of its control center interface to match that of the first device after the personalized data has been migrated, thus preserving the user's habits.

[0032] Thirdly, an electronic device is provided, comprising: a display screen for displaying an interface; a memory for storing computer program instructions; and a processor for executing the computer program instructions to support the electronic device in implementing the method as described in any possible implementation of the first aspect.

[0033] Fourthly, an electronic device is provided, comprising: a display screen for displaying an interface; a memory for storing computer program instructions; and a processor for executing the computer program instructions to support the electronic device in implementing the method as described in any possible implementation of the second aspect.

[0034] Fifthly, a data migration system is provided, comprising: an electronic device as described in the third aspect, and an electronic device as described in the fourth aspect.

[0035] In a sixth aspect, a computer-readable storage medium is provided that stores computer program instructions that, when executed by a processor, implement the method as described in any possible implementation of the first or second aspect.

[0036] In a seventh aspect, a computer program product comprising instructions is provided, which, when run on a computer, causes the computer to implement the method as described in any possible implementation of the first or second aspect.

[0037] Eighthly, a chip system is provided, comprising processing circuitry and a storage medium storing computer program instructions; when executed by the processor, the computer program instructions implement the method as described in any possible implementation of the first or second aspect. The chip system may be composed of chips or may include chips and other discrete devices. Attached Figure Description

[0038] Figure 1 is a schematic diagram of the effect of personalized data migration;

[0039] Figure 2 is a schematic diagram of two data migration architectures provided in the embodiments of this application;

[0040] Figure 3 is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application;

[0041] Figure 4 is a flowchart of a data migration method provided in an embodiment of this application;

[0042] Figure 5 is a schematic diagram of layout parameters corresponding to personalized data provided in an embodiment of this application;

[0043] Figure 6 is a schematic diagram of an architecture for obtaining personalized data based on a control center interface, as provided in an embodiment of this application.

[0044] Figure 7 is a schematic diagram of obtaining personalized data based on a control center interface according to an embodiment of this application;

[0045] Figure 8A is a schematic diagram of a first device determining personalized data according to an embodiment of this application;

[0046] Figure 8B is a schematic diagram of the contents of an IconClass class provided in an embodiment of this application;

[0047] Figure 8C is a schematic diagram of the contents of a FarmlandClass provided in an embodiment of this application;

[0048] Figure 8D is a schematic diagram of the contents of a personalized data (Farmland.config) provided in an embodiment of this application;

[0049] Figure 8E is a schematic diagram of a user interface for customizing and modifying personalized data according to an embodiment of this application;

[0050] Figure 9 is a schematic diagram of another user-customizable interface for modifying personalized data provided in an embodiment of this application;

[0051] Figure 10 is a schematic diagram of the effect of a second device laying out an interface based on personalized data according to an embodiment of this application;

[0052] Figure 11A is a schematic diagram of the effect of another second device based on personalized data for interface layout provided in an embodiment of this application;

[0053] Figure 11B is a schematic diagram of the data migration process and effect in a new device replacement scenario provided by an embodiment of this application;

[0054] Figure 12 is a flowchart of another data migration method provided in an embodiment of this application;

[0055] Figure 13 is a schematic diagram of another architecture for obtaining personalized data based on the control center interface provided in an embodiment of this application;

[0056] Figure 14 is a schematic diagram of the effect of interface layout based on personalized data in another second device provided in the embodiment of this application;

[0057] Figure 15 is a flowchart of another data migration method provided in an embodiment of this application;

[0058] Figure 16 is a structural block diagram of an electronic device provided in an embodiment of this application;

[0059] Figure 17 is a structural block diagram of another electronic device provided in an embodiment of this application. Detailed Implementation

[0060] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; "and / or" in this text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0061] In the following text, the terms "first," "second," etc., are used only to distinguish different descriptive objects and do not limit the position, order, priority, quantity, or content of the described objects. For example, if the described object is a "field," then the ordinal numbers before "field" in "first field" and "second field" do not limit the position or order of the "fields." "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the described object is a "level," then the ordinal numbers before "level" in "first level" and "second level" do not limit the priority of the "levels." Furthermore, the quantity of described objects is not limited by ordinal numbers and can be one or more; for example, in "first device," the number of "devices" can be one or more. In addition, objects modified by different prefixes can be the same or different. For example, if the described object is "device," then "first device" and "second device" can be devices of the same type or different types. Similarly, if the described object is "information," then "first information" and "second information" can be information with the same content or information with different content. In summary, the use of ordinal numbers and other prefixes used to distinguish the described objects in the embodiments of this application does not constitute a limitation on the described objects. The description of the described objects is given in the claims or the context of the embodiments, and the use of such prefixes should not constitute an unnecessary limitation.

[0062] Furthermore, in the embodiments of this application, "connection" can be a direct connection or an indirect connection; in addition, it can refer to an electrical connection or a communication connection; for example, the connection of two electrical components A and B can refer to A and B being directly connected, or it can refer to A and B being indirectly connected through other electrical components or connection media, or it can refer to A and B being indirectly connected through other communication devices or communication media, as long as it enables communication between A and B.

[0063] As described in the background section, existing automatic data migration technologies only target application data such as contacts, text messages, photos, and videos stored on older devices. They cannot migrate personalized data about user habits and / or preferences, thus failing to provide users with a sufficiently good user experience.

[0064] Take personalized data as an example, which relates to the parameters of the control center switch items. The control center can be an interface that integrates various functions of the user's device (such as WiFi, Bluetooth, cellular communication, airplane mode, eye protection mode, do not disturb mode, etc.), such as the interface that is brought up when the user performs a pull-down operation on the status bar at the top edge of the device's display screen.

[0065] We know that the arrangement of various switches on the control center interface is usually linear, meaning that the positions of each switch are coupled. For example, please refer to Figure 1, which shows a schematic diagram of a personalized data migration effect. As shown in Figure 1(a), taking a control center interface of an electronic device including switch-1, switch-2, ..., switch-n (where n is a positive integer greater than 2) as an example, the relative positional relationship between switch-1, switch-2, ..., switch-n is fixed. That is, switch-2 is located at position 2 after position 1 of switch-1, switch-3 is located at position 3 after position 2 of switch-2, and so on.

[0066] In this scenario, if the parameters of the control center switches are directly migrated from one device (such as an old device in a replacement scenario) to another device (such as a new device in a replacement scenario), and if the new and old devices differ in the switches they support, the coupling relationship between the switches will cause the layout of the switches on the control center interface of the new device to change after the data migration. For example, suppose the new device does not support switch item -2, which is supported by the old device as shown in Figure 1(a). When the new device receives the parameters of the control center switches from the old device and performs the corresponding configuration, the new device will move all switches after switch item -2 forward sequentially, as shown in Figure 1(b). Ultimately, the positions of the switches on the control center interface of the new device will still not be consistent with those of the old device. The operating habits that users have developed when using the old device cannot be directly applied to the new device. If users want to maintain the switch layout habits of the old device, they need to manually adjust each switch, which is not a good user experience.

[0067] To facilitate the convenient and accurate migration of user-specific data from one device to another, ensuring that the positions of various settings representing user habits and / or preferences remain unchanged after migration, this application provides a device data migration method. Based on this method, a first device can decouple multiple settings used to represent user habits and / or preferences, making them independent in relative position. Ultimately, after migrating the personalized data corresponding to each setting to a second device, the second device can maintain a consistent layout with the first device when arranging the settings, preserving user habits and improving user experience.

[0068] It should be noted that the scenario in this application embodiment where the first device migrates user personalized data to the second device may be a scenario of replacing a device with a new one, also known as a device cloning scenario. In this scenario, the first device is the old device and the second device is the new device. However, this application embodiment does not limit the usage scenario. For example, the scenario of migrating user personalized data from the first device to the second device may also be a conventional scenario with device synchronization requirements.

[0069] When migrating data from a first device to a second device, including but not limited to user personalization data, or application data such as contacts, SMS messages, photos, and videos, the first device can complete the data migration through various migration methods.

[0070] As an example, please refer to Figure 2, which shows two data migration architectures provided in the embodiments of this application.

[0071] As shown in Figure 2(a), data migration between the first and second devices can be accomplished through cross-device transmission. Alternatively, as shown in Figure 2, personalized data can be sent from the first device to the second device by one scanning the other's QR code. Another example is that the first device can connect to the other's wireless local area network (WLAN) hotspot, enabling personalized data transmission between the two devices. Furthermore, a communication connection may be established between the first and second devices, including but not limited to Bluetooth, Wi-Fi Direct, and data cable connections, allowing the first device to send personalized data to the second device. Finally, if both devices have an application with data cloning capabilities installed and are logged into the same user account, the first device can clone personalized data to the second device using this application.

[0072] As shown in Figure 2(b), both the first device and the second device maintain communication connections with the cloud server, and data migration between the first device and the second device can be completed through cloud synchronization. Cloud synchronization is used to synchronize data from one location to another, such as synchronizing from the first device to the second device in this embodiment. Exemplarily, cloud synchronization can be implemented using a cloud computing platform or a web-based application, which helps ensure data consistency and availability and reduces data duplication and redundancy. In this embodiment, the first device can upload the personalized data to be migrated to the cloud server, which then sends it to the second device.

[0073] Of course, the data migration architectures shown in Figure 2(a) and Figure 2(b) are only examples. In actual applications, the specific composition of the data migration architecture and the specific data migration method are not limited and can be determined according to the specific situation.

[0074] The electronic devices described in this application (such as the first device or the second device) may include, but are not limited to, smartphones, netbooks, tablets, smart drawing tablets, handwriting tablets, smartwatches, smart bracelets, phone watches, smart glasses, smart cameras, PDAs, in-vehicle computers, personal computers (PCs), personal digital assistants (PDAs), portable multimedia players (PMPs), augmented reality (AR) / virtual reality (VR) devices, smart TVs, projection devices, or motion-sensing game consoles in human-computer interaction scenarios. Alternatively, the electronic device may also be other types or structures of electronic devices with a display screen, which is not limited in this application.

[0075] As an example, please refer to Figure 3, which shows a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application.

[0076] As shown in Figure 3, the electronic device may include a processor 310, a memory (including an external memory interface 320 and an internal memory 321), a universal serial bus (USB) interface 330, a charging management module 340, a power management module 341, a battery 342, an antenna 1, an antenna 2, a mobile communication module 350, a wireless communication module 360, an audio module 370, a speaker 370A, a receiver 370B, a microphone 370C, a headphone jack 370D, a sensor module 380, buttons 390, a motor 391, an indicator 392, a camera 393, a display screen 394, etc.

[0077] The sensor module 380 may include, but is not limited to, one or more of the following: touch sensor 380A, pressure sensor 380B, temperature sensor, gyroscope sensor, barometric pressure sensor, magnetic sensor, accelerometer, distance sensor, proximity sensor, fingerprint sensor, ambient light sensor, bone conduction sensor, etc.

[0078] Processor 310 may include one or more processing units. For example, processor 310 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a flight controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors.

[0079] In some embodiments of this application, where the electronic device is the first device, the processor 310 can be used to generate personalized data about user habits and / or preferences.

[0080] As an example, the processor 310 can automatically generate personalized data about user habits and / or preferences based on the layout of various settings on the quick access interface of the first device; the settings represented by this personalized data are decoupled, such as not being related to each other in relative position. For example, the processor 310 of the first device can automatically generate personalized data about user habits and / or preferences based on the parameters of the settings on the quick access interface.

[0081] As an example, processor 310 can automatically generate personalized data about user habits and / or preferences based on the user's custom settings regarding the layout of various settings on the quick access interface of the first device; the settings represented by this personalized data are decoupled, such as being unrelated in relative position. For example, the first device can display a custom settings interface to the user via display screen 394, where the user can customize the layout of various settings on the quick access interface of the first device.

[0082] In some embodiments of this application, when the electronic device is the first device, the processor 310 can also be used to generate an interface layout strategy. The interface layout strategy represents the handling strategy for special cases when laying out settings based on personalized data. For example, if a special case is that a certain setting supported by the first device is not supported by the second device, the handling strategy may be to reserve the position corresponding to the setting or lay out other settings at the position corresponding to the setting.

[0083] In some embodiments of this application, when the electronic device is a second device, the processor 310 can be used to arrange the various settings on the shortcut interface of the second device according to the acquired personalized data. For example, the processor 310 of the second device can arrange the various settings in their corresponding positions according to the personalized data.

[0084] In some embodiments of this application, when the electronic device is a second device, if the second device does not support a certain setting represented by the personalized data when laying out settings based on personalized data, the processor 310 of the second device can perform corresponding processing according to the interface layout strategy. For example, the processor 310 of the second device can reserve the position corresponding to the setting or lay out other settings at the position corresponding to the setting.

[0085] As an example, the reason why the second device does not support a certain setting may include, but is not limited to, at least one of the following: the hardware of the second device does not support the function corresponding to the setting; the identifier (such as the name) of a certain setting in the first device is inconsistent with the identifier (such as the name) of a setting with the same function in the second device; or the function corresponding to the setting has not been authorized by the user in the second device.

[0086] Taking the example that the hardware of the second device does not support the function corresponding to the setting item, if the display hardware of the second device does not support the adaptive refresh rate adjustment function, then the second device does not support the "adaptive refresh rate" setting item; or, if the display hardware of the second device does not support the original color gamut display function, then the second device does not support the "original color mode" setting item.

[0087] Taking the example that the identifier (e.g., name) of a setting item in the first device is inconsistent with the identifier (e.g., name) of a setting item with the same function in the second device, assuming that the operating system of the second device names a setting item as "Name A", and the setting item with the same function in the personalization data is named "Name B", since "Name A" and "Name B" are different, the second device cannot determine a setting item that matches the setting item "Name B", and therefore the second device will determine that it does not support the setting item "Name B". For example, "Name A" is such as "Night Mode", and "Name B" is such as "Dark Mode".

[0088] Taking the example of a setting item whose corresponding function is not authorized by the user on the second device, suppose a certain setting item on the second device is a third-party setting item (such as a setting item for a function provided by a third-party application), which requires user authorization before the function can be used normally. However, this setting item has not been authorized by the user, so the second device will determine that it does not support the setting item.

[0089] As an example, for settings items corresponding to functions that have not been authorized by the user, as mentioned above, the second device may not place the setting item in the corresponding location, but may display it in another way (such as a lighter color) to indicate that the setting item is temporarily unavailable. If the user clicks on the temporarily unavailable setting item for the first time, the second device may pop up a window prompting the user that authorization is required to enable it, and then display the setting item in the normal display mode after obtaining user authorization.

[0090] The reasons why the second device does not support a certain setting are given above as examples only, and the application implementation does not limit the specific implementation.

[0091] The processor 310 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 310 is a cache memory. This memory can store instructions or data that the processor 310 has just used or that are used repeatedly. If the processor 310 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 310, and thus improves the efficiency of the system.

[0092] In some embodiments of this application, the memory of the processor 310 can be used to store parameters of settings and user-personalized data. The user-personalized data is obtained by decoupling the various settings according to their parameters, and / or by obtaining user-defined operations.

[0093] In some embodiments of this application, the memory of the processor 310 can be used to store application data, including but not limited to contacts, text messages, photos, videos, and other data.

[0094] In some embodiments of this application, the memory of the processor 310 can be used to store interface layout strategies. These strategies characterize handling strategies for special cases when laying out settings based on personalized data. For example, a special case might be that a setting supported by the first device is not supported by the second device. The handling strategy might be to reserve the location corresponding to that setting or to lay out other settings at that location.

[0095] In some embodiments, the processor 310 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0096] The MIPI interface can be used to connect the processor 310 to peripheral devices such as the display screen 394 and the camera 393. The MIPI interface includes a camera serial interface (CSI) and a display serial interface (DSI). In some embodiments of this application, the processor 310 can communicate with the camera 393 via the CSI interface to realize the image capture function of the electronic device. In some embodiments of this application, the processor 310 can communicate with the display screen 394 via the DSI interface to realize the display function of the electronic device, such as interface display.

[0097] The charging management module 340 receives charging input from the charger. The power management module 341 connects to the battery 342, the charging management module 340, and the processor 310. The power management module 341 receives input from the battery 342 and / or the charging management module 340 to power the processor 310, internal memory 321, display screen 394, camera 393, and wireless communication module 360, etc.

[0098] The wireless communication function of electronic devices can be realized through antenna 1, antenna 2, mobile communication module 350, wireless communication module 360, modem processor and baseband processor, etc.

[0099] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the electronic device can be used to cover one or more communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with a tuning switch.

[0100] The mobile communication module 350 can provide solutions for wireless communication applications in electronic devices, including 2G / 3G / 4G / 5G. The mobile communication module 350 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 350 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation.

[0101] Wireless communication module 360 ​​can provide solutions for wireless communication applications in electronic devices, including wireless local area networks (WLAN) (such as WiFi networks), Bluetooth BT, global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technology.

[0102] In some embodiments, antenna 1 of the electronic device is coupled to mobile communication module 350, and antenna 2 is coupled to wireless communication module 360, enabling the electronic device to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies. The GNSS may include Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), BeiDou Navigation Satellite System (BDS), Quasi-Zenith Satellite System (QZSS), and / or Satellite Based Augmentation Systems (SBAS).

[0103] In some embodiments of this application, antenna 1 of the electronic device is coupled to mobile communication module 350, and antenna 2 is coupled to wireless communication module 360, enabling the electronic device to communicate with a cloud server via wireless communication technology. For example, if the electronic device is a first device, it can upload user's personalized data to the cloud server; if the electronic device is a second device, it can download user's personalized data from the first device to the cloud server.

[0104] Electronic devices implement display functions through GPUs, displays 394, and APs. The GPU is a microprocessor for image processing, connected to the displays 394 and the AP. The GPU performs mathematical and geometric calculations for graphics rendering. Processor 310 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0105] Display screen 394 is used to display images, videos, etc. Display screen 394 includes a display panel. The display panel can be a low-temperature polycrystalline silicon (LTPS) display, a low-temperature polycrystalline oxide (LTPO) display, a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED) display, a flexible light-emitting diode (FLED), a Miniled LED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc.

[0106] In some embodiments of this application, when the electronic device is the first device, the electronic device can display a shortcut interface, a custom settings interface, etc. through the GPU, the display screen 394, and the AP.

[0107] In some embodiments of this application, when the electronic device is a second device, the electronic device can display a shortcut interface through a GPU, a display screen 394, and an AP, etc.

[0108] The external memory interface 320 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device. The external memory card communicates with the processor 310 through the external memory interface 320 to perform data storage.

[0109] Internal memory 321 can be used to store computer executable program code. Exemplarily, the computer program may include an operating system program and application programs. The executable program code includes instructions. Processor 310 executes various functional applications and data processing of the electronic device by running the instructions stored in internal memory 321. Internal memory 321 may include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function, etc. The data storage area may store data created during the use of the electronic device, etc. Furthermore, internal memory 321 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. Processor 310 executes various functional applications and data processing of the electronic device by running instructions stored in internal memory 321 and / or instructions stored in memory disposed within the processor.

[0110] In some embodiments of this application, the internal memory 321 may be used to store parameters of settings and user-personalized data.

[0111] In some embodiments of this application, the internal memory 321 may be used to store application data, including but not limited to contact data, SMS messages, photos, videos, etc.

[0112] In some embodiments of this application, the internal memory 321 may be used to store interface layout strategies.

[0113] Touch sensor 380A, also known as a "touch panel," can be located on display screen 394. The touch sensor 380A and display screen 394 together form a touchscreen, also known as a "touch screen." Touch sensor 380A detects touch operations applied to or near it. The touch sensor can transmit raw information, such as touch position, touch pressure, touch angle, touch area, and touch duration, to the processor for subsequent operation information acquisition, input event generation, and processing. The processor can also provide visual output related to the touch operation through display screen 394. In some embodiments, touch sensor 380A may also be located on the surface of the electronic device, in a different position than display screen 394.

[0114] Pressure sensor 380B is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 380B can be disposed on display screen 394. There are many types of pressure sensors, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may include at least two parallel plates with conductive material. When force is applied to the pressure sensor, the capacitance between the electrodes changes. The electronic device determines the pressure intensity based on the change in capacitance. When a touch operation is applied to display screen 394, the electronic device can detect the touch force, etc., through the pressure sensor. The electronic device can also calculate the touch position based on the detection signal from pressure sensor 380B. In some embodiments, pressure sensor 380B can be used to detect information such as the touch position, touch force, touch angle, touch area, and touch duration of a stylus.

[0115] In some embodiments of this application, the touch sensor 380A and / or the pressure sensor 380B can be used to detect user operations on settings items on the quick access interface, such as adding settings items, removing settings items, moving settings items, etc.

[0116] In some embodiments of this application, the touch sensor 380A and / or the pressure sensor 380B can be used to detect user operations on the custom settings interface regarding the layout of various settings items on the quick access interface of the first device, such as adding settings items, removing settings items, moving settings item positions, etc.

[0117] In this application embodiment, the touch operation detected by the touch sensor 380A can be the user's operation on the touch screen by using their finger, or it can be the user's click (such as single click, double click, etc.) operation / long press operation / swipe (such as swipe down, swipe up, swipe left, swipe right, etc.) operation / drag operation / floating gesture operation, etc., using touch auxiliary tools such as stylus, stylus, stylus ball, etc. This application does not limit it.

[0118] Electronic devices can implement audio functions through audio modules 370, speakers 370A, receivers 370B, microphones 370C, and access points (APs), such as music playback and recording.

[0119] In addition, for the description of hardware such as button 390, motor 391, and indicator 392, please refer to conventional technology; the embodiments of this application will not be repeated here.

[0120] It is understood that the structure illustrated in Figure 3 of this application does not constitute a specific limitation on the electronic device. In other embodiments of this application, the electronic device may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0121] The data migration method for the device provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0122] Please refer to Figure 4, which illustrates a data migration method provided in this application embodiment, taking data migration from a first device to a second device as an example. As shown in Figure 4, the data migration method for devices provided in this application embodiment may include steps S401-S403:

[0123] S401: The first device responds to the data migration request and obtains the user's personalized data, which represents the layout and position of the settings items on the first interface.

[0124] The user's personalized data represents the user's habits and / or preferences when using the quick access interface (denoted as the first interface) on the first device. The first interface includes one or more settings items, which are decoupled and unrelated in relative position. For example, the user's personalized data represents the layout of the settings items on the first interface when the user uses the first interface on the first device.

[0125] Taking the control center interface as an example, the settings items on the first interface include, but are not limited to, general switches, specific switches, and third-party switches. For instance, settings items on the first interface such as cellular switch, airplane mode switch, eye protection mode switch, do not disturb switch, silent switch, flashlight switch, auto-rotate switch, mobile data switch, WLAN switch, Bluetooth switch, and HyperTerminal switch are not limited. General switches include conventional switches such as cellular switch, airplane mode switch, eye protection mode switch, do not disturb switch, silent switch, flashlight switch, auto-rotate switch, mobile data switch, WLAN switch, and Bluetooth switch; specific switches include switches provided by specific manufacturers such as HyperTerminal switches; and third-party switches include function switches enabled by third-party applications downloaded and installed from app stores, such as switches for a specific function provided by a third-party application.

[0126] As an example, personalized data characterizes a user's settings layout habits and / or preferences when using the first interface, such as personalized data including layout parameters of the first interface.

[0127] As an example, the layout parameters of the first interface include the layout position of each setting item on the first interface. For example, the layout position of each setting item can be identified by position parameters, such as row number and column number.

[0128] In some embodiments, the layout parameters of the first interface may also include the row and column parameters of the layout settings on the first interface. The row and column parameters can be represented by (a, b), where a is the number of rows and b is the number of columns.

[0129] As an example, please refer to Figure 5, which shows a schematic diagram of layout parameters corresponding to personalized data provided in an embodiment of this application. For example, the personalized data includes row and column parameters (3, 4) representing the number of rows 3 and columns 4 of the layout settings items on the first interface shown in Figure 5, and position parameters -1 (e.g., (1, 1)) representing the location of switch items-1,-2,-3,-4,-5,-6,-7,-8,-9,-10,-11, and-12 on the first interface, respectively. Parameter-2 (e.g., (1,2)), position parameter-3 (e.g., (1,3)), position parameter-4 (e.g., (1,4)), position parameter-5 (e.g., (2,1)), position parameter-6 (e.g., (2,2)), position parameter-7 (e.g., (2,3)), position parameter-8 (e.g., (2,4)), position parameter-9 (e.g., (3,1)), position parameter-10 (e.g., (3,2)), position parameter-11 (e.g., (3,3)), position parameter-12 (e.g., (3,4)).

[0130] As one possible implementation, the first device acquires personalized data, including: the first device automatically generates personalized data based on the layout of each setting item on the first interface.

[0131] For example, taking the control center interface as the first interface, please refer to Figure 6. Figure 6 shows a schematic diagram of an architecture for obtaining personalized data based on the control center interface provided in this application embodiment. As shown in Figure 6, the first device can provide the user with control center functions through the system user interface (UI). The control center functions include providing one or more switch items (i.e., the settings items mentioned above) to facilitate users to perform relevant setting operations, such as turning the switch on / off, through this shortcut entry. In this application embodiment, the first device can generate a configuration file about the control center based on the various switch items in the control center, i.e., the personalized data described in this application embodiment.

[0132] Please refer to Figure 7, which shows a schematic diagram of obtaining personalized data based on a control center interface according to an embodiment of this application. As shown in Figure 7, the first device can first decouple the switch items (i.e., the setting items mentioned above) arranged on the control center interface 700, so that they are not related to each other in relative position. Then, the first device can generate row and column parameters (3, 4) according to the row number 3 and column number 4 of the switch items (i.e., the setting items mentioned above) arranged on the control center interface 700, and generate their respective position parameters according to the row number and column number of the switch items-1,-2,-3,-4,-5,-6,-7,-8,-9,-10,-11, and-12 respectively, as shown in Figure 7. Position parameter-1 (e.g., (1 ,1)), position parameter-2 (e.g. (1,2)), position parameter-3 (e.g. (1,3)), position parameter-4 (e.g. (1,4)), position parameter-5 (e.g. (2,1)), position parameter-6 (e.g. (2,2)), position parameter-7 (e.g. (2,3)), position parameter-8 (e.g. (2,4)), position parameter-9 (e.g. (3,1)), position parameter-10 (e.g. (3,2)), position parameter-11 (e.g. (3,3)), position parameter-12 (e.g. (3,4)).

[0133] As one possible implementation, the first device acquires personalized data, including: the first device automatically generates personalized data based on the user's custom settings for various settings items on the first interface.

[0134] As an example, please refer to Figure 8A, which illustrates a process for a first device to determine personalized data according to an embodiment of this application. As shown in S801 and S802 of Figure 8A, in response to receiving an operation from a user to open a first interface, the control center function of the first device loads the icon class (loadIconClass) and displays the initial farmland class (InitFarmland). Then, as shown in S803 of Figure 8A, the first device determines the configuration file (.config) based on the user's operation to adjust the number of rows and columns of the farmland, and / or the user's operation to place setting icons at various locations. Then, as shown in S804 of Figure 8A, the first device determines whether it has already stored layout parameters corresponding to the configuration file; if so, as shown in S805 of Figure 8A, the first device uses these layout parameters as personalized data and sends the personalized data to the second device; if not, as shown in S806 and S805 of Figure 8A, the first device obtains the layout parameters of the first interface based on the configuration file (.config) and sends these layout parameters as personalized data to the second device. For example, the data format of personalized data may be Farmland.config, as shown in Figure 8A.

[0135] As an example, the IconClass class shown in Figure 8A might look like Figure 8B, the InitFarmland class shown in Figure 8A might look like the FarmlandClass class in Figure 8C, and the final Farmland.config file shown in Figure 8A might look like Figure 8D. In the IconClass class shown in Figure 8B, Attribute row refers to the number of icon rows, Attribute column refers to the number of icon columns, and Operation Init, Operation Farm, Operation Dig, and Operation Update refer to the initialization, farmland location customization, setting customization, and update functions supported by the IconClass class, respectively. In the FarmlandClass class shown in Figure 8C, Attribute row refers to the number of farmland rows, Attribute column refers to the number of farmland columns, and Operation InitFarmland and Operation Update refer to the farmland initialization and update functions supported by FarmlandClass, respectively. As shown in Figure 8D, Farmland.config (Farmland.cfg) includes the row and column parameters of the farmland (Farmland: (a, b)) and the position parameters corresponding to each setting item (such as Icon (mute), Icon (flashlight), Icon (auto-rotate), Icon (move data) etc.), as well as other related information (info).

[0136] In some embodiments, the first device may allow users to customize and modify personalized data, including but not limited to modifying the number of rows / columns, initializing the layout, adding or removing settings, and adjusting the position of settings, without limitation. Layout initialization refers to restoring the first device to its factory default layout.

[0137] For example, taking the control center interface as the first interface, please refer to Figure 8E. Figure 8E shows a schematic diagram of an interface for user-customized modification of personalized data provided in an embodiment of this application. As shown in Figure 8E, the first device can display the generated personalized data through interface 800. Users can make relevant modifications on interface 800, such as including but not limited to modifying the number of rows / columns, layout initialization, adding switch items (i.e., the settings items mentioned above), removing switch items, and adjusting the position of switch items. Figure 8E shows an example where the user changes the row and column parameters from (3, 4) to (4, 3). The modified personalized data is shown in interface 801. The first device can update the row and column parameters to (4, 3) according to the user's custom modification operation. The position parameters of switch item-1, switch item-2, switch item-3, switch item-4, switch item-5, switch item-6, switch item-7, switch item-8, switch item-9, switch item-10, switch item-11, and switch item-12 are updated to (1, 1), (1, 2), (1, 3), (2, 1), (2, 2), (2, 3), (3, 1), (3, 2), (3, 3), (4, 1), (4, 2), (4, 3).

[0138] For example, taking the control center interface as the first interface, please refer to Figure 9. Figure 9 shows another user-customizable interface for modifying personalized data provided in this application embodiment. As shown in Figure 9, the first device can display the generated personalized data through interface 900. The user can make relevant modifications on interface 900, such as including but not limited to modifying the number of rows / columns, layout initialization, adding switch items (i.e., the settings items mentioned above), removing switch items, and adjusting the position of switch items. Figure 9 takes the example of the user swapping the positions of switch items-1 and-2 and removing switch item-12. The modified personalized data is shown in interface 801. The first device can then modify the position parameter-1 of switch item-1 from (1,1) to (1,2) and the position parameter-2 of switch item-2 from (1,2) to (1,1) according to the user's custom modification operation, and delete switch item-12 and its position parameter (3,4).

[0139] It should be noted that Figures 7-9 only illustrate the method and specific content of determining personalized data described in the embodiments of this application, using the control center interface as an example of the first interface. In practical applications, the process of determining personalized data corresponding to other first interfaces can also refer to the process of determining personalized data corresponding to the control center interface, which will not be elaborated here.

[0140] S402: The first device sends personalized data to the second device.

[0141] As one possible implementation, the first device can send personalized data to the second device via cross-device transmission.

[0142] For example, the first device can send personalized data to the second device by scanning a QR code on the second device used for data cloning. Alternatively, the first device can send personalized data to the second device by providing a QR code for data cloning that the second device can scan.

[0143] For example, the first device can send personalized data to the second device by connecting to the second device's WLAN hotspot. Alternatively, the first device can send personalized data to the second device by opening a WLAN hotspot for the second device to connect to.

[0144] For example, the first device can send personalized data to the second device through a communication connection established with the second device, such as a Bluetooth connection, WiFi Direct connection, or data cable connection.

[0145] For example, if both the first and second devices have an application with data cloning capabilities installed and are logged into the same user account, the first device can use this application to clone personalized data to the second device.

[0146] As one possible approach, the first device can send personalized data to the second device via cloud synchronization.

[0147] For example, the first device can upload the personalized data to be migrated to a cloud server, which will then send it to the second device.

[0148] Of course, the above-mentioned cross-device transmission methods and cloud synchronization methods are only examples of possible ways for the first device to send personalized data to the second device. In practical applications, the first device can also send personalized data to the second device through other transmission methods. This application embodiment does not make specific limitations.

[0149] S403: The second device lays out the corresponding settings on the interface based on the personalized data from the first device.

[0150] As one possible implementation, the second device can arrange the settings on the quick access interface (referred to as the second interface) of the second device according to the layout parameters of the quick access interface (i.e., the first interface) of the first device included in the personalized data from the first device.

[0151] As an example, the layout parameters of the first interface include the row and column parameters of the settings on the first interface and the position parameters corresponding to each setting item. The second device can lay out the same number of rows and columns of settings on the quick access interface (i.e., the second interface) of the second device according to the row and column parameters of the settings on the first interface, and lay out the same settings at the corresponding positions on the second interface according to the position parameters corresponding to each setting item on the first interface.

[0152] Taking the layout parameters of the first interface, including row and column parameters (a, b) and position parameters (1, 1), (1, 2), ..., (1, b), (2, 1), ..., (a, b) representing user habits and / or preferences, as an example, when the second device sets the second interface according to the layout parameters of the first interface, the second device can lay out a rows and b columns of setting items on the second interface, and lay out the a*b setting items at the corresponding positions on the second interface according to the position parameters corresponding to each of the a*b setting items.

[0153] For example, please refer to Figures 10 and 11A. Figures 10 and 11A show the effect of two second devices arranging the interface according to personalized data, with the layout parameters of the first interface including row and column parameters (3, 4) and the position parameters (1, 1), (1, 2), (1, 3), (1, 4), (2, 1), (2, 2), (2, 3), (2, 4), (3, 1), (3, 2), (3, 3), (3, 4) of the first interface representing user habits and / or preferences, respectively.

[0154] As shown in Figure 10, assuming the second device supports switches -1 to -12, when laying out the second interface, the second device arranges switches in 3 rows and 4 columns on the second interface. Based on the position parameters of the 12 switches, switches -1, -2, -3, -4, -5, -6, -7, -8, -9, -10, -11, and -12 are placed at positions (1,1), (1,2), (1,3), (1,4), (2,1), (2,2), (2,3), (2,4), (3,1), (3,2), (3,3), and (3,4), respectively. This ensures that the switch layout on the second device's quick access interface remains consistent with the user's habits and / or preferences on the first device's quick access interface, maintaining user habits and improving user experience.

[0155] As shown in Figure 11A, assuming the second device supports switch items -1 to -5 and switch items -7 to -12, but does not support switch item -6, when laying out the second interface, the second device lays out 3 rows and 4 columns of switch items on the second interface, and according to the position parameters of the 11 switch items -1 to -5 and switch items -7 to -12, the switch items -1, -2, -3, -4, -7, -8, -9, -10, -11, and -12 are laid out at the positions (1,1), (1,2), (1,3), (1,4), (2,1), (2,3), (2,4), (3,1), (3,2), (3,3), and (3,4), respectively. As shown in Figure 11A, since the second device does not support switch item -6, it will not place the switch item at position (2,2) when laying out the switches on the second interface. That is, the second device reserves position (2,2) on the second interface as a blank space for users to customize switches according to their needs. Based on this, not only can the layout position of the same switch item on the quick access interface of the second device remain consistent with that of the first device, maintaining user habits and improving user experience; it also allows users to more intuitively see which functions on the first device are not enabled on the second device, facilitating flexible configuration of custom switches later.

[0156] As an example, as shown in Figure 11A, a new control (e.g., indicated by a "+") can be displayed in the reserved empty space, allowing the user to add a switch item to the reserved empty space on the second interface by clicking the new control. For instance, in response to the user clicking the new control, the second device can display an interface for adding switch items, from which the user can select the switch item to add.

[0157] As an example, the interface displayed on the second device for adding switches may include one or more candidate switches. For instance, these candidate switches may include switches supported by the second device and / or switches not supported by the second device. If the user selects a switch not supported by the second device, the second device may redirect to the download and installation interface for that switch, or display a user-authorized download option and redirect to the download and installation interface after user authorization. Alternatively, these candidate switches may include switches that the user frequently uses within a preset time period while using the first device.

[0158] As an example, the reason why the second device does not support switch item -6 may include, but is not limited to, at least one of the following: the hardware of the second device does not support the function corresponding to switch item -6; the identifier (such as name) of switch item -6 in the operating system of the first device is inconsistent with the identifier (such as name) of the switch item with the same function in the operating system of the second device; or the function corresponding to switch item -6 has not been authorized by the user in the second device.

[0159] It is understandable that, based on the data migration method shown in Figure 4, the first device can decouple multiple settings items on the quick access interface (such as the first interface) that represent user habits and / or preferences, making them independent in relative position. Ultimately, after migrating the data representing the user's settings layout habits and / or preferences when using the first interface, such as personalized data including the layout parameters of the first interface, to the second device, the second device can maintain consistency with the first interface to the greatest extent when laying out the quick access interface (such as the second interface), such as keeping the layout position of each setting item consistent with the first interface, maintaining the user's usage habits, and improving the user experience.

[0160] For example, in a replacement scenario, as shown in Figure 11B, based on the data migration method shown in Figure 4, the old device can determine a 3*4 layout for the farm based on user operations on the control center interface, such as adjusting the number of rows and columns in the farm, and / or placing setting icons at various locations within the farm. This generates personalized data (Farmland.cfg) representing the user's habits and / or preferences when using the control center interface. Within the 3*4 farm, the settings are decoupled; for example, their relative positions are unrelated. Thus, when the new device lays out its control center interface based on the personalized data (Farmland.cfg), it can ensure that the settings maintain maximum consistency with the control center interface on the old device. Therefore, in the scenario of replacing a device with a new one, this solution can conveniently and accurately migrate personalized data about the user's settings layout habits and / or preferences when using quick access interfaces (such as the first interface) from the old device to the new device while reducing user operations. This fully preserves the user's usage habits and / or preferences on the new device, thereby improving the user experience.

[0161] In some embodiments, to further improve the flexibility of interface layout based on personalized data and enhance the user experience, if the second device does not support a certain setting item on the first interface, the second device can refer to an interface layout strategy when laying out the second interface. The interface layout strategy represents the handling strategy for special cases when laying out settings based on personalized data. For example, if the second device does not support a certain setting item on the first interface, the second device can refer to the interface layout strategy to reserve the position corresponding to that setting item or lay out other settings items at that position.

[0162] As an example, the interface layout strategy might be determined by the first device and sent to the second device.

[0163] As another example, the interface layout strategy may be determined by the second device.

[0164] For example, please refer to Figure 12. Figure 12 shows a flowchart of another data migration method provided by an embodiment of this application, taking the interface layout strategy determined by the first device and sent to the second device as an example. As shown in Figure 12, the data migration method of the device provided by the embodiment of this application may include S1201-S1203:

[0165] S1201: The first device responds to the data migration request and obtains the user's personalized data and interface layout strategy.

[0166] As one possible implementation, the first device can determine the interface layout strategy based on the default strategy of the function / application to which the first interface belongs.

[0167] For example, if the default strategy of the function / application to which the first interface belongs is to reserve the position corresponding to a certain setting item in the special case where a certain setting item is not supported, then the first device determines the interface layout strategy as the first strategy. Alternatively, if the default strategy of the function / application to which the first interface belongs is to place other setting items in the position corresponding to a certain setting item in the special case where a certain setting item is not supported, then the first device determines the interface layout strategy as the second strategy.

[0168] As one possible implementation, the first device can determine the interface layout strategy based on the user's custom settings.

[0169] For example, the first device can display a settings interface for users to customize the interface layout strategy. Taking the first interface as a control center interface as an example, please refer to Figure 13. Figure 13 shows another schematic diagram of the architecture for obtaining personalized data based on the control center interface provided in this application embodiment. As shown in Figure 13, the first device can provide the user with control center functions through the system UI. The control center functions include providing one or more switch items (i.e., the settings items mentioned above) to facilitate users to perform related setting operations, such as turning the switch on / off, through this shortcut entry. In this application embodiment, the first device can generate a configuration file about the control center based on the various switch items of the control center, i.e., the personalized data described in this application embodiment, and generate an interface layout strategy based on the user's customized settings for special situations (such as the first strategy or the second strategy).

[0170] For example, the first strategy, such as strategyMode{0}, indicates that in the special case where a certain setting item is not supported, the position corresponding to that setting item is reserved; the second strategy, such as strategyMode{1}, indicates that in the special case where a certain setting item is not supported, other setting items are placed at the position corresponding to that setting item.

[0171] Alternatively, the first strategy, such as strategyMode{1}, indicates that for the special case where a certain setting is not supported, the position corresponding to that setting is reserved; the second strategy, such as strategyMode{0}, indicates that for the special case where a certain setting is not supported, other setting items are placed at the position corresponding to that setting.

[0172] The specific representation of the first and second strategies is not specifically limited in the embodiments of this application, and can be determined according to the specific circumstances.

[0173] For details regarding the first device's response to the data migration request to obtain personalized data, please refer to the explanation of S401 above; it will not be repeated here.

[0174] It should be noted that the embodiments of this application do not limit the specific relationship between personalized data and interface layout strategy. For example, in some examples, personalized data and interface layout strategy may be independent of each other; in other examples, personalized data may include interface layout strategy. For example, as shown in FIG8D, the Farmland.cfg (i.e., personalized data) obtained by the first device includes Strategy mode (i.e., interface layout strategy).

[0175] S1202: The first device sends personalized data and interface layout strategy to the second device.

[0176] As one possible implementation, the first device can send personalized data and interface layout strategies to the second device via cross-device transmission.

[0177] For example, the first device can send personalized data and interface layout strategies to the second device by scanning a QR code on the second device used for data cloning. Alternatively, the first device can send personalized data and interface layout strategies to the second device by providing a QR code for data cloning that the second device can scan.

[0178] For example, the first device can send personalized data and interface layout strategies to the second device by connecting to the second device's WLAN hotspot. Alternatively, the first device can send personalized data and interface layout strategies to the second device by opening a WLAN hotspot for the second device to connect to.

[0179] For example, the first device can send personalized data and interface layout strategies to the second device through a communication connection established with the second device, such as a Bluetooth connection, WiFi Direct connection, or data cable connection.

[0180] For example, if both the first and second devices have an application with data cloning capabilities installed and are logged into the same user account, the first device can use this application to clone personalized data and interface layout strategies to the second device.

[0181] As one possible implementation, the first device can send personalized data and interface layout strategies to the second device via cloud synchronization.

[0182] For example, the first device can upload the personalized data and interface layout strategy to be migrated to the cloud server, which will then send it to the second device.

[0183] Of course, the above-mentioned cross-device transmission methods and cloud synchronization methods are only examples of possible ways for the first device to send data to the second device. In practical applications, the first device can also send personalized data and interface layout strategies to the second device through other transmission methods. This application embodiment does not make specific limitations.

[0184] It should be noted that the embodiments of this application do not limit the specific method by which the first device sends the personalized data and interface layout strategy pair to the second device. For example, when the personalized data and interface layout strategy are independent of each other, the first device may send the personalized data and interface layout strategy together to the second device, or it may send the personalized data and interface layout strategy together to the second device separately. As another example, when the personalized data includes the interface layout strategy, the first device will send the personalized data including the interface layout strategy to the second device.

[0185] S1203: The second device performs the corresponding interface layout based on the personalized data, and performs the corresponding processing according to the interface layout strategy when the second device does not support a certain setting item.

[0186] As one possible implementation, the second device can lay out its own shortcut interface (hereinafter referred to as the second interface) based on the layout parameters of the first device's shortcut interface (i.e., the first interface) included in the personalized data from the first device. For example, assuming the layout parameters of the first interface include the row and column parameters of the settings items on the first interface and the position parameters corresponding to each setting item, the second device can lay out the same number of rows and columns of settings items on its own shortcut interface (i.e., the second interface) based on the row and column parameters of the settings items on the first interface, and lay out the same settings items at the corresponding positions on the second interface based on the position parameters corresponding to each setting item on the first interface.

[0187] Taking the layout parameters of the first interface as including row and column parameters (a, b) and position parameters (1, 1), (1, 2), ..., (1, b), (2, 1), ..., (a, b) of the a*b setting items on the first interface, respectively representing user habits and / or preferences, and the second device supporting the a*b setting items as an example, the second device can lay out a row and b column setting items on the second interface, and lay out the a*b setting items at the corresponding positions on the second interface according to the position parameters corresponding to each of the a*b setting items.

[0188] For example, assuming a=3 and b=4, the position parameters of switch items-1,-2,-3,-4,-5,-6,-7,-8,-9,-10,-11, and-12 on the first interface are (1,1), (1,2), (1,3), (1,4), (2,1), (2,2), (2,3), (2,4), (3,1), (3,2), (3,3), and (3,4). The second device can achieve the layout effect shown in Figure 10 by making the corresponding interface layout based on the personalized data.

[0189] Taking the layout parameters of the first interface, including row and column parameters (a, b) and position parameters (1, 1), (1, 2), ..., (1, b), (2, 1), ..., (a, b) representing user habits and / or preferences for using the a*b settings on the first interface, as an example, if the second device does not support a certain setting in the a*b settings (e.g., denoted as "setting-x"), the second device will perform corresponding processing according to the interface layout strategy. For example, if the interface layout strategy is the first strategy, the second device will reserve the position corresponding to setting-x; if the interface layout strategy is the second strategy, the second device will place other settings at the position corresponding to setting-x.

[0190] For example, assuming a=3 and b=4, the position parameters of switch items -1, switch item -2, switch item -3, switch item -4, switch item -5, switch item -6, switch item -7, switch item -8, switch item -9, switch item -10, switch item -11, and switch item -12 on the first interface are (1,1), (1,2), (1,3), (1,4), (2,1), (2,2), (2,3), (2,4), (3,1), (3,2), (3,3), and (3,4). The second device does not support switch item -6, and the interface layout strategy is the first strategy, as shown in Figure 11A. The second device reserves the position (2,2) corresponding to switch item -6 according to the interface layout strategy, resulting in the layout effect shown in Figure 11A.

[0191] Alternatively, assuming a = 3 and b = 4, the position parameters of switch items -1, -2, -3, -4, -5, -6, -7, -8, -9, -10, -11, and -12 on the first interface are (1,1), (1,2), (1,3), (1,4), (2,1), (2,2), (2,3), (2,4), (3,1), (3,2), (3,3), and (3,4). The second device does not support switch item -6, and the interface layout strategy is the second strategy, as shown in Figure 14. The second device places switch item -13 at position (2,2) corresponding to switch item -6 according to the interface layout strategy, resulting in the layout effect shown in Figure 14.

[0192] For example, please refer to Figure 15. Figure 15 shows a flowchart of another data migration method provided by an embodiment of this application, taking the interface layout strategy determined by a second device as an example. As shown in Figure 15, the data migration method of the device provided by this embodiment of the application may include S401-S403 and S1501, wherein S401-S403 are as described above, and S1501 is as follows:

[0193] S1501: When the second device does not support a certain setting item, the second device determines the interface layout strategy and performs corresponding processing according to the interface layout strategy.

[0194] As one possible implementation, the second device can determine the interface layout strategy based on the default strategy of the function / application to which the second interface belongs.

[0195] For example, if the default strategy of the function / application to which the second interface belongs is to reserve the position corresponding to a certain setting item in the special case where it is not supported, then the second device determines the interface layout strategy as the first strategy. Alternatively, if the default strategy of the function / application to which the second interface belongs is to place other setting items in the position corresponding to a certain setting item in the special case where it is not supported, then the second device determines the interface layout strategy as the second strategy.

[0196] As one possible implementation, the second device can determine the interface layout strategy based on the user's custom settings.

[0197] For example, the second device can display a settings interface for users to customize the interface layout strategy. Taking a control center interface as an example, the second device can provide control center functions to users through the system UI. The control center functions include providing one or more switch items (i.e., the settings items mentioned above) to facilitate users to perform relevant setting operations, such as turning switches on / off, through this shortcut. In this embodiment, the second device can generate a configuration file about the control center based on the various switch items in the control center, i.e., the personalized data described in this embodiment, and generate an interface layout strategy based on the user's customized settings for special situations (such as the first strategy or the second strategy).

[0198] For example, the first strategy, such as strategyMode{0}, indicates that in the special case where a certain setting item is not supported, the position corresponding to that setting item is reserved; the second strategy, such as strategyMode{1}, indicates that in the special case where a certain setting item is not supported, other setting items are placed at the position corresponding to that setting item.

[0199] Alternatively, the first strategy, such as strategyMode{1}, indicates that for the special case where a certain setting is not supported, the position corresponding to that setting is reserved; the second strategy, such as strategyMode{0}, indicates that for the special case where a certain setting is not supported, other setting items are placed at the position corresponding to that setting.

[0200] The specific representation of the first and second strategies is not specifically limited in the embodiments of this application, and can be determined according to the specific circumstances.

[0201] Taking the layout parameters of the first interface, including row and column parameters (a, b) and position parameters (1, 1), (1, 2), ..., (1, b), (2, 1), ..., (a, b) representing user habits and / or preferences for using the a*b settings on the first interface, as an example, if the second device does not support a certain setting in the a*b settings (e.g., denoted as "setting-x"), the second device will perform corresponding processing according to the interface layout strategy. For example, if the interface layout strategy is the first strategy, the second device will reserve the position corresponding to setting-x; if the interface layout strategy is the second strategy, the second device will place other settings at the position corresponding to setting-x.

[0202] For example, assuming a=3 and b=4, the position parameters of switch items -1, switch item -2, switch item -3, switch item -4, switch item -5, switch item -6, switch item -7, switch item -8, switch item -9, switch item -10, switch item -11, and switch item -12 on the first interface are (1,1), (1,2), (1,3), (1,4), (2,1), (2,2), (2,3), (2,4), (3,1), (3,2), (3,3), and (3,4). The second device does not support switch item -6, and the interface layout strategy is the first strategy, as shown in Figure 11A. The second device reserves the position (2,2) corresponding to switch item -6 according to the interface layout strategy, resulting in the layout effect shown in Figure 11A.

[0203] Alternatively, assuming a = 3 and b = 4, the position parameters of switch items -1, -2, -3, -4, -5, -6, -7, -8, -9, -10, -11, and -12 on the first interface are (1,1), (1,2), (1,3), (1,4), (2,1), (2,2), (2,3), (2,4), (3,1), (3,2), (3,3), and (3,4). The second device does not support switch item -6, and the interface layout strategy is the second strategy, as shown in Figure 14. The second device places switch item -13 at position (2,2) corresponding to switch item -6 according to the interface layout strategy, resulting in the layout effect shown in Figure 14.

[0204] As one possible implementation, in the examples shown in Figure 12 or Figure 15, when the second device lays out other settings at the positions corresponding to the settings it does not support according to the second strategy, the second device can determine which setting to lay out at that position according to preset rules. For example, the second device can lay out the settings that the user uses most frequently in the recent period (e.g., a week, half a month, a month, etc.) besides the aforementioned a*b settings when using various shortcut interfaces in the first device at the positions corresponding to the settings it does not support. Alternatively, the second device can lay out the settings that the user uses most recently besides the aforementioned a*b settings when using various shortcut interfaces in the first device at the positions corresponding to the settings it does not support. Furthermore, the second device can lay out a switch item that is newly added to the second device compared to the first device at the positions corresponding to the settings it does not support. Regarding the specific preset rules, this application embodiment does not limit them and can be determined according to the specific circumstances.

[0205] The second device can place other settings in the positions corresponding to settings it does not support. For example, as shown in Figure 14, by placing switch item -13 at position (2,2), the second interface of the second device can be made without empty space, making it more integrated and aesthetically pleasing. On the other hand, it can also improve the user experience. For example, if the newly placed switch item (switch item -13 as shown in Figure 14) is the switch item that the user recently used or the switch item that the user has used most frequently, then placing this switch item can make it convenient for the user to use it next time. Or, if the newly placed switch item is a switch item that the second device has added compared to the first device, then placing this switch item can make it easier for the user to access or discover the new functions of the second device, thus improving the user experience of using the second device.

[0206] It is understandable that, based on the data migration method shown in Figure 12 or Figure 15, the first device can decouple multiple settings on the quick access interface (such as the first interface) that represent user habits and / or preferences, making them independent in relative position. Ultimately, after migrating the layout habits and / or preferences of settings that represent the user's use of the first interface, such as personalized data including the layout parameters of the first interface, to the second device, the second device can maintain consistency with the first interface to the greatest extent when laying out the quick access interface (such as the second interface). For example, it can ensure that each setting item maintains the same layout position as the first interface, maintain the user's usage habits, and when the second device does not support a certain setting item on the first interface, it can perform corresponding processing according to the specific interface layout strategy, further improving the flexibility of interface layout based on user personalized data and further improving the user experience.

[0207] It should be understood that the various solutions in the embodiments of this application can be used in a reasonable combination, and the explanations or descriptions of the various terms appearing in the embodiments can be referenced or explained to each other in the various embodiments, without limitation.

[0208] It should also be understood that, in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0209] It is understood that, in order to implement the functions of any of the above embodiments, electronic devices (such as the first device or the second device) include hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0210] This application embodiment can divide an electronic device (such as a first device or a second device) into functional modules. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0211] As an example, please refer to Figure 16, which shows a structural block diagram of an electronic device provided in an embodiment of this application. As shown in Figure 16, the electronic device may include a personalized data determination module 1610 and a communication module 1620 according to the functional modules.

[0212] The personalized data determination module 1610 is used to support the electronic device in acquiring the user's personalized data, such as acquiring layout parameters of the first interface representing the user's settings layout habits and / or preferences when using the first interface, acquiring handling strategies for special cases when setting items are laid out based on the user's personalized data, such as interface layout strategies, and / or other processes related to the embodiments of this application. The communication module 1620 is used to support the electronic device in sending the user's personalized data, interface layout strategies, and / or other data related to the embodiments of this application to other devices (such as a second device).

[0213] As an example, please refer to Figure 17, which shows a structural block diagram of another electronic device provided in an embodiment of this application. As shown in Figure 17, the electronic device may include a communication module 1710 and an interface layout module 1720 according to the division of functional modules.

[0214] The communication module 1710 is used to support the electronic device in receiving personalized data from other devices (such as the first device), such as receiving layout parameters of the first interface representing the user's settings layout habits and / or preferences when using the first interface, receiving handling strategies for special cases when setting items are laid out based on the user's personalized data, such as interface layout strategies, and / or other data related to the embodiments of this application. The interface layout module 1720 is used to support the electronic device in laying out the interface according to the user's personalized data, and in handling special cases such as not supporting a certain setting item according to the interface layout strategy, and / or other processes related to the embodiments of this application.

[0215] It should also be understood that the various modules in an electronic device (such as the first device or the second device) can be implemented in software and / or hardware, without specific limitations. In other words, electronic devices or cloud servers are presented in the form of functional modules. Here, "module" can refer to application-specific integrated circuits (ASICs), circuits, processors and memories that execute one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the above functions.

[0216] In an alternative approach, when data transmission is implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are implemented. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital video disk (DVD)), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0217] The steps of the methods or algorithms described in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, portable hard disk, CD-ROM, or any other form of storage medium well known in the art. One exemplary embodiment couples a storage medium to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in an electronic device (such as a first device or a second device). Of course, the processor and storage medium can also exist as discrete components.

[0218] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

Claims

1. A data migration method for a device, characterized in that, Applied to a first device, the method includes: In response to a data migration request, the user's personalized data is obtained, which represents the layout position of multiple settings items on the first interface of the first device; The personalized data is sent to the second device, and the personalized data is used by the second device to lay out the corresponding settings on the second interface.

2. The method according to claim 1, characterized in that, The layout positions of the multiple settings are represented by row numbers and column numbers, and the layout positions of the multiple settings are used for the second device to lay out the same settings at corresponding positions on the second interface.

3. The method according to claim 1 or 2, characterized in that, The method further includes: In response to the data migration request, obtain the interface layout strategy; The interface layout strategy is sent to the second device, and the interface layout strategy is used by the second device to perform corresponding processing based on the interface layout strategy when encountering a preset situation.

4. The method according to claim 3, characterized in that, The preset condition includes: the second device does not support the first setting among the plurality of settings.

5. The method according to claim 4, characterized in that, The second device may not support the first setting item for at least one of the following reasons: the hardware of the second device does not support the function corresponding to the first setting item; the identifier of the first setting item in the first device is inconsistent with the identifier of the setting item with the same function in the second device; or the function corresponding to the first setting item has not been authorized by the user in the second device.

6. The method according to claim 4 or 5, characterized in that, The interface layout strategy includes a first strategy or a second strategy. The first strategy is used to instruct the second device to reserve the position corresponding to the layout position of the first setting item on the second interface. The second strategy is used to instruct the second device to lay out a second setting item at the position corresponding to the layout position of the first setting item on the second interface. The second setting item does not belong to the plurality of setting items.

7. The method according to claim 6, characterized in that, The second setting is the setting that the user uses most frequently during a preset time period when using the first device; or, The second setting is the setting that the user last used while using the first device; or, The second setting is a setting that the second device supports but is not included in the plurality of settings.

8. The method according to any one of claims 1-7, characterized in that, The first interface is the control center interface, and the multiple settings include any one or more of the following: cellular switch, airplane mode switch, eye protection mode switch, do not disturb switch, silent switch, flashlight switch, auto rotate switch, mobile data switch, wireless LAN switch, Bluetooth switch, and HyperTerminal switch.

9. The method according to claim 8, characterized in that, The second interface is the control center interface.

10. The method according to any one of claims 1-9, characterized in that, The acquisition of user personalized data includes: The personalized data is generated based on the layout of the multiple settings items on the first interface; or, The personalized data is automatically generated based on the user's custom settings on the first interface.

11. The method according to any one of claims 1-10, characterized in that, The data migration request is a request to migrate data from the first device to the second device in the scenario of replacing a device with a new one.

12. The method according to claim 11, characterized in that, The method further includes: In response to the data migration request, application data is sent to the second device.

13. The method according to any one of claims 1-12, characterized in that, Sending the personalized data to the second device includes: The personalized data is sent directly to the second device; or, The personalized data is sent to the second device via a cloud server.

14. A data migration method for a device, characterized in that, Applied to a second device, the method includes: Receive personalized data from a user of a first device, wherein the personalized data represents the layout and position of multiple settings items on a first interface of the first device; The layout of settings on the second interface of the second device is determined based on the personalized data.

15. The method according to claim 14, characterized in that, The layout positions of the multiple settings items are represented by row numbers and column numbers. The step of laying out the settings items on the second interface of the second device based on the personalized data includes: At least one of the plurality of settings is arranged at a corresponding position on the second interface based on the personalized data.

16. The method according to claim 15, characterized in that, The second device supports the plurality of settings, and the step of arranging at least one of the plurality of settings at a corresponding position on the second interface according to the personalized data includes: The multiple settings items are arranged at corresponding positions on the second interface based on the personalized data.

17. The method according to any one of claims 14-16, characterized in that, The method further includes: The interface layout strategy is received from the first device, and the interface layout strategy is used by the second device to perform corresponding processing based on the interface layout strategy when encountering a preset situation. When laying out the settings on the second interface of the second device based on the personalized data, if a preset situation is encountered, corresponding processing is performed based on the interface layout strategy.

18. The method according to claim 17, characterized in that, The preset conditions include: the second device does not support the first setting among the plurality of settings, and the interface layout strategy is the first strategy; The step of laying out the settings on the second interface of the second device according to the personalized data includes: laying out the other settings among the plurality of settings, excluding the first setting, at the corresponding positions on the second interface according to the personalized data; According to the first strategy, the position corresponding to the layout position of the first setting item on the second interface is used as a reserved position.

19. The method according to claim 17, characterized in that, The preset conditions include: the second device does not support the first setting among the plurality of settings, and the interface layout strategy is the second strategy; The step of laying out the settings on the second interface of the second device according to the personalized data includes: laying out the other settings among the plurality of settings, excluding the first setting, at the corresponding positions on the second interface according to the personalized data; According to the second strategy, a second setting item is placed at the position corresponding to the layout position of the first setting item on the second interface, and the second setting item does not belong to the plurality of setting items.

20. The method according to claim 19, characterized in that, The second setting is the setting that the user uses most frequently during a preset time period when using the first device; or, The second setting is the setting that the user last used while using the first device; or, The second setting is a setting that the second device supports but is not included in the plurality of settings.

21. The method according to any one of claims 18-20, characterized in that, The second device may not support the first setting item for at least one of the following reasons: the hardware of the second device does not support the function corresponding to the first setting item; the identifier of the first setting item in the first device is inconsistent with the identifier of the setting item with the same function in the second device; or the function corresponding to the first setting item has not been authorized by the user in the second device.

22. The method according to any one of claims 14-21, characterized in that, The first interface is the control center interface, and the multiple settings include any one or more of the following: cellular switch, airplane mode switch, eye protection mode switch, do not disturb switch, silent switch, flashlight switch, auto rotate switch, mobile data switch, wireless LAN switch, Bluetooth switch, and HyperTerminal switch.

23. The method according to claim 22, characterized in that, The second interface is the control center interface.

24. An electronic device, characterized in that, The electronic device includes: Memory is used to store computer program instructions; A processor for executing the computer program instructions to support the electronic device in implementing the method as described in any one of claims 1-13.

25. An electronic device, characterized in that, The electronic device includes: Memory is used to store computer program instructions; A processor for executing the computer program instructions to support the electronic device in implementing the method as described in any one of claims 14-23.

26. A data migration system, characterized in that, The system includes: The electronic device as claimed in claim 24, and the electronic device as claimed in claim 25.

27. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions that, when executed by a processing circuit, implement the method as described in any one of claims 1-13 or 14-23.

28. A computer program product containing instructions, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the method as described in any one of claims 1-13 or 14-23.

Images