Push information processing method and device and storage medium

Abstract

The invention discloses a push information processing method and device and a storage medium. The embodiment of the invention is applied to a vehicle-mounted terminal, and the method comprises the steps: obtaining the cache capacity of a push information cache list corresponding to a target application; when the cache capacity meets a preset capacity condition, determining candidate deletion push information meeting a preset screening condition based on the position of the to-be-pushed information in the push information cache list; repeatedly pushed information in the multiple pieces of information to be pushed is obtained; selecting push information to be deleted from the candidate deletion push information and the repeated push information; the to-be-deleted push information is deleted, the updated push information cache list is obtained, and in the embodiment of the invention, the target push information needing to be displayed can be quickly screened out from the updated push information cache list. Therefore, according to the scheme, the content popularization efficiency and the starting speed of the application program during starting can be improved, the user experience is improved, and occupation of storage resources is reduced.

Description

Technical Field

[0001] This application relates to the field of computers, and in particular to a method, device, and storage medium for processing push information. Background Art

[0002] The splash screen advertisement refers to the advertisement screen displayed when an application is launched. When a user opens an application, a splash screen is usually seen first, and advertisement content can be displayed on this screen. Splash screen advertisements are usually used to display advertisement information or brand promotion to users during the application loading process, so as to attract users' attention and increase brand exposure.

[0003] Currently, in order not to affect the startup speed of the application, the splash screen advertisement is usually sent to the application in advance by means of pre-storage. However, since different splash screen advertisements are displayed at different time periods for the application, multiple splash screen advertisements need to be stored. When the splash screen advertisement of the application is in a dynamically updated state, it is necessary to continuously store the splash screen advertisement of the application, thus occupying a large amount of storage resources.

[0004] However, due to limited storage resources, a large number of splash screen advertisements are likely to cause insufficient storage space on the device. Loading and displaying the splash screen advertisement when the application is launched will increase the startup time, resulting in a decline in user experience. Summary of the Invention

[0005] Embodiments of this application provide a method, device, and storage medium for processing push information, which can improve the content promotion efficiency and startup speed of the application when it is launched, improve the user experience, and reduce the occupation of storage resources.

[0006] Embodiments of this application provide a method for processing push information, including:

[0007] Obtain the cache capacity of the push information cache list corresponding to the target application. The push information cache list caches multiple push information to be sent for the target application, and the arrangement order of the push information in the push information cache list is determined based on the access order of the target application to the push information to be sent;

[0008] When the cache capacity meets the preset capacity condition, based on the position of the push information to be sent in the push information cache list, determine the candidate deletion push information that meets the preset screening condition from the multiple push information to be sent;

[0009] Perform a duplication detection on the multiple push information to be sent to obtain the duplicate push information among the multiple push information to be sent;

[0010] Based on the information validity time of the candidate deletion push information and the information validity time of the duplicate push information, select the push information to be deleted from the candidate deletion push information and the duplicate push information;

[0011] Delete the push information to be deleted from the push information cache list to obtain an updated push information cache list, so that when the target application is started, the target push information can be displayed on the application startup page of the target application through the updated push information cache list.

[0012] An embodiment of the present application further provides a processing device for push information, including:

[0013] An acquisition unit, configured to acquire the cache capacity of the push information cache list corresponding to the target application. The push information cache list caches multiple push information to be pushed for the target application, and the arrangement order of the push information to be pushed in the push information cache list is determined based on the access order of the target application to the push information to be pushed;

[0014] A content screening unit, configured to, when the cache capacity meets the preset capacity condition, determine candidate deletion push information that meets the preset screening condition from multiple push information to be pushed based on the position of the push information to be pushed in the push information cache list;

[0015] A duplicate detection unit, configured to perform duplicate detection on multiple push information to be pushed to obtain duplicate push information among the multiple push information to be pushed;

[0016] A deletion determination unit, configured to select push information to be deleted from the candidate deletion push information and the duplicate push information based on the information validity time of the candidate deletion push information and the information validity time of the duplicate push information;

[0017] A content deletion unit, configured to delete the push information to be deleted from the push information cache list to obtain an updated push information cache list, so that when the target application is started, the target push information can be displayed on the application startup page of the target application through the updated push information cache list.

[0018] In some embodiments, the push information cache list includes multiple push information storage nodes, and the push information storage nodes store push information to be pushed;

[0019] The duplicate detection unit includes a hash table acquisition subunit and a duplicate determination subunit:

[0020] A hash table acquisition subunit, configured to acquire the hash table corresponding to the push information cache list. The hash table includes the content identifier corresponding to the push information to be pushed and the index position information corresponding to the content identifier. The index position information records the storage node information of the push information to be pushed corresponding to the content identifier in the push information cache list;

[0021] A repeated determination subunit, configured to, if at least two storage node information are recorded at an index position information corresponding to a content identifier, use the to-be-pushed information respectively stored in the push information storage nodes corresponding to the at least two storage node information as repeated push information.

[0022] In some embodiments, after the content deletion unit, there further include a content identifier acquisition subunit, an index determination subunit, and a position adjustment subunit:

[0023] The content identifier acquisition subunit is configured to acquire a target content identifier corresponding to the target push information;

[0024] The index determination subunit is configured to determine, from a hash table, target index position information corresponding to the target content identifier;

[0025] The position adjustment subunit is configured to, according to the target storage node information recorded in the target index position information, remove the push information storage node corresponding to the target storage node information from the updated push information cache list, and add the push information storage node corresponding to the target storage node information to a preset position in the updated push information cache list.

[0026] In some embodiments, the deletion determination unit includes a first deletion subunit, a second deletion subunit, and a third deletion subunit:

[0027] The first deletion subunit is configured to, if there is repeated push information, determine target repeated push information from the repeated push information according to the information validity time of each repeated push information;

[0028] The second deletion subunit is configured to, when the information validity time of the candidate deletion push information does not meet a preset validity condition, use the candidate deletion push information and the target repeated push information as to-be-deleted push information; when the information validity time of the candidate deletion push information meets the preset validity condition, use the target repeated push information as to-be-deleted push information;

[0029] The third deletion subunit is configured to, if there is no repeated push information, use the candidate deletion push information as to-be-deleted push information.

[0030] In some embodiments, there further include an expiration determination subunit, an update acquisition subunit, and a content update subunit:

[0031] The expiration determination subunit is configured to determine, from multiple to-be-pushed information, expired push information according to the information validity time of each to-be-pushed information in the push information cache list;

[0032] The update acquisition subunit is configured to acquire updated push information of a promotion subject corresponding to the expired push information;

[0033] The content updating subunit is used to update the expired push information in the push information cache list by using the updated push information.

[0034] In some embodiments, the acquisition unit includes a first acquisition subunit, a content caching subunit, and a second acquisition subunit:

[0035] The first acquisition subunit is used to acquire the recommended push information to be cached required by the target application and the push information cache list corresponding to the target application;

[0036] The content caching subunit is configured to cache the push information to be cached in the push information cache list if the push information cache list does not include the push information to be cached;

[0037] The second acquiring subunit is configured to acquire the cache capacity of the push information cache list corresponding to the target application after the push information to be cached is completely cached.

[0038] In some embodiments, before the acquisition unit, an authentication subunit, an application identification acquisition subunit, an application identification sending subunit and a content receiving subunit are further included:

[0039] The authentication subunit is used to send the application information of the target application to the device server corresponding to the target device where the target application is located, so that the device server can authenticate the application information;

[0040] The application identification acquisition subunit is used to obtain the target application identification corresponding to the target application on the target device sent by the device server if the program information authentication is successful;

[0041] An application identification sending subunit, configured to send the target application identification to a push information server corresponding to the target application, so that the push information server uses the target application identification to push the cached push information for the target application in the target device to the device server;

[0042] The content receiving subunit is configured to receive, based on the target application identifier, push information to be cached and sent by the device server for the target application.

[0043] In some embodiments, after the content receiving subunit, a content parsing subunit, a content packaging subunit and a content storage subunit are further included:

[0044] The content parsing sub-unit is used to parse the push information to be cached and obtain promotion sub-information of at least one content attribute in the push information to be cached;

[0045] The content encapsulation sub-unit is used to encapsulate each promotion sub-information based on content attributes to obtain a push information data structure model;

[0046] A content storage subunit, configured to store the promotion sub-information corresponding to each content attribute encapsulated in the push information data model according to the push information storage policy corresponding to each content attribute.

[0047] In some embodiments, after the content deletion unit, there are further included a request acquisition subunit, a target promotion determination subunit, and a target promotion display subunit:

[0048] The request acquisition subunit is configured to acquire a startup request for a target application;

[0049] The target promotion determination subunit is configured to determine target push information based on the startup time corresponding to the startup request and the information delivery time of each to-be-pushed information in the updated push information recommendation list;

[0050] The target promotion display subunit is configured to display the target push information on the application startup page of the target application.

[0051] In some embodiments, the target promotion determination subunit is configured to determine at least one candidate push information from the to-be-pushed information according to the startup time corresponding to the startup request and the information delivery time of each to-be-pushed information in the updated push information recommendation list; and determine the target push information from the at least one candidate push information based on the position of each candidate push information in the updated push information recommendation list.

[0052] In some embodiments, the target promotion determination subunit is configured to acquire the display priority corresponding to the candidate push information; and determine the target push information from the at least one candidate push information according to the display priority corresponding to the candidate push information and the position of each candidate push information in the updated push information recommendation list.

[0053] An embodiment of the present application further provides an electronic device, including a processor and a memory, where the memory stores multiple instructions; the processor loads the instructions from the memory to execute the steps in any one of the push information processing methods provided by the embodiments of the present application.

[0054] An embodiment of the present application further provides a computer-readable storage medium, where the computer-readable storage medium stores multiple instructions, and the instructions are suitable for being loaded by a processor to execute the steps in any one of the push information processing methods provided by the embodiments of the present application.

[0055] An embodiment of the present application further provides a computer program product, including a computer program / instructions, where when the computer program / instructions are executed by a processor, the steps in any one of the push information processing methods provided by the embodiments of the present application are implemented.

[0056] An embodiment of the present application can obtain the cache capacity of the push message cache list corresponding to the target application. The push message cache list caches multiple push messages to be sent for the target application, and the arrangement order of the push messages to be sent in the push message cache list is determined based on the access order of the target application to the push messages to be sent. When the cache capacity meets the preset capacity condition, based on the position of the push messages to be sent in the push message cache list, candidate push messages to be deleted that meet the preset screening conditions are determined from the multiple push messages to be sent. Duplicate detection is performed on the multiple push messages to be sent to obtain duplicate push messages among the multiple push messages to be sent. Based on the information validity time of the candidate push messages to be deleted and the information validity time of the duplicate push messages, push messages to be deleted are selected from the candidate push messages to be deleted and the duplicate push messages. The push messages to be deleted are deleted from the push message cache list to obtain an updated push message cache list, so that when the target application is started, the target push messages can be displayed on the application start page of the target application through the updated push message cache list.

[0057] In the present application, by determining the arrangement order of the push messages to be sent in the push message cache list based on the access order of the target application to the push messages to be sent, the push messages to be sent that are frequently accessed can be preferentially displayed when the target application is started. To avoid the impact of too many push messages to be sent in the push message cache list on the startup speed of the target application, when the cache capacity of the push message cache list meets the preset capacity condition, candidate push messages to be deleted that may not be displayed in the push message cache list, as well as duplicate push messages, can be screened out, and push messages to be deleted are selected from the candidate push messages to be deleted and the duplicate push messages, so as to avoid accidentally deleting the candidate push messages that the target application may need to display when the cache space of the push message cache list is released. By deleting the push messages to be deleted from the push message cache list, the obtained updated push message cache list can release the cache space, ensuring that the push messages to be sent cached in the updated push message cache list are within a reasonable range, so that when the target application is started, the target push messages to be displayed can be quickly screened out from the updated push message cache list, which is beneficial to improving the content promotion efficiency and startup speed of the application program when starting, improving the user experience, and reducing the occupation of storage resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative efforts.

[0059] Figure 1a It is a schematic diagram of the scenario of the method for processing push messages provided by the embodiment of the present application;

[0060] Figure 1b is a schematic flowchart of a method for processing push information provided by an embodiment of the present application;

[0061] Figure 2a is a schematic diagram of a scenario of a method for displaying a startup screen advertisement provided by an embodiment of the present application;

[0062] Figure 2b is a flowchart of the registration work of a startup screen advertisement provided by an embodiment of the present application;

[0063] Figure 2c is a flowchart of receiving a startup screen advertisement provided by an embodiment of the present application;

[0064] Figure 2d is a flowchart of clearing a startup screen advertisement provided by an embodiment of the present application;

[0065] Figure 2e is a schematic diagram of displaying a target startup screen advertisement provided by an embodiment of the present application;

[0066] Figure 2f is a flowchart of loading a target startup screen advertisement provided by an embodiment of the present application;

[0067] Figure 3 is a schematic structural diagram of a device for processing push information provided by an embodiment of the present application;

[0068] Figure 4 is a schematic structural diagram of an electronic device provided by an embodiment of the present application. Detailed implementation manners

[0069] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative efforts belong to the scope of protection of the present application.

[0070] An embodiment of the present application provides a method, a device, and a storage medium for processing push information.

[0071] Among them, the device for processing push information can be specifically integrated in an electronic device, and the electronic device can be a device such as a terminal or a server. Among them, the terminal can be a device such as a mobile phone, a tablet computer, a smart Bluetooth device, a laptop computer, or a personal computer (PC); the server can be a single server or a server cluster composed of multiple servers.

[0072] In some embodiments, the processing device for push messages may also be integrated in multiple electronic devices. For example, the processing device for push messages may be integrated in multiple servers, and the multiple servers are used to implement the method for processing push messages of the present application.

[0073] In some embodiments, the server may also be implemented in the form of a terminal.

[0074] In the embodiments of the present application, the term "module" or "unit" refers to a computer program with a predetermined function or a part of a computer program, which works together with other related parts to achieve a predetermined goal, and can be fully or partially implemented by using software, hardware (such as a processing circuit or a memory), or a combination thereof. Similarly, one processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be a part of the overall module or unit that includes the function of the module or unit.

[0075] It can be understood that in the specific implementation manner of the present application, when it comes to obtaining relevant data such as application programs, when the embodiments of the present application are applied to specific products or technologies, user permission or consent needs to be obtained, and the collection, use, and processing of relevant data need to comply with relevant laws, regulations, and standards of relevant countries and regions.

[0076] For example, referring to Figure 1a , the electronic device may obtain the cache capacity of the push message cache list corresponding to the target application. The push message cache list caches multiple push messages to be pushed for the target application, and the arrangement order of the push messages to be pushed in the push message cache list is determined based on the access order of the target application to the push messages to be pushed; when the cache capacity meets the preset capacity condition, based on the position of the push messages to be pushed in the push message cache list, candidate deleted push messages that meet the preset screening conditions are determined from the multiple push messages to be pushed; a duplicate detection is performed on the multiple push messages to be pushed to obtain duplicate push messages among the multiple push messages to be pushed; based on the information validity time of the candidate deleted push messages and the information validity time of the duplicate push messages, the push messages to be deleted are selected from the candidate deleted push messages and the duplicate push messages; the push messages to be deleted are deleted from the push message cache list to obtain an updated push message cache list, so that when the target application is started, the target push messages are displayed on the application start page of the target application through the updated push message cache list.

[0077] Among them, by determining the arrangement order of the to-be-pushed information in the push information cache list based on the access order of the to-be-pushed information for the target application, the frequently accessed to-be-pushed information can be preferentially displayed when the target application is started. To avoid the impact of too much to-be-pushed information in the push information cache list on the startup speed of the target application, when the cache capacity of the push information cache list meets the preset capacity condition, the candidate deleted push information that may not be displayed and the duplicate push information in the push information cache list can be screened out, and the to-be-deleted push information is selected from the candidate deleted push information and the duplicate push information, so as to avoid accidentally deleting the candidate deleted push information that the target application may need to display when the cache space of the push information cache list is released. By deleting the to-be-deleted push information from the push information cache list, the obtained updated push information cache list can release the cache space, ensuring that the to-be-pushed information cached in the updated push information cache list is within a reasonable range, so that when the target application is started, the target push information to be displayed can be quickly screened out from the updated push information cache list, which is beneficial to improving the content promotion efficiency and startup speed of the application program when starting, improving the user experience, and reducing the occupation of storage resources.

[0078] The following will be described in detail respectively. It should be noted that the serial numbers of the following embodiments do not limit the preferred order of the embodiments.

[0079] In this embodiment, a method for processing push information is provided, as Figure 1b shown, and the specific process of this method for processing push information can be as follows:

[0080] 101. Obtain the cache capacity of the push information cache list corresponding to the target application. The push information cache list caches multiple pieces of to-be-pushed information for the target application, and the arrangement order of the to-be-pushed information in the push information cache list is determined based on the access order of the target application to the to-be-pushed information.

[0081] Among them, the target application is any application program installed on the terminal device. For example, the target application can be a system-built-in application program, such as contacts, phone, messages, browser, etc., or it can also be a third-party application program, such as social media, music player, map navigation, payment application, etc.

[0082] The to-be-pushed information refers to the information that the target application needs to promote cached in the push information cache list. For example, the to-be-pushed information can be advertisements, promotion information, or other marketing content, etc.

[0083] The push message cache list refers to a list of push messages to be displayed that are pre-cached by the target application when it starts up. For example, the push message cache list can include advertisements, promotional information, or other marketing content that the target application needs to display when it starts up. By pre-caching this content, it can be quickly retrieved and displayed when the target application starts up, improving the user experience and promotion effect.

[0084] The cache capacity refers to the capacity occupied by the push messages to be cached in the push message cache list. For example, the cache capacity can specifically be the number of push messages to be cached in the promotion memory cache list (i.e., the cache positions of the push messages in the push message cache list) or the byte occupancy, etc.

[0085] The arrangement order represents the relative positions of the push messages to be pushed in the push message cache list.

[0086] The access order refers to the order in which the target application accesses the push messages to be pushed when it starts up.

[0087] For example, if multiple push messages to be pushed in the push message cache list include Push Message 1, Push Message 2, and Push Message 3, and the arrangement order of the push messages in the push message cache list is Push Message 2, Push Message 1, Push Message 3, it means that when the target application last started up, it accessed Push Message 2, that is, the push message at the front of the push message cache list is the most recently accessed or used push message.

[0088] In some embodiments, in order to detect the cache capacity of the push message cache list corresponding to the target application and obtain the cache capacity of the push message cache list corresponding to the target application, it includes:

[0089] Obtain the push messages to be cached recommended by the target application and the push message cache list corresponding to the target application;

[0090] If the push message cache list does not include the push messages to be cached, cache the push messages to be cached in the push message cache list;

[0091] After the push messages to be cached are cached, obtain the cache capacity of the push message cache list corresponding to the target application.

[0092] Among them, the push messages to be cached refer to the push messages to be pushed that the target application needs to recommend and wait to be cached in the push message cache list. For example, the push messages to be cached can be push messages to be cached recommended by the target application obtained from local (such as local storage space) or remote (such as a server).

[0093] For example, the push message cache list includes pending push message 1 and pending push message 2, and the pending cached push message is pending push message 3. By analyzing the push message cache list, it can be seen that pending push message 3 is not included in the push message cache list. Then, pending push message 3 is cached into the push message cache list. If there are 5 cache positions in the push message cache list, after pending push message 3 is cached, 3 cache positions in the push message cache list are occupied, and 2 cache positions are left.

[0094] In some embodiments, the push message cache list includes multiple push message storage nodes, and the push message storage nodes store pending push messages;

[0095] If the pending cached push message is not included in the push message cache list, caching the pending cached push message into the push message cache list includes:

[0096] Obtain the hash table corresponding to the push message cache list and the specified content identifier corresponding to the pending cached push message. The hash table includes the content identifier corresponding to the pending push message and the index position information corresponding to the content identifier. The index position information records the storage node information of the pending push message corresponding to the content identifier in the push message cache list;

[0097] Determine the specified index position information corresponding to the specified content identifier from the hash table;

[0098] If the specified index position information does not record storage node information, it is determined that the pending cached push message is not included in the push message cache list.

[0099] Wherein, the push message storage node is a node in the push message cache list that can cache push messages, that is, the aforementioned push message storage node.

[0100] The hash table is used to quickly search for, insert, and delete pending push messages in the push message cache list.

[0101] The content identifier corresponding to the pending push message is used to identify the pending push message, and specifically may be a specific key value mapped by the pending push message. For example, the content identifier corresponding to the pending push message may be a content identifier obtained based on at least one of the user identifier for logging in to the target application, the version identifier of the pending push message, the content identifier, the timestamp, etc.

[0102] The index position information corresponding to the content identifier refers to the hash value obtained by converting the content identifier through a hash function, and this hash value corresponds to a specific index position in the hash table.

[0103] The storage node information refers to the information of the push message storage node where the pending push message is located in the push message cache list recorded in the hash table.

[0104] For example, if a push message to be cached is obtained and its content identifier is "ABC". First, the specified index position information corresponding to "ABC" will be searched for through a hash table. If the storage node information of the push message to be cached corresponding to "ABC" in the push message cache list is recorded at the specified index position information, it proves that the push message to be cached is cached in the push message cache list. If the storage node information of the push message to be cached corresponding to "ABC" in the push message cache list is not recorded at the specified index position information, it proves that the push message to be cached is not cached in the push message cache list.

[0105] In some embodiments, in order to receive a push message to be cached for a target application, before obtaining the push message to be cached recommended by the target application, it further includes:

[0106] Sending the application information of the target application to the device server corresponding to the target device where the target application is located, so that the device server performs an authentication process on the application information;

[0107] If the program information authentication is successful, obtain the target application identifier corresponding to the target application on the target device sent by the device server;

[0108] Sending the target application identifier to the push message server corresponding to the target application, so that the push message server uses the target application identifier to push the push message to be cached for the target application in the target device to the device server;

[0109] Based on the target application identifier, receive the push message to be cached for the target application sent by the device server.

[0110] Among them, the application information refers to the relevant data required for authentication and identity verification of the target application, and this application information can reflect whether the target application has legitimate access rights. For example, the application information may include the identifier, profile, certificate, etc. of the target application.

[0111] The target device is the terminal device where the target application is located. For example, the target device includes but is not limited to mobile phones, computers, intelligent voice interaction devices, smart home appliances, vehicle terminals, aircraft, etc.

[0112] The device server refers to the server that provides management and control services for the target device and can communicate with the target device. For example, the device server may be the manufacturer's server of the target device or the server that manages the target device, etc., and it can push information to the target device.

[0113] The target application identifier is an identifier used to uniquely identify the target application on the target device. The device server can use this identifier to determine the specific information or push content to be sent to the target application in the target device. Through the target application identifier, the device server can accurately send information to the target application on the target device to meet the needs of personalized push or targeted promotion.

[0114] The push information server is used to establish a mapping relationship between the push information and the target application identifier. The push information server can use the target application identifier to push the to-be-cached push information for the target application in the target device to the device server.

[0115] So that the push information server can push the to-be-cached push information for the target application in the target device to the device server.

[0116] The identifier of the target application is the unique identifier of the target application. By providing the correct identifier of the target application to the device server, the device server can locate and send information to the target application.

[0117] The description file contains the configuration information of the target application, including the permissions, functions, and related settings of the push service of the target application. After these configuration information are packaged into the description file, developers can download it to the target device so that the target application can normally connect and communicate with the device server.

[0118] The certificate is a certificate for authentication and encryption when the target application communicates with the device server. The certificate is usually generated by the device server and downloaded to the target device. Through the certificate, the target application can establish a secure connection with the device server and ensure the confidentiality and integrity of the communication.

[0119] For example, when the target application needs to carry out certain content promotion activities during the anniversary celebration, the push information server actively sends a message to the device server. Among them, the assembly of the to-be-cached push information needs to be docked according to the specifications of the device server. Then it is processed by the device server and transmitted to the target device.

[0120] In some embodiments, the to-be-cached push information is pushed to the target terminal in a silent push manner, that is, after the target terminal receives the to-be-cached push information, it is not displayed in the notification bar, and the to-be-cached push information is directly sent to the target application in the background of the target terminal, and the content promotion module of the target application parses and processes the to-be-cached push information.

[0121] In some embodiments, in order to store the to-be-cached push information in the local of the target device where the target application is located, after receiving the to-be-cached push information for the target application sent by the device server based on the target application identifier, it further includes:

[0122] Parse and process the cached push information to obtain promotion sub-information of at least one content attribute in the cached push information;

[0123] Based on the content attribute, encapsulate each promotion sub-information to obtain a push information data structure model;

[0124] According to the push information storage policy corresponding to each content attribute, store the promotion sub-information corresponding to each content attribute encapsulated in the push information data model.

[0125] Among them, the content attribute can refer to various features of the cached push information. For example, the content attribute can indicate the specific content of the cached push information itself, the information validity period, the information delivery time, and the display priority, etc.

[0126] The promotion sub-information refers to the relevant information of the content attribute in the cached push information. For example, the promotion sub-information can be the specific content of the cached push information itself, the information validity period, the information delivery time, and the display priority, etc.

[0127] The push information data structure model uniformly encapsulates the to-be-promoted sub-information of each content attribute to better manage and operate the cached push information, and achieve accurate positioning and display of the cached push information.

[0128] The push information storage policy refers to the policy used to store the promotion sub-information corresponding to the content attribute. For example, the push information storage policy can include SharedPreferences, file storage, and SQLite, etc.

[0129] 102. When the cache capacity meets the preset capacity condition, based on the position of the to-be-pushed information in the push information cache list, determine the candidate deleted push information that meets the preset screening condition from multiple to-be-pushed information.

[0130] Among them, the preset capacity condition is a condition preset for measuring the capacity of the push information cache list to avoid the push information cache list caching too many to-be-pushed information and affecting the startup speed of the target application. For example, the preset capacity condition can specifically indicate that the cache capacity is not less than (i.e., greater than or equal to) the capacity threshold in the preset capacity condition, that is, when the cache capacity is greater than or equal to the capacity threshold, based on the position of the to-be-pushed information in the push information cache list, determine the candidate deleted push information that meets the preset screening condition from multiple to-be-pushed information.

[0131] The position is the relative position where the to-be-pushed information is stored in the push information cache list.

[0132] For example, the push message cache list includes to-be-pushed message 1, to-be-pushed message 2, and to-be-pushed message 3. In the push message cache list, to-be-pushed message 2 is followed by to-be-pushed message 1, and to-be-pushed message 1 is followed by to-be-pushed message 3. This indicates that to-be-pushed message 2 ranks first in the push message cache list. That is, when the target application starts, it first attempts to display to-be-pushed message 2. If the target application cannot meet the display conditions of to-be-pushed message 2 during the current startup, it then continues to attempt to display to-be-pushed message 1. And when it cannot meet the display conditions of to-be-pushed message 1, it continues to attempt to display to-be-pushed message 3. The display conditions can specifically refer to the information delivery time of the to-be-pushed message. That is, when the target application starts at the content delivery time, it can display the to-be-pushed message.

[0133] The preset screening condition is a condition preset for screening the to-be-pushed messages in the push message cache list that may be deleted, so that the to-be-pushed messages that may be deleted have less impact on the subsequent startup of the target application.

[0134] For example, the preset screening condition can indicate that the to-be-pushed message at the preset screening position in the push message cache list is used as the candidate deletion push message. The preset screening position can be the last n rows or the first n rows of the push message cache list, where the last n rows or the first n rows are less than the total number of rows in the push message cache list. Among them, the push message cache list is composed of push message storage nodes storing to-be-pushed messages arranged in order. The last n rows refer to the last n push message storage nodes in the push message cache list, and the first n rows refer to the first n push message storage nodes in the push message cache list.

[0135] The candidate deletion push message is a to-be-pushed message that is not frequently used in the push message cache list. That is, when the target application is at the information delivery time of the candidate deletion push message, the target application is not frequently enabled, indicating that if the candidate deletion push message is deleted, the target application has less chance of using the candidate deletion push message when starting up, that is, it is difficult to appear in the startup process of the target application. Therefore, the candidate deletion push message is re-cached locally or remotely to avoid the startup speed of the target application.

[0136] For example, the specification capacity of the push message cache list is q push message storage nodes and p byte occupancy. Currently, the cache capacity occupied by the push message cache list is m push message storage nodes and k byte occupancy. The preset capacity can refer to q push message storage nodes and p byte occupancy, or (q - x) push message storage nodes, (p - z) byte occupancy. If at least one of m push message storage nodes and k byte occupancy is not less than their respective preset capacities, the to-be-pushed messages in the last n rows of the push message cache list can be used as the candidate deletion push messages. Here, the values of q, p, m, k, x, and z are not restricted.

[0137] 103. Perform duplicate detection on multiple messages to be pushed, and obtain duplicate push messages among the multiple messages to be pushed.

[0138] Among them, the duplicate push message refers to the messages to be pushed with the same or similar content among the multiple messages to be pushed.

[0139] For example, the push message cache list may include messages to be pushed A and message to be pushed B with the same or similar content. In the push message cache list, message to be pushed A and message to be pushed B may be different versions of the same advertisement. Specifically, they may be used for A / B testing or multivariate testing, and they may be different in terms of copywriting, position, size, etc. In addition, message to be pushed A may also be the message to be pushed for updating message to be pushed B, or the same message to be pushed is cached in the push message cache list at least twice, and so on.

[0140] In some embodiments, in order to obtain duplicate push messages in the push message cache list, the push message cache list includes multiple push message storage nodes, and the push message storage nodes store messages to be pushed;

[0141] Performing duplicate detection on multiple messages to be pushed, and obtaining duplicate push messages among the multiple messages to be pushed, includes:

[0142] Obtain the hash table corresponding to the push message cache list. The hash table includes the content identifier corresponding to the message to be pushed and the index position information corresponding to the content identifier. The index position information records the storage node information of the message to be pushed corresponding to the content identifier in the push message cache list;

[0143] If the index position information corresponding to the content identifier records at least two storage node information, then regard the messages to be pushed stored in the push message storage nodes corresponding to the at least two storage node information as duplicate push messages.

[0144] For example, suppose the hash table includes content identifier 123, content identifier 456, content identifier 789, and content identifier 234. The index position information corresponding to 123 records storage node information 1 and storage node information 4, the index position information corresponding to 456 records storage node information 2, the index position information corresponding to 789 records storage node information 3, and the index position information corresponding to 234 records storage node information 5. Regularly or when obtaining the message to be cached and pushed, detect the hash table corresponding to the push message cache list, and it can be obtained that the index position information corresponding to 123 records storage node information 1 and storage node information 4. That is, regard the messages to be pushed stored in the push message storage node 1 corresponding to storage node information 1 and the push message storage node 4 corresponding to storage node information 4 as duplicate push messages.

[0145] 104. Select the push messages to be deleted from the candidate deletion push messages and the duplicate push messages based on the information validity period of the candidate deletion push messages and the information validity period of the duplicate push messages.

[0146] Among them, the information validity period of the candidate deletion push message refers to the valid time of the candidate deletion push message in the promotion activity. If the information validity period is exceeded, the candidate deletion promotion will no longer be displayed.

[0147] The information validity period of the duplicate push message refers to the valid time of the duplicate push message in the promotion activity. If the information validity period is exceeded, the duplicate push message will no longer be displayed.

[0148] The push messages to be deleted are the push messages to be pushed that are waiting to be deleted among the candidate deletion push messages and the duplicate push messages. For example, the push messages to be deleted can be the push messages to be pushed that have expired, or the push messages to be pushed that are about to expire when there are no expired push messages to be pushed, or the push messages to be pushed that have expired and are about to expire, and so on.

[0149] In some embodiments, in order to determine the push messages to be deleted, select the push messages to be deleted from the candidate deletion push messages and the duplicate push messages based on the information validity period of the candidate deletion push messages and the information validity period of the duplicate push messages, including:

[0150] If there are duplicate push messages, determine the target duplicate push messages from the duplicate push messages according to the information validity period of each duplicate push message;

[0151] When the information validity period of the candidate deletion push message does not meet the preset validity condition, use the candidate deletion push message and the target duplicate push message as the push messages to be deleted;

[0152] When the information validity period of the candidate deletion push message meets the preset validity condition, use the target duplicate push message as the push message to be deleted;

[0153] If there are no duplicate push messages, use the candidate deletion push message as the push message to be deleted.

[0154] Among them, the target duplicate push message refers to the push message to be deleted among the duplicate push messages.

[0155] The preset validity condition is the condition preset to measure whether the candidate deletion push message is valid.

[0156] For example, there are duplicate push message a and duplicate push message a`. The information validity period of duplicate push message a is t, and the information validity period of duplicate push message a` is t`. Compare the information validity period t and the information validity period t`.

[0157] If the information validity time t reflects that the repeated push message a has expired, while the information validity time t' reflects that the repeated push message a' has not expired, then the repeated push message a is taken as the target repeated push message.

[0158] If the information validity time t is less than the information validity time t', then the repeated push message a can be taken as the target repeated push message. If the information validity time t is greater than the information validity time t', then the repeated push message a' can be taken as the target repeated push message. If the information validity time t is equal to the information validity time t', then either the repeated push message a or the repeated push message a' can be taken as the target repeated push message.

[0159] When the target repeated push message is obtained, continue to determine whether the candidate deletion push message is valid. When the candidate deletion push message is invalid, both the target repeated push message and the candidate deletion push message are taken as the push messages to be deleted, so as to release more cache space, which is beneficial to accelerating the startup speed of the target application. When the candidate deletion push message is valid, only the target repeated push message is taken as the push message to be deleted, so as to avoid the need to re-cache the candidate deletion push message when the target application starts during the information delivery time of the candidate deletion push message, which is beneficial to the startup of the target application. In the case where there is no repeated push message, the candidate deletion push message is directly taken as the push message to be deleted, releasing the cache space of the cache list of the push message to be cached, so as to cache new push messages to be sent.

[0160] 105. Delete the push message to be deleted from the push message cache list to obtain an updated push message cache list, so that when the target application starts, the target push message is displayed on the application startup page of the target application through the updated push message cache list.

[0161] Among them, the updated push message cache list is the push message cache list from which the push message to be deleted has been deleted.

[0162] It can be selected to remove it from the local storage to release the storage space. It can also be selected to keep it in the local storage for subsequent use or backup. Whether to delete the local storage specifically can be determined according to actual requirements and business regulations. Generally speaking, if the push message to be deleted has expired or is no longer needed, then it can be deleted from the local storage to save storage resources; if the push message to be deleted may still be used, then it can be kept in the local storage for subsequent use or backup.

[0163] The application startup page is the page that is first shown to the user when the target application starts. Usually, the application startup page will display the icon and name of the target application.

[0164] The target push message is the push message to be pushed that matches the startup time of the target application.

[0165] In some embodiments, in order to enable the arrangement order of the push messages to be pushed in the push message cache list to be determined based on the access order of the target application to the push messages to be pushed, the push message to be deleted is deleted from the push message cache list to obtain an updated push message cache list. After the target push message is displayed on the application startup page of the target application through the updated push message cache list when the target application starts, it further includes:

[0166] Obtain the target content identifier corresponding to the target push message;

[0167] Determine the target index position information corresponding to the target content identifier from the hash table;

[0168] According to the target storage node information recorded by the target index position information, remove the push message storage node corresponding to the target storage node information from the updated push message cache list, and add the push message storage node corresponding to the target storage node information to a preset position in the updated push message cache list.

[0169] Among them, the target content identifier is used to identify the target push message, and specifically, it can be a specific key value mapped by the target push message.

[0170] The target index position information refers to the hash value obtained by converting the target content identifier through a hash function, and this hash value corresponds to a specific index position in the hash table.

[0171] The target storage node information refers to the information of the push message storage node where the target push message is located in the push message cache list recorded in the hash table.

[0172] The preset position refers to a specified position extracted from the updated push message cache list for inserting the push message to be pushed used when the target application starts. For example, the preset position can be the beginning, end, etc. of the updated push message cache list. For example, by looking up the hash table, the target index position information corresponding to the target content identifier "ABC123" of the target push message is found to be 2. Then, according to the target index position information 2, it is known that the target storage node information is the information stored in the 3rd row of the updated push message cache list. Next, remove the push message storage node in the third row from the updated push message cache list, and add the removed push message storage node to the preset position of the updated push message cache list.

[0173] Among them, if the preset position is at the beginning of the update push message cache list, the preset screening position in the foregoing preset screening condition may be the last n rows. If the preset position is at the end of the update push message cache list, the preset screening position in the preset screening condition may be the first n rows.

[0174] In some embodiments, in order to display push messages that match the startup time of the target application, after deleting the push messages to be deleted from the push message cache list to obtain an updated push message cache list, so as to display the target push messages on the application startup page of the target application when the target application starts, it further includes:

[0175] Obtain a startup request for the target application;

[0176] Based on the startup time corresponding to the startup request and the information delivery time of each push message to be pushed in the updated push message recommendation list, determine the target push message;

[0177] Display the target push message on the application startup page of the target application.

[0178] Among them, the startup request is a request sent by the user when opening the target application.

[0179] The startup time is the time when the target application sends the startup request.

[0180] The information delivery time refers to a specific time period for displaying the push message to be pushed to the target audience. This time period can be a specific time range of a day, a week, or a month, and is used to determine when the push message to be pushed is displayed. During this time period, the push message to be pushed will be displayed to the target audience regularly or on demand to increase the exposure and influence of the advertisement.

[0181] In some embodiments, in order to quickly obtain the target push message, based on the startup time corresponding to the startup request and the information delivery time of each push message to be pushed in the updated push message recommendation list, determining the target push message includes:

[0182] According to the startup time corresponding to the startup request and the information delivery time of each push message to be pushed in the updated push message recommendation list, determine at least one candidate push message from the push messages to be pushed;

[0183] Based on the position of each candidate push message in the updated push message recommendation list, determine the target push message from at least one candidate push message.

[0184] Among them, the candidate push information is the information to be pushed that is suitable for display to the user at the startup time in the candidate push information recommendation list, and there is an intersection between the information delivery time of the candidate push information and the startup time. For example, there may be at least one candidate push information that matches the startup time in the updated push information recommendation list, or there may be no candidate push information.

[0185] For example, if there is only one candidate push information, then use this candidate push information as the target push information. If there are multiple candidate push information, it can be to use the candidate push information ranked at the top in the updated push information recommendation list as the target push information to quickly start the target application, or it can be to use any one of the candidate push information other than the one ranked at the top as the target push information to increase the exposure of this candidate push information.

[0186] In some embodiments, in order to be able to preferentially display the push information, based on the position of each candidate push information in the updated push information recommendation list, determining the target push information from at least one candidate push information includes:

[0187] Obtain the display priority corresponding to the candidate push information;

[0188] According to the display priority corresponding to the candidate push information and the position of each candidate push information in the updated push information recommendation list, determine the target push information from at least one candidate push information.

[0189] Among them, the display priority is used to reflect the display priority of the candidate push information in the same time period.

[0190] For example, the candidate push information includes candidate push information X, candidate push information Y, and candidate push information Z. Among them, the display priority corresponding to candidate push information X is high, and it is located in the second row of the updated push information recommendation list. The display priority corresponding to candidate push information Y is low, and it is located in the first row of the updated push information recommendation list. The display priority corresponding to candidate push information Z is medium, and it is located in the third row of the updated push information recommendation list.

[0191] Since the display priority corresponding to candidate push information Y in the updated push information recommendation list is low, it is possible to directly access candidate push information X downward without accessing candidate push information Y. Since the display priority corresponding to candidate push information X is high, directly use candidate push information X as the target push information, which is convenient for quickly determining the target push information and saves time and resources.

[0192] In some embodiments, in order to be able to display the push information according to specific display requirements, displaying the target push information on the application startup page of the target application includes:

[0193] Obtain the display requirements for the target push information;

[0194] According to the display requirements of the push information, display the target push information on the application startup page of the target application.

[0195] Among them, the display requirements of the push information refer to the specific requirements and specifications of the target push information displayed on the application startup page of the target application. The display requirements of the push information can be requirements for advertisers, users, application developers, etc., aiming to ensure the effective display of the target push information and a good user experience.

[0196] For example, the display requirements of the push information can be the display form, display timing, display frequency, target audience positioning, etc. of the target push information.

[0197] In some embodiments, in order to update the expired push information, it further includes:

[0198] Determine the expired push information from multiple push information to be sent according to the information validity period of each push information to be sent in the push information cache list;

[0199] Obtain the updated push information of the promotion entity corresponding to the expired push information;

[0200] Use the updated push information to update the expired push information in the push information cache list.

[0201] Among them, the expired push information refers to the push information to be sent that has exceeded its information validity period.

[0202] The promotion entity is the entity or organization of the expired push information, usually an advertiser or a brand.

[0203] The updated push information is the push information invested by the promotion entity to update the expired push information.

[0204] For example, after obtaining the updated push information, the updated push information can be used to replace the expired push information in the push information cache list.

[0205] If the promotion entities of the updated push information and the expired push information are the same, and the updated push information and the expired push information have the same content identifier, that is, it is not necessary to modify the content corresponding to the expired push information in the hash table after updating the expired push information.

[0206] If the update push information and the expired push information have different content identifiers, that is, the update push information corresponds to an update content identifier, after the expired push information is updated, the content corresponding to the expired push information in the hash table is deleted, and the index position information corresponding to the update content identifier is determined in the hash table, and the storage node information of the push information storage node where the update push information is located in the push information cache list is added at the index position information.

[0207] In the embodiment of the present application, the cache capacity of the push information cache list corresponding to the target application can be obtained. The push information cache list caches multiple push information to be pushed for the target application, and the arrangement order of the push information to be pushed in the push information cache list is determined based on the access order of the target application to the push information to be pushed; when the cache capacity meets the preset capacity condition, based on the position of the push information to be pushed in the push information cache list, candidate deletion push information that meets the preset screening conditions is determined from the multiple push information to be pushed; a repeatability detection is performed on the multiple push information to be pushed to obtain duplicate push information among the multiple push information to be pushed; based on the information validity time of the candidate deletion push information and the information validity time of the duplicate push information, the push information to be deleted is selected from the candidate deletion push information and the duplicate push information; the push information to be deleted is deleted from the push information cache list to obtain an updated push information cache list, so that when the target application is started, the target push information is displayed on the application start page of the target application through the updated push information cache list.

[0208] As can be seen from the above, in the embodiment of the present application, the arrangement order of the push information to be pushed in the push information cache list can be determined based on the access order of the target application to the push information to be pushed, and the push information to be pushed that is frequently accessed can be preferentially displayed when the target application is started. In order to avoid the influence of too much push information to be pushed in the push information cache list on the startup speed of the target application, when the cache capacity of the push information cache list meets the preset capacity condition, candidate deletion push information that may not be displayed in the push information cache list and duplicate push information can be screened out, and the push information to be deleted is selected from the candidate deletion push information and the duplicate push information, so as to avoid accidentally deleting the candidate deletion push information that the target application may need to display when the cache space of the push information cache list is released. By deleting the push information to be deleted from the push information cache list, the obtained updated push information cache list can release the cache space, ensuring that the push information to be pushed cached in the updated push information cache list is within a reasonable range, so that when the target application is started, the target push information to be displayed can be quickly screened out from the updated push information cache list, which is beneficial to improving the content promotion efficiency and startup speed of the application program when starting, improving the user experience, and reducing the occupation of storage resources.

[0209] The method described in the above embodiment will be further described in detail below.

[0210] In this embodiment, taking the push information to be the boot screen advertisement data as an example, the method of the embodiment of the present application will be described in detail.

[0211] As Figure 2a shown, the specific process of a method for processing boot screen advertisement data is as follows:

[0212] 201. Obtain the cache capacity of the push information cache list corresponding to the target application. The push information cache list caches multiple pieces of boot screen advertisement data to be pushed for the target application. The arrangement order of the boot screen advertisement data to be pushed in the push information cache list is determined based on the access order of the target application to the push information.

[0213] In some embodiments, before obtaining the cache capacity of the push information cache list corresponding to the target application, it further includes:

[0214] As Figure 2b shown, the push service used is the push long connection channel of the manufacturer of the target device docked by the target application. Therefore, when the target device needs to be involved in the docking of the target application (Application, App) to the target device, on the server side, the advertisement server (i.e., the push information server) of the target application needs to dock the push service of the manufacturer (i.e., the device server). Before executing the boot screen advertisement data delivery function, it is necessary to perform the registration work on the boot screen advertisement data:

[0215] 1). Each target application has its own application identifier (Application Identity Document, AppID), profile, certificate, etc. These application information are downloaded in advance on the console of the device server, and these information are sent to the device server through the system programming interface (Application Programming Interface, API) provided by the target device.

[0216] 2). After the target device receives the request for registration pushed by the target application, it sends the application information of the target application to the device server. After receiving the application information of the target application, the device server will issue the target application identifier (token) corresponding to the target application on the target device to the target application after successful authentication according to the console. Using the target application identifier, when the target device receives the data pushed by the push information server subsequently, it can accurately deliver it to the target application corresponding to the target application identifier.

[0217] 3). After receiving the target application identifier, the target application will send it to the corresponding push information server, and the push information server will store the target application identifier and the information of the target application in the target device corresponding to the target application identifier.

[0218] 4) Assemble the startup screen advertisement data at a specific time (for example, when certain advertising activities need to be carried out during the anniversary of the target application), where the startup screen advertisement data carries the target application identifier of the target application, and trigger the push information server to push the assembled startup screen advertisement data to the device server. The assembly of the startup screen advertisement data needs to be docked according to the specifications of the device server. Then, after being processed by the device server, it is transmitted to the target device. This application uses the silent push method, that is, after the target device receives the pushed startup screen advertisement data, it is not displayed in the notification bar. The background of the target device, according to the target application in the target device corresponding to the target application identifier, sends the startup screen advertisement data to the corresponding target application, and the advertisement module of the target application parses and processes the startup screen advertisement data.

[0219] Such as Figure 2c As shown, when the target device receives the startup screen advertisement data to be cached through the push channel, the following technologies are used to process and store the startup screen advertisement data:

[0220] a) Data parsing: First, the target device needs to parse the received startup screen advertisement data to be cached. The startup screen advertisement data to be cached is usually in the data interchange format (JavaScript Object Notation, JSON format), and the native JSON parsing library or a third-party library (such as Gson, Jackson, Moshi, etc.) can be used to parse the JSON data. Among them, Gson, Jackson, etc. are open-source libraries used for converting between Java objects and JSON data. It provides a set of simple and flexible interfaces that can serialize Java objects into JSON-formatted data and deserialize JSON data into Java objects. Moshi is an open-source library used for converting between Java and Kotlin objects and JSON data. Different from other JSON libraries, Moshi uses some new technologies, such as Kotlin coroutines, Kotlin reflection, etc., which gives it great advantages in terms of performance and functionality. After parsing, the target application can obtain various content attributes in the startup screen advertisement data to be cached, such as advertisement content, advertisement validity period (i.e., information valid time), advertisement delivery time period (i.e., information delivery time), advertisement display priority (i.e., display priority), etc. If the type of the startup screen advertisement data to be cached is a video type, the video will be downloaded from the corresponding cloud object storage (Cloud ObjectStorage, COS) service through the video address (videoURL) field.

[0221] b), Data Model: If the cached boot screen advertisement data after parsing has not expired, in order to facilitate data processing and storage, it is necessary to encapsulate the cached boot screen advertisement data after parsing into a data model object (i.e., the push information data structure model). Define an advertisement data model class (i.e., content attributes) using the corresponding coding language, which includes promotion sub-information such as advertisement content, advertisement validity period, advertisement placement time period, etc., and provide corresponding initialization methods and data operation methods.

[0222] c), Data Storage: Based on the content attributes, after encapsulating each promotion sub-information to obtain the push information data structure model, it needs to be stored locally for reading and display when booting. Different storage technologies can be adopted according to the promotion sub-information of different content attributes:

[0223] Shared Preferences: Suitable for storing simple data such as advertisement placement time period. Shared Preferences is a lightweight data storage solution provided by the Android system, which can conveniently store and read basic data types (such as strings, numbers, dates, etc.).

[0224] File Storage: Suitable for storing advertisement content such as pictures and videos. The advertisement content can be downloaded to the local storage directory (such as Internal Storage, External Storage, etc.), and the file path is saved to the push information data structure model. When reading the boot screen advertisement data, the corresponding picture or video resource can be loaded according to the file path.

[0225] Lite Database (SQLite): Suitable for storing structured boot screen advertisement data such as advertisement validity period. It is a lightweight relational database provided by the operating system, which can conveniently store the push information data structure model into the database. When using SQLite, corresponding tables and columns need to be created for the content attributes.

[0226] 202. When the cache capacity meets the preset capacity condition, based on the position of the boot screen advertisement data to be pushed in the push information cache list, determine the boot screen advertisement data to be deleted that meets the preset screening conditions from multiple boot screen advertisement data to be pushed. The boot screen advertisement data to be deleted is the boot screen advertisement data that is not frequently accessed.

[0227] 203. After deleting the boot screen advertisement data to be deleted, perform a duplication detection on the boot screen advertisement data to be pushed except for the boot screen advertisement data to be deleted. If there are duplicate boot screen advertisement data, determine the duplicate boot screen advertisement data to be deleted from the duplicate boot screen advertisement data based on the information validity period of the duplicate boot screen advertisement data.

[0228] 204. Delete the duplicate boot screen advertisement data to be deleted.

[0229] In some embodiments, it further includes:

[0230] As Figure 2d shown, when it is found that some of the locally cached boot screen advertisement data has expired during data storage, the Least Recently Used (LRU) algorithm can be used to clean and process the data. The LRU algorithm is a commonly used cache eviction strategy, and its core idea is to evict the least recently used cache item. The following is the execution process of the LRU algorithm for cleaning:

[0231] Ⅰ). Data structure preparation: To implement the LRU algorithm, a doubly linked list (DoubleLinkedList) (i.e., the push message cache list) and a hash map (HashMap) need to be prepared. The push message cache list is used to store cache items (i.e., the boot screen advertisements to be pushed). Among them, the arrangement order of the boot screen advertisement data to be pushed in the push message cache list is determined based on the access order of the target application to the boot screen advertisement data to be pushed; the hash map is used to store the key (i.e., the content identifier) of the boot screen advertisement data to be pushed and the index position information corresponding to the content identifier. The index position information records the storage node information of the boot screen advertisement data corresponding to the content identifier in the push message cache list.

[0232] Ⅱ). Cache addition: When adding boot screen advertisement data to be cached, first check whether the boot screen advertisement data to be cached already exists in the hash map. If it does not exist, create a new push message storage node and add it to the head of the push message cache list; at the same time, add the content identifier of the boot screen advertisement data to be cached and its corresponding index position information to the hash map. If the size of the hash map exceeds its cache capacity limit, cache eviction is required. Specifically, when it is found that the index position information corresponding to the content identifier in the hash map records at least two storage node information, node data deduplication operations are performed, and only one storage node information corresponding to the content identifier is retained in the push message cache list. The corresponding business scenario is: the pictures or videos of some boot screen advertisement data need to be subject to A / B testing in business, that is, it is the same boot screen advertisement data in the user interface, but the display methods such as copywriting, position, size, etc. are different. Only the key boot screen advertisement data is added once during cache addition.

[0233] Ⅲ) Cache Eviction: When the cache capacity of the push message cache list reaches the upper limit, the least recently used boot screen advertisement data needs to be evicted. According to the LRU algorithm, the least recently used boot screen advertisement data is located at the tail of the push message cache list. Therefore, remove the push message storage node at the tail from the push message cache list and delete it from the hash table. If the boot screen advertisement data stored in the push message storage node at the tail has expired, delete it from the local storage to free up storage space.

[0234] Ⅳ) Cache Access: When a target application starts and needs to access a cached boot screen advertisement data, first look up the corresponding push message storage node in the hash table. According to the content identifier of the boot screen advertisement, if the push message storage node of the boot screen advertisement is found, remove it from the push message cache list and readd it to the head of the push message cache list, indicating that this push message storage node has been recently accessed. If the push message storage node is not found, it means that the boot screen advertisement data has not been cached and needs to be obtained from the local storage or the server side.

[0235] Ⅴ) Cache Update: When it is found that the locally cached boot screen advertisement data has expired, the cache needs to be updated. First, obtain the latest boot screen advertisement data from the local storage or the server side and add it to the push message cache list. Then, remove the expired boot screen advertisement data from the cache.

[0236] 205. After deleting the duplicate boot screen advertisement data to be deleted, obtain the start request for the target application, and determine the target boot screen advertisement data based on the start time corresponding to the start request and the information delivery time of each boot screen advertisement data in the push message recommendation list.

[0237] 206. Based on the target boot screen advertisement data, display the target boot screen advertisement on the application start page of the target application.

[0238] As Figure 2e shown and Figure 2f shown, the process of the target application loading the target boot screen advertisement data when starting:

[0239] ⅰ) Target Device Startup Detection: When the target device starts, the target application needs to detect whether the current time (i.e., the start time) is within the advertisement delivery time period. If it is within the advertisement delivery time period, proceed to the next step of loading the boot screen advertisement data (i.e., the target boot screen advertisement data). If multiple boot screen advertisement data will be displayed during this time period, filter the multiple boot screen advertisement data according to the display priority to obtain the target boot screen advertisement data; if it is not within the delivery time period, skip the display of the boot screen advertisement data.

[0240] ii), Loading advertising resources from the cache: The target application reads the startup screen advertisement data that meets the delivery time period from the local cache (i.e., the push information cache list). To improve the loading speed, the startup screen advertisement data that is most recently and frequently used in the local cache can be preferentially read.

[0241] iii), Displaying the startup screen advertisement: The target application displays the loaded startup screen advertisement data on the startup screen (i.e., the application startup page). The display duration can be set according to the actual requirements of the advertisement content. During the display process, the target application needs to detect the user's operations, such as clicking the skip button, clicking the advertisement, etc., in order to end the display of the startup screen advertisement data at an appropriate time.

[0242] iv), Updating the cache data: After the display of the startup screen advertisement data ends, the target application needs to update the startup screen advertisement data in the local cache. Specifically, it is necessary to increment the usage frequency of the just-displayed startup screen advertisement data in the cache so that the LRU algorithm can correctly manage the cache data.

[0243] Beneficial effects produced by this application:

[0244] 1. Real-time update of advertisement content: Through the push service, the latest startup screen advertisement data can be pushed to the target device in real time, ensuring that the startup screen advertisement data seen by the user when starting the target application is the latest, thereby improving the delivery effect of the startup screen advertisement data and the user experience.

[0245] 2. Efficient cache management: Using the LRU algorithm to manage the cache of the startup screen advertisement data can ensure that the most recently accessed startup screen advertisement data is always retained in the cache, while cleaning up the expired startup screen advertisement data in a timely manner. This not only improves the utilization rate of the cache but also saves the storage space of the target device.

[0246] 3. Reduction of network traffic consumption: Since the startup screen advertisement data is updated in real time through the push service, the user device does not need to pull the startup screen advertisement data from the server side when starting up, thereby reducing the consumption of network traffic.

[0247] 4. Automatic cleaning of expired advertisement resources: Through regular checks and the LRU algorithm, expired startup screen advertisement data (such as pictures, videos, texts, etc.) can be automatically cleaned up to avoid waste of storage space.

[0248] 5. Flexible advertisement delivery strategy: The push service can achieve targeted advertisement delivery according to the characteristics and behaviors of the target device, thereby improving the delivery effect of the startup screen advertisement data and the user experience.

[0249] 6. Reduce server pressure: Since the startup screen advertisement data is updated in real time through the push service, the target device does not need to pull the startup screen advertisement data from the server side when starting up, thus reducing the server pressure.

[0250] 7. Enhance user stickiness: The real-time updated startup screen advertisement data can attract users' attention and improve users' interest and stickiness in the application.

[0251] As can be seen from the above, a method for delivering and cleaning startup screen advertisement data based on the push service is proposed to solve the problem that if the startup screen advertisement data is requested in real time during the startup process, it will affect the startup speed of the target application, and if the cached startup screen advertisement data is used, it will involve the problems of timeliness and waste of storage resources. The push service technology is adopted, and the push channel of the device server issues the startup screen advertisement data and the cleaning command at an appropriate time. The target application receives and parses the startup screen advertisement data, and the LRU algorithm is used to clean and reuse the local startup screen advertisement data.

[0252] To better implement the above method, the embodiment of the present application also provides a processing device for push information. The processing device for push information can be specifically integrated in an electronic device, and the electronic device can be a terminal or other devices. Among them, the terminal can be a mobile phone, a computer, a smart voice interaction device, a smart home appliance, a vehicle-mounted terminal, an aircraft, etc.

[0253] For example, in this embodiment, taking the processing device for push information specifically integrated in a mobile phone as an example, the method of the embodiment of the present application will be described in detail.

[0254] For example, as Figure 3 shown, the processing device for push information may include an acquisition unit 301, a content screening unit 302, a duplicate detection unit 303, a deletion determination unit 304, and a content deletion unit 305, as follows:

[0255] (1). Acquisition unit 301.

[0256] The acquisition unit 301 is used to acquire the cache capacity of the push information cache list corresponding to the target application. The push information cache list caches multiple push messages to be pushed for the target application, and the arrangement order of the push messages to be pushed in the push information cache list is determined based on the access order of the target application to the push messages to be pushed.

[0257] In some embodiments, the acquisition unit includes a first acquisition subunit, a content cache subunit, and a second acquisition subunit:

[0258] The first acquisition subunit is used to acquire the push messages to be cached recommended by the target application and the push information cache list corresponding to the target application;

[0259] A content caching subunit, configured to cache the to-be-cached push information into the push information caching list if the to-be-cached push information is not included in the push information caching list;

[0260] A second obtaining subunit, configured to obtain the caching capacity of the push information caching list corresponding to the target application after the caching of the to-be-cached push information is completed.

[0261] In some embodiments, before the obtaining unit, there further include an authentication subunit, an application identifier obtaining subunit, an application identifier sending subunit, and a content receiving subunit:

[0262] The authentication subunit is configured to send the application information of the target application to the device server corresponding to the target device where the target application is located, so that the device server performs authentication processing on the application information;

[0263] The application identifier obtaining subunit is configured to obtain the target application identifier corresponding to the target application on the target device sent by the device server if the program information authentication is successful;

[0264] The application identifier sending subunit is configured to send the target application identifier to the push information server corresponding to the target application, so that the push information server uses the target application identifier to push the to-be-cached push information for the target application in the target device to the device server;

[0265] The content receiving subunit is configured to receive the to-be-cached push information for the target application sent by the device server based on the target application identifier. I

[0266] In some embodiments, after the content receiving subunit, there further include a content parsing subunit, a content encapsulating subunit, and a content storing subunit:

[0267] The content parsing subunit is configured to perform parsing processing on the to-be-cached push information to obtain promotion sub-information of at least one content attribute in the to-be-cached push information;

[0268] The content encapsulating subunit is configured to perform encapsulation processing on each piece of promotion sub-information based on the content attribute to obtain a push information data structure model;

[0269] The content storing subunit is configured to store the promotion sub-information corresponding to each content attribute encapsulated in the push information data model according to the push information storage policy corresponding to each content attribute.

[0270] (2). Content screening unit 302.

[0271] The content screening unit 302 is configured to, when the cache capacity meets the preset capacity condition, determine candidate push messages to be deleted that meet the preset screening condition from multiple push messages to be pushed based on the positions of the push messages to be pushed in the push message cache list.

[0272] (3). The duplicate detection unit 303.

[0273] The duplicate detection unit 303 is configured to perform duplicate detection on multiple push messages to be pushed to obtain duplicate push messages among the multiple push messages to be pushed.

[0274] In some embodiments, the push message cache list includes multiple push message storage nodes, and the push message storage nodes store push messages to be pushed;

[0275] The duplicate detection unit includes a hash table acquisition subunit and a duplicate determination subunit:

[0276] The hash table acquisition subunit is configured to obtain a hash table corresponding to the push message cache list. The hash table includes content identifiers corresponding to the push messages to be pushed and index position information corresponding to the content identifiers. The index position information records the storage node information of the push messages to be pushed corresponding to the content identifiers in the push message cache list;

[0277] The duplicate determination subunit is configured to, if the index position information corresponding to the content identifier records at least two pieces of storage node information, use the push messages to be pushed respectively stored in the push message storage nodes corresponding to the at least two pieces of storage node information as duplicate push messages.

[0278] (4). The deletion determination unit 304.

[0279] The deletion determination unit 304 is configured to select push messages to be deleted from the candidate push messages to be deleted and the duplicate push messages based on the information validity time of the candidate push messages to be deleted and the information validity time of the duplicate push messages.

[0280] In some embodiments, the deletion determination unit includes a first deletion subunit, a second deletion subunit, and a third deletion subunit:

[0281] The first deletion subunit is configured to, if there are duplicate push messages, determine target duplicate push messages from the duplicate push messages according to the information validity time of each duplicate push message;

[0282] The second deletion subunit is configured to, when the information validity time of the candidate push messages to be deleted does not meet the preset validity condition, use the candidate push messages to be deleted and the target duplicate push messages as push messages to be deleted; when the information validity time of the candidate push messages to be deleted meets the preset validity condition, use the target duplicate push messages as push messages to be deleted;

[0283] The third deletion subunit is configured to use the candidate deletion push message as the to-be-deleted push message if there is no duplicate push message.

[0284] (5). Content deletion unit 305.

[0285] The content deletion unit 305 is configured to delete the to-be-deleted push message from the push message cache list to obtain an updated push message cache list, so as to display the target push message on the application startup page of the target application by using the updated push message cache list when the target application is started.

[0286] In some embodiments, after the content deletion unit, there further include a content identifier acquisition subunit, an index determination subunit, and a position adjustment subunit:

[0287] The content identifier acquisition subunit is configured to acquire a target content identifier corresponding to the target push message;

[0288] The index determination subunit is configured to determine target index position information corresponding to the target content identifier from a hash table;

[0289] The position adjustment subunit is configured to remove the push message storage node corresponding to the target storage node information from the updated push message cache list according to the target storage node information recorded in the target index position information, and add the push message storage node corresponding to the target storage node information to a preset position of the updated push message cache list.

[0290] In some embodiments, there further include an expiration determination subunit, an update acquisition subunit, and a content update subunit:

[0291] The expiration determination subunit is configured to determine expired push messages from multiple to-be-pushed messages according to the information validity time of each to-be-pushed message in the push message cache list;

[0292] The update acquisition subunit is configured to acquire updated push messages of the promotion entity corresponding to the expired push messages;

[0293] The content update subunit is configured to update the expired push messages in the push message cache list by using the updated push messages.

[0294] In some embodiments, after the content deletion unit, there further include a request acquisition subunit, a target promotion determination subunit, and a target promotion display subunit:

[0295] The request acquisition subunit is configured to acquire a startup request for the target application;

[0296] The target promotion determination subunit is configured to determine target push messages based on the startup time corresponding to the startup request and the information delivery time of each to-be-pushed message in the updated push message recommendation list;

[0297] A target promotion display subunit, configured to display target push information on the application startup page of a target application.

[0298] In some embodiments, the target promotion determination subunit is configured to determine at least one candidate push message from the to-be-pushed messages according to the startup time corresponding to the startup request and the information delivery time of each to-be-pushed message in the updated push message recommendation list; and determine the target push message from the at least one candidate push message based on the position of each candidate push message in the updated push message recommendation list.

[0299] In some embodiments, the target promotion determination subunit is configured to obtain the display priority corresponding to the candidate push message; and determine the target push message from the at least one candidate push message according to the display priority corresponding to the candidate push message and the position of each candidate push message in the updated push message recommendation list.

[0300] In specific implementation, each of the above units may be implemented as an independent entity, or may be combined arbitrarily and implemented as the same or several entities. For the specific implementation of each of the above units, reference may be made to the foregoing method embodiments and will not be elaborated herein.

[0301] As can be seen from the above, the processing device for push messages in this embodiment obtains the cache capacity of the push message cache list corresponding to the target application by the obtaining unit. The push message cache list caches multiple to-be-pushed messages for the target application, and the arrangement order of the to-be-pushed messages in the push message cache list is determined based on the access order of the target application to the to-be-pushed messages. When the cache capacity meets the preset capacity condition, the content screening unit determines candidate deleted push messages that meet the preset screening condition from the multiple to-be-pushed messages based on the positions of the to-be-pushed messages in the push message cache list. The duplicate detection unit performs duplicate detection on the multiple to-be-pushed messages to obtain duplicate push messages among the multiple to-be-pushed messages. The deletion determination unit selects the to-be-deleted push messages from the candidate deleted push messages and the duplicate push messages based on the information validity time of the candidate deleted push messages and the information validity time of the duplicate push messages. The content deletion unit deletes the to-be-deleted push messages from the push message cache list to obtain an updated push message cache list, so as to display the target push information on the application startup page of the target application when the target application starts, and reduce the occupation of storage resources.

[0302] Thus, the embodiments of the present application can improve the content promotion efficiency and startup speed of the application program when starting, and improve the user experience.

[0303] The embodiments of the present application further provide an electronic device, which can be a device such as a terminal, a server, etc. Among them, the terminal can be a mobile phone, a tablet computer, a smart Bluetooth device, a laptop computer, a personal computer, etc.; the server can be a single server or a server cluster composed of multiple servers, etc.

[0304] In some embodiments, the processing device for the push information can also be integrated in multiple electronic devices. For example, the processing device for the push information can be integrated in multiple servers, and the processing method for the push information of the present application can be implemented by multiple servers.

[0305] In this embodiment, the electronic device in this embodiment being a mobile phone will be described in detail as an example. For example, as Figure 4 shown, it shows a schematic structural diagram of the mobile phone involved in the embodiments of the present application. Specifically:

[0306] The mobile phone may include components such as a processor 401 with one or more processing cores, a memory 402 with one or more computer-readable storage media, a power supply 403, an input module 404, and a communication module 405. Those skilled in the art can understand that Figure 4 the mobile phone structure shown in does not constitute a limitation on the mobile phone, and it may include more or fewer components than shown, or combine certain components, or have different component arrangements. Among them:

[0307] The processor 401 is the control center of the mobile phone, connecting various parts of the entire mobile phone through various interfaces and lines. By running or executing software programs and / or modules stored in the memory 402, and by calling data stored in the memory 402, it executes various functions of the mobile phone and processes data. In some embodiments, the processor 401 may include one or more processing cores; in some embodiments, the processor 401 may integrate an application processor and a modem processor, where the application processor mainly processes the operating system, user interface, and application programs, etc., and the modem processor mainly processes wireless communication. It can be understood that the above-mentioned modem processor may not be integrated into the processor 401 either.

[0308] The memory 402 can be used to store software programs and modules. The processor 401 executes various functional applications and data processing by running the software programs and modules stored in the memory 402. The memory 402 mainly includes a program storage area and a data storage area. Among them, the program storage area can store an operating system, application programs required for at least one function (such as a sound playback function, an image playback function, etc.); the data storage area can store data created according to the use of the mobile phone, etc. In addition, the memory 402 can include high-speed random access memory and can also include non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices. Correspondingly, the memory 402 can also include a memory controller to provide the processor 401 with access to the memory 402.

[0309] The mobile phone further includes a power supply 403 for powering each component. In some embodiments, the power supply 403 can be logically connected to the processor 401 through a power management system, so as to implement functions such as management of charging, discharging, and power consumption management through the power management system. The power supply 403 can also include any components such as one or more DC or AC power supplies, a recharge system, a power failure detection circuit, a power converter or inverter, and a power status indicator.

[0310] The mobile phone may further include an input module 404, which can be used to receive input digital or character information, and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function controls.

[0311] The mobile phone may further include a communication module 405. In some embodiments, the communication module 405 can include a wireless module. The mobile phone can perform short-distance wireless transmission through the wireless module of the communication module 405, thereby providing users with wireless broadband Internet access. For example, the communication module 405 can be used to help users send and receive emails, browse the web, and access streaming media, etc.

[0312] Although not shown, the mobile phone may further include a display unit, etc., which will not be elaborated here. Specifically, in this embodiment, the processor 401 in the mobile phone will load the executable files corresponding to the processes of one or more application programs into the memory 402 according to the following instructions, and the processor 401 will run the application programs stored in the memory 402, thereby implementing the steps in the methods of the embodiments of the present application.

[0313] For the specific implementation of the above operations, reference can be made to the previous embodiments, which will not be elaborated here.

[0314] As can be seen from the above, ensuring that the to-be-pushed information cached in the update push information cache list is within a reasonable range can enable the target push information to be quickly screened out from the update push information cache list when the target application is started. This is beneficial to improving the content promotion efficiency and startup speed of the application during startup, enhancing the user experience, and reducing the occupation of storage resources.

[0315] Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructions or by controlling relevant hardware through instructions. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0316] Therefore, an embodiment of the present application provides a computer-readable storage medium storing multiple instructions that can be loaded by a processor to execute the steps in any of the push information processing methods provided by the embodiments of the present application. For example, the instructions can execute the following steps:

[0317] Obtain the cache capacity of the push information cache list corresponding to the target application. The push information cache list caches multiple to-be-pushed information for the target application, and the arrangement order of the to-be-pushed information in the push information cache list is determined based on the access order of the target application to the to-be-pushed information;

[0318] When the cache capacity meets the preset capacity condition, based on the position of the to-be-pushed information in the push information cache list, determine candidate deletion push information that meets the preset screening condition from the multiple to-be-pushed information;

[0319] Perform duplicate detection on the multiple to-be-pushed information to obtain duplicate push information among the multiple to-be-pushed information;

[0320] Based on the information validity period of the candidate deletion push information and the information validity period of the duplicate push information, select the to-be-deleted push information from the candidate deletion push information and the duplicate push information;

[0321] Delete the to-be-deleted push information from the push information cache list to obtain an updated push information cache list, so that when the target application is started, the target push information can be displayed on the application startup page of the target application through the updated push information cache list.

[0322] Among them, the storage medium may include: read-only memory (ROM, Read Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disc, etc.

[0323] According to one aspect of the present application, there is provided a computer program product or a computer program, which includes computer programs / instructions stored in a computer-readable storage medium. The processor of the electronic device reads the computer programs / instructions from the computer-readable storage medium, and the processor executes the computer programs / instructions, so that the electronic device executes the methods provided in various alternative implementations of the processing aspect of pushing information provided in the above embodiments.

[0324] Since the instructions stored in this storage medium can execute the steps in any of the processing methods of pushing information provided in the embodiments of the present application, the beneficial effects that can be achieved by any of the processing methods of pushing information provided in the embodiments of the present application can be realized. For details, see the previous embodiments and will not be elaborated here.

[0325] The above has introduced in detail a method, apparatus and storage medium for processing pushed information provided in the embodiments of the present application. Specific examples are used herein to elaborate on the principle and implementation manner of the present application. The description of the above embodiments is only used to help understand the method and its core idea of the present application; at the same time, for those skilled in the art, according to the idea of the present application, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation to the present application.

Claims

1. A method for processing push information, characterized in that, Including: Obtain the cache capacity of the push information cache list corresponding to the target application, where the push information cache list caches multiple push information to be pushed for the target application, and the arrangement order of the push information to be pushed in the push information cache list is determined based on the access order of the target application to the push information to be pushed; When the cache capacity meets the preset capacity condition, based on the position of the push information to be pushed in the push information cache list, determine candidate deleted push information that meets the preset screening condition from the multiple push information to be pushed; Perform a duplication detection on the multiple push information to be pushed to obtain duplicate push information among the multiple push information to be pushed; Based on the information validity time of the candidate deleted push information and the information validity time of the duplicate push information, select the push information to be deleted from the candidate deleted push information and the duplicate push information; Delete the push information to be deleted from the push information cache list to obtain an updated push information cache list, so that when the target application is started, the target push information is displayed on the application start page of the target application through the updated push information cache list.

2. The method for processing push information according to claim 1, wherein The push information cache list includes multiple push information storage nodes, and the push information storage nodes store the push information to be pushed; The performing a duplication detection on the multiple push information to be pushed to obtain duplicate push information among the multiple push information to be pushed includes: Obtain the hash table corresponding to the push information cache list, where the hash table includes the content identifier corresponding to the push information to be pushed and the index position information corresponding to the content identifier, and the index position information records the storage node information of the push information to be pushed corresponding to the content identifier in the push information cache list; If the index position information corresponding to the content identifier records at least two storage node information, then use the push information stored in the push information storage nodes corresponding to the at least two storage node information as duplicate push information.

3. The method for processing push information according to claim 2, wherein, After the deleting the push information to be deleted from the push information cache list to obtain an updated push information cache list, so that when the target application is started, the target push information is displayed on the application start page of the target application through the updated push information cache list, it further includes: Obtain the target content identifier corresponding to the target push information; Determine the target index position information corresponding to the target content identifier from the hash table; According to the target storage node information recorded in the target index position information, remove the push information storage node corresponding to the target storage node information from the updated push information cache list, and add the push information storage node corresponding to the target storage node information to a preset position in the updated push information cache list.

4. The method for processing push information according to claim 1, wherein The based on the information validity time of the candidate deleted push information and the information validity time of the duplicate push information, selecting the push information to be deleted from the candidate deleted push information and the duplicate push information includes: If there is such duplicate push information, determine target duplicate push information from the duplicate push information according to the information validity period of each piece of duplicate push information; When the information validity period of the candidate push information to be deleted does not meet the preset validity condition, use the candidate push information to be deleted and the target duplicate push information as the push information to be deleted; When the information validity period of the candidate push information to be deleted meets the preset validity condition, use the target duplicate push information as the push information to be deleted; If there is no such duplicate push information, use the candidate push information to be deleted as the push information to be deleted.

5. The method for processing push information according to claim 1, wherein, It further includes: Determine expired push information from the multiple pieces of push information to be sent according to the information validity period of each piece of push information in the push information cache list; Obtain updated push information of the promotion entity corresponding to the expired push information; Use the updated push information to update the expired push information in the push information cache list.

6. The method for processing push information according to claim 1, wherein The obtaining the cache capacity of the push information cache list corresponding to the target application includes: Obtain the push information to be cached that needs to be recommended by the target application and the push information cache list corresponding to the target application; If the push information cache list does not include the push information to be cached, cache the push information to be cached in the push information cache list; After the caching of the push information to be cached is completed, obtain the cache capacity of the push information cache list corresponding to the target application.

7. The method for processing push information according to claim 6, wherein Before the obtaining the push information to be cached that needs to be recommended by the target application, it further includes: Send the application information of the target application to the device server corresponding to the target device where the target application is located, so that the device server performs authentication processing on the application information; If the authentication of the program information is successful, obtain the target application identifier corresponding to the target application on the target device sent by the device server; Send the target application identifier to the push information server corresponding to the target application, so that the push information server uses the target application identifier to push the push information to be cached for the target application in the target device to the device server; Based on the target application identifier, receive the push information to be cached for the target application sent by the device server.

8. The method for processing push information according to claim 7, wherein After the receiving, based on the target application identifier, the push information to be cached for the target application sent by the device server, it further includes: Perform parsing processing on the push information to be cached to obtain promotion sub-information of at least one content attribute in the push information to be cached; Based on the content attribute, perform encapsulation processing on each piece of promotion sub-information to obtain a push information data structure model; According to the push information storage policy corresponding to each content attribute, store the promotion sub-information corresponding to each content attribute encapsulated in the push information data model.

9. The method for processing push information according to claim 1, wherein After deleting the to-be-deleted push information from the push information cache list to obtain an updated push information cache list, so as to display target push information on the application startup page of the target application through the updated push information cache list when the target application is started, it further includes: Obtain a startup request for the target application; Based on the startup time corresponding to the startup request and the information delivery time of each to-be-pushed information in the updated push information recommendation list, determine the target push information; Display the target push information on the application startup page of the target application.

10. The method for processing push information according to claim 9, wherein The determining the target push information based on the startup time corresponding to the startup request and the information delivery time of each to-be-pushed information in the updated push information recommendation list includes: According to the startup time corresponding to the startup request and the information delivery time of each to-be-pushed information in the updated push information recommendation list, determine at least one candidate push information from the to-be-pushed information; Based on the position of each candidate push information in the updated push information recommendation list, determine the target push information from the at least one candidate push information.

11. The method for processing push information according to claim 10, wherein The determining the target push information from the at least one candidate push information based on the position of each candidate push information in the updated push information recommendation list includes: Obtain the display priority corresponding to the candidate push information; According to the display priority corresponding to the candidate push information and the position of each candidate push information in the updated push information recommendation list, determine the target push information from the at least one candidate push information.

12. A processing device for pushing information, characterized in that, Includes: An acquisition unit, configured to acquire the cache capacity of the push information cache list corresponding to the target application, where the push information cache list caches multiple to-be-pushed information for the target application, and the arrangement order of the to-be-pushed information in the push information cache list is determined based on the access order of the target application to the to-be-pushed information; A content screening unit, configured to, when the cache capacity meets a preset capacity condition, determine candidate deletion push information that meets the preset screening condition from the multiple to-be-pushed information based on the position of the to-be-pushed information in the push information cache list; A duplicate detection unit, configured to perform duplicate detection on the multiple to-be-pushed information to obtain duplicate push information among the multiple to-be-pushed information; A deletion determination unit, configured to select to-be-deleted push information from the candidate deletion push information and the duplicate push information based on the information validity time of the candidate deletion push information and the information validity time of the duplicate push information; A content deletion unit, configured to delete the to-be-deleted push information from the push information cache list to obtain an updated push information cache list, so as to display target push information on the application startup page of the target application through the updated push information cache list when the target application is started.

13. An electronic device, characterized in that, Includes a processor and a memory, where the memory stores multiple instructions; the processor loads the instructions from the memory to execute the steps in the processing method of the push information according to any one of claims 1 to 11.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores multiple instructions, and the instructions are suitable for being loaded by a processor to execute the steps in the method for processing push information according to any one of claims 1 to 11.

15. A computer program product, comprising a plurality of instructions, characterized in that, When the instructions are executed by the processor, the steps in the method for processing push information according to any one of claims 1 to 11 are implemented.

Images