Message notification method and device, wearable equipment, storage medium and product
A dual-core dual-system architecture in wearable devices addresses high power consumption by utilizing a low-power first operating system for smartwatches, optimizing power usage and maintaining seamless notification processing and user experience.
Patent Information
- Application Number
- CN202411081692.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-07
- Publication Date
- 2024-12-06
AI Technical Summary
Single-core, single-system smartwatches face high power consumption and short battery life, necessitating an adaptation of the operating system for dual-core hardware, particularly in processing notification messages.
Implement a dual-core dual-system architecture in wearable devices, where a first core controller runs a low-power first operating system and a second core controller runs a higher-power second operating system, with distinct processing strategies for each to manage notification messages, optimizing power consumption and user experience.
The dual-core system reduces power consumption by leveraging lower-power operations for the first operating system, while ensuring seamless notification processing and user experience through strategic synchronization and display management across both cores.
Smart Images

Figure CN119088198A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of wearable devices, and in particular to a message notification method, apparatus, wearable device, storage medium and product. Background Art
[0002] The smartwatch operating system was originally developed for single-core, single-system smartwatches. However, the biggest problem with single-core, single-system smartwatches is their high power consumption and short battery life. How to adapt the original smartwatch operating system to dual-core hardware, especially how to process notification messages, is the focus of the industry. Summary of the invention
[0003] The embodiments of the present application provide a message notification method, apparatus, wearable device, storage medium and product, which can reduce the power consumption of electronic devices. The technical solution is as follows:
[0004] On the one hand, a message notification method is provided, which is performed by a wearable device, wherein the wearable device includes a first core controller and a second core controller, wherein the first core controller is used to run a first operating system, and the second core controller is used to run a second operating system, and the power consumption of the first core controller running the first operating system is lower than the power consumption of the second core controller running the second operating system;
[0005] The method comprises:
[0006] When the first operating system receives a first notification message from an electronic device connected to the wearable device, processing the first notification message based on a first processing strategy;
[0007] When the second operating system receives the second notification message of the wearable device, the second notification message is processed based on a second processing strategy.
[0008] On the other hand, a message notification device is provided, which is deployed in a wearable device, wherein the wearable device includes a first core controller and a second core controller, wherein the first core controller is used to run a first operating system, and the second core controller is used to run a second operating system, and the power consumption of the first core controller running the first operating system is lower than the power consumption of the second core controller running the second operating system;
[0009] The device comprises:
[0010] A first processing module, configured to process a first notification message from an electronic device connected to the wearable device based on a first processing strategy when the first operating system receives the first notification message from the electronic device connected to the wearable device;
[0011] The second processing module is configured to process the second notification message based on a second processing strategy when the second operating system receives the second notification message from the wearable device.
[0012] On the other hand, a wearable device is provided, the wearable device comprising a first core controller, a second core controller and a memory, the first core controller is used to run a first operating system, the second core controller is used to run a second operating system, and the power consumption of the first core controller running the first operating system is lower than the power consumption of the second core controller running the second operating system;
[0013] At least one program code is stored in the memory, and the at least one program code is loaded and executed by the first core controller and the second core controller to implement the message notification method described in any of the above implementation modes.
[0014] On the other hand, a computer-readable storage medium is provided, in which at least one program code is stored. The at least one program code is loaded and executed by a processor to implement the message notification method described in any of the above implementations.
[0015] On the other hand, a computer program product is provided, wherein the computer program product stores at least one program code, and the at least one program code is used to be executed by a processor to implement the message notification method as described in any of the above implementations.
[0016] In an embodiment of the present application, by setting a first processing strategy and a second processing strategy, the first operating system processes the received first notification message based on the first processing strategy, and the second operating system processes the received second notification message based on the second processing strategy, thereby enabling the notification message to be processed based on a dual-core dual system. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] Figure 1 A notification architecture diagram of a single-core single-system wearable device shown in an exemplary embodiment of the present application is shown;
[0018] Figure 2 A flowchart of a message notification method shown in an exemplary embodiment of the present application is shown;
[0019] Figure 3 A flowchart of a message notification method shown in an exemplary embodiment of the present application is shown;
[0020] Figure 4 A flowchart of a message notification method shown in an exemplary embodiment of the present application is shown;
[0021] Figure 5A flowchart of a message notification method shown in an exemplary embodiment of the present application is shown;
[0022] Figure 6 A flowchart of a message notification method shown in an exemplary embodiment of the present application is shown;
[0023] Figure 7 A flowchart of a message notification method shown in an exemplary embodiment of the present application is shown;
[0024] Figure 8 A flowchart of a message notification method shown in an exemplary embodiment of the present application is shown;
[0025] Fig. 9 A flowchart of a message notification method shown in an exemplary embodiment of the present application is shown;
[0026] Fig.10 A flowchart of a message notification method shown in an exemplary embodiment of the present application is shown;
[0027] Fig.11 A block diagram of a message notification device shown in an exemplary embodiment of the present application is shown;
[0028] Fig.12 A block diagram of a wearable device according to an exemplary embodiment of the present application is shown. DETAILED DESCRIPTION
[0029] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.
[0030] The term "multiple" as used herein refers to two or more than two. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship.
[0031] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.) and signals involved in this application are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions. For example, the notification messages involved in this application are all obtained with full authorization.
[0032] The wearable operating system in the related art is developed for single-core single-system wearable devices. For the existing wearable operating system, in order to adapt it to the dual-core hardware, it needs to run on one of the dual cores and cooperate with the other core and the system running on it. This application is a solution for the dual-core dual-system notification scenario. For example, the notification architecture of a single-core single-system wearable device is as follows: Figure 1 As shown; please refer to Figure 1 , the notification architecture includes: electronic devices and wearable devices, the wearable devices include a data center (WearServices) in the WearOS system and a system interface (SysUI) in the WearOS system, WearServices is used to run the WearOS operating system, and notification messages are transmitted between WearServices and electronic devices via a wireless link (Bluetooth communication link or Wifi communication link, etc.), and notification messages are transmitted between WearServices and SysUI via a cross-process communication channel. For example, a notification message on an electronic device is forwarded to WearServices in a wearable device via a wireless link, and then WearServices forwards the notification message to SysUI for display through a cross-process communication channel. In addition, WearServices is also responsible for receiving notification messages on wearable devices, and forwarding notification messages to SysUI for display through a cross-process communication channel. In some embodiments, the wearable device may be a smart watch or a smart bracelet, etc.; the electronic device may be a smart phone, a tablet computer, or a vehicle-mounted terminal, etc.
[0033] In some embodiments, the dual-core dual-system wearable device includes a first core controller and a second core controller, the first core controller is used to run the first operating system, the second core controller is used to run the second operating system, and the power consumption of the first core controller running the first operating system is lower than the power consumption of the second core controller running the second operating system, that is, the first operating system is a small-core operating system, and the second operating system is a large-core operating system; for example, the first operating system can be (Real Time Operating System, RTOS), the second operating system can be Hongmeng operating system, Android operating system, etc., such as WearOS; the first core controller can be a microcontroller unit (Microcontroller Unit, MCU). The second core controller can be a central processing unit (Central Processing Unit, CPU).
[0034] In some embodiments, the first core controller and the second core controller may be two independently packaged chips respectively; in other embodiments, the first core controller and the second core controller may be two different processing modules packaged in the same chip, without limitation.
[0035] In some embodiments, the first operating system can be running all the time. In some embodiments, the first operating system can be running or sleeping, for example, it can sleep when there is no business to be executed, that is, it can sleep or wake up according to demand. In some embodiments, the second operating system can also sleep or wake up according to demand. In addition, the operation of the operating system (the first operating system or the second operating system) is divided into foreground operation and background operation. Whichever operating system is running in the foreground, the operating rights of part or all of the peripherals such as screen display, motor vibration, sound playback, and user interaction of the wearable device will be handled by that operating system. In some embodiments, the operating system running in the foreground will at least have direct control over the screen display; in some embodiments, the operating system running in the foreground can also have direct control over other peripherals; of course, in some embodiments, some peripherals are fixedly connected to a certain operating system, that is, they are directly controlled by the operating system, and another operating system needs to control them with the help of the operating system with direct control. In some embodiments, some peripherals can switch direct control rights between two operating systems. In some embodiments, all peripherals can be mounted on a certain system (it can also be understood as being connected to the core controller running the system), that is, the direct control rights of the peripherals are owned by one system. Of course, the above embodiments can be combined with each other and exist at the same time without conflict. In order to reduce the power consumption of the wearable device, in some embodiments, the first operating system can be run in the foreground as much as possible, and the second operating system can be put into a dormant state. The second operating system will only be awakened when the capabilities of the second operating system are needed, and the second operating system will be run in the background. Only when it is necessary (such as opening a third-party application) will the second operating system be switched to the foreground to run, and the first operating system will be switched to the background to run. Therefore, in order to receive the notification message synchronized by the electronic device to the wearable device when the first operating system is running in the foreground and the second operating system is in a dormant state, the notification message of the electronic device is directly sent to the first operating system, and then the first operating system synchronizes the notification message to the second operating system when the second operating system is switched to the foreground to run, so as to update the notification interface of the second operating system. Alternatively, when the second operating system is in the background (for example, in the background wake-up state), the first operating system synchronizes the notification message to the second operating system to update the notification interface of the second operating system.
[0036] It can be understood that the notification message can be generated by an electronic device that can wirelessly communicate with the wearable device and sent to the wearable device through a wireless link, such as a first notification message; the notification message can also be generated by the first operating system end or the second operating system end, for example, the notification message generated by the application of the second operating system can be the second notification message, and the notification message generated by the application of the first operating system can be the fifth notification message.
[0037] In some embodiments, the notification message is generated by an application of an operating system of the wearable device. If it is generated by an application of the first operating system, the first operating system can receive the notification message (for example, the notification message can be the fifth notification message) and then forward it to the second operating system; if the second operating system is running in the background when the notification message is received, the second operating system is controlled to switch to the foreground and process the notification message. If the notification message is generated by the application of the second operating system (for example, the notification message can be the second notification message), it is directly received and processed by the second operating system and synchronized to the first operating system. If the second operating system is running in the background when receiving the notification message, the second operating system can be switched to the foreground to process the notification message. In some embodiments, when the second operating system is running in the background, its application generates a notification message (for example, the notification message can be the second notification message), which can be synchronized by the second operating system to the first operating system, and the first operating system prompts the notification message in the foreground (the prompt may be a prompt based on the resources of the first operating system that can be supported, such as a simple text notification). When it is used to trigger the notification message, the second operating system is switched to the foreground to process the notification message. Of course, after the second operating system synchronizes the notification message (for example, the notification message may be the second notification message) to the first operating system, if the user does not trigger the notification message within a preset time, the second operating system may enter a sleep state to save power consumption. When the user triggers the notification message on the first operating system, the second operating system is woken up and switched to the foreground to run, so as to process the notification message.
[0038] In some embodiments, it is not necessary to distinguish whether the second operating system is in the foreground or the background. As long as the synchronization conditions are met, the second operating system can be awakened to synchronize the notification message. For example, when a notification message transmitted by an electronic device wirelessly connected to the wearable device is received (for example, the notification message can be the first notification message), the type of the notification message is determined. When the type of the message indicates that the second operating system is required to execute, the second operating system can be awakened first to synchronize the notification message to the second operating system, and a notification message prompt is performed on the first operating system. When the user triggers the prompt, the second operating system is switched to the foreground to process the business corresponding to the notification message.
[0039] In some embodiments, based on the type of notification message received (for example, the notification message may be the first notification message and / or the second notification message), it is determined whether the notification message is processed by the first operating system or the second operating system. When it is determined that the notification message is processed by the second operating system, a notification message prompt may be first performed on the first operating system. When a trigger instruction for the prompt is received from the user, the second operating system is woken up and the notification message is synchronized to the second operating system, so that the second operating system runs in the foreground to facilitate processing of the business corresponding to the notification message.
[0040] Please refer to Figure 2 , which shows a flow chart of a message notification method shown in an exemplary embodiment of the present application. The execution subject in the embodiment of the present application may be a wearable device, the wearable device includes a first core controller and a second core controller, the first core controller is used to run a first operating system, the second core controller is used to run a second operating system, and the power consumption of the first core controller running the first operating system is lower than the power consumption of the second core controller running the second operating system. Among them, the power consumption of the first core processor running the first operating system is lower than the power consumption of the second core processor running the second operating system, which can be manifested in one or more of the following aspects: when the first system or the second system does not perform any business operations, the power consumption of the first system is lower than the power consumption of the second system. For example, when no business operations are performed, the first system and the second system can be in a dormant state or a wake-up state; or, the power consumption when processing a certain business through the first system is lower than the power consumption when processing the same business through the second system; the above power consumption can be compared by measuring the current; or, according to the fact that the processing performance of the first system is lower than the processing performance of the second system, it can be considered that the power consumption of running the first system is lower than the power consumption of running the second system. . See Figure 2 , the method comprising:
[0041] Step 201: When the first operating system receives a first notification message from an electronic device connected to a wearable device, the first notification message is processed based on a first processing strategy.
[0042] The first notification message is a notification message of an application included in the electronic device. When the electronic device is a mobile phone, the first notification message can be called a mobile phone notification. The first notification message is first sent to the first core controller, and the first core controller processes the first notification message based on the first processing strategy. The first processing strategy may include a first synchronization strategy; accordingly, this step may be: when the first operating system receives the first notification message of the electronic device connected to the wearable device, the first core controller synchronizes the first notification message to the second operating system based on the first synchronization strategy. In some embodiments, when the second core controller includes WearServices and SysUI, the first core controller synchronizes the first notification message to WearService based on the synchronization strategy, and WearService synchronizes the first notification message to SysUI through a cross-process communication channel for display. In other embodiments, the first strategy processing may also include a first display strategy, and accordingly, this step may be: when the first operating system receives the first notification message of the wearable device, the first core controller displays the first notification message based on the first display strategy.
[0043] Step 202: When the second operating system receives a second notification message from the wearable device, the second notification message is processed based on a second processing strategy.
[0044] The second notification message is a notification message of an application included in the wearable device. When the wearable device is a watch, the second notification message can be called a watch notification. The second notification message can be first sent to the second core controller, and the second core controller processes the second notification message based on the second processing strategy. In some embodiments, the second strategy processing information may include a second synchronization strategy; accordingly, this step may be: when the second operating system receives the second notification message of the wearable device, the second core controller synchronizes the second notification message to the first operating system based on the second synchronization strategy. In other embodiments, the second strategy processing information may also include a second display strategy, and accordingly, this step may be: when the second operating system receives the second notification message of the wearable device, the second core controller displays the second notification message based on the second display strategy.
[0045] In some embodiments of the present application, notification messages (including first notification messages and second notification messages) are synchronized between the first operating system and the second operating system, so that the wearable device can display accurate notification messages regardless of whether the first operating system or the second operating system is running in the foreground.
[0046] In some embodiments of the present application, by setting a first processing strategy and / or a second processing strategy, the first operating system processes the received first notification message based on the first processing strategy, and the second operating system processes the received second notification message based on the second processing strategy, thereby enabling the notification message to be processed based on a dual-core dual system.
[0047] For example, an operating system that receives a notification message can determine an operating system that processes the notification message based on the type of the received notification message. If the operating system for processing the notification message is in a dormant state, the operating system for processing the notification message is woken up to synchronize the notification message. In addition, the processing of the notification message (for example, displaying and responding to user touch) is implemented by switching the operating system for processing the notification message to the foreground.
[0048] Please refer to Figure 3 , which shows a flow chart of a message notification method shown in an exemplary embodiment of the present application. The execution subject in the embodiment of the present application can be a wearable device, and the wearable device includes a first core controller and a second core controller. The first core controller is used to run a first operating system, and the second core controller is used to run a second operating system. The power consumption of the first core controller running the first operating system is lower than the power consumption of the second core controller running the second operating system. See Figure 3 , the method comprising:
[0049] Step 301: The wearable device receives a first notification message from the electronic device through a first operating system.
[0050] In some embodiments, when the wearable device is powered on, the first operating system is always in operation (in some embodiments, the first operating system can also be in a dormant state when there is no business demand; the first operating system is awakened when there is business); and no matter whether the first operating system is running in the foreground or the background, the first notification message of the electronic device is sent to the first operating system, and the first operating system receives the first notification message sent by the electronic device. In other embodiments, when the wearable device is powered on, the first operating system is always in operation (in some embodiments, the first operating system can also be in a dormant state when there is no business demand; the first operating system is awakened when there is business); and whichever operating system is running in the foreground, the first notification message of the electronic device is sent to that operating system; accordingly, this step can be: when the first operating system is running in the foreground, the first notification message of the electronic device is sent to the first operating system, and the first operating system receives the first notification message sent by the electronic device; when the second operating system is running in the foreground, the first notification message of the electronic device is sent to the second operating system, and the second operating system receives the first notification message sent by the electronic device.
[0051] In other embodiments, when the wearable device is in the power-on state, the first operating system is always in the running state (in some embodiments, the first operating system can also be in the dormant state when there is no business demand; the first operating system is awakened when there is business); and when the second operating system is in the running state, the first notification message of the electronic device is sent to the second operating system; and when the second operating system is in the dormant state, the first notification message of the electronic device is sent to the first operating system; accordingly, this step can be: when the second operating system is in the running state, the first notification message of the electronic device is sent to the second operating system, and the second operating system receives the first notification message sent by the electronic device; when the second operating system is in the dormant state, the first notification message of the electronic device is sent to the first operating system, and the first operating system receives the first notification message sent by the electronic device.
[0052] Step 302: When the second operating system is in a dormant state, the wearable device stores a first notification message through the first core controller.
[0053] For example, the wearable device storing the first notification message through the first core controller can be understood as storing the first notification message in a storage space accessible to the first core controller, which can be inside the first core controller or outside the first core controller.
[0054] When the first operating system receives the first notification message, the first core controller determines whether the second operating system is in a dormant state; when the second operating system is not in a dormant state (that is, the second operating system is in a running state), the first core controller synchronizes the first notification message to the second operating system. The running state includes foreground running and background running; in some embodiments, when the second operating system is in the foreground running, the first core controller synchronizes the first notification message to the second operating system; and / or, when the second operating system is in the background running, the first core controller synchronizes the first notification message to the second operating system. In addition, after the first notification message is synchronized to the second operating system, the second core controller will also transmit the first notification message to the SysUI included in the second core controller for display.
[0055] When the second operating system is in a dormant state, the first core controller stores the first notification message, and synchronizes the first notification message to the second operating system when the second operating system is subsequently switched to a running state.
[0056] Step 303: When the second operating system is switched to the running state, the wearable device batches the multiple first notification messages stored in the first core controller to obtain one or more batches of notification messages.
[0057] Since the native interface between WearService and SysUI included in the second controller may not support batch addition or deletion of notification messages; therefore, when the first core controller receives a large number of first notification messages and then the second operating system switches to the running state, a large amount of notification message data will be triggered to be synchronized; when the user pulls out the SysUI notification bar interface, he will see that notification messages are added one by one, resulting in a poor user experience; therefore, in some embodiments of the present application, the synchronization mechanism of notification messages is optimized, and multiple first notification messages are synchronized in batches, thereby improving the user experience. Accordingly, the steps for the wearable device to batch the multiple first notification messages stored in the first core controller to obtain one or more batches of notification messages can be:
[0058] The wearable device divides the multiple first notification messages stored in the first core controller into one or more of a first batch of notification messages, a second batch of notification messages and a third batch of notification messages based on the multiple first notification messages stored in the first core controller and the second notification messages stored in the second core controller, the first batch of notification messages are read notification messages, or the second batch of notification messages are unchanged notification messages, or the third batch of notification messages are newly added notification messages, the third batch of notification messages includes a first notification message set and a second notification message set, the first notification message set includes a first preset number of notification messages that have been recently added, and the second notification message set includes other newly added notification messages except the first notification message set.
[0059] For example, the wearable device storing the second notification message through the second core controller can be understood as storing the second notification message in a storage space accessible to the second core controller, which can be inside the second core controller or outside the second core controller.
[0060] A read notification message refers to a notification message that is read when the first operating system is running in the foreground; an unchanged notification message refers to a notification message that is always displayed in the notification bar interface when the first operating system is running in the foreground; a newly added notification message refers to a notification message received by the first operating system when the first operating system is running in the foreground, and / or a notification message received by the first operating system when the first operating system is running in the background.
[0061] When the operating system running in the foreground of the wearable device is switched from the first operating system to the second operating system, the notification message stored in the first core controller is frozen (at this time, the notification message is not stored in the first core controller, and the message stored in the first core controller is not deleted) and the notification message stored in the second core controller is frozen (at this time, the notification message is not stored in the second core controller, and the message stored in the second core controller is not deleted), thereby determining the first notification message stored in the first core controller and the second notification message stored in the second core controller. In addition, since the notification message is divided into two types, one is the first notification message from the electronic device (also referred to as a remote notification message), and the other is the second notification message from the wearable device (also referred to as a local notification message); when the first operating system determines the synchronization message that needs to be synchronized to the second operating system, it distinguishes whether the notification message is a local notification message or a remote notification message. Since the local notification message may be synchronized from the second operating system to the first operating system; therefore, the local notification message does not need to be synchronized to the second operating system, and in this step, only the remote notification message needs to be synchronized to the second operating system, that is, the first notification message is synchronized. In addition, the local notification message is generated by the second operating system, and there is no local notification message in the electronic device; therefore, the first operating system can also synchronize the local notification message to the electronic device; in some embodiments, when the first operating system is running in the background, the local notification message is synchronized to the electronic device; and / or when the first operating system is running in the foreground, the local notification message is synchronized to the electronic device.
[0062] In some other embodiments, the first operating system may also receive notification messages from wearable devices; for ease of distinction, the notification message received by the first operating system from the wearable device is referred to as the fifth notification message, and when the second operating system receives the fifth notification message from the wearable device, the fifth notification message is synchronized to the second operating system and / or the fifth notification message is synchronized to the electronic device. The fifth notification message is also a local notification message, so in this step, the first operating system determines the fifth notification message generated by the first operating system from the local notification message, and then batches the fifth notification message and multiple first notification messages to obtain one or more batches of notification messages, and then executes step 304.
[0063] Step 304: The wearable device synchronizes one or more batches of notification messages to the second operating system.
[0064] This step can be implemented by at least one of the following steps (1) to (3), including:
[0065] (1) The wearable device synchronizes the message identifiers of the first batch of notification messages to the second operating system.
[0066] Please refer to Figure 4 When the operating system running in the foreground is switched from the first operating system to the second operating system, or when the second operating system is switched from the sleep state to the background running state, the first core controller synchronizes the message identifier of the read notification message (the message identifier of the first batch of notification messages) to the second operating system, so that the second operating system updates the unread icon of the application based on the message identifier of the read notification message, and the unread icon is used to indicate the number of unread notification messages; when the number of unread notification messages is 0, the unread icon of the application is deleted. Among them, the first core controller informs the second operating system of the message identifier of the read notification message through the first protocol. In some embodiments of the present application, since the message identifier of the read notification message is synchronized during the operating system switching stage, the status of the notification message can be accurately displayed after the operating system is switched.
[0067] (2) The wearable device synchronizes the second batch of notification messages to the second operating system, so that the second operating system deletes other notification messages except the second batch of notification messages.
[0068] Please continue to refer to Figure 4 , the first notification message set in the second batch of notification messages and the third batch of notification messages are synchronized in the first stage, and the notification messages synchronized in the first stage are the notification messages displayed on the home page of the notification bar interface. Correspondingly, the second core controller (specifically the WearService in the second core controller) sends the second protocol to the first core controller to request to start the first stage synchronization. The first core controller receives the first protocol and sends the third protocol to the second core controller, and the second protocol carries the second batch of notification messages. After receiving the third protocol, the second core controller deletes other notification messages except the second batch of notification messages to prevent the problem of inaccurate display of notification messages due to inconsistency between the notification messages of the first operating system and the second operating system.
[0069] (3) The wearable device synchronizes the first notification message set in the third batch of notification messages to the second operating system; when the synchronization of the first notification message set is completed, the wearable device synchronizes the second notification message set in the third batch of notification messages to the second operating system.
[0070] The first notification message set includes notification messages of type picture and notification messages of type text; in this step, the first core controller first synchronizes notification messages of type picture to the second core controller, and then synchronizes notification messages of type text to the second core controller. For example, please continue to refer to Figure 4The first core controller sends the fourth protocol to the second core controller, and the fourth protocol carries the notification message of the type of picture included in the first notification message set, and then sends the fifth protocol to the second core controller, and the fifth protocol carries the notification message of the type of text included in the first notification message set.
[0071] Please continue to refer to Figure 4 , when the synchronization of the first notification message set is completed, the first core controller sends the sixth protocol to the second core controller to inform the second core controller that the first phase has been synchronized and carries a mark whether the second phase synchronization is required. When the second phase synchronization is required, the second core controller prepares the historical notification interface of the notification bar interface, and then sends the seventh protocol to the first core controller to start the second phase synchronization. The second notification message set also includes notification messages of the message type of picture and notification messages of the type of text; the first core controller first synchronizes the notification message of the type of picture to the second core controller, and then synchronizes the notification message of the type of text to the second core controller. Correspondingly, the first core controller sends the fourth protocol to the second core controller, the fourth protocol carries the notification message of the type of picture included in the second notification message set, and then sends the fifth protocol to the second core controller, the fifth protocol carries the notification message of the type of text included in the second notification message set, and then sends the sixth protocol to the second core controller to inform that the second phase synchronization is completed; after receiving the sixth protocol, the second core controller completes the notification message.
[0072] In some embodiments, step 304 may be implemented by one or more of the above steps (1) to (3); and, when step 304 is implemented by multiple steps of the above steps (1) to (3), the execution order of the multiple steps may be adjusted as needed; for example, step 304 may be implemented by the following steps (1) to (3), and the execution order of (1) to (3) may be (1)-(2)-(3), (1)-(3)-(2), (2)-(1)-(3), (2)-(3)-(1), (3)-(2)-(1), or (3)-(1)-(2). In some embodiments of the present application, the execution order of (1) to (3) is not specifically limited.
[0073] In some embodiments of the present application, by optimizing the synchronization mechanism of notification messages, multiple first notification messages are synchronized in batches, and the message identifiers of the read notification messages are synchronized first, so that the second operating system after switching can accurately display the number of unread messages on the application icon; then the unchanged notification messages and the most recently added notification messages are synchronized again, so that the notification messages displayed in the notification bar interface can be synchronized at the first time, so that the user is unaware of the switching of the operating system running in the foreground, thereby improving the user experience.
[0074] Please refer to Figure 5 , which shows a flow chart of a message notification method shown in an exemplary embodiment of the present application. The execution subject in the embodiment of the present application can be a wearable device, and the wearable device includes a first core controller and a second core controller. The first core controller is used to run a first operating system, and the second core controller is used to run a second operating system. The power consumption of the first core controller running the first operating system is lower than the power consumption of the second core controller running the second operating system. See Figure 5 , the method comprising:
[0075] Step 501: The wearable device receives a second notification message of the wearable device through a second operating system.
[0076] The second notification message is a notification message of an application included in the wearable device; after receiving the second notification message, the second core controller (specifically, the WearService in the second core controller) determines the type of the second notification message; when the second notification message is a full-screen notification message, execute step 502; when the second notification message is a non-full-screen notification message, synchronize the second notification message to the first operating system. In some embodiments, a full-screen notification message refers to a notification message that requires opening the corresponding application interface to display; for example, a notification message for a voice call is a full-screen notification message. Since only notification messages sent by applications on wearable devices can be configured for full-screen notification messages, full-screen notification messages are always sent to the second core controller, and then synchronized to the first core controller by the second core controller.
[0077] Step 502: When the second notification message is a full-screen notification message, the wearable device determines the operating system running in the foreground.
[0078] When the operating system running in the foreground is the first operating system, step 503 is executed; when the operating system running in the foreground is the second operating system, step 504 is executed.
[0079] Step 503: When the operating system running in the foreground is the first operating system, the wearable device switches the operating system running in the foreground from the first operating system to the second operating system, displays the application interface corresponding to the second notification message through the second operating system, and displays the second notification message based on the application interface.
[0080] Step 504: When the operating system running on the current platform is the second operating system, the wearable device directly displays the application interface corresponding to the second notification message through the second operating system, and displays the second notification message based on the application interface.
[0081] In some embodiments of the present application, through the cooperation of the first core controller and the second core controller, the operating system of the wearable device can be integrated with the dual-core hybrid technology and still support full-screen notification messages.
[0082] Please refer to Figure 6 , which shows a flow chart of a message notification method shown in an exemplary embodiment of the present application. The execution subject in the embodiment of the present application can be a wearable device, and the wearable device includes a first core controller and a second core controller. The first core controller is used to run a first operating system, and the second core controller is used to run a second operating system. The power consumption of the first core controller running the first operating system is lower than the power consumption of the second core controller running the second operating system. See Figure 6 , the method comprising:
[0083] Step 601: The wearable device displays a notification details interface, where the notification details interface displays at least one third notification message and an operation button corresponding to the third notification message, where the at least one third notification message includes at least one of the first notification message and the second notification message.
[0084] The third notification message carries Action or ContentIntent. The operation buttons corresponding to the third notification message carrying Action include reply buttons and non-reply buttons. The operation buttons corresponding to the third notification message carrying ContentIntent include non-reply buttons. The reply buttons can reply based on the third notification message, and the non-reply buttons are "Open on xxx". When the user clicks the non-reply button, the wearable device immediately opens the application corresponding to the third notification message and displays the third notification message on the application. When the user clicks the reply button, the wearable device can reply to the third notification message.
[0085] Step 602: When a triggering operation of an operation button corresponding to any third notification message is detected, the wearable device determines the type of the operation button.
[0086] The types of operation buttons include reply type and non-reply type. In some embodiments, after the wearable device determines the type of the operation button, it processes the third notification message based on the type of the operation button through steps 603-607.
[0087] Step 603: When the type of the operation button is non-reply type, the wearable device determines the source of the third notification message and the operating system running in the foreground.
[0088] The source of the third notification message is an electronic device or a wearable device.
[0089] Step 604: When the source of the third notification message is an electronic device and the operating system running in the foreground is the second operating system, the wearable device forwards the trigger operation to the first operating system, so that the first operating system forwards the trigger operation to the electronic device, and the electronic device executes the trigger operation.
[0090] When the source of the third notification message is an electronic device and the operating system running in the foreground is the first operating system, the wearable device directly forwards the trigger operation to the electronic device through the first operating system, and the electronic device performs the trigger operation. In the case where the third notification message is the first notification message, the trigger operation may be invokeRemoteNotificationAction. In the case where the third notification message is the second notification message, the trigger operation is onInvokedLocalNotificationAction. When the source of the third notification message is an electronic device and the operating system running in the foreground is the first operating system, the first operating system forwards the trigger operation to the electronic device, and the electronic device performs the trigger operation.
[0091] Step 605: When the source of the third notification message is a wearable device, and the operating system running in the foreground is the first operating system, the wearable device forwards the trigger operation to the second operating system, and switches the second operating system to the foreground, so that the second operating system executes the trigger operation.
[0092] In some embodiments, when the first operating system has stronger capabilities, the trigger operation can also be performed through the first operating system; accordingly, step 605 can be replaced by: when the source of the third notification message is a wearable device, and the operating system running in the foreground is the first operating system, the wearable device performs the trigger operation through the first operating system. In other embodiments, when the source of the third notification message is a wearable device, and the operating system running in the foreground is the second operating system, the wearable device directly performs the trigger operation through the second operating system.
[0093] Step 606: When the type of the operation button is a reply type, the wearable device switches the second operating system to the foreground and generates multiple quick reply phrases through the second operating system.
[0094] In some embodiments, when the type of the operation button is a reply type, the wearable device can also generate multiple quick reply words through the first operating system; accordingly, step 606 can be replaced with: when the type of the operation button is a reply type, the wearable device generates multiple quick reply words through the first operating system.
[0095] Step 607: The wearable device displays a notification reply interface, where the notification reply interface includes a quick reply list, where the quick reply list includes multiple quick reply words.
[0096] In some embodiments of the present application, through the cooperation of the first core controller and the second core controller, the operating system of the wearable device can be integrated with the dual-core hybrid technology and still support intelligent reply language.
[0097] Please refer to Figure 7 , which shows a flow chart of a message notification method shown in an exemplary embodiment of the present application. The execution subject in the embodiment of the present application is a wearable device, and the wearable device includes a first core controller and a second core controller. The first core controller is used to run a first operating system, and the second core controller is used to run a second operating system. The power consumption of the first core controller running the first operating system is lower than the power consumption of the second core controller running the second operating system. Figure 7 , the method comprising:
[0098] Step 701: When the state of the third notification message changes, the wearable device determines the operating system running in the foreground, and the third notification message is any notification message of the first notification message and the second notification message.
[0099] The first core controller and the second core controller not only need to synchronize whether there are unread notification messages, but also need to accurately synchronize the status of each notification message, whether it is read or unread, so that the present application can support the display of the number of unread notification messages. Therefore, when the status of the third notification message changes, that is, when the status of the third notification message is changed from unread to read, the wearable device determines the operating system running in the foreground, and then synchronizes the status of the third notification message between the first operating system and the second operating system based on the operating system running in the foreground through steps 702-703.
[0100] Step 702: When the operating system running on the current platform is the second operating system, the wearable device synchronizes the status of the third notification message to the first operating system.
[0101] Step 703: When the operating system currently running is the first operating system, the wearable device temporarily suspends synchronization of the status of the first notification message; when the operating system currently running is switched from the first operating system to the second operating system, the status of the first notification message is synchronized to the second operating system.
[0102] In some embodiments, when the second operating system is in the background running state, the status of the first notification message can also be synchronized; accordingly, step 703 can be replaced by: when the operating system currently running is the first operating system and the second operating system is in the sleep state, the wearable device temporarily suspends synchronization of the status of the first notification message; when the second operating system switches from the sleep state to the background running state, the wearable device synchronizes the status of the first notification message to the second operating system.
[0103] In some embodiments of the present application, the second core controller synchronizes the status of the first notification message to the first core controller, thereby ensuring that regardless of whether the operating system running in the foreground is the first operating system or the second operating system, the wearable device can accurately display the status of the notification message, thereby improving the accuracy of the status synchronization of the notification message.
[0104] Please refer to Figure 8 , which shows a flow chart of a message notification method shown in an exemplary embodiment of the present application. The execution subject in the embodiment of the present application can be a wearable device, and the wearable device includes a first core controller and a second core controller. The first core controller is used to run a first operating system, and the second core controller is used to run a second operating system. The power consumption of the first core controller running the first operating system is lower than the power consumption of the second core controller running the second operating system. See Figure 8 , the method comprising:
[0105] Step 801: when the wearable device is turned off, the wearable device stores a fourth notification message in a database through the second operating system, where the fourth notification message is a notification message that has not been processed before the wearable device is turned off.
[0106] In some embodiments, since the storage space of the second core controller is larger than the storage space of the first core controller; therefore, the second core controller will store the currently held fourth notification message in the database for persistent storage when the wearable device is turned off. In other embodiments, the first core controller and the second core controller can share storage space; then the third notification message can also be stored through the first core memory; accordingly, step 801 can be: when the wearable device is turned off, the wearable device stores the fourth notification message in the database (database in the shared storage space) through the first operating system. In other embodiments, the first core controller and the second core controller can share storage space, and before the wearable device is turned off, which operating system is in the running state, which operating system executes the storage step of the fourth notification message; accordingly, step 801 can be replaced by: when the first operating system is in the running state before the wearable device is turned off, the wearable device stores the fourth notification message in the database (database in the shared storage space) through the first operating system; and / or, when the second operating system is in the running state before the wearable device is turned off, the wearable device stores the fourth notification message in the database (database in the shared storage space) through the second operating system. When both operating systems are in running state, whichever operating system is in the foreground will execute the step of storing the fourth notification message; accordingly, step 801 can be replaced by: when the first operating system is in the foreground before the wearable device is shut down, the wearable device stores the fourth notification message in the database through the first operating system; and / or, when the second operating system is in the foreground before the wearable device is shut down, the wearable device stores the fourth notification message in the database through the second operating system.
[0107] Step 802: When the wearable device is turned on, the wearable device synchronizes the stored fourth notification message to the first operating system through the second operating system.
[0108] In some embodiments, the fourth notification message is synchronized through the first operating system; accordingly, step 802 can be replaced by: when the wearable device is turned on, the wearable device synchronizes the stored fourth notification message to the second operating system through the first operating system. In other embodiments, the first core controller and the second core controller can share a storage space, and when the wearable device is turned on, the first operating system and the second operating system may not synchronize the fourth notification message, and no matter which operating system needs to use the fourth notification message, it can directly obtain the fourth notification message from the shared storage space.
[0109] In some embodiments of the present application, when the wearable device is turned on, the second core controller can recover the fourth notification message from the database, while the first core controller will lose all notification messages; therefore, when the wearable device is turned on, the first core controller will request the second core controller to synchronize the recovered fourth notification message to the first core controller, so as to ensure that the notification messages of the first core controller and the second core controller are always consistent.
[0110] Please refer to Fig. 9 , which shows a flow chart of a message notification method shown in an exemplary embodiment of the present application. The execution subject in the embodiment of the present application can be a wearable device, and the wearable device includes a first core controller and a second core controller. The first core controller is used to run a first operating system, and the second core controller is used to run a second operating system. The power consumption of the first core controller running the first operating system is lower than the power consumption of the second core controller running the second operating system. See Fig. 9 , the method comprising:
[0111] Step 901: When the number of notification messages stored in the first core controller exceeds a second preset number, the wearable device deletes a first target notification message whose storage time is farthest from the current time based on the storage time of each notification message.
[0112] When the first target notification message to be deleted is the first notification message (mobile phone notification), the second core controller sends a third deletion instruction to the first core controller, and the third deletion instruction is used to notify the first core controller to delete the first target notification message. The third deletion instruction can be dismissRemoteNotifications. When the first target notification message to be deleted is the second notification message (watch notification), the second core controller sends a fourth deletion instruction to the first core controller, and the fourth deletion instruction is used to notify the first core controller to delete the first target notification message. The fourth deletion instruction can be deleteLocalNotifications.
[0113] Step 902: The wearable device notifies the second operating system to synchronously delete the first target notification message.
[0114] In some embodiments, the notification messages stored in the second core controller may also exceed the threshold and need to be deleted; accordingly, steps 901-902 can be replaced as follows: when the number of notification messages stored in the second core controller exceeds a third preset number, the wearable device deletes the second target notification message whose storage time is farthest from the current time based on the storage time of each notification message, and notifies the first operating system to synchronously delete the second target notification message.
[0115] In some embodiments of the present application, since the storage space of the first core controller is limited, the number of notification messages that it can store is limited (for example, a maximum of 200). Due to the development of the WearOS system, the number of notification messages stored by the second core controller is uncontrollable; therefore, in order to ensure the consistency of the notification messages of the first core controller and the second core controller, when the first core controller deletes the notification message because the number is exceeded, the second core controller will be immediately informed to delete it synchronously, thereby ensuring that the notification messages of the first core controller and the second core controller are always consistent.
[0116] Please refer to Fig.10 , which shows a flow chart of a message notification method shown in an exemplary embodiment of the present application. The execution subject in some embodiments of the present application is a wearable device, and the wearable device includes a first core controller and a second core controller. The first core controller is used to run a first operating system, and the second core controller is used to run a second operating system. The power consumption of the first core controller running the first operating system is lower than the power consumption of the second core controller running the second operating system. See Fig.10 , the method comprising:
[0117] Step 1001: When a deletion operation of deleting any notification message is detected, the wearable device determines the operating system running in the foreground.
[0118] Step 1002: When the operating system running on the current platform is the second operating system, the wearable device performs a deletion operation on the notification message based on the second operating system.
[0119] When the notification message to be deleted is the first notification message (mobile phone notification), the wearable device sends a first deletion instruction to the second core controller, instructing the second core controller to delete the first notification message based on the first deletion instruction. The first deletion instruction may be onDeletedRemoteNotification. When the notification message to be deleted is the second notification message (watch notification), the wearable device sends a second deletion instruction to the second core controller, instructing the second core controller to delete the first notification message based on the second deletion instruction. The second deletion instruction may be onDismisseNotifications.
[0120] In some embodiments, when the operating system currently running is the first operating system, the wearable device performs a deletion operation on the notification message based on the first operating system. In other embodiments, when the operating system currently running is the first operating system, the deletion operation is performed on the notification message based on the execution type of the deletion operation; accordingly, after executing step 1002, step 1003 is executed.
[0121] Step 1003: When the operating system running on the foreground is the first operating system, the wearable device determines an execution type of the deletion operation, where the execution type is used to indicate that the deletion operation needs to be executed in the foreground or in the background.
[0122] The deletion operation performed in the background may be deleting a broadcast message or deleting a started service, etc. The deletion operation performed in the foreground may be opening an application interface to perform the deletion operation. After the wearable device determines the execution type of the deletion operation, the notification message is deleted based on the execution type through steps 1004 and 1005.
[0123] Step 1004: When the execution type is foreground execution, the wearable device switches the operating system running in the foreground from the first operating system to the second operating system, and performs a deletion operation on the notification message based on the second operating system.
[0124] Step 1005: When the execution type is background execution, the wearable device executes a deletion operation on the notification message in the background through the second operating system.
[0125] In some embodiments, when the execution type is background execution, the wearable device can also perform a deletion operation on the notification message in the background through the first operating system.
[0126] In some embodiments of the present application, through the cooperation of the first core controller and the second core controller, a single-core single system can be run on one of the dual cores, and cooperate with the other core and the operating system running on it, thereby supporting the deletion operation.
[0127] Please refer to Fig.11 , which shows a block diagram of a message notification device shown in an exemplary embodiment of the present application, the device is deployed in a wearable device, the wearable device includes a first core controller and a second core controller, the first core controller is used to run a first operating system, the second core controller is used to run a second operating system, and the power consumption of the first core controller running the first operating system is lower than the power consumption of the second core controller running the second operating system; the device includes:
[0128] The first processing module 1101 is configured to process the first notification message based on a first processing strategy when the first operating system receives a first notification message from an electronic device connected to the wearable device; and / or
[0129] The second processing module 1102 is configured to process the second notification message based on a second processing strategy when the second operating system receives the second notification message from the wearable device.
[0130] In some embodiments, the first processing module 1101 is used to store the first notification message through the first core controller when the second operating system is in a sleep state; when the second operating system switches to a running state, the multiple first notification messages stored in the first core controller are batched to obtain one or more batches of notification messages; and the one or more batches of notification messages are synchronized to the second operating system in batches.
[0131] In some embodiments, the first processing module 1101 is used to divide the multiple first notification messages stored in the first core controller into one or more of a first batch of notification messages, a second batch of notification messages and a third batch of notification messages based on the multiple first notification messages stored in the first core controller and the second notification messages stored in the second core controller; the first batch of notification messages are read notification messages; or the second batch of notification messages are unchanged notification messages; or the third batch of notification messages are newly added notification messages, the third batch of notification messages includes a first notification message set and a second notification message set, the first notification message set includes a first preset number of recently added notification messages, and the second notification message set includes other newly added notification messages except the first notification message set.
[0132] In some embodiments, the first processing module 1101 is used to synchronize the message identifiers of the first batch of notification messages to the second operating system; and / or synchronize the second batch of notification messages to the second operating system so that the second operating system deletes other notification messages except the second batch of notification messages; and / or synchronize the first notification message set in the third batch of notification messages to the second operating system; when the synchronization of the first notification message set is completed, synchronize the second notification message set in the third batch of notification messages to the second operating system.
[0133] In some embodiments, the apparatus further comprises:
[0134] The first determination module is used to determine the operating system running in the foreground when the second notification message is a full-screen type notification message; the third processing module is used to switch the operating system running in the foreground from the first operating system to the second operating system when the operating system running in the foreground is the first operating system, and display the application interface corresponding to the second notification message through the second operating system, and display the second notification message based on the application interface; and / or, the fourth processing module is used to directly display the application interface corresponding to the second notification message through the second operating system, and display the second notification message based on the application interface when the operating system running in the foreground is the second operating system.
[0135] In some embodiments, the apparatus further comprises:
[0136] A display module is used to display a notification details interface, which displays at least one third notification message and an operation button corresponding to the third notification message, and the at least one third notification message includes at least one of the first notification message and the second notification message; a fifth processing module is used to process the third notification message based on the type of the operation button when a trigger operation of the operation button corresponding to any third notification message is detected.
[0137] In some embodiments, the fifth processing module is used to determine the source of the third notification message and the operating system running in the foreground when the type of the operation button is non-reply; when the source of the third notification message is an electronic device and the operating system running in the foreground is a second operating system, the trigger operation is forwarded to the first operating system, so that the first operating system forwards the trigger operation to the electronic device, and the trigger operation is executed by the electronic device; and / or, when the source of the third notification message is a wearable device and the operating system running in the foreground is the first operating system, the trigger operation is executed by the first operating system, or the trigger operation is forwarded to the second operating system, and the second operating system is switched to the foreground, so that the second operating system executes the trigger operation.
[0138] In some embodiments, the fifth processing module is used to switch the second operating system to foreground operation when the type of the operation button is a reply type, generate multiple quick reply words through the second operating system; display a notification reply interface, the notification reply interface includes a quick reply word list, and the quick reply word list includes multiple quick reply words.
[0139] In some embodiments, the apparatus further comprises:
[0140] The second determination module is used to determine the operating system running in the foreground when the status of the third notification message changes, and the third notification message is any notification message between the first notification message and the second notification message; the first synchronization module is used to synchronize the status of the third notification message between the first operating system and the second operating system based on the operating system running in the foreground.
[0141] In some embodiments, the synchronization module is used to synchronize the status of the third notification message to the first operating system when the operating system running on the current platform is the second operating system; to suspend synchronization of the status of the first notification message when the operating system running on the current platform is the first operating system; and to synchronize the status of the first notification message to the second operating system when the operating system running on the current platform is switched from the first operating system to the second operating system.
[0142] In some embodiments, the apparatus further comprises:
[0143] A storage module is used to store a fourth notification message in a database through a second operating system when the wearable device is turned off, wherein the fourth notification message is a notification message that has not been processed before the wearable device is turned off; a second synchronization module is used to synchronize the stored fourth notification message to the first operating system through the second operating system when the wearable device is turned on.
[0144] In some embodiments, the apparatus further comprises:
[0145] The third synchronization module is used to delete the target notification message with the storage time farthest from the current time based on the storage time of each notification message when the number of notification messages stored in the first core controller exceeds the second preset number, and notify the second operating system to synchronously delete the target notification message.
[0146] In some embodiments, the apparatus further comprises:
[0147] The third determination module is used to determine the operating system running in the foreground when a deletion operation is detected that any notification message is deleted; the first deletion module is used to perform a deletion operation on the notification message based on the second operating system when the operating system running on the current platform is the second operating system; the second deletion module is used to determine the execution type of the deletion operation when the operating system running on the current platform is the first operating system, and the execution type is used to indicate that the deletion operation needs to be executed in the foreground or in the background; based on the execution type, the notification message is deleted.
[0148] In some embodiments, a second deletion module is used to switch the operating system running in the foreground from a first operating system to a second operating system when the execution type is foreground execution, and to perform a deletion operation on the notification message based on the second operating system; when the execution type is background execution, the deletion operation is performed on the notification message in the background through the second operating system.
[0149] In some embodiments of the present application, by setting a first processing strategy and a second processing strategy, the first operating system processes the received first notification message based on the first processing strategy, and the second operating system processes the received second notification message based on the second processing strategy, thereby running a single-core single system on one of the dual cores and cooperating with the other core and the operating system running on it, thereby being able to process the notification message based on the dual-core dual system.
[0150] It should be noted that the message notification device provided in the above embodiment only uses the division of the above functional modules as an example when performing message notification. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the wearable device is divided into different functional modules to complete all or part of the functions described above. In addition, the message notification device provided in the above embodiment and the message notification method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.
[0151] Please refer to Fig.12 , which shows a structural block diagram of a wearable device 1200 provided by an exemplary embodiment of the present application. The wearable device 1200 includes a first core controller 1210, a second core controller 1220 and a memory 1230, the first core controller 1210 is used to run a first operating system, the second core controller 1220 is used to run a second operating system, and the power consumption of the first core controller 1210 running the first operating system is lower than the power consumption of the second core controller 1220 running the second operating system;
[0152] At least one program code is stored in the memory 1230, and the at least one program code is loaded and executed by the first core controller 1210 and the second core controller 1220 to implement the above-mentioned message notification method. The second core controller 1220 includes WearService1221 and SysUI1222, WearService1221 is used to run the second operating system, and SysUI1222 is used to display the notification message. The first core controller 1210 or WearService1221 may include one or more processing cores. The first core controller 1210 or WearService1221 uses various interfaces and lines to connect the various parts of the entire wearable device 1200, and executes various functions and processes data of the wearable device 1200 by running or executing instructions, programs, code sets or instruction sets stored in the memory 1230, and calling data stored in the memory 1230. Optionally, the first core controller 1210 or WearService1221 can be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), and programmable logic array (PLA). The first core controller 1210 or WearService1221 can integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), a neural network processor (NPU), and a modem. Among them, the CPU mainly processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing the content that SysUI1222 needs to display; the NPU is used to implement artificial intelligence (AI) functions; and the modem is used to process wireless communications. It is understandable that the above-mentioned modem may not be integrated into the processor first core controller 1210 or WearService1221, and may be implemented separately through a chip.
[0153] The memory 1230 may include a random access memory 1230 (Random Access Memory, RAM), and may also include a read-only memory 1230 (Read-Only Memory). Optionally, the memory 1230 includes a non-transitory computer-readable storage medium. The memory 1230 can be used to store instructions, programs, codes, code sets, or instruction sets. The memory 1230 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 a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the following various method embodiments, etc.; the data storage area may store data created according to the use of the wearable device 1200 (such as audio data, a phone book), etc.
[0154] SysUI1222 is a display component for displaying a user interface. Optionally, the SysUI1222 is a SysUI1222 with a touch function. Through the touch function, the user can use any suitable object such as a finger or a touch pen to perform touch operations on the SysUI1222. SysUI1222 is usually set on the front panel of the wearable device 1200. SysUI1222 can be designed as a full screen, a curved screen, a special-shaped screen, a double-sided screen or a folding screen. SysUI1222 can also be designed as a combination of a full screen and a curved screen, a combination of a special-shaped screen and a curved screen, etc., which is not limited in this embodiment.
[0155] In addition, those skilled in the art can understand that the structure of the wearable device 1200 shown in the above drawings does not constitute a limitation on the wearable device 1200, and the wearable device 1200 may include more or fewer components than shown, or combine certain components, or arrange the components differently. For example, the wearable device 1200 also includes an audio acquisition device, a speaker, a radio frequency circuit, an input unit, a sensor, an audio circuit, a wireless fidelity (Wireless Fidelity, Wi-Fi) module, a power supply, a Bluetooth module and other components, which will not be repeated here.
[0156] An embodiment of the present application also provides a computer-readable medium, which stores at least one program code, and the at least one program code is loaded and executed by the processor to implement the message notification method shown in the above embodiments.
[0157] An embodiment of the present application further provides a computer program product, which stores at least one program code, and the at least one program code is loaded and executed by the processor to implement the message notification method shown in the above embodiments.
[0158] In some embodiments, the computer program product involved in the embodiments of the present application may be deployed to be executed on a wearable device, or on multiple wearable devices located at one location, or on multiple wearable devices distributed at multiple locations and interconnected by a communication network. Multiple wearable devices distributed at multiple locations and interconnected by a communication network may constitute a blockchain system.
[0159] Those skilled in the art should be aware that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented with hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein the communication media include any media that facilitates the transmission of a computer program from one place to another. The storage medium can be any available medium that a general or special-purpose computer can access.
[0160] The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.
Claims
1. A message notification method, It is characterized in that The method is executed by a wearable device, wherein the wearable device includes a first core controller and a second core controller, wherein the first core controller is used to run a first operating system, and the second core controller is used to run a second operating system, and the power consumption of the first core controller running the first operating system is lower than the power consumption of the second core controller running the second operating system; The method comprises: When the first operating system receives a first notification message from an electronic device connected to the wearable device, processing the first notification message based on a first processing strategy; and / or, When the second operating system receives the second notification message of the wearable device, the second notification message is processed based on a second processing strategy.
2. The method according to claim 1, It is characterized in that The processing of the first notification message based on the first processing strategy includes: When the second operating system is in a dormant state, storing the first notification message through the first core controller; When the second operating system is switched to the running state, the plurality of first notification messages stored in the first core controller are divided into batches to obtain one or more batches of notification messages; The one or more batches of notification messages are synchronized to the second operating system in batches.
3. The method according to claim 2, It is characterized in that The step of batching the plurality of first notification messages stored in the first core controller to obtain one or more batches of notification messages includes: Based on the multiple first notification messages stored in the first core controller and the second notification messages stored in the second core controller, dividing the multiple first notification messages stored in the first core controller into one or more of a first batch of notification messages, a second batch of notification messages, and a third batch of notification messages; The first batch of notification messages are read notification messages; or the second batch of notification messages are unchanged notification messages; or the third batch of notification messages are newly added notification messages, and the third batch of notification messages includes a first notification message set and / or a second notification message set, the first notification message set includes a first preset number of recently added notification messages, and the second notification message set includes other newly added notification messages except the first notification message set.
4. The method according to claim 3, It is characterized in that The step of synchronizing the batch or batches of notification messages to the second operating system in batches includes: synchronizing the message identifiers of the first batch of notification messages to the second operating system; and / or, synchronizing the second batch of notification messages to the second operating system, so that the second operating system deletes other notification messages except the second batch of notification messages; and / or, The first set of notification messages in the third batch of notification messages is synchronized to the second operating system; when the synchronization of the first set of notification messages is completed, the second set of notification messages in the third batch of notification messages is synchronized to the second operating system.
5. The method according to claim 1, It is characterized in that The processing the second notification message based on the second processing strategy includes: When the second notification message is a full-screen notification message, determining an operating system running in the foreground; When the operating system running in the foreground is the first operating system, switching the operating system running in the foreground from the first operating system to the second operating system, displaying an application interface corresponding to the second notification message through the second operating system, and displaying the second notification message based on the application interface; and / or, When the operating system running in the foreground is the second operating system, the application interface corresponding to the second notification message is directly displayed through the second operating system, and the second notification message is displayed based on the application interface.
6. The method according to claim 1, It is characterized in that The method further comprises: Displaying a notification details interface, wherein the notification details interface displays at least one third notification message and an operation button corresponding to the third notification message, wherein the at least one third notification message includes at least one of the first notification message and the second notification message; When a triggering operation of an operation button corresponding to any third notification message is detected, the third notification message is processed based on the type of the operation button.
7. The method according to claim 6, It is characterized in that The processing of the third notification message based on the type of the operation button includes: When the type of the operation button is non-reply type, determining the source of the third notification message and the operating system running in the foreground; When the source of the third notification message is the electronic device, and the operating system running in the foreground is the second operating system, the trigger operation is forwarded to the first operating system, so that the first operating system forwards the trigger operation to the electronic device, and the electronic device executes the trigger operation; and / or, When the source of the third notification message is the wearable device and the operating system running in the foreground is the first operating system, the trigger operation is performed through the first operating system, or the trigger operation is forwarded to the second operating system, and the second operating system is switched to the foreground, so that the second operating system performs the trigger operation.
8. The method according to claim 6, It is characterized in that The processing of the third notification message based on the type of the operation button includes: When the type of the operation button is a reply type, switching the second operating system to the foreground to run, and generating a plurality of quick reply phrases through the second operating system; A notification reply interface is displayed, wherein the notification reply interface includes a quick reply list, and the quick reply list includes multiple quick reply words.
9. The method according to claim 1, It is characterized in that The method further comprises: When the state of a third notification message changes, determining the operating system running in the foreground, the third notification message being any notification message of the first notification message and the second notification message; Based on the operating system running in the foreground, the state of the third notification message is synchronized between the first operating system and the second operating system.
10. The method according to claim 9, It is characterized in that The operating system based on the foreground operation, synchronizing the state of the third notification message between the first operating system and the second operating system, includes: When the operating system running in the foreground is the second operating system, synchronizing the state of the third notification message to the first operating system; and / or, When the operating system running in the foreground is the first operating system, synchronization of the status of the first notification message is temporarily suspended; when the operating system running in the foreground is switched from the first operating system to the second operating system, synchronization of the status of the first notification message to the second operating system.
11. The method according to claim 1, It is characterized in that The method further comprises: When a deletion operation is detected in which any notification message is deleted, determining the operating system running in the foreground; When the operating system running in the foreground is the second operating system, based on the second operating system, performing a deletion operation on the notification message; and / or, When the operating system running in the foreground is the first operating system, determine the execution type of the deletion operation, where the execution type is used to indicate that the deletion operation needs to be executed in the foreground or in the background; and perform a deletion operation on the notification message based on the execution type.
12. A message notification device, It is characterized in that Deployed in a wearable device, the wearable device includes a first core controller and a second core controller, the first core controller is used to run a first operating system, the second core controller is used to run a second operating system, and the power consumption of the first core controller running the first operating system is lower than the power consumption of the second core controller running the second operating system; The device comprises: A first processing module is configured to process a first notification message from an electronic device connected to the wearable device based on a first processing strategy when the first operating system receives the first notification message from the electronic device connected to the wearable device; and / or The second processing module is used to process the second notification message based on a second processing strategy.
13. A wearable device, It is characterized in that The wearable device includes a first core controller, a second core controller and a memory, the first core controller is used to run a first operating system, the second core controller is used to run a second operating system, and the power consumption of the first core controller running the first operating system is lower than the power consumption of the second core controller running the second operating system; At least one program code is stored in the memory, and the at least one program code is loaded and executed by the first core controller and the second core controller to implement the message notification method according to any one of claims 1 to 11.
14. A computer-readable storage medium, It is characterized in that The storage medium stores at least one program code, and the at least one program code is loaded and executed by the processor to implement the message notification method according to any one of claims 1 to 11.
15. A computer program product, It is characterized in that The computer program product stores at least one program code, and the at least one program code is used to be executed by a processor to implement the message notification method according to any one of claims 1 to 11.
Citation Information
Cited By
Message notification method and apparatus, wearable device, storage medium, and product
WO2026032387A1
Message synchronization method and apparatus, and electronic device, storage medium and product
WO2026171163A1
