Interface display method and electronic device

Abstract

The embodiment of the present application is suitable for the technical field of data processing, and provides an interface display method and an electronic device. The first card is displayed by responding to the first operation on the first device icon, the first device icon is the icon of the first device in the trust ring device interface, and the first card is used for displaying at least one shared service control. Then, the first capsule icon corresponding to the target shared service control is displayed by responding to the second operation on any shared service control (target shared service control) displayed on the first card. The moving range of the first capsule icon is any range on the trust ring device interface. In this way, in the setting process of the trust ring, the first capsule icon appearing in the interface can be moved anywhere on the trust ring setting interface. Compared with the traditional method in which the icon can only move along the preset track in the system, the interface display method provided in the embodiment of the present application has more moving tracks of the first capsule icon, and the user experience is improved.

Description

Technical Field

[0001] This application relates to the field of data processing, and more specifically, to an interface display method and an electronic device. Background Technology

[0002] Currently, multiple electronic devices form a trust ring by connecting to the same local area network or directly (e.g., establishing a Wi-Fi Direct connection or a Bluetooth connection) through trusted authentication. Electronic devices within this trust ring can then collaborate on management and share resources.

[0003] For example, a mobile phone and a portable Android device (PAD) are connected to the same local area network, forming a trust ring. The PAD is connected to a mouse and keyboard, and the mobile phone can use the mouse and keyboard connected to the PAD through the trust ring. Before using the mouse and keyboard connected to the PAD, the mobile phone usually needs to drag the icons of the mouse and keyboard connected to the PAD to the phone's icon in the trust ring's settings interface to grant the phone permission to use the mouse and keyboard. However, currently, the icons of shareable resources (such as the mouse and keyboard) are usually drawn using operating system plugins and moved based on operating system control logic. This results in a monotonous dynamic effect when dragging the icons of shareable resources, affecting the user experience.

[0004] Therefore, how to enrich the dynamic effects of the shareable resource icons during the trust ring setup process has become an urgent problem to be solved. Summary of the Invention

[0005] This application provides an interface display method that can enrich the dynamic effects of shareable resource icons during the trust ring setup process.

[0006] Firstly, a method for displaying an interface is provided, the method comprising:

[0007] In response to a first operation on the first device icon, a first card is displayed. The first device icon is the icon of the first device in the trust ring device interface. The first card is used to display at least one shared business control.

[0008] In response to a second operation on the target shared business control, a first capsule icon corresponding to the target shared business control is displayed. The target shared business control is any shared business control displayed on the first card. The movement range of the first capsule icon is any range on the trust ring device interface.

[0009] The first device icon can also be referred to as the first icon. The first device icon can refer to the bubble icon 10C3 of the PC in the Trust Ring device interface 10C. The first card can refer to the card displaying the shared services of the first device; for example, the first card could be like...Figure 7 The card shown is 10C41. It is understood that the first card includes multiple shared business controls. It is understood that the operation on the target shared business control can be a click operation or a long-press operation; this application embodiment does not limit this. The first capsule icon can be as follows: Figure 8 The second keyboard and mouse shared capsule icon 10C42A is shown in (b) of the image.

[0010] The interface display method provided in this application embodiment displays a first card in response to a first operation on a first device icon. The first device icon is the icon of the first device in the trust ring device interface, and the first card is used to display at least one shared business control. Then, in response to a second operation on displaying any shared business control (target shared business control) on the first card, a first capsule icon corresponding to the target shared business control is displayed. The movement range of the first capsule icon is any range on the trust ring device interface. This allows the first capsule icon appearing in the interface to move arbitrarily on the trust ring setting interface during the trust ring setup process. Compared with traditional methods where the icon can only move according to a preset trajectory in the system, the interface display method provided in this application embodiment provides a richer movement trajectory for the first capsule icon, improving the user experience.

[0011] In conjunction with the first aspect, in some embodiments of the first aspect, the second operation on the target shared business control includes: performing a long press operation on the target shared business control; in response to the second operation on the target shared business control, displaying a first capsule icon corresponding to the target shared business control includes: in response to the long press operation on the target shared business control, displaying a first capsule icon corresponding to the target shared business control, wherein the first capsule icon is a capsule icon in a moving state.

[0012] In this way, the target shared business control only requires a long press operation to display the first capsule icon that can be moved freely on the trust ring settings interface, which improves the convenience and efficiency of moving the first capsule icon.

[0013] In conjunction with the first aspect, in some embodiments of the first aspect, a second operation on the target shared business control includes: clicking the target shared business control to display a second capsule icon, the second capsule icon being an initial capsule icon; dragging the second capsule icon; and, in response to the second operation on the target shared business control, displaying a first capsule icon corresponding to the target shared business control, including: in response to dragging the second capsule icon, displaying the first capsule icon corresponding to the target shared business control, the first capsule icon being a moved capsule icon.

[0014] The second capsule icon can refer to the initial capsule icon; for example, the second capsule icon can refer to... Figure 8 The first keyboard and mouse shared capsule icon 10C42 is shown in (a) in the image.

[0015] Thus, the process of displaying the first capsule icon is divided into two parts. First, the second capsule icon is displayed by clicking the target shared business control. Then, the first capsule icon is displayed when the second capsule icon is dragged. This avoids the situation where the first capsule icon cannot be displayed due to the user accidentally releasing the button when the user directly displays the first capsule icon by long-pressing the target shared business control, thus improving the fault tolerance of displaying the first capsule icon.

[0016] In conjunction with the first aspect, in some embodiments of the first aspect, the method further includes: when the first capsule icon is detected to move to the second device icon, displaying a first bubble icon, wherein the second device icon refers to the second device in the trust ring device interface, and the first bubble icon is used to indicate that the second device has successfully established the target shared service, wherein the target shared service refers to the shared service corresponding to the target shared service control.

[0017] The first bubble icon can refer to a bubble icon that indicates a successful connection. For example, the first bubble icon can refer to... Figure 13 The first successful connection bubble icon 10C44 is shown in (a) in the image.

[0018] The interface display method provided in this application embodiment detects that the first capsule icon moves to the second device icon, and then displays a first bubble icon. The second device icon refers to the second device in the trust ring device interface, and the first bubble icon is used to indicate that the second device has successfully established a target shared service. The target shared service refers to the shared service corresponding to the target shared service control. This is equivalent to switching the first capsule icon displayed during the movement process to the first bubble icon during the establishment of the target shared service by the second device, which enriches the display mode of the icon during the establishment of the target shared service by the second device and improves the user experience.

[0019] In conjunction with the first aspect, in some embodiments of the first aspect, before displaying the first bubble icon, the method further includes: displaying a second bubble icon, the second bubble icon being used to indicate that the second device is waiting to establish a target shared service.

[0020] The second bubble icon can refer to a bubble icon in the connection waiting state, for example, the second bubble icon can refer to the first connection waiting bubble 10C43.

[0021] The interface display method provided in this application embodiment detects that when the first capsule icon moves to the second device icon, it displays a second bubble icon in a connection waiting state, and then displays a first bubble icon in a connection successful state. It is understood that it usually takes a long time for the second device to establish a target shared service. If the second bubble icon is not displayed, the user cannot know the current status of the second device while waiting to establish the target shared service. By displaying the second bubble icon in the connection waiting state, the user is prompted that the target shared service is being established and only needs to wait. No additional operation is required, thereby avoiding system lag caused by the user performing other operations.

[0022] In conjunction with the first aspect, in some embodiments of the first aspect, after displaying the first bubble icon, the method further includes: when it is detected that the first bubble icon has moved back to the first device icon, turning off the first bubble icon and closing the target sharing service established by the second device.

[0023] The process of moving the first bubble icon back to the first device icon and closing the first bubble icon can be seen in the example below. Figure 13 (b) and Figure 13 As shown in (c), when the first successful connection bubble icon 10C44 is dragged back to the PC bubble icon 10C3, the first successful connection bubble icon 10C44 is closed.

[0024] The interface display method provided in this application embodiment can close the target shared service established by the second device when the first bubble icon is moved back to the first device icon, thereby improving the convenience of closing the target shared service established by the second device.

[0025] In conjunction with the first aspect, in some embodiments of the first aspect, the method further includes: in response to clicking the first bubble icon, displaying a third capsule icon, wherein the third capsule icon displays a first device identifier corresponding to the target shared service.

[0026] The third capsule icon can refer to a capsule icon in its completed form. For example, the third capsule icon could be like this: Figure 12 The third keyboard and mouse shared capsule icon 10C45 is shown in (b) of the image.

[0027] In conjunction with the first aspect, in some embodiments of the first aspect, the third capsule icon further includes a first close button, and the method further includes: in response to an operation on the first close button, closing the third capsule icon and closing the target sharing service established by the second device.

[0028] In response to the operation of the first close button, the third capsule icon is closed, and the target sharing service established by the second device is also closed. See, for example... Figure 12 (c) and Figure 12As shown in (d), clicking the close button on the third keyboard and mouse sharing capsule icon 10C45 closes the third keyboard and mouse sharing capsule icon 10C45. Simultaneously closing the third keyboard and mouse sharing capsule icon 10C45 closes the target sharing service established by the second device.

[0029] The interface display method provided in this application embodiment displays a third capsule icon in response to clicking the first bubble icon, and then closes the third capsule icon and closes the target sharing service established by the second device in response to the operation of the first close button. This is equivalent to being able to close the target sharing service established by the second device simply by operating the first bubble icon displayed at the second device icon, which improves the intuitiveness of closing the target sharing service established by the second device.

[0030] In conjunction with the first aspect, in some embodiments of the first aspect, the method further includes: detecting that the first capsule icon has not moved to the second device icon, and detecting when the user raises their hand, displaying the second capsule icon, which is the capsule icon in the initial state.

[0031] When the user raises their hand, the first capsule icon does not move to the second device icon, which is equivalent to the user canceling the operation to establish service sharing. Based on this, the capsule icon in its moving state can be switched back to the initial capsule icon. For details, please refer to [link to documentation]. Figure 15 (a) and Figure 15 As shown in (b) of the diagram.

[0032] It should be noted that service sharing can refer to sharing services from one electronic device within a trust ring with other electronic devices in the same ring, enabling those other devices to perform those services. Services can refer to the hardware and software resources within an electronic device. From the perspective of the electronic device, this is equivalent to transferring the hardware and software resources that serve other electronic devices to the current electronic device; therefore, service sharing can also be called service transfer.

[0033] In conjunction with the first aspect, in some embodiments of the first aspect, the second capsule icon includes a second close button, and the method further includes: closing the second capsule icon in response to a click operation on the second close button.

[0034] The interface display method provided in this application embodiment allows the second capsule icon (i.e., the second capsule icon) to be closed via the second close button on the second capsule icon when the initial state capsule icon is displayed, which means canceling the operation of establishing business sharing. This improves the convenience of canceling the establishment of business sharing.

[0035] In conjunction with the first aspect, in some embodiments of the first aspect, the method further includes: in response to a drag operation on the first bubble icon, determining whether the first bubble icon has moved to a third device icon, the third device icon referring to the icon of a third device in the trust ring device interface; if the first bubble icon has moved to the third device icon, then displaying the third bubble icon, the third bubble icon being used to indicate that the third device has successfully established the target sharing service.

[0036] The third device icon can refer to the icon of any electronic device (third device) in the trust ring other than the first and second devices. For example, if the trust ring includes a PAD, a mobile phone, and a PC, and the first device is the PC, the second device is the mobile phone, then the third device could refer to the PAD in the trust ring. Figure 14 The PAD bubble icon 10C2 shown in (b) is a third bubble icon. This third bubble icon can be used to indicate that the third device has successfully established a target sharing service, which is a target sharing service successfully established by the second device. The third bubble icon can refer to, for example... Figure 14 The second successful connection bubble icon 10C47 is shown in (d) in the image.

[0037] The interface display method provided in this application embodiment, after the second device successfully establishes the target shared service, displays a third bubble icon indicating that the third device has successfully established the target shared service by dragging the first bubble icon displayed at the second device icon and dragging the first bubble icon to the third device icon. This allows the third device to directly establish the target shared service by dragging the first bubble icon displayed at the second device icon, avoiding the situation where the previous target shared service must be disconnected before establishing the target shared service on the new device, thus improving the efficiency and convenience of establishing the target shared service again.

[0038] In conjunction with the first aspect, in some embodiments of the first aspect, before displaying the third bubble icon, the method further includes: displaying a fourth bubble icon, the fourth bubble icon being used to indicate that the third device is waiting to establish a target shared service.

[0039] The fourth bubble image can be used to indicate that the third device is waiting to establish a target sharing service. The fourth bubble icon can be as follows: Figure 14 The second connection waiting bubble icon 10C46 is shown in (c) in the diagram.

[0040] The interface display method provided in this application displays a fourth bubble icon in a connection waiting state and then displays a third bubble icon in a connection successful state during the process of establishing a target shared service on a third device. It is understood that it usually takes a long time for a third device to establish a target shared service. If the fourth bubble icon is not displayed, the user will not be able to know the current status of the third device while waiting to establish the target shared service. By displaying the fourth bubble icon in the connection waiting state, the user is prompted that the target shared service is being established and only needs to wait. No additional operation is required, thereby avoiding system lag caused by the user performing other operations.

[0041] In a second aspect, a user interface display device is provided, including a unit for performing any of the methods in the first aspect. This device may be a server, a terminal device, or a chip within a terminal device. The device may include an input unit and a processing unit.

[0042] When the device is a terminal device, the processing unit may be a processor, and the input unit may be a communication interface; the terminal device may also include a memory for storing computer program code, which, when the processor executes the computer program code stored in the memory, causes the terminal device to perform any of the methods in the first aspect.

[0043] When the device is a chip within a terminal device, the processing unit can be an internal processing unit of the chip, and the input unit can be an output interface, pin, or circuit, etc.; the chip may also include a memory, which can be an internal memory of the chip (e.g., a register, cache, etc.) or an external memory (e.g., a read-only memory, random access memory, etc.); the memory is used to store computer program code, and when the processor executes the computer program code stored in the memory, the chip performs any of the methods in the first aspect.

[0044] In one possible implementation, the memory stores computer program code; the processor executes the computer program code stored in the memory, and when the computer program code stored in the memory is executed, the processor performs the following actions: in response to a first operation on a first device icon, displaying a first card, the first device icon being the icon of a first device in the trust ring device interface, the first card being used to display at least one shared business control; in response to a second operation on a target shared business control, displaying a first capsule icon corresponding to the target shared business control, the target shared business control being any shared business control displayed on the first card, the first capsule icon having a movement range of any range on the trust ring device interface.

[0045] Thirdly, a computer-readable storage medium is provided, the computer-readable storage medium storing computer program code, which, when executed by an interface display device, causes the interface display device to perform any of the interface display methods in the first aspect.

[0046] Fourthly, a computer program product is provided, the computer program product comprising: computer program code, which, when executed by an interface display device, causes the interface display device to perform any of the apparatus methods in the first aspect.

[0047] The interface display method and electronic device provided in this application embodiment, in response to a first operation on a first device icon, displays a first card. The first device icon is the icon of the first device in the trust ring device interface, and the first card is used to display at least one shared business control. Then, in response to a second operation on displaying any shared business control (target shared business control) on the first card, a first capsule icon corresponding to the target shared business control is displayed. The movement range of the first capsule icon is any range on the trust ring device interface. This allows the first capsule icon appearing in the interface to move arbitrarily on the trust ring setting interface during the trust ring setup process. Compared with the traditional method where the icon can only move according to a preset trajectory in the system, the interface display method provided in this application embodiment provides a richer movement trajectory for the first capsule icon, improving the user experience. Attached Figure Description

[0048] Figure 1 This is a schematic diagram of a trust loop that includes electronic devices;

[0049] Figure 2 This is a schematic diagram of a hardware system for an electronic device applicable to this application;

[0050] Figure 3 This is a schematic diagram of a software system applicable to an electronic device of this application;

[0051] Figure 4 This is a schematic diagram of an interface display method provided in an embodiment of this application;

[0052] Figure 5 This is a schematic diagram of another interface display method provided in an embodiment of this application;

[0053] Figure 6 This is a schematic diagram of another interface display method provided in an embodiment of this application;

[0054] Figure 7 This is a schematic diagram of another interface display method provided in an embodiment of this application;

[0055] Figure 8This is a schematic diagram of another interface display method provided in an embodiment of this application;

[0056] Figure 9 This is a schematic diagram of another interface display method provided in an embodiment of this application;

[0057] Figure 10 This is a schematic diagram of another interface display method provided in an embodiment of this application;

[0058] Figure 11 This is a schematic diagram of another interface display method provided in an embodiment of this application;

[0059] Figure 12 This is a schematic diagram of another interface display method provided in an embodiment of this application;

[0060] Figure 13 This is a schematic diagram of another interface display method provided in an embodiment of this application;

[0061] Figure 14 This is a schematic diagram of another interface display method provided in an embodiment of this application;

[0062] Figure 15 This is a schematic diagram of another interface display method provided in an embodiment of this application;

[0063] Figure 16 This is a schematic diagram of the structure of an interface layout module and a service interaction control module provided in an embodiment of this application;

[0064] Figure 17 These are schematic diagrams of different forms of capsule icons provided in the embodiments of this application;

[0065] Figure 18 These are schematic diagrams of different forms of bubble icons provided in the embodiments of this application;

[0066] Figure 19 This is a flowchart illustrating an interface display method provided in an embodiment of this application;

[0067] Figure 20 This is a schematic diagram of an interface display device provided in this application;

[0068] Figure 21 This is a schematic diagram of an electronic device with an interface display provided in this application. Detailed Implementation

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

[0070] Hereinafter, the terms "first," "second," and "third" 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. Thus, a feature defined as "first," "second," or "third" may explicitly or implicitly include one or more of that feature.

[0071] For ease of understanding, the examples provided are for reference only and are related to the concepts in the embodiments of this application.

[0072] 1. Trust loop.

[0073] Multiple electronic devices, after passing trusted authentication, connect to the same local area network or are directly connected (e.g., establishing a Wi-Fi Direct connection or a Bluetooth connection), forming a trust ring capable of communicating with each other. Electronic devices within this trust ring can be collaboratively managed and share resources. For example, electronic devices within the trust ring can perform functions such as cross-platform service calls to collect materials, synchronize materials, organize materials, and synchronize the organized results.

[0074] Electronic devices can establish trust relationships and form trust loops through trusted authentication using any of the following methods:

[0075] 1) Log in to the same account on two or more electronic devices. Electronic devices under the same account are trusted through account authentication to establish a trust relationship and form a trust loop.

[0076] 2) Two or more electronic devices establish a trust relationship and form a trust loop by performing trusted authentication through a proprietary protocol.

[0077] 3) Two or more electronic devices can establish a trust relationship and form a trust loop by logging into the cloud for trusted authentication.

[0078] The above methods are merely examples, and the embodiments of this application do not limit them.

[0079] It is understood that the electronic device in this application can be a mobile phone, tablet computer, or other electronic device, as well as a desktop computer, laptop computer, handheld computer, notebook computer, ultra-mobile personal computer (UMPC), netbook, cellular phone, personal digital assistant (PDA), augmented reality (AR) device, virtual reality (VR) device, artificial intelligence (AI) device, wearable device (such as smartwatch, smart bracelet, etc.), in-vehicle device, smart home device (such as smart TV, large screen, etc.) and / or smart city device. The embodiments of this application do not impose any special restrictions on the specific type of electronic device.

[0080] For example, such as Figure 1 As shown, devices such as mobile phones, tablets, desktop computers, laptops, and smart TVs can log in to the same account and connect to the same local area network, forming a trust ring. Within this trust ring, devices that are already working together can continue their current tasks on the mobile phone, such as continuing to watch videos on the mobile phone on the smart screen, or easily browse and edit files on the mobile phone on the computer.

[0081] 2. Trusted devices.

[0082] Electronic devices within a trust ring can be considered trusted devices of other devices. In other words, electronic devices that have a trust relationship through trusted authentication are called trusted devices. For example, a mobile phone and a tablet within the same trust ring can be considered trusted devices of each other; that is, the tablet is a trusted device of the mobile phone, and the mobile phone is also a trusted device of the tablet.

[0083] Trusted devices within a trust ring can share resources. Typically, this involves granting permissions to resources on one device to another. For example, granting permission for resource A1 from device A to another device B within the trust ring. This requires dragging the icon of resource A1 from device A onto the icon of device B in the trust ring's settings interface to grant device B permission to use resource A1. However, currently, the icons displayed in the trust ring's settings interface are typically drawn using operating system plugins and moved based on operating system control logic. This results in a monotonous dynamic effect when dragging icons for shareable resources, negatively impacting the user experience.

[0084] In view of this, the interface display method provided in this application embodiment displays a first card in response to a first operation on a first device icon. The first device icon is the icon of the first device in the trust ring device interface, and the first card is used to display at least one shared business control. Then, in response to a second operation on displaying any shared business control (target shared business control) on the first card, a first capsule icon corresponding to the target shared business control is displayed. The movement range of the first capsule icon is any range on the trust ring device interface. This allows the first capsule icon appearing in the interface to move arbitrarily on the trust ring setting interface during the trust ring setup process. Compared with the traditional method where the icon can only move according to a preset trajectory in the system, the interface display method provided in this application embodiment has a richer movement trajectory of the first capsule icon, improving the user experience.

[0085] The interface display method provided in this application can be applied to electronic devices. Optionally, the electronic device includes a terminal device, which can also be called a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device can be a mobile phone, smart TV, wearable device, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc. The embodiments of this application do not limit the specific technology or device form used in the terminal device.

[0086] For example, Figure 2A schematic diagram of the structure of electronic device 100 is shown. Electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, antenna 1, antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0087] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer 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.

[0088] 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.

[0089] 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 instruction fetching and execution.

[0090] 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.

[0091] 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.

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

[0093] 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.

[0094] 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.

[0095] Electronic device 100 can perform shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0096] Electronic device 100 can implement audio functions, such as music playback and recording, through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0097] It should be noted that any electronic device mentioned in the embodiments of this application may include more or fewer modules in electronic device 100.

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

[0099] Figure 3 This is a software structure block diagram of the electronic device 100 according to an embodiment of this application.

[0100] The layered architecture of the electronic device 100 divides the 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.

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

[0102] like Figure 3 As shown, the application package may include applications such as trust ring, camera, gallery, call, map, navigation, WLAN, Bluetooth, music, video, and SMS.

[0103] 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.

[0104] 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.

[0105] 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.

[0106] 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.

[0107] 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.

[0108] 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.

[0109] The kernel layer is the layer between hardware and software. The kernel layer includes at least display drivers, camera drivers, audio drivers, sensor drivers, Wi-Fi drivers, etc.

[0110] It should be noted that the electronic device mentioned in the embodiments of this application may include more or fewer modules of the above-mentioned electronic device.

[0111] The application scenarios and different interfaces involved in the embodiments of this application are described below with reference to the accompanying drawings.

[0112] The interface display method provided in this application embodiment can be applied to, for example, Figure 4 In the application scenarios shown. For example... Figure 4As shown, mobile phone 10 and PAD 20 log in to a unified account, such as account "1111". Trusted authentication is performed between mobile phone 10 and PAD 20 to establish a trust relationship, forming a trust ring. Since trusted devices in the trust ring can share resources, when sharing resources between trusted devices, it is necessary to grant access to resources on one device to another.

[0113] For example, mobile phone 10 and PAD 20 are two electronic devices within a trust ring. An external mouse and keyboard connected to PAD 20 can be accessed by mobile phone 10 by granting them usage permissions. Specifically, when permissions are granted to the external mouse and keyboard on PAD 20, a navigation icon for the external mouse and keyboard is displayed in the settings interface of either PAD 20 or mobile phone 10. For example, as... Figure 5 As shown in (a), on any display interface 10A (e.g., the main interface) of the mobile phone 10, the user swipes down. In response to the user's swipe-down operation, the mobile phone 10 switches from display interface 10A to display interface 10B, as shown in (a). Figure 5 As shown in (b) above. The display interface 10B can be the interface for the display control center. The display interface 10B includes a trust ring settings card 10B1. When the user clicks the trust ring settings card 10B1, as shown... Figure 5 As shown in (c) above. In response to the user's tapping of the Trust Ring settings card 10B1, the display interface of the phone 10 switches to display interface 10C, which is the Trust Ring settings interface, as shown below. Figure 5 As shown in (d) above. The trust ring settings interface displays bubble icons for each electronic device within the trust ring. For example, as shown below... Figure 5 As shown in (d), the trust ring includes a mobile phone bubble icon 10C1, a PAD bubble icon 10C2, and a PC bubble icon 10C3. Optionally, the trust ring's settings interface can also display prompts indicating that users can share services by touching the bubble icons. For example, the trust ring's settings interface can display the prompt "Click the device ball to select the required service to complete the transfer."

[0114] Users can tap the bubble icon of a trusted device to open the selection card for shareable services on that device. For example, ... Figure 6 As shown in (a), the user can click the PC bubble icon 10C3 in the display interface 10C. In response to the user clicking the PC bubble icon 10C3, a shared service selection card 10C4 can be displayed above the PC bubble icon 10C3, as shown... Figure 6 As shown in (b) above. Among them, services that can be shared with other electronic devices include screen sharing, keyboard and mouse sharing, remote control, file access, and cross-platform calls.

[0115] Screen sharing refers to displaying the interface of electronic device B on electronic device A, while simultaneously receiving and responding to user operations through electronic device A.

[0116] Mouse and keyboard sharing can refer to granting access to the mouse and keyboard of electronic device A to electronic device B, allowing the user to input commands to electronic device B using the mouse and keyboard of electronic device A.

[0117] Remote control can refer to a user establishing remote control of another electronic device directly through a device in a trust loop.

[0118] File access can refer to a user accessing files stored on electronic device B through electronic device A.

[0119] Cross-device invocation can refer to a user calling resources in electronic device B from electronic device A. For example, a user can call the camera, audio player, and other hardware and software devices of electronic device B in the trust ring through electronic device A, thereby achieving flexible control over multiple devices in the trust ring.

[0120] The following explains how trusted devices in a trust loop establish business sharing.

[0121] It should be noted that service sharing can refer to sharing services from one electronic device within a trust ring with other electronic devices in the same ring, enabling those other devices to perform those services. Services can refer to the hardware and software resources within an electronic device. From the perspective of the electronic device, this is equivalent to transferring the hardware and software resources that serve other electronic devices to the current electronic device; therefore, service sharing can also be called service transfer.

[0122] For example, let's take keyboard and mouse sharing as an example for illustration.

[0123] like Figure 7 As shown, users can share keyboard and mouse by selecting the keyboard and mouse sharing icon 10C41 in card 10C4 through the touch sharing service. It is understood that the user touching the keyboard and mouse sharing icon 10C41 can mean that the user clicks the keyboard and mouse sharing icon 10C41 or that the user long-presses the keyboard and mouse sharing icon 10C41. This embodiment of the application does not limit this.

[0124] In one possible scenario, when a user clicks the keyboard and mouse sharing icon 10C41, in response to this action, the sharing service selection card 10C41 is collapsed, and the first keyboard and mouse sharing capsule icon 10C42 is displayed, as shown below. Figure 8As shown in (a) above. Optionally, a pop-up window can also be displayed on the trust ring settings interface, prompting the user to share the keyboard and mouse by dragging and dropping the first keyboard and mouse sharing capsule icon 10C42. For example, as shown in... Figure 8 As shown in (a), the pop-up window displays the message "Drag and drop the service onto the target device to complete the transfer." At this point, the user can click the First Keyboard and Mouse Sharing Capsule icon 10C42, as shown... Figure 8 As shown in (b) above. In response to the user clicking the first keyboard and mouse sharing capsule icon 10C42, the close button 10C42 in the first keyboard and mouse sharing capsule icon 10C42 closes and switches to the second keyboard and mouse sharing capsule icon 10C42A, which moves with the user's finger, as shown in (b). Figure 8 As shown in (c) of the diagram. The icon of a device that cannot perform keyboard and mouse sharing is set to gray, indicating that the device cannot perform keyboard and mouse sharing. For example, if the current keyboard and mouse sharing is sharing the keyboard and mouse connected to the PC, since the keyboard and mouse are already connected to the PC, this device cannot perform keyboard and mouse sharing with the PC. Therefore, at the bottom of the Trust Ring settings interface, the PC icon is set to gray, indicating that the PC cannot perform keyboard and mouse sharing. It is understandable that during the dragging of the second keyboard and mouse sharing capsule icon 10C42A, the Trust Ring settings interface can also display the movement trajectory of the second keyboard and mouse sharing capsule icon 10C42A, such as... Figure 8 As shown in (d) in the figure.

[0125] In one possible scenario, when a user long-presses the mouse sharing icon 10C41, in response to the user's long-press action on the mouse sharing icon 10C41, the sharing service selection card 10C41 is collapsed, and the second mouse sharing capsule icon 10C42A is displayed, as shown below. Figure 9 As shown in (a) above. At this time, the user's finger is still touching the second keyboard and mouse sharing capsule icon 10C42A. The second keyboard and mouse sharing capsule icon 10C42A can already move according to the user's finger movement, without the user needing to click on the second keyboard and mouse sharing capsule icon 10C42A to wake it up, as shown below. Figure 9 As shown in (b) above. It is understandable that during the dragging of the second keyboard and mouse shared capsule icon 10C42A, the display interface can also show the movement trajectory of the second keyboard and mouse shared capsule icon 10C42A.

[0126] When the second keyboard and mouse sharing capsule icon 10C42A moves from the PC bubble icon 10C3 to the mobile bubble icon 10C1, as follows: Figure 10As shown in (a) above. It can be understood that the movement of the second keyboard and mouse shared capsule icon 10C42A from the PC bubble icon 10C3 to the mobile bubble icon 10C1 can mean that the second keyboard and mouse shared capsule icon 10C42A moves from the PC bubble icon 10C3 to within a preset range around the mobile bubble icon 10C1, for example, the distance between the second keyboard and mouse shared capsule icon 10C42A and the mobile bubble icon 10C1 is less than a preset threshold. Alternatively, there may be partial or complete overlap between the second keyboard and mouse shared capsule icon 10C42A and the mobile bubble icon 10C1. In this case, the second keyboard and mouse shared capsule icon 10C42A is converted into the first connection waiting bubble 10C43, as shown below. Figure 10 As shown in (b) above. The second keyboard and mouse sharing capsule icon 10C42A transforms into the first connection waiting bubble 10C43, indicating that the PC begins to grant the phone access to the keyboard and mouse, and the phone begins to establish a connection with the keyboard and mouse connected to the PC. Understandably, during the dragging of the second keyboard and mouse sharing capsule icon 10C42A, the prompt message displayed on the trust ring settings interface may change from "Click the device ball, select the required service to complete the process" to "Flowing through the 'Keyboard and Mouse Sharing' service." After the phone successfully establishes a connection with the keyboard and mouse connected to the PC, the connection waiting bubble icon 10C43 transforms into the first connection success bubble icon 10C44, as shown below. Figure 10 As shown in (c) above. In this scenario, the user can input information into the phone using a mouse and keyboard to control the phone. Simultaneously, the displayed message on the Trust Ring settings interface can change from "Streaming 'Keyboard and Mouse Sharing' service" to "Using 'Keyboard and Mouse Sharing' service". Optionally, a pop-up window 10C5 can also be displayed on the Trust Ring settings interface, showing a message indicating successful establishment of the sharing service. For example, as... Figure 10 As shown in (c), the pop-up window 10C5 displays "Keyboard and mouse sharing successfully completed," indicating that the mobile phone can now use the mouse and keyboard connected to the PC. Optionally, when the second keyboard and mouse sharing capsule icon 10C42A moves from the PC bubble icon 10C3 to a preset range around the mobile phone bubble icon 10C1, the electronic device can also vibrate to notify the user that the second keyboard and mouse sharing capsule icon 10C42A has been dragged into the preset range of the mobile phone bubble icon 10C1. The user can choose to continue dragging the second keyboard and mouse sharing capsule icon 10C42A or release it as needed, so that the sharing service corresponding to the second keyboard and mouse sharing capsule icon 10C42A can be granted access to the mobile phone.

[0127] It should be noted that the method provided in this application embodiment does not use a system-provided plugin to generate the aforementioned icon. For example, a system-provided plugin could refer to Android. TMThe second keyboard and mouse sharing capsule icon 10C42A is a plugin within the system. Therefore, the movement of the second keyboard and mouse sharing capsule icon 10C42A does not need to follow the movement rules of the system plugin. In other words, the second keyboard and mouse sharing capsule icon 10C42A can be moved freely within the trust ring settings interface.

[0128] For example, the second keyboard and mouse shared capsule icon 10C42A may not move along the preset path 10C6 between the PC bubble icon 10C3 and the mobile phone bubble icon 10C1, wherein the preset path 10C5 can be as follows: Figure 11 As shown in (a) above. The second keyboard and mouse sharing capsule icon 10C42A can be moved to the edge of the trust ring settings interface, as shown below. Figure 11 As shown in (b) above. Alternatively, move the second keyboard and mouse sharing capsule icon 10C42A above the prompt displayed on the Trust Ring settings interface, as shown below. Figure 11 As shown in (c) in the figure.

[0129] Once the keyboard and mouse on the phone are successfully connected to the PC, a successful first connection bubble icon 10C44 will appear near the phone's bubble icon 10C1, for example... Figure 10 As shown in (c) above. At this point, the user clicks the first successful connection bubble icon 10C44, as shown below. Figure 12 As shown in (a) above. In response to the user clicking the first successful connection bubble icon 10C44, the first successful connection bubble icon 10C44 switches to the third keyboard and mouse sharing capsule icon 10C45, as shown below. Figure 12 As shown in (b) above. The third keyboard and mouse sharing capsule icon 10C45, compared to the first keyboard and mouse sharing capsule icon 10C42, adds a close button 10C451. In one possible scenario, the third keyboard and mouse sharing capsule icon 10C45 may also display a tooltip indicating the source of the keyboard and mouse used by the phone. For example, as... Figure 12 As shown in (b), the third keyboard and mouse sharing capsule icon 10C45 also displays the message "MagicBook," indicating that the keyboard and mouse used by the phone are connected to the PC (MagicBook). When the user clicks the close button 10C451, as... Figure 12 As shown in (c) above. In response to the user clicking the close button 10C451, the phone disconnects from the keyboard and mouse connected to the PC, and the third keyboard and mouse sharing capsule icon 10C45 is removed from the trust ring settings interface, as shown below. Figure 12 As shown in (d) in the diagram. Understandably, the prompt message on the Trust Ring settings interface can also be switched from "Using the 'Keyboard and Mouse Sharing' service" to "Click the device ball and select the required service to complete the transfer".

[0130] In one possible scenario, the user can disconnect the phone from the PC by dragging the first connection success bubble icon 10C44 back to the PC bubble icon 10C3. For example, as shown... Figure 13 As shown in (a), the user drags the first successful connection bubble icon 10C44 from the mobile phone bubble icon 10C1. The user drags the first successful connection bubble icon 10C44 into the preset area of ​​the PC bubble icon 10C3, as shown. Figure 13 As shown in (b) above. It is understandable that during the dragging of the first successful connection bubble icon 10C44, the first successful connection bubble icon 10C44 is a gray icon, indicating that it is currently unavailable. If the first successful connection bubble icon 10C44 is dragged into the preset area of ​​the PC bubble icon 10C3, the first successful connection bubble icon 10C44 disappears, and the prompt message displayed in the trust ring settings interface changes from "Using the 'Keyboard and Mouse Sharing' service" to "Click the device ball, select the required service to complete the transfer," as shown below. Figure 13 As shown in (c) above. Optionally, when the first successful connection bubble icon 10C44 is dragged into the preset range of the PC bubble icon 10C3, the electronic device can also vibrate to notify the user that the first successful connection bubble icon 10C44 has been dragged into the preset range of the PC bubble icon 10C3. The user can choose to continue dragging the first successful connection bubble icon 10C44 or release it as needed, so that the shared service corresponding to the first successful connection bubble icon 10C44 can be opened to the PC for use.

[0131] In one possible scenario, after the phone successfully establishes a connection with the keyboard and mouse connected to the PC, the user can also drag and drop the first successful connection bubble icon 10C44 on the phone's bubble icon 10C1 to allow other trusted devices within the trust ring to also connect to and use the PC-connected keyboard and mouse. For example, as shown... Figure 14 As shown in (a), the user clicks the first successful connection bubble icon 10C44 on the phone bubble icon 10C1 and begins dragging the first successful connection bubble icon 10C44 towards the PAD bubble icon 10C2, as shown in (a). Figure 14As shown in (b) above. It is understandable that during the dragging of the first successful connection bubble icon 10C44, the first successful connection bubble icon 10C44 is grayed out, indicating that it is currently unavailable. When the first successful connection bubble icon 10C44 is within the preset range of the PAD bubble icon 10C2, for example, when the distance between the first successful connection bubble icon 10C44 and the PAD bubble icon 10C2 is less than a preset threshold, the keyboard and mouse connected to the PC grant access to the PAD, and the PAD begins to establish a connection with the keyboard and mouse connected to the PC. At this time, on the trust ring settings interface, the second connection waiting bubble icon 10C46 is displayed near the PAD bubble icon 10C2, as shown below. Figure 14 As shown in (c) above. The first connection success bubble icon 10C44 changes to the second connection waiting bubble 10C46, indicating that the PC begins to grant the PAD access to the keyboard and mouse. The PAD can then begin establishing a connection with the keyboard and mouse connected to the PC. Optionally, during the connection establishment process between the PAD and the PC, the prompt message displayed on the trust ring settings interface can be changed from "Transferring the 'Keyboard and Mouse Sharing' service" to "Click the device ball, select the desired service to complete the transfer," such as... Figure 14 As shown in (c) above. After the PAD successfully establishes a connection with the keyboard and mouse connected to the PC, the second connection waiting bubble 10C46 changes to the second connection success bubble icon 10C47, as shown below. Figure 14 As shown in (d) above. In this case, the user can input information into the PAD using the mouse and keyboard to control the PAD. Optionally, the prompt message displayed on the trust ring settings interface can be changed from "Click the device ball to select the required service to complete the flow" to "Using the 'Keyboard and Mouse Sharing' service," as shown below. Figure 14 As shown in (d) in the figure.

[0132] Understandably, if the second keyboard and mouse sharing capsule icon 10C42A moves from the PC bubble icon 10C3 to the mobile bubble icon 10C1, and the user raises their hand before the second keyboard and mouse sharing capsule icon 10C42A has moved to the mobile bubble icon 10C1, then... Figure 15 As shown in (a) above. In response to the user raising their hand, the second keyboard and mouse shared capsule icon 10C42A switches to the first keyboard and mouse shared capsule icon 10C42, and is displayed at the PC bubble icon 10C3, as shown below. Figure 15 As shown in (b) of the diagram.

[0133] The following explains the specific process of displaying the capsule and bubble icons on trusted devices.

[0134] Trusted devices in the trust loop can include an interface layout module, which is used to create and manage capsule icons and bubble icons that appear during the shared business flow. For example, the interface layout module can be used to create and manage the aforementioned first keyboard and mouse shared capsule icon 10C42, second keyboard and mouse shared capsule icon 10C42A, first connection waiting bubble 10C43, first connection successful bubble icon 10C44, third keyboard and mouse shared capsule icon 10C45, second connection waiting bubble icon 10C46, and second connection successful bubble icon 10C47. Among them, such as... Figure 16 As shown, the interface layout module includes a capsule layout submodule and a bubble layout submodule. The bubble layout submodule can also be a service sphere layout submodule. The capsule layout submodule can include a capsule back panel common layout unit, a capsule service name common layout unit, a capsule service icon common layout unit, a capsule back panel animation customization unit, a capsule device name customization layout unit, and a capsule hidden button customization layout unit. The service sphere layout submodule can include a service sphere back panel common layout unit, a service sphere device name common layout unit, a service sphere icon common layout unit, a service sphere animation customization unit, a service sphere device name customization layout unit, and a service sphere hidden button customization layout unit.

[0135] The capsule layout submodule can be used to create capsule icons such as the first shared keyboard and mouse capsule icon 10C42, the second shared keyboard and mouse capsule icon 10C42A, and the third shared keyboard and mouse capsule icon 10C45, and manage the initial shape, movement effects, and connection status of the capsule icons. For example, Figure 16 As shown, the Capsule Layout submodule includes several modules: the Capsule Backboard Common Layout Unit for setting the backboard layout of the capsule icon; the Capsule Service Name Common Layout Unit for setting the service name of the capsule icon; the Capsule Service Icon Common Layout Unit for setting the common layout of the capsule icon; the Capsule Backboard Animation Customization Unit for generating dynamic effects for the capsule icon backboard based on user settings; the Capsule Device Name Customization Layout Unit for generating the device name corresponding to the capsule icon based on the user's device; and the Capsule Hidden Button Customization Layout Unit for generating other buttons on the capsule icon based on user settings. Thus, a complete capsule icon can be generated using the Capsule Layout submodule.

[0136] The Service Ball Layout submodule can be used to create the aforementioned first connection waiting bubble 10C43, first connection successful bubble icon 10C44, second connection waiting bubble icon 10C46, and second connection successful bubble icon 10C47. The Service Ball Layout submodule can also manage the initial shape of the bubble icons, their movement animations, and their connection status. For example, as... Figure 16As shown, the Service Ball Layout submodule includes several submodules: the Service Ball Backplane Common Layout Unit for setting the background layout of the bubble icon; the Service Ball Device Name Common Layout Unit for setting the name of the service ball icon; the Service Ball Icon Common Layout Unit for setting the common layout of the service ball icons; the Service Ball Animation Customization Unit for generating dynamic effects for the bubble icon background based on user settings; the Service Ball Device Name Customization Layout Unit for generating the device name corresponding to the service ball icon based on the user's device; and the Service Ball Hidden Button Customization Layout Unit for generating other buttons on the bubble icon based on user settings. Thus, a complete bubble icon can be generated using the Service Ball Layout submodule.

[0137] Understandably, to reduce waiting time during the drag-and-drop of capsule or bubble icons and improve user experience, the capsule layout submodule and service sphere layout submodule have already begun loading when the trust ring settings interface is displayed. Thus, while the user is dragging the capsule or bubble icon, there is no need to wait for the capsule layout submodule and service sphere layout submodule to load, allowing the electronic device to quickly generate the capsule or bubble icon and respond quickly to user actions, enabling the movement and animation display of the capsule or bubble icon.

[0138] The interface layout module can connect to the service interaction control module. Based on user actions, the service interaction control module can determine whether to generate corresponding capsule icons and bubble icons, move them, show or stop their dynamic effects, or toggle between them. The service interaction control module then sends the determined action generation instructions to the interface layout module, enabling the interface layout module to control the capsule and bubble icons based on these instructions.

[0139] The following explains the specific process of determining the form transition between capsule icons and bubble icons.

[0140] For example, a capsule icon can include three states: initial state, moving state, and connected state. The initial state can be as follows: Figure 17 As shown in (a) above, the movement pattern can be as follows: Figure 17 As shown in (b) above, the connected configuration can be as follows: Figure 17 As shown in (c) above. The initial form may include a business icon 161, a prompt message 162, and a close button 163. The business icon 161 can be an icon for shared services, such as... Figure 17 The icon for keyboard and mouse sharing is shown in (a); the tooltip 162 is used to indicate the sharing activity, for example, such as... Figure 17The information shown in (a) as "Keyboard and Mouse Sharing" indicates that the current sharing service is a keyboard and mouse sharing service; the close button 163 is used to close the capsule icon in the initial form. The mobile form may include a service icon 161 and a prompt message 162; that is, compared to the initial form, the mobile form does not have a close button 163. The connected form may include a service icon 161, a prompt message 162, a close button 163, and a device name 164; compared to the initial form, the connected form adds a device name 164. The device name 164 can be used to indicate which device is the current sharing source of the sharing service, for example, such as... Figure 17 As shown in (c), device name 164 is “MagicBook”, indicating that the source of the currently shared keyboard and mouse is a PC named “MagicBook”.

[0141] Among them, the first keyboard and mouse shared capsule icon 10C42 can be the capsule icon in its initial form, the second keyboard and mouse shared capsule icon 10C42A can be the capsule icon in its moving form, and the third keyboard and mouse shared capsule icon 10C45 can be the capsule icon in its connected form.

[0142] For example, the bubble icon can include two forms: a connection waiting form and a connection successful form. The connection waiting form can be as follows: Figure 18 As shown in (a) above, a successful connection can be represented as follows: Figure 18 As shown in (b) above. A shared service icon can be displayed in the successful connection status.

[0143] Among them, the first connection waiting bubble 10C43 and the second connection waiting bubble icon 10C46 can be bubble icons in the form of connection waiting, and the first connection successful bubble icon 10C44 and the second connection successful bubble icon 10C47 can be bubble icons in the form of connection successful.

[0144] For instructions on how to switch between the various forms of the capsule icon and the various forms of the bubble icon, please refer to [link / reference]. Figure 19 The flowchart is shown below. Figure 19 As shown, it includes:

[0145] S101. In response to the user clicking the first icon, display the first card.

[0146] Here, the first icon can refer to the icon of the first trusted device in the trust ring device interface. The first icon can also be called the first device icon.

[0147] For example, such as Figure 6 As shown in (a), the first icon can be the PC bubble icon 10C3 in the Trust Ring Device Interface 10C.

[0148] The first card can refer to a card that displays the shared services of the first device. For example, the first card can be like this: Figure 7 The card shown is 10C41. It is understood that the first card includes multiple shared business controls.

[0149] S102. In response to the user's operation on the target shared business control in the first card, display the capsule icon in its initial form.

[0150] Target shared business controls can refer to Figure 7 The "keyboard and mouse sharing" control shown can also be any control in the first card; this application embodiment does not limit this. It is understood that the operation on the target sharing business control can be a click operation or a long-press operation; this application embodiment does not limit this. Clicking the first icon displays the first card. The initial capsule icon can be as follows: Figure 8 The first keyboard and mouse shared capsule icon 10C42 is shown in (a) in the image.

[0151] S103. A drag operation on the initial capsule icon is detected, and the capsule icon in the moved form is displayed.

[0152] For example, a mobile capsule icon can be like... Figure 8 The second keyboard and mouse shared capsule icon 10C42A is shown in (b) of the image.

[0153] The interface display method provided in this application embodiment displays a first card in response to clicking a first icon. The first icon can refer to a first device icon, which is the icon of the first device in the trust ring device interface. The first card is used to display at least one shared business control. Then, in response to a second operation of displaying any shared business control (target shared business control) on the first card, a first capsule icon corresponding to the target shared business control is displayed. The movement range of the first capsule icon is any range on the trust ring device interface. This allows the first capsule icon appearing in the interface to move arbitrarily on the trust ring setting interface during the trust ring setup process. Compared with the traditional method where the icon can only move according to a preset trajectory in the system, the interface display method provided in this application embodiment has a richer movement trajectory of the first capsule icon, improving the user experience.

[0154] S104. When the capsule icon in the moving form is detected to move to the second icon, the capsule icon in the moving form is switched to the bubble icon in the connection waiting form.

[0155] The second icon can refer to the icon of another trusted device (e.g., a second device) in the trust ring device interface. For example, the second icon could be the phone's bubble icon in the trust ring settings interface, such as... Figure 6The bubble icon 10C1 of the mobile phone is shown in (a). The bubble icon in the connection waiting state can refer to the first connection waiting bubble 10C43. When the second keyboard and mouse sharing capsule icon 10C42A is detected to move to the bubble icon 10C1 of the mobile phone, the second keyboard and mouse sharing capsule icon 10C42A is switched to the first connection waiting bubble 10C43.

[0156] Among them, the capsule icon in a moving state can be the first capsule icon, and the bubble icon in a waiting state can be the second bubble icon. The second icon can be called the second device icon.

[0157] The interface display method provided in this application embodiment detects that when the first capsule icon moves to the second device icon, it displays a second bubble icon in a connection waiting state, and then displays a first bubble icon in a connection successful state. It is understood that it usually takes a long time for the second device to establish a target shared service. If the second bubble icon is not displayed, the user cannot know the current status of the second device while waiting to establish the target shared service. By displaying the second bubble icon in the connection waiting state, the user is prompted that the target shared service is being established and only needs to wait. No additional operation is required, thereby avoiding system lag caused by the user performing other operations.

[0158] S105. When the second device is detected to have successfully established service sharing, the bubble icon in the connection waiting state will be switched to the bubble icon in the connection successful state.

[0159] In this context, "successfully establishing service sharing on the second device" can mean that the first device has successfully granted service permissions to the second device. For example, if the shared service refers to keyboard and mouse sharing, the second device is a mobile phone, and the first device is a PC, then "successfully establishing service sharing on the second device" could mean that the mouse and keyboard connected to the PC have successfully granted permissions to the mobile phone, allowing the mouse and keyboard connected to the PC to access the mobile phone. A bubble icon indicating a successful connection could represent, for example,... Figure 13 The first successful connection bubble icon 10C44 is shown in (a) in the image.

[0160] Among them, the bubble icon that shows a successful connection can become the first bubble icon.

[0161] The interface display method provided in this application embodiment detects that the first capsule icon moves to the second device icon, and then displays a first bubble icon. The second device icon refers to the second device in the trust ring device interface, and the first bubble icon is used to indicate that the second device has successfully established a target shared service. The target shared service refers to the shared service corresponding to the target shared service control. This is equivalent to switching the first capsule icon displayed during the movement process to the first bubble icon during the establishment of the target shared service by the second device, which enriches the display mode of the icon during the establishment of the target shared service by the second device and improves the user experience.

[0162] S106. When the bubble icon indicating a successful connection is detected and dragged back to the first device icon, the bubble icon indicating a successful connection is closed.

[0163] For example, such as Figure 13 (b) and Figure 13 As shown in (c), when the first successful connection bubble icon 10C44 is dragged back to the PC's bubble icon 10C3, the first successful connection bubble icon 10C44 is closed. Simultaneously with closing the successful connection bubble icon, the shared target service established by the second device is closed.

[0164] Among them, the bubble icon that shows a successful connection can become the first bubble icon.

[0165] The interface display method provided in this application embodiment can close the target shared service established by the second device when the first bubble icon is moved back to the first device icon, thereby improving the convenience of closing the target shared service established by the second device.

[0166] S107. When a click operation is detected on the bubble icon in the "connection successful" state, the bubble icon in the "connection successful" state is switched to the capsule icon in the "completed" state.

[0167] For example, such as Figure 12 (a) and Figure 12 As shown in (b), when the first successful connection bubble icon 10C44 is clicked, the first successful connection bubble icon 10C44 is switched to the third keyboard and mouse sharing capsule icon 10C45.

[0168] Among them, the bubble icon that has been successfully connected can be called the first bubble icon, and the capsule icon that has been completed can be called the third capsule icon.

[0169] S108. Detecting a click operation on the close button on the completed capsule icon, close the completed capsule icon, and close the sharing service.

[0170] Among them, the close button on the capsule icon that has reached its completed form can be called the first close button.

[0171] For example, such as Figure 12 (c) and Figure 12 As shown in (d), clicking the close button on the third keyboard and mouse sharing capsule icon 10C45 closes the third keyboard and mouse sharing capsule icon 10C45.

[0172] The interface display method provided in this application embodiment displays a third capsule icon in response to clicking the first bubble icon, and then closes the third capsule icon and closes the target sharing service established by the second device in response to the operation of the first close button. This is equivalent to being able to close the target sharing service established by the second device simply by operating the first bubble icon displayed at the second device icon, which improves the intuitiveness of closing the target sharing service established by the second device.

[0173] S109. If it is detected that the capsule icon in the moving form has not moved to the second icon, and the user raises their hand, the capsule icon in the moving form is switched back to the capsule icon in the initial form.

[0174] Specifically, when the user raises their hand, the first capsule icon (the mobile capsule icon) does not move to the second device icon. Therefore, it's equivalent to the user canceling the operation to establish service sharing. Based on this, the mobile capsule icon (the first capsule icon) can be switched back to the initial capsule icon (the second capsule icon). For details, please refer to [link to documentation]. Figure 15 (a) and Figure 15 As shown in (b) of the diagram.

[0175] S110. Detecting that the user clicked the close button on the initial capsule icon, close the initial capsule icon.

[0176] The close button on the initial capsule icon can be referred to as the second close button.

[0177] The interface display method provided in this application embodiment allows the second capsule icon (i.e., the second capsule icon) to be closed via the second close button on the second capsule icon when the initial state capsule icon is displayed, which means canceling the operation of establishing business sharing. This improves the convenience of canceling the establishment of business sharing.

[0178] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0179] It is understood that, in order to achieve the above functions, the electronic device includes hardware and / or software modules that perform the respective functions. Based on the algorithmic steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is implemented 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 implementation should not be considered beyond the scope of this application.

[0180] This application embodiment can divide an electronic device into functional modules based on the above method examples. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one module. It should be noted that the module division in this application embodiment is illustrative and represents only one logical functional division; other division methods may be used in actual implementation. It should also be noted that the module names in this application embodiment are illustrative, and the names of the modules are not limited in actual implementation.

[0181] Figure 20 This is a schematic diagram of the interface display device provided in an embodiment of this application.

[0182] It should be understood that the interface display device 600 can perform... Figure 19 The interface display method shown; the interface display device 600 includes: an acquisition unit 610 and a processing unit 620.

[0183] Processing unit 620 is configured to display a first card in response to a first operation on a first device icon, wherein the first device icon is the icon of a first device in the trust ring device interface, and the first card is configured to display at least one shared business control.

[0184] The processing unit 620 is configured to respond to a second operation on a target shared service control by displaying a first capsule icon corresponding to the target shared service control. The target shared service control is any shared service control displayed on the first card, and the movement range of the first capsule icon is any range on the trust ring device interface.

[0185] In one embodiment, the processing unit 620 is further configured to perform a long-press operation on the target shared business control; in response to the long-press operation on the target shared business control, displaying a first capsule icon corresponding to the target shared business control, wherein the first capsule icon is a capsule icon in a moving state.

[0186] In one embodiment, the processing unit 620 is specifically configured to perform a click operation on the target shared service, display a second capsule icon, the second capsule icon being a capsule icon in an initial state; perform a drag operation on the second capsule icon; and in response to the drag operation on the second capsule icon, display a first capsule icon corresponding to the target shared service control, the first capsule icon being a capsule icon in a moving state.

[0187] In one embodiment, the processing unit 620 is further configured to display a first bubble icon when it detects that the first capsule icon has moved to the second device icon. The second device icon refers to the second device in the trust ring device interface. The first bubble icon is used to indicate that the second device has successfully established a target shared service. The target shared service refers to the shared service corresponding to the target shared service control.

[0188] In one embodiment, the processing unit 620 is further configured to display a second bubble icon, which indicates that the second device is waiting to establish the target shared service.

[0189] In one embodiment, the processing unit 620 is further configured to, upon detecting that the first bubble icon moves back to the first device icon, close the first bubble icon and close the target sharing service established by the second device.

[0190] In one embodiment, the processing unit 620 is further configured to display a third capsule icon in response to clicking the first bubble icon, wherein the third capsule icon displays a first device identifier corresponding to the target shared service.

[0191] In one embodiment, the third capsule icon further includes a first close button, and the processing unit 620 is further configured to close the third capsule icon and close the target sharing service established by the second device in response to the operation of the first close button.

[0192] In one embodiment, the processing unit 620 is further configured to detect that the first capsule icon has not moved to the second device icon, and to display the second capsule icon when the user raises their hand, wherein the second capsule icon is the capsule icon in the initial state.

[0193] In one embodiment, the second capsule icon includes a second close button, and the processing unit 620 is further configured to close the second capsule icon in response to a click operation on the second close button.

[0194] In one embodiment, the processing unit 620 is further configured to, in response to a drag operation on the first bubble icon, determine whether the first bubble icon has moved to a third device icon, the third device icon referring to the icon of a third device in the trust ring device interface; if the first bubble icon has moved to the third device icon, then the third bubble icon is displayed, the third bubble icon being used to indicate that the third device has successfully established the target shared service.

[0195] In one embodiment, the processing unit 620 is further configured to display a fourth bubble icon, which indicates that the third device is waiting to establish the target shared service.

[0196] The interface display device provided in this embodiment is used to execute the interface display method of the above embodiment. The technical principle and technical effect are similar, and will not be described again here.

[0197] It should be noted that the aforementioned interface display device 600 is embodied in the form of a functional unit. The term "unit" here can be implemented in software and / or hardware, and there is no specific limitation on this.

[0198] For example, a "unit" can be a software program, a hardware circuit, or a combination of both that implements the above functions. The hardware circuit may include an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor) and memory for executing one or more software or firmware programs, integrated logic circuitry, and / or other suitable components that support the described functions.

[0199] Therefore, the units of the various examples described in the embodiments of this application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0200] Figure 21A schematic diagram of the structure of an electronic device provided in this application is shown. Figure 17 The dashed lines indicate that the unit or module is optional. The electronic device 700 can be used to implement the interface display method described in the above method embodiments.

[0201] The electronic device 700 includes one or more processors 701, which can support the interface display method in the method embodiments of the electronic device 700. The processor 701 can be a general-purpose processor or a special-purpose processor. For example, the processor 701 can be a central processing unit (CPU), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, such as discrete gates, transistor logic devices, or discrete hardware components.

[0202] The processor 701 can be used to control the electronic device 700, execute software programs, and process data from the software programs. The electronic device 700 may also include a communication unit 705 for inputting (receiving) and outputting (transmitting) signals.

[0203] For example, electronic device 700 may be a chip, communication unit 705 may be the input and / or output circuit of the chip, or communication unit 705 may be the communication interface of the chip, and the chip may be a component of terminal device or other electronic device.

[0204] For example, electronic device 700 can be a terminal device, communication unit 705 can be the transceiver of the terminal device, or communication unit 705 can be the transceiver circuit of the terminal device.

[0205] The electronic device 700 may include one or more memories 702, which store a program 704. The program 704 can be executed by the processor 701 to generate instructions 703, causing the processor 701 to execute the impedance matching method described in the above method embodiments according to the instructions 703.

[0206] Optionally, the memory 702 may also store data. Optionally, the processor 701 may also read the data stored in the memory 702, which may be stored at the same memory address as the program 704, or the data may be stored at a different memory address than the program 704.

[0207] The processor 701 and memory 702 can be configured separately or integrated together; for example, integrated on the system on chip (SOC) of the terminal device.

[0208] For example, the memory 702 can be used to store the relevant program 704 of the interface display method provided in the embodiments of this application, and the processor 701 can be used to call the relevant program 704 of the interface display method stored in the memory 702 when performing interface display, and execute the interface display method of the embodiments of this application; including: in response to a first operation on a first device icon, displaying a first card, the first device icon being the icon of a first device in the trust ring device interface, the first card being used to display at least one shared service control; in response to a second operation on a target shared service control, displaying a first capsule icon corresponding to the target shared service control, the target shared service control being any shared service control displayed on the first card, the movement range of the first capsule icon being any range on the trust ring device interface.

[0209] This application also provides a computer program product that, when executed by processor 701, implements the interface display method described in any of the method embodiments of this application.

[0210] The computer program product can be stored in memory 702, for example, program 704. Program 704 is finally converted into an executable object file that can be executed by processor 701 after processing such as preprocessing, compilation, assembly and linking.

[0211] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a computer, implements the interface display method described in any of the method embodiments of this application. The computer program may be a high-level language program or an executable object program.

[0212] The computer-readable storage medium is, for example, memory 702. Memory 702 can be volatile memory or non-volatile memory, or memory 702 can include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0213] In this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

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

[0215] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0216] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0217] 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 example, the division of units is merely a logical functional division, and other division methods may exist in actual implementation; for example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

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

[0219] In addition, 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.

[0220] 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 that can be easily conceived by those skilled in the art within the scope of the technology 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 includes: The trust ring interface is displayed, which includes at least a first device icon, a second device icon, and a third device icon. The first device icon is the icon of the first device in the trust ring interface, the second device icon is the icon of the second device in the trust ring interface, and the third device icon is the icon of the third device in the trust ring interface. The first device, the second device, and the third device are trusted devices to each other, and the first device, the second device, and the third device are different electronic devices. The second electronic device displays the trust ring interface. In response to a first operation on the first device icon, a first card is displayed, the first card being used to display at least one shared business control; In response to a second operation on a target shared business control, a first capsule icon corresponding to the target shared business control is displayed. The target shared business control is any shared business control displayed on the first card. The movement range of the first capsule icon is any range on the trust ring device interface. When the first capsule icon is detected to move to the second device icon, a first bubble icon is displayed. The first bubble icon is used to indicate that the second device has successfully established the target shared service. The target shared service refers to the shared service corresponding to the target shared service control. In response to a drag operation on the first bubble icon, it is determined whether the first bubble icon has moved to the third device icon, wherein, during the process of the first bubble icon moving to the third device icon, the second device maintains the establishment of the target sharing service; If the first bubble icon moves to the third device icon, the third bubble icon is displayed, which indicates that the third device has successfully established the target sharing service.

2. The method according to claim 1, characterized in that, The second operation on the target shared business control includes: Perform a long press operation on the target shared business control; The step of displaying the first capsule icon corresponding to the target shared business control in response to the second operation on the target shared business control includes: In response to a long press operation on the target shared business control, a first capsule icon corresponding to the target shared business control is displayed, wherein the first capsule icon is a capsule icon in a moving state.

3. The method according to claim 1, characterized in that, The second operation on the target shared business control includes: Clicking on the target shared service displays a second capsule icon, which is the initial capsule icon. Drag and drop the second capsule icon; The step of displaying the first capsule icon corresponding to the target shared business control in response to the second operation on the target shared business control includes: In response to a drag operation on the second capsule icon, the first capsule icon corresponding to the target shared business control is displayed, wherein the first capsule icon is a capsule icon in a moving state.

4. The method according to any one of claims 1 to 3, characterized in that, Before displaying the first bubble icon, the method further includes: A second bubble icon is displayed, which indicates that the second device is waiting to establish the target shared service.

5. The method according to claim 4, characterized in that, After displaying the first bubble icon, the method further includes: When the first bubble icon is detected to have moved back to the first device icon, the first bubble icon is turned off, and the target sharing service established by the second device is turned off.

6. The method according to any one of claims 1 to 3, characterized in that, The method further includes: In response to clicking the first bubble icon, a third capsule icon is displayed, on which the first device identifier corresponding to the target shared service is displayed.

7. The method according to claim 6, characterized in that, The third capsule icon also includes a first close button, and the method further includes: In response to the operation of the first close button, the third capsule icon is closed, and the target sharing service established by the second device is closed.

8. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The system detects that the first capsule icon has not moved to the second device icon, and displays the second capsule icon when the user raises their hand. The second capsule icon is the capsule icon in its initial state.

9. The method according to claim 8, characterized in that, The second capsule icon includes a second close button, and the method further includes: In response to a click on the second close button, the second capsule icon is closed.

10. The method according to any one of claims 1 to 9, characterized in that, Before displaying the third bubble icon, the method further includes: A fourth bubble icon is displayed, which indicates that the third device is waiting to establish the target shared service.

11. An electronic device, characterized in that, The electronic device includes a module for performing the method as described in any one of claims 1 to 10.

12. An electronic device, characterized in that, The electronic device includes: one or more processors, and memory; The memory is coupled to the one or more processors, the memory being used to store computer program code, the computer program code including computer instructions, the one or more processors invoking the computer instructions to cause the electronic device to perform the method as described in any one of claims 1 to 10.

13. A chip system, characterized in that, The chip system is applied to an electronic device, the chip system including one or more processors, the one or more processors being used to invoke computer instructions to cause the electronic device to perform the method as described in any one of claims 1 to 10.

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

Images