Display control method, device and computer equipment for notification toolbar

Abstract

This application relates to a method and computer device for controlling the display of a notification toolbar. The method includes: obtaining a display update request for the notification toolbar, the display update request carrying terminal usage parameters; the notification toolbar has at least two columns, and the column parameters of the at least two columns are not completely identical; based on message configuration parameters corresponding to a preset message pool, determining the message type to be displayed for each column according to the usage parameters; wherein the message pool includes one or more message types; obtaining the message display content corresponding to the message type to be displayed for each column based on the usage parameters; encapsulating the message display content corresponding to the message type to be displayed for each column with the display style information of the notification toolbar into information to be displayed; and pushing the information to be displayed to the terminal to display the information in the terminal's notification toolbar. This method can enrich the content that can be displayed in the notification toolbar.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to a method, apparatus and computer device for controlling the display of a notification toolbar. Background Technology

[0002] The notification toolbar, as an effective entry point to reach users, can be used for system or application notifications on a terminal operating system. Taking terminal operating system notifications as an example, the notification toolbar can alert users to system updates and system risks; when a user triggers the relevant notification, they can perform a system update or risk mitigation action. Taking app store applications as another example, the notification toolbar can provide application update notifications, junk file cleanup notifications, etc.

[0003] Traditional notification toolbars display fixed messages in each section, limiting the number of messages that can be shown. Summary of the Invention

[0004] Therefore, it is necessary to provide a method, device, computer equipment, and storage medium for controlling the display of a notification toolbar that enriches the content displayed in the notification toolbar, in order to address the aforementioned technical problems.

[0005] A method for controlling the display of a notification toolbar, the method comprising:

[0006] Obtain a display update request for the notification toolbar, the display update request carrying the terminal's usage parameters; the notification toolbar has at least two fields, and the field parameters of the at least two fields are not completely identical;

[0007] Based on the message configuration parameters corresponding to the preset message pool, the message type to be displayed in each column is determined according to the usage parameters; wherein, the message pool includes one or more message types;

[0008] Based on the usage parameters, obtain the message display content corresponding to the message type to be displayed in each column;

[0009] The message display content corresponding to the message type to be displayed in each column and the display style information of the notification toolbar are encapsulated into information to be displayed;

[0010] The information to be displayed is pushed to the terminal so that it is displayed in the terminal's notification toolbar.

[0011] A display control device for a notification toolbar, comprising:

[0012] The request acquisition module is used to acquire the display update request of the notification toolbar, the display update request carrying the terminal's usage parameters; the notification toolbar has at least two fields, and the field parameters of the at least two fields are not completely the same;

[0013] The message determination module is used to determine the message type to be displayed for each field based on the message configuration parameters corresponding to the preset message pool and according to the usage parameters; wherein, the message pool includes one or more message types;

[0014] The content acquisition module is used to acquire the message display content corresponding to the message type to be displayed in each column based on the usage parameters.

[0015] The encapsulation module is used to encapsulate the message display content corresponding to the message type to be displayed in each column and the display style information of the notification toolbar into information to be displayed;

[0016] The sending module is used to push the information to be displayed to the terminal so that the information to be displayed is displayed in the notification toolbar of the terminal.

[0017] A computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program performing the following steps:

[0018] Obtain a display update request for the notification toolbar, the display update request carrying the terminal's usage parameters; the notification toolbar has at least two fields, and the field parameters of the at least two fields are not completely identical;

[0019] Based on the message configuration parameters corresponding to the preset message pool, the message type to be displayed in each column is determined according to the usage parameters; wherein, the message pool includes one or more message types;

[0020] Based on the usage parameters, obtain the message display content corresponding to the message type to be displayed in each column;

[0021] The message display content corresponding to the message type to be displayed in each column and the display style information of the notification toolbar are encapsulated into information to be displayed;

[0022] The information to be displayed is pushed to the terminal so that it is displayed in the terminal's notification toolbar.

[0023] A computer-readable storage medium having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0024] Obtain a display update request for the notification toolbar, the display update request carrying the terminal's usage parameters; the notification toolbar has at least two fields, and the field parameters of the at least two fields are not completely identical;

[0025] Based on the message configuration parameters corresponding to the preset message pool, the message type to be displayed in each column is determined according to the usage parameters; wherein, the message pool includes one or more message types;

[0026] Based on the usage parameters, obtain the message display content corresponding to the message type to be displayed in each column;

[0027] The message display content corresponding to the message type to be displayed in each column and the display style information of the notification toolbar are encapsulated into information to be displayed;

[0028] The information to be displayed is pushed to the terminal so that it is displayed in the terminal's notification toolbar.

[0029] The aforementioned notification toolbar display control method, device, computer equipment, and storage medium, when receiving a notification toolbar display update request, determine the message type to be displayed for each column based on the message configuration parameters of the message pool and the usage parameters of each column. In other words, the message type to be displayed for each column is obtained from the message pool by matching the usage parameters and message configuration parameters. This enables the delivery of toolbar messages that conform to the actual usage state of the terminal, achieving personalized message display control. At the same time, the messages to be displayed for each column are not fixed, but are matched from the message pool, which includes multiple message types. This allows for adaptive configuration of the notification toolbar display content based on the usage parameters and also enriches the display content available in the notification toolbar. Attached Figure Description

[0030] Figure 1 This is an application environment diagram of a notification toolbar display control method in one embodiment;

[0031] Figure 2 This is a flowchart illustrating a method for controlling the display of a notification toolbar in one embodiment;

[0032] Figures 3 to 6 These are schematic diagrams illustrating the display style of a notification toolbar according to one embodiment;

[0033] Figure 7 This is a flowchart illustrating the steps of determining the message type to be displayed in a field, as shown in one embodiment.

[0034] Figure 8 This is an interactive schematic diagram of a notification toolbar display control method according to one embodiment;

[0035] Figure 9 A schematic diagram illustrating the server-side processing flow of one embodiment;

[0036] Figure 10A flowchart illustrating the server-side data source recall process in one embodiment;

[0037] Figure 11 This is a schematic diagram of the card setter processing in one embodiment;

[0038] Figure 12 This is a schematic diagram of the filter processing flow of one embodiment;

[0039] Figure 13 This is a structural block diagram of the display control device for the notification toolbar in one embodiment;

[0040] Figure 14 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0041] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0042] The notification toolbar display control method provided in this application can be applied to, for example... Figure 1 In the application environment shown, terminal 102 communicates with server 104 via a network. Terminal 102 sends a display update request to the server, and server 104 receives the display update request for the notification toolbar. The display update request carries the terminal's usage parameters. The notification toolbar has at least two columns, and the column parameters of the at least two columns are not completely identical. Based on the message configuration parameters corresponding to a preset message pool, the message type to be displayed for each column is determined according to the usage parameters. The message pool includes one or more message types. Based on the usage parameters, the message display content corresponding to the message type to be displayed for each column is obtained. The message display content corresponding to the message type to be displayed for each column is encapsulated with the display style information of the notification toolbar into information to be displayed. The information to be displayed is pushed to the terminal to be displayed in the terminal's notification toolbar. Terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, and portable wearable devices. Server 104 can be implemented using a standalone server or a server cluster consisting of multiple servers.

[0043] In one embodiment, such as Figure 2 As shown, a method for controlling the display of a notification toolbar is provided, which can be applied to... Figure 1 Taking the server in the example, the following steps are included:

[0044] Step 202: Obtain the display update request of the notification toolbar, the display update request carrying the terminal's usage parameters; the notification toolbar has at least two fields, and the field parameters of the at least two fields are not completely the same.

[0045] The notification toolbar is used to display notifications and has at least two fields. A field is a container used to display messages. A notification toolbar can be divided into multiple fields, each displaying different types of notification messages. The more fields there are, the more types of messages the notification toolbar can display, resulting in richer information. The notification toolbar can present different display formats depending on the number of fields, their distribution, and the content displayed. For example... Figures 3 to 6 The notification toolbars shown are all from app store applications, such as... Figures 3 to 6 The notification toolbar shown has six sections that can be used to display different notification messages.

[0046] In this notification toolbar, at least two sections have different section parameters. These parameters specifically define the display style of the section, such as section height, width, background color, and display area. Different section parameters result in different display styles for the corresponding sections. For example, the background colors, widths, and display areas of the two sections may differ.

[0047] When the update conditions for the notification toolbar are met, the terminal requests an update to the server, sending a display update request. The update conditions for the notification toolbar can be set as needed and may include time conditions, status conditions, etc. For example, reaching a certain time condition triggers a request to the server to update the display of the notification toolbar. Similarly, reaching a certain status parameter condition triggers a request to the server to update the display of the notification toolbar.

[0048] Usage parameters refer to parameters generated by the user during terminal use, including operational parameters and user-specific parameters. Operational parameters include remaining memory and application cache. User parameters include the user's geographical location, gender, and installed applications.

[0049] Step S204: Based on the message configuration parameters corresponding to the preset message pool, determine the message type to be displayed for each column according to the usage parameters; wherein, the message pool includes one or more message types.

[0050] In this process, the server responds to the display update request and, based on the message configuration parameters corresponding to the preset message pool, determines the message type to be displayed for each field according to the usage parameters.

[0051] A message pool is pre-maintained, configured with multiple message types, and frequently updated. In other words, the message pool pre-configures various message types that can be displayed in the notification toolbar, along with corresponding message configuration parameters for each type. The specific message types can be set according to requirements and application scenarios. In one implementation, the number of message types in the message pool exceeds the number of fields in the notification toolbar. When a display update request is received from the terminal, notification messages for each field are matched from the message pool, enabling personalized display for each field.

[0052] Message configuration parameters can include conditional parameters corresponding to each message type. These conditional parameters can be used to filter messages for each field, determining the message type displayed in each field. Conditional parameters refer to the requirements for displaying the message in the toolbar, including message display priority, the effective field for the message, and at least one of the following: targeted push conditions and display trigger conditions.

[0053] In one embodiment, a set of message configuration parameters is configured for messages in the message pool, including condition parameters for messages of each message type.

[0054] In one embodiment, multiple sets of message configuration parameters are pre-configured for messages in the message pool. The message types in each set of configuration parameters are not entirely the same, or the condition parameters corresponding to each message type are not entirely the same. When a display update request is received, it is assigned to one of the sets of configuration parameters, and the message to be displayed in each field is determined based on the corresponding configuration parameters. In other words, different display update requests from different terminals are assigned to different message configuration parameters. Because the condition parameters of the messages in each set of configuration parameters are different, the notification toolbar displayed on the terminal also differs.

[0055] Specifically, based on message configuration parameters, the message type to be displayed in each field is determined according to the usage parameters. In other words, messages in the message pool are filtered based on the message configuration parameters and usage parameters to determine the message type for each field in the notification toolbar; that is, message types that match the message configuration parameters and usage parameters are selected for each field.

[0056] Understandably, when a notification toolbar has multiple sections, the notification content for each section is determined sequentially according to a preset order. This preset order can be the numerical order of the sections. For example, if a notification toolbar has six sections, the notification content for sections 1-6 will be determined sequentially based on their numerical order.

[0057] Step S206: Based on the usage parameters, obtain the message display content corresponding to the message type to be displayed in each column.

[0058] Specifically, after determining the message type to be displayed in each field, the message display content corresponding to that message type can be determined based on usage parameters. That is, in addition to displaying the display parameters related to the message type in the field, the usage parameters of the terminal related to that message type are also displayed, thus providing the user with information about the terminal's usage status. For example, if the message type is junk file cleaning, the message display content for that field will include the amount of junk files on the terminal, based on the junk file size on the terminal included in the usage parameters.

[0059] Understandably, the message display content corresponding to the message to be displayed can also be determined in conjunction with message configuration parameters. For example, message configuration parameters also include display parameters corresponding to each message type. Display parameters refer to the display elements of each type of message in the notification toolbar, including the main message title, message subtitle, and the jump link after clicking the message. Among them, the main message title can include at least one of text content and icon content. The message subtitle can be an explanation of the main title of the message type, an operation instruction for the message type, or a description of the effect of the main title of the message type. The jump link after clicking the message refers to the link to the page to which the user should jump after the message is triggered in the notification display bar.

[0060] After determining the message types to be displayed in each field, the message display content for each message type is obtained based on the display parameters corresponding to that message type. In other words, the message display content is determined according to the display parameters of the message type.

[0061] Step 208: Encapsulate the message display content corresponding to the message type to be displayed in each column and the display style information of the notification toolbar into information to be displayed.

[0062] The display style of the notification toolbar refers to its presentation format. In one implementation, the display style of the notification toolbar is set by the operators. In other words, the notification toolbar has a fixed display style, and the display style information of the notification toolbar is fixed.

[0063] In one implementation, the notification toolbar has several preset display styles. During operation, multiple test groups can be set up based on the display styles, with each test group corresponding to one display style. Each display style has different display style information, including parameters such as the number of fields, the coordinate position of each field, and the size of each field. When a user's display update request is received, the request is assigned, and a display style is determined. Based on a period of operation, the best-performing set of display styles is identified. Subsequent updates can be based on the best-performing display styles and message content to improve the notification display effect, such as increasing user click-through rates.

[0064] Specifically, encapsulation involves filling the message display content and notification toolbar display style information into a specified data structure according to a format agreed upon with the terminal, thus obtaining the information to be displayed. Specifically, if the notification display bar is ultimately displayed on the terminal in card form, then the message display content and notification toolbar display style information can be filled into the specified data structure of the card content according to a format agreed upon with the terminal, resulting in the information to be displayed, which is a card-style notification toolbar.

[0065] Step S210: Push the information to be displayed to the terminal so that the information to be displayed is displayed in the notification toolbar of the terminal.

[0066] Specifically, the notification display content and notification toolbar display style information are filled into a specified data structure according to the format agreed upon with the terminal. The data structure is then returned to the terminal, which parses the data to obtain the notification display content and notification toolbar display style information and displays it on the notification toolbar.

[0067] Traditional notification toolbars typically send all pre-defined, fixed-type messages to the terminal from the server at once. Each message contains both content and information such as thresholds and filtering conditions, and the terminal matches the messages with changes in its operating status. This approach results in only a small number of messages being displayed in the notification bar, meaning the sent messages are not effectively utilized and a significant amount of bandwidth is wasted. Furthermore, the message types are fixed, limiting the types of messages displayed. The solution proposed in this application, on the one hand, combines message configuration parameters and usage parameters to filter messages from a message pool to obtain the notification display content for each section. This allows for the delivery of toolbar messages that match the terminal's actual state, achieving personalized message display control and reducing interference caused by messages that are not relevant to the user's current state. On the other hand, it only sends the notification display content for the matched sections, saving user bandwidth.

[0068] The above-described notification toolbar display control method, when receiving a notification toolbar display update request, determines the message type to be displayed for each field based on the message configuration parameters of the message pool and the usage parameters. In other words, the message type to be displayed for each field is obtained from the message pool by matching the usage parameters and message configuration parameters. This allows the toolbar messages that match the actual usage state of the terminal to be sent, realizing personalized message display control. At the same time, the messages to be displayed for each field are not fixed, but are matched from the message pool, which includes multiple message types. It can adaptively configure the display content of the notification toolbar according to the usage parameters and also enrich the display content of the notification toolbar.

[0069] In one embodiment, the update conditions include at least one of the following: the daemon process of the terminal application starts; the notification message in any field of the notification toolbar is processed; the terminal's usage parameters related to the message type change; and the time condition for a preset timed update request is reached.

[0070] Under certain conditions, the terminal application's daemon process starts. A daemon process runs from system startup to system shutdown, operating independently of the terminal and not interacting with the client. While regular processes stop when the terminal is closed, daemon processes do not. In other words, when a terminal-related application starts, it sends a display update request to the server. For example, in the application scenario of an app store application, when the app store application starts, it sends a display update request to the server.

[0071] Based on the condition that a notification message in any field of the notification toolbar has been processed, specifically, that a display update request is triggered to the server after the expected processing of the message has been completed. For example, if a message in the notification toolbar of an app store application is about junk file cleanup, when the user clicks on the junk file cleanup message, the user will be directed to the junk management page. When the user performs the junk file cleanup action, a new display update request is triggered.

[0072] The system works by periodically scanning terminal usage data when changes occur in terminal-related message types. Specifically, it scans business data relevant to the application scenario and sends a display update request to the server when changes happen. Taking an application marketplace application as an example, usage parameters include garbage data, RAM usage, number of updated applications, and the list of installed applications. In other words, the terminal periodically scans for garbage data, RAM usage, number of updated applications, and the list of installed applications; when these usage parameters change, a display update request is triggered.

[0073] The condition for triggering a pre-set timed update request is to be met, specifically, the terminal periodically sends a display update request to the server. In one implementation, the display update request is triggered at a 2-hour interval.

[0074] The display update request sent by the terminal includes the terminal's usage parameters.

[0075] In another embodiment, the message configuration parameters include multiple message types and corresponding message activation fields and message display priorities for each message type.

[0076] Based on the message configuration parameters corresponding to one or more preset message types, the message type to be displayed in each field is determined according to the usage parameters, such as... Figure 7 As shown, it includes:

[0077] S702, according to the specified column order of the at least two columns, for each column in the at least two columns, determine the first candidate message type from the message pool in descending order of message display priority of message type.

[0078] Specifically, based on the field number, the message type to be displayed for each of at least two fields is determined sequentially. That is, the message type to be displayed is determined for each field based on its field number. Specifically, the first field is taken as the current field. After obtaining the message type to be displayed for that field, the next field is then taken as the current field, and this process is repeated until the message type to be displayed for each field is obtained.

[0079] Message display priority refers to the order in which messages are displayed. Generally, messages are prioritized based on their importance. It's understandable that when there are multiple sets of message configuration parameters, the priority settings for each message type can differ within each set. Taking an app store application as an example, message types might include junk file cleanup messages, app update messages, promotional messages, app 1 cleanup messages, app 2 cleanup messages, phone acceleration messages, good status notification messages, large file cleanup messages, and one-click phone status check messages. Among these, junk file cleanup messages, app update messages, and app cleanup messages are the most relevant to the business logic, so junk file cleanup messages are given the highest priority, followed by app update messages and app cleanup messages.

[0080] Specifically, for each field, the first candidate message type is determined from the message pool in descending order of message display priority. That is, the first candidate message type is the message type with the highest current display priority in the message pool.

[0081] Based on the message display priority from high to low according to message type, the first candidate message type is determined from the message pool. This allows for the priority display of message types with higher priority, while also ensuring that message matching has a single order, thus improving the efficiency of filtering messages for each field.

[0082] S704, determine whether the message configuration parameters of the first candidate message type meet the display conditions in the field, wherein the display conditions in the field include the message activation field of the first candidate message type matching the field. If yes, proceed to step S706; otherwise, proceed to step S708.

[0083] S706, the first candidate message type is selected as the message type to be displayed in the field.

[0084] Specifically, the display conditions for a field refer to the display conditions for the currently matched field. As mentioned earlier, the message type to be displayed for each field is determined according to the specified field order. After the current field is matched, the message type to be displayed for the next field is matched. That is, the display conditions for each field can be set individually, meaning that the display conditions set for each field can be different.

[0085] Specifically, the display conditions for the column include: the effective column for the first candidate message type matches the column.

[0086] Specifically, the message's effective fields refer to the designated fields in which the message can be displayed; that is, the message is only allowed to be displayed in the specified fields. A single message can have multiple effective fields. For example, for the "junk cleanup" message, if effective fields are set to 2, 4, and 5, then according to the aforementioned settings, the message can only be displayed in the 2nd, 4th, or 5th field.

[0087] Specifically, based on the characteristics of the fields and the message bar type, the effective fields for each message type can be set. For example, since field number 2 in the notification toolbar has a large display area, important message types can be set to be effective in field number 2, thus setting the effective fields for important message types to include field number 2.

[0088] To improve processing efficiency, the effective message type for each field can be determined based on the message effective field in the message configuration parameters of each message type, thereby obtaining a list of candidate message types for the current field, and then determining whether the first candidate message type is in the list of candidate message types for the current field.

[0089] For example, if there are 7 messages in the message pool, each with an effective field, and the notification toolbar has 3 fields, then for each field, the candidate message types for that field are determined based on all messages that are effective in that field. For instance, if 5 messages have effective fields that include the first field, then for the first field, there are 5 corresponding candidate messages. To determine if the effective field of the first candidate message type matches the field, it can be determined whether the first candidate message type is among these 5 candidate message types. If it is, then the effective field of the first candidate message type matches the field.

[0090] S708, according to the message display priority of message type from high to low, the next message type of the first candidate message type is taken as the new first candidate message type.

[0091] Specifically, if the judgment result in step S704 is negative, that is, if the message configuration of the first candidate message type does not meet the display conditions in the column, then the next message type of the first candidate message type will be taken as the new first candidate message type in order of message display priority from lowest to highest.

[0092] In step S708, the process returns to step S702 to continue determining whether the next first candidate message type meets the display conditions in the column, until all first candidate message types have been determined, or the message type to be displayed in the column is determined.

[0093] In this embodiment, by determining whether a message meets the display conditions of a column according to the message display priority from high to low, the type of message to be displayed in that column is determined, thereby achieving a fast matching and search of the type of message to be displayed in that column.

[0094] It is understandable that for each field in the notification toolbar, the matching process from step S702 to step S708 is implemented. In this process, after filtering the current field to obtain the message type to be displayed based on the field number, the next field is determined to be the message type to be displayed based on the field number.

[0095] In another embodiment, the message display content corresponding to the message type to be displayed in each field and the display style information of the notification toolbar are encapsulated into display information. In practical applications, a card assembler and a filter can be set on the server. The card assembler assembles messages for each field to obtain the notification display content. The card assembler calls the filter to obtain the message type to be displayed required for card assembly in each field. The notification display bar is finally displayed on the terminal in the form of cards. The message display content and the display style information of the notification toolbar can be filled into the specified data structure of the card content according to the format agreed with the terminal to obtain the display information, which is a card-shaped notification toolbar.

[0096] The notification display includes the message's main title and / or subtitle and / or icon and / or a link to the page after clicking the message. Therefore, a crucial step is determining the type of message to be displayed for each field.

[0097] The notification content displayed varies across different sections. For example, some sections include a message icon, others include message type and condition-related information, and still others include both an icon and a link. Therefore, the card assembler uses different card-grouping methods depending on the section and message type. Specifically, a card-grouping method can be set for each section and message type. For instance, in a notification toolbar with six sections, if section 1 is used, the message's main title and icon are grouped into a card to obtain the notification content. If sections 2-6 are used, a filter is applied to obtain the message type to be displayed, and cards are grouped accordingly. If section 6 is used, the message's main title, icon, and link are grouped into a card to obtain the notification content.

[0098] In another embodiment, the message configuration parameters further include targeted push conditions for the message type. The parameters in the usage parameters corresponding to the first candidate message type satisfy the targeted push conditions for the first candidate message type.

[0099] The targeted push conditions for a message type refer to the fact that this message type will only be sent to users whose usage parameters meet specific characteristics. These targeted push conditions define the specific characteristics that must be met for this message type to be targeted. These specific characteristics include, but are not limited to, whether a certain application is installed or not, the user's gender, and the user's city.

[0100] That is, in determining whether the message configuration parameters of the first candidate message type meet the display conditions in the field, the method further includes: determining whether the parameters in the usage parameters corresponding to the first candidate message type meet the targeted push conditions of the first candidate message type. For example, after determining that the message effective field of the first candidate message type matches the field, it further determines whether the parameters in the usage parameters corresponding to the first candidate message type meet the targeted push conditions of the first candidate message type.

[0101] The parameters used include attribute values ​​across multiple dimensions, such as garbage data size, RAM usage percentage, number of updatable applications, user gender, and whether application A or application B is installed. The message configuration parameters for the corresponding first candidate message type can be configured with parameters for those dimensions. Specifically, the parameter in the parameters used that corresponds to the first candidate message type refers to the parameter in the parameters used that corresponds to the dimension of the first candidate message type. For example, if one of the message configuration parameters for the first candidate message type is "application A cache cleanup," then the parameter in the parameters used that corresponds to the first candidate message type is the cache size of application A.

[0102] Using parameters corresponding to the first candidate message type to satisfy the targeted push conditions for the first candidate message type. Specifically, this means using parameters in the parameters corresponding to the dimension of the first candidate message type to satisfy the characteristics defined by the targeted push conditions. For example, for a message type of "Application A cache cleanup," the targeted push conditions include: the user has installed application A. Then, it is further determined whether the parameters corresponding to the first candidate message type include "the user has installed application A." If so, the parameters in the parameters corresponding to the first candidate message type are used to satisfy the targeted push conditions for the first candidate message type.

[0103] In this embodiment, by setting various push conditions in the message configuration parameters, messages can be pushed to designated users.

[0104] In another embodiment, at least two fields include a first type of field and a second type of field, the display area of ​​the field corresponding to the second type of field is larger than that of the first type of field, and the message configuration parameters also include the display trigger conditions of the message type.

[0105] The first type of field is a regular field. If it is determined that the message configuration parameters of the first candidate message type meet the display conditions of the field, then the first candidate message type is used as the message type to be displayed in the field.

[0106] The second type of field has a larger display area compared to the first type. Generally speaking, the larger the display area, the more information can be displayed. To effectively utilize the second type of field, when determining the message type to be displayed, some relevant usage parameters are also displayed to guide user clicks. Taking the message type to be displayed as "junk cleanup" as an example, to guide user clicks on this field, the amount of junk data obtained from the user parameters is usually also included as display content, such as... Figure 2 The second column shows 101MB of system junk. This 101MB figure is based on the actual amount of junk on the terminal, determined by usage parameters. If the amount of junk is too small, it discourages users from actively clicking on it. This is because, based on user habits, users typically only actively clear system junk when the amount is substantial.

[0107] Therefore, for the second type of field, the display conditions for the field also include: the parameter in the usage parameters corresponding to the first candidate message type satisfies the display trigger condition of the first candidate message type.

[0108] The display trigger conditions refer to the conditions under which a message will be displayed in the notification toolbar. Typically, a display trigger condition is a threshold for one of the usage parameters; only when a certain parameter in a specific dimension reaches the corresponding threshold can the corresponding message be displayed in the notification toolbar. It is understandable that different message types have different display trigger conditions.

[0109] Specifically, in addition to displaying the message type and / or message icon, the second category of fields also displays user parameters related to the display trigger conditions.

[0110] The type of the current field can be determined based on the field identifier. For example, a notification toolbar may have six fields, such as... Figure 2 As shown, column 2 has more space than the other columns, therefore column 2 is a second-type column, while columns 1 and 3 through 6 are first-type columns. When the current column is column 2, which is a second-type column, it is determined that the message configuration parameters of the first candidate message type meet the display conditions for that column. Besides determining whether the effective column of the first candidate message type matches the column, and whether the parameters in the usage parameters corresponding to the first candidate message type meet the targeted push conditions for the first candidate message type, it is further determined that the parameters in the usage parameters corresponding to the first candidate message type meet the display trigger conditions for the first candidate message type. When all three conditions are met, the corresponding first candidate message type is determined as the message type to be displayed.

[0111] If the current field is a first type of field, it is determined that the message configuration parameters of the first candidate message type meet the display conditions of the field. The message type to be displayed can be determined based on whether the effective field of the first candidate message type matches the field and whether the parameters in the usage parameters corresponding to the first candidate message type meet the targeted push conditions of the first candidate message type.

[0112] For example, in terms of visual design, the first type of column has more space than other columns, aiming to display richer content. Taking junk file cleaning as an example, in columns other than 2, it only displays a junk file cleaning guide icon and a brief title. However, in column 2, it also displays the current user's junk file value. Therefore, a junk file threshold needs to be configured for column 2. When the user's junk file value does not reach this threshold, column 2 filters out the junk file cleaning message to prevent the displayed junk file value from being too small, which would discourage the user from clicking the message. In this embodiment, by setting message display conditions for messages displayed in columns with more content, the message is only displayed when the display conditions are met, thus guiding the user to click the message.

[0113] For example, the messages in a message pool and their configuration parameters are as follows:

[0114] Garbage cleanup messages (priority 10, garbage threshold 100MB (message display conditions), columns 2, 3, 4, and 5 were selected);

[0115] Application update message (priority 8, application update threshold is 2, fields 3, 4, and 5 are selected);

[0116] Promotional message (priority 7, content is a download guide for application A, targeted push condition is that the device does not have application A installed, and columns 2 and 3 are selected).

[0117] A terminal initiates a request with the following parameters: 80MB of garbage data, 5 updated applications, and application A not included in the installed application list. After the request reaches the server, taking field 2 as an example, based on the message effectiveness criteria, the candidate messages for field 2 include promotional messages and garbage cleanup messages. These are processed sequentially from highest to lowest priority. First, the garbage data is checked; since it does not reach the 100MB threshold for garbage cleanup messages, this message is filtered out. Since the promotional message is selected for field 2 and the targeted push conditions are met, this promotional message is ultimately selected for field 2, becoming the message type to be displayed for field 2.

[0118] The above method, by configuring different types of fields, allows for the display of more message content in specific fields as needed, achieving differentiated message display and highlighting important messages.

[0119] In another embodiment, when the column is a second type of column, if the parameter in the usage parameters corresponding to the first candidate message type does not meet the display trigger conditions of all the first candidate message types, then the promotion message is determined as the message type to be displayed in the column.

[0120] Specifically, promotional messages refer to messages pushed to users during product operation to promote specific products or content. For example, messages promoting a game or an application.

[0121] In the notification toolbar, the second type of column has a larger display area, thus having a more prominent effect. Therefore, when the parameter corresponding to the first candidate message type in the usage parameters does not meet the display trigger conditions for all first candidate message types, the promotional message will be displayed in the second type of column, thereby enabling the promotional message to be displayed in a prominent column.

[0122] Among them, "promotional message" is a general term for a type of message, which can be used to create various different promotional content based on a promotional task over a certain period of time. The promotional message that is ultimately displayed can be at least one of the following: promotional content that is within the effective period, matches the usage parameters, or has not been pushed to this terminal.

[0123] Promotional content can include at least one of the following: trending news push notifications, application recommendations, and weather forecast push notifications.

[0124] Specifically, the promotional content is time-sensitive. When generating promotional content, an effective period is set for each piece of content, and the content is cleaned up regularly to ensure its timeliness.

[0125] The promotional content can also be determined based on the terminal's usage parameters, specifically the user attribute parameters. For example, for push notifications sent to users in specific geographic locations, if the usage parameters determine that the user has not installed application A, the promotional message could recommend application A. Similarly, if the user parameters determine that the user is female and has not installed a game application B targeted at women, the promotional message could recommend game application B.

[0126] Among them, there can be multiple promotional messages in the message pool. To avoid duplicate pushes of promotional content, according to the push strategy, the promotional messages to be displayed are promotional content that have not been pushed to this terminal.

[0127] In this embodiment, by displaying the promotional message in the second type of column, the promotional message can be displayed in a prominent column.

[0128] In one embodiment, after the step of using the first candidate message type as the message type to be displayed in the field, the method further includes: deleting the first candidate message type from the message pool.

[0129] Specifically, once the message type to be displayed in the current field is determined, the first candidate message type in the message pool is deleted to avoid duplicate display.

[0130] In another embodiment, the message configuration parameters corresponding to the preset message pool are determined experimentally. Before determining the message type to be displayed for each column based on the usage parameters according to the preset message pool message configuration parameters, the method further includes: determining the experimental group identifier for the display update request; obtaining the message configuration parameters of the corresponding experimental group according to the experimental group identifier; the message configuration parameters corresponding to each experimental group are not completely the same, and the message configuration parameters include at least one of the following: message effective column, message display priority, targeted push condition, and display trigger condition; after pushing the information to be displayed to the terminal to display the information to be displayed in the notification toolbar of the terminal, the method further includes: determining the message configuration parameters corresponding to the experimental group identifier with the highest feedback popularity as the message configuration parameters corresponding to the message pool based on the feedback from the notification toolbar.

[0131] Specifically, in this embodiment, multiple experimental group identifiers and corresponding message configuration parameters are set for each experimental group identifier. The message display styles for each experimental group can also be different.

[0132] When a display update request is received, different experimental groups are matched. These groups can be assigned sequentially or based on user characteristics. Different experimental groups have different message configuration parameters, resulting in different display effects on the terminal's notification toolbar. This allows for diverse notification content display and the collection of data on the effects of various message configuration parameters. Specifically, message configuration parameters include at least one of the following: message activation field, message display priority, targeted push conditions, and display trigger conditions.

[0133] In another embodiment, based on feedback from the notification toolbar, the message configuration parameters corresponding to the experimental group identifier with the highest feedback popularity are determined as the message configuration parameters corresponding to the message pool.

[0134] The feedback popularity reflects user engagement with the notification toolbar and / or conversion rates. Higher usage and conversion rates result in higher feedback popularity. Therefore, the highest feedback popularity can be either the highest click-through rate or the highest conversion rate.

[0135] Click-through rate (CTR) is the ratio of clicks to push notifications. A higher CTR indicates a larger number of clicks on the notification toolbar, meaning the notification toolbar effectively encourages user clicks. Conversion rate is the ratio of conversions to push notifications. A conversion specifically refers to a user's desired action after viewing a notification from the notification toolbar, such as a purchase or download. Taking an app store application as an example, the conversion action specifically refers to a user's download of the application; the conversion rate is the ratio of app downloads to push notifications. A higher conversion rate indicates a larger number of downloads, meaning the notification toolbar effectively promotes download behavior.

[0136] Taking click-through rate (CTR) as an example, the experimental group with the highest feedback engagement is identified based on click behavior on the notification toolbar. Generally, a higher CTR indicates a higher percentage of users interacting with the notification after seeing it, suggesting that the message configuration parameters for that experimental group are reasonable and have high acceptance. Therefore, the message configuration parameters corresponding to that experimental group are designated as the specified message configuration parameters. When a new display update request is received, the display is updated based on the specified message configuration parameters, that is, the message configuration parameters corresponding to the experimental group with the highest CTR are extended to all display update requests.

[0137] The above-mentioned notification toolbar display control method involves conducting experiments on display update requests in advance, creating multiple experimental groups, determining different message configuration parameters, and then determining the optimal message configuration parameters based on feedback from different message configuration parameters, so as to operate based on the optimal message configuration parameters.

[0138] In one embodiment, taking an application market application as an example, the method for controlling the display of the notification toolbar is explained.

[0139] In this embodiment, the notification toolbar has 6 slots. Slot 1 displays the application icon and name, and slot 6 displays the "More Settings" icon. Slot 2 can display message types including: junk file cleanup, application 1 cleanup, application 2 cleanup, large file cleanup, phone acceleration, application update, search, promotional messages, and one-click phone status check. Slots 3-5 can display message types including: junk file cleanup, application 1 cleanup, application 2 cleanup, large file cleanup, phone acceleration, application update, and search. When creating a card for slot 2, the system checks whether the effective slots for each message configuration are met, whether the message display conditions are met, and whether the targeted push conditions are met. The message content includes a main title, a subtitle, and a jump link. When creating a card for slots 3-5, the system checks whether the message display conditions are met, and the message content includes an icon, text, and a jump link.

[0140] like Figure 8 As shown, this display method is jointly completed by the terminal, access layer, scenario-side service, experimental group platform, data source recall service, and message system.

[0141] The terminal initiates a display update request for the notification toolbar at a specified time, and enters the toolbar scene service through the access layer.

[0142] In this context, the "scene-side service" refers to the access service on the server side for each terminal's scene; in this solution, it refers to the notification toolbar scene. In this embodiment, the scene-side service is the link of the toolbar scene.

[0143] The processing flow of the scenario-based service is as follows: Figure 9 As shown, the display update request initiated by the terminal reaches the toolbar scene service through the access layer. The toolbar scene service parses the terminal request, packages the request information into a request format, and requests it to the experimental platform. The experimental platform uses the request information to retrieve the corresponding adapter from the backend data source recall service, obtaining two types of information: ① the content to be displayed in the field, and ② the address of the icon for the application update display. Next, the assembled field display information and the application update icon are combined into a card and returned. The structure returned after being packaged by the experimental platform is the request response.

[0144] The scenario service parses the response packets from the experimental platform, extracts the cards assembled from the data source, and combines them with style information to form the notification display content, which is then returned to the terminal. If no data is obtained or the experimental platform reports an error, the service reads the fallback configuration from the backend configuration file and returns it. The style information includes the style value of the notification toolbar, indicating whether the server selected a message configured normally by the content system or a fallback configuration generated by the server in case of an exception.

[0145] The fallback configuration is a fallback strategy used when the server encounters an abnormal situation while processing messages and cannot select the corresponding message. Each slot is fixed to a specific message, such as slot 1 for application icon and description, slot 2 for one-click phone status check, slot 3 for junk file cleanup, slot 4 for application search, slot 5 for phone acceleration, and slot 6 for more function settings.

[0146] The scenario provider requests the experimental platform, which uses the request information to retrieve the backend data source for service recall. Specifically, the experimental platform maps users to experimental groups, each with different content. Different users are assigned to different experimental groups based on rules, thus obtaining different content sources.

[0147] Among them, the server-side data source recall business processing flow, such as Figure 10 As shown, the data source recall service returns the message configuration parameters of the specified experimental group, calls the filter to determine the message type to be displayed in each field, and calls the card grouper to obtain the notification display content of each field according to the message type to be displayed.

[0148] Specifically, when retrieving data from the CMS cache (content system), the data is sorted according to its priority. Specifically, the update request carries an experiment group identifier (configured by the CMS data source group card). The corresponding message configuration data is located based on the experiment group identifier; if not found, an error is reported, and the scenario provider is redirected to a fallback page.

[0149] After finding the corresponding message configuration data, the field loader calls the card assembler sequentially from field 1 to field 6 (input parameters: field information, message configuration parameters, output parameters: card assembler rules). The card assembler calls the filter (input parameters: field information, message configuration parameters, output parameters: message type) and finally adds it to the card.

[0150] Specifically, the card grouping rules for each message in each field are extracted into a card grouper, which includes three parts: filtering, resource acquisition, and card grouping. The processing of the card grouper is shown in Figure 11. The input parameters of the card grouper are field information and CMS data (message configuration parameters), and the output parameter is the card grouping result. When the card grouping is successful, the corresponding message in the CMS data will be removed to avoid duplicate display (the message is deleted after successful card grouping). When the field is field 1, the card is grouped according to the icon in the message configuration parameters. When the field is fields 2-5, the filter is called to obtain the available message types, and card grouping is performed according to the message types. When the field is field 6, the card is grouped according to the icon and jump link in the message configuration parameters.

[0151] The filter performs filtering based on field information and message configuration parameters. Specifically, the filter processing is shown in Figure 12, and the filtering rules include:

[0152] S1201: Confirmation field.

[0153] S1202: Filter messages that are not effective in the specified field based on the field and the effective field of the message.

[0154] S1203, determine whether it is column number 2. In this embodiment, column number 2 is regarded as the second type of column.

[0155] If so, proceed to step S1204 and select the message type with the highest priority.

[0156] S1205: Based on the display trigger conditions and the targeted push conditions, determine which message types are configured for the first message in the current field; if it is not field 2, then take the first message in sequence and return it; if it is field 2, then take the first message in sequence and filter it according to the display trigger conditions and the targeted push conditions, and the fallback message must meet the display trigger conditions and the targeted push conditions.

[0157] S1206, determine whether the display trigger condition and / or targeted push condition are met. If yes, proceed to step S1207; otherwise, select the next message type according to priority and return to step S1205 to determine the next message type.

[0158] S1207, Return message type.

[0159] S1208, Remove this message type.

[0160] If the determination in step S1203 is negative, step S1209 is executed to retrieve the message with the highest priority.

[0161] After step S1209, step S1210 is executed, and the message type is returned.

[0162] After the card assembler calls the filter, the message type is obtained. Since the card assembly rules for each message in different fields are different, the card assembly rules are confirmed according to the message type and field information.

[0163] After the card assembler returns successfully, the corresponding message is deleted from the message list t. After adding the return result to the card, the filtering and card assembly for the next field are entered.

[0164] The technical solution of this application can bring greater traffic savings. The server combines the current status information uploaded by the terminal to screen and filter the messages in the message pool, and only sends the personalized message content that conforms to the user's status, saving the waste of user traffic. As a solution one, all types of full-volume messages are sent at one time. As a solution two, the solution of this application is adopted.

[0165] The theoretical calculation comparison of the effective traffic of the two solutions: Define the full-volume message as N messages, and the messages that can be exposed through screening and filtering are M messages (M < N). For the proportion of the effective traffic sent, the existing technical solution is M / N; the solution of this application is M / M = 100%. The specific experimental data comparison is as follows.

[0166] The current resident notification toolbar counts 2 million users in 1 day according to 9 types of messages. The experimental data of the displayed message types and display conditions are shown in Table 1:

[0167] Table 1 Statistics of the number of exposed users of each message type in the existing toolbar

[0168] Message Type Exposure conditions Number of users exposed percentage Garbage Cleanup Clean up junk files with confidence (>=100MB) 1195493 55.77% Application Update Apps to be updated >= 1 657221 32.86% Promotional message Accident rate affects operational content 419038 20.95% Application 1 Cleanup Safely clean up junk files in this program >= 100MB 328895 16.44% Application 2 Clean Safely clean up junk files in this program (>=100MB) 265871 13.29% Phone acceleration The phone's memory usage exceeds 60%. 185233 9.26% Good status indication The phone is in good condition. 115892 5.79% Large file cleanup Contains files that consume more than 1GB of memory. 104278 5.21 Check phone status with one click Backup configuration display 56697 2.83%

[0169] The size of a single message sent is about 200B, and the traffic of the messages that ultimately fail to be successfully exposed to the user's mobile phone is the wasted traffic. For the two solutions, the wasted traffic comparison for 2 million users in 1 day is described as follows.

[0170] Solution one:

[0171] The wasted traffic is:

[0172] [(1 - 59.77%) + (1 - 32.86%) + (1 - 20.95%) + (1 - 16.44%) + (1 - 13.29%) + (1 - 9.26%) + (1 - 5.79%) + (1 - 5.21%) + (1 - 2.83%)] * 2 million * 200B = 2798MB.

[0173] Solution two:

[0174] Considering a 0.5% network loss rate for message delivery and a 0.7% physical exposure loss rate for the terminal mobile phone after displaying the conditions, the wasted bandwidth is 200W * 200B * 9 * 0.5% * (1 + 0.7%) = 18MB.

[0175] Based on experimental data comparison, the solution of this invention, compared to Solution 1, saves up to 2780MB of data per day based on 2 million users. Furthermore, the data saving increases proportionally with the number of users. It is evident that in this application's solution, the terminal sends a request to the server carrying user status parameters. The server then dynamically sends toolbar messages that match the current user status according to a personalized strategy, based on uplink information, before displaying them on the terminal. This enriches the user's content experience, achieving a better user experience and improving business conversion rates. Furthermore, it helps reduce the interference caused by messages that do not match the user's current status, while simultaneously saving user data.

[0176] It should be understood that, although Figure 2 The steps in the flowchart 7-12 are shown sequentially as indicated by the arrows; however, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order in which these steps are performed, and they can be executed in other orders. Furthermore, Figure 2 At least some of the steps in 7-12 may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but may be executed at different times. The execution order of these steps or stages is not necessarily sequential, but may be executed in turn or alternately with other steps or at least some of the steps or stages in other steps.

[0177] In one embodiment, such as Figure 13 As shown, a display control device for a notification toolbar is provided. This device can be a software module, a hardware module, or a combination of both, integrated into a computer device. Specifically, the device includes:

[0178] The request acquisition module 1302 is used to acquire the display update request of the notification toolbar, the display update request carrying the terminal's usage parameters; the notification toolbar has at least two columns, and the column parameters of the at least two columns are not completely the same;

[0179] The message determination module 1304 is used to determine the message type to be displayed for each column based on the message configuration parameters corresponding to the preset message pool and according to the usage parameters; wherein, the message pool includes one or more message types;

[0180] The content acquisition module 1306 is used to acquire the message display content corresponding to the message type to be displayed in each column based on the usage parameters.

[0181] The encapsulation module 1308 is used to encapsulate the message display content corresponding to the message type to be displayed in each column and the display style information of the notification toolbar into information to be displayed;

[0182] The sending module 1310 is used to push the information to be displayed to the terminal so as to display the information to be displayed in the notification toolbar of the terminal.

[0183] In another embodiment, the message configuration parameters include multiple message types and corresponding message activation fields and message display priorities for each message type. The message determination module is further configured to determine a first candidate message type from the message pool in the order of the specified field order of the at least two fields, according to the message display priority of the message type from high to low. If the message configuration parameters of the first candidate message type meet the display conditions of the field according to the usage parameters, the first candidate message type is used as the message type to be displayed in the field. The display conditions of the field include the message activation field of the first candidate message type matching the field. If the message configuration parameters of the first candidate message type do not meet the display conditions of the field according to the usage parameters, the next message type of the first candidate message type is used as the new first candidate message type according to the message display priority of the message type from high to low, and the process returns to the step of "If the message configuration parameters of the first candidate message type meet the display conditions of the field according to the usage parameters, then the first candidate message type is used as the message type to be displayed in the field" and subsequent steps.

[0184] In another embodiment, the message configuration parameters further include targeted push conditions for the message type; the display conditions of the field further include: the parameter in the usage parameters corresponding to the first candidate message type satisfies the targeted push conditions for the first candidate message type.

[0185] In another embodiment, the at least two columns include a first type of column and a second type of column, wherein the display area of ​​the column corresponding to the second type of column is larger than that of the first type of column, and the message configuration parameters also include the display trigger conditions of the message type;

[0186] The message determination module is further configured to, when the column is a first type of column, if it is determined that the message configuration parameters of the first candidate message type meet the display conditions of the column, then use the first candidate message type as the message type to be displayed in the column; and to, when the column is a second type of column, if the display conditions of the column further include: the parameter in the usage parameters corresponding to the first candidate message type meets the display trigger condition of the first candidate message type, and if it is determined that the message configuration parameters of the first candidate message type meet the display conditions of the column, then use the first candidate message type as the message type to be displayed in the column.

[0187] In another embodiment, the message determination module is further configured to, when the column is a second type of column, determine the promotional message as the message type to be displayed for the column if the parameter corresponding to the first candidate message type in the usage parameters does not meet the display trigger conditions of all the first candidate message types.

[0188] In another embodiment, the message determination module is further configured to, after the step of setting the first candidate message type as the message type to be displayed in the field, further include: deleting the first candidate message type from the message pool.

[0189] In another embodiment, the display update request is sent when the terminal meets an update condition, which includes at least one of the following conditions:

[0190] The daemon process of the terminal application starts;

[0191] Notification messages in any field of the notification toolbar have been processed;

[0192] The terminal's usage parameters related to message types have changed; and

[0193] The preset time condition for requesting an update has been met.

[0194] In another embodiment, the message configuration parameters corresponding to the preset message pool are determined experimentally; the device further includes:

[0195] The experiment module is used to determine the experiment group identifier for the display update request; obtain the message configuration parameters of the corresponding experiment group according to the experiment group identifier; the message configuration parameters corresponding to each experiment group are not completely the same, and the message configuration parameters include at least one of the following: message effective field, message display priority, targeted push condition, and display trigger condition; after the information to be displayed is pushed to the terminal to display the information to be displayed in the terminal's notification toolbar, based on the feedback from the notification toolbar, the message configuration parameters corresponding to the experiment group identifier with the highest feedback popularity are determined as the message configuration parameters corresponding to the message pool.

[0196] Specific limitations regarding the display control device for the notification toolbar can be found in the above description of the display control method for the notification toolbar, and will not be repeated here. Each module in the aforementioned display control device for the notification toolbar can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in the computer device in hardware form, or stored in the memory of the computer device in software form, so that the processor can call and execute the corresponding operations of each module.

[0197] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 14 As shown, the computer device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores message data. The network interface communicates with external terminals via a network connection. When executed by the processor, the computer program implements a method for controlling the display of a notification toolbar.

[0198] Those skilled in the art will understand that Figure 14 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0199] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0200] In one embodiment, a computer-readable storage medium is provided storing a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0201] In one embodiment, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and executes the computer instructions, causing the computer device to perform the steps in the above method embodiments.

[0202] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the methods described above. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0203] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0204] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A method for controlling the display of a notification toolbar, characterized in that, The method includes: Obtain a display update request for the notification toolbar, the display update request carrying the terminal's usage parameters; the notification toolbar has at least two fields, and the field parameters of the at least two fields are not completely identical; Based on the message configuration parameters corresponding to the preset message pool, the message type to be displayed for each column is determined according to the usage parameters, including: sequentially determining a first candidate message type from the message pool for each of the at least two columns in descending order of message display priority; if the message configuration parameters of the first candidate message type, determined according to the usage parameters, meet the display conditions for the column, then the first candidate message type is used as the message type to be displayed for the column; the display conditions for the column include the first candidate message type's effective column matching the column; wherein, the message configuration parameters include multiple message types and the effective column and message display priority corresponding to each message type, and the message pool includes one or more message types; Based on the usage parameters, obtain the message display content corresponding to the message type to be displayed in each column; The message display content corresponding to the message type to be displayed in each column and the display style information of the notification toolbar are encapsulated into information to be displayed; The information to be displayed is pushed to the terminal so that it is displayed in the terminal's notification toolbar.

2. The method according to claim 1, characterized in that, The method of determining the message type to be displayed for each field based on the message configuration parameters corresponding to the preset message pool, according to the usage parameters, also includes: If, based on the usage parameters, it is determined that the message configuration parameters of the first candidate message type do not meet the display conditions in the column, then, according to the message display priority of message types from high to low, the next message type of the first candidate message type is taken as the new first candidate message type, and the process returns to the step of, if, based on the usage parameters, it is determined that the message configuration parameters of the first candidate message type meet the display conditions in the column, then the first candidate message type is taken as the message type to be displayed in the column and subsequent steps are performed.

3. The method according to claim 2, characterized in that, The message configuration parameters also include targeted push conditions for message types; the display conditions for the field also include: the parameters in the usage parameters corresponding to the first candidate message type satisfy the targeted push conditions for the first candidate message type.

4. The method according to claim 2 or 3, characterized in that, The at least two columns include a first type of column and a second type of column, the display area of ​​the column corresponding to the second type of column is larger than that of the first type of column, and the message configuration parameters also include the display trigger conditions of the message type; If, based on the usage parameters, the message configuration parameters of the first candidate message type satisfy the display conditions of the column, then the first candidate message type is used as the message type to be displayed in the column, including: When the column is a first type of column, if it is determined that the message configuration parameters of the first candidate message type meet the display conditions of the column, then the first candidate message type is used as the message type to be displayed in the column. When the column is a second type of column, the display conditions of the column also include: the parameter in the usage parameters corresponding to the first candidate message type satisfies the display trigger condition of the first candidate message type; if the message configuration parameter of the first candidate message type is determined to satisfy the display conditions of the column according to the usage parameters, then the first candidate message type is used as the message type to be displayed in the column.

5. The method according to claim 4, characterized in that, When the column is a second type of column, if the parameter in the usage parameters corresponding to the first candidate message type does not meet the display trigger conditions of all the first candidate message types, then the promotion message is determined as the message type to be displayed in the column.

6. The method according to claim 2, characterized in that, After the step of setting the first candidate message type as the message type to be displayed in the field, the method further includes: deleting the first candidate message type from the message pool.

7. The method according to claim 1, characterized in that, The display update request is sent when the terminal meets the update conditions, which include at least one of the following conditions: The daemon process of the terminal application starts; Notification messages in any field of the notification toolbar have been processed; The terminal's usage parameters related to message types have changed; and The preset time condition for requesting an update has been met.

8. The method according to claim 1, characterized in that, The message configuration parameters corresponding to the preset message pool were determined experimentally; before determining the message type to be displayed for each field based on the usage parameters according to the preset message pool message configuration parameters, the method further includes: Determine the experimental group identifier for the display update request; The message configuration parameters for the corresponding experimental group are obtained according to the experimental group identifier. The message configuration parameters for each experimental group are not completely the same. The message configuration parameters include at least one of the following: message activation field, message display priority, targeted push conditions, and display trigger conditions. After pushing the information to be displayed to the terminal to show the information in the terminal's notification toolbar, the method further includes: Based on the feedback from the notification toolbar, the message configuration parameters corresponding to the experimental group with the highest feedback popularity are determined as the message configuration parameters corresponding to the message pool.

9. A display control device for a notification toolbar, characterized in that, The device includes: The request acquisition module is used to acquire the display update request of the notification toolbar, the display update request carrying the terminal's usage parameters; the notification toolbar has at least two fields, and the field parameters of the at least two fields are not completely the same; The message determination module is used to determine the message type to be displayed for each column based on the message configuration parameters corresponding to a preset message pool, according to the usage parameters. This includes: sequentially determining a first candidate message type from the message pool for each of the at least two columns in descending order of message display priority; if the message configuration parameters of the first candidate message type, determined according to the usage parameters, satisfy the display conditions for that column, then the first candidate message type is used as the message type to be displayed for that column; the display conditions for that column include the first candidate message type's effective column matching the column; wherein the message configuration parameters include multiple message types and the corresponding effective column and message display priority for each message type, and the message pool includes one or more message types; The content acquisition module is used to acquire the message display content corresponding to the message type to be displayed in each column based on the usage parameters. The encapsulation module is used to encapsulate the message display content corresponding to the message type to be displayed in each column and the display style information of the notification toolbar into information to be displayed; The sending module is used to push the information to be displayed to the terminal so that the information to be displayed is displayed in the notification toolbar of the terminal.

10. The display control device for the notification toolbar according to claim 9, characterized in that, The message determination module is further configured to, if the message configuration parameters of the first candidate message type determined according to the usage parameters do not meet the display conditions in the column, then, in descending order of message display priority of message types, take the next message type of the first candidate message type as the new first candidate message type, and return to execute the steps of, if the message configuration parameters of the first candidate message type determined according to the usage parameters meet the display conditions in the column, then take the first candidate message type as the message type to be displayed in the column and subsequent steps.

11. The display control device for the notification toolbar according to claim 10, characterized in that, The message configuration parameters also include targeted push conditions for message types; The display conditions for the column also include: the parameter in the usage parameters corresponding to the first candidate message type satisfies the targeted push conditions of the first candidate message type.

12. The display control device for the notification toolbar according to claim 10 or 11, characterized in that, The at least two columns include a first type of column and a second type of column, the display area of ​​the column corresponding to the second type of column is larger than that of the first type of column, and the message configuration parameters also include the display trigger conditions of the message type; The message determination module is further configured to, when the field is a first type of field, if it is determined that the message configuration parameters of the first candidate message type meet the display conditions of the field, then use the first candidate message type as the message type to be displayed in the field. It is also used to, when the column is a second type of column, further include the following display conditions for the column: the parameter in the usage parameters corresponding to the first candidate message type satisfies the display trigger condition of the first candidate message type; if the message configuration parameter of the first candidate message type is determined to satisfy the display conditions of the column according to the usage parameters, then the first candidate message type is used as the message type to be displayed in the column.

13. The display control device for the notification toolbar according to claim 12, characterized in that, The message determination module is further configured to, when the column is a second type of column, determine the promotional message as the message type to be displayed for the column if the parameter corresponding to the first candidate message type in the usage parameters does not meet the display trigger conditions of all the first candidate message types.

14. The display control device for the notification toolbar according to claim 10, characterized in that, The message determination module is further configured to delete the first candidate message type from the message pool after the step of using the first candidate message type as the message type to be displayed in the field.

15. The display control device for the notification toolbar according to claim 9, characterized in that, The display update request is sent when the terminal meets the update conditions, which include at least one of the following conditions: The daemon process of the terminal application starts; Notification messages in any field of the notification toolbar have been processed; The terminal's usage parameters related to message types have changed; and The preset time condition for requesting an update has been met.

16. The display control device for the notification toolbar according to claim 9, characterized in that, The message configuration parameters corresponding to the preset message pool were determined experimentally; the device also includes: The experiment module is used to determine the experiment group identifier for the display update request; obtain the message configuration parameters of the corresponding experiment group according to the experiment group identifier; the message configuration parameters corresponding to each experiment group are not completely the same, and the message configuration parameters include at least one of the following: message effective field, message display priority, targeted push condition, and display trigger condition; after the information to be displayed is pushed to the terminal to display the information to be displayed in the terminal's notification toolbar, based on the feedback from the notification toolbar, the message configuration parameters corresponding to the experiment group identifier with the highest feedback popularity are determined as the message configuration parameters corresponding to the message pool.

17. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 8.

18. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 8.

19. A computer program product comprising computer instructions, characterized in that, When the computer instructions are executed by the processor, they implement the steps of the method according to any one of claims 1 to 8.

Images