Data migration method and device and storage medium

Abstract

The invention provides a data migration method and device and a storage medium. According to the method, after connection is established between first electronic equipment and second electronic equipment, the first electronic equipment generates a desktop icon temporary table under the condition that the second electronic equipment supports a resource library function, and the second electronic equipment performs data recovery based on the desktop icon temporary table. And the third interface and the fourth interface in the second electronic equipment are consistent with the icons in the first interface and the second interface in the first electronic equipment respectively, so that personalized migration of the use habits of the user is realized, and the user experience is improved.

Description

Technical Field

[0001] This application relates to the field of terminal equipment, and more particularly to a data migration method, device, and storage medium. Background Technology

[0002] With the continuous development of electronic device technology, smartphones, tablets, and other smart electronic devices have become indispensable products in people's daily lives, work, and entertainment. The rapid iteration of new functions and features has accelerated the pace of electronic device upgrades and replacements, and to some extent, increased the frequency with which users replace their electronic devices.

[0003] To ensure new electronic devices meet users' personalized needs and reduce the time required for adaptation, users typically migrate data from their old devices to the new ones when switching. However, current data migration methods fail to meet the demands of personalized data migration. In other words, even after the data migration is complete, users still need to readjust to the new electronic device. Summary of the Invention

[0004] This application provides a data migration method, device, and storage medium. During the data migration process, the method determines whether the personalized function resource library of the new device is supported. If the determination result is that it is supported, the desktop icon data of the old device is migrated in a personalized manner, so that the user's personalized usage habits on the desktop of the electronic device are migrated to the new electronic device, thereby improving the user experience.

[0005] In a first aspect, embodiments of this application provide a data migration method, the method comprising: establishing a connection between a first electronic device and a second electronic device, the first electronic device including a first interface and a second interface, the first interface and the second interface respectively containing icons of multiple applications, the number of icons in the first interface being greater than or equal to the number of icons in the second interface; the first electronic device acquiring a first identifier of the second electronic device, the first identifier being used to identify whether the second electronic device supports a resource library function; if it is determined that the first identifier supports the resource library function, the second electronic device including a third interface and a fourth interface, the third interface and the fourth interface respectively containing icons of multiple applications, the number of icons in the third interface being greater than or equal to the number of icons in the fourth interface; the first electronic device generating a temporary desktop icon table; the first electronic device migrating the temporary desktop icon table to the second electronic device; the second electronic device performing data recovery based on the temporary desktop icon table, so that the number of icons in the third interface is equal to the number of icons in the first interface, and the number of icons in the fourth interface is equal to the number of icons in the second interface.

[0006] For example, the first electronic device is a legacy electronic device in the following embodiments, and the second electronic device is a new electronic device in the following embodiments.

[0007] For example, the first interface can be the resource library interface of the first electronic device, such as... Figure 3 Interface 10b is shown in (2).

[0008] For example, the second interface can be the main interface of the first electronic device, such as... Figure 3 Interface 10a shown in (1), and Figure 6 The interface shown in (1) is shown in the middle.

[0009] It should be understood that if the user does not remove any icons from the main interface, the number of icons in the first interface is equal to the number of icons in the second interface; if the user removes any icons from the main interface, the number of icons in the first interface is greater than the number of icons in the second interface.

[0010] For example, the above-mentioned library function includes a library interface.

[0011] For example, after the first electronic device establishes a connection with the second electronic device, the first electronic device may actively obtain the first identifier of the second electronic device; or the second electronic device may actively send the first identifier to the first electronic device.

[0012] For example, the third interface could be the resource library interface of the second electronic device, such as... Figure 3 Interface 10b is shown in (2).

[0013] For example, the fourth interface can be the main interface of the first electronic device, such as... Figure 3 Interface 10a shown in (1), and Figure 6 The interface shown in (2) is shown in the middle.

[0014] Understandably, when the first electronic device generates a temporary table of desktop icons, it also generates the corresponding table data.

[0015] For example, the temporary desktop icon table contains information about all icons in the first interface, that is, it includes information about icons that have been removed from the second interface.

[0016] For example, no operation was performed on the icons of the first and second electronic devices during the cloning process. Therefore, the number of icons in the third interface is equal to the number of icons in the first interface, that is, the icons displayed in the third interface are completely identical to the icons displayed in the first interface (in terms of quantity and position); the number of icons in the fourth interface is equal to the number of icons in the second interface, that is, the icons displayed in the fourth interface are completely identical to the icons displayed in the second interface (in terms of quantity and position).

[0017] Therefore, after the first electronic device and the second electronic device establish a connection, the first electronic device generates a temporary table of desktop icons when the second electronic device supports the resource library function. The second electronic device then restores the data based on this temporary table of desktop icons, so that the icons of the third and fourth interfaces in the second electronic device are consistent with those of the first and second interfaces in the first electronic device, respectively. This achieves personalized migration of user habits and improves the user experience.

[0018] According to the first aspect, the field information of the desktop icon temporary table includes the icon, package name, container where the icon is located, and screen where the icon is located. The desktop temporary table contains all the icon information in the first interface.

[0019] According to the first aspect, or any implementation of the first aspect above, the first interface is the resource library interface of the first electronic device, and the second interface is the main interface of the first electronic device.

[0020] According to the first aspect, or any implementation of the first aspect above, the third interface is the resource library interface of the second electronic device, and the fourth interface is the main interface of the second electronic device.

[0021] According to the first aspect, or any implementation of the first aspect above, after the first electronic device migrates the desktop icon temporary table to the second electronic device, and the second electronic device performs data recovery based on the desktop icon temporary table, the method includes: deleting the desktop icon temporary table after the data recovery is completed.

[0022] According to the first aspect, or any implementation of the first aspect above, the method further includes: when it is determined that the first identifier does not support the resource library function, the second electronic device includes the fourth interface, and the first electronic device generates a desktop icon original table; the first electronic device migrates the desktop original table to the second electronic device, and the second electronic device performs data recovery based on the desktop icon original table, so that the number of icons in the four interfaces is equal to the number of icons in the second interface.

[0023] Understandably, if the first identifier indicates that the resource library function is not supported, then the second electronic device will not have a resource library interface, which means there will be no third interface.

[0024] For example, the original desktop icon table contains information about all icons in the second interface, but does not include information about icons that have been removed from the second interface.

[0025] Therefore, if the second electronic device does not support the resource library, the icons on the main interface of the first electronic device can be migrated to the second electronic device to achieve compatibility with the second electronic device, avoid display errors, and improve the user experience.

[0026] According to the first aspect, or any implementation of the first aspect above, the field information of the desktop original table includes the icon, package name, container where the icon is located, and screen where the icon is located, and the desktop original table contains all the icon information in the second interface.

[0027] According to the first aspect, or any implementation of the first aspect above, before the first electronic device and the second electronic device establish a connection, the method further includes: the first electronic device receiving a first operation applied to the second interface, the first operation being an icon removal operation; in response to the first operation, the first electronic device removing the selected icon from the second interface, such that the number of icons in the second interface is less than the number of icons in the first interface.

[0028] For example, the user interface corresponding to the first operation can be Figure 4 and Figure 5 The interface shown is for removing desktop icons.

[0029] Understandably, if an icon is removed from the second screen, the icon on the first screen will not be affected and will continue to be displayed on the first screen.

[0030] According to the first aspect, or any implementation of the first aspect above, the establishment of a connection between the first electronic device and the second electronic device includes: in response to a second operation performed on the first electronic device, the first electronic device enters a fifth interface, the fifth interface being a QR code scanning interface; in response to a third operation performed on the second electronic device, the second electronic device enters a sixth interface, the sixth interface including a QR code for connection; in response to a fourth operation performed on the first electronic device, the first electronic device enters a seventh interface, the fourth operation being to use the fifth interface for a QR code scanning operation on the sixth interface, the seventh interface being the interface for establishing a connection between the first electronic device and the second electronic device.

[0031] For example, the fifth interface can be referred to as the QR code scanning interface for old electronic devices, as illustrated in the diagram. Figure 9 Interface 40a is shown in (1).

[0032] For example, the sixth interface can be referred to as the connection interface of the new electronic device, as illustrated in the diagram. Figure 9 Interface 40b is shown in (2).

[0033] For example, the seventh interface can be called the connection status interface. This interface can be displayed when both the new and old electronic devices enter the connection state, to remind the user that the two electronic devices are currently connected. See the illustration for an example. Figure 9 Interface 40c is shown in (3).

[0034] According to the first aspect, or any implementation of the first aspect above, after the first electronic device and the second electronic device establish a connection, the method further includes: the first electronic device generating a desktop icon table, the desktop icon table including the temporary desktop icon table and the original desktop icon table; the first electronic device sending the desktop icon table to the second electronic device; if the second electronic device supports a resource library function, the second electronic device copying the temporary desktop icon table and performing data recovery based on the temporary desktop icon table, so that the number of icons in the third interface is equal to the number of icons in the first interface, and the number of icons in the fourth interface is equal to the number of icons in the second interface; if the second electronic device does not support a resource library function, the second electronic device copying the original desktop icon table and performing data recovery based on the original desktop icon table, so that the number of icons in the four interfaces is equal to the number of icons in the second interface; after the data recovery is completed, deleting the temporary desktop icon table.

[0035] Therefore, the first electronic device does not need to determine whether the second electronic device supports the resource library. It directly generates a temporary desktop icon table and a raw desktop icon table and sends them to the second electronic device. Upon receiving the temporary desktop icon table and the raw desktop icon table, the second electronic device determines whether it supports the resource library and then selects to copy the corresponding desktop icon table. This reduces data interaction between the old and new electronic devices and improves the stability of data cloning.

[0036] Secondly, embodiments of this application provide an electronic device. The electronic device includes: a memory and a processor, the memory and the processor being coupled; the memory stores program instructions, which, when executed by the processor, cause the electronic device to perform the methods of the first aspect or any possible implementation thereof.

[0037] Thirdly, embodiments of this application provide a computer-readable medium for storing a computer program, the computer program including instructions for performing the method in the first aspect or any possible implementation of the first aspect.

[0038] Fourthly, embodiments of this application provide a computer program including instructions for performing the method in the first aspect or any possible implementation thereof.

[0039] Fifthly, embodiments of this application provide a chip including a processing circuit and transceiver pins. The transceiver pins and the processing circuit communicate with each other via an internal connection path. The processing circuit executes the method in the first aspect or any possible implementation of the first aspect to control the receiving pin to receive signals and to control the transmitting pin to transmit signals. Attached Figure Description

[0040] Figure 1 A schematic diagram of the hardware structure of an electronic device as an example;

[0041] Figure 2 A schematic diagram of the software structure of an electronic device as an example;

[0042] Figure 3 The diagram illustrates the main interface and the resource library interface as an example.

[0043] Figure 4 This is an example of a user interface diagram showing a selected icon.

[0044] Figure 5 This is an example of a user interface diagram illustrating the removal of an icon;

[0045] Figure 6 This is an illustrative diagram of a machine replacement cloning process.

[0046] Figure 7 This is a schematic diagram illustrating the process of entering the machine swapping and cloning interface;

[0047] Figure 8 This is a schematic diagram illustrating the process of entering the machine swapping and cloning interface;

[0048] Figure 9 This is a schematic diagram of the user interface for the scanning connection, as exemplarily shown.

[0049] Figure 10 A user interface diagram illustrating data selection is shown as an example.

[0050] Figure 11 A user interface diagram illustrating data transmission is shown as an example.

[0051] Figure 12 A user interface diagram illustrating data transmission is shown as an example.

[0052] Figure 13 This is a schematic diagram illustrating the data cloning process as an example.

[0053] Figure 14 This is a schematic diagram illustrating the process of cloning a desktop icon as an example. Detailed Implementation

[0054] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0055] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0056] The terms "first" and "second," etc., used in the specification and claims of this application are used to distinguish different objects, not to describe a specific order of objects. For example, "first target object" and "second target object," etc., are used to distinguish different target objects, not to describe a specific order of target objects.

[0057] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0058] In the description of the embodiments in this application, unless otherwise stated, "multiple" means two or more. For example, multiple processing units means two or more processing units; multiple systems means two or more systems.

[0059] To facilitate understanding, the relevant terms involved in the embodiments of this application will be introduced below.

[0060] (1) Resource Library

[0061] The resource library is a display interface proposed in this application embodiment for centrally displaying all application icons on an electronic device.

[0062] In this display interface, the electronic device sorts and categorizes all application icons based on preset rules. Users can quickly find the icon of the application they need through the categories and launch the application by clicking the icon directly in the display interface. Users can also move the application icon from the display interface to the main screen of the electronic device by long-pressing or other interactive methods.

[0063] In addition, users cannot remove application icons or uninstall applications from the library interface.

[0064] (2) Main interface

[0065] In this embodiment, the main interface is the default interface displayed after the phone starts up, including shortcuts (icons and names) for multiple applications. The main interface may also include multiple sub-interfaces, such as the negative one screen or user extension interfaces.

[0066] In this interface, users can customize the display position and hierarchy of each application icon on the main screen according to their individual needs. Users can launch their corresponding application by directly clicking the icon. This interface also allows users to uninstall applications and remove their icons. Uninstalling an application will delete all files and entry points related to that application, including the application icon in the resource library. Removing the application icon will retain the application's files, and the application icon will still be displayed in the resource library, meaning users can still launch the application through the icon in the resource library.

[0067] (3) Cloning

[0068] Cloning, also known as "data migration" of electronic devices, refers to the process of transferring data from an old electronic device to a new one, allowing the new device to restore its data based on this data. Typically, cloning an electronic device imports all data from the old device into the new one, including desktop icons, contacts, text messages, photos, videos, and application data. This allows users to seamlessly transition to the new device and continue using it efficiently.

[0069] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended as the only limitation on this embodiment.

[0070] To better understand the technical solutions provided in the embodiments of this application, before describing the technical solutions of the embodiments of this application, the hardware structure of the electronic devices (e.g., mobile phones, tablet computers, touch-screen PCs, etc.) to which the embodiments of this application are applicable will first be described with reference to the accompanying drawings. For ease of explanation, Figure 1 Let's take a mobile phone as an example.

[0071] See Figure 1The mobile phone 100 may include: a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

[0072] The processor 110 may include one or more processing units, such as an application processor (AP), a modem, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU), etc., which will not be listed here and this application does not limit them.

[0073] The controller mentioned above, which serves as the processing unit, can be the central nervous system and command center of the mobile phone 100. In practical applications, the controller can generate operation control signals based on the instruction opcode and timing signals to control the fetching and execution of instructions.

[0074] The aforementioned modulation and demodulation processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal and transmits the demodulated low-frequency baseband signal to the baseband processor for processing.

[0075] The aforementioned baseband processor is used to process the low-frequency baseband signal transmitted by the regulator and then transmit the processed low-frequency baseband signal to the application processor.

[0076] It should be noted that in some implementations, the baseband processor can be integrated into the modem, meaning the modem can have the functionality of a baseband processor.

[0077] The aforementioned application processor is used to output sound signals through audio devices (not limited to speaker 170A, receiver 170B, etc.) or to display images or videos through display screen 194.

[0078] The aforementioned digital signal processor is used to process digital signals. Specifically, in addition to processing digital image signals, a digital signal processor can also process other digital signals. For example, when the mobile phone 100 is selecting a frequency point, the digital signal processor can be used to perform Fourier transforms on the frequency point energy, etc.

[0079] The aforementioned video codecs are used for compressing or decompressing digital video. For example, mobile phone 100 may support one or more video codecs. Thus, mobile phone 100 can play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG 2, MPEG 3, MPEG 4, etc.

[0080] The aforementioned ISP is used to output digital image signals to the DSP for processing. Specifically, the ISP is used to process the data fed back by the camera 193.

[0081] The DSP mentioned above is used to convert digital image signals into standard RGB, YUV, and other image signal formats.

[0082] Furthermore, it should be noted that, regarding the processor 110 including the aforementioned processing units, in some implementations, the different processing units can be independent devices. That is, each processing unit can be considered as a processor. In other implementations, the different processing units can also be integrated into one or more processors. For example, in some implementations, the modem processor can be an independent device. In other implementations, the modem processor can be independent of the processor 110 and housed in the same device as the mobile communication module 150 or other functional modules.

[0083] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended as the only limitation on this embodiment.

[0084] In addition, the processor 110 may also include one or more interfaces. These 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., which will not be listed here, and this application does not impose any limitations on them.

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

[0086] See also Figure 1 The external storage interface 120 can be used to connect an external storage card, such as a Micro SD card, to expand the storage capacity of the mobile phone 100. The external storage card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external storage card.

[0087] See also Figure 1The internal memory 121 can be used to store computer executable program code, which includes instructions. The processor 110 executes various functional applications and data processing of the mobile phone 100 by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application required for a function (such as sound playback function, image playback function, and the cloning function of the electronic device mentioned in this embodiment), etc. The data storage area may store data created during the use of the mobile phone 100 (such as application data that needs to be cloned in this embodiment, and temporary data generated during the cloning process), etc. In addition, the internal memory 121 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.

[0088] See also Figure 1 The charging management module 140 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging implementations, the charging management module 140 receives charging input from the wired charger via the USB interface 130. In some wireless charging implementations, the charging management module 140 receives wireless charging input via the wireless charging coil of the mobile phone 100. While charging the battery 142, the charging management module 140 can also supply power to the electronic device via the power management module 141.

[0089] See also Figure 1 The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the processor 110, internal memory 121, external memory, display 194, camera 193, and wireless communication module 160, etc.

[0090] See also Figure 1 The wireless communication function of mobile phone 100 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor.

[0091] See also Figure 1The audio module 170 may include a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, etc. For example, the mobile phone 100 can implement audio functions through the application processor and the speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, etc. in the audio module 170. Examples include recording and video recording functions.

[0092] See also Figure 1 The sensor module 180 may include pressure sensors, gyroscope sensors, barometric pressure sensors, magnetic sensors, accelerometers, distance sensors, proximity sensors, fingerprint sensors, temperature sensors, touch sensors, ambient light sensors, bone conduction sensors, etc., which will not be listed here, and this application does not limit them.

[0093] See also Figure 1 The buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch buttons. The mobile phone 100 can receive button input and generate button signal inputs related to the user settings and function control of the mobile phone 100.

[0094] See also Figure 1 Motor 191 can generate vibration alerts. Motor 191 can be used for incoming call vibration alerts or for touch vibration feedback.

[0095] See also Figure 1 The indicator 192 can be an indicator light, which can be used to indicate charging status, power changes, messages, missed calls, notifications, etc.

[0096] See also Figure 1 The camera 193 is used to capture still images or videos. The mobile phone 100 can achieve shooting functions through the ISP, camera 193, video codec, GPU, display 194, and application processor.

[0097] See also Figure 1 The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. In some implementations, the mobile phone 100 may include one or N displays 194, where N is a positive integer greater than 1. The mobile phone 100 can implement display functions through a GPU, the display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. The processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0098] That concludes the introduction to the hardware structure of the Mobile 100. It should be understood that... Figure 1The mobile phone 100 shown is just an example. In a specific implementation, the mobile phone 100 may have more or fewer components than shown in the figure, may combine two or more components, or may have different component configurations. Figure 1 The various components shown can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0099] To better understand Figure 1 The software structure of the mobile phone 100 shown is described below. Before describing the software structure of the mobile phone 100, the possible architectures for the software system of the mobile phone 100 will be explained first.

[0100] Specifically, in practical applications, the software system of Mobile 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture.

[0101] Furthermore, it is understood that the software systems used by mainstream electronic devices currently include, but are not limited to, Windows, Android, and iOS systems. For ease of explanation, this application embodiment uses the layered architecture of the Android system as an example to illustrate the software structure of the electronic device 100.

[0102] Furthermore, the data migration schemes provided in the embodiments of this application are also applicable to other systems in specific implementations.

[0103] See Figure 2 This is a software structure block diagram of the mobile phone 100 according to an embodiment of this application.

[0104] like Figure 2 As shown, the layered architecture of the mobile phone 100 divides the software into several layers, each with a clear role and division of labor. Layers communicate with each other through software interfaces. In some implementations, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0105] The application layer can include a series of application packages. For example... Figure 2 As shown, the application package may include clone, app store, video, shopping, permission management, Bluetooth, Wi-Fi, settings and other applications, which will not be listed here and this application does not limit them.

[0106] The application framework layer provides application programming interfaces (APIs) and programming frameworks for applications within the application layer. In some implementations, these APIs and frameworks can be described as functions. For example... Figure 2 As shown, the application framework layer may include functions such as a view system, a content provider, a speech recognition module, a wake word / command word detection module, a scene recognition module, a speech data fusion module, a speech activity detection module, a voiceprint verification module, and a wake word voiceprint template management module. These will not be listed here, and this application does not impose any restrictions on them.

[0107] It should be understood that the above description is merely an example provided to better understand the technical solution of this embodiment, and is not intended as the only limitation on this embodiment.

[0108] Furthermore, it is understood that the above division of functional modules is merely an example provided to better understand the technical solution of this embodiment, and is not intended to be the sole limitation of this embodiment. In practical applications, the above functions can also be integrated into a single functional module, and this embodiment does not impose any restrictions on this.

[0109] Furthermore, in practical applications, the aforementioned functional modules can also be represented as services or frameworks. For example, a speech recognition module can be represented as a speech recognition service or a speech recognition framework. This embodiment does not impose any restrictions on this.

[0110] In addition, it should be noted that the window manager, located in the application framework layer, is used to manage window applications. The window manager can obtain the screen size, determine whether there is a status bar, lock the screen, and capture the screen, etc.

[0111] Furthermore, it should be noted that the content provider located in the application framework layer is used to store and retrieve data, making this data accessible to the application. This data may include desktop icons, videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc., which will not be listed here, and this application does not impose any limitations on this.

[0112] Furthermore, it should be noted that the view system described above, located in the application framework layer, includes visual controls, such as controls for displaying text and controls for displaying images. The view system can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text notification icon could include views for displaying text and views for displaying images.

[0113] Furthermore, it should be noted that the phone manager located in the application framework layer is used to provide communication functions for mobile phone 100, such as call status management (including call connection, call termination, etc.).

[0114] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, etc., which will not be listed here, and this application does not impose any restrictions on them.

[0115] In addition, it should be noted that the notification manager located in the application framework layer allows the application to display notification information in the status bar. It can be used to convey informational messages and can disappear automatically after a short time without user interaction.

[0116] The Android Runtime consists of core libraries and a virtual machine. The Android Runtime is responsible for the scheduling and management of the Android system.

[0117] The core library consists of two parts: one part is the functionalities that need to be called by the Java language, and the other part is the Android core library.

[0118] The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0119] System libraries can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), etc.

[0120] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0121] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

[0122] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0123] Understandably, the 2D graphics engine mentioned above is a 2D drawing engine.

[0124] Furthermore, it is understandable that the kernel layer in the Android system is the layer between hardware and software. The kernel layer includes at least display drivers, camera drivers, audio drivers, sensor drivers, etc. For example, a sensor driver can be used to output detection signals from sensors (such as touch sensors) to the view system, so that the view system responds to the detection signals and displays the corresponding application interface.

[0125] This concludes the introduction to the software structure of electronic device 100. It is understandable that... Figure 2 The layers in the illustrated software structure and the components contained in each layer do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer layers than illustrated, and each layer may include more or fewer components; this application does not impose any limitations.

[0126] With the continuous development of electronic device technology, smartphones, tablets, and other smart electronic devices have become indispensable products in people's daily lives, work, and entertainment. Typically, to facilitate user operation, electronic devices provide multiple application entry points on the main interface. Users can quickly launch and display the application interface by interacting with these entry points on the main interface.

[0127] For example, Figure 3 Figure (1) shows the main interface 10a of the electronic device. This interface 10a includes icons and names of multiple applications, including clock, email, gallery, memo, video, fitness, weather, browser, settings, voice recorder, reading A and chat B.

[0128] Understandably, in this interface 10a, clicking the icon of the aforementioned application can quickly launch the corresponding application, thereby displaying the application's interface.

[0129] However, with the rapid development of applications, the number of applications installed on users' electronic devices is increasing, which undoubtedly leads to a cluttered main interface and greatly reduces user operability. Therefore, in order to improve user efficiency, this application embodiment also provides a resource library function (i.e., a resource library interface), which automatically categorizes the icons of user-installed applications into the resource library, and provides a function to remove application icons on the main interface, keeping the main interface clean and improving user efficiency.

[0130] Users can swipe up on the main interface 10a, and the electronic device responds to this action to enter the resource library interface.

[0131] For example, Figure 3Figure (2) shows a resource library interface 10b for an electronic device. This interface 10b includes all applications installed on the electronic device, provides a search bar at the top, and places icons of frequently used applications in the top "Frequently Used" column. It also intelligently categorizes and displays each application, greatly improving the user's efficiency.

[0132] Understandably, on electronic devices that support an app library, users can remove the icon of any application from the main screen, and the icon of the removed application will still be displayed in the app library. However, when a user uninstalls an application from the main screen, the application icon will also be deleted from the app library.

[0133] Optionally, after removing an application icon from the main interface, users can long-press the corresponding icon in the resource library and drag it back to the main interface to redisplay the removed icon.

[0134] To help users understand the process of removing application icons in the main interface 10a, the following explanation, in conjunction with accompanying drawings, illustrates the process.

[0135] See also Figure 3 In the middle (1), under normal circumstances, there are two ways for users to remove icons in the main interface 10a. Method 1: By long-pressing the target icon and selecting "remove" in the pop-up box, the target icon can be removed. Method 2: By moving two fingers toward each other in the main interface 10a, the electronic device enters the icon batch operation interface, and multiple icons can be removed at the same time in this interface. Here, we will explain the icon removal operation using method 2. When the user moves two fingers toward each other in the main interface 10a, the electronic device responds to this operation and enters the icon batch operation interface, which displays as follows. Figure 4 Interface 20a is shown in (1).

[0136] Figure 4 Figure (1) shows a user interface 20a for batch icon operations. This interface 20a includes a middle page operation bar 20a-1, a right-side page operation bar 20a-2, a left-side page operation bar 20a-3, and a bottom toolbar 20a-4. Each page operation bar displays the corresponding application icon from the interface.

[0137] For example, the middle page operation bar 20a-1 displays icons for multiple applications, including an icon for Reading A, an icon for Chat B 20a-5, etc.

[0138] After the user clicks icon 20a-5 in the middle page operation bar 20a-1 and selects the icon for chat application B, the following will be displayed: Figure 4Interface 20b is shown in (2).

[0139] Figure 4 Figure (2) shows the user interface 20b after the user selects an icon. In this interface 20b, the upper left corner of the application icon after being clicked by the user will display a selection control to indicate that the icon has been selected.

[0140] For example, after a user selects icon 20a-5 in interface 20a, a selection control appears in the upper left corner of interface 20b. Simultaneously, after a user selects icon 20b-1 in interface 20b, the application reads icon A, and a selection indicator appears in its upper left corner.

[0141] When a user long-presses one of the selected icons and drags it upwards on the electronic device, the device displays the icon operation interface, such as... Figure 5 Interface 20c is shown in (1).

[0142] Figure 5 Figure (1) shows the icon operation interface 20c. In this interface 20c, when the user long-presses a selected icon, other selected icons will dynamically overlap below the icon layer. As the user's finger moves up, the top of the electronic device displays the share control 20c-1 and the remove control 20c-2.

[0143] Optionally, in this interface 20c, users can share the selected application with others by dragging the selected icon to the sharing control 20c-1.

[0144] Optionally, the sharing control 20c-1 can be implemented by calling the interface provided by the chat software on the electronic device to share the application.

[0145] In one application scenario, the user can also drag the selected icon onto the removal control 20c-2. In response to this operation, the electronic device will display a removal confirmation dialog box at the bottom of the screen, showing... Figure 5 Interface 20d is shown in (2).

[0146] Figure 5 (2) shows the user interface 20d for the removal confirmation. The interface 20d includes a bottom pop-up box 20d-1, which includes: a title “Remove 2 apps?”, an instruction “Remove from desktop” will keep the app in the library, the icon and name of the selected app, an uninstall button, a remove button 20d-2, and a cancel button.

[0147] Optionally, in this interface 20d, when the user clicks the uninstall button, the electronic device responds to the operation and uninstalls the selected application. After the uninstallation is completed, all files and information of the selected application, including the icon in the resource library, will be deleted from the electronic device.

[0148] Optionally, in this interface 20d, when the user clicks the cancel button, the electronic device responds to the operation and cancels the operation.

[0149] In one application scenario, the user may also click the remove button 20d-2. In response, the electronic device will remove the selected application's icon from the main screen but retain it in the resource library. The display interface in the resource library can be found in [reference needed]. Figure 3 The interface 10b shown in (2) shows the main interface after the icon is removed, as follows: Figure 6 The interface shown in (1) is shown in the middle.

[0150] Therefore, in comparison Figure 3 Interface 10b shown in (2) and Figure 6 As shown in the interface in (1), it can be observed that as the user adjusts the electronic device, the number of icons on the main interface will be less than the number of icons on the resource library interface. The electronic device achieves a clean and tidy main interface for the user during daily use, as well as the need to open the target application in the resource library in specific scenarios, greatly improving the user experience.

[0151] However, as electronic devices are upgraded, users will also replace them with new ones. When users switch to a new electronic device, if they cannot migrate their settings from the old device to the new one, especially if the personalized usage methods of the main interface and resource library interface mentioned above cannot be migrated, users may have to spend a lot of time and effort to readjust and adapt on the new phone, which greatly reduces the user experience.

[0152] In view of this, in order to make the new electronic device more user-friendly, this application also provides a data migration method. During the data migration process of the old electronic device, the method verifies whether the new electronic device supports the resource library. If the verification is successful, the resource library and desktop icons on the main interface of the old electronic device are migrated to the new electronic device through a temporary desktop icon table. If the verification fails, the original desktop icon table is used to migrate only the desktop icons on the main interface of the old electronic device to the new electronic device. This achieves the purpose of migrating the user's personalized usage habits on the desktop of the electronic device to the new electronic device, greatly improving the user experience.

[0153] For example, see Figure 6 , Figure 6A schematic diagram of an electronic device cloning is shown. Figure 6 The electronic device O100 shown in (1) is an old electronic device. Figure 6 The electronic device N100 shown in (2) is a new electronic device.

[0154] After the data migration of the electronic devices is completed, users want the main interface and resource library in the new electronic device N100 to be consistent with those in the old electronic device O100. In other words, users want the main interface of the new electronic device N100 to be like... Figure 6 The user interface shown in (2) is consistent.

[0155] To facilitate understanding of the data cloning process between a user's new electronic device and an old electronic device, the data cloning process in the embodiments of this application is described below with reference to the accompanying drawings.

[0156] See Figure 7 Middle (1), Figure 7 Figure (1) shows the main interface 30a of the electronic device. In this interface 30a, when the user clicks icon 30a-1, the electronic device responds to this operation and enters the settings interface, displaying, as shown below. Figure 7 Interface 30b is shown in (2).

[0157] Figure 7 Figure (2) shows the settings interface 30b of the electronic device. This interface 30b displays various settings functions for the electronic device, including biometrics and password, applications, battery, users and accounts, system and updates 30b-1, about the phone, etc. Among these, system and updates 30b-1 includes the "swap device cloning" function required in this embodiment. When the user clicks on system and updates 30b-1, the electronic device responds to this operation by displaying, as shown in Figure (2). Figure 8 Interface 30c is shown in (1).

[0158] See Figure 8 Middle (1), Figure 8 The system and update settings interface 30c is shown in Figure (1). This interface 30c displays several functions related to the system and updates, including software updates, machine clone 30c-1, backup and recovery, etc.

[0159] In this embodiment, the user needs to migrate data from the old electronic device to the new electronic device. Therefore, the user clicks on the device swapping / cloning 30c-1, and the electronic device responds to this operation, entering the device swapping / cloning interface and displaying the following... Figure 8 Interface 30d is shown in (2).

[0160] Figure 8Figure (2) shows the device selection interface 30d for electronic device replacement and cloning. This interface 30d includes controls 30d-1 and 30d-2. Control 30d-1 is used to identify the currently operated electronic device as the old electronic device after the user clicks it; control 30d-2 is used to identify the currently operated electronic device as the new electronic device after the user clicks it.

[0161] It should be noted that during the device cloning process, users need to enable the device cloning function on both the new and old electronic devices simultaneously. Only by establishing a connection between the new and old electronic devices through the device cloning function can the data migration process be completed normally.

[0162] Therefore, users can access this interface 30d to operate new and old electronic devices, and select whether the currently operated electronic device is a new or old electronic device according to the prompts.

[0163] For example, when a user clicks control 30d-1 on interface 30d of electronic device O100, it indicates that the currently operated electronic device is an older device. Electronic device O100 then enters the QR code scanning interface and displays the following... Figure 9 Interface 40a is shown in (1).

[0164] Figure 9 Figure (1) shows the QR code scanning interface 40a of the old electronic device. When the electronic device O100 enters this interface 40a, the electronic device O100 will simultaneously turn on its rear camera, so that the interface 40a displays the image captured by the camera. At the same time, in order to remind the user that the camera needs to be pointed at the QR code interface provided by the new electronic device N100, a QR code scanning animation area 40a-1 is also displayed in this interface 40a. In this area 40a-1, the QR code scanning animation is played to remind the user that the QR code scanning operation needs to be performed.

[0165] For example, the scanning animation described above could be achieved by moving a thin line from top to bottom. The thin line could be a bright-colored line.

[0166] Optionally, to prevent users from being unable to establish a connection between the new and old electronic devices after scanning, this embodiment of the application provides a manual connection option at the bottom of the interface 40a, allowing users to manually complete the connection between the new and old electronic devices.

[0167] For example, when a user clicks control 30d-2 on interface 30d of electronic device N100, it indicates that the currently operating electronic device is a new electronic device. Electronic device N100 then enters the interface for connecting to the old device, displaying as shown below. Figure 9 Interface 40b is shown in (2).

[0168] Figure 9 Figure (2) shows the QR code interface 40b of the new electronic device. When the electronic device N100 enters this interface, it will simultaneously obtain the name and password of the currently connected WIFI and generate its corresponding QR code, which will be displayed in the QR code display area 40b-1. This allows the user to connect by pointing the camera of the old electronic device O100 at the QR code.

[0169] Optionally, the interface 40b may also display the name and password of the current Wi-Fi, allowing users to manually connect to the Wi-Fi and establish a connection between the new electronic device and the old electronic device.

[0170] Optionally, to make data migration more convenient for users, the connection between the new electronic device and the old electronic device in this application embodiment can be via direct WIFI connection, Bluetooth connection, or NFC touch connection. This application embodiment does not limit this.

[0171] After the old electronic device O100 scans the code, a connection is established between the new and old electronic devices, and both display the following: Figure 9 Interface 40c is shown in (3).

[0172] Figure 9 (3) shows the interface 40c for establishing a connection between electronic devices. While this interface 40c is displayed, electronic device O100 establishes a connection with electronic device N100.

[0173] Optionally, to enhance the security of users' personal information, during the connection establishment process between electronic device O100 and electronic device N100, electronic device O100 and electronic device N100 can also perform authentication separately. The authentication content includes, but is not limited to, whether the login account and password on the electronic devices are consistent.

[0174] Optionally, to prevent users from making erroneous operations due to not being able to obtain the current connection status during the connection process, the interface 40c can also indicate to the user that a connection is in progress by playing a connection animation. This connection animation could be an illustration of the electronic devices on the left and right sides of the interface 40c sending signal waves to each other.

[0175] It should be noted that during the connection establishment process between the new and old electronic devices, they will also exchange information after the connection is established. This information includes, but is not limited to, version information and whether the resource library is supported. Through this information exchange, the old electronic device can identify whether the new electronic device supports the resource library, thereby processing the data during the data preparation phase.

[0176] For example, the data processing includes, but is not limited to, creating a temporary table of desktop icons when the new electronic device supports a resource library, and creating an original table of desktop icons when the new electronic device does not support a resource library.

[0177] Optionally, the table fields of the temporary desktop icon table and the original desktop icon table include, but are not limited to, the icon of each application, package name, container of the icon, and screen information.

[0178] Optionally, the table data corresponding to the desktop icon temporary table can be the data corresponding to all icons in the resource library interface. For example, such as Figure 3 The data of all icons in interface 10b shown in (2)

[0179] Optionally, the table data corresponding to the original desktop icon table can be the data corresponding to all icons in the main interface. For example, such as... Figure 3 The data of all icons in interface 10a shown in (1), or as shown in (2) Figure 6 The main interface shown in (1) contains all the icon data.

[0180] Optionally, if the user does not remove any icons from the main interface, the number of icons in the resource library interface is equal to the number of icons in the main interface; if the user removes any icons from the main interface, the number of icons in the resource library interface is greater than the number of icons in the main interface.

[0181] After electronic device O100 and electronic device N100 establish a connection, electronic device O100 displays a data selection interface, showing, for example... Figure 10 Interface 50a is shown in (1).

[0182] Figure 10 Figure (1) shows a data selection interface 50a. This interface 50a includes a multi-select list and a "Next" control 50a-1. The multi-select list lists all applications that the user can clone. When the user selects the multi-select control corresponding to an application, the electronic device will back up the corresponding application data.

[0183] After the user completes the data selection and clicks the "Next" control 50a-1, the electronic device responds to the operation by displaying the following: Figure 10 The data migration description interface 50b is shown in (2).

[0184] Figure 10 (2) shows the data migration instruction interface 50b. This interface 50b displays the data migration instructions and the "Start Migration" control 50b-1.

[0185] After the user clicks control 50b-1, the electronic device O100 begins preparing data, displaying as shown below. Figure 10 The data preparation interface 50c shown in (3) is shown in the middle.

[0186] Figure 10 Figure (3) shows the user interface 50c for data preparation. In this interface 50c, the electronic device obtains the data volume of each selected application through the content provider in the application framework layer of the electronic device, thereby estimating the estimated time for sending data based on the statistical results, and displaying it in the interface 50c.

[0187] After the electronic device O100 completes data preparation, it will automatically enter the data transmission interface, displaying something like this. Figure 11 Interface 60a is shown in (1).

[0188] Figure 11 Figure (1) shows the user interface 60a of the data transmission process. This interface 60a includes a data transmission progress display 60a-1, data transmission details 60a-2, and an application data transmission list 60a-3. The data transmission progress display 60a-1 displays the percentage of the current overall data transmission progress; the data transmission details 60a-2 displays the current data transmission status; and the application data transmission list 60a-3 displays the currently transmitting application.

[0189] For example, after data transmission begins, the data transmission details 60a-2 will also display the amount of data currently transmitted, the current transmission rate, and the remaining transmission time, as shown below. Figure 11 Interface 60b is shown in (2). By displaying the above information, the user is reminded of the current status of the data migration, making it clear to the user that the data migration is in progress and improving the user experience.

[0190] In some possible scenarios, since users do not need to interact with electronic devices during data migration, in order to reduce the power consumption of electronic devices, in this embodiment of the application, the electronic device may also enter a black screen state after the data migration begins, displaying, as shown below. Figure 12 Interface 60c is shown in (1).

[0191] Figure 12 Figure (1) shows the energy-saving interface 60c during the data migration process. This interface 60c displays the current data migration status information and a user operation prompt 60c-1. The user operation prompt 60c-1 is displayed as "Tap to Return," reminding the user that clicking anywhere on the current interface will cause the electronic device to enter a screen-on state, displaying something like... Figure 11 Interface 60b is shown in (2).

[0192] Optionally, no user operation is required on the new electronic device during the data migration process. Therefore, the new electronic device can display a data receiving interface, a black screen, or the main interface. The data receiving interface and the black screen can simultaneously display the data receiving progress; their interfaces can be found in [reference needed]. Figure 11 Interface 60b shown in (2) or Figure 12 The interface 60c shown in (1) is not limited in this embodiment of the application.

[0193] After the data transmission is complete, the old electronic device will also display a completion screen, such as... Figure 12 Interface 60d is shown in (2).

[0194] Figure 12 Figure (2) shows the user interface 60d after data transmission is completed. This interface 60d displays a message indicating that data transmission is complete. After the user clicks the "OK" control, the old electronic device returns to the main interface, and the user can then use the old electronic device normally.

[0195] Simultaneously, after the data transmission is complete, the new electronic device will parse the data sent by the old electronic device in the background and restore it. After data restoration, the main interface will be refreshed to display the cloned interface, such as... Figure 6 The interface shown in (2) is shown in the middle.

[0196] Therefore, during the data migration process from the old electronic device to the new electronic device, the system can verify whether the new electronic device supports the resource library. If the verification is successful, the resource library and desktop icons on the main interface of the old electronic device can be migrated to the new electronic device using a temporary desktop icon table. If the verification fails, the original desktop icon table can be used to migrate only the desktop icons on the main interface of the old electronic device to the new electronic device. This achieves the goal of migrating users' personalized usage habits on the desktop of the old electronic device to the new electronic device, greatly improving the user experience.

[0197] To better understand the data migration method provided in this application, which involves migrating data from an old electronic device to a new electronic device via data cloning, the following example uses a mobile phone as an example, where the first electronic device is the old electronic device (O100), the second electronic device is the new electronic device (N100), and both the old and new electronic devices are mobile phones.

[0198] See Figure 13 , Figure 13 The data migration process described in this application embodiment includes:

[0199] Step S101: The first electronic device enters the cloning scanning interface.

[0200] For example, the first electronic device mentioned above is an old electronic device O100, and the cloned QR code scanning interface can be found in [reference needed]. Figure 9 Interface 40a is shown in (1).

[0201] Before the first electronic device enters the cloning scanning interface, the user needs to access the system and update interface through the settings interface on the first electronic device, and then access the device replacement cloning interface through the system and update interface. In the device replacement cloning interface, the user must select "This is the old device," which means... Figure 7 and Figure 8 The diagram shows how to access the cloning QR code scanning interface.

[0202] In step S102, the second electronic device displays the connection QR code interface.

[0203] For example, the second electronic device mentioned above is a new electronic device N100, and the connection QR code interface can be found here. Figure 9 Interface 40b is shown in (2). In this interface, the second electronic device displays the connection method currently available for establishing a communication channel with the first electronic device in the form of a QR code, which is used to establish a connection between the two devices after the first electronic device scans the code.

[0204] Optionally, the connection between the first electronic device and the second electronic device can be established through methods including but not limited to Wi-Fi, Bluetooth, and NFC touch connection.

[0205] In step S103, the first electronic device uses the clone scanning interface to scan the connected QR code interface to establish a connection between the first electronic device and the second electronic device.

[0206] For example, during the process of establishing a connection between the first electronic device and the second electronic device, the interfaces of the first electronic device and the second electronic device can display as follows: Figure 9 Interface 40c is shown in (3).

[0207] Optionally, during the connection establishment process, the first electronic device and the second electronic device can also perform mutual authentication. The authentication methods include, but are not limited to, whether the login account and password in the electronic device are consistent.

[0208] In step S104, the second electronic device sends version information and whether resource library information is supported to the first electronic device.

[0209] For example, after establishing a connection, the second electronic device sends version information and whether it supports the resource library to the first electronic device.

[0210] Step S105: The first electronic device identifies whether the second electronic device supports the resource library.

[0211] For example, the first electronic device can determine whether the second electronic device supports library identification. After identification is completed, the first electronic device can choose whether to perform the library cloning step during the subsequent cloning process.

[0212] In step S106, the first electronic device displays a list of cloneable applications.

[0213] An example list of cloneable applications is as follows: Figure 10 Interface 50a is shown in (1). In this interface 50a, "Select All" is displayed by default. Users can also deselect some of the selected applications according to their own needs, so that they are not cloned during the cloning process.

[0214] In step S107, the first electronic device responds to the user's operation and obtains the list of applications that the user has selected to clone.

[0215] For example, the above user operation could be the user clicking control 50a-1 in interface 50a, and Figure 10 The operation of control 50b-1 in interface 50b shown in (2) is as follows. After the user completes the above click operation, the application that the user needs to clone can be determined, thereby determining the list of cloned applications.

[0216] Step S108: The first electronic device generates resource identifiers (URIs) corresponding to the data of each application in the application list.

[0217] For example, the process of generating resource identifiers described above can be understood as a data preparation process for the first electronic device, whose user interface is as follows: Figure 10 Interface 50c is shown in (3).

[0218] Step S109: The first electronic device generates backup data and completes the data backup.

[0219] For example, after generating the resource identifier, the first electronic device will query the data of the corresponding application based on the identifier and back up the data.

[0220] For example, in the case where the second electronic device supports a resource library, the first electronic device will list all applications in the first electronic device based on the resource identifier.

[0221] In step S110, the first electronic device sends backup data to the second electronic device.

[0222] Specifically, after the data backup is complete, the first electronic device will send data to the second electronic device through the previously established connection. The user interface corresponding to the data transmission process is as follows: Figure 11 Middle (1) Figure 11 Zhong (2) and Figure 12The interface shown in (1) is shown in the middle.

[0223] Step S111: The second electronic device receives the backup data.

[0224] Specifically, the second electronic device will synchronously receive the data sent by the first electronic device. After the data transmission is complete, the first electronic device will display... Figure 12 Interface 60d is shown in (2).

[0225] In step S112, the second electronic device restores the application data of each application from the backup data.

[0226] Specifically, the second electronic device will restore the application data of each application from the backup data, including installed applications and generated historical data.

[0227] In step S113, the second electronic device completes data recovery and updates the main interface and resource library.

[0228] Specifically, after completing data recovery, the second electronic device will update its main interface and resource library interface, displaying, as follows: Figure 6 The interface shown in (2) and Figure 3 Interface 10b is shown in (2).

[0229] Therefore, by verifying whether the new electronic device supports the resource library during the data migration process of the old electronic device, and after the verification is passed, the resource library and desktop icons of the main interface of the old electronic device are migrated to the new electronic device through a temporary desktop icon table. This achieves the goal of migrating the user's personalized usage habits on the desktop of the old electronic device to the new electronic device, greatly improving the user experience.

[0230] To further illustrate the resource library data processing steps during the cloning process, the first electronic device will still be the old electronic device O100, and the second electronic device will be the new electronic device N100. Figure 14 The process will be explained.

[0231] See Figure 14 , Figure 14 The resource library data migration process according to this application embodiment includes:

[0232] In step S201, the cloning process of the first electronic device calls the desktop cloning entry point and triggers a desktop cloning request.

[0233] Specifically, after the user triggers the cloning (i.e., in situations such as...) Figure 10When the "Start Migration" button (control 50b-1) is clicked in the interface 50b shown in (2), the first electronic device enters the data preparation stage. Among them, when the first electronic device clones the icons on the desktop (i.e. the main interface), it calls the desktop provider.call cloning entry point to trigger the desktop cloning request.

[0234] Optionally, when the cloning process calls the desktop provider.call cloning entry point, relevant parameters can also be passed in, which are used to identify that the cloning request at this time is a desktop cloning request.

[0235] In step S202, the content provider of the first electronic device parses the cloning request, enters the mobile phone query process, and obtains the query results.

[0236] Specifically, after parsing the desktop cloning request, the content provider process processes the request, enters the old phone query process, and returns relevant desktop information. This information includes, but is not limited to, whether the new electronic device is in this resource library.

[0237] The query results include, but are not limited to, the URIs of applications displayed on the desktop (i.e., the main interface) of old electronic devices, as well as the URIs of applications whose icons have been removed from the desktop.

[0238] Step S203: Based on the query results, generate a desktop icon table, which includes a temporary desktop icon table and an original desktop icon table.

[0239] Optionally, the desktop icon table mentioned above includes a temporary desktop icon table and a raw desktop icon table. The field information of the desktop icon table includes, but is not limited to, the icon of each application, package name, container where the icon is located, and screen information.

[0240] For example, the container where the application icon is located can be the folder where the icon is located, and the screen where the icon is located is the screen information, including the negative one screen, the main screen, the second screen, etc.

[0241] The desktop temporary table can be created only if it is determined that a new electronic device supports the resource library; the desktop original table can be created by default.

[0242] In step S204, the content provider of the first electronic device returns the desktop icon table to the cloning process of the first electronic device.

[0243] Step S205: The cloning process of the first electronic device queries table data based on the desktop icon table.

[0244] Specifically, the cloning process of the first electronic device obtains the data required for the desktop icon table based on the URI corresponding to each application.

[0245] In step S206, the content provider of the first electronic device adds data to the desktop icon table to complete the data backup.

[0246] Specifically, the first electronic device adds the icon and other data of the applications whose icons have been removed to the original desktop icon table. The data fields include the application's icon, package name, the container where the icon is located, and the screen information where it is located. The first electronic device adds the icon and other data of all applications to the temporary desktop icon table.

[0247] In other words, the data in the temporary desktop icon table is the full data, while the data in the original desktop icon table is the data after filtering out icons removed by the user.

[0248] For example, the steps for a user to remove an icon can be referred to Figure 4 and Figure 5 The user interface shown.

[0249] In step S207, the cloning process of the first electronic device sends table data to the cloning process of the second electronic device.

[0250] Understandably, before the first electronic device sends data to the second electronic device, the cloning process of the first electronic device has already established a connection with the cloning process of the second electronic device. The steps for establishing this connection can be referred to... Figures 7 to 9 The user interface shown.

[0251] In step S208, the cloning process of the first electronic device sends the desktop icon table and table data to the cloning process of the second electronic device.

[0252] In step S209, the cloning process of the second electronic device receives the data and forwards it to the content provider of the second electronic device.

[0253] In step S210, the content provider of the second electronic device determines whether the second electronic device supports a resource library.

[0254] Step S211: If the judgment result is yes, copy the desktop icon temporary table.

[0255] Step S212: Restore the desktop based on the copied desktop temporary table data.

[0256] Step S213: After the recovery is complete, delete the temporary table of desktop icons.

[0257] Therefore, desktop data can be restored through a temporary desktop table, thus enabling the main interface of the second electronic device to be... Figure 6 The user interface shown in (2) is the resource library interface of the second electronic device. Figure 3 The user interface shown in (2) is shown in the middle.

[0258] Step S214: If the judgment result is negative, copy the original desktop icon table and restore the desktop based on the original desktop icon table.

[0259] This allows desktop data to be restored from the original desktop table, ensuring that the main interface of the second electronic device remains consistent with that of the first electronic device even if the second electronic device does not support a resource library.

[0260] Step S215, cloning complete.

[0261] Therefore, by verifying whether the new electronic device supports the resource library during the data migration process of the old electronic device, and after the verification is passed, the resource library and desktop icons of the main interface of the old electronic device are migrated to the new electronic device through a temporary desktop icon table. This achieves the goal of migrating the user's personalized usage habits on the desktop of the old electronic device to the new electronic device, greatly improving the user experience.

[0262] Furthermore, it is understood that, in order to achieve the aforementioned functions, the electronic device includes hardware and / or software modules corresponding to the execution of each function. Based on the algorithmic steps of the various 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 a hardware-driven or software-driven manner 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 in conjunction with the embodiments, but such implementation should not be considered beyond the scope of this application.

[0263] Furthermore, it should be noted that in practical application scenarios, the data migration methods provided in the above embodiments, implemented by electronic devices, can also be executed by a chip system included in the electronic device. This chip system may include a processor. The chip system can be coupled to a memory, enabling it to call a computer program stored in the memory during runtime to implement the steps executed by the electronic device. The processor in the chip system can be an application processor or a non-application processor.

[0264] In addition, this application embodiment also provides a computer-readable storage medium storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device performs the above-described related method steps to implement the data migration method in the above embodiment.

[0265] In addition, this application also provides a computer program product that, when run on an electronic device, causes the electronic device to perform the above-mentioned related steps to realize the data migration method in the above embodiments.

[0266] In addition, embodiments of this application also provide a chip (which may also be a component or module), the chip may include one or more processing circuits and one or more transceiver pins; wherein, the transceiver pins and the processing circuits communicate with each other through internal connection paths, the processing circuits execute the above-mentioned related method steps to implement the data migration method in the above embodiments, so as to control the receiving pin to receive signals and control the transmitting pin to transmit signals.

[0267] Furthermore, as can be seen from the above description, the electronic devices, computer-readable storage media, computer program products, or chips provided in the embodiments of this application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0268] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A data migration method, characterized in that, The method includes: A first electronic device establishes a connection with a second electronic device. The first electronic device includes a first interface and a second interface. The first interface and the second interface each contain icons of multiple applications. The number of icons in the first interface is greater than or equal to the number of icons in the second interface. The first electronic device acquires a first identifier of the second electronic device, the first identifier being used to identify whether the second electronic device supports the resource library function; If the first identifier is determined to support the resource library function, the second electronic device includes a third interface and a fourth interface, the third interface and the fourth interface respectively contain icons of multiple applications, the number of icons in the third interface is greater than or equal to the number of icons in the fourth interface, and the first electronic device generates a temporary desktop icon table. The first electronic device migrates the temporary desktop icon table to the second electronic device, and the second electronic device performs data recovery based on the temporary desktop icon table so that the number of icons in the third interface is equal to the number of icons in the first interface, and the number of icons in the fourth interface is equal to the number of icons in the second interface.

2. The method according to claim 1, characterized in that, The desktop icon temporary table includes fields for icon, package name, container where the icon is located, and screen where the icon is located. The desktop temporary table contains all icon information in the first interface.

3. The method according to claim 1, characterized in that, The first interface is the resource library interface of the first electronic device, and the second interface is the main interface of the first electronic device.

4. The method according to claim 1, characterized in that, The third interface is the resource library interface of the second electronic device, and the fourth interface is the main interface of the second electronic device.

5. The method according to claim 1, characterized in that, After the first electronic device migrates the temporary desktop icon table to the second electronic device, and the second electronic device performs data recovery based on the temporary desktop icon table, the process includes: After the data recovery is complete, delete the temporary table of desktop icons.

6. The method according to claim 1, characterized in that, The method further includes: If it is determined that the first identifier does not support the resource library function, the second electronic device includes the fourth interface, and the first electronic device generates the original table of desktop icons; The first electronic device migrates the original desktop table to the second electronic device, and the second electronic device performs data recovery based on the original desktop icon table so that the number of icons in the four interfaces is equal to the number of icons in the second interface.

7. The method according to claim 6, characterized in that, The field information of the original desktop table includes the icon, package name, container where the icon is located, and screen where the icon is located. The original desktop table contains all the icon information in the second interface.

8. The method according to claim 1, characterized in that, Before the first electronic device and the second electronic device establish a connection, the method further includes: The first electronic device receives a first operation applied to the second interface, the first operation being an icon removal operation; In response to the first operation, the first electronic device removes the selected icon from the second interface, so that the number of icons in the second interface is less than the number of icons in the first interface.

9. The method according to claim 1, characterized in that, The first electronic device establishes a connection with the second electronic device, including: In response to a second operation performed on the first electronic device, the first electronic device enters a fifth interface, which is a barcode scanning interface. In response to a third operation performed on the second electronic device, the second electronic device enters a sixth interface, which includes a QR code for connection. In response to a fourth operation performed on the first electronic device, the first electronic device enters a seventh interface. The fourth operation is to use the fifth interface for scanning a code on the sixth interface. The seventh interface is the interface through which the first electronic device and the second electronic device establish a connection.

10. The method according to claim 1, characterized in that, After the first electronic device and the second electronic device establish a connection, the method further includes: The first electronic device generates a desktop icon table, which includes a temporary desktop icon table and an original desktop icon table. The first electronic device sends the desktop icon list to the second electronic device; When the second electronic device supports the resource library function, the second electronic device copies the desktop icon temporary table and performs data recovery based on the desktop icon temporary table, so that the number of icons in the third interface is equal to the number of icons in the first interface, and the number of icons in the fourth interface is equal to the number of icons in the second interface. If the second electronic device does not support the resource library function, the second electronic device copies the original desktop icon table and performs data recovery based on the original desktop icon table so that the number of icons in the four interfaces is equal to the number of icons in the second interface. After the data recovery is complete, delete the temporary table of desktop icons.

11. An electronic device, characterized in that, The electronic device includes: a memory and a processor, the memory and the processor being coupled; the memory stores program instructions, which, when executed by the processor, cause the electronic device to perform the data migration method as described in any one of claims 1 to 10.

12. A computer-readable storage medium, characterized in that, The method includes a computer program that, when run on an electronic device, causes the electronic device to perform the data migration method as described in any one of claims 1 to 10.

Images