Message push method, device, electronic device and computer-readable storage medium

Abstract

The present disclosure relates to a message push method, device, electronic device, computer-readable storage medium, and computer program product. The method obtains a message to be pushed, and verifies the count of received messages of the target account identifier under the message frequency control dimension at the current moment according to a pre-configured message frequency control dimension and a corresponding message frequency control threshold. When the verification passes, the message to be pushed is determined to be a target push message, and the target push message is pushed to the target account identifier. Because this embodiment needs to verify the count of received messages of the target account identifier under the message frequency control dimension obtained by the server at the current moment according to the pre-configured message frequency control dimension and the message frequency control threshold corresponding to the message frequency control dimension before pushing the message to the target account identifier, and the message is pushed only when the verification passes. Therefore, the number of messages received by the user terminal can be controlled from different dimensions, thereby avoiding the flooding of messages on the user terminal.

Description

Technical Field

[0001] The present disclosure relates to Internet technologies, and in particular to a message push method, device, electronic device, computer-readable storage medium, and computer program product. Background Art

[0002] With the development of Internet technology, various applications have emerged. Usually, applications can push different messages to users based on different business expectations. For example, based on production business expectations, production promotion messages can be pushed to users; based on growth business expectations, activity-related messages can be pushed to users; based on live broadcast business expectations, live broadcast on / off messages can be pushed to users. Therefore, if the message platform does not limit the number of messages received by users, different applications will frequently push multiple messages to users in order to achieve their own business goals, which will lead to message flooding on the user side.

[0003] In the related art, a common message frequency control method is to restrict the number of messages of a certain type received by a user, such as restricting an application to only push one message of type xx to a user per day.

[0004] However, the message frequency control method in the related art can only constrain the sender, and can only constrain the number of messages of a certain type received by the user within a certain period. For example, when there are dozens of business directions pushing messages to users during a certain activity, although the sender has set a frequency limit of 2 messages per day, the user can still receive dozens or even hundreds of push messages every day. Therefore, the current message frequency control method cannot effectively solve the problem of user-side message flooding. Summary of the invention

[0005] The present disclosure provides a message push method, device, electronic device, computer-readable storage medium, and computer program product to at least solve the problem that the message frequency control method in the related art cannot well solve the problem of user-side message flooding. The technical solution of the present disclosure is as follows:

[0006] According to a first aspect of an embodiment of the present disclosure, a message push method is provided, including:

[0007] Acquire a message to be pushed, where the message to be pushed carries an identifier of a target account to be pushed;

[0008] According to a pre-configured message frequency control dimension, obtaining a count of messages received by the target account identifier under the message frequency control dimension at the current moment;

[0009] Obtaining a pre-configured message frequency control threshold corresponding to the message frequency control dimension, and determining that the verification is passed when the count is less than the message frequency control threshold corresponding to the message frequency control dimension;

[0010] When the verification is passed, it is determined that the message to be pushed is a target push message, and the target push message is stored in the storage space corresponding to the target account identifier.

[0011] In one of the embodiments, obtaining the message to be pushed includes: obtaining a candidate push message from a message queue, the candidate push message carrying a target account identifier for the corresponding push; obtaining a count of received messages for the target account identifier under the message frequency control dimension according to a pre-configured message frequency control dimension; verifying the count according to a pre-configured message frequency control threshold corresponding to the message frequency control dimension; when the verification passes, determining that the candidate push message is a message to be pushed.

[0012] In one of the embodiments, after the verification is passed and it is determined that the message to be pushed is a target push message, the method further includes: updating the count of received messages of the target account identifier under the message frequency control dimension to obtain an updated count.

[0013] In one of the embodiments, the message frequency control dimension includes an account dimension and a corresponding at least one first frequency control period; obtaining the count of messages received by the target account identifier under the message frequency control dimension at the current moment according to the pre-configured message frequency control dimension includes: determining the target account dimension corresponding to the target account identifier and the corresponding at least one target first frequency control period according to the target account identifier and the pre-configured account dimension and the corresponding at least one first frequency control period; obtaining the first count of messages received by the target account identifier in at least one target first frequency control period under the target account dimension at the current moment.

[0014] In one of the embodiments, the message frequency control dimension also includes a message type dimension and at least one corresponding second frequency control period; the message to be pushed also carries a corresponding message type; and according to the pre-configured message frequency control dimension, obtaining the count of received messages of the target account identifier under the message frequency control dimension at the current moment includes: determining the target message type dimension and the corresponding at least one target second frequency control period to which the message to be pushed belongs according to the message type of the message to be pushed, and the pre-configured message type dimension and the corresponding at least one second frequency control period; obtaining the second count of messages corresponding to the target message type dimension in the received messages of the target account identifier at the current moment within the at least one target second frequency control period.

[0015] In one of the embodiments, the message frequency control dimension also includes a message box dimension and a corresponding at least one third frequency control period; obtaining the count of messages received by the target account identifier under the message frequency control dimension at the current moment according to the pre-configured message frequency control dimension includes: determining the target message box of the message to be pushed relative to the target account identifier and the corresponding at least one third frequency control period according to the message type of the message to be pushed, and the pre-configured message box dimension and the corresponding at least one third frequency control period; obtaining the third count of messages received by the target account identifier through the target message box within the at least one target third frequency control period at the current moment.

[0016] In one of the embodiments, the method further includes: obtaining and storing message frequency control configuration information, the message frequency control configuration information including a message frequency control dimension and a corresponding message frequency control threshold; the message frequency control dimension including at least one of an account dimension, a message type dimension, and a message box dimension.

[0017] In one of the embodiments, the method further includes: when the count is greater than or equal to the message frequency control threshold of the corresponding message frequency control dimension, determining that the verification fails; when the verification fails, determining that the message push fails.

[0018] According to a second aspect of an embodiment of the present disclosure, a message push device is provided, including:

[0019] A module for acquiring messages to be pushed, configured to execute acquisition of messages to be pushed, wherein the messages to be pushed carry a target account identifier to be pushed;

[0020] A count acquisition module is configured to execute, according to a pre-configured message frequency control dimension, acquiring a count of messages received by the target account identifier under the message frequency control dimension at a current moment;

[0021] A verification module is configured to execute acquisition of a pre-configured message frequency control threshold corresponding to the message frequency control dimension, and determine that the verification is passed when the count is less than the message frequency control threshold corresponding to the message frequency control dimension;

[0022] The message storage module is configured to determine that the message to be pushed is a target push message when the verification is passed, and store the target push message in the storage space corresponding to the target account identifier.

[0023] According to a third aspect of an embodiment of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement the message push method as described in any one of the first aspects above.

[0024] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided. When instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the message push method as described in any one of the first aspects above.

[0025] According to a fifth aspect of an embodiment of the present disclosure, a computer program product is provided, wherein the computer program product includes instructions, and when the instructions are executed by a processor of an electronic device, the electronic device is enabled to execute the message push method as described in any one of the first aspects above.

[0026] The technical solution provided by the embodiments of the present disclosure brings at least the following beneficial effects: the server obtains the message to be pushed, and according to the pre-configured message frequency control dimension, obtains the count of the target account identifier's received messages under the message frequency control dimension at the current moment, and verifies the count according to the pre-configured message frequency control threshold corresponding to the message frequency control dimension. When the verification passes, it is determined that the message to be pushed is a target push message, and the target push message is stored in the storage space corresponding to the target account identifier, thereby completing the push of the target push message to the target account identifier. Because this embodiment needs to verify the count of the target account identifier's received messages under the message frequency control dimension obtained by the server at the current moment according to the pre-configured message frequency control dimension and the message frequency control threshold corresponding to the message frequency control dimension before pushing the message to the target account identifier, and the message is pushed only when the verification passes, so the number of messages received by the user end can be controlled from different dimensions, thereby avoiding the flooding of messages on the user end.

[0027] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.

[0029] Figure 1 The figure is a flowchart of a message pushing method according to an exemplary embodiment.

[0030] Figure 2 The figure is a schematic diagram showing the steps of obtaining a message to be pushed according to an exemplary embodiment.

[0031] Figure 3 The figure is a flowchart of a message pushing method according to another exemplary embodiment.

[0032] Figure 4 It is a schematic diagram of a message server according to an exemplary embodiment.

[0033] Figure 5 The figure is a block diagram of a message pushing device according to an exemplary embodiment.

[0034] Figure 6 It is a block diagram of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION

[0035] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings.

[0036] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0037] It should also be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for display, data for analysis, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties.

[0038] In one embodiment, Figure 1 As shown, a message push method is provided. This embodiment takes the method applied to a server as an example. Specifically, the server may be a message server. In this embodiment, the method may include the following steps:

[0039] In step S110, the message to be pushed is obtained.

[0040] Among them, the message to be pushed carries the target account identifier to be pushed. Specifically, the message to be pushed can be a message obtained by the server to be pushed to the target account, that is, the message corresponding to the message task processed by the server by calling the message RPC (Remote Procedure Call). The target account can be the designated receiving account for the message to be pushed, and the target account identifier refers to the account information corresponding to the target account, for example, it can be a user nickname, user ID (Identity document), user mobile phone number, etc. The target account identifier is usually unique and is used to distinguish different user accounts.

[0041] For example, messages include but are not limited to activity notification messages, service notification messages, creation incentive messages, live broadcast notification messages, messages triggered by user behavior, etc. User behavior includes but is not limited to like, favorite, poke, comment, @, etc. Specifically, if user A likes the work of user B, the server will push a like message from user A to user B. The like message is the message to be pushed, and user B who receives the like message is the target account identifier.

[0042] In step S120, according to the pre-configured message frequency control dimension, the count of messages received by the target account identifier under the message frequency control dimension at the current moment is obtained.

[0043] Among them, the message frequency control dimension refers to the angle of limiting the number of messages a user receives. For example, from the user's perspective, the number of messages a user receives within a period T can be limited; for example, from the message type perspective, the number of messages a user receives from category X within a period T can be limited; for example, from the message box perspective, the number of messages a user receives from a single message box within a period T can be limited, where the message box is based on certain business rules and converges messages of the same business into one box to display to the user.

[0044] In this embodiment, in order to avoid the flooding of user-side messages, the message frequency control dimension can be pre-configured on the server side. Therefore, when the server obtains the message to be pushed, it can obtain the count of the target account identifier under the message frequency control dimension at the current moment according to the pre-configured message frequency control dimension. Among them, the current moment refers to the moment when the server obtains the message to be pushed to the target account identifier. The count of the message received by the target account identifier can refer to the count of the message received by the target account identifier under the dimension corresponding to the pre-configured message frequency control dimension. For example, if the pre-configured message frequency control dimension is from the user's perspective, that is, the number of messages received by the user within a period T is limited, then the count is based on the user's perspective. The number of messages that the target account identifier has received within the period T. If the pre-configured message frequency control dimension is other dimensions, the number of messages received by the target account identifier is obtained based on the corresponding dimension.

[0045] In step S130, a pre-configured message frequency control threshold corresponding to the message frequency control dimension is obtained, and when the count is less than the message frequency control threshold corresponding to the message frequency control dimension, it is determined that the verification is passed.

[0046] Among them, the message frequency control threshold is the maximum value of the number of messages corresponding to the message frequency control dimension. For example, if the pre-configured message frequency control dimension is from the user's perspective, that is, the number of messages received by the user within a period T is limited, then the message frequency control threshold is the pre-configured maximum value of the number of messages received by the user within the period T. Similarly, if the pre-configured message frequency control dimension is from the message type perspective, that is, the number of messages of type X received by the user within a period T is limited, then the message frequency control threshold is the pre-configured maximum value of the number of messages of type X received by the user within the period T.

[0047] In this embodiment, the server verifies the count of received messages identified by the target account under the message frequency control dimension obtained at the current moment according to the pre-configured message frequency control dimension and the message frequency control threshold corresponding to the message frequency control dimension, that is, verifies whether the current count is less than the message frequency control threshold of the corresponding message frequency control dimension. When the current count is less than the message frequency control threshold of the corresponding message frequency control dimension, it is determined that the verification has passed.

[0048] For example, if the pre-configured message frequency control dimension and the corresponding message frequency control threshold are, the maximum number of messages a user receives within period T is d1, which means that the user can only receive d1 messages at most within period T. If the target account identifier obtained by the server at the current moment receives messages within period T, the count of the number of messages is b1, that is, the user has received b1 messages cumulatively at the current moment. If b1 is less than d1, it means that the user can continue to receive messages, so the verification is determined to be passed. Then, the message to be pushed can be determined as the target push message, and the target push message can be stored in the storage space corresponding to the target account identifier, thereby realizing message push based on the message frequency control dimension and the message frequency control threshold, avoiding user-side message flooding.

[0049] In step S140, when the verification passes, it is determined that the message to be pushed is a target push message, and the target push message is stored in the storage space corresponding to the target account identifier.

[0050] Among them, the target push message refers to the message that can be pushed to the target account identifier in the end. Specifically, if the current count does not reach the corresponding message frequency control threshold, it means that the user can continue to receive messages. Therefore, if the verification is passed, the server determines the above-mentioned message to be pushed as the target push message, and stores the target push message in the storage space corresponding to the target account identifier, that is, the process of the message RPC pushing the target push message to the target account identifier is completed.

[0051] In the above message push method, the server obtains the message to be pushed, obtains the count of the target account identifier's received messages under the message frequency control dimension at the current moment according to the pre-configured message frequency control dimension, and verifies the count according to the pre-configured message frequency control threshold corresponding to the message frequency control dimension. When the verification passes, it is determined that the message to be pushed is a target push message, and the target push message is stored in the storage space corresponding to the target account identifier, thereby completing the push of the target push message to the target account identifier. Because this embodiment needs to verify the count of the target account identifier's received messages under the message frequency control dimension obtained by the server at the current moment according to the pre-configured message frequency control dimension and the message frequency control threshold corresponding to the message frequency control dimension before pushing the message to the target account identifier, and the message push is performed only when the verification passes. Therefore, the number of messages received by the user end can be controlled from different dimensions, thereby avoiding the flooding of messages on the user end.

[0052] In an exemplary embodiment, the above method may further specifically include: when the count is greater than or equal to the message frequency control threshold of the corresponding message frequency control dimension, determining that the verification fails; when the verification fails, determining that the message push fails.

[0053] Specifically, still using the above embodiment for illustration, if the pre-configured message frequency control dimension and the corresponding message frequency control threshold are, the maximum number of messages received by the user within period T is d1. If the count of the number of messages received by the target account identifier obtained by the server at the current moment within period T is b1, if b1 is greater than d1, or b1 is equal to d1, it means that the number of messages received by the user has reached the maximum value of the control, that is, the user can no longer continue to receive messages, and therefore, it is determined that the verification has failed. Since the user can no longer continue to receive messages, it can be determined that the message push has failed, that is, the push of the message to be pushed to the user has failed. This prevents users from being disturbed by too many messages and improves user experience.

[0054] In an exemplary embodiment, in step S140, when the verification passes and it is determined that the message to be pushed is a target push message, the above method may also include: updating the count of received messages of the target account identifier under the message frequency control dimension to obtain an updated count.

[0055] Specifically, when the verification is passed, it can be determined that the message to be pushed this time is the target push message, which means that the target push message can be pushed to the target account ID. Therefore, in order to obtain the accurate count of the user's received messages when the subsequent message is pushed, when the verification is passed and it is determined that the message to be pushed is the target push message, the server can also update the count of the target account ID's received messages under the message frequency control dimension, that is, perform an update by adding 1 to the corresponding count, thereby obtaining the updated count.

[0056] It is understandable that for each message push, the count obtained during verification is the count updated after the last successful verification, and the count updated for this push will be used for verification during the next message push. Therefore, for each message push, when the verification passes, the corresponding count will be updated in time, so that there will be no concurrency problems, and the accurate count of the user's received messages can be obtained for each message push.

[0057] In an exemplary embodiment, if Figure 2 As shown, in step S110, the message to be pushed is obtained, which can be specifically implemented by the following steps:

[0058] In step S210, a candidate push message is obtained from a message queue.

[0059] The message queue may be a container for storing message tasks that want to send candidate push messages to users. The candidate push messages carry the corresponding target account identifier for the push. Specifically, the candidate push messages may be messages that the business party wants to send to users.

[0060] In this embodiment, when the business party wants to push a message to a user, it applies to the server, and after the application is approved, it pushes the candidate push message to the specified user by calling the message push SDK (Software Development Kit) provided by the server, and the SDK forwards the message task of pushing the candidate push message to the message queue. The server pushes the candidate push message by consuming the message task in the message queue. Specifically, when the server consumes the message task in the message queue, it first obtains the candidate push message corresponding to the message task from the message queue.

[0061] In step S220, according to the pre-configured message frequency control dimension, the count of the received messages of the target account identifier under the message frequency control dimension is obtained.

[0062] In this embodiment, the server obtains the count of received messages of the target account identifier under the message frequency control dimension based on the candidate push message corresponding to the message task obtained from the message queue and the pre-configured message frequency control dimension, and then verifies the count through subsequent steps. Only when the verification is passed, the candidate push message corresponding to the message task is treated as a to-be-pushed message and handed over to the message RPC for processing, thereby reducing the processing pressure of the message RPC.

[0063] In step S230, the count is verified according to a pre-configured message frequency control threshold corresponding to the message frequency control dimension.

[0064] The message frequency control dimension may refer to an angle for limiting the number of messages received by a user. The message frequency control threshold is the maximum value of the number of messages corresponding to the message frequency control dimension.

[0065] In this embodiment, the server verifies the count of received messages of the target account identifier under the currently acquired message frequency control dimension according to the pre-configured message frequency control dimension and the message frequency control threshold corresponding to the message frequency control dimension, that is, verifies whether the current count reaches the corresponding message frequency control threshold. If the current count is less than the message frequency control threshold of the corresponding message frequency control dimension, it is determined that the verification is passed. If the count is greater than or equal to the message frequency control threshold of the corresponding message frequency control dimension, it is determined that the verification is not passed. Thus, it is determined whether to hand over the candidate push message to the message RPC for processing based on the verification result to reduce the processing pressure of the message RPC. Among them, the current refers to the moment when the server obtains the candidate push message corresponding to the message task from the message queue, which is earlier than the moment when the server obtains the message to be pushed to the target account identifier. Therefore, the timing of the counts obtained by the server twice is different. If the count is not updated during this period, the counts obtained twice are the same. If the count is updated during this period, the counts obtained twice are different.

[0066] In step S240, when the verification passes, the candidate push message is determined to be the message to be pushed.

[0067] The message to be pushed is the message that the server obtains and will push to the target account. Specifically, if the current count does not reach the corresponding message frequency control threshold, it means that the user can continue to receive messages. Therefore, the verification passes, and the server determines the candidate push message as the message to be pushed and sends it to the message RPC for further processing.

[0068] In the above embodiment, the server obtains the count of received messages of the target account identifier under the message frequency control dimension based on the candidate push message corresponding to the message task obtained from the message queue and according to the pre-configured message frequency control dimension, and then verifies the count according to the pre-configured message frequency control threshold corresponding to the message frequency control dimension. Only when the verification passes, the candidate push message corresponding to the message task is determined to be the message to be pushed, and is handed over to the message RPC for further processing. Because the message task has been filtered based on the message frequency control dimension and the corresponding message frequency control threshold and the count of user received messages before the message RPC is processed, the processing pressure of the message RPC can be reduced while avoiding the flooding of messages on the user side.

[0069] In an exemplary embodiment, in step S210, before obtaining the candidate push message from the message queue, the above method may further include: obtaining and storing message frequency control configuration information. The message frequency control configuration information includes a message frequency control dimension and a corresponding message frequency control threshold. Specifically, the message frequency control dimension may refer to an angle for limiting the number of messages received by a user. For example, the message frequency control dimension may include at least one of an account dimension, a message type dimension, and a message box dimension. The message frequency control threshold is the maximum value of the number of messages corresponding to the message frequency control dimension.

[0070] Specifically, the account dimension may refer to the number of messages received by the user within a period T from the user's perspective. For example, the maximum number of messages received by the user within period T1 may be limited to n1, and the maximum number of messages received by the user within period T2 may be limited to n2. The message type dimension may refer to the number of messages received by the user within period T from the message type perspective. For example, the maximum number of messages received by the user within period T3 from the X-type message may be limited to n3, and the maximum number of messages received by the user within period T4 from the X-type message may be limited to n4. The message box dimension may refer to the number of messages received by the user from a single message box within period T from the message box perspective. For example, the maximum number of messages received by the user from a single message box within period T5 may be limited to n5, and the maximum number of messages received by the user from a single message box within period T6 may be limited to n6. Among them, the time periods T1, T2, T3, T4, T5 and T6, and the corresponding message frequency control thresholds n1, n2, n3, n4, n5 and n6 can be set to specific values ​​according to actual needs, and this is not limited in this embodiment.

[0071] In this embodiment, before obtaining the candidate push message from the message queue, the server first obtains and stores the message frequency control configuration information, thereby providing a basis for subsequent frequency control, and based on the message frequency control configuration information, it can effectively, quickly and conveniently meet almost all frequency control requirements.

[0072] In an exemplary embodiment, the pre-configured message frequency control dimension includes an account dimension and a corresponding at least one first frequency control period; then, based on the pre-configured message frequency control dimension, a count of messages received by the target account identifier under the message frequency control dimension at the current moment is obtained, including: determining the target account dimension and the corresponding at least one target first frequency control period corresponding to the target account identifier according to the target account identifier, and the pre-configured account dimension and the corresponding at least one first frequency control period; obtaining a first count of messages received by the target account identifier within at least one target first frequency control period under the target account dimension at the current moment.

[0073] For example, if the pre-configured account dimension and the corresponding at least one first frequency control period include: a limit on the number of messages received by the same user in period T1, and a limit on the number of messages received by the same user in period T2, where T1 is different from T2. Then, obtaining a first count of messages received by the target account identifier at the current moment in at least one target first frequency control period under the target account dimension specifically includes: obtaining a count C1 of messages received by the target account identifier at the current moment in period T1, and obtaining a count C2 of messages received by the target account identifier at the current moment in period T2, and using C1 and C2 as the first counts.

[0074] In one scenario, if the pre-configured account dimension and the corresponding at least one first frequency control period include: a limit on the number of messages received by users with account type Y1 in period T1, a limit on the number of messages received by users with account type Y2 in period T2, and a limit on the number of messages received by users with account type Y3 in period T3. Then, a first count of received messages of the target account identifier at the current moment in at least one target first frequency control period under the target account dimension is obtained, specifically including: firstly, determining the corresponding account type according to the target account identifier, and if it is determined that the account type corresponding to the target account identifier is Y2, then further obtaining the count of received messages of the target account identifier at the current moment in period T2 as the first count. Among them, the account type can be determined based on at least one of different account levels, historical behaviors of the account, etc., which is not limited in this embodiment.

[0075] It is understandable that for the same account type, different frequency control periods can also be configured, and the number of messages received in different frequency control periods can be limited. For example, if the account type corresponding to the target account identifier is Y1, and the pre-configured account dimension and the corresponding at least one first frequency control period include: a limit on the number of messages received by users with account type Y1 in period f1, and a limit on the number of messages received by users with account type Y1 in period f2. Then, the first count of received messages in at least one target first frequency control period under the target account dimension at the current moment is obtained, specifically including: obtaining the count m1 of messages received by the target account identifier at the current moment in period f1, and obtaining the count m2 of messages received by the target account identifier at the current moment in period f2, and taking m1 and m2 as the first count.

[0076] In the above embodiment, the message frequency control is performed based on the account dimension, so that different frequency control strategies can be adopted according to different accounts, thereby improving the flexibility of frequency control.

[0077] In an exemplary embodiment, the pre-configured message frequency control dimension may also include a message type dimension and at least one corresponding second frequency control period; the message to be pushed also carries a corresponding message type. Then, according to the pre-configured message frequency control dimension, the count of received messages of the target account identifier under the message frequency control dimension at the current moment is obtained, including: according to the message type of the message to be pushed, the pre-configured message type dimension and the corresponding at least one second frequency control period, determining the target message type dimension and the corresponding at least one second frequency control period to which the message to be pushed belongs; obtaining the second count of messages corresponding to the target message type dimension in the received messages of the target account identifier at the current moment within at least one second frequency control period.

[0078] Among them, message types include but are not limited to activity notification messages, service notification messages, creation incentive messages, live broadcast notification messages, user behavior trigger messages and other types.

[0079] For example, if the pre-configured message type dimension and the corresponding at least one second frequency control period include: a limit on the number of activity notification messages received by the user within period T1, a limit on the number of service notification messages received by the user within period T2, and a limit on the number of creation incentive messages received by the user within period T3, etc. T1, T2, and T3 may be the same or different. If the message type carried by the message to be pushed is an activity notification message, then the count of messages received by the target account identifier under the message frequency control dimension at the current moment is obtained, specifically including: first, according to the message type carried by the message to be pushed, determining that the target message type dimension to which the message to be pushed belongs is the activity notification message dimension, and the corresponding at least one target second frequency control period is period T1, and then obtaining the number of activity notification messages received by the user corresponding to the target account identifier at the current moment within period T1, that is, the second count.

[0080] In one scenario, for the same message type dimension, different frequency control periods can be pre-configured, and the number of messages of the same type received in different frequency control periods can be limited. Then, message frequency control can be performed according to different frequency control periods under the same message type, thereby realizing a multi-dimensional and configurable frequency control solution.

[0081] In the above embodiment, message frequency control is performed based on the message type dimension, so that different frequency control strategies can be used for control according to different message types. This not only realizes a multi-dimensional and configurable frequency control scheme, but also further improves the flexibility and diversity of frequency control.

[0082] In an exemplary embodiment, the preconfigured message frequency control dimension may also include a message box dimension and at least one corresponding third frequency control period. Then, according to the preconfigured message frequency control dimension, the count of messages received by the target account identifier under the message frequency control dimension at the current moment is obtained, including: determining the target message box and the corresponding at least one target third frequency control period of the message to be pushed relative to the target account identifier according to the message type of the message to be pushed, the preconfigured message box dimension and the corresponding at least one third frequency control period; obtaining the third count of messages received by the target account identifier through the target message box within at least one target third frequency control period at the current moment.

[0083] Among them, the message box is a form of displaying the same business messages to users in one box based on certain business rules. For example, operational business messages such as event notification messages, creation incentive messages, live broadcast notification messages, service notification messages, etc. can be displayed to users in the same box. Functional user behavior messages such as likes, favorites, pokes, comments, @, etc. can also be displayed to users in the same box.

[0084] The message box dimension can be based on the perspective of the message box to perform frequency control on the number of messages received from a single message box. For example, if the pre-configured message box dimension and the corresponding at least one third frequency control period include: limiting the number of messages received by the user from the message box Z1 within the period T1, limiting the number of messages received by the user from the message box Z2 within the period T2, etc. T1 and T2 can be the same or different, and Z1 and Z2 are different message boxes.

[0085] Then, the count of the received messages of the target account identifier under the message frequency control dimension at the current moment is obtained, specifically including: first, according to the message type of the message to be pushed, the corresponding target message box is determined. If in this embodiment, according to the message type of the message to be pushed, the corresponding target message box is determined to be Z1, then the number of messages received by the target account identifier from the message box Z1 within the period T1 at the current moment, i.e., the third count, is further obtained.

[0086] In one scenario, for the same message box dimension, different frequency control periods can be pre-configured, and the number of messages received from the same message box in different frequency control periods can be limited. Then, message frequency control can be performed according to different frequency control periods under the same message box, thereby realizing a multi-dimensional and configurable frequency control solution.

[0087] In the above embodiment, message frequency control is performed based on the message example dimension, so that different frequency control strategies can be used for control according to different message boxes. This not only realizes a multi-dimensional and configurable frequency control scheme, but also further improves the flexibility and diversity of frequency control.

[0088] In an exemplary embodiment, if Figure 3 As shown, the message push method disclosed in the present invention is further described. This embodiment uses the method applied to a message server as an example. Specifically, the method may include the following steps:

[0089] In step S310, message frequency control configuration information is obtained and stored.

[0090] In this embodiment, the message server is as follows Figure 4 As shown, it includes a frequency control strategy module, a frequency control verification module and a frequency control counting module connected in sequence, and also includes a message RPC and a message task queue respectively connected to the frequency control verification module, and a message storage module connected to the message RPC.

[0091] Specifically, the server first obtains the message frequency control configuration information, and stores the obtained message frequency control configuration information in the frequency control strategy module. Among them, the message frequency control configuration information includes the message frequency control dimension and the corresponding message frequency control threshold. For example, if the message frequency control configuration information obtained by the server in this embodiment includes: the maximum number of messages received by the user in period T1 based on the account dimension is n1, and the maximum number of messages received by the user in period T2 is n2; it also includes the maximum number of messages received by the user in period T3 based on the message type dimension. The maximum number of messages received by the user in period T3 is n3, and the maximum number of messages received by the user in period T4 is n4. The maximum number of messages received by the user from the message box Z1 in period T5 is n5, and the maximum number of messages received by the user from the message box Z2 in period T6 is n6. Then the server stores the above-obtained message frequency control configuration information in the frequency control strategy module.

[0092] In step S320, a candidate push message is obtained from the message queue, and a frequency control verification module is called to verify the message task corresponding to the candidate push message.

[0093] In this embodiment, when the business party wants to push a message to a user, it applies to the server, and after the application is approved, calls the message push SDK provided by the server to push the candidate push message to the specified user, and the SDK forwards the message task of pushing the candidate push message to the message queue. The server consumes the message task in the message queue, first obtains the candidate push message corresponding to the message task from the message queue, and then calls the frequency control verification module to verify the message task corresponding to the candidate push message. Among them, the candidate push message carries the corresponding message type and the target account identifier to be pushed.

[0094] Specifically, during verification, the frequency control verification module obtains the pre-configured message frequency control configuration information from the frequency control strategy module, and based on the message type corresponding to the candidate push message and the target account identifier to be pushed, determines the target message frequency control dimension and message frequency control threshold that match the message type and target account identifier from the message frequency control configuration information.

[0095] For example, if the message type corresponding to the candidate push message is X1, and the message receiving end corresponding to the target account identifier uses the message box Z1 to receive the X1 message. The target message frequency control dimension and target message frequency control threshold that match the message type and the target account identifier determined from the message frequency control configuration information include: the maximum number of messages received by the target account identifier in period T1 is n1, the maximum number of messages received by the target account identifier in period T2 is n2, the maximum number of messages received by the target account identifier in period T3 is n3, and the maximum number of messages received by the target account identifier from the message box Z1 in period T5 is n5.

[0096] Then, the frequency control verification module calls the frequency control counting module to obtain the count of messages received by the target user identifier under the corresponding dimension based on the frequency control dimension of the target message. For example, the count L1 of messages received by the target account identifier in period T1, the count L2 of messages received by the target account identifier in period T2, the count L3 of X1 messages received by the target account identifier in period T3, and the count L4 of messages received by the target account identifier from the message box Z1 in period T5.

[0097] The frequency control verification module compares the counts obtained by the frequency control counting module with the corresponding target message frequency control threshold. If each count is less than the corresponding target message frequency control threshold, it means that the corresponding message task verification has passed. If any count is greater than or equal to the corresponding target message frequency control threshold, it means that the corresponding message task verification has failed.

[0098] In step S330, the candidate push message corresponding to the verified message task is determined as the message to be pushed, and the message RPC is called to process the message task.

[0099] Specifically, the server determines the candidate push message corresponding to the verified message task as the message to be pushed, and calls the message RPC to process the message task.

[0100] In step S340, the message RPC calls the frequency control verification module again to verify the message task corresponding to the message to be pushed based on the message to be pushed corresponding to the received message task.

[0101] Specifically, the process of verifying the message task in this step is similar to the verification in the above step S320, and will not be described in detail in this embodiment.

[0102] It should be noted that, since the above step S320 is based on the verification of the message tasks in the message queue, only the tasks that have exceeded the frequency control threshold can be preliminarily intercepted, and for concurrent tasks that have not exceeded the frequency control threshold, there may be a situation where they are missed. Based on this, this embodiment verifies the message tasks by calling the frequency control verification module again through the message RPC, so that the above concurrent tasks can be accurately intercepted. And because the message tasks arriving at the message RPC have been verified as mentioned above, the processing pressure of the message RPC can be reduced and the processing efficiency can be improved.

[0103] In step S350, the to-be-pushed message corresponding to the message task that has passed the message RPC verification again is determined as the target push message, and the count of the received messages of the target account identifier is updated to obtain an updated count.

[0104] Specifically, when the message RPC is verified again, it means that the to-be-pushed message corresponding to the message task can be pushed to the user corresponding to the target account identifier. Therefore, the to-be-pushed message corresponding to the message task is determined as the target push message. The count of the received messages of the target account identifier is updated to obtain an updated count. The updated count is the cumulative count of the last successful message push to the user plus this push. For example, if the cumulative count of the last successful message push to the target account identifier is K, the updated count of this push is K+1.

[0105] In step S360, the server calls the message storage module to store the target push message that has passed the re-verification into the storage space corresponding to the target account identifier.

[0106] Specifically, the server calls the message storage module to store the target push message that has passed the re-verification into the storage space corresponding to the target account identifier, thereby completing the push of the message task. The user corresponding to the target account identifier can access the message page (i.e., message Tab) through the client, pull the message feed, and display the message in the corresponding storage space based on the message rendering and display strategy module.

[0107] In step S370, when the verification fails, it means that the corresponding message task push fails.

[0108] Specifically, when the verification fails, it means that the corresponding message task push fails. The server can also feedback the push result to the corresponding business party based on the failed message task, so as to facilitate the business party to perform corresponding processing.

[0109] Since the push process is verified twice, it can not only avoid the problem of message flooding on the user side, but also reduce the processing pressure of the message RPC and improve the processing efficiency.

[0110] It should be understood that although Figure 1-Figure 4 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 1-Figure 4 At least part of the steps may include multiple steps or multiple stages. These steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed in turn or alternately with other steps or at least part of the steps or stages in other steps.

[0111] It can be understood that the same / similar parts between the various embodiments of the above method in this specification can refer to each other, and each embodiment focuses on the differences from other embodiments. For related points, please refer to the description of other method embodiments.

[0112] Figure 5 FIG. 1 is a block diagram of a message push device according to an exemplary embodiment. Figure 5 The device includes a message acquisition module 502 to be pushed, a count acquisition module 504, a verification module 506 and a message storage module 508.

[0113] The message acquisition module 502 is configured to acquire the message to be pushed, wherein the message to be pushed carries the target account identifier to be pushed;

[0114] The count acquisition module 504 is configured to execute, according to a pre-configured message frequency control dimension, acquiring a count of received messages of the target account identifier under the message frequency control dimension at a current moment;

[0115] A verification module 506 is configured to verify the count according to a pre-configured message frequency control threshold corresponding to the message frequency control dimension;

[0116] The message storage module 508 is configured to determine that the message to be pushed is a target push message when the verification is passed, and store the target push message in the storage space corresponding to the target account identifier.

[0117] In an exemplary embodiment, the module for acquiring messages to be pushed is also configured to execute: acquiring candidate push messages from the message queue, the candidate push messages carrying the corresponding target account identifier for the push; acquiring the count of messages received by the target account identifier under the message frequency control dimension according to the pre-configured message frequency control dimension; verifying the count according to the pre-configured message frequency control threshold corresponding to the message frequency control dimension; and when the verification passes, determining that the candidate push message is the message to be pushed.

[0118] In an exemplary embodiment, the device further includes a count update module configured to execute: updating the count of received messages of the target account identifier under the message frequency control dimension to obtain an updated count.

[0119] In an exemplary embodiment, the message frequency control dimension includes an account dimension and at least one corresponding first frequency control period; the count acquisition module is also configured to execute: determining the target account dimension and at least one corresponding target first frequency control period corresponding to the target account identifier according to the target account identifier and the pre-configured account dimension and at least one corresponding first frequency control period; obtaining the first count of received messages within at least one target first frequency control period under the target account dimension by the target account identifier at the current moment.

[0120] In an exemplary embodiment, the message frequency control dimension also includes a message type dimension and at least one corresponding second frequency control period; the message to be pushed also carries a corresponding message type; the count acquisition module is also configured to execute: according to the message type of the message to be pushed, and the pre-configured message type dimension and at least one corresponding second frequency control period, determine the target message type dimension and at least one corresponding target second frequency control period to which the message to be pushed belongs; obtain the second count of messages corresponding to the target message type dimension in the received messages of the target account identifier within the at least one target second frequency control period at the current moment.

[0121] In an exemplary embodiment, the message frequency control dimension also includes a message box dimension and at least one corresponding third frequency control cycle; the count acquisition module is also configured to execute: according to the message type of the message to be pushed, and the pre-configured message box dimension and at least one corresponding third frequency control cycle, determine the target message box and at least one corresponding target third frequency control cycle of the message to be pushed relative to the target account identifier; obtain the third count of the target account identifier receiving messages through the target message box within the at least one target third frequency control cycle at the current moment.

[0122] In an exemplary embodiment, the device also includes a message frequency control configuration information acquisition module, which is configured to execute: acquiring and storing message frequency control configuration information, the message frequency control configuration information including a message frequency control dimension and a corresponding message frequency control threshold; the message frequency control dimension including at least one of an account dimension, a message type dimension, and a message box dimension.

[0123] In an exemplary embodiment, the verification module is further configured to execute: when the count is less than a message frequency control threshold corresponding to the message frequency control dimension, determining that the verification is passed.

[0124] In an exemplary embodiment, the verification module is further configured to execute: when the count is greater than or equal to the message frequency control threshold of the corresponding message frequency control dimension, determine that the verification fails; when the verification fails, determine that the message push fails.

[0125] Figure 6 is a block diagram of an electronic device S00 for message push according to an exemplary embodiment. For example, the electronic device S00 may be a server. Figure 6 The electronic device S00 includes a processing component S20, which further includes one or more processors, and a memory resource represented by a memory S22 for storing instructions executable by the processing component S20, such as an application. The application stored in the memory S22 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component S20 is configured to execute the instructions to perform the above method.

[0126] The electronic device S00 may further include: a power supply component S24 configured to perform power management of the electronic device S00, a wired or wireless network interface S26 configured to connect the electronic device S00 to a network, and an input / output (I / O) interface S28. The electronic device S00 may operate based on an operating system stored in the memory S22, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD or the like.

[0127] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory S22 including instructions, and the above instructions can be executed by a processor of the electronic device S00 to complete the above method. The storage medium can be a computer-readable storage medium, for example, the computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0128] In an exemplary embodiment, a computer program product is further provided. The computer program product includes instructions. The instructions can be executed by a processor of the electronic device S00 to complete the above method.

[0129] It should be noted that the above-mentioned devices, electronic devices, computer-readable storage media, computer program products, etc. may also include other implementation methods according to the description of the method embodiments. The specific implementation methods can refer to the description of the relevant method embodiments, which will not be described one by one here.

[0130] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the claims.

[0131] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A message push method, characterized in that: The method is applied to a server, and the method comprises: Obtain a candidate push message from the message queue, wherein the candidate push message carries a target account identifier for the corresponding push; According to a pre-configured message frequency control dimension, obtaining a count of messages received by the target account identifier under the message frequency control dimension; According to a pre-configured message frequency control threshold corresponding to the message frequency control dimension, the count is verified, and when the verification passes, the candidate push message is determined to be a message to be pushed and is handed over to the message RPC for processing; Call the message RPC to obtain the count of received messages of the target account identifier under the message frequency control dimension at the current moment according to the message frequency control dimension; the message frequency control dimension refers to a dimension that limits the number of messages received by a user within a frequency control period, including at least one of an account dimension, a message type dimension, and a message box dimension. The message box is a form in which messages of the same business are converged into one box to be displayed to the user based on certain business rules; When it is determined according to the message RPC that the count is less than the message frequency control threshold of the corresponding message frequency control dimension, it is determined that the verification is passed; When the verification passes, it is determined that the message to be pushed is a target push message, and the message RPC is called to store the target push message in the storage space corresponding to the target account identifier.

2. The method according to claim 1, characterized in that The method further comprises: Message frequency control configuration information is obtained, where the message frequency control configuration information includes a message frequency control dimension and a corresponding message frequency control threshold.

3. The method according to claim 1, characterized in that After the verification is passed and it is determined that the message to be pushed is a target push message, the method further includes: The count of messages received by the target account identifier under the message frequency control dimension is updated to obtain an updated count.

4. The method according to any one of claims 1 to 3, characterized in that: The message frequency control dimension includes an account dimension and at least one corresponding first frequency control period; and obtaining, according to the message frequency control dimension, a count of received messages of the target account identifier under the message frequency control dimension at the current moment, including: Determine, according to the target account identifier, and the pre-configured account dimension and the corresponding at least one first frequency control period, a target account dimension and the corresponding at least one first frequency control period corresponding to the target account identifier; Obtain a first count of messages received by the target account identifier at a current moment within at least one target first frequency control period under the target account dimension.

5. The method according to claim 4, characterized in that The message frequency control dimension also includes a message type dimension and at least one corresponding second frequency control period; the message to be pushed also carries a corresponding message type; and obtaining, according to the message frequency control dimension, a count of messages received by the target account identifier under the message frequency control dimension at the current moment, including: Determine, according to the message type of the message to be pushed, and the pre-configured message type dimension and the corresponding at least one second frequency control period, the target message type dimension to which the message to be pushed belongs and the corresponding at least one second frequency control period; Obtain a second count of messages corresponding to the target message type dimension in received messages for the target account identifier within the at least one target second frequency control period at the current moment.

6. The method according to claim 5, characterized in that The message frequency control dimension also includes a message box dimension and at least one corresponding third frequency control period; and obtaining, according to the message frequency control dimension, a count of received messages of the target account identifier under the message frequency control dimension at the current moment, including: Determine, according to the message type of the message to be pushed, and the pre-configured message box dimension and the corresponding at least one third frequency control period, a target message box of the message to be pushed relative to the target account identifier and the corresponding at least one third frequency control period; A third count of messages received by the target account identifier through the target message box within the at least one target third frequency control period at the current moment is obtained.

7. A message push device, characterized in that: The device is applied to a server and includes: The module for acquiring messages to be pushed is configured to execute acquiring candidate push messages from the message queue, the candidate push messages carrying the corresponding target account identifier for push; acquiring the count of messages received by the target account identifier under the message frequency control dimension according to the pre-configured message frequency control dimension; verifying the count according to the pre-configured message frequency control threshold corresponding to the message frequency control dimension, and when the verification passes, determining that the candidate push message is a message to be pushed and handing it over to the message RPC for processing; The count acquisition module is configured to execute the call of the message RPC and obtain the count of the received messages of the target account identifier under the message frequency control dimension at the current moment according to the message frequency control dimension; the message frequency control dimension refers to the dimension that limits the number of messages received by the user within the frequency control period, including at least one of the account dimension, the message type dimension and the message box dimension, and the message box is a form in which messages of the same business are converged into one box to be displayed to the user based on certain business rules; A verification module is configured to determine that the verification is passed when it is determined according to the message RPC that the count is less than the message frequency control threshold of the corresponding message frequency control dimension; The message storage module is configured to execute, when the verification is passed, determining that the message to be pushed is a target push message, calling the message RPC to store the target push message in the storage space corresponding to the target account identifier.

8. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the message pushing method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: When the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the message pushing method as described in any one of claims 1 to 6.

10. A computer program product, comprising instructions, characterized in that: When the instruction is executed by a processor of an electronic device, the electronic device is enabled to execute the message pushing method as described in any one of claims 1 to 6.

Images