Lock screen interface display method and device, wearable equipment and storage medium
By incorporating low-power and high-power processors into wearable devices, the synchronized display of the lock screen status is achieved, thus solving the problem of short battery life in wearable devices and improving their overall battery performance.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
- Filing Date
- 2021-03-26
- Publication Date
- 2026-05-05
AI Technical Summary
Wearable devices have small battery capacity and short battery life. In existing technologies, the single processor works for a long time, resulting in high power consumption and affecting the device's battery life.
In wearable devices, a low-power first processor and a high-power second processor are set up. When the second processor receives a screen lock command, it synchronizes the screen lock state with the first processor, so that the first processor displays the screen lock interface, thereby reducing the overall power consumption.
Displaying the lock screen interface using a low-power processor reduces the power consumption of wearable devices and improves battery life.
Smart Images
Figure CN121979376A_ABST
Abstract
Description
[0001] This application is a divisional application of the invention patent application filed on March 26, 2021, with application number 202110328514.X and invention title "Display method, device, wearable device and storage medium for lock screen interface". Technical Field
[0002] This application relates to the field of wearable device technology, and in particular to a method, apparatus, wearable device, and storage medium for displaying a lock screen interface. Background Technology
[0003] Wearable devices are portable electronic devices that can be worn directly or integrated into clothing or accessories. Common wearable devices include smartwatches, smart bracelets, smart glasses, and so on.
[0004] For portability and wearability, wearable devices are typically designed to be small, which means they can only be equipped with smaller capacity batteries. For example, smartwatches have short battery life and require frequent charging. Summary of the Invention
[0005] This application provides a method, apparatus, wearable device, and storage medium for displaying a lock screen interface. The technical solution is as follows: On one hand, embodiments of this application provide a method for displaying a lock screen interface, the method being applied to a wearable device, wherein the wearable device is provided with at least a first processor and a second processor, and the power consumption of the second processor is higher than that of the first processor; The method includes: When the second processor is in a wake-up state and receives a screen lock command, the screen state corresponding to the second processor is set to a screen lock state. The second processor synchronizes the screen lock state to the first processor. Set the screen state corresponding to the first processor to the locked screen state; The lock screen interface is displayed through the first processor.
[0006] On the other hand, embodiments of this application provide a display device for a lock screen interface, the device being applied to a wearable device, the wearable device having at least a first processor and a second processor, the power consumption of the second processor being higher than that of the first processor; The device includes: The state setting module is used to set the screen state corresponding to the second processor to the locked state when the second processor is in the wake-up state and the second processor receives a lock screen command. A state synchronization module is used to synchronize the screen lock state to the first processor via the second processor; The state setting module is also used to set the screen state corresponding to the first processor to the lock screen state; The interface display module is used to display the lock screen interface through the first processor.
[0007] On the other hand, embodiments of this application provide a wearable device, the wearable device including a processor and a memory; the processor includes at least a first processor and a second processor, the power consumption of the second processor is higher than that of the first processor, the memory stores a computer program, the computer program is loaded and executed by the processor to implement the lock screen interface display method as described above.
[0008] In another aspect, embodiments of this application provide a computer-readable storage medium storing a computer program that is loaded and executed by a processor to implement the lock screen display method as described above.
[0009] In another aspect, embodiments of this application provide a computer program product including computer instructions stored in a computer-readable storage medium. A processor of a wearable device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the wearable device to perform the lock screen display method described above.
[0010] The technical solution provided in this application can bring the following beneficial effects: Wearable devices are equipped with a low-power first processor and a high-power second processor. The first and second processors can communicate with each other. The second processor can synchronize the screen lock state with the first processor, so that when the second processor receives a screen lock command, the first processor can display the screen lock interface. In the screen lock state, the user interface is displayed by the processor with lower power consumption, which can reduce the power consumption of the wearable device and improve its battery life. Attached Figure Description
[0011] Figure 1 This is a flowchart of a lock screen interface display method provided in one embodiment of this application; Figure 2 This is a flowchart of a lock screen display method provided in another embodiment of this application; Figure 3 This is a flowchart of a lock screen display method provided in another embodiment of this application; Figure 4This is a block diagram of a lock screen display device provided in one embodiment of this application; Figure 5 This is a structural block diagram of a wearable device provided in one embodiment of this application. Detailed Implementation
[0012] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.
[0013] In related technologies, wearable devices typically incorporate a single processor, which, through an operating system running on that processor, handles all system events generated during device operation. Therefore, this processor needs strong data processing capabilities and must remain operational throughout the device's lifespan. However, in everyday use, wearable devices often only require functions with lower processing power. For example, smartwatches or smart bracelets mostly only need to provide notifications and display the time. Therefore, keeping the processor constantly active does not improve the performance of wearable devices; instead, it increases power consumption and shortens battery life.
[0014] To reduce the power consumption of wearable devices while ensuring their performance, the wearable devices in this embodiment of the application are equipped with at least a first processor and a second processor with different processing performance and power consumption. The first processor and the second processor can communicate with each other. The second processor can synchronize the screen lock state with the first processor, so that when the second processor receives a screen lock command, the first processor can display the screen lock interface. In the screen lock state, the user interface is displayed by the processor with lower power consumption, which can reduce the power consumption of the wearable device and improve its battery life.
[0015] The present application will now be described through several embodiments.
[0016] Please refer to Figure 1 The diagram illustrates a flowchart of a lock screen display method according to an embodiment of this application. This method can be applied to wearable devices, which include at least a first processor and a second processor, wherein the power consumption of the second processor is higher than that of the first processor. The method may include the following steps.
[0017] Step 101: When the second processor is in a wake-up state and receives a screen lock command, set the screen state corresponding to the second processor to a screen lock state.
[0018] In this embodiment, the power consumption of the first processor is lower than that of the second processor. Exemplarily, the processing performance of the first processor is lower than that of the second processor; exemplarily, both the processing power and processing speed of the first processor are lower than those of the second processor. Exemplarily, the second system running on the second processor can process events processed by the first system running on the first processor, but the first system may not necessarily be able to process events processed by the second system.
[0019] For example, taking a smartwatch as an example of a wearable device, the first processor can be an MCU (Micro Controller Unit), and the second processor can be a CPU (Central Processing Unit). The first system is an RTOS (Real-Time Operating System) running on the MCU, and the second system is an Android operating system running on the CPU. The events that the first system can handle include, but are not limited to, at least one of the following: watch face display, watch face interface switching, notification message display, and other scenarios with low processing performance requirements or weak interaction. The events that the second system can handle include, but are not limited to, at least one of the following: answering calls, launching applications, watch face compilation, function settings, and other scenarios with high processing performance requirements or strong interaction.
[0020] The wake-up state refers to the running state. When a processor is in the wake-up state, it means that the processor is running, that is, the processor is in a normal working state.
[0021] A lock screen command is a command to lock the screen. For example, lock screen commands can be triggered by voice, gestures, touch, or pressing a physical button. For instance, a user can say "lock screen" to the wearable device, triggering the second processor to receive the lock screen command; a user can make the gesture corresponding to "lock screen" on the wearable device, triggering the second processor to receive the lock screen command; a user can touch the "lock screen" icon on the wearable device, triggering the second processor to receive the lock screen command; or a user can press a physical button on the wearable device (e.g., pressing the power button), triggering the second processor to receive the lock screen command.
[0022] In one possible implementation, when the second processor's runtime reaches the screen lock time (equivalent to the second processor receiving a screen lock command), the second processor automatically sets the screen state to lock. The screen lock time can be set by the user or it can be a default time; this application embodiment does not limit this.
[0023] In this embodiment, the wearable device has a display screen (also referred to as a screen). The screen states include a locked state and an unlocked state. The unlocked state refers to the wearable device's display screen being in a normal display state. The unlocked state and the locked state are two different states. The display screen can be controlled by a first processor or a second processor. When the second processor receives a lock screen command, it sets the screen state corresponding to the second processor to the locked state.
[0024] The screen state corresponding to the processor refers to the state of the wearable device's display screen when the system running the processor obtains screen control permissions. For example, the screen state corresponding to the second processor refers to the state of the wearable device's display screen when the second system running the second processor obtains screen control permissions. The screen state corresponding to the first processor refers to the state of the wearable device's display screen when the first system running the first processor obtains screen control permissions.
[0025] In one possible implementation, the screen state corresponding to the second system is set to the lock screen state.
[0026] Step 102: The lock screen state is synchronized to the first processor via the second processor.
[0027] The second processor and the first processor can communicate with each other. When the second processor receives a screen lock command and its screen state is set to the screen lock state, the second processor needs to synchronize its screen state with the first processor so that the screen states of the first and second processors are synchronized, thereby ensuring that the display screen can display normally when the system switches.
[0028] In one possible implementation, the lock screen state is synchronized to the first system via a second system.
[0029] In a possible implementation, the second processor synchronizes the screen state by sending a byte stream of data to the first processor. For example, taking a locked screen state as an example, the corresponding byte stream data can be as follows: message SyncLockScreenStatus { / / Message screen status is locked int32 status = 1; / / The status field is assigned a value of 1, and the status field is a 32-bit integer. } Step 103: Set the screen state corresponding to the first processor to the lock screen state.
[0030] After setting the screen state corresponding to the second processor to the locked state, the screen state corresponding to the first processor is also set to the locked state.
[0031] In one possible implementation, the screen state corresponding to the first system is set to the lock screen state.
[0032] Step 104: Display the lock screen interface via the first processor.
[0033] The lock screen refers to the interface displayed when a wearable device is locked.
[0034] When the second processor receives the screen lock command, it indicates that the user does not need to use the second processor to handle more complex events. At this time, the wearable device's display screen can be controlled by the first processor, that is, the lock screen interface can be displayed by the first processor. Since the first processor has low power consumption, the battery life of the wearable device can be improved.
[0035] In one possible implementation, the lock screen interface is displayed through the first system.
[0036] In possible implementations, steps 103 and 104 can be executed simultaneously; or steps 103 can be executed first, followed by steps 104; or steps 104 can be executed first, followed by steps 103. This application embodiment does not limit this.
[0037] In one possible implementation, when the first processor is awake and receives a lock screen command, the screen state corresponding to the first processor is set to the lock screen state; the lock screen state is synchronized to the second processor via the first processor; the screen state corresponding to the second processor is set to the lock screen state; and the lock screen interface is displayed via the first processor. When the first processor receives a lock screen command, it sets the screen state corresponding to the first processor to the lock screen state and synchronizes it to the second processor, facilitating subsequent unlocking of the wearable device via the second processor.
[0038] In summary, the technical solution provided in this application embodiment includes a low-power first processor and a high-power second processor in the wearable device. The first processor and the second processor can communicate with each other. The second processor can synchronize the screen lock state with the first processor, so that when the second processor receives a screen lock command, the first processor can display the screen lock interface. By displaying the user interface through the low-power processor in the screen lock state, the power consumption of the wearable device can be reduced and the battery life of the wearable device can be improved.
[0039] Please refer to Figure 2The diagram illustrates a flowchart of a lock screen display method according to another embodiment of this application. This method can be applied to wearable devices, which include at least a first processor and a second processor, wherein the power consumption of the second processor is higher than that of the first processor. The method may include the following steps.
[0040] Step 201: When the second processor is in a wake-up state and receives a screen lock command, set the screen state corresponding to the second processor to a screen lock state.
[0041] In possible implementations, the lock screen state includes an encrypted lock screen state and an unencrypted lock screen state. An encrypted lock screen state requires verification information to unlock, while an unencrypted lock screen state can be unlocked without requiring verification information.
[0042] Step 202: In the case of a lock screen state including an encrypted lock screen state, the encrypted lock screen state is synchronized to the first processor via the second processor.
[0043] When the second processor sets up lock screen verification, that is, when the screen state corresponding to the second processor is an encrypted lock screen state, the encrypted lock screen state is synchronized to the first processor through the second processor, so that the first processor knows that the second processor needs to be woken up when unlocking.
[0044] In one possible implementation, if the lock screen state includes an encrypted lock screen state, the encrypted lock screen state is synchronized to the first system via the second system.
[0045] Step 203: In the case of a lock screen state including an unencrypted lock screen state, the unencrypted lock screen state is synchronized to the first processor via the second processor.
[0046] In one possible implementation, if the lock screen state includes an unencrypted lock screen state, the unencrypted lock screen state is synchronized to the first system via the second system.
[0047] After the encrypted or unencrypted lock screen state is synchronized to the first processor via the second processor, the screen state corresponding to the first processor is set to the lock screen state.
[0048] Step 204: Set the screen state corresponding to the first processor to the encrypted lock screen state.
[0049] In one possible implementation, the screen state corresponding to the first system is set to an encrypted lock screen state.
[0050] Step 205: Set the screen state corresponding to the first processor to an unencrypted lock screen state.
[0051] In one possible implementation, the screen state corresponding to the first system is set to an unencrypted lock screen state.
[0052] It should be noted that steps 202 and 203 will not be executed simultaneously, nor will steps 204 and 205. Step 204 may be executed after step 202; or step 205 may be executed after step 203; or steps 202 and 204 may be executed simultaneously; or steps 203 and 205 may be executed simultaneously; or step 204 may be executed first, followed by step 202; or step 205 may be executed first, followed by step 203. This embodiment of the application does not limit the specific execution of these steps.
[0053] Step 206: Display the lock screen interface via the first processor.
[0054] In one possible implementation, the lock screen interface is displayed through the first system.
[0055] For example, the lock screen interfaces for encrypted and unencrypted lock screen states are the same, but the interfaces triggered after unlocking are different. When the lock screen state includes an encrypted lock screen state, the interface triggered after unlocking is the unlock interface; when the lock screen state includes an unencrypted lock screen state, the interface triggered after unlocking is directly the user interface, without needing to go through the unlock interface.
[0056] For example, the lock screen interfaces for encrypted and unencrypted lock screen states are different. When the lock screen state includes the encrypted lock screen state, a lock screen prompt message will be displayed on the lock screen interface to remind the user that unlocking (entering the correct verification information) is required to open the user interface.
[0057] Please refer to Figure 3 The diagram illustrates a flowchart of a lock screen display method according to another embodiment of this application. This method can be applied to wearable devices, which include at least a first processor and a second processor, wherein the power consumption of the second processor is higher than that of the first processor. The method may include the following steps.
[0058] Step 301: When the second processor is in a wake-up state and receives a screen lock command, set the screen state corresponding to the second processor to a screen lock state.
[0059] Step 302: The lock screen state is synchronized to the first processor via the second processor.
[0060] Step 303: Set the screen state corresponding to the first processor to the lock screen state.
[0061] Step 304: Display the lock screen interface via the first processor.
[0062] In possible implementations, steps 303 and 304 can be executed simultaneously; or step 303 can be executed first, followed by step 304; or step 304 can be executed first, followed by step 303. This application embodiment does not limit this.
[0063] The descriptions of steps 301 to 304 can be found in the above embodiments, and will not be repeated here.
[0064] Step 305: When the screen lock state includes the encrypted screen lock state, the second processor is in a sleep state and the first processor receives the unlock command, the second processor is woken up by the first processor.
[0065] Hibernation refers to a state where the processor is not running, or in a non-working state. When a processor is in hibernation, it means that the processor is not running.
[0066] An unlock command refers to a command to unlock the display screen of a wearable device. In possible implementations, the unlock command can be triggered by voice, gesture, touch, etc. For example, a user can say "unlock" to the wearable device, thus triggering the first processor to receive the unlock command; another example is that a user can make the corresponding "unlock" gesture towards the wearable device, thus triggering the first processor to receive the unlock command; yet another example is that a user can swipe up on the lock screen, thus triggering the first processor to receive the unlock command.
[0067] Since the wearable device's display is controlled by the first processor when the screen is locked, the unlock command is also received by the first processor. When the first processor receives the unlock command, it wakes up the second processor.
[0068] In the case of a locked screen state, including an encrypted locked screen state, where the second processor is in a sleep state and the first processor receives an unlock command, the second processor is woken up by the first processor.
[0069] In possible implementations, when the screen lock state includes an encrypted screen lock state, the second processor is in a sleep state, and the first system receives an unlock command, the second system is woken up by the first system.
[0070] Step 306: Receive the verification information input by the user through the second processor.
[0071] In this embodiment, the verification information is used to trigger the second processor to perform identity verification. The verification information may include any of the following: password, voice, face, iris, or fingerprint.
[0072] For example, the verification information is used to trigger a second system to perform authentication.
[0073] In possible implementations, the first processor corresponds to the first system, which is a system running on the first processor, and the second processor corresponds to the second system, which is a system running on the second processor. For example, the first system may be referred to as a small core, and the second system may be referred to as a large core.
[0074] Step 306 may include the following sub-steps: Step 306a: The unlock interface is displayed through the second system.
[0075] The unlock screen refers to the interface used to unlock the device. It is the interface where users can enter verification information. Users can enter verification information on the unlock screen.
[0076] Because the wake-up and display process of the second system takes some time, a brief period of unresponsiveness may occur during the switch from the first system to the second system, affecting the user experience. To reduce the display latency of the lock screen during system switching, when the first system wakes up the second system, the first system can first draw and display the unlock screen (only responsible for drawing the interface image, not executing specific functions of the second system under the first system). The unlock screen is the user interface of the second system. In response to the second system completing the drawing of the unlock screen, the unlock screen is displayed through the second system. After the second system completes the drawing of the unlock screen, the system running on the wearable device switches from the first system to the second system, thereby displaying the lock screen and executing the corresponding unlock function through the second system. Since the unlock screen drawn and displayed by the first and second systems are consistent, there will be no sudden change in the screen before and after the system switch, making the system switching process less noticeable. Because the first system is in a wake-up state, it can immediately draw and display the lock screen after receiving the unlock command, thus visually improving the system switching speed.
[0077] In possible implementations, after the unlock interface is displayed through the second system, the first system can remain in a wake-up state. Since the first system has low power consumption, it has little impact on the battery life of the wearable device. Of course, after the unlock interface is displayed through the second system, the first system can be in a sleep state, and this application embodiment does not limit this.
[0078] In possible implementations, to ensure that the system switches to the second system promptly after the first system draws and fully displays the unlock screen, and to avoid the situation where the user's operation becomes unresponsive after the first system has fully displayed the unlock screen (at which point the lock screen is drawn and displayed by the first system), the sliding speed of the unlock screen is determined based on the time it takes for the second system to wake up and draw the unlock screen. This ensures that the second system has already drawn the unlock screen when the unlock screen drawn by the first system has completely occupied the display screen of the wearable device, thus achieving system switching without the user's awareness.
[0079] Step 306b: Receive the verification information entered by the user on the unlock screen through the second system.
[0080] Since the second system is more secure than the first system, receiving the verification information entered by the user on the unlock screen through the second system can ensure the security of the information.
[0081] Step 307: The second processor executes the unlocking process based on the user-input verification information and preset verification information.
[0082] The preset verification information can be information that the user has pre-stored in the wearable device to verify the user's identity. The type of the preset verification information is consistent with the type of verification information entered by the user. That is, when the user enters a password, the preset verification information is also a password; when the user enters a voice verification information, the preset verification information is also a voice verification information; when the user enters a face verification information, the preset verification information is also a face verification information; when the user enters an iris verification information, the preset verification information is also an iris verification information; and when the user enters a fingerprint verification information, the preset verification information is also a fingerprint verification information.
[0083] In possible implementations, step 307 may include the following sub-steps: Step 307a: The second system confirms whether the verification information entered by the user is consistent with the preset verification information.
[0084] Step 307b: In response to the user-input verification information matching the preset verification information, the user interface is displayed through the first system or the second system based on the operating mode of the wearable device.
[0085] Taking the password as the verification information as an example, the unlock interface is displayed through the second system, and the password entered by the user in the unlock interface is received through the second system. In response to the fact that the entered password is consistent with the preset password, the user interface is displayed through the first system or the second system based on the operating mode of the wearable device.
[0086] In one possible implementation, the wearable device can pre-store multiple preset verification information. When the verification information entered by the user matches one of the multiple preset verification information, the user interface is displayed through a first system or a second system based on the operating mode of the wearable device.
[0087] In a possible implementation, step 307b may include the following sub-steps: 1. When the wearable device operates in a smart mode, the first user interface is displayed through the second system.
[0088] 2. When the wearable device operates in a non-smart mode, a second user interface is displayed through the first system.
[0089] In possible implementations, the wearable device can operate in both smart and non-smart modes. Smart mode, also known as performance mode, refers to a mode where both the first and second processors remain active, allowing the wearable device to quickly execute high-performance events. Non-smart mode, also known as low-power mode, refers to a mode where only the first processor remains active, while the second processor is in sleep mode. Of course, in other possible implementations, the wearable device may also have other operating modes, which are not limited in this embodiment.
[0090] Unlike smartphones, which are electronic devices with strong interactive attributes, wearable devices, as auxiliary electronic devices, have only weak interactions with users in most usage scenarios. For example, users mostly only use smartwatches to check the time. Therefore, when the wearable device processes events through the first processor (the first system processes events), keeping the second processor in a sleep state (the second system is in a sleep state) can reduce the overall power consumption of the wearable device.
[0091] This application embodiment enhances the display diversity of wearable devices by intelligently displaying the user interface after unlocking based on the operating mode of the wearable device.
[0092] The first user interface refers to the interface controlled by the first system. In possible implementations, the first user interface may display icons such as fitness and health icons, weather icons, alarm clock icons, and system switching icons, but this application embodiment does not limit this.
[0093] The second user interface refers to the interface controlled by the second system. In possible implementations, the second user interface may display a voice assistant icon, icons of various applications, etc., but this application embodiment does not limit this.
[0094] In a possible implementation, when the lock screen state includes an unencrypted lock screen state and the first processor receives an unlock command, the first user interface is displayed through the first processor.
[0095] In possible implementations, the above method may also include the following steps: First, when the second processor is in a sleep state and the first processor is in a wake-up state, the third user interface is displayed through the first processor; Second, in response to a system switching command, a fourth user interface is displayed via a second processor.
[0096] In possible implementations, the system switching command is triggered by a shortcut key (such as a physical button on a wearable device), a swipe (such as a single-finger or two-finger swipe on the wearable device's display), or other means.
[0097] In response to a system switching command, the system switches from the third user interface to the fourth user interface. The third user interface refers to the interface controlled by the first system, and the fourth user interface refers to the interface controlled by the second system.
[0098] During operation, the wearable device uses a first system running on a low-power processor to handle events requiring low performance, while keeping the high-power processor in a sleep state (correspondingly, the second system running on the high-power processor is also in a sleep state). This approach reduces the wearable device's power consumption while implementing its basic functions. When a high-performance event occurs (such as when an application is launched), the high-power processor is woken up, and the second system is switched to handle the event, ensuring that triggered events are responded to and processed promptly, thus meeting the performance requirements of the wearable device.
[0099] For example, when a user needs to use a function that is not available in the user interface displayed by the first system, the wearable device needs to switch from the first system to the second system so that the user can select the function to be used from the user interface displayed by the second system.
[0100] When the first processor is in a wake-up state (at this time, the wearable device's interface is the user interface displayed by the first system) and the second processor is in a sleep state, when a system switching command is received, it indicates that the first system needs to be switched to the second system. Since the first processor does not have the function and ability to process the corresponding events, it is necessary to wake up the second processor, which is in a sleep state, so that the second system can process them.
[0101] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.
[0102] Please refer to Figure 4 This diagram illustrates a block diagram of a lock screen display device according to an embodiment of this application. The device is applied to a wearable device, which includes at least a first processor and a second processor, wherein the power consumption of the second processor is higher than that of the first processor. The device has the functionality to implement the method example described above; this functionality can be implemented in hardware or by hardware executing corresponding software. The device 400 may include: The state setting module 410 is used to set the screen state corresponding to the second processor to the lock screen state when the second processor is in the wake-up state and the second processor receives a lock screen command. The state synchronization module 420 is used to synchronize the screen lock state to the first processor through the second processor; The state setting module 410 is also used to set the screen state corresponding to the first processor to the lock screen state. The interface display module 430 is used to display the lock screen interface through the first processor.
[0103] In summary, the technical solution provided in this application embodiment includes a low-power first processor and a high-power second processor in the wearable device. The first processor and the second processor can communicate with each other. The second processor can synchronize the screen lock state with the first processor, so that when the second processor receives a screen lock command, the first processor can display the screen lock interface. By displaying the user interface through the low-power processor in the screen lock state, the power consumption of the wearable device can be reduced and the battery life of the wearable device can be improved.
[0104] In an illustrative embodiment, the lock screen state includes an encrypted lock screen state and an unencrypted lock screen state; The state synchronization module 420 is used for: When the lock screen state includes the encrypted lock screen state, the encrypted lock screen state is synchronized to the first processor via the second processor. If the lock screen state includes the unencrypted lock screen state, the unencrypted lock screen state is synchronized to the first processor by the second processor.
[0105] In an illustrative embodiment, the device 400 further includes: A processor wake-up module (not shown in the figure) is used to wake up the second processor through the first processor when the lock screen state includes an encrypted lock screen state, the second processor is in a sleep state and the first processor receives an unlock command. An information receiving module (not shown in the figure) is used to receive verification information input by the user through the second processor, and the verification information is used to trigger the second processor to perform identity verification; The information unlocking module (not shown in the figure) is used to execute the unlocking process based on the user-input verification information and preset verification information by the second processor.
[0106] In an illustrative embodiment, the first processor corresponds to a first system, which refers to a system running by the first processor, and the second processor corresponds to a second system, which refers to a system running by the second processor. The information receiving module is used for: The unlock interface is displayed through the second system; The second system receives the verification information entered by the user on the unlock interface.
[0107] In an illustrative embodiment, the information unlocking module includes: An information confirmation unit (not shown in the figure) is used to confirm whether the verification information input by the user is consistent with the preset verification information through the second system; The interface display unit (not shown in the figure) is used to display the user interface through the first system or the second system in response to the user input verification information being consistent with the preset verification information, based on the operating mode of the wearable device.
[0108] In an illustrative embodiment, the interface display unit is used for: When the wearable device operates in a smart mode, the first user interface is displayed through the second system; When the wearable device operates in a non-smart mode, a second user interface is displayed through the first system.
[0109] In an illustrative embodiment, the interface display module 430 is further configured to: When the second processor is in sleep mode and the first processor is in wake-up mode, the third user interface is displayed through the first processor; In response to a system switching command, a fourth user interface is displayed via the second processor.
[0110] It should be noted that the apparatus provided in the above embodiments is only illustrated by the division of the above functional modules. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.
[0111] Please refer to Figure 5 The diagram illustrates a structural block diagram of a wearable device provided in one embodiment of this application.
[0112] The wearable device in this application embodiment may include one or more of the following components: processor 510 and memory 520.
[0113] Processor 510 may include one or more processing cores. Exemplarily, processor 510 includes at least a first processor 511 and a second processor 512. The first processor 511 can be used to run a first system, and the second processor 512 can be used to run a second system. The power consumption of the first processor 511 is lower than that of the second processor 512. Processor 510 connects various parts within the wearable device using various interfaces and lines, and performs various functions and processes data of the wearable device by running or executing instructions, programs, code sets, or instruction sets stored in memory 520, and by calling data stored in memory 520. Optionally, processor 510 may be implemented using at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). Processor 510 may integrate one or a combination of several of the following: Central Processing Unit (CPU), Graphics Processing Unit (GPU), Neural-network Processing Unit (NPU), and modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the content displayed on the touchscreen; the NPU implements artificial intelligence (AI) functions; and the modem handles wireless communication. It is understood that the modem may not be integrated into the processor 510 and can be implemented as a separate chip.
[0114] Optionally, the processor 510 executes the program instructions in the memory 520 to implement the methods provided in the above-described method embodiments.
[0115] The memory 520 may include random access memory (RAM) or read-only memory (ROM). Optionally, the memory 520 may include a non-transitory computer-readable storage medium. The memory 520 may be used to store instructions, programs, code, code sets, or instruction sets. The memory 520 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the various method embodiments described above, etc.; the data storage area may store data created based on the use of the wearable device (such as audio data, phonebook, etc.).
[0116] The wearable device in this embodiment further includes a communication component 530 and a display component 540. The communication component 530 can be a Bluetooth component, a WiFi (Wireless Fidelity) component, an NFC (Near Field Communication) component, etc., used to communicate with external devices (servers or other terminal devices) via wired or wireless networks; the display component 540 is used to display a graphical user interface and / or receive user interaction operations.
[0117] In addition, those skilled in the art will understand that the structure of the wearable device shown in the above figures does not constitute a limitation on the wearable device. The wearable device may include more or fewer components than shown, or combine certain components, or have different component arrangements. For example, the wearable device may also include radio frequency circuits, input units, sensors, audio circuits, speakers, microphones, power supplies, etc., which will not be described in detail here.
[0118] In an exemplary embodiment, a computer-readable storage medium is also provided, wherein a computer program is stored therein, the computer program being loaded and executed by a processor of a wearable device to implement the various steps in the above-described lock screen interface display method embodiments.
[0119] In an exemplary embodiment, a computer program product is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a wearable device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the wearable device to perform the aforementioned lock screen display method.
[0120] The above description is merely an exemplary embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.
Claims
1. A method for displaying a lock screen interface, characterized in that, The method is applied to a wearable device, wherein the wearable device is provided with at least a first processor and a second processor; The method includes: When the second processor is in a wake-up state and receives a screen lock command, the screen state corresponding to the second processor is set to a screen lock state. The second processor synchronizes the screen lock state to the first processor. Set the screen state corresponding to the first processor to the locked screen state; The lock screen interface is displayed through the first processor.
2. The method according to claim 1, characterized in that, The lock screen state includes an encrypted lock screen state and an unencrypted lock screen state; The step of synchronizing the screen lock state to the first processor via the second processor includes: When the lock screen state includes the encrypted lock screen state, the encrypted lock screen state is synchronized to the first processor via the second processor. If the lock screen state includes the unencrypted lock screen state, the unencrypted lock screen state is synchronized to the first processor by the second processor.
3. The method according to claim 1, characterized in that, After displaying the lock screen interface through the first processor, the process further includes: In the case where the lock screen state includes an encrypted lock screen state, the second processor is in a sleep state and the first processor receives an unlock command, the second processor is woken up by the first processor. The second processor receives user-input verification information, which is used to trigger the second processor to perform identity verification. The second processor executes the unlocking process based on the user-input verification information and preset verification information.
4. The method according to claim 3, characterized in that, The first processor corresponds to the first system, which refers to the system running by the first processor; the second processor corresponds to the second system, which refers to the system running by the second processor. The step of receiving user-input verification information through the second processor includes: The unlock interface is displayed through the second system; The second system receives the verification information entered by the user on the unlock interface.
5. The method according to claim 4, characterized in that, The step of executing the unlocking process by the second processor based on the user-input verification information and preset verification information includes: The second system confirms whether the verification information entered by the user is consistent with the preset verification information; In response to the user input verification information matching the preset verification information, the user interface is displayed through the first system or the second system based on the operating mode of the wearable device.
6. The method according to claim 5, characterized in that, The operating mode based on the wearable device is displayed through the first system or the second system, including: When the wearable device operates in a smart mode, the first user interface is displayed through the second system; When the wearable device operates in a non-smart mode, a second user interface is displayed through the first system.
7. The method according to claim 1, characterized in that, The power consumption of the second processor is higher than that of the first processor.
8. The method according to claim 4, characterized in that, The method further includes: The unlock interface is drawn and displayed by the first system, and the unlock interface is the user interface of the second system; After the second system completes the drawing of the unlock interface, the system running on the wearable device is switched from the first system to the second system, and the unlock interface is displayed through the second system.
9. The method according to claim 1, characterized in that, The method further includes: When the second processor is in sleep mode and the first processor is in wake-up mode, the third user interface is displayed through the first processor; In response to a system switching command, a fourth user interface is displayed via the second processor.
10. The method according to claim 4, characterized in that, The method further includes: When the first processor is in the wake-up state, the first processor processes low-performance events, which are events that draw and display the lock screen interface or the unlock interface, where the unlock interface is the user interface of the second system. In the event of a pending high-performance event, the first processor wakes up the second processor, and the second processor processes the high-performance event, which is to draw the unlock interface and execute the unlock process. The sliding speed of the unlock interface displayed by the first system is determined based on the time required for the second system to be woken up and complete the drawing of the unlock interface.
11. A method for displaying a lock screen interface, characterized in that, The method is applied to a wearable device, wherein the wearable device is provided with at least a first processor and a second processor; The method includes: When the first processor is in a wake-up state and the first processor receives a screen lock command, the screen state corresponding to the first processor is set to a screen lock state. The lock screen state is synchronized to the second processor via the first processor; Set the screen state corresponding to the second processor to the locked screen state; The lock screen interface is displayed through the first processor.
12. The method according to claim 11, characterized in that, The power consumption of the second processor is higher than that of the first processor.
13. A display device for a lock screen interface, characterized in that, The device is applied to a wearable device, which is provided with at least a first processor and a second processor; The device includes: The state setting module is used to set the screen state corresponding to the second processor to the locked state when the second processor is in the wake-up state and the second processor receives a lock screen command. A state synchronization module is used to synchronize the screen lock state to the first processor via the second processor; The state setting module is also used to set the screen state corresponding to the first processor to the lock screen state; The interface display module is used to display the lock screen interface through the first processor.
14. A display device for a lock screen interface, characterized in that, The device is applied to a wearable device, which is provided with at least a first processor and a second processor; The device includes: The state setting module is used to set the screen state corresponding to the first processor to the locked state when the first processor is in the wake-up state and the first processor receives a screen lock command. A state synchronization module is used to synchronize the screen lock state to the second processor via the first processor; The state setting module is also used to set the screen state corresponding to the second processor to the lock screen state; The interface display module is used to display the lock screen interface through the first processor.
15. A wearable device, characterized in that, The wearable device includes a processor and a memory; the processor includes at least a first processor and a second processor, the power consumption of the second processor being higher than that of the first processor, and the memory stores a computer program, which is loaded and executed by the processor to implement the lock screen interface display method as described in any one of claims 1 to 10, or to implement the lock screen interface display method as described in claim 11 or 12.
16. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which is loaded and executed by a processor to implement the lock screen display method as described in any one of claims 1 to 10, or to implement the lock screen display method as described in claim 11 or 12.
17. A computer program product, characterized in that, The computer program product includes computer instructions that are loaded and executed by a processor to implement the lock screen display method as described in any one of claims 1 to 10, or to implement the lock screen display method as described in claim 11 or 12.