WO2024001812A1 - Message management method, electronic device and system - Google Patents

Abstract

The present application relates to the technical field of terminals. Provided are a message management method, an electronic device and a system. In the present application, when it is determined that a notification message is allowed to be sent, a first device sends a received notification message to a second electronic device, thereby protecting user privacy. The method comprises: after a first notification message of a first application is received, and when it is determined that a notification message is allowed to be sent to a second device, a first device forwarding the first notification message to the second device, or sending to the second device a notification message associated with message content of the first notification message.

Description

Message management method, electronic device and system

This application claims priority to the Chinese patent application submitted to the State Intellectual Property Office on June 27, 2022, with application number 202210738273.0 and the invention name "Message Management Method, Electronic Device and System", the entire content of which is incorporated herein by reference. Applying.

Technical field

The embodiments of the present application relate to the field of terminal technology, and in particular, to a message management method, electronic device and system.

Background technique

With the development of terminal technology, users have more and more electronic devices. Among them, different applications are installed in different electronic devices, or different versions of the same application are installed to implement corresponding functions. In the process of using electronic devices, users need to repeatedly switch between multiple electronic devices to use the functions of different electronic devices.

In this regard, different electronic devices can form a multi-screen collaborative system by establishing multi-screen collaborative connections. In this way, the source device in the multi-screen collaboration system can project the display interface to the screen projection window of the receiving device. The user can use the functions of the source device through the projection window displayed by the receiving device, such as in the receiving device. View the push messages received by the source device in the screencasting window of the source device. However, during multi-screen collaboration, if the user wants to view the complete content of the push message, he or she needs to instruct the source device to start the application and display the corresponding message interface. Only then can the message interface be projected to the projection window of the receiving device. Display affects the user's use of other functions of the source device. Moreover, the push of messages may lead to the leakage of user privacy of the source device.

Contents of the invention

In order to solve the above technical problems, this application provides a message management method, electronic device and system. In the technical solution provided by this application, when the first device determines that sending the notification message is allowed, it sends the received notification message to the second electronic device, thereby protecting user privacy.

In order to achieve the above technical objectives, the embodiments of this application provide the following technical solutions:

The first aspect is to provide a message management method. The method includes: a first device receiving a first notification message of a first application. When the first device determines that sending a notification message to the second device is allowed, the first device sends a second notification message to the second device. The second notification message is the same as the first notification message, or the message content of the second notification message is the same as the first notification message. The message content of the message is associated, and the second notification message is used to instruct the second device to display the second notification message.

In some examples, the first device is a source device and the second device is a sink device. The first device and the second device can establish a multi-screen collaborative connection. The first notification message is a notification message received by the first application, or the first notification message is a notification message generated by the first application.

In some examples, the first application is a system application or a third-party application, and the first notification message is a system notification message or a third-party application notification message.

In this way, after receiving the notification message, the source device will forward the notification message to the receiving device only if it determines that forwarding of the notification message is allowed. In this way, on the basis of forwarding notification messages, user privacy can be protected, thereby avoiding leakage of user privacy and improving user experience.

According to the first aspect, when the first device determines that the notification message is allowed to be sent to the second device, sending the second notification message to the second device includes: the first device determines that the first application is allowed to send the notification message to the second device. In this case, send a second notification message to the second device.

For example, if application 1 is installed on the source device, application 1 is allowed to forward notification messages to receiving device 2, but is not allowed to forward notification messages to receiving device 2. Optionally, the receiving end device 1 and the receiving end device 2 are devices of different device types. For example, the receiving device 1 is a public device, and the public device includes electronic devices that are allowed to be used by any user, such as a large-screen device installed in a living room. The receiving device 2 is a privacy device, which includes electronic devices that are allowed to be used by some users, such as laptops with a power-on password set. In this way, the notification message of Application 1 will not be forwarded to the public device, thus ensuring the privacy of the notification message of Application 1.

In this way, according to the application type, configure whether to allow the notification message of the application to be forwarded to further ensure the security of user privacy and improve the user experience.

According to the first aspect, or any implementation of the above first aspect, when the first device determines that sending the notification message to the second device is allowed, sending the second notification message to the second device includes: the first device Determine that the first device and the second device correspond to the same account; or, if it is determined that the second device has obtained user authorization, send a second notification message to the second device.

For example, application 2 is installed on the source device, and the notification message forwarding rules configured by application 2 include forwarding notification messages to receiving device 1 and receiving device 2, and the user permissions are the same. That is to say, after receiving the notification message from Application 2, if the source device determines that the electronic device establishing a multi-screen collaborative connection with the source device includes the receiving device 1 and the receiving device 2, it can further determine that the receiving device 1 and the receiving device 2 Whether the receiving device 2 and the source device are logged into the same account, or whether the receiving device 1 and the receiving device 2 are instructed to confirm the password (such as obtaining user permissions through user operations). The source device can then send the notification message to the sink device configured with user permissions. For example, if App 2 is an SMS application, in order to prevent the notification messages received by App 2 from leaking user privacy, you can set the user permission to forward the notification messages of App 2. If it is determined to forward the notification message to a public device, you need to confirm your login account or password. Confirm to protect user privacy.

In this way, by setting the user permission to forward notification messages of the application, the security of user privacy is further ensured and the user experience is improved.

According to the first aspect, or any implementation of the above first aspect, the method further includes: the first device receiving a third notification message of the second application. When the first device determines that sending the notification message of the second application to the second device and the third device is allowed, after determining that the third device displays the interface of the second application, the first device sends the third device corresponding to the third notification message. Notification message; the fourth notification message is the same as the third notification message, or the message content of the fourth notification message is associated with the message content of the third notification message.

For example, the source device receives a notification message from a map application and determines that the receiving device that is allowed to forward the notification message may include cockpit screen 1 (such as a third device) and cockpit screen 2 (such as a second device). Furthermore, the source device determines that the cockpit screen 1 is displaying the map application, and can determine that the cockpit screen 1 has a higher priority for displaying the notification message. Then, the source device can send the notification message of the map application to the cockpit screen 1.

In this way, based on the display content of the receiving device, the source device preferentially forwards the received notification message to the receiving device that is displaying the source device application corresponding to the notification message. This allows the notification message to match the content displayed on the receiving device, further improving the user experience.

According to the first aspect, or any implementation of the first aspect above, the method further includes: when the first device determines that sending the notification message to the fourth device is not allowed, not sending the first notification message corresponding to the fourth device. a second notification message; wherein the first application in the first device is not allowed to send a notification message to the fourth device, and/or the fourth device corresponds to different accounts from the first device, and/or the first device does not obtain Allow sending to fourth device User authorization to send notification messages.

In this way, after receiving the notification message, the source device will not forward the notification message to the receiving device if it determines that forwarding of the notification message is not allowed. In this way, on the basis of forwarding notification messages, user privacy can be protected, thereby avoiding leakage of user privacy and improving user experience.

According to the first aspect, or any implementation of the above first aspect, the method further includes: the first device receiving a notification message triggering indication sent by the second device; wherein the notification message triggering indication is that the second device detects that the user has The second device displays a second notification message indicative of being sent after the first operation. The first device sends the display data of the first application corresponding to the second notification message to the second device according to the notification message triggering instruction; wherein the display data is the display data determined by whether the first application is in the foreground running state or the background running state. The display data Used to instruct the second device to display the interface of the first application corresponding to the second notification message according to the display data.

In this way, in different multi-screen collaboration scenarios, the receiving device can not only display the notification message sent by the source device, but also receive the user's operation on the notification message, thereby displaying the detailed content of the notification message. In order to meet the user's usage needs and reduce the user's operational difficulty.

According to the first aspect, or any implementation of the above first aspect, the first device sends the display data of the first application corresponding to the second notification message to the second device according to the notification message triggering instruction, including: the first device according to The notification message triggers an indication to determine the startup status of the first application. If it is determined that the first application corresponding to the notification message trigger indication has not been started, after starting the first application in the background, the display data is obtained; or, if it is determined that the first application corresponding to the notification message trigger indication has been started, the display data is obtained. The first device sends the display data of the first application corresponding to the second notification message to the second device.

For example, if the source device is displaying other applications in the foreground, starting the application corresponding to the notification message will not affect the display of the foreground application on the source device. For another example, if the source device is in the locked screen state, the user does not need to perform operations such as unlocking the source device. The source device can automatically launch the application corresponding to the notification message in the locked screen state.

In this way, the source device starts the application corresponding to the notification message in the background without affecting the operation of the source device, thereby improving the user experience.

According to the first aspect, or any implementation of the above first aspect, the first device sends the display data of the first application corresponding to the second notification message to the second device according to the notification message triggering instruction, including: the first device sends the display data of the first application corresponding to the second notification message to the second device. When it is determined that the first application allows the second device to display the detailed content of the notification message of the first application, the display data of the first application corresponding to the second notification message is sent to the second device according to the notification message triggering instruction.

In this way, only when permitted, the receiving device can expand and display the detailed content of the notification message forwarded by the source device, further protecting user privacy and improving user experience.

According to the first aspect, or any implementation of the above first aspect, the method further includes: the first device displays the first interface. The first device receives the user's setting operation on the first interface of whether the application in the first device allows forwarding of notification messages, and/or the setting operation of whether to allow sending notification messages to the second device.

In this way, users can customize notification message forwarding rules according to their needs, so that the source device notification message forwarding rules can better meet user needs.

The second aspect is to provide a message management method. The method includes: the second device receives a second notification message sent by the first device; wherein the second notification message is that the first device sends the second notification message to the second device under the condition that the first device determines that sending the notification message to the second device is allowed. , the second notification message is a notification message determined by the first device according to the first notification message of the first application in the first device, and the second notification message is the same as the first notification message, or the second notification message is the same as the first notification message. The message content of the second notification message is associated with the message content of the first notification message. The second device displays a second notification message.

In this way, during the process of multi-screen collaboration, the receiving device can also display the notification messages received by the source device through the multi-screen collaboration connection, thereby avoiding the omission of notification messages caused by the user not paying attention to the source device. Moreover, the user does not need to operate two electronic devices, and can check the notification message of the other electronic device while operating one electronic device, reducing the difficulty of user operation.

According to the second aspect, the second device displays the second notification message, including: the second device displays the second notification message when it is determined that display of the notification message of the first application is allowed.

In this way, the receiving device can protect user privacy on the basis of displaying notification messages, thereby avoiding leakage of user privacy and improving user experience.

According to the second aspect, or any implementation of the above second aspect, the second device displays the second notification message when it is determined that the second device is in a scene that allows display of the notification message of the first application.

For example, the receiving device can be configured to display the notification message of Application 2 in some display scenarios. For example, the receiving device supports displaying notification messages of Application 2 in non-video playback scenarios. This prevents the display of notification messages from affecting the user's video viewing experience.

In this way, based on different scenarios, the receiving device determines whether to allow the notification message to be displayed, further improving the user experience.

According to the second aspect, or any implementation of the above second aspect, the method further includes: after the second device detects the user's first operation on the second notification message, and determines that the second notification message is allowed to be operated, Send a notification message triggering indication to the first device; the notification message triggering indication is used to request to obtain display data of the first application corresponding to the second notification message, where the display data is display data determined to be in a foreground running state or a background running state. The second device receives the display data sent by the first device. The second device displays the interface of the first application corresponding to the second notification message according to the display data.

In this way, the user can open the notification message on the receiving device without operating the source device, thereby reducing the user's operation difficulty and improving the user experience.

In addition, the source device directly determines the display data, and the receiving device does not need to install the application corresponding to the notification message. It can directly display the application interface corresponding to the notification message based on the display data, thereby reducing the difficulty of application development.

According to the second aspect, or any implementation of the above second aspect, the method further includes: the second device displays the second interface. The second device receives the user's setting operation on the second interface to allow the application of the second device to display notification messages, and/or the setting operation to allow the display of notification messages to a scene.

In this way, users can customize the notification message display rules and notification message operation rules according to their needs, so that the notification message display rules and notification message operation rules of the receiving end device can better meet the user's needs.

For the technical effects corresponding to the second aspect and any one of the implementation methods of the second aspect, please refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect, which will not be described again here.

In a third aspect, embodiments of the present application provide an electronic device. The electronic device includes: a processor and a memory. The memory is coupled to the processor, and the memory is used to store computer program code. The computer program code includes computer instructions. When the processor reads the computer instructions from the memory, the electronic device executes: the first device receives a first notification message of the first application. When the first device determines that sending a notification message to the second device is allowed, the first device sends a second notification message to the second device. The second notification message is the same as the first notification message, or the second notification message is The information content is associated with the message content of the first notification message, and the second notification message is used to instruct the second device to display the second notification message.

According to a third aspect, when the first device determines that the notification message is allowed to be sent to the second device, sending the second notification message to the second device includes: the first device determines that the first application is allowed to send the notification message to the second device. In this case, send a second notification message to the second device.

According to the third aspect, or any implementation of the above third aspect, when the first device determines that sending the notification message to the second device is allowed, sending the second notification message to the second device includes: the first device Determine that the first device and the second device correspond to the same account; or, if it is determined that the second device has obtained user authorization, send a second notification message to the second device.

According to the third aspect, or any implementation of the above third aspect, when the processor reads the computer-readable instructions from the memory, it also causes the electronic device to perform the following operations: the first device receives the third notification message of the second application . When the first device determines that sending the notification message of the second application to the second device and the third device is allowed, after determining that the third device displays the interface of the second application, the first device sends the third device corresponding to the third notification message. Notification message; the fourth notification message is the same as the third notification message, or the message content of the fourth notification message is associated with the message content of the third notification message.

According to the third aspect, or any implementation of the above third aspect, when the processor reads the computer-readable instructions from the memory, it also causes the electronic device to perform the following operations: the first device determines that it is not allowed to send data to the fourth device. In the case of a notification message, the second notification message corresponding to the first notification message is not sent to the fourth device; wherein the first application in the first device is not allowed to send the notification message to the fourth device, and/or the fourth device and The first device corresponds to a different account, and/or the first device does not obtain user authorization that is allowed to send the notification message to the fourth device.

According to the third aspect, or any implementation of the above third aspect, when the processor reads the computer-readable instructions from the memory, it also causes the electronic device to perform the following operations: the first device receives the notification message sent by the second device to trigger Instruction; wherein, the notification message triggering indication is an instruction sent after the second device detects the user's first operation on the second notification message displayed by the second device. The first device sends the display data of the first application corresponding to the second notification message to the second device according to the notification message triggering instruction; wherein the display data is the display data determined by whether the first application is in the foreground running state or the background running state. The display data Used to instruct the second device to display the interface of the first application corresponding to the second notification message according to the display data.

According to the third aspect, or any implementation manner of the above third aspect, the first device sends the display data of the first application corresponding to the second notification message to the second device according to the notification message triggering instruction, including: the first device according to The notification message triggers an indication to determine the startup status of the first application. If it is determined that the first application corresponding to the notification message trigger indication has not been started, after starting the first application in the background, the display data is obtained; or, if it is determined that the first application corresponding to the notification message trigger indication has been started, the display data is obtained. The first device sends the display data of the first application corresponding to the second notification message to the second device.

According to the third aspect, or any implementation of the above third aspect, the first device sends the display data of the first application corresponding to the second notification message to the second device according to the notification message triggering instruction, including: the first device sends the display data of the first application corresponding to the second notification message to the second device. When it is determined that the first application allows the second device to display the detailed content of the notification message of the first application, the display data of the first application corresponding to the second notification message is sent to the second device according to the notification message triggering instruction.

According to the third aspect, or any implementation of the above third aspect, when the processor reads the computer-readable instructions from the memory, it also causes the electronic device to perform the following operations: the first device displays the first interface. First setting The device receives, on the first interface, the user's setting operation on whether the application in the first device is allowed to forward notification messages, and/or the setting operation on whether the application in the first device is allowed to send notification messages to the second device.

For the technical effects corresponding to the third aspect and any one of the implementation methods of the third aspect, please refer to the technical effects corresponding to the above-mentioned third aspect and any one of the implementation methods of the third aspect, which will not be described again here.

In a fourth aspect, embodiments of the present application provide an electronic device. The electronic device includes: a processor, a memory and a display screen. The memory and the display screen are coupled to the processor. The memory is used to store computer program codes. The computer program codes include computer instructions. When the processor reads the computer instructions from the memory, the electronic device The device executes: the second device receives a second notification message sent by the first device; wherein the second notification message is a notification message determined by the first device according to the first notification message of the first application in the first device, and the second notification message The message content is the same as the first notification message, or the message content of the second notification message is associated with the message content of the first notification message. The second device displays a second notification message.

According to a fourth aspect, the second device displays the second notification message, including: when the second device determines that display of the notification message of the first application is allowed, displaying the second notification message.

According to the fourth aspect, or any implementation of the above fourth aspect, the second device displays the second notification message when it is determined that the second device is in a scene that allows display of the notification message of the first application.

According to the fourth aspect, or any implementation of the above fourth aspect, when the processor reads the computer-readable instructions from the memory, it also causes the electronic device to perform the following operations: the second device detects the user's response to the second notification message. After the first operation, when it is determined that the operation of the second notification message is allowed, a notification message triggering indication is sent to the first device; the notification message triggering indication is used to request to obtain the display data of the first application corresponding to the second notification message, and the display data Display data determined when the first application is in a foreground running state or a background running state. The second device receives the display data sent by the first device. The second device displays the interface of the first application corresponding to the second notification message according to the display data.

According to the fourth aspect, or any implementation of the above fourth aspect, when the processor reads the computer-readable instructions from the memory, it also causes the electronic device to perform the following operations: the second device displays the second interface. The second device receives the user's setting operation on the second interface to allow the application of the second device to display notification messages, and/or the setting operation to allow the display of notification messages to a scene.

For the technical effects corresponding to the fourth aspect and any one of the implementation methods of the fourth aspect, please refer to the technical effects corresponding to the above-mentioned second aspect and any one of the implementation methods of the second aspect, which will not be described again here.

In a fifth aspect, embodiments of the present application provide a message management system. The system includes a first device and a second device. Wherein, the first device is used to receive a first notification message of the first application. The first device is also configured to send a second notification message to the second device if it is determined that the notification message is allowed to be sent to the second device. The second notification message is the same as the first notification message, or the message content of the second notification message is Associated with the message content of the first notification message. The second device is used to receive the second notification message. The second device is also used to display the second notification message.

According to the fifth aspect, the first device is specifically configured to send the second notification message to the second device when it is determined that the first application allows sending the notification message to the second device.

According to the fifth aspect, or any implementation of the fifth aspect above, the second device is specifically configured to display the second notification message when it is determined that display of the notification message of the first application is allowed.

According to the fifth aspect, or any implementation of the fifth aspect above, the second device is specifically configured to display the second notification message when it is determined that the second device is in a scenario that allows display of the notification message of the first application.

According to the fifth aspect, or any implementation of the fifth aspect above, the first device is further configured to send a second notification message to the second device when it is determined that sending the notification message to the second device is allowed, including: The first device, after determining that the first device and the second device correspond to the same account; or, after determining that the second device has obtained user authorization, sends a second notification message to the second device.

According to the fifth aspect, or any implementation of the fifth aspect above, the system further includes a third device. The first device is also configured to receive a third notification message from the second application. The first device is also configured to send a third notification message to the third device after determining that the third device displays the interface of the second application when it is determined that the notification message of the second application is allowed to be sent to the second device and the third device. The corresponding fourth notification message; the fourth notification message is the same as the third notification message, or the message content of the fourth notification message is associated with the message content of the third notification message.

According to the fifth aspect, or any implementation of the fifth aspect above, the system further includes a fourth device. The first device is also configured to not send the second notification message corresponding to the first notification message to the fourth device when it is determined that the notification message is not allowed to be sent to the fourth device; wherein the first application in the first device does not The notification message is allowed to be sent to the fourth device, and/or the fourth device and the first device correspond to different accounts, and/or the first device does not obtain user authorization that allows the notification message to be sent to the fourth device.

According to the fifth aspect, or any implementation of the above fifth aspect, the second device is further configured to detect the user's first operation on the second notification message. The second device is further configured to send a notification message triggering indication to the first device when it is determined that operation of the second notification message is allowed. The first device is also used to receive notification message trigger instructions. The first device is further configured to send display data of the first application corresponding to the second notification message to the second device according to the notification message triggering instruction; the display data is display data determined by whether the first application is in a foreground running state or a background running state. The second device is also used to receive display data. The second device is also configured to display the interface of the first application corresponding to the second notification message according to the display data.

For the technical effects corresponding to the fifth aspect and any one of the implementation methods of the fifth aspect, please refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect, or for the technical effects corresponding to the above-mentioned second aspect and any one of the implementation methods. The technical effects corresponding to either implementation method in the two aspects will not be described again here.

In a sixth aspect, embodiments of the present application provide an electronic device that has the function of implementing the message management method in the above first aspect and any possible implementation manner thereof. This function can be implemented by hardware, or can be implemented by hardware and corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

For the technical effects corresponding to the sixth aspect and any one of the implementation methods of the sixth aspect, please refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect, which will not be described again here.

In a seventh aspect, embodiments of the present application provide an electronic device that has the function of implementing the message management method in the above first aspect and any possible implementation manner thereof. This function can be implemented by hardware, or can be implemented by hardware and corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

For the technical effects corresponding to the seventh aspect and any one of the implementation methods of the seventh aspect, please refer to the technical effects corresponding to the above-mentioned second aspect and any one of the implementation methods of the second aspect, which will not be described again here.

In an eighth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program (which may also be referred to as instructions or codes). When the computer program is executed by an electronic device, it causes the electronic device to perform the method of the first aspect or any one of the embodiments of the first aspect; or , causing the electronic device to perform the second aspect Or the method of any embodiment of the second aspect.

For the technical effects corresponding to the eighth aspect and any one of the implementation methods of the eighth aspect, please refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect, or for the technical effects corresponding to the above-mentioned second aspect and any one of the implementation methods. The technical effects corresponding to either implementation method in the two aspects will not be described again here.

In a ninth aspect, embodiments of the present application provide a computer program product. When the computer program product is run on an electronic device, it causes the electronic device to execute the method of the first aspect or any one of the embodiments of the first aspect; or, causes the electronic device to execute The device performs the second aspect or the method of any one of the implementation modes of the second aspect.

For the technical effects corresponding to the ninth aspect and any one of the implementation methods of the ninth aspect, please refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect, or for the technical effects corresponding to the above-mentioned second aspect and any one of the implementation methods. The technical effects corresponding to either implementation method in the two aspects will not be described again here.

In a tenth aspect, embodiments of the present application provide a circuit system. The circuit system includes a processing circuit. The processing circuit is configured to execute the method of the first aspect or any one of the implementation modes of the first aspect; or, the processing circuit is configured to execute The method of the second aspect or any one of the second aspects.

For the technical effects corresponding to the tenth aspect and any one of the implementation methods of the tenth aspect, please refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect, or you can refer to the above-mentioned second aspect and the third aspect. The technical effects corresponding to either implementation method in the two aspects will not be described again here.

In an eleventh aspect, embodiments of the present application provide a chip system, including at least one processor and at least one interface circuit. The at least one interface circuit is used to perform transceiver functions and send instructions to at least one processor. When at least one processes When the processor executes the instruction, at least one processor executes the first aspect or the method of any one of the implementations of the first aspect; or, at least one processor executes the second aspect or the method of any one of the implementations of the second aspect.

For the technical effects corresponding to the eleventh aspect and any one of the implementation methods of the eleventh aspect, please refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect, or you can refer to the above-mentioned second aspect. And the technical effects corresponding to any implementation method in the second aspect will not be described again here.

Description of drawings

Figure 1 is a schematic diagram of a screen projection scene provided by an embodiment of the present application;

Figure 2 is a schematic diagram 2 of the screen projection scene provided by the embodiment of this application;

Figure 3 is a schematic diagram of a communication system applied to a message management method provided by an embodiment of the present application;

Figure 4 is a schematic diagram of the hardware structure of the source device or the receiving device provided by the embodiment of the present application;

Figure 5 is a schematic flow chart of the message management method provided by the embodiment of the present application;

Figure 6 is a schematic diagram of module interaction provided by the embodiment of this application;

Figure 7 is a schematic diagram of the application scenario of the message management method provided by the embodiment of the present application;

Figure 8 is a schematic flowchart 2 of the message management method provided by the embodiment of the present application;

Figure 9 is a schematic diagram 2 of the application scenario of the message management method provided by the embodiment of the present application;

Figure 10 is a schematic diagram of a notification message control scenario in the message management method provided by the embodiment of the present application;

Figure 11 is a schematic flowchart three of the message management method provided by the embodiment of the present application;

Figure 12 is a schematic structural diagram of a source device provided by an embodiment of the present application;

Figure 13 is a schematic structural diagram of a receiving end device provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. In the description of the embodiments of the present application, the terms used in the following embodiments are only for the purpose of describing specific embodiments and are not intended to limit the present application. As used in the specification and appended claims of this application, the singular expressions "a," "an," "," "the above," "the" and "the" are intended to include, for example, " "one or more" unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of this application, "at least one" and "one or more" refer to one or more than two (including two).

Reference in this specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Therefore, the phrases "in one embodiment", "in some embodiments", "in other embodiments", "in other embodiments", etc. appearing in different places in this specification are not necessarily References are made to the same embodiment, but rather to "one or more but not all embodiments" unless specifically stated otherwise. The terms “including,” “includes,” “having,” and variations thereof all mean “including but not limited to,” unless otherwise specifically emphasized. The term "connected" includes both direct and indirect connections unless otherwise stated. “First” and “second” are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the quantity of indicated technical features.

In the embodiments of this application, words such as "exemplarily" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "such as" in the embodiments of the present application is not to be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a concrete manner.

In some scenarios, with the development of terminal technology, electronic equipment forms are becoming more and more diverse, including mobile phones, laptops, large-screen devices and other forms. Users may need to use different forms of electronic devices in daily life or office work. By realizing collaborative work between multiple electronic devices, users can meet the functional needs of different electronic devices.

In some embodiments, multi-screen collaborative connections between multiple devices can be established to meet the user's needs for using multiple device functions. For example, multi-screen collaborative applications are installed in different electronic devices, and then multi-screen collaborative connections between different electronic devices can be established through the multi-screen collaborative applications. Among the various electronic devices that establish a multi-screen collaborative connection, the source device can project the display content to the receiving device for display, and the user can view the projected content of the source device on the receiving device. Among them, screen casting includes, for example, push screen casting and mirror screen casting.

Optionally, push screencasting includes, for example, putting multimedia resources of the source device onto the receiving device for playback. The multimedia resources include audio and video resources. For example, the mobile phone sends the resource address of the video to the large-screen device, and the large-screen device can play the corresponding video based on the resource address. And during the screencasting process, it does not affect the user's use of the mobile phone.

Exemplarily, as shown in Figure 1, the source device 11 (such as a mobile phone) and the sink device 12 (such as a large screen device) establish a multi-screen collaborative connection, and the source device 11 puts video resources to the sink device 12 to play on. As shown in Figure 1, during the video playback process of the receiving device 12, the use of the source device 11 will not be affected, for example, the source device 11 displays the desktop. However, push screencasting is usually used for multimedia resource screencasting and is not suitable for other screencasting content in many scenarios. For example, as shown in Figure 1, the source device 11 displays a notification pop-up window 101, prompting the user that the source device 11 has received a new message. During this process, the source device 11 cannot push the new message to the receiving device 12. Moreover, during the push screencasting process, users generally pay more attention to the display content of the receiving device 12, so there is a risk of missing new messages from the source device 11, affecting the user experience.

Optionally, mirroring screen projection includes, for example, projecting the display content of the source device's display screen to the sink device's display screen for display, that is, mirroring the entire display screen of the source device on the sink device. For example, the mobile phone sends the display content to the laptop, and the laptop displays the received display content in the screen projection window. During this process, the display content in the laptop screen projection window changes as the display content on the mobile phone display changes.

Illustratively, as shown in (a) of Figure 2, the source device 21 (such as a mobile phone) and the receiving device 22 (such as a laptop) establish a multi-screen collaborative connection, and the source device 21 puts the content displayed on the display screen. to the screen projection window 201 of the receiving end device 22 for display. As shown in (a) of FIG. 2 , during the process of the source device 21 displaying the desktop, the desktop display content of the source device 21 is mirrored in the screen projection window 201 of the receiving device 22 . If the source device 21 displays a notification pop-up window 202, a notification pop-up window 203 with corresponding content will also be displayed in the projection window 201 of the corresponding receiving device 22 to prompt the user that the source device 21 has received a new message.

However, during this process, since the source device mirrors the display content in the screen projection window of the receiving device, if the push message involves user privacy, the receiving device (for example, the receiving device is a public device) displays the push message. , which will lead to the leakage of user privacy.

Further, as shown in (a) of Figure 2, after the receiving device 22 detects the user's click on the notification pop-up window 203, it can determine that the user has instructed to open the notification message, and then the receiving device 22 can send a message to the source device 21. Message details display request. Correspondingly, as shown in (b) of FIG. 2 , the source device 21 starts the application corresponding to the notification message according to the message details display request, and displays the notification message interface. Then, the notification message interface of the source device 21 will also be mirrored in the projection window 201 of the receiving device 22, thereby enabling the user to reversely operate the notification message on the receiving device 22 side to view the details of the notification message.

However, it can be seen that in the process of reverse operation of the notification message, the source device needs to open the corresponding application in the foreground, and then cast the screen to the screen projection window of the receiving device for display. It does not support black screen on the source device or starting applications in the background, and the scenarios are very limited.

In addition, in the scenario shown in (a) of FIG. 2 , the receiving device 22 needs to display the screen projection window 201 in the foreground in order to display the display content of the source device 21 . If the screen casting window 201 is switched to the background or closed, the receiving device 22 cannot display the push messages received by the source device 21 , which may also lead to the omission of new messages.

In this regard, some electronic devices are configured with message aggregation pages. When the receiving device determines that the screen casting window is in the background, it can display the obtained push message on the message aggregation page, thereby avoiding failure to receive the delivered message. However, in this scenario, if the user needs to view the detailed and complete content of the push, he or she also needs to instruct the source device through the receiving device to launch the application corresponding to the push message in the foreground, and then use mirroring to realize the push message on the receiving device. The application interface corresponding to the push message is displayed in the screen casting window. There are also the above-mentioned problems of user privacy leakage and scene limitations.

In other embodiments, after receiving a notification message (such as a new email notification), the source device (such as a mobile phone) can detect whether there is a prompt device (such as a user wearing a mobile phone) in the surrounding environment that can be used to prompt the source device to generate a notification message. wearable devices), and connected devices (such as large-screen devices) that can be used to display notification messages. After determining that these two devices exist, the source device can send an instruction to the prompt device to instruct the prompt device to display a prompt message. The prompt information is used to prompt the user that the source device has received the notification message, and to prompt the user whether to view the prompt message through the connecting device. In response to the user's determination operation on the prompting device, the prompting device may send indication information to the corresponding connecting device. Correspondingly, the connecting device launches the service or application corresponding to the notification message according to the instruction information. Therefore, the user can view the notification message on the connected device side. In this way, through multi-device collaborative work, when the source device is not around the user, the prompt device near the user can also prompt the user to process the notification message through a connecting device with a notification message processing function, thereby avoiding notifications from the source device. Message missing.

However, in this process, there is also the risk of leaking user privacy. Moreover, the connecting device needs to support the same service or application corresponding to the notification message in the source device. This requires developers to develop the same service or application adapted to different forms of electronic devices during the development process, which increases the development time. Difficulty affects the versatility of the solution.

Therefore, embodiments of the present application provide a message management method. Through the message management policy, the receiving device can display push messages from the source device allowed by the user to protect user privacy. In addition, users can push messages in reverse on the receiving device without affecting other functions of the source device, improving the user experience.

Figure 3 is a schematic diagram of a communication system in which the message management method provided by the embodiment of the present application is applied. As shown in Figure 3, the communication system includes a source device 100 and a sink device 200. Optionally, the number of source devices 100 or sink devices 200 is one or more. For example, as shown in FIG. 3 , the source device 100 includes source device 1 and source device 2 , and the sink device 200 includes sink device 1 , sink device 2 , and sink device 3 .

Optionally, the source device 100 or the sink device 200 may be, for example, a mobile phone, a tablet computer, a large-screen device, a car machine, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant. (personal digital assistant, PDA), wearable devices, artificial intelligence (AI) devices and other terminal devices with screen projection function. The operating systems installed on the source device 100 or the receiving device 200 include but are not limited to or other operating systems. The embodiment of the present application does not limit the specific type of the source device 100 or the sink device 200 or the operating system installed.

In some embodiments, the source device 100 and the sink device 200 establish a wireless communication connection. Among them, the wireless communication technology for establishing a wireless communication connection includes but is not limited to at least one of the following: Bluetooth (bluetooth, BT) (for example, traditional Bluetooth or low-power (bluetooth low energy, BLE) Bluetooth), wireless local area network (wireless local area network) area networks, WLAN) (such as wireless fidelity (Wi-Fi) network), near field communication (NFC), Zigbee, frequency modulation (FM), infrared , IR), ultra wideband (UWB), etc.

Optionally, the source device 100 and the sink device 200 support the proximity discovery function. For example, after the source device 100 is close to the sink device 200, the source device 100 and the sink device 200 can discover each other, and then establish a Wi-Fi peer-to-peer (P2P) connection, a Bluetooth connection, etc. Wireless communication connection.

Optionally, the source device 100 and the sink device 200 establish a wireless communication connection through a local area network. For example, the source device 100 and the sink device 200 are both connected to the same router and can discover each other and establish a wireless communication connection.

Optionally, the source device 100 and the sink device 200 can also establish a communication connection through a third-party device in the local area network. The third-party device is, for example, a router, a gateway, an intelligent device controller, a server, or a wireless access point. , AP) equipment, etc.

Optionally, the source device 100 and the sink device 200 can also communicate through a distributed soft bus. It should be noted that the relevant content of the distributed soft bus can be referred to the existing technology, which will not be described again in the embodiments of this application.

For example, FIG. 4 shows a schematic structural diagram of the source device 100 or the sink device 200.

The source device 100 or the sink device 200 may include a processor 110, an external memory interface 120, an internal Memory 121, universal serial bus (USB) interface 130, charging management module 140, power management module 141, battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, Sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and subscriber identification module (subscriber identification module, SIM) card interface 195, etc.

It can be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the source device 100 or the sink device 200. In other embodiments of the present application, the source device 100 or the sink device 200 may include more or less components than shown in the figures, or combine some components, or split some components, or arrange different components. The components illustrated may be implemented in hardware, software, or a combination of software and hardware.

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

The controller can generate operation control signals based on the instruction operation code and timing signals to complete the control of fetching and executing instructions.

The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in processor 110 is cache memory. This memory may hold instructions or data that have been recently used or recycled by processor 110 . If the processor 110 needs to use the instructions or data again, it can be called directly from the memory. Repeated access is avoided and the waiting time of the processor 110 is reduced, thus improving the efficiency of the system.

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

The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (derail clock line, SCL). In some embodiments, processor 110 may include multiple sets of I2C buses. The processor 110 can separately couple the touch sensor, charger, flash, camera 193, etc. through different I2C bus interfaces. For example, the processor 110 can be coupled to a touch sensor through an I2C interface, so that the processor 110 and the touch sensor communicate through an I2C bus interface to implement the touch function of the source device 100 or the sink device 200 .

The MIPI interface can be used to connect the processor 110 with peripheral devices such as the display screen 194 and the camera 193 . MIPI interfaces include camera serial interface (CSI), display serial interface (DSI), etc. In some embodiments, the processor 110 and the camera 193 communicate through the CSI interface to implement the shooting function of the source device 100 or the sink device 200 . The processor 110 and the display screen 194 communicate through the DSI interface to implement the display function of the source device 100 or the sink device 200 .

The USB interface 130 is an interface that complies with USB standard specifications. Specifically, it can be a Mini USB interface, Micro USB interface, USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the source device 100 or the sink device 200, and can also be used to transmit data between the source device 100 or the sink device 200 and peripheral devices. It can also be used to connect headphones to play audio through them. This interface can also be used to connect other first electronic devices, such as AR devices.

It can be understood that the interface connection relationship between the modules illustrated in the embodiment of the present application is only a schematic explanation and does not constitute a structural limitation on the source device 100 or the sink device 200 . In other embodiments of the present application, the source device 100 or the sink device 200 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

The charging management module 140 is used to receive charging input from the charger. Among them, the charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from the wired charger through the USB interface 130 . In some wireless charging embodiments, the charging management module 140 may receive wireless charging input through the wireless charging coil of the source device 100 or the sink device 200 . While charging the battery 142, the charging management module 140 can also provide power to the first electronic device through the power management module 141.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charging management module 140, and supplies power to the processor 110, the internal memory 121, the display screen 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 can also be used to monitor battery capacity, battery cycle times, battery health status (leakage, impedance) and other parameters. In some other embodiments, the power management module 141 may also be provided in the processor 110 . In other embodiments, the power management module 141 and the charging management module 140 may also be provided in the same device.

The wireless communication function of the source device 100 or the receiving device 200 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in source device 100 or sink device 200 may be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example: Antenna 1 can be reused as a diversity antenna for a wireless LAN. In other embodiments, antennas may be used in conjunction with tuning switches.

The mobile communication module 150 can provide wireless communication solutions including 2G/3G/4G/5G applied on the source device 100 or the sink device 200 . 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 through the antenna 1, perform filtering, amplification and other processing on the received electromagnetic waves, and transmit them to the 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 through the antenna 1 for radiation. In some embodiments, at least part of the functional modules of the mobile communication module 150 may be disposed in the processor 110 . In some embodiments, at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be provided in the same device.

A modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs sound signals through the audio device, or displays images or videos through the display screen 194 . In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be independent of the processor 110 and may be provided in the same device as the mobile communication module 150 or other functional modules.

The wireless communication module 160 can provide wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), Bluetooth (bluetooth, BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (infrared, IR) and other wireless communication solutions . The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2 , frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 . The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.

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

The source device 100 or the sink device 200 implements the display function through the GPU, the display screen 194, and the application processor. The GPU is an image processing microprocessor and is connected to the display screen 194 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, videos, etc. Display 194 includes a display panel. The display panel can use a liquid crystal display (LCD), such as an organic light-emitting diode (OLED), an active matrix organic light emitting diode or an active matrix organic light emitting diode (active-matrix). Production and manufacturing of organic light emitting diodes (AMOLED), flexible light-emitting diodes (FLED), Mini-led, Micro-led, Micro-oled, quantum dot light emitting diodes (QLED), etc. . In some embodiments, the source device 100 or the sink device 200 may include 1 or N display screens 194, where N is a positive integer greater than 1.

In some embodiments, the source device 100 and the sink device 200 establish communication connections through respectively configured wireless communication modules 160 . Subsequently, after receiving the notification message, the source device 100 determines that the notification message can be forwarded to the receiving device 200 with which a communication connection is established according to the message management policy. Then, the source device 100 may send the notification message to the receiving device 200. After receiving the notification message, the receiving device 200 determines that the display scene of the current display screen 194 can display the notification message according to the message management policy, and then the notification message can be displayed through Display 194 displays the notification message.

Subsequently, in response to the user's operation on the notification message, the receiving device 200 may send a notification message triggering indication to the source device 100 . The source device 100 starts the corresponding application in the background according to the notification message triggering instruction, determines the application interface display content corresponding to the notification message, and sends the application interface display content to the receiving device 200 . Therefore, the receiving device 200 can display the application interface corresponding to the notification message, thereby meeting the user's need to view the specific content of the notification message on the receiving device 200 side.

Camera 193 is used to capture still images or video. The object passes through the lens to produce an optical image that is projected onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the ISP to convert it into a digital image signal. ISP outputs digital image signals to DSP for processing. DSP converts digital image signals into standard RGB, YUV and other format image signals. In some embodiments, the source device 100 or the sink device 200 may include 1 or N cameras 193, where N is a positive integer greater than 1.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the source device 100 or the sink device 200 . The external memory card communicates with the processor 110 through the external memory interface 120 to implement the data storage function. Such as saving music, videos, etc. files in external memory card.

Internal memory 121 may be used to store computer executable program code, which includes instructions. The internal memory 121 may include a program storage area and a data storage area. Among them, the stored program area can store an operating system, at least one application program required for a function (such as a sound playback function, an image playback function, etc.). The storage data area may store data created during use of the source device 100 or the sink device 200 (such as audio data, phone book, etc.). In addition, the 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. The processor 110 executes various functional applications and data processing of the source device 100 or the sink device 200 by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.

The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. Audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be provided in the processor 110 , or some functional modules of the audio module 170 may be provided in the processor 110 . The source device 100 or the sink device 200 can play music, record, etc. through the audio module 170 . The audio module 170 may include a speaker, a receiver, a microphone, a headphone interface, and an application processor to implement audio functions.

The sensor module 180 may include a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.

Touch sensor, also known as "touch device". The touch sensor can be disposed on the display screen 194, and the touch sensor and the display screen 194 form a touch screen, which is also called a "touch screen". Touch sensors are used to detect touches on or near them. The touch sensor can pass the detected touch operation to the application processor to determine the touch event type. Visual output related to the touch operation may be provided through display screen 194 . In other embodiments, the touch sensor may also be disposed on the surface of the source device 100 or the sink device 200 and the display screen 194 The location is different.

The buttons 190 include a power button, a volume button, etc. Key 190 may be a mechanical key. It can also be a touch button. The source device 100 or the sink device 200 may receive key input and generate key signal input related to user settings and function control of the source device 100 or the sink device 200.

The motor 191 can generate vibration prompts. The motor 191 can be used for vibration prompts for incoming calls and can also be used for touch vibration feedback. For example, touch operations for different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. The motor 191 can also respond to different vibration feedback effects for touch operations in different areas of the display screen 194 . Different application scenarios (such as time reminders, receiving information, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized.

The indicator 192 may be an indicator light, which may be used to indicate charging status, power changes, or may be used to indicate messages, missed calls, notifications, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to or separated from the source device 100 or the sink device 200 by inserting it into the SIM card interface 195 or pulling it out from the SIM card interface 195 . The source device 100 or the sink device 200 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1.

The following takes the source device 100 as the source device and the receiving device 200 as the receiving device as an example to describe the message management method provided by the embodiment of the present application.

In some embodiments, after the source device and the sink device establish a communication connection, the source device can send screen projection content to the sink device to implement screen projection display on the sink device side. Among them, screen casting includes, for example, push screen casting and mirror screen casting.

Optionally, after the receiving device establishes a screencasting connection with the receiving device, it can obtain the application list information of the source device, and display the corresponding application icon according to the application list information. Afterwards, the receiving device may send an application launch request to the source device in response to the user's operation on the application icon. In response to the received application startup request, the source device starts the corresponding application in the background and sends the application data to the receiving device. Then the receiving device can display the application interface based on the obtained application data. This enables the application in the source device to be launched through screen projection without affecting the operation of the source device. In this way, even if the receiving device does not install the application of the source device, it can determine that the application is installed on the source device based on the application list information, so that the receiving device can display the application interface for the user to use.

Optionally, the source device receives a notification message during the process of establishing a communication connection with the receiving device, and can forward the notification message to the receiving device for display. Moreover, in response to the user's operation on the notification message on the receiving device, the source device can launch the application corresponding to the notification message and cast the screen to the receiving device for display. In this way, the notification message can be operated on the receiving end device side and the omission of the message can be avoided.

The following is a detailed introduction to the notification message forwarding process in the message management process.

Illustratively, Figure 5 illustrates a notification message forwarding method in the message management process provided by an embodiment of the present application. As shown in Figure 5, the method includes the following steps.

S501. The source device and the receiving device establish a communication connection.

In some embodiments, the source device and the sink device support establishing a communication connection through multiple methods. The communication connection is used to implement screen projection from the source device to the sink device.

For example, the source device and the sink device are connected to the same local area network. After the source device and the sink device discover each other, they can establish a communication connection for screen projection in response to user operations.

For another example, both the source device and the sink device are installed with applications for establishing a screen projection connection (such as a computer manager application, etc.). In response to user operations in the application, the source device and the sink device can establish a screen casting connection.

In some embodiments, the receiving device can obtain the application list information of the application in the source device through the established communication connection, and display the corresponding application icon. Then, in response to the user's operation of starting the application (such as clicking the application icon), the receiving device can request the source device to obtain the application interface data corresponding to the application icon operated by the user, so as to display the application interface in the source device.

For example, as shown in Figure 6, the source device 61 includes a device interconnection module 613, and the sink device 62 includes a device interconnection module 621. Then, the source device 61 and the sink device 62 can establish a communication connection through their respective device interconnection modules. Optionally, the device interconnection module is, for example, the mobile communication module 150 as shown in Figure 4, or the wireless communication module 160.

It should be noted that, as shown in Figure 6, the dotted arrows are used to indicate the notification message forwarding process between modules, and the solid arrows are used to indicate the notification message operation response process between modules.

S502. The source device receives the notification message.

In some embodiments, notification messages include, for example, system notification messages and third-party application notification messages. For example, new SMS notifications received by the source device. For another example, the source device receives New message notifications for the app.

For example, as shown in Figure 6, after the system or application of the source device 61 receives or generates a notification message, it sends the notification message to the notification management module 611, which is used to manage notifications in the source device 61. information.

S503. The source device sends a notification message to the receiving device.

In some embodiments, after the source device receives the notification message, it determines that the source device has established a communication connection with the receiving device, and can forward the received notification message to the receiving device, thereby avoiding the possibility that the user is not paying attention to the source device. resulting in the omission of notification messages.

For example, as shown in FIG. 6 , after the notification management module 611 in the source device 61 determines that the source device 61 has received the notification message, it forwards the notification message to the notification collaboration module 612 . Afterwards, the notification cooperation module 612 sends the notification message to the receiving end device 62 through the device interconnection module 613.

Optionally, the notification collaboration module 612 constructs a new notification message for sending to the receiving device 62 based on the original content of the received notification message according to preset rules. For example, the new notification message includes the original content of the notification message and the name of the source device. In this way, when the receiving device 62 displays the notification message, the user can determine based on the displayed content that the notification message is a notification received by the application in the source device 61 information. Afterwards, the notification coordination module 612 serializes the new notification message and sends it to the receiving device 62 .

It should be noted that serialization processing includes, for example, the process of converting an object to be transmitted (such as a Java object) into a byte sequence. This process is used to ensure the integrity and deliverability of the object when transferring and saving the object.

S504. The receiving device displays a notification message.

In some embodiments, after receiving the notification message, the receiving device displays the notification message in a preset manner. For example, the receiving device displays a pop-up window showing the received notification message.

Optionally, after receiving the notification message forwarded by the source device, the receiving device can also construct a new notification message for display based on the received notification message. For example, the source device forwards a notification message to the receiving device, and the notification message includes the original content of the system or application notification message. Then, the receiving device can construct a new notification message for display based on the original content of the notification message and the device name of the source device to help the user Determine the content and source of notification messages.

For example, as shown in FIG. 6 , the receiving device 62 receives the notification message sent by the source device through the device interconnection module 621 . Afterwards, the device interconnection module 621 sends the received notification message to the notification collaboration module 622. After the notification collaboration module 622 deserializes the serialized notification message, it sends the obtained notification message content to the notification management module 623 , and the notification message is distributed through the notification management module 623 . For example, the notification message management module 623 sends the notification message to the notification display module 624. Thereby, the receiving device 62 displays the obtained notification message through the notification display module 624 .

It should be noted that deserialization processing includes, for example, the process of restoring a byte sequence into an object (such as a Java object). This process is used to reconstruct the object through deserialization based on the object status and description information saved in the byte stream. This enables the transmission of notification messages.

For example, as shown in Figure 7, the mobile phone 100 (source device) and the large screen device 200 (receiving device) establish a communication connection through the above step S501, and the large screen device 200 displays the display content of the application in the mobile phone 100 (such as display Video content in mobile video playback applications). After receiving the notification message, the mobile phone 100 determines that a communication connection that can be used for screen casting has been established with the large screen device 200, and can send the notification message to the large screen device 200 (ie, step S502 and step S503). Afterwards, as shown in FIG. 7 , after receiving the notification message, the large-screen device 200 displays the notification message 71 on the display screen. The notification message 71 includes the original content of the notification message (such as a weather warning message) and the name of the source device (such as a mobile phone). In this way, the display content of the user notification message 71 can determine that the notification message is a notification message sent by the mobile phone.

As shown in FIG. 7 , when the large-screen device 200 displays the content displayed by the mobile phone 100 application, it is not limited to displaying it in the screen projection window. Correspondingly, the notification message can be displayed on the display interface of the large-screen device 200 through various methods such as pop-up windows, so that there will be no problem that the notification message cannot be displayed due to the user closing the screen projection window or minimizing the screen projection window. .

In this way, during the process of multi-screen collaboration, the receiving device can also display the notification messages received by the source device through the multi-screen collaboration connection, thereby avoiding the omission of notification messages caused by the user not paying attention to the source device. Moreover, the user does not need to operate two electronic devices, and can check the notification message of the other electronic device while operating one electronic device, reducing the difficulty of user operation.

In addition, the receiving device adaptively displays notification messages according to the current interface display requirements, so that the display of notification messages is consistent with the display of other messages on the receiving device, ensuring the user's experience.

In some embodiments, since the source device does not need to support the application corresponding to the notification message, the difficulty of application development is also reduced.

In some scenarios, in order to ensure user privacy and security and user screencasting experience, notification message management policies for the source device and the receiving device can be preset. Among them, the notification message management policy of the source device can be used to set the notification message forwarding rules of the source device. The notification message management policy of the receiving device can be used to set the notification message display rules of the receiving device.

The following is a detailed introduction to the notification message management strategies of the source device and the sink device.

In some scenarios, after determining that the source application has received the notification message, the source device can determine whether it is currently in a collaborative business scenario, and determine whether to forward the notification message and the destination receiving end to receive the notification message based on the notification message forwarding rules. equipment.

For example, as shown in FIG. 8 , step S801 may also be included after the above step S502.

S801. The source device determines that forwarding of the notification message is allowed.

In some embodiments, after receiving the notification message, the source device determines that the notification message is allowed to be forwarded according to the notification message forwarding rules, and then forwards the notification message to the receiving device.

Optionally, as shown in Table 1 below, you can configure the notification message forwarding rules of the source device according to the application. For example, notification messages from different applications can be forwarded to the same or different receiving devices and configured with corresponding user permissions. Optionally, the user permissions for notification message forwarding include, for example, that the source device can send the notification message of the application to the receiving device of all users, or can send the notification message of the application to the receiving device of the same user as the source device. The receiving device may not support forwarding notification messages for the app.

Table 1

For example, as shown in Table 1 above, Application 1, Application 2 and Application 3 are installed on the source device. Among them, the notification message forwarding rules configured by application 1 include the ability to forward notification messages to all users of receiving device 1 and receiving device 2 (that is, user permissions are not restricted). Optionally, the receiving end device 1 and the receiving end device 2 are devices of different device types. For example, the receiving device 1 is a public device, and the public device includes electronic devices that are allowed to be used by any user, such as a large-screen device installed in a living room. The receiving device 2 is a privacy device, which includes electronic devices that are allowed to be used by some users, such as laptops with a power-on password set.

For another example, as shown in Table 1 above, Application 1, Application 2 and Application 3 are installed on the source device. Among them, the notification message forwarding rules configured by application 2 include that the notification message can be forwarded to the receiving end device 1 and the receiving end device 2, and the user permissions are the same user. That is to say, after receiving the notification message from Application 2, if the source device determines that the electronic device establishing a multi-screen collaborative connection with the source device includes the receiving device 1 and the receiving device 2, it can further determine that the receiving device 1 and the receiving device 2 Whether the receiving device 2 and the source device are logged into the same account, or whether the receiving device 1 and the receiving device 2 are instructed to confirm the password (such as obtaining user permissions through user operations). The source device can then send the notification message to the sink device configured with user permissions. For example, if App 2 is an SMS application, in order to prevent the notification messages received by App 2 from leaking user privacy, you can set the user permission to forward the notification messages of App 2. If it is determined to forward the notification message to a public device, you need to confirm your login account or password. Confirm to protect user privacy.

Optionally, the login account is, for example, a login account for a smart home system, or a local area network login account, etc. For example, before the equipment in a smart home system is delivered to users for use, installation and maintenance engineers need to configure and debug the equipment. This process is the pre-installation process of smart home equipment. During the pre-installation process, the electronic device logs in to the same account for device configuration and commissioning. Then, during the process of establishing a communication connection between the source device and the sink device, the source device can determine whether the sink device is logged in to the account. For another example, if the source device and the sink device are connected to the same encrypted Wi-Fi local area network, the source device can determine that the sink device and the source device are logged in to the same account.

Optionally, the password confirmation process includes, for example, the source device sending a user authority confirmation instruction to the receiving device, and the receiving device displays prompt information in a pop-up window to prompt the user to confirm the user authority. After receiving the user's confirmation operation, the receiving device can send a user permission confirmation response to the source device, and then the source device can determine that the receiving device has the user permission to display the notification message, that is, the password confirmation is completed. Alternatively, the source device sends a user permission confirmation instruction to the receiving device, and the receiving device determines that the receiving device has obtained user authorization (for example, the receiving device determines that the correct password, graphic gesture, After fingerprinting, etc.), a user permission confirmation response can be sent to the source device, and then the source device can determine that the receiving device has the user permission to receive the notification message, that is, the password confirmation is completed.

For another example, as shown in Table 1 above, Application 1, Application 2 and Application 3 are installed on the source device. Among them, the notification message forwarding rules configured by application 3 include that the receiving device 1 and the receiving device 2 do not support the forwarding of notification messages. Then, after the source device determines that the notification message is a notification message received by application 3, and determines that the receiving device that establishes the multi-screen collaborative connection includes receiving device 1 and/or receiving device 2, it may determine not to send the notification message to receiving device 1. and/or the receiving end device 2 forwards the notification message.

In some embodiments, the notification message forwarding rules of the source device may be preset default rules. For example, the source device can obtain the corresponding notification message forwarding rules before the user uses it. For example, the source device manufacturer configures the notification message forwarding rules in the source device before it is delivered to users for use.

Optionally, the source device detects the user's editing operation on the notification message forwarding rules, and can modify the corresponding notification message forwarding rules accordingly. For example, on the source device setting interface or application setting interface, the source device can receive the user's editing operation on the notification message forwarding rules, so that the notification message forwarding rules can better meet the user's usage needs.

In some embodiments, the notification message forwarding rules shown in Table 1 above may also include, for example, a receiving device that displays or starts the application corresponding to the notification message with a high priority, and a receiving device that does not display or start the application corresponding to the notification message. has low priority.

For example, after receiving the notification message from Application 1, the source device determines that it can send the notification message to the receiving device 1 and the receiving device 2 with which it has established a multi-screen collaborative connection based on the notification message forwarding rules shown in Table 1 above. Furthermore, the source device determines that the sink device 1 is currently displaying the application 1 . Then, the source device can determine that the priority of the receiving device 1 is higher, and can send the notification message of the application 1 to the receiving device 1 .

As a possible implementation method, the source device and the sink device establish a multi-screen collaborative connection, and the sink device can start the application in the source device according to the application list of the source device. Therefore, the source device can determine the application launched and displayed by the sink device.

For example, in the scenario shown in Figure 9, the source device is a mobile phone and the receiving device is a car machine. The vehicle where the car machine is located is equipped with two cockpit screens (such as cockpit screen 1 and cockpit screen 2). The mobile phone and the cockpit screen Screen 1 and cockpit screen 2 establish multi-screen collaborative connections respectively. Among them, cockpit screen 1 displays the map application in the mobile phone, and cockpit screen 2 displays the music application in the mobile phone.

For example, the mobile phone receives The new message notification of the application is determined according to the notification message forwarding rules. The receiving device corresponding to the application may include cockpit screen 1 and cockpit screen 2, and the user permissions are the same. Moreover, during the process of establishing communication connections between the mobile phone and the cockpit screen 1 and the cockpit screen 2, it has been determined that the cockpit screen 2 and the mobile phone are logged into the same account. Then, the mobile phone can send the message to cockpit screen 2 App notification messages. As shown in FIG. 9 , during the process of displaying the interface 903 , the cockpit screen 2 displays a new message notification 92 according to the received notification message.

For another example, the mobile phone receives a notification message from a map application. According to the notification message forwarding rules, it is determined that the receiving device corresponding to the map application can include cockpit screen 1 and cockpit screen 2, and the user permissions are all users. In addition, the mobile phone determines that the cockpit screen 1 is displaying the map application, and can determine that the cockpit screen 1 has a higher priority for displaying the notification message. Then, the mobile phone can send the notification message of the map application to the cockpit screen 1. As shown in FIG. 9 , during the process of displaying the interface 901 , the cockpit screen 1 displays the navigation notification message 91 according to the received notification message.

In this way, the source device can protect user privacy based on the notification message forwarding rules, thereby avoiding leakage of user privacy and improving user experience.

In some scenarios, after receiving the notification message sent by the source device, the receiving device can determine whether to display the notification message according to the notification message display rules.

For example, as shown in FIG. 8 , step S802 may also be included after the above step S503.

S802. The receiving device determines that display of the notification message is allowed.

In some embodiments, after receiving the notification message, the receiving device determines that the notification message is allowed to be displayed according to the notification message display rules, and then displays the notification message through the notification message display module.

Optionally, as shown in Table 2 below, the notification message display rules of the receiving device can be configured according to the application. For example, the receiving device supports displaying notification messages of a certain application in all display scenarios, supports displaying notification messages of a certain application in some display scenarios, does not support displaying notification messages of a certain application, and is configured with corresponding user permissions.

Table 2

Optionally, the display scenes include, for example, video playback scenes, game scenes, call scenes, etc. Optionally, notification messages of different applications have different levels of importance, and the display scenario of the notification messages can be determined based on the level of importance.

For example, as shown in Table 2 above, Application 1, Application 2 and Application 3 are installed on the source device. Among them, the notification message of application 1 is of high importance (such as Application notification messages), to avoid missing notification messages, you can configure the notification message display rules of the receiving device to include notification messages from Application 1 in all display scenarios.

For another example, if the notification message of Application 2 is of medium importance, the notification message display rules of the receiving device can be configured to include displaying the notification message of Application 2 in some display scenarios. For example, the receiving device supports displaying notification messages of Application 2 in non-video playback scenarios. This prevents the display of notification messages from affecting the user's video viewing experience.

For another example, if the notification message of Application 3 is of low importance, the notification message display rules of the receiving device can be configured to include disallowing the display of the notification message of Application 3 in all display scenarios.

Optionally, the user permissions for displaying notification messages on the receiving device side include, for example, the receiving device can display the notification messages of the application sent by the source device corresponding to all users, or display the notification messages sent by the source device of the same user as the receiving device. or does not support displaying notification messages for this app.

It should be noted that, for the specific content of the method for the receiving device to determine user permissions, please refer to the relevant content of the above-mentioned method for the source device to determine user permissions, and will not be described again here.

For example, after the receiving device determines that the source device is logged in with the same account or the password is confirmed, it can be determined that the source device and the receiving device correspond to the same user. As shown in Table 2 above, the receiving device can display the notification message of Application 1 sent by the source device of the same or different users in all scenarios; the receiving device can display the notification message in some scenarios. Display notification messages of application 2 sent by the source device of the same user; the receiving device does not support displaying notification messages of application 3 sent by the source device in all scenarios.

For example, in the scenario shown in Figure 7, after receiving the notification message of the weather application sent by the mobile phone 100, the large-screen device 200 determines that the large-screen device 200 supports displaying the notification of the weather application in all display scenarios according to the notification message display rules. messages, and the large-screen device 200 supports displaying notification messages of the weather application sent by all users' source devices. Then, the large-screen device 200 determines that the notification message is allowed to be displayed, and may display the notification message 71 on the display screen.

For another example, in the scenario shown in Figure 9, after the cockpit screen 1 receives the notification message of the map application sent by the mobile phone, it determines that the cockpit screen 1 supports display in the navigation scene (such as displaying the map application interface) according to the notification message display rules. Notification messages of the map application, and the cockpit screen 1 supports display of notification messages of the navigation application sent by all users' source devices. Then, after determining that the current scene is a navigation scene, the cockpit screen 1 determines that the notification message is allowed to be displayed, and can display the navigation notification message 91 on the display screen.

As another example, in the scene shown in Figure 9, the cockpit screen 2 receives the After applying the notification message, make sure that the cockpit screen 2 supports display in all display scenarios according to the notification message display rules. Application notification messages, and the cockpit screen 2 supports displaying the notification messages sent by the user's source device. Application notification message. Then, after determining that the mobile phone and the cockpit screen 2 correspond to the same user, the cockpit screen 2 determines that the notification message is allowed to be displayed, and can display the new message notification 92 on the display screen.

In this way, the receiving device can protect user privacy based on the notification message display rules, thereby avoiding user privacy leakage and improving user experience.

In some embodiments, the receiving device can obtain notification message display rules or user permissions in new scenarios in real time according to scene switching during use.

In some embodiments, the notification message display rules of the receiving device may be preset default rules, or rules determined in response to the user's editing operation on the default rules, or rules determined for the user.

It should be noted that the notification message display rules are default rules or user-edited rules. Please refer to the relevant content of the above notification message forwarding rules, which will not be described again here.

In some embodiments, in different multi-screen collaboration scenarios, the electronic device can serve as a source device or a sink device. For example, in the process of establishing a multi-screen collaborative connection between electronic device 1 and electronic device 2, electronic device 1 serves as the source device and electronic device 2 serves as the receiving device. For another example, in the process of establishing a multi-screen collaborative connection between electronic device 1 and electronic device 3, electronic device 3 serves as the source device and electronic device 1 serves as the receiving device.

Then, as a possible implementation, the notification message management policy that can be configured for the electronic device that supports both the source device and the sink device includes notification message forwarding rules and notification message display rules, and can be configured for the electronic device that only supports the source device. The configured notification message management policy includes notification message forwarding rules, and the notification message management policy configured for an electronic device that only supports an electronic device as a receiving end device includes notification message display rules.

In this way, in different screen projection scenarios, the electronic device can obtain the corresponding message management strategy according to its role (such as a source device or a receiving device) to realize the forwarding and display of notification messages.

In some embodiments, message management policies may be stored in the electronic device. When the electronic device determines that the notification message needs to be forwarded or displayed, the electronic device can obtain the locally stored notification message management policy.

In other embodiments, the server supports managing message management policies of different electronic devices. When the electronic device determines that it needs to use the message management policy, it may request the server to download the message management policy.

For example, the server manages notification message management policies according to accounts, and the same account corresponds to one or several sets of notification message management policies. In the case where the same account corresponds to multiple sets of notification message management policies, each set of message management policies corresponds to the identity (ID) of a different electronic device. If different electronic devices have corresponding notification message management policies preset before leaving the factory, after the user creates an account, he can log in to the account on multiple electronic devices. Then, one account can correspond to multiple sets of notification message management policies for multiple electronic devices.

Subsequently, after receiving the notification message management policy request sent by the electronic device, the server can send the notification message management policy corresponding to the account to the electronic device according to the account logged in by the electronic device and the electronic device ID. For example, the notification message management policy carries account information and electronic device ID. Then, the server can determine the corresponding account based on the account information in the received notification message management policy request, and determine the notification message management policy under the account. Afterwards, the server obtains the notification message management policy corresponding to the electronic device under the account based on the electronic device ID. Optionally, the server synchronizes the notification message management policy with the electronic device according to the preset rules. For example, after detecting the user's editing operation on the notification message management policy, the electronic device can send a notification message management policy update instruction to the server. The notification message management policy update instruction carries the edited notification message management policy, the electronic device Account information, electronic device ID. Correspondingly, after receiving the notification message management policy update instruction sent by the electronic device, the server synchronously updates the corresponding notification message management policy based on the electronic device account information and electronic device ID.

In this way, the server manages the notification message management policy in an orderly manner according to the account. Moreover, according to the electronic device functions and user needs, different electronic devices correspond to different notification message management strategies, so that the electronic device can meet the user's personalized usage needs on the basis of forwarding and displaying notification messages.

Optionally, a default notification message management policy is also preset in the server, and different accounts can correspond to the same or different default notification message management policies. Then, after the server obtains the notification message management policy request sent by the electronic device, it can directly deliver to it the preset default notification message management policy corresponding to the account information based on the account information. That is, the same account can correspond to a set of default notification message management policies.

In this way, different electronic devices with the same account implement the forwarding and display of notification messages according to the same default notification message management policy. Different electronic devices of the same user can provide users with the same experience of forwarding and displaying notification messages, thereby improving the user experience. usage experience.

In some embodiments, the server sends the latest notification message management policy to the electronic device according to a preset cycle. In this way, when the electronic device determines that it needs to forward or display the notification message, it can forward or display the notification message according to the latest notification message management policy sent by the server. It is no longer necessary to separately request the server to download the notification message management policy, thereby reducing the forwarding or display delay of the notification message.

For example, as shown in Figure 10, the source device 1, the source device 2, the sink device 1, and the sink device 2 can implement a many-to-many multi-screen collaborative connection. Among them, the source device side (such as source device 1 and source device 2) can implement notification message forwarding control according to the notification message forwarding rules, and the receiving device side (such as receiving device 1 and receiving device 2) can implement notification message forwarding control according to the notification message forwarding rules. Message display rules implement display control of notification messages. The source device and the receiving device can obtain the notification message management policy locally and/or from the server, thereby forwarding and displaying the notification message.

In some embodiments, notification message management policies may include notification message forwarding rules and/or notification message display rules.

For example, the notification message management policy may include notification message forwarding rules and notification message display rules. So, During the multi-screen collaboration process, the source device needs to determine whether to forward the notification message according to the notification message forwarding rules, and the receiving device needs to determine whether to display the received notification message according to the notification message display rules. For example, in some scenarios, after the source device sends a notification message to the receiving device according to the notification message forwarding rules, the receiving device determines not to display the received notification message according to the notification message display rules.

In this way, through the management and control of notification messages from the electronic devices at both ends, the forwarding and display of notification messages can better meet the user's requirements.

For another example, the notification message management policy may include notification message forwarding rules. Then, during the multi-screen collaboration process, the source device only needs to determine whether to forward the notification message according to the notification message forwarding rules. After receiving the notification message, the receiving device can directly display the notification message.

For another example, the notification message management policy may include notification message display rules. Then, during the multi-screen collaboration process, after the application in the source device detects the notification message, it can directly send the notification message to the receiving device. After receiving the notification message, the receiving device determines whether to display the notification message according to the notification message display rules.

In this way, the management and control of notification messages from single-ended electronic devices not only meets the requirements for notification message forwarding and display control, but also reduces the power consumption of some electronic devices. For example, some electronic devices have weak processing capabilities. Such electronic devices may not confirm whether notification messages are forwarded or displayed, but directly forward or display received notification messages.

The following is a detailed introduction to the process of displaying the specific content of the notification message on the receiving device.

In some scenarios, during the process of displaying the notification message, the receiving device can also respond to the user's operation and display the interface corresponding to the notification message, thereby meeting the user's need to view the specific content of the notification message.

Illustratively, Figure 11 illustrates a notification message opening method in the message management process provided by an embodiment of the present application. As shown in Figure 11, the method includes the following steps.

S1101. The receiving device detects the user's operation on the notification message.

In some embodiments, during the process of displaying the notification message, the receiving device detects any operation such as the user's touch operation on the notification message, the operation of opening the notification message through the remote control, the operation of opening the notification message by voice, etc., It can be determined that the user instructed to open the notification message.

Among them, opening the notification message is used to indicate that the application interface corresponding to the notification message is displayed on the receiving device side. For example, the notification message is a new message notification of the SMS application, and opening the notification message is used to indicate that the SMS application interface including the specific content of the new message in the SMS application is displayed on the receiving end device.

S1102. The receiving device sends a notification message triggering instruction to the source device.

In some embodiments, in response to the user's operation on the notification message, the receiving device sends a notification message triggering indication to the source device to instruct the source device to obtain the interface content corresponding to the notification message. Correspondingly, the source device receives the notification message triggering indication.

Optionally, the notification message triggering indication includes serialized user operation data. Then, after receiving the notification message trigger indication, the source device can determine the application interface display data acquisition event corresponding to the user operation data through a deserialization operation.

For example, as shown in FIG. 6 , the notification message display module 624 in the receiving device 62 detects the user's touch operation on the notification message during the process of displaying the notification message, and can send the notification message to the source device 61 through the device interconnection module 621 Send a notification message to trigger the indication. Correspondingly, the source device 61 obtains the notification message triggering indication sent by the receiving device 62 through the device interconnection module 613 .

In other embodiments, the notification message management policy may also include notification message operation rules. The receiving device Whether the user is allowed to operate the displayed notification message can be determined based on the local notification message operation rules.

For example, in some scenarios, the receiving device does not allow users to operate notification messages of some applications. That is, in these cases, the receiving device is only used to display the obtained notification messages. Optionally, in these cases, if the receiving device detects the user's operation on the notification message, a pop-up window can be displayed to remind the user that the notification message cannot be opened in the current scene. Further, in these cases, the receiving end device may no longer perform the following steps S1103 to S1107.

It should be noted that for the specific content of the notification message operation rules, please refer to the relevant content of the above notification message display rules. For example, notification message display rules include notification message operation rules, or notification message operation rules and notification message display rules are the same.

S1103. The source device determines the startup status of the application corresponding to the notification message according to the notification message triggering instruction.

In some embodiments, the notification message triggering indication carries the identification of the application corresponding to the notification message. After receiving the notification message triggering indication, the source device can determine the application corresponding to the notification message based on the identifier, and then determine whether the application is started (that is, determine the startup status of the application). Optionally, if the application corresponding to the notification message has not been started, the following step S1104 may be performed, and then the following step S1105 may be performed. If the application corresponding to the notification message has been started, the following step S1105 can be directly performed.

In some embodiments, after receiving the notification message triggering indication, the source device may first determine whether the source device allows the application interface content of the notification message to be displayed on the receiving device. After the source device determines the content of the application interface that allows the notification message to be displayed on the receiving device, it then determines the startup status of the application corresponding to the notification message.

Exemplarily, as shown in Figure 6, the device interconnection module 613 in the source device 61 sends the received notification message trigger indication to the notification display module 614, and the notification message display module 614 processes the notification message through a deserialization operation. Trigger instructions to obtain data acquisition events displayed on the application interface. In addition, if the notification display module 614 determines that the current scenario is a multi-screen collaboration scenario, the application interface display data acquisition event may be sent to the collaboration configuration module 615 . Afterwards, the collaborative configuration module 615 determines the interface display data acquisition strategy for the application corresponding to the notification message based on the current scene and device status. Afterwards, the collaborative configuration module 615 obtains the corresponding application interface display data according to the interface display data acquisition strategy.

For example, the notification message management policy may also include notification message operation rules. The source device may determine whether the source device supports opening the notification message on the receiving device side according to the local notification message operation rules.

Optionally, the notification message operation rules include interface display data acquisition strategies in different scenarios and device states, such as allowing acquisition of display data (i.e., supporting opening of the notification message on the receiving device side) or not allowing acquisition of display data (i.e., not allowing the acquisition of display data). Support opening the notification message on the receiving device side).

Optionally, the source device and/or the receiving device are configured with corresponding notification message operation policies. The notification message operation rules on the source device side and the notification message operation rules on the receiving device side may be the same or different.

It should be noted that for the specific content of the notification message operation rules of the source device, please refer to the relevant content of the above notification message forwarding rules. For example, the notification message forwarding rules include the notification message operation rules, or the notification message operation rules are the same as the notification message forwarding rules. .

S1104. If the application corresponding to the notification message has not been started, the source device starts the application in the background.

In some embodiments, the source device determines that the application corresponding to the notification message has not been started, and can start the application in the background, thereby obtaining the application interface display data corresponding to the notification message.

In this way, the source device starts the application corresponding to the notification message through the background, which will not affect the operation of the source device. Thereby improving the user experience. For example, if the source device is displaying other applications in the foreground, starting the application corresponding to the notification message will not affect the display of the foreground application on the source device. For another example, if the source device is in the locked screen state, the user does not need to perform operations such as unlocking the source device. The source device can automatically launch the application corresponding to the notification message in the locked screen state.

S1105. The source device determines the display data of the application corresponding to the notification message.

In some embodiments, after the source device determines that the application corresponding to the notification message has been started (including starting in the background in response to the notification message triggering indication, or starting before receiving the notification message triggering indication), the source device may request the application to obtain the notification message. Corresponding display data.

For example, as shown in Figure 6, the collaborative configuration module 615 in the source device 61 determines that the interface display data acquisition policy includes allowing acquisition of display data according to the notification message operation rules. Then, the collaborative configuration module 615 determines the startup status of the application corresponding to the notification message through the application management module 616 (ie, the above step S1103). If it is not started, the application can be started (ie, step S1104 above). After that, the collaborative configuration module 615 obtains the display content of the application corresponding to the notification message through the application management module 616, and determines the display data of the display content on the virtual display screen (dispaly) through the window management module 617, that is, determines the application after the notification message is opened. The interface displays content (ie, step S1105 above).

Optionally, in a multi-screen collaboration scenario, the collaboration configuration module 615 is not only used to manage the display of the application interface corresponding to the notification message, but also can be used to manage the audio of the application interface corresponding to the notification message (such as sound effects during the interface display process, etc.) . Optionally, the collaborative configuration module 615 can determine the audio data of the application interface corresponding to the notification message through the audio management module (not shown in Figure 6).

S1106. The source device sends display data to the receiving device.

In some embodiments, after determining the display data, the source device may send the display data to the sink device. Correspondingly, the receiving device receives the display data sent by the source device.

Optionally, the source device can also send determined audio data to the sink device.

For example, as shown in Figure 6, after determining the display data, the collaboration configuration module 615 in the source device 61 starts the multi-screen collaboration service through the multi-screen collaboration module 618. Afterwards, the multi-screen cooperation module 618 sends the display data to the receiving end device 62 through the device interconnection module 613.

Optionally, after determining the display data, the window management module 617 can also directly start the multi-screen collaboration service through the multi-screen collaboration module 618, and send the display data to the multi-screen collaboration module 618 to achieve sending the display data to the receiving end device. 62, thereby completing the cross-device transmission of display data. In other words, the module division and the interaction process between modules in Figure 6 do not constitute a restriction on the notification message interaction between the source device and the receiving device. The source device and the receiving device may include more or more With a small number of modules, the interaction process between each module can also execute the interaction of notification messages according to the developer's configuration.

S1107. The receiving device displays the application interface according to the display data.

In some embodiments, after receiving the display data, the receiving device can display the corresponding application interface according to the display data. Optionally, during the process of displaying the application interface, the receiving device can also play corresponding audio based on the obtained audio data.

For example, as shown in FIG. 6 , the device interconnection module 621 in the receiving device 62 sends the received display data sent by the source device 61 to the multi-screen collaboration module 625 . Afterwards, the multi-screen collaboration module 625 displays the display data through the window management module 626, thereby displaying the application interface corresponding to the notification message.

In this way, the user can open the notification message on the receiving device without operating the source device, thereby reducing the user's operational difficulty and improving the user experience.

In addition, the source device directly determines the display data, and the receiving device does not need to install the application corresponding to the notification message. It can directly display the application interface corresponding to the notification message based on the display data, thereby reducing the difficulty of application development.

The following is a detailed introduction to the operation process of notification messages based on specific scenarios.

For example, in the scenario shown in FIG. 7 , the large-screen device 200 establishes a multi-screen collaborative connection with the mobile phone 100 , and the large-screen device 200 displays the notification message 71 sent by the mobile phone 100 . The large-screen device 200 detects the user's touch operation on the notification message 71 and can determine that the user instructed to open the notification message 71 . Then the large-screen device 200 sends a triggering instruction of the notification message 71 to the mobile phone. Correspondingly, the mobile phone 100 determines that the application corresponding to the notification message 71 is a weather application according to the triggering instruction of the notification message 71, and determines that the weather application has not been started. The mobile phone 100 starts the weather application in the background and obtains the weather application interface display data corresponding to the notification message 71 . Afterwards, the mobile phone 100 sends the display data to the large screen device 200 . The large-screen device 200 displays an interface shown as reference numeral 72 according to the obtained display data, which is a weather application interface corresponding to the notification message 71 . This meets the user's need to view weather warnings on the large screen device 200 .

Optionally, before sending the triggering instruction of the notification message 71 to the mobile phone, the large-screen device 200 may determine that the notification message allows the user to operate according to the notification message operation rules. Afterwards, the triggering instruction of the notification message 71 is sent to the mobile phone. Alternatively, the large screen device 200 determines that the notification message does not allow the user to operate according to the notification message operation rules, and may display a pop-up message to remind the user that the notification message 71 is not operable.

As another example, in the scenario shown in Figure 9, the mobile phone establishes multi-screen collaborative connections with cockpit screen 1 and cockpit screen 2 respectively. After detecting the user's touch operation on the navigation notification message 91 on the interface 901, the cockpit screen 1 determines the notification message that allows the user to operate the map application in the current scene according to the notification message operation rules. Then, the cockpit screen 1 sends the triggering instruction of the navigation notification message 91 to the mobile phone, and the corresponding mobile phone determines the startup state of the map application according to the triggering instruction of the navigation notification message 91 . If it is not started, the phone can start the map application in the background. Afterwards, the mobile phone sends the map application interface display data corresponding to the determined navigation notification message 91 to the cockpit screen 1, and the cockpit screen 1 can display the interface 902 based on the display data. On the interface 902, the user can view the specific navigation notification message content.

As another example, in the scenario shown in Figure 9, the mobile phone establishes multi-screen collaborative connections with cockpit screen 1 and cockpit screen 2 respectively. After the cockpit screen 2 detects the user's touch operation on the new message notification 92 on the interface 903, it determines that the user is allowed to operate the corresponding button of the new message notification 92 in the current scene according to the notification message operation rules. Application notification message. Then, the cockpit screen 2 sends the trigger instruction of the new message notification 92 to the mobile phone, and the corresponding mobile phone determines that the mobile phone is allowed to be displayed on the cockpit screen 2 according to the trigger instruction of the new message notification 92 and the local notification message operation rules. application interface. So, the phone is OK The startup status of the application. If it is not started, the phone can start it in the background. application. After that, the mobile phone will notify the corresponding 92 of the determined new message. The application interface display data is sent to the cockpit screen 2, and the cockpit screen 2 can display the interface 904 based on the display data. On interface 904, the user can determine The specific content of new messages received by the application.

In this way, in different multi-screen collaboration scenarios, the notification message can be displayed on the receiving device and the user's operation on the notification message can be received, thereby meeting the user's usage needs and reducing the user's operation difficulty.

The message management method provided by the embodiment of the present application is described in detail above with reference to Figures 5-11. The electronic device provided by the embodiment of the present application will be described in detail below with reference to FIG. 12 and FIG. 13 .

In one possible design, FIG. 12 is a schematic structural diagram of a source device provided by an embodiment of the present application. As shown in the picture As shown in 12, the source device 1200 may include: a transceiver unit 1201 and a processing unit 1202. The source device 1200 may be used to implement the functions of the source device involved in the above method embodiments.

Optionally, the transceiver unit 1201 is used to support the source device 1200 to perform S501, S502 and S503 in Figure 5; and/or to support the source device 1200 to perform S1102 and S1106 in Figure 11.

Optionally, the processing unit 1202 is used to support the source device 1200 to perform S801 in Figure 8; and/or to support the source device 1200 to perform S1103, S1104 and S1105 in Figure 11.

The transceiver unit may include a receiving unit and a transmitting unit, may be implemented by a transceiver or a transceiver-related circuit component, and may be a transceiver or a transceiver module. The operation and/or function of each unit in the source device 1200 is to implement the corresponding process of the message management method in the above method embodiment. All relevant content of each step involved in the above method embodiment can be quoted to the corresponding functional unit. Function description, for the sake of brevity, will not be repeated here.

Optionally, the source device 1200 shown in Figure 12 may also include a storage unit (not shown in Figure 12), in which programs or instructions are stored. When the transceiver unit 1201 and the processing unit 1202 execute the program or instruction, the source device 1200 shown in FIG. 12 can execute the message management method in the above method embodiment.

For the technical effects of the source device 1200 shown in Figure 12, reference can be made to the technical effects of the message management method in the above method embodiment, which will not be described again here.

In addition to being in the form of the source device 1200, the technical solution provided by this application can also be a functional unit or chip in the source device, or a device used in conjunction with the source device.

In a possible design, FIG. 13 is a schematic structural diagram of a receiving end device provided by an embodiment of the present application. As shown in Figure 13, the receiving end device 1300 may include: a transceiver unit 1301, a processing unit 1302, and a display unit 1303. The receiving end device 1300 may be used to implement the functions of the receiving end device involved in the above method embodiments.

Optionally, the transceiver unit 1301 is used to support the receiving end device 1300 to perform S501 and S503 in Figure 5; and/or to support the receiving end device 1300 to perform S1101, S1102 and S1106 in Figure 11.

Optionally, the processing unit 1302 is configured to support the receiving end device 1300 in executing S802 in Figure 8 .

Optionally, the display unit 1303 is used to support the receiving end device 1300 to perform S504 in Figure 5; and/or to support the receiving end device 1300 to perform S1107 in Figure 11.

The transceiver unit may include a receiving unit and a transmitting unit, may be implemented by a transceiver or a transceiver-related circuit component, and may be a transceiver or a transceiver module. The operation and/or function of each unit in the receiving device 1300 is to implement the corresponding process of the message management method in the above method embodiment. All relevant content of each step involved in the above method embodiment can be quoted from the corresponding functional unit. Function description, for the sake of brevity, will not be repeated here.

Optionally, the receiving device 1300 shown in Figure 13 may also include a storage unit (not shown in Figure 13), in which programs or instructions are stored. When the transceiver unit 1301, the processing unit 1302, and the display unit 1303 execute the program or instruction, the receiving device 1300 shown in FIG. 13 can execute the message management method in the above method embodiment.

For the technical effects of the receiving device 1300 shown in Figure 13, reference can be made to the technical effects of the message management method in the above method embodiment, which will not be described again here.

In addition to being in the form of the receiving end device 1300, the technical solution provided by this application can also be a functional unit or chip in the receiving end device, or a device used in conjunction with the receiving end device.

Embodiments of the present application also provide a chip system, including: a processor, the processor is coupled to a memory, and the memory is used to store programs or instructions. When the program or instructions are executed by the processor, the chip system implements any of the above methods. method in the example.

Optionally, there may be one or more processors in the chip system. The processor can be implemented in hardware or software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like. When implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in memory.

Optionally, there may be one or more memories in the chip system. The memory may be integrated with the processor or may be provided separately from the processor, which is not limited by the embodiments of the present application. For example, the memory may be a non-transient processor, such as a read-only memory ROM, which may be integrated with the processor on the same chip, or may be separately provided on different chips. The embodiments of this application vary on the type of memory, and The arrangement of the memory and processor is not specifically limited.

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

It should be understood that each step in the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software. The method steps disclosed in conjunction with the embodiments of this application can be directly implemented by a hardware processor, or executed by a combination of hardware and software modules in the processor.

Embodiments of the present application also provide a computer-readable storage medium. A computer program is stored in the computer-readable storage medium. When the computer program is run on a computer, it causes the computer to perform the above related steps to implement the above embodiments. message management method.

An embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, it causes the computer to perform the above related steps to implement the message management method in the above embodiment.

In addition, the embodiment of the present application also provides a device. The device may specifically be a component or module, and the device may include one or more connected processors and memories. Among them, memory is used to store computer programs. When the computer program is executed by one or more processors, the device is caused to execute the message management method in each of the above method embodiments.

Among them, the devices, computer-readable storage media, computer program products or chips provided by the embodiments of the present application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects it can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be described again here.

The steps of the methods or algorithms described in connection with the disclosure of the embodiments of this application can be implemented in hardware or by a processor executing software instructions. Software instructions can be composed of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read only memory (ROM), erasable programmable read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM), register, hard disk, removable hard disk, compact disc (CD-ROM) or any other form of storage well known in the art storage medium. An exemplary storage medium is coupled to the processor such that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and storage medium may be located in an application specific integrated circuit (AP device application specific integrated circuit, ASIC).

Through the above description of the embodiments, those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the division of the above functional modules is used as an example. In practical applications, the above function allocation can be completed by different functional modules according to needs; that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. For the specific working processes of the systems, devices and units described above, reference can be made to the corresponding processes in the foregoing method embodiments, which will not be described again here.

In the several embodiments provided in this application, it should be understood that the disclosed method can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of modules or units is only a logical function division, and there may be other division methods in actual implementation; for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not implement. In addition, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, indirect coupling or communication connection of modules or units, and may be in electrical, mechanical or other forms.

In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated units can be implemented in the form of hardware or software functional units.

Computer-readable storage media includes but is not limited to any of the following: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, etc. Various media that can store program code.

The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application shall be covered by the protection scope of the present application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims (26)

1. A message management system, characterized in that the system includes a first device and a second device;

   The first device is configured to receive a first notification message from a first application;

   The first device is further configured to send a second notification message to the second device when it is determined that sending a notification message to the second device is allowed, where the second notification message is the same as the first notification message. The same, or the message content of the second notification message is associated with the message content of the first notification message;

   The second device is used to receive the second notification message;

   The second device is also configured to display the second notification message.
2. The system according to claim 1, characterized in that:

   The first device is specifically configured to send the second notification message to the second device when it is determined that the first application allows sending a notification message to the second device.
3. The system according to claim 1 or 2, characterized in that,

   The second device is specifically configured to display the second notification message when it is determined that display of the notification message of the first application is allowed.
4. The system according to any one of claims 1-3, characterized in that,

   The second device is specifically configured to display the second notification message when it is determined that the second device is in a scene that allows display of the notification message of the first application.
5. The system according to any one of claims 1-4, characterized in that,

   The first device is further configured to send a second notification message to the second device when it is determined that sending a notification message to the second device is allowed, including:

   The first device, after determining that the first device and the second device correspond to the same account; or, after determining that the second device has obtained user authorization, sends a second message to the second device. notification message.
6. The system according to any one of claims 1-5, characterized in that the system further includes a third device;

   The first device is also configured to receive a third notification message from the second application;

   The first device is further configured to determine that the third device displays the notification message of the second application when it is determined that sending a notification message of the second application to the second device and the third device is allowed. After entering the interface, send a fourth notification message corresponding to the third notification message to the third device; the fourth notification message is the same as the third notification message, or the message content of the fourth notification message is the same as the third notification message. The message content of the third notification message is related.
7. The system according to any one of claims 1-6, characterized in that the system further includes a fourth device;

   The first device is further configured to not send the second notification message corresponding to the first notification message to the fourth device when it is determined that the notification message is not allowed to be sent to the fourth device; wherein , the first application in the first device is not allowed to send notification messages to the fourth device, and/or the fourth device and the first device correspond to different accounts, and/or the The first device does not have user authorization to send notification messages to the fourth device.
8. The system according to claims 1-7, characterized in that,

   The second device is also configured to detect the user's first operation on the second notification message;

   The second device is further configured to send a notification message triggering indication to the first device when it is determined that operation of the second notification message is allowed;

   The first device is also configured to receive the notification message triggering indication;

   The first device is further configured to send the display data of the first application corresponding to the second notification message to the second device according to the notification message triggering instruction; the display data is the first application Display data determined by whether the application is running in the foreground or in the background;

   The second device is also used to receive the display data;

   The second device is further configured to display the interface of the first application corresponding to the second notification message according to the display data.
9. A message management method, characterized in that the method includes:

   The first device receives a first notification message from the first application;

   When the first device determines that sending a notification message to the second device is allowed, the first device sends a second notification message to the second device. The second notification message is the same as the first notification message, or the second notification message is the same as the first notification message. The message content of the second notification message is associated with the message content of the first notification message, and the second notification message is used to instruct the second device to display the second notification message.
10. The method according to claim 9, characterized in that, when the first device determines that sending a notification message to the second device is allowed, sending a second notification message to the second device includes:

    If the first device determines that the first application allows sending a notification message to the second device, the first device sends the second notification message to the second device.
11. The method according to claim 9 or 10, characterized in that, when the first device determines that sending a notification message to the second device is allowed, sending a second notification message to the second device includes:

    The first device determines that the first device and the second device correspond to the same account; or, when it determines that the second device has obtained user authorization, sends a second notification to the second device information.
12. The method according to any one of claims 9-11, characterized in that the method further includes:

    The first device receives a third notification message from the second application;

    When the first device determines that sending the notification message of the second application to the second device and the third device is allowed, and after determining that the third device displays the interface of the second application, the first device sends the notification message to the second device and the third device. The third device sends a fourth notification message corresponding to the third notification message; the fourth notification message is the same as the third notification message, or the message content of the fourth notification message is the same as the third notification message. Messages are associated with the message content.
13. The method according to any one of claims 9-12, characterized in that the method further includes:

    When the first device determines that sending a notification message to the fourth device is not allowed, the first device does not send the second notification message corresponding to the first notification message to the fourth device; wherein, the third device The first application in a device is not allowed to send notification messages to the fourth device, and/or the fourth device and the first device correspond to different accounts, and/or the first device does not Obtain user authorization that is allowed to send notification messages to the fourth device.
14. The method according to any one of claims 9-13, characterized in that the method further includes:

    The first device receives a notification message triggering indication sent by the second device; wherein the notification message triggering indication is when the second device detects that the user responds to the second notification message displayed by the second device. Instructions sent after the first operation;

    The first device sends the display data of the first application corresponding to the second notification message to the second device according to the notification message triggering instruction; wherein the display data is that the first application is in Display data determined by the foreground running state or the background running state, the display data being used to instruct the second device to The display data displays the interface of the first application corresponding to the second notification message.
15. The method of claim 14, wherein the first device sends the display data of the first application corresponding to the second notification message to the second device according to the notification message triggering instruction, include:

    The first device determines the startup status of the first application according to the notification message triggering indication;

    If it is determined that the first application corresponding to the notification message trigger indication has not been started, after starting the first application in the background, the display data is obtained; or, if it is determined that the first application corresponding to the notification message trigger indication Started to obtain the display data;

    The first device sends the display data of the first application corresponding to the second notification message to the second device.
16. The method according to claim 14 or 15, characterized in that the first device sends the display of the first application corresponding to the second notification message to the second device according to the notification message triggering instruction. Data, including:

    When the first device determines that the first application allows the second device to display the detailed content of the notification message of the first application, the first device sends the notification message trigger instruction to the second device. Display data of the first application corresponding to the second notification message.
17. The method according to any one of claims 9-16, characterized in that the method further includes:

    The first device displays a first interface;

    The first device receives the user's setting operation on the first interface on whether the application in the first device allows forwarding of notification messages, and/or the setting operation on whether to allow sending notification messages to the second device. .
18. A message management method, characterized in that the method includes:

    The second device receives a second notification message sent by the first device; wherein the second notification message is a second notification message sent by the first device to the second device when it is determined that sending a notification message to the second device is allowed. Notification message, the second notification message is a notification message determined by the first device according to the first notification message of the first application in the first device, the second notification message is the same as the first notification message , or the message content of the second notification message is associated with the message content of the first notification message;

    The second device displays the second notification message.
19. The method according to claim 18, characterized in that the second device displays the second notification message, including:

    If the second device determines that display of the notification message of the first application is allowed, the second device displays the second notification message.
20. The method according to claim 18 or 19, characterized in that,

    The second device displays the second notification message when it is determined that the second device is in a scene that allows display of the notification message of the first application.
21. The method according to any one of claims 18-20, characterized in that the method further includes:

    After the second device detects the user's first operation on the second notification message, and determines that the second notification message is allowed to be operated, it sends a notification message triggering indication to the first device; the notification The message trigger indication is used to request to obtain the display data of the first application corresponding to the second notification message, where the display data is the display data determined by whether the first application is in a foreground running state or a background running state;

    The second device receives the display data sent by the first device;

    The second device displays the interface of the first application corresponding to the second notification message according to the display data.
22. The method according to any one of claims 18-21, characterized in that the method further includes:

    The second device displays a second interface;

    The second device receives a user's setting operation on the second interface to allow the application of the second device to display notification messages, and/or a setting operation to allow the display of notification messages to a scene.
23. An electronic device, characterized in that it includes: a processor and a memory, the memory is coupled to the processor, the memory is used to store computer program code, the computer program code includes computer instructions, when the processor The computer instructions are read from the memory, causing the electronic device to execute the method according to any one of claims 9-17.
24. An electronic device, characterized in that it includes: a processor, a memory and a display screen, the memory and the display screen are coupled to the processor, the memory is used to store computer program code, the computer program code includes Computer instructions, when the processor reads the computer instructions from the memory, cause the electronic device to execute the method according to any one of claims 18-22.
25. A computer-readable storage medium, characterized in that the computer-readable storage medium includes a computer program. When the computer program is run on an electronic device, the electronic device causes the electronic device to execute any one of claims 9-17. The method described in claim 18; and/or, causing the electronic device to perform the method described in any one of claims 18-22.
26. A computer program product, characterized in that, when the computer program product is run on a computer, the computer is caused to perform the method according to any one of claims 9-17; and/or, the computer is caused to The method as claimed in any one of claims 18-22 is performed.