Method of displaying application interface, apparatus, device and storage medium

Abstract

To provide a method of displaying an application interface that allows for visually improving a startup speed of an application on a wearable device.SOLUTION: A method includes: rendering and displaying an interface of a target application by a first system in response to an application-startup instruction for the target application if the first system is in a wakeup state and a second system is in a sleep state (301); rendering an interface of the target application by the second system in response to a switchover of the second system from the sleep state to a wakeup state (302); and displaying an interface of the target application and executing the target application by the second system in response to a completion of rendering the interface of the target application by the second system (303).SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] Reference to Related Applications This application claims the priority of Chinese Patent Application No. 202110366882.3, filed on April 6, 2021, with the invention title of "Method, Device, Device, and Storage Medium for Displaying Application Interface", and all its contents are incorporated herein by reference.

[0002] Embodiments of this application relate to the field of wearable devices, and in particular to a method, device, device, and storage medium for displaying an application interface.

Background Art

[0003] A wearable device is a portable electronic device that can be directly worn or integrated into clothing or accessories. Common wearable devices include smart watches, smart bracelets, smart glasses, etc.

[0004] Taking the example that the wearable device is a smart watch, the user can use the wearable device to check the time, and use the application programs installed on the wearable device to realize functions such as sleep quality monitoring, exercise statistics, and checking notifications and messages.

Summary of the Invention

[0005] In embodiments of this application, a method, device, device, and storage medium for displaying an application interface are provided. The technical solution is as follows.

[0006] In one aspect, in embodiments of this application, a method for displaying an application interface is provided. The method is used for a wearable device that supports the execution of a first system and a second system. The method includes When the first system is in the wake-up state and the second system is in the sleep state, the first system draws and displays the interface of the target application, after the second system is switched from the sleep state to the wake-up state, the second system draws the interface of the target application, in response to the completion of the drawing of the interface of the target application by the second system, the second system displays the interface of the target application and executes the target application.

[0007] In another aspect, in the embodiments of the present application, an application interface display device is provided. The device is used in a wearable device that supports the execution of the first system and the second system. The device includes a first system module and a second system module. The first system module is configured to draw and display the interface of the target application by the first system when the first system is in the wake-up state and the second system is in the sleep state, The second system module is configured to draw the interface of the target application by the second system after the second system is switched from the sleep state to the wake-up state, The second system module is further configured to display the interface of the target application and execute the target application by the second system in response to the completion of the drawing of the interface of the target application by the second system.

[0008] In another aspect, in an embodiment of the present application, a wearable device is provided. The wearable device includes a processor and a memory. At least one instruction is stored in the memory, and when the at least one instruction is executed by the processor, it is used to implement the method for displaying the application interface described in the above aspect.

[0009] In another aspect, in an embodiment of the present application, a computer-readable storage medium is provided. At least one instruction is stored in the readable storage medium, and when the at least one instruction is executed by a processor, it is used to implement the method for displaying the application interface described in the above aspect.

[0010] In another aspect, in an embodiment of the present application, a computer program product or a computer program is provided. The computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and by executing the computer instructions, causes the computer device to execute the method for displaying the application interface according to the above aspect.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

DETAILED DESCRIPTION OF THE INVENTION

[0012] To make the objectives, technical solutions, and advantages of the present application more clear, the embodiments of the present application will be described in further detail below with reference to the drawings.

[0013] As used herein, "a plurality of" means two or more. The term "and / or" describes the relationship of the related objects and indicates that there are three types of relationships. For example, in the case of A and / or B, it indicates three situations: only A exists, both A and B exist simultaneously, and only B exists. Also, the symbol " / " generally indicates that the related objects before and after are in an "or" relationship.

[0014] In the related art, a single processor is installed in a wearable device, and by executing the operating system in the processor, all system events that occur during the operation of the device are processed. Therefore, the processor has high data processing capabilities and needs to maintain its operating state during the operation of the device. However, during daily use, in many cases, the wearable device only needs to implement functions with low requirements for processing performance. For example, in many cases, a smartwatch or a smart bracelet only needs to display the time and prompt messages. Therefore, the processor maintaining its operating state for a long time increases the power consumption of the wearable device without improving its performance, shortening the continuous usage time of the wearable device.

[0015] In order to ensure the performance of the wearable device and reduce its power consumption, in one possible embodiment, at least a first processor and a second processor with different processing performance and power consumption are installed in the wearable device. The first processor executes a first system, the second processor executes a second system (i.e., a dual-core dual-system), and a system switching mechanism is designed for the dual-core dual-system.

[0016] During the operation of the wearable device, by executing the first system with a processor having low power consumption, events with low requirements for processing performance are processed, and a processor with high power consumption is maintained in a sleep state (accordingly, the second system executed by the processor with high power consumption is in a sleep state). While realizing the basic functions of the wearable device, the power consumption of the wearable device can be reduced. When an event with high requirements for processing performance occurs (for example, when an application program is started), the processor with high power consumption is woken up and switched to the second system to process the event, ensuring that the triggered event is responded to and processed in real time and meeting the performance requirements of the wearable device.

[0017] In addition, it takes a certain amount of time (at least 200 ms to 300 ms) for the processor with high power consumption to switch from the sleep state to the wake-up state. Therefore, in order to reduce the display delay of the application screen during application startup, in this application, a mechanism for pre-displaying the start-up effect is introduced. Before the processor with high power consumption is woken up, the first system executed by the processor with low power consumption draws and displays the application interface. After the processor with high power consumption is woken up, the second system executed by the processor with high power consumption displays the application interface, executes the application, and pre-displays the application startup effect. Thereby, the startup speed of the application is visually improved, and the display delay of the application screen during system switching is reduced.

[0018] In an embodiment of the present application, the first processor and the second processor operate asynchronously, and the first system and the second system need to implement system communication (also referred to as dual-core communication). In one possible application scenario, the first system is a real-time operating system (RTOS) executed by a microcontroller unit (MCU), and the second system is an Android operating system executed by a central processing unit (CPU).

[0019] As shown in FIG. 1, a dual-core communication software framework of an Android operating system according to an exemplary embodiment of the present application is shown. The dual-core communication software framework follows the design principles of "low coupling, high reliability, and high multiplexing", and includes the development of a kernel module, a hardware abstraction layer interface definition language (HIDL) module, a native service module, a framework service module, a framework application programming interface (FrameworkAPI) module, and an application (APP) module.

[0020] The APP module includes functional modules such as the desktop launcher, settings, and system user interface (SystemUI). The FrameworkAPI module includes management modules such as the microcontroller unit management (MCU Manager), sensor management (Sensor Manager), and location management (Location Manager). The framework service module includes service modules such as the MCU management service (MCU Manager Service), system sensor management (System Sensor Manager), and location management service (Location Manager Service). The native service module includes service modules such as the data call control service (data call control (dcc) service) and sensor service (Sensor service). The HIDL module includes modules such as the sensor hardware abstraction layer (Sensor HAL) and global positioning system hardware abstraction layer (global positioning system (GPS) HAL). The kernel module includes DCC transfer drivers such as dcc_datah, dcc_data, Mcu_sensor, Mcu_gps, and Mcu_factory.

[0021] In the dual-core communication software framework, the transport layer serves as an interface layer connecting the upper and lower layers, shielding the transmission details of communication in the lower layer (data link layer) of the system from the application layer and providing a service channel for the application scenario. The application layer, as the provider of services, responds to the interaction between humans and the man-machine, transmits the data generated during the interaction between humans and the man-machine through the transport layer, and responds to external data requests.

[0022] The RTOS is designed using the peer - to - peer principle. Taking the example that the wearable device is a smart watch, as shown in FIG. 2, a dual - core communication software framework of the RTOS according to one exemplary embodiment of the present application is shown.

[0023] The dual - core communication software framework of the RTOS is divided into an Application Layer, a Service Layer, a Framework Layer, a Hardware Abstraction Layer (HAL), and a Platform Layer.

[0024] The application layer includes application modules such as watch face, Daily Tracker, Message center, Voice around Apps, Health Apps, Settings, etc. The service layer includes service modules such as Sport&health task, System manager task, Activity Manager Service (AMS), Audio Service, Log Service, Odette File Transfer Protocol (OFTP) Service, Bluetooth (BT) Service, Delegate Service, Remote Procedure Call (RPC) Service, sensor Service, storage Service, etc. The framework layer includes framework modules such as Message Pub, User Interface Framework (UI Framework), graphics 2D (G2D) Engine, Audio Middleware, Preference, File system, Algorithms, advanced input output system (Aios), AsycEvent, etc. It includes hardware abstraction modules such as HAL, Screen / touch panel (TP), Audio, Global Positioning System (GPS), sensors, Keypad, Motor, etc.The platform layer includes a Board Support Package (BSP) and LOW level drivers. The BSP includes a screen / touch panel, keys, GPS, codec, sensors, Flash, motors, Pseudo static random access memory (PSRAM), etc. The LOW level drivers include a Universal Asynchronous Receiver / Transmitter (Uart), an analog-to-digital converter (ADC), general Purpose Input Output (GPIO), a Serial Peripheral Interface (SPI), an Inter-Integrated Circuit (I2C), an Input Output System (IOS), Pulse Code Modulation (PCM), Inter-IC SoundI2S, and a hardware timer (HWTimer).

[0025] Note that the above dual-core communication software framework is described only as an example. Those skilled in the art can also add, delete, or correct the above framework according to actual needs, and the specific structure of the dual-core communication software framework is not limited in the embodiments of this application.

[0026] Referring to Figure 3, Figure 3 is a flowchart showing a display method of an application interface according to an exemplary embodiment of the present application. In this embodiment, the method is described by taking as an example its application to a wearable device that supports the execution of a first system and a second system. The method can include the following steps.

[0027] Step 301: When the first system is in the wake-up state and the second system is in the sleep state, in response to the application start instruction of the target application, the first system draws and displays the interface of the target application.

[0028] In one possible embodiment, the wearable device includes a first processor and a second processor. The processing performance of the first processor is lower than that of the second processor (both the processing capacity and processing speed of the first processor are lower than those of the second processor), and the power consumption of the first processor is smaller than that of the second processor. Accordingly, the second system (executed by the second processor) can process the events processed by the first system (executed by the first processor), but the first system cannot necessarily process the events processed by the second system.

[0029] In another possible embodiment, the wearable device can also include a single processor. The first system and the second system are respectively executed on different cores of the processor. The processing performance of the core executing the second system is higher than that of the core executing the first system.

[0030] For example, taking the wearable device as a smart watch, 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. Accordingly, the events that can be processed by the first system include scenarios with low requirements for processing performance or weak interactions, such as watch face display, watch face interface switching, and display of notifications and messages. The events that can be processed by the second system include scenarios with high requirements for processing performance or strong interactions, such as incoming calls, application startup, watch face editing, and function settings.

[0031] In one possible embodiment, the operating modes of the wearable device include a performance mode, a hybrid mode, and a low power consumption mode. In the performance mode, both the second processor and the first processor maintain a wake-up state (accordingly, both the first system and the second system are in a wake-up state). In the low power consumption mode, only the first processor maintains a wake-up state, and the second processor is in an off state (i.e., the first system is in a wake-up state, and the second system is in an off state). In the hybrid mode, when the first system processes an event, the second processor is in a standby state and can be switched between a sleep state and a wake-up state (i.e., when the first system is in a wake-up state, the second system may be in a wake-up state or a sleep state).

[0032] Optionally, in the wake-up state, system-related data is cached in a memory such as a random access memory (RAM) that can be executed at any time. In the sleep state, most of the hardware modules of the processor are turned off, and system-related data is stored in a hard disk such as a read-only memory (ROM). When switching from the sleep state to the wake-up state, system-related data is written from the hard disk to the memory.

[0033] Unlike electronic devices with strong interaction attributes such as smartphones, as an auxiliary electronic device, in most usage scenarios, the wearable device has only a weak interaction with the user. For example, in most scenarios, the user raises the arm to check the time or message prompt by the smartwatch. Therefore, when the first system processes an event, the wearable device can reduce the overall power consumption of the wearable device by controlling the second processor to be in a sleep state (the second system is in a sleep state).

[0034] When the first system is in the wake-up state and the second system is in the sleep state, upon receiving an application startup instruction for a target application, it indicates that the target application needs to be started and executed. Since the first system does not have the ability to execute the target application, it is necessary to wake up the second system in the sleep state, and the second system starts and executes the target application.

[0035] However, since the wake-up process of the second system takes a certain amount of time (at least 200 ms to 300 ms), a phenomenon occurs where there is no response for some time after triggering the startup of the target application (specifically, it is necessary to wait for the time until the application screen appears), which affects the user experience. In the embodiments of the present application, in order to reduce the display delay of the application screen during system switching, when the wearable device receives an application startup instruction for a target application during the execution of the first system, first, the first system draws and displays the interface of the target application (it is not responsible for starting or executing the target application by the first system, but only for drawing the graphic interface).

[0036] Optionally, the application startup instruction is triggered by a shortcut key (e.g., a physical key) or by a widget of the first system. The target application may be a health monitoring application, an instant messaging application, a timing application, an alarm application, a sports application, etc. The interface of the target application may be a still image (e.g., the first frame of the application interface) or a video (e.g., the startup video of the application startup process). In the embodiments of the present application, the triggering method of the application startup instruction, the type of the target application, and the type of the interface are not limited.

[0037] Since the first system is in the wake-up state, immediately after receiving an application startup instruction, it can draw and display the interface, that is, immediately after the startup of the target application is triggered, the interface of the target application can be displayed. Thereby, the startup speed of the application is visually improved.

[0038] Exemplarily, as shown in FIG. 4, taking the case where the wearable device is a smartwatch as an example, the smartwatch is installed with an RTOS (executed by the first processor) and an Android system (executed by the second processor). When the first processor is in the wake-up state and the second processor is in the sleep state, the smartwatch displays the watch face 41 by the RTOS and keeps low power consumption by making the Android system in the sleep state. When the user needs to check sports data through the sports application, the sports application can be quickly started by double-clicking the physical key. When receiving the startup instruction of the sports application, the RTOS draws and displays the application interface 42 of the sports application.

[0039] Step 302: In response to the second system switching from the sleep state to the wake-up state, the second system draws the interface of the target application.

[0040] In one possible embodiment, while the first system is drawing and displaying the interface, the second system is synchronously woken up, that is, the second processor is switched from the sleep state to the wake-up state. After the second system is switched to the wake-up state, the second system starts and executes the target application. During the startup of the target application, the second system also needs to draw the interface of the target application.

[0041] Optionally, the interface of the target application drawn by the second system is the same as the interface of the target application drawn by the first system. For example, both the second system and the first system draw the first frame of the application interface after the target application is launched. Or, the interface of the target application drawn by the second system is different from the interface of the target application drawn by the first system. For example, the interface drawn by the first system is a transition animation during application startup, and the interface drawn by the second system is the first frame of the application interface after the playback of the transition animation is completed. Of course, the first system and the second system can also draw other interfaces belonging to the target application. In this embodiment, the specific interfaces drawn by the first system and the specific interfaces drawn by the second system are not limited.

[0042] Optionally, the first processor wakes up the second processor by sending an interrupt to the second processor.

[0043] Step 303: In response to the completion of the drawing of the interface of the target application by the second system, the second system displays the interface of the target application and executes the target application.

[0044] After the drawing of the interface by the second system is completed, the system running on the wearable device is switched from the first system to the second system, and the second system displays the interface of the target application and continues to execute the target application.

[0045] Optionally, after being switched to the second system, the first system may remain in the wake-up state (low power consumption and little impact on continuous usage time), or the first system may be switched to the sleep state. This is not limited in this embodiment.

[0046] Exemplarily, as shown in FIG. 4, during the display of the application interface 42 by the RTOS, the Android system is switched from the sleep state to the wake-up state. After waking up the Android system (for example, after 200 ms have elapsed), the system running on the smartwatch is switched from the RTOS to the Android system, and the Android system displays the application interface 42 and runs the sports application.

[0047] Optionally, after the second system completes event processing (for example, after ending the target application and returning to the watch face), the second processor is switched back to the sleep state, switched to the first system, and the first system processes the event. Thereby, the wearable device maintains high performance (but high power consumption) in few scenarios and low power consumption (but low performance) in many scenarios, further reducing the power consumption of the wearable device and extending the continuous usage time of the wearable device.

[0048] As described above, in the embodiments of the present application, in a wearable device that supports a dual system, when the first system is in an operating state and the second system is in a sleep state, upon receiving an application startup instruction for a target application, first, the first system draws and displays the interface of the target application, and after waking up the second system, the second system displays the interface of the target application and executes the target application. According to the proposal according to the embodiments of the present application, by pre-displaying the startup effect of the application by the first system, it is possible to visually improve the startup speed of the application and reduce the display delay of the application screen during system switching.

[0049] Optionally, the first system drawing and displaying the interface of the target application includes the first system obtaining target interface resource corresponding to the target application from a first storage space which is a storage space corresponding to the first system, and drawing and displaying the interface of the target application by the first system based on the target interface resource.

[0050] Optionally, the first system obtaining the target interface resource corresponding to the target application from the first storage space includes the first system obtaining target application information corresponding to the target application, and obtaining the target interface resource from the first storage space by the first system based on the target application information.

[0051] Optionally, the method further includes when the second system is in a wake-up state, the second system sending an interface resource update message to the first system, and Further including updating, by the first system, the interface resources stored in the first memory space based on the interface resource update message.

[0052] Optionally, when the second system is in a wake-up state, the second system sending an interface resource update message to the first system includes the following. When the second system is in a wake-up state, in response to receiving a language update broadcast, the second system obtains first application information of the first application. The first interface resources corresponding to the first application are stored in the first memory space. The second system sends a first interface resource update message including the first application information and the updated first interface resources to the first system. Updating, by the first system, the interface resources stored in the first memory space based on the interface resource update message is Including the first system associating the first application information and the updated first interface resources and storing them in the first memory space.

[0053] Optionally, the second system obtaining the first application information of the first application includes The second system sending a query message to the first system; The first system sending the first application information of the first application to the second system and deleting the first interface resources corresponding to the first application from the first memory space.

[0054] Optionally, the second system obtaining the first application information of the first application includes The second system obtaining the first application information of the first application from the second memory space, which is the memory space corresponding to the second system. The first system memorizes in the first memory space by associating first application information with an updated first interface resource. This is In response to identifying that the first interface resource update message includes a forced update identifier, the first system deletes the interface resource memorized in the first memory space, and memorizes in the first memory space by associating first application information with the updated first interface resource. This includes

[0055] Optionally, when the second system is in a wake-up state, the second system sending an interface resource update message to the first system includes the following. When the second system is in a wake-up state, in response to monitoring a start-up form update message of a second application, the second system acquires second application information and a second interface resource of the second application. The start-up form update message is used to represent a change in the start-up form of the second application. The second system sends a second interface resource update message including an update form, second application information, and a second interface resource to the first system. Updating the interface resource memorized in the first memory space by the first system based on the interface resource update message is Based on the update form, the first system updating the second interface resource corresponding to the second application information in the first memory space. This includes

[0056] Optionally, based on the update form, the first system updating the second interface resource corresponding to the second application information in the first memory space is In response to the update form being an addition, the first system memorizing in the first memory space by associating second application information with the second interface resource, and In response to the update mode being deletion, the first system deletes second application information and second interface resources from the first memory space, including this.

[0057] Optionally, the method In response to the update mode being addition and the second application information being stored in the first memory space, identifying that there is an update conflict, In response to the update mode being deletion, the second application information being stored in the first memory space, and the second application information being used by a startup mode other than the startup mode waiting to be deleted, further including identifying that there is an update conflict, If there is an update conflict, the second interface resources in the first memory space are not updated.

[0058] Optionally, based on the update mode, the first system updating the second interface resources corresponding to the second application information in the first memory space is Based on the update mode, in response to the second interface resource update message not including a forced update identifier and being identified that there is no update conflict, the first system updating the second interface resources corresponding to the second application information in the first memory space, including this. The above method Based on the update mode, in response to being identified that the second interface resource update message includes a forced update identifier, the first system further including updating the second interface resources corresponding to the second application information in the first memory space.

[0059] Optionally, the first memory space is used to store interface resources corresponding to applications supported to be launched by the first system, The forms of starting an application in the first system include at least one of starting by a shortcut key and starting by a widget of the first system.

[0060] Optionally, in response to the completion of the drawing of the interface of the target application by the second system, the second system displays the interface of the target application and executes the target application, in response to the completion of the drawing of the interface of the target application by the second system, the second system sends a switching instruction to the first system to instruct the first system to transfer the display right of the graphical user interface (GUI); in response to the second system obtaining the display right of the GUI, the second system displays the interface of the target application and executes the target application.

[0061] Optionally, the wearable device includes a first processor and a second processor, the power consumption of the second processor is greater than that of the first processor, the first system is a system executed by the first processor, and the second system is a system executed by the second processor.

[0062] In one possible embodiment, the first system and the second system respectively correspond to data storage spaces. Since the first system is only responsible for processing simple events and the second system needs to process complex events, the storage space corresponding to the second system is much larger than the storage space corresponding to the first system. To realize the drawing and display of the interface by the first system, the interface resources corresponding to the application are stored in the storage space corresponding to the first system. When receiving an application start instruction, the first system draws the application interface based on the interface resources in the storage space. Hereinafter, exemplary embodiments will be used for description.

[0063] Referring to FIG. 5, FIG. 5 is a flowchart showing a method for displaying an application interface according to another exemplary embodiment of the present application. In this embodiment, the method is described by taking the application to a wearable device as an example. The method can include the following steps.

[0064] Step 501: When the first system is in a wake-up state and the second system is in a sleep state, in response to an application startup instruction of a target application, the first system obtains a target interface resource corresponding to the target application from a first storage space which is a storage space corresponding to the first system in the first storage space.

[0065] In an embodiment of the present application, the first system corresponds to the first storage space, and at least one interface resource corresponding to an application is stored in the first storage space. The interface resource refers to a resource required for drawing an application interface, and the interface resource can include a character resource, an image resource, a video resource, a special-effect resource, an interface-layout resource, etc. In this embodiment, the specific content included in the interface resource is not limited.

[0066] In one possible embodiment, interface resources corresponding to each application in the second system are stored in the first storage space. For example, when a sports application, a health monitoring application, an alarm application, and an instant messaging application are installed in the second system, interface resources corresponding to each of the four applications are stored in the first storage space.

[0067] Since the capacity of the first memory space is limited, it is not the case that all applications in the second system are supported to be launched by the first system (i.e., the target application is an application supported to be launched in the first system). Therefore, in another possible embodiment, the first memory space is used to store interface resources corresponding to applications supported to be launched in the first system. Thereby, while realizing seamless system switching, the memory space occupied by the interface resources is reduced.

[0068] Optionally, an application supported to be launched in the first system is an application that can be launched when the second system is in a sleep state. For example, if a start-up entry of the application is set in the first system, the application belongs to the applications supported to be launched in the first system, and / or if the application is set to be launchable by a shortcut key, the application belongs to the applications supported to be launched in the first system.

[0069] In some embodiments, the form of launching an application in the first system includes at least one of launching by a shortcut key and launching by a widget of the first system.

[0070] The form of launching an application in the first system via shortcut keys can be set by the user himself. For example, launching a specific application by double-clicking a physical key or launching a specific application by long-pressing a physical key can be set. Widgets can be added to the first system by the user himself. For example, a widget corresponding to a health monitoring application is added to the watch face so that the user can launch the health monitoring application by clicking on the widget displayed in the first system.

[0071] For example, if a sports application, a health monitoring application, an alarm application, and an instant messaging application are installed in the second system, since the sports application supports launching by double-clicking a physical key and the health monitoring application supports triggering by a widget on the watch face, only the interface resources corresponding to the sports application and the interface resources corresponding to the health monitoring application are stored in the first storage space, and there is no need to store the interface resources corresponding to the alarm application and the interface resources corresponding to the instant messaging application.

[0072] Regarding the specific form of obtaining the target interface resources corresponding to the target application, in one possible implementation, application information and interface resources are associated and stored in the first storage space, that is, the mapping relationship between the application information and the interface resources is stored.

[0073] Optionally, the application information includes at least one of an application package name and an application activity name. If an application has only a single functional interface, the application information includes the application package name. If an application has multiple functional interfaces and a specific functional interface can be launched and displayed in the first system, the application information includes the application package name and the application activity name (corresponding to the specific functional interface).

[0074] Upon receiving an application launch instruction for a target application, the first system obtains target application information corresponding to the target application, and based on the target application information, the first system obtains target interface resources from the first storage space. The target application information includes at least one of a target application package name and a target application activity name.

[0075] In some embodiments, the first system searches the first storage space for interface resources that match the target application information based on the target application information, and identifies the searched interface resources as the target interface resources corresponding to the target application.

[0076] In an exemplary example, the mapping relationship between the application information and the interface resources in the first storage space is as shown in Table 1.

[0077]

Table 1

[0078] When the application package name of the target application is obtained as "sport_app", the first system identifies the interface resource file A in the first memory space as the target interface resource. When the application package name of the target application is obtained as "health_app", the first system identifies the interface resource file B in the first memory space as the target interface resource.

[0079] Step 502: Based on the target interface resource, the first system draws and displays the interface of the target application.

[0080] Furthermore, when the target interface resource is obtained, the first system immediately draws and displays the interface in real time.

[0081] Optionally, during the drawing of the interface by the first system, in addition to using the target interface resource, other data such as time data and sensor data (e.g., pedometer data) need to be used, thereby ensuring the accuracy of the content in the drawn interface.

[0082] In an exemplary example, the target interface resource corresponding to the sports application obtained by the first system includes an image resource, a character resource, and an interface layout resource. The first system draws the image resource and the character resource at the corresponding interface positions according to the interface element layout method indicated by the interface layout resource, and renders the current time and pedometer data on the interface to obtain the application interface of the sports application.

[0083] Step 503: In response to the second system switching from the sleep state to the wake-up state, the second system draws the interface of the target application.

[0084] For the implementation of this step, reference can be made to Step 302, which is omitted in this embodiment.

[0085] Step 504: In response to the second system completing the drawing of the interface of the target application, the second system sends a switching instruction to the first system to instruct the first system to transfer the display permission of the graphical user interface (GUI) to the second system.

[0086] To ensure the normal use of the target application, during system switching, the first system needs to transfer the display permission of the GUI to the second system so that the GUI of the second system is displayed on the wearable device during the operation of the target application. In one possible embodiment, after completing the interface drawing, the second system sends a switching instruction to the first system to instruct the first system to transfer the display permission of the GUI to the second system.

[0087] Step 505: In response to the second system obtaining the display permission of the GUI, the second system displays the interface of the target application and executes the target application.

[0088] After obtaining the display permission of the GUI, the second system displays the interface of the target application for which the drawing has been completed and executes the target application. Accordingly, the interface of the target application is displayed on the wearable device.

[0089] In this embodiment, by storing application information and interface resources in the first storage space, when the first system receives an application startup instruction, based on the target application information of the target application, the first system can accurately obtain the corresponding target interface resources from the first storage space, which helps to improve the speed and accuracy of interface drawing.

[0090] Moreover, only the interface resources of the applications supported to be launched by the first system are stored in the first storage space. Thereby, while realizing seamless system switching, the storage space occupied by the interface resources is reduced, and the need for the capacity of the first storage space is reduced.

[0091] In the above embodiment, the interface of the application in the wearable device does not necessarily remain unchanged, and the applications supported to be launched by the first system may also change. Therefore, in order to ensure the accuracy of the application interface displayed during application startup, the interface resources stored in the first storage space also need to be updated accordingly. In one possible embodiment, when the second system is in a wake-up state, the wearable device sends an interface resource update message to the first system by the second system (when there is an interface resource update event), and the first system updates the interface resources stored in the first storage space based on the interface resource update message. The interface resource update message includes at least the application information of the applications waiting for update.

[0092] Taking as an example that the first system is an RTOS executed by an MCU and the second system is an Android system executed by a CPU, as shown in FIG. 6, when there is an interface resource update event (including events such as language update, widget update, shortcut key update, etc.) in the application layer (Application), the application layer presets the updated interface resources to the framework resources corresponding to the Android system and the Android application package (APK).

[0093] The interface resource management and control center set in the framework layer is responsible for monitoring interface resource update events. When monitoring that there is an interface resource update event, the interface resource management and control center obtains the interface resources from the framework resource APK and communicates with the MCU through the dual-core communication module set in the kernel layer (specifically, set in the DCC of the kernel layer). The MCU updates the interface resources stored in the first storage space based on the received interface resource update data.

[0094] For different update scenarios, the update process of interface resources due to the interaction between the second system and the first system is also different. When there is a system-level interface resource update event, the first system needs to update all the interface resources stored in the first storage space. When there is an application-level interface resource update event, the first system only needs to update the interface resources of a specific application. Hereinafter, the update process of interface resources in different update scenarios will be described using embodiments respectively.

[0095] Referring to FIG. 7, FIG. 7 is a flowchart showing an update process of interface resources according to an exemplary embodiment of the present application. In this embodiment, the method is described by taking the application to a wearable device as an example. The method can include the following steps.

[0096] Step 701: When the second system is in a wake-up state, in response to receiving a language update broadcast, the second system acquires first application information of a first application. A first interface resource corresponding to the first application is stored in a first storage space.

[0097] In one possible embodiment, when the system language of the wearable device is changed, the second system receives a language update broadcast including the system language after the switch. For example, when the user switches the system language of the wearable device from Chinese to English, the second system receives a language update broadcast instructing the switch to English.

[0098] When the system language is changed, the application languages of all applications in the second system need to be changed accordingly, and the content (e.g., text content) included in the application interface also changes. Therefore, after receiving the language update broadcast, the second system needs to identify that the interface resources of all applications need to be updated and acquires the first application information of the first application in the first storage space.

[0099] Regarding the form of acquiring the first application information, in one possible embodiment, since a mapping relationship between the first application information and the first interface resource is stored in the first storage space, the second system can acquire the first application information by the first system. Optionally, this step can include the following steps.

[0100] 1. The second system sends a query message to the first system.

[0101] Optionally, the second system sends a query message to the first system via the dual-core communication module of the kernel layer, and requests the first system to query the first application information stored in the first storage space. Accordingly, when receiving the query message, the first system obtains the stored first application information from the first storage space.

[0102] Exemplarily, as shown in FIG. 8, when in the wake-up state, upon receiving a language update broadcast (ACTION_LOCALE_CHANGED), the Android system sends a query message to the RTOS.

[0103] 2. The first system sends the first application information of the first application to the second system, and deletes the first interface resource corresponding to the first application from the first storage space.

[0104] Optionally, after querying the first application information of each first application, the first system sends a query result including the first application information to the second system via the dual-core communication module of the kernel layer.

[0105] Combined with the data shown in Table 1 of the above embodiment, the query results fed back by the first system to the second system include the application package names sport_app and health_app.

[0106] After the system language is updated, since the originally stored interface resources become invalid, in one possible embodiment, to release the first memory space and ensure the accuracy of subsequent interface resource updates, the first system deletes the first interface resources corresponding to the first application from the first memory space.

[0107] Optionally, the query message sent by the second system contains a pre-set identifier. When it is identified that the query message contains a pre-set identifier, the first system determines that interface resource update due to the change of the system language is necessary, and deletes the first interface resources stored in the first memory space. In connection with the data shown in Table 1 of the above embodiment, the first system deletes the interface resource file A and the interface resource file B stored in the first memory space.

[0108] Exemplarily, as shown in FIG. 8, the RTOS feeds back the query result to the Android system and at the same time deletes the first interface resources stored in the first memory space.

[0109] Step 702: The second system sends a first interface resource update message including the first application information and the updated first interface resources to the first system.

[0110] In one possible embodiment, the second system obtains the updated first interface resources corresponding to the first application stored in the second memory space based on the first application information. The second memory space is the memory space corresponding to the second system, and the updated first interface resources are stored in the second memory space by each first application. For example, the interface resource management control center in the second system obtains the updated first interface resources from the framework resource APK.

[0111] In connection with the illustration in the above steps, the second system obtains updated interface resource files A' and B' based on the application package names sport_app and health_app.

[0112] Optionally, the character resources included in the updated first interface resource are different from the character resources included in the first interface resource before the update. For example, the updated character resources are in the English version of the first application, and the character resources before the update are in the Chinese version of the first application.

[0113] Furthermore, so that the first system updates the interface resources in the first storage space, the second system sends a first interface resource update message to the first system via the dual-core communication module.

[0114] In one possible embodiment, the first interface resource update message may include the following fields. 1. A path for representing an update path. In this embodiment, the value of the path field represents triggering interface resource updates by system language updates. 2. An action for representing the update mode of the interface resources. In this embodiment, the value of the action field represents switching of the interface resources. 3. The packagename which is the application package name. 4. The data which is the updated interface resource. 5. An extra for representing whether to force the update of the interface resources. In this embodiment, the value of the extra field represents forcing the update of the interface resources.

[0115] Note that the first interface resource update message may include other fields. In this embodiment, the description is given by way of example only for including the above fields, but it is not limited thereto.

[0116] Exemplarily, as shown in FIG. 8, when the Android system receives a query result, it acquires updated first interface resources based on the query result, and sends a first interface resource update message to the RTOS based on the first interface resources.

[0117] Step 703: The first system associates the first application information with the updated first interface resources and stores them in the first storage space.

[0118] When receiving the first interface resource update message, the first system associates and stores the first application information with the updated first interface resources. During subsequent system switching, the first system can draw and display the application interface based on the updated interface resources, ensuring that the language adopted by the displayed application interface matches the system language.

[0119] In connection with the example in the above step, after the first system updates the interface resources based on the first interface resource update message, the mapping relationship between the application information and the interface resources in the first storage space is shown in Table 2.

[0120]

Table 2

[0121] Optionally, after the interface resource update is completed, the first system sends a completion notice to the second system to notify the second system that the interface resource update is completed. If the second system does not receive the completion notice within the preset time, it sends the first interface resource update message to the first system again.

[0122] Exemplarily, as shown in FIG. 8, after updating the first interface resource, the RTOS sends a completion notice to the Android system.

[0123] In addition to adopting the form of obtaining the first application information from the first system, in another possible embodiment, since each application stores the updated interface resource in the second system (the second storage space), the wearable device can also obtain the first application information of the first application from the second storage space by the second system, and set a forced update identifier in the first interface resource update message sent to the first system.

[0124] Accordingly, when the first system identifies that the first interface resource update message includes a forced update identifier (for example, set in the extra field in the first interface update message), it deletes the interface resource stored in the first storage space, associates the first application information with the updated first interface resource, and stores them in the first storage space, so as not to store two sets of interface resources of the same application.

[0125] In this embodiment, when updating the system language, the second system obtains the first application information of each first application, and obtains the updated first interface resource based on the first application information, and then transmits the updated first interface resource to the first system. The first system updates the first interface resource stored in the first storage space to ensure that the language of the application interface displayed on the first system matches the system language during subsequent system switching.

[0126] Referring to FIG. 9, FIG. 9 is a flowchart showing a process for updating an interface resource according to another exemplary embodiment of the present application. In this embodiment, the method is described by taking the application to a wearable device as an example. The method can include the following steps.

[0127] Step 901: When the second system is in a wake-up state, in response to monitoring a start-up manner update message of the second application, the second system obtains the second application information and the second interface resource of the second application. The start-up manner update message is used to represent a change in the start-up manner of the second application.

[0128] To improve the start-up efficiency of the application, the user may set a quick start-up manner for the application in the second system so that the application in the second system can be started by the first system. The setting of the quick start-up manner can include adding a widget of the application to the first system and setting a shortcut key for starting the application.

[0129] Accordingly, when the startup mode of the second application is updated (for example, adding a fast startup mode or deleting a fast startup mode), the first system needs to adaptively update the interface resources in the first storage space.

[0130] In one possible embodiment, when the startup mode of the second application in the second system changes, the second system monitors a startup mode change message. The startup mode change message can include a target startup mode and an update form corresponding to the target startup mode.

[0131] For example, when widget-based startup is set for the second application, the target startup mode is widget startup and the update form is addition. When it is set that the shortcut key startup mode is deleted from the second application, the target startup mode is shortcut key startup and the update form is deletion.

[0132] Furthermore, the second system acquires second application information and second interface resources corresponding to the second application. The second system can acquire the second interface resources from the second storage space based on the application information of the second application in the startup mode update message.

[0133] Optionally, when the update form indicated by the startup mode update message is addition, the second system acquires the second application information and the second interface resources. When the update form indicated by the startup mode update message is deletion, the second system acquires only the second application information.

[0134] Exemplarily, as shown in FIG. 10, when the Android system monitors a startup form update message of a second application (including ACTION_SHORTCUT_SETTING_CHANGED and ACTION_WIDGET_CHANGED), it acquires second interface resources of the second application.

[0135] Step 902: The second system sends a second interface resource update message including an update form, second application information, and second interface resources to the first system.

[0136] Based on the acquired second interface resources, the second system sends a second interface resource update message to the first system via a dual-core communication module. In addition to including the second application information and the second interface resources, the second interface resource update message further includes a target startup form and an update form.

[0137] In one possible embodiment, the second interface resource update message may include the following fields. 1. path for representing an update path. In this embodiment, the value of the path field represents triggering interface resource update by an update of a fast startup form (including an update of a widget and an update of a shortcut key). 2. action for representing a manner of updating interface resources. In this embodiment, the value of the action field represents adding interface resources or deleting interface resources. 3. packagename which is an application package name. 4. activityname which is an application activity name for indicating a specific application interface of the application. 5. data which is the updated interface resource. extra for indicating whether to forcefully update the interface resource

[0138] Note that the second interface resource update message may include other fields. In this embodiment, the description is given by way of example only for including the above fields, but it is not limited thereto.

[0139] Exemplarily, as shown in FIG. 10, after obtaining the second interface resource, the Android system sends a second interface resource update message to the RTOS, and instructs the RTOS to update the interface resource stored in the first storage space.

[0140] Step 903: Based on the update form, the first system updates the second interface resource corresponding to the second application information in the first storage space.

[0141] In one possible embodiment, the first system updates the second interface resource corresponding to the second application information in the first storage space based on the obtained second interface resource update message.

[0142] Regarding the specific form of interface resource update, in some embodiments, when the update form is addition, the wearable device associates the second application information and the second interface resource by the first system and stores them in the first storage space. When the update form is deletion, the wearable device deletes the second application information and the second interface resource from the first storage space by the first system.

[0143] In one possible application scenario, when the second interface resource of the second application is stored in the first storage space, directly updating the interface resource based on the second interface resource update message may cause an update conflict.

[0144] For example, when the second interface resource of the second application is stored in the first memory space, if the second interface resource update message instructs the addition of the second interface resource of the second application (which can support different fast startup forms), directly adding the second interface resource to the first memory space will cause duplicate storage of interface resources and waste of memory space.

[0145] In another example, when the second interface resource of the second application is stored in the first memory space and it is supported that the second application is started in at least two different fast startup forms, if the second interface resource update message instructs the deletion of the second interface resource of the second application (deleting one of the fast startup forms), directly deleting the second interface resource from the first memory space will result in the second application being started only in other fast startup forms, causing the first system to be unable to draw and display the application interface.

[0146] Therefore, in one possible embodiment, when the first system receives the second interface resource update message, it detects an update collision based on the update form and the second application information. If there is no update collision, the first system updates the interface resources in the first memory space based on the update form indicated by the second interface resource update message. If there is a collision, the first system does not respond to the second interface resource update message.

[0147] Regarding a specific form for detecting whether there is an update conflict, in one possible embodiment, when the update form is an addition (addition of a second interface resource), the first system detects whether second application information exists in the first storage space. If the second application information does not exist in the first storage space, it is identified that there is no update conflict, and the second application information and the second interface resource are associated and stored in the first storage space.

[0148] In an exemplary example, if the mapping relationship between the application information and the interface resource in the first storage space is as shown in Table 1, the update form included in the second interface resource update message is an addition, and the included second application information is "Application Package Name: alarm_app" (alarm application), then since the second application information is not included in the first storage space, it is identified that there is no update conflict, and the interface resource is updated. After the interface resource is updated, the mapping relationship between the application information and the interface resource in the first storage space is shown in Table 3.

[0149]

Table 3

[0150] Optionally, in response to the update form being an addition and the second application information being stored in the first storage space, the first system identifies that there is an update conflict and does not update the second interface resource in the first storage space.

[0151] Optionally, when the update form is an addition and it is identified that there is an update conflict, the first system adds a corresponding startup form waiting for addition to the second application information.

[0152] For example, when associated with the data shown in Table 3, the update form included in the second interface resource update message is an addition, and the included second application information is "Application Package Name: sport_app", since the first storage space contains the second application information, it is identified that there is an update conflict, the interface resource file A is not updated, and only the target startup form "shortcut key" in the second interface resource update message is added to sport_app.

[0153] In another possible embodiment, when the update form is a deletion (deletion of the second interface resource), the first system detects whether the second application information stored in the first storage space is used by a startup form other than the startup form to be deleted based on the target startup form (i.e., the startup form to be deleted) in the second interface resource update message. If there is no startup form other than the startup form to be deleted (i.e., the second application is started only using the shortcut form indicated by the startup form to be deleted), the first system identifies that there is no update conflict and deletes the second application information and the second interface resource from the first storage space.

[0154] In an exemplary example, the mapping relationship among the application information, interface resources, and startup forms in the first storage space is shown in Table 4.

[0155]

Table 4

[0156] If the update form included in the second interface resource update message is deletion, and the included second application information is "Application Package Name: health_app", and the startup form waiting to be deleted is "shortcut key", the first system determines that there is no update conflict and updates the interface resource. After the interface resource is updated, the mapping relationship among the application information, interface resource, and startup form in the first storage space is shown in Table 5.

[0157]

Table 5

[0158] Optionally, in response to the update form being deletion and the second application information being stored in the first storage space and the second application information being used by a startup form other than the startup form waiting to be deleted, the first system determines that there is an update conflict and does not update the second interface resource in the first storage space.

[0159] Optionally, if the update form is deletion and it is determined that there is an update conflict, the first system deletes the corresponding startup form waiting to be deleted for the second application information.

[0160] For example, in connection with the data shown in Table 4, if the update form included in the second interface resource update message is deletion and the included second application information is "Application Package Name: health_app", since the first storage space contains the second application information, it is determined that there is an update conflict, the interface resource file A is not updated, and only the startup form "shortcut key" waiting to be deleted in the second interface resource update message for health_app is deleted.

[0161] In one possible embodiment, the second system can instruct a forced update to the second interface resource by setting a forced update identifier in the second interface resource update message.

[0162] Optionally, in response to recognizing that the forced update identifier is not included in the second interface resource update message, the first system detects an update conflict based on the update form and the second application information. In response to recognizing that the forced update identifier is included in the second interface resource update message, the first system updates the second interface resource corresponding to the second application information in the first storage space based on the update form.

[0163] Optionally, after the interface resource update is completed, the first system sends a completion notice of the update to the second system to notify the second system that the interface resource update is completed. If the second system does not receive the completion notice of the update within a preset time, it sends a second interface resource update message to the first system again.

[0164] Exemplarily, as shown in FIG. 10, after receiving the second interface resource update message, if the forced update identifier is included in the second interface resource update message, the RTOS system directly updates (adds or deletes) the interface resource. If the forced update identifier is not included in the second interface resource update message, the RTOS system updates (adds or deletes) the interface resource conditionally (i.e., when there is no update conflict), and after updating the second interface resource, it sends a completion notice of the update to the Android system.

[0165] In this embodiment, when there is an update in the startup form of the second application, the second system acquires the second application information of the second application, acquires the second interface resource based on the second application information, and sends a second interface resource update message to the first system. The first system determines whether there is an update conflict in the second interface resource. If there is no update conflict, the second interface resource is updated; if there is an update conflict, the second interface resource is not updated. Thereby, after the startup form is updated, the normal operation of the function of seamless system switching is ensured.

[0166] In addition, in each of the above embodiments, only the display process of the application interface in the dual-core dual-system device is described as an example. In other possible application scenarios, a single-core dual-system (for example, a processor executes different systems on different cores) device can also adopt the proposal according to the embodiment of the present application to realize the display of the application interface during system switching, which will not be elaborated herein.

[0167] Referring to FIG. 11, FIG. 11 is a block diagram showing the structure of a display device for an application interface according to an embodiment of the present application. The device can be implemented as all or part of a wearable device by software, hardware, or a combination of both. The device includes a first system module 1101 and a second system module 1102. The first system module 1101 is configured to draw and display the interface of the target application by the first system in response to an application startup instruction of the target application when the first system is in a wake-up state and the second system is in a sleep state. The second system module 1102 is configured to draw the interface of the target application by the second system in response to the switching of the second system from the sleep state to the wake-up state. The second system module 1102 is further configured to display the interface of the target application and execute the target application by the second system in response to the completion of the drawing of the interface of the target application by the second system.

[0168] Optionally, the first system module 1101 acquires, by the first system, the target interface resource corresponding to the target application from the first storage space which is the storage space corresponding to the first system, and is configured to draw and display the interface of the target application by the first system based on the target interface resource.

[0169] Optionally, specifically, the first system module 1101 acquires, by the first system, the target application information corresponding to the target application, and is configured to acquire the target interface resource from the first storage space by the first system based on the target application information.

[0170] Optionally, the second system module 1102 is further configured to send an interface resource update message to the first system by the second system when the second system is in a wake-up state. The first system module 1101 is further configured to update the interface resource stored in the first storage space by the first system based on the interface resource update message.

[0171] Optionally, specifically, the second system module 1102 When the second system is in a wake-up state, in response to receiving a language update broadcast, the second system is configured to obtain first application information of a first application, and a first interface resource corresponding to the first application is stored in a first storage space. The second system module 1102 is configured to send, by the second system, a first interface resource update message including the first application information and the updated first interface resource to the first system. Specifically, the first system module 1101 is configured to store, by the first system, the first application information and the updated first interface resource in association with each other in the first storage space.

[0172] Optionally, specifically, the second system module 1102 is configured to send, by the second system, a query message to the first system. Specifically, the first system module 1101 is configured to send, by the first system, the first application information of the first application to the second system, and delete the first interface resource corresponding to the first application from the first storage space.

[0173] Optionally, specifically, the second system module 1102 is configured to obtain, by the second system, the first application information of the first application from a second storage space which is a storage space corresponding to the second system. Specifically, in response to identifying that a forced update identifier is included in the first interface resource update message, the first system module 1101 is configured to delete, by the first system, the interface resource stored in the first storage space, and store the first application information and the updated first interface resource in association with each other in the first storage space.

[0174] Optionally, the second system module 1102 is specifically configured to, when the second system is in a wake-up state, in response to monitoring a startup form update message of a second application, obtain second application information and second interface resources of the second application by the second system, and the startup form update message is used to represent a change in the startup form of the second application. The second system module 1102 is configured to transmit, by the second system, a second interface resource update message including an update form, second application information, and second interface resources to the first system. The first system module 1101 is specifically configured to update, by the first system, second interface resources corresponding to the second application information in the first storage space based on the update form.

[0175] Optionally, the first system module 1101 is specifically configured to, in response to the update form being an addition, associate the second application information and the second interface resources by the first system and store them in the first storage space, in response to the update form being a deletion, delete the second application information and the second interface resources from the first storage space by the first system.

[0176] Optionally, the first system module 1101 is further configured to, in response to the update form being an addition and the second application information being stored in the first storage space, identify that there is an update conflict, in response to the update form being a deletion, the second application information being stored in the first storage space, and the second application information being used by a startup form other than the startup form waiting to be deleted, identify that there is an update conflict. If there is an update conflict, the second interface resource in the first memory space is not updated.

[0177] Optionally, the first system module 1101 further In response to the second interface resource update message not including a forced update identifier and being identified as having no update conflict, based on the update form, the first system updates the second interface resource corresponding to the second application information in the first memory space, In response to being identified that the second interface resource update message includes a forced update identifier, based on the update form, the first system is configured to update the second interface resource corresponding to the second application information in the first memory space.

[0178] Optionally, the first memory space is used to store interface resources corresponding to applications supported to be launched by the first system. The forms of launching an application in the first system include at least one of launching by a shortcut key and launching by a widget of the first system.

[0179] Optionally, the second system module 1102 further In response to the completion of the drawing of the interface of the target application by the second system, the second system sends a switching instruction to the first system to instruct the first system to transfer the display permission of the graphical user interface (GUI) to the second system. In response to the second system obtaining the display permission of the GUI, the second system is configured to display the interface of the target application and execute the target application.

[0180] Optionally, the wearable device includes a first processor and a second processor, the power consumption of the second processor being greater than that of the first processor. The first system is a system executed by the first processor, and the second system is a system executed by the second processor.

[0181] As described above, in the embodiments of the present application, in a wearable device that supports a dual system, when the first system is in an operating state and the second system is in a sleep state, upon receiving an application startup instruction for a target application, first, the first system draws and displays the interface of the target application, and after waking up the second system, the second system displays the interface of the target application and executes the target application. According to the proposal according to the embodiments of the present application, by pre-displaying the startup effect of the application by the first system, it is possible to visually improve the startup speed of the application and reduce the display delay of the application screen during system switching.

[0182] In this embodiment, by storing application information and interface resources in the first storage space, when the first system receives an application startup instruction, the first system can accurately obtain the corresponding target interface resources from the first storage space based on the target application information of the target application, which helps to improve the speed and accuracy of the interface drawing of the target application.

[0183] Also, only the interface resources of the applications supported to be started in the first system are stored in the first storage space, thereby realizing seamless system switching, reducing the storage space occupied by the interface resources, and reducing the need for the capacity of the first storage space.

[0184] In this embodiment, when updating the system language, the second system obtains the first application information of each first application, and obtains the updated first interface resource based on the first application information, and then transmits the updated first interface resource to the first system. The first system updates the first interface resource stored in the first storage space to ensure that the language of the application interface displayed on the first system matches the system language during subsequent system switching.

[0185] In this embodiment, when there is an update to the startup form of the second application, the second system obtains the second application information of the second application, obtains the second interface resource based on the second application information, and transmits a second interface resource update message to the first system. The first system determines whether there is an update conflict in the second interface resource. If there is no update conflict, the second interface resource is updated; if there is an update conflict, the second interface resource is not updated. Thereby, the normal operation of the function of seamless system switching is ensured after the startup form is updated.

[0186] Referring to FIG. 12, FIG. 12 is a block diagram showing the structure of a wearable device according to an exemplary embodiment of the present application. The wearable device in the present application can include at least one or more processors 1210 and one or more memories 1220.

[0187] Optionally, the processor 1210 includes at least a first processor 1211 and a second processor 1212. The first processor 1211 is used to execute a first system, the second processor 1212 is used to execute a second system, the power consumption of the first processor 1211 is lower than that of the second processor 1212, and the performance of the first processor 1211 is lower than that of the second processor 1212. The processor 1210 utilizes various interfaces and lines to connect all parts within the electronic device, executes instructions, programs, code sets or instruction sets stored in the memory 1220, and calls the data stored in the memory 1220, thereby executing various functions and processing data of the electronic device. Optionally, the processor 1210 may be implemented using at least one of digital signal processing (DSP), field programmable gate array (FPGA), and programmable logic array (PLA). The processor 1210 can integrate one or several combinations of a central processing unit (CPU), a graphics processing unit (GPU), a neural-network processing unit (NPU), and a modem, etc. The CPU mainly processes the operating system, user interface, application programs, etc. The GPU is responsible for rendering and drawing the content that needs to be displayed on the touch display screen. The NPU is used to implement artificial intelligence (AI) functions. The modem is used to process wireless communication. The above modem does not have to be integrated into the processor 1210 and may be implemented with only one chip.

[0188] The memory 1220 can include a random access memory (RAM) and can also include a read only memory (ROM). Optionally, the memory 1220 includes a non-transitory computer-readable storage medium. The memory 1220 can be used to store instructions, programs, codes, code sets, or instruction sets. The memory 1220 can include a program storage area and a data storage area. The program storage area can store instructions for implementing an operating system, instructions for at least one function (such as a touch function, an audio playback function, an image playback function, etc.), instructions for implementing each method embodiment, and the like. The data storage area can store data created according to the use of the wearable device (such as audio data, a phone book), etc.

[0189] The wearable device according to an embodiment of the present application further includes a communication component 1230 and a display component 1240. The communication component 1230 can be a Bluetooth service module, a wireless fidelity (WiFi) module, a near field communication (NFC), and communicates with an external device (a server or another terminal device) via a wired or wireless network. The display component 1240 is used for displaying a GUI and / or receiving user interaction operations.

[0190] In addition to the above, those skilled in the art can understand the following. The structure of the wearable device shown in the above drawings does not limit the wearable device. The wearable device may have more or fewer components than those shown, or may combine some components, or have different arrangements of components. For example, the wearable device also includes components such as a wireless circuit, an input unit, a sensor, an audio circuit, a speaker, a microphone, a power source, etc., and the description thereof is omitted here.

[0191] In an embodiment of the present application, a computer-readable storage medium is further provided. At least one instruction is stored in the storage medium. The at least one instruction is used to implement the display method of the application interface described in the above embodiment when executed by a processor.

[0192] In an embodiment of the present application, a computer program product or a computer program is provided. The computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to execute the display method of the application interface according to the above embodiment.

[0193] Those skilled in the art can be aware of the following. In one or more of the above examples, the functions described in the embodiments of the present application can be realized by hardware, software, firmware, or any combination thereof. When these functions are realized by software, they may be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. The computer-readable medium includes a computer storage medium and a communication medium. The communication medium includes any medium that facilitates the transmission of a computer program from one place to another. The storage medium may be any available medium accessible by a general-purpose or special-purpose computer.

[0194] The above are only selectable embodiments of the present application and do not limit the present application. Any modifications, equivalent replacements, improvements, etc. within the scope of the spirit and principle of the present application are included in the protection scope of the present application.

Claims

1. 1. A method for displaying an application interface, the method being performed by a wearable device supporting execution of a first system and a second system, the method comprising: When the first system is in a wake-up state and the second system is in a sleep state, rendering and displaying an interface of a target application by the first system; After the second system is switched from a sleep state to a wake-up state, rendering an interface of the target application by the second system; and in response to the second system completing the rendering of the interface of the target application, displaying, by the second system, the interface of the target application and executing the target application.

13. A method for displaying an application interface comprising:

2. Rendering and displaying an interface of a target application by the first system when the first system is in a wake-up state and the second system is in a sleep state includes: and when the first system is in a wake-up state and the second system is in a sleep state, in response to an application launch indication of the target application, rendering and displaying an interface of the target application by the first system. The method of claim 1, wherein the application interface is displayed on the display screen.

3. Rendering and displaying an interface of the target application by the first system includes: obtaining, by the first system, a target interface resource corresponding to the target application from a first storage space, the first storage space being a storage space corresponding to the first system; and rendering and displaying an interface of the target application by the first system based on the target interface resources.

3. The method for displaying an application interface according to claim 1 or 2.

4. obtaining, by the first system, the target interface resource corresponding to the target application from the first storage space; obtaining, by the first system, target application information corresponding to the target application; and obtaining the target interface resource from the first storage space by the first system based on the target application information.

4. The method of claim 3, wherein the application interface is displayed on the display device.

5. The method for displaying an application interface includes: sending an interface resource update message by the second system to the first system when the second system is in a wake-up state; and updating, by the first system, the interface resource stored in the first storage space based on the interface resource update message.

5. The method for displaying an application interface according to claim 3 or 4.

6. sending the interface resource update message by the second system to the first system when the second system is in a wake-up state; When the second system is in a wake-up state, in response to receiving a language update broadcast, acquiring, by the second system, first application information of a first application, where a first interface resource corresponding to the first application is stored in the first storage space; sending, by the second system to the first system, a first interface resource update message including the first application information and an updated first interface resource; updating, by the first system, the interface resource stored in the first storage space based on the interface resource update message; storing, by the first system, the first application information and the updated first interface resource in the first storage space in association with each other; 6. The method of claim 5, wherein the application interface is displayed on the display device.

7. Obtaining the first application information of the first application by the second system includes: sending a query message by the second system to the first system; transmitting, by the first system, the first application information of the first application to the second system, and deleting the first interface resource corresponding to the first application from the first storage space; 7. The method of claim 6, wherein the application interface is displayed.

8. Obtaining the first application information of the first application by the second system includes: obtaining, by the second system, the first application information of the first application from a second storage space corresponding to the second system; storing, by the first system, the first application information and the updated first interface resource in the first storage space in association with each other, In response to identifying that the first interface resource update message includes a forced update identifier, the first system deletes the interface resource stored in the first storage space, and associates the first application information with the updated first interface resource in the first storage space.

7. The method of claim 6, wherein the application interface is displayed.

9. sending the interface resource update message by the second system to the first system when the second system is in a wake-up state; When the second system is in a wake-up state, in response to monitoring an activation configuration update message of a second application, acquiring, by the second system, second application information and second interface resources of the second application, wherein the activation configuration update message is used to indicate a change in an activation configuration of the second application; sending, by the second system to the first system, a second interface resource update message including an update configuration, the second application information, and the second interface resource; updating, by the first system, the interface resource stored in the first storage space based on the interface resource update message; updating, by the first system, the second interface resource corresponding to the second application information in the first storage space based on the update form; 6. The method of claim 5, wherein the application interface is displayed on the display device.

10. updating the second interface resource corresponding to the second application information in the first storage space by the first system based on the update form, in response to the update type being addition, storing, by the first system, the second application information and the second interface resource in association with each other in the first storage space; and in response to the update type being deletion, deleting, by the first system, the second application information and the second interface resource from the first storage space.

10. The method of claim 9, wherein the application interface is displayed on the display device.

11. The method for displaying an application interface includes: determining that an update conflict exists in response to the update type being addition and the second application information being stored in the first storage space; and determining that an update conflict exists in response to the update mode being deletion, the second application information being stored in the first storage space, and the second application information being used in an activation mode other than a deletion waiting activation mode; If an update conflict exists, the second interface resource in the first storage space is not updated. The method of claim 10, wherein the application interface is displayed.

12. updating the second interface resource corresponding to the second application information in the first storage space by the first system based on the update form, In response to identifying that the second interface resource update message does not include a forced update identifier and that there is no update conflict, updating, by the first system, the second interface resource corresponding to the second application information in the first storage space based on the update configuration; The method for displaying an application interface includes: and updating, by the first system, the second interface resource corresponding to the second application information in the first storage space based on the update form in response to identifying that the second interface resource update message includes the forced update identifier.

10. The method of claim 9, wherein the application interface is displayed on the display device.

13. displaying, by the second system, an interface of the target application and executing the target application in response to the second system completing the rendering of the interface of the target application; In response to the second system completing the rendering of the interface of the target application, sending a switch instruction by the second system to the first system to instruct the first system to transfer a display authority of a graphical user interface (GUI); and in response to the second system obtaining the authorization to display the GUI, displaying, by the second system, the interface of the target application and executing the target application. The application interface according to any one of claims 1 to 12, How the interface is displayed.

14. The target application is an application that cannot be launched or executed by the first system, and the method of displaying the application interface includes: and when the first system is in a wake-up state and the second system is in a sleep state, waking up the second system in a sleep state in response to the application launch instruction of the target application, and launching and executing the target application by the second system. A method for displaying an application interface according to any one of claims 1 to 13.

15. the interface of the target application rendered by the first system and the interface of the target application rendered by the second system are the same or different; A method for displaying an application interface according to any one of claims 1 to 14.

16. Rendering an interface of the target application by the second system includes: during launching of the target application by the second system, rendering an interface of the target application by the second system; A method for displaying an application interface according to any one of claims 1 to 15.

17. A wearable device comprising a processor and a memory, At least one instruction is stored in the memory, and the at least one instruction is executed by the processor to realize the method for displaying an application interface according to any one of claims 1 to 16. A wearable device characterized by:

18. A computer-readable storage medium having stored thereon at least one instruction, comprising: The at least one instruction is used to implement the method for displaying an application interface according to any one of claims 1 to 16 when executed by a processor. A computer-readable storage medium comprising:

Images