CN115022264A - Message pushing method and device, electronic equipment and computer readable storage medium - Google Patents
Message pushing method and device, electronic equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN115022264A CN115022264A CN202210736893.0A CN202210736893A CN115022264A CN 115022264 A CN115022264 A CN 115022264A CN 202210736893 A CN202210736893 A CN 202210736893A CN 115022264 A CN115022264 A CN 115022264A
- Authority
- CN
- China
- Prior art keywords
- message
- frequency control
- dimension
- target
- pushed
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 54
- 238000012795 verification Methods 0.000 claims abstract description 35
- 238000004590 computer program Methods 0.000 claims abstract description 7
- 238000012545 processing Methods 0.000 description 13
- 238000010586 diagram Methods 0.000 description 6
- 230000006399 behavior Effects 0.000 description 5
- 238000011217 control strategy Methods 0.000 description 5
- 230000000694 effects Effects 0.000 description 5
- 230000001186 cumulative effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The disclosure relates to a message pushing method, a message pushing device, an electronic device, a computer readable storage medium and a computer program product. The method comprises the steps of obtaining a message to be pushed, verifying the count of the message received by a target account identifier under the message frequency control dimension at the current moment according to the message frequency control dimension configured in advance and a corresponding message frequency control threshold, determining the message to be pushed as the target push message when the verification is passed, and finishing pushing the target push message to the target account identifier. In this embodiment, before pushing a message to a target account identifier, according to a preconfigured message frequency control dimension and a message frequency control threshold corresponding to the message frequency control dimension, a count of messages received by the target account identifier at the message frequency control dimension acquired by the server at the current time needs to be checked, and message pushing is performed only when the check is passed.
Description
Technical Field
The present disclosure relates to internet technologies, and in particular, to a message pushing method, apparatus, electronic device, computer-readable storage medium, and computer program product.
Background
With the development of internet technology, various applications have come into play. Typically, applications may push different messages to users based on different business desires. For example, a production promotion message may be pushed to a user based on a production service expectation, an activity-related message may be pushed to a user based on an growth service expectation, a live broadcast on-off message may be pushed to a user based on a live broadcast service expectation, and the like. Therefore, if the message platform does not limit the number of messages received by the user, different applications may frequently push multiple messages to the user to achieve their business objectives, thereby flooding the user side with messages.
In the related art, a common message frequency control method is to restrict the number of messages received by a user to a certain type, for example, restrict an application program to only push one xx type of message to the user in one day.
However, the message frequency control method in the related art can only make a constraint on the sender, and can only restrict the number of messages of a certain type received by the user in a certain period. For example, when there are tens of service directions pushing messages to users during a certain activity period, although the sending party has a frequency limit of 2 pieces/day, the users can still receive dozens or even hundreds of pushing messages each day. Therefore, the current message frequency control method cannot well solve the problem of message flooding at the user end.
Disclosure of Invention
The present disclosure provides a message pushing method, device, electronic device, computer readable storage medium and computer program product, so as to solve at least the problem that the message frequency control method in the related art cannot well solve the message flooding at the user end. The technical scheme of the disclosure is as follows:
according to a first aspect of the embodiments of the present disclosure, a message pushing method is provided, including:
acquiring a message to be pushed, wherein the message to be pushed carries a target account identifier to be pushed;
according to a pre-configured message frequency control dimension, obtaining the count of the received messages of the target account identifier under the message frequency control dimension at the current moment;
acquiring a message frequency control threshold value corresponding to the message frequency control dimension, which is configured in advance, and determining that the check is passed when the count is smaller than the message frequency control threshold value of the corresponding message frequency control dimension;
and when the verification is passed, determining that the message to be pushed is a target push message, and storing the target push message in a storage space corresponding to the target account identifier.
In one embodiment, the obtaining the message to be pushed includes: acquiring candidate push messages from a message queue, wherein the candidate push messages carry corresponding pushed target account identifications; according to the message frequency control dimension configured in advance, obtaining the count of the received messages of the target account identifier under the message frequency control dimension; checking the count according to a message frequency control threshold value which is configured in advance and corresponds to the message frequency control dimension; and when the verification is passed, determining the candidate push message as a message to be pushed.
In one embodiment, after the checking is passed and the message to be pushed is determined to be the target push message, the method further includes: and updating the count of the received messages of the target account identifier under the message frequency control dimension to obtain the updated count.
In one embodiment, the message frequency control dimension comprises an account dimension and at least one corresponding first frequency control period; the obtaining of the count of the received messages of the target account identifier under the message frequency control dimension at the current moment according to the pre-configured message frequency control dimension includes: according to the target account identification, the account dimension configured in advance and at least one corresponding first frequency control period, determining the target account dimension corresponding to the target account identification and at least one corresponding first frequency control period; and acquiring a first count of received messages of the target account identification in at least one target first frequency control period of the target account dimension at the current moment.
In one embodiment, the message frequency control dimension further includes a message type dimension and a corresponding at least one second frequency control period; the message to be pushed also carries a corresponding message type; the obtaining of the count of the received messages of 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 a target message type dimension to which the message to be pushed belongs and at least one corresponding target second frequency control period according to the message type of the message to be pushed, the message type dimension configured in advance and the at least one corresponding second frequency control period; and acquiring a second count of messages corresponding to the target message type dimension in the received messages in the at least one target second frequency control period of the target account identifier at the current moment.
In one embodiment, the message frequency control dimension further comprises a message box dimension and at least one corresponding third frequency control period; the obtaining of the count of the received messages of 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 a target message box of the message to be pushed relative to the target account identifier and at least one corresponding target third frequency control period according to the message type of the message to be pushed, the preset message box dimension and at least one corresponding third frequency control period; and acquiring a third count of messages received by the target message box within the at least one target third frequency control period of the target account identifier at the current moment.
In one embodiment, the method further comprises: acquiring and storing message frequency control configuration information, wherein the message frequency control configuration information comprises message frequency control dimensions and corresponding message frequency control thresholds; the message frequency control dimension includes at least one of an account dimension, a message type dimension, and a message box dimension.
In one embodiment, the method further comprises: determining that the check fails when the count is greater than or equal to a message frequency control threshold of a corresponding message frequency control dimension; and when the check fails, determining that the message pushing fails.
According to a second aspect of the embodiments of the present disclosure, there is provided a message pushing apparatus, including:
the system comprises a to-be-pushed message acquisition module, a to-be-pushed message acquisition module and a to-be-pushed message acquisition module, wherein the to-be-pushed message acquisition module is configured to execute acquisition of a to-be-pushed message, and the to-be-pushed message carries a target account identifier to be pushed;
the counting acquisition module is configured to execute counting 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 configured in advance;
the checking module is configured to execute the steps of obtaining a message frequency control threshold value corresponding to the message frequency control dimension, and when the count is smaller than the message frequency control threshold value of the corresponding message frequency control dimension, determining that the checking is passed;
and the message storage module is configured to determine that the message to be pushed is the target push message when the verification is passed, and store the target push message in a storage space corresponding to the target account identifier.
According to a third aspect of the embodiments of the present disclosure, there is provided an electronic apparatus including: a processor; a memory for storing the processor-executable instructions; wherein the processor is configured to execute the instructions to implement the message pushing method of any of the first aspects above.
According to a fourth aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium, wherein instructions, when executed by a processor of an electronic device, enable the electronic device to perform the message pushing method according to any one of the first aspect above.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product, which includes instructions that, when executed by a processor of an electronic device, enable the electronic device to perform the message pushing method according to any one of the first aspects above.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects: the server acquires the message to be pushed, acquires the count of the received message of the target account identifier under the message frequency control dimension at the current moment according to the message frequency control dimension configured in advance, verifies the count according to the message frequency control threshold value corresponding to the message frequency control dimension configured in advance, determines the message to be pushed as the target push message when the verification is passed, and stores the target push message in the storage space corresponding to the target account identifier, thereby completing the pushing of the target push message to the target account identifier. In this embodiment, before pushing a message to a target account identifier, according to a preconfigured message frequency control dimension and a message frequency control threshold corresponding to the message frequency control dimension, a count of messages received by the target account identifier at the message frequency control dimension acquired by the server at the current time needs to be checked, and message pushing is performed only when the check is passed.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.
Fig. 1 is a flowchart illustrating a message pushing method according to an exemplary embodiment.
Fig. 2 is a diagram illustrating a step of acquiring a message to be pushed according to an exemplary embodiment.
Fig. 3 is a flowchart illustrating a message push method according to another exemplary embodiment.
Fig. 4 is a schematic diagram of a message server shown in accordance with an example embodiment.
Fig. 5 is a block diagram illustrating a message pushing device according to an example embodiment.
FIG. 6 is a block diagram illustrating an electronic device in accordance with an example embodiment.
Detailed Description
In order to make the technical solutions of the present disclosure better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
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 for presentation, analyzed data, etc.) referred to in the present disclosure are both information and data that are authorized by the user or sufficiently authorized by various parties.
In one embodiment, as shown in fig. 1, a message pushing method is provided, and this embodiment is illustrated by applying the method to a server. In particular, the server may be a message server. In this embodiment, the method may include the steps of:
in step S110, a message to be pushed is acquired.
And the message to be pushed carries the target account identifier to be pushed. Specifically, the message to be pushed may be a message to be pushed to the target account, which is acquired by the server, that is, a message corresponding to a message task processed by the server through a Remote Procedure Call (RPC) Call. The target account may be a designated receiving account of the message to be pushed, and the target account identifier refers to account information corresponding to the target account, and may be, for example, a nickname of the user, an Identity document (Identity document), a mobile phone number of the user, and the like. The target account identification is typically unique and is used to distinguish between different user accounts.
For example, messages include, but are not limited to, activity notification messages, service notification messages, authored incentive messages, live notification messages, user behavior triggered messages, and the like. User behavior includes, but is not limited to, likes, favorites, stamps, comments, @, etc. Specifically, if user a points up with user B's work, the server will push a message of points up from user a to user B. The approval message is a message to be pushed, and the user B receiving the approval message is a target account identifier.
In step S120, according to the preconfigured message frequency control dimension, a count of the received messages of the target account identifier in the message frequency control dimension at the current time is obtained.
The message frequency control dimension refers to an angle for limiting the number of messages received by a user. For example, from the perspective of the user, the number of messages that the user receives in the period T may be limited; for example, from the perspective of message type, the number of messages that the user receives the X-type messages in the period T may be limited; for example, from the perspective of a message box, the number of messages that a user receives from a single message box within a period T may be limited, where the message box converges messages of the same service to a box for presentation to the user based on certain service rules.
In this embodiment, to avoid flooding of the user-side messages, the message frequency control dimension may be configured in advance at the server side. Therefore, after the server obtains the message to be pushed, the count of the received message of the target account identifier under the message frequency control dimension at the current moment can be obtained according to the message frequency control dimension configured in advance. The current moment is the moment when the server acquires the message to be pushed to the target account identifier. The count of the messages received by the target account identifier may be a count of the message received by the target account identifier in a dimension corresponding to a preconfigured message frequency control dimension. For example, if the preconfigured message frequency control dimension is from the user perspective, that is, the number of messages that the user receives messages in the period T is limited, the count is counted based on the user perspective, and the target account identifies the number of messages that have received messages in the period T. And if the pre-configured message frequency control dimension is other dimensions, acquiring the message quantity of the received message of the target account identifier based on the corresponding dimension.
In step S130, a message frequency control threshold corresponding to the message frequency control dimension configured in advance is obtained, and when the count is smaller than the message frequency control threshold corresponding to the message frequency control dimension, it is determined that the check is passed.
Wherein the message frequency control threshold is a maximum value of a number of messages corresponding to the message frequency control dimension. For example, if the preconfigured message frequency control dimension is from the perspective of the user, that is, the number of messages that the user receives messages in the period T is limited, the message frequency control threshold is the maximum value of the preconfigured number of messages that the user receives messages in the period T. Similarly, if the preconfigured message frequency control dimension is from the perspective of the message type, that is, the number of messages for the user to receive the X-type messages in the period T is limited, the message frequency control threshold is the maximum value of the number of messages for the preconfigured user to receive the X-type messages in the period T.
In this embodiment, the server checks the count of the received messages of the target account identifier in the message frequency control dimension obtained at the current time according to the message frequency control dimension configured in advance and the message frequency control threshold corresponding to the message frequency control dimension, that is, checks whether the current count is smaller than the message frequency control threshold corresponding to the message frequency control dimension, and determines that the check is passed when the current count is smaller than the message frequency control threshold corresponding to the message frequency control dimension.
For example, if the preconfigured message frequency control dimension and the corresponding message frequency control threshold are d1, the maximum value of the number of messages received by the user in the period T indicates that the user can only receive d1 messages at most in the period T. If the count of the number of messages received by the target account id acquired by the server at the current time within the period T is b1, that is, the user cumulatively receives b1 messages at the current time, if b1 is smaller than d1, it indicates that the user can still receive messages, and therefore, the verification is determined to be passed. And then the message to be pushed can be determined as a target push message, and the target push message is stored in a storage space corresponding to the target account identifier, so that message pushing based on the message frequency control dimension and the message frequency control threshold value is realized, and message flooding at a user side is avoided.
In step S140, when the verification passes, it is determined that the message to be pushed is the target push message, and the target push message is stored in the storage space corresponding to the target account identifier.
The target push message is a message which can be finally pushed to the target account identifier. Specifically, if the current count does not reach the corresponding message frequency control threshold, it indicates that the user can continue to receive messages, and therefore, the server determines the message to be pushed as a target push message and stores the target push message in the storage space corresponding to the target account identifier after the verification is passed, that is, the process of pushing the target push message to the target account identifier by using the RPC message is completed.
In the message pushing method, the server obtains the message to be pushed, obtains the count of the received message of the target account identifier under the message frequency control dimension at the current moment according to the message frequency control dimension configured in advance, verifies the count according to the message frequency control threshold value corresponding to the message frequency control dimension configured in advance, determines the message to be pushed as the target pushing message when the verification is passed, and stores the target pushing message in the storage space corresponding to the target account identifier, thereby completing the pushing of the target pushing message to the target account identifier. In this embodiment, before pushing a message to a target account identifier, according to a preconfigured message frequency control dimension and a message frequency control threshold corresponding to the message frequency control dimension, a count of messages received by the target account identifier at the message frequency control dimension acquired by the server at the current time needs to be checked, and message pushing is performed only when the check is passed.
In an exemplary embodiment, the method may further 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 check is not passed; and when the verification fails, determining that the message pushing fails.
Specifically, still in the foregoing embodiment, if the preconfigured message frequency control dimension and the corresponding message frequency control threshold are, the maximum value of the number of messages received by the user in the period T is d 1. If the count of the number of messages received by the target account identifier acquired by the server at the current moment in the period T is b1, if b1 is greater than d1 or b1 is equal to d1, it indicates that the number of messages received by the user has reached the regulatory maximum value, that is, the user cannot continue to receive messages, and therefore, the verification is determined not to pass. Since the user may not continue to receive messages, it may be determined that the message push failed, i.e., that the message to be pushed is pushed to the user failed. Therefore, the user is prevented from being disturbed by too many messages, and the user experience is improved.
In an exemplary embodiment, in step S140, after determining that the message to be pushed is the target push message when the check is passed, the method may further include: and updating the count of the received messages of the target account identifier under the message frequency control dimension to obtain the updated count.
Specifically, when the verification passes, it may be determined that the current message to be pushed is the target push message, that is, it indicates that the target push message may be pushed to the target account identifier. Therefore, in order to obtain an accurate count of messages received by a user during subsequent message pushing, after the verification is passed and the message to be pushed is determined to be the target message pushing, the server can update the count of the received messages of the target account identifier under the message frequency control dimension, namely, the corresponding count is updated by adding 1, so that the updated count is obtained.
It can be understood that, for each message push, the count obtained during verification is the count updated after the last verification is successful, and the count updated during the current push is used for verification during the next message push. Therefore, for each message pushing, when the verification is passed, the corresponding count can be updated in time, so that the concurrency problem can not be caused, and the accurate count of the message received by the user can be obtained during each message pushing.
In an exemplary embodiment, as shown in fig. 2, in step S110, the obtaining of the message to be pushed may specifically be implemented by the following steps:
in step S210, candidate push messages are obtained from the message queue.
Wherein the message queue may be a container for holding message tasks that want to send candidate push messages to the user. The candidate push message carries a target account identifier corresponding to the push. In particular, the candidate push message may be a message that the service party wants to send to the user.
In this embodiment, when a service party wants to push a message to a user, the service party applies for the message to a server, and after the application is passed, pushes a candidate push message to a specified user by invoking a message push SDK (Software Development Kit) provided by the server, and the SDK forwards a message task for pushing the candidate push message to a message queue. And the server realizes the pushing of the candidate pushing message by consuming the message task in the message queue. Specifically, when the server consumes the message task in the message queue, first, the candidate push message corresponding to the message task is obtained from the message queue.
In step S220, according to the preconfigured message frequency control dimension, a count of the received messages of the target account identifier under the message frequency control dimension is obtained.
In this embodiment, the server obtains a count of messages received by the target account identifier in the message frequency control dimension based on the candidate push messages corresponding to the message task obtained from the message queue and according to the message frequency control dimension configured in advance, and then verifies the count through the subsequent steps. And only if the verification is passed, the candidate push message corresponding to the message task is taken as the message to be pushed and is processed by the message RPC, so that the processing pressure of the message RPC is reduced.
In step S230, the count is checked according to a pre-configured message frequency control threshold corresponding to the message frequency control dimension.
The message frequency control dimension may refer to an angle that defines the number of messages received by a user. The message frequency control threshold is then the maximum value of the number of messages corresponding to the message frequency control dimension.
In this embodiment, the server checks the count of the received messages of the target account identifier under the currently acquired message frequency control dimension according to the message frequency control dimension configured in advance and the message frequency control threshold corresponding to the message frequency control dimension, that is, checks whether the current count reaches the corresponding message frequency control threshold. And if the current count is smaller than the message frequency control threshold value of the corresponding message frequency control dimension, determining that the verification is passed. And if the count is greater than or equal to the message frequency control threshold value of the corresponding message frequency control dimension, determining that the check is not passed. Therefore, whether the candidate push message is to be processed by the message RPC is determined according to the checking result so as to relieve the processing pressure of the message RPC. The current time refers to the time when the server acquires the candidate push message corresponding to the message task from the message queue, and the time is earlier than the time when the server acquires the message to be pushed to the target account identifier. Therefore, the server acquires the counts twice at different timings, and if the counts are not updated during this period, the counts acquired twice are the same, and if the counts are updated during this period, the counts acquired twice are different.
In step S240, when the check is passed, the candidate push message is determined to be a message to be pushed.
The message to be pushed is a message to be pushed to the target account and acquired by the server. Specifically, if the current count does not reach the corresponding message frequency control threshold, it indicates that the user can continue to receive messages, so that the server determines the candidate push messages as messages to be pushed after the verification is passed, and delivers the messages to the message RPC for continuous processing.
In the above embodiment, the server obtains, based on the candidate push message corresponding to the message task obtained from the message queue, a count of the received messages of the target account identifier under the message frequency control dimension according to the message frequency control dimension configured in advance, and then verifies the count according to the message frequency control threshold value corresponding to the message frequency control dimension configured in advance. And only when the verification is passed, determining that the candidate push message corresponding to the message task is the message to be pushed, and handing the message to the message RPC for continuous processing. Because the message tasks are filtered based on the message frequency control dimension, the corresponding message frequency control threshold and the count of the messages received by the user before the message RPC is processed, the processing pressure of the message RPC can be reduced while the message of the user side is prevented from flooding.
In an exemplary embodiment, before acquiring the candidate push message from the message queue in step S210, the method may further include: and acquiring and storing message frequency control configuration information. The message frequency control configuration information comprises a message frequency control dimension and a corresponding message frequency control threshold. In particular, the message frequency control dimension may refer to an angle defining the number of messages that a user receives a message. 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 then the maximum value of the number of messages corresponding to the message frequency control dimension.
In particular, the account dimension may refer to the limitation of the number of messages that the user receives within the period T from the user's perspective. For example, the maximum value of the number of messages that the user receives the message within the period T1 may be defined as n1, and the maximum value of the number of messages that the user receives the message within the period T2 may be defined as n 2. The message type dimension may be from the perspective of message type, that is, the number of messages that the user receives X types of messages in the period T is limited. For example, the maximum value of the number of messages for which the user receives the type X messages in the period T3 may be defined as n3, and the maximum value of the number of messages for which the user receives the type X messages in the period T4 may be defined as n 4. The message box dimension may then be from a message box perspective, i.e. defining the number of messages a user receives from a single message box within a period T. For example, the maximum number of messages that the user receives from a single message box within the period T5 may be defined as n5, and the maximum number of messages that the user receives from a single message box within the period T6 may be defined as n 6. The time periods T1, T2, T3, T4, T5, and T6, and the corresponding message frequency control thresholds n1, n2, n3, n4, n5, and n6 may all be set to specific values according to actual needs, which is not limited in this embodiment.
In this embodiment, before the server obtains the candidate push message from the message queue, the server first obtains and stores the message frequency control configuration information, so as to provide a basis for subsequent frequency control.
In an exemplary embodiment, the preconfigured message frequency control dimension includes an account dimension and a corresponding at least one first frequency control period; then, according to the pre-configured message frequency control dimension, obtaining the count of the received messages of the target account identifier under the message frequency control dimension at the current moment, including: determining a target account dimension corresponding to the target account identifier and at least one corresponding target first frequency control period according to the target account identifier, and a preconfigured account dimension and at least one corresponding first frequency control period; and acquiring a first count of received messages of the target account identifier at the current moment in at least one target first frequency control period of the target account dimension.
For example, if the preconfigured account dimension and the corresponding at least one first frequency control period include: a limit on the number of messages that the same user receives within a period T1, and a limit on the number of messages that the same user receives within a period T2, where T1 is different from T2. Then, obtaining a first count of received messages of the current time target account identifier in at least one target first frequency control period of the target account dimension, specifically including: and acquiring a count C1 that the target account identifier at the current moment receives the message in the period T1, acquiring a count C2 that the target account identifier at the current moment receives the message in the period T2, and taking C1 and C2 as a first count.
In one scenario, if the preconfigured account dimension and the corresponding at least one first frequency control period include: a definition of the number of messages received by a user of account type Y1 in the period T1, a definition of the number of messages received by a user of account type Y2 in the period T2, and a definition of the number of messages received by a user of account type Y3 in the period T3. Then, obtaining a first count of received messages of the current time when the target account identifier is in at least one target first frequency control period of the target account dimension, specifically including: firstly, the account type corresponding to the target account identifier is determined according to the target account identifier, and if the account type corresponding to the target account identifier is determined to be Y2, the count of the messages received by the target account identifier in the period T2 at the current moment is further acquired as a first count. The account type may be determined based on at least one of different account levels, historical behaviors of the account, and the like, which is not limited in this embodiment.
It can be understood that different frequency control periods can be configured for the same account type, and the number of messages received in different frequency control periods is limited. For example, if the account type corresponding to the target account id is Y1, the preconfigured account dimension and the corresponding at least one first frequency control period include: a limit on the number of messages a user of account type Y1 receives within the period f1, and a limit on the number of messages a user of account type Y1 receives within the period f 2. Then, obtaining a first count of received messages of the current time target account identifier in at least one target first frequency control period of the target account dimension, specifically including: and acquiring a count m1 that the target account identifier at the current moment receives the message in the period f1, acquiring a count m2 that the target account identifier at the current moment receives the message in the period f2, and taking m1 and m2 as a first count.
In the embodiment, the message frequency control is performed based on the account dimension, so that different frequency control strategies can be adopted for control according to different accounts, and the flexibility of frequency control is improved.
In an exemplary embodiment, the preconfigured message frequency control dimension may further include a message type dimension and a corresponding at least one second frequency control period; the message to be pushed also carries the corresponding message type. Obtaining 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 configured in advance, wherein the count comprises the following steps: determining a target message type dimension to which the message to be pushed belongs and at least one corresponding target second frequency control period according to the message type of the message to be pushed, the message type dimension configured in advance and the at least one corresponding second frequency control period; and acquiring a second count of the messages corresponding to the type dimension of the target message in the received messages in at least one target second frequency control period of the target account identifier at the current moment.
The message type includes, but is not limited to, an activity notification type message, a service notification type message, a composition incentive type message, a live notification type message, a user behavior trigger type message, and the like.
For example, if the preconfigured message type dimension and the corresponding at least one second frequency control period include: a limit on the number of messages for which the user receives active notification class messages within the period T1, a limit on the number of messages for which the user receives service notification class messages within the period T2, and a limit on the number of messages for which the user receives authoring incentive class messages within the period T3, etc. Wherein T1, T2 and T3 may be the same or different. If the message type carried by the message to be pushed is an active notification type message, acquiring the count of the received message of the target account identifier under the message frequency control dimension at the current moment, specifically comprising: firstly, 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 an active notification type message dimension, and further acquiring the number of messages, namely a second count, of the user receiving the active notification type message in the period T1, corresponding to the target account identification at the current moment, based on that at least one corresponding target second frequency control period is the period T1.
In a scene, different frequency control periods can be configured in advance for the same message type dimension, the number of messages of the same type received in different frequency control periods is limited, and then message frequency control can be performed according to different frequency control periods of the same message type, so that a multi-dimensional configurable frequency control scheme is realized.
In the above embodiment, the message frequency control is performed based on the message type dimension, so that control can be performed by adopting different frequency control strategies according to different message types, a multi-dimensional configurable frequency control scheme can be realized, and the flexibility and diversity of frequency control are further improved.
In an exemplary embodiment, the preconfigured message frequency control dimensions may further include a message box dimension and a corresponding at least one third frequency control period. Obtaining 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 configured in advance, wherein the count comprises the following steps: determining a target message box of the message to be pushed relative to the target account identifier and at least one corresponding target third frequency control period according to the message type of the message to be pushed, the preset message box dimension and at least one corresponding third frequency control period; and acquiring a third count of messages received by the target message box in at least one target third frequency control period of the target account identifier at the current moment.
The message box is a form that the messages of the same service are converged to a box to be displayed to a user based on a certain service rule. For example, for operation-class service messages such as activity notification messages, authoring incentive messages, live notification messages, service notification messages, etc., it is possible to converge to the same box for presentation to the user. And for the user behavior messages of the function class, such as praise, collection, one stamp, comment, @ and other messages, the messages can be converged to the same box to be displayed for the user.
The message box dimension may be the frequency control of the number of messages received from a single message box from the message box perspective. For example, if the preconfigured message box dimensions and the corresponding at least one third frequency control period include: the number of messages the user receives from message box Z1 during period T1, the number of messages the user receives from message box Z2 during period T2, and so on. Wherein T1 and T2 can be the same or different, and Z1 and Z2 are different message boxes.
Obtaining the count of the received messages of the target account identifier under the message frequency control dimension at the current moment, which specifically includes: firstly, a corresponding target message box is determined according to the message type of the message to be pushed. If the target message box corresponding to the message to be pushed is determined to be Z1 according to the message type of the message to be pushed in the embodiment, the number of messages received by the target account identifier from the message box Z1 in the period T1 at the current moment, that is, the third count, is further obtained.
In a scene, different frequency control periods can be configured in advance for the same message box dimension, the number of messages received from the same message box in different frequency control periods is limited, and then message frequency control can be performed according to different frequency control periods under the same message box, so that a multi-dimensional configurable frequency control scheme is realized.
In the above embodiment, the message frequency control is performed based on the message instance dimension, so that control can be performed by adopting different frequency control strategies according to different message boxes, a multi-dimensional configurable frequency control scheme can be realized, and the flexibility and diversity of frequency control are further improved.
In an exemplary embodiment, as shown in fig. 3, the message pushing method of the present disclosure is further explained, and this embodiment is exemplified by applying the method to a message server. Specifically, the method may comprise the steps of:
in step S310, the message frequency control configuration information is acquired and stored.
In this embodiment, as shown in fig. 4, the message server includes a frequency control policy module, a frequency control checking module, and a frequency control counting module, which are connected in sequence, and further includes a message RPC and a message task queue, which are connected to the frequency control checking module, respectively, and a message storage module connected to the message RPC.
Specifically, the server first obtains the message frequency control configuration information, and stores the obtained message frequency control configuration information in the frequency control policy module. The message frequency control configuration information comprises a message frequency control dimension and a corresponding message frequency control threshold. For example, if the message frequency control configuration information acquired by the server in this embodiment includes: the maximum number of messages that the user receives within the period T1 is n1 and the maximum number of messages that the user receives within the period T2 is n2, defined based on account dimensions; the maximum value of the number of messages of the user receiving the X1 type messages in the period T3 is n3, and the maximum value of the number of messages of the user receiving the X2 type messages in the period T4 is n 4; also included is a maximum number of messages, defined based on the message box dimensions, that the user receives messages from message box Z1 for period T5 of n5, and a maximum number of messages that the user receives messages from message box Z2 for period T6 of n 6. The server stores the acquired message frequency control configuration information in a frequency control strategy module.
In step S320, a candidate push message is obtained from the message queue, and a frequency control verification module is invoked to verify a message task corresponding to the candidate push message.
In this embodiment, when a service party wants to push a message to a user, the service party applies for the message to a server, and invokes a message push SDK provided by the server to push the candidate push message to an appointed user after the application is passed, and the SDK forwards a message task for pushing the candidate push message to a message queue. The server consumes the message task in the message queue, firstly obtains the candidate push message corresponding to the message task from the message queue, and then calls the frequency control checking module to check the message task corresponding to the candidate push message. And the candidate push message carries a corresponding message type and a target account identifier to be pushed.
Specifically, during verification, the frequency control verification module acquires pre-configured message frequency control configuration information from the frequency control strategy module, and determines a target message frequency control dimension and a message frequency control threshold value matched with the message type and the target account identifier from the message frequency control configuration information based on the message type corresponding to the candidate push message and the target account identifier to be pushed.
For example, if the message type corresponding to the candidate push message is X1 type, and the message receiver corresponding to the target account id receives the X1 type message by using the message box Z1. The target message frequency control dimension and the target message frequency control threshold value which are matched with the message type and the target account identifier and are determined from the message frequency control configuration information include: the maximum number of messages for which the target account identification receives messages in period T1 is n1, the maximum number of messages for which the target account identification receives messages in period T2 is n2, the maximum number of messages for which the target account identification receives X1 type messages in period T3 is n3, and the maximum number of messages for which the target account identification receives messages from message box Z1 in period T5 is n 5.
And then the frequency control checking module calls a frequency control counting module to obtain the count of the received messages of the target user identification in the corresponding dimension based on the target message frequency control dimension. For example, a count L1 of messages received by the target account identifier in a period T1 is obtained, a message count L2 of messages received by the target account identifier in a period T2 is obtained, a count L3 of messages received by the target account identifier in a period T3 of the X1 type is obtained, and a count L4 of messages received by the target account identifier from a message box Z1 in a period T5 is obtained.
And the frequency control checking module compares the counts acquired by the frequency control counting module with the corresponding target message frequency control threshold, and if each count is smaller than the corresponding target message frequency control threshold, the corresponding message task passes the checking. And as long as any one of the counts is greater than or equal to the corresponding target message frequency control threshold, the corresponding message task check is not passed.
In step S330, the candidate push message corresponding to the verified message task is determined as a message to be pushed, and a message RPC is called to process the message task.
Specifically, the server determines the candidate push message corresponding to the verified message task as a message to be pushed, and calls a message RPC to process the message task.
In step S340, the message RPC checks the message task corresponding to the message to be pushed based on the message to be pushed corresponding to the received message task by calling the frequency control check module again.
Specifically, the process of checking the message task in this step is similar to the check in step S320, and this embodiment will not be described again.
It should be noted that, since the step S320 is performed based on the message task in the message queue for verification, only the task that has exceeded the frequency control threshold can be initially intercepted, and for the concurrent task that has not exceeded the frequency control threshold, there may be a case of missed interception. Based on this, in the embodiment, the frequency control check module is called again through the message RPC to check the message task, so that the concurrent task can be intercepted accurately. And because the message task reaching the message RPC is checked, the processing pressure of the message RPC can be reduced, and the processing efficiency is improved.
In step S350, the message to be pushed corresponding to the message task that the message RPC rechecks passes is determined as the target push message, and the count of the message received by the target account identifier is updated to obtain the updated count.
Specifically, when the message RPC is checked again, it indicates that the message to be pushed corresponding to the message task can be pushed to the user corresponding to the target account identifier, and therefore, the message to be pushed corresponding to the message task is determined as the target push message. And updating the count of the message received by the target account identifier to obtain the updated count. The updated count is obtained by adding the current push to the cumulative count of the messages successfully pushed to the user last time, for example, if the cumulative count of the messages successfully pushed to the target account identifier last time is K, the updated count of the current push is K + 1.
In step S360, the server calls the message storage module to store the target push message passing the re-verification in the storage space corresponding to the target account identifier.
Specifically, the server calls the message storage module to store the target push message passing the rechecking to the storage space corresponding to the target account identifier, so that the push of the message task is completed. And the user corresponding to the target account identifier can access the message page (namely, the message Tab) through the client, pull the message Feed, and display the message corresponding to the storage space based on the message rendering and display policy module.
In step S370, when the check fails, it indicates that the corresponding message task push failed.
Specifically, when the verification fails, the pushing of the corresponding message task is indicated to fail, and the server may also feed back a pushing result to the corresponding service party based on the message task with the pushing failure, so that the service party performs corresponding processing conveniently.
Because the push process is verified twice, the problem of flooding of the user side information can be avoided, the processing pressure of the RPC information can be reduced, and the processing efficiency is improved.
It should be understood that although the various steps in the flowcharts of fig. 1-4 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 1-4 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least some of the other steps or stages.
It is understood that the same/similar parts between the embodiments of the method described above in this specification can be referred to each other, and each embodiment focuses on the differences from the other embodiments, and it is sufficient that the relevant points are referred to the descriptions of the other method embodiments.
Fig. 5 is a block diagram illustrating a message pushing apparatus according to an example embodiment. Referring to fig. 5, the apparatus includes a to-be-pushed message obtaining module 502, a count obtaining module 504, a checking module 506 and a message storing module 508.
A to-be-pushed message obtaining module 502 configured to perform obtaining of a to-be-pushed message, where the to-be-pushed message carries a target account identifier to be pushed;
a count obtaining module 504, configured to perform, according to a pre-configured message frequency control dimension, obtaining a count of messages received by the target account identifier in the message frequency control dimension at the current moment;
a checking module 506 configured to perform checking on the count according to a preconfigured message frequency control threshold corresponding to the message frequency control dimension;
and the message storage module 508 is configured to determine that the message to be pushed is a target push message when the verification passes, and store the target push message in a storage space corresponding to the target account identifier.
In an exemplary embodiment, the to-be-pushed message obtaining module is further configured to perform: acquiring candidate push messages from a message queue, wherein the candidate push messages carry corresponding pushed target account identifications; according to the message frequency control dimension configured in advance, obtaining the count of the received messages of the target account identifier under the message frequency control dimension; checking the count according to a message frequency control threshold value which is configured in advance and corresponds to the message frequency control dimension; and when the verification is passed, determining the candidate push message as a message to be pushed.
In an exemplary embodiment, the apparatus further comprises a count update module configured to perform: and updating the count of the received messages of the target account identifier under the message frequency control dimension to obtain the updated count.
In an exemplary embodiment, the message frequency control dimension includes an account dimension and a corresponding at least one first frequency control period; the count acquisition module is further configured to perform: according to the target account identification, the preset account dimension and the corresponding at least one first frequency control period, determining the target account dimension corresponding to the target account identification and the corresponding at least one first frequency control period; and acquiring a first count of received messages of the target account identification in at least one target first frequency control period of the target account dimension at the current moment.
In an exemplary embodiment, the message frequency control dimension further comprises a message type dimension and a corresponding at least one second frequency control period; the message to be pushed also carries a corresponding message type; the count acquisition module is further configured to perform: determining a target message type dimension to which the message to be pushed belongs and at least one corresponding target second frequency control period according to the message type of the message to be pushed, the message type dimension configured in advance and the at least one corresponding second frequency control period; and acquiring a second count of messages corresponding to the type dimension of the target message in the received messages in the at least one target second frequency control period of the target account identifier at the current moment.
In an exemplary embodiment, the message frequency control dimensions further include a message box dimension and a corresponding at least one third frequency control period; the count acquisition module is further configured to perform: determining a target message box of the message to be pushed relative to the target account identifier and at least one corresponding target third frequency control period according to the message type of the message to be pushed, the preset message box dimension and at least one corresponding third frequency control period; and acquiring a third count of messages received by the target message box within the at least one target third frequency control period of the target account identifier at the current moment.
In an exemplary embodiment, the apparatus further includes a message frequency control configuration information obtaining module configured to perform: acquiring and storing message frequency control configuration information, wherein the message frequency control configuration information comprises message frequency control dimensions and corresponding message frequency control thresholds; the message frequency control dimension includes at least one of an account dimension, a message type dimension, and a message box dimension.
In an exemplary embodiment, the verification module is further configured to perform: and when the count is smaller than the message frequency control threshold value of the corresponding message frequency control dimension, determining that the check is passed.
In an exemplary embodiment, the verification module is further configured to perform: determining that the check fails when the count is greater than or equal to a message frequency control threshold of a corresponding message frequency control dimension; and when the check fails, determining that the message pushing fails.
Fig. 6 is a block diagram illustrating an electronic device S00 for message push according to an example embodiment. For example, the electronic device S00 may be a server. Referring to FIG. 6, electronic device S00 includes a processing component S20 that further includes one or more processors and memory resources represented by memory S22 for storing instructions, such as applications, that are executable by processing component S20. The application program stored in the memory S22 may include one or more modules each corresponding to a set of instructions. Further, the processing component S20 is configured to execute instructions to perform the above-described method.
The electronic device S00 may further include: the power supply module S24 is configured to perform power management of the electronic device S00, the wired or wireless network interface S26 is configured to connect the electronic device S00 to a network, and the 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.
In an exemplary embodiment, a computer-readable storage medium comprising instructions, such as the memory S22 comprising instructions, executable by the processor of the electronic device S00 to perform the above method is also provided. The storage medium may be a computer-readable storage medium, which may be, for example, a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
In an exemplary embodiment, there is also provided a computer program product comprising instructions executable by a processor of the electronic device S00 to perform the above method.
It should be noted that the descriptions of the above-mentioned apparatus, the electronic device, the computer-readable storage medium, the computer program product, and the like according to the method embodiments may also include other embodiments, and specific implementations may refer to the descriptions of the related method embodiments, which are not described in detail herein.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements 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 (10)
1. A message pushing method, the method comprising:
acquiring a message to be pushed, wherein the message to be pushed carries a target account identifier to be pushed;
according to a pre-configured message frequency control dimension, obtaining the count of the received messages of the target account identifier under the message frequency control dimension at the current moment;
acquiring a message frequency control threshold corresponding to the message frequency control dimension, wherein the message frequency control threshold is configured in advance, and when the count is smaller than the message frequency control threshold corresponding to the message frequency control dimension, the check is determined to be passed;
and when the verification is passed, determining that the message to be pushed is a target push message, and storing the target push message in a storage space corresponding to the target account identifier.
2. The method of claim 1, wherein the obtaining the message to be pushed comprises:
acquiring candidate push messages from a message queue, wherein the candidate push messages carry corresponding pushed target account identifications;
according to the message frequency control dimension configured in advance, obtaining the count of the received messages of the target account identifier under the message frequency control dimension;
checking the count according to a message frequency control threshold value which is configured in advance and corresponds to the message frequency control dimension;
and when the verification is passed, determining the candidate push message as a message to be pushed.
3. The method of claim 1, wherein after the message to be pushed is determined to be the target push message by the verification, the method further comprises:
and updating the count of the received messages of the target account identifier under the message frequency control dimension to obtain the updated count.
4. The method of any one of claims 1 to 3, wherein the message frequency control dimension comprises an account dimension and a corresponding at least one first frequency control period; the obtaining of the count of the received messages of the target account identifier under the message frequency control dimension at the current moment according to the pre-configured message frequency control dimension includes:
according to the target account identification, the preset account dimension and the corresponding at least one first frequency control period, determining the target account dimension corresponding to the target account identification and the corresponding at least one first frequency control period;
and acquiring a first count of received messages of the target account identification in at least one target first frequency control period of the target account dimension at the current moment.
5. The method of claim 4, wherein the message frequency control dimension further comprises a message type dimension and a corresponding at least one second frequency control period; the message to be pushed also carries a corresponding message type; the obtaining of the count of the received messages of 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 a target message type dimension to which the message to be pushed belongs and at least one corresponding target second frequency control period according to the message type of the message to be pushed, the message type dimension configured in advance and the at least one corresponding second frequency control period;
and acquiring a second count of messages corresponding to the type dimension of the target message in the received messages in the at least one target second frequency control period of the target account identifier at the current moment.
6. The method of claim 5, wherein the message frequency control dimensions further include a message box dimension and a corresponding at least one third frequency control period; the obtaining of the count of the received messages of 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 a target message box of the message to be pushed relative to the target account identifier and at least one corresponding target third frequency control period according to the message type of the message to be pushed, the preset message box dimension and at least one corresponding third frequency control period;
and acquiring a third count of messages received by the target message box within the at least one target third frequency control period of the target account identifier at the current moment.
7. A message push apparatus, comprising:
the system comprises a to-be-pushed message acquisition module, a to-be-pushed message acquisition module and a to-be-pushed message acquisition module, wherein the to-be-pushed message acquisition module is configured to execute acquisition of a to-be-pushed message, and the to-be-pushed message carries a target account identifier to be pushed;
the counting acquisition module is configured to execute counting of the received messages of the target account identifier under the message frequency control dimension at the current moment according to the pre-configured message frequency control dimension;
the checking module is configured to execute the steps of obtaining a message frequency control threshold value corresponding to the message frequency control dimension, and when the count is smaller than the message frequency control threshold value of the corresponding message frequency control dimension, determining that the checking is passed;
and 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 a storage space corresponding to the target account identifier.
8. An electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the message push method of any one of claims 1 to 6.
9. A computer-readable storage medium, wherein instructions in the computer-readable storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the message push method of any of claims 1-6.
10. A computer program product comprising instructions therein, wherein the instructions, when executed by a processor of an electronic device, enable the electronic device to perform the message push method of any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210736893.0A CN115022264A (en) | 2022-06-27 | 2022-06-27 | Message pushing method and device, electronic equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210736893.0A CN115022264A (en) | 2022-06-27 | 2022-06-27 | Message pushing method and device, electronic equipment and computer readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115022264A true CN115022264A (en) | 2022-09-06 |
Family
ID=83076398
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210736893.0A Pending CN115022264A (en) | 2022-06-27 | 2022-06-27 | Message pushing method and device, electronic equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115022264A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115633010A (en) * | 2022-10-20 | 2023-01-20 | 北京达佳互联信息技术有限公司 | Message control method and message control device |
| CN116389594A (en) * | 2023-05-12 | 2023-07-04 | 广州此声网络科技有限公司 | Message processing method, device and computer equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104660482A (en) * | 2013-11-20 | 2015-05-27 | 中兴通讯股份有限公司 | Method and device for pushing social network information |
| US20180213048A1 (en) * | 2017-01-23 | 2018-07-26 | Microsoft Technology Licensing, Llc | Secured targeting of cross-application push notifications |
| CN108419206A (en) * | 2018-02-28 | 2018-08-17 | 北京邮电大学 | A kind of target homing system and method |
| CN112016030A (en) * | 2020-09-09 | 2020-12-01 | 湖南快乐阳光互动娱乐传媒有限公司 | Message pushing method, device, server and computer storage medium |
| CN112364239A (en) * | 2020-10-21 | 2021-02-12 | 广州市百果园网络科技有限公司 | Message pushing strategy determining method, device, equipment and storage medium |
-
2022
- 2022-06-27 CN CN202210736893.0A patent/CN115022264A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104660482A (en) * | 2013-11-20 | 2015-05-27 | 中兴通讯股份有限公司 | Method and device for pushing social network information |
| US20180213048A1 (en) * | 2017-01-23 | 2018-07-26 | Microsoft Technology Licensing, Llc | Secured targeting of cross-application push notifications |
| CN108419206A (en) * | 2018-02-28 | 2018-08-17 | 北京邮电大学 | A kind of target homing system and method |
| CN112016030A (en) * | 2020-09-09 | 2020-12-01 | 湖南快乐阳光互动娱乐传媒有限公司 | Message pushing method, device, server and computer storage medium |
| CN112364239A (en) * | 2020-10-21 | 2021-02-12 | 广州市百果园网络科技有限公司 | Message pushing strategy determining method, device, equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 黄红元: "上海证券交易所联合研究报告 2013 证券信息前沿技术专集", 31 December 2014, 上海：上海人民出版社, pages: 162 - 165 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115633010A (en) * | 2022-10-20 | 2023-01-20 | 北京达佳互联信息技术有限公司 | Message control method and message control device |
| CN116389594A (en) * | 2023-05-12 | 2023-07-04 | 广州此声网络科技有限公司 | Message processing method, device and computer equipment |
| CN116389594B (en) * | 2023-05-12 | 2023-09-01 | 广州此声网络科技有限公司 | Message processing method, device and computer equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN115022264A (en) | Message pushing method and device, electronic equipment and computer readable storage medium | |
| WO2017125015A1 (en) | Method for processing workflow of distributed system and workflow engine system | |
| US20160335142A1 (en) | Notification Service Processing Method for Business Process Management and Business Process Management Engine | |
| US20210019765A1 (en) | Blockchain-based business processing method and system | |
| CN109933439B (en) | Message transmission method, device, computer equipment and storage medium | |
| US9053136B2 (en) | Systems and methods for identifying contacts as users of a multi-tenant database and application system | |
| EP2985730A1 (en) | Method and device for partially-upgrading | |
| US20180260790A1 (en) | Automated appointment scheduling | |
| CN110880100A (en) | Business approval processing method, device and system | |
| CN112689202B (en) | Live broadcast room message processing method and device, server and storage medium | |
| CN110231998A (en) | Detection method, device and the storage medium of distributed timing task | |
| CN112767113A (en) | Account checking data processing method, device and system based on block chain | |
| CN114268628B (en) | Method, system, equipment and storage medium for networking cross-block chain service platform | |
| CN111767558A (en) | Data access monitoring method, device and system | |
| CN115878341A (en) | Message subscription method and device, storage medium and electronic device | |
| CN114007111A (en) | Resource distribution method and device, electronic equipment and storage medium | |
| CN110389976B (en) | Multi-interface data scheduling method and device | |
| CN111625323A (en) | Distributed task processing method, device, equipment and computer readable storage medium | |
| CN107425994B (en) | Method, terminal and server for realizing remote parameter management | |
| CN105763535A (en) | Method, device and system for processing session message list | |
| CN110311794B (en) | Social group joining method and device, server and storage medium | |
| CN116208709A (en) | Voice outbound method, device, electronic equipment and storage medium | |
| CN115729961A (en) | Data query method, device, equipment and computer readable storage medium | |
| US20230053967A1 (en) | Group updating method, message sending method, and apparatuses | |
| CN113610565A (en) | Network activity evaluation method and device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |