Message Collaboration Method and Device

Abstract

An embodiment of the present application provides a message collaboration method and apparatus. The method includes: establishing a communication connection between a first electronic device and a second electronic device; when the first electronic device receives a first message, the first electronic device sends the first message to the second electronic device; the second electronic device displays the first message in the form of a card; when the first electronic device receives a second message, the first electronic device sends the second message to the second electronic device; the second electronic device displays the second message in the form of a card; when the first electronic device determines that the message content of the first message has not changed, the first electronic device refuses to send the first message to the second electronic device. In this way, the first electronic device can refuse to continue sending messages with unchanged content to the second electronic device, preventing the second electronic device from missing the second message due to repeatedly popping up the same first message, thereby enhancing the user experience of using the second electronic device.

Description

[0001] This application is a divisional application of the patent application "Message Collaboration Method and Device" with the application number 202210530344.8 filed on May 16, 2022. Technical Field

[0002] This application relates to the field of terminal technologies, and in particular, to a message collaboration method and device. Background Art

[0003] With the popularization and development of the Internet, people's functional requirements for electronic devices have become increasingly diverse. Various types of electronic devices, such as mobile phones, smart watches, wearable devices, and tablet computers, have become an essential part of people's lives. Users often use different types of electronic devices simultaneously, enabling communication connections to be established between the electronic devices. Taking the establishment of a communication connection between a mobile phone and a smart watch as an example, when the mobile phone receives and displays various types of notification messages (such as text messages, emails, application notifications, etc.), the smart watch that has established a communication connection with the mobile phone can synchronously receive and display the same notification messages as the mobile phone.

[0004] However, in different scenarios of data transmission between a mobile phone and a smart watch, there may be problems with message collaboration between the mobile phone and the smart watch, affecting the user experience of using the smart watch. Summary of the Invention

[0005] Embodiments of this application provide a message collaboration method and device, enabling a smart watch to achieve message collaboration between a mobile phone and the smart watch by determining the display form of a message on the smart watch, thereby enhancing the user experience of using the smart watch.

[0006] In a first aspect, embodiments of this application provide a message collaboration method applied to a message collaboration system. The message collaboration system includes: a first electronic device and a second electronic device. The method includes: establishing a communication connection between the first electronic device and the second electronic device; the first electronic device sending a first message to the second electronic device; the second electronic device displaying the first message in a card form; the first electronic device sending a second message to the second electronic device; wherein, the first message list of the first electronic device includes the second message and the first message; the second electronic device displays the second message in a card form; when the first electronic device determines that the message content of the first message has not changed, the first electronic device no longer sends the first message to the second electronic device again. In this way, when the message in the message list of the first electronic device does not change, the first electronic device can refuse to continue sending the message with unchanged content to the second electronic device, preventing the second electronic device from missing the second message due to repeatedly popping up the same first message, thereby enhancing the user experience of using the second electronic device.

[0007] Among them, the first message may be the meeting message of Meeting 1 in the embodiments of the present application; the second message may be the meeting message of Meeting 2 in the embodiments of the present application; the first electronic device may be the mobile phone in the embodiments of the present application; the second electronic device may be the smart watch in the embodiments of the present application.

[0008] In a possible implementation manner, the method further includes: when the first electronic device determines that the message content of the first message has changed, sending a first instruction to the second electronic device; the second electronic device removing the first message from the second message list according to the first instruction to obtain a third message list; the third message list includes the second message; the first electronic device sending the third message and a first identifier to the second electronic device; the first identifier is used to indicate that the third message is not displayed in the form of a card on the second electronic device; the second electronic device displaying the third message in the third message list according to the first identifier to obtain a fourth message list; among them, the fourth message list includes the third message and the second message. In this way, when the message list in the first electronic device changes, the first electronic device can send the message with changed content to the second electronic device, so that the second electronic device can silently refresh the message list, avoiding the user from missing the message, and further enhancing the user experience of using the second electronic device.

[0009] Among them, the third message may be the meeting message of the changed Meeting 1 in the embodiments of the present application; the first identifier may be the second flag bit being 1 in the embodiments of the present application.

[0010] In a possible implementation manner, the first electronic device includes a first module. When the first electronic device determines that the message content of the first message has not changed, the first electronic device no longer sends the first message to the second electronic device again, including: when the first electronic device determines that the message content of the first message has not changed, the first electronic device sets a second identifier for the first message; the first electronic device sends the first message and the second identifier to the first module; the first module determines not to send the first message to the second electronic device again according to the second identifier. In this way, the first electronic device can determine whether to send the first message to the second electronic device based on the first identifier, enhancing the intelligence of the first electronic device.

[0011] Among them, the first module may be the mobile phone middleware in the embodiments of the present application; the second identifier may be the second flag bit being 0 in the embodiments of the present application.

[0012] In a possible implementation, the first electronic device sends a third message and a first identifier to the second electronic device, including: the first electronic device sends the third message and the first identifier to a first module; the first module determines to send the third message and the first identifier to the second electronic device according to the first identifier. In this way, the first module can determine whether to push the third message to the second electronic device according to the identifier of the third message, enhancing the intelligence of the first electronic device.

[0013] In a second aspect, an embodiment of the present application provides a message collaboration method, which is applied to a first electronic device. The method includes: the first electronic device establishes a communication connection with the second electronic device; the first electronic device sends a first message to the second electronic device; the first electronic device sends a second message to the second electronic device; wherein, the first message list of the first electronic device includes the second message and the first message; when the first electronic device determines that the message content of the first message has not changed, the first electronic device no longer sends the first message to the second electronic device again. In this way, when the messages in the message list of the first electronic device do not change, the first electronic device can refuse to continue sending the message with unchanged content to the second electronic device, preventing the second electronic device from missing the second message due to repeatedly popping up the same first message, thereby enhancing the user experience of using the second electronic device.

[0014] In a possible implementation, the method further includes: when the first electronic device determines that the message content of the first message has changed, and sends a first instruction to the second electronic device; the first instruction is used to instruct the second electronic device to remove the first message from the second message list to obtain a third message list; the third message list includes the second message; the first electronic device sends a third message and a first identifier to the second electronic device; the first identifier is used to indicate that the third message is not displayed in the form of a card on the second electronic device; the fourth message list of the second electronic device includes the third message and the second message. In this way, when the message list in the first electronic device changes, the first electronic device can send the message with changed content to the second electronic device, enabling the second electronic device to silently refresh the message list, preventing the user from missing messages, and thus enhancing the user experience of using the second electronic device.

[0015] In a possible implementation, the first electronic device includes a first module. When the first electronic device determines that the message content of the first message has not changed, the first electronic device no longer sends the first message to the second electronic device again, including: when the first electronic device determines that the message content of the first message has not changed, the first electronic device sets a second identifier for the first message; the first electronic device sends the first message and the second identifier to the first module; the first module determines, according to the second identifier, not to send the first message to the second electronic device again. In this way, the first electronic device can determine whether to send the first message to the second electronic device based on the first identifier, enhancing the intelligence of the first electronic device.

[0016] In a possible implementation, the first electronic device sends a third message and a first identifier to the second electronic device, including: the first electronic device sends the third message and the first identifier to the first module; the first module determines, according to the first identifier, to send the third message and the first identifier to the second electronic device. In this way, the first module can determine whether to push the third message to the second electronic device according to the identifier of the third message, enhancing the intelligence of the first electronic device.

[0017] In a third aspect, an embodiment of the present application provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the terminal device executes the method described in the second aspect or any implementation manner of the second aspect.

[0018] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium stores instructions, and when the instructions are executed, the computer executes the method described in the second aspect or any implementation manner of the second aspect.

[0019] In a fifth aspect, a computer program product includes a computer program. When the computer program is run, the computer executes the method described in the second aspect or any implementation manner of the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 It is a schematic diagram of the architecture of a communication system 10 provided by an embodiment of the present application;

[0021] Figure 2 It is a schematic diagram of the hardware structure of an electronic device 100 provided by an embodiment of the present application;

[0022] Figure 3 It is a schematic diagram of the hardware structure of an electronic device 200 provided by an embodiment of the present application;

[0023] Figure 4 It is a schematic flowchart of a message collaboration method;

[0024] Figure 5 A schematic diagram of an interface for meeting reminder provided by an embodiment of the present application;

[0025] Figure 6 Another schematic diagram of an interface for meeting reminder provided by an embodiment of the present application;

[0026] Figure 7 A schematic diagram of a process flow of a message collaboration method provided by an embodiment of the present application;

[0027] Figure 8 Another schematic diagram of an interface for meeting reminder provided by an embodiment of the present application;

[0028] Figure 9 A schematic diagram of a process flow of another message collaboration method;

[0029] Figure 10 Another schematic diagram of an interface for meeting reminder provided by an embodiment of the present application;

[0030] Figure 11 Another schematic diagram of an interface for meeting reminder provided by an embodiment of the present application;

[0031] Figure 12 A schematic diagram of a process flow of another message collaboration method provided by an embodiment of the present application;

[0032] Figure 13 Another schematic diagram of an interface for meeting reminder provided by an embodiment of the present application;

[0033] Figure 14 A schematic diagram of a process flow of another message collaboration method;

[0034] Figure 15 Another schematic diagram of an interface for meeting reminder provided by an embodiment of the present application;

[0035] Figure 16 A schematic diagram of a process flow of another message collaboration method provided by an embodiment of the present application;

[0036] Figure 17 Another schematic diagram of an interface for meeting reminder provided by an embodiment of the present application;

[0037] Figure 18 A schematic diagram of the structure of a message collaboration device provided by an embodiment of the present application;

[0038] Figure 19 A schematic diagram of the hardware structure of another terminal device provided by an embodiment of the present application. Detailed implementation manners

[0039] For the convenience of clearly describing the technical solutions of the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish identical or similar items with basically the same functions and roles. For example, the first value and the second value are only used to distinguish different values, and do not limit their order. Those skilled in the art can understand that terms such as "first" and "second" do not limit the quantity and execution order, and terms such as "first" and "second" do not necessarily limit being different.

[0040] It should be noted that in the present application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Exactly speaking, using words such as "exemplary" or "for example" is intended to present relevant concepts in a specific manner.

[0041] In the present application, "at least one" means one or more, and "a plurality" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. The character " / " generally represents that the associated objects before and after are in an "or" relationship. "At least one (item)" or its similar expression below refers to any combination of these items, including any combination of single item (item) or plural items (items). For example, at least one (item) of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c can be single or multiple.

[0042] First, a communication system 10 provided by the present application is introduced.

[0043] Please refer to Figure 1 , Figure 1 which exemplarily shows a schematic diagram of the architecture of a communication system 10 provided by an embodiment of the present application.

[0044] As Figure 1 shown, the communication system 10 may include an electronic device 100 and an electronic device 200.

[0045] The electronic device 100 may be an electronic device such as a mobile phone, a tablet computer, a PC, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA). The present application does not impose any restrictions on the specific type of the electronic device 100.

[0046] The electronic device 200 may be an electronic device such as a smart watch, a smart bracelet, a wearable device, an augmented reality (AR) / virtual reality (VR) device, etc. The present application does not impose any restrictions on the specific type of the electronic device 200.

[0047] As Figure 1 shown, the electronic device 100 may establish a wireless communication connection with the electronic device 200 and transmit data information to each other through wireless communication technologies. Specifically, the wireless communication may be one or more wireless communication connections among Bluetooth, Wi-Fi direct, or Wi-Fi softAP.

[0048] In a possible implementation manner, the electronic device 100 may establish a wired communication connection with the electronic device 200 to perform data interaction. For example, the electronic device 100 and the electronic device 200 may establish a wired connection through a universal serial bus (USB) and transmit data information to each other based on the above-mentioned wired communication connection method.

[0049] It can be understood that the exemplary communication system structure shown in the embodiments of the present application does not constitute a specific limitation on the communication system 10. In other embodiments of the present application, the communication system 10 may include more or fewer electronic devices than shown, or may include different types of electronic devices from those shown. For example, the communication system 10 may further include multiple electronic devices 200 that establish communication connections with the electronic device 100, such as smart watches, or multiple different types of electronic devices, such as a display with communication functions, a tablet computer, a PC, etc. The present application does not impose any restrictions on this.

[0050] Based on the above communication system 10, a message collaboration method mentioned in the present application is introduced. For example, on the basis of the establishment of a communication connection between the electronic device 100 and the electronic device 200, there may be a situation where the electronic device 100 pushes the same message to the electronic device 200 multiple times, causing the electronic device 200 to receive the same message multiple times. For another example, on the basis of the establishment of a communication connection between the electronic device 100 and the electronic device 200, when the electronic device 100 sequentially initiates multiple meeting reminders, the electronic device 200 may display the earliest initiated meeting message, resulting in the user missing other meeting messages. For yet another example, on the basis of the establishment of a communication connection between the electronic device 100 and the electronic device 200, when the electronic device 100 merges messages in the message list, since the electronic device 200 does not support message merging, there may be a situation where one merged message is displayed on the electronic device 100 while multiple messages are displayed on the electronic device 200. Therefore, the problem of message non-collaboration between the above-mentioned electronic device 100 and the electronic device 200 affects the user experience.

[0051] In view of this, an embodiment of the present application provides a message collaboration method, enabling the electronic device 200 to determine the display form of a message in the electronic device 200 based on the flag carried when the electronic device 100 sends the message, realizing message collaboration between the electronic device 100 and the electronic device 200, and further enhancing the user experience of using the electronic device 200.

[0052] Next, the electronic device 100 provided in the embodiment of the present application will be introduced.

[0053] Exemplarily, Figure 2 FIG. is a schematic hardware structure diagram of an electronic device 100 provided in an embodiment of the present application.

[0054] As Figure 2 shown, the electronic device 100 may include a processor 101, a memory 102, a wireless communication module 103, a display screen 104, a sensor module 105, etc. Each of the above modules may be connected through a bus or other means. In the embodiment of the present application, the connection through a bus is taken as an example.

[0055] It can be understood that the structure schematically shown in the embodiment of the present invention does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may further include more or fewer components than shown in the figure, or combine certain components, or split certain components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

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

[0057] The controller may generate operation control signals according to the instruction operation code and timing signals to complete the control of fetching instructions and executing instructions.

[0058] A memory may also be provided in the processor 101 for storing instructions and data. In some embodiments, the memory in the processor 101 is a cache memory. This memory may store instructions or data that the processor 101 has just used or recycled. If the processor 101 needs to use the instruction or data again, it can directly call it from the memory. This avoids repeated accesses and reduces the waiting time of the processor 101, thus improving the efficiency of the system.

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

[0060] In a possible implementation, the electronic device 100 may establish a wired communication connection with the electronic device 200 through the USB interface and transmit data information to each other based on the above-mentioned wired communication connection method.

[0061] The memory 102 is coupled to the processor 101 and is used to store various software programs and / or multiple sets of instructions. In a specific implementation, the memory 102 may include a volatile memory, such as a random access memory (RAM); it may also include a non-volatile memory, such as a ROM, a flash memory, a hard disk drive (HDD), or a solid state drive (SSD); the memory 102 may also include a combination of the above types of memories. The memory 102 may store some program codes so that the processor 101 can call the program codes stored in the memory 102 to implement the implementation method of the embodiments of the present application in the electronic device 100. The memory 102 may store an operating system, such as an embedded operating system like uCOS, VxWorks, RTLinux, etc.

[0062] The wireless communication module 103 may include a Bluetooth communication module 103A and a WLAN communication module 103B. In some embodiments, the WLAN communication module 103B may be integrated with other communication modules (e.g., the Bluetooth communication module 103A). The WLAN communication module 103B and / or the Bluetooth communication module 103A may transmit signals to detect devices near the scanning electronic device 100, so that the electronic device 100 can discover nearby devices using one or more wireless communication technologies such as Bluetooth or WLAN, such as the electronic device 200. The electronic device 100 may establish a wireless communication connection with the electronic device 200 through one or more wireless communication technologies such as WLAN and Bluetooth, and perform data transmission and data reception based on the above wireless communication connection. The electronic device 100 may transmit data to the electronic device 200 based on one or more wireless communication technologies in the Bluetooth communication module 103A or the WLAN communication module 103B. The electronic device 100 may also obtain data instructions sent by the electronic device 200 through the above wireless communication connection. Among them, the Bluetooth communication module 103A may provide a solution for Bluetooth communication including one or more of classic Bluetooth (basic rate / enhanced datarate, BR / EDR) or Bluetooth low energy (BLE). The WLAN communication module 103B may provide a solution for WLAN communication including one or more of wireless fidelity direct (Wi-Fi direct), wireless fidelity local area networks (Wi-Fi LAN), or wireless fidelity software access point (Wi-Fi softAP). The wireless communication module 103 may receive electromagnetic waves via an antenna ( Figure 2 not shown), perform frequency modulation and filtering processing on the electromagnetic wave signal, and send the processed signal to the processor 101. The wireless communication module 103 may also receive the signal to be transmitted from the processor 101, perform frequency modulation on it, amplify it, and convert it into electromagnetic wave radiation through the antenna.

[0063] In some embodiments, the wireless communication module 103 may also provide solutions for wireless communication applied to the electronic device 100, including global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (IR), etc.

[0064] The display screen 104 can be used to display images, videos, etc. The display screen 104 can include a display panel. The display panel can adopt a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Miniled, a MicroLed, a Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 can include one or N display screens 104, where N is a positive integer greater than 1.

[0065] The sensor module 105 can include a touch sensor 105A, etc. The touch sensor 105A can also be referred to as a "touch control device". The touch sensor 105A can be disposed on the display screen 104, and the touch sensor 105A and the display screen 104 form a touch screen, also known as a "touch control screen". The touch sensor 105A can be used to detect touch operations acting thereon or nearby. Optionally, the sensor module 105 can further include a gyroscope sensor ( Figure 2 (not shown), an acceleration sensor ( Figure 2 (not shown), etc. Among them, the gyroscope sensor can be used to determine the motion posture of the electronic device 100. In some embodiments, the electronic device 100 can determine the angular velocity of the electronic device 100 around three axes (i.e., the x, y, and z axes) through the gyroscope sensor. The acceleration sensor can be used to detect the magnitude of the acceleration of the electronic device 100 in various directions (generally the x, y, and z axes). When the electronic device 100 is stationary, the magnitude and direction of gravity can be detected.

[0066] The audio module 106 can be used to convert digital audio information into an analog audio signal for output, and can also be used to convert an analog audio input into a digital audio signal. The audio module 106 can also be used to encode and decode audio signals. In some embodiments, the audio module 106 can also be disposed in the processor 101, or part of the functional modules of the audio module 106 can be disposed in the processor 101.

[0067] The speaker 107, which can also be referred to as a "horn", is used to convert an audio electrical signal into a sound signal. The electronic device 100 can listen to music or a hands-free call through the speaker 107.

[0068] Optionally, the electronic device 100 may further include a mobile communication module ( Figure 2 not shown). The mobile communication module may provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied to the electronic device 100.

[0069] Next, an exemplary electronic device 200 provided in the embodiments of the present application will be introduced.

[0070] Exemplarily, Figure 3 FIG. 12 is a schematic hardware structure diagram of an electronic device 200 provided in an embodiment of the present application.

[0071] As Figure 3 exemplarily shown, the electronic device 200 may include a processor 201, a memory 202, a wireless communication module 203, a power switch 204, a display screen 205, and so on. Each of the above modules may be connected through a bus or other means. In the embodiments of the present application, the connection through a bus is taken as an example.

[0072] The processor 201 may be used to read and execute computer-readable instructions. In a specific implementation, the processor 201 may mainly include a controller, an arithmetic unit, and registers. Among them, the controller is mainly responsible for instruction decoding and sending control signals for the operations corresponding to the instructions. The arithmetic unit is mainly responsible for storing register operands and intermediate operation results temporarily stored during the execution of instructions. In a specific implementation, the hardware architecture of the processor 201 may be an application-specific integrated circuit (ASIC) architecture, a MIPS architecture, an ARM architecture, or an NP architecture, etc.

[0073] In some embodiments, the processor 201 may be used to parse the data information received by the wireless communication module 203. The processor 201 may respond according to the data information and perform corresponding operations. The processor 201 may also be used to generate signals sent by the wireless communication module 203 outward, such as Bluetooth signals, etc.

[0074] The memory 202 is coupled to the processor 201 and is used to store various software programs and / or multiple groups of instructions. In a specific implementation, the memory 202 may include a high-speed random-access memory, and may also include a non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 202 may also store a communication program, which may be used to communicate with the electronic device 100 or other electronic devices.

[0075] The wireless communication module 203 may include a Bluetooth communication module 203A or others. The electronic device 200 may receive or transmit wireless signals through one or more of the Bluetooth communication modules 203A to establish a wireless communication connection with the electronic device 100. The electronic device 200 may obtain the data transmitted by the electronic device 100 through the above wireless communication connection, or send data instructions to the electronic device 100 through the above wireless communication connection. Among them, the Bluetooth communication module 203A may provide a solution for Bluetooth communication including one or more of classic Bluetooth (basic rate / enhanced data rate, BR / EDR) or Bluetooth low energy (BLE). Optionally, the wireless communication module 203 may further include a WLAN communication module ( Figure 3 not shown in the figure), and the WLAN communication module may provide a solution for WLAN communication including one or more of Wi-Fi direct, Wi-Fi LAN, or Wi-Fi softAP. In some embodiments, the WLAN module may be integrated with the Bluetooth communication module 203A. The electronic device 200 may establish a wireless communication connection with the electronic device 100 through the wireless communication technology provided by the WLAN module and perform data interaction with the electronic device 200 based on the wireless communication connection.

[0076] The power switch 204 may be used to control the power supply to the electronic device 200.

[0077] The display screen 205 may be used to display images, videos, controls, text information, etc. The display screen 205 may include a display panel. The display panel may adopt a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Miniled, a MicroLed, a Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 200 may include 1 or N display screens 205, and N is a positive integer greater than 1.

[0078] Optionally, the electronic device 200 may include a touch sensor, which may also be referred to as a "touch control device". The touch sensor may be disposed on the display screen 205. The touch sensor and the display screen 205 together form a touch screen, which may also be referred to as a "touch control screen". The touch sensor may be used to detect touch operations acting thereon or nearby.

[0079] Optionally, the electronic device 200 may include one or more physical buttons. The one or more physical buttons may receive input operations (e.g., pressing the physical button) applied by the user on the button. In response to the input operation, the electronic device 200 may perform operations corresponding to the controls displayed on the display screen corresponding to the physical button.

[0080] Optionally, the electronic device 200 may further include a USB interface. The electronic device 200 may establish a wired communication connection with the electronic device 100 through the USB interface, and transmit data information to each other through the wired communication connection.

[0081] It can be understood that Figure 3 The illustrated electronic device 200 is only one implementation manner of the embodiments of the present application, and does not constitute a specific limitation on the electronic device 200. For example, the electronic device 200 may be a smart watch, and the electronic device 200 may further include a watch band, a watch face, and a crown. The watch face may include a display screen 205 for displaying images, videos, controls, text information, etc. The watch band may be used to fix the electronic device 200 on the limbs of the human body for easy wearing. The crown may be used to control the display content of the electronic device 200. In practical applications, the electronic device 200 may further include more or fewer components than those shown in the figure, which is not limited here.

[0082] The technical problems and technical solutions of the present application will be introduced below with specific embodiments. The specific embodiments in the following scenarios may be implemented independently or in combination with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0083] It can be understood that in the following introduction of message coordination between the electronic device 100 and the electronic device 200, the electronic device 100 is taken as a mobile phone and the electronic device 200 is taken as a smart watch as an example for illustration, and this example does not constitute a limitation on the embodiments of the present application.

[0084] Scenario 1: On the basis of establishing a communication connection between the mobile phone and the smart watch, there may be a situation where the mobile phone pushes the same message to the smart watch multiple times, causing the smart watch to receive the same message multiple times. Specifically, Figure 4 It is a schematic flowchart of a message coordination method.

[0085] As Figure 4As shown, a mobile middleware can be set in the mobile phone according to an embodiment of the present application, and the mobile middleware can be a pre-installed software module in the mobile phone. Among them, the mobile middleware is used to implement the push of messages such as phone messages, text messages, and system notifications between the mobile phone and the smart watch. It can be understood that the mobile middleware can also have one or more of the following functions, for example: the function of establishing a Bluetooth connection with the smart watch, the function of establishing a secure connection channel, the function of being responsible for the assembly, parsing, and encryption of instructions, etc.

[0086] As Figure 4 shown, the message collaboration method includes the following steps:

[0087] S401. The smart watch establishes a communication connection with the mobile phone.

[0088] Exemplarily, a wireless communication connection can be established between the mobile phone and the smart watch through a solution including one or more of classic Bluetooth (basic rate / enhanced data rate, BR / EDR) or Bluetooth low energy (BLE) provided by the Bluetooth communication module, and data transmission and data reception are performed based on the wireless communication connection. Or, a wireless communication connection can be established between the mobile phone and the smart watch through a solution including one or more of Wi-Fi direct, Wi-Fi LAN, or Wi-Fi softAP provided by the WLAN communication module, and data transmission and data reception are performed based on the wireless communication connection. Or, a communication connection can also be established between the mobile phone and the smart watch through wireless means such as logging in to the same cloud account.

[0089] It can be understood that in the embodiment of the present application, the manner of establishing a communication connection between the mobile phone and the smart watch is not limited.

[0090] S402. The smart watch negotiates parameters with the mobile middleware.

[0091] In the embodiment of the present application, the parameters can include: parameters for establishing a communication connection between devices, parameters for negotiating service capabilities between devices, and parameters for negotiating command capabilities between devices, etc.

[0092] S403. The mobile middleware monitors the status of the mobile phone.

[0093] In the embodiment of the present application, the status of the mobile phone can include: the status when the mobile phone receives a new message, such as the status when the mobile phone receives a new meeting reminder, etc. Exemplarily, a listener for monitoring the status of the mobile phone can be set in the mobile middleware. When the mobile phone receives a new meeting reminder, the listener in the mobile middleware can monitor the message of the new meeting reminder.

[0094] It can be understood that S401 - S403 can be preparatory steps before the smartwatch and the mobile phone perform message collaboration; and the mobile phone and the smartwatch can also complete the preparatory work before the above - mentioned message collaboration between the smartwatch and the mobile phone through other means, which is not limited in the embodiments of the present application.

[0095] S404. When the mobile phone receives a meeting reminder, the mobile phone sends the meeting message with a control to the smartwatch through the mobile phone middleware.

[0096] In the embodiments of the present application, the control can be a control for setting a reminder after a few minutes. For example, the control can be a control for setting a reminder for the meeting message after 5 minutes.

[0097] Exemplarily, Figure 5 is a schematic diagram of an interface for a meeting reminder provided by the embodiments of the present application. When the mobile phone receives a meeting reminder, the interface shown as a in Figure 5 can be displayed in the message list of the mobile phone, and the mobile phone can send the meeting message with a control to the smartwatch through the mobile phone middleware. Among them, the control can be a control for setting a reminder after 5 minutes. For example, the control can be Figure 5 the control 502 shown as a in

[0098] As Figure 5 the interface shown as a in

[0099] This interface can be the interface corresponding to the message list of the mobile phone. This interface may include: time information, a control for indicating the on or off state of the WLAN function, a control for indicating the on or off state of the Bluetooth function, a control for indicating the on or off state of the mobile data function, a control for indicating the on or off state of the ringing function, a control for indicating the on or off state of the auto - rotation function, a control for setting the screen brightness, and the meeting message 501 with a control. Among them, the meeting message 501 with a control may include: a control 502 for setting a reminder after 5 minutes, and a meeting reminder initiated by the calendar application at 11:10, such as a test, and a meeting in Xi'an from 11:30 to 12:30 today.

[0100] S405. The smartwatch displays the meeting message with a control in the form of a card.

[0101] Exemplarily, when the smartwatch receives the meeting message with a control sent by the mobile phone through the mobile phone middleware, the smartwatch can display asFigure 5 The interface shown as b in [description], which may include a conference message 503 with controls. Among them, the conference message 503 with controls may include: a control 504 for setting a reminder in 5 minutes, and a conference reminder, such as a schedule, a test, from 11:30 to 12:30 today in Xi'an.

[0102] It can be understood that the Figure 5 conference message 503 with controls in the interface shown as b in [description] can correspond to the Figure 5 conference message 501 with controls in the interface shown as a in [description]; the Figure 5 control 504 for setting a reminder in 5 minutes in the interface shown as b in [description] can correspond to the Figure 5 control 502 for setting a reminder in 5 minutes in the interface shown as a in [description].

[0103] In a possible implementation, when the smartwatch receives a conference message with controls, the smartwatch can not only display the conference message with controls in the form of a card in the interface shown as b in [description], but also default to display the conference message with controls in the message list. For example, the smartwatch can display the interface shown as c in [description] when it receives an operation of the user opening the message list. Figure 5 Figure 5 It can be understood that when the smartwatch does not receive any operation of the user on the card within a time threshold for displaying the interface shown as b in [description], the smartwatch will return to the desktop state; furthermore, when the smartwatch receives an operation of the user swiping up on the interface where the desktop state is located, the smartwatch can display the interface shown as c in [description]. Therefore, the operation of the user opening the message list can be: receiving an operation of the user swiping up in the desktop state of the smartwatch. And the operation of the user opening the message list in the following text can all refer to this, and will not be elaborated below.

[0104] It can be understood that since the conference message will be displayed in the message list while popping up the card, and no message prompting the user to open the message list will be generated when it is displayed in the message list, so if the smartwatch does not receive an operation of the user opening the message list, the smartwatch may not display the interface shown as c in [description]. In the embodiment of the present application, the smartwatch will receive a message of the user deleting the conference message displayed in the message list, so the content displayed in the message list is introduced here. Figure 5 Figure 5

[0105] Figure 5

[0106] Figure 5 ​​​​​The interface shown in c in FIG. 5 may include a conference message 505 with controls. The conference message 505 with controls may include: a control 506 for setting a reminder in 5 minutes, and conference reminders, such as schedule, test, and today 11:30-12:30.

[0107] It is understandable that the Figure 5 The conference message 505 with controls in the interface shown in c can be used with Figure 5 The conference message 501 with controls in the interface shown in a corresponds to the one in FIG. Figure 5 The control 506 for setting a reminder after 5 minutes in the interface shown in c can be used with Figure 5 It corresponds to the control 502 for setting a reminder after 5 minutes in the interface shown in a.

[0108] S406: When the smart watch receives the user's click operation on the control, the smart watch sends a meeting message with a reminder in 5 minutes to the mobile phone.

[0109] In the embodiment of the present application, the meaning of the control can be found in the description of the step shown in S404, which will not be repeated here; for example, the control can be Figure 5 The control 504 shown in b in FIG. 5 is used to set a reminder after 5 minutes.

[0110] For example, in Figure 5 In the interface shown in b, when the smart watch receives the user's triggering operation of the control 504 for setting a reminder in 5 minutes, the smart watch can send a meeting message with a reminder in 5 minutes to the mobile phone, and the mobile phone can display the following Figure 6 The interface shown in a.

[0111] For example, Figure 6 A schematic diagram of another interface for meeting reminders provided in an embodiment of the present application.

[0112] Adaptively, when the mobile phone receives the meeting message with a reminder in 5 minutes sent by the smart watch, the mobile phone can delete the meeting message with the control described in step S404 in the message list (or understand as deleting the meeting message with the control described in step S404). Figure 5 The conference message 501 with the control 502 shown in a in FIG) and the conference message without the control pops up (or is understood as showing Figure 6 (a) The conference message 601 without controls in the interface shown in FIG. 5 . Further, the mobile phone may execute the step shown in S407.

[0113] like Figure 6The interface shown as a in [description], which may include: a meeting message 601 without controls. Among them, the meeting message 601 without controls may include: a meeting reminder that the calendar application will initiate again at 11:15, such as a test, and Xi'an from 11:30 to 12:30 today.

[0114] It can be understood that, compared with Figure 5 the interface shown as a in [description], Figure 6 in the meeting message 601 without controls in the interface shown as a in [description], there is no control for setting a reminder in 5 minutes.

[0115] S407. The mobile phone sends the meeting message without controls to the smart watch through the mobile phone middleware.

[0116] In the embodiments of the present application, the meaning of the control can be referred to the description in the steps shown in S404, and will not be elaborated here; for example, the meeting message without controls can be Figure 6 the meeting message 601 without controls shown as a in [description].

[0117] It can be understood that when the message in the message list of the mobile phone changes, the mobile phone can synchronously send the changed message to the smart watch to make the messages of the mobile phone and the smart watch consistent. For example, when the mobile phone receives the meeting message with a reminder in 5 minutes sent by the smart watch in the steps shown in S406, the mobile phone can refresh the message list, display the meeting message without controls, and send the meeting message without controls to the smart watch.

[0118] S408. The smart watch displays the meeting message without controls in the form of a card.

[0119] Exemplarily, when the smart watch receives the meeting message without controls sent by the mobile phone, the smart watch can display an interface as shown in b in Figure 6 [description], which may include a meeting message 602 without controls displayed in the form of a card. Among them, the meeting message 602 without controls may include: meeting reminders, such as schedules, tests, and Xi'an from 11:30 to 12:30 today.

[0120] In possible implementation manners, when the smart watch receives the meeting message without controls, the smart watch can not only display the meeting message without controls in the form of a card in the interface as shown in b in Figure 6 [description], but also default to display the meeting message without controls in the message list. For example, the smart watch can display an interface as shown in c in Figure 6 [description] when receiving an operation of the user to open the message list.

[0121] Such as Figure 6The interface shown in c in FIG. 6 may include a meeting message 603 with controls and a meeting message 604 without controls. The meeting message 603 with controls may include controls for indicating a reminder in 5 minutes and a meeting reminder, such as a schedule, a test, and today's time from 11:30 AM to 12:30 PM. The meeting message 604 without controls may include a meeting reminder, such as a schedule, a test, and today's time from 11:30 AM to 12:30 PM.

[0122] It is understandable that the Figure 6 The conference message 604 without controls in the interface shown in c can be Figure 6 The interface shown in a corresponds to the conference message 601 without controls; Figure 6 The conference message 603 with controls in the interface shown in c can be used with Figure 5 This corresponds to the conference message 501 with the control 502 in the interface shown in a.

[0123] It is understood that the smartwatch displays the conference message with controls in card format in step S405, and upon receiving the user's control triggering a 5-minute reminder, executes step S408, displaying the conference message in card format without controls. The conference message in step S405 and step S408 contain the same content and are both displayed in card format. Therefore, the repeated display of the same message content in the same display format affects the user experience of using the smartwatch.

[0124] In view of this, for scenario one, an embodiment of the present application provides a message collaboration method, so that the smart watch and the mobile phone can avoid the same message popping up repeatedly in the form of a card by transmitting a flag bit for indicating the display method of the message.

[0125] For example, Figure 7 A flowchart of a message collaboration method provided in an embodiment of the present application.

[0126] like Figure 7 As shown, the message collaboration method may include the following steps:

[0127] S701. The smart watch establishes a communication connection with the mobile phone.

[0128] S702: The smart watch negotiates parameters with the mobile phone middleware.

[0129] S703. The mobile phone middleware monitors the mobile phone status.

[0130] It can be understood that the descriptions in the steps shown in S701 - S703 can refer to the descriptions in the steps shown in S401 - S403, which will not be elaborated here; moreover, the steps shown in S701 - S703 can be preparatory steps before the smartwatch and the mobile phone perform message collaboration. The mobile phone and the smartwatch can also complete the above preparatory work for message collaboration between the smartwatch and the mobile phone through other means, and this application embodiment does not make any limitations in this regard.

[0131] S704. When the mobile phone middleware monitors a meeting reminder, the mobile phone middleware sends a meeting message prompt to the smartwatch.

[0132] Among them, this meeting message prompt is used to indicate that the smartwatch is about to receive a meeting message sent by the mobile phone.

[0133] S705. The smartwatch sends a request message to the mobile phone middleware.

[0134] In the embodiment of this application, this request message is used to obtain the first flag bit corresponding to the meeting message described in the step shown in S704; this first flag bit is used to indicate the display mode of the meeting message on the smartwatch. For example, when the first flag bit is 0, it means that the meeting message will be displayed in the form of a card on the smartwatch; or, when the first flag bit is 1, it means that the meeting message on the smartwatch will not be displayed in the form of a card, so the meeting message will be displayed in the form of a message list on the smartwatch. It can be understood that this first flag bit is not limited to 0 and 1, and can also be in other forms, and this application embodiment does not make any limitations in this regard.

[0135] It can be understood that other content can also be included in this request message. For example, this request message can also be used to obtain the directory ID corresponding to the message. Among them, this directory ID is used to indicate the application to which the message belongs, and the attributes of this message can include one or more of the following fields, for example: the package name of the message application, the message title, the message subtitle, the message content, the time when the message is generated, the type of the message (such as meeting or memo), the specific content, and action reverse control, etc.

[0136] It can be understood that when the mobile phone receives a new message reminder, the mobile phone and the smartwatch can default to execute the steps shown in S704 - S705 to determine the first flag bit corresponding to this new message, so that the smartwatch that receives this new message can determine the display mode of the new message according to this first flag bit.

[0137] S706. The mobile phone sends the meeting message with controls (the first flag bit is 0) to the smartwatch through the mobile phone middleware.

[0138] In the embodiments of the present application, the meanings of the control and the conference message with the control can be referred to the description in the steps shown in S404, and will not be elaborated here.

[0139] Exemplarily, the specific process of the mobile phone sending the conference message with the control to the smart watch through the mobile phone middleware can be: the mobile phone sends the conference message with the control to the mobile phone middleware, and the mobile phone middleware can default to set the first identification flag bit of the conference message with the control to 0. Then the mobile phone middleware sends the conference message with the control (the first flag bit is 0) to the smart watch, so that the smart watch can display the conference message with the control according to the first flag bit.

[0140] S707. The smart watch displays the conference message with the control in the form of a card according to the first flag bit.

[0141] Exemplarily, when the first flag bit is 0, the smart watch displays the conference message with the control in the form of a card. For example, the smart watch can display an interface as shown in b in Figure 5 .

[0142] In a possible implementation manner, when the smart watch receives the conference message with the control, the smart watch can not only display the conference message with the control in the form of a card in the interface as shown in b in Figure 5 , but also default to display the conference message with the control in the message list. For example, the smart watch can display an interface as shown in c in Figure 5 when receiving the operation of the user opening the message list.

[0143] S708. When the smart watch receives the operation of the user clicking the control, the smart watch can send a conference message with a reminder after 5 minutes to the mobile phone.

[0144] Among them, the steps shown in S708 can be referred to the description in the steps shown in S406, and will not be elaborated here.

[0145] S709. The mobile phone sends a message for removing the conference message with the control in the message list to the smart watch through the mobile phone middleware.

[0146] Exemplarily, in the message list of the smart watch as shown in c in Figure 5 , when the smart watch receives the message sent by the mobile phone through the mobile phone middleware for removing the conference message with the control in the message list, the smart watch can remove the conference message with the control in the message list. At this time, the message list of the smart watch may not contain any conference messages.

[0147] S710. The mobile phone sends the meeting message without controls to the mobile phone middleware.

[0148] In the embodiments of the present application, for the meeting message without controls described in the steps shown in S710, reference can be made to the description in the steps shown in S407, which will not be elaborated here.

[0149] S711. The mobile phone middleware determines the consistency between the meeting message without controls and the meeting message with controls.

[0150] Exemplarily, the mobile phone middleware can respectively obtain the message identity (notification identity, UID) information corresponding to the meeting message without controls, and obtain the UID information corresponding to the meeting message with controls, and determine the consistency of the above two meeting messages based on the consistency of the above two UID information.

[0151] Specifically, when the mobile phone middleware determines that the UID information of the above two meeting messages is consistent, the mobile phone middleware can set the first flag bit in the meeting message without controls to 1, indicating that the smart watch can display the meeting message without controls in the form of a message list instead of in the form of a card, and display the meeting message without controls in the form of a message list in the smart watch. Or, when the mobile phone middleware determines that the UID information of the above two meeting messages is inconsistent, the mobile phone middleware can set the first flag bit in the meeting message without controls to 0, indicating that the smart watch can display the meeting message without controls in the form of a card.

[0152] In a possible implementation, the mobile phone middleware can store the UID information of the messages sent within a time threshold, so that the mobile phone middleware can determine the consistency of any two messages based on the UID information of the messages. Or, the mobile phone middleware can also periodically clear the stored UID information of the messages, which is not limited in the embodiments of the present application.

[0153] S712. The mobile phone middleware sends the meeting message without controls (the first flag bit is 1) to the smart watch.

[0154] S713. The smart watch refreshes the message list according to the first flag bit.

[0155] It can be understood that when the smart watch receives the meeting message without controls and determines that the first flag bit is 1, the smart watch no longer pops up the meeting message without controls in the form of a card. Instead, the smart watch refreshes the message list and, when receiving an operation for the user to open the message list, displays the meeting message without controls in the form of a message list. For example, the smart watch can display an interface as shown in Figure 8 shown.

[0156] Exemplarily, Figure 8 This is another schematic diagram of the interface for meeting reminder provided by the embodiments of the present application. As Figure 8 shown, when the first flag bit is 1, the smart watch refreshes the message list and displays meeting messages without controls in the message list. Then, when the smart watch receives an operation from the user to open the message list, the smart watch can display the meeting message without controls as shown in Figure 8 the figure. For example, the meeting message without controls can be: schedule, test, and 11:30 - 12:30 today.

[0157] Based on this, the mobile phone can send a message carrying the first flag bit to the smart watch, so that the smart watch can determine in which form to display the message based on the first flag bit, avoiding the repeated pop - up of the message in the form of a card, thereby enhancing the user experience of using the smart watch.

[0158] Scenario 2: On the basis of establishing a communication connection between the mobile phone and the smart watch, when the mobile phone initiates multiple meeting reminders in sequence, the smart watch finally displays the meeting message initiated first, resulting in a situation where the user may miss other meeting messages.

[0159] Exemplarily, Figure 9 This is a flowchart of another message collaboration method.

[0160] As Figure 9 shown, the message collaboration method may include:

[0161] S901. The smart watch establishes a communication connection with the mobile phone.

[0162] S902. The smart watch negotiates parameters with the mobile phone middleware.

[0163] S903. The mobile phone middleware monitors the status of the mobile phone.

[0164] It can be understood that the descriptions in the steps shown in S901 - S903 can refer to the descriptions in the steps shown in S401 - S403, which will not be elaborated here; and the steps shown in S901 - S903 can be preparation steps before the smart watch and the mobile phone perform message collaboration. The mobile phone and the smart watch can also complete the above - mentioned preparation work before message collaboration between the smart watch and the mobile phone in other ways, which is not limited in the embodiments of the present application.

[0165] S904. When the mobile phone receives a reminder for Meeting 1, the mobile phone sends the meeting message of Meeting 1 to the smart watch through the mobile phone middleware.

[0166] Exemplarily, Figure 10 This is yet another schematic diagram of the interface for meeting reminder provided by the embodiments of the present application.

[0167] When the mobile phone receives a reminder for Meeting 1, the mobile phone can display an interface as shown in Figure 10 a in the figure. In this interface, it can display Meeting 1 initiated by the calendar application at 13:40. For example, Meeting 1 may include: 14:00 - 15:00 today, and a control for setting a reminder 5 minutes later.

[0168] S905. The smartwatch displays the meeting message of Meeting 1 in the form of a card.

[0169] Exemplarily, when the smartwatch receives the meeting message of Meeting 1 sent by the mobile phone through the mobile phone middleware, the smartwatch can display an interface as shown in Figure 10 b in the figure. In this interface, it can display the meeting message of Meeting 1 in the form of a card, such as: schedule, Meeting 1, 14:00 - 15:00 today, and a control for setting a reminder 5 minutes later.

[0170] In a possible implementation, when the smartwatch receives the meeting message of Meeting 1, the smartwatch can not only display the meeting message of Meeting 1 in the form of a card in the interface as shown in Figure 10 b in the figure, but also default to display the meeting message of Meeting 1 in the message list. For example, when the smartwatch receives an operation to open the message list by the user, it can display an interface as shown in Figure 10 c in the figure.

[0171] S906. When the mobile phone receives a reminder for Meeting 2, the mobile phone sends the meeting message of Meeting 2 to the smartwatch through the mobile phone middleware, and then sends the carried meeting message of Meeting 1 to the smartwatch through the mobile phone middleware.

[0172] Exemplarily, Figure 11 This is another schematic diagram of the interface for meeting reminder provided by the embodiments of the present application.

[0173] Among them, Meeting 1 in the step shown in S906 can be Figure 11 Meeting 1 carried below Meeting 2 in the message list of the mobile phone in the interface shown in a in the figure. Meeting 1 in the step shown in S906 can be the same as or different from Meeting 1 in the step shown in S905.

[0174] It can be understood that when there are two messages in the message list of the mobile phone as shown in Figure 11 a in the figure, the mobile phone can first send the currently received meeting message of Meeting 2 to the smartwatch, and then send the meeting message of Meeting 1 carried below Meeting 2 to the smartwatch, so that the smartwatch can display Meeting 2 in the form of a card in the interface as shown in Figure 11 b in the figure, and then jump to an interface as shown in Figure 11The meeting 1 is displayed in the form of a card in the interface shown in c.

[0175] Exemplarily, when the mobile phone receives a reminder of meeting 2, the message list of the mobile phone can display an interface as shown in Figure 11 a in it. Multiple meeting messages can be displayed in this interface. For example: Meeting 2 initiated by the calendar application at 13:45, today from 14:05 to 15:05, and a control for setting a reminder 5 minutes later corresponding to meeting 2; and, meeting 1 initiated by the calendar application at 13:45, today from 14:00 to 15:00, and a control for setting a reminder 5 minutes later. It can be understood that at this time, two meeting messages, namely meeting 1 and meeting 2, can be displayed in the message list of the mobile phone.

[0176] Adaptively, when the smartwatch receives the meeting message of meeting 2 sent by the mobile phone, the smartwatch can display an interface as shown in Figure 11 b in it. The meeting message of meeting 2 can be displayed in the form of a card in this interface, such as: schedule, meeting 2, today from 14:05 to 15:05, and a control for setting a reminder 5 minutes later. Further, when the smartwatch receives the meeting message of meeting 1, the smartwatch can Figure 11 jump from the interface shown in b in it to an interface as shown in Figure 11 c in it. The Figure 11 meeting message of meeting 1 carried can be displayed in the interface shown in c in it. The interface shown in c in it is similar to the interface shown in Figure 11 b in it, which will not be elaborated here. Figure 10 In a possible implementation, when the smartwatch receives the meeting message of meeting 2, the smartwatch can not only display the meeting message of meeting 2 in the form of a card in the interface as shown in b in it, but also default to display the meeting message of this meeting 2 in the message list. For example, when the smartwatch receives an operation of the user to open the message list, it can display an interface as shown in

[0177] d in it. As shown in Figure 11 d in it, the meeting message of meeting 2 and the meeting message of meeting 1 can be displayed in the message list of the smartwatch. Figure 11 Figure 11 In a possible implementation, when the smartwatch receives the meeting message of meeting 1 after receiving the meeting message of meeting 2, the smartwatch can not only display the meeting message of meeting 1 in the form of a card in the interface as shown in

[0178] c in it, but also default to display the meeting message of this meeting 1 in the message list. For example, when the smartwatch receives an operation of the user to open the message list, it can display an interface as shown in Figure 11 e in it. As shown in Figure 11 e in it, the meeting message of meeting 1 can be displayed in the message list of the smartwatch.Figure 11 In the interface shown at e in , the meeting messages of Meeting 1, the meeting messages of Meeting 2, and the meeting messages of Meeting 1 can be displayed in the message list of the smartwatch.

[0179] It can be understood that when the mobile phone has a new message notification, such as Meeting 2, it will refresh other notification messages of the same application in the message list, such as refreshing Meeting 2 and Meeting 1, and the refreshed Meeting 2 and Meeting 1 carried below Meeting 2 in the message list will be sent to the smartwatch as new messages. Therefore, Meeting 2 and Meeting 1 can be sent to the watch in sequence through the steps shown in S906.

[0180] It can be understood that since the mobile phone middleware does not perceive the message content when monitoring a new message, but directly sends it to the smartwatch, when there are two meetings in the message list of the mobile phone, such as including Meeting 1 and Meeting 2, after the mobile phone sends the meeting message of Meeting 2 to the smartwatch, it can send other messages carried by Meeting 2 in the message list, such as the message of Meeting 1 carried in the message list, to the smartwatch, so that the smartwatch can immediately jump to the meeting message of Meeting 1 displayed in card form after displaying the meeting message of Meeting 2 in card form. Therefore, when the user does not pay attention to the smartwatch all the time, it may happen that only the message of Meeting 1 finally displayed is seen, thus missing other meetings.

[0181] In view of this, for Scenario 2, the embodiment of the present application provides a message collaboration method. The smartwatch can determine whether to display the carried meeting through a flag bit sent by the mobile phone for indicating whether the carried meeting has changed, while avoiding missing meeting reminders and enhancing the user experience of using the smartwatch.

[0182] Exemplarily, Figure 12 is a schematic flowchart of another message collaboration method provided by the embodiment of the present application.

[0183] As Figure 12 shown, the message collaboration method may include the following steps:

[0184] S1201. The smartwatch establishes a communication connection with the mobile phone.

[0185] S1202. The smartwatch negotiates parameters with the mobile phone middleware.

[0186] S1203. The mobile phone middleware monitors the mobile phone status.

[0187] S1204. When the mobile phone receives a reminder for Meeting 1, the mobile phone sends the meeting message of Meeting 1 to the smartwatch through the mobile phone middleware.

[0188] S1205. The smartwatch displays the meeting messages of Meeting 1 in the form of cards.

[0189] S1206. When the mobile phone receives a reminder for Meeting 2, the mobile phone sends the meeting messages of Meeting 2 to the smartwatch through the mobile phone middleware.

[0190] S1207. The smartwatch displays the meeting messages of Meeting 2 in the form of cards.

[0191] It can be understood that the steps shown in S1201 - S1207 above are similar to the steps shown in S901 - S907, and the interfaces displayed on the mobile phone and the smartwatch can also refer to the steps shown in S901 - S907 above, which will not be elaborated here.

[0192] S1208. The mobile phone determines a second flag bit according to the change situation of the message content of Meeting 1.

[0193] In the embodiments of the present application, when the mobile phone determines that the message content of Meeting 1 has not changed, it can determine that the second flag bit in the meeting message of Meeting 1 is 0, so that the mobile phone can execute the steps shown in S1209; or when the mobile phone determines that the message content of Meeting 1 has changed, and the second flag bit in the meeting message of Meeting 1 is 1, the mobile phone can execute the steps shown in S1210 - S1212.

[0194] It can be understood that the change in the message content of Meeting 1 can be understood as a change in the meeting theme or meeting time of Meeting 1, etc. For example, before the mobile phone receives a reminder for Meeting 2, the user changes the meeting time or meeting theme of Meeting 1, etc., so that when the mobile phone receives a reminder for Meeting 2 and sends the meeting messages of Meeting 2, and then sends Meeting 1, it is recognized that the message content of Meeting 1 is inconsistent with the message content of Meeting 1 in the steps shown in S1204.

[0195] It can be understood that the second flag bit is not limited to 0 and 1, and can also be in other forms, which are not limited in the embodiments of the present application.

[0196] S1209. The mobile phone sends the meeting messages of Meeting 1 (the second flag bit is 0) to the mobile phone middleware.

[0197] Exemplarily, when the mobile phone middleware determines that the second flag bit of the meeting message of Meeting 1 is 0, the mobile phone middleware can determine that it is not necessary to continue pushing the meeting message of Meeting 1 to the smartwatch.

[0198] It can be understood that when the meeting message of Meeting 1 in the message list on the mobile phone remains unchanged, the mobile phone can refuse to continue sending Meeting 1 to the smart watch, preventing the smart watch from missing the meeting message of Meeting 2 due to repeatedly popping up the meeting message of Meeting 1, thereby enhancing the user experience of using the smart watch.

[0199] S1210. The mobile phone sends the message for removing the meeting message of Meeting 1 in the message list to the smart watch through the mobile phone middleware.

[0200] When the mobile phone determines that the second flag bit of the meeting message of Meeting 1 is 1, the mobile phone can send the message for removing the meeting message of Meeting 1 in the message list to the smart watch through the mobile phone middleware. Therefore, the smart watch can remove the meeting message of Meeting 1 in the message list, enabling the changed meeting message of Meeting 1 to be normally displayed in the message list when the subsequent message content changes.

[0201] Exemplarily, Figure 13 This is another schematic diagram of the meeting reminder interface provided by the embodiment of the present application.

[0202] Correspondingly, when the smart watch receives the message for removing the meeting message of Meeting 1 sent by the mobile phone through the mobile phone middleware, the smart watch can remove the meeting message of Meeting 1 in the message list and, when receiving the operation of the user to open the message list, display the interface as shown in Figure 13 as shown in a in. As shown in the interface in Figure 13 as shown in a in, the meeting message of Meeting 2 can be displayed in this interface.

[0203] S1211. The mobile phone sends the meeting message of Meeting 1 (with the second flag bit being 1) to the smart watch through the mobile phone middleware.

[0204] Exemplarily, when the mobile phone determines that the second flag bit of the meeting message of Meeting 1 is 1, the mobile phone can push the meeting message of Meeting 1 to the smart watch through the mobile phone middleware.

[0205] S1212. The smart watch refreshes the message list according to the second flag bit.

[0206] Exemplarily, when the smart watch receives the meeting message of Meeting 1, it can refresh the message list according to the second flag bit being 1. For example, the smart watch can display when receiving the operation of the user to open the message list: the meeting message of Meeting 2 and the carried meeting message of Meeting 1.

[0207] It can be understood that since the second flag bit in the carried meeting message of Meeting 1 is 1, Meeting 1 will not be displayed in the smart watch in the form of a card but in the message list.

[0208] Exemplarily, when the smartwatch receives the meeting message of Meeting 1 sent by the mobile phone through the mobile phone middleware and determines that the second flag bit in the meeting message of Meeting 1 is 1, the smartwatch can refresh the message list, and when receiving the operation of the user to open the message list, display an interface as shown in Figure 13 shown in b of the figure. The interface may include: the meeting message of Meeting 1 and the meeting message of Meeting 2 displayed in the form of a message list. For example: Meeting 1 with schedule reminder, today 14:03 - 15:03; and, Meeting 2 with schedule reminder, today 14:05 - 15:05. It can be understood that the message content of Meeting 1 may be inconsistent with the message content of Meeting 1 in the steps shown in S1205.

[0209] Based on this, when the message list in the mobile phone changes, the mobile phone can send the message with content changes to the smartwatch, so that the smartwatch can silently refresh the message list, preventing the user from missing messages, and thus enhancing the user experience of using the smartwatch.

[0210] Scenario 3: On the basis of establishing a communication connection between the mobile phone and the smartwatch, when the mobile phone merges the messages in the message list, since the smartwatch does not support message merging, there may be a situation where one merged message is displayed on the mobile phone while multiple messages are displayed on the smartwatch, resulting in a problem of message non - coordination between the smartwatch and the mobile phone. Specifically, Figure 14 is a schematic flow diagram of another message coordination method.

[0211] As Figure 14 shown, the message coordination method may include the following steps:

[0212] S1401. The smartwatch establishes a communication connection with the mobile phone.

[0213] S1402. The smartwatch negotiates parameters with the mobile phone middleware.

[0214] S1403. The mobile phone middleware monitors the mobile phone status.

[0215] S1404. When the mobile phone receives a reminder for Meeting 1, the mobile phone sends the meeting message of Meeting 1 to the smartwatch through the mobile phone middleware.

[0216] S1405. The smartwatch displays the meeting message of Meeting 1 in the form of a card.

[0217] S1406. When the mobile phone receives a reminder for Meeting 2, the mobile phone sends the meeting message of Meeting 2 to the smartwatch through the mobile phone middleware.

[0218] S1407. The smartwatch displays the meeting message of Meeting 2 in the form of a card.

[0219] It can be understood that the steps shown in S1401 - S1407 are similar to the steps shown in S901 - S907, and the interfaces displayed on the mobile phone and the smart watch can also refer to the steps shown in S901 - S907, which will not be elaborated here.

[0220] S1408. The mobile phone combines the meeting messages in the message list.

[0221] Exemplarily, the mobile phone can automatically combine the messages of the same application in the message list when receiving a certain number of messages; or, the mobile phone can automatically combine the messages of the same application in the message list within a certain time threshold; or, the mobile phone can also combine the messages of the same application in the message list when receiving an operation from the user to combine the message list. The embodiments of the present application do not make limitations in this regard.

[0222] Exemplarily, Figure 15 is a schematic diagram of another interface for meeting reminder provided by the embodiments of the present application. In Figure 15 the corresponding embodiment, taking the mobile phone automatically combining the messages of the same application in the message list when receiving a certain number of messages as an example for illustration, this example does not constitute a limitation on the embodiments of the present application.

[0223] When the mobile phone displays that there are 2 meeting messages in the message list as shown in a in Figure 15 , when the mobile phone determines that it has received at least two messages from the calendar application, it can automatically combine the messages of the calendar application in the message list and generate a meeting summary notice, and then display the interface as shown in b in Figure 15 . As shown in the interface in b in Figure 15 , the combined meeting message 1501 can be displayed in this interface. For example, the combined meeting message 1501 can include: 2 schedules initiated by the calendar application at 13:45, including Meeting 1 and Meeting 2.

[0224] S1409. The mobile phone sends the combined meeting message to the smart watch through the mobile phone middleware.

[0225] S1410. The smart watch displays the combined meeting message in the form of a card.

[0226] When the smart watch receives the combined meeting message, it can display the combined meeting message in the form of a card, and when receiving an operation from the user to open the message list, it displays the combined meeting message, the meeting message of Meeting 1, and the meeting message of Meeting 2.

[0227] Exemplarily, when the smart watch receives the combined meeting message, it can display as shown in Figure 15The interface shown in c, which includes: the merged meeting messages, and the merged meeting messages can be two schedule meetings, Meeting 1 and Meeting 2. Further, when the smartwatch receives the operation of the user to open the message list, the smartwatch displays Figure 15 The interface shown in d, which includes: the merged meeting messages, the meeting messages of Meeting 1, and the meeting messages of Meeting 2. The meeting messages of the merged meeting can be two schedule meetings, Meeting 1 and Meeting 2; the meeting messages of Meeting 2 can be schedule meeting 2, today 14:05-15:05; the meeting messages of Meeting 1 can be schedule meeting 1, today 14:00-15:00.

[0228] It can be understood that when the mobile phone merges the meeting messages in the message list, a merged message can be generated. When the mobile phone sends the merged message to the smartwatch as a new notification, it may cause the situation that the smartwatch displays multiple messages, resulting in the problem of message non-synergy between the smartwatch and the mobile phone.

[0229] In view of this, for Scenario 3, the embodiment of the present application provides a message coordination method. When the mobile phone performs message merging, it can send a removal command to the smartwatch to delete the messages to be merged, and then send the merged message to the smartwatch, so as to achieve message coordination between the smartwatch and the mobile phone, thereby enhancing the user experience of using the smartwatch.

[0230] Exemplarily, Figure 16 It is a schematic flowchart of another message coordination method provided by the embodiment of the present application.

[0231] As Figure 16 shown, the message coordination method may include the following steps:

[0232] S1601. The smartwatch establishes a communication connection with the mobile phone.

[0233] S1602. The smartwatch and the mobile phone middleware negotiate parameters.

[0234] S1603. The mobile phone middleware monitors the status of the mobile phone.

[0235] S1604. When the mobile phone receives a reminder for Meeting 1, the mobile phone sends the meeting messages of Meeting 1 to the smartwatch through the mobile phone middleware.

[0236] S1605. The smartwatch displays the meeting messages of Meeting 1 in the form of cards.

[0237] S1606. When the mobile phone receives a reminder for Meeting 2, the mobile phone sends the meeting messages of Meeting 2 to the smartwatch through the mobile phone middleware.

[0238] S1607. The smartwatch displays the meeting messages of Meeting 2 in the form of cards.

[0239] S1608. The mobile phone combines the meeting messages in the message list.

[0240] It can be understood that the steps shown in S1601 - S1608 above are similar to the steps shown in S1401 - S1408, and will not be elaborated here.

[0241] S1609. The mobile phone sends the message for removing the message of Meeting 1 in the message list to the smartwatch through the mobile phone middleware.

[0242] Adaptively, when the smartwatch receives the message for removing the message of Meeting 1 sent by the mobile phone, it can remove the message of Meeting 1 in the message list. At this time, only the meeting messages of Meeting 2 are included in the message list of the smartwatch.

[0243] Exemplarily, Figure 17 Another schematic diagram of the interface for meeting reminder provided by the embodiment of the present application. As Figure 17 shown, when the smartwatch receives the message for removing the message of Meeting 1 sent by the mobile phone, the smartwatch can switch from the interface shown in Figure 17 a to the interface shown in Figure 17 b. In a possible implementation manner, the smartwatch can also send a response message to the mobile phone for indicating that Meeting 1 has been removed.

[0244] S1610. The mobile phone sends the message for removing the message of Meeting 2 in the message list to the smartwatch through the mobile phone middleware.

[0245] Adaptively, when the smartwatch receives the message for removing the message of Meeting 2 sent by the mobile phone, it can remove the message of Meeting 2 in the message list. At this time, no meetings are included in the message list of the smartwatch. In a possible implementation manner, the smartwatch can also send a response message to the mobile phone for indicating that Meeting 2 has been removed.

[0246] S1611. The mobile phone sends the combined meeting messages (the third flag bit is 1) to the smartwatch through the mobile phone middleware.

[0247] In a possible implementation manner, when the mobile phone determines that the message content of each meeting message in the combined meeting message is the same as the message content of the meeting messages sent before, such as the message content of Meeting 1 in the step of S1604 and the message content of Meeting 2 in the step of S1606, the mobile phone can add a third flag bit to the combined meeting message, and the third flag bit can be 1. Wherein, the third flag bit being 1 is used to indicate that the smartwatch will not pop up the combined meeting message in the form of a card.

[0248] In a possible implementation, when the mobile phone determines that the message content of each meeting message in the merged meeting message is the same as the message content of the meeting messages sent before, and the UID information of each meeting in the merged meeting message is the same as the UID information of Meeting 1 in the step shown in S1604 (and the UID information of Meeting 2 in the step shown in S1606), the mobile phone can add a third flag bit to the merged meeting message, and the third flag bit can be 1.

[0249] S1612. The smartwatch refreshes the message list according to the third flag bit.

[0250] Exemplarily, when the smartwatch receives the merged meeting message and determines that the third flag bit of the merged meeting message is 1, it can refresh the message list, and when it receives the operation of the user to open the message list, it displays the merged meeting message.

[0251] Such as Figure 17 shown, when the smartwatch receives the operation of the user to open the message list, it can display an interface as shown in c in Figure 17 . The interface may include: the merged meeting message, such as 2 scheduled meetings, Meeting 1 and Meeting 2.

[0252] Based on this, the mobile phone can delete the messages to be merged by sending a removal command to the smartwatch, and then send the merged message to the smartwatch, so as to achieve message coordination between the smartwatch and the mobile phone, thereby enhancing the user experience of using the smartwatch.

[0253] Scenario 4: After the smartwatch and the mobile phone are synchronously upgraded, they support a new message format. If a single device is upgraded, there may be a situation where the message display is abnormal between the devices. For example, on the basis of establishing a communication connection between the new version of the smartwatch and the old version of the mobile phone, the new version of the smartwatch needs to parse new fields, while the old version of the mobile phone does not have these new fields, which may lead to abnormal parsing of the fields sent by the mobile phone by the smartwatch.

[0254] In view of this, in the embodiments of the present application, on the basis of establishing a communication connection between the new version of the smartwatch and the old version of the mobile phone, the new version of the smartwatch can preferentially parse the old fields in the messages sent by the old version of the mobile phone and ignore the new fields that cannot be parsed, so as to ensure that the new version of the smartwatch can normally display the messages sent by the old version of the mobile phone. Among them, the smartwatch can determine whether the versions between the smartwatch and the mobile phone are consistent based on the version number of the smartwatch and the version number of the mobile phone.

[0255] It can be understood that the interfaces provided in the above embodiments are only examples and cannot limit the embodiments of the present application.

[0256] As described above in connection with Figure 5 - Figure 17 , the method provided in the embodiments of the present application has been described. Next, the apparatus for executing the above method provided in the embodiments of the present application will be described. As Figure 18 shown, Figure 18 FIG. is a schematic structural diagram of a message collaboration apparatus provided in an embodiment of the present application. The message collaboration apparatus may be a terminal device in the embodiments of the present application, or a chip or a chip system in the terminal device.

[0257] As Figure 18 shown, the message collaboration apparatus 1800 may be used in a communication device, a circuit, a hardware component, or a chip. The message collaboration apparatus 1800 includes: a display unit 1801, a processing unit 1802, a communication unit 1803, etc. Among them, the display unit 1801 is used to support the display steps of the message collaboration method; the processing unit 1802 is used to support the message collaboration apparatus 1800 to execute the information processing steps; the communication unit 1803 is used to support the message collaboration apparatus 1800 to execute steps such as receiving or sending messages.

[0258] The message collaboration apparatuses of the first electronic device (or the second electronic device) described in the embodiments of the present application may all include Figure 18 the units described in the corresponding embodiments.

[0259] Specifically, the processing unit 1802 and the display unit 1801 may be integrated together, and communication may occur between the processing unit 1802 and the display unit 1801.

[0260] In a possible implementation manner, the message collaboration apparatus 1800 may further include: a storage unit 1804. Among them, the storage unit 1804 may include one or more memories, and the memory may be a device or a circuit for storing programs or data.

[0261] The storage unit 1804 may exist independently and be connected to the processing unit 1802 through a communication bus. The storage unit 1804 may also be integrated with the processing unit 1802.

[0262] Taking the message collaboration device 1800 as an example of the chip or chip system of the terminal device in the embodiments of the present application, the storage unit 1804 may store computer-executable instructions of the method of the terminal device, so that the processing unit 1802 executes the method of the terminal device in the above embodiments. The storage unit 1804 may be a register, a cache, or a random access memory (RAM), etc., and the storage unit 1804 may be integrated with the processing unit 1802. The storage unit 1804 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, and the storage unit 1804 may be independent of the processing unit 1802.

[0263] In a possible implementation manner, the message collaboration device 1800 may further include: a communication unit 1803. Wherein, the communication unit 1803 is used to support the message collaboration device 1800 to interact with other devices. Exemplarily, when the message collaboration device 1800 is a terminal device, the communication unit 1803 may be a communication interface or an interface circuit. When the message collaboration device 1800 is a chip or chip system in the terminal device, the communication unit 1803 may be a communication interface. For example, the communication interface may be an input / output interface, a pin, or a circuit, etc.

[0264] The device in this embodiment can correspondingly be used to execute the steps executed in the above method embodiments, and its implementation principle and technical effects are similar, and will not be elaborated here.

[0265] Figure 19 This is a schematic diagram of the hardware structure of another terminal device provided by the embodiments of the present application. As Figure 19 shown, the terminal device includes a processor 1901, a communication line 1904, and at least one communication interface ( Figure 19 exemplarily taking the communication interface 1903 as an example for illustration).

[0266] The processor 1901 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the solution of the present application.

[0267] The communication line 1904 may include a circuit for transmitting information between the above components.

[0268] The communication interface 1903 uses any transceiver-like device for communicating with other devices or communication networks, such as Ethernet, wireless local area networks (WLAN), etc.

[0269] Optionally, the terminal device may further include a memory 1902.

[0270] The memory 1902 can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or it can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory can exist independently and be connected to the processor through the communication line 1904. The memory can also be integrated with the processor.

[0271] Among them, the memory 1902 is used to store computer execution instructions for implementing the solution of this application, and is controlled by the processor 1901 for execution. The processor 1901 is used to execute the computer execution instructions stored in the memory 1902, thereby implementing the method provided by the embodiments of this application.

[0272] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not make specific limitations thereto.

[0273] In a specific implementation, as an embodiment, the processor 1901 may include one or more CPUs, such as Figure 19 CPU0 and CPU1 in

[0274] In a specific implementation, as an embodiment, the terminal device may include multiple processors, such as Figure 19The processors 1901 and 1905 therein. Each of these processors can be a single-CPU processor or a multi-CPU processor. The processors herein can refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).

[0275] In the above embodiments, the instructions stored in the memory for the processor to execute can be implemented in the form of a computer program product. Among them, the computer program product can be pre-written in the memory or downloaded and installed in the memory in software form.

[0276] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are fully or partially generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from a website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server or data center that includes one or more integrated available media. For example, the available medium can include magnetic media (such as floppy disks, hard disks, or magnetic tapes), optical media (such as digital versatile discs (DVDs)), or semiconductor media (such as solid state disks (SSDs)), etc.

[0277] The embodiments of the present application also provide a computer-readable storage medium. The methods described in the above embodiments can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. The computer-readable medium can include a computer storage medium and a communication medium, and can also include any medium that can transfer a computer program from one place to another. The storage medium can be any target medium accessible by a computer.

[0278] As a possible design, a computer-readable medium may include a compact disc read-only memory (CD-ROM), RAM, ROM, EEPROM, or other optical disc storage; the computer-readable medium may include magnetic disk storage or other magnetic disk storage devices. Moreover, any connecting wire may also be appropriately referred to as a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of the medium. As used herein, magnetic disks and optical discs include optical discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where magnetic disks typically reproduce data magnetically, while optical discs use lasers to optically reproduce data.

[0279] The above combinations should also be included within the scope of computer-readable media. The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present invention can easily think of changes or substitutions, which should all be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims

1. A message collaboration method, characterized in that Applied to a message collaboration system, the message collaboration system includes: a first electronic device and a second electronic device, and the method includes: The first electronic device establishes a communication connection with the second electronic device; The first electronic device sends a first message to the second electronic device, and the first message is included in the first message list of the first electronic device; The second electronic device displays the first message in the form of a card; The first electronic device sends a second message to the second electronic device, and the second message is included in the first message list of the first electronic device; wherein, the first message and / or the second message is a notification message of a first application, and the first application is an application in the first electronic device; The second electronic device displays the second message in the form of a card; and / or, when the first message further carries a first control, and the first control is used to trigger the display of the first message again after a first duration, then when the second message is triggered to be displayed based on the first control, the second electronic device does not display the second message in the form of a card and displays the second message in a fifth message list; When the second electronic device displays the second message in the form of a card, the method further includes: When the first electronic device determines that the message content of the first message has not changed, the first electronic device no longer sends the first message to the second electronic device; and / or, the method further includes: The first electronic device combines the first message in the first message list with the second message into a fourth message; The first electronic device sends the fourth message and a first identifier to the second electronic device, and the first identifier is used to indicate that the fourth message is not displayed in the form of a card in the second electronic device; the second electronic device does not display the fourth message in the form of a card; The second electronic device displays the fourth message in a sixth message list.

2. The method according to claim 1, wherein The method further includes: When the first electronic device determines that the message content of the first message has changed and sends a first instruction to the second electronic device; The second electronic device removes the first message from the second message list according to the first instruction to obtain a third message list; the third message list includes the second message; The first electronic device sends a third message and a first identifier to the second electronic device; the first identifier is used to indicate that the third message is not displayed in the form of a card in the second electronic device; The second electronic device displays the third message in the third message list according to the first identifier to obtain a fourth message list; wherein, the fourth message list includes the third message and the second message.

3. The method according to claim 2, characterized in that, The first electronic device includes a first module. When the first electronic device determines that the message content of the first message has not changed, the first electronic device no longer sends the first message to the second electronic device, including: When the first electronic device determines that the message content of the first message has not changed, the first electronic device sets a second identifier for the first message; The first electronic device sends the first message and the second identifier to the first module; The first module determines, based on the second identifier, not to send the first message to the second electronic device again.

4. The method according to claim 3, wherein The first electronic device sending the third message and the first identifier to the second electronic device includes: The first electronic device sends the third message and the first identifier to the first module; The first module determines, based on the first identifier, to send the third message and the first identifier to the second electronic device.

5. A message collaboration method, characterized in that, Applied to a first electronic device, the method includes: The first electronic device establishes a communication connection with a second electronic device; The first electronic device sends a first message to the second electronic device, and the first message is included in the first message list of the first electronic device; The first electronic device sends a second message to the second electronic device, and the second message is included in the first message list of the first electronic device; wherein, the first message and / or the second message is a notification message of a first application, and the first application is an application in the first electronic device; When the first electronic device determines that the message content of the first message has not changed, the first electronic device does not send the first message to the second electronic device again; and / or, when the first message further carries a first control, and the first control is used to trigger the first message to be displayed again after a first duration, then when the second message is triggered to be displayed based on the first control, the first electronic device further instructs the second electronic device not to display the second message in the form of a card; and / or, the method further includes: The first electronic device combines the first message and the second message in the first message list into a fourth message; The first electronic device sends the fourth message and a first identifier to the second electronic device, and the first identifier is used to indicate that the fourth message is not displayed in the form of a card in the second electronic device.

6. The method according to claim 5, characterized in that, The method further includes: When the first electronic device determines that the message content of the first message has changed, and sends a first instruction to the second electronic device; the first instruction is used to instruct the second electronic device to remove the first message from the second message list to obtain a third message list; the third message list includes the second message; The first electronic device sends a third message and a first identifier to the second electronic device; the first identifier is used to indicate that the third message is not displayed in the form of a card in the second electronic device; the third message and the second message are included in the fourth message list of the second electronic device.

7. The method according to claim 6, wherein The first electronic device includes a first module. When the first electronic device determines that the message content of the first message has not changed, the first electronic device no longer sends the first message to the second electronic device again, including: When the first electronic device determines that the message content of the first message has not changed, the first electronic device sets a second identifier for the first message; The first electronic device sends the first message and the second identifier to the first module; The first module determines, based on the second identifier, not to send the first message to the second electronic device again.

8. The method according to claim 7, wherein The first electronic device sending the third message and the first identifier to the second electronic device includes: The first electronic device sends the third message and the first identifier to the first module; The first module determines, based on the first identifier, to send the third message and the first identifier to the second electronic device.

9. A message collaboration method, characterized in that Applied to the second electronic device, the method includes: The second electronic device establishes a communication connection with the first electronic device; The second electronic device receives the first message from the first electronic device, and the first message is included in the first message list of the first electronic device; The second electronic device displays the first message in the form of a card; The second electronic device receives the second message from the first electronic device, and the second message is included in the first message list of the first electronic device; wherein, the first message and / or the second message is a notification message of a first application, and the first application is an application in the first electronic device; The second electronic device displays the second message in the form of a card; and / or, when the first message also carries a first control, and the first control is used to trigger the first message to be displayed again after a first duration, then when the second message is triggered to be displayed based on the first control, the second electronic device does not display the second message in the form of a card and displays the second message in a fifth message list; When the second electronic device displays the second message in the form of a card, the method further includes: When the message content of the first message has not changed, the second electronic device does not receive the first message in the first message list; and / or, the method further includes: The second electronic device receives the fourth message and the first identifier from the first electronic device, where the first identifier is used to indicate that the fourth message is not displayed in the form of a card in the second electronic device, and the fourth message is obtained by merging the first message and the second message; the second electronic device does not display the fourth message in the form of a card; The second electronic device displays the fourth message in a sixth message list.

10. The method according to claim 9, wherein The method further includes: The second electronic device receives a first instruction sent by the first electronic device, where the first instruction is sent by the first electronic device when the message content of the first message has changed; The second electronic device removes the first message from the second message list according to the first instruction, obtaining a third message list; the third message list includes the second message; The second electronic device receives a third message and a first identifier from the first electronic device, where the first identifier is used to indicate that the third message is not displayed in the form of a card on the second electronic device; The second electronic device displays the third message in the third message list according to the first identifier, obtaining a fourth message list; wherein, the fourth message list includes the third message and the second message.

11. An electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, the electronic device is caused to execute the method according to any one of claims 5-8, or execute the method according to any one of claims 9-10.

12. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, the computer is caused to execute the method according to any one of claims 5-8, or execute the method according to any one of claims 9-10.

Images