Notification synchronization method and electronic device

Abstract

Embodiments of the present application provide a notification synchronization method and an electronic device. In the method, a first electronic device receives a first notification sent by a push server and a device identifier list comprising device identifiers of one or more electronic devices, and then determines, on the basis of whether the device identifier list comprises a device identifier of a second electronic device in a same network as the first electronic device, whether to synchronize the first notification to the second electronic device. Specifically, if the device identifier list does not comprise the device identifier of the second electronic device, the first electronic device performs synchronization, and if the device identifier list comprises the device identifier of the second electronic device, the first electronic device does not perform synchronization. The first notification is from a first application and corresponds to a first account, and the one or more electronic devices and the first electronic device log into the first application via the first account. According to the method and the electronic device, upon receiving a notification message, an electronic device can determine which devices the notification message has been sent to on the basis of a device identifier list included in the notification message, and can thus avoid forwarding the notification message to other devices that have already received the notification message, thereby avoiding duplicate message notifications.

Description

Notification synchronization method and electronic device

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on December 27, 2023, with application number 202311836023.1 and application name “Method and electronic device for notification synchronization”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] Embodiments of the present application relate to the field of notification synchronization, and more specifically, to a notification synchronization method and electronic device. Background Art

[0003] The message notification function of an electronic device is designed to remind users of communication information from others or other real-time information in an application. Users can open the application by tapping the notification displayed on the screen of the electronic device, or perform related operations directly from the notification.

[0004] For single-device notification scenarios, notifications are mainly pushed from the cloud or sent locally by applications. For cross-device notification scenarios, the notification synchronization strategy between devices depends on customized scenarios. For example: scenarios where notifications are synchronized between mobile phones and watches, scenarios where notifications are synchronized between mobile phones and headphones, and scenarios where multi-screen collaboration is required. In the current notification synchronization method, the notification management rules are simple, and there is a lack of a good management and control mechanism for the presentation and reminders of notifications. There are too many notifications and they are chaotic. It is easy to have duplicate reminders of notification messages, which affects the user experience.

[0005] Summary of the Invention

[0006] The present application provides a notification synchronization method and electronic device. Through this method and electronic device, after receiving a notification message, the electronic device can determine which devices the notification message is sent to based on the device identification list carried by the notification message. The electronic device can avoid forwarding the notification message to other devices that have received the notification message, thereby avoiding the inconvenience caused to the user by repeated reminders of message notifications.

[0007] In a first aspect, a method for notification synchronization is provided, the method comprising: a first electronic device receives a first notification and a device identification list sent by a push server, wherein the first electronic device logs in to a first application through a first account, the device identification list includes device identifications of one or more electronic devices, the one or more electronic devices log in to the first application through the first account, and the first notification is a notification of the first application corresponding to the first account; when the device identification list does not include the device identification of the second electronic device, the first electronic device synchronizes the first notification to the second electronic device; or when the device identification list includes the device identification of the second electronic device, the first electronic device does not synchronize the first notification to the second electronic device, and the second electronic device and the first electronic device are in the same network.

[0008] The first notification and the device identification list received by the first electronic device are sent by the push server based on the device identification of the first electronic device.

[0009] Optionally, the push server may also be referred to as a push cloud.

[0010] In an embodiment of the present application, the push server sends the notification message to all devices corresponding to the device identification list respectively. The notification message sent by the push server to the electronic device carries the device identification list. In this way, after receiving the notification message, the electronic device can determine which devices the notification message is sent to based on the device identification list. The electronic device can avoid repeatedly forwarding the notification message to other devices that have received the notification message, thereby avoiding the trouble caused to the user due to the repeated sending of message notifications.

[0011] With reference to the first aspect, in a possible implementation manner, the device identification list includes the device identification of the first electronic device.

[0012] In another embodiment, the device identification list does not include the device identification of the first electronic device.

[0013] In an embodiment of the present application, the device identification list sent by the push server to the electronic device includes the device identification list of the electronic device. That is, the push server can directly forward the received device identification list to the electronic device without editing the device identification list. For example, the device identification of the electronic device is not deliberately deleted from the device identification list. In this way, the operation of the push server can be simplified and the feasibility is enhanced.

[0014] In combination with the first aspect, in a possible implementation, the first electronic device synchronizing the first notification to the second electronic device includes: the first electronic device synchronizing the first notification to the database of the second electronic device through the database of the first electronic device.

[0015] In one implementation, the database of the first electronic device and the database of the second electronic device are synchronized across devices. When the database of one electronic device is updated, the databases of the other electronic devices synchronized across devices are updated synchronously.

[0016] Optionally, the update of the database may include the addition of notification messages; it may also include the status update of notification messages, such as the reading status of notification messages; it may also include the status update of electronic devices, such as unlock status, lock screen status, screen off status, etc.

[0017] In an embodiment of the present application, multiple electronic devices located in the same network can synchronize notification messages, the status of notification messages (reading status, etc.) and the status of electronic devices (unlocked status, etc.) across terminals through a database, thereby better realizing message collaborative reminders between multiple electronic devices. For example: when one device reads the notification, the notification displayed on the other device disappears synchronously.

[0018] In combination with the first aspect, in a possible implementation, the method also includes: the first electronic device determines whether the first notification has been received; if the first electronic device determines that the first notification has not been received, the first electronic device issues a reminder of the first notification to the user.

[0019] It is understandable that multiple electronic devices may receive the same message notification multiple times due to reasons such as message sending and receiving delays or because they are not in the same network.

[0020] In an embodiment of the present application, when an electronic device receives a notification message, it can determine whether the notification message has been received before. If the notification message has been received, the user will not be reminded of the notification message again, thereby further avoiding repeated reminders of the notification message and improving the user experience.

[0021] In combination with the first aspect, in a possible implementation, before the first electronic device issues a reminder of the first notification to the user, the method further includes: the first electronic device determines a reminder method for the first notification according to a state of the first electronic device.

[0022] In one example, when the first electronic device is in an unlocked state, the first electronic device may issue a reminder of the first notification through a pop-up window, ringtone, vibration, etc.; when the first electronic device is in a locked screen state, the first electronic device may silently remind the first notification.

[0023] In an embodiment of the present application, when multiple electronic devices within a network collaborate to provide notification message reminders, the reminder method can be determined based on the current status of the electronic device. In this way, when a user is using one of the electronic devices, the electronic device being used will explicitly remind the user, enabling the user to accurately receive the notification message reminder.

[0024] In combination with the first aspect, in one possible implementation, before the first electronic device receives the first notification and device identification list sent by the push server, the method also includes: the first electronic device sends the device identification of the first electronic device to the application server of the first application, so that when the application server of the first application generates the first notification, it sends the first notification and the device identification of the first electronic device to the push server.

[0025] In one example, when a first electronic device is turned on for the first time, the first electronic device registers the device identification of the first electronic device with a push server. Based on this, when the first application installed on the first electronic device is logged in to for the first time through the first account on the first electronic device, the first electronic device will send the device identification of the first electronic device to the application server of the first application to inform the server of the first application: the device identification of the electronic device that logs in to the first application through the first account is the device identification of the first electronic device. Similarly, if the user switches the account corresponding to the first application on the first electronic device from the first account to the second account, the first electronic device will resend the device identification of the first electronic device to the application server of the first application.

[0026] In an embodiment of the present application, the electronic device can send the device identification of the electronic device to the application server. In this way, after receiving the notification message of the application, the application server can send the received device identification list and notification message together to the push server, and the push server can further push it to the electronic device.

[0027] In combination with the first aspect, in a possible implementation, before the first electronic device sends the device identification of the first electronic device to the application server of the first application, the method also includes: the first electronic device sends a first request message to the push server, and the first request message is used to request registration of the device identification of the first electronic device; the first electronic device receives the device identification of the first electronic device sent by the push server.

[0028] In an embodiment of the present application, the electronic device can register its own device identification with the push server and send the device identification to the application server. In this way, after the application server generates a notification message for the application, it can send the received device identification list and the notification message together to the push server, and the push server can further push it to the electronic devices in the device identification list, so that the electronic device can determine which devices the notification message is sent to based on the device identification list, thereby providing a basis for whether the electronic device synchronizes message notifications to other devices.

[0029] In combination with the first aspect, in one possible implementation, after the first electronic device synchronizes the first notification to the second electronic device, the method further includes: when the status of the first notification changes, the first electronic device synchronizes the status of the first notification to the second electronic device.

[0030] The status of the first notification may include a reception status of the notification message, a reading status of the notification message, an update status of the notification message, or a status of an electronic device that receives the notification message.

[0031] In an embodiment of the present application, multiple electronic devices located in the same network can synchronize notification messages, the status of notification messages (reading status, etc.), and the status of electronic devices (unlocked status, etc.) across terminals, thereby better realizing message collaborative reminders between multiple electronic devices. For example: when one device reads the notification, the notification displayed on the other device disappears synchronously.

[0032] In combination with the first aspect, in one possible implementation, the first electronic device synchronizes the status of the first notification to the second electronic device, including: the first electronic device updates the status of the first notification to the database of the first electronic device, and the database of the first electronic device and the database of the second electronic device are synchronized across ends.

[0033] In some embodiments, when the state of the first electronic device changes, the first electronic device updates the state of the first electronic device to a database of the first electronic device.

[0034] In some embodiments, when the first electronic device receives the first notification, the first electronic device updates the first notification to a database of the first electronic device.

[0035] In an embodiment of the present application, multiple electronic devices located in the same network can synchronize notification messages, the status of notification messages (reading status, etc.) and the status of electronic devices (unlocked status, etc.) across terminals through a database, thereby better realizing message collaborative reminders between multiple electronic devices. For example: when one device reads the notification, the notification displayed on the other device disappears synchronously.

[0036] In a second aspect, a method for notification synchronization is provided, the method comprising: a push server receives a first notification and a device identification list sent by an application server of a first application, the device identification list including the device identification of one or more electronic devices that have logged into the first application through a first account, the device identification list including the device identification of the first electronic device, and the first notification is a notification of the first application corresponding to the first account; the push server sends the first notification and the first device identification list to the first electronic device based on the device identification of the first electronic device, the first device identification list is the same as the device identification list, or the first device identification list includes all device identifications in the device identification list except the device identification of the first electronic device.

[0037] In an embodiment of the present application, the push server sends the notification message to the corresponding devices in the device identification list respectively. The notification message sent by the push server to the electronic device carries the device identification list. In this way, after receiving the notification message, the electronic device can determine which devices the notification message is sent to based on the device identification list. The electronic device can avoid repeatedly forwarding the notification message to other devices that have received the notification message, thereby avoiding the trouble caused to the user due to the repeated sending of message notifications.

[0038] In combination with the second aspect, in a possible implementation, when the device identification list includes the device identification of the second electronic device, the method also includes: the push server sends the first notification and the second device identification list to the second electronic device based on the device identification of the second electronic device, and the second device identification list is the same as the device identification list, or the second device identification list includes all device identifications in the device identification list except the device identification of the second electronic device.

[0039] In an embodiment of the present application, the push server sends the notification message to all devices corresponding to the device identification list respectively. The notification message sent by the push server to the electronic device carries the device identification list. In this way, after receiving the notification message, the electronic device can determine which devices the notification message is sent to based on the device identification list. The electronic device can avoid repeatedly forwarding the notification message to other devices that have received the notification message, thereby avoiding the trouble caused to the user due to the repeated sending of message notifications.

[0040] In combination with the second aspect, in a possible implementation, before the push server receives the first notification and device identification list sent by the application server of the first application, the method also includes: the push server receives a first request message sent by the first electronic device, and the first request message is used to request registration of the device identification of the first electronic device; the push server sends the device identification of the first electronic device to the first electronic device, so that the first electronic device sends the device identification of the first electronic device to the application server of the first application, and then the application server of the first application sends the first notification and the device identification of the first electronic device to the push server when generating the first notification.

[0041] In an embodiment of the present application, the push server can register the device identification of the electronic device based on the registration request of the electronic device and send it to the electronic device, so that the electronic device can send the device identification to the application server after obtaining its own device identification. In this way, after the application server generates the notification message of the application, it can send the received device identification list and notification message together to the push server, and the push server further pushes it to the electronic devices in the device identification list, so that the electronic device can determine which devices the notification message is sent to based on the device identification list, thereby providing a basis for whether the electronic device synchronizes message notifications to other devices.

[0042] In conjunction with the second aspect, in a possible implementation, the push server is pre-set with a notification synchronization rule, and the notification synchronization rule is used for electronic devices in the network to synchronize notifications.

[0043] In some embodiments, the notification synchronization rules can be determined based on the type of electronic device in the network. For example, when the electronic device is a watch, the user needs to enable notification synchronization authorization for the watch in the relevant application of the electronic device that receives the notification message before the notification can be synchronized to the watch. For another example, when the electronic device is a PC, the notification can be synchronized to the PC only when the PC and the electronic device that receives the notification message are in a collaborative state.

[0044] In an embodiment of the present application, a notification synchronization strategy that unifies end-cloud collaboration and end-end collaboration is provided, and notification synchronization is performed between all electronic devices in the same network based on the notification synchronization rules preset by the push server. In this way, notification synchronization between multiple electronic devices does not rely on customized scenarios, but is applicable to a unified set of notification synchronization strategies, thereby improving the convenience of notification synchronization.

[0045] According to a third aspect, a method for synchronizing notifications is provided, the method comprising: after generating a first notification, the application server of the first application sends the first notification and a device identification list to a push server, the device identification list including the device identifications of one or more electronic devices that have logged into the first application through a first account, the device identification list being used by the push server to send the first notification and the device identification list to the one or more electronic devices, the first notification being a notification of the first application corresponding to the first account.

[0046] In some embodiments, the device identification list sent by the push server to the target electronic device may be the same as the received device identification list, or may be a device identification list obtained by deleting the device identification of the target electronic device from the received device identification list.

[0047] In an embodiment of the present application, the notification message sent by the application server carries a device identification list, and the push server can send the notification message to all devices corresponding to the device identification list respectively. The notification message sent by the push server to the electronic device also carries the device identification list. In this way, after receiving the notification message, the electronic device can determine which devices the notification message is sent to based on the device identification list. The electronic device can avoid repeatedly forwarding the notification message to other devices that have received the notification message, thereby avoiding the trouble caused to the user due to the repeated sending of message notifications.

[0048] In combination with the third aspect, in one possible implementation, when the device identification list includes the device identification of the first electronic device, before sending the first notification and the device identification list to the push server, the method also includes: the application server of the first application receives the device identification of the first electronic device sent by the first electronic device.

[0049] In some embodiments, when the first electronic device logs in to the first application through the first account for the first time, the application server of the first application receives the device identification of the first electronic device sent by the first electronic device.

[0050] In an embodiment of the present application, the electronic device can send its own device identification to the application server, so that after the application server generates a notification message, it can send the received device identification and notification message together through the push server, so that the electronic device can determine which devices the notification message is sent to based on this, thereby providing a basis for whether the electronic device synchronizes message notifications to other devices.

[0051] In combination with the third aspect, in one possible implementation, when the device identification list includes the device identification of the second electronic device, before sending the first notification and the device identification list to the push server, the method also includes: the application server of the first application receives the device identification of the second electronic device sent by the second electronic device.

[0052] In some embodiments, when the second electronic device logs in to the first application through the first account for the first time, the application server of the first application receives the device identification of the second electronic device sent by the second electronic device.

[0053] In an embodiment of the present application, the electronic device can send its own device identification to the application server, so that after generating a notification message, the application server can push the device identification list composed of the received device identifications and the notification message to all devices in the device identification list through the push server, and also enable the electronic device to determine which devices the notification message is sent to based on this, thereby providing a basis for whether the electronic device synchronizes message notifications to other devices.

[0054] In a fourth aspect, an electronic device is provided, comprising a memory and a processor, wherein the memory is used to store computer program code, and the processor is used to execute the computer program code stored in the memory to implement the method in the above-mentioned first aspect or any possible implementation of the first aspect, or to implement the method in the above-mentioned second aspect or any possible implementation of the second aspect, or to implement the method in the above-mentioned third aspect or any possible implementation of the third aspect.

[0055] In a fifth aspect, a system is provided, which includes one or more first electronic devices, a push server and an application server, wherein the first electronic device is used to execute the method in the above-mentioned first aspect or any possible implementation of the first aspect, the push server is used to execute the method in the above-mentioned second aspect or any possible implementation of the second aspect, and the application server is used to execute the method in the above-mentioned third aspect or any possible implementation of the third aspect.

[0056] In the sixth aspect, a computer-readable storage medium is provided, which stores a computer program or instruction. When the computer program or instruction is executed, it implements the method in the above-mentioned first aspect or any possible implementation of the first aspect, or implements the method in the above-mentioned second aspect or any possible implementation of the second aspect, or implements the method in the above-mentioned third aspect or any possible implementation of the third aspect.

[0057] In the seventh aspect, a chip is provided, in which instructions are stored. When the chip is run on a device, the chip executes the method in the above-mentioned first aspect or any possible implementation of the first aspect, or executes the method in the above-mentioned second aspect or any possible implementation of the second aspect, or executes the method in the above-mentioned third aspect or any possible implementation of the third aspect.

[0058] In an eighth aspect, a computer program product is provided, in which a computer program or instruction is stored. When the computer program or instruction is executed, the method in the first aspect or any possible implementation of the first aspect is implemented, or the method in the second aspect or any possible implementation of the second aspect is implemented, or the method in the third aspect or any possible implementation of the third aspect is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] FIG1 is a schematic structural diagram of an electronic device provided in an embodiment of the present application;

[0060] FIG2 is a block diagram of the software structure of the electronic device provided in an embodiment of the present application;

[0061] FIG3 is a schematic diagram of notification synchronization corresponding to a scenario in which notifications are synchronized between a mobile phone and a watch;

[0062] FIG4 is a schematic diagram of notification synchronization corresponding to a scenario in which notifications are synchronized between a mobile phone and a cockpit;

[0063] FIG5 is a schematic diagram of notification synchronization corresponding to a scenario in which notifications are synchronized between a mobile phone and a tablet;

[0064] FIG6 is a schematic diagram of notification synchronization corresponding to a scenario in which notifications are synchronized between a mobile phone and a headset;

[0065] FIG7 is a schematic diagram of a scenario provided by an embodiment of the present application;

[0066] FIG8 is a schematic diagram illustrating a notification message sending method according to an embodiment of the present application;

[0067] FIG9 is a schematic diagram of a cross-device notification subscription method provided in an embodiment of the present application;

[0068] FIG10 is a schematic diagram of a system architecture for notification synchronization provided by an embodiment of the present application;

[0069] FIG11 is a schematic flowchart of a notification synchronization method provided in an embodiment of the present application;

[0070] FIG12 is a schematic flowchart of another notification synchronization method provided in an embodiment of the present application;

[0071] FIG13 is a schematic flowchart of another notification synchronization method provided in an embodiment of the present application;

[0072] FIG14 is a schematic flowchart of another notification synchronization method provided in an embodiment of the present application;

[0073] FIG15 is a schematic flowchart of another notification synchronization method provided in an embodiment of the present application;

[0074] FIG16 is a schematic flowchart of another notification synchronization method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0075] The technical solutions of this application will be described below in conjunction with the accompanying drawings. Obviously, the embodiments described are only part of the embodiments of this application, rather than all the embodiments.

[0076] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings in the embodiments of the present application. In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "plurality" or "multiple" refers to two or more than two.

[0077] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood to indicate or imply relative importance or implicitly specify the number of the technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.

[0078] The terms used in the following embodiments are only for the purpose of describing specific embodiments and are not intended to limit the present application. As used in the specification of this application and the appended claims, the singular expressions "a", "an", "said", "above", "the" and "this" are intended to also include expressions such as "one or more", unless there is a clear contrary indication in the context. It should also be understood that in the following embodiments of the present application, "at least one", "one or more" refer to one, two or more. The term "and / or" is used to describe the association relationship of associated objects, indicating that three relationships can exist; for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and subsequent associated objects are in an "or" relationship.

[0079] References to "one embodiment" or "some embodiments" in this specification mean that a particular feature, structure, or characteristic described in conjunction with that embodiment is included in one or more embodiments of the present application. Thus, phrases such as "one embodiment," "some embodiments," "another embodiment," and "other embodiments" appearing in various places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically stated. The terms "including," "comprising," "having," and variations thereof mean "including but not limited to," unless otherwise specifically stated.

[0080] The method provided in the embodiments of the present application can be applied to electronic devices such as mobile phones, tablet computers, wearable devices, in-vehicle devices, augmented reality (AR) / virtual reality (VR) devices, laptop computers, ultra-mobile personal computers (UMPCs), netbooks, and personal digital assistants (PDAs). The embodiments of the present application do not impose any restrictions on the specific types of electronic devices.

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

[0082] It should be understood that the structures illustrated in the embodiments of the present application do not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

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

[0084] The controller may be the nerve center and command center of the electronic device 100. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

[0085] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

[0086] In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface.

[0087] The USB interface 130 is an interface that complies with USB standards and may be a Mini USB interface, a Micro USB interface, a USB Type-C interface, or the like. The USB interface 130 can be used to connect a charger to charge the electronic device 100, or to transfer data between the electronic device 100 and peripheral devices. It can also be used to connect headphones to play audio. This interface can also be used to connect other electronic devices, such as augmented reality devices.

[0088] It is understood that the interface connection relationship between the modules illustrated in the embodiments of the present application is merely an illustrative illustration and does not constitute a structural limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection methods from the above embodiments, or a combination of multiple interface connection methods.

[0089] The charging management module 140 is configured to receive charging input from a charger. The charger can be either a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input via the wireless charging coil of the electronic device 100. While charging the battery 142, the charging management module 140 can also provide power to the electronic device via the power management module 141.

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

[0091] The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

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

[0093] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

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

[0095] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the electronic device 100. The wireless communication module 160 can be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

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

[0097] Electronic device 100 implements display functionality through a GPU, display screen 194, and an application processor. A GPU is a microprocessor for image processing that connects display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or modify display information.

[0098] Display screen 194 is used to display images, videos, and the like. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-oLed, or a quantum dot light-emitting diode (QLED). In some embodiments, electronic device 100 may include one or N display screens 194, where N is a positive integer greater than one.

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

[0100] The ISP processes data fed back by camera 193. For example, when taking a photo, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, which is then passed to the ISP for processing and converted into a visible image. The ISP can also perform algorithmic optimization on image noise, brightness, and skin tone. It can also optimize parameters such as exposure and color temperature of the captured scene. In some embodiments, the ISP can be located within camera 193.

[0101] The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, and then passes the electrical signal to the ISP for conversion into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the electronic device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0102] The digital signal processor is used to process digital signals. In addition to processing digital image signals, it can also process other digital signals. For example, when the electronic device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0103] Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. This allows electronic device 100 to play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, and MPEG4.

[0104] The NPU is a neural network (NN) computing processor. Drawing on the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it rapidly processes input information and can continuously self-learn. The NPU can enable intelligent cognitive applications in electronic device 100, such as image recognition, face recognition, speech recognition, and text comprehension.

[0105] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 via the external memory interface 120 to implement data storage functions. For example, files such as music and videos can be stored on the external memory card.

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

[0107] The electronic device 100 can implement audio functions such as music playback and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

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

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

[0110] The receiver 170B, also called a "handset", is used to convert audio electrical signals into sound signals. When the electronic device 100 receives a call or a voice message, the user can place the receiver 170B close to the ear to hear the voice.

[0111] Microphone 170C, also known as "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak by putting their mouth close to the microphone 170C to input the sound signal into the microphone 170C. The electronic device 100 can be provided with at least one microphone 170C. In other embodiments, the electronic device 100 can be provided with two microphones 170C, which can not only collect sound signals but also realize noise reduction function. In other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify the source of sound, realize directional recording function, etc.

[0112] The headphone jack 170D is used to connect a wired headphone and can be the USB interface 130 or a 3.5mm open mobile terminal platform (OMTP) standard interface or a cellular telecommunications industry association of the USA (CTIA) standard interface.

[0113] The buttons 190 include a power button, a volume button, and the like. The buttons 190 may be mechanical buttons or touch buttons. The electronic device 100 may receive key inputs and generate key signal inputs related to user settings and function control of the electronic device 100.

[0114] Motor 191 can generate vibration prompts. Motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. For touch operations acting on different areas of the display screen 194, motor 191 can also correspond to different vibration feedback effects. Different application scenarios (for example: time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

[0115] The indicator 192 may be an indicator light, which may be used to indicate the charging status, power level changes, messages, missed calls, notifications, etc.

[0116] The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to or disconnected from the electronic device 100 by inserting it into or removing it from the SIM card interface 195. The electronic device 100 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, and the like. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the multiple cards can be the same or different. The SIM card interface 195 can also be compatible with different types of SIM cards. The SIM card interface 195 can also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement functions such as calls and data communications. In some embodiments, the electronic device 100 uses an embedded SIM (eSIM) card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

[0117] It should be understood that the phone cards in the embodiments of the present application include but are not limited to SIM cards, eSIM cards, universal subscriber identity modules (USIM), universal integrated circuit cards (UICC), and the like.

[0118] The software system of the electronic device 100 can adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. In the embodiment of the present application, the Android system with a layered architecture is used as an example to illustrate the software structure of the electronic device 100.

[0119] Figure 2 is a software structure diagram of the electronic device 100 according to an embodiment of the present application. The layered architecture divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, namely, the application layer, the application framework layer, the Android runtime (Android runtime) and the system library, and the kernel layer, from top to bottom. The application layer can include a series of application packages.

[0120] As shown in FIG2 , the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and short message.

[0121] The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0122] As shown in FIG2 , the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, and the like.

[0123] The window manager is used to manage window programs. The window manager can obtain the display size, determine whether there is a status bar, lock the screen, take screenshots, etc.

[0124] Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0125] The view system includes visual controls, such as those for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views. For example, a display interface containing a text notification icon might include a view for displaying text and a view for displaying images.

[0126] The phone manager is used to provide communication functions of the electronic device 100, such as management of call status (including answering, hanging up, etc.).

[0127] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0128] The Notification Manager allows applications to display notifications in the status bar. These messages can be displayed briefly and then disappear automatically without user interaction. For example, the Notification Manager is used to notify users of completed downloads and message reminders. The Notification Manager can also display notifications in the top status bar of the system as icons or scrolling text, such as notifications from background applications, or as dialog windows on the screen. Examples include text messages in the status bar, beeps, vibrations on electronic devices, and flashing indicator lights.

[0129] Android Runtime includes core libraries and a virtual machine. Android runtime is responsible for scheduling and management of the Android system.

[0130] The core library consists of two parts: one is the function that needs to be called by the Java language, and the other is the Android core library.

[0131] The application layer and application framework layer run in a virtual machine. The virtual machine executes Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

[0132] The system library can include multiple functional modules, such as a surface manager, media libraries, a 3D graphics processing library (such as OpenGL ES), and a 2D graphics engine (such as SGL).

[0133] The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

[0134] The media library supports playback and recording of a variety of common audio and video formats, as well as static image files. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0135] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0136] A 2D graphics engine is a drawing engine for 2D drawings.

[0137] The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, camera driver, audio driver, and sensor driver.

[0138] It should be understood that the technical solutions in the embodiments of the present application can be used in Android, IOS, Hongmeng and other systems.

[0139] The technical solutions of the embodiments of the present application can be applied to electronic devices with message notification functions. For example, they can be applied to televisions, desktop computers, laptops, and car screens. They can also be applied to portable electronic devices such as mobile phones, folding screens, tablet computers, cameras, video cameras, video recorders, watches, and bracelets. They can also be applied to other electronic devices with message notification functions, such as speakers, and can also be applied to electronic devices in 5G networks or electronic devices in future evolved public land mobile communication networks (PLMNs). The main application scenario can be a message notification management scenario for multiple devices. For example, it can be applied to the message notification management scenario for multiple devices in Huawei Super Terminal.

[0140] In order to more clearly understand the solution of the present application, the relevant terms involved in the embodiments of the present application are first introduced below.

[0141] 1. HyperTerminal

[0142] HyperTerminal is a unique feature of HarmonyOS that enables fast connection and collaborative operation between mobile phones and Huawei devices. It automatically discovers nearby devices logged into the same Huawei account, forming a HyperTerminal to create a full-scenario collaborative experience. Users can easily control multiple systems simultaneously without having to operate them one by one, improving user convenience. In other words, a HyperTerminal refers to a group of trusted smart devices within the same device. These devices automatically discover and network together when they are in close proximity. Devices within the HyperTerminal connect to each other and exchange data without authentication, creating a full-scenario multi-device intelligent collaboration experience.

[0143] HyperTerminal can be used to connect multiple smart devices (such as mobile phones, watches, tablets, computers, car displays, etc.) together, thereby realizing multi-device collaborative management and resource sharing. For example, the "pull and close" connection method of the HyperTerminal can be used to achieve collaboration between two or more devices.

[0144] The message notification function of an electronic device is designed to remind users of communication information from others or other real-time information in an application. Users can open the application by tapping the notification displayed on the screen of the electronic device, or perform related operations directly from the notification.

[0145] Currently, for single-device notification scenarios, notifications are primarily sent via cloud push or local apps. For cross-device notifications, the inter-device notification synchronization strategy depends on customized scenarios. Examples include scenarios involving synchronization of phone and watch notifications, synchronization of phone and earphone notifications, multi-screen collaboration, and multi-device collaboration.

[0146] 3 to 6 , a notification synchronization method that relies on customized scenario implementation is introduced below.

[0147] FIG3 shows a schematic diagram of notification synchronization corresponding to a scenario where notifications are synchronized between a mobile phone and a watch.

[0148] As shown in Figure 3, the mobile phone 300 and the watch 301 can be paired through the sports health APP. After the pairing is completed, the user can authorize the watch 301 to be notified in the message notification setting interface of the mobile phone 300 (as shown in (a) in Figure 3). The sports health APP on the watch 301 subscribes to the system notifications on the mobile phone 300 according to the user's authorization. For example, when the user opens the notification permission of the information application for the watch 301 in the message notification setting interface of the mobile phone 300, when the notification of the information application is displayed on the display screen of the mobile phone 300, the display screen of the watch 301 will synchronously display the notification (as shown in (b) and (c) in Figure 3).

[0149] In this scenario, the collaborative management of notifications between devices requires a separate APP to customize the processing, resulting in a geometric increase in the complexity of notification collaboration between multiple devices.

[0150] FIG4 shows a notification synchronization diagram corresponding to a scenario where notifications are synchronized between a mobile phone and a cockpit.

[0151] As shown in Figure 4, the mobile phone 400 and the car screen 410 can be distributedly paired through the super desktop. After the pairing is completed, when the user opens a super desktop application on the car screen 410, the desktop of the mobile phone 400 will read the notification of the application and synchronize it to the car screen 410. For example: when the user opens the information application on the car screen 410, after the information application of the mobile phone 400 receives the notification, its desktop will read the notification and synchronize it to the car screen 410 (as shown in (a), (b) and (c) in Figure 4), where (b) and (c) in Figure 4 are two ways of synchronously displaying notifications on the car display screen.

[0152] In this scenario, applications that support notification synchronization are limited to instant messaging applications such as Changlian, WeChat, and QQ.

[0153] FIG5 shows a schematic diagram of notification synchronization corresponding to a scenario where notifications are synchronized between a mobile phone and a tablet.

[0154] As shown in Figure 5, the mobile phone 500 and the tablet 510 can achieve multi-screen collaboration in the form of a super terminal (as shown in (a) in Figure 5). After achieving multi-screen collaboration, the distributed service (PCASsssistant) module of the mobile phone 500 will subscribe to instant messaging notifications and text messages from the notification service of the mobile phone 500. When the mobile phone 500 receives a notification, the notification is transmitted to the tablet 510 through the soft bus and synchronously displayed in the notification center of the tablet 510, or displayed in a pop-up window on the screen of the tablet 510 (as shown in (b) in Figure 5 and (c) in Figure 5).

[0155] FIG6 shows a notification synchronization diagram corresponding to a scenario where notifications of a mobile phone and a headset are synchronized.

[0156] As shown in Figure 6, the mobile phone 600 and the headset 610 can be paired and connected via Bluetooth. After the connection is completed, the audio product manager of the mobile phone 600 can subscribe to flight, itinerary and other notifications from the notification service of the mobile phone 600. When the notification is displayed on the screen of the mobile phone 600, the headset 610 will broadcast the notification synchronously. The headset can be replaced with a Bluetooth speaker.

[0157] Therefore, in the current multi-device notification synchronization method, the notification synchronization strategy between devices relies on customized scenarios, and the notification management rules are single. The presentation and reminders of notifications lack a good management and control mechanism, and there are many notifications and they are chaotic. For example: when a device can receive remote notifications from the cloud and local distributed cross-device notifications, a notification conflict scenario will occur; the notifications under the device account system and the application account system cannot be well coordinated (for example: in the mobile phone and PC notification synchronization scenario, when the device accounts of the mobile phone and PC are the same, there are scenarios with different application accounts, and there is a risk of privacy leakage); when there are more than three devices, it is difficult to achieve coordinated reminders and system control of notification status, which affects the user's multi-device usage experience.

[0158] In view of this, an embodiment of the present application provides a method and electronic device for notification synchronization, which can realize unified cross-device collaborative notification management between multiple devices, so that notification synchronization between multiple devices can be applicable to the same set of notification synchronization strategies without relying on customized scenarios; and, the method can realize unified distributed scheduling that takes into account both end-cloud collaboration and end-end collaboration, and can solve problems such as "how to avoid repeated reminders of the same notification" and "how to realize collaborative reminders and system control of notification status between multiple devices", where "end" refers to the device end and "cloud" refers to the cloud end.

[0159] For example, FIG7 shows a schematic diagram of a scenario provided in an embodiment of the present application.

[0160] As shown in FIG7 , the scenario applicable to the embodiment of the present application is that multiple electronic devices synchronize notifications through an application server and a push cloud, wherein the synchronization process includes end-cloud synchronization (i.e., synchronization between the push cloud and multiple electronic devices) and end-end synchronization (i.e., synchronization between multiple electronic devices). The specific process of the notification generated by the application server being sent to the device for display is as follows:

[0161] S701: The first electronic device requests the push cloud to register a device identifier. After the push cloud registration is completed, the first device identifier is returned to the first electronic device. The first device identifier is the device identifier of the first electronic device, and the first electronic device belongs to multiple electronic devices on the terminal side.

[0162] The multiple electronic devices may be multiple electronic devices networked through a hyper terminal.

[0163] Alternatively, the push cloud may also be referred to as a push server.

[0164] S702: The first electronic device sends the first device identification to the application server.

[0165] Similarly, the second electronic device that has registered its device identification in the push cloud can also send its device identification to the application server.

[0166] Similarly, other electronic devices that have established a connection with the push cloud can also register device identifications and send the registered device identifications to the application server, so that the application server can generate a device identification list.

[0167] The application server may be a third-party application server.

[0168] S703: After generating the first notification, the application server forwards the first notification and the device identification list to the push cloud.

[0169] S704: After receiving the first notification and the device identification list, the push cloud sends the first notification to all electronic devices in the device identification list based on the device identification list.

[0170] For example, Figure 8 shows a schematic diagram illustrating a notification message sending method provided by an embodiment of the present application. As shown in Figure 8, notification messages from third-party applications can only be sent through the push cloud (e.g., the manufacturer's Push cloud) channel, and non-manufacturer remote notification channels (e.g., the third-party message server channel) are disabled, and cannot be sent through the application's own channel.

[0171] For example, FIG9 shows a schematic diagram of a cross-device notification subscription method provided in an embodiment of the present application.

[0172] As shown in FIG9 , multiple electronic devices can be networked based on the Huawei Super Terminal. For example, the multiple electronic devices may include large-screen devices, tablet computers, speakers, headphones, watches, laptop computers, mobile phones, etc.

[0173] The push cloud can preset notification synchronization policies (which can also be described as preset notification synchronization subscription rules). When the notification synchronization policies on the electronic device side need to be updated, the terminal electronic device only needs to synchronize the notification subscription rules from the push cloud side.

[0174] In one example, when a new device joins the current network or a device exits the current network, it is determined that the notification synchronization policy on the electronic device side needs to be updated; in another example, when the notification synchronization policy preset by the push cloud changes, it is determined that the notification synchronization policy on the electronic device side needs to be updated.

[0175] In some embodiments, the notification synchronization subscription rule may be a synchronization rule determined according to the category of the notification. Different categories of the notification correspond to different message values, that is, different levels of importance, and the corresponding reminder methods will also be different.

[0176] In one implementation, a set of notification classification strategies is preset in the electronic device. When the electronic device receives a notification message, it classifies the notification based on the notification classification strategy and then determines the notification synchronization mode.

[0177] In an example, the notification synchronization subscription rule may be the subscription rule shown in Table 1 below.

[0178] Table 1

[0179] Among them, "√" means that as long as they are in the same network, notification messages will be synchronized.

[0180] Among them, "authorization required" means whether to synchronize notification messages based on the user's authorization settings for the application. Taking the information application as an example, if the user authorizes the watch for notification messages under the information application on the mobile phone, then when the information application on the mobile phone receives the notification reminder, the reminder will be synchronized on the watch; for another example, if the user authorizes the car screen for notification messages under the information application on the mobile phone, then when the information application on the mobile phone receives the notification reminder, the reminder will be synchronized on the car screen.

[0181] "Collaboration" refers to the synchronization of notification messages when electronic devices (such as PAD, PC, large screen, etc.) and central devices (such as mobile phones) are in a collaborative state.

[0182] Here, “ / ” indicates that no synchronous reminder of notification message will be given.

[0183] In one example, a mobile phone, watch, PAD, and headset are located in the same network. When the mobile phone receives a notification message, the mobile phone determines that the notification message is an emergency event reminder based on a preset notification classification strategy. The notification message is then synchronized on the mobile phone, watch, PAD, and headset.

[0184] In another example, a mobile phone, watch, PAD, and headphones are located in the same network. When the mobile phone receives a travel notification message, the mobile phone determines that the notification message is a real-time progress reminder based on a preset notification classification strategy. The travel notification message is then synchronized on the headphone end. If the user has authorized the travel application notification reminder for the watch on the mobile phone end, the travel notification message reminder is also synchronized on the watch end; if the user has authorized the mobile phone notification message to the car screen, the travel notification message reminder is also synchronized on the car screen; if the PAD and the mobile phone are in a collaborative state, the travel notification message reminder is also synchronized on the PAD.

[0185] As can be seen from Table 1, in the cross-device notification subscription scenario, unified distributed notification management of multiple devices can be achieved by presetting unified notification synchronization rules in the cloud.

[0186] In some embodiments, when one of multiple electronic devices receives a notification, it will store the notification in a distributed database on this end. The distributed database on this end and the distributed databases of other electronic devices can be synchronized across ends in real time. Based on the distributed database, the notification can be synchronized between trusted devices within the network.

[0187] In some embodiments, the notification synchronization rule may be:

[0188] a) System notifications can be directly forwarded and shared between trusted devices in the HyperTerminal;

[0189] b) For application notifications, cross-device synchronization of notifications must meet relevant conditions. First, user authorization is required. For portable devices (such as watches and cockpits), notification synchronization can be achieved directly after user authorization. For electronic devices without application accounts (such as headphones, speakers, monitors, etc.), a separate system module is required for synchronization control; for electronic devices with independent application accounts (such as PCs, PADs, large screens, etc.), notification end-side synchronization can only be performed when the electronic devices are in a collaborative state.

[0190] In some embodiments, the notification synchronization rule may further include a notification deduplication rule. In one example, the notification deduplication rule may be embodied as follows:

[0191] Since when a portable device (such as a watch, cockpit, etc.) is independently connected to the Internet, it may receive the same message from a third-party application sent by other electronic devices and a push cloud, in an embodiment of the present application, the message identifier received by the device = the device identifier list + the notification identifier. When processing the received message, the notification service module of the device can parse out the notification identifier in the message. If the message corresponding to the notification identifier has been received, the user will not be reminded again.

[0192] In some embodiments, the notification synchronization rule may further include a notification setting information synchronization rule. In one example, the notification setting information synchronization rule may be embodied as follows:

[0193] When a user turns on or off an application notification setting on any one of multiple devices, the setting is automatically stored in a distributed database, and the setting can be automatically synchronized to other devices in the multiple devices. The notification setting may include, for example, ringtone, vibration, and other settings.

[0194] In some embodiments, the notification synchronization rule may further include a notification status information synchronization rule. In one example, the notification status information synchronization rule may be embodied as follows:

[0195] After the notification is synchronized to multiple electronic devices, if the user reads the notification on any of the multiple electronic devices, the status of the notification (read) will be automatically stored in the distributed database, so that the status of the notification can be synchronized among multiple electronic devices based on the distributed database, and then other electronic devices among the multiple electronic devices can cancel the notification synchronously.

[0196] In some embodiments, the notification synchronization rule may further include a notification reminder rule. In one example, the notification reminder rule may be embodied as follows:

[0197] If the mobile device is unlocked, the mobile phone will remind you; if the mobile device is not unlocked and other devices are unlocked, the other devices will remind you and the mobile phone will remind you silently; if the mobile phone and other devices are both unlocked, multiple devices will remind you together.

[0198] For example, FIG10 shows a schematic diagram of a system architecture for notification synchronization provided in an embodiment of the present application.

[0199] As shown in Figure 10, the system includes a push cloud, an application server, a first electronic device and a second electronic device, wherein the system architecture of the first electronic device includes an application layer, a service layer and a data layer, the application layer includes a first user interface, a first setting module, a first push module and a first application, the service layer includes a first notification management module and a first device management module, and the data layer includes a first database; similarly, the system architecture of the second electronic device also includes an application layer, a service layer and a data layer, the application layer includes a second user interface, a second setting module, a second push module and a second application, the service layer includes a second notification management module and a second device management module, and the data layer includes a second database, and the first database and the second database are synchronized across ends, thereby enabling notification message synchronization between the first electronic device and the second electronic device.

[0200] Optionally, the database mentioned above may be a distributed database.

[0201] Among them, the push cloud can be a notification push cloud provided by the device manufacturer, such as Huawei Push Cloud, etc. The push cloud can be understood as a cloud-side module of the notification service, which is responsible for generating the device identification of the device (such as device token), pushing notifications to the device side, and synchronizing notification subscription rules between devices.

[0202] The application server can be a third-party application server, which can be a cloud server built by a third-party application manufacturer. The third-party application can interact with its own cloud server. Usually, the third-party application will interact with its own server for data. After the device identification is registered, the device side corresponding to the third-party application needs to query the device identification of the local device from the database through the device management module and send the device identification to the third-party application server. In this way, the third-party application will form a device identification list with all the received device identifications, and the third-party application server will carry the device identification list when sending a notification message to the push cloud.

[0203] The first user interface, the notification center performs user reminders, user presentation and user interaction of notifications through the first user interface, and the first user interface is used to write the notification status after user interaction (for example, the reading status of the notification) into the first notification management module, which is stored in the first database by the first notification management module, and then the notification status is synchronized to other devices by the first database, such as to the second electronic device.

[0204] The first setting module is used for notification settings. When the user completes the notification settings, the notification settings are written into the first notification management module, which is then stored in the first database. The first database then synchronizes the notification settings to other devices, such as the second electronic device.

[0205] The first push module is used for interaction between the first electronic device and the push cloud. For example, the first push module is used to request the push cloud to register a device identifier, and is also used to receive the first device identifier sent by the push cloud in response to the registration request. The first device identifier is the device identifier of the first electronic device. It is also used to receive notification messages and a list of device identifiers sent by the push cloud, and is also used to store the received notification messages in the first database, and then the first database synchronizes the notification messages to other devices, such as to the second electronic device.

[0206] The first notification management module is responsible for the life cycle management of notification messages, including the reception of notification messages, reminders of notification messages, deduplication of notification messages (i.e. avoiding repeated reminders), subscription of notification messages, storage of setting information of notification messages, and deletion of notification messages.

[0207] The first device management module is responsible for processing the status information of the first device, for example: it is used to register the device identification of the first device with the push cloud, and is also used to provide a query interface for the first device identification; it is also used to monitor the unlocking status of the first device, and store the unlocking status of the first device in the first database, and then the first database synchronizes the unlocking status of the first device to other devices, such as synchronizing it to the second electronic device.

[0208] The first database is used to synchronize the changes in the data in the database (for example, notification setting information, notification reading status, notification lock status, notification content, device identification information, and other related data) to the databases of other electronic devices when the changes occur.

[0209] Similarly, the functions of the second user interface, second setting module, second push module and second application, second notification management module and second device management module, and second database included in the second electronic device are similar to the functions of the first user interface, first setting module, first push module and first application, first notification management module and first device management module, and first database included in the first electronic device. For the sake of brevity, they will not be repeated here.

[0210] For example, FIG11 shows a schematic flow chart of a notification synchronization method 1100 provided in an embodiment of the present application. This method can be applied to a scenario where a first electronic device and a second electronic device are independently connected to a network, and the first electronic device and the second electronic device are in a collaborative state or a non-collaborative state. As shown in FIG11 , the method 1100 includes:

[0211] S1101: When the application server generates a first notification, it sends the first notification and a device identification list to the push cloud, wherein the device identification list includes a first device identification and a second device identification, the first device identification is used to indicate a first electronic device, and the second device identification is used to indicate a second electronic device.

[0212] The first notification may be generated and sent by an application of another device outside the network, for example.

[0213] Among them, the device identification list includes one or more device identifications. Taking the first device identification among the one or more device identifications as an example, the first device identification is used to represent the device identification of the first electronic device. The first device identification is the device identification that the first electronic device requests to register with the push cloud. After the first electronic device obtains the first device identification registered with the push cloud, it sends it to the application server. Similarly, the explanation of each device identification in the one or more device identifications is similar to this. For the sake of brevity, it will not be repeated here.

[0214] Among them, the electronic device is independently connected to the Internet, which can be understood as the electronic device registering the device identification with the push cloud.

[0215] S1102: Based on the first device identification included in the device identification list, the push cloud sends a first notification and the device identification list to the first electronic device.

[0216] S1103: The first electronic device reminds the user of the first notification.

[0217] In some embodiments, the first electronic device may remind the user of the first notification by displaying the first notification on the screen of the first electronic device. The first electronic device may also remind the user of the first notification by issuing a voice prompt, a vibration prompt, etc. This application does not limit this.

[0218] In one scenario, a first electronic device and a second electronic device are in a collaborative state. The first electronic device detects that the device identification list includes the second device identification, and it can be considered that the second electronic device has also received the first notification sent by the push cloud, and the first electronic device does not forward the first notification to the second electronic device; similarly, the second electronic device detects that the device identification list includes the first device identification, and it can be considered that the first electronic device has also received the first notification sent by the push cloud, and the second electronic device does not forward the first notification to the first electronic device.

[0219] In another scenario, the first electronic device and the second electronic device are in a non-cooperative state, and thus no synchronization of notification messages occurs between the first electronic device and the second electronic device.

[0220] S1104: Based on the second device identification included in the device identification list, the push cloud sends the first notification and the device identification list to the second electronic device.

[0221] S1105: The second electronic device reminds the user of the first notification.

[0222] In some embodiments, the second electronic device can remind the user of the first notification by displaying the first notification on the screen of the second electronic device. The second electronic device can also remind the user of the first notification by issuing voice prompts, vibration prompts, etc. This application does not limit this.

[0223] It should be noted that the execution order of S1102 and S1103 and S1104 and S1105 is not limited. For example, S1102 and S1103 can be executed simultaneously or at different times.

[0224] In one embodiment, the way for the first electronic device and the second electronic device to achieve a collaborative state can be that the first electronic device and the second electronic device are networked based on Huawei's super terminal; it can also be that the first electronic device and the second electronic device are networked through mutual authentication; it can also be that the first electronic device and the second electronic device are networked in other ways, and this application does not limit this.

[0225] In an embodiment of the present application, a distributed unified control strategy based on end-cloud collaboration and end-end collaboration is provided. After the application server generates a notification message, the notification message sent to the cloud carries a device identification list, and the push cloud sends the notification message to all devices corresponding to the device identification list respectively. The notification message sent by the push cloud to the electronic device carries the device identification list. In this way, after receiving the notification message, the electronic device can determine which devices the notification message is sent to based on the device identification list, and the electronic device can avoid repeatedly forwarding the notification message to other devices that have received the notification message, thereby avoiding the trouble caused to the user due to the repeated sending of message notifications.

[0226] For example, FIG12 shows a schematic flow chart of another notification synchronization method 1200 provided in an embodiment of the present application. This method can be applied to a scenario where a first electronic device is independently connected to the network, a second electronic device is not independently connected to the network, and the first electronic device and the second electronic device are in a collaborative state. As shown in FIG12 , the method 1200 includes:

[0227] S1201: When the application server generates a first notification, it sends the first notification and a device identification list to the push cloud, wherein the device identification list includes a first device identification, and the first device identification is used to indicate a first electronic device.

[0228] S1202: Based on the first device identification included in the device identification list, the push cloud sends a first notification and the device identification list to the first electronic device.

[0229] S1203: The first electronic device detects that the device identification list does not include the second device identification, and it can be considered that the second electronic device has not received the first notification sent by the push cloud, so the first electronic device forwards the first notification to the second electronic device.

[0230] In some embodiments, the way in which the first electronic device forwards the first notification to the second electronic device can be: the first electronic device stores the first notification in a first database of the local end, and based on cross-device synchronization between the first database and the second electronic device and real-time monitoring of data changes in the second database by the second electronic device, the second electronic device can obtain the first notification.

[0231] S1204: The first electronic device reminds the user of the first notification.

[0232] The explanation of this step is the same as that of S1105 and will not be repeated here for the sake of brevity.

[0233] S1205: After receiving the first notification, the second electronic device determines whether it has received the first notification. If so, it does not remind the user of the first notification. If not, it reminds the user of the first notification.

[0234] In some embodiments, after receiving the first notification, the second electronic device obtains the ID of the first notification by parsing the first notification, and then determines whether the first notification has been received based on the ID of the first notification.

[0235] In an embodiment of the present application, a distributed unified control strategy based on end-cloud collaboration and end-end collaboration is provided. After the application server generates a notification message, the notification message sent to the cloud carries a device identification list, and the push cloud sends the notification message to all devices corresponding to the device identification list respectively. The notification message sent by the push cloud to the electronic device carries the device identification list. In this way, after receiving the notification message, the electronic device can determine which devices the notification message is sent to based on the device identification list, and the electronic device can avoid repeatedly forwarding the notification message to other devices that have received the notification message, thereby avoiding the trouble caused to the user due to the repeated sending of message notifications; and when the electronic device receives the notification message, it can determine whether the notification message has been received. If the notification message has been received, the user will no longer be reminded of the notification message, thereby further avoiding repeated reminders of the notification message and improving the user experience.

[0236] For example, FIG13 shows a schematic flow chart of another notification synchronization method 1300 provided in an embodiment of the present application. This method can be applied to a scenario where a first electronic device and a second electronic device are independently connected to the network, a third electronic device is not independently connected to the network, the first electronic device, the second electronic device, and the third electronic device are in a collaborative state, and the first electronic device is the central device. As shown in FIG13, the method 1300 includes:

[0237] S1301: When the application server generates a first notification, it sends the first notification and a device identification list to the push cloud, wherein the device identification list includes a first device identification and a second device identification, the first device identification is used to indicate a first electronic device, and the second device identification is used to indicate a second electronic device.

[0238] The first notification may be generated and sent by an application of another device outside the network, for example.

[0239] S1302: Based on the first device identification included in the device identification list, the push cloud sends a first notification and the device identification list to the first electronic device.

[0240] S1303: Similarly, based on the second device identification included in the device identification list, the push cloud sends the first notification and the device identification list to the second electronic device.

[0241] S1304: The first electronic device detects that the device identification list includes the second electronic device but does not include the third electronic device. It can be considered that the second electronic device also received the first notification sent by the push cloud, and the third electronic device did not receive the first notification sent by the push cloud. In this case, the first electronic device forwards the first notification to the third electronic device.

[0242] In some embodiments, the way in which the first electronic device forwards the first notification to the third electronic device can be: the first electronic device stores the first notification in a first database of the local end, and based on cross-device synchronization between the first database and the third electronic device and real-time monitoring of data changes in the third database by the third electronic device, the third electronic device can obtain the first notification.

[0243] S1305: The first electronic device reminds the user of the first notification.

[0244] The explanation of this step is the same as that of S1105 and will not be repeated here for the sake of brevity.

[0245] S1306: The second electronic device detects that the device identification list includes the first electronic device, and it can be considered that the first electronic device has also received the first notification sent by the push cloud. Then the first electronic device does not forward the first notification to the second electronic device, but reminds the user of the first notification.

[0246] S1307: After receiving the first notification, the third electronic device determines whether it has received the first notification. If so, it does not remind the user of the first notification. If not, it reminds the user of the first notification.

[0247] In some embodiments, after receiving the first notification, the third electronic device obtains the ID of the first notification by parsing the first notification, and then determines whether the first notification has been received based on the ID of the first notification.

[0248] In one embodiment, the first electronic device, the second electronic device, and the third electronic device may realize a collaborative state by networking based on Huawei's super terminal; or by networking through mutual authentication; or by forming a network in other ways, which is not limited in this application.

[0249] In one example, the first electronic device is a central device (for example, a mobile phone), the second electronic device is an independent application account device (for example, a PC), and the third electronic device is a portable device that is not independently connected to the Internet (for example, a watch). The first electronic device serves as the central device, and the second and third electronic devices synchronize the device status information to the first electronic device, and then the first electronic device synchronizes to the second and third electronic devices; for example, after receiving the first notification, if one of the devices is in an unlocked state, the device will mainly remind the first notification, and the other devices will silently remind the first notification; if the second and third electronic devices have read the first notification, the notification reminders on the three devices will disappear synchronously. If the third electronic device reads the notification first and synchronizes the notification status to other devices, the notification reminders on the first and second electronic devices can be retained, and the notification reminder on the third electronic device will disappear.

[0250] On this basis, if more electronic devices are added to the network, the message synchronization principle of the portable device is the same as that of the third electronic device, and the message synchronization principle of the independent application account device is the same as that of the second electronic device.

[0251] For example, FIG14 shows a schematic flow chart of another notification synchronization method 1400 provided in an embodiment of the present application. As shown in FIG14 , the method 1400 includes:

[0252] S1401: The first device management module requests the first push module to register a first device identifier, where the first device identifier refers to a device identifier of a first electronic device.

[0253] In one implementation, the first device management module sends a first request message to the first push module, where the first request message is used to request registration of the first device identifier.

[0254] S1402: In response to receiving the registration request message sent by the first device management module, the first push module registers the first device identifier with the push cloud.

[0255] In one implementation, the process includes the following steps:

[0256] The first push module requests the push cloud to register the first device identifier, or the first push module forwards the first request message to the push cloud;

[0257] The push cloud generates a first device identifier corresponding to the first electronic device;

[0258] The push cloud sends the first device identifier to the first push module.

[0259] S1403: The first push module sends the first device identification to the first device management module.

[0260] S1404: The first device management module sends the first device identification to the first database, so as to store the first device identification in the first database.

[0261] S1405: The first application queries the first device identification from the first database through the first device management module.

[0262] In one implementation, the process includes the following steps:

[0263] The first application queries the device identification of the first electronic device, ie, the first device identification, from the first database through the query interface provided by the first device management module.

[0264] S1406: The first device management module sends the first device identifier to the first application.

[0265] S1407: The first application sends the first device identifier to the application server.

[0266] S1408: The second device management module requests the second push module to register a second device identifier, where the second device identifier refers to a device identifier of the second electronic device.

[0267] In one implementation, the second device management module sends a second request message to the second push module, where the second request message is used to request registration of the second device identifier.

[0268] S1409: In response to receiving the registration request message sent by the second device management module, the second push module registers the second device identifier with the push cloud.

[0269] In one implementation, the process includes the following steps:

[0270] The second push module requests the push cloud to register the second device identifier, or the second push module forwards the second request message to the push cloud;

[0271] The push cloud generates a second device identifier corresponding to the second electronic device;

[0272] The push cloud sends the second device identifier to the second push module.

[0273] S1410: The second push module sends the second device identification to the second device management module.

[0274] S1411: The second device management module sends the second device identification to the second database to store the second device identification in the second database.

[0275] S1412: The second application queries the second device identification from the second database through the second device management module.

[0276] In one implementation, the process includes the following steps:

[0277] The second application queries the device identification of the second electronic device, ie, the second device identification, through the query interface provided by the second device management module.

[0278] S1413: The second device management module sends the second device identification to the second application.

[0279] S1414: The second application sends the second device identifier to the application server.

[0280] S1415: When the application server generates the first notification, the application server sends the first notification and the device identification list to the push cloud.

[0281] The device identification list may include a first device identification and a second device identification.

[0282] The method of the embodiment of the present application can be applied to a scenario where the first electronic device and the second electronic device are both independently connected to the Internet. When the electronic devices are not independently connected to the Internet, the device identification will not be registered with the push cloud.

[0283] In an embodiment of the present application, the notification message sent by the application server to the push cloud carries the device identifiers of multiple devices served by the application server. In this way, the push cloud can push the notification message to multiple devices based on the multiple device identifiers carried by the notification message; and each of the multiple devices can also determine which devices the notification message has been sent to based on the multiple device identifiers carried by the notification message, thereby avoiding repeated synchronization of the same notification message.

[0284] For example, FIG15 shows a schematic flow chart of another notification synchronization method 1500 provided in an embodiment of the present application. As shown in FIG15 , the method 1500 includes:

[0285] S1501: The application server sends a first notification and a device identification list to the push cloud, where the device identification list includes a first device identification.

[0286] The first notification and the device identification list have a binding relationship, and the specific relationship may be, for example, that the first notification carries the device identification list.

[0287] S1502: Based on the first device identifier, the push cloud sends a first notification and a device identifier list to a first agent module of the first electronic device.

[0288] S1503: The first agent module forwards the first notification and the device identification list to the first notification management module.

[0289] S1504: If the first notification management module detects that the device identification list does not include the second device identification, the first notification management module sends the first notification to the first database. That is, the first notification management module stores the first notification in the first database.

[0290] S1505: The first notification management module sends the first notification to the first user interface, so that the first notification is displayed on the first user interface.

[0291] S1506: A first database of the first electronic device and a second database of the second electronic device are synchronized across devices, and the first notification is synchronized to the second database.

[0292] S1507: The second notification management module of the second electronic device monitors the status change of the second database and detects that a new first notification is added to the second database.

[0293] S1508: The second notification management module sends the first notification to the second user interface, so that the first notification is displayed on the second user interface.

[0294] S1509: In response to the user clicking on the first notification in the first user interface, the first user interface cancels the display of the first notification on the first user interface.

[0295] S1510: The first user interface sends a notification status update message to the first notification management module, indicating that the status of the first notification has changed to a read state.

[0296] S1511: The first notification management module updates the first database, and updates the reading status of the first notification in the first database to read.

[0297] S1512: A first database of the first electronic device and a second database of the second electronic device are synchronized across devices, and the reading status of the first notification is synchronized to the second database.

[0298] S1513: The second notification management module of the second electronic device monitors the status change of the second database, and monitors that the reading status of the first notification in the second database is updated to the read status.

[0299] S1514: The second user interface cancels the display of the first notification on the second user interface.

[0300] In one achievable embodiment, method 1500 is applicable to a scenario where a first electronic device and a second electronic device are located in the same network, the first electronic device is independently connected to the network, and the second electronic device is not independently connected to the network. In this scenario, the first electronic device may be, for example, a mobile phone, and the second electronic device may be, for example, a watch, and the user authorizes the watch to synchronously remind the first notification on the mobile phone.

[0301] In another achievable embodiment, method 1500 is applicable to a scenario in which the first electronic device and the second electronic device are in a collaborative state, the first electronic device and the second electronic device are independently connected to the network, the device account on the first electronic device and the device account on the second electronic device are the same, but the application account on the first electronic device and the application account on the second electronic device are different. In this scenario, the first electronic device can be, for example, a mobile phone, and the second electronic device can be, for example, a PC, and in this scenario, the type of the first notification can be limited to emergency event notifications and system application notifications.

[0302] It can be understood that in the above-mentioned second implementation method, since the application account on the first electronic device is different from the application account on the second electronic device, the second electronic device will not receive the first notification sent by the push cloud, but will receive the first notification synchronized by the first electronic device through the database. On this basis, if the application account of the second electronic device is switched to the same as the application account of the first electronic device, the push cloud will resend the first notification to the second electronic device. At this time, when the second electronic device receives the first notification, the second electronic device can parse the ID of the first notification. Based on the ID of the first notification, it can be determined that the first notification has been received before. Then, after receiving the first notification resent by the push cloud, the second electronic device will no longer send a reminder of the first notification to the user.

[0303] In an embodiment of the present application, a distributed unified control strategy based on end-cloud collaboration and end-end collaboration is provided. For multiple electronic devices in the same network, when a device receives a notification message, it can determine which devices the notification message has been sent to based on the device identification information carried in the notification message. In this case, the notification message will no longer be forwarded to these devices, thereby avoiding these devices from receiving the same notification message multiple times, thereby improving the user experience; and, multiple electronic devices can perform cross-end synchronization of notification messages, notification message status (reading status, etc.) and electronic device status (unlocked status, etc.) through a distributed database, thereby better realizing message collaborative reminders between multiple electronic devices. For example: when one device reads the notification, the notification displayed on the other device disappears synchronously.

[0304] For example, FIG16 shows a schematic flow chart of another notification synchronization method 1600 provided in an embodiment of the present application. As shown in FIG14 , the method 1600 includes:

[0305] S1601: The application server sends a first notification and a device identification list to the push cloud, where the device identification list includes a first device identification and a second device identification.

[0306] S1602: Based on the first device identifier, the push cloud sends a first notification and a device identifier list to a first agent module of the first electronic device.

[0307] S1603: The first agent module forwards the first notification and the device identification list to the first notification management module.

[0308] S1604: If the first notification management module detects that the device identification list includes the second device identification, it can be considered that the second electronic device has received the first notification, and the first notification will not be forwarded to the second electronic device. The first electronic device displays the first notification on the screen of the first electronic device.

[0309] S1605: Based on the second device identification, the push cloud sends the first notification and the device identification list to the second agent module of the second electronic device.

[0310] S1606: The second agent module forwards the first notification and the device identification list to the second notification management module.

[0311] S1607: If the second notification management module detects that the device identification list includes the first device identification, it can be considered that the first electronic device has received the first notification, and the first notification will not be forwarded to the first electronic device. The second electronic device displays the first notification on the screen of the second electronic device.

[0312] S1608: In response to the user clicking on the first notification in the first user interface, the first user interface cancels the display of the first notification on the first user interface.

[0313] S1609: The first user interface sends a notification status update message to the first notification management module, indicating that the status of the first notification has changed to a read state.

[0314] S1610: The first notification management module updates the first database, and updates the reading status of the first notification in the first database to read.

[0315] S1611: A first database of the first electronic device and a second database of the second electronic device are synchronized across devices, and the reading status of the first notification is synchronized to the second database.

[0316] S1612: The second notification management module of the second electronic device monitors the status change of the second database, and monitors that the reading status of the first notification in the second database is updated to the read status.

[0317] S1613: The second user interface cancels the display of the first notification on the second user interface.

[0318] In one achievable embodiment, method 1600 is applicable to a scenario in which the first electronic device and the second electronic device are located in the same network, the first electronic device and the second electronic device may be in a collaborative state or a non-collaborative state, the first electronic device and the second electronic device are both independently connected to the network, the device accounts of the first electronic device and the second electronic device are the same, and the application accounts of the first electronic device and the second electronic device are the same. In this scenario, the first electronic device may be, for example, a mobile phone, and the second electronic device may be, for example, a watch or a PC.

[0319] It can be understood that: in this implementation, if the first electronic device and the second electronic device are not located in the same network (for example, they do not form a super terminal), the first electronic device and the second electronic device each receive the first notification sent by the push cloud, and each processes the first notification. The notification status (reading status, etc.) of the first notification is not synchronized. Once the first electronic device and the second electronic device are located in the same network, the notification status will be immediately synchronized through cross-end synchronization of the first database of the first electronic device and the second database of the second electronic device.

[0320] It should be understood that the embodiment of the present application is introduced with the synchronization of notification messages between two electronic devices, but this does not constitute any limitation on the scenarios to which the solutions of the embodiments of the present application are applicable. The solutions provided by the embodiments of the present application can also be applied to the synchronization scenarios of notification messages between multiple electronic devices.

[0321] One or more of the modules or units described herein can be implemented in software, hardware, or a combination of the two. When any of the above modules or units is implemented in software, the software exists in the form of computer program instructions and is stored in a memory, and a processor can be used to execute the program instructions and implement the above method flow. The processor may include, but is not limited to, at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller (MCU), or an artificial intelligence processor, etc., a computing device that runs software, each computing device may include one or more cores for executing software instructions to perform operations or processing. The processor may be built into an SoC (system on chip) or an application specific integrated circuit (ASIC), or it may be an independent semiconductor chip. In addition to the core for executing software instructions to perform operations or processing within the processor, it may further include necessary hardware accelerators, such as a field programmable gate array (FPGA), a PLD (programmable logic device), or a logic circuit that implements dedicated logic operations.

[0322] When the modules or units described in this document are implemented in hardware, the hardware can be any one or any combination of a CPU, a microprocessor, a DSP, an MCU, an artificial intelligence processor, an ASIC, a SoC, an FPGA, a PLD, a dedicated digital circuit, a hardware accelerator, or a non-integrated discrete device, which can run the necessary software or not rely on the software to execute the above method flow.

[0323] When the modules or units described herein are implemented using software, they can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium can be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

[0324] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0325] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0326] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0327] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0328] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0329] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0330] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for notification synchronization, characterized in that, The method includes: A first electronic device receives a first notification and a device identifier list sent by a push server. The first electronic device logs in to a first application through a first account. The device identifier list includes device identifiers of one or more electronic devices that have logged in to the first application through the first account. The first notification is a notification corresponding to the first account of the first application. When the device identifier list does not include the device identifier of a second electronic device, the first electronic device synchronizes the first notification to the second electronic device; or When the device identifier list includes the device identifier of the second electronic device, the first electronic device does not synchronize the first notification to the second electronic device. The second electronic device and the first electronic device are in the same network.

2. The method according to claim 1, wherein The device identifier list includes the device identifier of the first electronic device.

3. The method according to claim 1 or 2, characterized in that, The first electronic device synchronizing the first notification to the second electronic device includes: The first electronic device synchronizes the first notification to the database of the second electronic device through the database of the first electronic device.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The first electronic device determines whether it has received the first notification; If the first electronic device determines that it has not received the first notification, the first electronic device issues a reminder of the first notification to the user.

5. The method according to any one of claims 1 to 4, characterized in that, Before the first electronic device receives the first notification and the device identifier list sent by the push server, the method further includes: The first electronic device sends the device identifier of the first electronic device to the application server of the first application, so that when the application server of the first application generates the first notification, it sends the first notification and the device identifier of the first electronic device to the push server. The device identifier of the first electronic device is used by the application server to send the notification corresponding to the first account of the first application to the first electronic device through the push server.

6. The method according to claim 5, wherein Before the first electronic device sends the device identifier of the first electronic device to the application server of the first application, the method further includes: The first electronic device sends a first request message to the push server. The first request message is used to request registration of the device identifier of the first electronic device. The first electronic device receives the device identifier of the first electronic device sent by the push server.

7. The method according to any one of claims 1 to 6, characterized in that, After the first electronic device synchronizes the first notification to the second electronic device, the method further includes: When the status of the first notification changes, the first electronic device synchronizes the status of the first notification to the second electronic device.

8. The method according to claim 7, characterized in that The first electronic device synchronizing the status of the first notification to the second electronic device includes: The first electronic device updates the status of the first notification to the database of the first electronic device, and the databases of the first electronic device and the second electronic device are cross - end synchronized.

9. A method for notification synchronization, characterized in that, The method includes: The push server receives a first notification and a device identifier list sent by the application server of the first application. The device identifier list includes the device identifiers of one or more electronic devices that have logged in to the first application through a first account. The device identifier list includes the device identifier of a first electronic device. The first notification is a notification corresponding to the first account of the first application. Based on the device identifier of the first electronic device, the push server sends the first notification and the first device identifier list to the first electronic device. The first device identifier list is the same as the device identifier list, or the first device identifier list includes all the device identifiers in the device identifier list except the device identifier of the first electronic device.

10. The method according to claim 9, characterized in that, When the device identifier list includes the device identifier of a second electronic device, the method further includes: Based on the device identifier of the second electronic device, the push server sends the first notification and the second device identifier list to the second electronic device. The second device identifier list is the same as the device identifier list, or the second device identifier list includes all the device identifiers in the device identifier list except the device identifier of the second electronic device.

11. The method according to claim 9 or 10, characterized in that, Before the push server receives the first notification and the device identifier list sent by the application server of the first application, the method further includes: The push server receives a first request message sent by the first electronic device. The first request message is used to request registration of the device identifier of the first electronic device. The push server sends the device identifier of the first electronic device to the first electronic device, so that the first electronic device sends the device identifier of the first electronic device to the application server of the first application. Further, when the application server of the first application generates the first notification, the application server of the first application sends the first notification and the device identifier of the first electronic device to the push server.

12. A method for notification synchronization, characterized in that, The method includes: After generating a first notification, the application server of the first application sends the first notification and a device identifier list to the push server. The device identifier list includes the device identifiers of one or more electronic devices that have logged in to the first application through a first account. The device identifier list is used for the push server to send the first notification and the device identifier list to the one or more electronic devices. The first notification is a notification corresponding to the first account of the first application.

13. The method according to claim 12, characterized in that, When the device identifier list includes the device identifier of the first electronic device, before sending the first notification and the device identifier list to the push server, the method further includes: The application server of the first application receives the device identifier of the first electronic device sent by the first electronic device.

14. The method according to claim 12 or 13, characterized in that, When the device identifier list includes the device identifier of the second electronic device, before sending the first notification and the device identifier list to the push server, the method further includes: The application server of the first application receives the device identifier of the second electronic device sent by the second electronic device.

15. An electronic device, characterized in that, Includes: One or more processors; one or more memories; and one or more computer programs, wherein the one or more computer programs are stored in the one or more memories, and the one or more computer programs include instructions that, when executed by the one or more processors, cause the electronic device to perform the method according to any one of claims 1 to 8, or perform the method according to any one of claims 9 to 11, or perform the method according to any one of claims 12 to 14.

16. A system, characterized in that, The system includes one or more first electronic devices, a push server, and an application server. The first electronic device is configured to perform the method according to any one of claims 1 to 8, the push server is configured to perform the method according to any one of claims 9 to 11, and the application server is configured to perform the method according to any one of claims 12 to 14.

17. A computer-readable storage medium, characterized in that, A program or instructions are stored in the storage medium, and when the program or instructions are run, the method according to any one of claims 1 to 8 is implemented, or the method according to any one of claims 9 to 11 is implemented, or the method according to any one of claims 12 to 14 is implemented.

18. A chip, characterized in that, Instructions are stored in the chip, and when the instructions are run, the method according to any one of claims 1 to 8 is implemented, or the method according to any one of claims 9 to 11 is implemented, or the method according to any one of claims 12 to 14 is implemented.

Images