WO2022127638A1

WO2022127638A1 - Unread message management method and device

Info

Publication number: WO2022127638A1
Application number: PCT/CN2021/135787
Authority: WO
Inventors: 汪舒凡
Original assignee: 华为技术有限公司
Priority date: 2020-12-15
Filing date: 2021-12-06
Publication date: 2022-06-23
Also published as: CN114640741A

Abstract

Embodiments of the present application relate to the technical field of communications, and provide an unread message management method and device. In the present application, unread messages of a target application are viewed together by means of a split-screen window, thereby improving the efficiency of a user for processing the unread messages, and avoiding missing important messages. The specific solution is: a terminal device displaying a first interface of a first application, the first interface comprising a first object identifier and a second object identifier, and the first object identifier having an unread message; receiving a first operation; and in response to the first operation, displaying a second interface of a first application, the second interface comprising the first object identifier, the second object identifier, and a first window, and the first window displaying the first object identifier. The method and device of the embodiments of the present application are used for unread message management and processing.

Description

Method and device for managing unread messages

This application claims the priority of the Chinese patent application with the application number 202011482586.1 and the application title "A method and apparatus for managing unread messages", which was submitted to the State Intellectual Property Office on December 15, 2020, the entire contents of which are incorporated by reference in this application.

technical field

The embodiments of the present application relate to the field of communication technologies, and in particular, to a method and device for managing unread messages.

Background technique

At present, many applications in terminal devices, such as the applications that come with Huawei mobile phones and third-party applications, all have a message sending and receiving mechanism. As shown in Figure 1, since the short message application in the terminal device receives many messages, the user may not be able to process all the received messages in time. Therefore, in the message viewing interface of the short message application, the distribution of unread messages is scattered.

In this way, when the user subsequently processes the unread messages, he needs to find and lock the specific location of the unread messages that need to be processed among the scattered unread messages, and then perform subsequent processing on the unread messages, for example, replying to the unread messages or Mark unread messages as read. However, when a user searches for unread messages in a message viewing interface of an existing application, there may be a risk of missing important unread messages, resulting in low efficiency for users to process unread messages.

SUMMARY OF THE INVENTION

Embodiments of the present application provide a method and device for managing unread messages, which can centrally view unread messages of a target application through a split-screen window, thereby improving the efficiency of users in processing unread messages and avoiding omitting important messages.

In order to achieve the above purpose, the embodiment of the present application adopts the following technical solutions:

In a first aspect, an embodiment of the present application provides a method for managing unread messages. The method includes: a terminal device displays a first interface of a first application, where the first interface includes a first object identifier and a second object identifier, wherein the first interface An object identifier has an unread message; receiving a first operation; in response to the first operation, displaying a second interface of the first application, the second interface including the first object identifier, the second object identifier and a first window, in the first window The first object identification is displayed.

In this solution, the terminal device can display the first window in response to the first operation, and the first window displays the first object identifier with the unread message. That is, the user can directly view the unread messages in the first application through the first window. In this way, through the first window, the user can centrally process unread messages in the first application, thereby improving the efficiency of the user in processing unread messages in the first application and avoiding omitting important messages.

In a possible design, after the terminal device starts the first application, the second interface of the first application is automatically displayed. In this way, the user can directly view unread messages through the first window in the second interface when opening the first application.

In a possible design, the number of unread messages corresponding to the first object identifier is also displayed in the first window. In this way, through the first window, the user can directly view the number of unread messages corresponding to the first object identifier.

In a possible design, the unread mark of the first object identification is also displayed in the second interface. In this way, based on the unread mark, the user can directly determine the identification of the object with the unread message.

In a possible design, the first interface further includes a third object identification, wherein the third object identification has unread messages; the third object identification is also displayed in the first window. If the third object identifier is topped on the first interface, in the first window, the arrangement priority of the first object identifier is higher than the arrangement priority of the third object.

In this solution, since the third object identifier is on top in the first interface, the user can directly view the unread messages of the third object identifier in the first interface. In this way, by lowering the arrangement priority of the third object identifier in the first window, the user can view more unread messages in the first window that cannot be viewed in the first interface.

In a possible design, the terminal device displays a third interface of the first application in response to the user's sliding operation on the first interface, and the third interface includes a fourth object identifier, wherein the fourth object identifier has an unread message; A fourth object identifier is also displayed in a window, wherein the arrangement priority of the fourth object identifier in the first window is greater than the arrangement priority of the first object.

In this solution, since the fourth object identifier is displayed in the third interface of the first application displayed in response to the user's sliding operation on the first interface, the user cannot directly view the fourth object identifier in the first interface of unread messages. In this way, by increasing the priority of arrangement of the fourth object identifier in the first window, the user can view more unread messages in the first window that cannot be viewed in the first interface.

In a possible design, the higher the priority of sorting the object IDs with the larger number of unread messages; the higher the ranking priority of the IDs with higher contact frequency.

In a possible design, the method further includes: in response to a second operation by the user on the first object identifier in the first window, the terminal device no longer displays the first object identifier in the first window, and does not display the first object identifier in the second interface. The unread mark of the first object identification is then displayed.

In this solution, in response to the user's second operation on the first object identifier in the first window, the terminal device can directly mark all unread messages corresponding to the first object identifier as read. In this way, the first object identification is no longer displayed in the first window, and the unread mark of the first object identification is no longer displayed in the second interface. For example, if the user is not interested in the unread message corresponding to the first object identifier, the user can directly perform the second operation, so that the terminal device no longer displays the first object identifier in the first window in response to the second operation, and displays the first object identifier in the second interface. The unread mark for the first object ID no longer appears in .

In a possible design, the second operation includes an operation of dragging the first object identifier in the first window out of the first window.

In a possible design, the method further includes: in response to a third operation by the user on the first object identifier in the first window, the terminal device displays a details interface of the unread message corresponding to the first object identifier. In this way, the user can directly view the detailed content of the unread message corresponding to the first object identifier.

In a possible design, the method further includes: in response to a fourth operation by the user on the first object identifier in the first window, the terminal device displays a preview interface of the unread message corresponding to the first object identifier. In this way, the user can preview the unread messages corresponding to the first object identifier, and then view the detailed content of some of the unread messages according to requirements.

In a possible design, the first object identifier has X unread messages, and the method further includes: if one unread message in the X unread messages is viewed, then the first object identifier corresponds to the unread message of the unread message. The number becomes X-1.

In a possible design, the first operation includes an operation on a preset control or a preset area on the first interface. Here, the terminal device displays the first window on the second interface by responding to an operation on a preset control or a preset area on the first interface.

In a possible design, the first window is a system split-screen window, and the system split-screen window further includes unread messages of the second application.

In a possible design, the unread messages of the first application in the system split-screen window come from the sub-database corresponding to the first application in the system database; the unread messages of the second application in the system split-screen window come from the system database The sub-database corresponding to the second application.

In this solution, since the data of the system split-screen window comes from the system database, and the system database includes sub-databases corresponding to each application, the system split-screen window may include unread messages of another application. The unread messages of each application come from sub-databases corresponding to each application in the system database respectively.

In a possible design, the first window is an application split screen window, and the method further includes: the terminal device starts the second application; and displays a first interface of the second application, where the first interface does not include the application split screen window.

In this solution, since the data of the application split-screen window comes from the application database corresponding to the application, not every application displays the application split-screen window. If the second application does not have an application split screen window, the first interface of the second application does not include the application split screen window.

In a possible design, the method further includes: in response to the fifth operation, the terminal device hides the first window. Here, in the case that the user does not need to view the first window, the terminal device may hide the first window. Afterwards, if the user needs to view the first window, the terminal device may redisplay the first window in response to the user's first operation.

In a second aspect, an embodiment of the present application provides a terminal device, the terminal device includes: a display screen for displaying an interface; one or more processors and one or more memories; the one or more memories are combined with one or more memories. A plurality of processors are coupled, and one or more memories are used to store computer program codes, and the computer program codes include computer instructions. When one or more processors execute the computer instructions, the terminal device executes any one of the possible implementations of the first aspect. A method for managing unread messages in the design.

In a third aspect, an embodiment of the present application provides a computer storage medium, including computer instructions, when the computer instructions are executed on a terminal device, the terminal device can execute the unread message in any possible design of the first aspect. management method.

In a fourth aspect, embodiments of the present application provide a computer program product, which, when the computer program product runs on a computer, enables the computer to execute the method for managing unread messages in any possible design of the first aspect.

For the beneficial effects corresponding to the above-mentioned other aspects, reference may be made to the description of the beneficial effects of the method, which will not be repeated here.

Description of drawings

Fig. 1 is a kind of application interface schematic diagram that provides;

FIG. 2 is a schematic structural diagram of a terminal device according to an embodiment of the present application;

3 is a schematic flowchart of an unread message management method provided by an embodiment of the present application;

4 is a schematic diagram of an application interface provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of another application interface provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of another application interface provided by an embodiment of the present application;

FIG. 7 is a schematic diagram of another application interface provided by an embodiment of the present application;

FIG. 8 is a schematic diagram of another application interface provided by an embodiment of the present application;

FIG. 9 is a schematic diagram of another application interface provided by an embodiment of the present application;

FIG. 10 is a schematic diagram of another application interface provided by an embodiment of the present application;

FIG. 11 is a schematic diagram of another application interface provided by an embodiment of the present application;

FIG. 12 is a schematic diagram of another application interface provided by an embodiment of the present application;

13 is a schematic diagram of a system split screen window in an application switching process provided by an embodiment of the present application;

14 is a schematic diagram of an application split-screen window in an application switching process provided by an embodiment of the present application;

FIG. 15 is a schematic diagram of a process of splitting windows in a display system according to an embodiment of the present application;

16 is a schematic flowchart of a system split-screen window configuration provided by an embodiment of the present application;

17 is a schematic diagram of a configuration process of a system split-screen window according to an embodiment of the present application;

18 is a schematic diagram of a process of displaying an application split-screen window according to an embodiment of the present application;

FIG. 19 is a schematic structural diagram of a terminal device provided by an embodiment of the application;

FIG. 20 is another schematic structural diagram of a terminal device provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. Wherein, in the description of the embodiments of the present application, unless otherwise stated, “/” means or means, for example, A/B can mean A or B; “and/or” in this document is only a description of the associated object The association relationship of , indicates that there can be three kinds of relationships, for example, A and/or B, can indicate that A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "plurality" refers to two or more than two.

Hereinafter, the terms "first" and "second" are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance or implying the number of indicated technical features. Thus, a feature defined as "first", "second" may expressly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.

The method for managing unread messages provided by the embodiments of the present application can be applied to mobile phones, tablet computers, wearable devices, vehicle-mounted devices, augmented reality (AR)\virtual reality (VR) devices, and notebook computers. , an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a netbook, a personal digital assistant (personal digital assistant, PDA) and other terminal devices, the embodiments of the present application do not impose any restrictions on this.

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

It can be understood that the structures illustrated in the embodiments of the present application do not constitute a specific limitation on the terminal device 100 . In other embodiments of the present application, the terminal device 100 may include more or less components than those shown in the drawings, or combine some components, or separate some components, or arrange different components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

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

The controller may be the nerve center and command center of the terminal device 100 . The controller can generate an operation control signal according to the instruction operation code and timing signal, and complete the control of fetching and executing instructions.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in processor 110 is cache memory. This memory may hold instructions or data that have just been used or recycled by the processor 110 . If the processor 110 needs to use the instruction or data again, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby increasing the efficiency of the system.

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

It can be understood that the interface connection relationship between the modules illustrated in the embodiments of the present application is only a schematic illustration, and does not constitute a structural limitation of the terminal device 100 . In other embodiments of the present application, the terminal device 100 may also adopt different interface connection manners in the foregoing embodiments, or a combination of multiple interface connection manners.

The wireless communication function of the terminal device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modulation and demodulation processor, the baseband processor, and the like.

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

The mobile communication module 150 may provide a wireless communication solution including 2G/3G/4G/5G, etc. applied on the terminal device 100 . The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA) and the like. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, filter and amplify the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and then turn it into an electromagnetic wave for radiation through the antenna 1 . In some embodiments, at least part of the functional modules of the mobile communication module 150 may be provided in the processor 110 . In some embodiments, at least part of the functional modules of the mobile communication module 150 may be provided in the same device as at least part of the modules of the processor 110 .

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

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

In some embodiments, the antenna 1 of the terminal device 100 is coupled with the mobile communication module 150, and the antenna 2 is coupled with the wireless communication module 160, so that the terminal device 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technologies may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), broadband Code Division Multiple Access (WCDMA), Time Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC , FM, and/or IR technology, etc. The GNSS may include a global positioning system (global positioning system, GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (quasi -zenith satellite system, QZSS) and/or satellite based augmentation systems (SBAS).

In some embodiments, the terminal device 100 may communicate with other terminal devices and servers through the mobile communication module 150 and/or the wireless communication module 160 .

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

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

The terminal device 100 can realize the shooting function through the ISP, the camera 193, the video codec, the GPU, the display screen 194 and the application processor.

The NPU is a neural-network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transfer mode between neurons in the human brain, it can quickly process the input information and can continuously self-learn. Applications such as intelligent cognition of the terminal device 100 can be implemented through the NPU, such as image recognition, face recognition, speech recognition, text understanding, and the like.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal device 100 . The external memory card communicates with the processor 110 through the external memory interface 120 to realize the data storage function. For example to save files like music, video etc in external memory card.

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

The terminal device 100 may implement audio functions through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, an application processor, and the like. Such as music playback, recording, etc.

The pressure sensor 180A is used to sense pressure signals, and can convert the pressure signals into electrical signals. In some embodiments, the pressure sensor 180A may be provided on the display screen 194 . There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, and the like. The capacitive pressure sensor may be comprised of at least two parallel plates of conductive material. When a force is applied to the pressure sensor 180A, the capacitance between the electrodes changes. The terminal device 100 determines the intensity of the pressure according to the change in capacitance. When a touch operation acts on the display screen 194, the terminal device 100 detects the intensity of the touch operation according to the pressure sensor 180A. The terminal device 100 may also calculate the touched position according to the detection signal of the pressure sensor 180A. In some embodiments, touch operations acting on the same touch position but with different touch operation intensities may correspond to different operation instructions. For example, when a touch operation whose intensity is less than the first pressure threshold acts on the short message application icon, the instruction for viewing the short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold acts on the short message application icon, the instruction to create a new short message is executed.

The fingerprint sensor 180H is used to collect fingerprints. The terminal device 100 can use the collected fingerprint characteristics to realize fingerprint unlocking, accessing application locks, taking photos with fingerprints, answering incoming calls with fingerprints, and the like.

Touch sensor 180K, also called "touch panel". The touch sensor 180K may be disposed on the display screen 194 , and the touch sensor 180K and the display screen 194 form a touch screen, also called a “touch screen”. The touch sensor 180K is used to detect a touch operation on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to touch operations may be provided through display screen 194 . In other embodiments, the touch sensor 180K may also be disposed on the surface of the terminal device 100 , which is different from the position where the display screen 194 is located.

The keys 190 include a power-on key, a volume key, and the like. Keys 190 may be mechanical keys. It can also be a touch key. The terminal device 100 may receive key input and generate key signal input related to user settings and function control of the terminal device 100 .

Motor 191 can generate vibrating cues. The motor 191 can be used for incoming call vibration alerts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, playing audio, etc.) can correspond to different vibration feedback effects. The motor 191 can also correspond to different vibration feedback effects for touch operations on different areas of the display screen 194 . Different application scenarios (for example: time reminder, receiving information, alarm clock, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

The indicator 192 can be an indicator light, which can be used to indicate the charging state, the change of the power, and can also be used to indicate a message, a missed call, a notification, and the like.

An embodiment of the present application provides a method for managing unread messages. A mobile phone can display a split-screen window corresponding to a target application according to a user's operation, so that the user can directly and conveniently view the number of unread messages and the corresponding unread messages through the split-screen window. Contact objects and other related information to facilitate users to manage unread messages.

The target application includes an application that can send and receive messages. In some embodiments, the target application may be a system application (eg, a short message application, a calling application, etc.) built in the mobile phone, or a third-party application (eg, WeChat, Alipay, etc.). In other embodiments, the target application may be a communication application (eg, QQ, Dingding, etc.), or an information application (eg, Sina News, Toutiao, etc.). Among them, the system applications that come with the mobile phone are usually pre-installed in the mobile phone before the mobile phone leaves the factory. This embodiment of the present application does not limit this.

For ease of understanding, the following embodiments of the present application will take a mobile phone with the structure shown in FIG. 2 as an example, and take the target application as a short message application (hereinafter referred to as a short message application) built in the mobile phone as an example, and the embodiments of the present application will be described with reference to the accompanying drawings. The provided unread message management method will be explained in detail. As shown in Figure 3, the method includes the following steps:

S301, the mobile phone opens the first interface of the target application.

In some embodiments, the mobile phone can open the first interface of the target application in response to the user's preset operation. The preset operation may be an operation on a certain target application icon, and in response to the preset operation, the mobile phone opens a corresponding application interface, that is, the first interface of the target application. As shown in FIG. 4 , in response to the user's operation on the short message application icon 401 shown in (a) of FIG. 4 , the mobile phone opens the short message application interface shown in (b) of FIG. 4 .

The preset operation for opening the first interface of the target application may be a single-click operation, a double-click operation, a sliding operation, or a long-press operation on the application icon, and may also be a voice input, a gesture operation, or other forms of operation. This embodiment of the present application does not limit this.

The first interface of the target application may include an identifier of the contact object (which may be referred to as an object identifier). The identification of the contact object may be the avatar, icon or name of the contact object. Optionally, if the identifier of a contact object has unread messages, the first interface may further include the number of unread messages.

Exemplarily, in the application interface of the embodiment of the present application, an object identifier with unread messages is called a first object identifier, and an object identifier where all messages are read messages is called a second object identifier. For example, in the SMS application interface shown in (b) of FIG. 4 , the first object identifier includes notification message, Huawei notification, contact object 2 and contact object 3, and the second object identifier includes contact object 1 and contact object 4.

Exemplarily, the short message application interface as shown in (b) in Figure 4 includes the identification of the contact object and the number of unread messages corresponding to the identification of the contact object, and the user can view the contact object and the number of corresponding unread messages. . The user clicks on the contact object's avatar, name, or the number of unread messages, etc., to enter the message details interface to view the specific content of the message.

Optionally, the user can also directly query all messages sent by the contact object by entering the full name of the contact object in the search bar 402; or the user can enter a keyword in the contact object or message content to directly query the keyword containing the keyword. news.

Optionally, the mobile phone may display an unread mark in front of the avatar of the contact object corresponding to the unread message. The unread mark may be a dot as shown in (b) in FIG. 4 , or may be other mark symbols such as “!”, which are not limited in this application.

Alternatively, the phone can also display the total number of unread messages next to "Information". As shown in (b) of Figure 4, N is the total number of all unread messages.

S302. After the mobile phone detects the first operation of the user, a split screen window is displayed, and the split screen window includes the identifier of the contact object with the unread message.

The interface after the mobile phone displays the split-screen window in response to the first operation may be referred to as the second interface of the target application, and the second interface of the target application includes the object identifier (ie, the first object identifier) with unread messages, all The messages are the object identifier (ie, the second object identifier) of the read message and the split screen window. The split screen window is also referred to as the first window in this application. Object identifiers with unread messages are collectively displayed in the split-screen window, and object identifiers (ie, second object identifiers) whose messages are all read messages are not included in the split-screen window.

Wherein, the identification of the contact object with unread messages may include identifications such as avatars, icons, names or controls corresponding to the contact objects with unread messages.

Optionally, the split screen window may further include the number of unread messages corresponding to the identifier of each contact object.

Optionally, the mobile phone may also display an unread mark in front of the avatar of the contact object corresponding to the unread message in the second interface. The unread mark may be a dot as shown in (b) in FIG. 5 , or may be other mark symbols such as "!".

Optionally, the unread mark of the first object identifier may also be displayed in the split screen window.

In this embodiment of the present application, the contact object may be a contact person or a message sender, where the message sender may include a subscription number, notification information, application information, or system information, and the like. Exemplarily, in communication applications such as SMS applications, contact objects usually include contacts, subscription numbers, notification information, etc.; in other non-communication applications such as health applications, contact objects usually include notification information, application information, and system information.

In some embodiments, the user's first operation includes a user's triggering operation on a specific area, a user's triggering operation on a physical key, voice input, gesture operation, and other operations capable of displaying a split-screen window. This application does not limit the type of the first operation. In addition, a specific area may also be called a hot area or other names, which are not limited in this embodiment of the present application.

Exemplarily, as shown in FIG. 5 , the mobile phone may display a split-screen window 502 in response to a user's triggering operation on a specific area 501 in the application interface.

Wherein, in some embodiments, when the application interface as shown in (a) in FIG. 5 is displayed on the mobile phone, the user can trigger the specific area 501 by clicking, double-clicking or pressing pressure, etc., so that the mobile phone displays as shown in FIG. 5 In the second interface of the short message application shown in (b), the second interface of the short message application includes an object identifier with unread messages (that is, the first object identifier), and all messages are the object identifiers of read messages (that is, the first object identifier). two object identifiers) and a split screen window 502. The user can also trigger the specific area 501 through voice input, gesture operation or other triggering operations, so that the mobile phone displays the split-screen window 502 . The embodiments of the present application also do not limit the manner in which the mobile phone displays a split-screen window in response to a user triggering a specific area.

In the embodiment of the present application, the above-mentioned specific area may be set at a plurality of different positions on the application interface, so as to facilitate the user to call out the split-screen window by triggering the specific area. In some embodiments, as shown in (a) of FIG. 6, a specific area may be set on the right side of the application interface. In other embodiments, as shown in (b) of FIG. 6 , the specific area may also be set at other positions of the application interface, such as the left or lower side of the application interface.

Certain areas can be provided in different shapes or forms. In some embodiments, as shown in (a) of FIG. 6 , the specific area is set as a rectangle. In other embodiments, as shown in (c) of FIG. 6 , the specific area may also be set as a circle or a triangle, and the shape of the specific area is not limited in this application. In other embodiments, the specific area may also be set in the form of a control or in other forms, and the application does not limit the form of the specific area.

In this embodiment of the present application, the split screen window includes identifiers of contact objects with unread messages, and the number of unread messages corresponding to the identifier of each contact object. As shown in the split screen window 502 in (b) of FIG. 5 , the number of unread messages can be displayed in the form of superscripts on the upper right of the identification (eg avatar) of the contact object with unread messages, or it can be displayed in other This is not limited in this application.

It should be noted that when there are many contact objects, all contact objects cannot be displayed on the current application interface, that is, the identifiers of some contact objects are displayed at the bottom of the application interface, and users can view all contact objects by sliding the screen up and down. . Exemplarily, in the interface shown in (a) of FIG. 6, the user cannot view the identification of the contact object (for example, contact object 5) displayed on the bottom layer, and the mobile phone can display the contact object 5 in response to the user's sliding operation. The third interface shown in (d) in FIG. 6 , so as to show the user the identification of the contact object that is not displayed in the interface shown in (a) in FIG. 6 , such as contact object 5 . In this embodiment of the present application, an identifier of a contact object (eg, contact object 5 ) that is not displayed in the current application interface is also referred to as a fourth object identifier.

The arrangement order of the contact objects corresponding to the unread messages in the split-screen window can be based on various sorting rules, so that the user can conveniently query the unread messages.

In some embodiments, the identities of contact objects with unread messages displayed in the split screen window may be ordered according to static rules. Static rules indicate that sorting is a way of sorting according to fixed criteria.

For example, the mobile phone can sort the identifiers of contact objects with unread messages in the split screen window according to the number of unread messages corresponding to the identifiers of the contact objects. The greater the number of unread messages, the higher the priority of the identification of the corresponding contact object in the split screen window, for example, the higher or higher the position of the identification of the contact object displayed in the split screen window. As shown in (a) of FIG. 7 , the number of unread messages corresponding to the “notification message” is the largest, and the identifier and related information of the “notification message” in the split screen window are ranked at the top.

For another example, the mobile phone may sort the identifiers of the contact objects in the split-screen window according to the contact frequency between the user and the contact objects. The higher the contact frequency between the user and the contact object, that is to say, the more times the user contacts the contact object, the higher the priority of the contact object's identification in the split screen window. For example, the contact object's identification is in the split screen The position displayed in the window is higher or higher. As shown in (b) in Figure 7, the user has the highest contact frequency with "contact object 3", followed by the contact frequency with "contact object 5 (not displayed in the current interface)", then the contact frequency of "contact object 3" is the second. The related information is arranged at the top in the split-screen window, and the related information of "contact object 5" is arranged in the second position in the split-screen window.

In other embodiments, the identities of contact objects with unread messages displayed in the split screen window may be sorted according to dynamic rules. Dynamic rules represent a way of sorting when there are sticky contact objects. Because in the application interface, the user can usually directly see the unread information corresponding to the identification of the top contact object, and it is less likely for the user to miss the unread information corresponding to the identification of the top contact object. Therefore, in the split screen window, you can Decreases the priority of the identification of the sticky contact object. In addition, sorting the identifiers of the contact objects with unread messages displayed in the split-screen window according to the dynamic rule sorting may not only lower the priority of the identifiers of the top contact objects, but also reduce the priority of the identifiers of the contact objects in the current application interface. The identities of the displayed contact objects are all prioritized in descending order. In this way, the ranking priority of the identifications of the contact objects at the bottom layer of the current application interface (that is, the contact objects not displayed in the current application interface) is increased, and the identification priority of the identifications of the contact objects displayed in the current application interface is decreased, so as to facilitate the user View the unread messages corresponding to the identifiers of the contact objects that are not displayed in the current application interface.

Exemplarily, as shown in (c) of FIG. 7 , "contact object 2" is a top contact object. In this embodiment of the present application, the identifier of the top contact object is also referred to as a third object identifier. That is to say, in the current application interface, the user can directly see whether the identification of the top contact object "Contact Object 2" has corresponding unread information. In this way, the user omits to process the unread information corresponding to the identification of "Contact Object 2". Information is less likely. Therefore, in the split-screen window, the priority of the identification of "contact object 2" can be lowered, the identification of the non-top contact object and the corresponding unread message are displayed first, and finally the identification of the top contact object and the corresponding unread message are displayed. . In this way, more unread messages corresponding to the identifiers of the contact objects that the user cannot directly view on the current application interface can be viewed through the split-screen window, thereby preventing the user from missing unread messages received earlier.

It should be noted that the sorting rule of the identifiers of the contact objects in the split-screen window may be pre-configured, or may be set by the user according to requirements. For example, a "sort option" 701 can be set on the split screen window, and the mobile phone can display a selection bar as shown in (d) in Figure 7 in response to the user's operation on the "sort option" 701. If the user selects "static sorting" , the next-level selection bar can be displayed, so that the user can sort the identifiers of the contact objects in the split-screen window according to his desired sorting rule. The user may also select the desired sorting rule by double-clicking the top of the split-screen window, gesture operation, voice input, and other methods, and the embodiment of the present application does not limit the manner in which the user sets the sorting rule.

Split-screen windows can be displayed in multiple locations on the screen. Exemplarily, a split screen window is usually displayed near a specific area. For example, split-screen windows can also be displayed on the top, bottom, or left side of the screen. The embodiment of the present application does not limit the display position of the split-screen window.

In some embodiments, as shown in (a) of FIG. 5 , the split screen window is displayed on top of the application interface. In other embodiments, when the split-screen window is displayed, the boundary of the application interface may also move with the split-screen window, so as to avoid the split-screen window from obscuring the application interface.

In addition, users can also drag and drop the split-screen window to any position on the application interface according to their needs. In addition, the user can also adjust the length and width of the split-screen window or the size of the contact object's avatar in the split-screen window as required, so that more messages that are not processed by the user are displayed in the split-screen window.

It should be noted that when the user does not need to view information such as unread messages through the split-screen window, the split-screen window can also be hidden, and when the user needs it, the mobile phone displays the split-screen window in response to the user's first operation. Exemplarily, the mobile phone can hide the split-screen window in response to a user's touch operation, voice input, or gesture input. Here, the operation of hiding the split screen window may also be referred to as the fifth operation.

It should also be noted that when the user exits the short message application, the split screen window may not disappear, and the identifiers of the contact objects with unread messages and the corresponding unread messages of the short message application are still displayed. Afterwards, if the user needs to close the split-screen window, the split-screen window can be closed by clicking a preset close option in the split-screen window, voice input, or gesture input, and other methods.

In some embodiments, the mobile phone can also automatically display a split-screen window by default when the target application is opened. For example, when the mobile phone opens the SMS application, a split-screen window is automatically displayed, and the split-screen window includes the identifiers of the contact objects with unread messages and the corresponding number of unread messages.

In other embodiments, the mobile phone can also directly display the split-screen window of the target application on the desktop in response to the user's specific operation on the application icon of the target application without opening the application interface of the target application. Therefore, without opening the application interface of the target application, the user can directly view the unread messages of the target application, and it is convenient for the user to process and manage the unread messages of the target application.

The above method describes that after the application interface of a certain target application is opened, the mobile phone displays a split-screen window containing relevant information of unread messages of the target application in response to the user's first operation. However, it can be understood that, on the desktop of the mobile phone (ie, when the application interface of any application is not opened), the mobile phone can also display a split-screen window in response to the user's first operation. In this case, the split-screen window may contain information about unread messages of various applications existing in the mobile phone.

The above describes the specific process that the mobile phone displays the split-screen window in response to the user's operation. The unread message management method described in the embodiment of the present application can centrally view all unread messages in a target application through a split-screen window, thereby improving the efficiency of the user in processing unread messages and avoiding missing important messages.

In addition, the method for managing unread messages described in the embodiments of the present application is more targeted, and does not need to pay attention to unread messages in applications that are not frequently used, which can further save the user's time and energy.

After displaying the split-screen window, the mobile phone can also process the unread message corresponding to the contact object displayed in the split-screen window in response to the user's operation. The methods described in the embodiments of the present application also include:

S303. After the mobile phone responds to the user's second operation on the identifier of the contact object in the split-screen window, the mobile phone marks the unread message corresponding to the identifier of the contact object as read.

In some embodiments, if the user is not interested in the unread message corresponding to the identifier of a certain contact object in the split screen window, the second operation may be performed. Wherein, the second operation may include dragging the contact object out of the split-screen window, gesture operation after clicking the identification of the contact object in the split-screen window, voice input, or other indications corresponding to the identification of the contact object in the split-screen window. Operations that are not of interest to read messages. This application does not limit the type of the second operation.

In this way, the identifier of the contact object is no longer displayed in the split-screen window, and in the application interface, the unread message corresponding to the identifier of the contact object is marked as read. For example, the unread mark in front of the unread message corresponding to the identifier of the contact object disappears, or the number of unread messages displayed behind the unread message disappears.

For example, since the messages in the "notification information" are generally not related to the user, the user is usually not interested in the unread messages corresponding to the "notification information". As shown in (a) in FIG. 8 , the user can drag the “notification information” logo out of the split screen window. In this way, as shown in (b) of FIG. 8 , information such as the identifier of “notification information” and the number of corresponding unread messages is no longer displayed in the split-screen window. In addition, in the application interface, the unread mark (eg, a small dot) in front of the "Notification Information" logo disappears, and the number of unread messages displayed behind the "Notification Message" logo also disappears. That is, after dragging the "notification message" logo out of the split screen window, the unread messages corresponding to the "notification message" logo are marked as read. In addition, the number of unread messages next to "Information" also changes from N to M, where the difference between N and M is the number of unread messages marked as read.

In other embodiments, the user may preview the content of the unread message before determining whether to mark the unread message as read. Exemplarily, in the case where the user may not be able to directly judge whether the unread message corresponding to the identifier of a certain contact object (for example, contact object 2) is interested, as shown in (a) of FIG. After the user performs operation 1 on the identification of the contact object, a message preview box 901 as shown in (b) of FIG. 9 is displayed. The operation 1 may be a click operation, voice input, gesture operation or other forms of operation. In the message preview box 901, the user can preview part of the content of the unread messages corresponding to the contact object 2, so as to determine whether these unread messages need to be processed. If, after previewing the unread messages, the user confirms that he is not interested in the unread messages corresponding to the identifier of the contact object 2 or does not need to process these unread messages, the user can, as shown in (c) of FIG. 9 , change the identifier of the contact object 2 Drag out the split screen window. After this, an application interface as shown in (d) in FIG. 9 is displayed, in which the unread mark in front of the logo of the contact object 2 disappears, and the number of unread messages behind the logo of the contact object 2 disappears . At the same time, the identification and related information of the contact object 2 are no longer displayed in the split screen window. In addition, the number of unread messages next to "Information" also changes from N to P, where the difference between N and P is the number of unread messages marked as read.

In this step, the mobile phone can directly mark the unread message corresponding to the identification of the contact object as read in response to the second operation of the user on the identification of the contact object in the split screen window that is not of interest. The operation is convenient and simple, and does not require the user to enter the details interface of the unread message. The user can directly mark the unread messages of no interest, such as useless messages or harassing messages, as read, which can effectively save the user's precious time and energy, and is convenient for the user. Concentrate on unread messages of no interest.

S304. After responding to the third operation by the user on the identifier of the contact object in the split screen window, the mobile phone displays an unread message corresponding to the identifier of the contact object.

In some embodiments, if the user is interested in the unread messages of a contact object in the split-screen window, the user may perform a third operation on the contact object, so that the mobile phone displays the unread message of the unread message in response to the third operation. Details interface, the details interface of the unread message displays the details of the unread message for the user to view or reply to the unread message corresponding to the identifier of the contact object. Referring to (a) in FIG. 10, if the user is interested in the unread message corresponding to the identification of the contact object 2, the user can perform a third operation, such as long-pressing the identification such as the avatar, icon, etc. of the contact object 2 in the split screen window, Or double-click the avatar, icon, etc. of the contact object 2 in the split screen window, or perform other gesture operations on the avatar, icon, etc. of the contact object 2. In this way, the mobile phone can display the details interface of the unread message as shown in (b) of FIG. 10 . In the details interface of unread messages, users can view the details of unread messages. Optionally, in the details interface of unread messages, the user can also reply to these messages.

In other embodiments, the mobile phone may also display a preview interface of unread messages in response to the user's fourth operation on the identification of the contact object in the split-screen window, so that the user can preview the content of the unread messages, so that the user can choose whether to enter the unread message or not. View the details of unread messages on the details interface of read messages. Wherein, preview information of the unread message, such as the beginning of the unread message, main content or keywords, etc., may be displayed in the preview interface.

For example, referring to (a) in FIG. 11 , if the user is interested in the unread message corresponding to the identification of the contact object 2, the user can first respond to the user's operation 1 on the identification of the contact object 2, such as click operation, voice input, Gesture operation or other forms of operation, a preview box 1101 of unread messages as shown in (b) of FIG. 11 is displayed. Within a preset time after the user previews the unread message, if the user wants to view the detailed content of the unread message, the mobile phone can respond to the user's identification of the contact object 2 or operation 2 of the unread message preview box 1101 to display the following: The details interface of the unread message shown in (d) in FIG. 11 is for the user to view the details of the unread message corresponding to the identifier of the contact object 2 . In some embodiments, in the details interface, the user can perform processing such as replying to unread messages. Wherein, operation 2 may also include a click operation (as shown in (c) in FIG. 11 ), voice input, gesture operation, or other forms of operation. In this embodiment of the present application, operation 1 is different from operation 2, and the present application does not limit the types of operation 1 and operation 2. The preset duration may be 1 minute, 45 seconds, or the like. Generally, the preset duration is not too long, and the embodiment of the present application does not limit the specific duration of the preset duration.

Optionally, after viewing the details of the unread message, if the user thinks that the unread message is important, and hopes to quickly find the message later, the user can also double-click the unread message, voice input, gesture input, or other means. Viewed messages are marked as unread again. In this way, the avatar of the contact object corresponding to the unread message in the split-screen window does not disappear, and the user can still quickly view the message through the split-screen window later.

In other embodiments, the mobile phone may also display a list of unread messages corresponding to the identification of the contact object in response to the user's operation on the identification of the contact object in the split screen window. Afterwards, if the user views an unread message corresponding to the identifier of the contact object, the number of unread messages corresponding to the identifier of the contact object in the split screen window is correspondingly reduced by one. For example, the number of unread messages corresponding to the identification of a contact object is X, if the mobile phone responds to the user's click operation on an unread message among the X unread messages, so that this unread message is viewed by the user, Then, the number of unread messages corresponding to the identifier of the contact object in the split screen window is reduced by one and becomes X-1. It can be understood that, correspondingly, the number of unread messages corresponding to the identifier of the contact object in the current application interface (ie, the second interface except the area of the split-screen window) is also reduced by one to X-1.

It can also be understood that, in still other embodiments, the mobile phone may not view unread messages through a split-screen window. For example, the user can view unread messages through the current application interface. If in the current application interface, the number of unread messages corresponding to the identifier of a contact object is X, and one of the unread messages is viewed by the user, the contact object's The number of unread messages corresponding to the identifier is reduced by one, and correspondingly, the number of unread messages corresponding to the identifier of the contact object in the split screen window is also reduced by one to X-1.

Wherein, if the above X unread messages are all viewed by the user, all unread messages corresponding to the identifier of the contact object have been read, and the identifier of the contact object may not be displayed in the split screen window.

In this step, the user can directly view the details of the unread messages of interest through the split-screen window, and does not need to query in sequence in the message list, and can quickly reply or process these unread messages of interest. Therefore, the split-screen window can effectively improve the user's efficiency in viewing, replying, or processing unread messages, thereby saving the user's time.

Through the method described above, the user can, according to different requirements, perform different operations on the identifiers of the contact objects with unread messages displayed in the split-screen window, and mark the unread messages corresponding to the identifiers of the contact objects that are not of interest as unread messages. Read, or display the detailed interface of unread messages of interest, so that users can more easily process and manage unread messages based on split-screen windows, improve users' handling and management of unread messages, and effectively save users' precious time .

In addition, in some embodiments, the above method can also be applied to the case where the system and the target application belong to different manufacturers. For example, when the system is a Huawei system and the target application is a third-party application (WeChat, Alipay, QQ, etc.), the above method is also applicable. As shown in (a) of FIG. 12 , when the target application is a third-party chat application, the split-screen window can still be displayed by the above method, which is convenient for the user to centrally manage and process unread messages.

In other embodiments, the above method can also be applied to applications with deep message catalogs. In such applications, because the message catalog is relatively deep, users usually need to perform multiple operations to view unread messages, and cannot directly view unread messages when the application interface is just opened, which takes a lot of time for users. For example, in a health application, users usually click the "My" option at the bottom right of the application interface to view the content of unread messages. Through the above method, as shown in (b) of FIG. 12 , in the health application, a split-screen window can also be displayed, and the relevant information of the unread messages can be displayed in the split-screen window. In this way, users can directly manage or process unread messages through the split-screen window, and do not need to spend time and effort to find a message interface. Thus, the efficiency of processing unread messages of the user is improved, and the precious time of the user is saved.

In this embodiment of the present application, the split-screen window may be a system split-screen window or an application split-screen window. The system split-screen window is drawn by the system of the mobile phone, and the data of unread messages displayed in the system split-screen window comes from the system database, which includes sub-databases corresponding to each application in the mobile phone. The application split screen window is drawn by the corresponding application, that is, the function is implemented by the developer of the corresponding application. The data of unread messages displayed in the application split screen window comes from the application database, and the application database includes relevant data corresponding to the application.

In some embodiments, if the split-screen window is a system split-screen window, the mobile phone can still display the system split-screen window after switching applications. It can also be understood that when any application is opened on the mobile phone, the system split-screen window can be displayed in response to the user's operation. As shown in Figure 13, the mobile phone first responds to the user's operation to open a first application, such as a short message application, and displays the application interface shown in (a) of Figure 13, wherein the identification of the contact object displayed in the system split screen window The data of unread messages comes from the sub-database corresponding to the SMS application in the system database. After that, the mobile phone opens a second application, such as a health application, in response to the user's operation, and displays the application interface as shown in (b) in FIG. 13 , wherein the system split screen window is the same as the system shown in (a) in FIG. The split-screen windows are the same. The difference is that the identification of the contact object displayed in the split-screen window of the system and the source of the data of unread messages have changed, which come from the sub-database corresponding to the health application in the system database.

Since the system split-screen window is drawn by the mobile phone system, when the mobile phone switches the first application to the second application in response to the user's operation, the system split-screen window displayed by the mobile phone in the application interface of the first application is different from that displayed in the second application. The system split-screen windows displayed in the application interface are usually consistent, for example, the initial shape, size, and display area of these system split-screen windows are consistent. Wherein, the identifier of the contact object displayed in the system split screen window and the data of the unread message respectively come from the sub-database corresponding to the current application in the system database.

It can also be understood that since the system database includes sub-databases corresponding to each application in the mobile phone, the split-screen window displayed by the mobile phone on the application interface of a target application, in addition to information such as unread messages corresponding to the target application, is included. In addition, information such as unread messages corresponding to other applications may also be included. For example, the system split-screen window displayed in the application interface of the SMS application may also include unread messages in other applications such as the health application.

In other embodiments, if the split-screen window is an application split-screen window, after the mobile phone switches applications, the application split-screen window may no longer be displayed. As shown in FIG. 14 , the mobile phone first opens a first application, such as a short message application, in response to the user's operation. If the SMS application is provided with an application split screen window, the mobile phone displays the application interface as shown in (a) in FIG. 14 , wherein the identification of the contact object and the data of unread messages displayed in the application split screen window come from the SMS application application database. After that, the mobile phone opens a second application, such as a health application, in response to the user's operation. If the health application does not have an application split-screen window, the mobile phone displays the application interface (also referred to as the first interface of the second application) as shown in (b) in FIG. 14 , wherein the mobile phone no longer displays the application split-screen window. .

Since the application split screen window is drawn by the application manufacturer of the application, if the application opened by the mobile phone in response to the user's operation is not set with the application split screen window, the mobile phone will no longer display the application split screen window, as shown in (b in Figure 14 ). ). In addition, due to different application manufacturers, application split-screen windows displayed in different applications are usually inconsistent in terms of size, shape or display area.

It can also be understood that, since the identification of the contact object and the data of unread messages displayed in the application split screen window come from the corresponding application database, it is also impossible to display unread messages of other applications in the application split screen window. For example, unread messages from other apps, such as the Health app, will not be displayed in the app split screen of the SMS app.

The above describes the process that the mobile phone displays unread messages through the split-screen window and the user processes the unread messages through the split-screen window. The following takes the split-screen window as the system split-screen window and the application as an SMS application (such as Huawei system and Huawei SMS app) built into the mobile phone as an example to describe the configuration process of displaying unread messages in the system split-screen window.

The configuration process of displaying unread messages in the system split-screen window means that when the user calls out the corresponding system split-screen window on the application interface of a target application, the relevant data corresponding to the target application is obtained from the system database and the system is updated. The process of filling the split screen window.

Exemplarily, as shown in (a) of FIG. 15 , the mobile phone calls out the system split screen window shown in (b) of FIG. 15 in response to the user's triggering operation on the specific area 1201 . Specifically, after the mobile phone responds to the user's triggering operation on the specific area 1201, as shown in (c) of FIG. 15, relevant data can be obtained from the sub-database (for example, sub-database 2) corresponding to the short message application in the system database, for example , the avatar of the contact object, the name of the contact object, the number of unread messages, the title, the content of the unread messages, and other data related to the SMS application, and then load the acquired related data, and make adjustments to the system split screen window. After the configuration operation, the system split screen window as shown in (b) in Figure 15 is finally displayed. Here, the adaptation operation refers to displaying the relevant data in the corresponding position in the split-screen window. For example, as shown in (b) of FIG. 15 , the avatars of the contact objects are displayed in the split-screen window according to the preset sorting rules. , and the number of unread messages corresponding to each contact object is displayed in the upper right corner of the contact object's avatar.

With reference to Figure 15, as shown in Figure 16, the system split-screen window configuration process specifically includes the following steps:

S1301. In response to the first operation of the user, the mobile phone acquires the data required by the system split screen window from the system database.

Among them, the system database is used for copying, classifying and storing the messages of each application. The system database may include multiple sub-databases, the messages or data of each application are stored in a sub-database, and the sub-database corresponds to the package name of the application. For example, the data of the short message application (for example, information such as message data, contact object avatar and title, etc.) are stored in a sub-database corresponding to the package name of the short message application.

It can be understood that the mobile phone obtains the data required by the system split-screen window from the sub-database corresponding to the current application in the system database. For example, when the mobile phone triggers a specific area on the application interface of the SMS application in response to the user's first operation to display the system split-screen window, it is obtained from the sub-database (for example, sub-database 2) corresponding to the SMS application in the system database. Data required for the system split screen window. Among them, if the current application is an SMS application, the data required by the system split screen window includes the contact person's avatar, the contact person's name, the number of unread messages, the title, the content of the unread messages, or other information related to the SMS application. And the data needed when displaying the system split screen window.

S1302, the mobile phone loads the acquired data, and performs an adaptation operation on the system split screen window.

After the mobile phone obtains the data required by the system split-screen window from the sub-database corresponding to the system database, the mobile phone loads the acquired data and performs an adaptation operation on the system split-screen window. The adaptation operation is used to fill the acquired data in the system split screen window to display the system split screen window. Specifically, the adaptation operation may be to display each relevant data in the corresponding position in the split screen window, for example, as shown in (b) of FIG. 15 , display the avatar of the contact object on the split screen according to the preset sorting rule window, and the number of unread messages corresponding to each contact object is displayed in the upper right corner of the contact object's avatar.

S1303, the mobile phone displays a system split screen window.

After the mobile phone loads the acquired data and adapts the system split screen, the mobile phone can display the final system split screen window on the current application interface. In the split-screen window of the system, the mobile phone displays information such as the identifier of the contact object corresponding to the unread message and the data of the unread message based on the acquired data. Users can view information about unread messages through the system split-screen window.

To sum up, as shown in Figure 17, the process for the mobile phone to load data from the system database and display it on the system split screen window is as follows: When the application interface of the target application is opened, the target application sends a broadcast to the system, which includes The package name corresponding to the target application; the system creates a system adapter ListAdapter, which is used to load the data in the system database and display it on the system split-screen window; the system creates a Loader, which is used to load the data in the system database ; The system queries the data in the sub-database corresponding to the package name in the system database (that is, the data in the sub-database corresponding to the current application). In this way, the mobile phone obtains the data in the sub-database in the system database by querying the sub-database corresponding to the target application through the system, so as to load the data through the Loader and display the relevant data in the system split-screen window through the ListAdapter.

The above describes the process that the mobile phone obtains the relevant data from the corresponding sub-database in the system database to display the system split-screen window. In some cases, the mobile phone may mark the unread message as read in response to the user's second operation on the contact object in the system split-screen window (for example, step S303); or the mobile phone may respond to the user's contact with the system split-screen window in the system split screen window. The third operation of the object is to display unread messages (eg step S304).

It can be understood that, after the second operation or the third operation, relevant data of the unread messages has changed, for example, data such as the number and content of the unread messages have changed. Correspondingly, the data of unread messages in the application database of the short message application and the sub-database corresponding to the short message application in the system database also change. In such a case, the refresh of the system split screen window can be triggered. Therefore, as shown in Figure 16, the system split-screen window configuration process further includes:

S1304, the mobile phone refreshes the system split screen window in response to the user's processing operation on the unread message.

In some embodiments, the user's processing operation on the unread message includes: the user drags the identifier of the contact object in the system split-screen window out of the system split-screen window, so that the unread message corresponding to the contact object is marked as read ; Users can change unread messages into read messages by viewing the details of unread messages; or other processing operations that turn unread messages into read messages.

After the user processes the unread messages, the relevant data of the unread messages changes, so that the relevant data in the corresponding sub-databases in the application database and the system database also changes. In this case, the refresh of the system split screen window can be triggered. That is to say, the mobile phone queries the changed relevant data in the corresponding sub-database in the system database through the system, and loads and displays the data in the system split-screen window, thereby completing the refresh of the system split-screen window.

In the following, the user drags the identification of the contact object in the system split-screen window out of the system split-screen window, so that the unread message corresponding to the contact object is marked as read, and the user checks the details of the unread message to make Take the unread message becoming read message as an example to describe the refresh process of the system split screen window in detail.

In some embodiments, when the user drags the identification of the contact object in the system split-screen window out of the system split-screen window, so that the unread message corresponding to the identification of the contact object is marked as read, in response to this operation, The data in the corresponding sub-data in the system database changes accordingly, and the sub-database is refreshed. After that, the system database notifies the application database that the relevant data of the unread messages has changed. At the same time, the mobile phone can query the data in the corresponding sub-database in the refreshed system database through the system, load the data through the Loader, and query the query through the ListAdapter. The received data is configured in the system split screen window to complete the refresh of the system split screen window.

In some other embodiments, when the user checks the detailed content of the unread message to make the unread message become a read message, because the user checks the detailed content of the unread message, the relevant information of the unread message in the database is applied. Data changes. Further, because the system database keeps monitoring the application database (for example, the system database monitors the application database through an interface), the system database can receive a notification that data in the application database has changed, thereby refreshing the corresponding sub-database in the system database. After that, the mobile phone queries the data in the corresponding sub-database in the refreshed system database through the system, loads the data through the Loader, and configures the queried data into the system split-screen window through the ListAdapter to complete the refresh of the system split-screen window.

To sum up, as shown in Figure 17, the mobile phone monitors the application database through the system database, and can obtain the corresponding sub-data in the system database through query when the relevant data of the unread message changes after the user processes the unread message. Refresh the system split-screen window with the relevant data after the database changes to display the currently existing unread messages.

It should be noted that, if the split-screen window is a system split-screen window, since the system split-screen window obtains relevant data from the system database, and the system database includes the sub-databases corresponding to each application in the mobile phone, the system split-screen database contains only the current In addition to the relevant data of the unread messages corresponding to the application, the relevant data of the unread messages of other applications may also be included.

The above description is based on an example that the system and the application are from the same manufacturer (that is, the application is a system application that comes with a mobile phone as an example). The above method can also be applied to a third-party application. For example, when the system is a Huawei system and the application is a third-party application (WeChat, Alipay, QQ, etc.), the above method is also applicable. However, when the application is a third-party application, the interface opened by the application database of the third-party application needs to be adapted to the system, so that the system database can monitor the application database.

In addition, the above-mentioned split-screen window may also be an application split-screen window. That is to say, the split-screen window may also be a split-screen window constructed by the mobile phone in the application based on the data in the application database. If the split-screen window is an application split-screen window, the display process of the application split-screen window is shown in FIG. 18 . Referring to (a) in FIG. 18 , the mobile phone calls out the application split screen window as shown in (b) in FIG. 18 in response to the user's triggering operation on the specific area 1401 . Specifically, after the mobile phone responds to the user's triggering operation on the specific area 1401, as shown in (c) of FIG. 18, relevant data can be obtained from the application database corresponding to the short message application, for example, the avatar of the contact object, the contact object's profile picture Name, number of unread messages, title, content of unread messages, and other data related to the SMS application, and then load the obtained related data, and adapt the application split screen window, the final display is as shown in Figure 18 (b) of the application split screen window. Here, the adaptation operation means displaying each data in the corresponding position. For example, as shown in (b) of FIG. 18 , the avatar of the contact object is displayed in the application split screen window according to the preset sorting rule, and the The number of unread messages corresponding to each contact object is displayed in the upper right corner of the contact object's avatar.

In addition, when the mobile phone refreshes the application split screen window in response to the user's processing operation on the unread message, after the user views the unread message or drags the identifier of the contact object corresponding to the unread message out of the application split screen window, the unread message The number, content and other data of the application database changes, so the relevant data of the unread messages in the application database also changes accordingly. Therefore, the application in the mobile phone can directly refresh the application split screen window by querying the relevant data of the unread messages in the application database of the application after the change.

It should be noted that if the split-screen window is an application split-screen window, since the application split-screen window obtains relevant data from the application database, the application split-screen window only contains the relevant data of the unread messages of the application corresponding to the application database. , will not also include data about unread messages from other apps.

It can be understood that, in order to realize the above-mentioned functions, the above-mentioned terminal and the like include corresponding hardware structures and/or software modules for executing each function. Those skilled in the art should easily realize that, in conjunction with the units and algorithm steps of each example described in the embodiments disclosed herein, the embodiments of the present application can be implemented in hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Experts may use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of the embodiments of the present application.

In this embodiment of the present application, functional modules may be divided into the above terminal and the like according to the above method examples. For example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. It should be noted that, the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division manners in actual implementation.

In the case where each functional module is divided according to each function, FIG. 19 shows a possible schematic structural diagram of the terminal involved in the above embodiment, where the terminal is used to implement the methods described in each of the above method embodiments. Specifically, it includes: a detection unit 1501 , a processing unit 1502 and a display unit 1503 .

The display unit 1503 is used to: display the application icon of the target application on the desktop; the detection unit 1501 is used to: detect the user's operation on the application icon; the processing unit 1502 is used to: open the application interface of the target application.

Further, the detection unit 1501 is further used for: detecting the first operation of the user; the processing unit 1502 is further used for: calling out the split screen window; the display unit 1503 is also used for: displaying the split screen window on the application interface, and in the split screen window The screen window displays information such as the identification of the contact object and the number of unread messages.

Further, the display unit 1503 is further configured to: display a message preview interface and a message detail interface.

Wherein, all relevant contents of the steps involved in the above method embodiments can be cited in the functional descriptions of the corresponding functional modules, which will not be repeated here.

In the case of using an integrated unit, the above-mentioned processing unit 1502 can be used as a processing module, the above-mentioned display unit 1503 can be used as an output module, and the above-mentioned detection unit 1501 can be used as an input module. Of course, the terminal may also include a storage module and a communication module. At this time, as shown in FIG. 20 , a possible schematic structural diagram of the terminal involved in the above embodiment is shown, including a processing module 1601 , a communication module 1602 , an input/output module 1603 and a storage module 1604 .

The processing module 1601 is used to control and manage the actions of the terminal. The communication module 1602 is used to support the communication between the terminal and other network entities. The input/output module 1603 is used to receive information input by the user or output information provided to the user and various menus of the terminal. The storage module 1604 is used to store program codes and data of the terminal.

Exemplarily, the processing module 1601 may be a processor or a controller, such as a central processing unit (Central Processing Unit, CPU), a GPU, a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application-Specific Integrated Circuit, ASIC), Field Programmable Gate Array (Field Programmable Gate Array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute the various exemplary logical blocks, modules and circuits described in connection with this disclosure. The processor may also be a combination that implements computing functions, such as a combination comprising one or more microprocessors, a combination of a DSP and a microprocessor, and the like.

The communication module 1602 may be a transceiver, a transceiver circuit, an input and output device, a communication interface, and the like. For example, the communication module 1602 may specifically be a Bluetooth device, a Wi-Fi device, a peripheral interface, and the like.

The storage module 1604 may be memory, which may include high-speed random access memory (RAM), and may also include non-volatile memory, such as magnetic disk storage devices, flash memory devices, or other volatile solid-state storage devices, and the like.

The input/output module 1603 can be input and output devices such as a touch screen, a keyboard, a microphone, and a display. Wherein, the display may specifically be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. In addition, a touch panel can also be integrated on the display to collect touch events on or near it, and send the collected touch information to other devices (eg, a processor, etc.).

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using a software program, it may take the form of a computer program product, in whole or in part. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general purpose computer, special purpose computer, computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media. The available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)), and the like.

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

Claims

A method for managing unread messages, applied to terminal equipment, characterized in that it includes:

displaying a first interface of a first application, the first interface including a first object identification and a second object identification, wherein the first object identification has an unread message;

receive the first operation;

In response to the first operation, a second interface of the first application is displayed, the second interface includes the first object identification, the second object identification and a first window, in which the first window is displayed the first object identifier.
The method according to claim 1, wherein the number of unread messages corresponding to the first object identifier is further displayed in the first window.
The method according to claim 1 or 2, wherein an unread mark of the first object identifier is further displayed in the second interface.
The method according to any one of claims 1-3, wherein the first interface further includes a third object identifier, wherein the third object identifier has an unread message; displaying the third object identifier;

If the third object identifier is topped on the first interface, in the first window, the arrangement priority of the first object identifier is higher than the arrangement priority of the third object.
The method according to any one of claims 1-4, wherein in response to a user's sliding operation on the first interface, a third interface of the first application is displayed, and the third interface includes the first interface. Four object identifiers, wherein the fourth object identifiers have unread messages;

The fourth object identifier is also displayed in the first window, wherein the arrangement priority of the fourth object identifier in the first window is greater than the arrangement priority of the first object.
The method according to any one of claims 1-5, wherein the method further comprises:

In response to the user's second operation on the first object identifier in the first window, the first object identifier is no longer displayed in the first window, and the first object identifier is no longer displayed in the second interface. An unread mark for object identification.
The method according to claim 6, wherein the second operation comprises an operation of dragging the first object identifier in the first window out of the first window.
The method according to any one of claims 1-5, wherein the method further comprises:

In response to the user's third operation on the first object identifier in the first window, a detail interface of the unread message corresponding to the first object identifier is displayed.
The method according to any one of claims 1-5, wherein the method further comprises:

In response to the user's fourth operation on the first object identifier in the first window, a preview interface of the unread message corresponding to the first object identifier is displayed.
The method according to any one of claims 1-9, wherein the first object identifier has X unread messages, and the method further comprises:

If one unread message among the X pieces of unread messages is checked, the number of unread messages corresponding to the first object identifier becomes X-1.
The method according to any one of claims 1-10, wherein the first operation includes an operation on a preset control or a preset area on the first interface.
The method according to any one of claims 1-11, wherein the first window is a system split screen window, and the system split screen window further includes unread messages of the second application.
The method according to claim 12, wherein the unread messages of the first application in the system split-screen window come from a sub-database corresponding to the first application in a system database; the system split-screen window The unread messages of the second application are from the sub-database corresponding to the second application in the system database.
The method according to any one of claims 1-11, wherein the first window is an application split-screen window, and the method further comprises:

Open the second application;

A first interface of the second application is displayed, where the first interface does not include the application split screen window.
The method according to any one of claims 1-14, wherein the method further comprises:

In response to the fifth operation, the first window is hidden.
A terminal device, characterized in that it includes:

Display screen, used to display the interface;

one or more processors and one or more memories;

The one or more memories are coupled to the one or more processors, the one or more memories for storing computer program code, the computer program code comprising computer instructions, when the one or more processors When executing the computer instructions, the terminal device executes the method for managing unread messages according to any one of claims 1-15.
A computer storage medium, characterized by comprising computer instructions, which, when the computer instructions are executed on a terminal device, cause the terminal device to perform the management of unread messages according to any one of claims 1-15 method.
A computer program product, characterized in that, when the computer program product runs on a computer, the computer is caused to execute the method for managing unread messages according to any one of claims 1-15.