WO2022142793A1

WO2022142793A1 - Interface rendering method and apparatus, wearable device, and readable storage medium

Info

Publication number: WO2022142793A1
Application number: PCT/CN2021/130845
Authority: WO
Inventors: 曹庆峰; 林春德; 马海龙; 曹智强
Original assignee: Oppo广东移动通信有限公司
Priority date: 2020-12-31
Filing date: 2021-11-16
Publication date: 2022-07-07
Also published as: CN114691130A

Abstract

An interface rendering method and apparatus, a wearable device, and a computer readable storage medium. The method comprises: responding to an interface rendering instruction, and determining an interface type of an interface to be rendered (220); and if the interface type belongs to a preset first-type interface, performing, by a first operating system, interface rendering to generate a first target interface (240). Power consumption of running a second operating system on the wearable device is greater than power consumption of running the first operating system on the wearable device, and therefore, the interface type of the interface to be rendered carried in the interface rendering instruction is identified, and if the interface type belongs to the preset first-type interface, it is only required to control the first operating system to perform interface rendering, without using the second operating system to perform interface rendering.

Description

Interface rendering method and device, wearable device, and readable storage medium

This application claims the priority of the Chinese patent application filed on December 31, 2020 with the application number 202011641335.3 and the invention title is "Interface rendering method and device, wearable device, and readable storage medium", the entire content of which is Incorporated herein by reference.

technical field

The present application relates to the field of computer technology, and in particular, to an interface rendering method and device, a wearable device, and a readable storage medium.

Background technique

With the continuous development of computer technology, wearable devices are becoming more and more powerful and more and more popular. Wearable devices have brought a lot of convenience to people's daily life and travel.

However, for the purpose of portability and thinning design, wearable devices are relatively small in size and cannot carry large-capacity batteries like mobile phones and other electronic devices. Therefore, the battery life of wearable devices has always been a shortcoming that hinders its development. Among them, interface rendering is one of the functions that consume more power on wearable devices. Therefore, how to reduce the power consumption of interface rendering on wearable devices has become a difficult problem that needs to be solved urgently.

SUMMARY OF THE INVENTION

Embodiments of the present application provide an interface rendering method and apparatus, a wearable device, and a readable storage medium, which can reduce the power consumption of the wearable device during interface rendering.

An interface rendering method is applied to a wearable device, wherein a first operating system and a second operating system can be run on the wearable device, and the power consumption when running the second operating system on the wearable device is greater than that on the wearable device. The power consumption when running the first operating system on the wearable device, the method includes:

Responding to the interface rendering instruction, and determining the interface type of the interface to be rendered;

If the interface type belongs to a preset first type of interface, the first operating system performs interface rendering to generate a first target interface;

If the interface type belongs to a preset second type of interface, the second target interface is generated by the second operating system performing interface rendering.

An interface rendering apparatus is applied to a wearable device. A first operating system and a second operating system can be run on the wearable device, and the power consumption when the second operating system is run on the wearable device is greater than that on the wearable device. The power consumption when running the first operating system on the wearable device, the device includes:

The interface type identification module is used to respond to the interface rendering instruction and determine the interface type of the interface to be rendered;

a first interface rendering module, configured to perform interface rendering by the first operating system to generate a first target interface if the interface type belongs to a preset first type of interface;

A second interface rendering module, configured to generate a second target interface by performing interface rendering by the second operating system if the interface type belongs to a preset second type of interface.

A wearable device includes a memory and a processor, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the processor causes the processor to perform the operations of the interface rendering method as described above.

A computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, implements the operations of the above-mentioned interface rendering method.

Description of drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the accompanying drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only These are some embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without any creative effort.

Fig. 1 is the application environment diagram of the interface rendering method in one embodiment;

2 is a flowchart of an interface rendering method in one embodiment;

3 is a flowchart of an interface rendering method in another embodiment;

4 is a flowchart of an interface rendering method in another embodiment;

5 is a schematic diagram of a distributed architecture of an interface rendering method based on dual virtual machines in one embodiment;

6 is a communication flow chart between the Android system running on the AP and the RTOS system running on the MCU in one embodiment;

7 is a schematic diagram of splitting a dial rendering function into a first dial rendering class and a second dial rendering class in one embodiment;

8 is a flowchart of an interface rendering method in a specific embodiment;

9 is a structural block diagram of an interface rendering apparatus in one embodiment;

10 is a structural block diagram of an interface rendering apparatus in yet another embodiment;

FIG. 11 is a schematic diagram of the internal structure of a wearable device in one embodiment.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present application more clearly understood, the present application will be described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application, but not to limit the present application.

FIG. 1 is an application scene diagram of an interface rendering method in one embodiment. As shown in FIG. 1 , the application environment includes a wearable device 120. A first operating system and a second operating system can be run on the wearable device, and the power consumption when running the second operating system on the wearable device is greater than that when the wearable device runs the second operating system. Power consumption when the first operating system is running on the device. The wearable device 120 uses the interface rendering method in this application to respond to the interface rendering instruction and determine the interface type of the interface to be rendered; if the interface type belongs to the preset first type of interface, the first operating system performs interface rendering A first target interface is generated; if the interface type belongs to a preset second type of interface, the second operating system performs interface rendering to generate a second target interface. Here, a wearable device refers to a portable device that is directly worn on the body or integrated into the user's clothing or accessories. The wearable device 120 may be a terminal device such as a smart bracelet, a smart watch, smart glasses, smart gloves, smart socks, and a smart belt, which is not limited in this application.

FIG. 2 is a flowchart of an interface rendering method in one embodiment. The interface rendering method in this embodiment is described by taking running on the wearable device 120 in FIG. 1 as an example. The first operating system and the second operating system can run on the wearable device, and the first operating system can run on the wearable device. The power consumption of the second operating system is greater than that of running the first operating system on the wearable device. As shown in FIG. 2 , an interface rendering method is provided, including operations 220 to 260 . in,

In operation 220, the interface type of the interface to be rendered is determined in response to the interface rendering instruction.

A first operating system and a second operating system can be run on the wearable device, wherein the power consumption when the second operating system is run on the wearable device is greater than the power consumption when the first operating system is run on the wearable device. For example, the second operating system may be an Android (Andriod) system, and correspondingly, the first operating system may be a real-time operating system, such as an RTOS system (real-time operating system), etc., which is not limited in this application.

Among them, the RTOS system consumes less power during operation, and the system can be used to support the basic functions of wearable devices, such as time display, alarm schedule, physiological data monitoring, call reminder and other functions. The Android Andriod system consumes a lot of power when running, and the Andriod system can be used to support complex functions of wearable devices, such as video and voice calling services, games, audio and video playback, WIFI, power management and other functions.

If the wearable device is a smart watch or smart bracelet, preset events can be set. If the wearable device detects that a preset event occurs, it triggers an interface rendering instruction, and performs interface rendering based on the interface rendering instruction. Among them, rendering refers to the process that the GPU reads data from the cache and renders it to the screen. In general, a drawing process may also be included before rendering, and drawing refers to a process in which the CPU converts the content to be rendered into data and stores it in the cache. Here, the preset events include acceleration data greater than a preset threshold, displacement within a preset time period greater than a preset threshold, gaze events (the user's eyes gaze on the screen for more than a preset duration), touch events, etc., which are not covered in this application. limited.

For example, the user wears the wearable device on the arm, and if the wearable device detects that a preset event occurs when the arm lifts up, an interface rendering instruction is triggered on the wearable device. That is, if the acceleration sensor in the wearable device detects that the acceleration data is greater than the preset threshold when the action of raising the arm occurs, it is considered that a preset event has occurred. The triggering interface rendering instruction is used to instruct interface rendering, which is dial rendering for a smart watch or smart bracelet.

Specifically, after the interface rendering instruction is triggered on the wearable device, the interface rendering instruction is received through the first operating system. Then continue to identify the interface type of the interface to be rendered carried in the interface rendering instruction by the first operating system. The interface rendering instruction carries the interface type of the interface to be rendered. The images to be rendered may be classified based on the number of elements included in the interface to be rendered, the color types of the elements, and the complexity of the elements. For example, it is divided into the first type of interface, the second type of interface, and the third type of interface, wherein the number of elements included in the third type of interface, the color type of the elements, and the complexity of the elements are all larger than those of the second type of interface. The number of elements contained in the class interface, the color types of the elements, and the complexity of the elements are more or greater than those of the first class interface.

In operation 240, if the interface type belongs to the preset first type of interface, the first operating system performs interface rendering to generate the first target interface.

If the interface type of the interface to be rendered carried in the interface rendering instruction is identified by the first operating system as belonging to the preset first type of interface, the first operating system is controlled to perform interface rendering according to the interface rendering instruction to generate the first target interface. The first target interface belongs to the first type of interface. Because the number of elements included in the first type of interface, the color types of the elements, and the complexity of the elements are relatively small, it is sufficient to control the first operating system to perform interface rendering, and the second operating system does not need to be used for interface rendering. The power consumption when running the second operating system on the wearable device is greater than the power consumption when running the first operating system on the wearable device. Therefore, by controlling the first operating system to render the first type of interface, the power consumption of interface rendering on the wearable device can be reduced.

In operation 260, if the interface type belongs to a preset second type of interface, the second operating system performs interface rendering to generate a second target interface.

Specifically, if the interface type of the interface to be rendered carried in the interface rendering instruction is identified by the first operating system as belonging to the preset second type of interface, the first operating system is controlled to perform interface rendering according to the interface rendering instruction to generate the second target interface . The second target interface belongs to the second type of interface. Because the number of elements, the color types of elements, and the complexity of the elements contained in the second type of interface are more or larger than the number of elements, the color types of elements, and the complexity of the elements contained in the first type of interface. An operating system is insufficient to support rendering of the second type of interface, so the second operating system is controlled to perform interface rendering. Because, the first operating system can be used to support basic functions of the wearable device, and the second operating system can be used to support complex functions of the wearable device.

The interface type of the interface to be rendered is determined in response to the interface rendering instruction. If the interface type belongs to the preset second type of interface, the second operating system performs interface rendering to generate the second target interface. Because the number of elements, the color types of elements, and the complexity of the elements contained in the second type of interface are more or larger than the number of elements, the color types of elements, and the complexity of the elements contained in the first type of interface. One operating system is not enough to support rendering of the second type of interface, so the second operating system is controlled to perform interface rendering to meet the needs of rendering more complex interfaces on the wearable device.

In this embodiment of the present application, the interface type of the interface to be rendered is determined in response to the interface rendering instruction. If the interface type belongs to the preset first type of interface, the first operating system performs interface rendering to generate the first target interface. If the interface type belongs to the preset second type of interface, the second operating system performs interface rendering to generate the second target interface. Because the power consumption of running the second operating system on the wearable device is greater than the power consumption of running the first operating system on the wearable device, by identifying the interface type of the interface to be rendered carried in the interface rendering instruction, if If the interface type belongs to the preset first type of interface, it is sufficient to control the first operating system to perform interface rendering, and it is not necessary to use the second operating system to perform interface rendering. Obviously, the power consumption of the wearable device during interface rendering is reduced.

In one embodiment, in response to the interface drawing and rendering instruction, determining the interface type of the interface to be drawn and rendered includes:

The interface rendering instruction is received through the first operating system, and the interface type of the to-be-rendered interface is determined by the first operating system.

In this embodiment of the present application, after the interface rendering instruction is triggered on the wearable device, the first operating system receives the interface rendering instruction, and then the first operating system continues to determine the interface type of the interface to be rendered. Of course, it is also possible to receive the interface rendering instruction through the second operating system, and then continue to determine the interface type of the interface to be rendered by the second operating system, which is not limited in this application.

In one embodiment, as shown in FIG. 3, an interface rendering method is provided, further comprising:

In operation 280, if the interface to be rendered belongs to the third type of interface, then the first operating system and the second operating system both perform interface rendering to generate a third target interface, and the third target interface is the first target interface and the second target interface. Synthesized interface.

Specifically, if the interface type of the interface to be rendered carried in the interface rendering instruction is identified by the first operating system as belonging to the preset third type of interface, the first operating system is controlled to perform interface rendering according to the interface rendering instruction to generate the third target interface . The third target interface belongs to the third type of interface. Because the number of elements, the color types of elements, and the complexity of the elements contained in the third type of interface are more or larger than the number of elements, the color types of elements, and the complexity of the elements contained in the second type of interface, the second type of interface contains more or more elements. The operating system is also insufficient to support rendering of the third type of interface, or even if the second operating system can support the rendering of the third type of interface, the power consumption of rendering is relatively high, so the first operating system and the second operating system are controlled to jointly perform interface rendering. Specifically, the third target interface includes two parts. The first operating system can be used to render a part of the third target interface, and the second operating system can be used to render another part of the third target interface. The rendering of these two parts has a sequential order. However, this application does not limit the sequence. Because the power consumption of running the second operating system on the wearable device is greater than the power consumption of running the first operating system on the wearable device, combining the two operating systems for rendering can achieve a complex rendering of the third operating system. While the target interface is displayed, the power consumption of the wearable device during the interface rendering process is reduced.

In this embodiment of the present application, the interface type of the interface to be rendered is determined in response to the interface rendering instruction. If the interface type belongs to the preset third type of interface, the second operating system performs interface rendering to generate the third target interface. Because the number of elements, the color types of elements, and the complexity of the elements contained in the third type of interface are more or larger than the number of elements, the color types of elements, and the complexity of the elements contained in the second type of interface. The second operating system is not enough to support the rendering of the second type of interface, or even though the second operating system can support the rendering of the third type of interface, the power consumption of rendering is high, so the first operating system and the second operating system are controlled to perform interface rendering to meet the needs of The need to render more complex interfaces on wearable devices. And because the power consumption when running the first operating system is relatively small, the first operating system is also used to render a part of the third target interface here, so the power consumption of the wearable device during the interface rendering process can be reduced.

In one embodiment, the first virtual machine runs on the first operating system, and the second virtual machine runs on the second operating system; the first virtual machine and the second virtual machine can run the same application program; operation 240, the first operation The system performs interface rendering to generate the first target interface, including:

The first operating system performs interface rendering by running the first virtual machine to generate the first target interface.

Specifically, if the first operating system is an RTOS system, the RTOS system generally runs on the coprocessor MCU of the wearable device, and the software on the MCU is often written in C language. If the second operating system is an Andriod system, the Andriod system generally runs on the main processor CPU of the wearable device, and the software on the CPU is usually written in a high-level architecture and language, such as JAVA language. In this way, because the RTOS system and the Andriod system are written in different languages, it is impossible to achieve joint compilation and deployment, and it is impossible to achieve a distributed architecture.

Therefore, a lightweight JVM virtual machine (Java Virtual Machine, Java virtual machine) is run on the first operating system (such as an RTOS system), and a DVM (Dalvik Virtual Machine) virtual machine is run in the second operating system (such as an Andriod system). And the first virtual machine and the second virtual machine can run the same type of application, where the same type of application can be a JAVA application. That is, through the first virtual machine and the second virtual machine, it is realized that both the first operating system and the second operating system can run the JAVA application program. Furthermore, the joint compilation and deployment of the JAVA application program in the first operating system and the second operating system is realized, and the efficiency of compilation and deployment is improved. Among them, the JVM is a fictional computer, which is realized by simulating various computer functions on an actual computer. A very important feature of the Java language is its independence from the platform, and the use of the Java virtual machine is the key to realizing this feature. If a general high-level language is to run on different platforms, at least it needs to be compiled into different object codes. After the introduction of the Java virtual machine, the Java language does not need to be recompiled when running on different platforms. The Java language uses the Java virtual machine to shield the information related to the specific platform, so that the Java language compiler only needs to generate the object code (bytecode) running on the Java virtual machine, and it can run on various platforms without modification. . When the Java virtual machine executes the bytecode, it interprets the bytecode into machine instructions for execution on a specific platform. That's why Java is able to "compile once, run anywhere".

All Java programs in the Android system run on the DVM. Each program on the Android system has its own thread, and the DVM only executes the Dalvik executable file of .dex. Each Android application corresponds to an independent DVM instance at the bottom and executes under its interpretation.

In this way, running the JVM virtual machine in the first operating system realizes that both the DVM virtual machine and the DVM virtual machine running in the second operating system are written in the JAVA language, thereby realizing joint compilation and deployment and distributed architecture. That is, the JVM virtual machine can be run in the first operating system to perform interface rendering.

Specifically, the wearable device determines the interface type of the interface to be rendered in response to the interface rendering instruction. If the interface type belongs to the preset first type of interface, the first operating system performs interface rendering by running the first virtual machine to generate the first target interface.

In the embodiment of the present application, the first virtual machine runs on the first operating system, for example, the JVM virtual machine runs on the RTOS system. In this way, running the JVM virtual machine in the first operating system realizes that both the DVM virtual machine and the DVM virtual machine running in the second operating system are written in JAVA language, and then the interface rendering process can be jointly compiled, deployed and distributed architecture. . That is, the JVM virtual machine can be run in the first operating system to perform interface rendering. Thus, the wearable device responds to the interface rendering instruction and determines the interface type of the interface to be rendered. If the interface type belongs to the preset first type of interface, the first operating system performs interface rendering by running the first virtual machine to generate the first target interface. The first target interface is independently rendered in the first operating system.

Continuing from the previous embodiment, the second virtual machine is run on the second operating system; in operation 260, the second operating system performs interface rendering to generate the second target interface; including:

The second virtual machine is run by the second operating system to perform interface rendering, and a second target interface is generated.

In this embodiment of the present application, the second virtual machine is run on the second operating system, for example, the DVM virtual machine is run in the Android system. The second virtual machine is run by the second operating system to perform interface rendering, and a second target interface is generated. A second target interface with more or larger number of elements, color types of elements, and complexity of elements included in the first type of interface is implemented on the second operating system. Because the first operating system is not enough to support rendering of the second type of interface, the second operating system is controlled to run the second virtual machine to perform interface rendering, so as to meet the requirements of rendering more complex interfaces on the wearable device.

In one embodiment, the second operating system runs the second virtual machine to perform interface rendering to generate the second target interface; including:

Send an interface rendering instruction to the second operating system through the first operating system;

According to the interface rendering instruction, the second operating system is controlled to run the second virtual machine to perform interface rendering, and a second target interface is generated.

As shown in Figure 4, an interface rendering method is provided, including:

Operation 402, receiving an interface rendering instruction through the first operating system; enter operation 404;

In operation 404, determine whether the interface type of the interface to be rendered carried in the interface rendering instruction is the first type of interface; if so, go to operation 406; if not, go to operation 408;

Operation 406, controlling the first operating system to run the first virtual machine to perform interface rendering according to the interface rendering instruction to generate the first target interface;

Operation 408, sending an interface rendering instruction to the second operating system through the first operating system;

Operation 410: Control the second operating system to run the second virtual machine to perform interface rendering according to the interface rendering instruction, and generate a second target interface.

Wherein, sending the interface rendering instruction to the second operating system through the first operating system may be performed through a virtual interface (VirtualAPI) between the first virtual machine in the first operating system and the second virtual machine in the second operating system communication. Among them, in fact, it is impossible to communicate directly through the VirtualAPI, and it must be transferred through the underlying dual-core communication interface (API). But to the Java caller, it looks like the scheduling is directly between the two virtual machines.

In the embodiment of the present application, the first virtual machine runs on the first operating system, for example, the JVM virtual machine runs on the RTOS system. In this way, running the JVM virtual machine in the first operating system realizes that both the DVM virtual machine and the DVM virtual machine running in the second operating system are written in JAVA language, and then the interface rendering process can be jointly compiled, deployed and distributed architecture. . Furthermore, communication between the first operating system and the second operating system may be performed through a virtual interface (VirtualAPI) between the first virtual machine and the second virtual machine. Therefore, if the first operating system determines that the interface type of the interface to be rendered carried in the interface rendering instruction is not the first type of interface, the first operating system sends the interface rendering instruction to the second operating system, which realizes the process of passing the first operating system. After the operating system makes the judgment, it controls the second operating system to run the second virtual machine to perform interface rendering to generate the second target interface. That is, a common compilation, deployment and distributed architecture can be implemented for the interface rendering process.

Continuing from the previous embodiment, sending an interface rendering instruction to the second operating system through the first operating system includes:

The first operating system is controlled to forward the interface rendering instruction to the second operating system through the dual-system communication interface.

As shown in FIG. 5 , it is a schematic diagram of a distributed architecture of an interface rendering method based on dual virtual machines in one embodiment. Wherein, the AP (Application Processor, application processor) 520 can run a second operating system, such as an Android system. MCU (Microcontroller Unit, Micro Control Unit) 540, on which a first operating system, such as an RTOS system, can run.

[Corrected 21.12.2021 in accordance with Rule 91]
Wear OS Clockwork runs on the second operating system, Wear OS Clockwork (written based on JAVA language) can communicate with DVM through Virtual Dual-core Communication, and DVM can communicate with the underlying dual-core through JNI (JavaNative Interface, Java Native Interface). module (Dual-core communication) to communicate. Among them, the dual-core communication module is written based on C language. Correspondingly, Light-WatchFace runs on the first operating system, Light-WatchFace (written based on JAVA language) can communicate with the Embedded JVM through Virtual Dual-core Communication, and the Embedded JVM can communicate with the underlying dual-core communication module (Dual) through JNI -core communication) to communicate. A dual-system communication interface 560 is configured between the dual-core communication module on the first operating system and the dual-core communication module on the second operating system, and the dual-system communication can be realized through the dual-system communication interface 560 . The dual-system communication interface 560 may be an SPI interface (Serial Peripheral Interface, serial peripheral interface), which, of course, is not limited in this application.

Among them, there is a virtual interface (Virtual API) between the Virtual Dual-core Communication on the first operating system and the Virtual Dual-core Communication on the second operating system, but in fact, it is impossible to communicate directly through the Virtual API. The underlying dual-core communication interface (API, Application Programming Interface) performs the transfer, and the specific reasons will not be repeated here.

[Corrected 21.12.2021 in accordance with Rule 91]
In the embodiment of the present application, based on the above distributed architecture, the Wear OS Clockwork of the first operating system can be controlled, and the interface rendering instruction is forwarded to the second operating system from top to bottom through the dual-system communication interface. After receiving the interface rendering instruction, the dual-system communication interface of the second operating system transmits the interface rendering instruction to the Embeded JVM from bottom to top. Then, interface rendering is performed on the Embedded JVM according to the interface rendering instruction to generate a second target interface. It is realized that if the interface type of the interface to be rendered carried in the interface rendering instruction belongs to the preset second type of interface, the second operating system is controlled to perform interface rendering according to the interface rendering instruction to generate the second target interface. Because the first operating system is not enough to support rendering of the second type of interface, the second operating system is controlled to run the second virtual machine to perform interface rendering, so as to meet the requirement of rendering more complex interfaces on the wearable device.

In one embodiment, controlling the first operating system to forward the interface rendering instruction to the second operating system through the dual-system communication interface includes:

sending the interface rendering instruction to the hardware abstraction layer of the first operating system through the application framework layer of the first operating system;

The interface rendering instruction is sent to the hardware abstraction layer of the second operating system through the peripheral interface through the hardware abstraction layer of the first operating system.

As shown in Figure 6, it is the communication flow chart between the Android system running on the AP and the RTOS system running on the MCU. Among them, Android adopts a layered architecture, which can be divided into four layers. From the top layer to the bottom layer, it is divided into application layer (app+System apps), application framework layer (JavaAPI Framework), system runtime library and runtime environment layer (Libraries). +android Runtime) and Linux kernel layer (HAL+Linux Kernel). Among them, HAL is a hardware abstraction layer (HardwareAbstraction Layer).

The first operating system in FIG. 6 includes an application layer 602 , an application framework layer 604 , a system runtime library 606 and a hardware abstraction layer 608 in sequence from the upper layer to the bottom layer, and other parts of the hierarchical structure are not shown in FIG. 6 for the time being. Shows. And the algorithm for identifying the interface type of the interface to be rendered carried in the interface rendering instruction is stored in the system runtime library 606 . Correspondingly, the second operating system in FIG. 6 sequentially includes an application layer 610 , an application framework layer 612 and a hardware abstraction layer 614 from the upper layer to the bottom layer, and other parts of the hierarchical structure are not shown in FIG. 6 for the time being.

Specifically, as shown in FIG. 6 , an interface rendering method is provided. After receiving the interface rendering instruction, the first operating system of the wearable device uses the algorithm in the system runtime library 606 to determine the content in the current interface rendering instruction. The interface type of the interface to be rendered. If it is determined that the interface type of the interface to be rendered is the first type of interface, the interface rendering instruction is sent to the application framework layer 604, and then sent to the application layer 602 through the application framework layer 604, and the application layer 602 performs rendering A first target interface is generated.

If the system runtime library 606 determines that the interface type of the interface to be rendered is the second type interface, the interface rendering instruction is sent to the application framework layer 604 , and then sent to the hardware abstraction layer 608 through the application framework layer 604 . The hardware abstraction layer 608 sends the interface rendering instruction to the hardware abstraction layer 614 of the second operating system through the peripheral interface, and notifies the second operating system to perform rendering. Specifically, the hardware abstraction layer 614 sends the interface rendering instruction to the application framework layer 612, and then the application framework layer 612 sends it to the application layer 610 for rendering to generate the second target interface.

In the embodiment of the present application, if the interface type belongs to the preset second type of interface, the interface rendering instruction is sent to the hardware abstraction layer of the first operating system through the application framework layer of the first operating system, and the hardware abstraction layer of the first operating system is used to send the interface rendering instruction to the hardware abstraction layer of the first operating system. The layer sends the interface rendering instruction to the hardware abstraction layer of the second operating system through the peripheral interface. Therefore, it is realized that the interface rendering instruction is sent from the first operating system to the second operating system, so that the second operating system can perform interface rendering to generate the second target interface.

In one embodiment, an interface rendering method is provided, further comprising:

Split the dial rendering function into the first dial rendering class and the second dial rendering class in advance;

Loading the first interface rendering class into the first virtual machine, where the first interface rendering class is used to render the first type of interface;

The second interface rendering class is loaded into the second virtual machine, and the second interface rendering class is used to render the second type of interface.

As shown in FIG. 7 , in the traditional method, the dial rendering functions are all run on the AP, while in the embodiment of the present application, the dial rendering functions are divided into a first dial rendering class and a second dial rendering class in advance. The first interface rendering class is loaded into the first virtual machine in the MCU, and the first interface rendering class is used to render the first type of interface. The second interface rendering class is loaded into the second virtual machine in the AP, and the second interface rendering class is used to render the second type of interface.

Because the dial rendering function is divided into the first dial rendering class and the second dial rendering class, and these two dial rendering classes can run independently under the corresponding operating system, it can be realized that if the interface type belongs to the preset The first type of interface is called, according to the interface rendering instruction, the first interface rendering class is called in the first virtual machine to perform interface rendering in the application layer of the first operating system to generate the first type of interface. At the same time, if the interface type belongs to the preset second type of interface, the second interface rendering class is called in the second virtual machine to perform interface rendering in the application layer of the second operating system to generate the second type of interface.

In the embodiment of the present application, because the dial rendering function is divided into a first dial rendering class and a second dial rendering class, and both of these two dial rendering classes can run independently under the corresponding operating system, it is possible to realize the Different interface types of the to-be-rendered interface carried in the interface rendering instruction control different operating systems to render the interface. It is not necessary to perform interface rendering under the second operating system, so the power consumption of the wearable device during interface rendering is reduced.

In one embodiment, the first operating system runs the first virtual machine to perform interface rendering to generate the first target interface, including:

The first interface rendering class is called in the first virtual machine to perform interface rendering in the application layer of the first operating system to generate the first type of interface.

In the embodiment of the present application, because the dial rendering function is divided into a first dial rendering class and a second dial rendering class, and these two dial rendering classes can run independently under the corresponding operating system, if the interface rendering instruction The to-be-rendered interface carried in the interface belongs to the preset first type of interface, and the first operating system is controlled to perform interface rendering. It is not necessary to perform interface rendering under the second operating system, so the power consumption of the wearable device during interface rendering is reduced.

In one embodiment, the second operating system runs the second virtual machine to perform interface rendering to generate the second target interface, including:

The second interface rendering class is called in the second virtual machine to perform interface rendering in the application layer of the second operating system to generate the second type of interface.

In the embodiment of the present application, because the dial rendering function is divided into a first dial rendering class and a second dial rendering class, and these two dial rendering classes can run independently under the corresponding operating system, if the interface rendering instruction The to-be-rendered interface carried in the interface belongs to a preset second type of interface, and controls the second operating system to perform interface rendering. The first operating system is insufficient to support rendering of the second type of interface, so the second operating system is controlled to perform interface rendering to meet the requirements of rendering more complex interfaces on the wearable device.

In one embodiment, at least one of the brightness of the interface of the second type, the number of included elements, and the color type of the elements is greater than the brightness of the interface of the first type, the number of included elements, and the color type of the elements.

Specifically, the number of elements contained in the second type of interface may be greater than the number of elements contained in the first type of interface, or the elements contained in the second type of interface may have more color types than the first type of interface. The color type of the element may also be that the brightness of the second type of interface is greater than the brightness of the first type of interface. Of course, it may also be that the brightness of the second type of interface, the number of elements included, and the color types of the elements are all greater than those of the first type of interface, which is not limited in this application. For example, for a wearable watch or bracelet, the second type of interface can be a common dial with multiple colors and elements, and the first type of interface can be a black and white low-light dial that only displays time hands.

In this embodiment of the present application, the second type of interface is distinguished from the first type of interface from at least one direction of brightness, the number of elements contained, and the color type of the elements. In order to respond to the interface rendering instruction and determine the interface type of the interface to be rendered, if the interface type belongs to the preset first type of interface, control the first operating system to perform interface rendering according to the interface rendering instruction to generate the first target interface. If the interface type belongs to the preset second type of interface, control the second operating system to perform interface rendering according to the interface rendering instruction to generate the second target interface. Therefore, it is possible to control different operating systems to perform interface rendering based on different interface types of the interface to be rendered carried in the interface rendering instruction. It is not necessary to perform interface rendering under the second operating system, so the power consumption of the wearable device during interface rendering is reduced.

In a specific embodiment, as shown in FIG. 8 , an interface rendering method is provided, which is applied to a wearable watch or a wristband, and a first operating system and a second operating system can be run on the wearable watch or the wristband, And the power consumption when running the second operating system on the wearable watch or the bracelet is greater than the power consumption when running the first operating system on the wearable watch or the bracelet, and the method includes:

In operation 802, the wearable watch or bracelet receives an interface rendering instruction through the RTOS system;

In operation 804, it is determined whether the interface type of the interface to be rendered carried in the interface rendering instruction is a low-light dial; if so, go to operation 806; if not, go to operation 808;

In operation 806, the RTOS system is controlled according to the interface rendering instruction, and the low-light dial rendering class is called in the JVM virtual machine to perform rendering to generate the low-light dial.

In operation 808, an interface rendering instruction is sent to the Android system through the RTOS system;

In operation 810, the Android system is controlled according to the interface rendering instruction, and the non-low-light dial rendering class is called in the DVM virtual machine to perform interface rendering, so as to generate a non-low-light dial.

In the embodiment of the present application, because the power consumption when running the Android system on the wearable device is greater than the power consumption when running the RTOS system on the wearable device, the interface type of the interface to be rendered carried in the interface rendering instruction is identified by identifying the interface type of the interface to be rendered. , if the interface type belongs to the preset low-light dial, you can control the TOS system for interface rendering, and do not need to use the Android system for interface rendering. Obviously, the power consumption of the wearable device during interface rendering is reduced.

In one embodiment, as shown in FIG. 9, an interface rendering apparatus 900 is provided, which is applied to a wearable device. A first operating system and a second operating system can run on the wearable device, and run on the wearable device. The power consumption of the second operating system is greater than that of running the first operating system on the wearable device, and the device includes:

an interface type identification module 920, configured to respond to the interface rendering instruction and determine the interface type of the interface to be rendered;

a first interface rendering module 940, configured to generate a first target interface by performing interface rendering by the first operating system if the interface type belongs to a preset first type of interface;

The second interface rendering module 960 is configured to generate a second target interface by performing interface rendering by the second operating system if the interface type belongs to a preset second type of interface.

In one embodiment, the interface type identification module 920 is further configured to receive an interface rendering instruction through the first operating system, and determine the interface type of the interface to be rendered and rendered by the first operating system.

In one embodiment, an interface rendering apparatus 900 is provided, which further includes a third interface rendering module; the third interface rendering module is used to render the interface to be rendered by the first operating system and the second interface if the interface to be rendered belongs to the third type interface. The operating systems all perform interface rendering to generate a third target interface, and the third target interface is an interface obtained by synthesizing the first target interface and the second target interface.

In one embodiment, the first virtual machine runs on the first operating system, and the second virtual machine runs on the second operating system; the first interface rendering module 940 is further configured to be executed by the first operating system by running the first virtual machine The interface rendering generates the first target interface; the second interface rendering module is further configured to run the second virtual machine by the second operating system to perform interface rendering to generate the second target interface.

In one embodiment, the second interface rendering module 960 includes an interface rendering instruction sending unit for sending an interface rendering instruction to the second operating system through the first operating system; an interface rendering unit for controlling the second operating system according to the interface rendering instruction The operating system runs the second virtual machine to perform interface rendering to generate a second target interface.

In one embodiment, the interface rendering instruction sending unit is further configured to control the first operating system to forward the interface rendering instruction to the second operating system through the dual-system communication interface.

In one embodiment, the interface rendering instruction sending unit is further configured to send the interface rendering instruction to the hardware abstraction layer of the first operating system through the application framework layer of the first operating system; The interface is set to send the interface rendering instruction to the hardware abstraction layer of the second operating system.

In one embodiment, as shown in FIG. 10, an interface rendering apparatus 900 is provided, which further includes a dial rendering function splitting module 980; the dial rendering function splitting module 980 is used to split the dial rendering function into A dial rendering class and a second dial rendering class; load the first interface rendering class into the first virtual machine, and the first interface rendering class is used to render the first interface; load the second interface rendering class into the second virtual machine , the second interface rendering class is used to render the second type of interface.

In one embodiment, the first interface rendering module 940 is further configured to call the first interface rendering class in the first virtual machine to perform interface rendering in the application layer of the first operating system to generate the first type of interface.

In one embodiment, the second interface rendering module 960 is further configured to call the second interface rendering class in the second virtual machine to perform interface rendering in the application layer of the second operating system to generate the second type of interface.

In one embodiment, the first operating system is an RTOS system, and the second operating system is an Android system.

In one embodiment, the first virtual machine is a JVM virtual machine, and the second virtual machine is a DVM virtual machine.

It should be understood that although the various operations in the flow charts in the above figures are displayed in sequence according to the arrows, these operations are not necessarily executed in the sequence indicated by the arrows. Unless otherwise specified herein, the execution of these operations is not strictly limited in order, and these operations may be performed in other orders. Moreover, at least a part of the operations in the above figures may include multiple sub-operations or multiple stages. These sub-operations or stages are not necessarily executed at the same time, but may be executed at different times. The execution of these sub-operations or stages The order is also not necessarily sequential, but may be performed alternately or alternately with other operations or at least a portion of sub-operations or phases of other operations.

The division of each module in the above interface rendering apparatus is only used for illustration. In other embodiments, the interface rendering apparatus may be divided into different modules as required to complete all or part of the functions of the above interface rendering apparatus.

For the specific limitation of the interface rendering apparatus, please refer to the limitation on the interface rendering method above, which will not be repeated here. Each module in the above-mentioned interface rendering apparatus may be implemented in whole or in part by software, hardware and combinations thereof. The above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

In one embodiment, a wearable device is also provided, including a memory and a processor, a computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes an interface provided by the above embodiments The operation of the render method.

FIG. 11 is a schematic diagram of the internal structure of a wearable device in one embodiment. As shown in Figure 11, the wearable device includes a processor and a memory connected through a system bus. Among them, the processor is used to provide computing and control capabilities to support the operation of the entire wearable device. The memory may include non-volatile storage media and internal memory. The nonvolatile storage medium stores an operating system and a computer program. The computer program can be executed by the processor to implement an interface rendering method provided by the above embodiments. Internal memory provides a cached execution environment for operating system computer programs in non-volatile storage media. The wearable device can be any terminal device such as a mobile phone, a tablet computer, a PDA (Personal Digital Assistant, personal digital assistant), a POS (Point of Sales, a sales terminal), a car computer, a wearable device, and the like.

The implementation of each module in the interface rendering apparatus provided in the embodiment of the present application may be in the form of a computer program. The computer program can be run on a wearable device or a wearable device. The program modules formed by the computer program can be stored on the wearable device or the memory of the wearable device. When the computer program is executed by the processor, the operations of the methods described in the embodiments of the present application are implemented.

Embodiments of the present application also provide a computer-readable storage medium. One or more non-volatile computer-readable storage media containing computer-executable instructions, when executed by one or more processors, cause the processors to perform the operations of the interface rendering method.

A computer program product containing instructions, when run on a computer, causes the computer to perform an interface rendering method.

Any reference to a memory, storage, database, or other medium as used in embodiments of the present application may include non-volatile and/or volatile memory. Suitable nonvolatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is available in various forms such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link (Synchlink) DRAM (SLDRAM), Memory Bus (Rambus) Direct RAM (RDRAM), Direct Memory Bus Dynamic RAM (DRDRAM), and Memory Bus Dynamic RAM (RDRAM).

The above interface rendering examples only express several embodiments of the present application, and the descriptions thereof are relatively specific and detailed, but should not be construed as a limitation on the scope of the patent of the present application. It should be pointed out that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can also be made, which all belong to the protection scope of the present application. Therefore, the scope of protection of the patent of the present application shall be subject to the appended claims.

Claims

An interface rendering method, characterized in that it is applied to a wearable device, the wearable device can run a first operating system and a second operating system, and the power consumption when running the second operating system on the wearable device is greater than the power consumption when the first operating system is run on the wearable device, and the method includes:

In response to the interface rendering instruction, determine the interface type of the interface to be rendered;

If the interface type belongs to a preset first type of interface, the first operating system performs interface rendering to generate a first target interface;

If the interface type belongs to a preset second type of interface, the second target interface is generated by the second operating system performing interface rendering.
The method according to claim 1, wherein the determining the interface type of the interface to be rendered and rendered in response to the interface drawing and rendering instruction comprises:

The interface rendering instruction is received through the first operating system, and the interface type of the interface to be rendered and rendered is determined by the first operating system.
The method according to claim 1, wherein the method further comprises:

If the interface to be rendered belongs to the third type of interface, the first operating system and the second operating system both perform interface rendering to generate a third target interface, and the third target interface is the first target interface An interface obtained by synthesizing the interface and the second target interface.
The method according to claim 1, wherein a first virtual machine runs on the first operating system, a second virtual machine runs on the second operating system, the first virtual machine and the The second virtual machine can run applications of the same type; the generating the first target interface by performing interface rendering by the first operating system includes:

performing interface rendering by the first operating system by running the first virtual machine to generate a first target interface;

The generating a second target interface by performing interface rendering by the second operating system; including:

The second virtual machine is run by the second operating system to perform interface rendering to generate a second target interface.
The method according to claim 4, wherein the second operating system runs the second virtual machine to perform interface rendering to generate a second target interface; comprising:

Send the interface rendering instruction to the second operating system through the first operating system;

Controlling the second operating system to run the second virtual machine to perform interface rendering according to the interface drawing instruction to generate a second target interface.
The method according to claim 5, wherein the sending the interface rendering instruction to the second operating system through the first operating system comprises:

The first operating system is controlled to forward the interface rendering instruction to the second operating system through a dual-system communication interface.
The method according to claim 6, wherein the controlling the first operating system to forward the interface rendering instruction to the second operating system through a dual-system communication interface comprises:

sending the interface rendering instruction to the hardware abstraction layer of the first operating system through the application framework layer of the first operating system;

The interface rendering instruction is sent to the hardware abstraction layer of the second operating system through the peripheral interface through the hardware abstraction layer of the first operating system.
The method according to claim 4, wherein the method further comprises:

Split the dial rendering function into the first dial rendering class and the second dial rendering class in advance;

Loading the first interface rendering class into the first virtual machine, where the first interface rendering class is used to render the first type of interface;

Loading the second interface rendering class into the second virtual machine, where the second interface rendering class is used to render the second type of interface.
The method according to claim 8, wherein the performing interface rendering by running the first virtual machine by the first operating system to generate the first target interface comprises:

The first interface rendering class is called in the first virtual machine to perform interface rendering in the application layer of the first operating system to generate a first type of interface.
The method according to claim 8, wherein the step of running the second virtual machine by the second operating system to perform interface rendering to generate the second target interface comprises:

The second interface rendering class is called in the second virtual machine to perform interface rendering in the application layer of the second operating system to generate a second type of interface.
The method according to claim 1, wherein at least one of the brightness of the second type interface, the number of elements included, and the color type of the element are greater than the brightness of the first type interface, the The number of elements included, the color type of the element.
The method according to any one of claims 1-11, wherein the first operating system is an RTOS system, and the second operating system is an Android system.
The method according to any one of claims 1-11, wherein the first virtual machine is a JVM virtual machine, and the second virtual machine is a DVM virtual machine.
An interface rendering device is characterized in that, it is applied to a wearable device, a first operating system and a second operating system can be run on the wearable device, and the function of running the second operating system on the wearable device is The power consumption is greater than the power consumption when the first operating system is run on the wearable device, and the device includes:

The interface type identification module is used to respond to the interface rendering instruction and determine the interface type of the interface to be rendered;

a first interface rendering module, configured to perform interface rendering by the first operating system to generate a first target interface if the interface type belongs to a preset first type of interface;

A second interface rendering module, configured to generate a second target interface by performing interface rendering by the second operating system if the interface type belongs to a preset second type of interface.
A wearable device, comprising a memory and a processor, wherein a computer program is stored in the memory, characterized in that, when the computer program is executed by the processor, the processor executes the execution as in claims 1 to 13 Operation of any one of the interface rendering methods.
A computer-readable storage medium on which a computer program is stored, characterized in that, when the computer program is executed by a processor, the operation of the interface rendering method according to any one of claims 1 to 13 is implemented.