Push message processing method, device, electronic device and storage medium

Abstract

The present application provides a push message processing method, device, electronic device, and storage medium. The method includes: obtaining a push message to be processed, and determining whether the application APP corresponding to the push message is running; if not, storing the push message in a cache list, so that the APP can obtain and output the push message from the cache list when it is running. In the implementation process of the above solution, by storing the push message in the cache list when it is determined that the APP is not running, so that the APP can obtain and output the push message from the cache list when it is running, the situation where the push message cannot be found again is avoided, and the re-access function of the push message is effectively realized.

Description

Technical Field

[0001] The present application relates to the technical field of message push processing, and more specifically, to a push message processing method, device, electronic device, and storage medium. Background Art

[0002] At present, the application APP on the terminal device (such as the mobile phone or tablet computer with Android operating system) usually receives many push messages (such as the APP notification message in the notification bar of the mobile phone). However, when the APP on the Android operating system is not running (in the foreground or background), the terminal device cannot receive the push message. When the push message is clicked, the corresponding APP is normally opened to display the content interface of the push message. In this process, unexpected situations may occur that make it impossible to display the content interface of the push message. These unexpected situations include: abnormal restart of the APP, APP crash causing the mobile phone to restart, the mobile phone being forced to restart by the user due to long-term unresponsiveness, etc. When the user wants to access the push message again, he cannot find the push message again. Summary of the Invention

[0003] The purpose of the embodiments of the present application is to provide a push message processing method, device, electronic device and storage medium, which are used to improve the problem of being unable to find and access the push message again.

[0004] The embodiment of the present application provides a push message processing method, comprising: obtaining a push message to be processed, and determining whether the application APP corresponding to the push message is running; if not, storing the push message in a cache list, so that the APP can obtain and output the push message from the cache list when it is running. In the implementation process of the above solution, by storing the push message in the cache list when it is determined that the APP is not running, so that the APP can obtain and output the push message from the cache list when it is running, the situation of not being able to find the push message again is avoided, and the push message re-access function is effectively realized.

[0005] Optionally, in an embodiment of the present application, after determining whether the application APP corresponding to the push message is running, the method further includes: if the APP corresponding to the push message is running, outputting the push message. In the implementation process of the above solution, by directly outputting the push message when the APP corresponding to the push message is running, the problem of the APP corresponding to the push message being unable to output the push message is avoided, thereby effectively improving the reach rate of the push message.

[0006] Optionally, in an embodiment of the present application, obtaining a push message to be processed includes: determining a target format based on network signal quality and / or network connection type, and obtaining the push message in the target format. In the implementation of the above solution, by determining the target format based on network signal quality and / or network connection type, and obtaining the push message in the target format, the problem of long reception time caused by poor network signal quality and / or non-preset network connection type is avoided, thereby effectively improving the reach rate of push messages.

[0007] Optionally, in an embodiment of the present application, storing the push message in the cache list includes: determining whether the priority of the push message is the highest priority in the cache list; if so, storing the push message in the cache list. In the implementation process of the above solution, when the priority of the push message is the highest priority in the cache list, the push message is stored in the cache list, the push message is obtained from the cache list, and the push message is output.

[0008] Optionally, in an embodiment of the present application, after determining whether the priority of the push message is the highest priority in the cache list, the method further includes: if the priority of the push message is not the highest priority in the cache list, deleting the message with the smallest storage timestamp value from the cache list, and storing the push message in the cache list. In the implementation of the above scheme, by deleting the message with the smallest storage timestamp value from the cache list and storing the push message in the cache list when the priority of the push message is not the highest priority in the cache list, the problem of the cache list being full and being unable to be stored in the cache list is avoided, thereby effectively improving the reach rate of push messages.

[0009] Optionally, in an embodiment of the present application, the APP obtains and outputs push messages from a cache list during runtime, including: when the APP is pre-loaded during startup, the push message is obtained from the cache list and output. In the implementation of the above solution, by obtaining the push message from the cache list and outputting the push message during the APP startup pre-load phase, the user's waiting time is effectively reduced, the probability of the user clicking on the link corresponding to the push message is increased, and the reach rate of the push message is improved.

[0010] Optionally, in an embodiment of the present application, after the APP obtains and outputs the push message from the cache list at runtime, the process further includes: in response to the opening operation of the push message, searching and accessing the target link corresponding to the push message in the cache list by the APP. In the implementation process of the above solution, by searching and accessing the target link corresponding to the push message in the cache list by the APP in response to the opening operation of the push message, the problem of the highest priority push message not being stored in the cache list is avoided, thereby effectively improving the reach rate of the highest priority push message.

[0011] An embodiment of the present application also provides a push message processing device, including: a push message acquisition module, used to obtain push messages to be processed and determine whether the application APP corresponding to the push message is running; a push message storage module, used to store the push message in a cache list if the application APP corresponding to the push message is not running, so that the APP can obtain and output the push message from the cache list during operation.

[0012] Optionally, in an embodiment of the present application, the push message processing device further includes: a push message output module, configured to output a push message if the APP corresponding to the push message is running.

[0013] Optionally, in an embodiment of the present application, the push message acquisition module includes: a target format determination submodule, configured to determine a target format according to network signal quality and / or network connection type, and acquire the push message in the target format.

[0014] Optionally, in an embodiment of the present application, the push message storage module includes: a priority judgment submodule, used to judge whether the priority of the push message is the highest priority in the cache list; and a push message storage submodule, used to store the push message in the cache list if the priority of the push message is the highest priority in the cache list.

[0015] Optionally, in an embodiment of the present application, the push message processing device further includes: a push message processing module, which is used to delete the message with the smallest storage timestamp value from the cache list if the priority of the push message is not the highest priority in the cache list, and store the push message in the cache list.

[0016] Optionally, in an embodiment of the present application, the push message storage module includes: a push message output submodule, which is used to obtain push messages from the cache list and output push messages when the APP is preloaded during operation.

[0017] Optionally, in an embodiment of the present application, the push message processing device further includes: a target link access module, which is used to search and access the target link corresponding to the push message in the cache list through the APP in response to the opening operation of the push message.

[0018] An embodiment of the present application further provides an electronic device, including: a processor and a memory, wherein the memory stores machine-readable instructions executable by the processor, and when the machine-readable instructions are executed by the processor, the method described above is performed.

[0019] An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the method described above is executed.

[0020] Other features and advantages of the embodiments of the present application will be described in the subsequent description, and in part will become apparent from the description, or may be understood by practicing the embodiments of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. It should be understood that the following drawings only illustrate certain embodiments of the embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without creative work.

[0022] Figure 1 A schematic diagram showing a flow chart of a push message processing method provided in an embodiment of the present application is shown;

[0023] Figure 2 A schematic diagram showing a push message on a mobile phone provided in an embodiment of the present application is shown;

[0024] Figure 3 A schematic diagram of a cache list provided in an embodiment of the present application is shown;

[0025] Figure 4 A schematic diagram of the structure of a push message processing device provided in an embodiment of the present application is shown;

[0026] Figure 5 A schematic structural diagram of an electronic device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0027] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments in the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the embodiments of the present application for protection, but merely represents selected embodiments in the embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work are within the scope of protection of the embodiments of the present application.

[0028] It is understood that the terms "first" and "second" in the embodiments of the present application are used to distinguish similar objects. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or order of execution, and that the terms "first" and "second" do not necessarily define differences.

[0029] It should be noted that the push message processing method provided in the embodiment of the present application can be executed by an electronic device, where the electronic device refers to a terminal device with the function of executing a computer program. The terminal device here includes but is not limited to: a smart phone (such as a phone with Apple MAC operating system or a phone with Android operating system), a personal computer, a tablet computer, a personal digital assistant or a mobile Internet device, etc.

[0030] The following describes application scenarios for this push message processing method, including but not limited to: enhancing mobile operating system functionality or improving push server message push services. For example, if an app push message in the notification bar of a mobile phone or tablet is clicked but cannot be found and clicked again, this push message processing method can be used to store the push message in a cache list. This allows the app to retrieve and output the push message from the cache list during runtime, avoiding the situation where the push message cannot be found again and effectively enabling push message re-accessibility.

[0031] See Figure 1 The following is a flow chart of a push message processing method provided by an embodiment of the present application; the implementation of the push message processing method may include:

[0032] Step S110: Obtain the push message to be processed, and determine whether the application APP corresponding to the push message is running.

[0033] See Figure 2A schematic diagram of a push message on a mobile phone provided by an embodiment of the present application is shown; the push message to be processed can be a push message received on a mobile phone, a tablet computer, a personal computer, etc. Therefore, the recipient of the push message should not be construed as limiting the embodiments of the present application. Here, a push message received on a mobile phone is used as an example. The push message can include a recommendation for mineral water, a new email, or a new album of songs, etc.

[0034] Step S120: If the application APP corresponding to the push message is not running, the push message is stored in a cache list, so that the APP can obtain and output the push message from the cache list when running.

[0035] See Figure 3 The schematic diagram of the cache list provided in the embodiment of the present application is shown; the cache list refers to a data structure provided on an electronic device for storing push messages, and specifically a cache list in an in-memory database such as Memcached and Redis can be used. The cache list stores multiple push messages, and these multiple push messages can be sorted according to the time when the user clicks the push message. Each push message can include multiple fields, such as an identification ID, message content, message link, and timestamp, etc. The identification ID is used to identify each push message, the message content is the specific content of the push message, the message link is the link accessed after the push message is clicked, and the timestamp can be the timestamp when the user calls up the APP after clicking the push message. The number of push messages stored in the cache list can also be set according to the specific situation, for example, to 5, 10, or 20, etc.

[0036] It is understandable that when the application APP on a mobile phone or tablet computer with an Android operating system is not running (in the foreground or background), the mobile phone or tablet computer cannot receive and display push messages. In this case, the push message can be stored in a cache list so that the APP can obtain and output the push message from the cache list when it is running (in the foreground or background), thereby increasing the usage frequency of the APP and the reach of the push message. Alternatively, when the application APP on a mobile phone or tablet computer with an Apple operating system receives a push message, an unexpected situation occurs during the user's click, resulting in the inability to display the content interface of the push message. These unexpected situations include: abnormal restart of the APP, APP crash causing the phone to restart, long-term unresponsiveness of the phone causing it to be forced to restart by the user, etc. At this time, the push message can be stored in a cache list so that the APP can obtain and output the push message from the cache list when it is running (in the foreground or background), thereby increasing the usage frequency of the APP and the reach of the push message.

[0037] In the above implementation process, by storing the push message in the cache list when it is determined that the APP is not running, the APP can obtain and output the push message from the cache list when it is running, avoiding the situation where the push message cannot be found again, and effectively realizing the re-access function of the push message.

[0038] As an optional implementation of the above push message processing method, after determining whether the application APP corresponding to the push message is running, it also includes:

[0039] Step S130: If the APP corresponding to the push message is running, the push message is output.

[0040] For example, the implementation of the above step S130 is as follows: the operating system of the electronic device can monitor whether the APP corresponding to the push message is running. If the APP corresponding to the push message is running, the push message can be directly output through the running APP.

[0041] As a first optional implementation of the above step S110, obtaining the push message to be processed according to the network status between the electronic device and the server may include:

[0042] Step S111: determining a target format according to network signal quality and / or network connection type, and obtaining a push message in the target format.

[0043] There are many ways to obtain the push message in step S111 above, including but not limited to the following three:

[0044] The first acquisition method is to determine the target format based on the network signal quality and obtain the push message in the target format. A specific example of this acquisition method is that the server can communicate with the electronic device (such as a mobile phone) in advance to obtain the network signal quality of the location of the electronic device. The network signal quality indicators here include but are not limited to: Signal to Interference plus Noise Ratio (SINR), Received Signal Strength Indication (RSSI), Reference Signal Receiving Power (RSRP) and / or Reference Signal Receiving Quality (RSRQ). Of course, the network signal quality here can also be determined based on the weight of each indicator. For example, the network signal quality of the electronic device is calculated using the formula SQ=w1×SINR+w2×RSSI+w3×RSRP+w4×RSRQ; wherein SQ represents the network signal quality of the electronic device, SINR represents the signal to interference plus noise ratio, w1 represents the weight of the signal to interference plus noise ratio, RSSI represents the received signal strength indication, w2 represents the weight of the received signal strength indication, RSRP represents the reference signal received power, w3 represents the weight of the reference signal received power, RSRQ represents the reference signal received quality, and w4 represents the weight of the reference signal received quality.

[0045] After obtaining the network signal quality of the electronic device, the server determines whether the network signal quality of the electronic device is greater than a preset threshold; if the network signal quality is greater than the preset threshold, the server sends a push message in audio format, picture format, or video format to the electronic device; if the network signal quality is less than or equal to the preset threshold, the server sends a push message in text format to the electronic device. The electronic device determines whether its own network signal quality is greater than a preset threshold; if the network signal quality is greater than the preset threshold, the electronic device (such as a mobile phone) receives the push message in audio format, picture format, or video format sent by the server; if the network signal quality is less than or equal to the preset threshold, the electronic device (such as a mobile phone) receives the push message in text format sent by the server.

[0046] The second acquisition method is to determine the target format according to the network connection type, and obtain the push message in the target format. A specific example of this acquisition method is: the server can communicate with the electronic device (such as a mobile phone) in advance to obtain the network connection type of the electronic device. After obtaining the network signal quality of the electronic device, the server determines whether the network connection type of the electronic device is a preset type (such as using WIFI connection); if the network connection type of the electronic device is a preset type (such as using WIFI connection), the server sends a push message in audio format, picture format or video format to the electronic device; if the network connection type of the electronic device is not a preset type (such as using WIFI connection), the server sends a push message in text format to the electronic device. The electronic device determines whether its own network connection type is a preset type (such as using WIFI connection); if the network connection type of the electronic device is a preset type (such as using WIFI connection), the electronic device (such as a mobile phone) receives the push message in audio format, picture format or video format sent by the server; if the network connection type of the electronic device is not a preset type (such as using WIFI connection), the electronic device (such as a mobile phone) receives the push message in text format sent by the server.

[0047] The third acquisition method is to determine the target format based on the network signal quality and the network connection type, and obtain the push message in the target format. This acquisition method is specifically for example: if the network connection type of the electronic device is not a preset type (for example, using WIFI connection), and the network signal quality is less than or equal to a preset threshold, then the electronic device (for example, a mobile phone) receives the push message in text format sent by the server; if the network connection type of the electronic device is a preset type (for example, using WIFI connection), or the network signal quality is greater than the preset threshold, then the electronic device (for example, a mobile phone) receives the push message in audio format, picture format or video format sent by the server.

[0048] As a second optional implementation of the above step S110, obtaining the push message to be processed based on the usage of the electronic device (for example, unlocked state and current time, etc.) may include:

[0049] Step S112: Obtain push messages to be processed according to the unlocking state of the electronic device.

[0050] The implementation of the above step S112 is, for example: determining whether the electronic device has been unlocked; if the electronic device has not been unlocked, obtaining and outputting the total number of push messages; if the electronic device has been unlocked, obtaining and outputting the specific content of the push message.

[0051] Step S113: Obtain the push message to be processed according to the current time of the electronic device.

[0052] An example of an implementation of the above step S113 is: determining whether the current time of the electronic device is within a preset time range (e.g., 3 p.m. to 4 p.m.); if the current time of the electronic device is within the preset time range (e.g., 3 p.m. to 4 p.m.), directly obtaining and outputting the specific content of the push message, because 3 p.m. to 4 p.m. is a time range frequently used by the user corresponding to the electronic device, and therefore the specific content of the push message can be directly output. Conversely, if the current time of the electronic device is within the preset time range (e.g., 3 p.m. to 4 p.m.), directly obtaining the push message and storing the push message in a cache list, because 3 p.m. to 4 p.m. is the time range least frequently used by the user corresponding to the electronic device, and therefore the push message can be directly stored in a cache list.

[0053] As an optional implementation of the above step S120, the implementation of storing the push message in the cache list may include:

[0054] Step S121: Determine whether the priority of the push message is the highest priority in the cache list.

[0055] An implementation method of the above-mentioned step S121 is, for example: using an executable program compiled or interpreted using a preset programming language to determine whether the priority of the push message is the highest priority in the cache list. The programming languages ​​that can be used are, for example: C, C++, Java, BASIC, JavaScript, LISP, Shell, Perl, Ruby, Python and PHP, etc.

[0056] Step S122: If the priority of the push message is the highest priority in the cache list, the push message is stored in the cache list, so that the APP obtains and outputs the push message from the cache list when running.

[0057] An example of an implementation method of the above-mentioned step S122 is: assuming that the priority of the push message is sorted in descending order of A, B, C, etc., if the priority of the push message is A, then the priority of the push message is the highest priority in the cache list, and the push message is stored in the cache list of memory databases such as Memcached and Redis, so that the APP can obtain and output the push message from the cache list of memory databases such as Memcached and Redis during runtime.

[0058] As an optional implementation of the above step S120, after determining whether the priority of the push message is the highest priority in the cache list, the following steps are further included:

[0059] Step S123: If the priority of the push message is not the highest priority in the cache list, the message with the smallest storage timestamp value is deleted from the cache list, and the push message is stored in the cache list.

[0060] For example, the implementation method of the above-mentioned step S123 is: assuming that the priority of the push message is sorted in descending order of A, B, C, etc., if the priority of the push message is B, then the priority B of the push message is not the highest priority A in the cache list, then the message with the smallest storage timestamp value will be deleted from the cache list of the memory database such as Memcached and Redis, and the push message will be stored in the cache list of the memory database such as Memcached and Redis.

[0061] As an optional implementation of step S120 above, the implementation of obtaining and outputting push messages from the cache list during the APP runtime may include:

[0062] Step S124: When the APP starts preloading during operation, the push message is obtained from the cache list and the push message is output.

[0063] An example of an implementation of the above step S124 is as follows: when the APP is pre-loaded during startup, push messages are obtained from the cache list, and these push messages are sorted in descending order of the push time of the push messages to obtain the sorted push messages; finally, the sorted push messages are output and displayed. It is understandable that since the APP needs to go through the pre-loading, initialization, pre-heating, screen opening waiting and advertising countdown stages from startup to operation before it can enter the normal operation stage, the above implementation method obtains the push message from the cache list and outputs the push message during the APP startup pre-loading stage, thereby effectively reducing the user's waiting time and increasing the probability of the user clicking on the link corresponding to the push message, thereby increasing the reach rate of the push message.

[0064] As an optional implementation of the above step S120, after the APP obtains and outputs the push message from the cache list during operation, the following steps may also be included:

[0065] Step S125: In response to the opening operation of the push message, the APP searches for and accesses the target link corresponding to the push message in the cache list.

[0066] For example, in the implementation of step S125, in response to the opening operation of the push message, the electronic device searches and accesses the target link corresponding to the push message in the cache list of a memory database such as Memcached and Redis through the APP, and obtains the data content corresponding to the target link from the server. The data content here can be, for example, a static web page in Hypertext Markup Language (HTML) 5. It is understandable that the data content accessed by the target link corresponding to the push message is prepared in advance by the server, for example: using a content delivery network (CDN) or an object storage service (OBS) to store the data content corresponding to the target link in advance. Then, after the target link corresponding to the push message on the electronic device is clicked, the electronic device can directly obtain the data content corresponding to the target link (e.g., a static HTML5 web page) from the CDN or OBS. Alternatively, the server can also use a memory database such as Memcached and Redis to store the HTML5 static web page in advance, and the electronic device can obtain the HTML5 static web page from the server's memory database such as Memcached and Redis.

[0067] As an optional implementation of the above step S120, when the number of push messages stored in the cache list reaches the storage upper limit threshold, the push message with the earliest timestamp is deleted. This implementation may include:

[0068] Step S126: Before storing the push message in the cache list, determine whether the number of push messages stored in the cache list is greater than or equal to the storage upper limit threshold.

[0069] For example, in step S126, before storing the push message in the cache list, an executable program compiled or interpreted in a preset programming language is used to determine whether the number of push messages stored in the cache list exceeds an upper storage threshold. Examples of acceptable programming languages ​​include C, C++, Java, BASIC, JavaScript, LISP, Shell, Perl, Ruby, Python, and PHP.

[0070] Step S127: If the number of push messages stored in the cache list is greater than or equal to the storage upper limit threshold, the message with the smallest storage timestamp value is deleted from the cache list.

[0071] For example, the implementation method of the above step S127 is: assuming that the storage upper limit threshold is 20, and the number of push messages stored in the cache list is 20, then it can be determined that the number of push messages stored in the cache list is equal to the storage upper limit threshold, and therefore, the message with the smallest storage timestamp value can be deleted from the cache list.

[0072] See Figure 4 FIG2 shows a schematic diagram of the structure of a push message processing device provided in an embodiment of the present application. The embodiment of the present application provides a push message processing device 200, including:

[0073] The push message acquisition module 210 is used to acquire the push message to be processed and determine whether the application APP corresponding to the push message is running.

[0074] The push message storage module 220 is configured to store the push message in a cache list if the application APP corresponding to the push message is not running, so that the APP can obtain and output the push message from the cache list when running.

[0075] Optionally, in the embodiment of the present application, the push message processing device further includes:

[0076] The push message output module is used to output the push message if the APP corresponding to the push message is running.

[0077] Optionally, in an embodiment of the present application, the push message acquisition module includes:

[0078] The target format determination submodule is used to determine the target format according to the network signal quality and / or the network connection type, and obtain the push message in the target format.

[0079] Optionally, in an embodiment of the present application, the push message storage module includes:

[0080] The priority judgment submodule is used to judge whether the priority of the push message is the highest priority in the cache list.

[0081] The push message storage submodule is used to store the push message in the cache list if the priority of the push message is the highest priority in the cache list.

[0082] Optionally, in the embodiment of the present application, the push message processing device further includes:

[0083] The push message processing module is used to delete the message with the smallest storage timestamp value from the cache list if the priority of the push message is not the highest priority in the cache list, and store the push message in the cache list.

[0084] Optionally, in an embodiment of the present application, the push message storage module includes:

[0085] The push message output submodule is used to obtain push messages from the cache list and output push messages when the APP is preloaded during startup.

[0086] Optionally, in the embodiment of the present application, the push message processing device further includes:

[0087] The target link access module is used to search and access the target link corresponding to the push message in the cache list through the APP in response to the opening operation of the push message.

[0088] It should be understood that the device corresponds to the above-mentioned push message processing method embodiment and can perform each step involved in the above-mentioned method embodiment. The specific functions of the device can be found in the description above. To avoid repetition, the detailed description is appropriately omitted here. The device includes at least one software function module that can be stored in the memory in the form of software or firmware or fixed in the operating system (OS) of the device.

[0089] See Figure 5 The electronic device 300 provided in the embodiment of the present application includes a processor 310 and a memory 320, wherein the memory 320 stores machine-readable instructions executable by the processor 310, and when the machine-readable instructions are executed by the processor 310, the method described above is performed.

[0090] The embodiment of the present application further provides a computer-readable storage medium 330 , on which a computer program is stored. When the computer program is run by the processor 310 , the above method is executed.

[0091] Among them, the computer-readable storage medium 330 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, disk or optical disk.

[0092] It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Similarities between the various embodiments can be referred to in conjunction with each other. For device embodiments, since they are generally similar to method embodiments, their description is relatively simple, and for relevant details, reference can be made to the description of the method embodiments.

[0093] In the several embodiments provided in the embodiments of the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are only schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible implementation architectures, functions and operations of the devices, methods and computer program products according to the multiple embodiments of the embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and a module, a program segment or a part of a code contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also be different from the order of occurrence marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, which is mainly based on the functions involved.

[0094] In addition, the functional modules of each embodiment in the embodiments of the present application can be integrated together to form an independent part, or each module can exist separately, or two or more modules can be integrated to form an independent part. In addition, in the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the embodiments of the present application. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in an appropriate manner in any one or more embodiments or examples. In addition, those skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradicting each other.

[0095] The above description is only an optional implementation method of the embodiment of the present application, but the protection scope of the embodiment of the present application is not limited to this. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed in the embodiment of the present application, and they should all be covered by the protection scope of the embodiment of the present application.

Claims

1. A push message processing method, characterized in that: Applied to a terminal device, when the application APP on the terminal device receives a push message to be processed, it cannot display the content interface of the push message to be processed during the click process; The push message processing method includes: Obtain the push message to be processed, and determine whether the application APP corresponding to the push message is running; If not, the push message is stored in a cache list, so that the APP obtains and outputs the push message from the cache list when the APP starts preloading; The acquiring of the push message to be processed includes: acquiring the push message to be processed according to an unlock state of the terminal device, or determining a target format according to a network signal quality and / or a network connection type between the terminal device and a server, and acquiring the push message to be processed from the server in the target format; After the APP obtains and outputs the push message from the cache list when starting preloading during operation, it also includes: in response to the opening operation of the push message, searching and accessing the target link corresponding to the push message in the cache list through the APP, and obtaining the data content corresponding to the target link from the memory database of the server.

2. The method according to claim 1, characterized in that After determining whether the application APP corresponding to the push message is running, the method further includes: If the APP corresponding to the push message is running, the push message is output.

3. The method according to claim 1, characterized in that The storing the push message in the cache list includes: Determine whether the priority of the push message is the highest priority in the cache list; If so, the push message is stored in the cache list.

4. The method according to claim 1, wherein After determining whether the priority of the push message is the highest priority in the cache list, the method further includes: If the priority of the push message is not the highest priority in the cache list, the message with the smallest storage timestamp value is deleted from the cache list, and the push message is stored in the cache list.

5. A push message processing device, characterized in that: Applied to a terminal device, when the application APP on the terminal device receives a push message to be processed, it cannot display the content interface of the push message to be processed during the click process; The push message processing device includes: A push message acquisition module is used to obtain the push message to be processed and determine whether the application APP corresponding to the push message is running; A push message storage module is used to store the push message in a cache list if the application APP corresponding to the push message is not running, so that the APP can obtain and output the push message from the cache list when starting preloading; The acquiring of the push message to be processed includes: acquiring the push message to be processed according to an unlock state of the terminal device, or determining a target format according to a network signal quality and / or a network connection type between the terminal device and a server, and acquiring the push message to be processed from the server in the target format; After the APP obtains and outputs the push message from the cache list when starting preloading during operation, it also includes: in response to the opening operation of the push message, searching and accessing the target link corresponding to the push message in the cache list through the APP, and obtaining the data content corresponding to the target link from the memory database of the server.

6. An electronic device, characterized in that: include: A processor and a memory, wherein the memory stores machine-readable instructions executable by the processor, and when the machine-readable instructions are executed by the processor, the method according to any one of claims 1 to 4 is performed.

7. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 4 is executed.

Images