Display method, device and equipment of user interface and storage medium

Abstract

Embodiments of the present application disclose a display method and device of a user interface, an apparatus and a storage medium, and belong to the field of wearable devices. The method comprises: displaying a first user interface through a first system when the first system is in an awake state and a second system is in a dormant state; in response to a system switching instruction, drawing and displaying a second user interface through the first system, the second user interface being a user interface of the second system; and in response to the second system completing drawing of the second user interface, displaying the second user interface through the second system. The second user interface is displayed through the first system, which can improve the starting speed of visual system switching and reduce the display delay of the second user interface of the second system during the system switching process.

Description

Technical Field

[0001] This application relates to the field of wearable devices, and in particular to a method, apparatus, device, and storage medium for displaying a user interface. Background Technology

[0002] Wearable devices are portable electronic devices that can be worn directly or integrated into clothing or accessories. Common wearable devices include smartwatches, smart bracelets, smart glasses, and so on.

[0003] Taking smartwatches as an example of wearable devices, users can use them to check the time and use apps installed on the devices to monitor sleep quality, track activity, and view notifications. Summary of the Invention

[0004] This application provides a method, apparatus, device, and storage medium for displaying a user interface. The technical solution is as follows:

[0005] On one hand, embodiments of this application provide a method for displaying a user interface, the method being used in a wearable device, the wearable device supporting the operation of a first system and a second system;

[0006] The method includes:

[0007] When the first system is in a wake-up state and the second system is in a sleep state, the first user interface is displayed through the first system;

[0008] In response to a system switching command, a second user interface is drawn and displayed through the first system, and the second user interface is the user interface of the second system;

[0009] In response to the completion of the second user interface drawing by the second system, the second user interface is displayed through the second system.

[0010] On the other hand, embodiments of this application provide a user interface display device for a wearable device, the wearable device supporting the operation of a first system and a second system;

[0011] The device includes:

[0012] The first system module is used to display a first user interface through the first system when the first system is in a wake-up state and the second system is in a sleep state.

[0013] The first system module is also used to respond to a system switching command by drawing and displaying a second user interface through the first system, wherein the second user interface is the user interface of the second system;

[0014] The second system module is used to display the second user interface in response to the second system completing the drawing of the second user interface.

[0015] On the other hand, embodiments of this application provide a wearable device, the wearable device including a processor and a memory; the memory stores at least one instruction, the at least one instruction being executed by the processor to implement the user interface display method described above.

[0016] On the other hand, embodiments of this application provide a computer-readable storage medium storing at least one instruction, which is executed by a processor to implement the user interface display method as described above.

[0017] On the other hand, embodiments of this application provide a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the user interface display method provided in the above aspects.

[0018] In this embodiment of the application, for a wearable device that supports dual systems, if the first system is in running state and the second system is in dormant state, and a system switching instruction is received, the first system first draws and displays the second user interface, and after the second system completes the drawing of the second user interface, the second user interface is displayed through the second system. By adopting the solution provided in this embodiment of the application, the first system can pre-display the second user interface, which can improve the visual startup speed of system switching and reduce the display delay of the second system displaying the second user interface during system switching. Attached Figure Description

[0019] Figure 1 This is a schematic diagram illustrating a dual-core communication software framework corresponding to a second processor, as shown in an exemplary embodiment of this application;

[0020] Figure 2 This is a schematic diagram illustrating a dual-core communication software framework corresponding to a first processor, as shown in an exemplary embodiment of this application;

[0021] Figure 3 A flowchart illustrating a user interface display method provided in an exemplary embodiment of this application is shown;

[0022] Figure 4 This is a user interface diagram illustrating the system switching process in a smartwatch, as shown in an exemplary embodiment of this application.

[0023] Figure 5 A flowchart illustrating a method for displaying a user interface provided in another exemplary embodiment of this application is shown;

[0024] Figure 6 This is a schematic diagram of a second user interface in a smartwatch, illustrating an exemplary embodiment of this application;

[0025] Figure 7 A flowchart illustrating a user interface resource update process provided in an exemplary embodiment of this application is shown;

[0026] Figure 8 This is a user interface diagram illustrating the system switching process in a smartwatch, as shown in an exemplary embodiment of this application.

[0027] Figure 9 This is a system interaction timing diagram illustrating a user interface resource update process in an exemplary embodiment of this application;

[0028] Figure 10 A structural block diagram of a display device for a user interface provided in another embodiment of this application is shown;

[0029] Figure 11 A structural block diagram of a wearable device provided in an exemplary embodiment of this application is shown. Detailed Implementation

[0030] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0031] In this article, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0032] In related technologies, wearable devices typically incorporate a single processor, which, through an operating system running on that processor, handles all system events generated during device operation. Therefore, this processor needs strong data processing capabilities and must remain operational throughout the device's lifespan. However, in everyday use, wearable devices often only require functions with low processing power demands. For example, smartwatches or smart bracelets mostly only need to display the time and provide notifications. Therefore, keeping the processor constantly active does not improve the performance of wearable devices; instead, it increases power consumption, resulting in shorter battery life.

[0033] In order to reduce the power consumption of wearable devices while ensuring their performance, in one possible implementation, the wearable device is equipped with at least a first processor and a second processor with different processing performance and power consumption, which are used to run the first system and the second system respectively (i.e., dual-core dual system), and a system switching mechanism is designed for the dual-core dual system.

[0034] During the operation of wearable devices, a first system running on a low-power processor handles events requiring low performance while keeping the high-power processor in a sleep state (correspondingly, the second system running on the high-power processor is also in a sleep state). This sleep state reduces the power consumption of the wearable device while fulfilling its basic functions. When there are events requiring high performance (such as when launching an application), the high-power processor is woken up, and the second system is switched to handle the event, ensuring that the triggered events can be responded to and processed in a timely manner, thus meeting the performance requirements of the wearable device.

[0035] Furthermore, since it takes a certain amount of time (at least 200ms to 300ms) for a high-power processor to switch from sleep to wake-up, this application introduces a system switching effect pre-display mechanism to reduce the display latency of the system screen during system switching. When the high-power processor switches to wake-up, the first system running on the low-power processor draws and displays the second user interface; after the high-power processor finishes drawing the second user interface, the second system running on the high-power processor receives the user interface display permission to realize the pre-display of system switching, thereby improving the visual startup speed of system switching and reducing the display latency of the user interface during system switching.

[0036] In this embodiment, the first processor and the second processor operate asynchronously, and the first system and the second system need to achieve system communication (or dual-core communication). In one possible application scenario, the first system is a real-time operating system (RTOS) running on a microcontroller unit (MCU), and the second system is an Android operating system running on a central processing unit (CPU).

[0037] like Figure 1As shown, this application illustrates a dual-core communication software framework for the Android operating system, as illustrated in an exemplary embodiment. This dual-core communication software framework follows the design principles of "low coupling, high reliability, and high reusability," and includes module development for the Kernel, HIDL (Hardware Abstraction Layer Interface Description Language), Native Service, Framework Service, Framework API, and APP (Application) components.

[0038] The APP module includes functional modules such as Launcher, Settings, and SystemUI; the Framework API module includes management modules such as MCUManager, SensorManager, and LocationManager; the Framework Service module includes service modules such as MCUManagerService, SystemSensorManager, and LocationManagerService; the Native Service module includes service modules such as dccservice and Sensorservice; the HIDL module includes modules such as SensorHAL and GPS HAL; and the Kernel module includes DCC Transfer Drivers such as dcc_datah, dcc_data, MCU_sensor, MCU_gps, and MCU_factory.

[0039] As the interface layer connecting the upper and lower layers in the dual-core communication software framework, the transport layer shields the application layer from the transmission details of the lower layer (data link layer) of the system, providing a service channel for application scenarios. The application layer, as the main provider of services, responds to human-computer interaction and transmits the data generated during the human-computer interaction process through the transport layer, as well as responding to external data requests.

[0040] RTOS is designed using the peer-to-peer principle. Taking a wearable device like a smartwatch as an example, such as... Figure 2 As shown, it illustrates a dual-core communication software framework for an RTOS according to an exemplary embodiment of this application.

[0041] The dual-core communication software framework of RTOS is divided into the Application Layer, Service Layer, Framework Layer, Hardware Abstraction Layer, and Platform Layer.

[0042] The application layer includes modules such as watch face, Daily Tracker, Messagecenter, Voice around Apps, Health Apps, and Settings; the service layer includes modules such as Sport & Health task, System manager task, AMS (Activity Management Service), Audio Service, Log Service, OFTP Service (Odette File Transfer Protocol Service), BT Service, Delegate Service, RPC Service, Sensor Service, and Storage Service; the framework layer includes modules such as Message Pub, UIFramework, G2D Engine, Audio Middleware, Preference, and File. The framework modules include system (file system), Algorithms, Aios, and AsycEvent (in-process asynchronous events); the hardware abstraction layer includes hardware abstraction modules such as Screen / TP (screen / touchscreen), Audio, GPS (Global Positioning System), Sensors, Keypad, and Motor; the platform layer includes Board Support Package (BSP) and Low-level Drivers. The BSP includes Screen / TP, Keys, GPS, Codec, Sensors, Flash, Motor, PSRAM (Pseudo-Static Random Access Memory), etc., while the Low-level Drivers include UART (Universal Asynchronous Receiver / Transmitter), ADC (Analog-to-Digital Converter), GPIO (General Purpose Input / Output), SPI (Serial Peripheral Interface), I2C (Integrated Circuit Bus), IOS (Input / Output System), PCM (Pulse Code Modulation), I2S (Integrated Audio Bus), and HWTimer (Hardware Timer).

[0043] It should be noted that the above dual-core communication software framework is for illustrative purposes only. Those skilled in the art can add, delete or modify the framework according to actual needs. The embodiments of this application do not limit the specific structure of the dual-core communication software framework.

[0044] Please refer to Figure 3 The diagram illustrates a flowchart of a user interface display method provided by an exemplary embodiment of this application. This embodiment uses the application of this method to a wearable device, and the wearable device supports running a first system and a second system as an example for illustration. The method may include the following steps.

[0045] Step 301: When the first system is in a wake-up state and the second system is in a sleep state, the first user interface is displayed through the first system.

[0046] In one possible implementation, the wearable device includes a first processor and a second processor, wherein the processing performance of the first processor is lower than that of the second processor (both the processing power and speed of the first processor are lower than those of the second processor), and the power consumption of the first processor is lower than that of the second processor. Accordingly, the second system (run by the second processor) is capable of processing events processed by the first system (run by the first processor), but the first system may not necessarily be capable of processing events processed by the second system.

[0047] In another possible implementation, the wearable device may also be equipped with a single processor, with the first system and the second system running on different cores of the processor, wherein the core running the second system has higher processing performance than the core running the first system.

[0048] For example, taking a wearable device like a smartwatch as an example, the first processor is an MCU, the second processor is a CPU, the first system is an RTOS, and the second system is an Android system. Correspondingly, the events that the first system can handle include scenarios with low processing performance requirements or weak interaction scenarios such as watch face display, watch face interface switching, and notification message display; the events that the second system can handle include scenarios with high processing performance requirements or strong interaction scenarios such as answering calls, launching applications, watch face editing, and function settings.

[0049] In one possible implementation, the wearable device operates in three modes: a performance mode, a hybrid mode, and a low-power mode. In the performance mode, both the second processor and the first processor remain awake (correspondingly, both the first system and the second system are awake). In the low-power mode, only the first processor remains awake (normal operating state), while the second processor remains off (i.e., the first system is awake and the second system is off). In the hybrid mode, when the first system processes events, the second processor remains in a sleep state or a standby state, and can switch between sleep and wake states (i.e., when the first system is awake, the second system can be either awake or sleep).

[0050] Optionally, in the wake-up state, system-related data is cached in memory (RAM) for easy access. In the hibernation state, most of the processor's hardware modules are shut down, and system-related data is stored in the hard disk (ROM), which writes the data to the hard disk when switching to the wake-up state.

[0051] Unlike smartphones, which are electronic devices with strong interactive features, wearable devices, as auxiliary electronic devices, have only weak interactions with users in most usage scenarios. For example, in most situations, users only use smartwatches to raise their wrists to check the time. Therefore, when the wearable device processes events through the first system, it controls the second processor to be in a sleep state (the second system is in a sleep state), thereby reducing the overall power consumption of the wearable device.

[0052] Step 302: In response to the system switching command, the second user interface is drawn and displayed through the first system. The second user interface is the user interface of the second system.

[0053] The system switching command is used to instruct the switching of the system running in the foreground. That is, the system running in the foreground needs to be switched from the first system to the second system, rather than simply switching the second system from the dormant state to the awake state. Correspondingly, the display permission of the graphical user interface of the wearable device will be switched from the first system to the second system.

[0054] In some possible application scenarios, when a user needs to use a function that is not available in the first user interface displayed by the first system, the user needs to switch from the first system to the second system and select the function to be used from the second user interface displayed by the second system.

[0055] When the first system is in a wake-up state (the wearable device's interface is the first user interface displayed by the first system) and the second system is in a sleep state, when a system switching command is received, it indicates that the first system needs to be switched to the second system. Since the first system does not have the function and ability to process the corresponding events, it is necessary to wake up the second system, which is in a sleep state, so that the second system can be processed.

[0056] However, since the wake-up and display process of the second system takes a certain amount of time (at least 200ms to 300ms), a brief period of unresponsiveness occurs during system switching (manifested as a delay between receiving the system switching command and displaying the switching animation; the second system wakes up during this delay and completes the drawing and display of the second user interface), affecting the user experience. In this embodiment, to reduce the display delay of the second user interface during system switching, when a system switching command to switch to the second system is received during the operation of the first system, the second user interface of the second system is first drawn and displayed by the first system (only responsible for drawing the interface image, not executing the specific functions of the second system under the first system; for example, if the second user interface displays an application icon, the first system only displays the application icon and does not have the function of launching the application).

[0057] Optionally, the system switching command can be triggered by a shortcut key (such as a physical button on a wearable device) or by swiping (such as swiping the display interface of a wearable device with one or two fingers). The second user interface can display icons such as fitness icons, instant messaging icons, alarm clock icons, weather icons, and voice assistant icons, and the displayed second user interface can be a static interface or a dynamic interface. This application does not limit the triggering method of the system switching command or the content displayed on the second user interface.

[0058] Since the first system is in a wake-up state, it can immediately draw and display the second user interface after receiving the system switching command, thereby visually improving the system switching speed.

[0059] In one possible implementation, in order to achieve smooth interface switching, after the first system draws the second user interface, it gradually replaces the first user interface by sliding until the second user interface is fully displayed. Optionally, the second user interface can also be displayed by rotation or split display. This application embodiment does not limit the specific display method of the second user interface.

[0060] Indicative, such as Figure 4 As shown, taking a smartwatch as an example of a wearable device, the smartwatch contains an RTOS (run by a first processor) and an Android system (run by a second processor). When the first processor is in a wake-up state and the second processor is in a sleep state, the smartwatch displays the first user interface 41 through the RTOS, while the Android system remains in a sleep state, thus maintaining low power consumption. When the user needs to switch the RTOS to the Android system, they can trigger a system switching command through a swipe operation. Accordingly, after receiving the system switching command, the RTOS draws and displays the second user interface 42 of the Android system.

[0061] Step 303: In response to the completion of the second user interface drawing by the second system, the second user interface is displayed through the second system.

[0062] After the second system completes the rendering of the second user interface, the system running on the wearable device switches from the first system to the second system. The second system then displays the second user interface and executes corresponding functions. For example, when a user needs to use the call function, they can access the communication interface by triggering an instant messaging application on the second user interface. Because the second user interface rendered and displayed by the first and second systems remains consistent, there is no abrupt change in the screen before and after the system switch, making the system switch process difficult to detect.

[0063] Optionally, after switching to the second system, the first system may remain in a wake-up state (low power consumption, with minimal impact on battery life), or the first system may switch to a sleep state. This embodiment does not limit this.

[0064] In one possible implementation, to ensure that the system switches to the second system in a timely manner after the first system draws and fully displays the second user interface, and to avoid the situation where the user clicks the icon and there is no response after the first system has fully displayed the second user interface (at which time the second user interface is drawn and displayed by the first system), the sliding speed of the second user interface is determined based on the time it takes for the second system to wake up and draw the second user interface. This ensures that the second system has already drawn the second user interface when the second user interface drawn by the first user fully occupies the display interface of the wearable device, and the system switch is achieved without the user's awareness.

[0065] Indicative, such as Figure 4 As shown, during the process of the RTOS displaying the second user interface 42, the second user interface 42 is displayed from left to right until the first user interface 41 is completely switched to the second user interface 42. During the process of the second user interface 42 being displayed from left to right, the Android system switches from a sleep state to a wake-up state. When the Android system wakes up and finishes drawing (for example, after 200ms), the system running on the smartwatch switches from the RTOS to the Android system, and the second user interface 43 is displayed through the Android system.

[0066] Optionally, after the second system completes event processing (such as returning to the watch face after a call ends), the second system switches back to sleep mode and continues to process events through the first system. This allows the wearable device to maintain high performance (but high power consumption) in a few scenarios, while maintaining low power consumption (but low performance) in most scenarios, further reducing the power consumption of the wearable device and extending its battery life.

[0067] In summary, in the embodiments of this application, for wearable devices that support dual systems, if the first system is in running state while the second system is in dormant state, and a system switching command is received, the first system first draws and displays the second user interface, and after the second system completes the drawing of the second user interface, the second user interface is displayed through the second system. By adopting the solution provided in the embodiments of this application, the first system can pre-display the second user interface, which can improve the visual startup speed of system switching and reduce the display delay of the second system displaying the second user interface during system switching.

[0068] In one possible implementation, the first system and the second system each have their own data storage space. Since the first system only handles simple events, while the second system handles complex events, the storage space for the second system is much larger than that for the first system. To enable the first system to draw and display the second user interface, the storage space for the first system stores the user interface resources corresponding to the second user interface. Upon receiving a system switching command, the first system draws the user interface based on the user interface resources in its storage space. An exemplary embodiment will be used for illustration below.

[0069] Please refer to Figure 5 The diagram illustrates a flowchart of a user interface display method provided by another exemplary embodiment of this application. This embodiment uses the application of this method to a wearable device as an example for illustration. The method may include the following steps.

[0070] Step 501: When the first system is in a wake-up state and the second system is in a sleep state, in response to the system switching command, the user interface resources corresponding to the second user interface are obtained from the first storage space through the first system. The first storage space is the storage space corresponding to the first system.

[0071] In this embodiment, the first system corresponds to a first storage space, which stores at least one user interface resource corresponding to a user interface. The user interface resource refers to the resources required to draw the user interface. The user interface resource may include text resources, image resources, animation resources, special effects resources, interface layout resources, etc. This embodiment does not limit the specific content included in the interface resources.

[0072] In one possible implementation, the first storage space stores user interface resources corresponding to the first user interface of the first system, and user interface resources corresponding to the second user interface of the second system. For example, when the first user interface is a watch face, the first storage space stores watch face resources. When a sports and health application, an alarm clock application, and an instant messaging application are installed in the second system, the corresponding sports and health icon, alarm clock application icon, and instant messaging icon are displayed on the second user interface. Accordingly, the first storage space stores icon resources corresponding to each application icon. Optionally, the second user interface may also display desktop widgets and voice assistants, and the corresponding user interface resources are also stored in the first storage space.

[0073] In some embodiments, the first system searches for the interface element resource corresponding to the interface element to be drawn from the first storage space.

[0074] In an illustrative example, the mapping relationship between interface elements and interface element resources in the first storage space is shown in Table 1.

[0075] Table 1

[0076]

[0077]

[0078] As shown in Table 1, when the second user interface displays an icon for an instant messaging application, the first system retrieves the interface element resource A corresponding to the interface element "instant messaging icon" from the first storage space.

[0079] Step 502: In response to the presence of variable interface elements in the interface elements, determine the target interface element resource corresponding to the variable interface element based on the current time. The variable interface element corresponds to at least two types of interface element resources, and different interface element resources correspond to different display time periods.

[0080] When obtaining interface element resources based on interface elements, in addition to identifying the fixed interface elements (such as the icons of alarm clock applications and instant messaging applications are fixed interface elements), it is also necessary to identify the variable interface elements (such as time display widgets and greetings are variable interface elements).

[0081] The appearance of variable interface elements may differ at different times, meaning that a variable interface element may correspond to multiple interface element resources. Therefore, when drawing variable interface elements, the first system also needs to utilize other data, such as time data, sensor data (e.g., pedometer data), etc., to ensure the accuracy and consistency of the interface elements in the drawn second user interface, and to avoid differences between the interface elements drawn by the first system and the second system, and the problem of sudden changes in the user interface when switching systems.

[0082] In one possible implementation, when the interface elements to be drawn include variable interface elements, the first system determines the target interface element resource from at least two types of interface element resources corresponding to the variable interface elements based on the current time. The different interface element resources correspond to different display time periods, and the display time period to which the current time belongs is the display time period corresponding to the target interface element resource.

[0083] For example, the variable interface element can be a greeting. The interface element corresponding to the time period from 0:00 to 12:00 is "Good morning", the interface element corresponding to the time period from 12:00 to 17:00 is "Good afternoon", and the interface element corresponding to the time period from 17:00 to 24:00 is "Good evening".

[0084] For illustrative purposes, when the second user interface to be drawn contains a greeting (the greeting is displayed as "Good morning," "Good afternoon," and "Good evening" depending on the time period), if the current time is 10:00, the first system will determine the interface element resource "Good morning" corresponding to the time period to which the current time belongs as the target greeting.

[0085] Step 503: Draw variable interface elements based on the target interface element resources.

[0086] Furthermore, after obtaining the corresponding interface resources, the first system draws the corresponding interface elements based on the determined target interface resources.

[0087] In an exemplary example, the first system obtains the interface resources, which include the image resources corresponding to the application icon and the text resources corresponding to the greeting. It then renders the application icon based on the image resources and the greeting based on the text resources.

[0088] Step 504: Display the interface elements at the positions indicated by the display position information to obtain the second user interface.

[0089] The first system determines the arrangement and layout of each interface element in the second user interface based on the position information of the interface elements contained in the user interface resources, and then displays the second user interface.

[0090] In one possible implementation, such as Figure 6As shown, the second user interface 600 displays a voice assistant 610 at the top, which displays a greeting 611. The greeting 611 displays different text messages depending on the current time period. The second user interface 600 also displays application icons such as an instant messaging icon 620, an alarm clock icon 630, and a fitness and health icon 640 at the bottom. It should be noted that the second user interface 600 is drawn and displayed by the first system at this time, and the displayed interface elements do not yet have corresponding functions.

[0091] Step 505: Based on the sliding direction of the sliding operation, the first system displays a switching animation from the first user interface to the second user interface.

[0092] After the first system draws the second user interface, it switches the first user interface to the second user interface based on the sliding direction of the sliding operation. The sliding direction of the sliding operation is set by the user in the second system, such as using switching animations like left and right switching, flying in, and splitting.

[0093] Indicative, such as Figure 4 As shown, the second user interface 402 drawn by the first system switches between left and right sides. It should be noted that this embodiment does not limit the switching animation of the user interface.

[0094] Step 506: In response to the completion of the second user interface drawing by the second system and the end of the swiping operation, the second user interface is displayed through the second system.

[0095] When the second user interface finishes sliding, the user interface switches from the first user interface to the second user interface. At this time, the second system is activated and draws all the interface elements contained in the second user interface. The first system is switched to the second system, and the second user interface is displayed through the second system. Since the interface elements contained in the second user interface before and after the system switch are the same, the system switch is achieved without the user's awareness.

[0096] To ensure that the second system controls the wearable device's interface display after the system switch is completed, once the second system has finished drawing the second user interface, it obtains control over the interface display by sending a switching command to the first system. After obtaining control, the second system will control the wearable device's display interface, and the first system can enter a sleep state or a shutdown state.

[0097] Optionally, in response to the second system completing the rendering of the second user interface, the wearable device sends a permission switching instruction to the first system through the second system. The permission switching instruction is used to instruct the first system to transfer the display permission of the graphical user interface (GUI).

[0098] To ensure the proper functioning of the second user interface, during system switching, the first system needs to transfer the display permission of the graphical user interface to the second system. This allows the second system to display its graphical user interface to the wearable device during normal operation. In one possible implementation, after the second system completes drawing the second user interface, it sends a permission switching command to the first system, instructing the first system to transfer the display permission of the graphical user interface to the second system.

[0099] In response to the second system obtaining permission to display the graphical user interface, the wearable device displays the second user interface through the second system.

[0100] After the second system obtains the permission to display the graphical user interface, the wearable device will switch from the first system to the second system and display the second user interface through the second system. In the second user interface displayed by the second system, the displayed interface elements have corresponding functions, such as entering the communication interface by clicking the instant messaging icon.

[0101] In this embodiment, by storing the user interface resources corresponding to the second user interface in the first storage space, the first system can accurately obtain the corresponding target interface element resources from the first storage space based on the variable and fixed interface elements contained in the second user interface after receiving the system switching command. Furthermore, the interface elements are displayed in the second user interface based on the display position information, which helps to improve the drawing speed and display accuracy of the second user interface.

[0102] Furthermore, by pre-displaying the second user interface in the first system, the startup speed of the visual system switching can be improved, and the display delay of the second user interface displayed in the second system during the system switching process can be reduced.

[0103] In addition, after the second system completes the drawing of the second user interface, it obtains the permission to display the graphical user interface by sending a permission switching command to the first system, ensuring that the second system displays the graphical user interface to the wearable device during normal operation.

[0104] In the above embodiments, since the second user interface of the second system in the wearable device is not static (e.g., the order of interface elements in the second user interface is adjusted, or interface elements displayed in the second user interface are added or deleted), the user interface resources stored in the first storage space also need to be updated accordingly to ensure the accuracy of the second user interface display after switching systems. In one possible implementation, when the second system is in a wake-up state or restarted, the second system automatically sends interface resource update data to the first system (when an interface resource update event exists). The first system then updates the user interface resources stored in the first storage space based on the interface resource update data. This user interface resource update data includes at least the interface element resources corresponding to the interface elements to be updated.

[0105] Please refer to Figure 7 The diagram illustrates a flowchart of a user interface resource update process provided in an exemplary embodiment of this application, which may include the following steps.

[0106] Step 701: When the second system is in the wake-up state, send interface resource update data to the first system through the second system. The interface resource update data adopts the data format agreed upon by the first system and the second system.

[0107] In one possible implementation, when the second system is in a wake-up state and detects an interface resource change event, it sends interface resource update data to the first system via the data link connecting the first and second systems. The interface resource change event includes at least one of interface element addition / deletion events, interface element position adjustment events, and system setting change events. System setting change events include system language changes, system font changes, system font size changes, system style changes, etc., which are not limited in this embodiment.

[0108] In another possible implementation, after each restart of the second system, it is necessary to send interface resource update data to the first system to ensure the consistency of the interface resources corresponding to the second user interface in the first system and the second system.

[0109] Optionally, when the second system determines that a UI resource change event has occurred, it encodes the UI resource update data corresponding to the second user interface into a byte stream according to the agreed protocol, and packages the byte stream and sends it to the first system through the data link. The UI resource update data adopts the data format agreed upon by the first system and the second system.

[0110] In an exemplary example, the format in which the second system sends data to the first system is as follows.

[0111]

[0112]

[0113] When the first system receives the data packet sent by the second system, it decodes the data packet according to the protocol agreed upon with the second system and obtains the user interface resources corresponding to the updated second user interface.

[0114] Step 702: Update the user interface resources stored in the first storage space through the first system based on the interface resource update data.

[0115] Upon receiving the updated interface resource data, the first system associates and stores the updated interface elements with the updated interface element resources. During subsequent system switching, the first system can draw and display the second user interface based on the updated interface element resources, ensuring that the displayed second user interface is consistent with the user interface of the second system.

[0116] Based on the examples of the above steps, after the first system updates the interface element resources based on the received data packets, the mapping relationship between interface elements and interface element resources in the first storage space is shown in Table 2.

[0117] Table 2

[0118] Interface elements UI element resources Instant Messaging Icon Interface element resource A' alarm clock icon Interface element resource B' Weather icon Interface element resources C Sports and Health Icons Interface element resource D

[0119] As shown in Table 2, based on the examples in the above steps, the interface element resources A and B corresponding to the instant messaging icon and the alarm clock icon are updated. The first system obtains the updated interface element resources A' and B' based on the received interface resource update data.

[0120] Taking language updates as an example, when the display language of the second user interface is updated from Chinese to English, the Chinese text information in the interface element resources is updated to English text information.

[0121] Indicative, such as Figure 8 As shown, when the RTOS is in working state, it displays the first user interface 81. When a system switch is required, the system switch is performed by sliding. The first system draws and displays the second user interface 82 based on the updated user interface resources. The interface elements displayed in the second user interface 82 are updated from Chinese to English.

[0122] Optionally, after completing the user interface resource update, the first system sends an update completion notification to the second system, informing the second system that the update of the user interface resources has been completed. If the second system does not receive the update completion notification within a preset time period, it resends the update data packet to the first system.

[0123] In another possible implementation, the data packet updated by the second system to the first system contains the interface element resources corresponding to all interface elements in the second user interface. Accordingly, when the system language of the wearable device changes, most of the user interface resources stored in the first storage space may become invalid. Therefore, in order to free up the first storage space and ensure the accuracy of subsequent user interface resource updates, when the first system receives the update data packet, the first system will delete the user interface resources in the first storage space and directly decode the received update data packet to obtain the user interface resources corresponding to the updated second user interface packet.

[0124] Indicative, such as Figure 9 As shown, taking the first system as RTOS and the second system as Android as an example, when the second user interface changes, a system settings change event is confirmed. The Android system then sends an update data packet to the RTOS. The update data packet contains the user interface resources corresponding to the updated second user interface. When the RTOS receives the data packet, it determines that the second user interface has changed, and deletes the user interface resources contained in the first storage space. It then decodes the received data packet, obtains the updated user interface resources, and stores them in the first storage space. Optionally, after the RTOS completes the update, it sends an update completion notification to the Android system.

[0125] In this embodiment, when the user interface resources are updated, the second system confirms the interface resource change event and sends the updated user interface resources to the first system. The first system then updates the user interface resources stored in the first storage space to ensure that the second user interface displayed by the first system is consistent with the second user interface displayed by the second system when the system is switched in the future, thus achieving seamless switching.

[0126] It should be noted that the above embodiments only illustrate the display process of the user interface under a dual-core dual-system device. In other possible application scenarios, single-core dual-system devices (such as different systems running on different cores of the processor) can also use the solution provided in the embodiments of this application to realize the display of the user interface during system switching. This embodiment will not elaborate on this.

[0127] Please refer to Figure 10 This diagram illustrates a structural block diagram of a user interface display device according to an embodiment of this application. The device can be implemented as all or part of a wearable device through software, hardware, or a combination of both. The device includes:

[0128] The first system module 1001 is used to display a first user interface through the first system when the first system is in a wake-up state and the second system is in a sleep state.

[0129] The first system module 1001 is also used to respond to a system switching command by drawing and displaying a second user interface through the first system, wherein the second user interface is the user interface of the second system;

[0130] The second system module 1002 is used to display the second user interface through the second system in response to the second system completing the drawing of the second user interface.

[0131] Optionally, the first system module 1001 is specifically used for:

[0132] In response to the system switching command, the user interface resources corresponding to the second user interface are obtained from the first storage space through the first system, where the first storage space is the storage space corresponding to the first system.

[0133] Based on the user interface resources, the second user interface is drawn using the first system;

[0134] The second user interface is displayed through the first system.

[0135] Optionally, the first system module 1001 is specifically used for: the user interface resource includes interface element resources corresponding to the interface elements and display position information;

[0136] Optionally, the first system module 1001 is specifically used for:

[0137] The interface elements are drawn based on the interface element resources;

[0138] The interface elements are displayed at the positions indicated by the display position information to obtain the second user interface.

[0139] Optionally, the first system module 1001 is specifically used for:

[0140] In response to the inclusion of a variable interface element in the interface elements, a target interface element resource corresponding to the variable interface element is determined based on the current time. The variable interface element corresponds to at least two types of interface element resources, and different interface element resources correspond to different display time periods.

[0141] The variable interface element is drawn based on the target interface element resource.

[0142] Optionally, the first system module 1001 is specifically used for: triggering the system switching command through a sliding operation;

[0143] Optionally, the first system module 1001 is specifically used for:

[0144] Based on the sliding direction of the sliding operation, the first system displays the switching animation from the first user interface to the second user interface;

[0145] Optionally, the second system module 1002 is further configured to:

[0146] In response to the second system completing the drawing of the second user interface and the end of the swiping operation, the second user interface is displayed through the second system.

[0147] Optionally, the second system module 1002 is further configured to:

[0148] When the second system is in a wake-up state, interface resource update data is sent from the second system to the first system, and the interface resource update data adopts a data format agreed upon by the first system and the second system; or,

[0149] After the second system restarts, it sends interface resource update data to the first system.

[0150] Based on the interface resource update data, the user interface resources stored in the first storage space are updated through the first system.

[0151] Optionally, the second system module 1002 is further used for:

[0152] When the second system is in a wake-up state, in response to an interface resource change event, the second system sends the interface resource update data to the first system. The interface resource change event includes at least one of interface element addition / deletion events, interface element position adjustment events, and system setting change events.

[0153] Optionally, the second system module 1002 is further used for:

[0154] The second system sends a permission switching instruction to the first system, the permission switching instruction being used to instruct the first system to transfer the display permission of the graphical user interface;

[0155] In response to the second system obtaining permission to display the graphical user interface, the second user interface is displayed through the second system.

[0156] Optionally, the wearable device is provided with a first processor and a second processor, wherein the power consumption of the second processor is higher than that of the first processor, and the first system is a system run by the first processor, and the second system is a system run by the second processor.

[0157] In summary, in the embodiments of this application, for wearable devices that support dual systems, if the first system is in running state while the second system is in dormant state, and a system switching command is received, the first system first draws and displays the second user interface, and after the second system completes the drawing of the second user interface, the second user interface is displayed through the second system. By adopting the solution provided in the embodiments of this application, the first system can pre-display the second user interface, which can improve the visual startup speed of system switching and reduce the display delay of the second system displaying the second user interface during system switching.

[0158] In this embodiment, by storing the user interface resources corresponding to the second user interface in the first storage space, the first system can accurately obtain the corresponding target interface element resources from the first storage space based on the variable and fixed interface elements contained in the second user interface after receiving the system switching command. Furthermore, the interface elements are displayed in the second user interface based on the display position information, which helps to improve the drawing speed and display accuracy of the second user interface.

[0159] Furthermore, by pre-displaying the second user interface in the first system, the startup speed of the visual system switching can be improved, and the display delay of the second user interface displayed in the second system during the system switching process can be reduced.

[0160] In addition, after the second system completes the drawing of the second user interface, it obtains the permission to display the graphical user interface by sending a permission switching command to the first system, ensuring that the second system displays the graphical user interface to the wearable device during normal operation.

[0161] In this embodiment, when the user interface resources are updated, the second system confirms the interface resource change event and sends the updated user interface resources to the first system. The first system then updates the user interface resources stored in the first storage space to ensure that the second user interface displayed by the first system is consistent with the second user interface displayed by the second system when the system is switched in the future, thus achieving seamless switching.

[0162] Please refer to Figure 11 The diagram illustrates a structural block diagram of a wearable device provided in an exemplary embodiment of this application. The wearable device in this application may include one or more components such as a processor 1110 and a memory 1120.

[0163] Processor 1110 includes at least a first processor 1111 and a second processor 1112, wherein the first processor 1111 is used to run a first system, and the second processor 1112 is used to run a second system. The power consumption of the first processor 1111 is lower than that of the second processor 1112, and the performance of the first processor 1111 is lower than that of the second processor 1112. Processor 1110 connects various parts within the electronic device using various interfaces and lines. It performs various functions of the electronic device and processes data by running or executing instructions, programs, code sets, or instruction sets stored in memory 1120, and by calling data stored in memory 1120. Optionally, processor 1110 can be implemented using at least one hardware form selected from Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). Processor 1111 can integrate one or more of the following: a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a Neural-network Processing Unit (NPU), and a modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the content displayed on the touchscreen; the NPU implements Artificial Intelligence (AI) functions; and the modem handles wireless communication. It is understood that the modem can also be implemented as a separate chip without being integrated into processor 1110.

[0164] The memory 1120 may include random access memory (RAM) or read-only memory (ROM). Optionally, the memory 1120 may include a non-transitory computer-readable storage medium. The memory 1120 may be used to store instructions, programs, code, code sets, or instruction sets. The memory 1120 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the various method embodiments described below, etc.; the data storage area may store data created based on the use of the wearable device (such as audio data, phonebook, etc.).

[0165] The wearable device in this embodiment further includes a communication component 1130 and a display component 1140. The communication component 1130 can be a Bluetooth component, a WiFi component, an NFC component, etc., used to communicate with external devices (servers or other terminal devices) via wired or wireless networks; the display component 1140 is used to display a graphical user interface and / or receive user interaction operations.

[0166] In addition, those skilled in the art will understand that the structure of the wearable device shown in the above figures does not constitute a limitation on the wearable device. The wearable device may include more or fewer components than shown, or combine certain components, or have different component arrangements. For example, the wearable device may also include radio frequency circuits, input units, sensors, audio circuits, speakers, microphones, power supplies, etc., which will not be described in detail here.

[0167] This application also provides a computer-readable storage medium storing at least one instruction, which is executed by a processor to implement the user interface display method as described in the above embodiments.

[0168] This application provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the user interface display method provided in the above embodiments.

[0169] Those skilled in the art will recognize that the functions described in the embodiments of this application in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0170] The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A display method of a user interface, characterized by, The method is used in a wearable device that supports running a first system and a second system; The method includes: When the first system is in a wake-up state and the second system is in a sleep state, the first user interface is displayed through the first system; In response to a system switching command, the user interface resources corresponding to the second user interface are obtained from the first storage space through the first system. The second user interface is the user interface of the second system, and the first storage space is the storage space corresponding to the first system. The user interface resources corresponding to the second user interface in the first storage space are consistent with the user interface resources in the storage space corresponding to the second system. The user interface resources include the interface element resources corresponding to the interface elements in the second user interface and the display position information. The display position information is used to characterize the arrangement and layout of the interface elements in the second user interface. Based on the user interface resources, the second user interface is drawn using the first system; The second user interface is displayed through the first system; In response to the completion of the second user interface by the second system, the second user interface is displayed through the second system, and the second user interface drawn by the second system is consistent with the second user interface drawn by the first system.

2. The method according to claim 1, characterized in that, The step of drawing the second user interface through the first system based on the user interface resources includes: The interface elements are drawn based on the interface element resources; The interface elements are displayed at the positions indicated by the display position information to obtain the second user interface.

3. The method according to claim 2, characterized in that, The step of drawing the interface elements based on the interface element resources includes: In response to the inclusion of a variable interface element in the interface elements, a target interface element resource corresponding to the variable interface element is determined based on the current time. The variable interface element corresponds to at least two types of interface element resources, and different interface element resources correspond to different display time periods. The variable interface element is drawn based on the target interface element resource.

4. The method according to claim 1, characterized in that, The system switching command is triggered by a sliding operation; The step of displaying the second user interface through the first system includes: Based on the sliding direction of the sliding operation, the first system displays a switching animation from the first user interface to the second user interface; The step of responding to the second system completing the rendering of the second user interface and displaying the second user interface through the second system includes: In response to the second system completing the drawing of the second user interface and the end of the swiping operation, the second user interface is displayed through the second system.

5. The method according to claim 1, characterized in that, The method further includes: When the second system is in a wake-up state, interface resource update data is sent from the second system to the first system, and the interface resource update data adopts a data format agreed upon by the first system and the second system; or, After the second system restarts, it sends interface resource update data to the first system. Based on the interface resource update data, the user interface resources stored in the first storage space are updated through the first system.

6. The method according to claim 5, characterized in that, When the second system is in a wake-up state, sending interface resource update data to the first system through the second system includes: When the second system is in a wake-up state, in response to an interface resource change event, the second system sends the interface resource update data to the first system. The interface resource change event includes at least one of interface element addition / deletion events, interface element position adjustment events, and system setting change events.

7. The method according to any one of claims 1 to 6, characterized in that, The step of displaying the second user interface through the second system includes: The second system sends a permission switching instruction to the first system, the permission switching instruction being used to instruct the first system to transfer the display permission of the graphical user interface; In response to the second system obtaining permission to display the graphical user interface, the second user interface is displayed through the second system.

8. The method according to any one of claims 1 to 6, characterized in that, The wearable device is equipped with a first processor and a second processor, the power consumption of the second processor is higher than that of the first processor, and the first system is a system run by the first processor, while the second system is a system run by the second processor.

9. A display device for a user interface, characterized in that, The device is used in a wearable device that supports the operation of a first system and a second system; The device includes: The first system module is used to display a first user interface through the first system when the first system is in a wake-up state and the second system is in a sleep state. The first system module is further configured to respond to a system switching command by obtaining user interface resources corresponding to the second user interface from the first storage space through the first system. The second user interface is the user interface of the second system, and the first storage space is the storage space corresponding to the first system. The user interface resources corresponding to the second user interface in the first storage space are consistent with the user interface resources in the storage space corresponding to the second system. The user interface resources include interface element resources corresponding to the interface elements in the second user interface and display position information. The display position information is used to characterize the arrangement and layout of the interface elements in the second user interface. Based on the user interface resources, the second user interface is drawn using the first system; The second user interface is displayed through the first system; The second system module is used to display the second user interface in response to the second system completing the drawing of the second user interface, wherein the second user interface drawn by the second system is consistent with the second user interface drawn by the first system.

10. A wearable device, characterized in that, The wearable device includes a processor and a memory; the memory stores at least one instruction, which is executed by the processor to implement the display method of the user interface as described in any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that, The storage medium stores at least one instruction, which is executed by a processor to implement the display method of the user interface as described in any one of claims 1 to 8.

Images