Application interface display method, apparatus, device, and storage medium

Abstract

A method, an apparatus, a device, and a storage medium for displaying an application interface in the field of wearable devices are provided. The method includes, when a first system is in a wake-up state and a second system is in a sleep state, rendering and displaying an interface of the target application by the first system in response to an application launch instruction of the target application (301); rendering the interface of the target application by the second system in response to switching the second system from the sleep state to the wake-up state (302); and displaying the interface of the target application and executing the target application by the second system in response to completion of rendering the interface of the target application by the second system (303). Displaying the application launch effect by the first system can visually improve the application launch speed and reduce the display delay of the application screen during system switching. Pre-displaying the application launch effect by the first system can visually improve the application launch speed and reduce the display delay of the application screen during system switching.

Description

[Technical field]

[0001] REFERENCE TO RELATED APPLICATIONS This application claims priority to China Patent Application No. 202110366882.3, filed on April 6, 2021, entitled "Application interface display method, apparatus, device, and storage medium," the entire contents of which are incorporated herein by reference.

[0002] TECHNICAL FIELD The embodiments of the present application relate to the field of wearable devices, and in particular to a method, an apparatus, a device, and a storage medium for displaying an application interface. [Background technology]

[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] For example, if the wearable device is a smart watch, a user can use the wearable device to check the time, and can use an application program 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 the embodiments of the present application, a method, apparatus, device and storage medium for displaying an application interface are provided, the technical solutions of which are as follows:

[0006] In one aspect, an embodiment of the present application provides a method for displaying an application interface, the method being used in 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, in response to an application launch indication of the target application, rendering and displaying, by the first system, an interface of the target application; Rendering an interface of the target application by the second system in response to the second system switching from a sleep state to a wake-up state; Responsive to completion of the rendering of the target application's interface by the second system, displaying, by the second system, the target application's interface and executing the target application.

[0007] In another aspect, an embodiment of the present application provides an application interface display apparatus for use in a wearable device supporting execution of a first system and a second system, the apparatus comprising a first system module and a second system module. the first system module is configured to, 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, render and display an interface of the target application by the first system; the second system module is configured to render an interface of the target application by the second system in response to the second system switching from a sleep state to a wake-up state; The second system module is further configured to display, by the second system, the interface of the target application and execute the target application in response to completion of the rendering of the interface of the target application by the second system.

[0008] In another aspect, an embodiment of the present application provides a wearable device, the wearable device comprising a processor and a memory, wherein 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 the above aspect.

[0009] In another aspect, an embodiment of the present application provides a computer-readable storage medium, which stores at least one instruction, and the at least one instruction is used to implement the method for displaying an application interface according to the above aspect by being executed by a processor.

[0010] In another aspect, an embodiment of the present application provides a computer program product or a computer program, the computer program product or the computer program including computer instructions stored in a computer-readable storage medium, a processor of a computing device reading the computer instructions from the computer-readable storage medium, and the processor executing the computer instructions to cause the computing device to perform the method of displaying an application interface according to the above aspect. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a schematic diagram illustrating a dual-core communication software framework corresponding to a second processor according to one exemplary embodiment of the present application. [Diagram 2] FIG. 2 is a schematic diagram illustrating a dual-core communications software framework corresponding to a first processor according to an exemplary embodiment of the present application. [Diagram 3] FIG. 3 is a flowchart illustrating a method for displaying an application interface according to an exemplary embodiment of the present application. [Figure 4]FIG. 4 is a schematic diagram showing an interface of an application launch process in a smart watch according to an exemplary embodiment of the present application. [Diagram 5] FIG. 5 is a flowchart illustrating a method for displaying an application interface according to an exemplary embodiment of the present application. [Figure 6] FIG. 6 is a schematic implementation diagram of an interface resource update process according to an exemplary embodiment of the present application. [Figure 7] FIG. 7 is a flow chart illustrating an interface resource update process according to an exemplary embodiment of the present application. [Figure 8] FIG. 8 is a sequence diagram of system interactions in an interface resource update process according to an exemplary embodiment of the present application. [Figure 9] FIG. 9 is a flowchart illustrating an interface resource update process according to another exemplary embodiment of the present application. [Figure 10] FIG. 10 is a sequence diagram of system interactions in an interface resource update process according to another exemplary embodiment of the present application. [Figure 11] FIG. 11 is a block diagram illustrating the structure of a display device of an application interface according to an exemplary embodiment of the present application. [Figure 12] FIG. 12 is a block diagram illustrating the structure of a wearable device according to one exemplary embodiment of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] In order to make the objectives, technical solutions and advantages of the present application clearer, the embodiments of the present application are further described in detail below with reference to the drawings.

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

[0014] In the related art, a single processor is installed in a wearable device, and an operating system is executed in the processor to process all system events that occur during the operation of the device, so the processor must have high data processing capabilities and must be kept in an operating state during the operation of the device. However, during daily use, the wearable device only needs to realize functions that require low processing performance in many cases. For example, a smart watch or a smart bracelet only needs to display the time and prompt messages in many cases. Therefore, if the processor keeps in an operating state for a long time, it will increase the power consumption of the wearable device without improving its performance, and the continuous use time of the wearable device will be shortened.

[0015] In order to ensure the performance of the wearable device while reducing the power consumption of the wearable device, in one possible embodiment, the wearable device is provided with at least a first processor and a second processor with different processing performance and power consumption, the first processor runs a first system, and the second processor runs 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 operation of the wearable device, the first system is executed by the low power consumption processor to process events with low processing performance requirements, and the high power consumption processor is kept in a sleep state (and accordingly, the second system executed by the high power consumption processor is in a sleep state). This allows the basic functions of the wearable device to be realized while reducing the power consumption of the wearable device. When an event with high processing performance requirements occurs (e.g., when an application program is started), the high power consumption processor 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] Also, it is necessary that it takes a certain time (at least 200ms to 300ms) for a processor with high power consumption to switch from a sleep state to a wake-up state. Therefore, in order to reduce the display delay of an application screen during application startup, a mechanism of pre-display of a start-up effect is introduced in this application. Before the processor with high power consumption is woken up, a first system executed by a processor with low power consumption draws and displays an application interface. After the processor with high power consumption is woken up, a second system executed by a processor with high power consumption displays an application interface, executes an application, and pre-displays the application start-up effect. This visually improves the startup speed of the application and reduces the display delay of the application screen during system switching.

[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 realize system communication (also called dual-core communication). In one possible application scenario, the first system is a Real Time Operating System (RTOS) running on a Micro Controller Unit (MCU), and the second system is an Android operating system running on a central processing unit (CPU).

[0019] As shown in Fig. 1, a dual-core communication software framework of an Android operating system according to one exemplary embodiment of the present application is illustrated. The dual-core communication software framework is developed according to the design principle of "low coupling, high reliability, high redundancy" and includes a kernel module, a Hardware Abstraction Layer (HAL) 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 desktop launcher, setting, and system user interface (SystemUI). The FrameworkAPI module includes management modules such as microcontroller unit management (MCU Manager), sensor management, and location manager. The framework service module includes service modules such as MCU Manager Service, system sensor management, and location manager service. The native service module includes service modules such as data call control (dcc) service, sensor service, and the like. The HIDL module includes modules such as sensor hardware abstraction layer (Sensor HAL), global positioning system hardware abstraction layer (GPS HAL), and the like. The kernel module includes DCC transfer drivers such as dcc_datah, dcc_data, Mcu_sensor, Mcu_gps, and Mcu_factory.

[0021] The transmission layer is an interface layer connecting the upper and lower layers in the dual-core communication software framework, 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 application scenarios. The application layer, as a service provider, responds to human-machine interaction, transmits data generated during human-machine interaction through the transmission layer, and responds to external data requests.

[0022] The RTOS is designed using the principle of parity. Taking the wearable device as an example that 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 RTOS dual-core communication software framework 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, Aios (advanced input output system), AsycEvent, etc. It also includes hardware abstraction modules such as HAL, Screen / touch panel (TP), Audio, Global Positioning System (GPS), sensors, Keypad, Motor, etc.The platform layer includes the board support package (BSP) and low level drivers. The BSP includes the screen / touch panel, keys, GPS, codec, sensors, flash, motors, pseudo static random access memory (PSRAM), etc. The low level drivers include the universal asynchronous receiver / transmitter (Uart), analog-to-digital converter (ADC), general purpose input output (GPIO), serial peripheral interface (SPI), integrated circuit (Inter-Integrated Circuit (I2C), input / output system (IOS), pulse code modulation (PCM), inter-IC sound (I2S), and hardware timer (HWTimer).

[0025] It should be noted that the above dual-core communication software framework is described as an example only, and those skilled in the art can add, delete or amend the above framework according to actual needs, and the embodiment of the present application does not limit the specific structure of the dual-core communication software framework.

[0026] Referring to Fig. 3, Fig. 3 is a flowchart illustrating a method for displaying an application interface according to an exemplary embodiment of the present application. In this embodiment, the method is described as being applied 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 a wake-up state and the second system is in a sleep state, in response to an application launch instruction of the target application, the first system renders and displays an interface of the target application.

[0028] In one possible embodiment, the wearable device comprises 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 power and the processing speed of the first processor are lower than those of the second processor), and the power consumption of the first processor is lower than that of the second processor. Accordingly, the second system (executed by the second processor) can process events processed by the first system (executed by the first processor), but the first system cannot necessarily process events processed by the second system.

[0029] In another possible embodiment, the wearable device may comprise a single processor, the first system and the second system each running on a different core of the processor, the processing performance of the core running the second system being higher than the processing performance of the core running the first system.

[0030] For example, the wearable device is 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 and low interaction, such as watch face display, watch face interface switching, and notification and message display. The events that can be processed by the second system include scenarios with high requirements for processing performance and high interaction, such as incoming calls, application launch, watch face editing, and function settings.

[0031] In one possible embodiment, the operation modes of the wearable device include a performance mode, a mixed mode, and a low power mode. In the performance mode, both the second processor and the first processor remain in an awake state (correspondingly, both the first system and the second system are in an awake state). In the low power mode, only the first processor remains in an awake state, and the second processor is in an off state (i.e., the first system is in an awake state and the second system is in an off state). In the mixed mode, when processing an event by the first system, the second processor is in a standby state and can be switched between a sleep state and a wake state (i.e., when the first system is in an awake state, the second system may be in an awake state or in 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) so that it 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, the system-related data is written from the hard disk to the memory.

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

[0034] When the first system is in a wake-up state and the second system is in a sleep state, upon receiving an application launch instruction for the target application, it indicates that the target application needs to be launched and executed, and since the first system does not have the ability to execute the target application, it needs to wake up the second system in the sleep state, and the target application is launched and executed by the second system.

[0035] However, since the wake-up process of the second system takes a certain amount of time (at least 200ms to 300ms), a phenomenon occurs in which there is no response for a while after triggering the launch of the target application (specifically, it is necessary to wait for a certain amount of time until the application screen appears), which affects the user experience. In an embodiment 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 launch instruction for the target application while the first system is running, the first system first renders and displays the interface of the target application (the first system does not launch or execute the target application, but is only responsible for rendering the graphic interface).

[0036] Optionally, the application launch instruction is triggered by a shortcut key (e.g., a physical key) or a widget of the first system. The target application may be a health monitoring application, an instant communication 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 moving image (e.g., the starting moving image of the application launch process). In the embodiment of the present application, the trigger manner of the application launch 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, it can draw and display the interface immediately after receiving the application launch instruction, i.e., it can display the interface of the target application immediately after the launch of the target application is triggered, thereby visually improving the launch speed of the application.

[0038] Illustratively, as shown in FIG. 4, take the wearable device as an example, a smart watch, in which an RTOS (executed by a first processor) and an Android system (executed by a second processor) are installed. When the first processor is in a wake-up state and the second processor is in a sleep state, the smart watch displays a watch face 41 by the RTOS, and makes the Android system sleep to keep low power consumption. When a user needs to check the sports data through a sports application, he or she can quickly launch the sports application by double-clicking a physical key. Upon receiving an instruction to launch the sports application, the RTOS draws and displays an application interface 42 of the sports application.

[0039] Step 302: Render an interface of the target application by the second system in response to switching the second system from a sleep state to a wake-up state.

[0040] In one possible embodiment, while the first system is drawing and displaying the interface, the second system is synchronously woken up, i.e., the second processor is switched from a sleep state to a wake-up state. After the second system is switched to the wake-up state, the target application is launched and executed by the second system. During the launch 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 the launch of the application, and the interface drawn by the second system is the first frame of the application interface after the transition animation is completed. Of course, the first system and the second system can also draw other interfaces belonging to the target application, and the specific interface drawn by the first system and the specific interface drawn by the second system are not limited in this embodiment.

[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 second system completing the rendering of the interface of the target application, the second system displays the interface of the target application and executes the target application.

[0044] After the second system has completed rendering the interface, the system executed 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] Alternatively, after switching to the second system, the first system may continue to remain in a wake-up state (which consumes less power and has less impact on continuous usage time) or the first system may be switched to a sleep state, and this embodiment is not limited thereto.

[0046] 4, the Android system is switched from a sleep state to a wake-up state while the application interface 42 is displayed by the RTOS. After the Android system is woken up (e.g., after 200 ms), the system executed by the smartwatch is switched from the RTOS to the Android system, and the application interface 42 is displayed by the Android system and the sports application is executed.

[0047] Optionally, after the second system completes the event processing (e.g., closes the target application and returns to the watch face), the second processor is switched to a sleep state again and switches to the first system to process the event through the first system, so that the wearable device maintains high performance (but high power consumption) in few scenarios and maintains low power consumption (but low performance) in many scenarios, further reducing the power consumption of the wearable device and extending the continuous use time of the wearable device.

[0048] As described above, in an embodiment of the present application, in a wearable device supporting dual systems, when a first system is in an operating state and a second system is in a sleeping state, upon receiving an application startup instruction for a target application, the first system first renders 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 of an embodiment of the present application, the first system pre-displays the startup effect of the application, thereby visually improving the startup speed of the application and reducing the display delay of the application screen during system switching.

[0049] Optionally, rendering and displaying an interface of the target application by the first system includes: Obtaining, by a 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; Rendering and displaying an interface of the target application by the first system based on the target interface resources.

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

[0051] Optionally, the method further comprises: sending an interface resource update message by the second system to the first system when the second system is in a wake-up state; The method further includes updating the interface resources stored in the first storage space by the first system based on the interface resource update message.

[0052] Optionally, when the second system is in a wake-up state, sending an interface resource update message by the second system to the first system includes: When the second system is in a wake-up state, in response to receiving the language update broadcast, first application information of the first application is obtained by the second system, a first interface resource corresponding to the first application is stored in a first storage space, and a first interface resource update message is sent by the second system to the first system, the first interface resource update message including the first application information and the updated first interface resource. Updating the interface resource stored in the first storage space by the first system based on the interface resource update message; The first system stores the first application information and the updated first interface resource in association with each other in the first storage space.

[0053] Optionally, 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; Sending, by the first system, first application information of the first application to the second system, and deleting, from the first storage space, a first interface resource corresponding to the first application.

[0054] Optionally, obtaining the first application information of the first application by the second system includes: The method includes obtaining, by the second system, first application information of the first application from a second storage space, which is a storage space corresponding to the second system. and 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 memory space, and associates first application information with the updated first interface resource and stores it in the first memory space.

[0055] Optionally, when the second system is in a wake-up state, sending an interface resource update message by the second system to the first system includes: When the second system is in a wake-up state, in response to monitoring an activation configuration update message of the second application, the second system obtains second application information and second interface resources of the second application, the activation configuration update message is used to indicate a change in an activation configuration of the second application, and the second system sends a second interface resource update message to the first system, the second system including the update configuration, the second application information, and the second interface resources. Updating the interface resource stored in the first storage space by the first system based on the interface resource update message; and updating, by the first system, a second interface resource corresponding to the second application information in the first storage space based on the update form.

[0056] Optionally, updating, by the first system, a second interface resource corresponding to the second application information in the first storage space based on an update form; in response to the update type being addition, storing, by the first system, second application information and a second interface resource in association with each other in the first storage space; 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.

[0057] Optionally, the method further comprises: 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; 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 the activation mode waiting for deletion; If an update conflict exists, the second interface resource in the first storage space is not updated.

[0058] Optionally, updating, by the first system, a second interface resource corresponding to the second application information in the first storage space based on an update form; In response to identifying that the second interface resource update message does not include a forced update identifier and that no update conflict exists, updating the second interface resource corresponding to the second application information in the first memory space by the first system based on the update type. The above method is The method further includes, in response to identifying that the second interface resource update message includes a forced update identifier, updating, by the first system, a second interface resource corresponding to the second application information in the first memory space based on an update type.

[0059] Optionally, the first storage space is used to store interface resources corresponding to applications supported to be launched on the first system; The manner in which the application is launched in the first system includes at least one of launching by a shortcut key and launching by a widget in the first system.

[0060] Optionally, in response to completion of rendering of the interface of the target application by the second system, displaying, by the second system, the interface of the target application and executing the target application, sending, in response to the second system completing the rendering of the interface of the target application, a switch instruction by the second system to the first system to instruct the first system to transfer display authority of a graphical user interface (GUI); In response to the second system obtaining permission to display the GUI, displaying, by the second system, an interface of the target application and executing the target application.

[0061] Optionally, the wearable device comprises a first processor and a second processor, the power consumption of the second processor being greater than the power consumption of the first processor, the first system being a system executed by the first processor, and the second system being 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, and the storage space corresponding to the second system is much larger than that corresponding to the first system, because the first system is only responsible for processing simple events, and the second system needs to process complex events. 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. Upon receiving an application launch instruction, the first system draws the application interface according to the interface resources in the storage space. The following description will be given using an exemplary embodiment.

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

[0064] Step 501: When a first system is in a wake-up state and a 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 memory space, which is a memory space corresponding to the first system.

[0065] In an embodiment of the present application, the first system corresponds to a first storage space, and the first storage space stores interface resources corresponding to at least one application. The interface resources refer to resources required for drawing an application interface, and may include text resources, image resources, video resources, special-effect resources, interface-layout resources, etc., and the specific contents included in the interface resources are not limited in this embodiment.

[0066] In one possible embodiment, the first memory space stores interface resources corresponding to each application in the second system, for example, if a sports application, a health monitoring application, an alarm application, and an instant communication application are installed in the second system, the first memory space stores interface resources corresponding to each of the four applications.

[0067] Due to the limited capacity of the first storage space, not 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 by the first system). Therefore, in another possible embodiment, the first storage space is used to store interface resources corresponding to applications supported to be launched by the first system, thereby reducing the storage space occupied by the interface resources while realizing seamless system switching.

[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 an application is set in the first system, the application belongs to the applications supported to be launched in the first system, and / or if an 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 manner of launching the application on the first system includes at least one of launching via a shortcut key and launching via a widget on the first system.

[0070] The manner in which an application is launched in the first system via a shortcut key can be set by the user himself, for example, launching a specific application by double-clicking a physical key or by pressing and holding a physical key. A widget can be added to the first system by the user himself, for example, a widget corresponding to a health monitor application is added to a watch face so that the user can launch the health monitor application by clicking on a widget displayed in the first system.

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

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

[0073] Optionally, the application information includes at least one of an application package name and an application activity name. If the application has only a single functional interface, the application information includes the application package name. If the 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 an application activity name (corresponding to the specific functional interface).

[0074] When receiving an application launch instruction of a target application, a first system obtains target application information corresponding to the target application, and the first system obtains a target interface resource from a first storage space based on the target application information, where 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 matching the target application information based on the target application information, and identifies the searched interface resources as target interface resources corresponding to the target application.

[0076] In an illustrative 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] If the application package name of the target application is obtained as sport_app, the first system identifies interface resource file A in the first storage space as the target interface resource. If the application package name of the target application is obtained as health_app, the first system identifies interface resource file B in the first storage space as the target interface resource.

[0079] Step 502: Render and display an interface of the target application by the first system based on the target interface resource.

[0080] Furthermore, upon obtaining the target interface resource, the first system immediately renders and displays the interface in real time.

[0081] Optionally, during rendering of an interface by the first system, in addition to needing to utilize target interface resources, other data such as time data, sensor data (e.g., pedometer data), etc., needing to be utilized, so as to ensure the accuracy of the content in the rendered interface.

[0082] In an illustrative example, the target interface resource corresponding to the sports application obtained by the first system includes an image resource, a text resource, and an interface layout resource. The first system draws the image resource and the text resource at a corresponding interface position according to an interface element layout manner indicated by the interface layout resource, and renders the current time and the pedometer data into the interface to obtain an application interface of the sports application.

[0083] Step 503: Render an interface of the target application by the second system in response to the second system switching from a sleep state to a wake-up state.

[0084] For the embodiment 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 rendering of the interface of the target application, the second system sends a switch instruction to the first system to instruct the first system to transfer display authority of a graphical user interface (GUI) to the first system.

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

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

[0088] After obtaining the GUI display authority, the second system displays the interface of the target application whose rendering is completed, and executes the target application, so that the interface of the target application is displayed on the wearable device accordingly.

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

[0090] In addition, the first memory space stores only the interface resources of applications that are supported to be launched on the first system, thereby realizing seamless system switching while reducing the memory space occupied by the interface resources and reducing the capacity needs of the first memory space.

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

[0092] Taking an example where 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 an interface resource update event (including events such as language update, widget update, and shortcut key update) exists in the application layer, the application layer pre-sets the updated interface resource to the framework resource Android application package (APK) corresponding to the Android system.

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

[0094] For different update scenarios, the update process of interface resources through 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 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. Below, the interface resource update process in different update scenarios will be described using respective embodiments.

[0095] Referring to Figure 7, Figure 7 is a flow chart showing an interface resource update process according to an exemplary embodiment of the present application. In this embodiment, the method is described as being applied to a wearable device. 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, first application information of a first application is obtained by the second system. A first interface resource corresponding to the first application is stored in a first memory 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 user to switch to English.

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

[0099] Regarding the manner of obtaining the first application information, in one possible embodiment, the first storage space stores a mapping relationship between the first application information and the first interface resource, so that the second system can obtain the first application information through the first system. Optionally, this step can include the following steps:

[0100] First, the second system sends a query message to the first system.

[0101] Optionally, the second system sends a query message to the first system through the kernel layer dual-core communication module to request the first system to query the first application information stored in the first storage space. In response, the first system obtains the stored first application information from the first storage space upon receiving the query message.

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

[0103] Second, the first system sends 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 the first system queries the first application information of each first application, it sends a query result including the first application information to the second system via the dual-core communication module in the kernel layer.

[0105] Combined with the data shown in Table 1 in 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 update, the originally stored interface resource becomes invalid, so in one possible embodiment, the first system deletes the first interface resource corresponding to the first application from the first memory space to release the first memory space and ensure the accuracy of subsequent interface resource updates.

[0107] Optionally, the query message sent by the second system includes a pre-set identifier. If the query message includes the pre-set identifier, the first system determines that an interface resource needs to be updated due to the change in the system language, and deletes the first interface resource stored in the first storage space. In conjunction 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 storage space.

[0108] Exemplarily, as shown in FIG. 8, the RTOS deletes the first interface resource stored in the first memory space while feeding back the query result to the Android system.

[0109] Step 702: Send a first interface resource update message by the second system to the first system, the message including the first application information and the updated first interface resource.

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

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

[0112] Optionally, the character resource included in the first interface resource after the update is different from the character resource included in the first interface resource before the update, for example, the character resource after the update is an English version of the first application, and the character resource before the update is a Chinese version of the first application.

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

[0114] In one possible embodiment, the first interface resource update message may include the following fields: 1. path for representing the update path: In this embodiment, the value of the path field represents that the system language update triggers the interface resource update. 2. Action for representing the update manner of the interface resource In this embodiment, the value of the action field represents the switching of the interface resource. 3.packagename which is the application package name. 4. data, the updated interface resource. 5. Extra for representing whether to forcibly update interface resources: In this embodiment, the value of the extra field represents to forcibly update interface resources.

[0115] The first interface resource update message may include other fields, and in this embodiment, the first interface resource update message is described as including the above fields only as an example, but is not limited thereto.

[0116] Exemplarily, as shown in FIG. 8, after receiving the query result, the Android system obtains an updated first interface resource based on the query result, and sends a first interface resource update message to the RTOS based on the first interface resource.

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

[0118] Upon receiving the first interface resource update message, the first system associates and stores the first application information with the updated first interface resource, and during subsequent system switching, the first system can render and display an application interface based on the updated interface resource, and ensure that the language adopted by the displayed application interface and the system language are consistent.

[0119] Combined with the examples in the above steps, after the first system updates the interface resource based on the first interface resource update message, the mapping relationship between the application information and the interface resource 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 an update completion notification to the second system to notify the second system that the interface resource update is completed. If the second system does not receive the update completion notification within a preset time, it sends a first interface resource update message to the first system again.

[0122] Exemplarily, as shown in FIG. 8, after the RTOS updates the first interface resource, it sends an update completion notification to the Android system.

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

[0124] In response to the above, when the first system identifies that the first interface resource update message includes a forced update identifier (e.g., set in an extra field in the first interface update message), it deletes the interface resources stored in the first memory space, associates the first application information with the updated first interface resources and stores them in the first memory space, thereby avoiding storing two sets of interface resources for the same application.

[0125] In this embodiment, when updating the system language, the second system obtains first application information of each first application, obtains updated first interface resources according to the first application information, and sends the updated first interface resources to the first system. The first system updates the first interface resources stored in the first storage space, and ensures that the language of the application interface displayed on the first system is consistent with the system language during subsequent system switching.

[0126] Referring to Figure 9, Figure 9 is a flowchart illustrating an interface resource update process according to another exemplary embodiment of the present application. In this embodiment, the method is described as being applied 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 second application information and second interface resources of the second application. The start-up manner update message is used to indicate a change in the start-up manner of the second application.

[0128] In order to improve the efficiency of launching an application, a user may set a quick start-up manner for an application in the second system so that the application in the second system can be launched by the first system. Setting the quick start-up manner may include adding a widget of the application to the first system and setting a shortcut key for launching the application.

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

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

[0131] For example, when the second application is set to be started by a widget, the target start mode is widget start and the update mode is addition.When the second application is set to be started by a shortcut key, the target start mode is shortcut key start and the update mode is deletion.

[0132] Further, the second system obtains second application information and second interface resources corresponding to the second application. The second system can obtain the second interface resources from the second storage space according to the application information of the second application in the launch mode update message.

[0133] Optionally, if the update mode indicated by the activation mode update message is addition, the second system obtains second application information and second interface resources, and if the update mode indicated by the activation mode update message is deletion, the second system obtains only second application information.

[0134] Exemplarily, as shown in FIG. 10, when the Android system monitors the launch mode update message (including ACTION_SHORTCUT_SETTING_CHANGED and ACTION_WIDGET_CHANGED) of the second application, it obtains the second interface resource of the second application.

[0135] Step 902: Send a second interface resource update message by the second system to the first system, the second interface resource update message including an update configuration, second application information, and a second interface resource.

[0136] According to the acquired second interface resource, the second system sends a second interface resource update message to the first system through the dual-core communication module, the second interface resource update message including the second application information and the second interface resource, and further including a target activation 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 the update path: In this embodiment, the value of the path field represents that the interface resource update is triggered by the update of the fast start mode (including the update of the widget and the update of the shortcut key). 2. Action for representing the update manner of an interface resource In this embodiment, the value of the action field represents adding an interface resource or deleting an interface resource. 3.packagename which is the application package name. 4. activityname which is the application activity name to point to a specific application interface of the application. 5. data, the updated interface resource. 6. Extra to indicate whether to force an update of interface resources.

[0138] The second interface resource update message may include other fields, and in this embodiment, the second interface resource update message is described as including the above fields only as an example, but 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 to instruct the RTOS to update the interface resource stored in the first memory space.

[0140] Step 903: Update a second interface resource corresponding to the second application information in the first storage space by the first system according to the update mode.

[0141] In one possible embodiment, the first system updates a 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 a specific form of the interface resource update, in some embodiments, when the update form is addition, the wearable device causes the first system to associate the second application information with the second interface resource and store them in the first memory space, and when the update form is deletion, the wearable device causes the first system to delete the second application information and the second interface resource from the first memory space.

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

[0144] For example, if a second interface resource of a second application is stored in the first memory space, and the second interface resource update message instructs adding a second interface resource of the second application (which can accommodate a different fast startup mode), directly adding the second interface resource to the first memory space would result in duplicate storage of the interface resource and waste of memory space.

[0145] In another example, when a second interface resource of a second application is stored in a first memory space and the second application is supported to be launched in at least two different fast start-up forms, if the second interface resource update message instructs deleting the second interface resource of the second application (deleting one of the fast start-up forms), directly deleting the second interface resource from the first memory space will result in the second application being launched only in the other fast start-up form, resulting in the first system being unable to render 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 type and the second application information. If there is no update collision, the first system updates the interface resource in the first storage space based on the update type 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 of detecting whether an update conflict exists, in one possible embodiment, when the update form is 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 determines that no update conflict exists, and associates the second application information with the second interface resource and stores them in the first storage space.

[0148] In an illustrative example, when the mapping relationship between the application information and the interface resource in the first storage space is as shown in Table 1, if the update type included in the second interface resource update message is addition and the included second application information is "application package name: alarm_app" (alarm application), it is determined that there is no update conflict because the second application information is not included in the first storage space, 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 as shown in Table 3.

[0149] [Table 3]

[0150] Optionally, in response to the update type being additive and second application information being stored in the first memory space, the first system determines that an update conflict exists and does not update the second interface resource in the first memory space.

[0151] Optionally, when the update type is addition, if it is determined that an update conflict exists, the first system adds a corresponding activation type waiting to be added to the second application information.

[0152] For example, in conjunction with the data shown in Table 3, if the update form contained in the second interface resource update message is addition and the included second application information is "application package name: sport_app", since the second application information is included in the first memory space, it is determined that an update conflict exists, and the interface resource file A is not updated, and only the target launch form "shortcut key" in the second interface resource update message is added to sport_app.

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

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

[0155] [Table 4]

[0156] If the update type included in the second interface resource update message is deletion, and the included second application information is "application package name: health_app", and the activation type 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 between the application information, interface resource, and activation type in the first storage space is shown in Table 5.

[0157] [Table 5]

[0158] Optionally, in response to the update type being deletion, and second application information being stored in the first memory space, and the second application information being used by an activation type other than the activation type awaiting deletion, the first system determines that an update conflict exists and does not update the second interface resource in the first memory space.

[0159] Optionally, when the update type is deletion, if it determines that an update conflict exists, the first system deletes the corresponding deletion-awaiting activation type for the second application information.

[0160] For example, in conjunction with the data shown in Table 4, if the update type included in the second interface resource update message is deletion and the included second application information is "application package name: health_app", since the second application information is included in the first memory space, it is determined that an update conflict exists, and the interface resource file A is not updated, and only the launch type "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 may indicate 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 second interface resource update message does not include a forced update identifier, the first system detects an update collision based on the update type and the second application information, and in response to recognizing that the second interface resource update message includes a forced update identifier, the first system updates a second interface resource corresponding to the second application information in the first storage space based on the update type.

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

[0164] 10, after the RTOS receives the second interface resource update message, if the second interface resource update message includes a forced update identifier, the RTOS system directly updates (adds or deletes) the interface resource. If the second interface resource update message does not include a forced update identifier, the RTOS system updates (adds or deletes) the interface resource according to a condition (i.e., if there is no update conflict), and after updating the second interface resource, sends an update completion notification to the Android system.

[0165] In this embodiment, when the startup mode of the second application is updated, the second system obtains second application information of the second application, obtains a 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, and if there is an update conflict, the second interface resource is not updated. This ensures normal operation of the function of seamless system switching after the startup mode is updated.

[0166] It should be noted that in the above embodiments, only the application interface display process in a dual-core dual-system device is described as an example. In other possible application scenarios, a single-core dual-system device (e.g., a processor runs different systems on different cores) can also adopt the proposals in the embodiments of the present application to realize the display of an application interface during system switching, which will not be described in detail.

[0167] 11, which is a block diagram showing the structure of a display device of an application interface according to one embodiment of the present application. The device can be implemented as a whole 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 render and display an interface of a target application by the first system in response to an application launch 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 render an interface of the target application by the second system in response to switching the second system from a sleep state to a wake-up state. The second system module 1102 is further configured to display, by the second system, the interface of the target application and execute the target application in response to completion of the rendering of the interface of the target application by the second system.

[0168] Optionally, the first system module 1101 is Obtaining, by the first system, a target interface resource corresponding to the target application from a first storage space, which is a storage space corresponding to the first system; The first system is configured to render and display an interface of the target application based on the target interface resource.

[0169] Optionally, the first system module 1101 specifically includes: Obtaining target application information corresponding to the target application by a first system; The target interface resource is configured to be obtained 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 by the second system to the first 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, the second system module 1102 may be specifically configured to obtain, by the second system, first application information of the first application in response to receiving the language update broadcast when the second system is in a wake-up state, and a first interface resource corresponding to the first application is stored in the first storage space; The second system module 1102 is configured to send, by the second system to the first system, a first interface resource update message including the first application information and the updated first interface resource. The first system module 1101 is specifically configured to store, by the first system, the first application information and the updated first interface resource in a first storage space in association with each other.

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

[0173] Optionally, the second system module 1102 is specifically configured to obtain, by the second system, first application information of the first application from a second memory space, which is a memory space corresponding to the second system. The first system module 1101 is specifically configured to, in response to identifying that the first interface resource update message includes a forced update identifier, delete the interface resource stored in the first memory space by the first system, and associate the first application information with the updated first interface resource and store it in the first memory space.

[0174] Optionally, the second system module 1102 may be specifically When the second system is in a wake-up state, the second system is configured to obtain second application information and second interface resources of the second application in response to monitoring an activation mode update message of the second application, and the activation mode update message is used to indicate a change in the activation mode of the second application. The second system module 1102 is configured to send, by the second system to the first system, a second interface resource update message including the update configuration, the second application information, and the second interface resource. The first system module 1101 is specifically configured to update, by the first system, a second interface resource corresponding to the second application information in the first storage space according to an update mode.

[0175] Optionally, the first system module 1101 specifically includes: In response to the update type being addition, storing, by the first system, second application information and a second interface resource in association with each other in the first storage space; In response to the update type being deletion, the first system is configured to delete the second application information and the second interface resource from the first storage space.

[0176] Optionally, the first system module 1101 further comprises: 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; determining that an update collision exists in response to an update mode being a deletion, second application information being stored in the first storage space, and the second application information being used in an activation mode other than the activation mode waiting for deletion; If an update conflict exists, the second interface resource in the first storage space is not updated.

[0177] Optionally, the first system module 1101 further comprises: In response to identifying that the second interface resource update message does not include a forced update identifier and no update conflict exists, update, by the first system, a second interface resource corresponding to the second application information in the first storage space according to an update form; In response to identifying that the second interface resource update message includes a forced update identifier, the first system is configured to update the second interface resource corresponding to the second application information in the first memory space based on the update type.

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

[0179] Optionally, the second system module 1102 further comprises: sending, by the second system, a switch instruction to the first system in response to the second system completing the rendering of the interface of the target application, the switch instruction instructing the first system to transfer a display authority of a graphical user interface (GUI); In response to the second system obtaining permission to display the GUI, the second system is configured to display an interface of the target application and execute the target application.

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

[0181] As described above, in an embodiment of the present application, in a wearable device supporting dual systems, when a first system is in an operating state and a second system is in a sleeping state, upon receiving an application startup instruction for a target application, the first system first renders 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 of an embodiment of the present application, the first system pre-displays the startup effect of the application, thereby visually improving the startup speed of the application and reducing the display delay of the application screen during system switching.

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

[0183] In addition, the first memory space stores only the interface resources of applications that are supported to be launched on the first system, thereby realizing seamless system switching while reducing the memory space occupied by the interface resources and reducing the capacity needs of the first memory space.

[0184] In this embodiment, when updating the system language, the second system obtains first application information of each first application, obtains updated first interface resources according to the first application information, and sends the updated first interface resources to the first system. The first system updates the first interface resources stored in the first storage space, and ensures that the language of the application interface displayed on the first system is consistent with the system language during subsequent system switching.

[0185] In this embodiment, when the startup mode of the second application is updated, the second system obtains second application information of the second application, obtains a 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, and if there is an update conflict, the second interface resource is not updated. This ensures normal operation of the function of seamless system switching after the startup mode is updated.

[0186] 12, which is a block diagram showing a structure of a wearable device according to an exemplary embodiment of the present application. The wearable device in the present application may 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, and the second processor 1212 is used to execute a second system, and 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 uses various interfaces and lines to connect all the parts in the electronic device, executes instructions, programs, code sets or instruction sets stored in the memory 1220, and calls data stored in the memory 1220 to execute various functions and process data of the electronic device. Optionally, the processor 1210 may be implemented using at least one hardware of digital signal processing (DSP), field programmable gate array (FPGA), and programmable logic array (PLA). The processor 1210 may integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), a neural-network processing unit (NPU), a modem, and the like. The CPU mainly processes the operating system, the user interface, and application programs, and 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 realize artificial intelligence (AI) functions. The modem is used to handle wireless communication. The modem may not be integrated into the processor 1210 and may be implemented in only one chip.

[0188] The memory 1220 may include a random access memory (RAM) or a read only memory (ROM). Optionally, the memory 1220 may include a non-transitory computer-readable storage medium. The memory 1220 may be used to store instructions, programs, codes, code sets, or instruction sets. The memory 1220 may include a program storage area and a data storage area. The program storage area may store instructions for implementing an operating system, instructions for at least one function (e.g., a touch function, a voice playback function, an image playback function, etc.), instructions for implementing each method embodiment, etc. The data storage area may store data (e.g., audio data, a phone book) generated in response to use of the wearable device, 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 may be a Bluetooth service module, a wireless fidelity (WiFi) module, or a near field communication (NFC) module, and communicates with an external device (a server or other terminal device) via a wired or wireless network. The display component 1240 is used to display a GUI and / or receive a user's interaction operation.

[0190] In addition, those skilled in the art can understand that the structure of the wearable device shown in the above drawings is not intended to limit the wearable device, and the wearable device may have more or less components than those shown, or may combine some components, or may have a different arrangement of components. For example, the wearable device may also include components such as a wireless circuit, an input unit, a sensor, an audio circuit, a speaker, a microphone, a power source, etc., which will not be described.

[0191] In an embodiment of the present application, a computer-readable storage medium is further provided, which stores at least one instruction, which is executed by a processor to realize the method for displaying an application interface described in the above embodiment.

[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 including computer instructions, the computer instructions being stored in a computer-readable storage medium, a processor of a computer device reading the computer instructions from the computer-readable storage medium, and the processor executing the computer instructions, thereby causing the computer device to perform the method for displaying an application interface according to the embodiment.

[0193] Those skilled in the art may be aware of the following: In one or more examples above, the functions described in the embodiments of the present application may be realized by hardware, software, firmware, or any combination thereof. If 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 the computer-readable medium. Computer-readable media include computer storage media and communication media. Communication media include any medium that facilitates the transmission of a computer program from one place to another. Storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0194] The above are only the optional embodiments of the present application, and are not intended to limit the present application. Any modifications, equivalent changes, improvements, etc. within 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, in response to an application launch instruction of a target application, acquiring, by the first system, a target interface resource corresponding to the target application from a first memory space, which is a memory space corresponding to the first system; Rendering and displaying an interface of the target application by the first system based on the target interface resources; responsive to completion of switching of the second system 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. 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. The method of claim 1, wherein the application interface is displayed on the display screen.

3. 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. The method of claim 1, wherein the application interface is displayed on the display screen.

4. 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; 4. The method of claim 3, wherein the application interface is displayed on the display device.

5. 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; 5. The method of claim 4, wherein the application interface is displayed on the display device.

6. 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.

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

7. 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; 4. The method of claim 3, wherein the application interface is displayed on the display device.

8. 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.

8. The method of claim 7, wherein the application interface is displayed on the display device.

9. 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.

9. The method of claim 8, 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 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.

8. The method of claim 7, wherein the application interface is displayed on the display device.

11. 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. A method for displaying an application interface according to any one of claims 1 to 10.

12. 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 11.

13. 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 12. A wearable device characterized by:

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

Images