Message notification method and apparatus, wearable device, storage medium, and product

Abstract

The present application relates to the technical field of wearable devices, and provides a message notification method and apparatus, a wearable device, a storage medium, and a product. The wearable device comprises a first core controller and a second core controller, wherein the power consumption of the first core controller running a first operating system is lower than that of the second core controller running a second operating system. The method comprises: when a first operating system receives a first notification message from an electronic device, processing the first notification message on the basis of a first processing strategy; and when a second operating system receives a second notification message from a wearable device, processing the second notification message on the basis of a second processing strategy. In the present application, when different operating systems of a wearable device receive a notification message, the notification message is processed by means of different processing strategy information, thereby enabling notification message processing based on a dual-core dual-system configuration.

Description

Message notification method and device, wearable device, storage medium and product

[0001] The present application claims priority from the Chinese patent application No. 202411081692.7, filed on August 7, 2024, and entitled "Message notification method and device, wearable device, storage medium and product", the entire content of which is incorporated herein by reference. TECHNICAL FIELD

[0002] The present application relates to the technical field of wearable devices, and in particular to a message notification method and device, a wearable device, a storage medium and a product. BACKGROUND

[0003] The smartwatch operating system is originally developed for a single-core single-system smartwatch, and the biggest problem of the single-core single-system smartwatch is 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

[0004] The present application provides a message notification method and device, a wearable device, a storage medium and a product, which can reduce the power consumption of an electronic device. The technical solution is as follows:

[0005] In one aspect, a message notification method is provided, which is executed by a wearable device, the wearable device comprising a first core controller and a second core controller, the first core controller being configured to run a first operating system, the second core controller being configured to run a second operating system, and the power consumption of the first core controller running the first operating system being lower than the power consumption of the second core controller running the second operating system; the method comprising: when the first operating system receives a first notification message of an electronic device connected to the wearable device, processing the first notification message based on a first processing strategy; and when the second operating system receives a second notification message of the wearable device, processing the second notification message based on a second processing strategy.

[0006] In another aspect, a message notification synchronization method is provided, which is executed by a wearable device, the wearable device comprising a first core controller and a second core controller, the method comprising: dividing notification messages held by the first core controller into deleted notification messages, unchanged notification messages and changed notification messages. The method further comprises one or more of the following:

[0007] The first core controller sends a first protocol to inform the second core controller of the message identifier of the read notification message; the second core controller sends a second protocol to start the first stage synchronization; the first stage synchronization includes synchronization of unchanged notification messages and synchronization of the latest N notification messages; the first core controller sends a third protocol to inform the second core controller of the unchanged notification messages; the second core controller deletes all notification messages except the unchanged notification messages; the first core controller sends a fourth protocol to synchronize the notification messages of the type of picture in the latest N notification messages of the second core controller; the first core controller sends a fifth protocol to synchronize the notification messages of the type of text in the latest N notification messages of the second core controller; the first core controller sends a sixth protocol to inform the second core controller that the first stage synchronization is completed, and the sixth protocol carries a flag indicating whether the second stage synchronization is needed; the second core controller prepares a history notification interface; the second core controller sends a seventh protocol to start the second stage synchronization; the first core controller sends the fourth protocol to synchronize the notification messages of the type of picture in other newly added notification messages of the second core controller; the first core controller sends the fifth protocol to synchronize the notification messages of the type of text in other newly added notification messages of the second core controller; the first core controller sends the sixth protocol to inform the second core controller that the second stage synchronization is completed; and the second core controller perfects the notification messages.

[0008] In another aspect, a message notification device is provided, which is deployed in a wearable device including a first core controller and a second core controller, the first core controller is configured to run a first operating system, the second core controller is configured 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: a first processing module configured to process a first notification message of an electronic device connected to the wearable device based on a first processing strategy when the first operating system receives the first notification message; and a second processing module configured to process a second notification message of the wearable device based on a second processing strategy when the second operating system receives the second notification message.

[0009] In another aspect, a message notification synchronization device is provided, which is deployed in a wearable device including a first core controller and a second core controller. The device includes a division module configured to divide notification messages held by the first core controller into deleted notification messages, unchanged notification messages, and changed notification messages. The device further includes one or more of the following modules: a first sending module configured to send a first protocol by the first core controller to inform the second core controller of message identifiers of read notification messages; a second sending module configured to send a second protocol by the second core controller to start a first stage synchronization; the first stage synchronization includes unchanged notification message synchronization and latest N notification message synchronization; a third sending module configured to send a third protocol by the first core controller to inform the second core controller of the unchanged notification messages; a deletion module configured to delete, by the second core controller, all notification messages other than the unchanged notification messages; a fourth sending module configured to send a fourth protocol by the first core controller to synchronize notification messages of a picture type in the latest N notification messages of the second core controller; a fifth sending module configured to send a fifth protocol by the first core controller to synchronize notification messages of a text type in the latest N notification messages of the second core controller; a sixth sending module configured to send a sixth protocol by the first core controller to inform the second core controller that the first stage synchronization is completed, and the sixth protocol carries a flag indicating whether a second stage synchronization is needed; a preparation module configured to prepare, by the second core controller, a historical notification interface; a seventh sending module configured to send a seventh protocol by the second core controller to start the second stage synchronization; an eighth sending module configured to send the fourth protocol by the first core controller to synchronize notification messages of the picture type in other newly added notification messages of the second core controller; a ninth sending module configured to send the fifth protocol by the first core controller to synchronize notification messages of the text type in the other newly added notification messages of the second core controller; a tenth sending module configured to send the sixth protocol by the first core controller to inform the second core controller that the second stage synchronization is completed; and a perfecting module configured to perfect, by the second core controller, notification messages.

[0010] In another aspect, a wearable device is provided, which includes a first core controller, a second core controller, and a memory. The first core controller is configured to run a first operating system, the second core controller is configured to run a second operating system, and power consumption of the first core controller running the first operating system is lower than power consumption of the second core controller running the second operating system. The memory stores at least one piece of program code, which is loaded and executed by the first core controller and the second core controller to implement the message notification method according to any of the above implementation manners. In another aspect, a computer readable storage medium is provided, which stores at least one piece of program code, which is loaded and executed by a processor to implement the message notification method according to any of the above implementation manners. In another aspect, a computer program product is provided, which stores at least one piece of program code, which is configured to be executed by a processor to implement the message notification method according to any of the above implementation manners. BRIEF DESCRIPTION OF DRAWINGS

[0011] FIG. 1 shows a notification architecture diagram of a single-core single-system wearable device according to an example embodiment of the present application;

[0012] FIG. 2 shows a flowchart of a message notification method according to an example embodiment of the present application;

[0013] FIG. 3 shows a flowchart of a message notification method according to an example embodiment of the present application;

[0014] FIG. 4 shows a flowchart of a message notification method according to an example embodiment of the present application;

[0015] FIG. 5 shows a flowchart of a message notification method according to an example embodiment of the present application;

[0016] FIG. 6 shows a flowchart of a message notification method according to an example embodiment of the present application;

[0017] FIG. 7 shows a flowchart of a message notification method according to an example embodiment of the present application;

[0018] FIG. 8 shows a flowchart of a message notification method according to an example embodiment of the present application;

[0019] FIG. 9 shows a flowchart of a message notification method according to an example embodiment of the present application;

[0020] FIG. 10 shows a flowchart of a message notification method according to an example embodiment of the present application;

[0021] FIG. 11 shows a flowchart of a message notification synchronization method according to an example embodiment of the present application;

[0022] FIG. 12 shows a block diagram of a message notification device according to an example embodiment of the present application;

[0023] FIG. 13 shows a block diagram of a message notification synchronization device according to an example embodiment of the present application;

[0024] FIG. 14 shows a block diagram of a wearable device according to an example embodiment of the present application. DETAILED DESCRIPTION

[0025] For the purpose of making the purpose, technical solutions and advantages of the present application clearer, the embodiments of the present application will be described in further detail below with reference to the drawings. In the present text, “a plurality of” refers to two or more. “And / or” describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can mean that there are three cases of A alone, A and B together, and B alone. The character “ / ” generally represents an “or” relationship between the associated objects. 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 for analysis, stored data, displayed data, etc.) and signals involved in the present application are all authorized by the user or fully authorized by all parties, and the collection, use and processing of related data need to comply with relevant laws, regulations and standards of relevant countries and regions. For example, the notification messages and the like involved in the present application are obtained under sufficient authorization.

[0026] In the embodiments of the present application, the following technical solutions are provided: a message notification method is executed by 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 method includes: when the first operating system receives a first notification message of 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 a second notification message of the wearable device, processing the second notification message based on a second processing strategy.

[0027] In some embodiments, the processing of the first notification message based on the first processing strategy comprises: when the second operating system is in a hibernation state, storing the first notification message by the first core controller; when the second operating system switches to a running state, obtaining one or more batches of notification messages by batching the first notification messages stored by the first core controller; and synchronizing the one or more batches of notification messages to the second operating system in batches.

[0028] In some embodiments, the obtaining one or more batches of notification messages by batching the first notification messages stored by the first core controller comprises: based on the first notification messages stored by the first core controller and the second notification messages stored by the second core controller, dividing the first notification messages stored by 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, the third batch of notification messages comprising a first notification message set and / or a second notification message set, the first notification message set comprising a first preset number of recently added notification messages, and the second notification message set comprising other newly added notification messages except the first notification message set.

[0029] In some embodiments, the synchronizing the one or more batches of notification messages to the second operating system in batches comprises: synchronizing 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, synchronizing the first notification message set in the third batch of notification messages to the second operating system; and when the synchronization of the first notification message set is completed, synchronizing the second notification message set in the third batch of notification messages to the second operating system.

[0030] In some embodiments, the processing of the second notification message based on the second processing strategy comprises: when the second notification message is a full-screen type of notification message, determining a foreground running operating system; when the foreground running operating system is the first operating system, switching the foreground running operating system from the first operating system to the second operating system, displaying an application interface corresponding to the second notification message by the second operating system, and displaying the second notification message based on the application interface; and / or, when the foreground running operating system is the second operating system, directly displaying an application interface corresponding to the second notification message by the second operating system, and displaying the second notification message based on the application interface.

[0031] In some embodiments, the method further includes: displaying a notification details interface, the notification details interface displays at least one third notification message and an operation button corresponding to the third notification message, 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 any operation button corresponding to a third notification message is detected, processing the third notification message based on the type of the operation button.

[0032] In some embodiments, the processing the third notification message based on the type of the operation button includes: when the type of the operation button is a 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, forwarding the triggering operation to the first operating system, so that the first operating system forwards the triggering operation to the electronic device, and the electronic device executes the triggering 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, executing the triggering operation through the first operating system, or forwarding the triggering operation to the second operating system and switching the second operating system to run in the foreground, so that the second operating system executes the triggering operation.

[0033] In some embodiments, the processing 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 run in the foreground, and generating a plurality of shortcut reply phrases through the second operating system; displaying a notification reply interface, the notification reply interface includes a shortcut reply phrase list, and the shortcut reply phrase list includes a plurality of shortcut reply phrases.

[0034] In some embodiments, the method further includes: 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, synchronizing the state of the third notification message between the first operating system and the second operating system.

[0035] In some embodiments, the foreground running operating system synchronizes the state of the third notification message between the first operating system and the second operating system, including: when the foreground running operating system is the second operating system, synchronizing the state of the third notification message to the first operating system; and / or, when the foreground running operating system is the first operating system, suspending synchronization of the state of the first notification message; when the foreground running operating system is switched from the first operating system to the second operating system, synchronizing the state of the first notification message to the second operating system.

[0036] In some embodiments, the method further includes: when detecting a deletion operation of any notification message being deleted, determining a foreground running operating system; when the foreground running operating system is the second operating system, performing a deletion operation on the notification message based on the second operating system; and / or, when the foreground running operating system is the first operating system, determining an execution type of the deletion operation, the execution type indicating whether the deletion operation needs to be executed in the foreground or in the background; and performing a deletion operation on the notification message based on the execution type.

[0037] In some embodiments of the present application, by setting the first processing strategy and the 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, so that the single-core single-system is run on one of the dual-cores, and cooperates with the other core and the operating system running thereon, thereby being able to process the notification message based on the dual-core dual-system.

[0038] A message notification synchronization method is executed by a wearable device, the wearable device comprising a first core controller and a second core controller, the method comprising: dividing notification messages held by the first core controller into deleted notification messages, unchanged notification messages and changed notification messages. The method further comprises one or more of: the first core controller sending a first protocol informing the second core controller of message identifiers of read notification messages; the second core controller sending a second protocol to start first stage synchronization; the first stage synchronization comprising unchanged notification message synchronization and latest N notification message synchronization; the first core controller sending a third protocol informing the second core controller of the unchanged notification messages; the second core controller deleting all notification messages other than the unchanged notification messages; the first core controller sending a fourth protocol to synchronize image type notification messages in the second core controller's latest N notification messages; the first core controller sending a fifth protocol to synchronize text type notification messages in the second core controller's latest N notification messages; the first core controller sending a sixth protocol informing the second core controller that the first stage synchronization is complete, and the sixth protocol carrying a flag indicating whether second stage synchronization is required; the second core controller preparing a history notification interface; the second core controller sending a seventh protocol to start second stage synchronization; the first core controller sending the fourth protocol to synchronize image type notification messages in other newly added notification messages of the second core controller; the first core controller sending the fifth protocol to synchronize text type notification messages in other newly added notification messages of the second core controller; the first core controller sending the sixth protocol informing the second core controller that the second stage synchronization is complete; and the second core controller perfecting notification messages.

[0039] In some embodiments, the changed notification message includes the latest N notification messages and the other newly added notification messages; the N is 20. In some embodiments, the method includes first stage synchronization and / or second stage synchronization; the first stage synchronization includes synchronizing the latest N notification messages in the unchanged notification message and the changed notification message; the second stage synchronization includes synchronizing the other newly added notification messages in the changed notification message; the types of the latest N notification messages and the other newly added notification messages include picture notification messages and text notification messages. In some embodiments of the present application, the notification messages held by the first core controller are divided into deleted notification messages, unchanged notification messages and changed notification messages, and the deleted notification messages, the unchanged notification messages and the changed notification messages are batch-synchronized to the second core controller through different number protocols, so that when the second operating system is running in the foreground, the notification bar interface of the wearable device can display the synchronized notification messages in the first time, so that the operating system running in the foreground is not perceived by the user when switching, and the user experience is improved.

[0040] The wearable operating system in the related art is developed for single-core single-system wearable devices. In order to adapt to the dual-core hardware, the existing wearable operating system needs to be run on one of the dual cores and cooperates with the other core and the system running thereon. The present 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 shown in FIG. 1. Referring to FIG. 1, the notification architecture includes an electronic device and a wearable device, the wearable device includes a data center (WearServices) in a WearOS system and a system interface (SysUI) in the WearOS system, the WearServices is used to run the WearOS operating system, and the WearServices and the electronic device transmit notification messages through a wireless link (such as a Bluetooth communication link or a Wifi communication link). The WearServices and the SysUI transmit notification messages through a cross-process communication channel. For example, the notification message on the electronic device is forwarded to the WearServices in the wearable device through the wireless link, and then the WearServices forwards the notification message to the SysUI through the cross-process communication channel for display. In addition, the WearServices is also responsible for receiving the notification message on the wearable device, and forwarding the notification message to the SysUI through the cross-process communication channel for display. In some embodiments, the wearable device can be a smart watch or a smart bracelet, etc.; the electronic device can be a smart phone, a tablet computer or a vehicle terminal, etc.

[0041] 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 configured to run a first operating system, the second core controller is configured 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, 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 a (Real Time Operating System, RTOS), and the second operating system can be a Harmony operating system, an Android operating system, etc., such as WearOS; the first core controller can be a microcontroller unit (MCU). The second core controller can be a central processing unit (CPU).

[0042] In some embodiments, the first core controller and the second core controller can be two independently packaged chips, respectively; in other embodiments, the first core controller and the second core controller can be two different processing modules packaged in the same chip, and no limitation is made thereto.

[0043] In some embodiments, the first operating system can always be running, in some embodiments, the first operating system can be running or sleeping, for example, when there is no business to be executed, it can be sleeping, that is, it can be sleeping or running according to the demand. In some embodiments, the second operating system can also be sleeping or running according to the demand. And the running of the operating system (the first operating system or the second operating system) is divided into foreground running and background running. Which operating system is running in the foreground, the wearable device screen display, motor vibration, sound playing, user interaction and part or all of the operation authority of other peripherals are handed over to the operating system to process. In some embodiments, the operating system running in the foreground will at least have direct control of the screen display; in some embodiments, the operating system running in the foreground can also have direct control of other parts of the peripheral; of course, in some embodiments, some peripherals are fixedly connected with a certain operating system, that is, directly controlled by the operating system, and the other operating system needs to borrow the operating system with direct control to control. In some embodiments, some peripherals can switch the direct control between the two operating systems. In some embodiments, the peripherals can be mounted on a certain system (also can be understood as being connected with the core controller running the system), that is, the direct control of the peripherals is owned by one system. Of course, the above embodiments can be combined with each other without conflict, and exist at the same time. In order to reduce the power consumption of the wearable device, in some embodiments, the first operating system can be running in the foreground as much as possible, and the second operating system can be in a sleep state. Only when the ability of the second operating system is needed, the second operating system will be woken up, and the second operating system will be running in the background. Only when it is needed (such as opening a third-party application), the second operating system will be switched to foreground running, and the first operating system will be switched to background running. Therefore, in order to receive the notification message of the electronic device synchronized to the wearable device when the first operating system is running in the foreground and the second operating system is in a sleep 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 foreground running, to update the notification interface of the second operating system. Or, the first operating system synchronizes the notification message to the second operating system when the second operating system is running in the background (for example, in a background wake-up state), to update the notification interface of the second operating system.

[0044] It can be understood that the notification message can be generated by the electronic device end which can wirelessly communicate with the wearable device and sent to the wearable device through the wireless link, for example, the 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.

[0045] In some embodiments, the notification message is generated by the application of a certain operating system of the wearable device, if the application of the first operating system generates the notification message (for example, the notification message can be the fifth notification message), the first operating system can receive the 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 is synchronized to the first operating system, if the second operating system is running in the background when the notification message is received, 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, the application thereof generates a notification message (for example, the notification message can be the second notification message), which can be synchronized to the first operating system by the second operating system, the first operating system prompts the notification message in the foreground (the prompt can be a prompt supported by the resources of the first operating system, for example, a simple text notification), and when the notification message is triggered, 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 can 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 can enter the sleep state, thereby saving 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 process the notification message.

[0046] In some embodiments, the second operating system can be woken up to synchronize the notification message to the second operating system regardless of whether the second operating system is in the foreground or the background, as long as the synchronization condition is met. For example, when the notification message transmitted by the electronic device wirelessly connected with 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 needed to execute, the second operating system can be woken up to synchronize the notification message to the second operating system, and the notification message is prompted 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.

[0047] In some embodiments, according to the type of the received notification message (for example, the notification message can 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, the notification message prompt can be performed on the first operating system first. When the triggering instruction of the user is received, 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 and facilitates processing of the business corresponding to the notification message.

[0048] Please refer to FIG. 2, which shows a flowchart of a message notification method according to an example embodiment of the present application. The execution subject in the embodiment of the present application can be a wearable device, which 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. The power consumption of the first core processor running the first operating system is lower than the power consumption of the second core operating system running the second operating system, which can be reflected in one or more of the following aspects: in the case of not performing any business operation on the first system or the second system, the power consumption of the first system is lower than that of the second system. For example, in the case of not performing any business operation, the first system and the second system can be in a sleep state or in 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 processing performance of the first system being 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. Referring to FIG. 2, the method includes:

[0049] Step 201: When the first operating system receives a first notification message of an electronic device connected to the wearable device, the first notification message is processed based on a first processing strategy.

[0050] The first notification message is a notification message of an application included in the electronic device. In the case where the electronic device is a mobile phone, the first notification message can be referred to as 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 a first processing strategy. The first processing strategy can include a first synchronization strategy. Correspondingly, this step can be: when the first operating system receives the first notification message of the electronic device connected with 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, in the case where the second core controller includes WearServices and SysUI, the first core controller synchronizes the first notification message to the WearService based on the synchronization strategy, and the WearService synchronizes the first notification message to the SysUI for display through a cross-process communication channel. In other embodiments, the first strategy processing can also include a first display strategy. Correspondingly, this step can 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.

[0051] Step 202: When the second operating system receives the second notification message of the wearable device, process the second notification message based on a second processing strategy.

[0052] The second notification message is a notification message of an application included in the wearable device. In the case where the wearable device is a watch, the second notification message can be referred to as 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 a second processing strategy. In some embodiments, the second strategy processing information can include a second synchronization strategy. Correspondingly, this step can 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 can also include a second display strategy. Correspondingly, this step can 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.

[0053] In some embodiments of the present application, the notification messages (including the first notification message and the second notification message) 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.

[0054] In some embodiments of the present application, 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, so that the notification message can be processed based on the dual-core dual-system.

[0055] For example, the operating system receiving the notification message can determine the operating system processing the notification message according to the type of the received notification message, and if the operating system processing the notification message is in a sleep state, the operating system processing the notification message is woken up to synchronize the notification message, and the processing of the notification message (such as display and response to user touch) is implemented by switching the operating system processing the notification message to the foreground.

[0056] Please refer to FIG. 3, which shows a flowchart of a message notification method according to an example embodiment of the present application. The execution subject in the embodiment of the present application can be a wearable device, which 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. Referring to FIG. 3, the method includes:

[0057] Step 301: The wearable device receives a first notification message of an electronic device through the first operating system.

[0058] In some embodiments, when the wearable device is in a powered-on state, the first operating system is always in a running state (in some embodiments, the first operating system can also be in a sleep state when there is no business demand; the first operating system is woken up when there is business); and no matter whether the first operating system is in foreground running or background running, the first notification message of the electronic device is sent to the first operating system, and the first notification message of the electronic device sent by the electronic device is received by the first operating system. In other embodiments, when the wearable device is in a powered-on state, the first operating system is always in a running state (in some embodiments, the first operating system can also be in a sleep state when there is no business demand; the first operating system is woken up when there is business); and the first notification message of the electronic device is sent to the operating system in foreground running; accordingly, this step can be: when the first operating system is in foreground running, the first notification message of the electronic device is sent to the first operating system, and the first notification message of the electronic device sent by the electronic device is received by the first operating system; when the second operating system is in foreground running, the first notification message of the electronic device is sent to the second operating system, and the first notification message of the electronic device sent by the electronic device is received by the second operating system.

[0059] In some embodiments, when the wearable device is in the powered-on state, the first operating system is always in the running state (in some embodiments, the first operating system can also be in the sleep state when there is no business demand; the first operating system is woken up 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 sleep state, the first notification message of the electronic device is sent to the first operating system; accordingly, the 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; and when the second operating system is in the sleep 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.

[0060] Step 302: When the second operating system is in the sleep state, the wearable device stores the first notification message through the first core controller.

[0061] In an 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 by the first core controller, which can be a storage space inside or outside the first core controller.

[0062] When the first operating system receives the first notification message, the first core controller determines whether the second operating system is in the sleep state; when the second operating system is not in the sleep state (i.e., the second operating system is in the 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 state, 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 state, the first core controller synchronizes the first notification message to the second operating system. And 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.

[0063] When the second operating system is in the sleep state, the first core controller stores the first notification message, and waits until the second operating system switches to the running state, and then synchronizes the first notification message to the second operating system.

[0064] Step 303: When the second operating system switches to the running state, the wearable device batches the plurality of first notification messages stored by the first core controller to obtain one or more batches of notification messages.

[0065] Since the native interface between WearService and SysUI included in the second controller can not support batch adding or deleting notification messages, when the first core controller receives a large number of first notification messages and then the second operating system switches to a running state, a large amount of synchronized notification message data is triggered at this time; when the user pulls out the notification bar interface of SysUI, a notification message is added one by one, which leads to a poor user experience; therefore, in some embodiments of the present application, the synchronization mechanism of the notification message is optimized, and the plurality of first notification messages are synchronized in batches, thereby improving the user experience. Correspondingly, the step of the wearable device dividing the plurality of first notification messages stored by the first core controller into one or more batches of notification messages according to the plurality of first notification messages stored by the first core controller and the second notification messages stored by the second core controller can be:

[0066] The wearable device divides the plurality of first notification messages stored by 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 plurality of first notification messages stored by the first core controller and the second notification messages stored by 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 newly added notification messages, and the second notification message set includes other newly added notification messages except the first notification message set.

[0067] In an example, the wearable device stores the second notification message through the second core controller can be understood as storing the second notification message in a storage space accessible by the second core controller, which can be an internal storage space of the second core controller or an external storage space of the second core controller.

[0068] The read notification message refers to the notification message read when the first operating system is in the foreground; the unchanged notification message refers to the notification message displayed in the notification bar interface when the first operating system is in the foreground; the newly added notification message refers to the notification message received by the first operating system when the first operating system is in the foreground, and / or the notification message received by the first operating system when the first operating system is in the background.

[0069] 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 messages stored in the first core controller are frozen (at this time, the notification messages are not stored in the first core controller, and the stored messages in the first core controller are not deleted), and the notification messages stored in the second core controller are frozen (at this time, the notification messages are not stored in the second core controller, and the stored messages in the second core controller are not deleted), so as to determine the first notification messages stored in the first core controller and the second notification messages stored in the second core controller. Moreover, the notification messages are divided into two types, one is the first notification message (also referred to as a remote notification message) from the electronic device, and the other is the second notification message (also referred to as a local notification message) from the wearable device; when determining the synchronization messages that need to be synchronized to the second operating system, the first operating system distinguishes whether the notification message is a local notification message or a remote notification message. Since the local notification message can be synchronized to the first operating system by the second operating system, the local notification message does not need to be synchronized to the second operating system, and only the remote notification message needs to be synchronized to the second operating system in this step, 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, the first operating system synchronizes the local notification message to the electronic device when running in the background; and / or the first operating system synchronizes the local notification message to the electronic device when running in the foreground.

[0070] In other embodiments, the first operating system can also receive the notification message of the wearable device; for the convenience of distinction, the notification message of the wearable device received by the first operating system is referred to as a fifth notification message, and when the second operating system receives the fifth notification message of 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 divides the fifth notification message and the plurality of first notification messages into one or more batches of notification messages, and then performs step 304.

[0071] Step 304: The wearable device synchronizes one or more batches of notification messages to the second operating system.

[0072] This step can be implemented by at least one of steps (1) to (3) below, comprising:

[0073] (1) The wearable device synchronizes the message identifiers of the first batch of notification messages to the second operating system.

[0074] Referring to FIG. 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 hibernation state to the background running state, the first core controller synchronizes the message identifiers of the read notification messages (the message identifiers 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 identifiers of the read notification messages, and the unread icon is used to represent the number of unread notification messages; when the number of unread notification messages is 0, the unread icon of the application is deleted. Wherein, the first core controller informs the second operating system of the message identifiers of the read notification messages through the first protocol. In some embodiments of the present application, because the synchronization of the message identifiers of the read notification messages is performed in the operating system switching stage, the state of the notification message can be accurately displayed after the operating system is switched.

[0075] (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.

[0076] Please continue to refer to FIG. 4, the first notification message set in the second batch of notification messages and the third batch of notification messages is synchronized in the first stage, and the notification message synchronized in the first stage is the notification message displayed on the first 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 second protocol and sends the third protocol to the second core controller, and the third 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, so as to prevent the problem of inaccurate display of notification messages due to inconsistency of notification messages between the first operating system and the second operating system.

[0077] (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.

[0078] The first notification message set includes a notification message of a picture type and a notification message of a text type; in this step, the first core controller synchronizes the notification message of the picture type to the second core controller first, and then synchronizes the notification message of the text type to the second core controller. For example, please continue to refer to FIG. 4, the first core controller sends a fourth protocol to the second core controller, the fourth protocol carries the notification message of the picture type included in the first notification message set, and then sends a fifth protocol to the second core controller, the fifth protocol carries the notification message of the text type included in the first notification message set.

[0079] Please continue to refer to FIG. 4, when the first notification message set synchronization is completed, the first core controller sends a sixth protocol to the second core controller to inform the second core controller that the first stage synchronization is completed, and carries a flag indicating whether the second stage synchronization is needed. When the second stage synchronization is needed, the second core controller prepares a history notification interface of the notification bar interface, and then sends a seventh protocol to the first core controller to start the second stage synchronization. The second notification message set also includes a notification message of a picture type and a notification message of a text type; the first core controller synchronizes the notification message of the picture type to the second core controller first, and then synchronizes the notification message of the text type to the second core controller. Correspondingly, the first core controller sends a fourth protocol to the second core controller, the fourth protocol carries the notification message of the picture type included in the second notification message set, and then sends a fifth protocol to the second core controller, the fifth protocol carries the notification message of the text type included in the second notification message set, and then sends a sixth protocol to the second core controller to inform that the second stage synchronization is completed; after receiving the sixth protocol, the second core controller perfects the notification message.

[0080] In some embodiments, step 304 can be implemented through one or more of steps (1) to (3) above; and when step 304 is implemented through multiple steps of (1) to (3) above, the execution order of the multiple steps can be adjusted as needed; for example, step 304 can be implemented through steps (1) to (3) below, and the execution order of (1) to (3) can be (1)-(2)-(3), or (1)-(3)-(2), or (2)-(1)-(3), or (2)-(3)-(1), or (3)-(2)-(1), or (3)-(1)-(2), and in some embodiments of the present application, the execution order of (1) to (3) is not specifically limited.

[0081] In some embodiments of the present application, by optimizing the synchronization mechanism of the notification message, the plurality of first notification messages are synchronized in batches, the message identifiers of the read notification messages are synchronized preferentially, so that the second operating system after switching can accurately display the number of unread messages on the icon of the application; then the unchanged notification messages and the recently added notification messages are synchronized again, so that the notification messages displayed in the notification bar interface can be synchronized in the first time, so that the foreground running operating system is not perceived by the user when switching, and the user experience is improved.

[0082] Please refer to FIG. 5, which shows a flowchart of a message notification method according to an exemplary embodiment of the present application. The execution subject in the embodiment of the present application can be a wearable device, which 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 that of the second core controller running the second operating system. Referring to FIG. 5, the method includes:

[0083] Step 501: The wearable device receives a second notification message of the wearable device through the second operating system.

[0084] The second notification message is a notification message of an application included in the wearable device. After the second core controller (specifically, the WearService in the second core controller) receives the second notification message, the type of the second notification message is determined. When the second notification message is a full-screen type notification message, step 502 is performed. When the second notification message is a non-full-screen type notification message, the second notification message is synchronized to the first operating system. In some embodiments, the full-screen type notification message refers to a notification message that needs to open the corresponding application interface for display. For example, the notification message of a voice call is a full-screen type notification message. Since the full-screen type notification message can only be configured by the application on the wearable device, the full-screen type notification message is always sent to the second core controller, and then synchronized to the first core controller by the second core controller.

[0085] Step 502: When the second notification message is a full-screen type notification message, the wearable device determines the foreground running operating system.

[0086] When the foreground running operating system is the first operating system, step 503 is performed. When the foreground running operating system is the second operating system, step 504 is performed.

[0087] Step 503: When the currently running operating system is the first operating system, the wearable device switches the foreground running operating system 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.

[0088] Step 504: When the currently running operating system 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.

[0089] 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 still support full-screen notification messages after the operating system is fused with the dual-core hybrid technology.

[0090] Please refer to FIG. 6, which shows a flowchart of a message notification method according to an example embodiment of the present application. The execution subject in the embodiment of the present application can be a wearable device, which 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. Referring to FIG. 6, the method includes the following steps:

[0091] Step 601: The wearable device displays a notification detail interface. The notification detail interface displays at least one third notification message and an operation button corresponding to the third notification message. The at least one third notification message includes at least one of the first notification message and the second notification message.

[0092] The third notification message carries Action or ContentIntent. The operation button corresponding to the third notification message carrying Action includes a reply type button and a non-reply type button. The operation button corresponding to the third notification message carrying ContentIntent includes a non-reply type button. The reply type button can reply based on the third notification message, and the non-reply type button is “open on xxx”. When the user clicks the non-reply type 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 type button, the wearable device can reply to the third notification message.

[0093] Step 602: When a triggering operation of any operation button corresponding to the third notification message is detected, the wearable device determines the type of the operation button.

[0094] The type of the operation button includes a reply type and a non-reply type; in some embodiments, after the wearable device determines the type of the operation button, the wearable device processes the third notification message based on the type of the operation button through steps 603-607.

[0095] Step 603: when the type of the operation button is the non-reply type, the wearable device determines the source of the third notification message and the foreground running operating system.

[0096] The source of the third notification message is the electronic device or the wearable device.

[0097] Step 604: when the source of the third notification message is the electronic device and the foreground running operating system 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.

[0098] When the source of the third notification message is the electronic device and the foreground running operating system 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 executes the trigger operation. In the case that the third notification message is the first notification message, the trigger operation can be invokeRemoteNotificationAction. In the case that the third notification message is the second notification message, the trigger operation is onInvokedLocalNotificationAction. When the source of the third notification message is the electronic device and the foreground running operating system is the first operating system, the first operating system forwards the trigger operation to the electronic device, and the electronic device executes the trigger operation.

[0099] Step 605: when the source of the third notification message is the wearable device and the foreground running operating system is the first operating system, the wearable device forwards the trigger operation to the second operating system and switches the second operating system to foreground running, so that the second operating system executes the trigger operation.

[0100] In some embodiments, when the first operating system is more powerful, the trigger operation can also be executed through the first operating system; accordingly, step 605 can be replaced by: when the source of the third notification message is the wearable device and the foreground running operating system is the first operating system, the wearable device executes the trigger operation through the first operating system. In other embodiments, when the source of the third notification message is the wearable device and the foreground running operating system is the second operating system, the wearable device directly executes the trigger operation through the second operating system.

[0101] Step 606: When the type of the operation button is the reply type, the wearable device switches the second operation system to the foreground, and generates a plurality of shortcut reply sentences through the second operation system.

[0102] In some embodiments, when the type of the operation button is the reply type, the wearable device can also generate a plurality of shortcut reply sentences through the first operation system; accordingly, step 606 can be replaced by: when the type of the operation button is the reply type, the wearable device generates a plurality of shortcut reply sentences through the first operation system.

[0103] Step 607: The wearable device displays a notification reply interface, and the notification reply interface includes a shortcut reply sentence list, and the shortcut reply sentence list includes a plurality of shortcut reply sentences.

[0104] In some embodiments of the present application, through the cooperation of the first core controller and the second core controller, the wearable device can still support intelligent reply sentences after the operating system of the wearable device is fused with the dual-core hybrid technology.

[0105] Please refer to FIG. 7, which shows a flowchart of a message notification method according to an example 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 operation system, and the second core controller is used to run a second operation system. The power consumption of the first core controller running the first operation system is lower than the power consumption of the second core controller running the second operation system. Referring to FIG. 7, the method includes:

[0106] Step 701: When the state of a third notification message changes, the wearable device determines the operating system running in the foreground, and the third notification message is any notification message in the first notification message and the second notification message.

[0107] The first core controller and the second core controller not only need to synchronize whether there is an unread notification message, but also need to accurately synchronize whether the state of each notification message is read or unread, so that the present application can support displaying the number of unread notification messages. Therefore, when the state of the third notification message changes, that is, the state of the third notification message is modified from unread to read, the wearable device determines the operating system running in the foreground, and then synchronizes the state of the third notification message between the first operation system and the second operation system based on the operating system running in the foreground through steps 702-703.

[0108] Step 702: When the operating system running in the foreground is the second operation system, the wearable device synchronizes the state of the third notification message to the first operation system.

[0109] In step 703, when the operating system running in the foreground is the first operating system, the wearable device suspends synchronizing the state of the first notification message; and when the operating system running in the foreground is switched from the first operating system to the second operating system, the wearable device synchronizes the state of the first notification message to the second operating system.

[0110] In some embodiments, the state of the first notification message can also be synchronized when the second operating system is in the background running state; correspondingly, step 703 can be replaced by: when the operating system running in the foreground is the first operating system and the second operating system is in the hibernation state, the wearable device suspends synchronizing the state of the first notification message; and when the second operating system is switched from the hibernation state to the background running state, the wearable device synchronizes the state of the first notification message to the second operating system.

[0111] In some embodiments of the present application, the second core controller synchronizes the state of the first notification message to the first core controller, thereby ensuring that the wearable device can accurately display the state of the notification message no matter whether the operating system running in the foreground is the first operating system or the second operating system, and improving the accuracy of the state synchronization of the notification message.

[0112] Please refer to FIG. 8, which shows a flowchart of a message notification method according to an example embodiment of the present application. The execution subject in the embodiment of the present application can be a wearable device, which 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 that of the second core controller running the second operating system. Referring to FIG. 8, the method includes:

[0113] In step 801, when the wearable device is powered off, the wearable device stores a fourth notification message into a database through the second operating system, the fourth notification message being a notification message that has not been processed before the wearable device is powered off.

[0114] In some embodiments, the storage space of the second core controller is larger than that of the first core controller; therefore, the second core controller stores the fourth notification message currently held into the database for persistent storage when the wearable device is powered off. In other embodiments, the first core controller and the second core controller can share the storage space; then the third notification message can also be stored through the first core controller; accordingly, step 801 can be that when the wearable device is powered off, the wearable device stores the fourth notification message into the database (the 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 the storage space, and before the wearable device is powered off, whichever operating system is in the running state, the operating system performs 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 powered off, the wearable device stores the fourth notification message into the database (the 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 powered off, the wearable device stores the fourth notification message into the database (the database in the shared storage space) through the second operating system. When both operating systems are in the running state, whichever operating system is in the foreground running, the operating system performs the storage step of the fourth notification message; accordingly, step 801 can be replaced by: when the first operating system is in the foreground running before the wearable device is powered off, the wearable device stores the fourth notification message into the database through the first operating system; and / or, when the second operating system is in the foreground running before the wearable device is powered off, the wearable device stores the fourth notification message into the database through the second operating system.

[0115] Step 802: When the wearable device is powered on, the wearable device synchronizes the stored fourth notification message to the first operating system through the second operating system.

[0116] In some embodiments, the synchronization of the fourth notification message is performed through the first operating system; accordingly, step 802 can be replaced by: when the wearable device is powered 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 the storage space, and when the wearable device is powered on, the first operating system and the second operating system can not perform the synchronization of the fourth notification message, and whichever operating system needs to use the fourth notification message can directly obtain the fourth notification message from the shared storage space.

[0117] In some embodiments of the present application, when the wearable device is powered on, the second core controller can recover the fourth notification message from the database, while the first core controller loses all notification messages; therefore, when the wearable device is powered on, the first core controller requests 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.

[0118] Please refer to FIG. 9, which shows a flow chart of a message notification method according to an exemplary embodiment of the present application. The execution subject in the embodiment of the present application can be a wearable device, which 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. Referring to FIG. 9, the method includes:

[0119] Step 901: When the number of notification messages stored by the first core controller exceeds a second preset number, the wearable device deletes a first target notification message with the storage time farthest from the current time based on the storage time of each notification message.

[0120] In the case that the first target notification message to be deleted is a first notification message (a mobile phone notification), the second core controller sends a third deletion instruction to the first core controller, the third deletion instruction being used to notify the first core controller to delete the first target notification message, and the third deletion instruction can be dismissRemoteNotifications. In the case that the first target notification message to be deleted is a second notification message (a watch notification), the second core controller sends a fourth deletion instruction to the first core controller, the fourth deletion instruction being used to notify the first core controller to delete the first target notification message, and the fourth deletion instruction can be deleteLocalNotifications.

[0121] Step 902: The wearable device notifies the second operating system to synchronize and delete the first target notification message.

[0122] In some embodiments, the notification messages stored by the second core controller can also exceed the threshold and need to be deleted; accordingly, steps 901-902 can be replaced by: when the number of notification messages stored by the second core controller exceeds a third preset number, the wearable device deletes a second target notification message with the storage time farthest from the current time based on the storage time of each notification message, and notifies the first operating system to synchronize and delete the second target notification message.

[0123] In some embodiments of the present application, the first core controller has limited storage space, and thus can store a limited number of notification messages (e.g., up to 200). Due to the development of the WearOS system, the number of notification messages stored by the second core controller is uncontrollable; therefore, to ensure the consistency of the notification messages of the first core controller and the second core controller, when the first core controller deletes a notification message due to exceeding the number, the second core controller is immediately notified to synchronously delete, so as to ensure that the notification messages of the first core controller and the second core controller are always consistent.

[0124] Please refer to FIG. 10, which shows a flowchart of a message notification method according to an exemplary embodiment of the present application. The execution subject in some embodiments of the present application is a wearable device, which 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 that of the second core controller running the second operating system. Referring to FIG. 10, the method includes:

[0125] Step 1001: When detecting a deletion operation of deleting any notification message, the wearable device determines the operating system running in the foreground.

[0126] Step 1002: When the operating system running in the foreground is the second operating system, the wearable device performs the deletion operation on the notification message based on the second operating system.

[0127] In the case that the notification message to be deleted is a first notification message (a 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 can be onDeletedRemoteNotification. In the case that the notification message to be deleted is a second notification message (a 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 can be onDismisseNotifications.

[0128] In some embodiments, when the operating system running in the foreground is the first operating system, the wearable device performs the deletion operation on the notification message based on the first operating system. In other embodiments, when the operating system running in the foreground is the first operating system, the deletion operation is performed on the notification message based on the type of the execution of the deletion operation; accordingly, after step 1002 is performed, step 1003 is performed.

[0129] Step 1003: When the currently running operating system is the first operating system, the wearable device determines an execution type of the deletion operation, the execution type indicating whether the deletion operation needs to be executed in the foreground or in the background.

[0130] The deletion operation executed in the background can be deleting a broadcast message or deleting a started service, etc. The deletion operation executed in the foreground can be opening an application interface to perform the deletion operation. After determining the execution type of the deletion operation, the wearable device performs the deletion operation on the notification message based on the execution type through steps 1004 and 1005.

[0131] Step 1004: When the execution type is the 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 the deletion operation on the notification message based on the second operating system.

[0132] Step 1005: When the execution type is the background execution, the wearable device performs the deletion operation on the notification message in the background through the second operating system.

[0133] In some embodiments, when the execution type is the background execution, the wearable device can also perform the deletion operation on the notification message in the background through the first operating system.

[0134] 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 cooperates with the other core and the operating system running thereon, thereby supporting the deletion operation.

[0135] Please refer to FIG. 11, which shows a flowchart of a message notification synchronization method according to an example embodiment of the present application. The execution subject in some embodiments of the present application is a wearable device, which includes a first core controller and a second core controller. As shown in FIG. 11, the method includes:

[0136] Step 1101: The first core controller divides the notification messages held by the first core controller into deleted notification messages, unchanged notification messages and changed notification messages.

[0137] When the first operating system acquires the first notification message and the second operating system is in the sleep state, the wearable device stores the first notification message through the first core controller; correspondingly, the notification message held by the first core controller includes a plurality of first notification messages. In addition, the application of the first operating system can also generate a fifth notification message, when the first operating system acquires the fifth notification message and the second operating system is in the sleep state, the wearable device stores the fifth notification message through the first core controller; correspondingly, the notification message held by the first core controller also includes the fifth notification message. The deleted notification message refers to the notification message deleted when the first operating system is in the foreground running; the unchanged notification message refers to the notification message displayed in the notification bar interface all the time when the first operating system is in the foreground running; the changed notification message refers to the changed notification message when the first operating system is in the foreground running; the changed notification message includes the latest N notification messages and other newly added notification messages; N is 20. The other newly added notification message includes the notification message received by the first operating system when the first operating system is in the foreground running, and / or the notification message received by the first operating system when the first operating system is in the background running. The other newly added notification message also includes the changed notification message of the first operating system when the first operating system is in the foreground running, and / or the changed notification message of the first operating system when the first operating system is in the background running. The step of the first core controller dividing the notification message held by the first core controller into the deleted notification message, the unchanged notification message and the changed notification message can be: the first core controller freezes the notification message held by the first core controller (at this time, no notification message is stored in the first core controller, and no notification message stored in the first core controller is deleted) and freezes the notification message held by the second core controller (at this time, no notification message is stored in the second core controller, and no notification message stored in the second core controller is deleted), compares the notification message held by the first core controller with the notification message held by the second core controller, and determines the deleted notification message, the unchanged notification message and the changed notification message. For example, the notification message held by the first core controller includes notification message 1, notification message 2 and notification message 3, the notification message held by the second core controller includes notification message 2, notification message 3, notification message 4 and notification message 5; by comparing the notification message held by the first core controller with the notification message held by the second core controller, it is obtained that the deleted notification message includes notification message 1, the unchanged notification message includes notification message 2 and notification message 3, and the changed notification message includes notification message 4 and notification message 5.

[0138] In some embodiments, after step 1101 is performed, one or more of steps 1102-1114 can be performed.

[0139] Step 1102: The first core controller sends a first protocol to inform the second core controller of the message identifier of the read notification message.

[0140] 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 to the second core controller through the first protocol; for example, when the first operating system is in the foreground running state and the state of the notification message stored in the first core controller is modified from unread to read, the notification message is recorded as read; when the second operating system is switched to the foreground running state, the first core controller sends the first protocol to the second core controller, and the first protocol carries the message identifier of the read notification message. In the embodiment of the present application, when the first operating system is in the foreground running state and the unread state of the notification message stored in the first core controller changes, the second operating system is not immediately synchronized, but is synchronized when the second operating system is switched to the foreground running state, thereby reducing the power consumption of the wearable device.

[0141] Step 1103: The second core controller sends a second protocol to start the first stage synchronization; the first stage synchronization includes synchronization of the unchanged notification message and the latest N notification messages.

[0142] The method includes first stage synchronization and / or second stage synchronization; the first stage synchronization includes synchronization of the unchanged notification message and the latest N notification messages in the changed notification message; the second stage synchronization includes synchronization of other newly added notification messages in the changed notification message; the types of the latest N notification messages and the other newly added notification messages include picture notification messages and text notification messages.

[0143] Step 1104: The first core controller sends a third protocol to inform the second core controller of the unchanged notification message.

[0144] The first core controller sends a third protocol to the second core controller, and the third protocol carries the unchanged notification message or the message identifier of the unchanged notification message.

[0145] Step 1105: The second core controller deletes all notification messages except the unchanged notification message.

[0146] The second core controller receives the third protocol, deletes all notification messages except the unchanged notification message based on the unchanged notification message, or deletes all notification messages except the unchanged notification message based on the message identifier of the unchanged notification message.

[0147] Step 1106: The first core controller sends a fourth protocol to synchronize the type of the picture notification message in the latest N notification messages of the second core controller.

[0148] The latest N notification messages include notification messages of the picture type and notification messages of the text type; in this step, the first core controller synchronizes the notification messages of the picture type to the second core controller, and then synchronizes the notification messages of the text type to the second core controller. Correspondingly, the first core controller sends a fourth protocol to the second core controller, and the fourth protocol carries the notification messages of the picture type in the latest N notification messages.

[0149] Step 1107: The first core controller sends a fifth protocol to synchronize the notification messages of the text type in the latest N notification messages of the second core controller.

[0150] The first core controller sends a fifth protocol to the second core controller, and the fifth protocol carries the notification messages of the text type in the latest N notification messages.

[0151] Step 1108: The first core controller sends a sixth protocol to inform the second core controller that the first stage synchronization is completed, and the sixth protocol carries a flag indicating whether the second stage synchronization is needed.

[0152] When the first stage synchronization is completed, the first core controller sends a sixth protocol to the second core controller to inform the second core controller that the first stage synchronization is completed, and carries a flag indicating whether the second stage synchronization is needed. When the second stage synchronization is needed, the second core controller performs step 1109.

[0153] Step 1109: The second core controller prepares a history notification interface.

[0154] The second core controller prepares a history notification interface of the notification bar interface.

[0155] Step 1110: The second core controller sends a seventh protocol to start the second stage synchronization.

[0156] The second core controller sends a seventh protocol to the first core controller to start the second stage synchronization after preparing the history notification interface.

[0157] Step 1111: The first core controller sends a fourth protocol to synchronize the notification messages of the picture type in other newly added notification messages of the second core controller.

[0158] The other newly added notification messages include notification messages of the picture type and notification messages of the text type; the first core controller synchronizes the notification messages of the picture type to the second core controller first, and then synchronizes the notification messages of the text type to the second core controller. Correspondingly, the first core controller sends a fourth protocol to the second core controller, and the fourth protocol carries the notification messages of the picture type included in the other newly added notification messages, and then performs step 1112.

[0159] Step 1112: The first core controller sends the fifth protocol to synchronize the second core controller with the notification message of the type of literal in the other newly added notification message.

[0160] The first core controller sends the fifth protocol to the second core controller, and the fifth protocol carries the notification message of the type of literal included in the other newly added notification message.

[0161] Step 1113: The first core controller sends the sixth protocol to inform the second core controller that the second stage synchronization is completed.

[0162] After the first core controller sends the fifth protocol to the second core controller, it means that the second stage synchronization is completed, at this time, the first core controller sends the sixth protocol to the second core controller to inform that the second stage synchronization is completed; after the second core controller receives the sixth protocol, it executes step 1114 based on the sixth protocol.

[0163] Step 1114: The second core controller perfects the notification message.

[0164] In some embodiments of the present application, the notification message held by the first core controller is divided into deleted notification message, unchanged notification message and changed notification message, and the deleted notification message, unchanged notification message and changed notification message are synchronized to the second core controller in batches through different number protocols, so that when the second operating system is running in the foreground, the notification bar interface of the wearable device can display the synchronized notification message in the first time, so that the operating system running in the foreground is not perceived by the user when switching, and the user experience is improved.

[0165] Referring to FIG. 12, a block diagram of a message notification device is shown according to an example embodiment of the present application. The device is deployed in a wearable device, which includes a first core controller and a second core controller. The first core controller is configured to run a first operating system, and the second core controller is configured 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. The device includes: a first processing module 1201 configured to process a first notification message of an electronic device connected to the wearable device based on a first processing strategy when the first notification message is received by the first operating system; and / or a second processing module 1202 configured to process a second notification message of the wearable device based on a second processing strategy when the second notification message is received by the second operating system. In some embodiments, the first processing module 1201 is configured to store the first notification message by the first core controller when the second operating system is in a sleep state; when the second operating system is switched to a running state, batch a plurality of first notification messages stored by the first core controller to obtain one or more batches of notification messages; and synchronize the one or more batches of notification messages to the second operating system. In some embodiments, the first processing module 1201 is configured to divide the plurality of first notification messages stored by 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 plurality of first notification messages stored by the first core controller and the second notification messages stored by 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 new notification messages, and 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 newly added notification messages, and the second notification message set includes other newly added notification messages except the first notification message set. In some embodiments, the first processing module 1201 is configured to synchronize 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; and synchronize the second 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.In some embodiments, the apparatus further includes: a first determining module configured to determine the foreground running operating system when the second notification message is a full screen type notification message; a third processing module configured to switch the foreground running operating system from the first operating system to the second operating system when the foreground running operating system is the first operating system, 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 a fourth processing module configured to directly display the application interface corresponding to the second notification message through the second operating system when the foreground running operating system is the second operating system, and display the second notification message based on the application interface. In some embodiments, the apparatus further includes: a display module configured to display a notification detail interface, the notification detail interface displaying at least one third notification message and an operation button corresponding to the third notification message, the at least one third notification message including at least one of the first notification message and the second notification message; and a fifth processing module configured to process the third notification message based on the type of the operation button when a triggering operation of any operation button corresponding to the third notification message is detected. In some embodiments, the fifth processing module is configured to determine the source of the third notification message and the foreground running operating system when the type of the operation button is a non-reply type, forward the triggering operation to the first operating system when the source of the third notification message is the electronic device and the foreground running operating system is the second operating system, so that the first operating system forwards the triggering operation to the electronic device and the electronic device executes the triggering operation; and / or execute the triggering operation through the first operating system when the source of the third notification message is the wearable device and the foreground running operating system is the first operating system, or forward the triggering operation to the second operating system and switch the second operating system to the foreground running, so that the second operating system executes the triggering operation. In some embodiments, the fifth processing module is configured to switch the second operating system to the foreground running when the type of the operation button is a reply type, generate a plurality of shortcut reply phrases through the second operating system, and display a notification reply interface, the notification reply interface including a shortcut reply phrase list including the plurality of shortcut reply phrases. In some embodiments, the apparatus further includes: a second determining module configured to determine the foreground running operating system when the state of the third notification message changes, the third notification message being any of the first notification message and the second notification message; and a first synchronization module configured to synchronize the state of the third notification message between the first operating system and the second operating system based on the foreground running operating system. In some embodiments, the first synchronization module is configured to synchronize the state of the third notification message to the first operating system when the foreground running operating system is the second operating system, temporarily suspend the synchronization of the state of the first notification message when the foreground running operating system is the first operating system, and synchronize the state of the first notification message to the second operating system when the foreground running operating system is switched from the first operating system to the second operating system.In some embodiments, the apparatus further comprises a storage module configured to store, by the second operating system, a fourth notification message into the database when the wearable device is powered off, the fourth notification message being a notification message that is not processed before the wearable device is powered off; and a second synchronization module configured to synchronize, by the second operating system, the stored fourth notification message to the first operating system when the wearable device is powered on. In some embodiments, the apparatus further comprises a third synchronization module configured to, when the number of notification messages stored by the first core controller exceeds the second preset number, delete, based on the storage time of each notification message, a target notification message whose storage time is farthest from the current time, and notify the second operating system to synchronize the deletion of the target notification message. In some embodiments, the apparatus further comprises a third determination module configured to, when a deletion operation of any notification message is detected, determine the operating system running in the foreground; a first deletion module configured to, when the operating system running in the foreground is the second operating system, perform the deletion operation on the notification message based on the second operating system; and a second deletion module configured to, when the operating system running in the foreground is the first operating system, determine an execution type of the deletion operation, the execution type indicating whether the deletion operation needs to be performed in the foreground or in the background, and perform the deletion operation on the notification message based on the execution type. In some embodiments, the second deletion module is configured to, when the execution type is foreground execution, switch the operating system running in the foreground from the first operating system to the second operating system, and perform the deletion operation on the notification message based on the second operating system; and when the execution type is background execution, perform the deletion operation on the notification message in the background by the second operating system. In some embodiments of the present application, by setting the first processing strategy and the 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, so that the single-core single-system is run on one of the dual cores, and cooperates with the other core and the operating system running thereon, and thus can process the notification message based on the dual-core dual-system.

[0166] It should be noted that the message notification apparatus provided in the above embodiments is only used as an example for message notification, and in actual applications, the above functions can be completed by different functional modules according to needs, i.e., the internal structure of the wearable device is divided into different functional modules to complete all or part of the above described functions. In addition, the message notification apparatus and the message notification method provided in the above embodiments belong to the same concept, and the specific implementation process is described in detail in the method embodiments, which will not be described here.

[0167] Please refer to FIG. 13, which shows a block diagram of a message notification synchronization device according to an example embodiment of the present application, which is deployed in a wearable device including a first core controller and a second core controller; the device includes: a division module 1301 for dividing the notification messages held by the first core controller into deleted notification messages, unchanged notification messages and changed notification messages.

[0168] The device further includes one or more of the following modules: a first sending module 1302 for the first core controller to send a first protocol to inform the second core controller of the message identifiers of the read notification messages; a second sending module 1303 for the second core controller to send a second protocol to start a first stage synchronization; the first stage synchronization includes unchanged notification message synchronization and latest N notification message synchronization; a third sending module 1304 for the first core controller to send a third protocol to inform the second core controller of the unchanged notification messages; a deletion module 1305 for the second core controller to delete all notification messages other than the unchanged notification messages; a fourth sending module 1306 for the first core controller to send a fourth protocol to synchronize the notification messages of the type of picture in the latest N notification messages of the second core controller; a fifth sending module 1307 for the first core controller to send a fifth protocol to synchronize the notification messages of the type of text in the latest N notification messages of the second core controller; a sixth sending module 1308 for the first core controller to send a sixth protocol to inform the second core controller that the first stage synchronization is completed, and the sixth protocol carries a flag indicating whether a second stage synchronization is needed; a preparation module 1309 for the second core controller to prepare a historical notification interface; a seventh sending module 1310 for the second core controller to send a seventh protocol to start a second stage synchronization; an eighth sending module 1311 for the first core controller to send a fourth protocol to synchronize the notification messages of the type of picture in other newly added notification messages of the second core controller; a ninth sending module 1312 for the first core controller to send a fifth protocol to synchronize the notification messages of the type of text in other newly added notification messages of the second core controller; a tenth sending module 1313 for the first core controller to send a sixth protocol to inform the second core controller that the second stage synchronization is completed; and a perfecting module 1314 for the second core controller to perfect the notification messages.

[0169] In some embodiments, the modified notification message includes the latest N notification messages and the other newly added notification messages; the N is 20. In some embodiments, the device process includes first stage synchronization and / or second stage synchronization; the first stage synchronization includes synchronizing the latest N notification messages in the unchanged notification message and the modified notification message; the second stage synchronization includes synchronizing the other newly added notification messages in the modified notification message; the types of the latest N notification messages and the other newly added notification messages include picture notification messages and text notification messages.

[0170] In some embodiments of the present application, the first core controller stores a plurality of first notification messages, and the plurality of first notification messages are synchronized to the second operating system in batches, so that part of the first notification messages stored in the first core controller can be synchronized to the second operating system as soon as possible, and the notification bar interface of the wearable device can display the synchronized first notification messages in the first time when the second operating system is running in the foreground, so that the operating system running in the foreground is not perceived by the user when switching, and the user experience is improved.

[0171] It should be noted that the message notification synchronization device provided in the above embodiments is only used as an example for dividing the above functional modules when synchronizing the message notification, and in actual applications, the above functions can be completed by different functional modules according to needs, that is, the internal structure of the wearable device is divided into different functional modules to complete all or part of the above described functions. In addition, the message notification synchronization device and the message notification synchronization method provided in the above embodiments belong to the same concept, and the specific implementation process is described in detail in the method embodiments, which will not be repeated here.

[0172] Please refer to FIG. 14, which shows a structural block diagram of a wearable device 1400 provided in an example embodiment of the present application. The wearable device 1400 includes a first core controller 1410, a second core controller 1420 and a memory 1430, the first core controller 1410 is used to run a first operating system, the second core controller 1420 is used to run a second operating system, and the power consumption of the first core controller 1410 running the first operating system is lower than the power consumption of the second core controller 1420 running the second operating system;

[0173] The memory 1430 stores at least one piece of program code, which is loaded and executed by the first core controller 1410 and the second core controller 1420 to implement the message notification method described above. The second core controller 1420 includes a WearService 1421 for running a second operating system and a SysUI 1422 for displaying notification messages. The first core controller 1410 or the WearService 1421 can include one or more processing cores. The first core controller 1410 or the WearService 1421 connects various parts in the entire wearable device 1400 through various interfaces and lines, performs various functions of the wearable device 1400 and processes data by running or executing instructions, programs, code sets or instruction sets stored in the memory 1430, and calling data stored in the memory 1430. Alternatively, the first core controller 1410 or the WearService 1421 can be implemented in at least one of a hardware form of a digital signal processing (DSP), a field-programmable gate array (FPGA), and a programmable logic array (PLA). The first core controller 1410 or the WearService 1421 can be integrated with a combination of one or more of a central processing unit (CPU), a graphics processing unit (GPU), a neural-network processing unit (NPU), and a modem. Among them, the CPU mainly processes operating systems, user interfaces, and application programs, etc.; the GPU is responsible for rendering and drawing the content to be displayed by the SysUI 1422; the NPU is used to implement artificial intelligence (AI) functions; and the modem is used to process wireless communication. It can be understood that the above-mentioned modem can also not be integrated into the processor first core controller 1410 or the WearService 1421, but be implemented separately through a chip. The memory 1430 can include a random access memory (RAM) and can also include a read-only memory (ROM). Optionally, the memory 1430 includes a non-transitory computer-readable storage medium.The memory 1430 can be used to store instructions, programs, codes, code sets, or instruction sets. The memory 1430 can include a storage program area and a storage data area, where the storage program area can store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing each of the method embodiments described below, etc., and the storage data area can store data created according to the use of the wearable device 1400 (such as audio data, a phone book, etc.). The SysUI 1422 is a display component for displaying a user interface. Optionally, the SysUI 1422 is a SysUI 1422 with a touch function, through which a user can use a finger, a stylus, or any suitable object to perform a touch operation on the SysUI 1422. The SysUI 1422 is usually arranged on the front panel of the wearable device 1400. The SysUI 1422 can be designed to be a full-screen, a curved screen, a special-shaped screen, a double-sided screen, or a folding screen. The SysUI 1422 can also be designed to be a combination of a full-screen and a curved screen, a combination of a special-shaped screen and a curved screen, etc., and the present embodiment does not limit this. In addition, those skilled in the art can understand that the structure of the wearable device 1400 shown in the above-mentioned drawings does not constitute a limitation on the wearable device 1400, and the wearable device 1400 can include more or fewer components than those shown in the drawings, or combine certain components, or different component arrangements. For example, the wearable device 1400 also includes audio acquisition devices, speakers, radio frequency circuits, input units, sensors, audio circuits, Wireless Fidelity (Wi-Fi) modules, power supplies, Bluetooth modules, etc., which are not described here.

[0174] The embodiments of the present application also provide a computer readable medium, which stores at least one program code, the at least one program code is loaded and executed by the processor to implement the message notification method shown in each of the above embodiments. The embodiments of the present application also provide a computer program product, which stores at least one program code, the at least one program code is loaded and executed by the processor to implement the message notification method shown in each of the above embodiments. In some embodiments, the computer program product related to the embodiments of the present application can be deployed to execute on a wearable device, or to execute on a plurality of wearable devices located in one place, or to execute on a plurality of wearable devices distributed in multiple places and interconnected through a communication network, and the plurality of wearable devices distributed in multiple places and interconnected through a communication network can constitute a blockchain system.

[0175] Those skilled in the art should be aware that, in the above one or more examples, the functions described in the embodiments of the present application can be implemented in hardware, software, firmware or any combination thereof. When implemented in software, the functions can be stored in a computer readable medium or transmitted as one or more instructions or code on the computer readable medium. The computer readable medium includes computer storage medium and communication medium, and the communication medium includes any medium that facilitates transfer of computer program from one place to another. The storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.

[0176] The above only describes optional embodiments of the present application, and is not intended to limit the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A message notification method performed by a wearable device, the wearable device comprising a first core controller and a second core controller, the first core controller configured to run a first operating system, the second core controller configured to run a second operating system, and a power consumption of the first core controller running the first operating system being lower than a power consumption of the second core controller running the second operating system; the method comprising: when the first operating system receives a first notification message of 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 a second notification message of the wearable device, processing the second notification message based on a second processing strategy. 2.The method of claim 1, wherein the processing the first notification message based on the first processing strategy comprises: when the second operating system is in a sleep state, storing the first notification message by the first core controller; when the second operating system switches to a running state, batching a plurality of first notification messages stored by the first core controller to obtain one or more batches of notification messages; and synchronizing the one or more batches of notification messages to the second operating system. 3.The method of claim 2, wherein the batching the plurality of first notification messages stored by the first core controller to obtain one or more batches of notification messages comprises: based on the plurality of first notification messages stored by the first core controller and second notification messages stored by the second core controller, dividing the plurality of first notification messages stored by 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 being read notification messages; or the second batch of notification messages being unchanged notification messages; or the third batch of notification messages being newly added notification messages, the third batch of notification messages comprising a first notification message set and / or a second notification message set, the first notification message set comprising a first preset number of recently added notification messages, and the second notification message set comprising other newly added notification messages other than the first notification message set. 4.The method of claim 3, wherein the synchronizing the one or more batches of notification messages to the second operating system comprises: synchronizing 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 other than the second batch of notification messages; and / or synchronizing the first notification message set in the third batch of notification messages to the second operating system; and when the synchronization of the first notification message set is completed, synchronizing the second notification message set in the third batch of notification messages to the second operating system. 5.The method of claim 1, wherein the processing the second notification message based on the second processing strategy comprises: ​ ​ ​ determining a foreground operating system when the second notification message is a full-screen type of notification message; when the foreground operating system is the first operating system, switching the foreground operating system 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 foreground operating system is the second operating system, directly displaying the application interface corresponding to the second notification message through the second operating system, and displaying the second notification message based on the application interface.

6. The method of claim 1, further comprising: displaying a notification details interface, the notification details interface displaying at least one third notification message and an operation button corresponding to the third notification message, the at least one third notification message including at least one of the first notification message and the second notification message; when a triggering operation of any operation button corresponding to a third notification message is detected, processing the third notification message based on a type of the operation button.

7. The method of claim 6, wherein processing the third notification message based on the type of the operation button comprises: when the type of the operation button is a non-reply type, determining a source of the third notification message and a foreground operating system; when the source of the third notification message is the electronic device and the foreground operating system is the second operating system, forwarding the triggering operation to the first operating system, so that the first operating system forwards the triggering operation to the electronic device and the electronic device executes the triggering operation; and / or when the source of the third notification message is the wearable device and the foreground operating system is the first operating system, executing the triggering operation through the first operating system, or forwarding the triggering operation to the second operating system and switching the second operating system to be foreground running, so that the second operating system executes the triggering operation.

8. The method of claim 6, wherein processing the third notification message based on the type of the operation button comprises: when the type of the operation button is a reply type, switching the second operating system to be foreground running, and generating a plurality of shortcut reply phrases through the second operating system; displaying a notification reply interface, the notification reply interface including a shortcut reply phrase list, the shortcut reply phrase list including the plurality of shortcut reply phrases.

9. The method of claim 1, further comprising: when a state of a third notification message changes, determining a foreground operating system, the third notification message being any of the first notification message and the second notification message; based on the foreground operating system, synchronizing the state of the third notification message between the first operating system and the second operating system. ​ ​ 10. The method of claim 9, wherein the synchronizing the state of the third notification message between the first operating system and the second operating system based on the foreground running operating system comprises: synchronizing the state of the third notification message to the first operating system when the foreground running operating system is the second operating system; and / or suspending the synchronization of the state of the first notification message when the foreground running operating system is the first operating system; and synchronizing the state of the first notification message to the second operating system when the foreground running operating system is switched from the first operating system to the second operating system.

11. The method of claim 1, further comprising: determining a foreground running operating system when a deletion operation of any notification message is detected; performing the deletion operation on the notification message based on the second operating system when the foreground running operating system is the second operating system; and / or determining a type of execution of the deletion operation, the type of execution indicating whether the deletion operation needs to be performed in foreground or background when the foreground running operating system is the first operating system; and performing the deletion operation on the notification message based on the type of execution.

12. A method for synchronizing notification messages, performed by a wearable device, the wearable device comprising a first core controller and a second core controller, the method comprising: dividing notification messages held by the first core controller into deleted notification messages, unchanged notification messages, and changed notification messages. The method further comprises one or more of: the first core controller sending a first protocol to inform the second core controller of message identifiers of read notification messages; 13. The method according to claim 12, wherein, the second core controller sending a second protocol to start a first stage of synchronization; the first stage of synchronization comprising synchronization of unchanged notification messages and synchronization of the latest N notification messages; the first core controller sending a third protocol to inform the second core controller of the unchanged notification messages; the second core controller deleting all notification messages other than the unchanged notification messages; the first core controller sending a fourth protocol to synchronize notification messages of a picture type among the latest N notification messages of the second core controller; the first core controller sending a fifth protocol to synchronize notification messages of a text type among the latest N notification messages of the second core controller; the first core controller sending a sixth protocol to inform the second core controller that the first stage of synchronization is completed, the sixth protocol carrying a flag indicating whether a second stage of synchronization is needed; the second core controller preparing a history notification interface; the second core controller sending a seventh protocol to start the second stage of synchronization; the first core controller sending the fourth protocol to synchronize notification messages of the picture type among other newly added notification messages of the second core controller; the first core controller sending the fifth protocol to synchronize notification messages of the text type among other newly added notification messages of the second core controller. ​ ​ The first core controller sends a sixth protocol to inform the second core controller that the second stage synchronization is completed. The second core controller sends a notification message.

14. The method of claim 12, wherein the modified notification message comprises the latest N notification messages and the other new notification messages; and the N is 20.

15. The method of claim 12, wherein the method comprises a first stage synchronization and / or a second stage synchronization. The first stage synchronization comprises synchronizing the unchanged notification messages and the latest N notification messages in the modified notification message. The second stage synchronization comprises synchronizing the other new notification messages in the modified notification message. The latest N notification messages and the other new notification messages comprise picture notification messages and text notification messages.

16. A notification message synchronization apparatus deployed in a wearable device, the wearable device comprising a first core controller and a second core controller, the first core controller configured to run a first operating system, the second core controller configured to run a second operating system, and the first core controller running the first operating system consumes less power than the second core controller running the second operating system; the apparatus comprising: a first processing module configured to process a first notification message based on a first processing strategy when the first notification message is received by the first operating system from an electronic device connected to the wearable device; and / or a second processing module configured to process a second notification message based on a second processing strategy.

17. A notification message apparatus deployed in a wearable device, the wearable device comprising a first core controller and a second core controller. The apparatus comprising: a division module configured to divide notification messages held by the first core controller into deleted notification messages, unchanged notification messages and modified notification messages.

18. The apparatus of claim 17, wherein the apparatus further comprises one or more of: a first sending module configured to send a first protocol by the first core controller to inform the second core controller of message identifiers of read notification messages; a second sending module configured to send a second protocol by the second core controller to start a first stage synchronization; the first stage synchronization comprises unchanged notification message synchronization and latest N notification message synchronization; a third sending module configured to send a third protocol by the first core controller to inform the second core controller of the unchanged notification messages; a deletion module configured to delete, by the second core controller, all notification messages other than the unchanged notification messages; a fourth sending module configured to send a fourth protocol by the first core controller to synchronize picture notification messages in the latest N notification messages of the second core controller; a fifth sending module configured to send a fifth protocol by the first core controller to synchronize text notification messages in the latest N notification messages of the second core controller. A sixth sending module, configured to send, by the first core controller, a sixth protocol to inform the second core controller that the first stage synchronization is completed, and the sixth protocol carries a flag indicating whether the second stage synchronization is needed; A preparation module, configured to prepare, by the second core controller, a history notification interface; A seventh sending module, configured to send, by the second core controller, a seventh protocol to start the second stage synchronization; An eighth sending module, configured to send, by the first core controller, a fourth protocol to synchronize the notification messages of the type of picture in the other newly added notification messages of the second core controller; A ninth sending module, configured to send, by the first core controller, a fifth protocol to synchronize the notification messages of the type of text in the other newly added notification messages of the second core controller; A tenth sending module, configured to send, by the first core controller, the sixth protocol to inform the second core controller that the second stage synchronization is completed; A perfecting module, configured to perfect, by the second core controller, the notification messages.

19. The apparatus according to claim 17, wherein the apparatus comprises the first stage synchronization and / or the second stage synchronization; the first stage synchronization comprises synchronizing the latest N notification messages in the unchanged notification messages and the changed notification messages; the second stage synchronization comprises synchronizing the other newly added notification messages in the changed notification messages; the types of the latest N notification messages and the other newly added notification messages comprise the picture notification messages and the text notification messages.

20. A wearable device, comprising a first core controller, a second core controller and a memory, wherein the first core controller is configured to run a first operating system, the second core controller is configured 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 memory stores at least one piece of program code, and the at least one piece of 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 14.

21. A computer readable storage medium, wherein the storage medium stores at least one piece of program code, and the at least one piece of program code is loaded and executed by a processor to implement the message notification method according to any one of claims 1 to 14.

22. A computer program product, wherein the computer program product stores at least one piece of program code, and the at least one piece of program code is used to be executed by a processor to implement the message notification method according to any one of claims 1 to 14.

Images