Application message push method, electronic device and storage medium
By carrying the target identifier in the target queue message sent by the message queue server and feedback response information from the message push server to the message queue server, the problem of repeated sending of application messages is solved and the user experience is improved.
Patent Information
- Application Number
- CN202111640438.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-12-29
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2041-12-29
AI Technical Summary
In the prior art, application messages are repeatedly sent to the user in a short time, resulting in frequent disturbances from the user and affecting the reading experience.
When the target queue message sent by the message queue server carries the target identifier, the message push server feedbacks the response information to the message queue server to confirm the message reception and avoid repeated sending of messages in a short time.
It effectively avoids the message push server repeatedly sending the same target application messages in a short time, improving the user's reading experience.
Smart Images

Figure CN114338792B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of computer technology, and in particular to a method for pushing application messages, an electronic device, and a storage medium. Background Art
[0002] Currently, when users use the application client, the application platform will push application messages to the user's application client based on operational needs. For example, when a book updates a new chapter, it is necessary to send a book update push message to the book's follow-up users, and when a large-scale promotion is carried out, it is necessary to send a discount push message to users.
[0003] However, sometimes the same application message may be repeatedly sent to the user within a short period of time, resulting in frequent interruptions to the user and seriously affecting the user's reading experience. Summary of the invention
[0004] In order to solve the above technical problem or at least partially solve the above technical problem, the present disclosure provides a method for pushing an application message, an electronic device and a storage medium.
[0005] In a first aspect, the present disclosure provides a method for pushing an application message, comprising:
[0006] Receive the target queue message sent by the message queue server;
[0007] In the case where the target queue message carries a target identifier, in response to the target identifier, response information for the target queue message is fed back to the message queue server; wherein the response information is used to enable the message queue server to confirm that the message push server has received the target queue message;
[0008] Push a target application message to a target user device corresponding to the target queue message; wherein the target application message is generated based on the message content in the target queue message.
[0009] In a second aspect, the present disclosure provides an electronic device, including a processor and a memory, wherein the memory is used to store executable instructions, and the executable instructions enable the processor to perform the following operations:
[0010] Receive the target queue message sent by the message queue server;
[0011] In the case where the target queue message carries a target identifier, in response to the target identifier, response information for the target queue message is fed back to the message queue server; wherein the response information is used to enable the message queue server to confirm that the message push server has received the target queue message;
[0012] Push a target application message to a target user device corresponding to the target queue message; wherein the target application message is generated based on the message content in the target queue message.
[0013] In a third aspect, the present disclosure provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, the processor implements the method for pushing application messages of the first aspect.
[0014] Compared with the prior art, the technical solution provided by the embodiments of the present disclosure has the following advantages:
[0015] The push method, electronic device and storage medium of the application message of the embodiment of the present disclosure can receive the target queue message sent by the message queue server, and in the case where the target queue message carries the target identifier, in response to the target identifier, feedback the response information for the target queue message to the message queue server, wherein the response information is used to make the message queue server confirm that the message push server has received the target queue message, and push the target application message to the target user device corresponding to the target queue message; wherein the target application message is generated based on the message content in the target queue message. It can be seen that when the target queue message includes the target identifier, the message push server can feedback the response information to the message queue server to inform the message queue server that the message push server has received the target queue message, thereby avoiding the message queue server from repeatedly sending the target queue message in a short time due to not receiving a response, thus avoiding frequent interruptions to the user and improving the user's reading experience. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the originals and elements are not necessarily drawn to scale.
[0017] Figure 1 A schematic diagram showing a flow chart of a method for pushing an application message provided by an embodiment of the present disclosure;
[0018] Figure 2 A schematic diagram showing a process flow of pushing an application message provided by an embodiment of the present disclosure;
[0019] Figure 3 A schematic structural diagram of an electronic device provided by an embodiment of the present disclosure is shown. DETAILED DESCRIPTION
[0020] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.
[0021] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.
[0022] The term "including" and its variations used herein are open inclusions, i.e., "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description.
[0023] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.
[0024] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".
[0025] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.
[0026] The embodiments of the present disclosure provide a method, electronic device, and storage medium for pushing application messages, which can avoid frequent interruptions to users and improve the user's reading experience.
[0027] Let's first combine Figure 1-2 The method for pushing application messages provided by an embodiment of the present disclosure is described.
[0028] The method for pushing application messages provided in the embodiments of the present disclosure may be executed by an electronic device with a message push function, wherein the electronic device may include but is not limited to mobile terminals such as smart phones, laptop computers, personal digital assistants (PDAs), tablet computers (PADs), portable multimedia players (PMPs), vehicle terminals (such as vehicle navigation terminals), wearable devices, etc., and fixed terminals such as digital TVs, desktop computers, smart home devices, etc.
[0029] Figure 1 A flow chart of a method for pushing an application message provided by an embodiment of the present disclosure is shown.
[0030] like Figure 1 As shown, the method for pushing application messages may include the following steps.
[0031] S110: Receive a target queue message sent by a message queue server.
[0032] In the embodiment of the present disclosure, the electronic device with the message push function may be, for example, a message push server, which may receive a target queue message sent by a message queue server.
[0033] In the embodiments of the present disclosure, the message queue server may be an electronic device having the function of transferring target queue messages. Specifically, the message queue server may receive the target queue messages generated by the message generation server, and forward the target queue messages to the message push server. The message queue server may include but is not limited to mobile terminals such as smart phones, laptops, PDAs, PADs, PMPs, vehicle-mounted terminals (such as vehicle-mounted navigation terminals), wearable devices, etc., as well as fixed terminals such as digital TVs, desktop computers, smart home devices, etc.
[0034] In the embodiment of the present disclosure, the target queue message may be any queue message that needs to be pushed to the target user equipment.
[0035] In some embodiments, the target queue message may include message content. The message push server may generate a target application message according to the message content.
[0036] Exemplarily, the message content of the target queue message may include book information, such as at least one of the book title, book introduction, author, publishing information, updated chapter information, etc. At this time, the target application message may include a book update prompt message, such as "Book Title has been updated, come and have a look." However, it is not limited to this.
[0037] Exemplarily, the message content of the target queue message may include promotion information, such as at least one of the promotion name and promotion time. At this time, the target application message may include a promotion reminder message, such as "XX promotion, welcome to order", but is not limited thereto.
[0038] Exemplarily, the message content of the target queue message may include red envelope information, such as at least one of the red envelope amount and the source of the red envelope, etc. At this time, the target application message may include a red envelope message, such as "XX sends you a red envelope, please check it", but it is not limited thereto.
[0039] In other embodiments, the target queue message may include message content and a target account, wherein the target account may be any account corresponding to the target application message generated based on the message content, that is, the target application message may be pushed to at least one user device under the target account.
[0040] S120: When the target queue message carries a target identifier, in response to the target identifier, feedback response information for the target queue message to the message queue server.
[0041] The response message is used to enable the message queue server to confirm that the message push server has received the target queue message.
[0042] In an embodiment of the present disclosure, after receiving a target queue message, the message queue server can detect whether the target queue message carries a target identifier. If it is detected that the target queue message carries a target identifier, the message queue server can feedback response information for the target queue message to the message queue server in response to the target identifier, so that the message queue server confirms that the message push server has received the target queue message.
[0043] In the embodiment of the present disclosure, the target identifier may be any identifier that can indicate that the message push server needs to immediately feed back a response message.
[0044] In some embodiments, the target queue message may include a first target field, which is used to indicate whether the target queue message requires the message push server to feedback a response message. For example, if the field value of the first target field is 1, it indicates that the target queue message requires the message push server to feedback a response message, that is, the field value 1 in the first target field is the target identifier.
[0045] In other embodiments, the target queue message may include a first type identifier for indicating a type, and the first type identifier is used to indicate whether the target queue message requires a message push server to feedback a response message. For example, when the type corresponding to the first type identifier is a preset type, it indicates that the target application message corresponding to the target queue message needs to be pushed to a large number of target accounts, and the target queue message requires a message push server to feedback a response message; wherein the preset type may include a tree root type, etc., but is not limited thereto.
[0046] In the embodiment of the present disclosure, the response message may be any message that enables the message queue server to confirm that the message push server has received the target queue message.
[0047] In some embodiments, the response message may include an acknowledgement character ACK (Acknowledge character), where ACK is used to indicate that the sent data has been confirmed to be received correctly.
[0048] In the embodiment of the present disclosure, the target identifier in the target queue message can be configured by the message generating server when generating the target queue message, or can be added by the message queue server after receiving the target queue message, and the embodiment of the present disclosure is not limited to this.
[0049] Optionally, the target queue message corresponding to a large number of target accounts may carry a target identifier. The specific definition of "a large number of target accounts" can be set by those skilled in the art according to actual conditions and is not limited here. For example, when the number of target accounts corresponding to the target queue message is greater than a preset number, the target identifier is carried in the target queue message. However, this is not limited to this.
[0050] For example, usually a large number of reading users will follow a certain book at the same time, so the target queue message including the book information can carry the target identifier. For another example, the application platform's preferential activities are usually carried out for a large number of new users and / or old users, so the target queue message including the preferential activity information can carry the target identifier. For another example, in order to promote user consumption, the application platform usually distributes red envelopes to a large number of new users and / or old users, so the target queue message including the red envelope message can also carry the target identifier. But it is not limited to this.
[0051] It is understandable that in the prior art, after the message queue server sends the target queue message to the message push server, if no message is received within 30S, the target queue message is sent to the message push server again. However, when the number of target accounts corresponding to the target queue message is huge, it is difficult for the message push server to complete the push of the target application message generated based on the message content of the target queue message within 30S, that is, it is difficult to feedback the push completion notification to the message queue server within 30S, resulting in the message queue server repeatedly sending the target queue message in a short time, and then causing the message push server to repeatedly push the same target application message to the target user device for the same target queue message, frequently disturbing the user. However, in the disclosed embodiment, the message push server can immediately feedback the response message to the message queue server after receiving the target queue message, so that the message queue server can confirm that the message push server has received the target queue message, and the subsequent message push server can push the target application message generated based on the message content of the target queue message to the target user device, then the message queue server will not repeatedly send the target queue message again in a short time, thereby avoiding the message push device from repeatedly pushing the same target application message in a short time.
[0052] S130: Push a target application message to a target user equipment corresponding to the target queue message.
[0053] The target application message is generated based on the message content in the target queue message.
[0054] In the disclosed embodiment, after receiving the target queue message, the message push service may generate a target application message according to the message content in the target queue message, and push the target queue message to the target user device corresponding to the target message.
[0055] In the embodiment of the present disclosure, the target user equipment may be a user equipment of a target account corresponding to any target queue message.
[0056] For example, when the target queue message content is book information and the target application message is a book update reminder message, the target user device can be any user device under any target account that updates the book. For another example, when the target queue message content is promotional event information and the target application message is a promotional event reminder message, the target user device can be any user device under any target account that has the right to participate in the promotional event. For another example, when the target queue message content is red envelope information and the target application message is a red envelope message, the target user device can be any user device under any target account that has the right to receive the red envelope.
[0057] In some embodiments, if the target queue message includes a target account corresponding to the target queue message, the message push server can determine the target account corresponding to the target queue message based on the target queue message itself.
[0058] In other embodiments, the message push server may determine whether each account is a target account based on the account information of each account.
[0059] For example, account information may include historically read books. When the target application message is a book update reminder message, for each account, the message push server can determine whether the reading user of the account is following the book corresponding to the book update reminder message based on the historically read books of the account, and if so, determine that the account is the target account.
[0060] For another example, the account information may include the account creation time and / or the account level. When the target application message is a reminder message or a red envelope message of a promotional activity, for each account, the message push server may determine whether the account is entitled to participate in the promotional activity based on the account creation time and / or the account level of the account, and if so, determine that the account is the target account.
[0061] For another example, when the target application message is a reminder message or a red envelope message for a promotion, for each account, the message push server can determine whether the account meets the screening conditions for receiving red envelopes based on the account creation time and / or account level of the account. If so, the account is determined to be the target account.
[0062] In some embodiments, for each target account, the message push server may use one user device under the target account as the target user device, or may use multiple user devices under the target account as the target user devices, which is not limited here.
[0063] The push method of application messages of the disclosed embodiment can receive the target queue message sent by the message queue server, and in the case where the target queue message carries the target identifier, in response to the target identifier, feedback the response information for the target queue message to the message queue server, wherein the response information is used to enable the message queue server to confirm that the message push server has received the target queue message, and push the target application message to the target user device corresponding to the target queue message; wherein the target application message is generated based on the message content in the target queue message. It can be seen that when the target queue message includes the target identifier, the message push server can feedback the response information to the message queue server to inform the message queue server that the message push server has received the target queue message, thereby avoiding the message queue server from repeatedly sending the target queue message in a short period of time due to not receiving a response, thereby avoiding frequent interruptions to users and improving the user's reading experience.
[0064] In another embodiment of the present disclosure, the method further includes: when the target queue message does not carry a target identifier, pushing a target application message to a target user equipment corresponding to the target queue message.
[0065] In an embodiment of the present disclosure, after receiving a target queue message, the message queue server can detect whether the target queue message carries a target identifier. If it is detected that the target queue message does not carry a target identifier, a response message may not be fed back to the message queue server, but a target application message may be pushed to the target user device corresponding to the target queue message.
[0066] In the embodiments of the present disclosure, the specific explanation of the target identifier is given in the previous text and will not be repeated here.
[0067] In some embodiments, the target queue message may include a first target field, which is used to indicate whether the target queue message requires the message push server to feedback a response message. For example, if the field value of the first target field is 0 or empty, it indicates that the target queue message does not carry a target identifier.
[0068] In other embodiments, the target queue message may directly not include a field for indicating whether the target queue message requires the message push server to feed back a response message.
[0069] In some other embodiments, the target queue message may include a first type identifier for indicating a type, and the first type identifier is used to indicate whether the target queue message requires the message push server to feedback a response message. For example, if the type corresponding to the first type identifier is not a preset type, it indicates that the target queue message does not require the message push server to feedback a response message.
[0070] Optionally, the target queue message corresponding to a small number of target accounts may not carry the target identifier. The specific definition of "a small number of target accounts" can be set by those skilled in the art according to actual conditions and is not limited here. For example, a queue message that does not correspond to a large number of target accounts is a queue message corresponding to a small number of target accounts.
[0071] It is understandable that when the number of target accounts corresponding to the target queue message is small, the time required for the message push server to complete the push of the target application message generated based on the message content of the target queue message is short. In this way, the message push server can feedback the push completion notification to the message queue server in a short time, so that the message queue server will not repeatedly send the target queue message in a short time. In addition, after receiving the target queue message, the message push server saves the communication consumption of feedbacking the response message to the message queue server, and directly sends the target application message to the target user device, which is conducive to improving the push efficiency.
[0072] In another embodiment of the present disclosure, the method also includes: if the push of the target application message is completed within the preset timeout retransmission period, then a completion push notification is fed back to the message queue server; wherein the completion push notification is used to enable the message queue server to confirm that the push of the target application message has been completed; if the push of the target application message is not completed within the preset timeout retransmission period, then the target queue message resent by the message queue server is received.
[0073] In the embodiment of the present disclosure, after receiving the target queue message, if the message push server completes the push of the target application message within the preset timeout retransmission period, it can feedback a push completion notification to the message queue server to enable the message queue server to confirm that the message push server has completed the push; if the push of the target application message is not completed within the preset timeout retransmission period, since the push completion notification is not fed back to the message queue server, the message queue server confirms that the message push server has not completed the push and re-sends the target queue message to the message push server.
[0074] In the embodiment of the present disclosure, the preset timeout retransmission duration is greater than or equal to the maximum duration required for the message queue server to complete message push.
[0075] In some embodiments, the preset timeout retransmission duration may be set by the message queue server itself, and the message queue server may also be configured by a message generation server or a message push server, which is not limited in the present disclosure.
[0076] Specifically, when the time required for the message queue server to complete the push of a certain application message A is longer than the time required for the push of any other application message, the time required for the message queue server to complete the push of the application message A can be used as a threshold, and the preset timeout retransmission time can be greater than or equal to the threshold. Optionally, the preset timeout retransmission time is greater than or equal to 24 hours.
[0077] In the embodiment of the present disclosure, the completion push notification may be any notification that enables the message queue server to know that the message push server has completed the push of the target application message.
[0078] In some embodiments, when the message push server completes the push of the target application message, it can immediately feedback the completion push notification to the message queue server, or it can feedback the completion push notification to the message queue server within the first preset time period after completing the push of the target application message, which is not limited here. Among them, the specific value of the first preset time period can be set by those skilled in the art according to actual conditions, which is not limited here, as long as the completion push notification can be fed back to the message queue server within the preset timeout retransmission duration.
[0079] In an embodiment of the present disclosure, when the message push server fails to complete the push of the target application message within the preset timeout retransmission period and the push fails, it may not feedback any notification to the message queue server. If the message queue server does not receive the completion notification of the push within the preset timeout retransmission period, it may resend the target queue message to the message push server.
[0080] Optionally, when the message push server fails to push within a preset timeout retransmission period, it can feedback a push failure notification to the message queue server. When the message queue server receives the push failure notification, it can resend the target queue message to the message push server.
[0081] It is understandable that, under normal circumstances, the preset timeout retransmission duration is sufficient for the message push server to complete the push of the application message, so that the message queue server can be prevented from resending the target queue message as much as possible. In addition, by setting the preset timeout retransmission duration to be greater than or equal to the maximum duration required for the message queue server to complete the message push, even if the message queue server retransmits the target queue message after the preset timeout retransmission duration, the time interval between two consecutive receptions of the same target queue message by the message push server is relatively long. In this way, the message push server will not repeatedly send the target application message generated based on the message content of the same target queue message to the target user device in a short period of time, that is, it will not cause frequent disturbances to the user.
[0082] In some further embodiments of the present disclosure, after receiving the target queue message sent by the message queue server, the method further includes: based on the book identifier, querying in the cache queue message whether there is a duplicate queue message corresponding to the target queue message; if it is detected that there is a duplicate queue message corresponding to the target queue message, deleting the target queue message.
[0083] In an embodiment of the present disclosure, after receiving the target queue message, the message queue server can detect whether a duplicate queue message corresponding to the target queue message already exists in the cache queue message based on the book identifier. When it is detected that a duplicate queue message corresponding to the target queue message already exists, the target queue message can be deleted to achieve queue message deduplication.
[0084] Specifically, the cache queue message may be a queue message that the message queue server fails to process and cache in time.
[0085] Specifically, the queue message may include a book identifier, and the book identifier may be any identifier that can represent the book corresponding to the queue message.
[0086] In some embodiments, when it is detected that the book identifier of the target queue message is the same as the book identifier of the cache queue message, it can be determined that the cache queue is a duplicate queue message corresponding to the target queue message.
[0087] In other embodiments, when it is detected that the repetition degree of the message content of the target queue message and the message content of the cache queue message is greater than a preset threshold, the cache queue can be determined to be a duplicate queue message corresponding to the target queue message. The specific value of the preset threshold can be set by those skilled in the art according to actual conditions and is not limited here.
[0088] It is understandable that when the message generation server crawls the same book through different websites, it may generate multiple target queue messages for the same book one after another. In this case, the message queue server will send the multiple target queue messages to the message push server, and the message push server will generate the same target application message based on the multiple target queue messages and send it to the target user device. However, in the embodiment of the present disclosure, the message push server can avoid repeatedly sending the same target application message in a short period of time by deleting the target queue message when detecting the existence of a duplicate queue message corresponding to the target queue message, thereby avoiding frequent interruptions to the user with the same target application message, thereby further improving the user experience.
[0089] In some further embodiments of the present disclosure, pushing a target application message to a target user device corresponding to a target queue message includes: detecting whether a target application message has been pushed to the target user device within a preset time period; if it is detected that the target application message has not been pushed to the target user device, pushing the target application message to the target user device.
[0090] In an embodiment of the present disclosure, the message push server pushes the target application message to the target user device corresponding to the target queue message. It can first detect whether the target application message has been pushed to the target user device within a preset time period. If it is detected that the target application message has not been pushed to the target user device, the target application message can be pushed to the target user device; if it is detected that the target application message has been pushed to the target user device, the target application message may no longer be pushed to the target user device.
[0091] In the embodiments of the present disclosure, those skilled in the art may set the specific duration of the preset time period according to actual conditions, which is not limited here. For example, the preset time period may include 30 minutes, 2 hours, or 3 hours, but is not limited thereto.
[0092] In some embodiments, detecting whether a target application message has been pushed to a target user device within a preset time period includes: querying in historical application messages whether a target historical application message corresponding to the target application message already exists.
[0093] In the embodiment of the present disclosure, the historical application message may be a historical application message sent by the message push server within a preset time period.
[0094] It can be understood that by comparing the historical application messages with the target application messages one by one, the method of querying whether there is a target historical application message corresponding to the target application message is simple and easy to implement.
[0095] In other embodiments, detecting whether a target application message has been pushed to a target user device within a preset time period includes: querying in historical message summaries whether a target historical message summary corresponding to the target application message already exists.
[0096] It is understandable that by comparing the historical message digests of the historical application messages with the target application message digests of the target application messages one by one, the efficiency of querying whether a target historical application message corresponding to the target application message already exists can be improved.
[0097] Optionally, the historical message digest may be a message digest of historical application messages sent by the message push server within a preset time period.
[0098] It is understandable that taking the message digests of historical application messages sent by the message push server within a preset time period as historical message digests and comparing them with the target application message digests one by one can simplify the method of querying whether the target historical message digest already exists.
[0099] Optionally, the historical message digest is a message digest of historical application messages that have been pushed to the target user equipment within a preset time period and are stored in association with the device information of the target user equipment.
[0100] Specifically, when storing historical message digests, the message push server may store them in association with the corresponding user devices. For example, for each historical message digest, the user devices that have received the historical application messages corresponding to the historical message digest may be stored in association. For another example, for each user device, the historical message digests of the historical application messages it has received may be stored in association.
[0101] It can be understood that using the message digest associated with the device information of the target user device as the historical message digest is conducive to reducing the number of historical message digests, thereby reducing the workload of comparing them with the target application message digests one by one, and improving the efficiency of querying whether the target historical message digest already exists.
[0102] It can also be understood that, as described above, when the message generation server crawls the same book through different websites, it may generate multiple target queue messages for the same book in succession. In this way, the message queue server will send the multiple target queue messages to the message push server, and the message push server will generate the same target application message based on the multiple target queue messages and send it to the target user device. However, in the embodiment of the present disclosure, the message push server can avoid repeatedly sending the same target application message within the preset time period by pushing the target application message to the target user device when it detects that the target application message has not been pushed to the target user device within the preset time period, thereby avoiding frequent interruptions to the user with the same target application message, thereby further improving the user experience.
[0103] In another embodiment of the present disclosure, a historical message digest is obtained by encoding a historical application message through a preset digest algorithm; wherein, querying in the historical message digest whether a target historical message digest corresponding to the target application message already exists includes: encoding the target application message to obtain a target application message digest; in the historical message digest, querying whether a target historical message digest identical to the target application message digest already exists.
[0104] In the disclosed embodiment, for each application message, the message push server can encode the application message by a preset digest algorithm to obtain a message digest of the application message, and store the message digest of the application message after the application message is pushed. Therefore, the message push server stores a historical message digest obtained by encoding the historical application message by a preset digest algorithm. In addition, the message push server can encode the target application message to obtain a target application message digest, and then query whether there is a target historical message digest that is the same as the target application message digest in the historical message digest.
[0105] In the embodiments of the present disclosure, those skilled in the art may set a preset digest algorithm according to actual conditions. For example, the preset digest algorithm may include an MD5 message digest algorithm (English: MD5 Message-Digest Algorithm), but is not limited thereto.
[0106] Specifically, the target application message digest is obtained by encoding the target application message through a preset digest algorithm.
[0107] It is understandable that by storing the target application message digest of the target application message, the storage space occupied by the message push server can be reduced, and the efficiency of querying whether a target historical application message corresponding to the target application message already exists can be improved.
[0108] In another embodiment of the present disclosure, pushing a target application message to a target user device corresponding to a target queue message includes: determining at least one target account corresponding to the target application message; determining the target user device based on at least one user device under each target account; and pushing the target application message to the target user device.
[0109] In an embodiment of the present disclosure, when the message push server pushes a target application message to a target user device corresponding to a target queue message, it can first determine at least one target account corresponding to the target application message, and then, for each target account, determine at least one user device under the target account as a target user device, and then push the target application message to each target user device.
[0110] In the embodiment of the present disclosure, the target account may be any account corresponding to the target queue message, and the specific examples are shown in the above text, which will not be repeated here. In addition, the specific implementation method of determining at least one target account corresponding to the target queue message is shown in the above text, which will not be repeated here.
[0111] In the embodiment of the present disclosure, the message push server may pre-store user device information of each account, and the user device information includes all user devices under the corresponding account.
[0112] Specifically, for each account, when the message push server detects that the account is logged in through a new user device, the new user device may be added to the user device information under the account.
[0113] In some embodiments, determining the target user device based on at least one user device under each target account may include: for each target account, taking all user devices under the target account as the target user device.
[0114] It is understandable that by using all user devices under each target account as target user devices, the user can receive the target application message in a timely manner regardless of which user device the user is currently using.
[0115] In other embodiments, the target user device is determined based on at least one user device under each target account, including: for at least one user device under each target account, a user device with a bookshelf synchronization function enabled is used as the target user device.
[0116] Specifically, for each account, when the message push server detects that the account has logged in through a certain user device and the bookshelf synchronization function has been activated, the user device may be determined as a user device with the bookshelf synchronization function activated.
[0117] Optionally, taking the user equipment with the bookshelf synchronization function enabled as the target user equipment may include: taking one of the user equipment with the bookshelf synchronization function enabled as the target user equipment.
[0118] It can be understood that when a user activates the bookshelf synchronization function, it indicates that multiple user devices with the bookshelf synchronization function activated are used by the same user. One of the user devices with the bookshelf synchronization function activated is used as the target user device, and the target application message can be sent to a user device of the target account, avoiding sending the target application message to multiple user devices used by the same user at the same time, further avoiding disturbing the user's reading.
[0119] In some further embodiments, the target user device is determined based on at least one user device under each target account, including: for at least one user device under each target account, the user device whose bookshelf contains the target book corresponding to the target application message is used as the target user device.
[0120] Specifically, for each account, the message push server may store the bookshelf of each user device under the account.
[0121] Specifically, multiple different users may use the same account, for example, multiple family members in a family may use the same account. Therefore, for each user device under the same account, when the bookshelf of the user device contains the target book corresponding to the target application message, it indicates that the user using the user device is following the target book, and the user device can be determined as the target user device; when the bookshelf of the user device does not contain the target book corresponding to the target application message, it indicates that the user using the user device is not following the target book, and the user device may not be determined as the target user device.
[0122] It is understandable that pushing the target application message to the user device whose bookshelf contains the target book corresponding to the target application message can achieve accurate push of the target application message and avoid the application message disturbing other users using the account.
[0123] Below, the method for pushing application messages provided by the embodiment of the present disclosure will be described in detail based on a specific example.
[0124] Figure 2 A flow chart of a process of pushing an application message provided by an embodiment of the present disclosure is shown.
[0125] like Figure 2 As shown, the method for pushing application messages may include the following steps.
[0126] S2010. Receive a target queue message sent by a message queue server.
[0127] S2020: When the target queue message carries a target identifier, in response to the target identifier, feedback response information for the target queue message to the message queue server.
[0128] The response information is used to enable the message queue server to confirm that the message push server has received the target queue message.
[0129] S2030. When the target queue message does not carry the target identifier, proceed to S2040.
[0130] S2040: Detect whether the target application message has been pushed to the target user device within a preset time period. If not, execute S2050; if not, execute S2080.
[0131] Optionally, detecting whether the target application message has been pushed to the target user equipment within a preset time period includes: querying in the historical message digest whether a target historical message digest corresponding to the target application message already exists.
[0132] Optionally, the historical message digest is a message digest of historical application messages that have been pushed to the target user equipment within a preset time period and are stored in association with the device information of the target user equipment.
[0133] Optionally, the historical message digest is obtained by encoding the historical application message through a preset digest algorithm; wherein, querying in the historical message digest whether a target historical message digest corresponding to the target application message already exists includes: encoding the target application message to obtain the target application message digest; in the historical message digest, querying whether a target historical message digest identical to the target application message digest already exists.
[0134] S2050: Push the target application message to the target user device.
[0135] Optionally, pushing a target application message to a target user device corresponding to a target queue message includes: determining at least one target account corresponding to the target application message; determining the target user device based on at least one user device under each target account; and pushing the target application message to the target user device.
[0136] Optionally, determining the target user device according to at least one user device under each target account includes: for at least one user device under each target account, taking the user device whose bookshelf contains the target book corresponding to the target application message as the target user device.
[0137] Optionally, the target user device is determined based on at least one user device under each target account, including: for at least one user device under each target account, a user device with a bookshelf synchronization function enabled is used as the target user device.
[0138] S2060: If the push of the target application message is completed within the preset timeout retransmission period, a push completion notification is fed back to the message queue server.
[0139] S2070: If the push of the target application message is not completed within the preset timeout retransmission period, the target queue message resent by the receiving message queue server.
[0140] The completion push notification is used to enable the message queue server to confirm that the target application message has been pushed; wherein the preset timeout retransmission duration is greater than or equal to the maximum duration required for the message queue server to complete the message push.
[0141] S2080: No longer push the target application message to the target user equipment.
[0142] In the application message push method provided by the embodiment of the present disclosure, when the target queue message includes the target identifier, the message push server can feedback the response information to the message queue server to inform the message queue server that the message push server has received the target queue message, thereby avoiding the message queue server from repeatedly sending the target queue message in a short time due to not receiving a response, so as to avoid frequent disturbing of the user. In addition, the message push server can avoid repeatedly sending the same target application message in the preset time period by pushing the target application message to the target user device again when it is detected that the target application message has not been pushed to the target user device within the preset time period, thereby avoiding frequent disturbing of the user with the same target application message, thereby further improving the user experience. In addition, by setting the preset timeout retransmission duration to be greater than or equal to the maximum duration required for the message queue server to complete the message push, even if the message queue server retransmits the target queue message after the preset timeout retransmission duration, the time interval between two consecutive receptions of the same target queue message by the message push server is longer, so that the message push server will not repeatedly send the target application message generated based on the message content of the same target queue message to the target user device in a short time, that is, it will not cause frequent disturbance to the user.
[0143] Figure 3 A schematic structural diagram of an electronic device provided by an embodiment of the present disclosure is shown.
[0144] The electronic device provided in the embodiment of the present disclosure may include an electronic device that supports an e-book reading function. The electronic device may include, but is not limited to, mobile terminals such as smart phones, laptops, personal digital assistants (PDAs), tablet computers (PADs), portable multimedia players (PMPs), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), wearable devices, and fixed terminals such as digital TVs, desktop computers, smart home devices, etc. It should be noted that the execution subject of the push method of the application message of the embodiment of the present disclosure may also be other devices with an audio adjustment function, such as an electronic reading platform or a text to speech (TTS) engine that supports an audio adjustment function, and this is not limited.
[0145] It should be noted that Figure 3 The electronic device 300 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.
[0146] The electronic device 300 conventionally includes a processor 310 and a computer program product or computer-readable medium in the form of a memory 320. The memory 320 may be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read-only memory), an EPROM, a hard disk or a ROM. The memory 320 has a storage space 321 for executable instructions (or program code) 3211 for executing any method steps of the above-mentioned note processing method. For example, the storage space 321 for executable instructions may include individual executable instructions 3211 respectively used to implement various steps in the above-mentioned note processing method. These executable instructions may be read from or written to one or more computer program products. These computer program products include program code carriers such as a hard disk, a compact disk (CD), a memory card or a floppy disk. Such a computer program product is typically a portable or fixed storage unit. The storage unit may have a storage device 3211 having a storage medium 3212 and a storage medium 3213. Figure 3 The memory 320 in the electronic device 300 is similarly arranged as a storage segment or storage space. The executable instructions can be compressed, for example, in an appropriate form. Generally, the storage unit includes executable instructions for executing the steps of the note processing method according to the present disclosure, that is, codes that can be read by a processor such as the processor 310, and when these codes are executed by the electronic device 300, the electronic device 300 executes the various steps in the note processing method described above.
[0147] Of course, to simplify, Figure 3Only some of the components related to the present disclosure in the electronic device 300 are shown, and components such as a bus, an input / output interface, an input device, an output device, etc. are omitted. In addition, according to specific application situations, the electronic device 300 may also include any other appropriate components.
[0148] The embodiments of the present disclosure also provide a computer-readable storage medium on which computer program instructions are stored. When the computer program instructions are executed by a processor, the processor executes the note processing method provided by the embodiments of the present disclosure.
[0149] The computer readable storage medium can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can include, for example, but is not limited to, a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.
[0150] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.
[0151] In the embodiments of the present disclosure, the program code for performing the operations of the present disclosure can be written in one or more programming languages or a combination thereof, including but not limited to object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., using an Internet service provider to connect through the Internet).
[0152] This application discloses:
[0153] 1A. A method for pushing an application message, wherein the method is applied to a message push server, and the method comprises:
[0154] Receive the target queue message sent by the message queue server;
[0155] In the case where the target queue message carries a target identifier, in response to the target identifier, feedback response information for the target queue message to the message queue server; wherein the response information is used to enable the message queue server to confirm that the message push server has received the target queue message;
[0156] Push a target application message to a target user equipment corresponding to the target queue message; wherein the target application message is generated based on the message content in the target queue message.
[0157] in
[0158] 2A. The method according to 1A, wherein the method further comprises:
[0159] If the push of the target application message is completed within the preset timeout retransmission duration, a push completion notification is fed back to the message queue server; wherein the push completion notification is used to enable the message queue server to confirm that the push of the target application message has been completed;
[0160] If the push of the target application message is not completed within the preset timeout retransmission duration, receiving the target queue message resent by the message queue server;
[0161] The preset timeout retransmission duration is greater than or equal to the maximum duration required for the message queue server to complete message push.
[0162] 3A. The method according to 1A, wherein after receiving the target queue message sent by the message queue server, the method further comprises:
[0163] Based on the book identifier, detecting whether a duplicate queue message corresponding to the target queue message already exists in the cache queue message;
[0164] If it is detected that a duplicate queue message corresponding to the target queue message already exists, the target queue message is deleted.
[0165] 4A. The method according to any one of items 1A to 3A, wherein pushing a target application message to a target user equipment corresponding to the target queue message comprises:
[0166] Detecting whether the target application message has been pushed to the target user equipment within a preset time period;
[0167] If it is detected that the target application message has not been pushed to the target user equipment, the target application message is pushed to the target user equipment.
[0168] 5A. The method according to 4A, wherein the detecting whether the target application message has been pushed to the target user equipment within a preset time period comprises:
[0169] It is queried in the historical message digest whether a target historical message digest corresponding to the target application message already exists.
[0170] 6A. The method according to 5A, wherein the historical message digest is a message digest of historical application messages that have been pushed to the target user device within the preset time period and is stored in association with the device information of the target user device.
[0171] 7A. The method according to 5A or 6A, wherein the historical message digest is obtained by encoding the historical application message using a preset digest algorithm;
[0172] The querying in the historical message digest whether the target historical message digest corresponding to the target application message already exists includes:
[0173] Encoding the target application message to obtain a target application message digest;
[0174] In the historical message digests, it is queried whether the target historical message digest identical to the target application message digest already exists.
[0175] 8A. The method according to any one of 1A to 7A, wherein the pushing the target application message to the target user equipment corresponding to the target queue message comprises:
[0176] Determine at least one target account corresponding to the target queue message;
[0177] Determine the target user device according to at least one user device under each of the target accounts;
[0178] Pushing the target application message to the target user equipment.
[0179] 9A. The method according to 8A, wherein determining the target user device according to at least one user device under each of the target accounts comprises:
[0180] For at least one user device under each target account, a user device with a bookshelf synchronization function enabled is used as the target user device.
[0181] 10A. The method according to 8A, wherein determining the target user device according to at least one user device under each of the target accounts comprises:
[0182] For at least one user device under each of the target accounts, a user device whose bookshelf contains the target book corresponding to the target application message is used as the target user device.
[0183] 11B. An electronic device, comprising a processor and a memory, wherein the memory is used to store executable instructions, and the executable instructions enable the processor to perform the following operations:
[0184] Receive the target queue message sent by the message queue server;
[0185] In the case where the target queue message carries a target identifier, in response to the target identifier, feedback response information for the target queue message to the message queue server; wherein the response information is used to enable the message queue server to confirm that the message push server has received the target queue message;
[0186] Push a target application message to a target user equipment corresponding to the target queue message; wherein the target application message is generated based on the message content in the target queue message.
[0187] in
[0188] 12B. The electronic device according to 11B, wherein the executable instructions further cause the processor to execute:
[0189] If the push of the target application message is completed within the preset timeout retransmission duration, a push completion notification is fed back to the message queue server; wherein the push completion notification is used to enable the message queue server to confirm that the push of the target application message has been completed;
[0190] If the push of the target application message is not completed within the preset timeout retransmission duration, receiving the target queue message resent by the message queue server;
[0191] The preset timeout retransmission duration is greater than or equal to the maximum duration required for the message queue server to complete message push.
[0192] 13B. The electronic device according to 11B, wherein after the processor executes the target queue message sent by the receiving message queue server, the executable instruction further causes the processor to execute:
[0193] Based on the book identifier, query in the cache queue message whether there is a duplicate queue message corresponding to the target queue message;
[0194] If it is detected that a duplicate queue message corresponding to the target queue message already exists, the target queue message is deleted.
[0195] 14B. The electronic device according to any one of 11B to 13B, wherein when the processor executes pushing the target queue message to a target user equipment corresponding to the target queue message, the executable instruction specifically causes the processor to execute:
[0196] Detecting whether the target application message has been pushed to the target user equipment within a preset time period;
[0197] If it is detected that the target application message has not been pushed to the target user equipment, the target application message is pushed to the target user equipment.
[0198] 15B. The electronic device according to 14B, wherein, when the processor executes the detection of whether the target application message has been pushed to the target user equipment within a preset time period, the executable instruction specifically causes the processor to execute:
[0199] It is queried in the historical message digest whether a target historical message digest corresponding to the target application message already exists.
[0200] 16B. The electronic device according to 14B, wherein the historical message digest is a message digest of historical application messages that have been pushed to the target user device within the preset time period and is stored in association with the device information of the target user device.
[0201] 17B. The electronic device according to 15B or 16B, wherein the historical message digest is obtained by encoding the historical application message through a preset digest algorithm;
[0202] Wherein, when the processor executes the querying in the historical message digest whether the target historical message digest corresponding to the target application message already exists, the executable instruction specifically causes the processor to execute:
[0203] Encoding the target application message to obtain a target application message digest;
[0204] In the historical message digests, it is queried whether the target historical message digest identical to the target application message digest already exists.
[0205] 18B. The electronic device according to any one of 11B to 17B, wherein when the processor executes the pushing of the target queue message to the target user equipment corresponding to the target application message, the executable instruction specifically causes the processor to execute:
[0206] Determine at least one target account corresponding to the target queue message;
[0207] Determine the target user device according to at least one user device under each of the target accounts;
[0208] Pushing the target application message to the target user equipment.
[0209] 19B. The electronic device according to 18B, wherein when the processor executes the step of determining the target user device according to at least one user device under each of the target accounts, the executable instructions specifically cause the processor to execute:
[0210] For at least one user device under each target account, a user device with a bookshelf synchronization function enabled is used as the target user device.
[0211] 20B. The electronic device according to 8B, wherein when the processor executes the step of determining the target user device according to at least one user device under each of the target accounts, the executable instructions specifically cause the processor to execute:
[0212] For at least one user device under each of the target accounts, a user device whose bookshelf contains the target book corresponding to the target application message is used as the target user device.
[0213] 21C. A computer-readable storage medium, wherein the storage medium stores a computer program, and when the computer program is executed by a processor, the processor implements the method for pushing application messages described in any one of 1A-10A above.
[0214] The various component embodiments of the present disclosure can be implemented in hardware in all or part of the steps, or implemented in software modules running on one or more processors, or implemented in a combination thereof. It should be understood by those skilled in the art that a microprocessor or a digital signal processor (DSP) can be used in practice to implement some or all functions of some or all components in the electronic device according to the embodiments of the present disclosure. The present disclosure can also be implemented as a device or apparatus program (e.g., a computer program and a computer program product) for executing part or all of the methods described herein. Such a program implementing the present disclosure can be stored on a computer-readable medium, or can have the form of one or more signals. Such a signal can be downloaded from an Internet website, or provided on a carrier signal, or provided in any other form.
[0215] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present disclosure (but not limited to) by each other to form a technical solution.
[0216] In addition, although each operation is described in a specific order, this should not be understood as requiring these operations to be performed in the specific order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination mode.
[0217] Although the subject matter has been described in language specific to structural features and / or methodological logical actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. On the contrary, the specific features and actions described above are merely example forms of implementing the claims.
Claims
1. A method for pushing application messages, characterized in that: Applied to a message push server, the method includes: Receive the target queue message sent by the message queue server; In the case where the target queue message carries a target identifier, in response to the target identifier, response information for the target queue message is fed back to the message queue server; wherein the response information is used to enable the message queue server to confirm that the message push server has received the target queue message, so that the message queue server does not repeatedly send the target queue message within a first preset time period, and the target identifier is an identifier indicating that the message push server needs to immediately feed back the response information. If the number of target accounts corresponding to the target queue message is greater than the preset number, the target queue message carries the target identifier; if the number of target accounts corresponding to the target queue message is less than or equal to the preset number, the target queue message does not carry the target identifier; Push a target application message to a target user device corresponding to the target queue message; wherein the target application message is generated based on the message content in the target queue message, and the target user device includes: one of multiple user devices with bookshelf synchronization function activated under the same target account.
2. The method according to claim 1, characterized in that The method further comprises: If the push of the target application message is completed within the preset timeout retransmission duration, a push completion notification is fed back to the message queue server; wherein the push completion notification is used to enable the message queue server to confirm that the push of the target application message has been completed; If the push of the target application message is not completed within the preset timeout retransmission duration, receiving the target queue message resent by the message queue server; The preset timeout retransmission duration is greater than or equal to the maximum duration required for the message queue server to complete message push.
3. The method according to claim 1, characterized in that After receiving the target queue message sent by the message queue server, the method further includes: Based on the book identifier, query in the cache queue message whether there is a duplicate queue message corresponding to the target queue message; If it is detected that a duplicate queue message corresponding to the target queue message already exists, the target queue message is deleted.
4. The method according to any one of claims 1 to 3, characterized in that: Pushing a target application message to a target user equipment corresponding to the target queue message includes: Detecting whether the target application message has been pushed to the target user equipment within a preset time period; If it is detected that the target application message has not been pushed to the target user equipment, the target application message is pushed to the target user equipment.
5. The method according to claim 4, characterized in that The detecting whether the target application message has been pushed to the target user equipment within a preset time period includes: It is queried in the historical message digest whether a target historical message digest corresponding to the target application message already exists.
6. The method according to claim 5, characterized in that The historical message digest is a message digest of historical application messages that have been pushed to the target user equipment within the preset time period and are stored in association with the equipment information of the target user equipment.
7. The method according to claim 5 or 6, characterized in that: The historical message digest is obtained by encoding the historical application message using a preset digest algorithm; The querying in the historical message digest whether the target historical message digest corresponding to the target application message already exists includes: Encoding the target application message to obtain a target application message digest; In the historical message digests, it is queried whether the target historical message digest identical to the target application message digest already exists.
8. The method according to claim 1, characterized in that The pushing the target application message to the target user equipment corresponding to the target queue message includes: Determine at least one target account corresponding to the target queue message; Determine the target user device according to at least one user device under each of the target accounts; Pushing the target application message to the target user equipment.
9. The method according to claim 8, characterized in that The determining the target user device according to at least one user device under each of the target accounts includes: For at least one user device under each target account, a user device with a bookshelf synchronization function enabled is used as the target user device.
10. The method according to claim 8, characterized in that The determining the target user device according to at least one user device under each of the target accounts includes: For at least one user device under each of the target accounts, a user device whose bookshelf contains the target book corresponding to the target application message is used as the target user device.
11. An electronic device, characterized in that: The invention comprises a processor and a memory, wherein the memory is used to store executable instructions, and the executable instructions enable the processor to perform the following operations: Receive the target queue message sent by the message queue server; In the case where the target queue message carries a target identifier, in response to the target identifier, response information for the target queue message is fed back to the message queue server; wherein the response information is used to enable the message queue server to confirm that the message push server has received the target queue message, so that the message queue server does not repeatedly send the target queue message within a first preset time period, and the target identifier is an identifier indicating that the message push server needs to immediately feed back the response information. If the number of target accounts corresponding to the target queue message is greater than the preset number, the target queue message carries the target identifier; if the number of target accounts corresponding to the target queue message is less than or equal to the preset number, the target queue message does not carry the target identifier; Push a target application message to a target user device corresponding to the target queue message; wherein the target application message is generated based on the message content in the target queue message, and the target user device includes: one of multiple user devices with bookshelf synchronization function activated under the same target account.
12. The electronic device according to claim 11, characterized in that: The executable instructions further cause the processor to execute: If the push of the target application message is completed within the preset timeout retransmission duration, a push completion notification is fed back to the message queue server; wherein the push completion notification is used to enable the message queue server to confirm that the push of the target application message has been completed; If the push of the target application message is not completed within the preset timeout retransmission duration, receiving the target queue message resent by the message queue server; The preset timeout retransmission duration is greater than or equal to the maximum duration required for the message queue server to complete message push.
13. The electronic device according to claim 11, characterized in that: After the processor executes the target queue message sent by the receiving message queue server, the executable instruction further causes the processor to execute: Based on the book identifier, query in the cache queue message whether there is a duplicate queue message corresponding to the target queue message; If it is detected that a duplicate queue message corresponding to the target queue message already exists, the target queue message is deleted.
14. The electronic device according to any one of claims 11 to 13, characterized in that: When the processor executes to push the target queue message to the target user equipment corresponding to the target queue message, the executable instruction specifically causes the processor to execute: Detecting whether the target application message has been pushed to the target user equipment within a preset time period; If it is detected that the target application message has not been pushed to the target user equipment, the target application message is pushed to the target user equipment.
15. The electronic device according to claim 14, characterized in that: When the processor executes the detection of whether the target application message has been pushed to the target user equipment within a preset time period, the executable instruction specifically causes the processor to execute: It is queried in the historical message digest whether a target historical message digest corresponding to the target application message already exists.
16. The electronic device according to claim 15, characterized in that: The historical message digest is a message digest of historical application messages that have been pushed to the target user equipment within the preset time period and are stored in association with the equipment information of the target user equipment.
17. The electronic device according to claim 15 or 16, characterized in that: The historical message digest is obtained by encoding the historical application message using a preset digest algorithm; Wherein, when the processor executes the querying in the historical message digest whether the target historical message digest corresponding to the target application message already exists, the executable instruction specifically causes the processor to execute: Encoding the target application message to obtain a target application message digest; In the historical message digests, it is queried whether the target historical message digest identical to the target application message digest already exists.
18. The electronic device according to claim 11, characterized in that: When the processor executes the step of pushing the target queue message to the target user equipment corresponding to the target application message, the executable instruction specifically causes the processor to execute: Determine at least one target account corresponding to the target queue message; Determine the target user device according to at least one user device under each of the target accounts; Pushing the target application message to the target user equipment.
19. The electronic device according to claim 18, characterized in that: When the processor executes the step of determining the target user device according to at least one user device under each of the target accounts, the executable instruction specifically causes the processor to execute: For at least one user device under each target account, a user device with a bookshelf synchronization function enabled is used as the target user device.
20. The electronic device according to claim 18, characterized in that When the processor executes the step of determining the target user device according to at least one user device under each of the target accounts, the executable instruction specifically causes the processor to execute: For at least one user device under each of the target accounts, a user device whose bookshelf contains the target book corresponding to the target application message is used as the target user device.
21. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by the processor, the processor implements the method for pushing application messages according to any one of claims 1 to 10.
