System, method and user interface for supporting scheduled mode changes on electronic devices
US-11669235-B2 · Jun 6, 2023 · US
US12339726B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12339726-B2 |
| Application number | US-202318336174-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 16, 2023 |
| Priority date | Dec 18, 2020 |
| Publication date | Jun 24, 2025 |
| Grant date | Jun 24, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method for system switching, a wearable device, and a storage medium are provided. The method is performed by a wearable device at least equipped with a first processor and a second processor. The second processor has higher power consumption than the first processor. The first processor is configured to run a first system, and the second processor is configured to run a second system. The method includes the following. A first event is processed with the first system when the second processor is in a dormant state. In response to a second event being triggered and the first processor failing to meet a processing capacity required for the second event, the second processor is switched to a wake-up state, and the second event is processed with the second system.
Opening claim text (preview).
What is claimed is: 1. A method for system switching, performed by a wearable device at least equipped with a first processor and a second processor, the second processor having higher power consumption than the first processor, the first processor being configured to run a first system and the second processor being configured to run a second system, and the method comprising: processing a first event with the first system when the second processor is in a dormant state; and switching the second processor to a wake-up state and processing a second event with the second system, in response to the second event being triggered and the first processor failing to meet a processing capacity required for the second event; wherein processing the second event with the second system comprises: sending event data of the second event to the second system with the first system; processing the event data with the second system to obtain event feedback data; and receiving the event feedback data sent by the second system with the first system, and displaying, with the first system, a graphical user interface (GUI) corresponding to the second event according to the event feedback data. 2. The method of claim 1 , wherein after processing the second event with the second system, the method further comprises: switching the second processor to the dormant state, in response to completion of processing of the second event. 3. The method of claim 2 , wherein the second system has a GUI display permission in a process of processing the second event; before switching the second processor to the dormant state, the method further comprises: sending a second switch instruction to the first system with the second system; and obtaining the GUI display permission with the first system from the second system in response to the second switch instruction. 4. The method of claim 1 , wherein the method further comprises: caching first data with the first system when the second processor is in the dormant state, wherein the first data is cached in a data storage space corresponding to the first system; and after switching the second processor to the wake-up state, the method further comprises: synchronizing the first data to the second system with the first system when the second processor is in the wake-up state. 5. The method of claim 4 , wherein synchronizing the first data to the second system with the first system comprises: binding, according to a data type of the first data, a data synchronization service through a data communication service provided by the second system, wherein different data types correspond to different data synchronization services; and synchronizing the first data to a target application in the second system through the data synchronization service bound, wherein the target application is used to process the first data. 6. The method of claim 5 , wherein synchronizing the first data to the second system with the first system further comprises: synchronizing target data in the first data to the second system with the first system, wherein a data volume of the target data is less than a data-volume threshold. 7. The method of claim 4 , wherein after caching the first data with the first system, the method further comprises: switching the second processor to the wake-up state and synchronizing the first data to the second system with the first system, in response to a data volume of the first data cached reaching a storage-capacity threshold. 8. The method of claim 4 , wherein after caching the first data with the first system, the method further comprises: switching the second processor to the wake-up state and synchronizing instant data to the second system with the first system, in response to the first data cached containing the instant data. 9. The method of claim 4 , wherein after caching the first data with the first system, the method further comprises: switching the second processor to the wake-up state and synchronizing the first data to the second system with the first system, in response to a data alignment time point being reached. 10. The method of claim 9 , wherein switching the second processor to the wake-up state in response to the data alignment time point being reached comprises: determining a target data alignment time point corresponding to the first data according to a real-time requirement of the first data, wherein data with different real-time requirements correspond to different data alignment time points, and a time interval between data alignment time points is negatively correlated with the real-time requirement; and switching the second processor to the wake-up state in response to the target data alignment time point being reached. 11. The method of claim 4 , wherein a communication component is mounted on the first processor, and before synchronizing the first data to the second system with the first system, the method further comprises: synchronizing second data to the second system with the first system in response to receiving, by the communication component, the second data sent by an external device, when the second processor is in the wake-up state. 12. The method of claim 1 , wherein after processing the second event with the second system, the method further comprises: synchronizing third data to the first system through a data communication service provided by the second system, wherein the third data is data generated in a process of processing the second event. 13. The method of claim 1 , wherein after processing the second event with the second system, the method further comprises: maintaining the second processor in the wake-up state within a dormant delay duration corresponding to the second event in response to completion of processing of the second event, wherein the dormant delay duration is determined according to at least one of a wake-up frequency of the second processor after the second event or an event type of the second event; and switching the second processor to the dormant state and processing the first event with the first system, in response to the dormant delay duration elapsed. 14. The method of claim 1 , further comprising: classifying, according to an application scenario of a triggered event, the triggered event as the first event or the second event, wherein the application scenario comprises a weak interaction scenario and a strong interaction scenario. 15. A wearable device, comprising: a first processor, configured to run a first system; a second processor, having higher power consumption than the first processor, and configured to run a second system; and a memory, coupled with the first processor and the second processor, and storing at least one instruction which, when executed by the first processor or the second processor, is operable with the wearable device to: process a first event with the first system when the second processor is in a dormant state; and switch the second processor to a wake-up state and process a second event with the second system, in response to the second event being triggered and the first processor failing to meet a processing capacity required for the second event; wherein the wearable device is further configured to: cache first data with the first system, wherein the first data is cached in a data storage space corresponding to the first system; wherein after switching the second processor to the wake-up state, the wearable device is further configured to: synchronize the first data to the second system with the first system when the second processor is in the wake-up
Power management, i.e. event-based initiation of a power-saving mode · CPC title
by switching to a less power-consuming processor, e.g. sub-CPU · CPC title
Multiproc · CPC title
Task life-cycle, e.g. stopping, restarting, resuming execution (G06F9/4881 takes precedence) · CPC title
Distribution of virtual machine instances; Migration and load balancing · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.