WO2021238387A1

WO2021238387A1 - Application execution method and apparatus

Info

Publication number: WO2021238387A1
Application number: PCT/CN2021/083899
Authority: WO
Inventors: 代海涛
Original assignee: 荣耀终端有限公司
Priority date: 2020-05-29
Filing date: 2021-03-30
Publication date: 2021-12-02
Also published as: CN111651254A

Abstract

An application execution method and apparatus. Said method comprises: a terminal device acquiring the category of an application; determining, according to the category of the application, a first execution domain from a plurality of execution domains; and executing the application in the first execution domain. Said method can be used to divide hardware into different execution domains, and allocate different categories of applications to corresponding execution domains, thereby improving the flexibility of system power consumption control, and reducing the overall power consumption level of systems.

Description

Method and device for executing application

Cross-references to related applications

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on May 29, 2020, with an application number of 202010479855.2. The application title is "a method and device for executing applications", the entire content of which is incorporated into this application by reference middle.

Technical field

This application relates to the field of terminals, and in particular to a method and device for executing applications.

Background technique

In wearable products, better user experience and more complete functions mean shorter battery life. Take a certain brand of device A as an example, under normal use, it only provides 18 hours of battery life. For example, watch the time 90 times during the battery life, watch 90 notifications, use the application (APP) for 45 minutes, and use Bluetooth to play music during 60 minutes of exercise. On the other hand, longer battery life means discounted user experience and incomplete features. Take device B of a certain brand as an example, under normal use, the battery life is 2 weeks. However, many user interface (UI) special effects of device B cannot be supported, for example, three-dimensional (3D) dials, UI transitions, vector rendering, and so on.

It can be seen from the above that the system cannot maintain a high battery life while providing a rich and cool user experience and/or complete functions. Therefore, how to solve the contradiction between battery life and user experience and functions is a problem that needs to be solved urgently.

Summary of the invention

The embodiments of the present application provide a method and device for executing applications, which are used to resolve the contradiction between battery life and user experience and functions.

In the first aspect, an embodiment of the present application provides a method for executing an application. The method includes: obtaining a category of an application; determining a first execution domain from a plurality of execution domains according to the category of the application; The application is executed in the application; the multiple execution domains are different execution domains obtained by dividing the hardware, and the multiple execution domains include a high-power execution domain and a low-power execution domain.

Using the above method, by dividing the hardware into different execution domains and assigning different types of applications to the corresponding execution domains, the flexibility of system power consumption control can be improved, and the overall power consumption level of the system can be reduced. Compared with the scenario where all applications are executed in the high-power execution domain, some applications are allocated to execute in the low-power execution domain. Since the power consumption level of the low-power execution domain is significantly lower than that of the high-power execution domain, the overall power consumption level can be reduced. Some applications are allocated to execute in the high-power execution domain, which can ensure user experience. Therefore, the contradiction between battery life and user experience and functions can be resolved.

In a possible design, the method further includes: controlling idle execution domains of the plurality of execution domains except for the first execution domain to enter an energy-saving state.

With the above design, the overall power consumption level of the system can be reduced.

In a possible design, the energy-saving state includes at least one of a standby state, a sleep state, and a deep sleep state.

In a possible design, the method further includes: determining that the shared peripheral that the application needs to access is exclusively occupied by the first execution domain, and setting a global exclusive flag for the shared peripheral; and when the shared peripheral is accessed After completion, the global exclusive identification set for the shared peripheral is cleared.

With the above design, by setting the global exclusive flag, other execution domains will not be able to obtain the control right of the peripheral, ensuring the exclusive access of the current execution domain to the peripheral, and avoiding data or status errors.

In a possible design, the method further includes: detecting a preset event, the preset event is used to trigger a second mode, and the second mode is the first characteristic of the plurality of characteristics included in the application The mode; the application includes multiple features, each feature corresponds to a functional segment of the application, the first feature is one of the multiple features; the mode for controlling the first feature starts from the first The mode is switched to the second mode, and the first mode is the initial mode of the first characteristic.

Using the above method can improve the flexibility of system power consumption control, and can reduce the overall power consumption level of the system.

In a possible design, the mode of the first characteristic includes at least two of a high experience mode, a low power consumption mode, and an off mode.

In a possible design, the mode of controlling the first characteristic in the application may be switched from the first mode to the second mode in the following manner, but not limited to: controlling the first characteristic from the first execution The domain is switched to a second execution domain for execution, wherein the first mode corresponds to the first execution domain, and the second mode corresponds to the second execution domain.

The above method avoids the fixed execution domain allocation method. According to the detected preset event, the characteristics in the application can be dynamically switched to the corresponding execution domain, which can improve the flexibility of system power consumption control and reduce the overall system Power consumption level.

In a second aspect, an embodiment of the present application provides a method for executing an application. The method includes: acquiring a category of a first characteristic, where the first characteristic is one of a plurality of characteristics included in an application, and each characteristic corresponds to all characteristics. A functional segment of the application; a first execution domain is determined from a plurality of execution domains according to the category of the first characteristic, and the first characteristic is executed in the first execution domain; the plurality of execution domains are pairs Different execution domains obtained by hardware division, and the multiple execution domains include a high power consumption execution domain and a low power consumption execution domain.

Using the above method, by dividing the hardware into different execution domains and assigning different types of characteristics to the corresponding execution domains, the flexibility of system power consumption control can be improved, and more detailed power consumption control can be achieved, which can reduce The overall power consumption level of the system.

In a possible design, the method further includes: acquiring a category of a second characteristic, where the second characteristic is one of a plurality of characteristics included in the application, and the second characteristic is different from the first characteristic; Determine a second execution domain from a plurality of execution domains according to the category of the second characteristic, execute the second characteristic in the second execution domain, and the second execution domain is different from the first execution domain, And the first characteristic and the second characteristic communicate through an IPC device or pipe.

With the above design, different types of features are allocated to the corresponding execution domains, which can improve the flexibility of system power consumption control. At the same time, the features executed in different execution domains can communicate through IPC devices or pipes.

In a possible design, the method further includes: controlling idle execution domains of the plurality of execution domains except for the first execution domain and the second execution domain to enter an energy-saving state.

In a possible design, the method further includes: determining that the shared peripheral that needs to be accessed by the first feature is exclusively occupied by the first execution domain, and setting a global exclusive flag for the shared peripheral; After being accessed, the global exclusive identifier set for the shared peripheral is cleared.

In a possible design, the method further includes: detecting a preset event, the preset event is used to trigger a second mode, and the second mode is a mode of the first characteristic; The mode is switched from the first mode to the second mode, and the first mode is the initial mode of the first characteristic.

In a possible design, the mode of controlling the first characteristic to switch from the first mode to the second mode may adopt but not limited to the following manner: controlling the first characteristic to switch from the first execution domain to The third execution domain is executed, wherein the first mode corresponds to the first execution domain, and the second mode corresponds to the third execution domain.

In a third aspect, an embodiment of the present application provides a communication device, the device includes a module for executing any one of the first aspect and the first aspect; or the device includes a module for executing the second aspect And any of the possible design modules in the second aspect.

In a fourth aspect, an embodiment of the present application provides a communication device, including a processor and an interface circuit, the interface circuit is used to receive signals from other communication devices other than the communication device and transmit them to the processor or The signal from the processor is sent to other communication devices other than the communication device, and the processor is used to implement any one of the first aspect and the first aspect through logic circuits or execution code instructions, Or realize any one of the possible designs of the second aspect and the second aspect.

In a fifth aspect, an embodiment of the present application provides a wearable device, including a processor and a memory, the memory is used to store a program, and the processor invokes the memory to execute any one of the first aspect and the first aspect Possible design, or any one of the second aspect and the second aspect.

The processor is used to implement any one of the possible designs of the first aspect and the first aspect, or to implement any one of the second aspect and the second aspect, through a logic circuit or executing code instructions.

In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium in which a computer program or instruction is stored. When the computer program or instruction is executed by a communication device, the first aspect and the first aspect are implemented. Any one of the possible designs, or the realization of any one of the second aspect and the second aspect.

In the seventh aspect, the embodiments of the present application provide a computer program product containing a program, which, when it runs on a communication device, enables the communication device to execute any one of the possible designs of the first aspect and the first aspect, or execute the first aspect Any one of the possible designs of the second aspect and the second aspect.

Description of the drawings

FIG. 1 is a schematic diagram of an example of a terminal device in an embodiment of the application;

2(a) and 2(b) are schematic diagrams of the structure of the terminal device in the embodiment of the application;

FIG. 3 is one of the schematic diagrams of a method for executing an application in an embodiment of this application;

4 is a schematic diagram of the correspondence between application classification and execution domain classification in an embodiment of this application;

FIG. 5 is one of the specific flowcharts of executing the application in the embodiment of this application;

FIG. 6 is the second specific flowchart of the application execution in the embodiment of this application;

FIG. 7 is a second schematic diagram of a method for executing an application in an embodiment of this application;

FIG. 8 is a schematic diagram of the correspondence between feature classification and execution domain classification in an embodiment of this application;

FIG. 9 is the third specific flowchart of the application execution in the embodiment of this application;

FIG. 10 is the fourth specific flowchart of the application execution in the embodiment of this application;

FIG. 11 is one of the schematic structural diagrams of a communication device in an embodiment of this application;

FIG. 12 is the second structural diagram of a communication device in an embodiment of this application.

Detailed ways

The embodiments of the present application will be described below in conjunction with the drawings.

As shown in FIG. 1, the embodiments of the present application can be applied to various terminal devices 100, such as mobile phones, personal computers (PC), tablets, wearable devices, and so on.

Fig. 2(a) shows one of the schematic structural diagrams of the terminal device 100. The terminal device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, and an antenna 2. , Mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, earphone jack 170D, sensor module 180, buttons 190, motor 191, indicator 192, camera 193, display screen 194, and Subscriber identification module (subscriber identification module, SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, and ambient light Sensor 180L, bone conduction sensor 180M, etc.

It can be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the terminal device 100. In other embodiments of the present application, the terminal device 100 may include more or fewer components than shown, or combine certain components, or split certain components, or arrange different components. The illustrated components can be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), and an image signal processor. (image signal processor, ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural-network processing unit (NPU) Wait. Among them, the different processing units may be independent devices or integrated in one or more processors.

The controller may be the nerve center and command center of the terminal device 100. The controller can generate operation control signals according to the instruction operation code and timing signals to complete the control of fetching and executing instructions.

A memory may also be provided in the processor 110 to store instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory can store instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to use the instruction or data again, it can be directly called from the memory. Repeated accesses are avoided, the waiting time of the processor 110 is reduced, and the efficiency of the system is improved.

In some embodiments, the processor 110 may include one or more interfaces. The interface can include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, and a universal asynchronous transmitter (universal asynchronous transmitter) interface. receiver/transmitter, UART) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, subscriber identity module (SIM) interface, and / Or Universal Serial Bus (USB) interface, etc.

The I2C interface is a bidirectional synchronous serial bus, which includes a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple sets of I2C buses. The processor 110 may couple the touch sensor 180K, charger, flash, camera 193, etc., respectively through different I2C bus interfaces. For example, the processor 110 may couple the touch sensor 180K through an I2C interface, so that the processor 110 and the touch sensor 180K communicate through the I2C bus interface to implement the touch function of the terminal device 100.

The I2S interface can be used for audio communication. In some embodiments, the processor 110 may include multiple sets of I2S buses. The processor 110 may be coupled with the audio module 170 through an I2S bus to implement communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 may transmit audio signals to the wireless communication module 160 through an I2S interface, so as to realize the function of answering calls through a Bluetooth headset.

The PCM interface can also be used for audio communication to sample, quantize and encode analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled through a PCM bus interface. In some embodiments, the audio module 170 may also transmit audio signals to the wireless communication module 160 through the PCM interface, so as to realize the function of answering calls through the Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

The UART interface is a universal serial data bus used for asynchronous communication. The bus can be a two-way communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, the UART interface is generally used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 through the UART interface to realize the Bluetooth function. In some embodiments, the audio module 170 may transmit audio signals to the wireless communication module 160 through a UART interface, so as to realize the function of playing music through a Bluetooth headset.

The MIPI interface can be used to connect the processor 110 with the display screen 194, the camera 193 and other peripheral devices. The MIPI interface includes camera serial interface (camera serial interface, CSI), display serial interface (display serial interface, DSI), etc. In some embodiments, the processor 110 and the camera 193 communicate through a CSI interface to implement the shooting function of the terminal device 100. The processor 110 and the display screen 194 communicate through a DSI interface to realize the display function of the terminal device 100.

The GPIO interface can be configured through software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 with the camera 193, the display screen 194, the wireless communication module 160, the audio module 170, the sensor module 180, and so on. The GPIO interface can also be configured as an I2C interface, I2S interface, UART interface, MIPI interface, etc.

The USB interface 130 is an interface that complies with the USB standard specification, and specifically may be a Mini USB interface, a Micro USB interface, a USB Type C interface, and so on. The USB interface 130 can be used to connect a charger to charge the terminal device 100, and can also be used to transfer data between the terminal device 100 and peripheral devices. It can also be used to connect earphones and play audio through earphones. This interface can also be used to connect to other terminal devices, such as AR devices.

It can be understood that the interface connection relationship between the modules illustrated in the embodiment of the present invention is merely a schematic illustration, and does not constitute a structural limitation of the terminal device 100. In other embodiments of the present application, the terminal device 100 may also adopt different interface connection modes in the foregoing embodiments, or a combination of multiple interface connection modes.

The charging management module 140 is used to receive charging input from the charger. Among them, the charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive the charging input of the wired charger through the USB interface 130. In some embodiments of wireless charging, the charging management module 140 may receive the wireless charging input through the wireless charging coil of the terminal device 100. While the charging management module 140 charges the battery 142, it can also supply power to the terminal device through the power management module 141.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charging management module 140, and supplies power to the processor 110, the internal memory 121, the external memory, the display screen 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle times, and battery health status (leakage, impedance). In some other embodiments, the power management module 141 may also be provided in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may also be provided in the same device.

The wireless communication function of the terminal device 100 can be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, and the baseband processor.

The antenna 1 and the antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the terminal device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna can be used in combination with a tuning switch.

The mobile communication module 150 may provide a wireless communication solution including 2G/3G/4G/5G and the like applied to the terminal device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), and the like. The mobile communication module 150 can receive electromagnetic waves by the antenna 1, and perform processing such as filtering, amplifying and transmitting the received electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor, and convert it into electromagnetic wave radiation via the antenna 1. In some embodiments, at least part of the functional modules of the mobile communication module 150 may be provided in the processor 110. In some embodiments, at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be provided in the same device.

The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low frequency baseband signal to be sent into a medium and high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. The low-frequency baseband signal is processed by the baseband processor and then passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.), or displays an image or video through the display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be provided in the same device as the mobile communication module 150 or other functional modules.

The wireless communication module 160 can provide applications on the terminal device 100 including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), and global navigation satellites. System (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be sent from the processor 110, perform frequency modulation, amplify it, and convert it into electromagnetic waves to radiate through the antenna 2.

In some embodiments, the antenna 1 of the terminal device 100 is coupled with the mobile communication module 150, and the antenna 2 is coupled with the wireless communication module 160, so that the terminal device 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), broadband Code division multiple access (wideband code division multiple access, WCDMA), time-division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC , FM, and/or IR technology, etc. The GNSS may include the global positioning system (GPS), the global navigation satellite system (GLONASS), the Beidou navigation satellite system (BDS), and the quasi-zenith satellite system (quasi). -zenith satellite system, QZSS) and/or satellite-based augmentation systems (SBAS).

The terminal device 100 implements a display function through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and is used for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 194 is used to display images, videos, and the like. The display screen 194 includes a display panel. The display panel can adopt liquid crystal display (LCD), organic light-emitting diode (OLED), active matrix organic light-emitting diode or active-matrix organic light-emitting diode (active-matrix organic light-emitting diode). AMOLED, flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, quantum dot light-emitting diode (QLED), etc. In some embodiments, the terminal device 100 may include one or N display screens 194, and N is a positive integer greater than one.

The terminal device 100 can implement a shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, and an application processor.

The ISP is used to process the data fed back from the camera 193. For example, when taking a picture, the shutter is opened, the light is transmitted to the photosensitive element of the camera through the lens, the light signal is converted into an electrical signal, and the photosensitive element of the camera transfers the electrical signal to the ISP for processing and is converted into an image visible to the naked eye. ISP can also optimize the image noise, brightness, and skin color. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, the ISP may be provided in the camera 193.

The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and is projected to the photosensitive element. The photosensitive element may be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then transfers the electrical signal to the ISP to convert it into a digital image signal. ISP outputs digital image signals to DSP for processing. DSP converts digital image signals into standard RGB, YUV and other formats of image signals. In some embodiments, the terminal device 100 may include one or N cameras 193, and N is a positive integer greater than one.

Digital signal processors are used to process digital signals. In addition to digital image signals, they can also process other digital signals. For example, when the terminal device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the energy of the frequency point.

Video codecs are used to compress or decompress digital video. The terminal device 100 may support one or more video codecs. In this way, the terminal device 100 can play or record videos in multiple encoding formats, such as: moving picture experts group (MPEG) 1, MPEG2, MPEG3, MPEG4, and so on.

NPU is a neural-network (NN) computing processor. By drawing on the structure of biological neural networks, for example, the transfer mode between human brain neurons, it can quickly process input information, and it can also continuously self-learn. Through the NPU, applications such as intelligent cognition of the terminal device 100 can be realized, such as image recognition, face recognition, voice recognition, text understanding, and so on.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to realize the data storage function. For example, save music, video and other files in an external memory card.

The internal memory 121 may be used to store computer executable program code, where the executable program code includes instructions. The processor 110 executes various functional applications and data processing of the terminal device 100 by running instructions stored in the internal memory 121. The internal memory 121 may include a storage program area and a storage data area. Among them, the storage program area can store an operating system, at least one application program (such as a sound playback function, an image playback function, etc.) required by at least one function. The data storage area can store data (such as audio data, phone book, etc.) created during the use of the terminal device 100. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash storage (UFS), and the like.

The terminal device 100 can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor. For example, music playback, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal for output, and is also used to convert an analog audio input into a digital audio signal. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be provided in the processor 110, or part of the functional modules of the audio module 170 may be provided in the processor 110.

The speaker 170A, also called "speaker", is used to convert audio electrical signals into sound signals. The terminal device 100 can listen to music through the speaker 170A, or listen to a hands-free call.

The receiver 170B, also called a "handset", is used to convert audio electrical signals into sound signals. When the terminal device 100 answers a call or voice message, it can receive the voice by bringing the receiver 170B close to the human ear.

The microphone 170C, also called "microphone", "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can make a sound by approaching the microphone 170C through the human mouth, and input the sound signal into the microphone 170C. The terminal device 100 may be provided with at least one microphone 170C. In other embodiments, the terminal device 100 may be provided with two microphones 170C, which can implement noise reduction functions in addition to collecting sound signals. In other embodiments, the terminal device 100 may also be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, and realize directional recording functions.

The earphone interface 170D is used to connect wired earphones. The earphone interface 170D may be a USB interface 130, or a 3.5mm open mobile terminal platform (OMTP) standard interface, or a cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor 180A is used to sense the pressure signal and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be provided on the display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors and so on. The capacitive pressure sensor may include at least two parallel plates with conductive materials. When a force is applied to the pressure sensor 180A, the capacitance between the electrodes changes. The terminal device 100 determines the strength of the pressure according to the change in capacitance. When a touch operation acts on the display screen 194, the terminal device 100 detects the intensity of the touch operation according to the pressure sensor 180A. The terminal device 100 may also calculate the touched position based on the detection signal of the pressure sensor 180A. In some embodiments, touch operations that act on the same touch position but have different touch operation intensities can correspond to different operation instructions. For example: when a touch operation whose intensity is less than the first pressure threshold is applied to the short message application icon, an instruction to view the short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold acts on the short message application icon, an instruction to create a new short message is executed.

The gyro sensor 180B may be used to determine the movement posture of the terminal device 100. In some embodiments, the angular velocity of the terminal device 100 around three axes (ie, x, y, and z axes) can be determined by the gyroscope sensor 180B. The gyro sensor 180B can be used for image stabilization. Exemplarily, when the shutter is pressed, the gyroscope sensor 180B detects the shaking angle of the terminal device 100, and calculates the distance that the lens module needs to compensate according to the angle, so that the lens can counteract the shaking of the terminal device 100 through a reverse movement to achieve anti-shake. The gyro sensor 180B can also be used for navigation and somatosensory game scenes.

The air pressure sensor 180C is used to measure air pressure. In some embodiments, the terminal device 100 calculates the altitude based on the air pressure value measured by the air pressure sensor 180C to assist positioning and navigation.

The magnetic sensor 180D includes a Hall sensor. The terminal device 100 may use the magnetic sensor 180D to detect the opening and closing of the flip holster. In some embodiments, when the terminal device 100 is a flip machine, the terminal device 100 can detect the opening and closing of the flip according to the magnetic sensor 180D. Then, according to the detected opening and closing state of the leather case or the opening and closing state of the flip cover, features such as automatic unlocking of the flip cover are set.

The acceleration sensor 180E can detect the magnitude of the acceleration of the terminal device 100 in various directions (generally three axes). When the terminal device 100 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of the terminal device, applied to applications such as horizontal and vertical screen switching, pedometer and so on.

Distance sensor 180F, used to measure distance. The terminal device 100 can measure the distance by infrared or laser. In some embodiments, when shooting a scene, the terminal device 100 may use the distance sensor 180F to measure the distance to achieve fast focusing.

The proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector such as a photodiode. The light emitting diode may be an infrared light emitting diode. The terminal device 100 emits infrared light to the outside through the light emitting diode. The terminal device 100 uses a photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the terminal device 100. When insufficient reflected light is detected, the terminal device 100 can determine that there is no object near the terminal device 100. The terminal device 100 can use the proximity light sensor 180G to detect that the user holds the terminal device 100 close to the ear to talk, so as to automatically turn off the screen to save power. The proximity light sensor 180G can also be used in leather case mode, and the pocket mode will automatically unlock and lock the screen.

The ambient light sensor 180L is used to sense the brightness of the ambient light. The terminal device 100 can adaptively adjust the brightness of the display screen 194 according to the perceived brightness of the ambient light. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also cooperate with the proximity light sensor 180G to detect whether the terminal device 100 is in a pocket to prevent accidental touch.

The fingerprint sensor 180H is used to collect fingerprints. The terminal device 100 can use the collected fingerprint characteristics to implement fingerprint unlocking, access application locks, fingerprint photographs, fingerprint answering calls, and so on.

The temperature sensor 180J is used to detect temperature. In some embodiments, the terminal device 100 uses the temperature detected by the temperature sensor 180J to execute a temperature processing strategy. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold value, the terminal device 100 reduces the performance of the processor located near the temperature sensor 180J, so as to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, the terminal device 100 heats the battery 142 to avoid abnormal shutdown of the terminal device 100 due to low temperature. In some other embodiments, when the temperature is lower than another threshold, the terminal device 100 boosts the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperature.

Touch sensor 180K, also called "touch panel". The touch sensor 180K may be provided on the display screen 194, and the touch screen is composed of the touch sensor 180K and the display screen 194, which is also called a “touch screen”. The touch sensor 180K is used to detect touch operations acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. The visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180K may also be disposed on the surface of the terminal device 100, which is different from the position of the display screen 194.

The bone conduction sensor 180M can acquire vibration signals. In some embodiments, the bone conduction sensor 180M can acquire the vibration signal of the vibrating bone mass of the human voice. The bone conduction sensor 180M can also contact the human pulse and receive the blood pressure pulse signal. In some embodiments, the bone conduction sensor 180M may also be provided in the earphone, combined with the bone conduction earphone. The audio module 170 can parse the voice signal based on the vibration signal of the vibrating bone block of the voice obtained by the bone conduction sensor 180M, and realize the voice function. The application processor may analyze the heart rate information based on the blood pressure beating signal obtained by the bone conduction sensor 180M, and realize the heart rate detection function.

The button 190 includes a power-on button, a volume button, and so on. The button 190 may be a mechanical button. It can also be a touch button. The terminal device 100 may receive key input, and generate key signal input related to user settings and function control of the terminal device 100.

The motor 191 can generate vibration prompts. The motor 191 can be used for incoming call vibration notification, and can also be used for touch vibration feedback. For example, touch operations that act on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. Acting on touch operations in different areas of the display screen 194, the motor 191 can also correspond to different vibration feedback effects. Different application scenarios (for example: time reminding, receiving information, alarm clock, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

The indicator 192 may be an indicator light, which may be used to indicate the charging status, power change, or to indicate messages, missed calls, notifications, and so on.

The SIM card interface 195 is used to connect to the SIM card. The SIM card can be inserted into the SIM card interface 195 or pulled out from the SIM card interface 195 to achieve contact and separation with the terminal device 100. The terminal device 100 may support 1 or N SIM card interfaces, and N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. The same SIM card interface 195 can insert multiple cards at the same time. The types of the multiple cards can be the same or different. The SIM card interface 195 can also be compatible with different types of SIM cards. The SIM card interface 195 can also be compatible with external memory cards. The terminal device 100 interacts with the network through the SIM card to implement functions such as call and data communication. In some embodiments, the terminal device 100 adopts an eSIM, that is, an embedded SIM card. The eSIM card can be embedded in the terminal device 100 and cannot be separated from the terminal device 100.

Fig. 2(b) shows the second structural diagram of the terminal device 100. The terminal device 100 has a processor 211, a memory 205, and various software loaded in the memory, including an operating system 201, a desktop program 202, a synthesizer 203, and a service program 204. At the same time, the terminal device 100 also has various peripherals, including communication devices 206 (such as bluetooth low energy (BLE), WiFi, modems, etc.), sensors 207 (such as gravity sensors, acceleration sensors, and angular velocity sensors). , Photoplethysmography (PPG) sensor, global positioning system (GPS) sensor, fingerprint sensor, etc.), input device 208 (such as keyboard, touch screen, etc.), memory 209 (such as built-in non-removable memory, Removable library card, etc.), output device 210 (such as printer, etc.), processor 211 (such as ARM, X86, MIPS, etc.), vibration device 212 (such as linear motor, eccentric motor, etc.), display device 213 (such as liquid crystal display) (liquid crystal display, LCD) screen, organic light-emitting diode (OLED) screen, active matrix organic light-emitting diode or active-matrix organic light-emitting diode (active-matrix organic light-emitting diode, AMOLED screen, etc.), camera equipment 214 (such as a front camera, a rear camera, a time of flight (TOF) camera, an infrared camera, etc.).

Generally speaking, high experience means higher frequency central processing unit (CPU), graphics processing unit (GPU), and more complex calculations and graphics and image processing. In terminal devices, especially devices such as mobile phones and wearable devices, due to the limited battery capacity, terminal devices that pursue high experience will inevitably lead to a decrease in battery life. Terminal devices pursuing long battery life may use specific hardware, such as ink screens (not active refresh, optional backlight), low-power memory (low working voltage), static memory (not active refresh), and low-power CPU (It may also be a microcontroller unit (MCU), low-power GPU (or GPU may be eliminated) to meet low power consumption at the hardware level, and at the same time cooperate with more stringent power management strategies at the software level (for example, global standby, hibernation) , Kill background processes by default, etc.) to achieve battery life goals. The above hardware and software design strategies generally lead to a decline in user experience. For example, ink screens will cause serious refresh delays and do not support color. Low power Consuming logic devices (memory, CPU, GPU) will cause the system to respond slowly. The software's aggressive standby or default killing process will cause the terminal device to become less responsive, and task switching is not very user-friendly (for example, applications placed in the background) After restoring to the foreground, the original state of the application cannot be restored).

In order to solve the contradiction between battery life and user experience and functions, a solution is proposed in the prior art: the system is configured with a "low power consumption mode". After the system enters the "low power consumption mode", all functions are Running in the "low power consumption mode", the system will try to close the "excess" functions and special effects at this time. At the same time, the hardware and sensors that these functions depend on also enter the dormant or power-off state, and the main CPU and main memory are dynamically reduced. Operating frequency, the screen works at a lower brightness and color depth, try to reduce the number of screen refreshes and content refresh. Using the above solution can extend the battery life to a certain extent, but because the hardware performance in the "low power mode" is very limited, and the functions are much less than in the normal mode, the user experience is also significantly reduced.

In addition, the prior art also proposes a solution: the system configures an "exclusive hardware mode". The system only provides some functions to the user in the "exclusive hardware mode". All the underlying software (such as operating systems, drivers, file systems, etc.) that these functions depend on run on an exclusive extremely low-power processor. The main CPU is completely powered off. The functions provided by peripherals and sensors in this mode are turned on on demand. Adopt the above-mentioned scheme, first, because this scheme uses the exclusive hardware, therefore increases the cost of the system. At the same time, because the performance of the exclusive hardware is very low, the functions in this mode are limited, only some basic functions are included, and the user experience is not as good as the normal mode. At the same time, in order to switch the system to the normal mode, since the main CPU is completely powered off, the switching takes a long time.

The following briefly describes the technical concepts involved in the embodiments of the present application.

In this embodiment of the application, the system is composed of an application, an application loader, and an execution domain.

Among them, the execution domain refers to a combination or range of hardware. In a specific execution domain, only hardware belonging to the execution domain can be accessed. The system can divide the hardware into multiple execution domains. Wherein, the division of the execution domain described above may be pre-divided (that is, statically divided), or it may be dynamically divided. The division of the execution domain described above may be divided in a physical way, or divided in a logical way. Among them, the so-called physical division refers to the hardware entity corresponding to a specific execution domain, and the so-called logical division refers to the determination of the execution domain through dynamic configuration and control.

Exemplarily, the system may divide the hardware into a first execution domain and a second execution domain, where the first execution domain is used to execute applications or performance with lower power consumption requirements, or applications or performance with higher battery life requirements, or Experience less demanding applications or performance. The second execution domain is used for applications or performance with higher power consumption requirements, or applications or performance with lower battery life requirements, or applications or performance with higher experience requirements.

Exemplarily, the execution domain is built on a dual CPU (MCU+AP) hardware architecture. Among them, MCU is weak in performance and low in power consumption, and it is a non-full-featured low-speed CPU. Application processor (AP) is a full-featured high-speed CPU, most of which will also integrate GPU, Internet service provider (ISP), high-speed dynamic memory controller, etc., such as AP can be used as the main mobile phone CPU, high performance and high power consumption.

The system divides the hardware into 2 execution domains, including MCU domain and AP domain. Among them, in the AP domain, the AP and the GPU on the AP side are used to provide users with a higher user experience, and the power consumption is higher. AP is the main CPU of the AP domain. The MCU domain is used to provide users with basic functions and a lower user experience, with lower power consumption. MCU is the main CPU of the MCU domain. The number of execution domains may also be greater than 2, which is not limited in the embodiment of the present application.

Each execution domain can access shared peripherals, which can also be referred to as public peripherals, can also access their own exclusive peripherals, or can be referred to as dedicated peripherals. As a kind of peripherals, the screen can be shared or exclusive. Among them, typical shared peripherals include touch screens, linear acceleration sensors, angular velocity sensors, PPG sensors, external memory (such as fixed or pluggable memory), cameras and image sensors. Typical exclusive peripherals include GPUs. Illustratively, GPUs are exclusively occupied by high-power execution domains. It should be understood that the foregoing division of shared peripherals and exclusive peripherals is only an example, and is not a limitation of the embodiments of the present application. Among them, in terms of physical connection, peripherals are fixedly connected to the external bus of a specific processor. Exemplarily, the MCU has two roles: one is the main CPU in the low-power domain, and the other is the public IO Hub. Among them, because the MCU has very low power consumption and can always keep working, the MCU can be used as a public IO Hub. For example, the Bluetooth controller is connected to the external bus of the MCU. If the AP needs to transmit data via Bluetooth, it needs to transfer it through the MCU first. At the software and/or logic level, peripherals can be considered to work in different execution domains.

The application loader is used to load the executable image and the corresponding data, symbols and other additional information into the memory, and wait for the operating system (OS) to schedule the CPU to execute. Typical application loader implementations include class loader in Java runtime, execve in Linux, ntdll.dll in windows, and so on.

In the embodiments of the present application, a characteristic refers to a functional segment of an application or software. An application can include multiple features. For example, the Home application includes features such as dial, weather, altitude, battery level, and Bluetooth status. Among them, the dial feature is responsible for providing the display of the dial, the weather feature is responsible for displaying the weather information of the specified area on the dial, the altitude feature is responsible for displaying the altitude information of the specified area on the dial, and the battery power and Bluetooth status are responsible for providing the display of the system status.

Dial features can also be divided into sub-features such as video dial, 3D dial, album dial, and standby dial. Among them, video dial, 3D dial, album dial, these features provide complex screen effects. The album dial also needs to read image files from the system album. The standby dial only provides a simple time display function, without complicated screen effects, and no need to obtain other system data.

For another example, various sports applications (such as running, swimming, outdoor, etc.) may also include features such as heart rate monitoring, wrist posture detection (such as raising the wrist to brighten the screen), and pressure monitoring.

The embodiment of the present application provides a method for executing an application to resolve the contradiction between battery life and user experience and functions. The execution subject of this method may be a terminal device, as shown in FIG. 1, such as a mobile phone or a smart watch, or may also be an application loader in the system. The following takes the application loader as an example for description. As shown in Figure 3, the method includes:

S301: The application loader obtains the category of the application.

Exemplarily, the system provides a notification mechanism to let the outside know the loading status and events, for example, a callback, and the application loader can obtain application information through the callback.

The application information includes the category of the application. In this embodiment, applications are divided into multiple categories. Exemplarily, applications are divided into a first category of applications and a second category of applications, and the basis for dividing the applications may include factors such as battery life, power consumption, and experience. For example, applications can be divided into long battery life applications (also referred to as low experience applications) and high experience applications (also referred to as short battery life applications). Or, according to the battery life characteristics of the application, the application can be divided into a long battery life application and a short battery life application. Or, according to the experience characteristics of the application, the application can be divided into a low-experience application and a high-experience application. Or, according to the power consumption characteristics of the application, the application can be divided into a low power consumption application and a high power consumption application. It is understandable that the number of application categories can also be greater than 2, and the above examples are not limited to the embodiments of the present application.

Among them, typical long-endurance applications include various sports APPs (running, swimming, outdoor, etc.). Typical high-experience applications include cool dials, interactive dials, video games, music playback, etc.

It is understandable that the number of execution domains and the number of application categories can be the same or different. Exemplarily, the number of classifications of applications may be greater than the number of execution domains, or the number of execution domains may be greater than the number of classifications of applications. For example, the system can further divide the low-power execution domain into more subdomains.

S302: The application loader determines a first execution domain from multiple execution domains according to the category of the application, and executes the application in the first execution domain.

Exemplarily, when the application loader pulls up an application, according to the acquired category of the application, the execution domain corresponding to the category of the application is queried, that is, the first execution domain is determined, where the correspondence between the category of the application and the execution domain Can be configured in advance. After determining the first execution domain, the application loader allocates the application to the first execution domain for execution.

For example, the application is a cool dial, the category of the cool dial is a high-experience application, and the application loader determines an AP domain (that is, a high-power execution domain) for a high-experience application according to the category of the cool dial. For another example, the application is a certain sports application, the category of the sports application is a long-life application, and the application loader determines the MCU domain (ie, a low-power execution domain) according to the category of the sports application as a long-life application.

At the same time, the application loader controls the idle execution domains other than the first execution domain to enter the energy-saving state. Wherein, the energy-saving state includes at least one of a standby state, a sleep state, and a deep sleep state. Exemplarily, the idle execution domain preferentially selects to enter the standby state.

Taking the Linux system as an example, the meanings of the above-mentioned energy-saving states are as follows:

The standby state means that the CPU is powered on and the memory is powered on. At this time, the CPU is working at a very low frequency. If it is a multi-core CPU, some of its cores will also be shut down. Since the CPU is always working, there is no need to restore the state, just increase the CPU working frequency and wake up other cores to work at full speed.

The sleep state means that the CPU is powered off and the memory is powered on. If you want to resume the CPU operation at this time, you need to wake up the CPU first, and then the CPU restores the state saved in the memory to its own register.

The deep sleep state means that both the CPU and memory are powered off. If you want the CPU to resume operation at this time, you need to reboot, that is, load the state and/or data of the CPU from the external memory.

It should be understood that the energy-saving state may also include other states, and the various states shown in the above examples may have different meanings in different systems.

In addition, when the system detects a preset operation, the application loader can control the first execution domain to enter the energy-saving state. The following takes Example 1 to Example 4 as examples for description.

Example 1: When the system detects that the user turns off the screen and the execution domain of the current application is a high-power execution domain, the application controller can control the high-power execution domain to enter the standby state.

Example 2: When the system detects that the user has not operated for a period of time (configurable, 5s by default), and the execution domain of the current application is a high-power execution domain, the application loader can control the high-power execution domain to enter the standby state.

Example 3: When the system detects that the current application is switched to the background by the user, and another application is started at the same time, the execution domain of the current application is a high-power execution domain, and the category of the newly started application is a long battery life application, then the newly started application The application is loaded into the low-power execution domain, and at this time the high-power execution domain has no other foreground applications, the application loader can control the high-power execution domain to enter the standby state.

Example 4: When the system detects that the current application is running with a low power consumption feature, and the execution domain of the current application is a high power consumption execution domain, the application loader can control the high power consumption execution domain to enter the standby state. For example, the Home application includes features such as dial, weather, altitude, battery level, and Bluetooth status. Further, the dial features can be divided into sub-features such as video dials, 3D dials, album dials, and standby dials. Among them, video dials, 3D dials, and album dials are high-experience features, and these features provide complex screen effects. The album dial also needs to read image files from the system album. The standby dial only provides a simple time display function, without complicated screen effects, and no need to obtain other system data. It is a feature of low power consumption. Therefore, when the dial feature is a standby dial, the application loader can control the high power consumption execution domain to enter the standby state.

Further, for the foregoing examples 1 to 4, when the high power consumption execution domain has been in the standby state for more than a period of time and has not exited, the high power consumption execution domain enters the sleep state. Generally, the deep sleep state requires the user to perform an explicit switch, and recovery from the deep sleep state requires a reboot.

It should be understood that when the system detects the reverse operation of Example 1 to Example 4, the application loader controls the high power consumption execution domain to exit from the standby state.

In addition, the application loader determines that the shared peripheral that the application needs to access is exclusively occupied by the first execution domain, and sets a global exclusive flag for the shared peripheral. After the shared peripheral is accessed, it clears the global exclusive flag set for the shared peripheral . Therefore, through this identification, other execution domains will not be able to obtain the control right of the peripheral, ensuring the exclusive access of the current execution domain to the peripheral, and avoiding data or status errors. It should be understood that for a CPU or Hub, peripherals are generally child nodes on the system and only support a single parent node. Therefore, regardless of whether a global exclusive flag is set, peripherals are generally exclusive. At the same time, peripherals can be time-division multiplexed or address multiplexed. Only one CPU can access during a multiplexing period.

Further, when the system detects a preset event, it queries the mode corresponding to the preset event, that is, determines the second mode, which is the mode of the first characteristic corresponding to the preset event, and controls the mode of the first characteristic in the application The mode is switched from the first mode to the second mode, and the first mode is the initial mode of the first characteristic. The application includes multiple characteristics, and the first characteristic is one of the multiple characteristics. Mode can refer to a certain state of a feature, which can be expressed in terms of appearance, behavior, etc., in which a feature can have multiple modes.

Illustratively, taking a smart watch as an example, the preset events may include but are not limited to the following events: "smart watch is removed from the wrist", "user raises the wrist", and "entering the night time period".

Exemplarily, the mode of the first characteristic includes at least two of a high experience mode, a low power consumption mode, and an off mode. In addition, the mode of the first characteristic may also adopt other designs, which are not limited in the embodiment of the present application. The mode of the characteristic has a corresponding relationship with the execution domain. For example, the modes of the first characteristic include a high experience mode and a low power consumption mode, the high experience mode corresponds to the high power consumption execution domain, and the low power consumption mode corresponds to the low power consumption execution domain.

For another example, the modes of the first characteristic include high experience mode, low power consumption mode, and shutdown mode. The high experience mode corresponds to the high power execution domain, the low power mode corresponds to the low power execution domain, and the shutdown mode does not correspond to any execution domain. .

Therefore, it can be understood that the number of modes and the number of execution domains of the characteristic may be the same or different.

Further, switching the mode of controlling the first characteristic in the application from the first mode to the second mode may refer to controlling the first characteristic to be executed from the first execution domain to the second execution domain, where the first mode corresponds to the first execution Domain, the second mode corresponds to the second execution domain. Exemplarily, when the mode of the first characteristic is switched from the high experience mode to the low power consumption mode, the execution domain of the first characteristic is controlled to switch from the high power consumption execution domain to the low power consumption execution domain. Or, switching the mode of controlling the first characteristic in the application from the first mode to the second mode may refer to controlling the first characteristic to stop executing in the first execution domain, that is, turning off the first characteristic. Exemplarily, when the mode of the first characteristic is switched from the high experience mode to the closed mode, the first characteristic is controlled to be turned off.

The following takes the dial characteristics in the cool dial as an example to illustrate the mode switching of the dial characteristics. Suppose the system includes two execution domains, namely a low-power execution domain and a high-power execution domain. The modes of the dial feature include high experience mode, low power consumption mode and off mode. The initial execution domain of the dial feature is the low-power execution domain, and the initial mode of the dial feature is the low-power mode.

Scenario 1: The user raises his wrist. When the system detects that the user raises the wrist, the dial feature is switched from the low-power consumption mode to the high-experience mode, and accordingly, the dial feature is switched from the low-power execution domain to the high-power execution domain. Exemplarily, at this time, the AP in the high-power execution domain and the GPU on the AP side are responsible for the calculation and drawing of the 3D model, lighting, and interaction on the dial. Users get a cool dial experience with full functions and special effects, such as a pinball game or a rolex of light and shadow.

Scenario 2: The user puts down his wrist. After the system detects that the user puts down the wrist for 3 seconds (the specific time interval can be set), the system determines that the user puts down the wrist for more than the specified time interval, the dial feature switches from the high experience mode to the low power consumption mode, and accordingly, the dial feature changes from high power consumption The execution domain switches to low-power execution domain execution. Due to the hardware capabilities of the low-power execution domain, the 3D model and lighting are not available, and the user gets a basic watch face that can check the time.

Scenario 3: The user takes the smart watch off the wrist. Scenario 3 is similar to scenario 2. The dial feature switches from a high experience mode to a low power consumption mode. Correspondingly, the dial feature switches from a high-power execution domain to a low-power execution domain.

Scenario 4: Enter the night time period. Since in most cases, the user has fallen asleep during the night time, it is unnecessary for the dial feature to execute in the low-power execution domain. Therefore, the dial feature is switched to the off mode, and the dial feature is no longer executed in any execution domain. Exemplarily, the dial and even the entire screen can be directly closed at this time.

Hereinafter, the embodiments of the present application will be described in detail by taking FIGS. 4 and 5 as examples.

Step 501: Obtain the category of the application, and determine the first execution domain.

Exemplarily, when the application loader starts the application, the category of the application is obtained, and the execution domain corresponding to the category of the application is queried according to the category of the application, and the first execution domain is determined.

Step 502: Wake up the first execution domain.

Exemplarily, in order to ensure user experience, it is recommended that the time for waking up the first execution domain should not exceed 300 ms.

Step 503: Determine whether other execution domains are idle, that is, whether execution domains other than the first execution domain are idle, if yes, go to step 504, otherwise go to step 505.

It should be understood that there may be more than one execution domain outside the first execution domain.

Step 504: Control the idle execution domain to enter the energy-saving state.

It should be understood that the number of energy-saving states may also be more than one. Exemplarily, for each execution domain except the first execution domain, it is judged whether the execution domain is idle, and if it is idle, the execution domain is controlled to enter the energy-saving state. For example, the standby state.

Step 505: Execute the application in the first execution domain.

Exemplarily, since the first execution domain has been awakened, the hardware units included in the first execution domain can work normally. Therefore, the context of the application is established in the first execution domain, the code of the application is loaded, and the application is executed immediately. Among them, the context includes the initialization of each register, the initialization of the allocation domain of the runtime memory, and so on.

Step 506: Determine whether the application needs to access peripherals.

If the peripheral needs to be accessed, step 507 is executed, and if the peripheral is not needed to be accessed, the process ends.

Step 507: If the application needs to access the peripheral, it is further judged whether the peripheral is a shared peripheral, that is, whether the shared peripheral is exclusively occupied by the first execution domain, if so, go to step 508, otherwise go to step 509 .

Step 508: Set a global exclusive identifier.

It is understandable that through this identification, other execution domains will not be able to obtain the control right of the peripheral, ensuring exclusive access to the peripheral by the current execution domain, and avoiding data or status errors.

Step 509: Perform normal peripheral reading and writing and control.

Specifically, if the application needs to access the shared peripheral, it executes normal read, write and control of the shared peripheral until the access to the shared peripheral is completed. If the application needs to access the exclusive peripheral, the normal exclusive peripheral read and write and control are performed until the exclusive peripheral access is completed. If the application needs to access shared peripherals and exclusive peripherals, perform normal shared peripheral read, write and control until the shared peripheral access is completed, and perform normal shared peripheral read, write and control until the exclusive peripheral access is completed .

Step 510: Clear the global exclusive flag after the access to the shared peripheral is completed.

After the global exclusive flag is cleared, the state of the shared peripheral is restored to available and ready.

It is understandable that when the application does not access the shared peripherals, but only accesses the exclusive peripherals, this step may not be executed at this time.

Hereinafter, the embodiment of the present application will be described in detail by taking FIG. 6 as an example.

Step 601: Obtain the category of the application, and allocate the application to the first execution domain for execution.

The application includes multiple characteristics, the first characteristic is one of the multiple characteristics, and the first mode is an initial mode of the first characteristic, which is associated with the first execution domain.

Step 602: Detect a preset event. If a preset event is detected, step 603 is executed, otherwise the process ends.

If the preset event is not detected, you can refer to the related content in the embodiment shown in FIG. 5, and the repetition will not be repeated.

Step 603: Query the mode of the first characteristic corresponding to the preset event, determine the second mode, and switch the mode of the first characteristic from the first mode to the second mode.

Step 604: Switch the first characteristic from the first execution domain to the execution domain corresponding to the second mode according to the execution domain corresponding to the second mode.

Step 605: resume the execution of the first feature in the execution domain corresponding to the second mode.

Step 606: Determine whether the application is finished, if the execution is finished, the process is finished, otherwise, the preset event is continuously detected, and step 602 is returned.

The embodiment of the present application provides a method for executing an application to resolve the contradiction between battery life and user experience and functions. The execution subject of this method may be a terminal device or may be an application loader in the system. The following takes the application loader as an example for description. As shown in Figure 7, the method includes:

S701: The application loader obtains the category of the first characteristic, where the first characteristic is one of the multiple characteristics included in the application.

In this embodiment, the application includes multiple features, and different features can communicate through inter-process communication (IPC) devices or pipes. Exemplarily, the characteristics are divided into a first category of characteristics and a second category of characteristics, and the basis for the classification of the characteristics may include factors such as battery life, power consumption, and experience. It is understandable that the number of application categories can also be greater than 2, and the above examples are not limited to the embodiments of the present application. Exemplarily, the characteristics can be divided into high experience characteristics and low power consumption characteristics, as shown in FIG. 4.

Generally, features that belong to the background computing category in the application, or features that do not require high user interaction experience, such as heart rate monitoring, wrist posture detection (for example, raising the wrist to brighten the screen), pressure monitoring, etc., can be used as the first Category features have become low-power features. Features that require higher user experience in applications can be used as second category features, which can also be referred to as high-experience features. For example, UI interface switching transition, various micro-motion effects, transition animation, etc. Among them, micro-motion effects refer to animation effects built into a small range of UI elements.

In addition, some features can also include sub-features, and the application loader can also obtain the categories of these sub-features. For example, dial features can also be divided into video dials, 3D dials, album dials, standby dials and other sub-characteristics. Among them, video dials, 3D dials, etc. Dials, photo album dials are high-experience features, and these features provide complex screen effects. The standby dial only provides a simple time display function, without complicated screen effects, and no need to obtain other system data. It is a feature of low power consumption.

It can be understood that the number of execution domains and the number of feature classifications can be the same or different. Exemplarily, the number of classifications of characteristics may be greater than the number of execution domains, or the number of execution domains may be greater than the number of classifications of characteristics.

S702: The application loader determines a first execution domain from multiple execution domains according to the category of the first characteristic, and executes the first characteristic in the first execution domain.

Exemplarily, when the application loader pulls up the application, it queries the execution domain corresponding to the first characteristic category according to the acquired first characteristic category, that is, determines the first execution domain, where the characteristic category corresponds to the execution domain The relationship can be configured in advance. After determining the first execution domain, the application loader assigns the first characteristic to the first execution domain for execution.

At the same time, the application loader may also obtain the category of the second characteristic, determine the second execution domain from a plurality of execution domains according to the category of the second characteristic, and execute the second characteristic in the second execution domain. Wherein, the second execution domain is different from the first execution domain, and the first characteristic and the second characteristic are communicated through an IPC device or a pipe. The second characteristic is one of a plurality of characteristics included in the application, and the second characteristic is different from the first characteristic. Exemplarily, the application loader allocates low power consumption features to the MCU domain for execution, and high experience features to the AP domain for execution.

Further, the application loader can control the idle execution domains except the first execution domain and the second execution domain to enter the energy-saving state. Wherein, the energy-saving state includes at least one of a standby state, a sleep state, and a deep sleep state. For the related description of the energy-saving state, please refer to the related content of part S302 in the embodiment shown in FIG. 3, and the repetition will not be repeated.

The application loader determines that the shared peripheral that needs to be accessed by the first feature is exclusively owned by the first execution domain, and sets a global exclusive flag for the shared peripheral. After the shared peripheral is accessed, it clears the global exclusive flag set for the shared peripheral . It should be understood that for a CPU or Hub, peripherals are generally child nodes on the system and only support a single parent node. Therefore, regardless of whether a global exclusive flag is set, peripherals are generally exclusive. At the same time, peripherals can be time-division multiplexed or address multiplexed. Only one CPU can access during a multiplexing period.

Further, when the system detects a preset event, it queries the mode corresponding to the preset event, that is, determines the second mode. The second mode is the mode of the first characteristic corresponding to the preset event, and the mode of controlling the first characteristic is from the first One mode is switched to the second mode, and the first mode is the initial mode of the first characteristic.

Further, switching the mode of controlling the first characteristic from the first mode to the second mode may refer to controlling the first characteristic to be executed from the first execution domain to the third execution domain, wherein the first mode corresponds to the first execution domain, and the first mode corresponds to the first execution domain. The second mode corresponds to the third execution domain. The third execution domain here may be the second execution domain or other execution domains, which is not limited in the embodiment of the present application. Exemplarily, when the mode of the first characteristic is switched from the high experience mode to the low power consumption mode, the execution domain of the first characteristic is controlled to switch from the high power consumption execution domain to the low power consumption execution domain. Or, switching the mode of controlling the first characteristic in the application from the first mode to the second mode may refer to controlling the first characteristic to stop executing in the first execution domain, that is, turning off the first characteristic. Exemplarily, when the mode of the first characteristic is switched from the high experience mode to the closed mode, the first characteristic is controlled to be turned off. For specific examples, you can refer to the dial characteristics in the cool dial as an example to illustrate the process of mode switching of the dial characteristics, and the repetition will not be repeated.

Hereinafter, the embodiments of the present application will be described in detail by taking FIGS. 8 and 9 as examples.

Step 901: Acquire the category of the first characteristic, and determine the first execution domain.

Exemplarily, when the application loader starts the application, the category of the first characteristic is acquired. For example, the first characteristic may be heart rate detection, or some kind of micro-motion effect. When the first characteristic is heart rate detection, the category of the first characteristic is a low power consumption characteristic, and when the first characteristic is a certain micro-motion effect, the category of the first characteristic is a high experience characteristic.

Exemplarily, the application loader queries the execution domain corresponding to the category of the first characteristic according to the category of the first characteristic, and determines the first execution domain. For example, the first characteristic is heart rate detection, the category of the first characteristic is low power consumption, and the application loader determines the MCU domain (that is, the low power execution domain) according to the low power consumption characteristic. For example, when the first characteristic is a certain micro-motion effect, the category of the first characteristic is a high-experience characteristic, and the application loader determines an AP domain (that is, a low-power execution domain) according to the high-experience characteristic.

Step 902: Wake up the first execution domain.

Step 903: Determine whether other execution domains are idle, that is, whether execution domains other than the first execution domain are idle, if yes, go to step 904, otherwise go to step 905.

Step 904: Control the idle execution domain to enter the energy-saving state.

Step 905: Execute the first characteristic in the first execution domain.

Step 906: Determine whether the first feature needs to access peripherals.

If the peripheral needs to be accessed, step 907 is executed. If the peripheral is not needed to be accessed, the process ends.

Step 907: If the first feature requires access to the peripheral, it is further judged whether the peripheral is a shared peripheral, that is, whether the shared peripheral is exclusively occupied by the first execution domain, if so, go to step 908, otherwise go to step 909.

Step 908: Set a global exclusive identifier.

Step 909: Perform normal peripheral reading and writing and control.

Step 910: Clear the global exclusive identifier after the access to the shared peripheral is completed.

Step 911: Determine whether to communicate with other features. If the first feature needs to communicate with other features, perform step 912; otherwise, the process ends.

Step 912: Turn on the IPC device. The first feature communicates with other features through the IPC device.

Step 913: Read and write the IPC device.

The following uses FIG. 10 as an example to describe the embodiments of the present application in detail.

Step 1001: Acquire the category of the first characteristic, and assign the first characteristic to the first execution domain for execution.

Exemplarily, when the application loader starts the application, it obtains the category of the first characteristic in the application, and according to the category of the first characteristic, queries the execution domain corresponding to the category of the first characteristic to determine the first execution domain.

Wherein, the application includes a first characteristic, and the first mode is an initial mode of the first characteristic, and is associated with the first execution domain.

For step 1002 to step 1006, reference may be made to the related content of the embodiment shown in FIG. 6, and the repetition will not be repeated.

The above method avoids the fixed execution domain allocation method. According to the detected preset event, the characteristics in the application can be dynamically switched to the corresponding execution domain, which can improve the flexibility of system power consumption control and reduce the overall power of the system. Consumption level.

It can be understood that, in order to implement the functions in the foregoing embodiments, the terminal device includes hardware structures and/or software modules corresponding to each function. Those skilled in the art should easily realize that, in combination with the units and method steps of the examples described in the embodiments disclosed in the present application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application scenarios and design constraints of the technical solution.

11 and FIG. 12 are schematic structural diagrams of possible communication devices provided by embodiments of this application. These communication devices can be used to implement the functions of the terminal equipment in the foregoing method embodiments, and therefore can also achieve the beneficial effects of the foregoing method embodiments. In the embodiment of the present application, the communication device may be a terminal device as shown in Fig. 1, a wearable device, or a module (such as a chip) applied to a terminal device.

As shown in FIG. 11, the communication device 1100 includes a processing unit 1110 and a transceiving unit 1120. The communication device 1100 is used to implement the functions of the terminal device in the method embodiments shown in FIG. 3, FIG. 4, FIG. 5, FIG. 6, FIG. 7, FIG. 8, FIG. 9 and FIG. 10.

When the communication device 1100 is used to implement the function of the terminal device in the method embodiment shown in FIG. 3: the transceiving unit 1120 is used to obtain the category of the application; the processing unit 1110 is used to determine the first from multiple execution domains according to the category of the application. Execution domain, the application is executed in the first execution domain.

When the communication device 1100 is used to implement the function of the terminal device in the method embodiment shown in FIG. 7: the transceiver unit 1120 is used to obtain the category of the first characteristic, and the first characteristic is one of the multiple characteristics included in the application. Each characteristic corresponds to a functional segment of the application; the processing unit 1110 is configured to determine a first execution domain from a plurality of execution domains according to the category of the first characteristic, and execute the first characteristic in the first execution domain.

More detailed descriptions about the processing unit 1110 and the transceiver unit 1120 can be obtained directly with reference to the relevant descriptions in the method embodiments shown in FIG. 3 and FIG. 7, and will not be repeated here.

As shown in FIG. 12, the communication device 1200 includes a processor 1210 and an interface circuit 1220. The processor 1210 and the interface circuit 1220 are coupled with each other. It can be understood that the interface circuit 1220 may be a transceiver or an input/output interface. Optionally, the communication device 1200 may further include a memory 1230 for storing instructions executed by the processor 1210 or storing input data required by the processor 1210 to run the instructions or storing data generated after the processor 1210 runs the instructions. In addition, the specific structure of the communication device may also be as shown in FIG. 2.

When the communication device 1200 is used to implement the method shown in FIG. 12, the processor 1210 is used to implement the function of the above-mentioned processing unit 1110, and the interface circuit 1220 is used to implement the function of the above-mentioned transceiving unit 1120.

When the foregoing communication device is a chip applied to a terminal device, the terminal device chip implements the function of the terminal device in the foregoing method embodiment.

In the various embodiments of this application, if there are no special instructions and logical conflicts, the terms and/or descriptions between different embodiments are consistent and can be mutually cited. The technical features in different embodiments are based on their inherent Logical relationships can be combined to form new embodiments.

In this application, "at least one" refers to one or more, and "multiple" refers to two or more. "And/or" describes the association relationship of the associated object, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B can be singular or plural. In the text description of this application, the character "/" generally indicates that the associated objects before and after are an "or" relationship; in the formula of this application, the character "/" indicates that the associated objects before and after are a kind of "division" Relationship.

It is understandable that the various numerical numbers involved in the embodiments of the present application are only for easy distinction for description, and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of the above processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic.

Claims

A method for executing an application, characterized in that the method includes:

Get the category of the application;

According to the category of the application, a first execution domain is determined from a plurality of execution domains, and the application is executed in the first execution domain; the plurality of execution domains are different execution domains obtained by dividing the hardware. One execution domain includes a high-power execution domain and a low-power execution domain.
The method of claim 1, further comprising:

Control the idle execution domains of the plurality of execution domains except the first execution domain to enter an energy-saving state.
The method of claim 1 or 2, further comprising:

Determining that the shared peripheral that the application needs to access is exclusively occupied by the first execution domain, and setting a global exclusive identifier for the shared peripheral;

After the shared peripheral is accessed, the global exclusive identifier set for the shared peripheral is cleared.
The method according to any one of claims 1 to 3, wherein the application includes a plurality of characteristics, and each characteristic corresponds to a functional segment of the application;

The method also includes:

A preset event is detected, the preset event is used to trigger a second mode, and the second mode is a mode of the first characteristic among the plurality of characteristics included in the application;

The mode for controlling the first characteristic is switched from the first mode to the second mode, and the first mode is the initial mode of the first characteristic.
The method of claim 4, wherein switching the mode of controlling the first characteristic in the application from the first mode to the second mode comprises:

Controlling the execution of the first characteristic from the first execution domain to the second execution domain, wherein the first mode corresponds to the first execution domain, and the second mode corresponds to the second execution domain.
A method for executing an application, characterized in that the method includes:

Acquiring a category of a first characteristic, where the first characteristic is one of a plurality of characteristics included in an application, and each characteristic corresponds to a functional segment of the application;

According to the category of the first characteristic, a first execution domain is determined from a plurality of execution domains, and the first characteristic is executed in the first execution domain; the plurality of execution domains are different execution domains obtained by dividing the hardware , The multiple execution domains include a high power consumption execution domain and a low power consumption execution domain.
The method of claim 6, further comprising:

Acquiring a category of a second characteristic, where the second characteristic is one of a plurality of characteristics included in the application, and the second characteristic is different from the first characteristic;

Determine a second execution domain from a plurality of execution domains according to the category of the second characteristic, execute the second characteristic in the second execution domain, and the second execution domain is different from the first execution domain, And the first characteristic and the second characteristic communicate through an inter-process communication IPC device or pipe.
The method of claim 7, further comprising:

Control the idle execution domains of the plurality of execution domains except the first execution domain and the second execution domain to enter an energy-saving state.
The method according to any one of claims 6-8, further comprising:

It is determined that the shared peripheral that needs to be accessed by the first characteristic is exclusively occupied by the first execution domain, and a global exclusive identifier is set for the shared peripheral;

After the shared peripheral is accessed, the global exclusive identifier set for the shared peripheral is cleared.
The method according to any one of claims 6-9, further comprising:

A preset event is detected, the preset event is used to trigger a second mode, and the second mode is a mode of the first characteristic;

The mode for controlling the first characteristic is switched from the first mode to the second mode, and the first mode is the initial mode of the first characteristic.
The method of claim 10, wherein the switching of the mode of controlling the first characteristic from the first mode to the second mode comprises:

Controlling the execution of the first characteristic from the first execution domain to the third execution domain, wherein the first mode corresponds to the first execution domain, and the second mode corresponds to the third execution domain.
A device for executing applications, characterized in that the device includes:

The obtaining unit is used to obtain the category of the application;

The processing unit is configured to determine a first execution domain from a plurality of execution domains according to the category of the application, and execute the application in the first execution domain; the plurality of execution domains are different executions obtained by dividing the hardware Domains, the multiple execution domains include a high power consumption execution domain and a low power consumption execution domain.
The device according to claim 12, wherein the processing unit is further configured to:

Control the idle execution domains of the plurality of execution domains except the first execution domain to enter an energy-saving state.
The device according to claim 12 or 13, wherein the processing unit is further configured to:

Determining that the shared peripheral that the application needs to access is exclusively occupied by the first execution domain, and setting a global exclusive identifier for the shared peripheral;

After the shared peripheral is accessed, the global exclusive identifier set for the shared peripheral is cleared.
The device according to any one of claims 12-14, wherein the processing unit is further configured to:

A preset event is detected, the preset event is used to trigger a second mode, and the second mode is a mode in which the application includes a first characteristic of a plurality of characteristics, and the application includes a plurality of characteristics, each characteristic A functional segment corresponding to the application;

The mode for controlling the first characteristic is switched from the first mode to the second mode, and the first mode is the initial mode of the first characteristic.
The device according to claim 15, wherein the processing unit is configured to: control the first characteristic to switch from the first execution domain to the second execution domain to execute, wherein the first mode corresponds to In the first execution domain, the second mode corresponds to the second execution domain.
A device for executing applications, characterized in that the device includes:

An acquiring unit, configured to acquire a category of a first characteristic, where the first characteristic is one of a plurality of characteristics included in an application, and each characteristic corresponds to a functional segment of the application;

The processing unit is configured to determine a first execution domain from a plurality of execution domains according to the category of the first characteristic, and execute the first characteristic in the first execution domain; the plurality of execution domains are hardware divisions Different execution domains obtained, the multiple execution domains include a high-power execution domain and a low-power execution domain.
17. The apparatus according to claim 17, wherein the acquiring unit is further configured to: acquire a category of a second characteristic, the second characteristic being one of a plurality of characteristics included in the application, and The second characteristic is different from the first characteristic;

The processing unit is further configured to determine a second execution domain from a plurality of execution domains according to the category of the second characteristic, execute the second characteristic in the second execution domain, and the second execution domain and The first execution domain is different, and the first characteristic and the second characteristic communicate through an inter-process communication IPC device or pipe.
The device according to claim 18, wherein the processing unit is further configured to control idle execution domains other than the first execution domain and the second execution domain among the plurality of execution domains to enter an energy-saving state .
The device according to any one of claims 17-19, wherein the processing unit is also used for

It is determined that the shared peripheral that needs to be accessed by the first characteristic is exclusively occupied by the first execution domain, and a global exclusive identifier is set for the shared peripheral;

After the shared peripheral is accessed, the global exclusive identifier set for the shared peripheral is cleared.
The device according to any one of claims 17-20, wherein the processing unit is further configured to detect a preset event, the preset event is used to trigger a second mode, and the second mode is The mode of the first characteristic;

The mode for controlling the first characteristic is switched from the first mode to the second mode, and the first mode is the initial mode of the first characteristic.
The device of claim 21, wherein the processing unit is further configured to control the first characteristic to switch from the first execution domain to a third execution domain to execute, wherein the first mode corresponds to In the first execution domain, the second mode corresponds to the third execution domain.
A computer storage medium, characterized in that a computer program or instruction is stored in the storage medium, and when the computer program or instruction is executed by a communication device, the method according to any one of claims 1 to 11 is implemented .
A wearable device, characterized by comprising a processor and a memory, the memory is used to store a program, and the processor calls the memory to execute the method according to any one of claims 1 to 11.
A communication device, characterized by comprising a processor and an interface circuit, the interface circuit is used to receive signals from other communication devices other than the communication device and transmit them to the processor or transfer signals from the processor The signal of is sent to another communication device other than the communication device, and the processor is used to implement the method according to any one of claims 1 to 11 through a logic circuit or an execution code instruction.