Message notification method, user interface, and related apparatus

Abstract

The present application discloses a message notification method, a user interface, and a related apparatus. The method comprises: a first device displays a first notification message; when identifying an event that a user triggers to push the first notification message again, the first device sends the message content of the first notification message to a second device; and when meeting a first condition, the second device displays a second notification message, wherein the message content of the second notification message is identical to that of the first notification message, the first condition may comprise one or more of the following: lighting up a screen, unlocking, starting a first application, changing the orientation of a device, switching a display screen or changing the folding form of the device, and the first application is a source application of the first notification message, or an application indicated by the first notification message, or an application selected by a user. In this way, notification messages can be pushed across the devices again, so that a plurality of devices can display the notification messages in a linkage manner, and thus a user avoids missing the notification messages pushed by the devices.

Description

Message notification methods, user interfaces and related devices

[0001] This application claims priority to Chinese Patent Application No. 202410685602.9, filed on May 29, 2024, entitled "Message Notification Method, User Interface and Related Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of terminals, and in particular to message notification methods, user interfaces, and related devices. Background Technology

[0003] To help users stay informed about relevant information within applications, electronic devices can display push notifications as a banner, briefly hovering above the screen. However, this notification is only displayed once and will not reappear. If the user's attention is not on the notification during its display, they may miss it, affecting their ability to process it. Summary of the Invention

[0004] This application provides a message notification method, user interface, and related devices, which enables the re-pushing of notification messages and minimizes the chance of users missing notification messages.

[0005] In a first aspect, embodiments of this application provide a message notification method, the method comprising: a first device displaying a first notification message; upon recognizing a first event, the first device sending the message content of the first notification message to a second device; the second device displaying a second notification message, wherein the message content of the second notification message is the same as that of the first notification message, when the second device satisfies a first condition; wherein the first condition includes one or more of the following: screen on, unlocking, reaching a first time, launching a first application, changing the device posture, switching the display screen, or changing the device folding form, wherein the first application is the source application of the first notification message, or the application indicated by the first notification message, or the application selected by the user.

[0006] Implementing the method provided in the first aspect can enable the push of notification messages across devices again. This is also because users usually carry multiple devices. Using the method provided in the embodiments of this application can solve the problem that when users are using multiple devices, notification messages will not be pushed across devices, causing users to miss notification messages, and realizes the linkage of multiple devices in pushing notification messages.

[0007] In conjunction with the first aspect, in one possible implementation, if the second device meets the first condition, the second device displays the second notification message, specifically including: the second device displays the second notification message when it is determined that the second device meets the first condition; or, the first device sends the message content of the first notification message to the second device, specifically including: the first device sends the message content of the first notification message to the second device when it is determined that the second device meets the first condition.

[0008] In other words, the first device can determine whether the second device meets the first condition, and the second device can determine whether it meets the first condition.

[0009] In conjunction with the first aspect, in one possible implementation, while the second device displays the second notification message, it also includes: the second device displaying a first prompt message on the second notification message, the first prompt message being used to indicate that the message content of the second notification message comes from the first device.

[0010] In this way, users viewing the second device can learn from the first prompt information on the second notification message that the second notification message is a message pushed again across devices.

[0011] In conjunction with the first aspect, in one possible implementation, after the second device displays the second notification message, the method further includes: the second device detecting a first operation acting on the second notification message; and the second device responding to the first operation by launching a second application or displaying a first page, wherein the second application is the application indicated by the jump information in the first notification message, and the first page is the page indicated by the jump information in the first notification message.

[0012] In other words, when a notification message originating from the first device is pushed by a second device, the second device can trigger a jump to the notification message based on the user's jump operation on the notification message, and view the message content of the notification message, thus realizing cross-device processing of the notification message. In this way, the user does not need to know whether the notification message pushed on the second device comes from another device, expanding the application of notification messages in cross-device push scenarios.

[0013] In conjunction with the first aspect, in one possible implementation, after the second device displays the second notification message, the method further includes: the second device detecting a first operation acting on the second notification message; the second device sending indication information of the first operation to the first device; the first device responding to the first operation by launching a second application or displaying a first page, wherein the second application is the application indicated by the jump information in the first notification message, and the first page is the page indicated by the jump information in the first notification message; the first device sending the content to be displayed after launching the second application or the first page to the second device; and the second device displaying the content to be displayed after launching the second application or the first page.

[0014] In other words, when the second device pushes a notification message from the first device, the second device can return the instruction information of the jump operation to the first device based on the user's jump operation on the notification message. The first device then responds to the jump operation to trigger the jump of the first notification message and displays the relevant content after the jump of the first notification message. In this way, the second device can display the relevant content after the jump of the first device through the first notification message through multi-screen collaboration.

[0015] In conjunction with the first aspect, in one possible implementation, the second device sends the instruction information for the first operation to the first device, specifically including: the second device sending the instruction information for the first operation to the first device when the second application is not installed.

[0016] In other words, even if the second device does not have the corresponding application installed, it can still display the page corresponding to the notification message after the jump through multi-screen collaboration. In this way, even if the second device does not have the corresponding application installed, it can still successfully respond to the user's jump operation and display the page corresponding to the notification message after the jump, so that the user can understand the details of the notification message and process the notification message.

[0017] In conjunction with the first aspect, in one possible implementation, after the second device displays the second notification message, the method further includes: the second device detecting a first operation acting on the second notification message; the second device launching a third application if the second application is not installed; the second application is the application indicated by the jump information in the first notification message, and the third application has the same functionality as the second application.

[0018] In other words, if the second device does not have the application corresponding to the second notification message installed, when the second device detects a jump operation acting on the second notification message, it can open an application similar to the application corresponding to the second notification message. In this way, even if the second device does not have the application corresponding to the second notification message installed, the second device can still achieve the jump of the notification message.

[0019] Secondly, embodiments of this application provide a message notification method, the method comprising: a first device displaying a first notification message; the first device identifying a first event; the first device displaying a third notification message when the first device meets a first condition, the third notification message having the same message content as the first notification message; wherein the first condition includes one or more of the following: screen on, unlocking, reaching a first time, launching a first application, changing the device posture, switching the display screen, or changing the device folding form, wherein the first application is the source application of the first notification message, or the application indicated by the first notification message, or the application selected by the user.

[0020] Implementing the method provided in the second aspect enables the notification message to be pushed again, preventing users from missing notification messages.

[0021] In one possible implementation, combining the first and second aspects, the first event is a user action that triggers the notification message to be displayed again; or, the first event is an event in which the first device does not receive an operation applied to the first notification message during the display of the first notification message; or, the first event is an event in which the user gazes at the first notification message for less than a first threshold.

[0022] In conjunction with the first and second aspects, in one possible implementation, the user operation that triggers the notification message to be displayed again includes: a second operation acting on the first notification message; a third operation acting on the first option among the multiple options after the first device displays multiple options in response to the second operation; wherein the multiple options are used to indicate different conditions, and the first option is used to indicate a first condition.

[0023] In other words, the first device can select a first condition from multiple conditions based on user actions, and initiate a re-push of the notification message when the specified conditions determined by the user are met. This allows the timing of the re-push of the notification message to be determined according to the user's wishes, improving user operability.

[0024] In one possible implementation, combining the first and second aspects, the first condition is determined based on one or more of the following: the type of the first notification message, the push time, and the importance; or, the first condition is a condition preset by the first device.

[0025] In conjunction with the first and second aspects, in one possible implementation, the first device displays the first notification message, specifically including: the first device displays the first notification message in the form of a banner, or displays the first notification message in the notification bar, or displays the first notification message on the lock screen.

[0026] Thirdly, embodiments of this application provide a message notification method, which includes: a first device displaying a first notification message; and when a first event is detected, the first device sending the message content of the first notification message to a second device.

[0027] Fourthly, embodiments of this application provide a message notification method, which includes: a second device receiving the message content of a first notification message; the second device displaying a second notification message when the second device meets a first condition; the second notification message having the same message content as the first notification message; wherein the first condition includes one or more of the following: screen on, unlocking, reaching a first time, launching a first application, changing the device posture, switching the display screen, or changing the device folding form; wherein the first application is the source application of the first notification message, or the application indicated by the first notification message, or the application selected by the user.

[0028] Fifthly, embodiments of this application provide an electronic device, including a memory, one or more processors, and one or more programs; when the one or more processors execute the one or more programs, the electronic device causes the electronic device to implement the methods described in the second aspect or any of the implementations of the second aspect, the third aspect, or the fourth aspect.

[0029] Sixthly, embodiments of this application provide a computer-readable storage medium including instructions that, when executed on an electronic device, cause the electronic device to perform the methods described in the second aspect or any of the implementations of the second aspect, the third aspect, or the fourth aspect.

[0030] In a seventh aspect, embodiments of this application provide a computer program product that, when run on a computer, causes the computer to execute the methods described in the second aspect or any of the implementations of the second aspect, the third aspect, or the fourth aspect. Attached Figure Description

[0031] Figure 1 illustrates a communication system 1000 provided in an embodiment of this application.

[0032] Figures 2A-2G, 3A-3B, 4A-4B, 5A-5B, 6A-6C, 7A-7C, 8A-8D, and 9 show some user interfaces provided in the embodiments of this application;

[0033] Figure 10 is a flowchart illustrating a message notification method provided in an embodiment of this application;

[0034] Figure 11 is a module interaction diagram of electronic device 100 and electronic device 200 involved in the message notification method provided in the embodiments of this application;

[0035] Figure 12 is a diagram of the module interactions involved in electronic device 200 when application X is installed and a notification message is triggered.

[0036] Figure 13 is a module interaction diagram between electronic device 100 and electronic device 200 during the process of jumping to a notification message through screen projection provided in the embodiments of this application.

[0037] Figure 14 is a flowchart illustrating another message notification method provided in an embodiment of this application;

[0038] Figure 15 is a module interaction diagram of the electronic device 100 provided in this application pushing a notification message again when the specified conditions are met.

[0039] Figure 16 is a schematic diagram of the hardware structure of the electronic device 300 provided in an embodiment of this application;

[0040] Figure 17 is a software structure block diagram of an electronic device 300 according to an embodiment of this application. Detailed Implementation

[0041] The technical solutions in the embodiments of this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; the word "and / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0042] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.

[0043] The term "user interface (UI)" used in the following embodiments of this application refers to the medium interface through which an application or operating system interacts and exchanges information with the user. It realizes the conversion between the internal form of information and the form that the user can accept. The user interface is source code written in a specific computer language such as Java or Extensible Markup Language (XML). The interface source code is parsed and rendered on the electronic device, ultimately presenting content that the user can recognize. A common form of user interface is the graphical user interface (GUI), which refers to a user interface related to computer operation displayed graphically. It can be visible interface elements such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets displayed on the screen of an electronic device.

[0044] This application provides a message notification method. During the display of a notification message, the method can identify whether the user has triggered the notification message to be pushed again. If the event of the user triggering the notification message to be pushed again is identified, the device or other devices can be controlled to display the notification message again when a specified condition is met, so as to achieve the effect of pushing the notification message again and avoid the user missing the notification message.

[0045] For example, the specified conditions may include one or more of the following: turning on the screen, unlocking, reaching a specified time, launching a specified application, changing the device's orientation, switching displays, changing the device's folding shape, etc.

[0046] Figure 1 shows a communication system 1000 provided in an embodiment of this application.

[0047] As shown in Figure 1, the communication system 1000 may include: electronic device 100 and electronic device 200.

[0048] For example, electronic device 100 and electronic device 200 can refer to devices such as mobile phones, watches, bracelets, tablets, and computers. The device types of electronic device 100 and electronic device 200 can be the same or different. This application embodiment does not limit the device types of electronic device 100 and electronic device 200.

[0049] In this embodiment of the application, electronic device 100 can be a device that displays the notification message for the first time, and electronic device 200 can be a device that displays the notification message again.

[0050] Electronic device 100 and electronic device 200 can establish a communication connection. This communication connection can be wired or wireless. The wireless connection can be a short-range connection such as Wi-Fi, Bluetooth, infrared, NFC, or ZigBee, or a long-range connection, including but not limited to long-range connections based on 2G, 3G, 4G, 5G, and subsequent standard protocols of mobile networks. In one possible implementation, electronic device 100 and electronic device 200 can be considered to have established a communication connection if they are logged into the same account on the same application.

[0051] Electronic device 100 can display a notification message, and during the display process, identify whether there is an event where the user has not paid attention to the notification message. If such an event is identified, electronic device 100 sends the message content of the notification message to electronic device 200. Further optionally, electronic device 100 can send the message content of the notification message to electronic device 200 if it determines that electronic device 200 meets specified conditions.

[0052] After receiving the message content of a notification message, the electronic device 200 can obtain a new notification message based on that message content and display the notification message. Optionally, the electronic device 200 can display the notification message only if it determines that specified conditions are met.

[0053] The specified conditions may include one or more of the following: screen on, unlocking, reaching a specified time, launching a specified application, changing the device's orientation, switching displays, changing the device's folding mode, etc. Detailed descriptions of the specified conditions can be found in subsequent content.

[0054] It is understood that the communication system 1000 shown in Figure 1 may also include more devices, and this application embodiment does not limit this.

[0055] The following describes the user interface for displaying notification messages on electronic device 100 or other devices, such as electronic device 200, under different specified conditions.

[0056] Figures 2A-2C illustrate the user interfaces for displaying notification messages across devices according to embodiments of this application. Figures 2A-2B show the user interface displayed on electronic device 100, and Figure 2C shows the user interface displayed on electronic device 200.

[0057] Figure 2A shows the user interface 10 of the electronic device 100 when displaying notification messages.

[0058] As shown in Figure 2A, the user interface 10 may include a notification message 101. This notification message 101 can be used to display notification messages pushed by the video application (hereinafter referred to as notification message 1). The message content of notification message 101 may include the text information: "The TV series is available online today, click to watch!"

[0059] For example, the notification message 101 can be displayed at the top of the user interface 10. Furthermore, if the electronic device 100 does not detect any user interaction with the notification message 101 while it is being displayed, the notification message 101 can disappear after a short pause.

[0060] It is understood that Figure 2A shows the user interface of the electronic device 100 displaying a notification message on a desktop. If the electronic device 100 is displaying other user interfaces, such as a camera interface or a game interface, and receives a notification message, the electronic device 100 can display the notification message on other user interfaces, such as the camera interface or the game interface. This application embodiment does not limit the user interface on which the electronic device 100 displays the notification message. Furthermore, the notification message shown in Figure 2A is merely an exemplary example. In other embodiments of this application, the application that pushes notification messages, and the notification messages pushed by the application, can be other, and this application embodiment does not limit them.

[0061] Optionally, in addition to displaying notification messages as a banner notification as shown in Figure 2A, the electronic device 100 can also display notification messages in the notification bar. When the electronic device 100 displays a notification message in the notification bar, this notification message can be placed at the top of the list of notification messages already displayed in the notification bar. This allows the user to prioritize viewing the most recently pushed notification messages from the electronic device 100. For example, the electronic device 100 can detect a user's swipe-down gesture from the top of the display screen, triggering the opening of the notification bar. This notification bar can be used to display one or more notification messages pushed by the application, as well as one or more function setting options, such as Wi-Fi settings, mobile network settings, Bluetooth settings, airplane mode settings, etc.

[0062] Optionally, if the electronic device 100 receives the notification message 1 while in a locked screen state, the electronic device 100 can also display the notification message 1 on the lock screen interface.

[0063] During the display of FIG2A on electronic device 100, electronic device 100 can detect user operation on notification message 101, such as long press operation. In response to the operation, electronic device 100 can add option 102 as shown in FIG2B on user interface 10. Option 102 can be used to trigger cross-device notification of notification message.

[0064] It is understood that, in addition to adding an option through user operations on the notification message as shown in Figures 2A-2B, and implementing cross-device notification through operations on that option, the electronic device 100 can also enable cross-device notification of the notification message through other user operations. For example, the notification message displayed by the electronic device 100 may also include a switch, and the electronic device 100 can detect the user's on / off operation on the switch to enable or disable cross-device notification of the notification message. As another example, if the electronic device 100 detects a specified operation on the notification message during the display of the notification message, it can also trigger cross-device notification of the notification message. This application embodiment does not limit the user operations that trigger cross-device notification of the notification message.

[0065] In addition, in some implementations, besides enabling cross-device notifications based on user actions, the electronic device 100 can also determine whether to enable cross-device notifications in other ways. For example, the electronic device 100 can identify the duration of the user's gaze at the notification message during its display and determine whether to enable cross-device notifications based on the duration of that gaze. As another example, the electronic device 100 can determine whether to enable cross-device notifications based on whether no action has been received applied to the notification message during its display.

[0066] As can be seen, whether based on user operation or the duration of user attention to the notification message, the purpose is to identify whether the user has not paid attention to the notification message. In other words, if the electronic device 100 detects that the user has not paid attention to the notification message during the display of the notification message, it can enable cross-device notification of the notification message. For a detailed description of this event, please refer to the subsequent method flow, which will not be elaborated here.

[0067] For example, during the display of the user interface 10 shown in FIG2B, if the electronic device 100 has not established a communication connection with other devices, after the electronic device 100 detects a user operation on option 102, such as a click operation, the electronic device 100 can select a target device for cross-device notification, establish a communication connection with the target device, and then enable cross-device notification of notification message 1 on the target device, that is, push the message content of notification message 1 again on the target device.

[0068] Assuming that electronic device 100 has established a communication connection with electronic device 200 before displaying user interface 10 as shown in FIG2B, after electronic device 100 detects the user operation applied to option 102, electronic device 100 can send the message content of notification message 1 to electronic device 200 so that electronic device 200 can push the message content of notification message 1.

[0069] For example, the electronic device 200 can directly push the message content of notification message 1 after receiving the message content of notification message 1.

[0070] For example, after receiving the message content of notification message 1, electronic device 200 can push the message content of notification message 1 if specified conditions are met. The specified conditions may include one or more of the following: screen on, unlocking, electronic device 100 reaching a specified time, launching a specified application, changing the device posture, switching the display screen, changing the device folding mode, etc.

[0071] Assuming that the electronic device 200 pushes the message content of notification message 1 while the screen is unlocked, and if the user interface 20 shown in Figure 2C is the user interface displayed after the screen of the electronic device 200 is unlocked, then the electronic device 200 can display notification message 201 on the user interface 20 shown in Figure 2C after the screen is unlocked. This notification message 201 has the same message content as the notification message 101 shown in Figure 2A. This notification message 201 can be used to display a notification message (hereinafter referred to as notification message 2) generated by the electronic device 200 based on the message content of notification message 1.

[0072] Optionally, the notification message 201 may also display a prompt message "Notification from device A", which indicates that the notification message 201 originates from electronic device 100.

[0073] It should be understood that in the user interface 20 shown in Figure 2C, "Device A" is only used to refer to the device name of electronic device 100. In actual application, the name "Device A" can be replaced with other names.

[0074] Additionally, it should be noted that, similar to the description of the electronic device 100 displaying notification messages, the electronic device 200 can display notification messages in other ways besides the banner display method shown in Figure 2C, such as displaying notification messages in the notification bar or on the lock screen. This application embodiment does not limit the way the electronic device 200 displays notification messages.

[0075] As can be seen from Figures 2A-2C, when the electronic device 100 pushes a notification message, the electronic device 100 can trigger the cross-device push of the notification message based on the user's operation, so that the notification message can be pushed again on other devices. In this way, when the user browses other devices, he / she can see the same notification message with the same content on other devices, thus achieving the effect of reminding the user again.

[0076] Figures 2D-2G show the relevant user interfaces involved when a user triggers a jump to a notification message in the case of a notification message being displayed across devices, as provided in the embodiments of this application.

[0077] When a notification message is pushed across devices, for example when the user interface 20 shown in Figure 2C is displayed on the electronic device 200, if the electronic device 200 has an application corresponding to the notification message 201 installed, such as a video application, then when the electronic device 200 detects a user's jump operation on the notification message 201, such as a click operation, the electronic device 200 can trigger the opening of the application corresponding to the notification message 201, or further open the application page corresponding to the notification message 201.

[0078] For example, the electronic device 200 may, in response to a user operation acting on the notification message 201, open the application page corresponding to the notification message 201, that is, open the video application, and display the playback page of the “TV series” indicated by the notification message 201 in the video application, such as the user interface 30 shown in (a) of FIG2D or the user interface 20 shown in (b) of FIG2D.

[0079] In Figure 2D(a), the user interface 30 is used to display the playback page of the "TV series" in full screen. In Figure 2D(b), the user interface 20 includes a window 202, which can be used to display the playback page of the "TV series" in a small floating window.

[0080] Optionally, the electronic device 200 can choose whether to display the application page corresponding to the notification message in full screen or display the application page corresponding to the notification message in a small floating window when the notification message is opened, depending on the different operations performed on the notification message 201.

[0081] For example, if electronic device 200 detects a click operation on notification message 201 while displaying user interface 20 as shown in FIG2C, electronic device 200 can respond to the operation by displaying user interface 30 as shown in FIG2D(a), displaying the application page corresponding to notification message 201 in full screen. If electronic device 200 detects a pull-down operation on notification message 201 while displaying user interface 20 as shown in FIG2C, electronic device 200 can respond to the operation by displaying user interface 20 as shown in FIG2D(b), displaying the application page corresponding to notification message 201 in a small window and floating display.

[0082] When a notification message is displayed across devices, for example, when an electronic device 200 displays a notification message 201 in the user interface 20 shown in Figure 2C, if the electronic device 200 does not have the application corresponding to the notification message 201 installed, i.e., a video application, then when the electronic device 200 detects a user operation on the notification message 201, such as a click operation, triggering the opening of the application corresponding to the notification message 201, since the electronic device 200 does not have the video application installed, the electronic device 200 can display a prompt message 203 as shown in Figure 2E in the user interface 20. This prompt message 203 can be used to remind the user that the current electronic device 200 does not have the video application installed.

[0083] As shown in Figure 2E, the prompt message 203 may include: option 203A and option 203B. Option 203A can be used to trigger the installation of a video application, and option 203B can be used to enable multi-screen collaboration, enabling electronic device 100 to project the video application's page onto electronic device 200.

[0084] For example, if electronic device 200 detects a user action, such as a click, on option 203B, electronic device 200 can perform multi-screen collaboration with electronic device 100. During multi-screen collaboration, electronic device 100 can display the user interface 40 shown in FIG2F, and electronic device 200 can display the user interface 20 shown in FIG2G.

[0085] As shown in Figure 2F, the user interface 40 is the application page corresponding to notification message 1, that is, the playback page of "TV series" in the video application.

[0086] As shown in Figure 2G, the user interface 20 includes a window 204, which can be used to display the content projected from the electronic device 100 onto the electronic device 200, i.e., the user interface 40 shown in Figure 2F.

[0087] In specific implementation, after electronic device 200 detects a user operation on option 203B shown in Figure 2E, electronic device 200 can send a notification message to the source of the notification message, i.e., electronic device 100, to indicate a jump, triggering electronic device 100 to open the application page corresponding to the notification message 1, and send the display content of the application page to electronic device 200 so that electronic device 200 can realize multi-screen collaboration.

[0088] Optionally, during the process of the electronic device 100 displaying the user interface 40 shown in FIG2F, the electronic device 100 can detect user operations performed on the user interface 40, change the content displayed by the electronic device 100, and send the changed display content to the electronic device 200 in real time, so that the electronic device 200 can also synchronously display the changed display content in the window 204. Additionally, during the process of the electronic device 200 displaying the user interface 20 shown in FIG2G, the electronic device 200 can also detect user operations performed on the window 204 within the user interface 20. The electronic device 200 can send the user operation to the electronic device 100, so that the electronic device 100 can change the content in the user interface 40 according to the user operation, and send the changed display content to the electronic device 200 in real time, so that the electronic device 200 can synchronously display the changed display content in the window 204.

[0089] It should be noted that Figures 2D-2G illustrate the example where the application corresponding to the notification message is the source application of the notification message. In other embodiments of this application, the application corresponding to the notification message can refer to the application indicated by the notification message. For example, if a notification message pushed by an SMS application is used to notify a shopping application of a promotional activity, then the application corresponding to the notification message can be the shopping application. Specifically, the application corresponding to the notification message can be determined through the jump information in the notification message. This application embodiment does not limit the application corresponding to the notification message.

[0090] It is understandable that even if the electronic device 200 has the application corresponding to the notification message 201 installed, the electronic device 200 can still establish multi-screen collaboration with the electronic device 100, and project the content displayed on the electronic device 100 after the notification message 1 triggers the jump onto the electronic device 200.

[0091] As can be seen from Figures 2D-2G, after a notification message is pushed to an electronic device 200 across devices, the electronic device 200 can also jump to the notification message based on the user's operation on the notification message during the display process. This allows the user to view the detailed content of the notification message again without being restricted by the device, thus enabling timely processing of the notification message.

[0092] Figures 3A and 3B show the relevant user interface of the electronic device 100 when the device posture changes and the notification message is displayed again.

[0093] The notification message 101 shown in Figure 3A is used to display the notification message 1 received by the electronic device 100. For a detailed description of the notification message 101, please refer to the relevant content in Figure 2A above, which will not be repeated here.

[0094] For example, when displaying the user interface 10 shown in FIG3A, the electronic device 100 may be in portrait mode.

[0095] If the electronic device 100 detects a user action on the notification message 101, such as a long press, in response to the action, the electronic device 100 can display option 103 as shown in FIG3A. Option 103 can be used to trigger the electronic device 100 to display the notification message 1 again when switching to landscape mode.

[0096] As shown in Figure 3A, after the electronic device 100 detects a user operation on option 103, such as a click, and then displays notification message 1 again when the electronic device 100 switches to landscape mode, assuming that the electronic device 100 switches to landscape mode while displaying the user interface 50 shown in Figure 3B, the electronic device 100 can display notification message 501 in the user interface 50. The message content of notification message 501 is the same as the message content of notification message 101 shown in Figure 3A.

[0097] For example, the notification message 501 may also display a prompt message "from 15 minutes ago". This prompt message is used to indicate the time interval since the electronic device 100 first pushed the notification message. The user can know from this prompt message that the notification message is a message pushed by the electronic device 100 again.

[0098] It is understood that the electronic device 100 can push notification messages again not only when switching from landscape to portrait mode, but also when switching from portrait to landscape mode. It should be understood that any change in the device's orientation can trigger the electronic device 100 to push notification messages again; this embodiment does not limit the specific circumstances of the device's orientation change.

[0099] As can be seen from Figures 3A and 3B, the electronic device 100 can be set to push a notification message again when the device posture changes. This not only avoids the user missing the notification message, but also allows the user to process the notification message in an appropriate device posture.

[0100] Figures 4A and 4B show the relevant user interface of the electronic device 100 when the device changes its folded state to display the notification message again.

[0101] In the user interface shown in Figures 4A and 4B, the electronic device 100 can be a foldable screen device. Depending on the folding direction, the foldable screen included in the electronic device 100 can be an inward-folding screen or an outward-folding screen. Furthermore, the number of displays included in the foldable screen can be two, three, or others. This application embodiment does not limit the foldable screen structure of the electronic device 100.

[0102] For example, the electronic device 100 shown in Figures 4A-4B has an externally folding screen and two displays. In this case, the folding state of the electronic device 100 can include: a folded state and an unfolded state. The folded state can refer to the angle between the two displays of the folded screen of the electronic device 100 being less than 180°, and the unfolded state can refer to the angle between the two displays of the folded screen of the electronic device 100 being equal to or close to 180°.

[0103] In this scenario, the electronic device 100 is in a collapsed state when displaying the user interface 10 shown in Figure 4A. The notification message 101 in the user interface 10 is used to display notification message 1 received by the electronic device 100. For a detailed description of the user interface 10, please refer to the relevant content in Figure 2A above, which will not be repeated here.

[0104] If the electronic device 100 detects a user action, such as a long press, on the notification message 101, in response to the action, the electronic device 100 can display option 104 as shown in FIG4A. Option 104 can be used to trigger the electronic device 100 to display the notification message 1 again when the folded state changes to the unfolded state.

[0105] Assuming the folded state of electronic device 100 changes from the folded state shown in FIG4A to the unfolded state shown in FIG4B, electronic device 100 can push notification message 1 again, that is, display notification message 105 in user interface 10 shown in FIG4B. The message content of notification message 105 is the same as the message content of notification message 101 shown in FIG4A.

[0106] For example, the notification message 105 may also display a prompt message "from 15 minutes ago". This prompt message indicates the time interval since the electronic device 100 first pushed the notification message. The user can know from this prompt message that the notification message is a message pushed by the electronic device 100 again.

[0107] It is understood that, in addition to pushing notification messages again when switching from a folded state to an unfolded state, the electronic device 100 can also display notification messages again when switching from an unfolded state to a folded state. Furthermore, the folding form can include other forms besides folded and unfolded, such as a semi-folded state, a semi-unfolded state, etc. That is to say, the electronic device 100 can also display notification messages again when the folding form changes in other ways; this embodiment of the application does not limit this.

[0108] As can be seen from Figures 4A and 4B, the electronic device 100 can be set to display the notification message again when the device's folding form changes. This not only prevents users from missing notification messages, but also allows users to trigger the notification message to be pushed again by changing the device's folding form, making it easier for users to handle notification messages when the device is in a suitable folding form.

[0109] Figures 5A and 5B show the relevant user interface of the electronic device 100 when the display screen is switched to display the notification message again.

[0110] In the user interface shown in Figures 5A and 5B, the electronic device 100 is a foldable screen device. The electronic device 100 may include an outer screen and an inner screen. The inner screen can be used to display the main display content provided by the electronic device 100 to the user, while the outer screen can be used to display auxiliary display content to the user. The electronic device 100 can switch the display screen used to display the image when its folding state changes. For example, when the electronic device 100 is in the unfolded state, it can display the image through the inner screen; when the electronic device 100 is in the folded state, it can display the image through the outer screen.

[0111] Figure 5A shows the user interface 10 displayed on the inner screen of the electronic device 100 when it is in the unfolded state. Notification message 101 in the user interface 10 is used to display notification message 1 received by the electronic device 100. For a detailed description of this user interface 10, please refer to the relevant content in Figure 2A above, which will not be repeated here.

[0112] If the electronic device 100 detects a user action on the notification message 101, such as a long press, in response to the action, the electronic device 100 can display option 106 as shown in FIG5A. Option 106 can be used to trigger the electronic device 100 to push the notification message 1 again when switching the display screen.

[0113] Suppose that the folded state of electronic device 100 changes from the unfolded state shown in Figure 5A to the folded state shown in Figure 5B, the electronic device 100 can switch the display screen of the display screen from the inner screen shown in Figure 5A to the outer screen shown in Figure 5B. At this time, the electronic device 100 can display the notification message again on the outer screen.

[0114] It is understood that in Figures 5A-5B, the electronic device 100 triggers the switching of the display screen by changing the folding shape. In other embodiments of this application, the electronic device 100 may also trigger the switching of the display screen in other ways. For example, the electronic device 100 may trigger the switching of the display screen based on user operation. The embodiments of this application do not limit the way in which the electronic device 100 triggers the switching of the display screen.

[0115] Additionally, it should be noted that the electronic device 100 shown in Figures 5A-5B is a horizontally folding screen device. In other embodiments of this application, the electronic device 100 can also be a vertically folding screen device. Furthermore, the folding screen can be an inwardly folding screen or an outwardly folding screen. This application does not limit the folding form of the device.

[0116] As can be seen from Figures 5A and 5B, the electronic device 100 can be configured to display the notification message again on the new display screen when switching screens. In this way, users can view the same notification message on different screens, avoiding users missing notification messages.

[0117] Figures 6A-6C show the relevant user interface of the electronic device 100 when the notification message is displayed again when the specified application is opened.

[0118] The notification message 101 shown in Figure 6A is used to display the notification message 1 received by the electronic device 100. For a detailed description of the notification message 101, please refer to the relevant content in Figure 2A above, which will not be repeated here.

[0119] If the electronic device 100 detects a user action on the notification message 101, such as a long press, in response to the action, the electronic device 100 can display option 107 as shown in FIG6A. Option 107 can be used to trigger the electronic device 100 to push the notification message 1 again when the application corresponding to the notification message 1 is opened.

[0120] As shown in Figure 6A, the electronic device 100 can detect user actions on option 107, such as a click action, and trigger a notification to notification message 1 again when the electronic device 100 opens a video application.

[0121] As shown in Figure 6B, the user interface 10 includes an icon 108, which can be used to trigger the opening of the video application. When the electronic device 100 detects a user action on the icon 108, such as a click, the electronic device 100 can open the video application and push notification message 1 again. At this time, the electronic device 100 can display the user interface 60 shown in Figure 6C.

[0122] It is understood that, in addition to opening the application by means of the application icon as shown in Figure 6B, the electronic device 100 can also open the application by other means, such as inputting voice commands. This application embodiment does not limit the way of opening the application.

[0123] As shown in Figure 6C, the user interface 60 is used to display the homepage of the video application. The user interface 60 also includes a notification message 601, which is used to display notification message 1.

[0124] For example, the notification message 601 may also display a prompt message "from 15 minutes ago". This prompt message is used to indicate the time interval since the electronic device 100 first pushed the notification message. The user can know from this prompt message that the notification message is a message pushed by the electronic device 100 again.

[0125] As can be seen from Figures 6A-6C, when the electronic device 100 pushes a notification message for an application, the electronic device 100 can be set to push the notification message again when the application is opened. This makes it easier for users to process the messages pushed by the application while using the application, which not only prevents users from missing notification messages, but also provides convenience for users to process notification messages.

[0126] It should be noted that Figures 6A-6C illustrate the process of electronic device 100 pushing a notification message again when the designated application opened by the electronic device 100 is used as the source application of the notification message. In other embodiments of this application, the designated application may also refer to the application selected by the user, or the application indicated by the notification message. For example, if the notification message received by electronic device 100 is a promotional activity related to a shopping application pushed by an SMS application, then the designated application may refer to the shopping application, and electronic device 100 may push the notification message again when the shopping application is opened.

[0127] Figures 7A-7C illustrate the user interface for displaying a notification message again when a specified application is opened across devices, as provided in this embodiment of the application. Figure 7A shows the user interface displayed on electronic device 100, while Figures 7B and 7C show the user interface displayed on electronic device 200. Electronic device 200 can refer to a device that has established a communication connection with electronic device 100.

[0128] The notification message 101 shown in Figure 7A is used to display the notification message 1 received by the electronic device 100. For a detailed description of the notification message 101, please refer to the relevant content in Figure 2A above, which will not be repeated here.

[0129] When electronic device 100 detects a user action, such as a long press, on notification message 101, in response to the action, electronic device 100 can display option 109 as shown in FIG7A. Option 109 can be used to trigger electronic device 100 to control the device to display notification message 1 after detecting that another device has opened a video application.

[0130] As shown in Figure 7A, when electronic device 100 detects a user operation, such as a click, on option 109, electronic device 100 can send the message content of notification message 1 to a device with which a communication connection has been established, such as electronic device 200. Specifically, electronic device 100 can send the message content of notification message 1 to electronic device 200 after electronic device 200 opens a video application, or electronic device 100 can send the message content of notification message 1 to electronic device 200 in response to the user operation on option 109 after detecting the operation.

[0131] It is understandable that if electronic device 100 does not establish a communication connection with other devices when it detects a user operation on option 109, then after electronic device 100 detects the user operation on option 109, electronic device 100 can search for nearby devices with which a communication connection can be established, so as to realize cross-device message notification with other devices.

[0132] Figure 7B can be used to illustrate the user interface 20 corresponding to the desktop on the electronic device 200. The user interface 20 may include an icon 205, which can be used to trigger the opening of a video application.

[0133] As shown in Figure 7B, when the electronic device 100 detects a user action, such as a click, on the icon 205, in response to the action, the electronic device 200 can open the video application and display the user interface 70 shown in Figure 7C, which can be used to display the home page of the video application.

[0134] Furthermore, when the electronic device 200 opens the video application, it can also display notification message 2 generated based on the message content of notification message 1, that is, display notification message 701 in the user interface 70 shown in FIG7C. Notification message 701 can be used to display the message content of notification message 2.

[0135] For example, the notification message 701 may also display the prompt messages "Notification from device A" and "From 15 minutes ago". The "Notification from device A" message can be used to indicate that the notification message is a notification message obtained by electronic device 200 across devices and is not a message pushed to electronic device 200 by an application in electronic device 200. The "From 15 minutes ago" message can be used to indicate the time interval between the first push of the notification message and the current time. The user can know from the prompt message that the notification message is a message pushed again.

[0136] It is understood that, in addition to opening the application via the application icon as shown in Figure 7B, the electronic device 200 can also open the application in other ways, and this application embodiment does not limit this.

[0137] As can be seen from Figures 7A-7C, after pushing a notification message, electronic device 100 can send the notification message across devices, such as electronic device 200, so that electronic device 200 can push the notification message when a specified application is opened. In this way, the user of electronic device 200 can view the notification messages that have been pushed from other devices in the past when the specified application is opened, so that the user can understand the content of the notification messages pushed by other devices on electronic device 200 and process them.

[0138] Additionally, it should be noted that, in addition to the notification message being triggered to re-display when a specified application is opened across devices as shown in Figures 7A-7C, the notification message can also be triggered to re-display when a specified page of an application is opened across devices. For example, electronic device 200 can display notification message 1 when the video playback interface of a video application is opened.

[0139] Figures 8A-8D show the relevant user interface for displaying the notification message again after a specified period of time, as provided in the embodiments of this application.

[0140] Figures 8A and 8B show the user interface of the electronic device 100 displaying the notification message again on its own device after a specified period of time, and Figures 8C and 8D show the user interface of the electronic device 100 displaying the notification message again through the electronic device 200 after a specified period of time.

[0141] The notification message 101 shown in Figure 8A is used to display the notification message 1 received by the electronic device 100. For a detailed description of the notification message 101, please refer to the relevant content in Figure 2A above, which will not be repeated here.

[0142] When electronic device 100 detects a user action, such as a long press, on notification message 101, in response to the action, electronic device 100 can display option 110 as shown in FIG8A. Option 110 can be used to trigger electronic device 100 to push notification message 1 again after 15 minutes.

[0143] As shown in Figure 8A, when the electronic device 100 detects a user action, such as a click, on option 110, in response to the action, the electronic device 100 can display the user interface 10 shown in Figure 8B after 15 minutes.

[0144] As shown in Figure 8B, the user interface 10 may include a notification message 111, which can be used to display the message content of notification message 1.

[0145] For example, the notification message 601 may also display a prompt message "from 15 minutes ago". This prompt message is used to indicate the time interval since the electronic device 100 first pushed the notification message. The user can know from this prompt message that the notification message is a message pushed by the electronic device 100 again.

[0146] It is understood that Figure 8B takes the example of the electronic device 100 pushing a notification message in the user interface 10 again. In other embodiments of this application, the electronic device 100 may also push the notification message again when displaying other user interfaces. Specifically, the user interface displayed when the electronic device 100 pushes the notification message again can be determined by the user interface that the electronic device 100 is in after the specified time interval.

[0147] The notification message 101 shown in Figure 8C is used to display the notification message 1 received by the electronic device 100. For a detailed description of this notification message 101, please refer to the relevant content in Figure 2A above, which will not be repeated here.

[0148] When electronic device 100 detects a user action, such as a long press, on notification message 101, in response to the action, electronic device 100 can display option 112 as shown in FIG8C. Option 112 can be used to trigger electronic device 100 to push notification message 1 across devices again after 15 minutes.

[0149] As shown in Figure 8C, when electronic device 100 detects a user action, such as a click, on option 112, electronic device 200 can display a notification message 206 as shown in Figure 8D after a 15-minute interval. This notification message 206 can be used to display the message content of notification message 1. Here, electronic device 200 can refer to a device that has established a communication connection with electronic device 100, or it can refer to a device selected by the user after enabling cross-device notifications.

[0150] For example, the notification message 206 may also display the prompt messages "Notification from device A" and "From 15 minutes ago". The "Notification from device A" message can be used to indicate that the notification message is a notification message obtained by electronic device 200 across devices and is not a message pushed to electronic device 200 by an application in electronic device 200. The "From 15 minutes ago" message can be used to indicate the time interval between the first push of the notification message and the current time. The user can know from the prompt message that the notification message is a message pushed again.

[0151] In a specific implementation, after detecting a user operation on option 112, electronic device 100 can, in response to the operation, send the message content of notification message 1 and a specified duration (i.e., 15 minutes) to electronic device 200, so that electronic device 200 can push notification message 1 after waiting for the specified duration. Alternatively, after detecting a user operation on option 112, electronic device 100 can, after waiting for the specified duration, send the message content of notification message 1 to electronic device 200, so that electronic device 200 can trigger message push after receiving the message content of notification message 1.

[0152] It is understood that Figure 8D takes the user interface 20 corresponding to the desktop when the electronic device 200 pushes a notification message as an example. In this embodiment of the application, the electronic device 200 can also push notification messages when displaying other interfaces. Specifically, the user interface displayed when the electronic device 200 pushes a notification message is determined by the interface displayed by the electronic device 200 when the specified time period is reached.

[0153] It should be noted that the specified waiting time for electronic device 100 or electronic device 200, besides the 15 minutes exemplified in Figures 8A and 8C, can also be other durations, and this application embodiment does not impose any restrictions on this. Furthermore, the specified duration can be a preset duration by electronic device 100, a user-set duration, or a duration determined by electronic device 100 based on information such as the currently running application and the application being used; this application embodiment does not restrict the method of determining the specified duration.

[0154] As can be seen from Figures 8A-8D, the electronic device 100 can push notification messages again on its own device or other devices after a specified time interval based on user operation settings, so that the user can see the notification message again after a certain time interval and avoid the user missing the notification message.

[0155] In summary, Figures 2A-2C, 3A-3B, 4A-4B, 5A-5B, 6A-6C, 7A-7C, and 8A-8D illustrate the relevant user interfaces for electronic devices 100 and 200 to display the notification message again after different specified conditions are met, following the initial display of the notification message by the electronic device 100.

[0156] In some implementations, the specified conditions for different notification messages can be different. For example, if the notification message displayed by electronic device 100 is notification message 1, the specified condition can be condition 1. In this case, electronic device 100 or electronic device 200 can push notification message 1 again when condition 1 is met. If the notification message displayed by electronic device 100 is notification message 2, the specified condition can be condition 2. In this case, electronic device 100 can push notification message 2 again when condition 2 is met. Thus, for different notification messages, electronic device 100 can display the notification message locally again or across devices when different conditions are met.

[0157] For example, when a notification message is sent again on the local machine, the specified conditions corresponding to the notification message can be selected by the user.

[0158] Figure 9 shows the user interface 10 of the electronic device 100 provided in this application embodiment, which involves selecting specified conditions based on user operation.

[0159] As shown in Figure 9, notification message 101 is used to display notification message 1 received by electronic device 100. For a detailed description of notification message 101, please refer to the relevant content in Figure 2A above, which will not be repeated here. When electronic device 100 detects a user operation on notification message 101, such as a long press, in response to this operation, electronic device 100 can display option bar 112 as shown in Figure 9. Option bar 112 can include multiple options, each corresponding to different specified conditions. As shown in Figure 9, option bar 112 can include option 112A, option 112B, and option 112C. Option 112A can be used to trigger electronic device 100 to display the notification message again when the screen is in landscape mode; option 112B can be used to trigger electronic device 100 to display the notification message again when the screen is unlocked; and option 112C can be used to trigger electronic device 100 to display the notification message again after 15 minutes. In this way, electronic device 100 can display the notification message again on its own device based on the user-selected option and when the specified conditions corresponding to the user-selected option are met.

[0160] It is understandable that when a notification message is sent across devices, the specified conditions for the notification message can also be selected by the user, which will not be elaborated here.

[0161] For example, when a notification message is sent again on the local device, the specified conditions corresponding to the notification message can be determined by electronic device 100. When a notification message is sent again across devices, the specified conditions corresponding to the notification message can be determined by electronic device 100 or electronic device 200. For example, electronic device 100 can determine the specified conditions corresponding to different notification messages based on information such as the application corresponding to the notification message, the content of the notification message, the structure of the device, and the number of displays on the device.

[0162] It is understood that the user interfaces shown in Figures 2A-2G, 3A-3B, 4A-4B, 5A-5B, 6A-6C, 7A-7C, 8A-8D, and 9 are merely exemplary examples and do not constitute a limitation on the embodiments of this application.

[0163] Figure 10 is a flowchart illustrating a message notification method provided in an embodiment of this application.

[0164] As shown in Figure 10, this message notification method involves electronic device 100 and electronic device 200, and mainly includes the following steps:

[0165] S101. Electronic device 100 displays notification message 1.

[0166] Notification message 1 can be a notification message pushed from the application server of the application to the electronic device 100 by the application. Specifically, the application server can send the application's notification message to the electronic device 100 to achieve the push notification.

[0167] For example, if the application is an e-commerce application, the notification message 1 may include information about the purchased goods; if the application is an instant messaging application, the notification message 1 may include chat information with contacts; if the application is an audio-visual entertainment application, the notification message 1 may include information about videos and music.

[0168] For example, the electronic device 100 may display notification message 1 as a banner, in the notification bar, or on the lock screen. This application embodiment does not limit the manner in which the electronic device 100 displays notification message 1.

[0169] Specifically, if the electronic device 100 is in a locked state, it can display notification message 1 on the lock screen after receiving notification message 1. If the electronic device 100 is in an unlocked state, it can display notification message 1 as a banner or in the notification bar.

[0170] Optionally, the notification messages received by the electronic device 100 can be assigned a priority. If notification message 1 is a high-priority notification message, the electronic device 100 can display notification message 1 as a banner when it is unlocked. If notification message 1 is a low-priority notification message, the electronic device 100 can display notification message 1 in the notification bar when it is unlocked.

[0171] For example, electronic device 100 can open the notification bar based on a user's pull-down operation at the top of the display screen.

[0172] For example, during the display of notification message 1 on the electronic device 100, if the electronic device 100 does not detect any user interaction with the notification message 1, the notification message 1 can be stopped after a certain period of time. In this way, after achieving the purpose of reminding the user, the notification message 1 can avoid obscuring other display content on the electronic device 100 and affecting the user's operations on the electronic device 100.

[0173] Referring to Figure 2A, notification message 1 can refer to notification message 101 shown in Figure 2A.

[0174] S102. When the first event is detected, electronic device 100 sends the message content of notification message 1 to electronic device 200.

[0175] The first event can be used to instruct the user to trigger a second push notification message 1.

[0176] For example, electronic device 200 can be a device that has established a communication connection with electronic device 100, or it can be a device selected by the user. This application embodiment does not limit the source of electronic device 200.

[0177] For example, the first event can exist in several of the following situations:

[0178] 1) This first event can be a user action that triggers the notification message to be displayed again.

[0179] The user operation can refer to a touch operation on the display screen or a voice command initiated by the user. This application embodiment does not limit the form of the user operation.

[0180] For example, the user action may include an action on the notification message and an action on a specified option, which may be an option displayed by the electronic device 100 in response to the action on the notification message, and the option may be used to trigger the notification message to be displayed again across devices.

[0181] Referring to Figures 2A and 2B, the user operation may include the operation on notification message 101 shown in Figure 2A, and the operation on option 102 shown in Figure 2B.

[0182] 2) The first event can be an event in which no operation is received on notification message 1 during the process of electronic device 100 displaying notification message 1.

[0183] This is because when the electronic device 100 displays a notification message, if the user notices the notification message, they may perform a corresponding operation on the notification message; if the user does not notice the notification message, they may continue to focus their attention on content other than the notification message and will not process the notification message.

[0184] In other words, the electronic device 100 can analyze whether the user has noticed the notification message 1 by checking whether the user performs any action on the notification message 1 during the push notification process, and then determine whether the notification message needs to be displayed again.

[0185] 3) The first event may include the user's gaze on notification message 1 for less than a threshold duration during the process of electronic device 100 displaying notification message 1.

[0186] This is because when electronic device 100 pushes a notification message, if the user looks at the notification message 1 for a shorter period of time, it means that the user is less likely to notice the notification message. Therefore, it is possible to determine whether to push a notification message on electronic device 200 again based on the length of time the user looks at the notification message 1.

[0187] In other words, the electronic device 100 can analyze whether the user has noticed the notification message 1 by the length of time the user looks at the notification message 1 during the push notification process, and then determine whether the notification message needs to be displayed again.

[0188] For example, during the display of notification message 1, the electronic device 100 can identify the user's pupils through the front-facing camera and determine the duration of the user's gaze on notification message 1 based on the location of the user's pupils.

[0189] It is understood that other situations may exist for this first event, and the embodiments of this application do not limit this.

[0190] S103. When the electronic device 200 meets the specified conditions, it displays notification message 2, and the content of notification message 2 is the same as that of notification message 1.

[0191] For example, after receiving the message content of notification message 1, the electronic device 200 can encapsulate the message content of notification message 1 into a new notification message, namely notification message 2.

[0192] For example, notification message 2 may refer to notification message 201 shown in FIG2C.

[0193] The determination of whether electronic device 200 meets the specified conditions can involve the following two situations:

[0194] 1) Electronic device 100 determines whether electronic device 200 meets the specified conditions.

[0195] In this case, electronic device 100 can determine that electronic device 200 meets the specified conditions and then send the message content of notification message 1 to electronic device 200.

[0196] In this way, the electronic device 200 can directly display notification message 2 after receiving the message content of notification message 1.

[0197] For example, electronic device 100 can obtain relevant information about electronic device 200 and determine whether electronic device 200 meets specified conditions based on the relevant information, thereby enabling the message content of notification message 1 to be sent to electronic device 200 when electronic device 200 meets the specified conditions.

[0198] For example, if the specified condition is that the screen of electronic device 200 is on, then electronic device 100 can request electronic device 200 to obtain the screen status of electronic device 200. After the screen of electronic device 200 is on, electronic device 200 can send the indication information of the screen being on to electronic device 100, so that electronic device 100 can send the message content of notification message 1 to electronic device 200, thereby enabling electronic device 200 to push notification messages when the screen is on.

[0199] 2) Determine whether electronic device 200 meets the specified conditions.

[0200] In this case, after recognizing the first event that the user has triggered the push notification message 1 again, the electronic device 100 can directly send the message content of the notification message 1 to the electronic device 200. The electronic device 200 can then display the notification message 2 if it is determined that the electronic device 200 meets the specified conditions.

[0201] Optionally, when sending the message content of notification message 1 to electronic device 200, electronic device 100 may also send the specified condition to electronic device 200.

[0202] Therefore, the embodiments of this application do not limit the device for determining the specified conditions.

[0203] The specified conditions may include one or more of the following: screen on, unlock, reaching a specified time (e.g., the first time), launching a specified application (e.g., the first application), changing the device's orientation, switching the display, or changing the device's folding shape, etc.

[0204] The specified time can be a preset time of electronic device 100 or electronic device 200, or a time selected by the user. Alternatively, the specified time can be a time determined based on a specified duration, which can be a preset duration of electronic device 100 or electronic device 200, or a duration selected by the user. For example, if the specified duration is 15 minutes, then the specified time can be the time 15 minutes after electronic device 100 stops displaying notification message 1.

[0205] The specified application can be the application that is the source of notification message 1, the application indicated by notification message 1, or the application selected by the user, etc.

[0206] The specified condition can be determined by electronic device 100 or electronic device 200.

[0207] This specified condition can be determined in the following ways:

[0208] 1) This specified condition can be determined based on notification message 1.

[0209] In other words, the specified conditions will be different if the notification messages pushed by the electronic device 100 are different.

[0210] Specifically, if the specified condition is to reach a specified time, the specified time can be determined according to notification message 1. If the specified condition is to launch a specified application, the specified application can be determined according to notification message 1. If the specified condition is to change the device orientation, the device orientation change can be determined according to notification message 1, specifically whether it is a switch from landscape to portrait mode, or a switch from portrait to landscape mode, etc.

[0211] For example, the specified conditions can be determined based on one or more of the following: the message content of notification message 1, the source application, and the importance, etc.

[0212] For example, if the specified condition is to reach a specified time, the specified time in the specified condition can be determined based on the time information such as the time point and time period carried in the message content of notification message 1. For example, if the message content of notification message 1 is: "The product promotion activity starts at 8 pm", then electronic device 100 can determine that the specified time is 8 pm or close to 8 pm.

[0213] For example, if the specified condition is to launch a specific application, then the source application of the notification message can be determined to be that specified application.

[0214] For example, if the specified condition is reaching a specified time, this specified time can be determined based on the importance of notification message 1. The more important the notification message, the shorter the time between the first notifications within the specified time interval; conversely, the less important the notification message, the longer the time between the first notifications within the specified time interval.

[0215] In this way, based on the notification messages pushed by the electronic device 100, the specified conditions that need to be met when the notification message is sent across devices again can be dynamically adjusted, so as to realize cross-device notification of different notification messages in different scenarios.

[0216] 2) This specified condition can be determined by the user.

[0217] For example, the electronic device 100 may have multiple preset conditions, and the electronic device 100 may select a specified condition from multiple conditions based on user operation, or the electronic device 100 may customize the specified condition based on user operation.

[0218] This improves user operability, allowing notification messages to be displayed across devices according to the user's wishes.

[0219] In one possible implementation, the electronic device 100 can determine the specified condition selected by the user based on the first event identified in step S102. Thus, the user's selection of the corresponding specified condition indicates that the user has triggered the push of the notification message 1 again.

[0220] In this case, if the first event is a user action that triggers the notification message to be displayed again, the user action may include: an action on the notification message 1 (e.g., a second action), and a selection action (e.g., a third action) on one of the multiple options (e.g., the first option) after the electronic device 100 displays multiple options in response to the action, wherein different options can be used to indicate different conditions, and the selected option is used to indicate the specified condition.

[0221] It is understandable that the electronic device 100 may determine the specified condition based on the user's operation after recognizing the first event mentioned in step S102. For example, after recognizing that the duration of the user's gaze at the notification message 1 exceeds a threshold, the electronic device 100 may provide multiple options corresponding to the conditions for the user to choose from, so that the user can determine the specified conditions that need to be met when the notification message is pushed again.

[0222] 3) This specified condition can be a preset condition.

[0223] Developers can pre-set the specified conditions and pre-configure them in electronic device 100. In this way, electronic device 100 can control the content of notification messages sent to other devices under the specified conditions according to the pre-configured conditions.

[0224] It is understood that other conditions may exist for the specified condition, and this application embodiment does not impose any restrictions on this. In addition, the specified condition can be determined by combining the above-mentioned methods. For example, the specified condition can be determined by combining user operations and notification messages. For example, the user can determine whether the specified condition is to turn on the screen, unlock the phone, reach a specified time, or launch a specified application, etc. If the user determines that the specified condition is to reach a specified time, the specified time can be determined based on the notification message, for example, based on the importance of the notification message.

[0225] In some implementations, in addition to determining whether electronic device 200 meets the specified conditions, it is also possible to determine whether electronic device 100 meets the specified conditions. In this way, electronic device 200 can display notification message 2 if both electronic devices 100 and 200 meet the specified conditions. The specified conditions that electronic device 100 needs to meet may be the same as or different from the specified conditions that electronic device 200 needs to meet.

[0226] Specifically, the specified conditions corresponding to electronic device 100 can also exist in various ways as described above for the specified conditions corresponding to electronic device 200, which will not be elaborated here.

[0227] For example, electronic device 100 can send the message content of notification message 1 to electronic device 200 if it determines that electronic device 100 meets condition 1 and electronic device 200 meets condition 2. Condition 1 and condition 2 can be the same or different. This allows for a comprehensive evaluation of the optimal timing for initiating cross-device display of the notification message by combining the states of electronic devices 100 and 200, so that electronic device 200 can push the notification message when the user has time to process it.

[0228] For example, condition 1 can be that the screen of electronic device 100 is off, and condition 2 can be that the screen of electronic device 200 is on. In this way, electronic device 200 can display notification message 2 when the screen of electronic device 100 is off and when the screen of electronic device 200 is on.

[0229] Understandably, electronic device 100 doesn't need to send the message content of notification message 1 to electronic device 200; it only needs to inform electronic device 200 that notification message 1 needs to be pushed again. This is because if electronic device 200 also receives a notification message with the same message content as notification message 1 from the application, then electronic device 200 doesn't need to obtain the message content of notification message 1 from electronic device 100. For example, if electronic device 100 and electronic device 200 are logged into the same account on the same instant messaging application, then both electronic device 100 and electronic device 200 can receive chat messages sent to that account by contacts.

[0230] Additionally, it's important to note that besides sending the message content of notification message 1 to electronic device 200, electronic device 100 can also send other information. For example, other information may include specified conditions. Upon receiving these conditions, electronic device 200 can push a notification message if it determines that it meets those conditions. Another example is the redirection information for notification message 1. This redirection information can be used to determine the application or page to open or display after the notification message triggers a redirect. This allows electronic device 200 to achieve cross-device redirection of notification messages. For a detailed description of notification message redirection, please refer to Figures 12 and 13 below.

[0231] In some implementations, while displaying notification message 2, electronic device 200 may also display a prompt message (e.g., a first prompt message) on notification message 2. This prompt message can be used to indicate that the message content of notification message 2 originates from electronic device 100. In this way, a user viewing electronic device 200 can understand through this prompt message that notification message 2 is a notification message pushed across devices again.

[0232] Additionally, similar to electronic device 100 pushing notification message 2, electronic device 200 pushing notification message 2 can mean displaying notification message 2 as a banner, displaying notification message 2 in the notification bar, or displaying notification message 2 on the lock screen. For details regarding how electronic device 200 displays notification message 2, please refer to the aforementioned description of electronic device 100 displaying notification message 1, which will not be repeated here.

[0233] In some implementations, the electronic device 100 can also set whether to allow or disallow the notification message to be pushed again based on user operation settings. Specifically, when the electronic device 100 displays a notification message that allows the notification to be pushed again, it can determine whether a first event triggering the user to push the notification message again has been detected, and ultimately decide whether to push the notification message again.

[0234] For example, electronic device 100 can be configured on an application-by-application basis, allowing notifications from a first application to be sent again, while disallowing notifications from a second application. Alternatively, it can be configured on a time-segment basis, allowing notifications sent in a first time period to be sent again, while disallowing notifications sent in a second time period. Furthermore, based on the importance of the notifications, it can configure important notifications to be sent again, while disallowing less important notifications. The applications, time periods, and importance levels mentioned above can all be set by the user or preset by the device.

[0235] In this way, the electronic device 100 can pre-filter some notification messages, avoiding the need for the electronic device 100 to identify whether the user has not paid attention to the message when pushing each notification message, thus reducing the computational load of the device.

[0236] In this embodiment of the application, electronic device 100 may also be referred to as a first device, electronic device 200 may also be referred to as a second device, the specified condition may also be referred to as a first condition, notification message 1 may also be referred to as a first notification message, and notification message 2 may also be referred to as a second notification message.

[0237] As can be seen from steps S101-S103, if the user does not pay attention to the notification message after the electronic device 100 displays it once, the electronic device 200 can display the notification message again under specified conditions. This is also to take into account that users usually carry multiple devices. Using the method provided in this application embodiment, the problem of notification messages not being pushed across devices when the user is using multiple devices can be solved, causing the user to miss notification messages, and realizing the linkage of multiple devices in pushing notification messages.

[0238] The following example, showing the notification message on electronic device 100 again when electronic device 200 turns on, illustrates the interaction process between various modules of electronic device 100 and electronic device 200 in the message notification method shown in Figure 11.

[0239] Figure 11 is a module interaction diagram of electronic device 100 and electronic device 200 involved in the message notification method provided in the embodiments of this application.

[0240] The message notification method provided in this application mainly involves three modules in electronic device 100: application X, notification center, and notification coordination service, and two modules in electronic device 200: notification center and notification coordination service. Application X can refer to any application in electronic device 100, notification center can be used to push notification messages, and notification coordination service can be used to manage the re-pushing of notification messages.

[0241] As shown in Figure 11, the message notification method provided in this application mainly involves the following steps:

[0242] S201. Application X in electronic device 100 sends notification message 1 to the notification center in electronic device 100.

[0243] It is understandable that, in addition to the application X in electronic device 100 sending notification messages to the notification center in electronic device 100, electronic device 100 can also receive notification messages sent by the server of application X to the notification center in electronic device 100.

[0244] S202. Notification message pushed by the notification center in electronic device 100.

[0245] For example, the notification center in the electronic device 100 can display notification message 1 in the form of a banner, in the notification bar, or on the lock screen.

[0246] S203. The notification center in the electronic device 100 detects that the user has triggered an operation to send a notification message again.

[0247] For example, the notification center in electronic device 100 can detect the operation performed on notification message 1 during the display of notification message 1, and trigger the push of notification message 1 again on electronic device 200.

[0248] Understandably, the notification center in electronic device 100 can also determine whether to trigger a second notification on electronic device 200 based on first events such as whether the user's operation on the notification message is detected during the display of notification message 1, or the duration of the user's gaze on notification message 1.

[0249] S204. The notification center in electronic device 100 sends the message content of notification message 1 and information of electronic device 200 to the notification collaboration service in electronic device 100.

[0250] After detecting that the user has triggered a notification on the electronic device 200, the notification center in the electronic device 100 can record information about the electronic device 200, which can be used to uniquely identify the electronic device 200.

[0251] The notification center in electronic device 100 sends the message content of notification message 1 and the information of electronic device 200 to the notification coordination service in electronic device 100. This enables electronic device 100 to store notification message 1 and the information of electronic device 200 in the notification coordination service and bind notification message 1 to electronic device 200. This allows notification message 1 to be sent to the device bound to notification message 1 when notification message 1 needs to be notified again.

[0252] For example, the notification coordination service in electronic device 100 can store notification message 1 and information of electronic device 200 in the format of [notification message 1 - device name of electronic device 200].

[0253] S205. The notification coordination service in electronic device 100 requests the screen status of electronic device 200 from the notification coordination service in electronic device 200.

[0254] The screen status can include: screen on, screen off.

[0255] Since electronic device 100 needs to control electronic device 200 to display notification messages when electronic device 200's screen is on, electronic device 100 needs to obtain the screen status of electronic device 200 and promptly send the message content of notification message 1 to electronic device 200 when electronic device 200's screen is on.

[0256] It is understandable that, in addition to screen status, for other specified conditions, the notification coordination service in electronic device 100 can request other information about electronic device 200 from the notification coordination service in electronic device 200. For example, if the specified condition is a change in device orientation, then this information could be the device orientation of electronic device 200.

[0257] S206. The notification coordination service in electronic device 200 sends an indication message for electronic device 200 to turn on its screen to the notification coordination service in electronic device 100.

[0258] When the screen is on, electronic device 200 can send a notification message to electronic device 100 indicating that its screen is on via a notification collaboration service. Conversely, when the screen is off, electronic device 200 can also send a notification message to electronic device 100 indicating that its screen is off via a notification collaboration service.

[0259] S207. The notification coordination service in electronic device 100 sends the message content of notification message 1 to the notification coordination service in electronic device 200.

[0260] When it is determined that the screen of the electronic device 200 is on, the electronic device 100 can send the message content of notification message 1 to the electronic device 200 through the notification collaboration service in the electronic device 100, so that the electronic device 200 can push notification messages when the screen is on.

[0261] S208. The notification coordination service in electronic device 200 obtains notification message 2 based on the message content of notification message 1.

[0262] The notification coordination service in electronic device 200 can encapsulate the message content of notification message 1 into a new notification message to obtain notification message 2.

[0263] S209. The notification coordination service in electronic device 200 sends notification message 2 to the notification center in electronic device 200.

[0264] S210. The notification center of electronic device 200 pushes notification messages 2.

[0265] For example, the notification center in the electronic device 200 can display notification message 2 in the form of a banner, in the notification bar, or on the lock screen.

[0266] As can be seen from steps S201-S210, electronic device 100 can enable cross-device push of notification messages based on user operation. Furthermore, electronic device 100 can send the message content of the notification message to electronic device 200 again when it detects that the screen of electronic device 200 is on, so that electronic device 200 can push notification messages when the screen is on.

[0267] Furthermore, after the notification message is pushed across devices again, for example, after electronic device 200 pushes notification message 2, electronic device 200 can also trigger the notification message to jump based on the user's jump operation on notification message 2 (e.g., the first operation), such as launching the application corresponding to notification message 2 (hereinafter referred to as application X), or further triggering electronic device 200 to display the application page corresponding to notification message 2 in application X.

[0268] It should be understood that the application corresponding to the notification message can refer to the application from which the notification message originates, or it can refer to the application indicated by the notification message. This application embodiment does not limit the application corresponding to the notification message.

[0269] For example, in addition to the message content, the notification message may also include redirection information, which can be used to indicate the application corresponding to the notification message or the application page corresponding to the notification message. Thus, during the process of electronic device 100 pushing notification message 1, if electronic device 100 detects a user's redirection operation on notification message 1, it can implement the redirection of notification message 1 based on the redirection information in notification message 1. Alternatively, during the process of electronic device 200 pushing notification message 1, if electronic device 200 detects a redirection operation on notification message 2, it can implement the redirection of notification message 2 based on the redirection information in notification message 2.

[0270] In other words, in this embodiment, if electronic device 100 triggers cross-device push notification messages on electronic device 200, when sending the message content of notification message 1 to electronic device 200, electronic device 100 can also send jump information of notification message 1 to electronic device 200. The notification message 2 obtained by electronic device 200 can include the message content of notification message 1 and the jump information of notification message 1. Thus, during the process of electronic device 200 displaying notification message 2, if electronic device 200 detects that the user has performed a jump operation on notification message 2, it can jump to notification message 2 based on the jump information.

[0271] Additionally, when notification messages are pushed across devices, such as when notification message 2 is pushed on electronic device 200, the following two situations exist:

[0272] 1) Application X is installed on electronic device 200.

[0273] If the electronic device 200 has application X installed, when the electronic device 200 detects a jump operation acting on notification message 2, it can directly open application X or display the application page corresponding to notification message 2.

[0274] For details regarding the interaction process between various modules during the notification message jump process based on the jump operation of the electronic device 200, please refer to the relevant content in Figure 12 below.

[0275] 2) Application X is not installed on electronic device 200.

[0276] If electronic device 200 does not have application X installed, then when electronic device 200 detects a jump operation acting on notification message 2, the following two situations may occur:

[0277] a) Electronic device 200 triggers the installation of application X, and after the installation of application X is completed, in response to the jump operation, opens application X, or further displays the application page corresponding to notification message 2 in application X.

[0278] In other words, if the electronic device 200 does not have application X installed, when the electronic device 200 detects that the user has performed a jump operation on notification message 2, the electronic device 200 can first install application X, and then trigger the jump of notification message 2 after the application X is installed.

[0279] For example, before installing application X, electronic device 200 may display a prompt message, such as prompt message 203 shown in FIG2E, to prompt the user that the application corresponding to notification message 2 is not currently installed.

[0280] Furthermore, the electronic device 200 can also select whether to install application X based on user operation. This improves user operability.

[0281] b) Electronic device 200 can find a local application that can replace application X (hereinafter referred to as application X'), and in response to the jump operation, open application X', or further display the application page corresponding to notification message 2 in application X'.

[0282] In other words, if the electronic device 200 does not have application X installed, after the electronic device 200 detects that the user has performed a jump operation on notification message 2, the electronic device 200 can open an application similar to application X, or display the application page corresponding to notification message 2 in that application.

[0283] In this context, an application similar to application X can refer to an application that contains the same functions as application X.

[0284] For example, if notification message 2 is an update message about a popular TV series pushed by video playback application 1 (i.e. application X), and if electronic device 200 does not have video playback application 1 installed, but has video playback application 2 (i.e. application X') that can also play the popular TV series installed, then electronic device 100 can open video playback application 2, or further display the playback interface of the popular TV series in video playback application 2.

[0285] c) In response to the jump operation, electronic device 100 can open application X, or further display the application page corresponding to notification message 2 in application X, and project the display content of electronic device 100 onto electronic device 200.

[0286] In other words, if electronic device 200 does not have application X installed, after electronic device 200 detects the user's adjustment operation on notification message 2, electronic device 200 can initiate a jump to notification message 1 and multi-screen collaboration to electronic device 100. After triggering the jump of notification message 1, electronic device 100 can project the display content onto electronic device 200 for display.

[0287] For details regarding the interaction process between various modules during the process of electronic device 100 and electronic device 200 switching to notification message 2 via screen mirroring, please refer to the relevant content in Figure 13 below.

[0288] Figure 12 is a diagram showing the module interactions involved in electronic device 200 when application X is installed and a notification message is triggered.

[0289] S301. The notification center in the electronic device 200 detects a jump operation performed on notification message 2.

[0290] For example, the electronic device 200 may detect a jump operation acting on the notification message 2 during the display of the notification message 2.

[0291] The jump operation can be a touch operation performed by the user on the display screen, or it can refer to the user's voice command. This application embodiment does not limit the form of the jump operation.

[0292] Referring to Figure 2C, this jump operation can refer to the operation performed on notification message 201.

[0293] S302. The notification center in electronic device 200 initiates a jump of notification message 2 to the notification collaboration service in electronic device 200.

[0294] S303. The notification collaboration service in electronic device 200 triggers the launch of application X based on the jump information in notification message 2.

[0295] If application X is installed on electronic device 200, the notification collaboration service in electronic device 200 can open application X, thereby enabling the jump to notification message 2.

[0296] Alternatively, the notification collaboration service in the electronic device can also open the application page corresponding to notification message 2 in application X based on the jump information in notification message 2.

[0297] Referring to Figure 2D, the application page can refer to the video playback page shown in (a) of Figure 2D, or it can refer to the video playback page displayed in window 202 shown in (b) of Figure 2D.

[0298] As can be seen from steps S301-S303, when electronic device 200 pushes a notification message from electronic device 100, electronic device 200 can also trigger the notification message to jump based on the user's jump operation on the notification message, and view the message content of the notification message, thus realizing cross-device processing of the notification message. In this way, the user does not need to know whether the notification message pushed on electronic device 200 comes from other devices, expanding the application of notification messages in cross-device push scenarios.

[0299] Figure 13 is a module interaction diagram between electronic device 100 and electronic device 200 during the process of jumping to a notification message through screen projection provided in the embodiments of this application.

[0300] S401. The notification center in electronic device 200 detects a jump operation performed on notification message 2.

[0301] S402. The notification center in electronic device 200 initiates a jump of notification message 2 to the notification collaboration service in electronic device 200.

[0302] For a detailed description of steps S401-S402, please refer to the relevant content of steps S301-S302 above, which will not be repeated here.

[0303] S403. The notification coordination service in electronic device 200 sends a jump operation instruction to the notification coordination service in electronic device 100.

[0304] Since application X is not installed in electronic device 200, electronic device 200 can send the instruction information for the jump operation to electronic device 100.

[0305] It is understandable that before electronic device 200 sends the instruction information for the jump operation to electronic device 100, it can also send a request for multi-screen collaboration to electronic device 100. If electronic device 100 agrees to multi-screen collaboration, it can then send notification message 2 to electronic device 100 to instruct for the jump.

[0306] S404. The notification collaboration service in electronic device 100 triggers the launch of application X based on the jump information in notification message 1.

[0307] Since notification message 2 and notification message 1 contain the same message content and jump information, after receiving the instruction information for jump information in notification message 2, electronic device 100 can find the historical cross-device push notification message 1 based on the information in notification message 2 or electronic device 200, and trigger the jump of notification message 1 based on the jump information in notification message 1.

[0308] Alternatively, the notification collaboration service in the electronic device 100 can also open the application page corresponding to notification message 1 in application X based on the jump information in notification message 1 after application X is launched.

[0309] Referring to Figure 2F, the application page corresponding to the notification message 1 displayed by the electronic device 100 can be the video playback page shown in Figure 2F.

[0310] S405. Application X in electronic device 100 sends the display content of application X to the notification collaboration service in electronic device 100.

[0311] After application X is launched, or after application X opens the application page corresponding to notification message 1, it can send the display content of application X to the notification collaboration service so that the notification collaboration service can project the display content to electronic device 200.

[0312] S406. The notification coordination service in electronic device 100 sends the display content of application X to the notification coordination service in electronic device 200.

[0313] In some implementations, application X in electronic device 100 can also change the display content of application X based on user operation and send the changed display content to electronic device 200.

[0314] S407. The notification collaboration service in electronic device 200 displays the content of application X through multi-screen collaboration.

[0315] Referring to Figure 2G, the content displayed by application X on electronic device 200 can be the content in window 204 shown in Figure 2G.

[0316] In some implementations, the notification collaboration service in electronic device 200 can also send the instruction information of the user operation to electronic device 100 based on the user operation on the display content of application X, so that electronic device 100 can change the display content of application X according to the user operation and send the changed display to electronic device 200, so that electronic device 200 can change the display content on electronic device 100 across devices based on the user operation.

[0317] As can be seen from steps S401-S407, when electronic device 200 detects that the user has performed a jump operation on the notification message, electronic device 200 can initiate a jump to electronic device 100 for the notification message and display the content of the notification message after the jump by screen projection. In this way, even if the application corresponding to the notification message is not installed on electronic device 200, electronic device 200 can still display the content of the notification message after the jump, so that the user can understand the details of the notification message and process the notification message.

[0318] In some implementations, in addition to enabling cross-device push of notification messages, the electronic device 100 can also push the notification message again locally if specified conditions are met.

[0319] Figure 14 is a flowchart illustrating another message notification method provided in an embodiment of this application.

[0320] As shown in Figure 14, the message notification method may include:

[0321] S501. Electronic device 100 displays notification message 1.

[0322] For example, the electronic device 100 may display notification message 1 in the form of a banner, or the electronic device 100 may display notification message 1 in the notification bar, or the electronic device 100 may display notification message 1 on the lock screen.

[0323] For example, the notification message 1 may refer to the notification message 101 shown in Figures 3A, 4A, 5A, 6A, and 8A.

[0324] S502. Electronic device 100 recognizes the first event.

[0325] The first event can be used to instruct the user to trigger a second push notification message 1.

[0326] The first event can be a user action that triggers the notification message to be displayed again, or a first event in which no user action on the notification message 1 is detected during the display of the notification message 1 on the electronic device 100, or a first event in which the user looks at the notification message 1 for less than a threshold during the display of the notification message 1 on the electronic device 100.

[0327] For example, the first event may include the user operation on option 103 as shown in FIG3A, or the first event may include the user operation on option 104 as shown in FIG4A, or the first event may include the user operation on option 106 as shown in FIG5A, or the first event may include the user operation on option 107 as shown in FIG6A, or the first event may include the user operation on option 110 as shown in FIG8A.

[0328] S503. When the specified conditions are met, the electronic device 100 displays notification message 3, and the content of notification message 3 is the same as that of notification message 1.

[0329] The specified conditions may include one or more of the following: turning on the screen, unlocking, reaching a specified time, launching a specified application, changing the device's posture, switching displays, changing the device's folding shape, etc.

[0330] For example, if the specified condition is to change the posture, then notification message 3 can be notification message 501 as shown in Figure 3B.

[0331] For example, if the specified condition is to change the folding form of the device, then notification message 3 can be notification message 105 as shown in Figure 4B.

[0332] For example, if the specified condition is to switch displays, then notification message 3 can be the message displayed on the outer screen as shown in Figure 5B.

[0333] For example, if the specified condition is to launch a specified application, then notification message 3 can be notification message 601 as shown in FIG6C.

[0334] For example, if the specified condition is the arrival of a specified time, then notification message 3 can be notification message 111 as shown in Figure 8B.

[0335] It should be understood that for details not described in steps S501-S503, such as the first event where the user triggers a push notification message again, or the selection of specified conditions based on user actions, please refer to the relevant content in steps S101-S103 above, which will not be repeated here.

[0336] In this embodiment of the application, notification message 3 may also be referred to as a third notification message.

[0337] As can be seen from steps S501-S503, after displaying notification message 1, if the electronic device 100 recognizes an event that requires pushing notification message 1 again, it can display notification message 3 under specified conditions to achieve the effect of pushing notification message again and prevent the user from missing the notification message.

[0338] The following example uses the user's action of triggering the re-display of the notification message by the first event recognized by the electronic device 100 to describe in detail the module interaction process involved when the electronic device 100 pushes the notification message again under specified conditions.

[0339] Figure 15 is a diagram showing the module interactions involved when the electronic device 100 provided in this application pushes a notification message again under specified conditions.

[0340] S601. Application X in electronic device 100 sends notification message 1 to the notification center in electronic device 100.

[0341] S602. Notification center push notification message in electronic device 100.

[0342] S603. The notification center in the electronic device 100 detects that the user has triggered an operation to push a notification message again under specified conditions.

[0343] The specified conditions can be selected by the user or preset by the electronic device 100. This application embodiment does not impose any restrictions on this.

[0344] S604. The notification center in electronic device 100 sends the message content and specified conditions of notification message 1 to the notification collaboration service in electronic device 100.

[0345] The notification center in electronic device 100 sends the message content of notification message 1 to the notification coordination service in electronic device 100, which allows the message content of notification message 1 to be temporarily stored in the notification coordination service.

[0346] In addition, after obtaining the specified conditions, the notification collaboration service can detect the status of the electronic device 100 and identify whether the electronic device 100 meets the specified conditions, so that the electronic device 100 can push notification messages in a timely manner when the specified conditions are met.

[0347] For example, if the specified condition is a change in the folding shape of the device, the notification collaboration service of the electronic device 100 can detect the folding shape of the electronic device 100 and identify whether the folding shape of the electronic device 100 has changed.

[0348] S605. Under specified conditions, the notification coordination service in electronic device 100 generates notification message 3 based on the message content of notification message 1.

[0349] For example, the electronic device 100 can encapsulate the message content of notification message 1 into a notification message that can be displayed on the user interface, namely notification message 3.

[0350] S606. The notification collaboration service in electronic device 100 sends a notification message 3 to the notification center in electronic device 100.

[0351] S607. Notification center push notification message in electronic device 100 3.

[0352] As can be seen from steps S601-S607, after the electronic device 100 pushes a notification message once, if the electronic device 100 detects that the user pushes the notification message again, the electronic device 100 can temporarily store the notification message and push the notification message again when the electronic device 100 meets the specified conditions, so as to remind the user again.

[0353] It is understood that for details regarding the content not described in steps S601-S607, please refer to the relevant content in steps S201-S210 mentioned above, which will not be repeated here.

[0354] Figure 16 is a schematic diagram of the hardware structure of the electronic device 300 provided in the embodiment of this application.

[0355] The electronic device 300 can be a mobile phone, tablet computer, desktop computer, laptop computer, handheld computer, notebook computer, ultra-mobile personal computer (UMPC), netbook, as well as cellular phone, personal digital assistant (PDA), augmented reality (AR) device, virtual reality (VR) device, artificial intelligence (AI) device, wearable device, in-vehicle device, smart home device and / or smart city device. The embodiments of this application do not impose any special restrictions on the specific type of the electronic device.

[0356] Electronic device 300 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, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity 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.

[0357] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 300. In other embodiments of this application, the electronic device 300 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0358] Processor 110 may include one or more processing units, such as application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU). These different processing units may be independent devices or integrated into one or more processors.

[0359] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.

[0360] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0361] The wireless communication function of electronic device 300 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

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

[0363] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 300. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0364] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates 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 processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 170A, receiver 170B, etc.) or displays images or videos through the display screen 194. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

[0365] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 300, 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), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, demodulates and filters the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, frequency modulate and amplify them, and then convert them into electromagnetic waves for radiation via antenna 2.

[0366] In some embodiments, antenna 1 of electronic device 300 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling electronic device 300 to communicate with networks and other devices via wireless communication technology. The wireless communication technology 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 technologies, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0367] Electronic device 300 implements display functions through a GPU, display screen 194, and application processor. The GPU is a microprocessor for image processing, connecting the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0368] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. In some embodiments, an electronic device may include one or N displays screens 194, where N is a positive integer greater than 1.

[0369] Electronic device 300 can achieve shooting function through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0370] Camera 193 is used to capture still images or videos. In some embodiments, electronic device 300 may include one or N cameras 193, where N is a positive integer greater than 1.

[0371] Internal memory 121 may include one or more random access memory (RAM) and one or more non-volatile memory (NVM).

[0372] The random access memory can be directly read and written by the processor 110. It can be used to store executable programs (such as machine instructions) of the operating system or other running programs, as well as user and application data.

[0373] Non-volatile memory can also store executable programs and user and application data, and can be pre-loaded into random access memory for direct reading and writing by the processor 110.

[0374] Electronic device 300 can implement audio functions, such as music playback and recording, through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0375] Touch sensor 180K, also known as a "touch device," can be located on display screen 194. The touch sensor 180K and display screen 194 together form a touchscreen, also known as a "touchscreen." Touch sensor 180K detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 194. In other embodiments, touch sensor 180K may also be located on the surface of electronic device 300, in a different position than display screen 194.

[0376] In this embodiment of the application, the electronic device 300 can be the aforementioned electronic device 100, wherein:

[0377] The processor 110 can be used to identify events that trigger the user to re-display the notification message, and to identify whether specified conditions are met.

[0378] The display screen 194 can be used to display notification messages, or further, to display notification messages when specified conditions are met.

[0379] The mobile communication module 150 or the wireless communication module 160 can be used to send notification messages, specify conditions, or receive relevant information from other devices, such as display status, device folding mode, etc.

[0380] In this embodiment of the application, the electronic device 300 can be the aforementioned electronic device 200, wherein:

[0381] Processor 110 can be used to identify whether specified conditions are met.

[0382] The display screen 194 can be used to display notification messages, or further, to display notification messages when specified conditions are met.

[0383] The mobile communication module 150 or the wireless communication module 160 can be used to receive the message content of notification messages, specify conditions, or send relevant information about the device, such as the display status, the folding mode of the device, etc.

[0384] The electronic device can be a portable terminal device running Harmony, iOS, Android, Microsoft, or other operating systems, such as a mobile phone, tablet computer, or wearable device. It can also be a non-portable terminal device such as a laptop computer or desktop computer with a touch-sensitive surface or touch panel. The software system of the electronic device 300 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment uses a layered Android system as an example to illustrate the software structure of the electronic device 300.

[0385] Figure 17 is a software structure block diagram of an electronic device 300 according to an embodiment of this application.

[0386] A layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0387] The application layer can include a series of application packages.

[0388] As shown in Figure 17, the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and SMS.

[0389] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0390] As shown in Figure 17, the application framework layer may include a notification center, notification collaboration service, window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

[0391] The notification center is used to retrieve notification messages, display them, and manage notification message navigation.

[0392] The notification coordination service can be used to manage the re-push of notification messages. Under specified conditions, it can control the re-push of notification messages on the local machine or on other devices.

[0393] The window manager is used to manage windowed applications. It can retrieve screen size, determine the presence of a status bar, lock the screen, and capture screenshots, among other things.

[0394] Content providers store and retrieve data, making that data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

[0395] A view system includes visual controls, such as controls for displaying text and controls for displaying images. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text notification icon could include views for displaying text and views for displaying images.

[0396] The phone manager is used to provide communication functions for electronic devices 300. For example, it manages call status (including connection and disconnection).

[0397] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0398] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of download completion or other notification alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating electronic devices, and flashing indicator lights.

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

[0400] The core library consists of two parts: one part is the functionalities that need to be called by the Java language, and the other part is the Android core library.

[0401] The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0402] System libraries can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), etc.

[0403] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0404] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

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

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

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

[0408] The following example, using a scene of capturing a photograph, illustrates the workflow of the software and hardware of the electronic device 300.

[0409] When touch sensor 180K receives a touch operation, a corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes the touch operation into a raw input event (including touch coordinates, timestamp of the touch operation, etc.). The raw input event is stored in the kernel layer. The application framework layer retrieves the raw input event from the kernel layer and identifies the control corresponding to the input event. Taking a single touch operation as an example, where the corresponding control is the camera application icon, the camera application calls the interface of the application framework layer to launch the camera application, and then calls the kernel layer to launch the camera driver, capturing still images or videos through camera 193.

[0410] It should be understood that each step in the above method embodiments can be completed by integrated logic circuits in the processor hardware or by instructions in software form. The method steps disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules in the processor.

[0411] This application also provides an electronic device, which may include a memory and a processor. The memory may be used to store a computer program; the processor may be used to invoke the computer program in the memory to cause the electronic device to perform the method executed by electronic device 100 or electronic device 200 in any of the above embodiments.

[0412] This application also provides a chip system including at least one processor for implementing the functions involved in the methods performed by electronic device 100 or electronic device 200 in any of the above embodiments.

[0413] In one possible design, the chip system also includes a memory for storing program instructions and data, which may be located within or outside the processor.

[0414] The chip system can consist of chips or include chips and other discrete components.

[0415] Optionally, the chip system may contain one or more processors. These processors can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor, implemented by reading software code stored in memory.

[0416] Optionally, the chip system may contain one or more memories. The memory may be integrated with the processor or disposed separately from it; this application embodiment does not limit this. For example, the memory may be a non-transient processor, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or disposed separately on different chips. This application embodiment does not specifically limit the type of memory or the arrangement of the memory and processor.

[0417] For example, the chip system may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a micro controller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0418] This application also provides a computer program product, which includes a computer program (also referred to as code or instructions) that, when run, causes a computer to perform the method executed by either electronic device 100 or electronic device 200 in any of the above embodiments.

[0419] This application also provides a computer-readable storage medium storing a computer program (also referred to as code or instructions). When the computer program is run, it causes a computer to perform the method executed by either electronic device 100 or electronic device 200 in any of the above embodiments.

[0420] It should be understood that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method embodiments can be completed by the integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method.

[0421] Additionally, this application also provides an apparatus. Specifically, the apparatus may be a component or module, and may include one or more processors and a memory connected together. The memory stores a computer program. When the computer program is executed by one or more processors, the apparatus performs the methods described in the above-described method embodiments.

[0422] The apparatus, computer-readable storage medium, computer program product, or chip provided in the embodiments of this application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0423] The various embodiments of this application can be combined arbitrarily to achieve different technical effects.

[0424] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as 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, all or part of the processes or functions described in this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0425] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

[0426] In summary, the above description is merely an embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made based on the disclosure of this application should be included within the scope of protection of this application.

Claims

1. A message notification method characterized by, The method includes: The first device displays the first notification message; When the first event is detected, the first device sends the message content of the first notification message to the second device; When the second device meets the first condition, the second device displays a second notification message, the content of which is the same as that of the first notification message. The first condition includes one or more of the following: turning on the screen, unlocking, reaching a first time, launching a first application, changing the device posture, switching the display screen, or changing the device folding mode, wherein the first application is the source application of the first notification message, or the application indicated by the first notification message, or the application selected by the user.

2. The method of claim 1, wherein, If the second device meets the first condition, the second device displays a second notification message, specifically including: If the second device determines that the first condition is met, the second device displays the second notification message; or, The first device sends the message content of the first notification message to the second device, specifically including: When the first device determines that the second device meets the first condition, it sends the message content of the first notification message to the second device.

3. The method according to claim 1 or 2, characterized in that, The second device, while displaying the second notification message, also includes: The second device displays a first prompt message on the second notification message, the first prompt message being used to indicate that the message content of the second notification message comes from the first device.

4. The method according to any one of claims 1 to 3, characterized in that, After the second device displays the second notification message, the method further includes: The second device detects a first operation performed on the second notification message; In response to the first operation, the second device launches a second application or displays a first page, wherein the second application is the application indicated by the jump information in the first notification message, and the first page is the page indicated by the jump information in the first notification message.

5. The method according to any one of claims 1 to 4, characterized in that, After the second device displays the second notification message, the method further includes: The second device detects a first operation performed on the second notification message; The second device sends the instruction information for the first operation to the first device; In response to the first operation, the first device launches a second application or displays a first page, wherein the second application is the application indicated by the jump information in the first notification message, and the first page is the page indicated by the jump information in the first notification message; The first device will send the content displayed after launching the second application or the first page to the second device; The second device displays the content displayed after the first device launches the second application or the first page.

6. The method of claim 5, wherein, The second device sends the instruction information for the first operation to the first device, specifically including: The second device sends the instruction information for the first operation to the first device if the second application is not installed.

7. The method according to any one of claims 1 to 3, characterized in that, After the second device displays the second notification message, the method further includes: The second device detects a first operation performed on the second notification message; The second device launches a third application without the second application being installed; the second application is the application indicated by the jump information in the first notification message, and the third application has the same functions as the second application.

8. A message notification method characterized by comprising: The method includes: The first device displays the first notification message; The first device detected the first event; When the first device meets the first condition, the third notification message is displayed, and the content of the third notification message is the same as that of the first notification message. The first condition includes one or more of the following: turning on the screen, unlocking, reaching a first time, launching a first application, changing the device posture, switching the display screen, or changing the device folding mode, wherein the first application is the source application of the first notification message, or the application indicated by the first notification message, or the application selected by the user.

9. The method according to any one of claims 1-8, characterized in that, The first event is a user action that triggers the notification message to be displayed again; or, The first event is an event in which the first device does not receive an operation applied to the first notification message while displaying the first notification message; or, The first event is an event in which the user gazes at the first notification message for a duration less than a first threshold.

10. The method of claim 9, wherein, The user operation that triggers the notification message to be displayed again includes: a second operation acting on the first notification message; and a third operation acting on the first option among the multiple options after the first device displays multiple options in response to the second operation, wherein the multiple options are used to indicate different conditions, and the first option is used to indicate the first condition.

11. The method according to any one of claims 1 to 10, characterized in that, The first condition is determined based on one or more of the following: the message content, source application, and importance of the first notification message, or the first condition is a condition preset by the first device.

12. An electronic device, comprising: The device includes a memory, one or more processors, and one or more programs; when the one or more processors execute the one or more programs, the electronic device causes the electronic device to perform the method as described in any one of claims 1 to 11.

13. A computer-readable storage medium comprising instructions, characterized in that, When the instructions are executed on an electronic device, the electronic device causes the electronic device to perform the method as described in any one of claims 1 to 11.

14. A computer program product, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the method as described in any one of claims 1 to 11.

Images