Live notification sharing method, and electronic device and server

Abstract

Provided in the present application are a live notification sharing method, and an electronic device and a server. The method comprises: in response to a first operation of a first user, a first electronic device creating, in a first application of the first electronic device, a first task related to a user account of a second user; the first electronic device generating a first live notification corresponding to the first task, and displaying the first live notification; and the first electronic device sending a first request message to a server, so as to request the server to share the first live notification with a second electronic device corresponding to the user account of the second user. By means of the solution, when a user triggers the creation of a first task in a first electronic device, the first electronic device can request a server to share a first live notification with a second electronic device corresponding to a second user account related to the first task, such that the second electronic device can synchronously display the live notification corresponding to the first task, thereby realizing convenient cross-device sharing of live notifications, and improving the user experience.

Description

A method for sharing live notifications, an electronic device, and a server

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202410798930.X, filed on June 19, 2024, with the State Intellectual Property Office of the People's Republic of China, entitled "A method for sharing live notifications, an electronic device and a server", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of terminal technology, and in particular to a method for sharing live notifications, an electronic device, and a server. Background Technology

[0004] As more applications are installed on electronic devices, the number of notification messages displayed on these devices is also increasing. For notifications with high timeliness requirements, such as food delivery notifications and express delivery notifications, electronic devices can display live notifications on the screen. Live notifications can include progress information of the events related to the notification. For example, after a user creates a food delivery order in a food delivery application, the electronic device can display a live notification corresponding to that order. The live notification for that order can include progress information such as "Preparing food" or "Delivering food".

[0005] However, current live notifications only support display on the electronic device that created the application task. If a user wants to share the progress information of the application task with other users, the user needs to launch the application on the electronic device, find the application task in the application, and then share the information of the application task with other users through the social function of the application or other social applications. The operation is cumbersome and the user experience is poor. Summary of the Invention

[0006] This application provides a live notification sharing method, electronic device, and server, which provide a convenient way to share live notifications across devices.

[0007] In a first aspect, this application provides a live notification method, which can be performed by a first electronic device. The method includes: in response to a first operation by a first user, the first electronic device creates a first task related to a second user's user account in a first application of the first electronic device; the first electronic device generates a first live notification corresponding to the first task, displays the first live notification, the first live notification including task progress information of the first task; and the first electronic device sends a first request message to a server, the first request message requesting the server to share the first live notification to a second electronic device corresponding to the second user's user account.

[0008] In the above method, when a user triggers the creation of a first task on a first electronic device, and the first electronic device generates a first live notification corresponding to the first task, the first electronic device can request the server to share the first live notification with the second electronic device corresponding to the second user account associated with the first task, so that the second electronic device can synchronously display the live notification corresponding to the first task, thereby realizing convenient sharing of live notifications across devices and improving user experience.

[0009] In one possible design, the first request message includes the second user's account information, which includes at least one of the account name and contact information entered by the first user when creating the first task. With this design, after the first user enters the second user's account information when creating the first task, the first electronic device can automatically request the server to share the live notification based on the second user's account information, thus eliminating the need for the user to manually select the user they want to share with, simplifying the user experience.

[0010] In one possible design, the method further includes: before the first task has ended, obtaining the updated task progress information of the first task, and sending a second request message to the server. The second request message requests the server to instruct the second electronic device to update the live notification corresponding to the first task, and the second request message includes the updated task progress information of the first task. With this design, before the first task in the first electronic device ends, as the first task progresses, the task progress information of the first task displayed in the first live notification changes. The first electronic device can request the server to instruct the second electronic device to update the live notification corresponding to the first task, thereby synchronizing the task progress information of the first task to the second electronic device in real time, ensuring the real-time nature of the task progress information of the first task in the live notification displayed by the second electronic device.

[0011] Optionally, the first electronic device obtains the progress information of the first task according to a preset period and sends a second request message to the server, so that the first electronic device can periodically request the server to instruct the second electronic device to update the real-time notification corresponding to the first task, and synchronize the progress information of the first task with the second electronic device in a timely manner.

[0012] In one possible design, the method further includes: displaying a sharing control in the first live notification; and, in response to a second operation by the first user on the sharing control, sending a third request message to a server, the third request message requesting the server to share the first live notification to a third electronic device corresponding to a third user's user account. With this design, the first live notification on the first electronic device can also display a sharing control, allowing the first user to actively choose to share the first live notification with other users, thus satisfying the user's need to share live notifications with different users.

[0013] In one possible design, the method further includes: after the first task ends, destroying the first live notification displayed on the first electronic device; and sending a fourth request message to the server, the fourth request message requesting the server to instruct the second electronic device to destroy the live notification corresponding to the first task. With this design, after the first task ends, the first electronic device can destroy the first live notification, and the first electronic device requests the server to instruct the second electronic device to destroy the live notification corresponding to the first task, thus preventing the live notification corresponding to an ended task from still occupying display resources.

[0014] In one possible design, the method further includes: displaying at least one first control corresponding to the status of the first task in the first live notification, wherein the at least one first control is used to provide an interactive entry point for business related to the first task. Through this design, the first electronic device can also display at least one first control corresponding to the status of the first task in the first live notification, allowing the user to trigger operations on the first control without unlocking, providing a more convenient interaction method and improving the user experience.

[0015] In one possible design, before displaying at least one first control corresponding to the state of the first task in the first live notification, the method further includes: obtaining state information of the first task corresponding to a first moment; and determining the at least one first control to be displayed in the first live notification based on the state information of the first task corresponding to the first moment. With this design, the electronic device can determine the control displayed in the first live notification based on the state of the first task, thereby adapting to the different functional interaction needs of the user in different states of the first task.

[0016] In one possible design, the first moment is the moment when the state of the first task changes, and / or, the first moment is a moment determined based on the start time of the first task and a second preset period. Through this design, the first electronic device can periodically determine the controls displayed in the first live notification, and / or, the first electronic device can re-determine the controls displayed in the first live notification when the state of the first task changes, in order to timely meet the user's interaction needs.

[0017] In one possible design, determining the at least one first control displayed in the first live notification based on the state information of the first task corresponding to the first moment includes: inputting the device identifier of the first electronic device, the application identifier of the first application, the type information of the first task, and the state information of the first task corresponding to the first moment into an intent-aware model; obtaining the probability value of each control among multiple controls related to the first task output by the intent-aware model; and selecting the at least one first control based on the probability value of each control among the multiple controls. Through this design, the at least one first control determined by the intent-aware model by the first electronic device is used to infer the control the user expects to use in the current state of the first task, thus better meeting the user's interaction needs.

[0018] In one possible design, at least one control with a probability value greater than a preset threshold is selected in descending order of the probability values ​​corresponding to the plurality of controls, and the selected at least one control is used as the at least one first control.

[0019] In one possible design, the number of the at least one first control is less than or equal to Q, where Q is a positive integer and is the maximum number of controls that the display style of the first live notification supports displaying.

[0020] In one possible design, the method further includes: sending a fifth request message to the server, the fifth request message requesting the server to instruct the second electronic device to update the controls in the live notification corresponding to the first task, the fifth request message including the identifier of the at least one first control. With this design, after the first electronic device displays at least one first control in the first live notification, the first electronic device can also request the server to instruct the second electronic device to update the controls in the live notification corresponding to the first task, thereby enabling the second electronic device to update the controls displayed in the second live notification in a timely manner, meeting the interaction needs of the second user.

[0021] Secondly, this application provides a live notification sharing method, which can be executed by a server. The method includes: the server receiving a first request message from a first electronic device, the first request message requesting the server to share a first live notification from the first electronic device to a second electronic device corresponding to a second user's user account, the first live notification being a live notification corresponding to a first task related to the second user's user account in a first application of the first electronic device; determining the device identifier of the second electronic device corresponding to the second user's user account based on a correspondence between the second user's user account and multiple user accounts and device identifiers of multiple electronic devices stored by the server; and sending information about the first live notification to the second electronic device based on the device identifier of the second electronic device.

[0022] In the above method, the first electronic device can request the server to share the first live notification with the second electronic device associated with the user account of the second user. The server can manage the user account and the identifier of the electronic device corresponding to the user account, thereby determining the device identifier of the second electronic device and sending the information of the first live notification to the second electronic device, so as to realize convenient sharing of live notifications across devices.

[0023] In one possible design, the method further includes: receiving a second request message sent by the first electronic device, the second request message requesting the server to instruct the second electronic device to update the live notification corresponding to the first task, the second request message including updated task progress information of the first task; and sending the updated task progress information of the first task in the second request message to the second electronic device. With this design, the server can synchronize the task progress information of the first task to the second electronic device in real time according to the second request message sent by the first electronic device, ensuring the real-time nature of the task progress information of the first task in the live notification corresponding to the first task displayed by the second electronic device.

[0024] In one possible design, after sending the first live notification information to the second electronic device based on the device identifier of the second electronic device, the method further includes: storing update status information corresponding to the second electronic device, the update status information being used to indicate the update status of the first live notification shared by the first electronic device to the second electronic device. Through this design, the server can manage the status of the live notification corresponding to the second electronic device receiving the live notification sharing, thereby achieving cloud-based control of live notification sharing.

[0025] In one possible design, the method further includes: receiving a third request message sent by the first electronic device, the third request message being used to request the server to share the first live notification to the third electronic device corresponding to the user account of the third user; determining the device identifier of the third electronic device corresponding to the user account of the third user based on the correspondence between the user account of the third user and the device identifiers of multiple user accounts and multiple electronic devices stored by the server; and sending the information of the first live notification to the third electronic device based on the device identifier of the third electronic device.

[0026] In one possible design, the method further includes: receiving a fourth request message sent by the first electronic device, the fourth request message being used to request the server to instruct the second electronic device to destroy the live notification corresponding to the first task; and sending a destruction notification message to the second electronic device, the destruction notification message being used to instruct the second electronic device to destroy the live notification corresponding to the first task. With this design, the server can instruct the second electronic device to destroy the live notification corresponding to the first task based on the fourth request message sent by the first electronic device, thereby preventing live notifications corresponding to completed tasks from still occupying display resources.

[0027] In one possible design, after sending a destruction notification message to the second electronic device, the method further includes: receiving a feedback message sent by the second electronic device, the feedback message indicating that the second electronic device has destroyed the live notification corresponding to the first task; and deleting the update status information corresponding to the second electronic device stored in the server. With this design, after determining that the second electronic device has destroyed the live notification corresponding to the first task, the server deletes the update status information corresponding to the second electronic device stored in the server, saving server storage resources.

[0028] In one possible design, the method further includes: receiving a fifth request message sent by the first electronic device, the fifth request message being used to request the server to instruct the second electronic device to update the controls in the live notification corresponding to the first task, the fifth request message including the identifier of at least one first control, the at least one first control being a control corresponding to the status of the first task, the at least one first control being used to provide an interactive entry point corresponding to the business related to the first task; and sending the identifier of the at least one first control to the second electronic device. With this design, the server can instruct the second electronic device to update the controls in the live notification corresponding to the first task based on the fifth request message sent by the first electronic device, thus timely meeting the interactive needs of the second user.

[0029] Thirdly, this application provides a live notification sharing method, which can be executed by a first server. The method includes: receiving a first request message sent by a first electronic device, the first request message requesting the first server to share a first live notification from the first electronic device to a second electronic device corresponding to the application user account of a second user, wherein the first live notification is a live notification corresponding to a first task related to the application user account of the second user in a first application of the first electronic device; determining the system account information of the second user corresponding to the application account information of the second user based on the correspondence between the application account information of the second user and the application account information and system account information of multiple users stored in the first server; and sending a sixth request message to the second server, the sixth request message requesting the second server to share the first live notification to the second electronic device corresponding to the system account information of the second user, the sixth request message including the system account information of the second user.

[0030] In the above method, the first electronic device can request the first server to share the first live notification to the second electronic device corresponding to the application user account of the second user. The first server stores the correspondence between application account information and system account information of multiple users. After the first server determines the system account information of the second user, it requests the second server to share the first live notification to the electronic device corresponding to the system account information of the second user. Thus, when the first electronic device obtains the application account information of the second user, it can also share the first live notification to the second electronic device of the second user, realizing convenient cross-device sharing of live notifications and improving user experience.

[0031] In one possible design, the first server is the server corresponding to the first application, and the second server is the server corresponding to the second electronic device.

[0032] Fourthly, this application provides a live notification sharing method, which can be executed by a second electronic device. The method includes: receiving information of a first live notification sent by a server, wherein the first live notification is a live notification corresponding to a first task related to a user account of the second user in a first application of the first electronic device; generating a second live notification based on the information of the first live notification; and displaying the second live notification on the second electronic device, wherein the second live notification includes task progress information of the first task in the first application of the first electronic device.

[0033] In the above method, the second electronic device can receive information from the first electronic device regarding the first live notification sent by the server. The second electronic device can then display a second live notification on its own device based on the information in the first live notification. The second user can then view the task progress information of the first task related to the second user on the first electronic device, thus satisfying the second user's need to understand the first task and improving the user experience.

[0034] In one possible design, the task progress information of the first task displayed in the second live notification is the same as the task progress information of the first task displayed in the first live notification. This design ensures the real-time nature of the task progress displayed in the second live notification, allowing the second user to promptly and accurately ascertain the task progress of the first task.

[0035] In one possible design, the display interface of the second electronic device when displaying the second live notification includes any of the following: lock screen, desktop, negative one screen, or the interface of any application. With this design, the second electronic device can display the second live notification in any display scenario after receiving the information from the first live notification.

[0036] In one possible design, the second live notification may have the same or different display styles as the first live notification, and the display style of the second live notification may be related to the display scenario of the second electronic device.

[0037] In one possible design, before generating the second live notification based on the information from the first live notification, the method further includes: displaying a first reminder message, the first reminder message being used to ask the second user whether to receive the live notification shared by the first user; and receiving a confirmation operation triggered by the second user. With this design, the second electronic device can display the second live notification only after the second user confirms receipt of the live notification shared by the first user, better meeting user needs.

[0038] In one possible design, the method further includes: receiving task progress information of the first task updated by the server; and displaying the task progress information of the first task updated in the second live notification.

[0039] In one possible design, the progress of the first task shown in the second live notification is the same as the progress of the first task shown in the first live notification.

[0040] In one possible design, the method further includes: displaying a sharing control in the second live notification; and, in response to a third operation by the second user on the sharing control, sending a seventh request message to the server, the seventh request message requesting the server to share the second live notification to a fourth electronic device corresponding to the user account of the fourth user. With this design, the second user can also actively choose to share the second live notification with other users, satisfying the user's need to further share live notifications.

[0041] In one possible design, the method further includes: receiving a destruction notification message sent by the server, the destruction notification message instructing the second electronic device to destroy the live notification corresponding to the first task; and destroying the second live notification. With this design, after the first task ends, the second electronic device can promptly destroy the second live notification according to the server's instruction, preventing the live notification corresponding to the completed task from still occupying display resources.

[0042] In one possible design, the method further includes: receiving an identifier of at least one first control related to the first task sent by the server, the at least one first control being used to provide an interactive entry point corresponding to the business related to the first task; and displaying the at least one first control in the second live notification. With this design, the second electronic device can promptly update the controls displayed in the second live notification based on the identifier of at least one first control sent by the server, thus meeting the interaction needs of the second user.

[0043] Fifthly, this application provides a live notification sharing method, which can be executed by a communication system including a first electronic device, a second electronic device, and a server. The method includes: in response to a first operation by a first user, the first electronic device creates a first task related to a second user's user account in a first application of the first electronic device; the first electronic device generates a first live notification corresponding to the first task and displays the first live notification, the first live notification including task progress information of the first task; the first electronic device sends a first request message to the server, the first request message requesting the server to share the first live notification to the second electronic device corresponding to the second user's user account; the server determines the device identifier of the second electronic device corresponding to the second user's user account based on the correspondence between the second user's user account and multiple user accounts and device identifiers of multiple electronic devices stored by the server; the server sends information of the first live notification to the second electronic device based on the device identifier of the second electronic device; the second electronic device generates a second live notification based on the information of the first live notification, and displays the second live notification, the second live notification including task progress information of the first task in the first application of the first electronic device.

[0044] In one possible design, the task progress of the first task displayed in the second live notification is the same as the task progress of the first task displayed in the first live notification.

[0045] In one possible design, the method further includes: before the first task is completed, the first electronic device obtains the task progress information of the first task with updated progress; the first electronic device sends a second request message to the second server, the second request message being used to request the second server to instruct the second electronic device to update the live notification corresponding to the first task; the second request message includes the task progress information of the first task with updated progress; the second server sends the task progress information of the first task with updated progress from the second request message to the second electronic device; the second electronic device displays the task progress information of the first task with updated progress in the second live notification.

[0046] In one possible design, the progress of the first task shown in the second live notification of the second electronic device is the same as the progress of the first task shown in the first live notification of the first electronic device.

[0047] In one possible design, the method further includes: the first electronic device displaying a sharing control in the first live notification; in response to a second operation by the first user on the sharing control, the first electronic device sending a third request message to the server, the third request message requesting the server to share the first live notification to a third electronic device corresponding to a third user's user account; the server determining the device identifier of the third electronic device corresponding to the third user's user account based on the correspondence between the third user's user account and multiple user accounts and device identifiers of multiple electronic devices stored by the server; and the server sending the information of the first live notification to the third electronic device based on the device identifier of the third electronic device.

[0048] In one possible design, the method further includes: the second electronic device displaying a sharing control in the second live notification; in response to a third operation by the second user on the sharing control, the second electronic device sending a seventh request message to the server, the seventh request message requesting the server to share the second live notification to a fourth electronic device corresponding to a fourth user's user account; the server determining the device identifier of the fourth electronic device corresponding to the fourth user's user account based on the correspondence between the fourth user's user account and multiple user accounts and device identifiers stored by the server; and the server sending the information of the second live notification to the fourth electronic device based on the device identifier of the fourth electronic device.

[0049] In one possible design, the method further includes: after the first task ends, the first electronic device destroys the first live notification displayed on the first electronic device; the first electronic device sends a fourth request message to the server, the fourth request message being used to request the server to instruct the second electronic device to destroy the live notification corresponding to the first task; the server sends a destruction notification message to the second electronic device, the destruction notification message being used to instruct the second electronic device to destroy the live notification corresponding to the first task; and the second electronic device destroys the second live notification.

[0050] In one possible design, the method further includes: the first electronic device displays at least one first control corresponding to the status of the first task in the first live notification, the at least one first control being used to provide an interactive entry point corresponding to the business related to the first task.

[0051] In one possible design, before the first electronic device displays at least one first control corresponding to the state of the first task in the first live notification, the method further includes: the first electronic device acquiring state information of the first task corresponding to a first moment; and the first electronic device determining the at least one first control to be displayed in the first live notification based on the state information of the first task corresponding to the first moment.

[0052] In one possible design, the first moment is the moment when the state of the first task changes, or the first moment is the moment determined based on the start time of the first task and a second preset period.

[0053] In one possible design, the first electronic device determines the at least one first control displayed in the first live notification based on the status information of the first task corresponding to the first time moment, including: the first electronic device inputting the device identifier of the first electronic device, the application identifier of the first application, the type information of the first task, and the status information of the first task corresponding to the first time moment into the intent-aware model; the first electronic device obtaining the probability value corresponding to each of the multiple controls related to the first task output by the intent-aware model; and the first electronic device selecting the at least one first control based on the probability value corresponding to each of the multiple controls.

[0054] In one possible design, the method further includes: the first electronic device sending a fifth request message to the server, the fifth request message being used to request the server to instruct the second electronic device to update the controls in the live notification corresponding to the first task, the fifth request message including the identifier of the at least one first control; the second server sending the identifier of the at least one first control to the second electronic device; and the second electronic device displaying the at least one first control in the second live notification.

[0055] Sixthly, this application provides a live notification sharing method, which can be executed by a first electronic device. The method includes: the first electronic device, in response to a first user's first operation, creating a first task in a first application of the first electronic device, generating a first live notification corresponding to the first task, and displaying the first live notification. The first live notification includes task progress information of the first task and also includes a sharing control. In response to a second operation by the first user on the sharing control in the first live notification, a third request message is sent to a server. The third request message requests the server to share the first live notification to a third electronic device corresponding to a third user's user account.

[0056] In one possible design, the method further includes: before the first task is completed, obtaining the task progress information of the first task with updated progress, and sending a second request message to the server, the second request message being used to request the server to instruct the second electronic device to update the real-time notification corresponding to the first task, the second request message including the task progress information of the first task with updated progress.

[0057] In one possible design, the method further includes: after the first task ends, destroying the first live notification displayed on the first electronic device; and sending a fourth request message to the server, the fourth request message being used to request the server to instruct the second electronic device to destroy the live notification corresponding to the first task.

[0058] In one possible design, the method further includes: displaying at least one first control corresponding to the status of the first task in the first live notification, wherein the at least one first control is used to provide an interactive entry point corresponding to the business related to the first task.

[0059] In one possible design, before displaying at least one first control corresponding to the state of the first task in the first live notification, the method further includes: obtaining state information of the first task corresponding to a first moment; and determining the at least one first control to be displayed in the first live notification based on the state information of the first task corresponding to the first moment.

[0060] In one possible design, the first moment is the moment when the state of the first task changes, or the first moment is the moment determined based on the start time of the first task and a second preset period.

[0061] In one possible design, determining the at least one first control displayed in the first live notification based on the status information of the first task corresponding to the first time moment includes: inputting the device identifier of the first electronic device, the application identifier of the first application, the type information of the first task, and the status information of the first task corresponding to the first time moment into an intent-aware model; obtaining the probability value corresponding to each of the multiple controls related to the first task output by the intent-aware model; and selecting the at least one first control based on the probability value corresponding to each of the multiple controls.

[0062] In one possible design, the method further includes: sending a fifth request message to the server, the fifth request message being used to request the server to instruct the second electronic device to update the controls in the live notification corresponding to the first task, the fifth request message including the identifier of the at least one first control.

[0063] In a seventh aspect, this application provides an electronic device comprising a plurality of functional modules; the plurality of functional modules interact to implement the methods performed by the first electronic device or the second electronic device in any of the above aspects and their respective embodiments. The plurality of functional modules may be implemented based on software, hardware, or a combination of software and hardware, and the plurality of functional modules may be arbitrarily combined or divided based on specific implementations.

[0064] Eighthly, this application provides an electronic device including at least one processor and at least one memory, wherein the at least one memory stores computer program instructions, and when the electronic device is in operation, the at least one processor executes the method executed by the first electronic device or the second electronic device in any of the above aspects and embodiments.

[0065] Ninthly, this application provides a server comprising multiple functional modules; the multiple functional modules interact to implement the methods executed by the server in any of the above aspects and their embodiments. The multiple functional modules can be implemented based on software, hardware, or a combination of software and hardware, and the multiple functional modules can be arbitrarily combined or divided based on specific implementations.

[0066] In a tenth aspect, this application provides a server including at least one processor and at least one memory, wherein the at least one memory stores computer program instructions, and when the server is running, the at least one processor executes the server execution method of any of the above aspects and their embodiments.

[0067] Eleventhly, this application also provides a computer program product containing instructions that, when the computer program product is run on a computer, cause the computer to perform the method executed by the server or electronic device in any of the above aspects and their respective embodiments.

[0068] In a twelfth aspect, this application also provides a computer-readable storage medium storing a computer program that, when executed by a computer, causes the computer to perform the method performed by the server or electronic device in any of the above aspects and embodiments.

[0069] In a thirteenth aspect, this application also provides a chip for reading a computer program stored in a memory and executing the method performed by a server or electronic device in any of the above aspects and their embodiments.

[0070] In a fourteenth aspect, this application also provides a chip system including a processor for supporting a computer device in implementing the methods performed by a server or electronic device in any of the foregoing aspects and their embodiments. In one possible design, the chip system further includes a memory for storing programs and data necessary for the computer device. The chip system may be composed of chips or may include chips and other discrete devices.

[0071] The technical effects that can be achieved by any of the technical solutions in aspects five to fourteen above can be described with reference to the technical effects that can be achieved by the technical solutions in aspects one to four above, and the repeated parts will not be repeated. Attached Figure Description

[0072] Figure 1 is an example diagram of a real-time notification display style provided in an embodiment of this application;

[0073] Figure 2 is a schematic diagram of a scenario in which a live notification sharing method provided in an embodiment of this application is applicable;

[0074] Figure 3 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;

[0075] Figure 4 is a software structure block diagram of an electronic device provided in an embodiment of this application;

[0076] Figure 5A is a schematic diagram of a live notification sharing method provided in an embodiment of this application;

[0077] Figure 5B is a schematic diagram of a live notification sharing method provided in an embodiment of this application;

[0078] Figure 6 is a schematic diagram of a live notification sharing method provided in an embodiment of this application;

[0079] Figure 7 is a flowchart illustrating a live notification sharing method provided in an embodiment of this application;

[0080] Figure 8 is a flowchart of a live notification sharing method provided in an embodiment of this application;

[0081] Figure 9 is a flowchart of a live notification sharing method provided in an embodiment of this application;

[0082] Figure 10 is a flowchart of a live notification sharing method provided in an embodiment of this application;

[0083] Figure 11 is a schematic diagram of a live notification provided in an embodiment of this application;

[0084] Figure 12 is a schematic diagram of a live notification provided in an embodiment of this application;

[0085] Figure 13 is a flowchart of a live notification sharing method provided in an embodiment of this application;

[0086] Figure 14 is a schematic diagram of the structure of a data processing device provided in an embodiment of this application;

[0087] Figure 15 is a schematic diagram of the structure of a data processing device provided in an embodiment of this application;

[0088] Figure 16 is a possible structural example of a device provided in an embodiment of this application. Detailed Implementation

[0089] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings. In the description of the embodiments of this application, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined with "first" and "second" may explicitly or implicitly include one or more of that feature.

[0090] It should be understood that in the embodiments of this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c can be single or multiple.

[0091] In this embodiment, the notification messages displayed by the electronic device may include live notifications and non-live notifications. Live notifications are used to indicate notifications with high timeliness requirements, such as incoming call notifications, ride-hailing order progress updates, and food delivery order progress updates. Non-live notifications are used to indicate notifications with lower timeliness requirements, such as application update notifications and content recommendations.

[0092] In some embodiments, a user can trigger the creation of a task in an application, mini-program, or cloud service on an electronic device. The electronic device generates and displays a live notification corresponding to the task created by the user. When the electronic device determines that a live notification needs to be displayed, it can determine the display position, display style, display content, and other information of the live notification in different display scenarios based on the current display scenario.

[0093] Optionally, display scenarios include always-on display (AOD), partial AOD, functional AOD, lock screen, notification center, status bar, floating card, desktop display, etc. The display styles of live notifications include, but are not limited to: card style, capsule style, floating window style, and visual image style. Optionally, the display style may also include the display color, such as capsule color, card color, text color, etc.

[0094] For example, Figure 1 is an example diagram of a real-time notification display style provided by an embodiment of this application. Figure 1 uses a ride-hailing order progress notification as an example for illustration. Referring to Figure 1(a), the electronic device can display a card-style real-time notification 101 on the lock screen interface. This real-time notification 101 may include relevant information about the ride-hailing order, allowing the user to view the notification and learn about the progress changes of the ride-hailing order. Referring to Figure 1(b), the electronic device can also display a capsule-style real-time notification 102 on the main interface of the electronic device. Since the capsule-style real-time notification occupies a smaller display area, it can include the main information of the ride-hailing order. As shown in Figure 1(b), the real-time notification 102 includes information about the distance between the vehicle and the user in the ride-hailing order.

[0095] It should be noted that the live notification display style shown in Figure 1 is only an example and not a limitation. In specific implementations, electronic devices may also display live notifications in other display styles or in other display areas of the electronic device. This application embodiment does not limit this.

[0096] After a user triggers the creation of a task, the electronic device generates and displays a live notification corresponding to the task. However, this live notification can only be displayed on the electronic device that triggered the task. In some scenarios, the task created by the user may be related to other users, such as user A hailing a taxi for user B or user A ordering takeout for user B. In such cases, user A can only notify user B of the task-related information through social applications or other means, resulting in a poor user experience.

[0097] Based on the above problems, this application provides a live notification sharing method. This method can be applied to the scenario shown in Figure 2. Referring to Figure 2, the scenario to which the live notification sharing method provided in this application is applicable may include a first electronic device, a second electronic device, and a system server. The system server can provide cloud services such as account management and message push for the electronic device. In specific implementation, the system server can be implemented by a computing device cluster, which includes at least one computing device. The at least one computing device can work collaboratively to realize multiple cloud service functions of the system server. Optionally, different functions of the system server can also be implemented by different computing device clusters. For example, computing device cluster 1, i.e., the account server, can be used to implement account management cloud services, and computing device cluster 2, i.e., the push server, can be used to implement message push cloud services. This application does not limit this. That is, the system server can include both an account server and a push server; or the system server may not distinguish between account servers and push servers. Optionally, the scenario to which the live notification sharing method provided in this application is applicable may also include an application server. This application server is used to provide cloud services for application clients installed on the electronic device and to manage user data of the application clients. The application server and the system server can be the same server or different servers.

[0098] In this embodiment, referring to the scenario shown in Figure 2, the first electronic device and the second electronic device can be from the same manufacturer. Both the first and second electronic devices can access the system server, allowing the system server to provide cloud services such as account management and push notifications. Alternatively, if both the first and second electronic devices have the same application installed, the application server can provide services related to that application. Furthermore, when the first and second electronic devices are from different manufacturers, or when the second electronic device does not have the same application installed as the first application that triggers the creation of a live notification on the first electronic device, the system server and the application server can collaboratively provide services to both devices.

[0099] In the live notification sharing method provided in this application embodiment, in response to a first user's first operation, the first operation is used to create a first task related to a second user's user account in a first application. A first electronic device generates a first live notification corresponding to the first task and displays the first live notification, which includes task progress information of the first task. The first electronic device sends a first request message to the server, which requests the server to share the first live notification to the second user's second electronic device. The server determines the device identifier of the second electronic device corresponding to the second user's user account and sends the information of the first live notification to the second electronic device according to the device identifier. The second electronic device generates a second live notification according to the information of the first live notification and displays the second live notification, which includes task progress information of the first task in the first electronic device. The functions performed by the server can be performed by the system server in the scenario shown in Figure 2, or by the system server and the application server working together. With this scheme, when a user triggers the creation of a first task on a first electronic device, and the first electronic device generates a first live notification corresponding to the first task, the first electronic device can request the server to share the first live notification with a second electronic device corresponding to a second user account associated with the first task. The server can identify the second electronic device corresponding to the second user account associated with the first task and send the information of the first live notification to the second electronic device. Thus, the second electronic device can synchronously display the second live notification on its screen according to the information of the first live notification, thereby realizing convenient cross-device sharing of live notifications and improving user experience.

[0100] The following describes an electronic device and embodiments for using such an electronic device. The electronic device in this application embodiment can be a tablet computer, mobile phone, in-vehicle device, augmented reality (AR) / virtual reality (VR) device, laptop computer, ultra-mobile personal computer (UMPC), netbook, personal digital assistant (PDA), wearable device, etc. This application embodiment does not impose any limitations on the specific type of electronic device.

[0101] In some embodiments of this application, the electronic device may also be a portable terminal device that includes other functions such as a personal digital assistant and / or a music player. Exemplary embodiments of the portable terminal device include, but are not limited to, devices equipped with... Or portable terminal devices with other operating systems.

[0102] Figure 3 is a schematic diagram of the structure of an electronic device 100 provided in an embodiment of this application. As shown in Figure 3, the electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, 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.

[0103] Processor 110 may include one or more processing units, such as an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors. The controller may serve as the central nervous system and command center of the electronic device 100. The controller can generate operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution. Processor 110 may also include memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that processor 110 has recently used or is repeatedly used. If processor 110 needs to reuse an instruction or data, it can directly retrieve it from the memory. This avoids repeated access, reduces the waiting time of processor 110, and thus improves system efficiency.

[0104] USB interface 130 is a USB standard compliant interface, specifically a Mini USB interface, Micro USB interface, USB Type-C interface, etc. USB interface 130 can be used to connect a charger to charge electronic device 100, and can also be used for data transfer between electronic device 100 and peripheral devices. Charging management module 140 receives charging input from the charger. Power management module 141 connects battery 142, charging management module 140, and processor 110. Power management module 141 receives input from battery 142 and / or charging management module 140, providing power to processor 110, internal memory 121, external memory, display 194, camera 193, and wireless communication module 160, etc.

[0105] The wireless communication function of electronic device 100 can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor, and baseband processor. Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover 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 tuning switches.

[0106] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 100. 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.

[0107] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, 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, performs frequency modulation and filtering of 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, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0108] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling electronic device 100 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).

[0109] The display screen 194 is used to display the display interface of an application, such as the display page of an application installed on the electronic device 100. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include one or N display screens 194, where N is a positive integer greater than 1.

[0110] Camera 193 is used to capture still images or videos. An object is projected onto a photosensitive element by generating an optical image through the lens. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, or other formats. In some embodiments, the electronic device 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0111] Internal memory 121 can be used to store computer executable program code, which includes instructions. Processor 110 executes various functional applications and data processing of electronic device 100 by running the instructions stored in internal memory 121. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system and software code for at least one application program. The data storage area may store data generated during the use of electronic device 100 (e.g., captured images, recorded videos, etc.). Furthermore, internal memory 121 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0112] The external storage interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device. The external memory card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, images, videos, and other files can be saved on the external memory card.

[0113] Electronic device 100 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.

[0114] The sensor module 180 may include a pressure sensor 180A, an acceleration sensor 180B, a touch sensor 180C, etc.

[0115] The pressure sensor 180A is used to sense pressure signals and can convert the pressure signals into electrical signals. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194.

[0116] Touch sensor 180C, also known as a "touch panel," can be located on display screen 194. The touch sensor 180C and display screen 194 together form a touchscreen, also known as a "touch screen." Touch sensor 180C 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 180C may also be located on the surface of electronic device 100, in a different position than display screen 194.

[0117] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch buttons. Electronic device 100 can receive button inputs and generate key signal inputs related to user settings and function control. Motor 191 can generate vibration alerts. Motor 191 can be used for incoming call vibration alerts or for touch vibration feedback. For example, touch operations applied to different applications (such as taking photos, audio playback, etc.) can correspond to different vibration feedback effects. Touch vibration feedback effects can also be customized. Indicator 192 can be an indicator light, used to indicate charging status, battery level changes, or to indicate messages, missed calls, notifications, etc. SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to achieve contact and separation with electronic device 100.

[0118] It is understood that the components shown in Figure 3 do not constitute a specific limitation on the electronic device 100. The electronic device may include more or fewer components than shown, or combine some components, or separate some components, or have different component arrangements. In addition, the combination / connection relationships between the components in Figure 3 can also be adjusted and modified.

[0119] Figure 4 is a software structure block diagram of an electronic device provided in an embodiment of this application. As shown in Figure 4, the software structure of the electronic device can be a layered architecture. For example, the software can be divided into several layers, each with a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the operating system is divided into four layers, from top to bottom: the application layer, the application framework layer (framework, FWK), the runtime and system libraries, and the kernel layer.

[0120] The application layer can include a series of application packages. As shown in Figure 4, the application layer can include camera, settings, skin modules, user interface (UI), third-party applications, etc. Third-party applications can include gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, SMS, etc.

[0121] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer can include some predefined functions. As shown in Figure 4, the application framework layer can include a window manager, content provider, view system, phone manager, resource manager, and notification manager.

[0122] The window manager is used to manage windowed applications. It can obtain the screen size, determine if a status bar is present, lock the screen, and capture screenshots. The content provider stores and retrieves data, making this data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

[0123] 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.

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

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

[0126] 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 message 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.

[0127] The runtime includes the core libraries and the virtual machine. The runtime is responsible for the scheduling and management of the operating system.

[0128] The core library consists of two parts: one part contains the functionalities that the Java language needs to call, and the other part contains the core libraries of the operating system. The application layer and application framework layer run in the 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.

[0129] 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), image processing libraries, etc.

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

[0131] 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.

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

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

[0134] 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.

[0135] The hardware layer can include various types of sensors, such as accelerometers, gyroscopes, and touch sensors.

[0136] It should be noted that the structures shown in Figures 3 and 4 are merely examples of electronic devices provided in the embodiments of this application, and cannot be used to limit the electronic devices provided in the embodiments of this application. In specific implementations, electronic devices may have more or fewer devices or modules than those shown in Figures 3 or 4.

[0137] The following describes the live notification sharing method provided in the embodiments of this application.

[0138] In this embodiment, in response to a first operation triggered by a first user in a first application of a first electronic device, the first electronic device creates a first task related to the user account of a second user and generates a first real-time notification corresponding to the first task. The first application of the first electronic device contains the user account of the first user, and the first operation can be an operation triggered by the first user to create the first task. The first task related to the user account of the second user can be, for example, a task where the first user hails a taxi for the second user or orders takeout for the second user.

[0139] For example, Figure 5A is a schematic diagram of a live notification sharing method provided in an embodiment of this application. Figure 5A illustrates this using the example of a first user triggering the creation of a ride-hailing task. Referring to Figure 5A(a), the first user can input the account information of a second user, such as the second user's username or phone number, into the passenger information input control 502 on the ride-hailing interface 501. After the first user clicks the "Confirm" control 503, the creation of the first task for the second user is triggered. In this example, the first operation can be the first user clicking the "Confirm" control 503, or the first operation can include a series of operations where the first user inputs the second user's account information into the passenger information input control 502 and clicks the "Confirm" control 503. Responding to the first operation, the first electronic device generates a first live notification corresponding to the first task after creating the first task. Referring to Figure 5A(b), after creating the first task, the first electronic device can display the first live notification 504 on the lock screen. Optionally, as shown in Figure 5A(b), the first live notification 504 of the first electronic device may also display a control 505 for contacting a driver. In another optional embodiment, since the first task is to call a car for the second user, the first live notification of the first electronic device may also display a control for contacting the second user (not shown in Figure 5A) to facilitate direct communication between the first user and the second user.

[0140] In this embodiment, a first electronic device sends a first request message to a server. This first request message requests the server to share a first live notification with the second electronic device corresponding to the user account of a second user. The first request message may include the second user's account information, which may include at least one of the user's username and contact information entered by the first user when creating the first task. The server may store the correspondence between user account information and device identifiers of the electronic devices used by the user. After receiving the first request message, the server can look up the device identifier of the second electronic device corresponding to the second user's account information. The server can then send the first live notification information to the second electronic device based on the found device identifier. The first live notification information may include the identifier of a first application, the identifier of a first task, and the task progress information of the first task.

[0141] In an optional implementation, based on the scenario shown in Figure 2, the server in the step of the first electronic device sending a first request message to the server can be a system server. Further, the system server can also include an account server and a push server. Then, the first electronic device can send a first request message to the account server. The account server determines the device identifier of the second electronic device based on the account information of the second user and sends an eighth request message to the push server. The eighth request message is used to request the push server to share the first live notification with the second electronic device. The eighth request message includes the device identifier of the second electronic device. The push server sends the information of the first live notification to the second electronic device based on the device identifier of the second electronic device.

[0142] Optionally, when the first application is already installed on the second electronic device, before sending the first live notification information to the second electronic device, the push server may also confirm with the application server whether there is a first task related to the second user's user account. For example, the push server may send a ninth request message to the application server, which requests the application server to confirm whether there is a first task related to the second user's user account. After the application server confirms that there is a first task related to the second user's user account in the first application, it may send a confirmation message to the push server, and then the push server sends the first live notification information to the second electronic device.

[0143] In another optional implementation, based on the scenario shown in Figure 2, the server in the step of the first electronic device sending a first request message to the server can also be an application server. The first electronic device can send a first request message to the application server. The account information of the second user in the first request message can be the application account information of the second user in the first application. The application server can store the correspondence between the user's application account information and system account information. The application server can determine the system account information of the second user based on the application account information of the second user. The application server can send a sixth request message to the account server. The sixth request message is used to request the account server to share the first live notification with the second electronic device. The sixth request message includes the system account information of the second user. The account server can determine the device identifier of the second electronic device based on the system account information of the second user and send an eighth request message to the push server. The eighth request message is used to request the account server to share the first live notification with the second electronic device. The eighth request message can include the device identifier of the second electronic device. After the push server confirms with the application server through a ninth request message that there is a first task related to the user account of the second user, the push server sends the information of the first live notification to the second electronic device.

[0144] In some embodiments, the server can also be used to manage the status of live notifications simultaneously displayed by multiple electronic devices. After the server sends the information of the first live notification to the second electronic device, the server can store the update status information corresponding to the second electronic device. The update status information corresponding to the second electronic device can be used to indicate the update status of the first live notification shared by the first electronic device to the second electronic device. For example, the update status information corresponding to the second electronic device may include the device identifier of the second electronic device and the status of the first live notification. For example, the update status of the live notification corresponding to the second electronic device stored by the server may include: the device identifier of the second electronic device, the identifier of the first live notification, and the status of the first live notification (such as "updating"). Optionally, the push server in the scenario shown in Figure 2 can be used to manage the status of live notifications simultaneously displayed by multiple electronic devices.

[0145] After receiving the first live notification, the second electronic device can generate a second live notification based on the information in the first live notification. The second live notification includes the task progress information of the first task in the first electronic device. Optionally, the second live notification can be a live notification with the same or different style as the first live notification. When generating the second live notification, the second electronic device can determine the style of the second live notification based on the scenario in which the second electronic device displays the second live notification. That is, in this embodiment of the application, the second live notification displayed in the second electronic device has the same function as the first live notification displayed in the first electronic device, while the style of the second live notification can be the same or different from the style of the first live notification.

[0146] Optionally, before generating the second live notification, the second electronic device may also display a first reminder message on the screen. The first reminder message is used to ask the second user whether to receive the live notification shared by the first user. After the second user confirms receipt, the second electronic device generates and displays the second live notification.

[0147] For example, referring to Figure 5A(c), after receiving the first live notification information sent by the server, the second electronic device can display a first reminder message 506. As shown in Figure 5A(c), this first reminder message 506 can be: "The first user is sharing a live notification from the first application with you. Do you want to receive it?". After the second user clicks the "Receive" control 507 corresponding to the first reminder message, the second electronic device can generate a second live notification based on the information of the first live notification and display the second live notification on the display interface of the second electronic device. As shown in Figure 5A(d), the second electronic device can display a second live notification 508, through which the second user can view the progress of the first task. The progress of the first task in the second live notification 508 is the same as the progress of the first task in the first live notification 504 on the first electronic device.

[0148] It should be noted that the display interface of the second electronic device when displaying the second live notification can be the lock screen, desktop, negative one screen, the interface of any application, or other interfaces.

[0149] After the first electronic device shares the first live notification with the second electronic device corresponding to the second user, a sharing control can be displayed on the first live notification on the first electronic device. This allows the first user to continue sharing the first live notification with electronic devices corresponding to other users besides the second user, such as a third user, a fourth user, etc. If the first user selects to share the first live notification with a third user through the sharing control on the first live notification, the first electronic device can send a third request message to the server. The third request message requests that the first live notification be shared with the third electronic device corresponding to the third user's user account. The server determines the device identifier of the third electronic device corresponding to the third user's user account based on the correspondence between the third user's user account and the device identifiers of multiple user accounts and multiple electronic devices stored on the server. The server then sends the first live notification information to the third electronic device based on the device identifier of the third electronic device.

[0150] For example, as shown in Figure 5A(e), the first live notification 504 of the first electronic device can also display a sharing control 509. After the first user clicks the sharing control 509, the first electronic device can jump to the interface shown in Figure 5A(f). This interface includes the identifiers of multiple users. The first user can select the user to whom the first live notification is to be shared in this interface. If the first user selects to share with a third user, the first electronic device can request the server to share the first live notification with the third electronic device corresponding to the user account of the third user. After the server determines the device identifier of the third electronic device, it sends the information of the first live notification to the third electronic device.

[0151] After displaying the second live notification, the second electronic device can continue to share the second live notification with the electronic devices corresponding to other users besides the first user. For example, if the second user selects to share the second live notification with the fourth user via the sharing control on the second live notification, the second electronic device can send a seventh request message to the server. The seventh request message requests that the second live notification be shared with the fourth electronic device corresponding to the fourth user's user account. The server determines the device identifier of the fourth electronic device corresponding to the fourth user's user account based on the correspondence between the fourth user's user account and the device identifiers of multiple user accounts and multiple electronic devices stored on the server. The server then sends the second live notification information to the fourth electronic device based on the device identifier of the fourth electronic device.

[0152] For example, as shown in Figure 5A(g), the second live notification 508 of the second electronic device can also display a sharing control 510. After the second user clicks the sharing control 510, the first electronic device can jump to the interface shown in Figure 5A(h). This interface includes the identifiers of multiple users. The second user can select the user to whom the second live notification is to be shared in this interface. If the second user selects to share with the fourth user, the second electronic device can request the server to share the second live notification with the fourth electronic device corresponding to the user account of the fourth user. After the server determines the device identifier of the fourth electronic device, it sends the information of the second live notification to the fourth electronic device.

[0153] In one optional implementation, before the first task of the first electronic device has ended, the first electronic device displays a first live notification. The first electronic device can send a second request message to the server, which can be used to request the server to instruct the second electronic device to update the live notification corresponding to the first task. Optionally, the first electronic device can obtain the task progress information of the first task with updated progress and send the second request message to the server. The second request message includes the task progress information of the first task with updated progress. After receiving the second request message, the server can send the task progress information of the first task with updated progress to the second electronic device. The second electronic device can update the content in the second live notification according to the task progress information of the first task with updated progress, such as displaying the task progress information of the first task with updated progress in the second live notification. Optionally, the first electronic device can obtain the task progress of the first task according to a first preset period and send the second request message to the server to synchronize the task progress information of the first task with the second electronic device in a timely manner. For example, the first electronic device can send the second request message to the push server in the scenario shown in Figure 2, and the push server synchronizes the task progress information of the first task with the second electronic device.

[0154] In another optional implementation, based on the scenario shown in Figure 2, if the second electronic device has the first application installed, the application server can trigger the push server to update the progress of the first task to the second electronic device without the first electronic device sending a request message to the push server. Optionally, when the second electronic device has the first application installed, the application server can obtain the task progress information of the first task with updated progress and send a tenth request message to the push server. The tenth request message is used to request the push server to instruct the second electronic device to update the live notification corresponding to the first task, and the tenth request message includes the task progress information of the first task with updated progress. Optionally, the application server can obtain the task progress information of the first task according to a first preset period and send the tenth request message to the push server. The push server sends the task progress information of the first task with updated progress to the second electronic device, and the second electronic device can update the content in the second live notification according to the task progress information of the first task with updated progress, such as the second electronic device displaying the task progress information of the first task with updated progress in the second live notification.

[0155] For example, Figure 5B is a schematic diagram of a live notification sharing provided by an embodiment of this application. Referring to Figure 5B(a), the first electronic device displays a first live notification 504 on the lock screen interface. The first electronic device requests the server to share the first live notification to the second electronic device. Referring to Figure 5B(b), the second electronic device generates a second live notification based on the information of the received first live notification and displays the second live notification 508 on the main interface. As shown in Figures 5B(a) and (b), the task progress information of the first task in the first live notification 504 and the second live notification 508 is the same, both being "The driver is expected to arrive in 5 minutes". As the first task progresses, the task progress information of the first task changes. For example, referring to Figure 5B(c), the task progress information of the first task displayed in the first live notification 504 of the first electronic device is "In progress, expected to arrive in 15 minutes". The first electronic device requests the server to synchronize the task progress information of the first task to the second electronic device. The second electronic device displays the task progress information of the first task sent by the server in the second live notification to realize the update of the task progress information. Referring to Figure 5B(d), the task progress information of the first task displayed in the second real-time notification 508 of the second electronic device is "In progress, expected to arrive in 15 minutes".

[0156] In this embodiment, after the first task ends, the first electronic device destroys the first live notification displayed on its screen and sends a fourth request message to the server. This fourth request message requests the server to instruct the second electronic device to destroy the live notification corresponding to the first task. Optionally, the first electronic device may send the fourth request message to the server after a preset time period following the end of the first task. Upon receiving the fourth request message, the server sends a destruction notification message to the second electronic device. Upon receiving the destruction notification message, the second electronic device destroys the second live notification and returns a feedback message to the server, indicating whether the second electronic device successfully destroyed the second live notification.

[0157] In one optional implementation, based on the scenario shown in Figure 2, the first electronic device can send a fourth request message to the system server. Alternatively, when the system server also includes an account server and a push server, the first electronic device can send a fourth request message to the push server. The fourth request message is used to request a notification to the second electronic device to destroy the live notification corresponding to the first task. The system server or the push server can send a destruction notification message to the second electronic device.

[0158] Optionally, as described above, the server can also be used to manage the status of live notifications displayed synchronously by multiple electronic devices. After receiving a feedback message from the second electronic device, if the server determines that the feedback message is used to instruct the second electronic device to successfully destroy the second live notification, the server can delete the updated status information corresponding to the second electronic device stored in the server and store the event of the first electronic device sharing the live notification with the second electronic device in the status log.

[0159] In some embodiments of this application, the first electronic device can trigger the sharing of live notifications by having the first user actively trigger the sharing of the first live notification with the second user. For example, Figure 6 is a schematic diagram of live notification sharing provided by an embodiment of this application. Referring to Figure 6, the first user triggers the creation of a first task in a first application of the first electronic device. The first task can be a regular ride-hailing task or a ride-hailing task for other users. After creating the first task, the first electronic device generates and displays a first live notification, as shown in Figure 6(a). The first electronic device can display the first live notification 602 on the lock screen interface 601. The first live notification may include a "share" control 602. When the first user clicks the "share" control 603, the first live notification 602 can be shared with other users, as shown in Figure 6(b). The first electronic device jumps to display a user selection interface 604. The first user can select the user account to share the first live notification on this interface 604, such as the first user choosing to share it with a second user. In implementation, the first electronic device determines the account information of the second user selected by the first user and requests the server to share the first live notification with the second electronic device corresponding to the second user. The server determines the device identifier of the second electronic device based on the second user's account information and sends the information of the first live notification to the second electronic device. Referring to Figure 6(c), the second electronic device can generate and display a second live notification 605 based on the received information of the first live notification. If the second electronic device is in a locked screen state, the second electronic device can display the second live notification 605 on the lock screen interface 606. This second live notification is the live notification corresponding to the first task, and the task progress of the first task displayed in the second live notification is the same as that in the first live notification. In this example, the way the server responds to the request of the first electronic device and shares the first live notification with the second electronic device can refer to the above embodiments, and the repeated parts will not be described again.

[0160] In some examples, after sharing the first live notification with the second user's corresponding second electronic device, the first electronic device can continue to share the first live notification with the electronic devices corresponding to other users. For example, the first user can choose to share the first live notification with a third user, a fourth user, etc. As shown in Figure 6(d), the first user can also click the "Share" control 603 again, and the first electronic device will jump to the user selection interface 604 shown in Figure 6(e). The first user can select the user to share the first live notification with again in this interface 604. For example, if the first user can continue to select a third user, the first electronic device can request the server to share the first live notification with the third user's corresponding third electronic device.

[0161] In other examples, after displaying the second live notification, the second electronic device can also share the second live notification with the electronic devices corresponding to other users besides the first user. For example, the second user can choose to share the second live notification with a third user, a fourth user, etc. As shown in Figure 6(c), the second live notification 605 includes a "share" control 607. When the second user clicks the "share" control 607 on the second electronic device, the second electronic device jumps to display the user selection interface 608 shown in Figure 6(f). The second user can select the user to share the second live notification on this interface 608. For example, if the second user can select a fourth user, the second electronic device can request the server to share the second live notification with the fourth electronic device corresponding to the fourth user's user account.

[0162] Based on the above embodiments, Figure 7 is a flowchart illustrating a live notification sharing method provided in this application embodiment. Referring to Figure 7, the method can be executed by a first electronic device, a server, and a third electronic device, and includes the following steps:

[0163] S701: In response to a first operation by a first user, a first task is created in a first application of a first electronic device.

[0164] S702: The first electronic device generates a first real-time notification corresponding to the first task and displays the first real-time notification.

[0165] The first live notification includes the task progress information of the first task, and also includes a sharing control.

[0166] For example, the first live notification displayed by the first electronic device can be seen in Figure 6(a) as the first live notification 602, which includes the task progress information of the ride-hailing task.

[0167] S703: In response to a second operation by the first user on the sharing control in the first live notification, the first electronic device sends a third request message to the server.

[0168] The third request message is used to request the server to share the first live notification with the third electronic device corresponding to the user account of the third user.

[0169] For example, the second operation could be the user clicking the share control and then selecting a third user's account. The second operation could include the user triggering a click on the "share" control 603 shown in Figure 6(a) and selecting a third user in Figure 6(b).

[0170] Optionally, the first electronic device may send a third request message to the account server or application server in the scenario shown in Figure 2.

[0171] S704: The server determines the device identifier of the third electronic device corresponding to the third user's user account based on the correspondence between the third user's user account and the device identifiers of multiple user accounts and multiple electronic devices stored on the server.

[0172] S705: The server sends a first real-time notification to the third electronic device based on the device identifier of the third electronic device.

[0173] S706: The second electronic device generates a second real-time notification based on the information in the first real-time notification, and displays the second real-time notification.

[0174] The second real-time notification includes task progress information of the first task in the first application of the first electronic device.

[0175] For example, the second live notification displayed by the second electronic device can be seen in the second live notification 605 shown in Figure 6(c). The second live notification 605 includes the task progress information of the ride-hailing task. The task progress information of the first task in the second live notification 605 can be the same as the task progress information of the first task in the first live notification 602 of the first electronic device shown in Figure 6(a).

[0176] It should be noted that the specific implementation of the live notification sharing method shown in Figure 7 can be found in the above embodiments of this application, and the repeated parts will not be described again.

[0177] Referring to the scenario shown in Figure 2 of this application embodiment, the live notification sharing method provided in this application embodiment is applicable to a variety of different scenarios. In different scenarios, the steps executed by the server in the above embodiments can be executed by the system server shown in Figure 2, or by the system server and application server shown in Figure 2 working together. Further, the system server shown in Figure 2 may include an account server and a push server. In this case, the steps executed by the server in the above embodiments can be executed by the account server and the push server, or by the account server, push server, and application server shown in Figure 2 working together. The flow of the live notification sharing method in different scenarios will be described below.

[0178] Scenario A: The account server and push server can provide account management services and message push services for the first electronic device and the second electronic device, and the first application is not installed on the second electronic device.

[0179] In scenario A provided in this application embodiment, the account server can provide account management services for the first electronic device and the second electronic device, and the push server can provide message push services for the first electronic device and the second electronic device. For example, the first electronic device and the second electronic device are electronic devices from the same manufacturer. In this scenario A, the second electronic device does not have the first application installed, so the first electronic device can share live notifications with the second electronic device through the account server and the push server. For example, Figure 8 is a flowchart of a live notification sharing method provided in this application embodiment. This method can be executed by the first electronic device, the second electronic device, the account server, and the push server. Referring to Figure 8, the method includes the following steps:

[0180] S801: In response to a first operation triggered by a first user, a first electronic device creates a first task related to a user account of a second user.

[0181] In this embodiment of the application, a user account of a first user is logged in in a first application of the first electronic device, and a first operation is used to create a first task related to the user account of a second user.

[0182] S802: The first electronic device generates a first live notification corresponding to the first task and displays the first live notification.

[0183] S803: The first electronic device sends a first request message to the account server.

[0184] The first request message is used to request the account server to share the first live notification with the second electronic device corresponding to the user account of the second user. The first request message includes the account information of the second user.

[0185] S804: The account server searches for the device identifier of the second electronic device corresponding to the second user's account information based on the second user's account information.

[0186] S805: The account server sends the eighth request message to the push server.

[0187] The eighth request message is used to request the push server to share the first live notification with the second electronic device. The eighth request message may include the device identifier of the second electronic device and the information of the first live notification.

[0188] S806: The push server sends the first push message to the second electronic device.

[0189] The first push message is used to push a real-time notification corresponding to the first task to the second electronic device. The first push message may include information of the first real-time notification, such as the identifier of the first application and information of the first task.

[0190] S807: The push server stores the update status information corresponding to the second electronic device.

[0191] For example, the update status information corresponding to the second electronic device stored on the push server may include: the device identifier of the second electronic device, the identifier of the first live notification, and the status of the first live notification being "updating".

[0192] S808: The second electronic device displays the first reminder message.

[0193] Optionally, the first notification message is used to ask the second user whether to receive the live notification shared by the first user.

[0194] S809: In response to the fourth operation triggered by the second user, the second electronic device generates a second live notification based on the information of the first live notification, and the second electronic device displays the second live notification.

[0195] The fourth operation is an operation triggered by the second user to confirm receipt of the live notification shared by the first user. For example, the fourth operation can be a click operation triggered by the second user on the "Receive" control corresponding to the first reminder message in (c) of Figure 5A.

[0196] The second live notification generated by the second electronic device includes the task progress information of the first task in the first electronic device. Optionally, the task progress information of the first task displayed in the second live notification is the same as the task progress information of the first task displayed in the first live notification in the first electronic device.

[0197] S810: The first electronic device sends a second request message to the push server.

[0198] The second request message can be used to request the push server to instruct the second electronic device to update the real-time notification corresponding to the first task. The second request message may include the task progress information of the first task with progress updates.

[0199] S811: The push server sends the progress information of the first task to the second electronic device.

[0200] S812: The second electronic device updates the progress information of the first task as shown in the second live notification.

[0201] It should be noted that S810-S812 can be steps that are executed periodically. For example, the first electronic device can execute S810 according to a first preset period, thereby synchronizing the progress of the first task with the second electronic device according to the first preset period, and ensuring the timeliness of the second real-time notification displayed by the second electronic device.

[0202] S813: After the first electronic device finishes the first task, it sends a fourth request message to the push server.

[0203] The fourth request message is used to request the push server to notify the second electronic device to destroy the real-time notification corresponding to the first task.

[0204] S814: The push server sends a destruction notification message to the second electronic device.

[0205] S815: Second live notification of the destruction of the second electronic device.

[0206] S816: The second electronic device sends a feedback message to the push server.

[0207] The feedback message indicates that the second electronic device has successfully destroyed the second live notification.

[0208] S817: The push server deletes the update status information corresponding to the second electronic device.

[0209] It should be noted that the embodiment shown in Figure 8 is only an example of the live notification sharing method provided in this application and is not a limitation. In specific implementation, each device may perform more or fewer steps than in Figure 8. For details, please refer to the foregoing embodiments of this application. Repeated parts will not be described again.

[0210] Scenario B: The account server and push server can provide account management services and message push services for the first electronic device and the second electronic device, and the first application is installed on the second electronic device.

[0211] In scenario B provided in this application embodiment, the account server can provide account management services for the first electronic device and the second electronic device, and the push server can provide message push services for the first electronic device and the second electronic device. For example, the first electronic device and the second electronic device are electronic devices from the same manufacturer. In this scenario B, the second electronic device has a first application installed, so the first electronic device can share live notifications with the second electronic device through the account server, the push server, and the application server. For example, Figure 9 is a flowchart of a live notification sharing method provided in this application embodiment. This method can be executed by the first electronic device, the second electronic device, the account server, the push server, and the application server. Referring to Figure 9, the method includes the following steps:

[0212] S901: In response to a first operation triggered by a first user, a first electronic device creates a first task related to a second user's user account.

[0213] In this embodiment of the application, a user account of a first user is logged in in a first application of the first electronic device, and a first operation is used to create a first task related to the user account of a second user.

[0214] S902: The first electronic device generates a first real-time notification corresponding to the first task and displays the first real-time notification.

[0215] S903: The first electronic device sends a first request message to the account server.

[0216] The first request message is used to request the account server to share the first live notification with the second electronic device corresponding to the user account of the second user. The first request message includes the account information of the second user.

[0217] S904: The account server searches for the device identifier of the second electronic device corresponding to the second user's account information based on the second user's account information.

[0218] S905: The account server sends the eighth request message to the push server.

[0219] The eighth request message is used to request the push server to share the first live notification with the second electronic device. The eighth request message may include the device identifier of the second electronic device and the information of the first live notification.

[0220] S906: The push server sends the ninth request message to the application server.

[0221] The ninth request message is used to request the application server to confirm whether there is a first task related to the second user's account.

[0222] S907: The application server determines that there is a first task related to the user account of the second user.

[0223] S908: The application server sends a confirmation message to the push server.

[0224] The confirmation message is used to indicate that there is a first task in the first application related to the user account of the second user.

[0225] S909: The push server sends the first push message to the second electronic device.

[0226] The first push message is used to push a real-time notification corresponding to the first task to the second electronic device. The first push message may include information of the first real-time notification, such as the identifier of the first application and information of the first task.

[0227] S910: The push server stores the update status information corresponding to the second electronic device.

[0228] The update status information corresponding to the second electronic device stored on the push server may include: the device identifier of the second electronic device, the identifier of the first live notification, and the status of the first live notification being "updating".

[0229] S911: The second electronic device displays the first reminder message.

[0230] The first notification message is used to ask the second user whether to receive the live notification shared by the first user.

[0231] S912: In response to a fourth operation triggered by a second user, the second electronic device generates a second live notification based on information from the first live notification, and the second electronic device displays the second live notification.

[0232] The fourth operation is an operation triggered by the second user to confirm receipt of the live notification shared by the first user. For example, the fourth operation can be a click operation triggered by the second user on the "Receive" control corresponding to the first reminder message in (c) of Figure 5A.

[0233] The second live notification generated by the second electronic device includes the task progress information of the first task in the first electronic device. Optionally, the task progress information of the first task displayed in the second live notification is the same as the task progress information of the first task displayed in the first live notification in the first electronic device.

[0234] S913: The application server sends the tenth request message to the push server.

[0235] The tenth request message can be used to request the push server to instruct the second electronic device to update the real-time notification corresponding to the first task. The tenth request message may include the task progress information of the first task with progress updates.

[0236] S914: The push server sends the progress information of the first task to the second electronic device.

[0237] S915: The second electronic device displays the task progress information of the first task in the second live notification.

[0238] S916: After the first electronic device completes the first task, it sends a fourth request message to the push server.

[0239] The fourth request message is used to request the push server to notify the second electronic device to destroy the real-time notification corresponding to the first task.

[0240] S917: The push server sends a destruction notification message to the second electronic device.

[0241] S918: Second live notification of the destruction of the second electronic device.

[0242] S919: The second electronic device sends a feedback message to the push server.

[0243] This feedback message is used to indicate that the second electronic device has successfully destroyed the second live notification.

[0244] S920: The push server deletes the update status information corresponding to the second electronic device.

[0245] It should be noted that S913-S915 can be steps that are executed periodically. For example, the application server can execute S911 according to a preset period, thereby synchronizing the progress of the first task with the second electronic device according to the preset period, and ensuring the timeliness of the second live notification displayed by the second electronic device.

[0246] Scenario C: The account server and push server are able to provide account management services and message push services for the second electronic device, and the first application is installed on the second electronic device.

[0247] In scenario C provided in this application embodiment, the account server can provide account management services for the second electronic device, and the push server can provide message push services for the second electronic device. For example, the first electronic device and the second electronic device are electronic devices from different manufacturers. In this scenario C, the second electronic device has a first application installed, so the first electronic device can share live notifications with the second electronic device through the application server, the account server, and the push server. For example, Figure 10 is a flowchart of a live notification sharing method provided in this application embodiment. This method can be executed by the first electronic device, the second electronic device, the account server, the push server, and the application server. Referring to Figure 10, the method includes the following steps:

[0248] S1001: In response to a first operation triggered by a first user, a first electronic device creates a first task related to a second user's user account.

[0249] In this embodiment of the application, a user account of a first user is logged in in a first application of the first electronic device, and a first operation is used to create a first task related to the user account of a second user.

[0250] S1002: The first electronic device generates a first real-time notification corresponding to the first task and displays the first real-time notification.

[0251] S1003: The first electronic device sends a first request message to the application server.

[0252] The first request message is used to request the application server to share the first live notification with the second electronic device corresponding to the user account of the second user. The first request message includes the application account information of the second user.

[0253] S1004: The application server sends the sixth request message to the account server.

[0254] The sixth request message is used to request the account server to share the first live notification with the second electronic device. The sixth request message may include the system account information of the second user. The system account information of the second user is determined by the application server based on the application account information of the second user and the correspondence between the application account information and system account information of multiple users stored in the application server.

[0255] S1005: The account server determines the device identifier of the second electronic device based on the system account information of the second user.

[0256] The account server can establish a mapping between system account information of multiple users and device identifiers of electronic devices. The account server can then use the system account information of a second user to locate the device identifier of a second electronic device.

[0257] S1006: The account server sends the eighth request message to the push server.

[0258] The eighth request message is used to request the push server to push the real-time notification corresponding to the first task to the second electronic device. The eighth request message may include the device identifier of the second electronic device.

[0259] S1007: The push server sends the ninth request message to the application server.

[0260] The ninth request message is used to request the application server to confirm whether there is a first task related to the second user's account.

[0261] S1008: The application server determines that there is a first task related to the user account of the second user.

[0262] S1009: The application server sends a confirmation message to the push server.

[0263] The confirmation message is used to indicate that there is a first task in the first application related to the user account of the second user.

[0264] S1010: The push server sends the first push message to the second electronic device.

[0265] The first push message is used to push a real-time notification corresponding to the first task to the second electronic device. The first push message may include information of the first real-time notification, such as the identifier of the first application and information of the first task.

[0266] S1011: The push server stores the update status information corresponding to the second electronic device.

[0267] The update status information corresponding to the second electronic device stored on the push server may include: the device identifier of the second electronic device, the identifier of the first live notification, and the status of the first live notification being "updating".

[0268] S1012: The second electronic device displays the first reminder message.

[0269] The first notification message is used to ask the second user whether to receive the live notification shared by the first user.

[0270] S1013: In response to the fourth operation triggered by the second user, the second electronic device generates a second live notification based on the information of the first live notification, and the second electronic device displays the second live notification.

[0271] The fourth operation is an operation triggered by the second user to confirm receipt of the live notification shared by the first user. For example, the fourth operation can be a click operation triggered by the second user on the "Receive" control corresponding to the first reminder message in (c) of Figure 5A.

[0272] The second live notification generated by the second electronic device includes the task progress information of the first task in the first electronic device.

[0273] S1014: The application server sends the tenth request message to the push server.

[0274] The tenth request message can be used to request the push server to instruct the second electronic device to update the real-time notification corresponding to the first task. The tenth request message may include the task progress information of the first task with progress updates.

[0275] S1015: The push server sends the progress information of the first task to the second electronic device.

[0276] S1016: The second electronic device displays the task progress information of the first task in the second live notification.

[0277] S1017: After the first task is completed, the first electronic device sends a fourth request message to the push server.

[0278] The fourth request message is used to request the push server to notify the second electronic device to destroy the real-time notification corresponding to the first task.

[0279] S1018: The push server sends a destruction notification message to the second electronic device.

[0280] S1019: Second live notification of the destruction of the second electronic device.

[0281] S1020: The second electronic device sends a feedback message to the push server.

[0282] This feedback message is used to indicate that the second electronic device has successfully destroyed the second live notification.

[0283] S1021: The push server deletes the update status information corresponding to the second electronic device.

[0284] It should be noted that S1014-S1016 can be steps that are executed periodically. For example, the application server can execute S1014 according to a preset period, thereby synchronizing the progress of the first task with the second electronic device according to the preset period, and ensuring the timeliness of the second live notification displayed by the second electronic device.

[0285] In some embodiments of this application, when the first electronic device displays a first real-time notification, the first real-time notification may also include controls related to the first task. These controls provide interactive entry points for services related to the first task, and the services related to different types of first tasks vary. For example, when the first task is a ride-hailing task, the controls that can be displayed in the first real-time notification include: contact driver, contact passenger, platform complaint, pay fare, driver rating, etc. As another example, when the first task is using a shared bicycle, the controls that can be displayed in the first real-time notification include: return the bicycle (lock), pay, report repair, etc. Since the display area in the first real-time notification is limited, in these embodiments of the application, the electronic device can determine the controls displayed in the first real-time notification based on the state of the first task, thereby adapting to the different functional interaction needs of the user in different states of the first task.

[0286] In one optional implementation, when the first electronic device displays a first real-time notification, the first real-time notification displays at least one first control corresponding to the status of the first task. The first electronic device can adjust the controls displayed in the first real-time notification in real time according to the status of the first task. Specifically, the first electronic device can adjust the controls displayed in the first real-time notification when it determines that the status of the first task has changed, and / or, the first electronic device can adjust the controls displayed in the first real-time notification according to the status of the first task according to a second preset period. The status of the first task is related to the type of the first task and can include multiple preset statuses of the first application. For example, taking a taxi-hailing task as an example, the status of the first task could be, for example, "hailing a taxi," "waiting for a taxi," "trip has been going on for M minutes," "arrived," etc., where M is a positive integer.

[0287] In this embodiment, the first electronic device determines at least one first control displayed in the first live notification based on the type information and status information of the first task. Specifically, the first electronic device inputs its device identifier, the application identifier of the first application, the type information and status information of the first task into a trained intent-aware model to obtain the probability value corresponding to each control among multiple controls related to the first task; based on the probability value corresponding to each control among the multiple controls, at least one control is selected as at least one first control. The type information of the first task can be, for example, ride-hailing, food delivery, etc. When the first task is a ride-hailing task, the status information of the first task can indicate, for example, the status of the first task as "hailing a ride," "waiting for a ride," "trip has been in progress for M minutes," "arrived," etc. The first electronic device can obtain the probability value corresponding to each control among the multiple controls related to the first task output by the intent-aware model, wherein the multiple controls related to the first task are multiple controls related to the first task that can be provided by the first application in advance.

[0288] For example, the result obtained by the first electronic device from the intent-aware model output can be: {'AppID': 129, 'intent_probability': {'API03': 0.96, 'API05': 0.67, 'API01': 0.38}}, where AppID is the application identifier of the first application, and intent_probability is the probability value corresponding to multiple controls related to the first task. For example, API03 represents a control of the first application, and 0.96 means that the probability of the user expecting to use API03 in the current state of the first task is 96%. Similarly, 'API05': 0.67 means that the probability of the user expecting to use API05 in the current state of the first task is 67%, and 'API01': 0.38 means that the probability of the user expecting to use API01 in the current state of the first task is 38%.

[0289] After obtaining the probability value of each control among multiple controls related to the first task output by the trained intent-aware model, the first electronic device selects at least one control as at least one first control. Specifically, it can select at least one control whose probability value is greater than a preset threshold in descending order of the probability values ​​of the multiple controls, and use the selected at least one control as at least one first control. Optionally, the number of first controls selected by the first electronic device is less than or equal to Q, where Q is a positive integer and Q is the maximum number of controls that the display style of the first live notification supports. That is, the first electronic device selects at most Q controls with probability values ​​greater than the preset threshold as first controls. Through the above design, the at least one first control determined by the first electronic device is the control that the user expects to use in the current state of the first task.

[0290] For example, assuming the output of the intent-aware model can be: {'AppID': 129, 'intent_probability': {'API03': 0.96, 'API05': 0.67, 'API01': 0.38}}, if the first electronic device determines that at most two controls are displayed in the first live notification, and the preset threshold is 50%, then the first electronic device can determine that at least one first control is API03 and API05.

[0291] After identifying the first control, the first electronic device can obtain the API configuration file of at least one first control from the configuration file of the first application. If the first electronic device can obtain the full set of API configuration files of at least one first control from the configuration file of the first application, then the first electronic device can determine that the first application has at least one first control and that at least one first control can be provided for user interaction. The first electronic device can then display at least one first control in the first live notification.

[0292] In this embodiment, after updating the controls displayed in the first live notification, the first electronic device can send a fifth request message to the server. The fifth request message requests the server to instruct the second electronic device to update the controls in the live notification corresponding to the first task. The fifth request message includes an identifier for at least one first control. The server can send the identifier for at least one first control to the second electronic device, so that the second electronic device can update the controls displayed in the second live notification according to the identifier of at least one first control, such as displaying at least one first control in the second live notification.

[0293] For example, Figure 11 is a schematic diagram of a real-time notification display provided in an embodiment of this application. Figure 11 illustrates a ride-hailing task as an example. Referring to Figure 11(a), when the first user triggers the creation of the first task, the first electronic device displays a first real-time notification. When the status of the first task is "Waiting for a ride, driver is late," as shown in Figure 11(a), the first real-time notification of the first electronic device displays a "Contact Driver" control 1101. Referring to Figure 11(b), when the status of the first task is "Arrived," the first real-time notification of the first electronic device displays a "Payment" control 1102. Referring to Figure 11(c), when the status of the first task is "Arrived, time exceeded estimated duration," the first real-time notification of the first electronic device displays a "Contact Platform" control 1103 and a "Payment" control 1102. In this embodiment, the first electronic device can also request the server to send the identifier of at least one first control displayed in the first live notification to the second electronic device, thereby synchronizing the controls displayed in the live notification corresponding to the first task to the second electronic device. The second electronic device can display at least one first control in the second live notification. For example, referring to Figure 11(d), when the first electronic device displays the first live notification shown in Figure 11(a), it sends the identifier of the "Contact Driver" control 1101 in the first live notification to the second electronic device through the server. Then, the second electronic device can display the "Contact Driver" control 1104 in the second live notification. Another example, referring to Figure 11(e)... When the first electronic device displays the first live notification shown in Figure 11(b), it sends the identifier of the "Payment" control 1102 in the first live notification to the second electronic device via the server. Then, the second electronic device can display the "Payment" control 1105 in the second live notification. For example, referring to Figure 11(f), when the first electronic device displays the first live notification shown in Figure 11(c), it sends the identifiers of the "Contact Platform" control 1103 and the "Payment" control 1102 in the first live notification to the second electronic device via the server. Then, the second electronic device can display the "Contact Platform" control 1106 and the "Payment" control 1105 in the second live notification.

[0294] For example, Figure 12 is a schematic diagram of a real-time notification provided in an embodiment of this application. Figure 12 shows a shared bicycle as the first task. Referring to Figure 12(a), when the first user triggers the creation of the first task, the first electronic device displays a first real-time notification. The status of the first task in the first real-time notification is "riding". The first real-time notification can also display information such as the user's riding time, cost, and whether speeding has occurred. As shown in Figure 12(a), the first real-time notification of the first electronic device can display a "Return Bike" control 1201. Referring to Figure 11(b), the status of the first task in the first real-time notification is "parked". The first real-time notification can also display information such as the location of the nearest parking spot to the user. At this time, the first real-time notification of the first electronic device displays a "Return Bike" control 1201. Referring to Figure 12(c), the status of the first task in the first real-time notification is "returned". The first real-time notification can also display information such as the user's riding time and cost. At this time, the first real-time notification of the first electronic device displays a "Pay" control 1202. In this embodiment of the application, the first electronic device may also request the server to send the identifier of at least one first control displayed in the first live notification to the second electronic device, thereby synchronizing the control displayed in the live notification corresponding to the first task to the second electronic device. The second electronic device may display at least one first control in the second live notification. Referring to Figure 12(d), when the first electronic device displays the first live notification shown in Figure 12(a), it sends the identifier of the "Go to Return the Vehicle" control 1201 in the first live notification to the second electronic device via the server. Then, the second electronic device can display the "Go to Return the Vehicle" control 1203 in the second live notification. As another example, referring to Figure 12(e), when the first electronic device displays the first live notification shown in Figure 12(b), it sends the identifier of the "Go to Return the Vehicle" control 1202 in the first live notification to the second electronic device via the server. Then, the second electronic device can display the "Go to Return the Vehicle" control 1203 in the second live notification. As yet another example, referring to Figure 12(f), when the first electronic device displays the first live notification shown in Figure 12(c), it sends the identifier of the "Go to Payment" control 1202 in the first live notification to the second electronic device via the server. Then, the second electronic device can display the "Go to Payment" control 1204 in the second live notification.

[0295] Optionally, the first electronic device may send the aforementioned fifth request message to the system server or application server in the scenario shown in Figure 2. In a specific implementation, the way the first electronic device shares the updated information of at least one first control with the second electronic device can be referred to the way the first electronic device shares the first live notification with the second electronic device in the foregoing embodiment. Repeated details will not be repeated.

[0296] It is understood that in the foregoing embodiments, the first server can send the task progress information of the first task to the second electronic device according to the first preset period, so that the second electronic device can update the second live notification. When updating the task progress information of the first task to the second electronic device, the first server can simultaneously send the identifier of at least one first control determined by the first electronic device to the second electronic device, so that the second electronic device can update the control displayed in the second live notification.

[0297] In other embodiments, the second electronic device may also determine the controls displayed in the second live notification based on the task progress information of the first task. For specific implementation, please refer to the method by which the first electronic device determines the controls in the above embodiments. Repeated details will not be repeated.

[0298] Optionally, this application embodiment also provides a training method for an intent-aware model. Taking the training of the intent-aware model by a first electronic device as an example, in the training method provided in this application embodiment, the first electronic device can acquire third-party authorization data or other profile data for model training. The first electronic device generates a training sample set based on the third-party authorization data or other profile data. This training sample set includes multiple training samples. The input features in each training sample include the device identifier of the electronic device, the application identifier of the application, the task type information, and the task status information. The labels in the training samples include the mapping relationship between user behavior data and multiple controls of the application. The mapping relationship between user behavior data and multiple controls of the application can be, for example, the frequency of user clicks on each control among multiple controls. The first electronic device can train the initial model to be trained based on the training sample set to obtain the intent-aware model. Specific training methods can include, for example, gradient descent.

[0299] It should be noted that the above embodiments use the example of the first electronic device training the intent-aware model and the first electronic device determining the control based on the intent-aware model. In specific implementations, the system server can also train the intent-aware model and determine the control based on the intent-aware model. For specific implementations, please refer to the foregoing embodiments. Repeated parts will not be described again.

[0300] Based on the same concept, this application also provides a live notification sharing method, which can be executed by a first electronic device, a server, and a second electronic device. Figure 13 is a flowchart of a live notification sharing method provided by an embodiment of this application. Referring to Figure 13, the method includes the following steps:

[0301] S1301: In response to a first operation triggered by a first user, a first electronic device creates a first task related to a second user's user account in a first application of the first electronic device.

[0302] Among them, the first task related to the user account of the second user can be, for example, the task in which the first user enters the user account information of the second user when creating the first task. For example, the first task can be the task created by the first user in the interface shown in Figure 5A(a) to hail a taxi for the second user.

[0303] S1302: The first electronic device generates a first real-time notification corresponding to the first task and displays the first real-time notification.

[0304] The first live notification includes the task progress information for the first task.

[0305] For example, the first real-time notification displayed by the first electronic device can be seen in the first real-time notification 504 shown in Figure 5A(b). The first electronic device displays the first real-time notification 504 corresponding to the ride-hailing task, which may include the task progress information of the ride-hailing task.

[0306] S1303: The first electronic device sends a first request message to the server.

[0307] The first request message is used to request the server to share the first live notification to the second electronic device corresponding to the user account of the second user.

[0308] Optionally, the first electronic device may send a first request message to the account server or application server in the scenario shown in Figure 2.

[0309] S1304: The server determines the device identifier of the second electronic device corresponding to the second user's user account based on the correspondence between the second user's user account and the device identifiers of multiple user accounts and multiple electronic devices stored on the server.

[0310] S1305: The server sends a first real-time notification to the second electronic device based on the device identifier of the second electronic device.

[0311] S1306: The second electronic device generates a second real-time notification based on the information of the first real-time notification, and displays the second real-time notification.

[0312] The second real-time notification includes task progress information of the first task in the first application of the first electronic device.

[0313] For example, the second live notification displayed by the second electronic device can be the second live notification 508 shown in (d) of Figure 5A, and the task progress information of the first task in the second live notification 508 can be the same as the task progress information of the first task in the first live notification 504 of the first electronic device shown in (b) of Figure 5A.

[0314] It should be noted that the live notification sharing method shown in Figure 13 of this application can be referred to the above embodiments of this application in specific implementation, and repeated parts will not be described again.

[0315] It is understood that, in order to achieve the functions of the electronic devices and servers in the above embodiments, the electronic devices and servers include corresponding hardware and / or software structures for performing each function. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0316] Figure 14 is a schematic diagram of a data processing device provided in an embodiment of this application. Referring to Figure 14, the data processing device may include a processing unit 1401, a display unit 1402, and a communication unit 1403. This data processing device can be used to implement the method executed by any of the electronic devices in the above embodiments. The data processing device may be the electronic device itself, or it may be a chip or chipset in the electronic device, or a part of the chip used to execute the relevant method function.

[0317] In one embodiment, the data processing apparatus shown in FIG14 can be used to implement the method executed by the first electronic device in the embodiments of this application. The processing unit 1401 is configured to, in response to a first operation by a first user, create a first task related to a second user's user account in a first application of the first electronic device; and generate a first real-time notification corresponding to the first task.

[0318] Display unit 1402 is used to display the first real-time notification, which includes the task progress information of the first task.

[0319] The processing unit 1401 is used to send a first request message to the server through the communication unit 1403. The first request message is used to request the server to share the first live notification to the second electronic device corresponding to the user account of the second user.

[0320] For example, the first request message includes the user account information of the second user, which includes at least one of the account name and contact information of the second user entered when the first user created the first task.

[0321] Optionally, the processing unit 1401 is further configured to: obtain the task progress information of the first task with progress updates before the first task is completed, and send a second request message to the server through the communication unit 1403. The second request message is used to request the server to instruct the second electronic device to update the real-time notification corresponding to the first task. The second request message includes the task progress information of the first task with progress updates.

[0322] Optionally, the display unit 1402 is also configured to display a sharing control in the first live notification.

[0323] Processing unit 1401 is further configured to: in response to the second operation of the first user on the sharing control, send a third request message to the server, the third request message being used to request the server to share the first live notification to the third electronic device corresponding to the user account of the third user.

[0324] Optionally, the processing unit 1401 is further configured to: destroy the first live notification displayed in the first electronic device after the first task ends; and send a fourth request message to the server through the communication unit 1403, the fourth request message being used to request the server to instruct the second electronic device to destroy the live notification corresponding to the first task.

[0325] Optionally, the display unit 1402 is further configured to display at least one first control corresponding to the status of the first task in the first live notification, wherein the at least one first control is used to provide an interactive entry point corresponding to the business related to the first task.

[0326] Optionally, the processing unit 1401 is further configured to: obtain the status information of the first task corresponding to a first moment before the display unit 1402 displays at least one first control corresponding to the status of the first task in the first live notification; and determine the at least one first control displayed in the first live notification based on the status information of the first task corresponding to the first moment.

[0327] For example, the first moment is the moment when the state of the first task changes, and / or the first moment is the moment determined based on the start time of the first task and the second preset period.

[0328] Optionally, the processing unit 1401 is specifically configured to: input the device identifier of the first electronic device, the application identifier of the first application, the type information of the first task, and the state information of the first task corresponding to the first time moment into the intent perception model; obtain the probability value of each of the multiple controls related to the first task output by the intent perception model; and select the at least one first control according to the probability value of each of the multiple controls.

[0329] Optionally, the processing unit 1401 is specifically used to: select at least one control whose probability value is greater than a preset threshold according to the probability values ​​corresponding to the plurality of controls in descending order, and use the selected at least one control as the at least one first control.

[0330] For example, the number of the at least one first control is less than or equal to Q, where Q is a positive integer, and Q is the maximum number of controls that the display style of the first live notification supports displaying.

[0331] Optionally, the processing unit 1401 is further configured to: send a fifth request message to the server via the communication unit 1403, the fifth request message being used to request the server to instruct the second electronic device to update the control in the live notification corresponding to the first task, the fifth request message including the identifier of the at least one first control.

[0332] In one embodiment, the data processing apparatus shown in FIG14 can be used to implement the method executed by the second electronic device in the embodiments of this application. The processing unit 1401 is configured to receive information of a first real-time notification sent by a server via a communication unit 1403, wherein the first real-time notification is a real-time notification corresponding to a first task related to the user account of the second user in a first application of the first electronic device; generate a second real-time notification based on the information of the first real-time notification; and a display unit 1402 is configured to display the second real-time notification, wherein the second real-time notification includes task progress information of the first task in the first application of the first electronic device.

[0333] For example, the task progress of the first task displayed in the second live notification is the same as the task progress of the first task displayed in the first live notification.

[0334] For example, the display interface of the second electronic device when displaying the second live notification includes any of the following: lock screen, desktop, negative one screen, or interface of any application.

[0335] For example, the display styles of the second live notification and the first live notification may be the same or different, and the display style of the second live notification is related to the display scenario of the second electronic device.

[0336] Optionally, the display unit 1402 is further configured to display a first reminder message, which is used to ask the second user whether to receive the live notification shared by the first user; the processing unit 1401 is further configured to receive a confirmation operation triggered by the second user.

[0337] Optionally, the processing unit 1401 is further configured to receive the progress update information of the first task sent by the server via the communication unit 1403; the display unit 1402 is further configured to display the progress update information of the first task in the second real-time notification.

[0338] For example, the progress of the first task shown in the second live notification is the same as the progress of the first task shown in the first live notification.

[0339] Optionally, the display unit 1402 is also configured to display a sharing control in the second live notification;

[0340] The processing unit 1401 is also configured to respond to the third operation of the second user on the sharing control by sending a seventh request message to the server through the communication unit 1403. The seventh request message is used to request the server to share the second live notification to the fourth electronic device corresponding to the user account of the fourth user.

[0341] Optionally, the processing unit 1401 is further configured to receive a destruction notification message sent by the server through the communication unit 1403, the destruction notification message being used to instruct the second electronic device to destroy the live notification corresponding to the first task; and to destroy the second live notification.

[0342] Optionally, the processing unit 1401 is further configured to receive, via the communication unit 1403, an identifier of at least one first control related to the first task sent by the server, wherein the at least one first control is used to provide an interactive entry point corresponding to the business related to the first task.

[0343] The display unit 1402 is also configured to display the at least one first control in the second live notification.

[0344] The division of units (functional modules) in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, each unit in the various embodiments of this application can be integrated into a processor, exist as a separate physical entity, or have two or more units integrated into a single module. The integrated units described above can be implemented in hardware or as software functional modules. It is understood that the function or implementation of each unit in the embodiments of this application can be further referred to the relevant descriptions in the method embodiments.

[0345] Figure 15 is a schematic diagram of a data processing device provided in an embodiment of this application. Referring to Figure 15, the data processing device may include a processing unit 1501 and a communication unit 1502. This data processing device can be used to implement any of the methods executed by the server in the above embodiments. The data processing device may be the server itself, or it may be a chip or chipset in the server, or a part of the chip used to execute related methods.

[0346] In one embodiment, the data processing apparatus shown in FIG15 can be used to implement the method executed by the server in the embodiments of this application. The processing unit 1501 is configured to receive a first request message sent by a first electronic device via a communication unit 1502. The first request message requests the server to share a first live notification from the first electronic device to a second electronic device corresponding to a second user's user account. The first live notification is a live notification corresponding to a first task related to the second user's user account in a first application of the first electronic device. Based on the correspondence between the second user's user account and multiple user accounts and device identifiers of multiple electronic devices stored by the server, the processing unit 1501 determines the device identifier of the second electronic device corresponding to the second user's user account. Based on the device identifier of the second electronic device, the processing unit sends the information of the first live notification to the second electronic device via the communication unit 1502.

[0347] Optionally, the processing unit 1501 is further configured to receive a second request message sent by the first electronic device through the communication unit 1502, the second request message being used to request the server to instruct the second electronic device to update the real-time notification corresponding to the first task, the second request message including the task progress information of the first task with progress update; and to send the task progress information of the first task with progress update in the second request message to the second electronic device through the communication unit 1502.

[0348] Optionally, the processing unit 1501 is further configured to store update status information corresponding to the second electronic device after the information of the first live notification is sent to the second electronic device through the communication unit 1502 according to the device identifier of the second electronic device, the update status information being used to indicate the update status of the first live notification shared by the first electronic device to the second electronic device.

[0349] Optionally, the processing unit 1501 is further configured to receive a third request message sent by the first electronic device, the third request message being used to request the server to share the first live notification to the third electronic device corresponding to the user account of the third user; determine the device identifier of the third electronic device corresponding to the user account of the third user based on the correspondence between the user account of the third user and the device identifiers of multiple user accounts and multiple electronic devices stored by the server; and send the information of the first live notification to the third electronic device through the communication unit 1502 based on the device identifier of the third electronic device.

[0350] Optionally, the processing unit 1501 is further configured to receive a fourth request message sent by the first electronic device through the communication unit 1502, the fourth request message being used to request the server to instruct the second electronic device to destroy the live notification corresponding to the first task; and to send a destruction notification message to the second electronic device through the communication unit 1502, the destruction notification message being used to instruct the second electronic device to destroy the live notification corresponding to the first task.

[0351] Optionally, the processing unit 1501 is further configured to, after sending a destruction notification message to the second electronic device, receive a feedback message sent by the second electronic device via the communication unit 1502, the feedback message being used to indicate that the second electronic device has destroyed the real-time notification corresponding to the first task; and delete the update status information corresponding to the second electronic device stored in the server.

[0352] Optionally, the processing unit 1501 is further configured to receive a fifth request message sent by the first electronic device through the communication unit 1502. The fifth request message is used to request the server to instruct the second electronic device to update the controls in the real-time notification corresponding to the first task. The fifth request message includes the identifier of at least one first control. The at least one first control is a control corresponding to the status of the first task. The at least one first control is used to provide an interactive entry point corresponding to the business related to the first task. The processing unit 1501 is also configured to send the identifier of the at least one first control to the second electronic device through the communication unit 1502.

[0353] In one embodiment, the data processing apparatus shown in FIG15 can be used to implement the method executed by the first server in the embodiments of this application. The processing unit 1501 is configured to receive a first request message sent by a first electronic device via a communication unit 1502. The first request message requests the first server to share a first live notification from the first electronic device to a second electronic device corresponding to the application user account of a second user. The first live notification is a live notification corresponding to a first task related to the application user account of the second user in a first application of the first electronic device. Based on the correspondence between the application account information of the second user and the application account information and system account information of multiple users stored in the first server, the processing unit 1501 determines the system account information of the second user corresponding to the application account information of the second user. The processing unit 1501 then sends a sixth request message to the second server via the communication unit 1502. The sixth request message requests the second server to share the first live notification to the second electronic device corresponding to the system account information of the second user. The sixth request message includes the system account information of the second user.

[0354] For example, the first server is the server corresponding to the first application, and the second server is the server corresponding to the second electronic device.

[0355] The division of units (functional modules) in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, each unit in the various embodiments of this application can be integrated into a processor, exist as a separate physical entity, or have two or more units integrated into a single module. The integrated units described above can be implemented in hardware or as software functional modules. It is understood that the function or implementation of each unit in the embodiments of this application can be further referred to the relevant descriptions in the method embodiments.

[0356] Figure 16 is a possible structural example of a device provided in an embodiment of this application. This device can be used to implement the functions of the server in the above embodiments, or to implement the functions of the electronic device in the above embodiments, and thus can also achieve the beneficial effects of the above embodiments.

[0357] Referring to Figure 16, the device 1600 may include a processor 1601, a memory 1602, and a communication interface 1603. The processor 1601, memory 1602, and communication interface 1603 are coupled to each other. Optionally, the memory 1602 may be used to store instructions executed by the processor 1601, input data required for the processor 1601 to execute instructions, or data generated after the processor 1601 executes instructions. The communication interface 1603 may be a transceiver or an input / output interface.

[0358] Optionally, referring to Figure 16, the processor 1601, the memory 1602, and the communication interface 1603 are interconnected via a bus 1604. The bus 1604 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is used in Figure 16, but this does not indicate that there is only one bus or one type of bus.

[0359] When device 1600 is applied to an electronic device, processor 1601 can be used to implement the processing functions of the electronic device in the above embodiments. For example, processor 1601 can be used to execute the operation of processing unit 1401 in the data processing device shown in FIG14. Communication interface 1603 can be used to implement the sending and receiving functions of the electronic device in the above embodiments. For example, communication interface 1603 can be used to execute the operation of communication unit 1403 in the data processing device shown in FIG14, which will not be described in detail here.

[0360] When device 1600 is applied to a server, processor 1601 can be used to implement the server's processing functions in the above embodiments. For example, processor 1601 can be used to execute the actions of processing unit 1501 in the data processing device shown in FIG15. Communication interface 1603 can be used to implement the server's sending and receiving functions in the above embodiments. For example, communication interface 1603 can be used to execute the actions of communication unit 1502 in the data processing device shown in FIG15, which will not be described in detail here.

[0361] It is understood that the processor 1601 in the embodiments of this application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0362] The memory 1602 in Figure 16 of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. It should be noted that the memory in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0363] Based on the above embodiments, this application also provides a communication system, which includes multiple electronic devices and a server, wherein the electronic devices are used to implement the functions of the electronic devices in the above embodiments, and the server is used to implement the functions of the server in the above embodiments.

[0364] Based on the above embodiments, this application also provides a computer program product containing instructions, which, when run on a computer, causes the computer to execute the methods described in the embodiments of this application.

[0365] Based on the above embodiments, this application also provides a computer-readable storage medium storing a computer program, which, when executed by a computer, causes the computer to perform the methods described in the embodiments of this application.

[0366] Based on the above embodiments, this application also provides a chip for reading computer programs stored in a memory to implement the methods described in the embodiments of this application.

[0367] Based on the above embodiments, this application provides a chip system including a processor for supporting a computer device in implementing the methods described in the embodiments of this application. In one possible design, the chip system further includes a memory for storing necessary programs and data of the computer device. This chip system may be composed of chips or may include chips and other discrete devices.

[0368] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0369] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0370] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0371] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0372] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of protection of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for sharing live notifications, characterized in that, Applied to a first electronic device, the method includes: In response to a first operation by a first user, a first task related to a second user's user account is created in a first application of the first electronic device; Generate a first real-time notification corresponding to the first task, and display the first real-time notification, which includes the task progress information of the first task. Send a first request message to the server, the first request message being used to request the server to share the first live notification to the second electronic device corresponding to the user account of the second user.

2. The method as described in claim 1, characterized in that, The method further includes: Before the first task is completed, the task progress information of the first task with updated progress is obtained, and a second request message is sent to the server. The second request message is used to request the server to instruct the second electronic device to update the real-time notification corresponding to the first task. The second request message includes the task progress information of the first task with updated progress.

3. The method as described in claim 1 or 2, characterized in that, The method further includes: Display the sharing control in the first live notification; In response to the first user's second operation on the sharing control, a third request message is sent to the server, the third request message being used to request the server to share the first live notification to the third electronic device corresponding to the third user's user account.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: After the first task is completed, the first live notification displayed on the first electronic device is destroyed; A fourth request message is sent to the server, the fourth request message being used to request the server to instruct the second electronic device to destroy the live notification corresponding to the first task.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: The first live notification displays at least one first control corresponding to the status of the first task, and the at least one first control is used to provide an interactive entry point for the business related to the first task.

6. The method as described in claim 5, characterized in that, Before displaying at least one first control corresponding to the status of the first task in the first live notification, the method further includes: Obtain the status information of the first task at the first moment; The at least one first control displayed in the first live notification is determined based on the status information of the first task corresponding to the first moment.

7. The method as described in claim 6, characterized in that, The first moment is the moment when the state of the first task changes, and / or the first moment is the moment determined based on the start time of the first task and the second preset period.

8. The method as described in claim 6 or 7, characterized in that, Determining the at least one first control displayed in the first live notification based on the status information of the first task corresponding to the first time moment includes: The device identifier of the first electronic device, the application identifier of the first application, the type information of the first task, and the status information of the first task corresponding to the first time moment are input into the intent perception model; Obtain the probability value of each control among the multiple controls related to the first task output by the intent-aware model; Based on the probability value corresponding to each of the plurality of controls, at least one first control is selected.

9. The method according to any one of claims 5-8, characterized in that, The method further includes: A fifth request message is sent to the server, the fifth request message being used to request the server to instruct the second electronic device to update the controls in the live notification corresponding to the first task, the fifth request message including the identifier of the at least one first control.

10. A method for sharing live notifications, characterized in that, Applied to a server, the method includes: The server receives a first request message sent by a first electronic device. The first request message is used to request the server to share a first live notification in the first electronic device to the second electronic device corresponding to the user account of the second user. The first live notification is a live notification corresponding to a first task related to the user account of the second user in the first application of the first electronic device. Based on the correspondence between the second user's user account and the multiple user accounts and device identifiers of multiple electronic devices stored on the server, the device identifier of the second electronic device corresponding to the second user's user account is determined; The information of the first live notification is sent to the second electronic device based on the device identifier of the second electronic device.

11. The method as described in claim 10, characterized in that, The method further includes: The server receives a second request message sent by the first electronic device. The second request message is used to request the server to instruct the second electronic device to update the real-time notification corresponding to the first task. The second request message includes the task progress information of the first task with progress updates. The task progress information of the first task, which is described in the second request message, is sent to the second electronic device.

12. The method as described in claim 10 or 11, characterized in that, After sending the first live notification information to the second electronic device based on the device identifier of the second electronic device, the method further includes: The update status information corresponding to the second electronic device is stored, and the update status information is used to indicate the update status of the first live notification shared by the first electronic device to the second electronic device.

13. The method according to any one of claims 10-12, characterized in that, The method further includes: The server receives a third request message sent by the first electronic device, the third request message being used to request the server to share the first live notification to the third electronic device corresponding to the user account of the third user. Based on the correspondence between the user account of the third user and the device identifiers of multiple user accounts and multiple electronic devices stored on the server, the device identifier of the third electronic device corresponding to the user account of the third user is determined; The information of sending the first live notification to the third electronic device according to the device identifier of the third electronic device.

14. The method according to any one of claims 10-13, characterized in that, The method further includes: Receive a fourth request message sent by the first electronic device, the fourth request message being used to request the server to instruct the second electronic device to destroy the live notification corresponding to the first task; Send a destruction notification message to the second electronic device, the destruction notification message being used to instruct the second electronic device to destroy the live notification corresponding to the first task.

15. The method as described in claim 14, characterized in that, After sending a destruction notification message to the second electronic device, the method further includes: Receive a feedback message sent by the second electronic device, the feedback message being used to indicate that the second electronic device has destroyed the live notification corresponding to the first task; Delete the update status information corresponding to the second electronic device stored in the server.

16. The method according to any one of claims 10-15, characterized in that, The method further includes: The system receives a fifth request message sent by the first electronic device. The fifth request message is used to request the server to instruct the second electronic device to update the controls in the real-time notification corresponding to the first task. The fifth request message includes the identifier of at least one first control. The at least one first control is a control corresponding to the status of the first task. The at least one first control is used to provide an interactive entry point corresponding to the business related to the first task. Send the identifier of the at least one first control to the second electronic device.

17. A method for sharing live notifications, characterized in that, Applied to a first server, the method includes: Receive a first request message sent by a first electronic device. The first request message is used to request the first server to share a first live notification in the first electronic device to the second electronic device corresponding to the application user account of the second user. The first live notification is a live notification corresponding to a first task related to the application user account of the second user in the first application of the first electronic device. Based on the correspondence between the application account information of the second user and the application account information and system account information of multiple users stored in the first server, the system account information of the second user corresponding to the application account information of the second user is determined. A sixth request message is sent to the second server. The sixth request message is used to request the second server to share the first live notification to the second electronic device corresponding to the system account information of the second user. The sixth request message includes the system account information of the second user.

18. The method as described in claim 17, characterized in that, The first server is the server corresponding to the first application, and the second server is the server corresponding to the second electronic device.

19. A method for sharing live notifications, characterized in that, Applied to a second electronic device, the method includes: Receive information from the server regarding a first live notification, wherein the first live notification is a live notification corresponding to a first task related to the user account of the second user in a first application of the first electronic device; A second live notification is generated based on the information from the first live notification, and the second electronic device displays the second live notification. The second live notification includes the task progress information of the first task in the first application of the first electronic device.

20. The method as described in claim 19, characterized in that, The task progress of the first task displayed in the second live notification is the same as the task progress of the first task displayed in the first live notification.

21. The method as described in claim 19 or 20, characterized in that, The display interface of the second electronic device when displaying the second live notification includes any of the following: lock screen, desktop, negative one screen, or the interface of any application.

22. The method according to any one of claims 19-21, characterized in that, Before generating the second live notification based on the information from the first live notification, the method further includes: Display a first reminder message, which is used to ask the second user whether to receive the live notification shared by the first user; Receive confirmation from the second user.

23. The method according to any one of claims 19-22, characterized in that, The method further includes: Receive the task progress information of the first task, which is updated by the server. The second live notification displays the task progress information of the first task that has been updated.

24. The method as described in claim 23, characterized in that, The progress of the first task shown in the second live notification is the same as the progress of the first task shown in the first live notification.

25. The method according to any one of claims 19-24, characterized in that, The method further includes: Display the sharing control in the second live notification; In response to the second user's third operation on the sharing control, a seventh request message is sent to the server, the seventh request message being used to request the server to share the second live notification to the fourth electronic device corresponding to the user account of the fourth user.

26. The method according to any one of claims 19-25, characterized in that, The method further includes: Receive a destruction notification message sent by the server, the destruction notification message being used to instruct the second electronic device to destroy the live notification corresponding to the first task; Destroy the second live notification.

27. The method according to any one of claims 19-26, characterized in that, The method further includes: The server receives an identifier of at least one first control related to the first task, wherein the at least one first control is used to provide an interactive entry point corresponding to the business related to the first task. The at least one first control is displayed in the second live notification.

28. A method for sharing live notifications, characterized in that, The method is applied to a communication system, which includes a first electronic device, a second electronic device, and a server; the method includes: In response to a first user’s first operation, the first electronic device creates a first task related to the second user’s user account in a first application of the first electronic device; The first electronic device generates a first real-time notification corresponding to the first task and displays the first real-time notification, which includes the task progress information of the first task. The first electronic device sends a first request message to the server, the first request message being used to request the server to share the first live notification to the second electronic device corresponding to the user account of the second user; The server determines the device identifier of the second electronic device corresponding to the second user's user account based on the correspondence between the second user's user account and the multiple user accounts and device identifiers of multiple electronic devices stored on the server. The server sends the first real-time notification information to the second electronic device based on the device identifier of the second electronic device; The second electronic device generates a second live notification based on the information in the first live notification, and displays the second live notification. The second live notification includes the task progress information of the first task in the first application of the first electronic device.

29. The method as described in claim 28, characterized in that, The task progress of the first task displayed in the second live notification is the same as the task progress of the first task displayed in the first live notification.

30. The method as described in claim 28 or 29, characterized in that, The method further includes: Before the first task is completed, the first electronic device obtains the task progress information of the first task with progress updates, and sends a second request message to the second server. The second request message is used to request the second server to instruct the second electronic device to update the real-time notification corresponding to the first task. The second request message includes the task progress information of the first task with progress updates. The second server sends the progress information of the first task, which is updated in the second request message, to the second electronic device; The second electronic device displays the progress information of the first task in the second live notification.

31. The method as described in claim 30, characterized in that, The progress of the first task shown in the second live notification of the second electronic device is the same as the progress of the first task shown in the first live notification of the first electronic device.

32. The method according to any one of claims 28-31, characterized in that, The method further includes: The first electronic device displays a sharing control in the first live notification; In response to the second operation of the first user on the sharing control, the first electronic device sends a third request message to the server, the third request message being used to request the server to share the first live notification to the third electronic device corresponding to the user account of the third user. The server determines the device identifier of the third electronic device corresponding to the third user's user account based on the correspondence between the third user's user account and the multiple user accounts and device identifiers of multiple electronic devices stored on the server. The server sends the first live notification information to the third electronic device based on the device identifier of the third electronic device.

33. The method according to any one of claims 28-32, characterized in that, The method further includes: The second electronic device displays a sharing control in the second live notification; In response to the second user's third operation on the sharing control, the second electronic device sends a seventh request message to the server, the seventh request message being used to request the server to share the second live notification to the fourth electronic device corresponding to the user account of the fourth user; The server determines the device identifier of the fourth electronic device corresponding to the fourth user's user account based on the user account of the fourth user and the correspondence between multiple user accounts and device identifiers of multiple electronic devices stored on the server. The server sends the second live notification information to the fourth electronic device based on the device identifier of the fourth electronic device.

34. The method according to any one of claims 28-33, characterized in that, The method further includes: After the first task is completed, the first electronic device destroys the first live notification displayed on the first electronic device; the first electronic device sends a fourth request message to the server, the fourth request message being used to request the server to instruct the second electronic device to destroy the live notification corresponding to the first task; The server sends a destruction notification message to the second electronic device, the destruction notification message being used to instruct the second electronic device to destroy the live notification corresponding to the first task; The second electronic device destroys the second live notification.

35. The method according to any one of claims 28-34, characterized in that, The method further includes: The first electronic device displays at least one first control in the first live notification that corresponds to the status of the first task. The at least one first control is used to provide an interactive entry point for the business related to the first task.

36. The method as described in claim 35, characterized in that, Before the first electronic device displays at least one first control corresponding to the status of the first task in the first live notification, the method further includes: The first electronic device acquires the status information of the first task corresponding to the first moment; The first electronic device determines the at least one first control displayed in the first live notification based on the status information of the first task corresponding to the first time.

37. The method as described in claim 36, characterized in that, The first moment is the moment when the state of the first task changes, or the first moment is the moment determined based on the start time of the first task and the second preset period.

38. The method as described in claim 36 or 37, characterized in that, The first electronic device determines the at least one first control displayed in the first live notification based on the status information of the first task corresponding to the first time moment, including: The first electronic device inputs the device identifier of the first electronic device, the application identifier of the first application, the type information of the first task, and the state information of the first task corresponding to the first time moment into the intent perception model; The first electronic device acquires the probability value of each of the multiple controls related to the first task output by the intent-aware model; The first electronic device selects at least one first control based on the probability value corresponding to each of the plurality of controls.

39. The method according to any one of claims 35-38, characterized in that, The method further includes: The first electronic device sends a fifth request message to the server, the fifth request message being used to request the server to instruct the second electronic device to update the controls in the live notification corresponding to the first task, the fifth request message including the identifier of the at least one first control; The second server sends the identifier of the at least one first control to the second electronic device; The second electronic device displays the at least one first control in the second live notification.

40. An electronic device, characterized in that, The method includes at least one processor coupled to at least one memory, the at least one processor being configured to read a computer program stored in the at least one memory to perform the method as described in any one of claims 1-9, or to perform the method as described in any one of claims 19-27.

41. A server, characterized in that, The method includes at least one processor coupled to at least one memory, the at least one processor being configured to read a computer program stored in the at least one memory to perform the method as described in any one of claims 10-16, or to perform the method as described in claim 17 or 18.

42. A chip system, characterized in that, The chip system includes a processing circuit and a storage medium, wherein the storage medium stores instructions; when the instructions are executed by the processing circuit, they implement the method as described in any one of claims 1-9, or execute the method as described in any one of claims 10-16, or execute the method as described in claims 17 or 18, or execute the method as described in any one of claims 19-27.

43. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-9, or the method as described in any one of claims 10-16, or the method as described in claim 17 or 18, or the method as described in any one of claims 19-27.

44. 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-9, or the method as described in any one of claims 10-16, or the method as described in claim 17 or 18, or the method as described in any one of claims 19-27.

Images