CN115344168A

CN115344168A - Message display method, terminal and computer readable storage medium

Info

Publication number: CN115344168A
Application number: CN202110522448.XA
Authority: CN
Inventors: 徐少非
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2021-05-13
Filing date: 2021-05-13
Publication date: 2022-11-15

Abstract

The embodiment of the application provides a message display method, a terminal and a computer readable storage medium. In response to the user starting the multi-page signature operation on the application, the terminal can display an application interface, the application interface displays the notification message received by the application in the first time period, in the process, the user does not need to repeatedly operate the terminal, the operation process is simple, and the user experience is good.

Description

Message display method, terminal and computer readable storage medium

Technical Field

The present application relates to the field of computers, and in particular, to a message display method, a terminal, and a computer-readable storage medium.

Background

Due to the portability of use, terminals have become essential communication devices in people's daily life. In the daily application of the terminal, the demand of the terminal from the user is not only solved the basic communication problem. An operating system and applications are installed in the terminal, so that the terminal can realize various functions.

Usually, the terminal sets a notification panel (notification panel) for displaying the messages received by the operating system or the application. Taking a mobile phone as an example, the mobile phone can display a status bar (status bar) at the same time when displaying applications such as a desktop. The status bar can display time, electric quantity, signal strength, bluetooth status, operator name and the like. If the situation that the user executes the pull-down operation on the status bar is detected, the mobile phone can display a pull-down menu. When messages of the system or the application exist in the mobile phone, the mobile phone can display the messages in a notification bar of a pull-down menu for a user to browse.

When the user views the message, the terminal can display the message only by opening the message. When the user needs to check the next message in the pull-down menu, the user needs to perform the pull-down operation on the status bar again, and then opens the message to be checked. When more messages are applied, the pull-down operation needs to be executed on the status bar again when the next message is checked every time, and the operation process is complicated, the operation efficiency is low, and the user experience is poor.

Disclosure of Invention

In order to solve the problems in the prior art, embodiments of the present application illustrate a message presentation method, a terminal, and a computer-readable storage medium

In a first aspect, an embodiment of the present application provides a message display method, where the method is applied to a terminal, and includes:

if the application supports a multi-page sign display mode, responding to the application executed and started by a user, and displaying an application interface, wherein the application interface comprises a first sub-window and a second sub-window, the first sub-window is used for displaying at least two first notification messages, the first notification messages comprise notification messages received by the application in a first time period, the first time period takes the time of the user for starting the multi-page sign operation last time as a starting point, and the time of executing and starting the multi-page sign operation this time as an end point.

In the implementation mode, in response to the user starting the multi-page signature operation on the application, the terminal can display an application interface, the application interface displays the notification message received by the application in the first time period, in the process, the user does not need to repeatedly operate the terminal, the operation process is simple, and the user experience is good.

With reference to the first aspect, in a first implementation manner, the step of displaying the application interface includes:

reading the display attribute of the application;

and adjusting the display style of the application interface according to the display attribute.

In the implementation mode, the terminal can adjust the display style of the application interface according to the display attribute, and the user experience is good.

With reference to the first aspect, in a second implementation manner, the first notification message includes a message tag and a message content; the first sub-window comprises a first display area and a second display area, the first display area is used for displaying the message labels, the second display area is used for displaying message contents corresponding to the target labels, and the target labels are labels selected by a user or labels selected by the terminal.

In this implementation manner, the space occupied by the message tag on the application interface is much smaller than the space occupied by the first notification message on the application interface, so that more message tags can be displayed on one application interface, and page-turning operation of a user can be reduced to a certain extent

With reference to the first aspect, in a third implementation manner, before the step of displaying the application interface, the method further includes:

reading a timestamp of each of the first notification messages, the timestamp being a time at which the notification message was generated;

and selecting a message tag contained in the first notification message generating the earliest time stamp as a target tag.

The implementation mode provides a selection scheme of the target label, and the user can preferentially read the first notification message which is recently received by adopting the implementation mode.

With reference to the first aspect, in a fourth implementation manner, the step of displaying the application interface if the application supports the multi-page sign-up display manner includes:

if the application supports a multi-page label display mode, clustering the notification message according to a message label contained in the notification message, wherein the clustered notification message comprises a clustering label and at least one clustering content;

displaying an application interface, wherein the application interface at least comprises a first sub-window, the first sub-window is used for displaying a clustering label and target clustering content, and the target clustering content is the clustering content corresponding to the clustering label selected by a user or the clustering content corresponding to the clustering label selected by the terminal.

In this implementation manner, in an application scenario where the message labels included in the plurality of first notification messages are the same, the display space of the application interface can be saved.

With reference to the first aspect, in a fifth implementation manner, the application interface further includes a second sub-window, where the second sub-window is used to display a second notification message, and the second notification message is different from the first notification message.

According to the implementation mode, the application interface can simultaneously display the second sub-window and the second sub-window, so that a user can acquire more information from one application interface, and the user experience is good.

With reference to the first aspect, in a sixth implementation manner, the method further includes:

and responding to the transfer operation of the user on the second notification message, and displaying the second notification message in the first sub-window, wherein the transfer operation comprises the operation of moving the second notification message from the first sub-window to the second sub-window.

According to the implementation mode, the content displayed on the application interface can be adjusted according to the operation of the user, the interactivity between the user and the terminal is improved, and the user experience is good.

With reference to the first aspect, in a seventh implementation manner, the method further includes:

and responding to the transfer operation of the first notification message by the user, and displaying the first notification message in the second sub-window, wherein the transfer operation comprises the operation of moving the first notification message from the second sub-window to the first sub-window.

With reference to the first aspect, in an eighth implementation manner, the method further includes:

and in response to the deletion operation of the user pair, deleting the first notification message in the first sub-window or deleting the second notification message in the second sub-window.

With reference to the first aspect, in a ninth implementation manner, the method further includes:

and responding to the amplification operation of the user, and amplifying the first notification message or amplifying the second notification message.

According to the implementation mode, the content displayed on the application interface can be adjusted according to the operation of the user, the interactivity between the user and the terminal is improved, and the user experience is good. With reference to the first aspect, in a tenth implementation manner, the method further includes:

and responding to the user movement operation, displaying the first notification messages in the first sub-window according to the arrangement sequence of the first notification messages after the movement, or displaying the second notification messages in the second sub-window according to the arrangement sequence of the second notification messages after the movement.

With reference to the first aspect, an eleventh implementation manner further includes:

and if the application does not support the multi-tab display mode to display the application interface, sequentially displaying the first notification message in a notification bar of a pull-down menu.

In the implementation mode, in response to the user starting the multi-page label operation on the application, the terminal can sequentially display the first notification message in the notification bar of the pull-down menu, and in the process, the user does not need to repeatedly operate the terminal, so that the operation process is simple, and the user experience is good.

In a second aspect, an embodiment of the present application provides a terminal, which includes a processor, where the processor is configured to execute the method provided in the embodiment of the present application.

In a third aspect, an embodiment of the present application provides a computer system, which includes a processor and a memory, where the memory is used to store a computer program, and the processor is used to execute the method provided by the embodiment of the present application.

In a fourth aspect, the present application provides a computer-readable storage medium, in which a computer program is stored, where the computer program is used by a processor to execute the method provided by the present application.

Drawings

FIG. 1 is a schematic diagram of a terminal according to one possible embodiment;

FIG. 2 is a block diagram of a software architecture of a terminal according to an exemplary embodiment;

FIG. 3 is a block diagram of a terminal according to an exemplary embodiment;

FIG. 4 is an interaction diagram of programs in a terminal according to an exemplary embodiment

FIG. 5 is a flow chart of a message presentation method provided by a possible embodiment;

FIG. 6 is a diagram illustrating a terminal display interface when a user performs operations on multiple tabs according to a possible embodiment;

FIG. 7 is a diagram illustrating a terminal display interface when a user performs operations on multiple tabs according to a possible embodiment;

FIG. 8 is a schematic diagram of an application interface shown in one possible embodiment;

FIG. 9 is a schematic diagram of an application interface shown in one possible embodiment;

FIG. 10 is a flow chart illustrating one manner of selecting a target tag;

FIG. 11 is a schematic diagram of an application interface shown in one possible embodiment;

FIG. 12 is a schematic diagram of an application interface shown in one possible embodiment;

FIG. 13 is a schematic diagram of an application interface shown in one possible embodiment;

FIG. 14 is a schematic diagram of an application interface shown in one possible embodiment;

FIG. 15 is a schematic diagram of an application interface shown in one possible embodiment;

FIG. 16 is a flow chart illustrating an application interface adjustment manner in accordance with an exemplary embodiment;

FIG. 17 is a schematic diagram of an application interface shown in one possible embodiment;

FIG. 18 is a schematic diagram of an application interface shown in one possible embodiment;

FIG. 19 is a schematic diagram of an application interface shown in one possible embodiment;

FIG. 20 is a flow chart illustrating the manner in which a first notification message is presented in accordance with a possible embodiment;

FIG. 21 is a schematic diagram of an application interface shown in one possible embodiment;

FIG. 22 is a diagram illustrating a change in an application interface during a second notification message transfer process in accordance with a possible embodiment;

FIG. 23 is a diagram illustrating a change in an application interface during a first notification message transfer process, in accordance with one possible embodiment;

FIG. 24 is a diagram illustrating a change in an application interface during a second notification message deletion process, in accordance with a possible embodiment;

FIG. 25 is a diagram illustrating a change in an application interface during a deletion of a first notification message in accordance with a possible embodiment;

FIG. 26 is a diagram illustrating a variation of an application interface during a second notification message magnification process in accordance with a possible embodiment;

FIG. 27 is a diagram illustrating a variation of an application interface during a second notification message magnification process in accordance with a possible embodiment;

FIG. 28 is a diagram illustrating a change in an application interface during movement of a second notification message in accordance with a possible embodiment;

fig. 29 is a schematic diagram illustrating a change of an application interface during a first notification message moving process according to a possible embodiment.

Detailed Description

The technical solutions in the embodiments of the present application will be described in detail below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application.

In the embodiments of the present application, the plural number means two or more. In addition, it is to be understood that the terms first, second, etc. in the description of the present application are used for distinguishing between the descriptions and not necessarily for describing a sequential or chronological order.

In the terminal mobile phone, the tablet computer, the notebook computer, the ultra-mobile personal computer (UMPC), the handheld computer, the netbook, the Personal Digital Assistant (PDA), the wearable terminal, the vehicle-mounted device, the virtual reality device, and the like, which are related to the embodiment of the present application, the embodiment of the present application does not limit the terminals.

Fig. 1 shows a schematic structural diagram of the terminal 100.

The terminal 100 may include a processor 110, an external memory interface 120, an internal memory 121, a Universal Serial Bus (USB) interface 130, a display 140, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, and the like.

It is to be understood that the illustrated structure of the embodiment of the present invention does not specifically limit the terminal 100. In other embodiments of the present application, terminal 100 may include more or fewer components than shown, or some components may be combined, some components may be split, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 110 may include one or more processing units, such as: the processor 110 may include an Application Processor (AP), a modem processor, a Graphics Processor (GPU), an Image Signal Processor (ISP), a controller, a memory, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), among others. Wherein, the different processing units may be independent devices or may be integrated in one or more processors.

A memory may also be provided in processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to reuse the instruction or data, it can be called directly from memory. Avoiding repeated accesses reduces the latency of the processor 110, thereby increasing the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit (I2C) interface, an integrated circuit built-in audio (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a general-purpose input/output (GPIO) interface, a Subscriber Identity Module (SIM) interface, and/or a Universal Serial Bus (USB) interface, etc.

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

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in terminal 100 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed as a diversity antenna of a 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 solution including 2G/3G/4G/5G wireless communication and the like applied to the terminal 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the same device as at least some of the modules of the processor 110.

The wireless communication module 160 may provide a solution for wireless communication applied to the terminal 100, including Wireless Local Area Networks (WLANs) (e.g., wireless fidelity (Wi-Fi) networks), bluetooth (BT), global Navigation Satellite System (GNSS), frequency Modulation (FM), near Field Communication (NFC), infrared (IR), and the like. 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, performs frequency modulation and filtering processing on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves.

In some embodiments, the antenna 1 of the terminal 100 is coupled to the mobile communication module 150 and the antenna 2 is coupled to the wireless communication module 160 so that the terminal 100 can communicate with a network and other devices through a wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general Packet Radio Service (GPRS), code Division Multiple Access (CDMA), wideband Code Division Multiple Access (WCDMA), time-division code division multiple access (time-division code division multiple access, TD-SCDMA), long Term Evolution (LTE), LTE, BT, GNSS, WLAN, NFC, FM, and/or IR technologies, etc. GNSS may include Global Positioning System (GPS), global navigation satellite system (GLONASS), beidou satellite navigation system (BDS), quasi-zenith satellite system (QZSS), and/or Satellite Based Augmentation System (SBAS).

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

The display screen 140 is used to display images, video, and the like. The display screen 140 includes a display panel. The display panel may be a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (active-matrix organic light-emitting diode, AMOLED), a flexible light-emitting diode (FLED), a miniature, a Micro-oeld, a quantum dot light-emitting diode (QLED), or the like. In some embodiments, terminal 100 may include 1 or N displays 140, N being a positive integer greater than 1.

The terminal 100 may implement a photographing function through the ISP, the camera 190, the video codec, the GPU, the display screen 140, and the application processor, etc.

The ISP is used to process the data fed back by the camera 190. For example, when a photo is taken, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing and converting into an image visible to naked eyes. The ISP can also carry out algorithm optimization on the noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in camera 190.

The camera 190 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing element converts the optical signal into an electrical signal, which is then passed to the ISP where it is converted into a digital image signal. And the ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into image signal in standard RGB, YUV and other formats. In some embodiments, the terminal 100 may include 1 or N cameras 190, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process other digital signals besides digital image signals. For example, when the terminal 100 selects a frequency bin, the digital signal processor is used to perform fourier transform or the like on the frequency bin energy.

Video codecs are used to compress or decompress digital video. The terminal 100 may support one or more video codecs. In this way, the terminal 100 can play or record video in a variety of encoding formats, such as: moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, and the like.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to extend the memory capability of the terminal 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music, video, etc. are saved in an external memory card.

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

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

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or some functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also called a "horn", is used to convert the audio electrical signal into an acoustic signal. The terminal 100 can listen to music through the speaker 170A or listen to a handsfree call.

The receiver 170B, also called "earpiece", is used to convert the electrical audio signal into an acoustic signal. When the terminal 100 receives a call or voice information, it can receive voice by bringing the receiver 170B close to the human ear.

The microphone 170C, also referred to as a "microphone," is used to convert sound signals into electrical signals. When making a call or sending voice information, the user can input a voice signal to the microphone 170C by uttering a voice signal close to the microphone 170C through the mouth of the user. The terminal 100 may be provided with at least one microphone 170C. In other embodiments, the terminal 100 may be provided with two microphones 170C to achieve a noise reduction function in addition to collecting sound signals. In other embodiments, the terminal 100 may further include three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, implement directional recording functions, and so on.

The earphone interface 170D is used to connect a wired earphone. The headset interface 170D may be the USB interface 130, or may be a 3.5mm open mobile platform (OMTP) standard interface, a cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

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

For example, a touch sensor may capture touch events of a user on or near the touch sensor (e.g., a user operating on the touch sensor surface using a finger, a stylus, etc. of any suitable object) and transmit the captured touch information to another device, such as the processor 110. For example, the touch sensor can be implemented in various ways, such as resistive, capacitive, infrared, and surface acoustic wave. The touch sensor may be integrated with the display screen 140 as a touch screen of the terminal 100, or the touch sensor and the display screen 140 may be implemented as two separate components to implement the input and output functions of the terminal 100.

Of course, the terminal 100 may further include a charging management module, a power management module, a battery, a key, an indicator, 1 or more SIM card interfaces, and the like, which is not limited in this embodiment of the application.

The software system of the terminal 100 may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes an Android system with a layered architecture as an example, and exemplarily illustrates a software structure of the terminal 100.

Fig. 2 is a block diagram of a software configuration of the terminal 100 according to the embodiment of the present application.

The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, an application layer 210, an application framework layer 220, an Android runtime (Android runtime) and system library 230, and a kernel layer 240, from top to bottom, respectively.

1. An application layer;

the application layer may include a series of applications.

As shown in fig. 2, the application programs may include Applications (APPs) such as call, contact, camera, gallery, calendar, map, navigation, bluetooth, music, video, and short message.

As shown in fig. 2, the application layer further includes Android core applications such as a launcher (also referred to as a desktop or a home screen). Generally, after the Android system is started, the launcher can be used as a core application to reside in the Android system to run.

2. An application framework layer;

the application framework layer provides an Application Programming Interface (API) and a programming framework for the application programs of the application layer. The application framework layer includes a number of predefined functions.

Illustratively, a notification manager, an activity manager, a window manager, a content provider, a view system, a phone manager, etc. may be included in the application framework layer.

3. Android runtime and system library;

the Android runtime comprises a core library and a virtual machine. The Android runtime is responsible for scheduling and managing an Android system.

The core library comprises two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. The virtual machine executes java files of the application layer and the application framework layer as binary files. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface managers (surface managers), media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., openGL ES), 2D graphics engines (e.g., SGL), and the like.

4. Inner core layer

The kernel layer is a layer between hardware and software. The kernel layer at least comprises a display driver, a camera driver, an audio driver, a sensor driver and the like, and the embodiment of the application does not limit the display driver, the camera driver, the audio driver, the sensor driver and the like.

Usually, the terminal sets a notification panel (notification panel) for displaying the messages received by the operating system or the application. Taking a mobile phone as an example, the mobile phone can display a status bar (status bar) at the same time when displaying applications such as a desktop. The status bar can display time, electric quantity, signal strength, bluetooth status, operator name and the like. If the situation that the user executes the pull-down operation on the status bar is detected, the mobile phone can display a pull-down menu. When messages of the system or the application exist in the mobile phone, the mobile phone can display the messages in a notification bar of a pull-down menu for a user to browse. When the user views the message, the terminal can display the message only by opening the message. When the user needs to check the next message in the pull-down menu, the user needs to perform the pull-down operation on the status bar again, and then opens the message to be checked. When the number of system or application messages is large, the next message is checked each time, and the pull-down operation is executed on the status bar again, so that the operation process is complicated, the operation efficiency is low, and the user experience is poor.

In order to solve the above technical problem, an embodiment of the present application illustrates a message presentation method, which is applicable to the terminal illustrated in the above embodiment, and specifically refer to fig. 3 and fig. 4, fig. 3 is a structural block diagram of the terminal provided in a feasible embodiment, and fig. 4 is an interaction diagram of each program in the terminal provided in a feasible embodiment. It can be seen that, in the present application, the terminal may include: a notification system 31, an Activity Start32, an asm (Activity Manager Service) 33, a split screen management 34, an mpm (Multi-Page Manager) 35, a Multi-Page stack management 36, and a presentation system 37. The functions and actions of the programs in the terminal are described below with reference to the accompanying drawings, and fig. 5 is a flowchart of a message presentation method provided in a possible embodiment, where it can be seen that the method includes:

s51, in response to the user executing the start multi-page signature operation on the application, the notification system 31 filters the notification message set;

in the application, the multiple tabs are multiple windows in one application interface, wherein one window is used for showing multiple messages, and the messages may include notification messages of a system or an application.

In the application, the operation of starting the multiple tabs is performed when the user controls one application to be displayed in a multiple tab mode. For example: as a feasible implementation manner, the operation of starting the multi-tab may be performed by merging two notification messages of the same application by the user, and then sliding the merged notification message by the single finger of the user, where the interface displayed by the terminal may refer to fig. 6, an OPEN control 61 appears in the interface, and the user touches the OPEN control 61 to start the multi-tab function of the application. For another example, as a feasible implementation manner, the operation of starting the multiple tabs may be performed by merging two notification messages of the same application by the user, and the user presses the interface displayed by the terminal at this time with the merged notification message for a long time, referring to fig. 7. And the user long presses the merged notification message to start the multi-page signature function of the application. It should be noted that, this embodiment merely describes two operations for executing the starting of the multi-tab by way of example, and the two operations are not limited to the above two operations, and the operation for starting the multi-tab during the actual application process may be, but is not limited to, the two operations.

In the present application, the notification service 31 of the terminal is used to record the notification message received by the terminal, and the notification message may include a notification message of a system and a notification message of an application. When a user executes an operation of starting multiple tabs on an application, the notification service 31 filters out first notification messages of the application to obtain a notification message set, and the notification message set at least includes two first notification messages.

There are various implementations of the first notification message of the screening application, for example: as a feasible implementation manner, the implementation manner of the first notification message for screening out the application may be: each notification message is configured with an application identifier, and when a user performs an operation of starting multiple tabs on an application, the notification service 31 may read the application identifier of the application, and then select a first notification message based on a corresponding relationship of the application identifiers. It should be noted that the present embodiment is merely an exemplary implementation manner for describing a first notification message of a screening application, and the implementation manner is not limited to the above, and the implementation manner of the first notification message of the screening application in the process of actual application may be, but is not limited to, the above implementation manner.

In this application, the notification message set includes at least two notification messages received from the application in the first time period. The first time period takes the time of starting the multi-page signature operation last time by the user as a starting point and takes the time of starting the multi-page signature operation executed this time as an end point. The first notification message is described below with reference to a specific example. In a feasible embodiment, the application selected by the user is a short message, the time for executing the operation of starting the multi-page signature on the short message application at this time is 10 o 'clock 27 min 05 sec, the time for executing the operation of starting the multi-page signature on the short message application at the last time is 10 o' clock 02 min 05 sec, in this embodiment, the first time period is [ 10 o 'clock 02 min 05 sec to 10 o' clock 27 min 05 sec ], and the notification message for receiving the short message application in [ 10 o 'clock 02 min 05 sec to 10 o' clock 27 min 05 sec ] is: message 11, message 12, message 13, and message 14; the first notification message in this embodiment includes: message 11, message 12, message 13, and message 14.

As a possible embodiment, notification service 31, after generating the set of notification messages, sends the notification messages to Activity Start32 in the form of a list. Activity Start32, in response to receiving the set of awareness messages, determines the application currently operated by the user and launches the application.

After the application is started, the AMS33 executes S42 to judge whether the application supports a multi-page sign display mode;

judging whether the application supports multiple page label display modes or not; for example: as a feasible implementation manner, the implementation manner of determining whether the application supports the multi-page label exhibition manner may be: storing the application supporting the multi-page sign display mode in a white list in advance, traversing the white list when a user executes the operation of starting the multi-page sign on a certain application, and determining whether the application supports the multi-page sign display mode if the application is recorded in the white list. For another example: as a feasible implementation manner, a multi-tab identifier may be configured for an application supporting the multi-tab display manner in advance, and when a user performs an operation of starting the multi-tab for a certain application, whether the application supports the multi-tab display manner may be determined by reading the multi-tab identifier. The style of the multi-tab identification is not limited in the application, and the style of the multi-tab identification can be set according to requirements in the actual application process. It should be noted that the present embodiment is only an exemplary implementation manner for describing two manners for determining whether the application supports the multi-page sign displaying manner, and the two implementation manners are not limited to the above two manners.

If the application supports a multi-page sign out mode, the AMS33 initiates the split screen service 34. When the split screen service 34 is activated, the presentation interface of the terminal may present multiple windows, each of which may present different content. As a possible implementation, the split screen service 34 may be a Magic window (parallel view application) if a "parallel world application" is installed in the terminal; as a feasible implementation, the Split screen service 34 may be an SSS (Split-screen System) of the mobile phone itself.

After split screen service 34 is launched, the split screen service sends a launch multi-tab command to MPM35 to cause MPM35 to draw an application interface of the currently launched application. The MPM35 outputs the drawn application interface to the presentation system 37.

The presentation system 37 performs S53 to display an application interface, where the application interface includes a first sub-window and a second sub-window, where the first sub-window is used to present the first notification message.

The following description will be made with reference to the drawings for illustrating the application interface. Fig. 8 is a schematic diagram of an application interface shown in a feasible embodiment, and it can be seen that the application interface includes a first sub-window 81, and the first time period in the embodiment shown in fig. 8 is [ 10 o 'clock 02 min 05 sec to 10 o' clock 27 min 05 sec ]. In the first time period, the terminal receives 4 first notification messages. The user can open the 4 first notification messages in sequence on the application interface.

Generally, to facilitate the user's view, as a possible implementation, the first notification message notification may be split into a message tag and a message content. The number of words contained in the message tag is less than that contained in the message content, so that more message tags can be displayed in one interface, and page turning operation of a user can be reduced to a certain extent.

In this application, the message tag may be a keyword of the first notification message, for example: in a feasible embodiment, the first notification message is "news about vaccine sent by people's daily newspaper", and the tag corresponding to the first notification message may be "vaccine"; for example, in a feasible embodiment, the first notification message is "a short message sent by three, and the tag corresponding to the first notification message may be" three by three ". It should be noted that the present embodiment is only an exemplary embodiment that introduces two types of labels, the two types are not limited, and the label type in the practical application process may be, but is not limited to, the two types.

As a feasible implementation manner, the first sub-window may include a first display area and a second display area, where the first display area is used for displaying the message label, and the second display area is used for displaying the message content corresponding to the target label.

The following description will be made with reference to the drawings for illustrating the application interface. Fig. 9 is a schematic diagram of an application interface shown in a feasible embodiment, and it can be seen that the application interface includes a first sub-window and a second sub-window, where the first sub-window includes a first display area 91 and a second display area 92, in the embodiment shown in fig. 9, 4 first notification messages are generated in a first time period, and the corresponding first display area displays 4 message labels, where the 4 message labels are a message label 93, a message label 94, a message label 95, and a message label 96. Fig. 9 shows an embodiment in which the target tag is a message tag 94, and correspondingly, the message content (message content 4) corresponding to the message tag 94 is displayed in the second display area 92.

It should be noted that fig. 9 is merely an exemplary illustration of the first display area and the second display area being arranged in a vertical direction, and the above illustration is not limited thereto, and in some possible embodiments, the first display area and the second display area are arranged in a horizontal direction.

In the application, the target tag is a tag selected by a user or a tag selected by a terminal. The implementation mode of selecting the target label is various;

for example, as a feasible implementation manner, the implementation manner of selecting the target tag may be that the user selects the target tag in the first display area. Specific implementations may continue with reference to fig. 9. Fig. 9 shows that the first display window in the application interface displays 4 message tags, and in response to the touch operation of the user on the tag 94, the terminal selects the tag 94 as a target tag.

For another example, as a feasible implementation manner, the implementation manner of selecting the target tag may be that the terminal randomly selects one tag from all message tags as the target tag.

For another example, fig. 10 shows a flow chart of a manner of selecting a target tab, the method further comprising, prior to the step of displaying the application interface:

s101, reading the time stamp of each first notification message;

in this embodiment, each first notification message is configured with a timestamp. Wherein the timestamp is the time at which the notification message was generated. For example, the generation time of the first notification message 1 is 10 o 'clock 27 min 5 sec, and then the timestamp of the first notification message 1 is "10 o' clock 27 min 5 sec".

The time stamp of each first notification message may be read in a manner of reading information that is conventional in the art, and the applicant does not limit the disclosure herein.

S102 selects a message tag included in the first notification message that generates the earliest/latest timestamp as a target tag.

For example, in a possible embodiment, the 4 first notification messages generated in the first time period are respectively: a first notification message 1, a first notification message 2, a first notification message 3, and a first notification message 4; the timestamp of the first notification message 1 is "10 o 'clock 27 min 5 sec", the timestamp of the first notification message 2 is "10 o' clock 32 min 10 sec", the timestamp of the first notification message 3 is "10 o 'clock 43 min 7 sec", and the timestamp of the first notification message 4 is "10 o' clock 56 min 9 sec". The implementation selects the message tag of the first notification message 1 as the target tag.

For example, in a possible embodiment, the 4 first notification messages generated in the first time period are respectively: the first notification message 1, the first notification message 2, the first notification message 3, and the first notification message 4, wherein the timestamp of the first notification message 1 is "10 o 'clock 27 min 5 sec", the timestamp of the first notification message 2 is "10 o' clock 32 min 10 sec", the timestamp of the first notification message 3 is "10 o 'clock 43 min 7 sec", and the timestamp of the first notification message 4 is "10 o' clock 56 min 9 sec". The implementation selects the message tag of the first notification message 4 as the target tag.

It should be noted that, the present application is only an exemplary implementation showing several selected target tags, and the implementation is not limited to the above implementation, and in the process of practical application, the implementation of the selected target tags may be, but is not limited to, several implementations.

Typically, the first presentation area may present a plurality of message tags, which may be ordered in some feasible real-time manner according to a preset sequence. The preset sequence may be a sequence pre-stored by the terminal, or a sequence set by the user according to the requirement without being limited by the applicant herein. For example, in some feasible embodiments, the terminal may sort the message tags in order of the timestamps from first to last; in some feasible embodiments, the terminal may sort the message tags in order of the timestamps from back to front; in some feasible embodiments, the terminal may sort the message tags according to a priority set by the user; it should be noted that, this embodiment is only an exemplary way to show several message tag arrangements, and the above arrangement is not limited, and the message tag arrangements in the practical application process may be, but not limited to, the above several ways.

As a possible implementation, the second sub-window is used to present the second notification message. In this application, the second notification message is different from the first notification message, and the description will be given below for the second notification message.

As a feasible embodiment, the second notification message may include a notification message that the application is received within the second time period. And the second time period takes the time when the user last starts the multi-page signature operation as an end point. For example, in a feasible embodiment, the multi-signature operation time of the last time the user started the sms application is 10 o 'clock 2 min 30 sec, and then the second time period may be a time before 10 o' clock 2 min 30 sec.

The starting time of the second time period is not limited in this embodiment. For example, in some feasible embodiments, the starting point of the second time period may be the time of first using the terminal, and then the second time period is [ the time of first using the terminal to the time of last starting the multi-signature operation ]; for example, in a feasible embodiment, the operation time of the multi-signature for the user to start the short message application last time is 10 o 'clock 2 min 30 sec, and the second time period in this implementation is [ time of using the terminal for the first time-10 o' clock 2 min 30 sec ]; for another example, in some feasible embodiments, the starting point of the second time period may be a preset time before the time of starting the multi-tab operation last time, wherein the preset time may be set according to requirements, for example, the preset time may be 1 week or 24 hours, which is not limited by the applicant herein. For example, in a feasible embodiment, the operation time of the multi-signature for the user to start the short message application last time is 10 o ' clock 2 min 30 sec at 5 days of 10 months, and the preset time is 24 hours, where the second time period in this embodiment is [ 10 o ' clock 2 min 30 sec at 4 days of 10 months to 10 o ' clock 2 min 30 sec at 5 days of 10 months ]. It should be noted that the present embodiment merely shows the starting times of several second time periods by way of example, and the starting times of the second time periods in the process of practical application may be, but are not limited to, the above-mentioned several ways.

In order to facilitate the user to view the unread notification messages, as a feasible embodiment, the second sub-window may only show the unread second notification messages.

For example, for a chat-type application, the first notification message may be a chat message received by the terminal within a first time period, and the first notification message may be a chat message received by the terminal within a second time period. The first notification message and the second notification message are presented in the following manner with reference to the specific drawings. Fig. 11 is a schematic diagram of an application interface shown in a possible embodiment, where the currently started application is a chat-type application, and it can be seen that the first sub-window 111 is used to display chat messages received within [ 10 o 'clock 2 min 30 sec to 10 o' clock 25 min 30 sec ], and the second sub-window 112 is used to display chat messages received within 10 o 'clock 2 min 30 sec to 10 o' clock 2 min 30 sec of 10 o 'clock 5 days [ 10 o' clock 4 d ].

As a possible implementation, the first notification message may be a video that the user has viewed by applying a recommended hot message for a first period of time. Fig. 12 is a schematic diagram of an application interface shown in a possible embodiment, where the currently started application is a video-class application, and it can be seen that the first sub-window 121 is used to show hot messages received within [ 10: 2: 30 sec to 10: 25: 30 sec ], and the second sub-window 122 is used to show videos that are watched by the user.

As a feasible implementation, the first notification message may be a hot top bar, and the second notification message may be a microblog message. The user can watch the message and the hot headline, so that much time of the user is saved. Fig. 13 is a schematic diagram of an application interface shown in a feasible embodiment, where the currently started application is a microblog-type application, it can be seen that the first sub-window 131 is used for displaying hot top bars received within [ 10 o 'clock 2 min 30 sec-10 o' clock 25 min 30 sec ], and the second sub-window 132 is used for displaying microblog messages.

As a feasible implementation manner, the first notification message can be a message related to the shopping website recommending commodities for the user, and the second notification message can be a message related to the shopping cart commodities the user joins. Fig. 14 is a schematic diagram of an application interface shown in a feasible embodiment, where the currently started application is a shopping application, and it can be seen that the first sub-window 141 is used to show a message related to a shopping website recommending a commodity for a user within [ 10 o 'clock 2 min 30 sec to 10 o' clock 25 min 30 sec ], and the second sub-window 142 is used to show a message related to a user joining a shopping cart commodity.

It should be noted that the present embodiment merely shows some types of the first notification message and the second notification message by way of example, and in the process of practical application, the types of the first notification message and the second notification message may be, but are not limited to, the above-mentioned several ways, and the applicant does not make much limitation here.

If the application does not support the multi-tab display mode to display the application interface, step S34 is executed to sequentially display the first notification messages in the notification bar of the pull-down menu.

The following describes a manner of displaying the first notification message applied to the no-more-tab displaying manner with reference to specific drawings. Fig. 15 is a schematic diagram of an application interface shown in a feasible embodiment, and it can be seen that 4 first notification messages of an application are received in a first time period, in response to a user executing a multi-tab starting operation on the application, the terminal determines that the application does not support a multi-tab displaying manner, and the terminal sequentially displays the first notification messages in a notification bar of a pull-down menu at preset time intervals, specifically, see an effect 151, an effect 152, an effect 153, and an effect 154 in fig. 15.

Generally, the content of the notification message corresponding to different applications has a certain difference, and as a feasible embodiment mode, in order to improve the experience of the user, the display attribute may be configured for the application, and the terminal may adjust the display style of the application interface according to the display attribute. The manner in which the notification message is presented is described below in conjunction with the specific figures.

FIG. 16 is a flow chart illustrating an application interface adjustment manner in one possible embodiment. In the implementation process, the MPM35 executes S161 to S162.

S161, reading the display attribute of the application;

in this embodiment, the display attribute includes an attribute related to the application presentation style. For example, the display attribute may include an attribute related to a presentation style of the first sub-window and the second sub-window, for example, the display attribute may be a width and a height of the first sub-window, the first sub-window is a position displayed in the presentation interface, and the content presented by the first sub-window is presented in a left direction, a right direction, or a center direction. The display properties may further include properties related to the presentation styles of the first notification message and the second notification message. The display attribute may be that the first notification message is displayed on the left, displayed on the right or displayed in the middle, the font size, the picture position, a row of several message tags, and the like.

S162, adjusting the display style of the display page according to the display attribute.

As a possible implementation, the display attribute may be pre-configured; for example, in a possible embodiment, the pre-configured display attributes may be that the first sub-window is displayed close to the left, the second sub-window is displayed close to the right, and the text in the first notification message and the second notification message is displayed in the middle. Referring to fig. 17, it can be seen that the first sub-window 171 is located on the left side, the second sub-window 172 is located on the right side, and the first notification message and the second notification message are displayed in the middle.

As a possible implementation, the display attribute may be determined according to the first notification message. For example, in a possible embodiment, the terminal receives 4 first notification messages, and the display attribute may be that 4 message tags are displayed in a row in the first display window. In particular, reference may be made to FIG. 18. In a possible embodiment, the terminal receives 3 first notification messages, and the display attribute may be that 3 message tags are displayed in a row in the first display window. In particular, reference may be made to FIG. 19.

In some application scenarios, the message tags included in the plurality of first notification messages are the same, in which case, if the message tag of each first notification message is displayed, a large display space is occupied, and especially, in the case of many first notification messages, it may be possible that all the message tags cannot be displayed in one page. In order to reduce the occurrence probability of the above problem to a certain extent, the present embodiment further optimizes the display manner of the first notification message, and the display manner of the first notification message is described below with reference to specific examples.

Fig. 20 is a flow chart illustrating a first notification message presentation manner according to a possible embodiment. S201 to S202 in the implementation process.

If the application supports a multi-page tag display mode, S201 clusters the notification message according to the message tag contained in the notification message, and the clustered notification message comprises a cluster tag and at least one cluster content;

for example, in a feasible embodiment, the notification message set screened by the terminal may be referred to table 1:

TABLE 1

Serial number	First notification message	Message label	Message content	Remarks for note
					1	Notification message 1	Zhang San	Content 1
2	Notification message 2	Li Si	Content 2
					3	Notification message 3	Zhang San	Content 3
4	Notification message 4	Zhang San	Content 4
					5	Notification message 5	Zhang San	Content 5
6	Notification message 6	Xiao Hong	Content 6
					7	Notification message 7	Li Si	Content 7

The clustered notification messages can refer to table 2;

TABLE 2

S202, displaying an application interface, wherein the application interface at least comprises a first sub-window, and the first sub-window is used for displaying the clustering label and the target clustering content, and the target clustering content is the clustering content corresponding to the clustering label selected by the user or the clustering content corresponding to the clustering label selected by the terminal.

The application interface shown in this embodiment will be described with reference to specific examples. FIG. 21 is a schematic diagram of an application interface shown in one possible embodiment. It can be seen that the application interface includes a first sub-window 211 and a second sub-window 212, where the first sub-window 211 includes a first display area and a second display area, the first display area is used to display a cluster label (zhang san, lie si, and small red), zhang san in this embodiment is a target cluster label, and the corresponding second sub-window 212 is used to display the cluster content (content 1, content 3, content 4, and content 5) corresponding to zhang san.

In order to improve the experience of the user, in some feasible embodiments, the content displayed on the application interface may be adjusted according to the operation of the user, and the adjustment manner of the content displayed on the application interface is described below with reference to a specific example.

As a feasible implementation, the method shown in the above embodiment further includes: in response to the user's operation on the notification message, the multi-page tab stack management 36 records the status message of the operated notification message, and generates a status instruction, which is fed to the multi-page tab management 35, so that the multi-page tab management 35 can adjust the content displayed on the application interface based on the status instruction. The above process is described below with reference to specific examples.

In some feasible embodiments, in response to a user's transfer operation for the notification message, the multi-tab stack management 36 feeds back a transfer instruction to the multi-tab management 35, and the multi-tab management 35 transfers the second notification message from the second sub-window to the first sub-window, or transfers the first message from the first sub-window to the second sub-window.

In this embodiment, the transfer operation includes an operation of moving the second notification message from the first sub-window to the second sub-window, or an operation of moving the first notification message from the first sub-window to the second sub-window. As a possible implementation manner, the transferring operation may be that the user selects a second notification message in advance, and then moves the selected second notification message from the second sub-window to the first sub-window by means of dragging. As a feasible implementation, the transfer operation may be that the user touches a transfer control on the application interface. The specific implementation process may be that the user selects a second notification message in advance and then moves the second notification message from the second sub-window to the first sub-window through a transfer control on the touch application interface. The transfer process of the first notification message may refer to the transfer process of the second notification message, which is not described in detail by the applicant. The embodiment only shows two transfer operations by way of example, and in the process of practical application, the transfer operation may be, but is not limited to, the above two ways.

The following describes the transfer process of the notification message with reference to specific figures.

Fig. 22 is a schematic diagram illustrating a change of an application interface in a second notification message transfer process according to a possible embodiment. In the initial state, the application interface displayed by the terminal can refer to the effect 221 in fig. 22. The user selects the notification message 12 in the effect 221, and then moves the notification message 12 from the second sub-window 223 to the first sub-window 224 by means of dragging, at which time, the application interface displayed by the terminal can refer to the effect 222 in fig. 22.

Fig. 23 is a schematic diagram illustrating a change of an application interface during a first notification message transfer process according to a feasible embodiment. Initially, the application interface exposed by the terminal can refer to the effect 231 in fig. 23. The user selects the first notification message 121 in the effect 231 and then moves the first notification message 121 from the first sub-window 235 to the second sub-window 234 by clicking the transition control 233, at which time, the application interface presented by the terminal can refer to the effect 232 in fig. 23.

In some possible embodiments, the method shown in the above embodiments further comprises:

and in response to the deletion operation of the first notification message by the user, deleting the first notification message in the first sub-window. Or, in response to the user's deletion operation of the second notification message, deleting the second notification message in the second sub-window.

In this embodiment, the deletion operation includes an operation of deleting the first notification message in the first sub-window or deleting the second notification message in the second sub-window. As a possible implementation, the deletion operation may be that the user selects a second notification message in advance, and then deletes the selected second notification message by long-pressing. As a feasible implementation, the deletion operation may be that the user touches a deletion control on the application interface. The specific implementation process may be that the user selects a second notification message in advance, and then deletes the second notification message through a deletion control on the touch application interface. The deleting process of the first notification message may refer to the deleting process of the second notification message, which is not described in detail by the applicant. The embodiment merely shows two deleting operations by way of example, and in the process of actual application, the deleting operation may be, but is not limited to, the two manners described above.

Fig. 24 is a schematic diagram illustrating a change of an application interface during a second notification message deletion process according to a feasible embodiment. Initially, the terminal presents the application interface, which can refer to the effect 241 in fig. 24. The user selects the notification message 11 in the effect 241 and then deletes the notification message 11 by means of a long press, at which time the application interface presented by the terminal may refer to the effect 242 in fig. 24.

Fig. 25 is a schematic diagram illustrating a change of an application interface during a first notification message transfer process according to a possible embodiment. Initially, the application interface displayed by the terminal can refer to the effect 251 in fig. 25. The user selects the notification message 24 in the effect 251 and then deletes the notification message 24 by clicking the delete control 253, at which time the application interface presented by the terminal can refer to the effect 252 in fig. 25.

In some feasible embodiments, the method shown in the above embodiments further comprises:

and amplifying the first notification message in response to the amplification operation of the first notification message by the user. And amplifying the second notification message in response to the amplification operation of the second notification message by the user.

In the present embodiment, the enlargement operation is an operation of enlarging the first notification message/the second notification message. As a possible implementation, the zooming-in operation may be that the user selects a second notification message in advance, and then zooms in the selected second notification message by touching the display screen twice in succession. As a feasible implementation, the deletion operation may be the user touching an enlargement control on the application interface. The specific implementation process may be that the user selects a second notification message in advance, and then the second notification message is amplified through an amplification control on the touch application interface. The process of enlarging the first notification message may refer to the process of enlarging the second notification message, which is not described in detail by the applicant. The embodiment is only an exemplary illustration of two amplification operations, and in the process of practical application, the amplification operation may be, but is not limited to, the two manners described above.

Fig. 26 is a schematic diagram illustrating a change of an application interface in a second notification message amplification process according to a feasible embodiment. Initially, the terminal exposes the application interface, which may refer to effect 261 in fig. 26. The user selects the notification message 11 in the effect 261 and then enlarges the second notification message 11 by touching the display screen twice, at which time the application interface displayed by the terminal can refer to the effect 262 in fig. 26.

Fig. 27 is a schematic diagram illustrating a change of an application interface in a first notification message transfer process according to a possible embodiment. Initially, the application interface displayed by the terminal can refer to the effect 271 in fig. 27. The user selects the notification message 24 in the effect 271 and then enlarges the notification message 24 by clicking the enlargement control 273, at which time the application interface presented by the terminal can refer to the effect 272 in fig. 27.

and responding to the movement operation of the user on the first notification message, and displaying the first notification message in the first sub-window according to the arrangement of the moved first notification message. And responding to the movement operation of the user on the second notification message, and displaying the second notification message in the first sub-window according to the arrangement of the moved second notification message.

In this embodiment, the moving operation includes an operation of controlling the first notification message to move within the first sub-window. Or controlling the operation of the second notification message moving within the second sub-window. As a feasible implementation manner, the moving operation may be that the user simultaneously selects the second notification message and then moves the display position of the second notification message by means of dragging. As a feasible implementation, the moving operation may be a user touching a moving control on the application interface. The specific implementation process may be that the user selects a second notification message in advance, and then moves the position of the second notification message through a mobile control on the touch application interface. The moving process of the first notification message may refer to the moving process of the second notification message, which is not described in detail by the applicant. The embodiment is only an exemplary illustration of two moving operations, and in the process of practical application, the moving operation may be, but is not limited to, the above two manners.

The following describes the moving process of the notification message with reference to specific figures.

Fig. 28 is a schematic diagram illustrating a change of an application interface during a second notification message moving process according to a feasible embodiment. Initially, the application interface displayed by the terminal can refer to the effect 281 in fig. 28. The user selects the notification message 12 in the effect 281 and then moves the notification message 12 upward by means of a drag, at which time the application interface presented by the terminal can refer to the effect 282 in fig. 28.

Fig. 29 is a schematic diagram illustrating a change of an application interface during a first notification message moving process according to a possible embodiment. In the initial state, the application interface displayed by the terminal can refer to the effect 291 in fig. 29. The user selects the notification message 24 in the effect 291, and then moves the notification message 24 upward by clicking the move control 293, at which time the application interface presented by the terminal can refer to the effect 292 in fig. 29.

Embodiments of the present application provide a computer system, which includes a processor and a memory, where the memory is used to store a computer program, and the processor is used to execute the computer program to implement the method provided by the embodiments of the present application.

The embodiment of the present application further provides a computer storage medium, where the computer storage medium includes computer instructions, and when the computer instructions are run on the terminal, the terminal is enabled to execute each function or step executed by the terminal in the above method embodiments.

Embodiments of the present application further provide a computer program product, which, when running on a computer, causes the computer to execute each function or step executed by the terminal in the foregoing method embodiments.

Through the description of the above embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.

It is understood that a person skilled in the art can combine, split, recombine and the like the embodiments of the present application to obtain other embodiments on the basis of several embodiments provided by the present application, and the embodiments do not depart from the scope of the present application.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, a module or a unit may be divided into only one logic function, and may be implemented in other ways, for example, a plurality of units or components may be combined or integrated into another device, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

Units described as separate parts may or may not be physically separate, and parts displayed as units may be one physical unit or a plurality of physical units, may be located in one place, or may be distributed to a plurality of different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially or partially contributed to by the prior art, or all or part of the technical solutions may be embodied in the form of a software product, where the software product is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the methods of the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A message display method is applicable to a terminal, and is characterized by comprising the following steps:

2. The message presentation method of claim 1, wherein the step of displaying an application interface comprises:

reading display attributes of the application, wherein the display attributes comprise presentation style related attributes of the display application;

3. The message presentation method of claim 1, wherein the first notification message comprises a message tag and a message content; the first sub-window comprises a first display area and a second display area, the first display area is used for displaying the message labels, the second display area is used for displaying message contents corresponding to the target labels, and the target labels are labels selected by a user or labels selected by the terminal.

4. The message presentation method of claim 3, wherein prior to the step of displaying an application interface, the method further comprises:

reading a timestamp of each of the first notification messages, the timestamp being a time at which the first notification message was generated;

and selecting the message tag contained in the first notification message generating the earliest/latest timestamp as the target tag.

5. The message presentation method of claim 3, wherein the step of displaying an application interface comprises:

clustering the first notification message according to the message tag, wherein the clustered first notification message comprises a clustering tag and at least one clustering content;

displaying an application interface, wherein the application interface comprises a first sub-window, the first sub-window is used for displaying a clustering label and target clustering content, and the target clustering content is the clustering content corresponding to the clustering label selected by a user or the clustering content corresponding to the clustering label selected by the terminal.

6. The message presentation method according to any of claims 1-5, wherein the second sub-window is used for presenting a second notification message, the second notification message being different from the first notification message.

7. The message presentation method of claim 6, wherein the method further comprises:

and transferring the second notification message from the second sub-window into the first sub-window in response to a transfer operation of the second notification message by a user, wherein the transfer operation comprises an operation of moving the second notification message from the first sub-window to the second sub-window.

8. The message presentation method of claim 6, wherein the method further comprises:

and transferring the first notification message from the first sub-window into the second sub-window in response to a transfer operation of the first notification message by a user, wherein the transfer operation comprises an operation of moving the first notification message from the second sub-window to the first sub-window.

9. The message presentation method of claim 6, wherein the method further comprises:

and in response to the deletion operation of the user, deleting the first notification message in the first sub-window or deleting the second notification message in the second sub-window.

10. The message display method of claim 6, wherein the method further comprises:

in response to a user's zoom-in operation, the first notification message is enlarged, or the second notification message is enlarged.

11. The message presentation method of claim 6, wherein the method further comprises:

12. The message presentation method of claim 6, wherein the method further comprises:

13. A terminal, characterized in that it comprises a processor for performing the method of any of the preceding claims 1-12.

14. A computer system, characterized in that the computer system comprises a processor and a memory for storing a computer program, the processor being adapted to execute the computer program to implement the method according to any of the claims 1-12.

15. A computer-readable storage medium, in which a computer program is stored which is used by a processor for implementing the method according to any one of the preceding claims 1 to 12.