Display synchronization method, electronic device, chip system, and storage medium

Abstract

The application discloses a display synchronization method, an electronic device, a chip system and a storage medium, which are applied to an electronic device. The method comprises the following steps: determining a first device, and displaying a device ball corresponding to the first device in a trust ring interface. The first device is a device in a same trust ring as the electronic device and online in networking. The device ball corresponding to the first device is used for triggering execution of trust ring service between the first device and the electronic device. A first event of the trust ring process is listened to. The first event comprises trust ring process collapse. If the first event is listened to, the device ball corresponding to the first device in the trust ring interface is invisible. The method can make the trust ring interface display synchronization, thereby avoiding the problem that the operation cannot respond to the service.

Description

Technical Field

[0001] This application relates to the field of computers, and more particularly to display synchronization methods, electronic devices, chip systems, and storage media. Background Technology

[0002] Multiple devices can establish communication connections to form a communication network (referred to as networking). After networking, users can trigger trust loop services (such as screen sharing, network sharing, etc.) between the devices through the trust loop interface. For example, Figure 1A As shown, Figure 1A This is the trust ring interface displayed on the computer. The computer, mobile phone, tablet, and keyboard are on the same network. The device sphere corresponding to the mobile phone is device sphere 101. When the user wants to share the screen, the user can click on this... Figure 1A The device ball 101 in the trust ring interface shown triggers screen sharing between the computer and the mobile phone.

[0003] Electronic devices can perceive the status of devices in the current network (e.g., online / offline) through the trust ring process. The electronic device will display the corresponding device icon in the trust ring interface, thus obtaining information such as... Figure 1A The trust ring interface is shown.

[0004] In reality, the trust ring process in electronic devices may crash due to reasons such as memory leaks. When the trust ring process crashes, it may result in the device becoming unresponsive to business operations. Summary of the Invention

[0005] This application provides a display synchronization method, electronic device, chip system, and storage medium that enable the trust ring interface display to be synchronized, thereby avoiding the problem of unresponsive business operations.

[0006] Firstly, some embodiments of this application provide a display synchronization method. This display synchronization method may include: determining a first device and displaying the device ball corresponding to the first device on a trust ring interface; the first device is a device located in the same trust ring as an electronic device in the network and is online; the device ball corresponding to the first device is used to trigger the execution of trust ring services between the first device and the electronic device; listening to a first event of the trust ring process, the first event including a trust ring process crash; if the first event is detected, making the device ball corresponding to the first device invisible on the trust ring interface.

[0007] By monitoring whether the trust ring process has crashed, and when the trust ring process crashes, the device spheres in the trust ring interface are set to invisible. This avoids the situation where the trust ring interface still displays the device spheres corresponding to other devices in the network after the trust ring process crashes. This achieves synchronization between the display of the trust ring interface and the state of the trust ring process, avoiding the problem of being unable to respond to business operations.

[0008] In one possible implementation, upon receiving a broadcast message from the trust ring process, it is determined whether the first event was successfully listened to. The broadcast message is used to indicate that the trust ring process's service startup is complete. If the first event was not successfully listened to, the trust ring process's first event is listened to again.

[0009] By using the above method, after receiving the broadcast information, it is verified whether the first event of the trust ring process has been successfully listened to. This avoids the problem that the first event of the trust ring process is not listened to because the trust ring process starts too late, which would lead to the inability to achieve display synchronization in the future. This ensures that the first event is listened to.

[0010] In one possible implementation, determining whether the first event was successfully monitored includes: determining the name of the trust ring process, which is preset in the electronic device; determining whether the first event was successfully monitored based on whether the name of the trust ring process maps to the identifier of the trust ring process; wherein, if the first event of the trust ring process is not successfully monitored, the name of the trust ring process is not mapped to the identifier of the trust ring process; if the first event of the trust ring process is successfully monitored, the name of the trust ring process maps to the identifier of the trust ring process.

[0011] In the above way, when the trust ring process is successfully monitored, the name in the trust ring process will be mapped to the identifier of the trust ring process. Therefore, by determining whether the name of the trust ring process is mapped to the identifier of the trust ring process, the first event of successfully monitoring the trust ring process can be accurately determined.

[0012] In one possible implementation, if the first event is detected, the device ball corresponding to the first device in the trust ring interface is made invisible, including: registering a first listener in the trust ring process after receiving the broadcast information sent by the trust ring process; if the first event in the trust ring process is detected, the interface display thread is notified through the first listener to make the device ball corresponding to the first device in the trust ring interface invisible.

[0013] Using the above method, the device sphere corresponding to the first device in the trust ring interface is made invisible through the first listening.

[0014] In one possible implementation, after making the device ball corresponding to the first device in the trust ring interface invisible, the method further includes: re-establishing the trust ring process through a keep-alive process; identifying a second device, which is a device that is located in the same trust ring as the electronic device in the network and is online; and displaying the device ball corresponding to the second device in the trust ring interface through a first listening notification interface display thread.

[0015] By using the above method, after the keep-alive process restarts the trust ring process, it re-acquires devices in the same trust ring as the electronic devices in the network, thus achieving synchronous display.

[0016] In one possible implementation, after the trust ring process is re-established through the keep-alive process, the method also includes: re-listening for the first event of the trust ring process.

[0017] By using the above method, after the trust ring process is restarted, the first event in the process of the trust ring is listened to again, so that synchronization can be displayed even after the trust ring is restarted.

[0018] In one possible implementation, before the trust ring process is re-established through the keep-alive process, the method further includes: if a first event is detected, saving the service information corresponding to the first service, wherein the first service is the trust ring service performed between the electronic device and the first device before the first event is detected; and if the trust ring process is re-established through the keep-alive process and the second device is the first device, performing the first service based on the service information corresponding to the first service.

[0019] The above method enables the intelligent and automatic continuation of business operations prior to the crash after the trust ring process collapses and is restarted.

[0020] In one possible implementation, the trust interface displays all device balls corresponding to the second devices, including: displaying device balls corresponding to the second devices and service status balls corresponding to the second devices, wherein the service status balls are determined based on the service information corresponding to the first service.

[0021] By using the above methods, the business status sphere can be visualized, allowing users to more easily understand the business currently in progress.

[0022] Secondly, this application provides a display synchronization device, which can be an electronic device, a device within an electronic device, or a device compatible with an electronic device; wherein, the device can also be a chip system, and the display synchronization device can execute the method executed by the electronic device in the first aspect. The function of the display synchronization device can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions. The unit can be software and / or hardware. The operation performed by the display synchronization device and its beneficial effects can be found in the method and beneficial effects described in the first aspect above, and will not be repeated here.

[0023] Thirdly, this application provides an electronic device including one or more processors and one or more memories. The one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer program code, including computer instructions, which, when executed by the one or more processors, cause the electronic device to perform the display synchronization method in any possible implementation of the first aspect described above.

[0024] Fourthly, this application provides a chip system including a processor and an interface, the processor and the interface being coupled; the interface is used to receive or output signals, and the processor is used to execute code instructions to perform the display synchronization method in any of the possible implementations of the first aspect above.

[0025] Fifthly, this application provides a computer-readable storage medium storing a computer program / instructions that, when the computer program product is run on a computer, cause the computer to execute the display synchronization method in any of the possible implementations of the first aspect described above.

[0026] Sixthly, this application provides a computer program product that, when run on a computer, causes the computer to execute the display synchronization method in any possible implementation of the first aspect described above. Attached Figure Description

[0027] Figure 1A A schematic diagram of a trust ring interface provided in an embodiment of this application;

[0028] Figure 1B This is a schematic diagram of another trust ring interface provided in an embodiment of this application;

[0029] Figure 1C A flowchart illustrating a trust ring process crash provided in an embodiment of this application;

[0030] Figure 1D A schematic diagram of a system architecture provided for an embodiment of this application;

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

[0032] Figure 3 A schematic diagram of the software structure of an electronic device provided in an embodiment of this application;

[0033] Figure 4 A flowchart illustrating a software-based display synchronization method provided in an embodiment of this application;

[0034] Figure 5 A flowchart illustrating a display synchronization method provided in an embodiment of this application;

[0035] Figure 6 This is another schematic diagram of a trust ring interface provided in an embodiment of this application;

[0036] Figure 7 This is a schematic diagram of the structure of a display synchronization device provided in an embodiment of this application;

[0037] Figure 8 This is a schematic diagram of the structure of a chip provided in an embodiment of this application. Detailed Implementation

[0038] The technical solutions of the embodiments of this application will be clearly and completely 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 the 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.

[0039] It should be understood that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0040] In this application, the reference to "embodiment" means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described in this application can be combined with other embodiments.

[0041] To better understand the display synchronization method provided in this application, the following is an introduction to the technical terms used in this application:

[0042] Trust ring

[0043] MagicRing is a technology solution based on an identity authentication system that enables trusted interconnection of multiple devices across systems, allowing services to flow and be shared intelligently between devices.

[0044] The Smart Connectivity Trust Ring integrates a wide range of devices and services, all visible and controllable within the Trust Ring interface. Devices from the same manufacturer's account, such as phones, tablets, computers, headphones, watches, printers, and in-vehicle systems, are automatically displayed on the Trust Ring interface for easy overview. Within the Trust Ring interface, simple operations allow users to access and transfer the superior services of each device on the Trust Ring to other devices. From a single device's Trust Ring interface, users can control the seamless flow of services across all devices in the ring. The Trust Ring interface also facilitates easy and efficient cross-device application transfer.

[0045] The following is combined Figure 1B The trust loop will be further explained. Figure 1B Three trust ring interfaces are shown: Trust Ring Interface 102, Trust Ring Interface 103, and Trust Ring Interface 104. First, the user launches the Trust Ring workbench and then enters Trust Ring Interface 102 by performing the corresponding operation (e.g., the user clicks the Trust Ring button to enter Trust Ring Interface 102). Trust Ring Interface 102 displays device spheres corresponding to each device located under the same trust ring in the network. Optionally, the three devices displayed in Trust Ring Interface 102 are logged into the same vendor account.

[0046] In the Trust Ring interface 102, when a user clicks on the device sphere corresponding to their own device, the interface automatically displays the icons and names of the Trust Ring services that their device can provide. The user can click / drag the icon of the Trust Ring service they wish to transfer to, and then drag that icon to the device sphere corresponding to the desired device to enable the service between the two devices. For example, as shown in Trust Ring interface 103, after clicking on the device sphere corresponding to the own device, two Trust Ring services that the device can provide are displayed: screen sharing and network sharing. When the user wants to share the screen between the own device and the mobile phone, they drag the screen sharing icon to the device sphere corresponding to the mobile phone, triggering the screen sharing service between the two devices.

[0047] After screen sharing is initiated between the device and the mobile phone, the corresponding service status ball is displayed in the Trust Ring interface. As shown in Trust Ring interface 104, the service status ball is displayed on the device ball corresponding to the mobile phone. This service status ball is used to indicate the Trust Ring service currently being performed by the mobile phone.

[0048] For devices operating under a trust ring system, the trust ring process provides the ability for each device to interact with other devices within the trust ring. Taking the local device as an example, the local device needs to rely on the trust ring process to perceive other devices within the trust ring, and when performing screen sharing, it also needs to rely on the trust ring process to send the corresponding data to the phone.

[0049] However, due to issues such as memory leaks, the trust loop process may crash, and the device is currently unaware of this crash. Therefore, the following situation may occur: after the device's trust loop process crashes, the device's trust loop interface may still display device spheres corresponding to other devices in the trust loop. If the user interacts with these device spheres in the trust loop interface, the electronic device will not respond to the corresponding interaction.

[0050] The following is combined Figure 1C This section explains why a crash in the trust ring process can cause display desynchronization. For example... Figure 1A As shown, assume the trust ring includes the following two devices: an electronic device, a first device, and a keyboard and mouse. For ease of description, the electronic device is referred to as... Figure 1B The host described, the first device, and electronic devices are similar.

[0051] The electronic device includes the following processes: a business center process, a trust ring process, and a keyboard and mouse process. The business center process can include threads for various business operations (such as threads for the trust ring business) and a user interface display thread. This user interface display thread is used to draw the UI, etc. (e.g.,...) Figure 1BThe trust ring interface 102 is drawn by the interface display thread. The trust ring process is used to provide electronic devices with the ability to interact with other devices in the trust ring. The keyboard and mouse process is a thread for special trust ring operations.

[0052] After a user starts the Trust Ring workbench, each service in the business center process registers an observer with the Trust Ring process. For example, the screen sharing service registers observer1 with the Trust Ring process, and the network sharing service registers observer2. Similarly, the keyboard and mouse process is also a Trust Ring service, so it will also register observer3 with the Trust Ring process.

[0053] Once the trust ring process discovers the first device in the authentication network, it reports the first device's online status to each service through the observers registered by each service. For example, the trust ring process reports the first device's online status to the screen sharing service through observer1, to the network sharing service through observer2, and to the keyboard and mouse service corresponding to the keyboard and mouse process through observer3. At this time, the trust ring interface of the electronic device displays the device ball corresponding to the keyboard and mouse and the device corresponding to the first device (e.g., ...). Figure 1C The device sphere marked 110 in the middle). Correspondingly, the trust ring interface of the first device displays the device spheres corresponding to the keyboard and mouse, as well as the devices corresponding to the electronic devices (such as...). Figure 1C (The device ball marked 111 in the middle).

[0054] Users through such Figure 1B The drag-and-drop operation shown triggers screen sharing between the electronic device and the first device. After successful screen sharing, the corresponding service status ball will be attached to the corresponding device ball in the trust ring interface. (e.g.) Figure 1C (The service status ball marked with 112 in the middle). Correspondingly, the same applies to the first device side.

[0055] If the trust ring process of the electronic device crashes at this time, it's equivalent to the electronic device disconnecting from the first device, and screen sharing ceases. However, because the service center process cannot detect the trust ring process crash, the interface display thread within the service center process will not update the trust ring interface. Therefore, the trust ring interface on the electronic device still displays the screen as it was before the trust ring process crashed. At this point, for the user, the trust ring interface displays normally, but the functionality is abnormal, and the trust ring service cannot be triggered correctly. Meanwhile, because the trust ring process on the first device side has not crashed, the first device can detect the disconnection of the electronic device, and its trust ring interface displays as shown below. Figure 1C As shown in the Trust Ring interface 113 marked in 113, the device sphere corresponding to the original electronic device in the Trust Ring interface 113 is no longer visible.

[0056] Therefore, in order to ensure that the trust ring interface display is synchronized and thus avoid the problem of unresponsive business operations, this application provides a display synchronization method. After the trust ring process crashes, the electronic device can promptly detect this and notify the interface display thread, causing the interface display thread to update the trust ring interface, making all device spheres in the trust ring interface invisible, thereby achieving synchronization between display and function.

[0057] The communication system provided in the embodiments of this application is described below. Figure 1D The diagram shown is a structural schematic of a communication system provided in an embodiment of this application. This communication system may include multiple devices, such as... Figure 1D As shown, the communication system includes device 120, device 121 and device 122.

[0058] Optionally, the communication system may include fewer devices (e.g., the communication system includes only two devices, device 120 and device 122), or the communication system may include more devices (e.g., the communication system includes five devices). The devices in the communication system can be different, such as... Figure 1D As shown, device 120 is a computer, device 121 is a tablet, and device 122 is a mobile phone. The devices in this communication system can also be identical; this similarity can be entirely the same or only slightly different. This application does not impose any restrictions on this.

[0059] Optionally, all devices in this communication system are located on the same network and logged into the same vendor account, meaning they are all within the same trust ring. The devices in this communication system can connect via WiFi and / or Bluetooth, and can perform trust ring services, such as screen sharing.

[0060] Optionally, devices can communicate with each other via short-range communication, establishing at least one link. These links can operate on the same frequency band or channel. Trust ring services between devices can be carried on these links. Each link can carry one or more services.

[0061] Figure 1DAny device mentioned can be a smart terminal device, and can be of various types; the specific type is not limited in this application embodiment. For example, it can be a mobile phone, and can also include tablet computers, desktop computers, laptop computers, handheld computers, smart screens, wearable devices, augmented reality (AR) devices, virtual reality (VR) devices, artificial intelligence (AI) devices, in-vehicle systems, smart headphones, game consoles, and can also be Internet of Things (IoT) devices or smart home devices such as smart TVs, etc. It is not limited to these; it can also include non-portable terminal devices such as laptops and desktop computers with touch-sensitive surfaces or touch panels.

[0062] The hardware of the electronic device involved in this application is described below, such as... Figure 2 The diagram shown is a hardware structure schematic of an electronic device 200 provided in an embodiment of this application. The electronic device 200 can be a mobile phone, laptop, large-screen device, etc., as mentioned above.

[0063] Electronic device 200 may include processor 201, memory 202, wireless communication module 203, mobile communication module 204, antenna 203A, antenna 204A, etc. The wireless communication module 203 may include a WLAN communication module, Bluetooth communication module, etc. All of the above components can transmit data via a bus.

[0064] Processor 201 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). These different processing units may be independent devices or integrated into one or more processors.

[0065] The memory 202 can be used to store computer executable program code, which may include instructions. The processor 201 executes various functional applications and data processing of the electronic device 200 by running the instructions stored in the memory 202, such as performing the various methods provided in the embodiments of this application.

[0066] The wireless communication function of electronic device 200 can be implemented through antenna 203A, antenna 204A, mobile communication module 204, wireless communication module 203, modem processor, and baseband processor.

[0067] Antennas 203A and 204A can be used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 200 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 203A can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

[0068] The mobile communication module 204 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 200. The mobile communication module 204 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 204 can receive electromagnetic waves via antenna 204A, and perform filtering and amplification on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 204 can also amplify the signal modulated by the modem processor, and the amplified signal is converted into electromagnetic waves and radiated out via antenna 204A. In some embodiments, at least some functional modules of the mobile communication module 204 may be housed in the processor 201. In some embodiments, at least some functional modules of the mobile communication module 204 and at least some modules of the processor 201 may be housed in the same device.

[0069] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 201 and may be housed in the same device as the mobile communication module 204 or other functional modules.

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

[0071] In some embodiments, the antenna 204A of the electronic device 200 is coupled to the mobile communication module 204, and the antenna 203A of the electronic device 200 is coupled to the wireless communication module 203, so that the electronic device 200 can communicate with the network and other devices through wireless communication technology.

[0072] It is understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on the electronic device 200. In other embodiments of this application, the electronic device 200 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.

[0073] In this embodiment, the wireless communication module 203 can be used for WiFi connection, data or instruction transmission between electronic devices.

[0074] The operations performed by each device in electronic device 200 can be specifically referred to in the relevant descriptions of the method embodiments above, and will not be elaborated here.

[0075] Figure 3 This is a schematic diagram of the software system structure of an electronic device 200 provided in an embodiment of this application.

[0076] Layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments, the Windows system is divided into four layers, from top to bottom: user mode and kernel mode. It should be noted that this application uses the Windows system as an example; other systems can be deduced similarly.

[0077] First, in user mode, there are four basic user mode processes in the Windows operating system: environment subsystem, system processes, service processes, and user processes.

[0078] The environment subsystem, or environment subsystem processes, refers to those processes that implement the supporting parts of the operating system environment. The environment refers to the customizable portion of the operating system presented to users and programmers. Windows NT initially provided three environment subsystems: Windows, POSIX, and OS / 2.

[0079] System processes refer to statically typed or hard-coded processes, such as the login process and session manager, which are not Windows services. In other words, these processes are not started by the Service Control Manager.

[0080] The service process hosts Windows services.

[0081] User processes can be 32-bit or 64-bit Windows processes, 15-bit Windows 3.1 processes, 16-bit MS-DOS processes, or 32-bit or 64-bit POSIX processes.

[0082] Subsystem DLLs and NTDLL.DLLs expose certain subsets of the basic Windows executable system services to applications. These subsystems can access different subsets of native Windows services. In Windows, user applications cannot directly call native Windows operating system services; instead, they need to call them through one or more subsystem dynamic link libraries (DLLs). The role of subsystem DLLs is to translate documented functions into corresponding internal (often undocumented) native system service calls, which are typically implemented in NTDLL.DLLs. This translation may or may not involve the environment subsystem processes that send messages to the user process to provide the service.

[0083] In kernel mode, the following components are included: windows and graphics, execution units, device drivers, the kernel, and the Hardware Abstraction Layer (HAL).

[0084] The Executable: The Windows Executable contains the operating system's basic services, such as memory management, process and thread management, security, networking, and inter-process communication.

[0085] Kernel: The Windows kernel contains low-level operating system functions such as thread scheduling, interrupt and exception dispatching, and multiprocessor synchronization. The kernel also provides a series of routines and basic objects that other parts of the execution body use to implement higher-level functionalities.

[0086] Device drivers: Device drivers include hardware device drivers that translate user I / O function calls into specific hardware device I / O requests, as well as non-hardware device drivers such as file system and network drivers.

[0087] Hardware Abstraction Layer (HAL): This layer of code is responsible for isolating the kernel, device drivers, and other parts of the Windows execution from platform-specific differences.

[0088] Windows and Graphics: The window and graphics system is used to implement user interface (GUI) functions (often also known as Windows User Interface (GDI) functions), such as handling windows, user interface controls, and drawing.

[0089] Hyper-V Hypervisor: This section contains only the hypervisor itself. It does not include other drivers or modules. However, the hypervisor itself consists of various internal layers and drivers, such as its own memory manager, virtual processor scheduler, interrupt and timer management, synchronization routines, partition (virtual machine instance) management, and inter-instance communication (IPC).

[0090] The following is combined Figure 4 This application describes the display synchronization method provided. Specifically, the method... Figure 4 The hardware structure of the electronic devices in the document can be found in the above. Figure 2 As shown, the software structure of this electronic device can be found in the above description. Figure 3 As shown. In Figure 3 The system processes can include business center processes, trust ring processes, and keyboard and mouse processes, etc.

[0091] Optionally, the electronic device can adopt a client / server architecture, with the client running in the business center process and the server running in the trust ring process. The client can also reside in other processes; this application does not impose any restrictions on this.

[0092] 401. The trust ring process monitors the business center process. Accordingly, the business center process is monitored by the trust ring process.

[0093] The trust ring process can use the Win API interface to listen to the business center process. This Win API interface is a sub-interface of the Windows system.

[0094] Optionally, after the trust ring workbench is started, and the business center process and trust ring process have both started, the trust ring process monitors the business center process. This trust ring workbench can be built into another workbench within the electronic device, or it can be a standalone workbench.

[0095] 402. The business center process monitors the trust ring process. Accordingly, the trust ring process is monitored by the business center process.

[0096] Optionally, the business center process can use the Win API interface to listen for dump events in the trust ring process.

[0097] Optionally, after the trust ring workbench is started, and after the business center process has started and the trust ring process has started, the business center process listens to the trust ring process.

[0098] Optionally, since the keyboard and mouse process is a special business process, it needs to monitor the trust ring process separately.

[0099] 403. The Trust Ring process notifies the business center process service to start.

[0100] Optionally, the trust ring process notifies the business center process of service startup. Specifically, the trust ring process sends a service startup broadcast to the business center process. This service startup broadcast is used to inform the business center process that the trust ring process initialization is complete, or that the trust ring process has started successfully.

[0101] 404. The business center process determines whether to monitor the trust ring process. If not, it re-monitors the trust ring process.

[0102] Since the timing of starting the business center process and starting the trust ring process may differ, after step 402, the business center process also needs to execute step 404 to check if the listening was successful. If the listening was unsuccessful, the business center process executes step 402 again to listen to the trust ring process again.

[0103] Optionally, if the business center process starts first and the trust ring process starts later, step 404 will determine that the trust ring process is not being monitored and needs to be monitored again.

[0104] Optionally, if the trust ring process starts first and the business center process starts later, then step 404 will determine that there is a listening trust ring process, and it is not necessary to listen to the trust ring process again.

[0105] The business center process registers the first listener with the trust ring process.

[0106] Optionally, after the business center process starts, each business within the business center process, upon receiving the service startup notification from the trust ring process, registers a first listener with the trust ring process. This first listener is used to monitor device online / offline status and changes in attribute values. These attribute values ​​represent the device's business execution status, thereby displaying the corresponding device sphere and status sphere on the trust ring interface.

[0107] For example, the business center process includes the following businesses: business A, business B, and business C. Business A registers a first listener A in the trust ring process, business B registers a first listener B in the trust ring process, and business C registers a first listener C in the trust ring process.

[0108] This step can be found above. Figure 1C The details described in the previous section will not be repeated here.

[0109] 405. The trust ring process determines whether to monitor the business center process. If not, it re-monitors the business center process.

[0110] Since the timing of starting the business center process and starting the trust ring process may differ, after step 401, the trust ring process also needs to execute step 405 to check if the listening was successful. If the listening was unsuccessful, the trust ring process executes step 401 again to listen to the business center process again.

[0111] Optionally, if the business center process starts first and the trust ring process starts later, then step 404 will determine that there is a listening trust ring process, and it is not necessary to listen to the trust ring process again.

[0112] Optionally, if the trust ring process starts first and the business center process starts later, step 404 will determine that the trust ring process is not being monitored and needs to be monitored again.

[0113] 406. The business center process saves the first listener to the MAP.

[0114] For example, the business center process stores the first listener A, the first listener B, and the first listener C mentioned above in a MAP.

[0115] After both the electronic device and the first device are discovered and authenticated, they go online normally. For the electronic device, when the trust ring process in the electronic device discovers the first device, it reports the first device to the business center process and the keyboard and mouse process. After receiving the report from the trust ring process, the business center process will display the device ball corresponding to the first device in the business interface.

[0116] 407. The business center process saves the information of the first device to container A.

[0117] The information of the first device is its identifier, with different devices corresponding to different identifiers. This information can be obtained by the trust ring process during the discovery and authentication network formation, and then reported to the business center process when the trust ring process reports the first device's information to the business center process upon its online deployment.

[0118] Optionally, the business center process will save information about all devices in the discovery and authentication network to container A. Assume that in the same trust ring within the network, besides electronic devices, there are also device 1, device A, device B, and device C. Then the business center process will save information about device 1, device A, device B, and device C to container A.

[0119] The electronic device and the first device perform a screen sharing service. This screen sharing service is a trust loop service. It should be noted that other trust loop services can also be performed between the electronic device and the first device, which is not limited herein.

[0120] 408. The business center process saves the currently executing business information.

[0121] Optionally, the service information includes the currently executed service (e.g., screen sharing service) and the device currently executing the service (e.g., the first device). The service information may also include the service status, such as whether the screen sharing service is running. In this embodiment, the screen sharing service is in the "on" state, and the network sharing service is in the "off" state.

[0122] After the trust ring process crashes:

[0123] 409. The business center process detected that the trust ring process had crashed.

[0124] Because the business center process monitors the trust ring process, it can promptly detect the trust ring process's collapse. In other words, the business center process detects the trust ring collapse through the monitoring operation in step 402.

[0125] 410. The business center process notifies all devices in each business container A to go offline.

[0126] Since the information of the first device in step 407 is stored in container A, based on the device information stored in container A, all devices of each service are notified to go offline.

[0127] Optionally, the service center process may notify all devices of each service to go offline via the first listener (step 406) stored in the MAP.

[0128] Since the first listener is a listener registered by each business, meaning there is a one-to-one mapping relationship between the first listener and the business, notifications can be sent to each business based on the first listener.

[0129] In other words, when the business center process detects that the trust ring process has crashed, it then notifies all services to take all devices offline. The business center process and the trust ring process detect each other through the business center process's monitoring of the trust ring process, and the business center process and each service communicate through the first monitoring.

[0130] The Trust Ring interface has been updated, and user-aware devices have been removed from the network.

[0131] Optionally, the trust ring interface is updated as follows: after receiving the notification, the interface display thread in the business center process redraws the trust ring interface and removes each device ball from the trust ring interface.

[0132] At this point, the connection between the electronic device and the first device has been lost. However, a keep-alive process still exists in the electronic device. This keep-alive process is used to restart processes in the whitelist if they crash. The Trust Ring process is in the whitelist, so when the Trust Ring process crashes, the keep-alive process automatically restarts it. Accordingly, the Trust Ring process is restarted by the keep-alive process.

[0133] 411. The trust ring process monitors the business center process.

[0134] Although the trust ring process was monitoring the business center process before it crashed, its monitoring stopped after the crash. Therefore, after the trust ring process is restarted by the keep-alive process, it needs to start monitoring the business center process again. The purpose of monitoring the business center process in steps 401 and 411 is that when the trust ring process crashes and is restarted by the keep-alive process, it needs to release data related to the business center process to avoid consuming memory and other resources.

[0135] Optionally, after step 411, and after the business center process registers the first listener with the trust ring process, the trust ring process can also perform step 405 after step 411 to determine whether the listening in step 411 was successful.

[0136] 412. The business center process monitors the trust ring process.

[0137] Optionally, this step can be referred to step 402 above. Since the keyboard and mouse process is a special process, it also needs to separately monitor the trust ring process again.

[0138] 413. The Trust Ring process notifies the business center process service to start.

[0139] Optionally, the notification may include an identifier for the trust ring process, which may include the process ID of the trust ring process.

[0140] Optionally, after step 413, the process may further include: the business center process determining whether to monitor the trust ring process; if not, then re-monitoring the trust ring process.

[0141] 414. The business center process obtains all online devices from the trust ring process.

[0142] Optionally, online devices are devices that are in the network and located under the same trust ring.

[0143] 415. The business center notifies all business devices that they are online.

[0144] Optionally, the business center process notifies each business device that it is online. Specifically, the business center process informs each business device that it is online through the first listener saved in step 406.

[0145] Optionally, upon receiving the notification, the interface display thread within the business center process redraws the trust ring interface, displaying the device spheres within it. These displayed device spheres correspond to the acquired online devices.

[0146] 416. The business center process traverses the MAP to register a second listener.

[0147] The second listener is the listener for each service to re-register with the trust ring process. The function of the second listener can be found in the above description of the first listener, and will not be repeated here.

[0148] Optionally, after each business in the business center process registers a second listener, the business center process saves the second listener to the MAP.

[0149] 417. The business center process notifies the corresponding business to be re-initiated based on the saved business information.

[0150] Optionally, the business center process may notify the corresponding business through a callback based on the business information saved in step 408. After receiving the notification, the business will automatically re-initiate the business.

[0151] Optionally, after a service is re-initiated, the interface display thread in the service center process will update the trust ring interface based on the service information and display the service status ball on the corresponding device ball in the trust ring interface.

[0152] The display synchronization method provided in the embodiments of this application is further described below: Please refer to Figure 5 As shown, Figure 5This is a flowchart illustrating a display synchronization method provided in an embodiment of this application. The display synchronization method includes the following steps 501-503. Figure 5 The method shown can be executed by an electronic device (specifically, the...). Figure 5 The execution entity of the method shown can be Figure 1D (Any of the devices in the list). Or Figure 5 The subject of the method shown can be a chip or chip system in an electronic device, but this application does not limit it. Figure 5 The method will be explained using an electronic device as the executing entity. Specifically:

[0153] 501. The electronic device identifies the first device and displays the device ball corresponding to the first device on the trust ring interface. The first device is a device that is located in the same trust ring as the electronic device in the network and is online. The device ball corresponding to the first device is used to trigger the execution of the trust ring service between the first device and the electronic device.

[0154] Optionally, the first device and the electronic device can be logged into the same manufacturer account. Alternatively, the first device and the electronic device can be logged into manufacturer accounts within the same group. For example, the accounts of parents and the user within a family can be grouped together, with the electronic device logging into its own manufacturer account and the first device logging into the father's manufacturer account.

[0155] Optionally, the first device is determined by the electronic device, specifically through a trust ring process. The first device can be one or more devices; any device that is located in the same trust ring as the electronic device and is online can be referred to as the first device.

[0156] For example, the trust ring interface in this electronic device can be seen in... Figure 1A As shown, the Figure 1A The interface can also display the device icon corresponding to the device itself (electronic device). For example, if the first device is a mobile phone and a tablet, then... Figure 1A As shown, the device ball corresponding to the mobile phone and the device ball corresponding to the tablet are displayed in the trust ring interface.

[0157] Optionally, the device ball corresponding to the first device can be displayed on the trust ring interface. Specifically, the device ball corresponding to the first device can be displayed on the trust ring interface based on the interface display thread.

[0158] Optionally, after the electronic device receives an instruction to start the Trust Ring workbench (e.g., the user clicks the Trust Ring button to enter the Trust Ring interface), the electronic device determines the first device.

[0159] 502. Electronic devices monitor the first event of the trust ring process, including trust ring process crash.

[0160] Optionally, the first event is the dump event.

[0161] Optionally, the electronic device listens for dump events in the trust ring process via a Win API interface.

[0162] Optionally, the monitoring of the first event of the trust ring process in step 502 can be achieved through the above-mentioned... Figure 4 This is performed in step 402 of the process. Specifically, the business center process in the electronic device listens for the first event of the trust ring process.

[0163] In one possible embodiment, when the electronic device receives a broadcast message sent by the trust ring process, it determines whether it has successfully listened to the first event. The broadcast message is used to indicate that the service startup of the trust ring process has been completed. If the electronic device has not successfully listened to the first event, it will listen to the first event of the trust ring process again.

[0164] Optionally, the broadcast information can be executed. Figure 4 The message is sent in step 403, which means that the trust ring process notifies the business center process to start the service via broadcast information.

[0165] Optionally, this step 502 corresponds to Figure 4 Step 404 in the process means that after the business center process in the electronic device receives the broadcast information sent by the trust ring process, it determines whether it has successfully listened to the first event.

[0166] Optionally, the first event of the trust ring process can be re-listened to, specifically by re-listening to the dump event in the trust ring process via the Win API interface.

[0167] In one possible embodiment, the electronic device determines whether it has successfully listened to the first event, including: the electronic device determining the name of the trust ring process, the name of the trust ring process being preset in the electronic device; the electronic device determining whether it has successfully listened to the first event based on whether the name of the trust ring process is mapped to the identifier of the trust ring process; wherein, when listening to the first event of the trust ring process is unsuccessful, the name of the trust ring process is not mapped to the identifier of the trust ring process; when listening to the first event of the trust ring process is successful, the name of the trust ring process is mapped to the identifier of the trust ring process.

[0168] Optionally, the name of the trust ring process is the default name of the trust ring process on the electronic device. Specifically, the name of the trust ring can be configured in a configuration file.

[0169] Optionally, the identifier of the trust ring process is the trust ring process number.

[0170] Optionally, when the electronic device re-listens for dump events in the trust ring process via the Win API interface, the electronic device will obtain the trust ring process ID of that trust ring process.

[0171] Optionally, when an electronic device successfully listens to a trust ring process, its name will correspond to the trust ring process's identifier. When determining whether the electronic device has successfully listened to the first event, it will check if the trust ring process's name is mapped to its identifier. If the trust ring process's name is mapped to its identifier, the electronic device determines that the trust ring process listening has been successful; otherwise, if the trust ring process's name is not mapped to its identifier, the electronic device determines that the trust ring process listening has failed.

[0172] For example, suppose the name of the trust ring process is MagicRing.exe, and the trust ring process ID is 234687. If an electronic device queries MagicRing.exe = 234687, it considers the monitoring of the trust ring process to be successful; if the device queries NULL, it considers the monitoring of the trust ring process to have failed.

[0173] Optionally, in addition to the above-mentioned determination method, this application also provides another method for determining whether to monitor the first event of the trust ring process. This method involves the electronic device, upon receiving a broadcast message from the trust ring process, determining whether the historical received messages include a successful monitoring message sent by the trust ring process. This successful monitoring message is sent by the trust ring process after being successfully monitored. Specifically, if the first event of the trust ring process is not successfully monitored, a successful monitoring message will not be received; conversely, if the first event of the trust ring process is successfully monitored, a successful monitoring message will be received.

[0174] Since listening failures typically occur because the trust ring process hasn't finished starting, and the electronic device is already listening to it, a message can only be sent after the trust ring process has finished starting. Therefore, if the received message history includes a successful listening message, it means that the trust ring process had already started when the listening was initiated, and the listening was successful.

[0175] 503. If an electronic device detects the first event, it will make the device sphere corresponding to the first device in the trust ring interface invisible.

[0176] Optionally, making the device sphere corresponding to the first device in the trust ring interface invisible can be achieved by: removing the device sphere corresponding to the first device from the trust ring interface; or setting the device sphere corresponding to the first device in the trust ring interface to be transparent. This application does not impose any limitations on this.

[0177] In one possible embodiment, if the electronic device detects the first event, it will make the device ball corresponding to the first device in the trust ring interface invisible, including: after receiving the broadcast information sent by the trust ring process, the electronic device registers a first listener in the trust ring process; if the electronic device detects the first event in the trust ring process, it will make the device ball corresponding to the first device in the trust ring interface invisible through the first listener notification interface display thread.

[0178] Optionally, the interface display thread can be located in the business center process. This interface display thread can be used to draw the interface, specifically the trust ring interface.

[0179] In one possible embodiment, the step of making the device sphere invisible in the trust ring interface can be found in the description of step 410 above.

[0180] Optionally, the device spheres corresponding to all devices in the trust ring interface can be made invisible, or the device spheres corresponding to all first devices in the trust ring interface can be made invisible.

[0181] For example, see Figure 1A As shown, Figure 1A The first device in the trust ring interface is a mobile phone and a tablet. The trust ring interface also includes a device ball corresponding to the device itself (electronic device). Making the device balls in the trust ring interface invisible can be done by setting the device balls corresponding to the mobile phone and tablet to invisible, or by setting the device balls of the mobile phone, tablet, and device itself to invisible.

[0182] In one possible embodiment, after the electronic device makes the device ball corresponding to the first device in the trust ring interface invisible, the method further includes: the electronic device re-establishing the trust ring process through a keep-alive process; the electronic device determining a second device, which is a device in the same trust ring as the electronic device in the network and is online; and the device ball corresponding to the second device being displayed in the trust ring interface through a first listening notification interface display thread.

[0183] The keep-alive process is used to restart processes in the whitelist after they crash. Since the trusted ring process is in the whitelist, the keep-alive process will automatically restart it if it crashes.

[0184] Optionally, the second device can be the first device, or it can be something other than the first device. For example, if the first device is a mobile phone and a tablet before the trust ring process crashes, and the second device is a mobile phone and a TV after the keep-alive process restarts the trust ring process.

[0185] Optionally, the device sphere displayed on the Trust Ring interface before the Trust Ring process crashes and the device sphere displayed on the Trust Ring interface after the Trust Ring process crashes can be exactly the same, partially the same, or completely different.

[0186] In one possible embodiment, after the electronic device re-establishes the trust ring process through a keep-alive process, the method further includes: the electronic device re-listening for the first event of the trust ring process.

[0187] Optionally, the re-establishment of listening to the trust ring process can be found in the description of step 412 above.

[0188] In one possible embodiment, before the electronic device re-establishes the trust ring process through the keep-alive process, the method further includes: if the electronic device detects the first event, it saves the service information corresponding to the first service, wherein the first service is the trust ring service performed by the electronic device and the first device before the first event is detected; and if the electronic device re-establishes the trust ring process through the keep-alive process and the second device is the first device, it performs the first service based on the service information corresponding to the first service.

[0189] Optionally, the service information includes the currently executed service (e.g., screen sharing service) and the device currently executing the service (e.g., the first device). The service information may also include the service status, such as whether the screen sharing service is running. In this embodiment, the screen sharing service is in the "on" state, and the network sharing service is in the "off" state.

[0190] For example, the service information is as follows: Screen sharing service (first service) — enabled — first device, network sharing service — disabled.

[0191] Optionally, after the trust ring process is re-established, the electronic device automatically restores all services based on the business information.

[0192] For example, suppose that at the first moment, the electronic device is conducting a screen sharing service with the television (first device), and a network sharing service with the electronic device and a mobile phone (another first device), and saves the service information for both the screen sharing and network sharing services. At the second moment, the trust ring process in the electronic device crashes, and the electronic device disconnects from both the television and the mobile phone. At the third moment, the keep-alive process restarts the trust ring process in the electronic device, at which point the television is turned off and no longer within the network. At the fourth moment, the network sharing service between the electronic device and the mobile phone is restored based on the service information of the network sharing service. Since the television is no longer within the network, it is not necessary to restore the screen sharing service between the electronic device and the television.

[0193] Optionally, if the electronic device and the first device were engaged in a file transfer service at the first moment (before the trust ring process of the electronic device crashed), then after the file transfer service is restored, the file data transferred at the first moment can continue to be transferred.

[0194] For example, suppose that at the first moment, the electronic device is transmitting images to the television, and the electronic device wants to transmit 10 images to the television. At the second moment, after transmitting 4 images, the trust loop process in the electronic device crashes, and the electronic device loses connection with the television. At the third moment, the keep-alive process restarts the trust loop process in the electronic device. At the fourth moment, image transmission resumes, and the electronic device continues transmitting images starting from the fifth image.

[0195] In one possible embodiment, the electronic device displays device balls corresponding to all second devices in the trust interface, including: the electronic device displays device balls corresponding to the second devices and service status balls corresponding to the second devices in the trust interface, wherein the service status balls are determined based on the service information corresponding to the first service.

[0196] Optionally, the service status sphere may include icons corresponding to the service, such as... Figure 1B As shown, the icons for screen sharing and network sharing services are different. Displaying the service icon in the service status ball allows users to more intuitively perceive the service currently in progress. Furthermore, since the service status ball is attached to the device ball, it allows users to more intuitively perceive the device currently performing the service.

[0197] The change process of the trust ring interface under the synchronous display method of this application can be found in [reference needed]. Figure 6 As shown, Figure 6 The leftmost diagram shows the trust loop interface of the electronic device before the trust loop process collapses in the first instant. Figure 6 The diagram in the middle represents the trust loop interface diagram when the trust loop process of the electronic device collapses at the second moment. Figure 6 The rightmost diagram shows the trust loop interface after the trust loop process of the electronic device is restarted at the third moment.

[0198] Please see Figure 7 , Figure 7 This is a schematic diagram of the structure of a display synchronization device 700 provided in an embodiment of this application. Figure 7 The display synchronization device shown can be an electronic device, a device within an electronic device, or a device that can be used in conjunction with an electronic device. Figure 7 The display synchronization device shown may include a determining unit 701 and a processing unit 702. Wherein:

[0199] The determining unit 701 is used to determine the first device and display the device ball corresponding to the first device on the trust ring interface. The first device is a device that is located in the same trust ring as the electronic device in the network and is online. The device ball corresponding to the first device is used to trigger the execution of the trust ring service between the first device and the electronic device.

[0200] Processing unit 702 is used to listen to the first event of the trust ring process, the first event including trust ring process crash;

[0201] The processing unit 702 is also configured to make the device ball corresponding to the first device in the trust ring interface invisible if the first event is detected.

[0202] In one possible embodiment, the processing unit 702 is further configured to, upon receiving a broadcast message sent by the trust ring process, determine whether the first event has been successfully monitored, wherein the broadcast message is used to indicate that the service startup of the trust ring process has been completed; if the first event has not been successfully monitored, then the first event of the trust ring process is monitored again.

[0203] In one possible embodiment, the determining unit 701 is further configured to determine the name of the trust ring process, the name of which is preset in the electronic device;

[0204] The processing unit 702 is further configured to determine whether the first event has been successfully monitored based on whether the name of the trust ring process is mapped to the identifier of the trust ring process; wherein, when the first event of the trust ring process is not successfully monitored, the name of the trust ring process is not mapped to the identifier of the trust ring process; when the first event of the trust ring process is successfully monitored, the name of the trust ring process is mapped to the identifier of the trust ring process.

[0205] In one possible embodiment, the processing unit 702 is further configured to register a first listener in the trust ring process after receiving broadcast information sent by the trust ring process; if a first event is detected in the trust ring process, the device ball corresponding to the first device in the trust ring interface is made invisible through the first listener notification interface display thread.

[0206] In one possible embodiment, the processing unit 702 is further configured to re-establish the trust ring process through a keep-alive process;

[0207] The determining unit 701 is also used to determine the second device, which is a device that is located in the same trust ring as the electronic device in the network and is online;

[0208] The processing unit 702 is also used to display the device ball corresponding to the second device in the trust ring interface through the first listening notification interface display thread.

[0209] In one possible embodiment, the processing unit 702 is also configured to re-listen to the first event of the trust ring process.

[0210] In one possible embodiment, the processing unit 702 is further configured to, if a first event is detected, save the service information corresponding to the first service, wherein the first service is a trust ring service between the electronic device and the first device before the first event is detected; and, if the trust ring process is re-established through a keep-alive process and the second device is the first device, perform the first service based on the service information corresponding to the first service.

[0211] In one possible embodiment, the processing unit 702 is further configured to display a device ball corresponding to the second device and a service status ball corresponding to the second device in the trust interface, wherein the service status ball is determined based on the service information corresponding to the first service.

[0212] For cases where the display synchronization device can be a chip or a chip system, please refer to [link / reference]. Figure 8 The diagram shows the structure of the chip. Figure 8 The chip 800 shown includes a processor 801 and an interface 802. Optionally, it may also include a memory 803. The number of processors 801 can be one or more, and the number of interfaces 802 can be multiple.

[0213] For cases where the chip is used to implement the electronic device in the embodiments of this application:

[0214] The interface 802 is used to receive or output signals;

[0215] The processor 801 is used to perform data processing operations of the electronic device.

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

[0217] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Accordingly, the predistortion device given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

[0218] It should be understood that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0219] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may 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). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0220] This application also provides a computer-readable storage medium storing a computer program, the computer program including program instructions that, when executed on an electronic device, implement the functions of any of the above method embodiments.

[0221] This application also provides a computer program product that, when run on a computer, enables the computer to perform the functions of any of the above method embodiments.

[0222] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0223] 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 display synchronization method, characterized in that, Applied to electronic devices, the method includes: The first device is identified and the device ball corresponding to the first device is displayed on the trust ring interface. The first device is a device that is in the same trust ring as the electronic device in the network and is online. The device ball corresponding to the first device is used to trigger the execution of the trust ring service between the first device and the electronic device. The business center process monitors and registers the first event of the trust ring process, including the collapse of the trust ring process. Upon receiving a broadcast message from the trust ring process, the name of the trust ring process is determined. The name of the trust ring process is preset in the electronic device. The broadcast message is used to indicate that the service startup of the trust ring process has been completed. Based on whether the name of the trust ring process maps to the identifier of the trust ring process, it is determined whether the first event was successfully monitored. Wherein, if the first event of the trust ring process is not successfully monitored, the name of the trust ring process does not map to the identifier of the trust ring process; if the first event of the trust ring process is successfully monitored, the name of the trust ring process maps to the identifier of the trust ring process. If the first event is detected by the business center process, then all device balls corresponding to the first device in the trust ring interface will be made invisible. If the first event is not successfully monitored, then the first event monitoring registration for the trust ring process is re-established.

2. The method according to claim 1, characterized in that, If the first event is detected, the device sphere corresponding to the first device in the trust ring interface will be made invisible, including: After receiving the broadcast information sent by the trust ring process, register the first listener in the trust ring process; If the first event in the trust ring process is detected, the device ball corresponding to the first device in the trust ring interface will be made invisible through the first monitoring notification interface display thread.

3. The method according to claim 2, characterized in that, After making the device sphere corresponding to the first device in the trust ring interface invisible, the method further includes: The trust ring process is re-established through a keep-alive process; The second device is identified as a device that is located in the same trust ring as the electronic device in the network and is online. The interface display thread will display the device sphere corresponding to the second device in the trust ring interface via the first listening notification.

4. The method according to claim 3, characterized in that, After the trust ring process is re-established through the keep-alive process, the method further includes: Re-listen to the first event of the trust ring process.

5. The method according to claim 3 or 4, characterized in that, Before re-establishing the trust ring process through a keep-alive process, the method further includes: If the first event is detected, the service information corresponding to the first service is saved. The first service is the trust loop service between the electronic device and the first device before the first event is detected. If the trust ring process is re-established through the keep-alive process, and the second device is the first device, the first service is performed based on the service information corresponding to the first service.

6. The method according to claim 5, characterized in that, The step of displaying all device spheres corresponding to the second device in the trust ring interface includes: The trust ring interface displays the device ball corresponding to the second device and the service status ball corresponding to the second device. The service status ball is determined based on the service information corresponding to the first service.

7. An electronic device comprising one or more memories and one or more processors, characterized in that, The memory is used to store a computer program; the processor is used to invoke the computer program, causing the electronic device to perform the method of any one of claims 1-6.

8. A chip system for use in electronic devices, characterized in that, The chip system includes at least one processor and an interface for receiving instructions and transmitting them to the at least one processor; the at least one processor executes the instructions to cause the electronic device to perform the method as described in any one of claims 1-6.

9. A computer-readable storage medium having a computer program / instructions stored thereon, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the method as described in any one of claims 1-6.

10. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the method as described in any one of claims 1-6.

Images