Interface display method, electronic device, and storage medium

Abstract

This application relates to the field of terminal technology, and more particularly to an interface display method, electronic device, and storage medium. The method includes: a first device displaying a first interface, the first interface including a first device identifier indicating the first device and a second device identifier indicating a second device. Next, in response to a trigger operation on the second device identifier, the first device displays a second interface. The second interface includes a first service identifier and a first application icon, the first service identifier indicating a first service provided by the second device, and the first application icon indicating a first application installed on the second device. When the first device receives a trigger operation on the first application icon, the first device displays a third interface. The third interface includes the display interface of the second application. This method can improve human-computer interaction efficiency and enhance the user experience.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to an interface display method, electronic device, and storage medium. Background Technology

[0002] With the development of terminal technology, users are using electronic devices more and more frequently, and the number of electronic devices they own is increasing.

[0003] Currently, users need to perform relatively complex operations to open an application installed on electronic device B on electronic device A, and for electronic device A to display the interface of the application installed on electronic device B. This leads to reduced human-computer interaction efficiency and a lower user experience. Summary of the Invention

[0004] This application provides an interface display method, an electronic device, and a storage medium to improve human-computer interaction efficiency and enhance user experience.

[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0006] Firstly, a method for displaying an interface is provided. This method can be applied to a first device, wherein the first device and a second device establish a communication connection, and the first device and the second device are different. Both the first device and the second device are electronic devices, such as mobile phones, tablets, PCs, etc. It should be understood that the aforementioned difference between the first device and the second device can be interpreted as the first device and the second device being electronic devices of different forms, such as the first device being a mobile phone and the second device being a tablet computer; or, the aforementioned difference between the first device and the second device can also be interpreted as the first device and the second device being electronic devices of the same form but different, such as the first device being mobile phone A and the second device being mobile phone B. The first device and the second device can establish a communication connection through long-range communication or short-range communication functions.

[0007] The method described above includes: a first device displaying a first interface, the first interface including a first device identifier indicating the first device and a second device identifier indicating a second device. Next, in response to a trigger operation on the second device identifier, the first device displays a second interface. The second interface includes a first service identifier and a first application icon, the first service identifier indicating a first service provided by the second device, and the first application icon indicating a first application installed on the second device. Next, when the first service identifier is dragged to the first device identifier, the first device executes the first service through interaction with the second device; that is, when the user triggers the first service on the first device, the first device executes the first service through interaction with the second device. When the first device receives a trigger operation on the first application icon, the first device displays a third interface; that is, when the user triggers the icon of the first application, the first device displays the third interface. The third interface includes the display interface of the second application; for example, the third interface includes the display interface when the second device runs the first application.

[0008] In the above method, when a user wants to use an application installed on a second device on a first device, the user can trigger the display of the second application's interface on the first device through a second interface displayed on the first device (e.g., the trust ring control interface). This improves human-computer interaction efficiency and enhances the user experience. Furthermore, the user can also trigger the first device from the second interface. Thus, this method improves human-computer interaction efficiency while increasing the user's flexibility in using the first device, further enhancing the user experience.

[0009] Optionally, the first device can display the third interface in full screen. Alternatively, the first device can display the third interface in a floating window. Alternatively, the first device can display the third interface in a split-screen window. Optionally, the first service includes any one of the following: screen sharing service, network sharing service, file sharing service, and cross-platform call service.

[0010] Optionally, the display interface of the first application running on the second device can be projected from the second device to the first device via a different source of screen mirroring. In other words, the second device can run the first application in the background without displaying the interface of the first application in the foreground, for example, when the screen of the second device is off.

[0011] In one possible design of the first aspect, the second interface further includes a first device identifier. After the first device displays the second interface, the method further includes: in response to a triggering operation on the first device identifier, the first device displays a fourth interface, the fourth interface including a second service identifier indicating a second service provided by the first device; the fourth interface does not include an application icon.

[0012] In this design, when a user triggers the device identifier of the first device in the second interface, the electronic device does not display the icons of applications installed on the first device.

[0013] In one possible design of the first aspect, after the first device displays the second interface, the method further includes: in response to a first long-press operation on the first application icon, the first device displays a first desktop and a second application icon. The second application icon corresponds to the first application, and during the display of the first desktop, the second application icon moves on the desktop following a first drag operation by the user; the first drag operation and the first long-press operation are consecutive user actions. Next, when the second application icon is dragged to a first position on the first desktop, in response to a release operation by the user, the first device adds a third application icon to the first desktop, the third application icon corresponding to the first application. Subsequently, in response to a trigger operation on the third application icon, the first device displays a third interface.

[0014] In this design, users can set the icon of a primary application to the home screen of their primary device. This means that users can manipulate the home screen to display icons of applications from other devices. Subsequently, users can trigger the display of a third interface on the primary device by using the icons of these installed applications on the primary device's home screen. This further simplifies user operation, enhances the convenience of using electronic devices, and improves the user experience.

[0015] In another possible design of the first aspect, the aforementioned first position is a non-edge position in the first desktop. Furthermore, the method further includes: in response to a second application icon being dragged to a second position on the first desktop, the first device displays a second desktop, the second position being located at the edge of the first desktop; after the first device displays the second desktop, in response to a user releasing their finger, the first device adds a third application icon to the second desktop.

[0016] In this design, users can flexibly customize the icons of applications installed on other devices and their layout on the home screen of the primary device. This further enhances the convenience of using electronic devices and improves the user experience.

[0017] In another possible design of the first aspect, the aforementioned third application icon further includes a badge, the state of which includes a first state or a second state. When the badge is in the first state, the method further includes: in response to a triggering operation on the third application icon, the first device displays a third interface. When the badge is in the second state, the method further includes: in response to a triggering operation on the third application icon, the first device displays a prompt indicating that the first application has not been launched.

[0018] In this design, the first device can use a status indicator to indicate whether an application installed on another device can be launched by the first device.

[0019] In another possible design of the first aspect, after the first device displays the second interface, the method further includes: in response to a first operation on the first application icon, the first device displays a first menu, the first menu including a first option and a second option. And, when the first option is triggered, the first device displays a third interface; when the second option is triggered, the first device adds a fourth application icon to the desktop of the first device, the fourth application icon corresponding to the first application.

[0020] In this design, users can either trigger the first device to display the third interface through the first menu, or trigger the first device to add icons of applications installed on other devices to the desktop of the first device through the first menu.

[0021] In another possible design of the first aspect, the first device displays a third interface, including: the first device displays the third interface through a first floating window; the first floating window includes a first control. The method further includes: in response to a trigger operation on the first control, adding a fifth application icon to the desktop of the first device, the fifth application icon corresponding to the first application.

[0022] In this design, users can trigger the first device to add icons of applications installed on other devices to the desktop through the first control of the first floating window.

[0023] In another possible design of the first aspect, the aforementioned first floating window further includes a second control. The method also includes: in response to a triggering operation on the second control, the first device displays a third interface in full screen, and the first device displays an adjustment control. Then, in response to a triggering operation on the adjustment control, the first device displays a second menu; the second menu includes the third control. Next, in response to a triggering operation on the third control, a sixth application icon is added to the desktop of the first device, the sixth application icon corresponding to the first application.

[0024] In this design, users can trigger a full-screen display of a third interface on the first device using a second control within the first floating window. Furthermore, users can add icons for applications installed on other devices to the desktop using a third control included in the second menu.

[0025] In another possible design of the first aspect, the first device establishes a communication connection with the third device; the second interface also includes a third device identifier indicating the third device. After the first device displays the second interface, the method further includes: in response to a triggering operation on the third device identifier, the first device displays a fifth interface; the fifth interface includes a third service identifier and a seventh application icon, the third service identifier indicating a third service provided by the third device, and the seventh application icon indicating a second application installed on the third device.

[0026] In another possible design of the first aspect, after the first device displays the fifth interface, the method further includes: in response to a swipe operation triggered on the fifth interface, the first device displays a sixth interface; the sixth interface includes icons of applications installed on the third device, and the sixth interface does not include service identifiers.

[0027] In another possible design of the first aspect, the aforementioned sixth interface further includes a first device identifier and a second device identifier; in response to a triggering operation on the second device identifier, the first device displays a seventh interface. The seventh interface includes icons for applications installed on the second device, but does not include service identifiers.

[0028] In another possible design of the first aspect, the sixth interface further includes a first application bar and a second application bar. The method further includes: the first device displaying icons of frequently used applications installed on the second device in the display area corresponding to the first application bar; and the first device displaying icons of each application installed on the second device in the display area corresponding to the second application bar.

[0029] In another possible design of the first aspect, the icons of the applications displayed in the display area corresponding to the second application bar are sorted alphabetically; the sixth interface also includes a first letter positioning bar, which includes the target letter; the method further includes: in response to a trigger operation on the target letter, the first device displays the icon of the application whose first letter is the target letter in the sixth interface.

[0030] In another possible design of the first aspect, after the first device displays the third interface, the method further includes: the first device receiving a second operation on the display interface when the second device runs the first application; the first device, through interaction with the second device, causing the first device to display a seventh interface; the seventh interface includes the interface response of the second device to the second operation when the second device runs the first application.

[0031] In this design, the user can operate the first application on the second device through the first device.

[0032] In a second aspect, an electronic device is provided, the electronic device including a memory and one or more processors, the memory being coupled to the processors; wherein the memory stores computer program code, the computer program code including computer instructions; when the computer instructions are executed by the processor, the electronic device performs the method provided by the first aspect and any possible design of the first aspect.

[0033] Thirdly, a computer-readable storage medium is provided, including computer instructions that, when executed on an electronic device, cause the electronic device to perform the methods provided by the first aspect and any possible design of the first aspect.

[0034] Fourthly, a computer program product containing instructions is provided, which, when run on an electronic device, enables the electronic device to perform the methods provided by the first aspect and any possible design of the first aspect.

[0035] Fifthly, a chip system is provided for use in an electronic device, the chip system including one or more processors for invoking computer instructions to cause the electronic device to perform the methods provided by the first aspect and any possible design of the first aspect.

[0036] The technical effects of any of the design methods in aspects two through five can be found in the technical effects of different design methods in aspect one, and will not be repeated here. Attached Figure Description

[0037] Figure 1 A schematic diagram of a communication system provided in an embodiment of this application;

[0038] Figure 2 A schematic diagram of the structure of an electronic device provided in an embodiment of this application;

[0039] Figure 3 A schematic diagram of the architecture of an electronic device provided in an embodiment of this application;

[0040] Figure 4 A schematic diagram of a set of user graphical interfaces provided in the embodiments of this application;

[0041] Figure 5 A schematic diagram of another set of user graphical interfaces provided in the embodiments of this application;

[0042] Figure 6 A schematic diagram of yet another set of user graphical interfaces provided in the embodiments of this application;

[0043] Figure 7 A schematic diagram of another set of user graphical interfaces provided in the embodiments of this application;

[0044] Figure 8 A schematic diagram of yet another set of user graphical interfaces provided in the embodiments of this application;

[0045] Figure 9 A schematic diagram of another set of user graphical interfaces provided in the embodiments of this application;

[0046] Figure 10A A schematic diagram of yet another set of user graphical interfaces provided in the embodiments of this application;

[0047] Figure 10B A schematic diagram of another set of user graphical interfaces provided in the embodiments of this application;

[0048] Figure 11 A schematic diagram of yet another set of user graphical interfaces provided in the embodiments of this application;

[0049] Figure 12 A schematic diagram of another set of user graphical interfaces provided in the embodiments of this application;

[0050] Figure 13 A schematic diagram of yet another set of user graphical interfaces provided in the embodiments of this application;

[0051] Figure 14A A schematic diagram of another set of user graphical interfaces provided in the embodiments of this application;

[0052] Figure 14B A schematic diagram of yet another set of user graphical interfaces provided in the embodiments of this application;

[0053] Figure 14C A schematic diagram of another set of user graphical interfaces provided in the embodiments of this application;

[0054] Figure 15 A schematic diagram of yet another set of user graphical interfaces provided in the embodiments of this application;

[0055] Figure 16 A schematic diagram of another set of user graphical interfaces provided in the embodiments of this application;

[0056] Figure 17 A schematic diagram of yet another set of user graphical interfaces provided in the embodiments of this application;

[0057] Figure 18 A schematic diagram of another set of user graphical interfaces provided in the embodiments of this application;

[0058] Figure 19 A schematic diagram of yet another set of user graphical interfaces provided in the embodiments of this application;

[0059] Figure 20 A schematic diagram of another set of user graphical interfaces provided in the embodiments of this application;

[0060] Figure 21 A schematic diagram of yet another set of user graphical interfaces provided in the embodiments of this application;

[0061] Figure 22 A schematic diagram of another set of user graphical interfaces provided in the embodiments of this application;

[0062] Figure 23 A schematic diagram of another set of user graphical interfaces provided in the embodiments of this application;

[0063] Figure 24 A schematic diagram illustrating the structure of another electronic device provided in an embodiment of this application;

[0064] Figure 25 This is a schematic diagram of a chip system provided in an embodiment of this application. Detailed Implementation

[0065] The technical solutions of the embodiments of this application are described below with reference to the accompanying drawings. In the description of the embodiments of this application, the terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to limit the application. As used in the specification and appended claims of this application, the singular expressions "a," "the," "the," "the," and "this" are intended to also include expressions such as "one or more," unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of this application, "at least one" and "one or more" refer to one or more (including two). The term "and / or" is used to describe the relationship between related objects, indicating that three relationships can exist; for example, A and / or B can represent: 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.

[0066] References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized. The term "connection" includes direct connections and indirect connections, unless otherwise stated. "First" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated.

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

[0068] The interface display method provided in this application embodiment can be applied to the communication system provided in this application embodiment. The communication system includes multiple electronic devices. Any electronic device can be a mobile phone, tablet (PAD), large screen (i.e., smart TV, also known as smart screen), etc. It is not limited to these; the electronic device can also be a personal computer (PC), personal digital assistant (PDA), augmented reality (AR) device, virtual reality (VR) device, vehicle-to-everything (V2X) interaction device, smart screen device, or other device with near-field communication or long-field communication capabilities. Among them, PC includes desktop computers and laptop computers; the following mainly uses a laptop computer as an example to illustrate the solution of this application.

[0069] by Figure 1 Taking the communication system shown as an example, the communication system includes a mobile phone 101, a PAD 102, a PC 103, and a large screen 104.

[0070] In the above Figure 1 In the communication system shown, multiple electronic devices can establish trust relationships through methods such as account authentication or device authorization.

[0071] For example, if the system authentication accounts logged in on mobile phone 101 and PC 103 are the same, it can be determined that there is a trust relationship between mobile phone 101 and PC 103. The system authentication account can be a registered account provided by a cloud server. For example, the system authentication account can be a Honor account.

[0072] It should be understood that the trust relationship between the aforementioned multiple electronic devices can also be established through other means (such as near-field or far-field methods such as WiFi or Bluetooth), and this application embodiment does not impose any limitations on this.

[0073] For ease of description below, in a communication system, when an electronic device establishes a trust relationship with other electronic devices, this can be referred to as the electronic device joining a trust loop. And, when the electronic device leaves the aforementioned communication system after joining a trust loop, this can be referred to as the electronic device leaving the trust loop. And, when the electronic device terminates its trust relationship with other devices after joining a trust loop, this can be referred to as the electronic device leaving the trust loop.

[0074] The following is a summary of the above. Figure 1 This section introduces the short-range or long-range communication functions of electronic devices.

[0075] Among them, the short-range communication function of electronic devices can be achieved through one or more communication technologies such as Bluetooth communication technology, Near Field Communication (NFC) technology, and Wireless Local Area Network (WLAN) communication technology (e.g., Wireless Fidelity (Wi-Fi) network).

[0076] Correspondingly, to achieve short-range communication between electronic devices, the corresponding communication switches need to be turned on, such as Bluetooth and WLAN. It's important to note that if only WLAN is turned on, a connection to a WLAN network is required for communication to occur. Typically, before joining a trust loop, electronic devices will prompt you to turn on Bluetooth and WLAN, allowing communication via WLAN when connected. Even without a WLAN network connection, Bluetooth communication is possible. Of course, in some technologies, electronic devices can communicate via WLAN Direct even with WLAN turned on but not connected to a WLAN network.

[0077] Long-distance communication capabilities of electronic devices can be achieved through communication technologies such as third-generation mobile communication technology (3G), fourth-generation mobile communication technology (4G), fifth-generation mobile communication technology (5G), and sixth-generation mobile communication technology (6G).

[0078] Correspondingly, in order to achieve remote communication between electronic devices, the electronic devices need to turn on the corresponding network switches (such as mobile communication switches or WLAN switches) and connect to the network.

[0079] It should be understood that the above description of communication technologies for realizing short-range or long-range communication functions of electronic devices is based on current technological developments and does not exclude communication technologies that will emerge from future technological evolutions. Those skilled in the art can select the communication technology capable of realizing short-range or long-range communication functions of electronic devices according to actual usage needs. This application's embodiments do not impose any limitations on the communication technologies for realizing short-range or long-range communication functions of electronic devices.

[0080] After joining a trust ring, any electronic device within the ring can not only operate its own services normally, but also access the services of other electronic devices, enabling service flow between devices. These services can include screen sharing, network sharing, file sharing, and so on.

[0081] Currently, when a user wants to use an application installed on electronic device B (e.g., the target application) on electronic device A, the user first needs to use the "screen sharing" service (also known as screen mirroring) of electronic device B on electronic device A, causing electronic device A to display the desktop of electronic device B. Then, the user triggers an action on the desktop of electronic device B displayed on electronic device A, causing electronic device A to display the interface of the target application. It is evident that the user needs to perform relatively complex operations to trigger electronic device A to display the interface of the target application installed on electronic device B. This leads to a decrease in the human-computer interaction efficiency of electronic device A and a decline in the user experience.

[0082] In view of this, embodiments of this application provide an interface display method. In this method, electronic device A can display a list of applications installed on electronic device B. Users can conveniently launch applications installed on electronic device B by viewing the list of applications installed on electronic device B on electronic device A, thus enabling electronic device A to display the interfaces of the applications installed on electronic device B. This improves the human-computer interaction efficiency of electronic device A and enhances the user experience.

[0083] Next, we will introduce the structure and software architecture of the electronic device.

[0084] Figure 2 A schematic diagram of the structure of the electronic device 100 is shown.

[0085] Electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, a sensor module 180, and a display screen 194, etc. The sensor module 180 may include a pressure sensor 180A, a touch sensor 180K, etc.

[0086] It is understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on the electronic device 100. For example, in some embodiments, the electronic device may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, an antenna 2, a wireless communication module 160, an input device, and a display screen 194, etc. The input device may be a keyboard and a mouse. In other embodiments of this application, the electronic 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.

[0087] Processor 110 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0088] The controller can be the nerve center and command center of the electronic device 100. The controller can generate operation control signals according to the instruction opcode and timing signals to complete the control of fetching and executing instructions.

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

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

[0091] It is understood that the interface connection relationships between the modules illustrated in the embodiments of the present invention are merely illustrative and do not constitute a structural limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0092] The wireless communication function of electronic device 100 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

[0093] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic 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.

[0094] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via 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.

[0095] A modem processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium- to high-frequency signal.

[0096] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (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.

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

[0098] Electronic device 100 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0099] 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 miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, electronic device 100 may include one or N displays 194, where N is a positive integer greater than 1.

[0100] The external storage interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.

[0101] Internal memory 121 can be used to store computer executable program code, which includes instructions. Processor 110 executes various functional applications and data processing of electronic device 100 by running the instructions stored in internal memory 121. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of electronic device 100 (such as audio data, phonebook, etc.). Furthermore, 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.

[0102] The pressure sensor 180A is used to sense pressure signals and can convert the pressure signals into electrical signals. In some embodiments, the pressure sensor 180A can be disposed on the display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc.

[0103] Touch sensor 180K, also known as a "touch panel," can be located on display screen 194. The touch sensor 180K and display screen 194 together form a touchscreen, also known as a "touch screen." Touch sensor 180K detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 194. In other embodiments, touch sensor 180K may also be located on the surface of electronic device 100, in a different position than display screen 194.

[0104] The technical solutions provided in this application are applicable to the above-mentioned... Figure 2 The structure of the electronic device is shown.

[0105] The software system of electronic device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This embodiment of the invention uses a layered architecture of Android. TM Taking the system as an example, the software structure of electronic device 100 is illustrated.

[0106] It should be understood that in actual use, the software system of electronic devices can also be other software systems, such as Windows. TM System, Linux TM Systems, etc. This application's embodiments are not limited in this respect.

[0107] Figure 3 This is a software structure block diagram of the electronic device 100 according to an embodiment of the present invention.

[0108] A layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0109] The application layer can include a series of application packages.

[0110] like Figure 3 As shown, the application package can include camera, gallery, and calendar applications.

[0111] The application layer may further include a control center application. This application typically includes various function switches for the operating system, such as Bluetooth, cellular data, Wi-Fi, volume, and brightness adjustment. The control center application may also include shortcuts to other applications, such as a flashlight or calculator. In this embodiment, the control center application may also include functions or entry points related to the trust ring of the electronic device. For example, the control center application may be used to display the control interface for the trust ring function (hereinafter referred to as the trust ring), which will be described in detail in subsequent embodiments and will not be repeated here.

[0112] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0113] like Figure 3 As shown, the application framework layer may include a window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

[0114] The window manager is used to manage windowed applications. It can retrieve screen size, determine the presence of a status bar, lock the screen, and capture screenshots, among other things.

[0115] Content providers store and retrieve data, making that data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

[0116] A view system includes visual controls, such as controls for displaying text and controls for displaying images. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text notification icon could include views for displaying text and views for displaying images.

[0117] The phone manager is used to provide communication functions for electronic device 100. For example, it manages call status (including connection and disconnection).

[0118] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0119] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of completed downloads or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating electronic devices, and flashing indicator lights.

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

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

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

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

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

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

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

[0127] A 2D graphics engine is a graphics engine for 2D drawing.

[0128] The kernel layer is the layer between hardware and software. The kernel layer contains at least the display driver, camera driver, audio driver, and sensor driver.

[0129] Among them, sensor drivers include at least accelerometer drivers and gyroscope drivers.

[0130] The technical solutions provided in this application are applicable to the above-mentioned... Figure 3 The software architecture of the electronic device is shown.

[0131] The following will be based on the above. Figure 1 Taking the example of mobile phone 101, PAD 102, and PC 103 joining a trust ring in the illustrated communication system, the technical solution provided by the embodiments of this application will be introduced.

[0132] Users can execute the services provided by the Trust Ring through the Trust Ring's control interface.

[0133] Below are some examples of how users can open the control interface of the trust ring.

[0134] Method 1: The phone can respond to the user's three-finger swipe up on the current screen and display the trust ring control interface.

[0135] The current interface is Figure 4 Taking desktop 400 as an example, in response to the user's three-finger swipe up on desktop 400, the phone can display... Figure 4 The control interface 410 of the trust ring shown includes a control component 411. The control component 411 includes icons of devices currently added to the trust ring, such as a mobile phone icon (also called a device ball) 412, a PC icon 413, and a PAD icon 414. The mobile phone icon 412 can be highlighted to indicate that the mobile phone is the local device.

[0136] Optionally, the control component 411 may also include a device name for each device. For example, the device name for a mobile phone is "Jack's Mobile Phone"; for example, the device name for a PAD is "Jack's PAD"; for example, the device name for a PC is "Jack's PC".

[0137] Optionally, the control component 411 may also include the avatar, name (e.g., Jack) of the system authentication account logged into by the electronic device that has been added to the trust ring.

[0138] Optionally, the control component can display the avatar and name of the system authentication account logged into by the electronic device that has joined the trust ring at its center. Additionally, a device sphere can surround the control component.

[0139] For further details on the user's interaction with control component 411, please refer to the following text, which will not be elaborated here.

[0140] Method 2: The phone can respond to a user swiping down from the top of the current screen (e.g., top right) to display a drop-down menu, which includes an entry point for the Trust Ring feature. In response to the user triggering this entry point (e.g., clicking), the phone displays the Trust Ring control interface.

[0141] The current interface is Figure 4 Taking desktop 420 as an example, in response to the user swiping down from the top right side of desktop 420, the phone can display... Figure 4 The interface 430 shown is a drop-down menu interface. Interface 430 includes an entry point 431 for the trust ring function. In response to the user's click on entry point 431, the phone can also display... Figure 4 The control center interface 410 is shown. Furthermore, entry point 431 can display devices that have already been added to the trust ring.

[0142] The above Figure 4 Both methods shown assume the current interface is the desktop, but this is not a limitation in practice. For example, the current interface can also be the application interface of chat applications, video applications, or other similar applications.

[0143] It should be understood that the way users open the Trust Ring control interface on the PAD is similar to the methods described in Method 1 and Method 2 above, and will not be elaborated further.

[0144] Method 3: The PC can respond to the user's trigger operation on the Honor Workbench application icon, and the PC displays the control interface of the Trust Ring.

[0145] The current interface is Figure 5 Taking desktop 500 as an example, in response to the user's trigger operation on the Honor Workbench application icon 501, the PC displays the trust ring control interface 510. Interface 510 includes control component 511. Compared with control component 411, control component 511, in addition to including icons of devices currently joined to the trust ring, may also include introductions to services (e.g., introductions to screen sharing services, keyboard and mouse sharing services, etc.). Furthermore, compared to control component 411, in control component 511, the PC icon is highlighted, while the phone icon is not highlighted; control component 511 indicates that the PC is the local machine by highlighting the PC icon.

[0146] The triggering operation mentioned above can be a double-click operation performed by the user using the mouse.

[0147] Understandably, in actual use, users may have more ways to open the control center interface. For different electronic devices, the way to open the control center interface may be the same or different. The specific design can be based on actual usage needs, and this application embodiment does not impose any restrictions.

[0148] Next, we will introduce some examples of services that electronic devices with a trust ring can provide.

[0149] For example, an electronic device with a trust ring added may provide the services shown in Table 1 below:

[0150] Table 1

[0151]

[0152] The technical solutions provided in the embodiments of this application will be further described below in conjunction with the user's experience of using the mobile phone.

[0153] In some embodiments, electronic device A displays a control center interface, which includes control components. In response to a trigger operation on an icon of electronic device B included in the control components, electronic device A can display icons of services provided by electronic device B on the control center interface. Users can conveniently trigger services provided by electronic device B by dragging the service icons.

[0154] When the electronic device is a mobile phone or tablet, the triggering operation can be a click operation, a long press operation, etc.; when the electronic device is a PC, the triggering operation can be a double-click operation, a single-click operation, etc. Further details regarding the triggering operations in the embodiments of this application can be found here and will not be repeated hereafter.

[0155] For example, see Figure 6 The phone displays the Trust Ring control interface 600, which includes a PC icon 602. Next, in response to a trigger operation on the PC icon 602, the phone can expand to display services provided by the PC, such as displaying interface 610; interface 610 includes a screen sharing service icon 611. Compared to interface 600, interface 610, in addition to including the phone icon and the PAD icon, also includes icons for one or more services that the PC can provide (e.g., the screen sharing service icon 611). Furthermore, interface 610 also includes icons for applications installed on the PC (e.g., the "Notes" application icon, the "Browser" application icon, etc.). A detailed description of the application icons included in interface 610 is provided below and will not be repeated here.

[0156] In some possible examples, after a triggering operation on the PC icon 602, the mobile phone can display an animation of the control component 601 included in the interface 600 rotating and moving upwards, so that the moved control component 601 is located at the top of the interface 610. Furthermore, the mobile phone can also display an animation of the icon 602 expanding (enlarging), with the expanded icon 602 as shown in the container 612 in the interface 610. Further still, the container 612 corresponds to the product form of the PC, and icons of the services that the PC can provide are displayed within the container 612.

[0157] See also Figure 6 After the phone displays interface 610, in response to a drag operation on the screen sharing service icon 611 (e.g., dragging the screen sharing service icon 611 to the "Jack's Phone" icon), the phone can interact with the PC to display the PC's screen on the phone in real time, i.e., invoke the PC's screen sharing service. At this time, as... Figure 6 As shown, the mobile phone can display the trust ring control interface 620. Interface 620 includes a floating window 621, which displays the currently displayed interface of the PC. Also, as seen from interface 620, the screen sharing service icon is attached near the "Jack's Phone" icon. The user can operate the PC screen through the floating window 621.

[0158] It should be understood that users can also trigger other services on interface 610 by dragging the service icon. For example, in response to dragging the "Remote Control" icon to the "Jack's PAD" icon, the PAD triggers the remote control service for the PC; that is, the user can control the PC from the PAD.

[0159] As one possible implementation, the screen sharing service described above can be a same-source projection for the PC, meaning the PC can display the above-mentioned content on its screen. Figure 6 The interface shown in the floating window 621. Alternatively, the screen sharing service described above can be a cross-source projection for the PC, that is, the above... Figure 6 The interface shown in the floating window 621 is from the PC. The PC can display a different interface on its screen than the interface shown in the floating window 621, or the PC screen can be turned off.

[0160] It should be understood that after a mobile phone triggers the PC's screen sharing service, the mobile phone can display the PC's current interface in a floating window. Alternatively, the mobile phone can display the PC's current interface in full screen. Or, the mobile phone can display the PC's current interface in a split-screen window. This application's embodiments do not limit this.

[0161] For example, on the phone display Figure 6 In the case of interface 600 shown, in response to a trigger operation on the PC icon 602, see [link to relevant documentation]. Figure 7 The mobile phone displays interface 700, which includes icons of applications installed on the PC. In addition to icons of services provided by the PC, interface 700 may also include icons of one or more applications installed on the PC. For example, interface 700 includes an icon 701 for a note-taking application installed on the PC. Next, in response to a triggering operation on icon 701, the mobile phone can interact with the PC to display the application interface of the note-taking application installed on the PC on the mobile phone. For example, the mobile phone may display a trust ring control interface 710, which includes a floating window 711 displaying the application interface of the note-taking application installed on the PC.

[0162] For example, in response to a triggering operation on icon 701, the mobile phone can instruct the PC to launch a note-taking application (e.g., launch the note-taking application in the foreground or background). After the PC launches the note-taking application, display data related to the note-taking application can be sent to the mobile phone, and then the mobile phone displays interface 710. Interface 710 includes the display interface when the PC is running the note-taking application, such as interface 710 including a floating window 711, which includes the display interface when the PC is running the note-taking application.

[0163] For example, the content displayed in the floating window 711 can be projected from the PC to the mobile phone via a different source. It should be understood that the above example uses the mobile phone displaying the application interface of a note-taking application installed on the PC in the form of a floating window as an example to illustrate the technical solution provided in this application embodiment. In actual use, the mobile phone can also display the interface of the application installed on the PC in many other ways. For example, the mobile phone can also display the application interface of the note-taking application installed on the PC in full screen. Alternatively, the mobile phone can also display the application interface of the note-taking application installed on the PC in a split-screen window. This application embodiment does not limit this.

[0164] from Figure 7 As the corresponding example shows, users can easily launch applications installed on their PCs through the trust ring control interface displayed on their mobile phones, allowing the mobile phones to display the interfaces of the applications installed on the PCs, thus improving the user experience.

[0165] Optionally, after the phone displays interface 710, users can use the note-taking application through the floating window 711.

[0166] For example, after the phone displays interface 710, and after the phone receives a trigger operation for the application interface of the note-taking app displayed in the floating window, the phone can transmit this operation to the PC, which then receives the trigger operation. The note-taking app running on the PC executes the corresponding interface response to the trigger operation (e.g., displaying the interface for creating a new note). Afterward, the phone displays the trust ring control interface 720. Interface 720 includes a floating window 721, which includes the interface response to the aforementioned trigger operation when the PC runs the note-taking app. For example, floating window 721 includes the interface for creating a new note.

[0167] Furthermore, the icons of applications included in interface 700 can be displayed in columns according to usage frequency. For example, the phone can display the icons of the N most frequently used applications in the "Frequently Used Applications" column. The phone can also display the icons of applications installed on the PC in the "All" column. Here, N is a positive integer.

[0168] In other possible examples, the icons of applications installed on the PC included in the "All" column could be sorted alphabetically by the first letter of the application's name (in pinyin). For example, on a mobile phone display... Figure 6 In the case of interface 600 shown, in response to a trigger operation on the PC icon 602, see [link to relevant documentation]. Figure 8 The phone can display interface 800; interface 800 includes icons of services provided by the PC, as well as icons of one or more applications installed on the PC. The application icons in the "All" section of interface 800 can be arranged alphabetically. Next, in response to a swipe operation triggered by the user on interface 800, the phone can display interface 810. Interface 810 includes a search bar 812 and a first-letter location bar 811. The user can use the search bar 812 to search for applications, and the user can also use the first-letter location bar 811 to locate applications.

[0169] For example, in response to a swipe operation triggered by the user on interface 800, the icons of PC-provided services included in interface 800 are collapsed (i.e., hidden and not displayed). Furthermore, the container corresponding to the PC's product form is collapsed, for example, the container is collapsed into a PC icon. Furthermore, the control component 801 included in interface 800 is reduced in size, from a circular ring displayed in interface 800 to a semi-circular ring in interface 810. It should be understood that the user will trigger a swipe operation to instruct the phone to display more application icons if the application icons currently displayed on interface 800 do not meet the user's needs. In other words, when the user triggers the swipe operation, the user expects to see more application icons; the user is not particularly concerned about the icons of PC-provided services or other electronic devices on the trust ring. Therefore, by collapsing the icons of PC-provided services, the phone can provide more display space to show application icons.

[0170] For example, see again Figure 8 After the phone displays interface 800, in response to a triggering operation on the "W" locator included in the initial letter locator bar 811, the phone can display interface 820. Interface 820 includes icons for applications whose first letter is W, such as "WeChat". TM "The app icon."

[0171] For example, see again Figure 8 After the phone displays interface 810, in response to the user's search operation, the phone can display interface 830. Interface 830 includes the icon for the "Music" application.

[0172] Comparing interfaces 820 and 830, it's clear that interface 820 includes not only icons of applications starting with the letter "W" but also icons of other applications; interface 830 only includes the icon for the "Music" application. It should be understood that when a user triggers a search for application icons using the initial letter of the name, the user's search target is vague. Therefore, interface 820 includes icons of other applications besides those starting with "W." Conversely, when a user searches for an application's icon by entering its name, the user's search is purposeful and precise. Therefore, interface 830 only includes the icon for the "Music" application. Thus, in this example, the phone can distinguish the nature of the user's search and display application icons based on that search. This better aligns with user habits and improves the user experience.

[0173] For example, see Figure 9The phone displays the trust ring control interface 900, which includes the phone's (i.e., the device's) icon 901. Next, in response to a trigger operation on the phone's icon 901, the phone can display interface 910; interface 910 includes icons for services provided by the phone, such as the "screen sharing" service icon and the "network sharing" service icon.

[0174] In comparison with the above Figure 6 The interface 610 shown, and the above Figure 9 Interface 910 is shown. Electronic device A (e.g., a mobile phone) displays the control interface of the trust ring; in response to a trigger operation on the icon of electronic device B (e.g., a PC) included in the control component, electronic device A displays icons of services provided by electronic device B on the control interface of the trust ring. Since electronic device B and electronic device A are not the same electronic device, electronic device A also displays icons of applications already installed on electronic device B on the control interface of the trust ring. Users can conveniently launch applications already installed on electronic device B from electronic device A using the application icons, causing electronic device A to display the interface of the applications installed on electronic device B.

[0175] It should be understood that during the use of electronic device A, the user may have a need to launch an application installed on electronic device B from electronic device A. Therefore, in some technical solutions provided in the embodiments of this application, electronic device A can display the application icon already installed on electronic device B through the control interface of the trust ring, allowing the user to conveniently launch the application installed on electronic device B from electronic device A through the application icon displayed on electronic device B. This satisfies the user's needs.

[0176] In one possible example, on the phone display Figure 6 In the case of interface 600 shown, in response to a trigger operation on the PC icon 602, see [link to relevant documentation]. Figure 10AThe phone displays the Trust Ring control interface 1000. The Trust Ring control interface 1000 includes an icon 1001 of the note-taking application installed on the PC. Next, in response to a long press on the note-taking application icon 1001, the phone displays a floating animation of icon 1001 and shows the home screen 1010. After the home screen 1010 is displayed, the floating icon 1011 can move in real-time following the user's drag operation. For example, in response to a drag operation on icon 1011, the display position of icon 1011 moves in real-time following the user's drag operation, and the phone can display the home screen 1020. The position after dragging is shown as the position of icon 1021 in the home screen 1020. Then, in response to the user releasing their finger (i.e., the user's finger stops touching the screen), the phone displays the home screen 1030, which includes the icon 1031 of the note-taking application installed on the PC. Compare the icons 1032 (for the note-taking app installed on the phone) and 1031 (for the note-taking app installed on the PC) on the desktop 1030. Icon 1031 includes a badge (e.g., a PC identifier); icon 1032 does not include a badge. This badge indicates that the application corresponding to icon 1031 is installed on a PC. This allows users to intuitively distinguish that the application comes from a PC. The badge included in icon 1031 may appear in response to the user releasing their finger. It should be understood that... Figure 10A In the middle, icons with thicker lines indicate that the icon is in a floating state.

[0177] In other embodiments, the name corresponding to the above icon 1031 may be "Notes from Jack's PC" ( Figure 10A (Not shown in the image); the name corresponding to icon 1032 could be "Notes". In this way, users can intuitively distinguish that the application corresponding to icon 1031 comes from a PC.

[0178] Optionally, in some embodiments, when an application's icon is dragged to the edge of the home screen, the phone can display another home screen. Users can arrange application icons with greater flexibility.

[0179] For example, see Figure 10B The phone displays the trust ring control interface 1070, which includes an icon 1071 for the note-taking application installed on the PC. Next, in response to a long press on icon 1071, the phone displays a first desktop 1040. During this process, icon 1041 moves on the first desktop 1040 following the user's drag-and-drop action. The user's drag-and-drop action and the user's long press action are consecutive user operations.

[0180] When icon 1071 is dragged to the first position, which is located in a non-edge area of ​​the desktop, in response to the user releasing the finger, the phone adds a note-taking application icon to the first position, as described above. Figure 10A The corresponding example is shown.

[0181] When icon 1071 is dragged to a second position, located at the edge of the screen, the phone displays a second desktop 1050. The second desktop 1050 is another desktop on the phone besides the first desktop. While the phone displays the second desktop 1050, the display position of the note-taking app icon 1051 moves on the second desktop 1050 following the user's dragging action. Next, icon 1051 is dragged to a third position, located in a non-edge area of ​​the phone. In response to the user releasing the finger, the phone adds the note-taking app icon 1061 to the second desktop 1060. The aforementioned edge area can be referred to as the edge position, and the aforementioned non-edge area can also be referred to as the non-edge position.

[0182] In one possible example, the user uses the above... Figure 10A The example demonstrates how to display icons of apps installed on a PC on a mobile phone's home screen. Next, see... Figure 11 The phone displays desktop 1100, which includes an icon 1101 for the note-taking application installed on the PC. In response to a triggering action on icon 1101, the phone displays desktop 1110. Desktop 1110 includes a floating window 1111 for displaying the interface of the note-taking application installed on the PC. Alternatively, if desktop 1100 is displayed, the phone displays the note-taking application interface 1120 in response to a triggering action on icon 1102.

[0183] For example, in response to a triggering action on icon 1101, the mobile phone can instruct the PC to launch a note-taking application (e.g., launch the note-taking application in the foreground or background). After the PC launches the note-taking application, the PC can send display data related to the note-taking application to the mobile phone, thereby displaying desktop 1110 on the mobile phone.

[0184] from Figure 11 As seen in the example, when a user launches a target application (e.g., a note-taking application) installed on different electronic devices, the phone displays the target application's interface in different formats. It should be understood that because the display sizes of PC and mobile phone screens differ, the phone can display the interface of an application installed on a PC as a floating window. This improves the user experience.

[0185] It should be noted that, in the technical solutions provided in this application embodiment, when a mobile phone launches an application installed on an electronic device other than the mobile phone, the mobile phone can display the application's interface in the form of a floating window (e.g., the above). Figure 11 The floating window 1111 or the above Figure 7 (e.g., a floating window 711). Alternatively, the phone can also display the application's interface in other forms such as split-screen. In this embodiment, it is described in the form of a floating window, but this does not mean that the phone can only display the interface of applications from electronic devices other than the phone in the form of a floating window. This embodiment does not impose any restrictions on this.

[0186] In one possible example, the user uses the above... Figure 10A The example demonstrates how to display icons of apps installed on a PC on a mobile phone's home screen. Next, see... Figure 12 The phone displays desktop 1200. This desktop includes an icon 1201 for the note-taking application installed on the PC; the icon 1201's badge 1201A indicates that the note-taking application originates from the PC. Next, after the phone or PC exits the trust loop, when the phone displays its desktop, it can show desktop 1210. Comparing desktop 1210 and desktop 1200, desktop 1210 includes an icon 1211 for the note-taking application installed on the PC, with badge 1211A in a second state (e.g., black and white), indicating that the note-taking application cannot be launched; desktop 1200 includes an icon 1201 for the note-taking application installed on the PC, with badge 1201A in a first state (e.g., colored), indicating that the note-taking application can be launched. Comparing desktop 1210 and desktop 1200, it is clear that the phone can use the badge state to indicate whether an application can be launched. This allows the user to intuitively understand whether an application can be launched.

[0187] For example, see [link to example]. Figure 12 After the phone displays desktop 1210, in response to a triggering operation on the note-taking icon 1211 installed on the PC, the phone can display desktop 1230, which includes a pop-up window 1231 indicating that the application cannot be launched.

[0188] In another possible mobile phone, after the phone displays desktop 1200, and after the phone or PC exits the trust loop, the phone can display desktop 1220 when displaying the desktop. Comparing desktop 1200 and desktop 1220, the icons 1201 included in desktop 1200 can be in a first state, and the icons 1221 included in desktop 1220 can be in a second state; wherein the first state and the second state are different. For example, the first state can be a color display, and the second state can be a black and white display; or, the contrast of the icons in the first state is higher than the contrast of the icons in the second state. The first state indicates that the phone can launch the application corresponding to the icon; the second state indicates that the phone cannot launch the application corresponding to the icon.

[0189] Understandable, Figure 12 In the corresponding example, if either the phone or the PC exits the trust ring, the phone cannot launch the note-taking application installed on the PC. Therefore, the phone can change the state of the icon displayed on the phone's home screen, or it can change the state of the badge displayed on the home screen. This way, the user can intuitively obtain information that the application cannot be launched.

[0190] For example, see Figure 13 The mobile phone through the above Figure 6 In a corresponding example, the mobile phone displays the trust ring control interface 1300. Interface 1300 includes a PAD icon 1301. Next, in response to a trigger operation on the PAD icon 1301, the mobile phone can display interface 1310. Comparing interfaces 1300 and 1310, the application icon displayed in interface 1300 is the icon of the application installed on the PC; the application icon displayed in interface 1310 is the icon of the application installed on the PAD. Furthermore, interface 1300 includes icons of services provided by the PC, and interface 1310 includes icons of services provided by the PAD.

[0191] As a possible example, in response to a trigger operation on icon 1301, the mobile phone can rotate the control component 1302 included in the display interface 1300, so that the rotated PAD icon is located in the center of the interface 1300. Then, icon 1301 expands (enlarges), and the expanded icon 1301 is shown as in container 1311 in the interface 1310. Furthermore, container 1311 corresponds to the product form of the PAD, and the mobile phone can display icons of services provided by the PAD within container 1311.

[0192] See you again Figure 13After the phone displays interface 1310, in response to a swipe operation triggered by the user on interface 1310, the phone can display interface 1320. The number of application icons included in interface 1320 is greater than the number of application icons included in interface 1310. Furthermore, in response to the swipe operation, the phone displays a shrinking animation of container 1311, while simultaneously removing the service icons from the display.

[0193] See also Figure 13 After the phone displays interface 1320, in response to a triggering operation on the PC icon 1321 included in interface 1320, the phone can display interface 1330. Interface 1330 includes icons of applications installed on the PC.

[0194] from Figure 13 As seen in the corresponding example, users can easily switch between the electronic devices they want to control through the trust ring's control interface. This improves the user experience.

[0195] The following describes the technical solution provided in the embodiments of this application in further detail, taking a user's use of a PC as an example.

[0196] Further information on triggering services on a PC.

[0197] For example, the PC via the above Figure 5 The corresponding example displays the trust loop control interface. See also... Figure 14A The PC displays a trust ring control interface 1400; the trust ring control interface 1400 includes a PC icon 1401. In response to a trigger operation on the PC icon 1401, the PC displays interface 1410. Interface 1410 includes icons of services provided by the PC, such as an icon 1411 for a keyboard and mouse sharing service. Interface 1410 also includes a mobile phone icon 1412. Further, in response to a trigger operation on the PC icon 1401, the mobile phone displays an animation of rotating and shifting a control component 1402, with the shifted control component 1402 located in the center of the PC's display area, as shown in interface 1410. Further still, the mobile phone displays an animation of expanding (enlarging) the PC icon 1402, with the icon 1402 enlarged to become a container 1413. Icons of services provided by the PC are displayed on the container 1413.

[0198] Next, see Figure 14B The PC receives an operation to drag icon 1411 to icon 1412; in response to this operation, the PC triggers a keyboard and mouse sharing service to the phone, and the PC displays interface 1420. Interface 1420 includes an icon 1421 for the phone, and the PC indicates that the keyboard and mouse sharing service to the phone has been triggered by displaying an icon for the keyboard and mouse sharing service around icon 1421.

[0199] After the PC-to-phone keyboard and mouse sharing service is triggered, the mouse cursor displayed on the PC can be dragged to the phone. For example, if the mouse cursor 1440A is displayed on Jack's PC, and then the cursor 1440A is moved to the edge of Jack's PC screen (e.g., the left edge), Jack's phone will display the mouse cursor 1440B. The movement of the mouse cursor can be achieved through an input device connected to the PC (e.g., a mouse, touchpad, etc.).

[0200] Furthermore, the aforementioned interface 1420 also includes an icon 1422 for a keyboard and mouse sharing service, and an icon 1423 for a tablet. After the PC displays interface 1420, the PC receives an operation to drag icon 1422 to icon 1423. See also Figure 14C In response to this operation, the PC initiates a keyboard and mouse sharing service with the PAD, and the PC displays interface 1430. Interface 1430 includes an icon 1431 for the mobile phone and an icon 1433 for the PAD. The PC indicates that the keyboard and mouse sharing service between the PC and the mobile phone has been triggered by displaying an icon for the keyboard and mouse sharing service around icon 1431. Similarly, the PC indicates that the keyboard and mouse sharing service between the PC and the PAD has been triggered by displaying an icon for the keyboard and mouse sharing service around icon 1433.

[0201] After the keyboard and mouse sharing service between the PC and the PAD is triggered, the mouse cursor displayed on the PC can be dragged to the PAD for display. For example, if the mouse cursor 1440C is displayed on Jack's PC, and the cursor 1440C is moved to the edge of Jack's PC's display (e.g., the right edge), the mouse cursor 1440D will be displayed on Jack's PAD.

[0202] For example, the PC via the above Figure 5 The corresponding example displays the trust loop control interface. See also... Figure 15 The PC displays the trust ring control interface 1500; the trust ring control interface 1500 includes an icon 1501 for the PAD. Next, in response to a trigger operation on icon 1501, the PC can expand the services provided by the PAD, for example, the PC displays interface 1510. Interface 1510 includes an application list, which includes icons of applications installed on the PAD. Interface 1510 also includes icons of services provided by the PAD. Users can trigger the PC to launch applications installed on the PAD via the application icons, or users can trigger services provided by the PAD via the service icons.

[0203] Comparing interfaces 1501 and 1410, it can be seen that electronic device A (e.g., PC) displays the control interface of the trust ring. In response to a trigger operation on the icon of electronic device B (e.g., PAD), which is included in the control component, electronic device A can display icons of services provided by electronic device B on the control interface of the trust ring. Since electronic device B and electronic device A are not the same electronic device, electronic device A can also display icons of applications already installed on electronic device B on the control interface of the trust ring. Users can conveniently launch applications already installed on electronic device B from electronic device A using the application icons, causing electronic device A to display the interface of the applications installed on electronic device B.

[0204] It should be understood that during the use of electronic device A, the user may have a need to launch an application installed on electronic device B from electronic device A. Therefore, in some technical solutions provided in the embodiments of this application, electronic device A can display the icon of the application already installed on electronic device B through the control interface of the trust ring. This allows the user to conveniently launch the application installed on electronic device B from electronic device A through the application icon displayed on the control interface of electronic device B, thus displaying the interface of the application installed on electronic device B on electronic device A. This satisfies the user's needs.

[0205] In other examples, the icons of applications installed on the PAD included in the "All" column above may be sorted alphabetically by the first letter of the application's name (in pinyin). For example, after the PC displays the Trust Ring control interface, in response to a trigger action on the PAD icon, see [link to relevant documentation]. Figure 16 The PC can then display interface 1600. Next, in response to a swipe action triggered on interface 1600, the PC displays interface 1610. Interface 1610 includes a search bar 1612 and a first-letter location bar 1611. Users can initiate a search for applications using the search bar 1612, and users can also locate applications using the first-letter location bar 1611.

[0206] For example, after PC displays interface 1610, in response to a triggering operation on the "Y" included in the initial letter positioning bar 1611, PC can display interface 1620. Interface 1620 includes icons for applications that begin with the letter Y, such as the icon for the "Music" application.

[0207] For example, after PC displays interface 1610, in response to the user's search operation, PC may display interface 1630. Interface 1630 includes an icon for the "Music" application.

[0208] Comparing interfaces 1620 and 1630, it's clear that interface 1620 includes not only icons of applications starting with the letter "Y" but also icons of other applications; interface 1630 only includes the icon for the "Music" application. It should be understood that when a user triggers a search for application icons using the initial letter of the search term, the user's search target is vague. Therefore, interface 1620 includes not only icons of applications starting with the letter "Y" but also icons of other applications. Conversely, when a user searches for an application's icon by entering its name, the user's search is purposeful and precise. Therefore, interface 1630 only includes the icon for the "Music" application. Thus, in this example, the phone can distinguish the nature of the user's search and display application icons based on that search. This better aligns with user habits and improves the user experience.

[0209] For example, in a PC via the above Figure 15 The corresponding example displays the trust loop control interface. For example, see [link to example]. Figure 17 The PC displays interface 1700, which includes an icon 1701 for the note-taking application. Next, in response to a triggering action on icon 1701, the PC can display interface 1710, which includes a floating window 1711. The floating window 1711 displays the application interface of the note-taking application installed on the PAD.

[0210] For example, in response to a triggering action on icon 1701, the PC can instruct the PAD to launch a note-taking application (e.g., launch the note-taking application in the foreground or background of the PAD). After the PAD launches the note-taking application, the PAD can send display data related to the note-taking application to the PC, and the PC will then display interface 1710.

[0211] For example, the content displayed in the floating window 1711 can be projected from the PAD onto the PC via a different source. It should be understood that the above example illustrates the technical solution provided in this application by showing the application interface of a note-taking application installed on the PAD as a floating window on the PC. In actual use, the PC can also display the interface of the application installed on the PAD in many other ways. For example, the PC can also display the application interface of the note-taking application installed on the PAD in full screen. This application does not limit this.

[0212] from Figure 17 As the corresponding example shows, users can easily launch applications installed on the PAD through the trust ring control interface displayed on the PC, which improves the user experience.

[0213] Optionally, after the PC display interface 1710, users can use the note-taking application through the floating window 1711.

[0214] For example, after the PC displays interface 1710, and after the PC receives a trigger operation for the application interface of the note-taking application displayed in the floating window, the PC can transmit this operation to the mobile phone, which then receives the trigger operation. The note-taking application running on the mobile phone executes the corresponding interface response to the trigger operation (e.g., displaying the interface for creating a new note). Afterwards, the PC displays the trust ring control interface. The trust ring control interface includes a floating window, which includes the interface response to the aforementioned trigger operation when the mobile phone is running the note-taking application. This process is similar to the above... Figure 7 The corresponding examples are similar and will not be repeated here.

[0215] For example, in a PC via the above Figure 15 The corresponding example displays the trust loop control interface. For example, see [link to example]. Figure 18 The PC displays interface 1800. Next, the PC receives a right-click operation on icon 1801 (referred to as a right-click trigger operation); in response to this operation, the PC can display interface 1810, which includes a menu 1811 for the note-taking application. The note-taking application menu 1811 includes a first option 1811A and a second option 1811B. The user can launch the note-taking application through the first option 1811A, and the user can display the note-taking application icon on the PC desktop through the second option 1811B.

[0216] For example, in response to a trigger operation on the first option 1811A, the phone displays interface 1820. Interface 1820 includes a floating window 1821, which displays the interface of a note-taking application installed on the PAD.

[0217] For example, in response to a triggering operation on the second option 1811B, the phone switches to the home screen 1830, which includes an icon 1831 for a note-taking application. Furthermore, icon 1831 includes a badge 1831A. This badge 1831A indicates that the note-taking application corresponding to icon 1831 originates from the tablet.

[0218] Similar to how users use mobile phones, PCs can indicate whether a note-taking application is available by the status of a badge. Alternatively, PCs can also indicate whether a note-taking application is available by the status of its icon. Specifically, as described above... Figure 12 The corresponding examples are similar, and will not be repeated here.

[0219] For example, in a PC via the above Figure 17 The corresponding example is after launching the note-taking application installed on the PAD. See also... Figure 19The phone displays interface 1900, which includes a floating window 1901. Floating window 1901 displays the application interface of a note-taking app installed on the PAD. Floating window 1901 includes a second option 1901A, which allows the user to display the note-taking app icon on the PC desktop. For example, in response to a triggering operation of the second option 1901A, the PC displays interface 1910, which includes the note-taking app icon 1911.

[0220] from Figure 19 As seen in the corresponding example, after the PC displays the note-taking application interface installed on the PAD as a floating window, it can create a shortcut to the note-taking application on the PC's desktop. This allows the user to subsequently launch the note-taking application from the desktop, enabling the PC to display the interface of the application installed on device B. This improves the user experience and makes operation more convenient.

[0221] For example, in a PC via the above Figure 17 The corresponding example is after launching the note-taking application installed on the PAD. See also... Figure 20 The mobile phone displays interface 2000; interface 2000 includes a floating window 2001; the floating window 2001 is used to display the interface of the note-taking application installed on the PAD. The floating window 2001 includes a maximize control 2001A. The maximize control 2001A is used to trigger the PC to display the note-taking application interface in full-screen (window) mode. Next, in response to the triggering operation of the maximize control 2001A, the PC can display a full-screen window interface 2010; the full-screen window interface 2010 is used to display the interface of the note-taking application installed on the PAD. It should be understood that, due to... Figure 20 During this process, the user launches the interface of the application installed on the PAD. Applications on the PAD may have various forms and different interface layouts, such as floating window interfaces, full-screen interfaces, etc.

[0222] The full-screen window interface 2010 includes a second control 2011A. In response to a trigger operation on the second control 2011A, the PC displays interface 2020. Interface 2020 includes a third control 2021. Subsequently, in response to a trigger operation on the third control 2021, the PC displays a desktop 2030. Desktop 2030 includes an icon 2031 for a note-taking application installed on the PAD.

[0223] pass Figure 20As the process shows, when a user uses a note-taking application installed on a PAD on a PC, the PC can display the PAD's note-taking application interface in a full-screen window. The user can then save the note-taking application icon to the PC's desktop from this full-screen window. This allows the user to easily launch the PAD-installed note-taking application later via the desktop icon, further enhancing the ease of application launch.

[0224] For example, in a PC via the above Figure 15 In the corresponding example, the PC displays the control interface of the trust ring. See also... Figure 21 The PC displays interface 2100. Interface 2100 includes a mobile phone icon 2101. Next, in response to a triggering operation on icon 2101, the PC can display interface 2110. Comparing interface 2110 and interface 2100, interface 2110 includes icons of services provided by the mobile phone, and also includes icons of applications installed on the mobile phone. Furthermore, in response to a triggering operation on icon 2101, the PC can display a rotation animation of control component 2102. Then, the mobile phone icon 2101 expands (enlarges), and the expanded icon 2101 is shown as in container 2111 in interface 2110. The PC displays icons of services provided by the mobile phone within container 2111.

[0225] from Figure 21 As seen in the corresponding example, users can easily switch between the electronic devices they want to control through the trust ring's control interface. This improves the user experience.

[0226] It should be understood that, through the technical solutions provided in the embodiments of this application, users can also use electronic device A to simultaneously launch multiple applications installed on other electronic devices. These other electronic devices can be different from electronic device A.

[0227] For example, taking electronic device A as a PC, see [link to relevant documentation]. Figure 22 The PC displays a desktop 2200, which includes an icon 2201 for the note-taking application installed on the PAD, an icon 2202 for the note-taking application installed on the PC, and an icon 2203 for the note-taking application installed on the mobile phone. Icon 2201 is identified by a badge 2201A indicating that the application is installed on the PAD, and icon 2203 is identified by a badge 2203A indicating that the application is installed on the mobile phone.

[0228] Next, in response to a triggering action on icon 2203, the PC can display desktop 2210. Desktop 2210 includes a floating window 2211, which displays the application interface of a note-taking application installed on the phone.

[0229] For example, in response to a triggering action on icon 2203, the PC indicates that the mobile phone can launch the note-taking application; after the note-taking application is launched, the PC displays desktop 2210.

[0230] Subsequently, in response to a triggering operation on the icon 2212 included on the desktop 2210, the PC can display an interface 2220, which includes a window 2222 and a floating window 2221. The window 2222 displays the interface of a note-taking application installed on the PC.

[0231] The floating window 2221 and the window 2222 included in the interface 2220 are visible. The floating window 2221 includes a navigation bar 2223, while the window 2222 does not include a navigation bar. The navigation bar allows users to more conveniently operate applications installed on their mobile phones via a PC.

[0232] It should be understood that when a PC displays an application installed on a PAD via a floating window, that floating window may also include a navigation bar.

[0233] For example, taking electronic device A as a mobile phone, see [link to relevant documentation]. Figure 23 The phone displays desktop 2300, which includes icons 2301 for the note-taking application installed on the PAD, 2302 for the note-taking application installed on the PC, and 2303 for the note-taking application installed on the phone.

[0234] Next, in response to a trigger operation on icon 2302, the phone displays desktop 2310. Desktop 2310 includes a floating window 2311, which displays the application interface of the note-taking application installed on the PC. Then, in response to a trigger operation on icon 2312 included in desktop 2310, the PC displays interface 2320. Interface 2320 is the application interface of the note-taking application installed on the phone. Interface 2320 also includes a floating window 2321.

[0235] It should be noted that the personal information used in the technical solution of this application is limited to information for which individual consent has been obtained, including but not limited to notifying and reminding users to read the relevant user agreement (notification) and sign the agreement (authorization) which includes authorization of relevant user information before users use the function.

[0236] Based on the algorithmic steps of the various examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in conjunction with the embodiments, but such implementations should not be considered beyond the scope of this application.

[0237] This embodiment can divide the electronic device into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0238] This application also provides an electronic device, such as... Figure 24 As shown, the electronic device may include one or more processors 2501, memory 2502 and communication interfaces 2503.

[0239] The memory 2502, communication interface 2503, and processor 2501 are coupled together. For example, the memory 2502, communication interface 2503, and processor 2501 can be coupled together via bus 2504.

[0240] The communication interface 2503 is used for data transmission with other devices. The memory 2502 stores computer program code. The computer program code includes computer instructions, which, when executed by the processor 2501, cause the electronic device to perform the relevant method steps in the above-described method embodiments of this application.

[0241] The processor 2501 can be a processor or controller, such as a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with this disclosure. The processor can also be a combination that implements computational functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0242] The bus 2504 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus 2504 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 24 The symbol is represented by only one line, but this does not mean that there is only one bus or one type of bus.

[0243] This application also provides a chip system, such as... Figure 25 As shown, the chip system 2600 includes at least one processor 2601 and at least one interface circuit 2602. The processor 2601 and the interface circuit 2602 are interconnected via lines. For example, the interface circuit 2602 can be used to receive signals from other devices (e.g., the memory of an electronic device). As another example, the interface circuit 2602 can be used to send signals to other devices (e.g., the processor 2601). Exemplarily, the interface circuit 2602 can read instructions stored in memory and send those instructions to the processor 2601. When the instructions are executed by the processor 2601, the electronic device can perform the steps in the above embodiments. Of course, the chip system may also include other discrete devices, and this application embodiment does not specifically limit this.

[0244] This application also provides a computer-readable storage medium storing computer program code. When the processor executes the computer program code, the electronic device executes the relevant method steps in the above method embodiments.

[0245] This application also provides a computer program product that, when run on a computer, causes the computer to execute the relevant method steps described in the above method embodiments.

[0246] The electronic devices, computer-readable storage media, or computer program products provided in this application are all used to perform the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

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

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

[0249] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0250] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0251] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, in essence, or the part that contributes, or all or part of the technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor 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.

[0252] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for displaying an interface, characterized in that, The method is applied to a first device, which establishes a communication connection with a second device; the method includes: The first device displays a first interface, which includes a first device identifier indicating the first device and a second device identifier indicating the second device; In response to a trigger operation on the second device identifier, the first device displays a second interface; the second interface includes a first service identifier and a first application icon, the first service identifier indicating a first service provided by the second device, and the first application icon indicating a first application installed on the second device; When the first service identifier is dragged to the first device identifier, the first device executes the first service by interacting with the second device; When the first device receives a trigger operation on the first application icon, the first device displays a third interface, which includes the display interface when the second device runs the first application.

2. The method according to claim 1, characterized in that, The second interface also includes the first device identifier; after the first device displays the second interface, the method further includes: In response to a trigger operation on the first device identifier, the first device displays a fourth interface, the fourth interface including a second service identifier indicating a second service provided by the first device; the fourth interface does not include application icons.

3. The method according to claim 1 or 2, characterized in that, After the first device displays the second interface, the method further includes: In response to a first long press operation on the first application icon, the first device displays the first desktop and the second application icon of the first device; Wherein, the second application icon corresponds to the first application. During the process of the first device displaying the first desktop, the second application icon moves on the first desktop following the user's first drag operation. The first drag operation and the first long press operation are consecutive operations of the user. When the second application icon is dragged to the first position on the first desktop, in response to the user's release operation, the first device adds a third application icon to the first desktop, and the third application icon corresponds to the first application; In response to a triggering operation on the third application icon, the first device displays the third interface.

4. The method according to claim 3, characterized in that, The first position is a non-edge position in the first desktop; the method further includes: In response to the second application icon being dragged to a second position on the first desktop, the first device displays a second desktop, the second position being located at the edge of the first desktop; After the first device displays the second desktop, in response to the user's release operation, the first device adds a third application icon to the second desktop.

5. The method according to claim 3, characterized in that, The third application icon includes a badge, and the badge's state includes a first state or a second state; When the superscript is in the first state, the method further includes: In response to a trigger operation on the third application icon, the first device displays the third interface; When the superscript is in the second state, the method further includes: In response to a triggering operation on the third application icon, the first device displays a prompt indicating that the first application has not been launched.

6. The method according to claim 1 or 2, characterized in that, After the first device displays the second interface, the method further includes: In response to a first operation on the first application icon, the first device displays a first menu, the first menu including a first option and a second option; When the first option is triggered, the first device displays the third interface; When the second option is triggered, the first device adds a fourth application icon to the desktop of the first device, and the fourth application icon corresponds to the first application.

7. The method according to any one of claims 1-6, characterized in that, The first device displays a third interface, including: The first device displays the third interface through the first floating window; the first floating window includes a first control; The method further includes: In response to the triggering operation of the first control, a fifth application icon is added to the desktop of the first device, and the fifth application icon corresponds to the first application.

8. The method according to claim 7, characterized in that, The first floating window also includes a second control; The method further includes: In response to the triggering operation of the second control, the first device displays the third interface in full screen, and the first device displays adjustment controls; In response to a triggering operation on the adjustment control, the first device displays a second menu; the second menu includes a third control; In response to the triggering operation of the third control, a sixth application icon is added to the desktop of the first device, the sixth application icon corresponding to the first application.

9. The method according to any one of claims 1-8, characterized in that, The first device and the third device establish a communication connection; the second interface also includes a third device identifier that indicates the third device; After the first device displays the second interface, the method further includes: In response to a trigger operation on the third device identifier, the first device displays a fifth interface; the fifth interface includes a third service identifier and a seventh application icon, the third service identifier indicating a third service provided by the third device, and the seventh application icon indicating a second application installed on the third device.

10. The method according to claim 9, characterized in that, After the first device displays the fifth interface, the method further includes: In response to a swipe action triggered on the fifth interface, the first device displays a sixth interface; the sixth interface includes icons of applications installed on the third device, but does not include service identifiers.

11. The method according to claim 10, characterized in that, The sixth interface also includes the first device identifier and the second device identifier; In response to a trigger operation on the second device identifier, the first device displays the seventh interface; The seventh interface includes icons for applications installed on the second device, but does not include service identifiers.

12. The method according to claim 10 or 11, characterized in that, The sixth interface also includes a first application bar and a second application bar; The method further includes: The first device displays icons of frequently used applications installed on the second device in the display area corresponding to the first application bar; The first device displays the icon of each application installed on the second device in the display area corresponding to the second application bar.

13. The method according to claim 12, characterized in that, The application icons displayed in the display area corresponding to the second application bar are sorted alphabetically by their first letter; the sixth interface also includes a first letter positioning bar, which includes the target letter; the method further includes: In response to a triggering operation on the target letter, the first device displays an icon of the application whose first letter is the target letter in the sixth interface.

14. The method according to any one of claims 1-13, characterized in that, The first device displays a third interface, including: The first device displays the third interface in full screen; or, The first device displays the third interface in a floating window; or, The first device displays the third interface in a split-screen window.

15. The method according to any one of claims 1-14, characterized in that, After the third interface is displayed on the first device, the method further includes: The first device receives a second operation on the display interface of the second device when the first application is running; In response to the second operation, the first device displays a seventh interface by interacting with the second device; the seventh interface includes the interface response of the second device to the second operation when the second device runs the first application.

16. The method according to any one of claims 1-15, characterized in that, If the first service includes a screen sharing service, performing the first service includes: displaying an interface from the second device on the second interface; If the first service includes a keyboard and mouse sharing service, the execution of the first service includes: the second device displaying the cursor of the mouse from the first device.

17. The method according to any one of claims 1-16, characterized in that, The display interface of the second device when running the first application is projected from the second device to the first device via a different source projection.

18. An electronic device, characterized in that, The electronic device includes a processor and a memory; the processor is coupled to the memory; the memory is used to store computer program code; the computer program code includes computer instructions, which, when executed by the processor, cause the electronic device to perform the method as described in any one of claims 1-17.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the method as described in any one of claims 1-17.

Images