Display method of application icons and related apparatus

Abstract

The application provides a display method of an application icon and a related device, which is beneficial to intuitively understanding the import progress of the application by the user and improving the display effect of the application icon during data migration. The method comprises the following steps: when receiving migration data sent by a second terminal device, a first terminal device displays a first interface; when the first terminal device receives the migration data, the first terminal device starts to import the migration data; during the process of importing the migration data by the first terminal device, the first terminal device displays a second interface, and the second interface comprises a first control; in response to the operation of selecting the first control by the user, the first terminal device displays a first desktop, and the first desktop comprises a first icon of a first application and a first import progress of the first application; the icon state of the first application is a first state; when the import progress of the first application changes, the first terminal device updates the icon state of the first application to a second state in the first desktop.

Description

Technical Field

[0001] This application relates to the field of terminals, and more specifically, to a method and related apparatus for displaying application icons. Background Technology

[0002] When users upgrade to a new phone, they can use data migration apps to transfer data from their old phone to their new phone.

[0003] Currently, new mobile phones can provide users with an entry point to the desktop when migrating data. After entering the desktop, the desktop can display application icons, and users can see which applications are waiting to be imported.

[0004] However, users currently cannot intuitively understand the application's import progress, resulting in poor display effects during data migration. Summary of the Invention

[0005] This application provides a method and related apparatus for displaying application icons, which helps users intuitively understand the progress of application import and improves the display effect of application icons during data migration.

[0006] In a first aspect, a method for displaying an application icon is provided, the method comprising: establishing a connection between a first terminal device and a second terminal device; when the first terminal device receives migration data sent by the second terminal device, the first terminal device displays a first interface, the first interface including one or more of the following: the amount of migration data, the transmission progress, or the transmission time; after the first terminal device has finished receiving the migration data, the first terminal device begins to import the migration data; during the import of migration data, the first terminal device displays a second interface, the second interface including a first control; in response to a user's selection of the first control, the first terminal device displays a first desktop, the first desktop including a first icon of the first application and a first import progress of the first application, the icon state of the first application being a first state; when the import progress of the first application changes, the first terminal device updates the icon state of the first application in the first desktop to a second state, the second state including a second icon of the first application and a second import progress.

[0007] In this application, a first terminal device and a second terminal device establish a connection for data migration. The first terminal device is the receiving end of the migration data, and the second terminal device is the sending end of the migration data. Upon confirming receipt of the migration data, the first terminal device begins importing the migration data and displays a second interface to the user, providing a first control for accessing the desktop. After the user selects the first control, the first terminal device can import the migration data in the background and display a first desktop to the user. The first desktop can display the status of application icons, allowing the user to intuitively understand the import progress. This improves the display effect of application icons during data migration and enhances the user experience.

[0008] In conjunction with the first aspect, in some implementations of the first aspect, the first state includes a waiting-to-import state. When the import progress of the first application changes, the first terminal device updates the icon state of the first application to a second state on the first desktop, including: when the import progress of the first application changes from waiting to import to installing application, the first terminal device updates the icon state of the first application to an installing state on the first desktop.

[0009] In this application, the first terminal device can detect whether a first application is installed on the first terminal device. If the first application is not installed, the first terminal device can initiate the application installation, thus changing the import progress of the first application from "waiting to import" to "installing application." Accordingly, the first terminal device updates the icon status of the first application on the first desktop from "waiting to import" to "installing."

[0010] In conjunction with the first aspect, in some implementations of the first aspect, the first state includes a waiting-to-import state. When the import progress of the first application changes, the first terminal device updates the icon state of the first application on the first desktop to a second state, including: when the import progress of the first application changes from waiting to import to importing application data, the first terminal device updates the icon state of the first application on the first desktop to an importing state.

[0011] In this application, the first terminal device can detect whether a first application is installed on the first terminal device and whether there is application data for the first application. If the first application is installed and there is application data for the first application, the first terminal device can initiate the import of application data, thus changing the import progress of the first application from waiting to import to importing application data. Accordingly, the first terminal device updates the icon status of the first application on the first desktop from the waiting to import state to the importing state.

[0012] In conjunction with the first aspect, in some implementations of the first aspect, the first state includes a waiting-to-import state. When the import progress of the first application changes, the first terminal device updates the icon state of the first application on the first desktop to a second state, including: when the import progress of the first application changes from waiting to import to complete import, the first terminal device updates the icon state of the first application on the first desktop to an import-completed state.

[0013] In this application, the first terminal device can detect whether a first application is installed on the first terminal device and whether there is application data for the first application. If the first application is installed but there is no application data for the first application, the first terminal device determines that the import of the first application is complete, thus changing the import progress of the first application from "waiting to import" to "import complete". Accordingly, the first terminal device updates the icon status of the first application on the first desktop from "waiting to import" to "import complete".

[0014] In conjunction with the first aspect, in some implementations of the first aspect, the first state includes an installation state. When the import progress of the first application changes, the first terminal device updates the icon state of the first application on the first desktop to a second state, including: when the import progress of the first application changes from installing the application to importing application data, the first terminal device updates the icon state of the first application on the first desktop to an importing state.

[0015] In this application, upon completion of the installation of the first application, if the first terminal device determines that the application data for the first application exists, the first terminal device can initiate the import of the application data. This changes the import process from installing the application to importing application data. Accordingly, the first terminal device updates the icon status of the first application on its first desktop from the "Installing" state to the "Importing" state.

[0016] In conjunction with the first aspect, in some implementations of the first aspect, the first state includes an installation state. When the import progress of the first application changes, the first terminal device updates the icon state of the first application on the first desktop to a second state, including: when the import progress of the first application changes from installing the application to importing completed, the first terminal device updates the icon state of the first application on the first desktop to an import completed state.

[0017] In this application, upon completion of the installation of the first application, if the first terminal device determines that there is no application data for the first application, the first terminal device determines that the import of the first application is complete. Thus, the import progress of the first application changes from "installing application" to "import complete." Correspondingly, the first terminal device updates the icon status of the first application on the first desktop from "installing" to "import complete."

[0018] In conjunction with the first aspect, in some implementations of the first aspect, the first state includes an importing state. When the import progress of the first application changes, the first terminal device updates the icon state of the first application on the first desktop to a second state, including: when the import progress of the first application changes from importing application data to import completed, the first terminal device updates the icon state of the first application on the first desktop to an import completed state.

[0019] In this application, after importing the application data of the first application, the first terminal device can determine that the import of the first application is complete, thus changing the import progress of the first application from importing application data to importing complete. Accordingly, the first terminal device refreshes the icon status of the first application on the first desktop from the importing state to the import complete state.

[0020] In conjunction with the first aspect, in some implementations of the first aspect, the first terminal device includes an import module and a desktop module. When the import progress of the first application changes, the first terminal device updates the icon state of the first application to a second state on the first desktop, including: the first terminal device detecting the import progress of the first application through the import module; when a change in import progress is detected, the first terminal device sending a first broadcast to the desktop module through the import module, the first broadcast indicating an update to the icon state of the first application; the first terminal device receiving the first broadcast through the desktop module; and the first terminal device updating the icon state of the first application to the second state on the first desktop through the desktop module based on the first broadcast.

[0021] In this application, the import module is mainly responsible for installing the application and importing application data, refreshing the notification icon status, and broadcasting the import process heartbeat. The desktop module is mainly responsible for implementing the application icon's placeholder on the desktop and refreshing the icon status.

[0022] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first terminal device sending first instruction information to the desktop module through the import module, the first instruction information being used to indicate the position of the icon of the first application on the first desktop; the first terminal device receiving the first instruction information through the desktop module; and the first terminal device, based on the first instruction information, using the desktop module to place the icon of the first application on the first desktop.

[0023] In this application, the import module of the first terminal device can receive desktop layout information from the second terminal device. After obtaining the desktop layout information, the import module can send first instruction information to the desktop module, indicating the position of the icon of the first application on the desktop. Based on the first instruction information, the desktop module can place the icon of the first application on the first desktop (also known as icon placeholder). This makes the layout of application icons on the desktop more in line with user habits and improves the user experience.

[0024] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: when the first terminal device detects that the user operation is a predefined operation, clearing the icons of the target application from the first desktop, the target application including applications that have not been fully installed.

[0025] In this application, the predefined operations include clearing the cloned application or canceling the import process. For the user's predefined operations, the first terminal device can stop the application import and clear the icons of incompletely installed applications from the desktop. Since incompletely installed applications cannot be used normally by the user, clearing the icons of the target applications from the desktop helps to avoid interfering with the user's use of the application.

[0026] In conjunction with the first aspect, in some implementations of the first aspect, when the first terminal device has received all the migration data, the first terminal device initiates the import of migration data, including: the first terminal device receiving second indication information from the second terminal device, the second indication information being used to indicate that all migration data has been sent; and the first terminal device initiating the import of migration data based on the second indication information, after determining that all migration data has been received.

[0027] In a second aspect, an application icon display device is provided, comprising: a method for performing any possible implementation of the first aspect described above. Specifically, the device includes a module for performing the method in any possible implementation of the first aspect described above.

[0028] Thirdly, another application icon display device is provided, including a processor and a memory, the processor being coupled to the memory for storing computer programs, and the processor being able to call and execute the computer programs in the memory to implement the method in any of the possible implementations of the first aspect above.

[0029] In one implementation, the display device for the application icon is a first terminal device. When the display device for the application icon is a first terminal device, the communication interface can be a transceiver or an input / output interface.

[0030] In another implementation, the display device for the application icon is a chip configured in the first terminal device. When the display device for the application icon is a chip configured in the first terminal device, the communication interface can be an input / output interface.

[0031] Fourthly, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is used to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the method in any possible implementation of the first aspect described above.

[0032] In specific implementation, the processor can be a chip, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver; the signal output by the output circuit can be, for example, but not limited to, output to a transmitter and transmitted by the transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0033] Fifthly, a processing apparatus is provided, including a processor and a memory. The processor is used to read instructions stored in the memory and to receive signals via a receiver and transmit signals via a transmitter to execute the method in any of the possible implementations of the first aspect described above.

[0034] Optionally, there may be one or more processors and one or more memories.

[0035] Alternatively, the memory can be integrated with the processor, or the memory can be set separately from the processor.

[0036] In the specific implementation process, the memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or set on different chips. This application does not limit the type of memory or the way the memory and processor are set.

[0037] It should be understood that the relevant data interaction process, such as sending indication information, can be the process of outputting indication information from the processor, and receiving capability information can be the process of the processor receiving input capability information. Specifically, the processed output data can be output to the transmitter, and the input data received by the processor can come from the receiver. Here, the transmitter and receiver can be collectively referred to as a transceiver.

[0038] The processing device in the fifth aspect above can be a chip. The processor can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. The memory can be integrated into the processor or located outside the processor and exist independently.

[0039] In a sixth aspect, a computer program product is provided, comprising: computer program code, which, when executed, causes a computer to perform the method in any of the possible implementations of the first aspect described above.

[0040] In a seventh aspect, a computer-readable storage medium is provided that stores a computer program, which, when executed, causes a computer to perform the method in any of the possible implementations of the first aspect described above. Attached Figure Description

[0041] Figure 1 This is a schematic diagram of the structure of a terminal device to which this application embodiment applies;

[0042] Figure 2 This is a software structure block diagram of a terminal device to which the embodiments of this application are applicable;

[0043] Figure 3 This is a schematic diagram of an interface for entering the desktop provided in an embodiment of this application;

[0044] Figure 4 This is a schematic diagram of an interface for refreshing icon status provided in an embodiment of this application;

[0045] Figure 5 This is a schematic flowchart illustrating a method for displaying application icons provided in an embodiment of this application;

[0046] Figure 6 This is a schematic diagram of an icon status refresh provided in an embodiment of this application;

[0047] Figure 7 This is a schematic diagram of another interface for entering the desktop provided in an embodiment of this application;

[0048] Figure 8 This is a schematic diagram of an interface for displaying icon status provided in an embodiment of this application;

[0049] Figure 9 This is a schematic block diagram of an application icon display device provided in an embodiment of this application;

[0050] Figure 10 This is a schematic block diagram of another application icon display device provided in the embodiments of this application. Detailed Implementation

[0051] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0052] To facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with essentially the same function and purpose. For example, "first control" and "second control" are used to distinguish different controls and do not limit their order. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that "first" and "second" do not necessarily imply that they are different.

[0053] It should be noted that, in this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of words such as "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0054] Furthermore, "at least one" refers to one or more, while "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b, and c, where a, b, and c can be single or multiple.

[0055] Figure 1 This is a schematic diagram of the structure of a terminal device to which this application embodiment applies. For example... Figure 1 As shown, the terminal device 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 speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

[0056] It is understood that the structure illustrated in this embodiment does not constitute a specific limitation on the terminal device 100. In other embodiments of this application, the terminal device 100 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.

[0057] Processor 110 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, display processing units (DPUs), and / or neural network processing units (NPUs). Different processing units may be independent devices or integrated into one or more processors. In some embodiments, terminal device 100 may also include one or more processors 110. The processor may serve as the central nervous system and command center of terminal device 100. The processor can generate operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution. Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have been used or repeatedly used by processor 110. If processor 110 needs to reuse an instruction or data, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the terminal device 100.

[0058] In some embodiments, the processor 110 may 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 USB interface, etc. The USB interface 130 is a USB standard-compliant interface, specifically a Mini USB interface, a MicroUSB interface, a USB Type-C interface, etc. The USB interface 130 can be used to connect a charger to charge the terminal device 100, and can also be used for data transfer between the terminal device 100 and peripheral devices. It can also be used to connect headphones for audio playback.

[0059] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are illustrative and do not constitute a structural limitation on the terminal device 100. In other embodiments of this application, the terminal device 100 may also adopt different interface connection methods or a combination of multiple interface connection methods as described in the above embodiments.

[0060] The wireless communication function of terminal device 100 can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor, and baseband processor. Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in terminal device 100 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

[0061] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the terminal device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low-noise amplifier, etc. The mobile communication module 150 can receive electromagnetic waves via the antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via the antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0062] The modem 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. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 170A, receiver 170B, etc.) or displays images or videos through the display screen 194. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

[0063] The wireless communication module 160 can provide solutions for wireless communication applications on the terminal device 100, including wireless local area networks (WLAN), Bluetooth, global navigation satellite system (GNSS), frequency modulation (FM), NFC, and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0064] In some embodiments, antenna 1 of terminal device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling terminal device 100 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include GSM, GPRS, CDMA, WCDMA, TD-SCDMA, LTE, GNSS, WLAN, NFC, FM, and / or IR technology, etc. The aforementioned 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).

[0065] Terminal device 100 can realize display functions through GPU, display screen 194, and application processor. The application processor may include NPU and / or DPU. GPU is a microprocessor for image processing, connected to display screen 194 and application processor. GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute instructions to generate or modify display information. NPU is a neural network (NN) computing processor that, by borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, can quickly process input information and can continuously learn itself. Through NPU, terminal device 100 can realize intelligent cognitive applications, such as image recognition, face recognition, speech recognition, and text understanding. DPU, also known as display sub-system (DSS), is used to adjust the colors of display screen 194. DPU can adjust the colors of the display screen through a 3D look-up table (3D LUT). DPU can also perform image scaling, noise reduction, contrast enhancement, backlight brightness management, HDR processing, and Gamma adjustment of display parameters.

[0066] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-OLED, or a quantum dot light-emitting diode (QLED). In some embodiments, terminal device 100 may include one or N displays 194, where N is a positive integer greater than 1.

[0067] Terminal device 100 can perform shooting functions through ISP, one or more cameras 193, video codec, GPU, one or more displays 194, and application processor.

[0068] 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 terminal device 100. The external storage card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, data files such as music, photos, and videos can be saved on the external storage card.

[0069] Internal memory 121 can be used to store one or more computer programs, which include instructions. Processor 110 can execute the instructions stored in internal memory 121, thereby enabling terminal device 100 to perform various functional applications and data processing. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system; it may also store one or more application programs (such as a gallery, contacts, etc.). The data storage area may store data created during the use of terminal device 100 (such as photos, contacts, etc.). In addition, 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. In some embodiments, processor 110 can execute instructions stored in internal memory 121 and / or instructions stored in memory disposed in processor 110 to enable terminal device 100 to perform various functional applications and data processing.

[0070] Terminal device 100 can implement audio functions such as music playback and recording through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, and an application processor. The audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The audio module 170 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 170 can be located in the processor 110, or some functional modules of the audio module 170 can be located in the processor 110. The speaker 170A, also called a "loudspeaker," is used to convert audio electrical signals into sound signals. Terminal device 100 can listen to music or hands-free calls through the speaker 170A. The receiver 170B, also called a "handpiece," is used to convert audio electrical signals into sound signals. When terminal device 100 answers a phone call or voice message, it can listen to the voice by bringing the receiver 170B close to its ear. Microphone 170C, also known as a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can speak by bringing their mouth close to microphone 170C, inputting the sound signal into microphone 170C. Terminal device 100 may be equipped with at least one microphone 170C. In some embodiments, terminal device 100 may be equipped with two microphones 170C, which, in addition to collecting sound signals, can also perform noise reduction. In other embodiments, terminal device 100 may be equipped with three, four, or more microphones 170C, which can collect sound signals, reduce noise, identify the sound source, and perform directional recording, etc. Headphone jack 170D is used to connect wired headphones. Headphone jack 170D can be a USB interface 130, a 3.5mm Open Mobile Terminal Platform (OMTP) standard interface, or a CTIA (Cellular Telecommunications Industry Association of the USA) standard interface.

[0071] Sensor 180 may include pressure sensor 180A, gyroscope sensor 180B, barometric pressure sensor 180C, magnetic sensor 180D, accelerometer sensor 180E, distance sensor 180F, proximity sensor 180G, fingerprint sensor 180H, temperature sensor 180J, touch sensor 180K, ambient light sensor 180L, bone conduction sensor 180M, etc.

[0072] The terminal device in this application embodiment can be a handheld device, vehicle-mounted device, etc. with wireless connection function. The terminal device can also be called a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. Currently, examples of terminal devices include: mobile phones, tablets, smart TVs, laptops, tablets, handheld computers, mobile internet devices (MIDs), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or future public land mobile communication networks. Terminal devices in a mobile network (PLMN), etc., are not limited in the specific technologies and device forms used in the embodiments of this application.

[0073] By way of example and not limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0074] It should be understood that in the embodiments of this application, the terminal device can be a means for implementing the functions of the terminal device, or a means for supporting the terminal device in implementing the functions, such as a chip system, which can be installed in the terminal. In the embodiments of this application, the chip system can be composed of chips, or it can include chips and other discrete devices.

[0075] The terminal device in this application embodiment can also be referred to as: user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device, etc. The following description will use a mobile phone as an example of the terminal device.

[0076] The software system of terminal device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment uses a layered Android system as an example to exemplify the software structure of terminal device 100.

[0077] Figure 2 This is a software architecture block diagram of a terminal device to which this application embodiment applies. The layered architecture divides the software system of the terminal device 100 into several layers, each with a clear role and division of labor. Layers communicate with each other through software interfaces. In some embodiments, the Android system can be divided into an application layer (APP), an application framework layer, an Android runtime, system libraries, and a kernel layer.

[0078] The application layer can include a series of application packages. The application layer runs applications by calling the application programming interface (API) provided by the application framework layer.

[0079] like Figure 2 As shown, the application layer may include a user interface (UI) layer and a logic layer. The UI layer may include cloned applications, desktop management applications, and other applications. Other applications may include applications for camera, calendar, maps, phone, music, WLAN, Bluetooth, video, social networking, gallery, navigation, and SMS. The logic layer includes an import module and a desktop module. The terminal device 100 can implement the function of cloning applications through software functional modules (e.g., the import module). The terminal device 100 can implement the function of desktop management applications through software functional modules (e.g., the desktop module).

[0080] The application framework layer provides APIs and a programming framework for applications within the application layer. The application framework layer includes predefined functions. For example... Figure 2 As shown, the application framework layer may include application package manager service (PMS), activity manager service (AMS), backup manager service (BMS), etc.

[0081] PMS is used to manage and track the installation, parsing, and access control of application packages.

[0082] AMS is primarily responsible for starting, switching, and scheduling the four major components (provider, service, receiver, and activity) in the Android system, as well as managing and scheduling application processes.

[0083] BMS can be used to bind or unbind backup entities. After binding a backup entity, protection for the four main components can be initiated.

[0084] The application framework layer may also include: a window manager, a content provider, a resource manager, a notification manager, a view system, a phone manager, etc., but this application embodiment does not limit this.

[0085] The Android runtime consists of core libraries and a virtual machine. The Android runtime is responsible for scheduling and managing the Android system. The core libraries comprise two parts: one part contains the functionalities that Java calls, and the other part consists of the Android core libraries. The application layer and application framework layer run in the 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. System libraries can include multiple functional modules. Examples include: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), and 2D graphics engines (e.g., SGL).

[0086] The Surface Manager manages the display subsystem and provides fusion of 2D and 3D layers for multiple applications. The Media Library supports playback and recording of various common audio and video formats, as well as still image files. The Media Library supports multiple audio and video encoding formats. The 3D Graphics Processing Library implements 3D graphics drawing, image rendering, compositing, and layer processing. The 2D Graphics Engine is the drawing engine for 2D graphics.

[0087] The kernel layer is the layer between hardware and software. It drives the hardware, enabling it to function. The kernel layer includes at least display drivers, audio drivers, camera drivers, and Bluetooth drivers, but this embodiment does not limit the specific drivers included in this application.

[0088] Typically, when a user upgrades to a new phone, they can use data migration apps (such as app cloning) to transfer data from their old phone to their new one. Data migration can be divided into two stages: data transfer and data import. The data transfer stage involves transferring data from the old phone to the new phone; the data import stage involves installing the app on the new phone and importing the app data.

[0089] It should be understood that installing an application and importing application data are two different stages. Installing an application refers to installing the application package. This is relevant when a user installs an application on a new phone. For example, installing on a new phone After that, users can use However, because the application data was not imported, the installation was... It cannot provide users with information such as contacts, chat history, and favorites from their old phone. After importing the application data, applications installed on the new phone can provide the application data from the old phone, thus providing convenience for users using the new device.

[0090] However, in current data migration scenarios, users cannot intuitively understand the progress of application import, and the display effect of application icons is poor.

[0091] In view of this, embodiments of this application provide a method and related apparatus for displaying application icons, allowing the terminal device to access the desktop during data migration. After accessing the desktop through this entry point, the terminal device can import data in the background. During the data import process, the terminal device can display the import progress of the application on the desktop in real time, with different icon states corresponding to different import progress stages. In this way, during the data import process, users can intuitively understand the current import progress of the application through different icon states, which helps improve the display effect of application icons in data migration scenarios and enhances the user experience.

[0092] For ease of description, in this application embodiment, the new terminal device in the data migration scenario is referred to as the first terminal device, and the old terminal device in the data migration scenario is referred to as the second terminal device. The first terminal device and the second terminal device may have the following characteristics: Figure 1 and / or Figure 2 The structure shown is not limited to the embodiments described herein.

[0093] Figure 3 This is a schematic diagram of an interface for entering the desktop provided in an embodiment of this application. Taking a mobile phone as an example, as shown... Figure 3 As shown in Interface A, when importing data using the cloned application, the phone can provide an entry point to the desktop for the user. For example, it can provide control 01, which is used to access the desktop. In response to the user clicking control 01, the phone displays... Figure 3 The desktop shown in interface B. You can see that, in Figure 3 The B interface displays application icons for multiple applications. Different applications may correspond to different icon states, and the icon states can indicate the application import progress.

[0094] It's important to note that when importing applications, the phone displays multiple application icons as placeholders on the home screen. Applications at different import stages display different icon states. These placeholder icons pre-position the icons of the applications to be imported on the home screen, allowing users to see their exact location beforehand and familiarize themselves with the device more quickly, thus improving the user experience.

[0095] In this embodiment of the application, the application icon may also be referred to as the application icon.

[0096] It should be noted that the icon status includes waiting to import, installing, importing, and import completed.

[0097] Among them, the "Waiting to Import" status indicates that the application is waiting to be installed, the "Installing" status indicates that the application package is being installed, and the "Importing" status indicates that the application data is being imported.

[0098] It should be noted that the application import process includes waiting to import, installing the application, importing application data, and import completion. For a specific application, the import process is considered complete once the application data for that application has been imported.

[0099] When the application's import progress reaches the "Waiting to Import" stage, the corresponding icon status will be "Waiting to Import". For example, as shown... Figure 3 As shown in interface B, The icon is in a "waiting to be imported" state, therefore... The current import progress is pending import.

[0100] When the application import process progresses to "Installing Application," the corresponding icon status will be "Installing." For example, such as... Figure 3 As shown in interface B, The icon indicates that it is in the installation process, therefore... The current import process involves installing the application.

[0101] When the application import progresses to "Importing application data," the corresponding icon status will be "Importing." For example, such as... Figure 3 As shown in interface B, The icon status is "importing," therefore... The current import progress involves importing application data.

[0102] When the application's import progress reaches the "import complete" state, the corresponding icon status will be "import complete". For example, as shown... Figure 3 As shown in interface B, and The icon status indicates that the import is complete. and The current import progress is complete.

[0103] It should be noted that when importing applications onto a mobile phone, the import progress is in chronological order as follows: waiting to import, installing the application, importing application data, and import completed.

[0104] It should be noted that the icon status in this application embodiment includes the brightness of the application icon and / or the text display below the application icon. Figure 3In Interface B, you can see that application icons in the "Waiting to Import" state are all dark, with the text "Waiting to Import" displayed below them; application icons in the "Installing" state are partially lit, with the text "Installing" displayed below them; application icons in the "Importing" state are also partially lit, with the text "Importing" displayed below them; and application icons in the "Import Completed" state are all lit, with the application's name displayed below them, indicating that the application has been successfully imported.

[0105] It should be understood that the illuminated area of ​​an application icon in the importing state is larger than that of an application icon in the installation state.

[0106] Figure 4 This is a schematic diagram of an interface for refreshing icon status provided in an embodiment of this application. Taking a mobile phone as the first terminal device, the mobile phone imports... For example, when the phone starts importing... At this point, the initial import process progresses to "waiting for import," as shown below. Figure 4 As shown in interface A, The icon is in a waiting import state.

[0107] When the phone starts installing At times, such as Figure 4 As shown in interface B, the phone will display the desktop... The icon status refreshes from "Waiting to Import" to "Installing". When the icon status is "Installing", The icon gradually lights up from completely dark. The progress of the icon lighting up and The installation progress matches, and The text below the icon reads "Installing".

[0108] When the phone starts importing When using application data, such as Figure 4 As shown in the C interface, the phone will display the desktop... The icon status refreshes from "Installing" to "Importing". When the icon status is "Importing", The area where the icon is lit up increases, and The text below the icon reads "Importing".

[0109] When the phone finishes When importing application data, such as Figure 4 As shown in the D interface, the phone will display the desktop... The icon status refreshes from "Importing" to "Import Completed". When the icon status is "Import Completed", All the icons are lit up, and The text below the icon reads "WeChat," indicating the application's name.

[0110] Optionally, import on mobile phone During the process, users can choose to pause. Importing. For example, users can import by clicking... The icon is used to pause. Importing. For example, the user can click again... The icon will continue the import process.

[0111] The above combination Figure 3 and Figure 4 This section introduces an interface that displays different icon states. Below, we'll combine... Figure 5 The present application describes a method for displaying application icons according to its embodiments.

[0112] like Figure 2 As shown, the first terminal device in this embodiment may include an import module and a desktop module. The import module functions to provide a list of applications to be imported, mapping data between applications and their icons, application installation and application data import, refreshing notification icon status, broadcasting a heartbeat during the import process, and providing an abnormal icon rollback mechanism. The desktop module functions to maintain mapping data between applications and their icons, implement icon placeholders for application icons on the desktop, and refresh icon status.

[0113] Figure 5 This is a schematic flowchart of an application icon display method 500 provided in an embodiment of this application. The steps of method 500 are mainly executed interactively by the import module and the desktop module. Method 500 includes steps S501 to S512, and the specific steps are as follows:

[0114] S501, the import module sends application information to the desktop module. Correspondingly, the desktop module receives the application information.

[0115] In this step, the application information includes a list of applications to be imported, the application packages of the applications to be imported, and the mapping data between applications and icons. The list of applications to be imported includes the names of the applications to be imported, and the mapping data between applications and icons indicates the icon for each application to be imported.

[0116] It should be understood that after data transmission is complete, the second terminal device can send an indication message to the import module of the first terminal device. This indication message indicates that all migration data has been sent. Upon receiving this indication message, the import module of the first terminal device triggers the start of data import, thereby executing the steps of method 500. Alternatively, after receiving the aforementioned indication message, the import module can also determine whether all migration data has been received. If it determines that all migration data has been received, it triggers the start of data import.

[0117] S502, the import module sends desktop layout information to the desktop module. Correspondingly, the desktop module receives the desktop layout information.

[0118] In this step, the desktop layout information is used to indicate the position of the application icon to be imported on the desktop. In a data migration scenario, the second terminal device can send desktop layout information to the import module of the first terminal device. This desktop layout information indicates the layout position of the application icon to be imported on the desktop of the second terminal device.

[0119] For example, The icon is positioned in the first row and first column of the first desktop page on the second terminal device. The icon is positioned in the first row and second column of the first desktop page on the second terminal device. The icon is positioned in the first row and third column of the first desktop page on the second terminal device. The icon is positioned in the first row and fourth column of the first desktop page on the second terminal device. The icon is positioned in the second row and first column of the first desktop page on the second terminal device.

[0120] S503, the desktop module uses application information and desktop layout information to place the icons of the applications to be imported on the desktop as placeholders.

[0121] In this step, the desktop module retrieves the icon of the application to be imported based on the application's information, and then places the icon of the application to be imported on the desktop as a placeholder based on the desktop layout information. While the icon is being placed, the icon of the application to be imported is in a "waiting to be imported" state. For example, Figure 4 The A interface shown in The icon status.

[0122] In this step, since the application icons can be placed according to the desktop layout information, it is more in line with the user's usage habits and helps to improve the user experience.

[0123] It should be understood that S502 is optional, meaning the desktop module does not know the layout position of the application to be imported on the desktop of the second terminal device. In this case, the desktop module places the icon of the application to be imported on the desktop as a placeholder based on the application information. For example, the desktop module may place the icon of the application to be imported on the desktop according to the alphabetical order of the first letter of the application name.

[0124] S504, the desktop module displays the icon of the application to be imported on the desktop in a waiting-to-import state.

[0125] In this step, if the import module has not started the import process, the initial icon state of the application to be imported is "waiting to be imported". For example, Figure 4 The A interface shown in The icon status.

[0126] It should be understood that there can be multiple applications to be imported. The following section, using S505 to S510 as an example, describes how to refresh the icon status of an application.

[0127] S505, when the import module starts installing the application, it sends a first icon status broadcast to the desktop module. The desktop module then receives the first icon status broadcast.

[0128] In this step, the first icon status broadcast is used to instruct the desktop module to refresh the application's icon status.

[0129] Optionally, the import module can broadcast the application's identifier and the refreshed icon status via the first icon status broadcast. The application's identifier is used by the desktop module to determine which application's icon status to refresh.

[0130] It should be understood that the import module can call the application installation interface to start the application installation.

[0131] In S506, the desktop module broadcasts the first icon status, refreshing the application's icon status from "waiting to import" to "installing." For example, this is done when the import module initiates the installation. After that, the desktop module can The icon status is changed by Figure 4 The "Waiting for Import" status shown on interface A has been refreshed to, as follows: Figure 4 The B interface shows the installation status.

[0132] S507, when the import module starts importing application data, it sends a second icon status broadcast to the desktop module. Correspondingly, the desktop module receives the second icon status broadcast.

[0133] In this step, the second icon status broadcast is used to instruct the desktop module to refresh the application's icon status.

[0134] Optionally, the import module can broadcast the application's identifier and the refreshed icon status via a second icon status broadcast. The application's identifier is used by the desktop module to determine which application's icon status to refresh.

[0135] It should be understood that after installation, the application can send initial feedback to the import module, indicating that the installation is complete. Once the import module confirms successful installation, it can call the interface for importing application data to begin importing the application's data.

[0136] In S508, the desktop module broadcasts the application's icon status from "Installing" to "Importing" based on the second icon status. For example, this can be done by starting the import process in the import module. After processing the application data, the desktop module can... The icon status is changed by Figure 4 The installation status shown on interface B in the image has been refreshed to resemble the following: Figure 4 The C interface shows the import status.

[0137] S509, upon completion of the import process, the import module sends a third icon status broadcast to the desktop module. The desktop module then receives the third icon status broadcast.

[0138] In this step, the third icon status broadcast is used to instruct the desktop module to refresh the application's icon status.

[0139] Optionally, the import module can broadcast the application's identifier and the refreshed icon status via a third icon status broadcast. The application's identifier is used by the desktop module to determine which application's icon status to refresh.

[0140] In S510, the desktop module uses a third-party icon status broadcast to refresh the application's icon status from the importing state to the import complete state. For example, after the import module completes... After importing the application data, the desktop module can... The icon status is changed by Figure 4 The import status shown in the C interface is refreshed to look like this. Figure 4 The import completion status is shown in the D interface.

[0141] Optionally, method 500 also includes S511 and S512.

[0142] S511, if the import module detects that the user operation is a predefined operation, it will stop the import of the application.

[0143] In this step, stopping the import of the application means stopping the import process of the application that is in the stages of waiting to be imported, installing, or importing.

[0144] During the interaction between the import module and the desktop module, the import module can send heartbeat broadcasts to the desktop module to indicate its online status. During the application import process, there may be abnormalities, such as the user accidentally removing the cloned application from the background (predefined operations include removing cloned applications). In this case, the import module will abort the application import, stop sending heartbeat broadcasts to the desktop module, and enter an offline state.

[0145] During the application import process, the import process may be interrupted, for example, if the user cancels the import process, i.e., the predefined operation includes canceling the import process. In this case, the import module can send a stop broadcast message to the desktop module, which indicates that the application import should be stopped.

[0146] S512, the desktop module cleans up the icons of target applications from the desktop.

[0147] In this step, the target application includes applications that have not been installed, which include applications whose import progress has progressed to importing application data, and applications whose import progress has progressed to installing applications.

[0148] It should be noted that applications whose import progress has progressed to "Importing Application Data" or "Import Completed" have already completed the installation. Users can use the installed applications normally, while applications that have not been installed cannot be used normally. Therefore, the desktop module can clean up the icons of applications that have not been installed on the desktop, while keeping the icons of applications that have been installed.

[0149] Optionally, in the event of an abnormal import process, since the import module stops sending heartbeat broadcasts, the desktop module can trigger a heartbeat broadcast timeout mechanism and clear the target application's icon on the desktop if it determines that the current time is longer than the duration of the last heartbeat broadcast received.

[0150] Optionally, if the import process is aborted, the desktop module can determine that the import process has been aborted after receiving the abort broadcast message and clear the icon of the target application on the desktop.

[0151] It should be noted that, for cases where the import process is aborted, for example, the user can cancel the import process of all applications to be imported, or the user can cancel the import process of a specific application among the applications to be imported. If the import process of all applications to be imported is canceled, the desktop module can remove the icon of the target application from the desktop. If the import process of a specific application to be imported is canceled, if the application has not been installed, the desktop module will remove the application's icon from the desktop; if the application has been installed, the desktop module will retain the application's icon on the desktop.

[0152] It should be noted that when there are multiple applications to be imported, the import module can determine the import order of the applications according to preset rules.

[0153] Optionally, the desktop module determines the import order of applications based on their usage frequency.

[0154] Optionally, the import module determines the import order of the applications to be imported according to the alphabetical order of their first names.

[0155] In one possible implementation, the import module can initiate the import of one application only after the previous application has been imported, following a preset installation order. The import order of the applications to be imported is determined by their alphabetical order, and the applications to be imported include... and For example, The first letter is "D". The first letter is "T". The first letter of is "W". The first letter of the name is "Z", therefore, the imported module is installed first. exist After installation, start the import process. Application data, in After the application data import is complete, the import module is finished. The modules are then imported. Afterwards, the installation begins in the order they were imported. exist After installation, start the import process. Application data, in After the application data import is complete, the import module is finished. The desktop modules are then imported in the same order. Import and Import.

[0156] In another possible implementation, the import module can install multiple applications simultaneously and import their application data sequentially.

[0157] The import order of applications is determined by their first alphabetical order. The applications to be imported include... and For example, importing modules can install simultaneously. and exist After installation, the import module will first start importing. The application data was imported into Douyin's application data import process, and... After installation, start the import process. Application data, in The application data import is complete, and After installation, start the import process. Application data, in The application data import is complete, and After installation, start the import process. Application data.

[0158] Optionally, the desktop layout information mentioned above may include card layout information. The card layout information may indicate which application cards are added to the desktop, and the layout position of the added cards.

[0159] In one possible implementation, the desktop module can add application cards to the desktop layout after all applications to be imported have been imported.

[0160] In another possible implementation, after an application is imported, the desktop module can detect whether the layout information of the card indicates that a card for that application should be added. If so, the desktop module adds the card for that application to the desktop.

[0161] In another possible implementation, the desktop module can, as described in S503, pre-place cards for the applications indicated in the card layout information in the corresponding layout positions when the desktop is in place of icon placeholders, and can prompt the user to wait for the application card to be added in that layout position.

[0162] The above combination Figure 5 This describes the process of the icon status refreshing from "Waiting to Install" to "Installing", from "Installing" to "Importing", and from "Importing" to "Import Completed". In some scenarios, the icon status may not follow this exactly. Figure 5 The order of descriptions will be refreshed. (See below for details.) Figure 6 The refresh order of icons under various possible scenarios is described.

[0163] Figure 6This is a schematic diagram illustrating an icon status refresh provided in an embodiment of this application. For example... Figure 6 As shown, taking one of the multiple applications to be imported as an example, the initial icon state of the application is "waiting to be imported".

[0164] Optionally, before starting the installation of the application, the import module can detect whether the application is already installed on the system and whether the application data exists.

[0165] In one possible scenario, after the user enters the desktop on the first terminal device, the user may have already installed the application on the first terminal device through other means, such as through an app store or browser (provided that an app store or browser is already installed on the first terminal device).

[0166] If the application is already installed on the first terminal device and has no application data, the import module, upon detecting the application's installation, sends a fourth icon status broadcast to the desktop module. This broadcast indicates that the application's refreshed icon status is now "import complete." Based on this broadcast, the desktop module refreshes the application's icon status from "waiting to import" to "import complete" on the desktop.

[0167] If the application is already installed on the first terminal device and has application data, the import module, upon detecting the application's installation, sends a fifth icon status broadcast to the desktop module. This broadcast indicates that the application's refreshed icon status is in the importing state. Based on this broadcast, the desktop module refreshes the application's icon status from the waiting-to-import state to the importing state on the desktop.

[0168] In another possible scenario, the application is not installed on the first terminal device.

[0169] If the application is not installed on the first terminal device, the import module can initiate the installation of the application and send a sixth icon status broadcast to the desktop module. This sixth icon status broadcast indicates that the application's refreshed icon status is in the installation process. Based on this sixth icon status broadcast, the desktop module refreshes the application's icon status from the "waiting to import" state to the "installing" state on the desktop.

[0170] After the application is installed in the import module and it is confirmed that the application has no data, the import module sends a seventh icon status broadcast to the desktop module. This broadcast indicates that the application's icon status will be updated to the import complete state. Based on this broadcast, the desktop module refreshes the application's icon status from the "installing" state to the "import complete" state on the desktop.

[0171] After the application is installed in the import module and its data is confirmed, the import module sends an eighth icon status broadcast to the desktop module. This broadcast indicates that the application's icon status has been refreshed to show that it is in the importing state. Based on this broadcast, the desktop module refreshes the application's icon status from "installing" to "importing" on the desktop.

[0172] Once the import module completes the import of the application, it sends a ninth icon status broadcast to the desktop module. This broadcast indicates that the application's icon status has been refreshed to show that the import is complete. Based on this broadcast, the desktop module refreshes the application's icon status from the importing state to the import complete state on the desktop.

[0173] During the application import process, there may be situations that affect the import of application data. One possible scenario is that the import module is already installed... Version 7.0 is being imported. Taking application data as an example, when importing... During the import of application data, the BMS in the application framework layer can call the AMS interface to refresh the status flag, for example, changing the status flag from "0" to "1". A status flag of "1" indicates that application data is being imported. If the user expects to download the latest version from the app store at this time... In version 8.0, the app store receives downloads. When requesting version 8.0, since PMS is responsible for application installation, the app store can send an installation command to PMS. Upon receiving the installation command, PMS sends a query command to AMS, which checks the status flag. PMS retrieves the status flag to confirm that the import module is being imported. Therefore, the PMS can send an instruction to the app store indicating that the installation failed. The app store can then display a message on the download page indicating that the application cannot be installed. Version 8.0.

[0174] Optionally, such as Figure 6 As shown, the import module can complete the import process. After reviewing the application data, reinstall. Version 8.0. In this case, the icon status also includes the application update status, which the desktop module can display on the desktop. The icon status refreshes from "Import Completed" to "Application Updated".

[0175] Through the above protection mechanism, the first terminal device can protect the process of importing application data and prevent the download of the latest version. Version 8.0 of the process affects the current process importing application data, improving the reliability of data transmission.

[0176] In the description above, such as Figure 3 As shown, the first terminal device can provide users with an entry point to the desktop during the data import process (e.g., Figure 3 (Control 01 shown in Interface A). Optionally, the first terminal device can also provide the user with an entry point to the desktop during data transmission.

[0177] Figure 7 This is a schematic diagram of another interface for entering the desktop provided in an embodiment of this application. Taking a mobile phone as an example, as follows... Figure 7 As shown in Interface A, when transferring data using the cloned application, the phone can display a data receiving interface, providing the user with an entry point to the desktop. For example, control 02 can be provided, allowing the user to access the desktop. In response to the user clicking control 02, the phone displays... Figure 7 The desktop shown in interface B. You can see that, in Figure 7 Interface B displays multiple application icons. Since the phone is still in the data transfer phase and the applications have not yet been installed or their data imported, the icons of the multiple applications to be imported are all in the "transferring" state, corresponding to the data transfer phase of the data migration.

[0178] It's important to note that in data migration scenarios involving new and old phones, before establishing a connection and initiating data transfer, the new phone can instruct the old phone to first transfer application information and desktop layout information. After receiving this information, the new phone can place placeholder icons on the desktop based on the information provided. This allows the new phone to display icons as shown in the image when the user clicks control 02. Figure 7 The desktop shown in interface B.

[0179] Figure 8 This is a schematic diagram of an interface for displaying icon status provided in an embodiment of this application. For example... Figure 8 As shown, after data transmission is complete, the phone enters the data import phase. The phone refreshes the icon status of multiple applications to be imported from the "transmitting" state to the "awaiting import" state. Then, based on the application's installation and data import, the phone refreshes the application icon status on the desktop. A description of the icon status refresh during the data import phase can be found above and will not be repeated here.

[0180] Similar to the implementation of refreshing icon states during the data import phase, the import module can send a tenth icon state broadcast to the desktop module after detecting that data transmission has ended. This first icon state broadcast instructs the desktop module to refresh the icon states of all applications to the "awaiting import" state. Based on this tenth icon state broadcast, the desktop module refreshes the icon states of all applications on the desktop from the "transferring" state to the "awaiting import" state.

[0181] like Figure 7 As shown in Interface B, application icons in the "Transferring" state are completely darkened. Since application icons in the "Waiting to Import" state are also completely darkened, they can be distinguished by the text displayed below the icons, such as... Figure 3 As shown in interface B, the text displayed below the application icon in the "Waiting to Import" state is "Waiting to Import". Figure 7 As shown in Interface B, the text displayed below the application icon whose icon status is "Transferring" is "Transferring".

[0182] In addition, when refreshing the icon status from the "Transferring" state to the "Waiting to Import" state, you can also refresh the color of the application icon to distinguish between the "Transferring" and "Waiting to Import" states using different colors.

[0183] It should be understood that the sequence number of each process 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.

[0184] The above text combines Figures 1 to 8 The present application describes in detail the method for displaying application icons according to embodiments of the present application. The following will be combined with... Figure 9 and Figure 10 A detailed description of an application icon display device according to an embodiment of this application.

[0185] Figure 9 A schematic block diagram of an application icon display device 900 provided in an embodiment of this application is shown. The device 900 includes a processing module 910 and a display module 920.

[0186] The processing module 910 is used to establish a connection with the second terminal device. The display module 920 is used to display a first interface when receiving migration data sent by the second terminal device. The first interface includes one or more of the following: the amount of migration data, the transmission progress, or the transmission time. The processing module 910 is also used to start importing migration data after receiving it. The display module 920 is also used to display a second interface during the import of migration data. The second interface includes a first control. In response to the user's selection of the first control, a first desktop is displayed. The first desktop includes a first icon of the first application and a first import progress of the first application. The icon state of the first application is in the first state. The processing module 910 is also used to update the icon state of the first application to a second state on the first desktop when the import progress of the first application changes. The second state includes a second icon of the first application and a second import progress.

[0187] The first interface can be seen as follows: Figure 7 Interface A is shown in the image. For the second interface, please refer to... Figure 3 In interface A, the first control can correspond to control 01, and the first desktop can be seen as follows: Figure 3 The desktop shown in interface B, the first application can be found here. Figure 3 The B interface shown in or When the first application is At that time, the first state is waiting to be imported, and when the first application is... At that time, the first state is "Installing", and the first application is... At that time, the first status is "Importing".

[0188] like Figure 3 As shown in Interface B, the desktop displays the application's icon and the text below the icon. The text below the icon describes the application's import progress, and different icon states include different icons and import progress.

[0189] Optionally, the first state includes a waiting-to-import state. The processing module 910 is configured to: update the icon status of the first application to the installing state on the first desktop when the import progress of the first application changes from waiting to import to installing application.

[0190] Optionally, the first state includes a waiting-to-import state. The processing module 910 is configured to: update the icon state of the first application to the importing state on the first desktop when the import progress of the first application changes from waiting to import to importing application data.

[0191] Optionally, the first state includes a waiting-to-import state. The processing module 910 is configured to: update the icon state of the first application to the import-completed state on the first desktop when the import progress of the first application changes from waiting to import to complete import.

[0192] Optionally, the first state includes the installation state. The processing module 910 is configured to: update the icon state of the first application to the importing state on the first desktop when the import progress of the first application changes from installing the application to importing application data.

[0193] Optionally, the first state includes the installation state. The processing module 910 is configured to: update the icon state of the first application to the import completed state on the first desktop when the import progress of the first application changes from installing application to import completed.

[0194] Optionally, the first state includes an importing state. The processing module 910 is configured to: update the icon state of the first application to the import completed state on the first desktop when the import progress of the first application changes from importing application data to import completed.

[0195] Optionally, the processing module 910 includes an import module and a desktop module, wherein the import module is configured to: detect the import progress of the first application; and, when a change in the import progress is detected, send a first broadcast to the desktop module, the first broadcast indicating an update to the icon state of the first application. The desktop module is configured to: receive the first broadcast; and, based on the first broadcast, update the icon state of the first application to a second state in the first desktop.

[0196] The first broadcast can correspond to the icon status broadcast described in the above embodiments.

[0197] Optionally, the processing module 910 includes an import module and a desktop module, wherein the import module is configured to: send first indication information to the desktop module, the first indication information indicating the position of the icon of the first application on the first desktop. The desktop module is configured to: receive the first indication information; and, based on the first indication information, place the icon of the first application on the first desktop as a placeholder.

[0198] The first instruction information can correspond to the desktop layout information described in the above embodiments.

[0199] Optionally, the processing module 910 is used to: clean up the icons of target applications from the first desktop when the user operation is detected to be a predefined operation, the target applications including applications that have not been fully installed.

[0200] Optionally, the device 900 further includes a transceiver module, configured to: receive second indication information from the second terminal device, the second indication information indicating that all migration data has been sent. The processing module 910 is configured to: based on the second indication information, and upon determining that all migration data has been received, initiate the import of migration data.

[0201] In an optional example, those skilled in the art will understand that device 900 may specifically be the first terminal device in the above embodiments, or the functions of the first terminal device in the above embodiments may be integrated into device 900. The above functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. Device 900 may be used to execute the various processes and / or steps corresponding to the first terminal device in the above method embodiments.

[0202] It should be understood that the device 900 described herein is embodied in the form of a functional module. The term "module" here can refer to application-specific integrated circuits (ASICs), electronic circuits, processors (e.g., shared processors, proprietary processors, or group processors, etc.) and memories for executing one or more software or firmware programs, integrated logic circuits, and / or other suitable components supporting the described functions. In embodiments of this application, Figure 9 The device 900 in the text can also be a chip or a chip system, such as a system on a chip (SoC).

[0203] Figure 10 A schematic block diagram of another application icon display device 1000 provided in an embodiment of this application is shown. The device 1000 includes a processor 1010, a transceiver 1020, and a memory 1030. The processor 1010, transceiver 1020, and memory 1030 communicate with each other via internal interconnection paths. The memory 1030 is used to store instructions, and the processor 1010 is used to execute the instructions stored in the memory 1030 to control the transceiver 1020 to transmit and / or receive signals.

[0204] It should be understood that the apparatus 1000 can be used to execute the various steps and / or processes corresponding to the first terminal device in the above method embodiments. Optionally, the memory 1030 may include read-only memory and random access memory, and provide instructions and data to the processor. A portion of the memory may also include non-volatile random access memory. For example, the memory may also store device type information. The processor 1010 can be used to execute instructions stored in the memory, and when the processor executes the instructions, the processor can execute the various steps and / or processes corresponding to the first terminal device in the above method embodiments.

[0205] It should be understood that, in the embodiments of this application, the processor 1010 may be a central processing unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0206] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, can implement the method executed by the first terminal device in any of the above method embodiments.

[0207] This application also provides a computer program product, including a computer program that, when executed by a processor, can implement the method executed by the first terminal device in any of the above method embodiments.

[0208] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The steps of the method disclosed in the embodiments of this application can be directly manifested as execution by a hardware processor, or as a combination of hardware and software modules within the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor executes the instructions in the memory, combining them with its hardware to complete the steps of the above method. To avoid repetition, detailed descriptions are omitted here.

[0209] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software 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] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and modules described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0211] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.

[0212] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0213] In addition, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module.

[0214] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0215] The above description is merely a specific embodiment of this application, but the protection scope of the embodiments of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the embodiments of this application should be included within the protection scope of the embodiments of this application. Therefore, the protection scope of the embodiments of this application should be determined by the protection scope of the claims.

Claims

1. A method for displaying an application icon, characterized in that, include: The first terminal device establishes a connection with the second terminal device; When the first terminal device receives migration data sent by the second terminal device, the first terminal device displays a first interface, which includes one or more of the following: the amount of migration data, the transmission progress, or the transmission time. After the first terminal device has received the migration data, the first terminal device begins to import the migration data; During the process of importing the migration data on the first terminal device, the first terminal device displays a second interface, which includes a first control. In response to the user's selection of the first control, the first terminal device displays a first desktop, which includes a first icon of the first application and a first import progress of the first application. The icon of the first application is in a first state, which is an installation state, and the installation state is the state of installing the first application. When the import progress of the first application changes, the first terminal device updates the icon status of the first application to a second status on the first desktop. The second status includes the second icon of the first application and the second import progress. The second status is an importing status. The importing status is the status of importing application data into the first application after the first application is installed. The application data includes user-specific data belonging to the first application contained in the migration data from the second terminal device.

2. The method according to claim 1, characterized in that, The third state includes the waiting-to-import state; The method further includes: When the import progress of the first application changes from waiting to import to installing the application, the first terminal device updates the icon status of the first application on the first desktop from the third status to the first status.

3. The method according to claim 1, characterized in that, The third status includes the import completion status; The method further includes: When the import progress of the first application changes from importing application data to importing completed, the first terminal device updates the icon status of the first application on the first desktop from the second status to the third status.

4. The method according to any one of claims 1 to 3, characterized in that, The first terminal device includes an import module and a desktop module; When the import progress of the first application changes, the first terminal device updates the icon state of the first application to a second state on the first desktop, including: The first terminal device detects the import progress of the first application through the import module; When a change in the import progress is detected, the first terminal device sends a first broadcast to the desktop module through the import module. The first broadcast is used to indicate an update to the icon status of the first application. The first terminal device receives the first broadcast through the desktop module; Based on the first broadcast, the first terminal device updates the icon status of the first application to the second status in the first desktop through the desktop module.

5. The method according to claim 4, characterized in that, The method further includes: The first terminal device sends first indication information to the desktop module through the import module. The first indication information is used to indicate the position of the icon of the first application on the first desktop. The first terminal device receives the first instruction information through the desktop module; Based on the first instruction information, the first terminal device places the icon of the first application on the first desktop through the desktop module.

6. The method according to any one of claims 1 to 3, characterized in that, The method further includes: When the first terminal device detects that the user operation is a predefined operation, it clears the icons of the target application from the first desktop. The target application includes applications that have not been fully installed.

7. The method according to any one of claims 1 to 3, characterized in that, After the first terminal device has received the migration data, the first terminal device begins to import the migration data, including: The first terminal device receives a second indication information from the second terminal device, the second indication information being used to indicate that the migration data has been completely sent; Based on the second instruction information, the first terminal device initiates the import of the migration data after determining that the migration data has been received.

8. A device for displaying application icons, characterized in that, It includes Module 1, Module 2, Module 3, and Module 4; among which, The first module is used to establish a connection between the first terminal device and the second terminal device; The second module is configured to display a first interface on the first terminal device when the first terminal device receives migration data sent by the second terminal device. The first interface includes one or more of the following: the amount of migration data, the transmission progress, or the transmission time. The third module is used to enable the first terminal device to start importing the migration data after the first terminal device has received the migration data. The second module is further configured to, during the process of importing the migration data into the first terminal device, display a second interface on the first terminal device, the second interface including a first control; The second module is further configured to respond to the user's selection of the first control, wherein the first terminal device displays a first desktop, the first desktop including a first icon of a first application and a first import progress of the first application, the icon state of the first application being a first state, the first state being an installation state, and the installation state being an installation state of the first application. The fourth module is used to update the icon status of the first application to a second status on the first desktop when the import progress of the first application changes. The second status includes the second icon of the first application and the second import progress. The second status is an importing status. The importing status is the status of importing application data into the first application after the first application is installed. The application data includes user-specific data belonging to the first application contained in the migration data from the second terminal device.

9. A device for displaying application icons, characterized in that, include: Processor and memory, of which, The memory is used to store computer programs; The processor is used to invoke and execute the computer program to cause the device to perform the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, Used to store computer programs that, when run on a computer, cause the computer to perform the method as described in any one of claims 1 to 7.

11. A computer program product, characterized in that, The computer program product includes computer program code that, when run on a computer, causes the computer to implement the method as described in any one of claims 1 to 7.

Images