Message processing method and related apparatus

Abstract

This application describes a message processing method and a related device. In this method, a terminal device receives a first push message from a first application sent by a push server; it then receives a second push message from a second application sent by the same server; the terminal device displays both messages in a first user interface; the terminal device receives a first input operation that the user applies to the second push message; and, in response to this operation, the terminal device displays a second user interface, where the format and / or display order of the second push message in the second user interface differs from the format and / or display order of the second push message in the first user interface. This simplifies querying a push message and improves the user experience.

Description

Message processing method and related apparatus This application claims priority from Chinese Patent Application No. 202110745458.X, filed with the National Intellectual Property Administration of China on June 30, 2021, and entitled "MESSAGE PROCESSING METHOD AND RELATED APPARATUS". Technical field This application relates to the field of electronic technologies, and, in particular, to a method of message processing and a related apparatus. Background In an era of mobile internet with rapidly developing information technologies, various applications (Apps) are constantly emerging. Most applications typically send important messages to the user using push notifications. Currently, a growing number of applications are installed on smartphones, and these smartphones receive an increasing number of push notifications. Because there are so many push notifications, and because they are displayed in reverse chronological order in the smartphone's notification bar, users have to manually search for them. As a result, it is difficult for users to quickly find important messages. In conclusion, in the current method of sending push messages, the operation of searching for a push message is cumbersome, a real user requirement cannot be met, and the user experience is poor. Document CN111274054 A describes a message processing method and electronic equipment, wherein the method comprises the steps: receiving a preset input of M push messages in N push messages under the condition that the N push messages are displayed on a first display screen, N and M being integers greater than 0; in response to the preset input, the content interfaces of the M push messages are displayed on a second display screen according to a preset sorting mode, and the second display screen is any display screen except the first display screen in the multiple display screens. Compendium The invention is defined by the appended claims. This application provides a message processing method and related apparatus, so that the operation of querying a push message can be simplified and the user experience can be effectively improved. According to the first aspect, this application provides a message processing method. The method includes: a terminal device receives a first push message from a first application sent by a push server; the terminal device receives a second push message from a second application sent by the push server; and the terminal device displays the first and second push messages in a first user interface. The terminal device receives a first input operation performed by a user in the second push message and displays a second user interface in response to the first input operation. A display form and / or a display sequence of the second push message in the second user interface is / are different from a display form and / or a display sequence of the second push message in the first user interface. During the implementation of this request, in response to a user input operation, the terminal device may change the display format and / or display sequence of a push message. This allows the user to assign a specific push message to a particular display format and / or sequence, enabling them to quickly locate the message. In one implementation, the second push message is a highlighted push message in the second user interface. During the implementation of this request, the user can highlight a push message of interest in the first user interface, allowing them to quickly locate the relevant push message. In one implementation, the second push message is the first push message at the top of the second user interface. During the implementation of this request, the user can set a push message of interest as the 1st push message at the top of the first user interface, so that the user can quickly locate the push message. In one implementation, the second push message is the 1st push message in the push messages of the first application in the second user interface. During the implementation of this request, the user can set a push message from the first application they are interested in as the 1st push message at the top of the push messages from the first application, so that the user can quickly locate the push message. The first push message sent by the push server carries at least one display flag. This flag is used to specify at least one storage duration, display format, and display sequence for the first push message. For the terminal device to display the first push message in a first user interface, the terminal device displays the first push message in the first user interface based on at least one display flag. The terminal device can determine a display format and / or a display sequence for the push message in the first user interface using a display marker that carries the push message, so that the user can quickly locate the push message. In one implementation, at least one display flag includes a persistence flag, and the persistence flag is used to instruct the terminal device to store the first push message within the first duration. After the terminal device displays the first push message in the first user interface based on at least one display flag, the method further includes: the terminal device deletes the first push message based on the persistence flag at a time whose interval from a time of receiving the first push message is the first duration. During the implementation of this request, the terminal device deletes the first push message only after its persistence period (i.e., initial duration) expires. This prevents an important push message from being automatically deleted by the system prematurely. In one implementation, at least one display flag includes a global pinning flag at the top. The terminal device displaying the first push message in the first user interface based on at least one display flag includes: displaying the first push message as the first push message at the top of the first user interface based on the global pinning flag at the top. In one implementation, displaying the first push message as the first push message at the top of the first user interface based on the global pinning flag at the top includes: displaying, based on the global pinning flag at the top, the first push message as the first push message at the top of the first user interface within a second duration after the first push message is received.The method also includes: the terminal device removes the global fixation mark at the top of the first push message at a time whose interval from a time of receipt of the first push message is the second duration. During the implementation of this request, the terminal device can, based on the global pinning mark at the top that carries the push message, set the push message as the first push message at the top of the first user interface within the global pinning duration at the top (i.e., the second duration), so that the user can quickly locate the push message. In one implementation, at least one display mark includes a pinning mark at the top within the application. The terminal device displaying the first push message in the first user interface based on at least one display mark includes: displaying the first push message as the first push message in the push messages of the first application in the first user interface based on the pinning mark at the top within the application. In one implementation, displaying the first push message as the first push message in the first application's push messages on the first user interface, based on the pinning mark at the top within the application, includes: displaying, on the first user interface, based on the pinning mark at the top within the application, the first push message as the first push message in the first application's push messages within one-third of the duration after the first push message is received. The method further includes: the terminal device removes the pinning mark at the top within the application from the first push message at a time whose interval from a time of receiving the first push message is one-third of the duration. During the implementation of this fulfillment of this request, the terminal device can set, based on the pinning mark at the top within the application that carries the push message, the first push message of the first application to the 1st push message at the top of the push messages of the first application within the pinning duration at the top within the application (i.e., the third duration), so that the user can quickly locate the push message. In one implementation, at least one display flag includes a highlight flag. Ensuring the terminal device displays the first push message in the first user interface based on at least one display flag includes: highlighting the first push message in the first user interface based on the highlight flag. In one implementation, highlighting the first push message in the first user interface based on the highlight flag includes: highlighting, based on the highlight flag, the first push message in the first user interface within one-fourth of the duration after the first push message is received. The method further includes: the terminal device removes the highlight flag from the first push message at a time whose interval from the time of receiving the first push message is one-fourth of the duration. During the implementation of this request, the terminal device can highlight, based on the highlighting mark carried by the push message, the push message in the first user interface within the highlighting duration (i.e., the fourth duration), so that the user can quickly locate the push message. In one implementation, the first highlighted push message includes one or more of the following display features: compared to a non-highlighted push message, the first push message has a different light background color; compared to a non-highlighted push message, the first push message has a different font, font size, and / or color; and compared to a non-highlighted push message, the first push message displays a highlighted icon. This implementation of the application does not specifically limit any particular form of highlighting display. According to a third aspect, this application provides a terminal device, which includes one or more processors and one or more memories. The one or more memories are coupled to the one or more processors. The memory is configured to store computer program code, and the computer program code includes computer instructions. When the one or more processors execute the computer instructions, the terminal device can perform the message processing method in any possible implementation of the first aspect. According to a fifth aspect, an implementation of this request provides a computer-readable storage medium, which includes computer instructions. When the computer instructions are executed on a computer, the terminal device can perform the message processing method in any possible implementation of the first aspect. Brief description of the drawings FIG.1 is a schematic diagram of a communications system according to one implementation of this request; FIG.2 is a block diagram of a software structure according to one implementation of this request; FIG. 3A and FIG. 3B are schematic diagrams of a user interface for a notification panel according to one implementation of this request; Figures 3C to 3E show a schematic diagram of a push message mailbox user interface according to one implementation of this application; Figures 3F to 3I show a schematic diagram of a user interface for opening a push message mailbox according to an implementation of this request; FIG.4A is a schematic diagram of a user interface that is displayed after receiving a global pinning push message at the top, according to one implementation of this request; FIG.4B is a schematic diagram of a user interface that is displayed after receiving a pinning push message at the top within the application, according to a realization of this request; Figures 4C to 4F are a schematic diagram of a user interface that is displayed after receiving a highlighted push message, according to a realization of this request; Figures 5A to 5G are a schematic diagram of a user interface for manually setting a fixing state on top according to an implementation of this request; Figures 6A to 6L are a schematic diagram of another user interface for manually setting a fixing state on top according to an implementation of this request; Figures 7A to 7F are a schematic diagram of a user interface for manually setting a highlighted state according to a realization of this request; Figures 8A to 8F are a schematic diagram of another user interface for manually setting a highlighted state according to a realization of this request; Figures 9A to 9C are a schematic diagram of a user interface for manual deletion according to one implementation of this application; Figures 10A to 10F are a schematic diagram of another user interface for manual deletion according to one implementation of this application; Figures 11A to 11C are a schematic flowchart of a message processing method according to one implementation of this application; FIG.12A and FIG.12B are a schematic flowchart of a push message preprocessing method according to one realization of this request; FIG.13 is a schematic diagram of a global fixing process at the top according to one embodiment of this application; FIG. 14 is a schematic diagram of a top-fixing process within the application, according to an embodiment of this application; FIG. 15 is a schematic diagram of a highlighting process according to one implementation of this request; FIG. 16 is a schematic flowchart of another message processing method according to one implementation of this request; FIG. 17 is a schematic diagram of a terminal device structure according to one embodiment of this application; and Figure 18 is a schematic diagram of the server structure according to one implementation of this application. Description of the implementations The technical solutions in embodiments of this application are clearly described below in detail with reference to the accompanying drawings. In the descriptions of embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B may mean either A or B. The term "and / or" in this specification simply describes an associative relationship to describe associated objects and indicates that three relationships are possible. For example, A and / or B may mean the following three cases: only A exists, both A and B exist, and only B exists. Furthermore, in the descriptions of embodiments of this application, "a plurality of" means two or more. The terms “first” and “second” below are for descriptive purposes only and should not be construed as an indication or inference of materiality or as an implied indication of a number of technical features. Therefore, a feature limited by “first” or “second” may explicitly or implicitly include one or more features. In the embodiment descriptions in this application, unless otherwise stated, “a plurality of” means two or more. First, a communications system 10 provided in embodiments of this application is described. Figure 1 shows an example of a schematic diagram of a communications system 10 structure according to one embodiment of this application. As shown in Figure 1, the communications system 10 includes one or more terminal devices (e.g., a terminal device 100), one or more application development servers (e.g., an application server 200), and one or more push servers (e.g., a push server 300). The application server 200 and the push server 300 can communicate with each other using a wireless communications network and / or a wired communications network. The push server 300 and the terminal device 100 can also communicate with each other using a wireless communications network or a wired communications network. The application server 200 can be a single server, a group of servers comprising multiple servers, or a cloud computing center. The application server 200 is a server that sends a message for a specific application (for example, a game application, a navigation application, a social application, a video application, or a reading application) installed on the terminal device 100. The application server 200 can also provide another service for the aforementioned application; for example, a real-time navigation service for the navigation application and an instant messaging service for the social application. This is not specifically limited herein. The push server 100 can be a single server, a group of servers comprising multiple servers, or a cloud computing center.The push server 100 is configured to perform preprocessing (e.g., security detection) on a push message from the application server 200, and can send a preprocessed push message to the terminal device 100. In this instance, application server 200 can request a push message persistence service from push server 100 for a specific application (e.g., application 1). Furthermore, based on this push message persistence service, application server 200 can also request a global pinning service, an in-application pinning service, and a highlighting service for a push message from application 1. Push message 1 is used as an example. The push message persistence service refers to the following: within the persistence duration of push message 1, push message 1 is stored in a push message mailbox of device 100 terminal, to prevent the system of device 100 terminal from automatically deleting push message 1 within a preset time period. The global pinning service at the top of push messages refers to the following: within the pinning duration at the top of push message 1, push message 1 is displayed as the 1st at the top of the push messages in the push message mailbox displayed on the terminal device 100. The pinning service at the top within the application for push messages refers to the following: within the pinning duration at the top within the application of push message 1, push message 1 is displayed as the 1st at the top of the push messages of application 1, in the push message mailbox that is displayed on the device 100 terminal. The push message highlighting service refers to the following: during the highlighting period of push message 1, push message 1 is displayed more prominently in the push messages of the push message inbox displayed on device 100. For example, push message 1 has a brighter backlight, a special character color, bold characters, and / or a specific icon. This is not specifically limited in this document. In this implementation of this request, push message 1 is used as an example. Push message 1 sent by application server 200 can carry parameters such as a persistence flag, a global pinning flag, an application pinning flag, and / or a highlighting flag. The four parameters above are used respectively to identify the persistence state, the global pinning state, the application pinning state, and the highlighting state of the push message. Consequently, the push message sent by application server 200 can carry additional parameters such as the persistence duration, the global pinning duration, the application pinning duration, and / or the highlighting duration of push message 1.The push server can preprocess the push message based on the parameter carried by the push message sent by the application server. The terminal device can perform, based on a parameter carried by a push message delivered by the push server, global pinning to the top, pinning to the top within the application, highlighting, and / or similar actions on the push message in a push mailbox user interface. In this embodiment of this application, the terminal device 100 can be a terminal running iOS, Android, Microsoft, or another operating system. For example, the terminal device 100 can be a mobile phone, tablet, desktop computer, laptop, handheld computer, notebook computer, ultramobile personal computer (UMPC), netbook, cell phone, personal digital assistant (PDA), augmented reality (AR) device, virtual reality (VR) device, artificial intelligence (AI) device, wearable device, vehicle-mounted device, smart home device, smart city device, and / or similar devices. A specific type of terminal device 100 is not specifically limited in this embodiment of this application. The terminal device 100, the application server 200, and the push server 300 can be deployed on land, including indoor or outdoor devices, handheld devices, or vehicle-mounted devices; or they can be deployed on a water surface; or they can be deployed on an aircraft or an artificial satellite in the air. This is not limited in the implementation of this application. It should be noted that FIG. 1 is simply a schematic diagram of a communications system structure according to one embodiment of this application. The communications system may also include other devices, for example, a wireless relay device and a wireless backhaul device (which are not shown in FIG. 1). This is not limited to the scope of this specification. The following describes a software system for the 100-terminal device in embodiments of this application. A software system for the 100-terminal device may use a layered architecture, an event-driven architecture, a microkernel architecture, a microservices architecture, or a cloud architecture. In this embodiment of the present invention, an Android system with a layered architecture is used as an example to describe a software structure for the 100-terminal device. FIG. 2 is a block diagram of a software structure of the terminal device 100 according to an embodiment of the present invention. In a layered architecture, the software is divided into several layers, each with a clear function and task. The layers communicate with each other through a software interface. In some implementations, the Android system is divided from top to bottom into four layers: an application layer, an application framework layer, an Android runtime and system library, and a kernel layer. The application layer may include a number of application packages. As shown in FIG.2, the application package may include applications such as Camera, Gallery, Calendar, Phone, Maps, Navigation, WLAN, Bluetooth, Music, Videos, and Messages. The application framework layer provides an application programming interface (API) and a programming framework for an application within the application layer. The application framework layer includes some predefined functions. As shown in FIG.2, the application framework layer may include a window manager, a content provider, a display system, a phone manager, a resource manager, a notification manager, and the like. The window manager is configured to manage a windowing program. The window manager can determine screen size, whether a status bar is present, whether a screen is locked, whether a screenshot is being taken, and similar actions. The content provider is configured to store and retrieve data, and to allow an application to access that data. The data may include video, images, audio, calls made and received, browsing history and bookmarks, an address book, and similar items. The display system includes visual controls, such as controls for displaying text and images. This system can be used to build an application. The display interface can include one or more views. For example, a display interface that includes a message notification icon might include a text view and an image view. The phone manager is configured to provide communication functions for the terminal device, such as managing call status (including answering, rejecting, and similar actions). The resource manager provides various resources for an application, such as a localized character string, an icon, an image, a presentation file, and a video file. The notification manager allows an application to display notification information in a status bar and can be configured to broadcast a notification message. The displayed information can disappear automatically after a brief pause without user interaction. For example, the notification manager can be configured to notify of a download completion, provide message notifications, and so on. The notification manager can also be a notification that appears in a top system status bar, in the form of a graphic or scrolling text (for example, a notification from an application running in the background), or it can be a notification that appears on the screen in the form of a dialog box. For example, text information might be displayed in the status bar, a warning tone might play, an electronic device might vibrate, or an indicator light might flash. In this implementation of this request, the notification manager includes a push service and a push message inbox. The push service is responsible for establishing a long link with the 200 push server, receiving a push message delivered by the 200 push server, and executing the corresponding logic for each parameter (e.g., a persistence flag, a global pinning flag, a pinning flag within the application, and / or a highlighting flag, persistence duration, global pinning duration, pinning duration within the application, and / or highlighting duration) in the push message delivered by the push server. In this way, the push message can be permanently displayed, pinned globally to the top, pinned to the top within the application, and highlighted in the push message inbox. The push message inbox is a system input provided by a smart terminal system for storing push messages. In the push message inbox user interface, the 100 terminal device can perform global pinning to the top, pinning to the top within the application, and / or highlighting of push messages according to the parameters of each push message. The Android runtime environment includes a kernel library and a virtual machine. The Android runtime environment is responsible for programming and managing the Android system. The core library includes two parts: a function that needs to be called by a Java language and an Android core library. The application layer and the application framework layer run in the virtual machine. The virtual machine executes Java files from the application layer and the application framework layer as binary files. The virtual machine is configured to implement features such as object lifecycle management, stack management, thread management, security and exception handling, and garbage collection. The system library may include a plurality of function modules, for example, a surface manager (surface manager), a multimedia library (media library), a three-dimensional graphics processing library (e.g., OpenGL ES), and a 2D graphics engine (e.g., SGL). The surface manager is configured to manage a visualization subsystem and provide merging of 2D and 3D layers for a plurality of applications. The media library supports playback and recording in a variety of commonly used audio and video formats, image files, and similar formats. The media library can support a variety of audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG. The three-dimensional graphics processing library is configured to implement three-dimensional graphics drawing, image rendering, compositing, layer processing, and the like. The 2D graphics engine is a drawing engine for drawing in 2D. The kernel layer is a layer between the hardware and the software. The kernel layer includes at least a display driver, a camera driver, an audio driver, and a sensor driver. The following describes an example of an application scenario for a message sending method provided in implementations of this application, with reference to the attached drawings. The following describes an example of a startup interface 11 provided in this implementation of this application. For example, FIG. 3A shows the home interface 11 on the terminal device 100, which is configured to display the applications installed on the terminal device 100. The home interface 11 may include: a status bar 101, a calendar indicator 102, a weather indicator 103, a tray 104 containing icons for commonly used applications, and other application icons 105. Tray 104, which includes icons for commonly used applications, may display: a "Phone" icon, a "Contacts" icon, a "Messages" icon, and a "Camera" icon. The other application icons 105 may display: a "Message Box" icon 105A, a "Photo Album" icon, a "Music" icon, an "Email" icon, a "Note" icon, a "Settings" icon, and similar icons. The home interface 11 may also include a page indicator 106. The other application icons may be distributed across multiple pages, and the page indicator 106 can be used to indicate the specific page on which a user is viewing an application. The user can swipe left or right in an area containing the other application icons to view an application's icon on another page. It can be understood that FIG.3A simply shows an example of the user interface on the terminal device 100, and should not constitute a limitation in this implementation of this application. The following describes an example of a notification bar interface provided in this implementation of this request. For example, the status bar 101 can receive an input operation (for example, a swipe-down operation shown in FIG. 3A) from the user, and in response to the input operation, the terminal device 100 can display the notification bar interface 12 shown in FIG. 3B. As shown in FIG. 3B, the notification bar interface 12 can display message cards (for example, from message card 201 to message card 206) corresponding to push messages that have recently been stored in the notification bar. Message card 201 is used as an example. The message card includes a push message (201A) and a push message reception time (201B). For example, push message 201A might receive an input operation (e.g., a touch operation) from the user, and in response to the input operation, the terminal device (100) displays the detailed content of push message 201A. Based on the reception times from message card 201 to message card 206, push messages are arranged from top to bottom in a sequence that is the reverse of their reception times on the notification bar interface (12). Specifically, for two push messages received sequentially, a message card for a push message received later is closer to the top of the terminal device than a message card for a push message received at the current time.It's understandable that when a large number of push messages are stored in the notification bar, the user has to manually search for the push message they need, which is time-consuming and leads to a poor user experience. It should be noted that, in this implementation of this request, the specific display content of the push message (e.g., push message 201A) on the message card can be a title, an introduction, or some content from the push message 201A. This is not specifically limited in this document. In some implementations, the notification bar interface 12 may include a delete control 207. The delete control 207 can receive an input operation (for example, a touch operation) from the user, and in response to the input operation, the device 100 terminal can delete all push messages stored in the notification bar. Typically, the device 100 terminal periodically and automatically deletes the push messages stored in the notification bar, or automatically deletes the push messages stored in the notification bar after a restart. Consequently, the user could miss an important push message. It should be noted that a specific format for displaying a push message is not limited in this application. This specification uses a message card display format as a descriptive example. The message card may also be referred to as a message bar or message box. This is not specifically limited in this specification. In this instance of this request, for a push message 1 that has a persistence flag, device 100 makes a copy of the push message 1, stores the copy in a push message mailbox, and can view the copy in a push message mailbox user interface. Device 100 deletes the push message 1 only after the persistence period of the push message 1 expires.Furthermore, when push message 1 has a global pinning mark at the top, it is globally pinned to the top of the push inbox user interface; when push message 1 has a pinning mark within the application, it is pinned to the top of the push inbox user interface; and when push message 1 has a highlighting mark, it is highlighted in the push inbox user interface. It can be understood that a global pinning display, an in-app pinning display, and / or a highlighting display can help the user quickly locate an important push message. For example, the "Message Box" icon 105A shown in FIG.3C can receive an input operation (e.g., a touch operation) from the user, and in response to the input operation, the terminal device 100 displays a push message box user interface 13 shown in FIG.3D. In some implementations, the push mailbox user interface includes several message cards. Each of the first N message cards (for example, message card 301) can display a globally pinned push message stored in the push mailbox, and the message cards following the first N are message cards that correspond to various applications, each of which has requested a persistence service. For example, message card 302 corresponds to a reading application, message card 303 to a video application, message card 304 to a gaming application, message card 305 to a bank card application, and message card 306 to a music application. N is a positive integer. In some implementations, the user interface 13 may also include a search control 307 and / or a configuration control 308. The search control 307 is configured to search the push message mailbox for a push message related to a character entered by the user. The configuration control 308 can receive an input operation (for example, a touch operation) from the user, and in response to the input operation, the terminal device 100 displays a configuration interface for the push message mailbox. In some embodiments, when the push message mailbox already displays N global pinning push messages on top, if the terminal device 100 receives another global pinning push message on top, the global pinning on top of the first push message received from the N global pinning push messages on top is canceled. The value of N is not specifically limited in this implementation of this application. In some implementations, the maximum value of N is 1, and the push message mailbox can only store one top-pin globally pinned message at a time. In some implementations, the value of N can be greater than 1, and a top-to-bottom arrangement sequence of the N message cards in user interface 13 can be a reverse sequence of top-pin globally pinned push message reception times corresponding to the message cards. For example, user interface 13 includes only one top-pin globally pinned push message. As shown in FIG. 3D, the first message card 301 at the top of user interface 13 includes a top-pin globally pinned push message 301A.Optionally, the 301 message card may also include at least one of an application icon 301B and an application name 301C that correspond to an application (i.e., a video application) corresponding to the push message 301A, and a time 301D of receipt of the push message 301A. It can be understood that, when the push message mailbox does not store a globally pinned push message at the top, the user interface 13 does not include a message card corresponding to the globally pinned push message at the top. In some implementations, a message card for each application can handle multiple push messages. However, in user interface 13, the message card can display a maximum of M push messages, and any additional push messages handled by the message card are hidden and not displayed. M is a positive integer. The value of M is not specifically limited in this implementation of the application. For example, M could be 1, 2, or 3. A later implementation uses an example where M equals 2 for the description.For example, the push message mailbox stores at least two non-global pinned push messages on top of the reading application, at least two non-global pinned push messages on top of the video application, one non-global pinned push message on top of the gaming application, and one non-global pinned push message on top of the bank card application. As shown in FIG. 3D, the reading application's message card 302 includes one 302A push message and one 302B push message, the video application's message card 303 includes one 303A push message and one 303B push message, and the gaming application's message card 304 and the bank card application's message card 305 each include one push message.In some embodiments, a message card corresponding to each application (e.g., application 1) can receive an input operation from the user, and in response to the input operation, the terminal device 100 can display more push messages managed by the message card of application 1. In some implementations, the message card for each application also includes a time for receiving a push message recently received by the application. For example, message card 302 also includes a time 302C for receiving a push message recently received by the reading application. In some implementations, a message card for each application handles a maximum of K pinned-to-top push messages within the application, where K is a positive integer. The value of K is not specifically limited in this implementation. For example, K could be 1, 2, or 3. Optionally, the top-to-bottom arrangement of the first K pinned-to-top push messages within the application, displayed on the message card for each application, is a reverse sequence of push message reception times. The top-to-bottom arrangement of non-pinned-to-top push messages within the application, displayed on the message card for each application, is also a reverse sequence of push message reception times.In a later embodiment, an example is used in which the value of K is 1 for the description. It is understood that if the push message mailbox stores a pinned-to-the-top push message within application 1, the first push message displayed on the message card for application 1 is the pinned-to-the-top push message within the application; otherwise, the first push message displayed on the message card for application 1 is a non-pinned-to-the-top push message within the application. In some implementations, the user can preset a value for M, a value for N, and / or a value for K, or the terminal device can preset them. This is not specifically limited in this memory. In some implementations, a top-to-bottom arrangement of application-related message cards in the user interface (UI) 13 can be the reverse of the sequence of the last push message received by the application-related message cards. Specifically, for two applications sequentially receiving push messages without a global top fix, a message card from an application receiving a push message later is closer to the top of the device 100 terminal than a message card from an application receiving a push message at the current time. In this implementation of the application, after the persistence period of each persistent push message expires, the push message mailbox deletes the push message. In some implementations, a message card for a globally pinned push message at the top also includes a deletion timestamp for the push message, and an application message card also includes a deletion timestamp for a push message recently received by the application. For example, as shown in FIG. 3E, message card 301 also includes a deletion timestamp 301E for push message 301A, and message card 302 also includes a deletion timestamp 302D for a push message recently received by the reading application. In some implementations, a display state for each push message is further identified in the user interface 13, and the display state of the push message can include read and / or unread. For example, as shown in FIG. 3E, when the user has viewed the global pinning push message at the top, the terminal device 100 identifies the push message using a read icon 301F; and when the push message 303B has been viewed on the video application message card 303, the terminal device 100 identifies the push message using a read icon 303C. In this implementation of this application, a push message that is not viewed by the user can be identified using an unread identifier. It should be noted that, in one implementation, the push message inbox may be a system application separate from the notification bar, and the "Message Inbox" icon (105A) is a shortcut entry to the system application. In another implementation, the push message inbox may be a feature implementation of the notification bar, and the "Message Inbox" icon (105A) is a shortcut entry to the feature. This is not specifically limited in this application. In some implementations, the push message inbox is a separate application from the notification bar. The push message inbox can retrieve push messages in the notification bar in real time and manage and display the received push messages. Optionally, the push message inbox can retrieve push messages in the notification bar only after the user grants permission for it to do so. For example, after the "Message Inbox" icon (105A) receives user input, the terminal device (100) first displays a permission request box (321) shown in Figure 3F. The permission request box (321) includes warning information (321A), a "Prohibit" control (321B), and an "Allow" control (321C).The 321A warning information is used to notify the user that the "push message box" needs permission to receive push messages in the notification bar. The 321B "Prohibit" control is used to reject the permission request and close the 321 permission request box. The 321C "Allow" control is used to allow the permission request. For example, in response to an input operation on the 321C "Allow" control, the terminal device 100 allows the push message box to receive a push message in the notification bar and displays, based on the push message received by the push message box, the push message box user interface 13 shown in FIG. 3D. In some embodiments, the push message inbox is a feature implementation of the notification bar. The terminal device 100 can manage and display a push message using the push message inbox only after the user enables a push message inbox feature in the notification bar. For example, the notification bar interface 12 may further include a control 208, as shown in FIG. 3G. As shown in FIG. 3H, in response to an input operation on control 208, the terminal device 100 may display a push message inbox feature control bar 322 in a user interface 14, where the feature control bar 322 includes an "ON / OFF" control 322A.When the "ON / OFF" control 322A is in the ON state, the push message inbox function is enabled; conversely, when the "ON / OFF" control 322A is in the OFF state, the push message inbox function is disabled. For example, in response to an input operation (e.g., a touch operation) for the "ON / OFF" control 322A, the terminal device can switch the "ON / OFF" control 322A to an ON state, as shown in FIG. 3I, and display messages from message card 301 to message card 305 in user interface 14 based on the push messages received by the notification bar. Optionally, in response to the input operation, search control 307 and / or configuration control 308 are also displayed on user interface 14.In some embodiments, after the user enables the push message mailbox function using the "ON / OFF" control 322A, in response to the input operation on the "Message Mailbox" icon 105A, the terminal device 100 can display the user interface 14 shown in FIG.3I. In some embodiments, in response to the user input operation shown in FIG. 3A, the terminal device 100 displays the user interface 13, and the user interface 13 is the notification bar interface of the terminal device 100. The device 100 terminal shown in FIG. 3D is used below as an example to describe a user interface that is displayed after the device 100 terminal receives several persistent push messages. For example, in the user interface 13 shown in FIG. 3D, push message 301A is pinned globally at the top, and push messages 302A and 303A are pinned at the top within the application. In some embodiments, for example, a value of N is 1. After receiving a global pinning push message on top (for example, a 309A push message), the terminal device 100 converts a global pinning push message on top (for example, the 301A push message shown in FIG. 3D) currently set by the system into a non-global pinning push message on top, and sets the 309A push message as a global pinning push message on top. Furthermore, after the video application's 301A push message is converted into a non-global pinning push message on top, the video application's 303 message card handles the 301A push message.Optionally, the 301A push message is a non-pinned push message at the top within the video application application, and the 303 message card sorts and displays the 301A push message based on the time of receipt of the 301A push message. For example, after the terminal device 100 shown in FIG. 3D receives the push message 309A shown in FIG. 4A, the terminal device displays a message card 309 corresponding to the push message 309A shown in FIG. 4A on user interface 13. This message card 309 is the first message card at the top of user interface 13 shown in FIG. 4A. Optionally, the push message 301A is a recently received push message from the video application, except for the pinned push message 303A at the top within the application. After the global pinning of the push message 301A is undone, the push message 301A is displayed as a push message following the push message 303A on the video application's message card 303. In some embodiments, for example, a value of N is 2. The user interface 13 shown in FIG. 3D currently displays only one global pinning push message 301A at the top. For example, as shown in FIG. 4B, after receiving a global pinning push message at the top (e.g., push message 309A), the terminal device 100 shown in FIG. 3D moves down one global pinning push message at the top (e.g., push message 301A shown in FIG. 3D) currently set by the system, displays the push message as the second push message at the top of the user interface 13, and sets the 309A push message as a global pinning push message at the top. In some embodiments, after receiving an in-application pinning push message (e.g., push message 303D), the terminal device 100 performs in-application pinning of the 303D push message to the corresponding video application's 303 message card. Optionally, a value of K is greater than 1. After the terminal device 100 receives the 303D push message, the first in-application pinning 303A push message of the current video application is moved down to become the second in-application pinning 303A push message. Optionally, a value of K is 1. After receiving the 303D push message, the terminal device 100 cancels the in-application pinning of the first in-application pinning 303A push message of the current video application.The 303 message card sorts and displays the 303A push message based on the time of receipt of the 303A push message. In a later implementation, an example is used where the value of K is 1 for the description. For example, as shown in FIG.4C, after receiving the 303D push message, the 100 terminal device shown in FIG.4A cancels the application attachment of the 303A push message, displays the 303D push message as the 1st push message on the 303 message card, and displays the 303A push message as the 2nd push message on the 303 message card. In some implementations, after receiving a highlighted push message (for example, a 302E push message), the 100 terminal device displays the push message as the first unfixed push message in the corresponding 302 message card of the reading application, based on the push message's reception time. Furthermore, the push message is highlighted during display. For example, the 302A push message on the 302 message card of the reading application shown in FIG. 4C is a pinned message at the top of the application. As shown in FIG. 4D, after receiving the 302E push message, the terminal device 100 shown in FIG. 4C displays the 302E push message as the second push message on the 303 message card and displays the content of the 302E push message in bold. In some embodiments, after receiving a highlighted push message (for example, the 302E push message), the terminal device 100 separately displays the 302E push message on a newly created message card and highlights the message during the display process. Optionally, the newly created message card is adjacent to the 302 message card of the reading application corresponding to the 302E push message and is located closer to the top of the terminal device 100. For example, as shown in FIG. 4E, after the terminal device 100 shown in FIG. 4C receives the 302E push message, the terminal device 100 displays the 302E push message on a 310 message card and highlights the backlight of the 310 message card. In some implementations, after receiving a highlighted and pinned push message within the application (for example, the 302E push message), the terminal device simultaneously pins and highlights the 302E push message within the application on the 302 message card of the reading application. For example, as shown in FIG. 4F, after receiving the highlighted and pinned 302E push message within the application, the terminal device shown in FIG. 4C displays the 302E push message as the first push message on the 302 message card and displays the content of the 302E push message in bold. It can be understood that the 302E push message may be more noticeable after being highlighted. A specific implementation of highlighting is not limited to this particular instance of the request. In this instance of this request, for a push message displayed in the push message inbox, the user can manually set an information status for the push message based on their requirements and preferences. The information status of the push message includes pinned status, highlighted status, display status, and similar options. The push message mailbox user interface 13 shown in FIG.4E is then used as an example to describe in detail how the user manually sets the information status of the push message. In some implementations, the terminal device 100 receives a push message in user interface 13 from the push message mailbox via the real-time notification bar. The push message sequence in user interface 13 may be the same as, or different from, the push message sequence in the notification bar. This is not specifically limited in this document. In this execution of this request, a push message 1 displayed on user interface 13 can receive a user input operation, and in response to the input operation, the terminal device 100 can change the pinning state of the push message 1 on user interface 13. The pinning state of the push message 1 includes a global pinning state, a pinning state within the application, or a state with no global pinning and no pinning within the application. In some embodiments, each message card in the user interface 13 further includes a top-mounted pinning control used to change a top-mounted pinning state. For example, as shown in FIG. 5A, a message card 309 includes a top-mounted pinning control 401, a message card 310 includes a top-mounted pinning control 402, and a message card 303 includes a top-mounted pinning control 403. For a global pinning push message at the top, the following message card 309 is used as an example to describe how a user manually sets a pinning state at the top of the push message. Message card 309 includes only one push message, 309A, for global top-mounted video application. The top-mounted control 401 can receive an input operation (e.g., a touch operation) from the user. In response to the input operation, terminal device 100 displays a "Cancel Global Top-Mounted" control 401A, as shown in Figure 5B. The "Cancel Global Top-Mounted" control 401A can receive an input operation (e.g., a touch operation) from the user. In response to the input operation, terminal device 100 cancels the global top-mounted push message 309A and commands and displays the push message 309A using message card 303 of the video application. For example, as shown in Figure 5C, in response to the input operation, the push message 309A is displayed as 2.º push message on message card 303. For a message card that includes only one push message with no global pinning at the top, the following message card 310 is used as an example to describe how a user manually sets a pinning state at the top of the push message. As shown in FIG. 5D, the message card 310 includes only one highlighted push message 302E, and the top-fixing control 402 can receive an input operation (e.g., a touch operation) from the user. In response to the input operation, the terminal device 100 displays a "Global Top Fixing" control 402A and a "Top Fixing Within the Application" control 402B, as shown in FIG. 5E. As shown in FIG. 5E and FIG. 5F, the "Global Top Fixing" control 402A can receive an input operation (e.g., a touch operation) from the user, and in response to the input operation, the terminal device 100 fixes the message card 310 on top. As shown in FIG. 5F and FIG.5G, the 402B control of "Fixing on top within the application" can receive an input operation (e.g., a touch operation) from the user and, in response to the input operation, the terminal device 100 displays the 302E push message as the 1st push message on the 302 message card. For a message card that includes a plurality of push messages without global pinning at the top, the following message card 303 is used as an example to describe how a user manually sets the pinning state at the top of a push message. As shown in FIG. 6A and FIG. 6B, the video application message card 303 includes a plurality of push messages without global pinning at the top (e.g., push message 303D and push message 303A), and the pinning control 403 at the top can receive an input operation (e.g., a touch operation) from the user. In response to the input operation, the terminal device 100 displays a selection control 403A corresponding to the video application, a selection control 403B corresponding to push message 303D, and a selection control 403C corresponding to push message 303A. As shown in FIG. 6B, after the user selects the corresponding video application selection control 403A, the terminal device 100 displays the "Global Pin to Top" control 403D, shown in FIG. 6C. In this case, the "Global Pin to Top" control 403D is used to perform global pinning to the top of the video application's message card 303. For example, as shown in FIG. 6D, in response to an input operation (e.g., a touch operation) for the "Global Pin to Top" control 403D, the terminal device 100 displays the video application's message card 303 as the first of the message cards corresponding to a plurality of applications in the user interface 13. Optionally, as shown in FIG.6D, the video application message card 303 is displayed after the global pinning push message 309A message card at the top. Optionally, the video application message card 303 can also be displayed as the first message card at the top of the user interface 13. As shown in FIG. 6E, after the user selects the corresponding selection control 403B for message 303D push, the terminal device 100 displays the "Global Top Pin" control 403D and the "Cancel Top Pin Within Application" control 403E, as shown in FIG. 6F. In this case, the "Global Top Pin" control 403D is used to display message 303D push via global top pinning. The "Cancel Top Pin Within Application" control 403E is used to cancel the top pinning of message 303D push within the application. As shown in FIG.6G, in response to an input operation (e.g., a touch operation) for the 403D control of "Global Fixing on Top", the terminal device 100 displays the 303D push message on the 1st message card which is on top. As shown in FIG. 6H, after the user selects the selection control 403C corresponding to the push message 303A, the terminal device 100 displays the "Global Top Fixing" control 403D and the "Top Fixing Within the Application" control 403F, as shown in FIG. 6I. In this case, the "Global Top Fixing" control 403D is used to perform the global top fix of the push message 303A, and the "Top Fixing Within the Application" control 403F is used to perform the top fix within the application of the push message 303A. For example, as shown in FIG.6J, in response to an input operation (e.g., a touch operation) on the "Global Fix on Top" control 403D, the terminal device 100 displays the push message 303A as the 1st message card that is on top.For example, as shown in FIG.6K, in response to an input operation (e.g., a touch operation) on the "Attach to top within application" control 403F, the terminal device 100 displays push message 303A as the 1st push message on the video application message card 303. In some embodiments, when an application that the user has selected to pin globally to the top (for example, the video application corresponding to message card 303 shown in FIG. 6C) is the same as an application corresponding to a push message pinned globally to the top (for example, push message 309A shown in FIG. 6C), in response to an input operation on control 403D for "Global Pin to Top", the terminal device 100 merges message card 303 and message card 309 corresponding to push message 309A, and displays a merged message card as the first message card in the user interface 13. For example, as shown in FIG. 6L, in response to the input operation, the terminal device 100 stops displaying push message card 309, displays push message 309A as the 1st push message on message card 303, and displays message card 303 as the 1st message card on user interface 13. In some embodiments, after the user sets push message 1 (for example, push message 303D shown in FIG. 6G or push message 303D shown in FIG. 6J) as a globally pinned push message on top, the terminal device 100 displays push message 1 using global pinning on top, until the user cancels the global pinning on top of push message 1. In some embodiments, after the user sets push message 1 (for example, push message 303D shown in FIG. 6G or push message 303D shown in FIG. 6J) as a globally pinned push message on top, if the terminal device 100 receives push message 2 that carries a globally pinned on top marker, the terminal device 100 displays push message 2 as the next push message (i.e., 2).º global fix push message at the top) of the 1 push message in the user interface 13. In some embodiments, after the user sets message 1 push (for example, message 303A push shown in FIG. 6K) as a pinned push message on top within application 1, the terminal device 100 pins message 1 push on top of the message cards in application 1, until the user cancels pinning message 1 push on top within the application. In some embodiments, after the user sets push message 1 (e.g., push message 303A shown in FIG. 6K) as a pinned-on-top push message within application 1, if terminal device 100 receives push message 2 from application 1 that has a pinned-on-top mark within the application, terminal device 100 displays push message 2 as the next push message (i.e., the 2nd pinned-on-top push message within the application on the message card of application 1) of push message 1 on the message card (e.g., push message card 303 shown in FIG. 6K) of application 1. In this execution of this request, the push message 1 in user interface 13 can receive an input operation from the user, and in response to the input operation, the terminal device 100 can change the highlighting state of the push message 1. The highlighting state of the push message 1 includes a highlighted state and a non-highlighted state. For a message card that includes only one highlighted push message, the following is used as an example of message card 310 to describe how a user manually sets a push message highlighting status. For example, as shown in FIG. 7A and FIG. 7B, message card 310 contains a highlighted push message 302E from a reading application, and message card 310 can receive an input operation (for example, a left swipe operation shown in FIG. 7A) from the user. In response to the input operation, terminal device 100 displays a "Cancel Highlight" control 501A. As shown in FIG. 7C, in response to an input operation (for example, a touch operation) on the "Cancel Highlight" control 501A, terminal device 100 displays the push message 302E on message card 302 from the reading application without highlighting. For a message card that includes only one non-highlighted push message, the following message card 309 is used as an example to describe how a user manually sets a push message highlighting status. For example, as shown in FIG. 7D and FIG. 7E, message card 309 contains an unhighlighted push message 309A from a video application, and message card 309 can receive an input operation (for example, a left swipe, as shown in FIG. 7D) from the user. In response to the input operation, terminal device 100 displays a "Highlight" control 501B. As shown in FIG. 7F, in response to an input operation (for example, a touch operation) for the "Highlight" control 501B, terminal device 100 highlights the backlight on message card 309. For a message card that includes a plurality of push messages, the following 303 message card is used as an example to describe how a user manually sets a highlight state for a push message. For example, as shown in FIG. 8A and FIG. 8B, the 303 message card includes an unhighlighted 303D push message and an unhighlighted 303A push message from the video application, and the 303 message card can receive an input operation (for example, a left swipe operation shown in FIG. 8A) from the user. In response to the above input operation, the terminal device 100 displays a 502A push message selection control, a 502B push message selection control, a 503A "Highlight" control, and a 503B "Cancel Highlight" control. For example, as shown in FIG. 8C and FIG. 8D, after the user selects control 502A, in response to an input operation (e.g., a touch operation) performed on control 503A, "Highlight," the terminal device 100 highlights message 303D. It should be understood that once message 303D is highlighted, control 503B, "Cancel Highlight," can be used to cancel the highlighting of message 303D. As shown in FIG. 8E and FIG. 8F, after the user selects control 502B, in response to an input operation (e.g., a touch operation) for control 503A, "Highlight," the terminal device 100 highlights message 303D on a newly created message card 311. In some embodiments, the 303 message card can receive an input operation (for example, a left swipe operation shown in FIG. 8A) from the user, and in response to the input operation, the terminal device 100 can highlight all push messages on the 303 message card. For example, the backlight color of the 303 message card is changed, or all push messages on the 303 message card are displayed in bold. In some embodiments, the push message 1 on user interface 13 can receive an input operation from the user, and in response to the input operation, the terminal device 100 can change the display state of the push message 1. The display state of the push message 1 includes a read state and an unread state. In some embodiments, the push message 1 on user interface 13 can receive an input operation from the user, and in response to the input operation, the terminal device 100 can delete the push message 1. For a message card that includes only one push message, the following message card 310 is used as an example to describe how a user manually sets a display state for the push message and how to delete the push message. For example, as shown in FIG. 9A and FIG. 9B, the 310 message card contains the 302E push message, and the 310 message card can receive an input operation (for example, a right swipe operation shown in FIG. 9A) from the user. In response to the input operation, the 100 terminal device displays a 601A "Read" control, a 601B "Not Read" control, and a 601C "Delete" control. The 601A "Read" control is configured to change the display state of the 302E push message to a read state, and the 601B "Not Read" control is configured to change the display state of the 302E push message to an unread state. The 601A "Read" control shown in FIG. 9B is highlighted. This indicates that the 302E push message is currently in the read state. As shown in FIG.9C, in response to an input operation (e.g., a touch operation) for the "Delete" control 601C, the terminal device 100 deletes the push message 302E. For a message card that includes multiple push messages, the following 303 message card is used as an example to describe how a user manually sets a push message display state and how the push message is deleted. For example, as shown in FIG. 10A and FIG. 10B, the 303 message card includes the 303D push message and the 303A push message, and the 303 message card can receive an input operation (for example, a right swipe operation shown in FIG. 10A) from the user. In response to the input operation, the 100 terminal device displays a 602A video application selection control, a 602B push message selection control, a 602C push message selection control, a 603A "Read" control, a 603B "Not Read" control, and a 603C "Delete" control. As shown in FIG. 10C, when the user selects control 602A, "Read" control 603A is configured to change the display states of all push messages on message card 303 to "Read," and "Unread" control 603B is configured to change the display states of all push messages on message card 303 to "Unread." Control 603C, "Delete," is also configured to delete all push messages managed by message card 303. As shown in FIG. 10D, in response to an input operation (e.g., a touch operation) for "Delete" control 603C, the terminal device deletes message card 303. As shown in FIG. 10E, the 303A push message is used as an example. When the user selects the corresponding 602C selection control for the 303A push message, the 603A "Read" control is configured to change the display state of the 303A push message to a read state, the 603B "Not Read" control is configured to change the display state of the 303A push message to an unread state, and the 603C "Delete" control is configured to delete the 303A push message. As shown in FIG. 10F, in response to an input operation (for example, a touch operation) for the 603C "Delete" control, the terminal device deletes the 303A push message from the 303 message card. Based on the above schematic diagrams of the communications system 10, the software system architecture, and the application scenario, a message processing method provided in implementations of this application is described below. In the proposed message processing method, a push message delivered by an application server to a terminal device using a push server can carry a persistence flag, a global pinning flag, an application pinning flag, and / or a highlight flag. When the push message carries a persistence flag, the terminal device can store the push message for the duration of the push message's persistence, preventing the system from automatically deleting it.When message 1 push has a global pinning mark at the top, an in-app pinning mark at the top, and / or a highlighting mark, the terminal device 100 can apply a global pinning mark, an in-app pinning mark, and / or highlighting mark to increase the visibility of message 1 push. This makes it convenient for a user to quickly locate message 1 push. Figures 11A through 11C show a schematic flowchart of a message processing method according to one implementation of this application. The message processing method includes, but is not limited to, steps S101 through S106. Phase 1: Maintaining a whitelist S101: Application server 200 sends an application request to push server 300, where the application request is used to request an access token ID from a push message from application server 200. S102: Send access token ID. S103: Send a registration request from an application 1, wherein the registration request is used to register a related service for the persistence of a push message from application 1, the registration request carries the application server access token ID 200, an application ID 1 and information related to the persistence of the push message from application 1, wherein the above related information is used to represent that the registration of a persistence service, a global pinning service, an in-application pinning service and / or a push message highlighting service from application 1 is requested, and when the registration of the global pinning service is requested, the registration request further includes the global pinning time 1 of the push message from application 1. In some implementations, when the registration request does not request to register the persistence service, a registration request for another service (for example, the global pinning service on top, the pinning service on top within the application, and / or the highlighting service) is invalid. S104: The push server 300 registers, in the whitelist, the access token ID of the application server 200, the application ID 1, and information related to the persistence of the push message from application 1. In some implementations, the push server 300 records, in the whitelist Table 1, the application server 200 access token ID, the application 1 ID, whether application 1 registers the persistence service, whether application 1 registers the global pinning service, whether application 1 registers the pinning service within the application, and whether application 1 registers the highlighting service. If application 1 registers the global pinning service, the push server 300 also records, in the whitelist Table 2, the application server 200 access token ID, the application 1 ID, and the global pinning time of the push message from application 1.Optionally, the global pinning time at the top of the push message includes a global pinning date at the top and / or a global pinning time period at the top within one day. In some implementations, multiple global pinning periods can be set for an application ID within a single day. In some embodiments, the total global pinning duration for an application ID within a single day cannot exceed the preset duration. Table 1 of the whitelist Table 2 of the whitelist In some implementations, as shown in Table 1 and Table 2, for one application record (e.g., application 1) on the whitelist, the 300 push server can set "Whether to perform global pinning on top," "Whether to perform pinning on top within the application," "Whether to perform highlighting," and "Global pinning time on top" in the application 1 whitelist record only when "Whether to perform persistence" for application 1 is set to "Yes." When the "Whether to perform persistence" option is set to "No," any other value, or null, other settings in the application 1 record are invalid. In some implementations, after stage S104, the method further includes: the push server 300 sends a log response to the application server 200, where the log response is used to notify the application server 200 whether the log request was successfully logged. Phase 2: Preprocessing a push message S105: Application server 200 sends a push message 1 from application 1 to push server 300, where the push message 1 carries the ID, persistence flag, and persistence duration 1 that are from application 1, and also carries a global pinning flag on top, a pinning flag on top within the application, and / or a highlighting flag, and consequently the push message 1 may also carry global pinning duration 2 on top, pinning duration 3 on top within the application, and / or highlighting duration 4. The persistence duration (1) indicates the length of time a push mailbox stores push message 1, which can also be referred to as the persistence duration. The global pinning duration (2) indicates the duration for which push message 1 remains pinned to the top of the push mailbox. The application pinning duration (3) indicates the duration for which push message 1 remains pinned to the top of the application within the push mailbox. The highlighting duration (4) indicates the duration for which push message 1 remains highlighted in the push mailbox. In some embodiments, the persistence duration 1 is greater than the overall fixation duration 2 on the top, the fixation duration 3 on the top within the application, and the highlighting duration 4. In some embodiments, at stage S105, push message 1 may not contain persistence duration 1, global pinning duration 2, in-application pinning duration 3, and / or highlighting duration 4. Optionally, the persistence duration, global pinning duration, in-application pinning duration, and / or highlighting duration of all push messages from application 1 may be preset by both the terminal device 100 and the application server 200 before stage S105. Optionally, the persistence duration, global pinning duration, in-application pinning duration, and / or highlighting duration of all push messages from all applications are the same and may be preset by the push server or the terminal device 100. In some embodiments, at stage S105, the push message 1 can carry only persistence duration 1, global pinning duration 2, in-app pinning duration 3, and / or highlighting duration 4. The terminal device 100 can determine global pinning duration 2, in-app pinning duration 3, and highlighting duration 4 based on persistence duration 1. Optionally, the terminal device 100 determines that global pinning duration 2, in-app pinning duration 3, and highlighting duration 4 are all equal to persistence duration 1. S106: Server 300 push performs preprocessing of message 1 push. S107: Server 300 push sends a preprocessed push message 1 to device 100 terminal. In some implementations, for a preprocessing process of message 1 push by server 300 push, see FIG. 12A and FIG. 12B. As shown in FIG. 12A and FIG. 12B, the preprocessing process includes, but is not limited to, S106A to S106N. S106A: Server 300 push analyzes push message 1 from application 1. S106B: The push server 300 determines if the push message 1 carries a persistence flag; and performs S106C when it carries a persistence flag, S106C. It should be noted that if push message 1 does not carry a persistence flag, after push server 300 forwards push message 1 to terminal device 100, terminal device 100 processes push message 1 according to a conventional push message processing procedure and does not store push message 1 in the push message mailbox. This is not described again in this document. For example, in some implementations, the 1 push message includes the following fields: 1. MsgBox{ 2. "storage": True / / (True or False) If persistence should be performed 3. "Storage_duration:120 / / If the duration of the push message should be stored, in seconds 4. "Whole_Top": True / / (True or False) Whether the global fix should be performed on the top 5. "Whole_Top_duration:120 / / Duration of the global fix on the top, in seconds 6. "App_Top": True / / (True or False) If the pinning should be done at the top within the application 7. "App_Top_duration:120 / / Duration of the pinned top within the application, in seconds 8. "Highlight":True / / (True or False) Whether highlighting should be performed 9. "HighLight_duration:120 / / Highlight duration, in seconds 10.} In an implementation, when a "storage" field in message 1 push is "True," it indicates that message 1 push has a persistence flag; or when a "storage" field in message 1 push is "False," or message 1 push does not have a "storage" field, it indicates that message 1 push does not have a persistence flag. When the "Whole_Top" field in message 1 push is "True," it indicates that message 1 push has a global top-pinning flag; or when the "Whole_Top" field in message 1 push is "False," or message 1 push does not have a "Whole_Top" field, it indicates that message 1 push does not have a global top-pinning flag.When the "App_Top" field for push message 1 is "True," this indicates that push message 1 is pinned to the top of the application; or when the "App_Top" field for push message 1 is "False," or push message 1 does not have an "App_Top" field, it indicates that push message 1 is not pinned to the top of the application. When the "Highlight" field for push message 1 is "True," it indicates that push message 1 is highlighted; or when the "Highlight" field for push message 1 is "False," or push message 1 does not have a "Highlight" field, it indicates that push message 1 is not highlighted. In some implementations, when push message 1 does not carry a persistence flag, other flags (for example, a global pinning flag at the top, a pinning flag at the top within the application, and a highlighting flag) carried by push message 1 are all invalid. Optionally, when push message 1 does not carry a persistence flag, or push message 1 carries a persistence flag but application 1 does not register a persistence service, the push server removes other flags (for example, a global pinning flag at the top, a pinning flag at the top within the application, and a highlighting flag) carried by push message 1. S106C: The push server 300 queries a whitelist based on an application ID 1 that carries the push message 1, to determine if application 1 registers a persistence service; and performs S106D when there is no registered persistence service; or performs S106E, S106I and S106I when the persistence service is registered. S106D: Server 300 push removes the persistence flag from message 1 push. It should be noted that, after removing the persistence flag from push message 1, the push server 300 can forward push message 1 to the terminal device 100. The terminal device 100 processes push message 1 according to a conventional push message processing procedure and does not store push message 1 in the push message mailbox. This is not described again in this document. In some implementations, after removing the persistence flag from push message 1, the push server 300 sends a warning message to the application server 200, to warn it that application 1 does not register a persistence service and that push message 1 cannot be persistent. It should be noted that, in this implementation of this request, the sequence for performing S106E, S106I, and S106I is not limited. Optionally, the terminal device 100 performs S106E, S106I, and S106I simultaneously. Alternatively, the terminal device 100 performs S106E, S106I, and S106I sequentially in a predefined sequence. S106E: The push server 300 determines whether the push message 1 carries a global pinning mark on top; and performs S106F when it carries a global pinning mark on top; or performs a next step when it does not carry any global pinning mark on top. S106F: Server 300 push queries a whitelist based on an application ID 1 that carries message 1 push, to determine if application 1 registers a global pinning service on top; and performs S106G when no global pinning service is registered on top; or performs S106H when the global pinning service is registered on top. S106G: Server 300 push cancels the global fix on top of message 1 push and performs a subsequent stage. In some implementations, the 300 push server removes the global pinning mark at the top of the 1 push message. Optionally, the 300 push server modifies a field value in the "global pinning mark at the top" of the 1 push message to "False". For example, the "global pinning mark at the top" field is "Whole_Top", and the 300 push server modifies the value of "Whole_Top" to "False". S106H: Server 300 push consults the whitelist to determine if the global pinning mark at the top of message 1 push expires; and performs S106G when the global pinning mark at the top of message 1 push expires; or performs a subsequent step when the global pinning mark at the top of message 1 push does not expire. In some implementations, the 300 push server consults the whitelist and determines a global pinning time at the top of application 1. When the current time is earlier than the end of the global pinning time at the top of application 1, the 300 push server determines that the global pinning mark at the top of push message 1 does not expire. Conversely, when the current time is not earlier than the end of the global pinning time at the top of application 1, the 300 push server determines that the global pinning mark at the top of push message 1 expires. In this implementation of this application, step S106H is optional. In some implementations, the registration request in step S103 may not carry the global fix time on top of application 1, and consequently, the terminal device 100 does not need to perform S106H. It should be noted that when server 300 pushes first from S106E to S106H, and then from S106I to S106K (or from S106L to S106N), the subsequent stage being performed means that S106I (or S106L) is performed. When server 300 pushes first from S106I to S106K and from S106L to S106N, and then from S106E to S106, the subsequent stage being performed means that S107 is performed. S106I: The notification server 300 determines if the push message 1 carries a pinning mark at the top within the application; and performs S106J when it carries a global pinning mark at the top; or performs a next stage when it does not carry the global pinning mark at the top. S106J: Server 300 push queries a whitelist based on an application ID 1 that carries message 1 push, to determine if application 1 registers a pinning service on top within the application; and performs S106K when no pinning service is registered on top within the application; or performs a next stage when a global pinning service is registered on top. S106K: Server 300 push cancels the pinning at the top within the application of message 1 push and performs a next stage. In some implementations, the 300 push server removes the pinning mark at the top within the application of the 1 push message. Optionally, the 300 push server modifies a field value in the "pin to top within the application" field of the 1 push message to "False". Optionally, the "pin to top within the application" field is "App_Top", and the 300 push server modifies the value of "App_Top" to "False". It should be noted that when server 300 pushes first from S106I to S106K, and then from S106E to S106H (or from S106L to S106N), the subsequent stage means that S106E (or S106L) is performed. When server 300 pushes first from S106E to S106H and from S106L to S106N, and then from S106I to S106K, the subsequent stage means that S107 is performed. S106L: The push server 300 determines if the push message 1 carries a highlight mark; and performs S106M when it carries a highlight mark; or performs a next stage when it does not carry any highlight mark. S106M: The push server 300 queries a whitelist based on an application ID 1 that carries the push message 1, to determine if application 1 registers a highlighting service; and performs S106K when no highlighting service is registered; or performs a next stage when the highlighting service is registered. S106N: Server 300 push cancels highlighting in message 1 push and performs the next stage. In some implementations, the 300 push server removes the highlight mark from the 1 push message. Optionally, the 300 push server modifies a field value in the "highlight mark" to "False". Alternatively, a field in the "highlight mark" is "Highlight", and the 300 push server modifies the value of "Highlight" to "False". It should be noted that when server 300 pushes first from S106L to S106N and then from S106E to S106H (or S106I to S106K), the subsequent stage means that S106E (or S106I) is performed. When server 300 pushes first from S106E to S106H and from S106I to S106K, and then from S106L to S106N, the subsequent stage means that S107 is performed. In this implementation of this request, step S106 is optional. In some implementations, the push server 300 can directly forward the push message 1 sent by the application server 200 to the terminal device 100 without preprocessing the push message 1. Phase 3: Persistent display of a push message In this execution of this request, device 100 terminal receives a preprocessed push message 1 sent by the push server 300. Device 100 terminal invokes a push service process to parse the push message 1 and performs persistent display of the push message 1 in the push message mailbox based on each parameter of the push message 1. S108: The terminal device stores the push message 1 in a notification bar, determines if the push message 1 carries a persistence flag, and performs S109 when it carries a persistence flag. In some implementations, when the push message 1 does not carry a persistence flag, the terminal device 100 performs processing according to an existing processing method for a push message. This is not described again in this document. S109: Device 100 terminal stores push message 1 in the push message mailbox and sets a storage time period in which the message is stored in the push message mailbox as a persistence duration 1. S110: The 100 terminal device performs a global fixing process at the top. In some embodiments, for the overall top fixing process, see FIG. 13. As shown in FIG. 13, the overall top fixing process includes, but is not limited to, S110A to S110H. S110A: The terminal device 100 determines whether the push message 1 carries a global pinning mark on top; and performs S110B when it carries a global pinning mark on top; or performs S111 when it does not carry any global pinning mark on top. It can be understood that, when the 1 push message does not carry a global pinning mark at the top, the 100 terminal device continues to determine whether the 1 push message carries a pinning mark at the top within the application and / or a highlight mark. S110B: The terminal device 100 determines if a current moment is within the global fix time 1 at the top of the push message 1; and performs S112 and S110C when the moment is not within the global fix time 1 at the top; or performs S110D when the moment is within the global fix time 1 at the top. In some embodiments, before step S110, the method further includes: the push server 200 sends the global pinning time 1 on top of application 1 to the terminal device 100. Optionally, the push message 1 delivered by the push server 200 carries the global pinning time 1 on top of application 1. S110C: the terminal device 100 detects that the global pinning time 1 on top has begun and performs S110D. It can be determined from the preprocessing of server 300 push that the global fixation mark at the top of message 1 push received by device 100 terminal does not expire. The current time is earlier than a start time of global fixation mark 1 at the top, or the current time is later than a start time of global fixation mark 1 at the top and earlier than an end time of global fixation mark 1 at the top. In some embodiments, when push message 1 carries a global pinning mark on top, but the current time is not within the global pinning time 1 on top, terminal device 100 can perform S112, i.e., continue determining whether push message 1 carries a highlight mark. Thus, when push message 1 also carries a highlight mark, terminal device 100 can first highlight push message 1 and perform S110D after the global pinning time 1 on top begins. S110D: The terminal device 100 determines if there is already a user-set global pinning push message in the push message mailbox; and performs S110E when there is a user-set global pinning push message; or performs S110F when there is no user-set global pinning push message. In some implementations, a user-set global pinning priority for a push message is higher than the global pinning priority delivered by the push message. Optionally, in a push mailbox user interface, the user-set global pinning priority is closer to the top of the device (100 terminals) compared to the global pinning priority delivered by the push server. S110E: Device 100 displays push message 1 alongside push message 2 and sets the global pinning duration at the top of push message 1 to the global pinning duration at the top of push message 2. In some implementations, after it is determined that the user-set global pinning push message at the top already exists in the push message mailbox, the global pinning flag at the top of push message 1 is removed, and S112 is performed. S110F: The terminal device 100 determines if there is already a system-set global pinning push message in the push message mailbox; and performs S110G when there is a system-set global pinning push message; or performs S110H when there is no system-set global pinning push message. The global top-fix push message set by the system refers to a global top-fix push message set by the terminal device 100 based on a global top-fix mark that carries the push message. S110G: The device 100 terminal cancels the global fix on top of the message 3 push and then performs S110H. S110H: The terminal device 100 performs a global pinning on top of push message 1 in the push message mailbox (i.e., displays push message 1 as the 1st push message at the top of the push message mailbox) and sets the duration of the global pinning on top of push message 1 as the duration of the global pinning on top. For example, push message 1 might be the global pinning push message 309A at the top shown in FIG. 4A. After receiving push message 309A, the terminal device 100 displays push message 309A on the first message card 309 of the user interface 13 shown in FIG. 4A. S111: The 100 terminal device performs a fixing process at the top within the application. In some embodiments, for the process of fixing the top part within the application, see FIG. 14. As shown in FIG.14, the global fixing process at the top includes, but is not limited to, S111A and S111B. S111A: Device 100 terminal determines if push message 1 has a pinning mark at the top within the application; and performs S111B when it has a pinning mark at the top within the application; or performs S112 when it does not have a pinning mark at the top within the application. S111B: Device 100 terminal pins push message 1 at the top of the push messages of application 1 in the push message mailbox and sets the pinning duration at the top within the application of push message 1 to pinning duration 3 within the application. For example, push message 1 might be a pinned 303D push message at the top within the video application shown in FIG. 4B. After receiving the 303D push message, the terminal device 100 displays the 303D push message as the 1st push message on the video application's 303 message card. S112: The terminal device 100 performs a highlighting process. In some embodiments, for the highlighting process, see FIG. 15. As shown in FIG. 15, the overall fixing process at the top includes, but is not limited to, S112A and S112B. S112A: determine if push message 1 carries a highlight flag; and execute S112B when it carries a highlight flag; or execute S113 when it does not carry any highlight flag. S112B: Highlight push message 1 in the push message mailbox and set the highlight duration of push message 1 to a highlight duration of 4. For example, message 1 push may be the highlighted message 302E push from the reading application shown in FIG. 4C. After receiving message 302E push, the terminal device 100 highlights message 302E push on the 302 message card of the reading application. For example, push message 1 might be the highlighted push message 302E from the reading application shown in FIG. 4D. After receiving push message 302E, terminal device 100 highlights push message 302E on a newly created message card 310. For example, push message 1 might be push message 302E pinned to the top within the application and highlighted in the reading application, as shown in FIG. 4E. After receiving push message 302E, the terminal device 100 displays push message 302E as the first push message in the reading application's message card 302. Additionally, push message 302E is highlighted during display. S113: Display push message 302E as the first push message of application 1 without global pinning to the top, without pinning to the top within the application, and without highlighting in the push message mailbox. S114: After the global fix duration 2 at the top expires, the terminal device 100 cancels the global fix at the top of the push message 1. In some embodiments, at stage S105, when push message 1 carries a global fix marker at the top, push message 1 does not carry the global fix duration 2 at the top. Push message 1 carries the global fix time 1 at the top. After receiving the push message, terminal device 100 performs the global fix marker at the top of push message 1 within the global fix time 1 at the top. It should be noted that step S114 is optional. This means that when message 1 push does not have a global fix marker at the top, device 100 terminal does not need to perform S114. S115: After the duration of the top fix within the application expires, the device 100 terminal cancels the top fix within the application in message 1 push. In some embodiments, at stage S105, when push message 1 carries a pinning mark on top within the application, push message 1 does not carry pinning duration 3 on top within the application. Push message 1 carries pinning time 1 on top within the application. After receiving the push message, terminal device 100 performs pinning on top within the application for push message 1 within pinning time 1 on top within the application. The global pinning time shown in Table 2 is referenced, and pinning time 1 on top within the application may include a date and / or a global pinning time period within a day. It should be noted that the S115 step is optional. This means that when the push message 1 does not have a global fixing mark at the top, the terminal device 100 does not need to perform S115. S116: After the highlight duration 4 expires, the terminal device 100 cancels the highlighting of the push message 1. In some implementations, at stage S105, when push message 1 carries a highlight marker, push message 1 does not carry the highlight duration 4. Push message 1 carries the highlight time 1. After receiving the push message, terminal device 100 highlights push message 1 within the highlight time 1. The global fixation time is referenced at the top of Table 2, and the highlight time 1 may include a date and / or a highlight time period within a day. It should be noted that the S116 step is optional. This means that when push message 1 does not carry a highlight marker, the terminal device 100 does not need to perform S116. S117: After persistence duration 1 expires, terminal device 100 deletes push message 1 from the push message mailbox. In this implementation of this request, step S109 is optional. In some implementations, the push message sent by the application server may not carry a persistence flag. After receiving the push message and storing it in the notification bar, the terminal device performs operations S110 through S116. In other words, the terminal device determines a display sequence (for example, whether the push message is globally pinned to the top or pinned to the top within the application) and a display form (for example, whether the push message is highlighted) based on the global pinning flag, the pinning flag within the application, and / or the highlighting flag carried by the push message.It should be noted that, in this implementation of this application, the sequence of execution of steps S110, S111, and S112 is not specifically limited. The message processing method shown in FIG. 11C uses an example for the description where S110, S111, and S112 are performed sequentially. Alternatively, the terminal device 100 can first determine whether the push message 1 carries a pinning mark at the top within the application or a highlighting mark. Similarly, in this implementation of the application, a specific sequence for performing S114, S115, and S116 is not limited. For example, for the pinning and highlighting of the push message 1, a sequence for performing S115 and S116 can be determined based on the pinning duration (3) and the highlighting duration (4) of the push message 1.When the highlight duration 4 expires before the top fix duration 3 within the application, S116 is performed before S115; or when the highlight duration 4 and the top fix duration 3 within the application expire at the same time, S116 and S115 can be performed simultaneously. Figure 16 shows a schematic flowchart of a message processing method according to one implementation of this application. The message processing method includes, but is not limited to, steps S201 through S206. S201: A terminal device receives the first push message from a first application that is sent by a push server. S202: The terminal device receives a second push message from a second application that is sent by the push server. S203: The terminal device displays the first push message and the second push message in a first user interface. S204: The terminal device receives a first input operation performed by a user in the second push message and displays a second user interface in response to the first input operation, wherein a display form and / or a display sequence of the second push message in the second user interface is / are different from a display form and / or a display sequence of the second push message in the first user interface. In this implementation of this application, the first user interface can be user interface 12, user interface 13, or user interface 14. This is not specifically limited in this document. The terminal device is terminal device 100. In some implementations, the second push message is the first push message at the top of the second user interface. For example, as shown in FIG. 5D, FIG. 5E, and FIG. 5F, the second application can be the reading application, and the second push message can be the reading application's 302E push message. The first application can be the video application, and the first push message can be the video application's 309A push message. Alternatively, the first application can be another application, such as the gaming or bank card application shown in FIG. 5E. The first input operation can be the touch operation shown in FIG. 5E, which is performed on the "Global Fix at Top" control 402A. As shown in FIG. 5F, in response to the first input operation, the terminal device displays the 302E push message as the first push message at the top of the user interface. For example, as shown in Figures 6E through 6H, the second application can be the video application, and the second push message can be the video application's 303D push message. The first application can be another application, as shown in Figure 6C. The first input operation can be the touch operation performed on the "Global Fix at Top" control (403D), as shown in Figure 6F. As shown in Figure 6G, in response to the first input operation, the terminal device displays the 303D push message as the first push message at the top of the user interface. In some implementations, the second message is the 1st push message in the push messages of the first application in the second user interface. For example, as shown in FIG. 5D, FIG. 5E, and FIG. 5G, the second application could be the reading application, and the second push message could be the reading application's 302E push message. The first application could be the video application, and the first push message could be the video application's 309A push message. Alternatively, the first application could be another application shown in FIG. 5E. The first input operation can be the touch operation performed on control 402B of "Fix at the top within the application" shown in FIG. 5E. As shown in FIG. 5G, in response to the first input operation, the terminal device displays push message 302E as the 1st push message on message card 302 in user interface 13. For example, as shown in Figures 6I through 6K, the second application can be the video application, and the second push message can be the video application's 303A push message. The first application can be another application shown in Figure 6I. The first input operation can be the touch operation performed on the "Attach to Top within the Application" control (403F) shown in Figure 6I. As shown in Figure 6K, in response to the first input operation, the terminal device displays the 303A push message as the first push message on the video application's 303 message card. In some implementations, the second push message is a highlighted push message in the second user interface. For example, as shown in Figures 7D through 7F, the second application could be the video application, and the second push message could be the video application's 309A push message. The first application could be another application, as shown in Figure 7E. The first input operation could be the touch operation performed on the "Highlight" control 501B, as shown in Figure 7E. As shown in Figure 7F, in response to the first input operation, the terminal device highlights the 309A push message on user interface 13. For example, as shown in Figures 8A through 8D, the second application could be the video application, and the second push message could be the video application's 303D push message. The first application could be another application, as shown in Figure 8C. The first input operation could be the touch operation performed on the "Highlight" control (503A), as shown in Figure 8C. As shown in Figure 8D, in response to the first input operation, the terminal device highlights the 303D push message on user interface 13. The first push message sent by the push server carries at least one display flag. This flag is used to specify at least one storage duration, display format, and display sequence for the first push message. For the terminal device to display the first push message in a first user interface, the terminal device displays the first push message in the first user interface based on at least one display flag. The display flags in the implementations of this application include, but are not limited to, a persistence flag, a global pinning flag, an in-app pinning flag, and a highlight flag. The persistence flag is used to indicate the storage duration of a push message, the global pinning flag and the in-app pinning flag are used to indicate a display sequence for a push message, and the highlight flag is used to indicate a display format for a push message. For example, the first application can be the previous application 1, and the first push message can be the previous push message 1. In some implementations, at least one display flag includes a persistence flag, and the persistence flag is used to instruct the terminal device to store the first push message within the first duration. After the terminal device displays the first push message in the first user interface based on at least one display flag, the method further includes: the terminal device deletes the first push message based on the persistence flag at a time whose interval from a time of receiving the first push message is the first duration. In this execution of this request, the first duration can be the previous persistence duration, for example, previous persistence duration 1. In some embodiments, at least one display marker includes a global pinning marker at the top. The terminal device displaying the first push message on the first user interface based on at least one display marker includes: displaying the first push message as the first push message at the top of the first user interface based on the global pinning marker at the top. In some embodiments, displaying the first push message as the first push message at the top of the first user interface based on the global pinning marker at the top includes: displaying, based on the global pinning marker at the top, the first push message as the first push message at the top of the first user interface within a second duration after the first push message is received.The method also includes: the terminal device removes the global fixation mark at the top of the first push message at a time whose interval from a time of receipt of the first push message is the second duration. In this application, the second duration can be the duration of global fixation in the anterior upper part, for example, duration 2 of global fixation in the anterior upper part. For example, the first push message might be the 309A push message from the video application shown in FIG. 4A and FIG. 4B. The 309A push message has a global pinning mark at the top, and the terminal device displays the 309A push message as the 1st push message in user interface 13. In some embodiments, at least one display flag includes a global pinning flag at the top. The terminal device displaying the first push message in the first user interface based on at least one display flag includes: displaying the first push message as the first push message in the push messages of the first application in the first user interface based on the pinning flag at the top within the application. In some embodiments, displaying the first push message as the first push message in the first application's push messages on the first user interface, based on the pinning mark at the top within the application, includes: displaying, on the first user interface based on the pinning mark at the top within the application, the first push message as the first push message in the first application's push messages within a third of the duration after the first push message is received. The method further includes: the terminal device removes the pinning mark at the top within the application from the first push message at a time whose interval from the time of receiving the first push message is a third of the duration. In this implementation of this request, the third duration can be the pinning duration at the top within the previous application, for example, pinning duration 3 at the top within the previous application. For example, the first push message could be the 303D push message from the video application shown in FIG. 4C. The 303D push message has a pinning mark at the top within the application, and the terminal device displays the 303D push message as the 1st push message on the 303 message card of the video application in user interface 13. In some implementations, at least one display flag includes a highlight flag. For the terminal device to display the first push message in the first user interface based on at least one display flag includes: highlighting the first push message in the first user interface based on the highlight flag. In some implementations, highlighting the first push message in the first user interface based on the highlight flag includes: highlighting, based on the highlight flag, the first push message in the first user interface within one-fourth of the duration after the first push message is received. The method further includes: the terminal device removing the highlight flag from the first push message at a time whose interval from the time of receiving the first push message is one-fourth of the duration. In this execution of this request, the fourth duration can be the previous highlighting duration, for example, the previous highlighting duration 4. For example, the first push message might be the 302E push message from the reading application shown in FIG. 4D to FIG. 4F. The 302E push message has a highlight marker, and the terminal device highlights the 302E push message in user interface 13. In some implementations, the first highlighted push message includes one or more of the following display features: compared to a non-highlighted push message, the first push message has a different light background color; compared to a non-highlighted push message, the first push message has a different font, font size, and / or color; and compared to a non-highlighted push message, the first push message displays a highlighted icon. This implementation of this application does not specifically limit any particular form of highlighting display. The following describes a structure of the 100 terminal device in implementations of this application. For example, FIG. 17 shows a schematic diagram of a terminal device 100 structure. The terminal device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus interface 130 (Universal Serial Bus, USB), a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communications module 150, a wireless communications module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display 194, a subscriber identification module card interface 195 (Subscriber Identification Module, SIM), and the like.The 180 sensor module may include a 180A pressure sensor, a 180B gyroscopic sensor, a 180C barometric pressure sensor, a 180D magnetic sensor, a 180E acceleration sensor, a 180F distance sensor, a 180G optical proximity sensor, a 180H fingerprint sensor, a 180J temperature sensor, a 180K touch sensor, a 180L ambient light sensor, a 180M bone conduction sensor, and the like. It can be understood that the structure illustrated in this embodiment of the present invention does not constitute a specific limitation of the terminal device 100. In some other embodiments of this application, the terminal device 100 may include more or fewer components than those shown in the figure, or combine some components, or divide some components, or have different component arrangements. The components shown in the figure may be implemented by hardware, software, or a combination of software and hardware. The 110 processor may include one or more processing units. For example, the 110 processor may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, a neural network processing unit (NPU), and / or similar components. The different processing units may be standalone components or may be integrated into one or more processors. The controller can generate an operation control signal based on the instruction's opcode and a timing sequence signal to control instruction fetching and execution. A memory can also be provided in the processor 110, configured to store instructions and data. In some implementations, the processor 110's memory is a cache. This memory can store instructions or data that are used only by, or used cyclically by, the processor 110. If the processor 110 needs to use the instructions or data again, it can directly retrieve them from memory. This avoids repeated access, reduces processor 110 wait time, and improves system efficiency. In some embodiments, the 110 processor may include one or more interfaces. The interface may include an integrated circuit interface (I2C), an integrated circuit audio interface (I2S), a pulse code modulation interface (PCM), a universal asynchronous receiver / transmitter interface (UART), a mobile industry processor interface (MIPI), a general-purpose input / output interface (GPIO), a subscriber identity module interface (SIM), a universal serial bus interface (USB), and / or similar interfaces. The charging management module 140 is configured to receive a charging input from a charger. The charger can be either a wireless or a wired charger. In some wired charging embodiments, the charging management module 140 can receive a charging input from a wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive a wireless charging input via a wireless charging coil of the terminal device 100. When the battery 142 is being charged, the charging management module 140 can also supply power to the terminal device using the power management module 141. The power management module 141 is configured to connect to the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives an input from the battery 142 and / or the charging management module 140 and supplies power to the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communications module 160, and similar components. The power management module 141 can also be configured to monitor parameters such as battery capacity, battery cycle count, and battery health status (electrical leakage or impedance). In some other embodiments, the power management module 141 can be arranged on the processor 110. In some other embodiments, the power management module 141 and the charging management module 140 can be arranged on the same component. A wireless communication function of the terminal device 100 can be implemented using antenna 1, antenna 2, mobile communications module 150, wireless communications module 160, modem processor, baseband processor, and the like. Antenna 1 and antenna 2 are configured to transmit and receive electromagnetic wave signals. Each antenna of the terminal device can be configured to cover one or more communication frequency bands. Different antennas can be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna in a wireless local area network. In some other embodiments, an antenna can be used in combination with a tuning switch. The mobile communications module 150 can provide a wireless communications solution, including 2G / 3G / 4G / 5G or similar technologies, for use with terminal device 100. The mobile communications module 150 may include at least a filter, a switch, a power amplifier, a low-noise amplifier (LNA), and similar components. The mobile communications module 150 can receive an electromagnetic wave via antenna 1, perform processing such as filtering and amplification of the received electromagnetic wave, and transmit the processed electromagnetic wave to the modem processor for demodulation. The mobile communications module 150 can further amplify a signal modulated by the modem processor and convert the signal into an electromagnetic wave for transmission via antenna 1.In some embodiments, at least some functional modules of the mobile communications module 150 may be arranged in the processor 110. In some embodiments, at least some functional modules of the mobile communications module 150 and some modules of the processor 110 may be arranged in the same component. The modem processor may include a modulator and a demodulator. The modulator is configured to modulate a low-frequency baseband signal into a medium-to-high-frequency signal. The demodulator is configured to demodulate a received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transfers the resulting low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs a sound signal through an audio device (not limited to the 170A speaker, 170B receiver, or similar) or displays an image or video using the 194 display. In some embodiments, the modem processor may be a separate component.In some other embodiments, the modem processor may be independent of the 110 processor and is arranged in the same component as the 150 mobile communications module or another functional module. The wireless communications module 160 can provide a wireless communications solution applicable to the terminal device 100, including a wireless local area network (WLAN) (e.g., a wireless fidelity network (Wireless Fidelity, Wi-Fi)), Bluetooth (Bluetooth, BT), a global navigation satellite system (Global Navigation Satellite System, GNSS), frequency modulation (Frequency Modulation, FM), near-field communication (NFC) technology, infrared (IR) technology, and similar technologies. The wireless communications module 160 can be one or more components that integrate at least one communications processor module.The wireless communications module 160 receives an electromagnetic wave through antenna 2, performs filtering and demodulation processing on the electromagnetic wave signal, and sends a processed signal to processor 110. The wireless communications module 160 can also receive a signal to be transmitted from processor 110, perform frequency modulation and amplification on the signal, and convert the signal into an electromagnetic wave for radiation through antenna 2. In some embodiments, in the terminal device 100, antenna 1 and the mobile communications module 150 are coupled, and antenna 2 and the wireless communications module 160 are coupled, so that the terminal device 100 can communicate with a network and with another device using a wireless communications technology.Wireless communications technology may include a global system for mobile communications (Global System for Mobile Communications, GSM), a general packet radio service (General Packet Radio Service, GPRS), code division multiple access (Code Division Multiple Access, CDMA), wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA), time division code division multiple access (Time Division Code Division Multiple Access, TD-SCDMA), long term evolution (Long Term Evolution, LTE), BT, a GNSS, a WLAN, NFC, FM, an IR technology and / or similar technologies.GNSS may include a global positioning system (Global Positioning System, GPS), a global navigation satellite system (Global Navigation Satellite System, GLONASS), a BeiDou navigation satellite system (BeiDou Navigation Satellite System, BDS), a quasi-zenithal satellite system (QZSS), and / or a satellite-based augmentation system (Satellite-Based Augmentation System, SBAS). The terminal device 100 implements a display function using the GPU, the 194 display, the application processor, and similar components. The GPU is a microprocessor for image processing and is connected to the 194 display and the application processor. The GPU is configured to perform mathematical and geometric calculations and render an image. The 110 processor may include one or more GPUs that execute program instructions to generate or change display information. The 194 display is configured to display an image, video, or similar content. The 194 display includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a mini-LED, a micro-LED, a micro-OLED, a quantum dot light-emitting diode (QLED), or similar. In some embodiments, the terminal 100 device can include one or N 194 displays, where N is a positive integer greater than 1. The terminal device 100 can implement a photography function using the ISP, camera 193, video codec, GPU, display 194, application processor and the like. The ISP is configured to process the data sent to it by the camera. For example, during photography, a shutter is pressed, transmitting a beam of light to a photosensitive element of a camera through a lens. An optical signal is converted into an electrical signal. The camera's photosensitive element transmits this electrical signal to the ISP for processing, which converts it into a visible image. The ISP can also perform algorithm optimization on image noise, brightness, and complexity. Furthermore, the ISP can optimize parameters such as exposure and color temperature for a photographic scene. In some embodiments, the ISP may be integrated into the camera. The 193 camera is configured to capture a still image or video. An optical image of an object is generated using the lens and projected onto a photosensitive element. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) photoelectric transistor. The photosensitive element converts the optical signal into an electrical signal and then transmits the electrical signal to the ISP for conversion into a digital image signal. The ISP sends the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard format such as RGB or YUV. In some embodiments, the terminal device 100 may include one or N 193 cameras, where N is a positive integer greater than 1. The digital signal processor is configured to process a digital signal, and it can process other digital signals in addition to the digital image signal. For example, when the terminal device selects a frequency, the digital signal processor is configured to perform Fourier transforms into frequency energy and similar operations. The video codec is configured to compress or decompress digital video. The 100 terminal device can support one or more video codecs. In this way, the 100 terminal device can play or record videos in multiple encoding formats, such as Moving Picture Experts Group (MPEG)-1, MPEG-2, MPEG-3, and MPEG-4. The NPU is a computer neural network processor (neural network, NN). The NPU rapidly processes input information with reference to the structure of a biological neural network, for example, the transmission mode between neurons in the human brain, and can also continuously perform a self-learning process. Applications such as intelligent device recognition, including image recognition, facial recognition, speech recognition, and text understanding, can be implemented using the NPU. Internal memory 121 may include one or more random access memories (Random Access Memory, RAM) and one or more non-volatile memories (Non-Volatile Memory, NVM). Random access memory can include static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM; for example, fifth-generation DDR SDRAM is commonly known as DDR5 SDRAM), and similar types. Non-volatile memory can include magnetic disk storage devices and flash memory. Based on its operating principle, flash memory can include NOR flash, NAND flash, 3D NAND flash, and similar types. Based on the possible arrangement of a storage unit, flash memory can include single-level cells (SLC), multi-level cells (MLC), triple-level cells (TLC), quad-level cells (QLC), and similar types. Based on storage specifications, flash memory can include universal flash storage (UFS), embedded multimedia cards (eMMC), and similar types. Random access memory can be read and written directly by the processor 110, and can be configured to store an executable program (for example, a machine instruction) of an operating system or other running program, and can be further configured to store user and application data, and the like. Non-volatile memory can also store an executable program, user and application data, and similar items. Non-volatile memory can be pre-loaded into random access memory so that the processor can directly read and write to it. The external memory interface 120 can be configured to connect to non-volatile external memory to expand the storage capacity of the terminal device 100. The non-volatile external memory communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music and videos are stored in the non-volatile external memory. The terminal device 100 can implement an audio function using the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone port 170D, the application processor, and similar components. For example, a music playback function and a recording function are implemented. The audio module 170 is configured to convert digital audio information into an analog audio signal output, and is also configured to convert an analog audio input into a digital audio signal. The audio module 170 can further be configured to encode and decode an audio signal. In some embodiments, the audio module 170 may be located within the processor 110, or some functional modules within the audio module 170 may be located within the processor 110. The 170A loudspeaker, also called a "loudspeaker", is configured to convert an electrical audio signal into a sound signal. The 170B receiver, also called a "headset", is configured to convert an electrical audio signal into a sound signal. The 170C microphone, also called a "micro" or "microphone", is configured to convert a sound signal into an electrical signal. The 170D headphone jack is configured to connect to a wired headset. The 180A pressure sensor is configured to detect a pressure signal and can convert the pressure signal into an electrical signal. The gyroscopic 180B sensor can be configured to determine a movement posture of the terminal 100 device. The 180C barometric pressure sensor is configured to measure barometric pressure. The 180D magnetic sensor includes a Hall sensor. The 180E acceleration sensor can detect acceleration magnitudes in various directions (typically on three axes) of the terminal device 100. It can detect the magnitude and direction of gravity when the terminal device 100 is stationary. The 180F distance sensor is configured to measure distance. The 100 terminal device can measure distance using infrared or a laser. The 180G optical proximity sensor may include a light-emitting diode (LED) and an optical detector, for example, a photodiode. The 180L ambient light sensor is configured to detect the brightness of the ambient light. The 180H fingerprint sensor is configured to collect a fingerprint. The 180J temperature sensor is configured to detect a temperature. The 180K touch sensor is also referred to as the "touch component." The 180K touch sensor may be arranged on the 194 display. The 180K touch sensor and the 194 display together constitute a touch display, which is also referred to as the "touch control display." The 180K touch sensor is configured to detect a touch operation performed on or near the touch sensor. The touch sensor can then transfer the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided using the 194 display. In some other embodiments, the 180K touch sensor may alternatively be arranged on a surface of the terminal device 100 in a position different from that of the 194 display. The 180M bone conduction sensor can obtain a vibration signal. Button 190 can be a mechanical button or a touch button. Terminal device 100 can receive the button input and generate a button signal input related to a user configuration and function control of terminal device 100. The 191 engine may generate a vibration warning. The following describes a 200 application server structure based on an implementation of this request. FIG.18 shows an example of the structure of a 200 application server according to an implementation of this application. As shown in FIG. 18, the application server 200 may include: one or more network device processors 701, a memory 702, a communications interface 703, a receiver 705, a transmitter 706, a coupler 707, an antenna 708, and a network device interface 709. These components may be connected using a bus 704 or in another manner. FIG. 18 uses an example where these components are connected using a bus. The 703 communications interface can be used by the application server 200 to communicate with another communications device, such as a terminal device. Specifically, the terminal device can be the terminal device 100 shown in Figure 17. The 703 communications interface could be a 5G communications interface or a future new radio communications interface. In addition to a wireless communications interface, the application server 200 can also be configured with a wired communications interface 703, such as a local access network (LAN) interface. The transmitter 706 can be configured to process the transmission of an output signal from the network device processor 701. The receiver 705 can be configured to process the reception of a mobile communications signal received by antenna 708. In some embodiments of this application, the 706 transmitter and 705 receiver can be considered as a wireless modem. On the application server 200, there can be one or more 706 transmitters and one or more 705 receivers. The 708 antenna can be configured to convert the electromagnetic energy of a transmission line into an electromagnetic wave in free space, or to convert an electromagnetic wave in free space into electromagnetic energy on a transmission line. The 707 coupler is configured to split the mobile communication signals received by the 708 antenna into a plurality of signal channels and assign that plurality of signal channels to a plurality of 705 receivers. Memory 702 is coupled to the network device processor 701 and is configured to store various software programs and / or multiple instruction sets. Specifically, memory 702 may include high-speed random-access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, a flash memory device, or another non-volatile solid-state storage device. Memory 702 may store a network communications program. The network communications program may be used to communicate with one or more additional devices, one or more terminal devices, or one or more network devices. In some implementations of this application, memory 702 can be configured to store a deployment program, on the application server side of 200, for an uplink synchronization method provided in one or more implementations of this application. For the implementation of the uplink synchronization method provided in one or more implementations of this application, see the preceding implementations. The network device processor 701 can be configured to read and execute computer-readable instructions. Specifically, the network device processor 701 can be configured to: invoke a program stored in memory 702, for example, the implementation program, on the application server side 200, of the uplink synchronization method provided in one or more embodiments of this application; and execute the instructions contained in the program. It should be noted that the Application Server 200 shown in Figure 18 is simply one implementation of this application. In the actual application, the Application Server 200 may include more or fewer components. This is not limited to the scope of this document. In this implementation of this application, for a push server 300 structure, refer to the application server 200 structure shown in FIG. 18. The details are not described again in this document. Implementations of this application can be combined randomly to achieve different technical effects. All or some of the above realizations can be implemented using software, hardware, firmware, or any combination thereof. When software is used to implement the realizations, all or some of them can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, all or some of the functions are processed according to this instruction. The computer can be a general-purpose computer, a dedicated computer, a network of computers, or another programmable device. The computer instructions can be stored on a computer-readable storage medium or can be transmitted from one computer-readable storage medium to another.For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via cable (e.g., coaxial cable, fiber optic cable, or digital subscriber line) or wirelessly (e.g., infrared, radio, or microwave). Computer-readable storage media can be any usable medium accessible by a computer or data storage device, such as a server or data center, that integrates one or more usable media. The usable media can be magnetic (e.g., a floppy disk, hard disk, or magnetic tape), optical (e.g., a DVD), semiconductor (e.g., a solid-state drive (SSD)), or similar. A person skilled in the art may understand that all or some of the processes of the methods described in the preceding embodiments can be implemented using a computer program to instruct the corresponding hardware. The program may be stored on a computer-readable storage medium. When the program is executed, the processes of the embodiments of the preceding methods can be performed. The storage medium described above includes any medium that can store program code, such as ROM, RAM, a magnetic disk, or an optical disk.

Claims

1. A message processing method, comprising: receiving (S201), by a terminal device (100), a first push message from a first application that is sent by a push server (300), wherein the first push message sent by the push server (300) carries at least one display flag, and the display flag is used to indicate at least one storage duration, display format, and display sequence that are of the first push message; receiving (S202), by the terminal device (100), a second push message from a second application that is sent by the push server (300); displaying (S203), by the terminal device (100), the first push message on a first user interface based on at least one display flag; displaying (S203), by the terminal device (100), the second push message on the first user interface; receiving (S204), by the terminal device (100),1. A first input operation performed by a user on the second push message; and displaying (S204), by the terminal device (100), a second user interface in response to the first input operation, wherein a display form and / or a display sequence of the second push message on the second user interface is / are different from a display form and / or a display sequence of the second push message on the first user interface.

2. The method of claim 1, wherein the second push message is a highlighted push message on the second user interface.

3. The method of claim 1 or 2, wherein the second push message is the first push message at the top of the second user interface.

4. The method of claim 1 or 2,wherein the second push message is the first push message in the push messages of the first application in the second user interface.

5. The method according to any one of claims 1 to 4, wherein at least one display marker comprises a persistence marker, and the persistence marker is used to instruct the terminal device (100) to store the first push message within the first duration; and after the display, by the terminal device (100), of the first push message in the first user interface based on at least one display marker, the method further comprises: deleting, by the terminal device (100), the first push message based on the persistence marker at a time interval from a time of receipt of the first push message is the first duration.

6. The method according to any one of claims 1 to 4,wherein at least one display mark comprises a global fixing mark at the top; and the display, by the terminal device (100), of the first push message on the first user interface based on at least one display mark comprises: displaying the first push message as the 1st push message on a top portion of the first user interface based on the global fixing mark at the top.

7. The method according to claim 6, wherein the display of the first push message as the 1st push message on the top of the first user interface based on the global fixing mark at the top comprises: displaying, based on the global fixing mark at the top, the first push message as the 1st push message on the top of the first user interface within a second duration after the first push message is received; and the method further comprises: removing,by the terminal device (100), the global fixation mark at the top of the first push message at a time whose interval with respect to the time of receipt of the first push message is the second duration.

8. The method according to any one of claims 1 to 4, wherein at least one display mark comprises a fixation mark at the top within the application; and the display, by the terminal device (100), of the first push message in the first user interface based on at least one display mark comprises: displaying the first push message as the 1st push message in the push messages of the first application in the user interface based on the fixation mark at the top within the application.

9. The method according to claim 8,wherein the display of the first push message as the 1st push message in the push messages of the first application in the first user interface based on the pinning mark at the top within the application comprises: displaying, based on the pinning mark at the top within the application, the first push message as the 1st push message in the push messages of the first application within the third duration after the first push message is received; and the method further comprises: removing, by the terminal device (100), the pinning mark at the top within the application of the first push message at a time interval from the time of receipt of the first push message being the third duration.

10. The method according to any one of claims 1 to 4, wherein at least one display mark comprises a highlight mark; and the display, by the terminal device (100),of the first push message in the first user interface based on at least one display marker comprises: highlighting, based on the highlight marker, the first push message in the first user interface.

11. The method according to claim 10, wherein the highlighting, based on the highlight marker, of the first push message in the first user interface comprises: highlighting, based on the highlight marker, the first push message in the first user interface within the fourth duration after the first push message is received; and the method further comprises: removing, by the terminal device (100), the highlight marker from the first push message at a time interval from the time of receipt of the first push message is the fourth duration.

12. The method according to claim 10,wherein the first highlighted push message comprises one or more of the following display features: compared to a non-highlighted push message, the first push message has a different light background color; compared to the non-highlighted push message, the first push message has a different font, a different font size, and / or a different color; and compared to the non-highlighted push message, the first push message carries a highlighted icon.

13. A terminal device (100), comprising a touchscreen, a memory (702), one or more processors (701), a plurality of applications, and one or more programs, wherein the one or more programs are stored in the memory (702), and when the one or more processors (701) execute the one or more programs, the terminal device (100) is enabled to implement the method according to any one of claims 1 to 12.

14. A storage medium,comprising computer instructions, wherein when the instructions are executed on a terminal device (100), the terminal device (100) can perform the method according to any one of claims 1 to 12.