CN116886765A - Message pushing method, device, equipment, medium and program product - Google Patents
Message pushing method, device, equipment, medium and program product Download PDFInfo
- Publication number
- CN116886765A CN116886765A CN202310898555.1A CN202310898555A CN116886765A CN 116886765 A CN116886765 A CN 116886765A CN 202310898555 A CN202310898555 A CN 202310898555A CN 116886765 A CN116886765 A CN 116886765A
- Authority
- CN
- China
- Prior art keywords
- message
- push
- push message
- frequency control
- preset
- 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 61
- 238000011217 control strategy Methods 0.000 claims abstract description 152
- 238000011161 development Methods 0.000 abstract description 4
- 238000001514 detection method Methods 0.000 description 13
- 238000004590 computer program Methods 0.000 description 11
- 238000012545 processing Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 9
- 238000004891 communication Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012163 sequencing technique Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000012856 packing Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000011282 treatment Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0894—Policy-based network configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The present disclosure relates to a message pushing method, apparatus, device, medium and program product. The message pushing method comprises the following steps: receiving a push message sent by a service server; acquiring attribute information of the push message; and under the condition that the attribute information of the push message meets a preset message frequency control strategy, sending the push message to a client so that the client displays the push message. By adopting the method provided by the embodiment of the disclosure, the code development and publishing cost can be reduced, and the message pushing efficiency can be improved.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, a medium, and a program product for pushing a message.
Background
In the related art, an in-station push message is an application program of an electronic device (such as a mobile phone, a tablet computer, etc.) when a user uses the application program, if the push message is received, a message prompt popup window popped up at the top of the application program. Currently, when a client displays a push message, it is generally required to perform frequency control detection on the push message. Therefore, once the frequency control strategy is changed, code development and edition release are needed to be carried out again on the client, which causes the message pushing process to be more complicated and affects the message pushing efficiency.
Disclosure of Invention
The disclosure provides a message pushing method, a device, equipment, a medium and a program product, which at least solve the problem that in the related art, a frequency control strategy cannot be immediately effective, so that delay exists in application of the frequency control strategy. The technical scheme of the present disclosure is as follows:
according to a first aspect of an embodiment of the present disclosure, there is provided a message pushing method, including:
receiving a push message sent by a service server;
acquiring attribute information of the push message;
sending the push message to a client under the condition that the attribute information of the push message meets a preset message frequency control strategy, so that the client displays the push message; the preset message frequency control strategy is used for adjusting the frequency of sending push messages to the client by the business server.
In a possible implementation manner, the preset message frequency control strategy includes a first message frequency control strategy;
and before the push message is sent to the client, if the attribute information of the push message meets a preset message frequency control policy, the method further comprises the following steps:
if the attribute information comprises the priority to which the push message belongs, acquiring the first displayed push message quantity corresponding to the priority to which the push message belongs;
And under the condition that the number of the first displayed push messages is smaller than a first preset number, determining that the attribute information of the push messages meets the first message frequency control strategy.
In a possible implementation manner, the preset message frequency control strategy includes a second message frequency control strategy;
and before the push message is sent to the client, the method further comprises the following steps of:
if the attribute information comprises the service type of the push message, acquiring a second displayed push message quantity corresponding to the service type of the push message;
and under the condition that the number of the second displayed push messages is smaller than a second preset number, determining that the attribute information of the push messages meets the second message frequency control strategy.
In a possible implementation manner, the preset message frequency control strategy includes a third message frequency control strategy;
and before the push message is sent to the client, the method further comprises the following steps of:
if the attribute information comprises the current time of the push message, acquiring the display time of the last push message; wherein, the last push message is the push message which has the shortest interval time with the push message and is displayed before the push message;
And under the condition that the interval time length between the display time of the last push message and the current time is longer than or equal to the preset time length, determining that the attribute information of the push message meets the third message frequency control strategy.
In a possible implementation manner, after the push message is sent to the client, at least one of the following is further included:
if the preset message frequency control strategy comprises a first message frequency control strategy, updating the first displayed push message quantity corresponding to the priority to which the push message belongs; the first message frequency control strategy is that the number of first displayed push messages corresponding to the priority to which the push messages belong is smaller than a first preset number;
if the preset message frequency control strategy comprises a second message frequency control strategy, updating the second displayed push message quantity corresponding to the service type to which the push message belongs; the second message frequency control strategy is that the number of second displayed push messages corresponding to the service type to which the push messages belong is smaller than a second preset number;
if the preset message frequency control strategy comprises a third message frequency control strategy, updating the display time of the last push message; the third message frequency control strategy is that the interval time length between the display time of the last push message and the current time of the push message is greater than or equal to the preset time length.
In one possible embodiment, the method further comprises at least one of:
resetting the number of the first displayed push messages corresponding to the priority to which the push messages belong at the starting time of the effective period corresponding to the priority to which each push message belongs;
and resetting the number of second displayed push messages corresponding to the service type to which the push message belongs at the starting moment of the effective period corresponding to the service type to which each push message belongs.
According to a second aspect of embodiments of the present disclosure, there is provided a message pushing apparatus, the apparatus comprising:
the message receiving module is configured to receive push messages sent by the business server side;
the information acquisition module is configured to acquire attribute information of the push message;
the pushing module is configured to send the pushing message to a client side so as to enable the client side to display the pushing message under the condition that the attribute information of the pushing message meets a preset message frequency control strategy; the preset message frequency control strategy is used for adjusting the frequency of sending push messages to the client by the business server.
In a possible implementation manner, the preset message frequency control strategy includes a first message frequency control strategy;
The apparatus further comprises:
the first quantity acquisition module is configured to acquire a first displayed push message quantity corresponding to the priority to which the push message belongs if the attribute information comprises the priority to which the push message belongs;
the first determining module is configured to determine that the attribute information of the push message meets the first message frequency control policy when the number of the first displayed push messages is smaller than a first preset number.
In a possible implementation manner, the preset message frequency control strategy includes a second message frequency control strategy;
the device further comprises:
the second number acquisition module is configured to acquire a second displayed push message number corresponding to the service type to which the push message belongs if the attribute information comprises the service type to which the push message belongs;
and the second determining module is configured to determine that the attribute information of the push message meets the second message frequency control strategy when the number of the second displayed push messages is smaller than a second preset number.
In a possible implementation manner, the preset message frequency control strategy includes a third message frequency control strategy;
The device further comprises:
the third quantity acquisition module is configured to acquire the display time of the last push message if the attribute information comprises the current time of the push message; wherein, the last push message is the push message which has the shortest interval time with the push message and is displayed before the push message;
and the third determining module is configured to determine that the attribute information of the push message meets the third message frequency control strategy under the condition that the interval time length between the display time of the last push message and the current time is greater than or equal to the preset time length.
In one possible embodiment, the apparatus further comprises at least one of:
the first updating module is configured to update the first displayed push message quantity corresponding to the priority to which the push message belongs if the preset message frequency control strategy comprises a first message frequency control strategy; the first message frequency control strategy is that the number of first displayed push messages corresponding to the priority to which the push messages belong is smaller than a first preset number;
the second updating module is configured to update the second displayed push message quantity corresponding to the service type to which the push message belongs if the preset message frequency control strategy comprises a second message frequency control strategy; the second message frequency control strategy is that the number of second displayed push messages corresponding to the service type to which the push messages belong is smaller than a second preset number;
The third updating module is configured to update the display time of the last push message if the preset message frequency control strategy comprises a third message frequency control strategy; the third message frequency control strategy is that the interval time length between the display time of the last push message and the current time of the push message is greater than or equal to the preset time length.
In one possible embodiment, the apparatus further comprises at least one of:
the first resetting module is configured to reset the first displayed push message quantity corresponding to the priority to which the push message belongs at the starting moment of the effective period corresponding to the priority to which each push message belongs;
and the second resetting module is configured to reset the second displayed push message quantity corresponding to the service type to which the push message belongs at the starting moment of the effective period corresponding to the service type to which each push message belongs.
According to a third aspect of embodiments of the present disclosure, there is provided 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 method of any of the first aspects.
According to a fourth aspect of embodiments of the present disclosure, there is provided a storage medium, which when executed by a processor of an electronic device, enables the electronic device to perform the method of any one of the first aspects.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of the first aspects.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:
in the embodiment of the disclosure, a push message pushed by a business server is received; acquiring attribute information of a push message; pushing the push message to the client under the condition that the attribute information of the push message meets a preset message frequency control strategy so that the client displays the push message; the preset message frequency control strategy is used for adjusting the frequency of sending push messages to the client by the service server. In this way, the process of determining whether the push message meets the preset message frequency control strategy, namely the process of performing frequency control strategy detection on the push message, is executed by the message center server, the frequency control strategy is also configured at the message center server, and if the server modifies the frequency control strategy, the push message can be directly validated without causing delay in the application of the frequency control strategy. In addition, because the frequency control strategy is configured at the message center server, the frequency control strategy detection is also executed by the message center server, and the client only needs to push message display, so that code development and edition are not needed to be carried out on the client to configure and update the frequency control strategy, thereby effectively improving the message pushing efficiency.
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 disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.
Fig. 1 is a schematic diagram of an application scenario of a message pushing method according to an exemplary embodiment.
Fig. 2 is a flowchart illustrating a message pushing method applied to a server side in a message according to an exemplary embodiment.
Fig. 3 is a flowchart illustrating a method of determining whether attribute information of a push message satisfies a preset message frequency control policy according to an exemplary embodiment.
Fig. 4 is a flowchart illustrating a message pushing method applied to a client according to an exemplary embodiment.
Fig. 5 is a schematic diagram illustrating a display of push messages according to an example embodiment.
Fig. 6 is a block diagram illustrating a message pushing device applied to a server side of a message center according to an exemplary embodiment.
Fig. 7 is a block diagram of an electronic device, according to an example embodiment.
Detailed Description
In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of 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 foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
The following describes in detail a message pushing method, device, apparatus, medium and program product provided by the embodiments of the present disclosure with reference to the accompanying drawings.
Fig. 1 is a schematic application scenario of a message pushing method according to an exemplary embodiment, as shown in fig. 1, a message center server may receive a Push message (i.e. Push message) pushed by a service server (e.g. service server 1, service server 2, service server 3 in fig. 1), and may perform frequency control detection according to a frequency control policy, push the Push message meeting a preset message frequency control policy to a client, and the client displays the Push message meeting the preset message frequency control policy. It will be appreciated that only 3 service servers are shown in fig. 1 by way of example, and that in implementation, the number of service servers may be greater or lesser.
As shown in fig. 2, a message pushing method applied to a server side in a message provided by an embodiment of the present disclosure may be shown in fig. 2, and the message pushing method may include the following steps.
S210, receiving a push message pushed by the business server.
The message pushing can be active message pushing performed on the user mobile equipment client by an operator through a product background or a third party tool, and is a channel for the application server to actively touch the client. Through message pushing, the user can see the pushed message in the mobile device client notification bar and status bar. Push messages are a real-time mobile communication technology that enables servers to quickly send information to clients, in mobile applications, by using a message push service to send push messages to clients, once they reach the user device they can be displayed on the screen of the device.
In the embodiment of the disclosure, the service server can push the push message to be pushed to the message center server, so that the message center server can receive the push message to perform frequency control strategy detection by the message center server, namely judging whether the push message meets the preset message frequency control strategy. It will be appreciated that the push message may be a push message of an application that the user opens at the electronic device client, and the push message may be one or more.
S220, obtaining attribute information of the push message.
In the embodiment of the disclosure, after receiving the push message pushed by the service server, the in-message platform server may acquire attribute information of the push message, so that the in-message platform server performs frequency control policy detection according to the attribute information of the push message, that is, determines whether the attribute information of the push message meets a preset message frequency control policy. It will be appreciated that if there are a plurality of push messages, attribute information of each push message may be acquired separately.
S230, under the condition that the attribute information of the push message meets the preset message frequency control strategy, the push message is sent to the client so that the client displays the push message.
The preset message frequency control strategy is used for adjusting the frequency of sending push messages to the client by the service server.
In the embodiment of the disclosure, after acquiring the attribute information of the push message, the message center server may determine whether the attribute information of the push message meets a preset message frequency control policy. The preset message frequency control strategy can be a preset frequency control strategy, and when the preset message frequency control strategy is met, the preset message frequency control strategy can be considered to be met, and the frequency control strategy can be set in a self-defined mode according to actual requirements. It is understood that the preset message frequency control policy may include one or more message frequency control policies. If the server side in the message determines that the attribute information of the push message meets the preset message frequency control strategy, the push message can be sent to the client side, so that the client side can display the push message. In this way, the frequency control strategy is processed by the server side in the message, and the client side only takes charge of displaying the push message, namely, the client side only needs to display the push message after receiving the push message, any push message is not required to be discarded, and the received push message can be displayed; the frequency control strategy is set at the server side in the message, so that the strategy modification is more flexible, the requirements of various frequency control strategies can be met, and the frequency control strategy can be quickly modified and can be effective in real time.
In the embodiment of the disclosure, a push message pushed by a business server is received; acquiring attribute information of a push message; pushing the push message to the client under the condition that the attribute information of the push message meets a preset message frequency control strategy so that the client displays the push message; the preset message frequency control strategy is used for adjusting the frequency of sending push messages to the client by the service server. In this way, the process of determining whether the push message meets the preset message frequency control strategy, namely the process of performing frequency control strategy detection on the push message, is executed by the message center server, the frequency control strategy is also configured at the message center server, and if the server modifies the frequency control strategy, the push message can be directly validated without causing delay in the application of the frequency control strategy. In addition, because the frequency control strategy is configured at the message center server, the frequency control strategy detection is also executed by the message center server, and the client only needs to push message display, so that code development and edition are not needed to be carried out on the client to configure and update the frequency control strategy, thereby effectively improving the message pushing efficiency.
In one possible implementation, the preset message frequency control policy may include a first message frequency control policy; the first message frequency control policy may be that the number of first displayed push messages corresponding to the priority to which the push messages belong is smaller than a first preset number.
At this time, the foregoing step may further include the following processing before sending the push message to the client if the attribute information of the push message satisfies the preset message frequency control policy:
if the attribute information comprises the priority to which the push message belongs, acquiring the number of the first displayed push messages corresponding to the priority to which the push message belongs;
and under the condition that the number of the first displayed push messages is smaller than a first preset number, determining that the attribute information of the push messages meets a first message frequency control strategy.
In the embodiment of the present disclosure, if the attribute information of the push message includes the priority to which the push message belongs, when determining whether the attribute information of the push message meets the preset message frequency control policy, the priority to which the push message belongs may be determined first, and the number of displayed push messages corresponding to the priority to which the push message belongs, that is, the number of first displayed push messages, is obtained. It may be appreciated that determining the priority to which the push message belongs may be determining the priority of the service type to which the push message belongs, different service types may correspond to different priorities, specific service types and priorities corresponding thereto, and the number of push messages that are pushed most per cycle of different priorities may be set in a customized manner, for example, it may be set that the highest priority pushes 80 push messages at most per cycle (e.g., per day), the high priority pushes 65 push messages at most per cycle, and the general priority pushes 50 push messages at most per cycle. Then, the number of the first displayed push messages corresponding to the priority to which the push message belongs may be compared with the maximum allowable number of the push messages (i.e., the first preset number) corresponding to the priority to which the push message belongs, so as to determine whether the number of the first displayed push messages corresponding to the priority to which the push message belongs is smaller than the first preset number. If the number of the first displayed push messages corresponding to the priority to which the push messages belong is smaller than the first preset number, the push messages can be considered to meet the first message frequency control strategy, and the push messages can be pushed to the client, so that the client displays the push messages after receiving the push messages. It can be appreciated that if there are a plurality of push messages, the foregoing process of determining whether the attribute information of the push message satisfies the preset message frequency control policy may be performed for each push message. Thus, the preset message frequency control strategy can comprise a priority dimension frequency control strategy, and whether the push message meets the frequency control strategy of the dimension can be determined from the priority dimension; the frequency control strategy is processed by the server side in the message, and the client side only takes charge of displaying the push message, namely, the client side only needs to display the push message after receiving the push message, any push message is not required to be discarded, and the received push message can be displayed; the frequency control strategy is set at the server side in the message, so that the strategy modification is more flexible, the requirements of various frequency control strategies can be met, and the frequency control strategy can be quickly modified and can be effective in real time.
In one possible implementation, the preset message frequency control policy may include a second message frequency control policy; the second message frequency control strategy is that the number of second displayed push messages corresponding to the service type to which the push messages belong is smaller than a second preset number;
at this time, the foregoing step may further include the following processing before sending the push message to the client if the attribute information of the push message satisfies the preset message frequency control policy:
if the attribute information comprises the service type of the push message, acquiring the number of second displayed push messages corresponding to the service type of the push message;
and under the condition that the number of the second displayed push messages is smaller than a second preset number, determining that the attribute information of the push messages meets a second message frequency control strategy.
In the embodiment of the present disclosure, if the attribute information of the push message includes a service type to which the push message belongs, when determining whether the attribute information of the push message satisfies a preset message frequency control policy, the service type to which the push message belongs may be determined first, and then the number of displayed push messages corresponding to the service type to which the push message belongs, that is, the number of second displayed push messages, is acquired. Comparing the second number of the displayed push messages with the maximum allowable number of the displayed push messages (namely, a second preset number) corresponding to the service type to which the push messages belong, so as to determine whether the second number of the displayed push messages is smaller than the second preset number. It can be understood that the second preset number corresponding to different service types may be set in a user-defined manner, for example, the second preset number corresponding to the service type 1 may be set to 10, the second preset number corresponding to the service type 2 may be set to 15, etc. If the number of the second displayed push messages is smaller than the second preset number, the push messages can be considered to meet the second message frequency control strategy, and the push messages can be pushed to the client, so that the client displays the push messages after receiving the push messages. Therefore, the frequency control strategy detection can be performed on the push message from the dimension of the service type, namely whether the push message meets the preset message frequency control strategy can be determined from different dimensions, so that the push message pushed to the client can be ensured to better meet the frequency control requirement in more aspects.
In one possible implementation manner, the preset message frequency control policy may include a third message frequency control policy, where the third message frequency control policy may be that a time interval between a display time of a previous push message and a current time is greater than or equal to a preset duration.
At this time, the foregoing steps further include the following processing before sending the push message to the client if the attribute information of the push message satisfies the preset message frequency control policy:
if the attribute information comprises the current time of the push message, acquiring the display time of the last push message; the last push message is the push message which has the shortest interval time with the push message and is displayed before the push message;
and under the condition that the interval time length between the display time of the last push message and the current time is longer than or equal to the preset time length, determining that the attribute information of the push message meets a third message frequency control strategy.
In the embodiment of the present disclosure, if the attribute information of the push message includes the current time to which the push message belongs, when determining whether the attribute information of the push message meets a preset message frequency control policy, determining the previous push message, that is, determining the historical push message which has the shortest interval time with the push message and is displayed before the push message, obtaining the display time of the previous push message, calculating the interval time between the display time of the previous push message and the current time to which the push message belongs, and comparing the interval time with the preset time to determine whether the interval time between the display time of the previous push message and the current time is greater than or equal to the preset time. It will be appreciated that the preset duration may be the shortest interval duration allowed between the display of two push messages. If the interval time length between the display time of the last push message and the current time is greater than or equal to the preset time length, the attribute information of the push message can be considered to meet the third message frequency control strategy, and the push message can be pushed to the client. In this way, the frequency control strategy detection can be performed on the push message from the dimension of the time interval, so that the push message pushed to the client can be better ensured to meet the frequency control requirement in more aspects.
It may be appreciated that the preset message frequency control policy may include conditions of one or more dimensions of the first message frequency control policy, the second message frequency control policy, and the third message frequency control policy. Moreover, in the case that the preset message frequency control policy includes the aforementioned conditions of multiple dimensions, the conditions of multiple dimensions may be combined according to different sequences. In this way, the preset message frequency control policy may include at least one of a priority dimension frequency control policy, a service type dimension frequency control policy, and a time interval dimension frequency control policy, and whether the push message meets the frequency control policy of the dimension may be determined from multiple dimensions. It should be noted that the preset push message may also include frequency control policies of other dimensions, and the sequence of the frequency control policies of the multiple dimensions may be adjusted according to actual needs. In this way, frequency control strategy detection can be performed on the target push message from multiple dimensions such as priority, service type and time interval, and whether the push message meets the preset message frequency control strategy can be determined from the multiple dimensions, so that the push message pushed to the client can be ensured to better meet the frequency control requirement in more aspects.
In order to make the process of determining whether the target push message meets the preset message frequency control policy clearer, as described below with reference to fig. 3, as shown in fig. 3, fig. 3 uses the preset message frequency control policy including a priority dimension, a service type dimension and a time interval dimension as the frequency control policy, and sequentially proceeds according to the foregoing sequence, which illustrates a flowchart for determining whether attribute information of the push message meets the preset message frequency control policy, and referring to fig. 3, the method may include the following steps:
s310, receiving a push message, namely receiving the push message pushed by the business server.
S320, obtaining attribute information of the push message.
S330, whether the priority dimension frequency control strategy is satisfied.
In the embodiment of the disclosure, whether the attribute information of the push message meets a priority dimension frequency control policy is determined, that is, whether the number of the displayed push messages corresponding to the priority to which the push message belongs is smaller than a first preset number is determined. If the number of the displayed push messages corresponding to the priority to which the push messages belong is smaller than the first preset number, it may be considered that the priority dimension frequency control policy is satisfied, and S340 is performed.
S340, whether the service type dimension frequency control strategy is satisfied.
In the embodiment of the disclosure, whether the attribute information of the push message meets a service type dimension frequency control policy is determined, that is, whether the number of the displayed push messages corresponding to the service type to which the push message belongs is smaller than a second preset number is determined. If the number of the displayed push messages corresponding to the service type to which the push message belongs is smaller than the second preset number, the service type dimension frequency control policy is considered to be satisfied, and S350 is executed.
S350, whether a time interval dimension frequency control strategy is met.
In the embodiment of the disclosure, whether the attribute information of the push message meets a time interval dimension frequency control strategy is determined, that is, whether the interval duration between the display time of the last push message and the current time is greater than or equal to the preset duration is determined. If the interval time length between the display time of the previous push message and the current time is greater than or equal to the preset time length, the time interval dimension frequency control strategy can be considered to be satisfied, and at this time, the push message can be considered to satisfy the time interval dimension frequency control strategy, and S360 can be executed.
S360, sending the push message to the client.
In one possible implementation manner, after the push message is sent to the client, at least one of the following processes may be further included:
If the preset message frequency control strategy comprises a first message frequency control strategy, updating the first displayed push message quantity corresponding to the priority to which the push message belongs; the first message frequency control strategy is that the number of the first displayed push messages corresponding to the priority to which the push messages belong is smaller than a first preset number;
if the preset message frequency control strategy comprises a second message frequency control strategy, updating the second displayed push message quantity corresponding to the service type to which the push message belongs; the second message frequency control strategy is that the number of second displayed push messages corresponding to the service type to which the push messages belong is smaller than a second preset number;
if the preset message frequency control strategy comprises a third message frequency control strategy, updating the display time of the last push message; the third message frequency control strategy is that the interval time length between the display time of the last push message and the current time of the push message is greater than or equal to the preset time length.
In the embodiment of the present disclosure, the number of the first displayed push messages corresponding to the priority, the number of the second displayed push messages corresponding to the service type, and the display time of the last push message may also be updated. For example, if the preset message frequency control policy includes the first message frequency control policy, after sending the push message to the client, the count value of the number of the first displayed push messages corresponding to the priority to which the push message belongs may be incremented by 1; if the preset message frequency control policy includes the second message frequency control policy, the count value of the number of the second displayed push messages corresponding to the service type to which the push message belongs may be increased by 1. For example, if before pushing a certain push message, the number of first displayed push messages corresponding to the priority to which the push message belongs and the number of second displayed push messages corresponding to the service type to which the push message belongs are respectively 10 and 12, and the display time of the previous push message is 10:00:00, if a certain push message is pushed at 10:00:10, the number of first displayed push messages corresponding to the priority to which the push message belongs and the number of second displayed push messages corresponding to the service type to which the push message belongs may be respectively updated to 11 and 13, and the display time of the previous push message is updated to 10:00:10. In this way, by updating the number of the displayed push messages corresponding to the priority to which the push messages belong, the number of the displayed push messages corresponding to the service types to which the push messages belong and the display time of the previous push message, more accurate data basis can be improved for judging whether the subsequently received push messages meet the preset message frequency control strategy.
In one possible implementation, the method provided by the embodiments of the present disclosure may further include at least one of the following treatments:
resetting the number of the first displayed push messages corresponding to the priority to which the push messages belong at the starting time of the effective period corresponding to the priority to which each push message belongs;
and resetting the number of the second displayed push messages corresponding to the service type to which the push messages belong at the starting moment of the effective period corresponding to the service type to which each push message belongs.
In the embodiment of the present disclosure, each frequency control policy generally sets an effective time, that is, each frequency control policy generally corresponds to an effective period, and if the effective period exceeds the effective period, the count value needs to be reset, that is, the number of the displayed push messages needs to be reset. For example, the number of the corresponding displayed push messages can be reset according to the respective effective periods of the frequency control strategies with different dimensions. For example, if the effective period corresponding to the priority to which the push message belongs is one day, that is, 24 hours, that is, the number of the first displayed push messages corresponding to the priority to which the push message belongs needs to be reset every 24 hours, the reset count value is 0. As such, periodic resetting of the number of push messages has been shown to provide a more accurate data basis for counting and frequency control policy detection for the next period.
In a possible implementation manner, the target push message which does not meet the preset message frequency control policy may also be discarded, and correspondingly, the specific implementation manner may be as follows:
and discarding the push message under the condition that the attribute information of the push message does not meet the preset message frequency control strategy.
The push message failing to meet the preset message frequency control policy includes at least one of that the number of first displayed push messages corresponding to the priority to which the push message belongs is greater than or equal to a first preset number, the number of second displayed push messages corresponding to the service type to which the push message belongs is greater than or equal to a second preset number, and the interval duration between the display time of the last push message and the current time is smaller than the preset duration.
In the embodiment of the present disclosure, after determining whether the attribute information of the push message meets the preset message frequency control policy, a case may also occur in which the attribute information of the push message does not meet the preset message frequency control policy, for example, referring to fig. 3, in a case in which the attribute information of the push message does not meet the preset message frequency control policy, for example, the push message does not meet the priority dimension frequency control policy, that is, the number of first displayed push messages corresponding to the priority to which the push message belongs is greater than or equal to the first preset number; the push message does not meet the service type dimension frequency control strategy, namely the number of the second displayed push messages corresponding to the service type to which the push message belongs is larger than or equal to a second preset number; the push message does not meet the time interval dimension frequency control strategy, namely the interval duration between the display time and the current time of the last push message is smaller than the preset duration; alternatively, the case that the preset message frequency control policy is not satisfied may also include one or more of the above three cases. At this time, the push message which does not meet the preset message frequency control policy may be discarded, and the push message which does not meet the preset message frequency control policy may not be pushed to the client. Therefore, the push messages sent to the client by the server in the message can be further ensured to meet the preset message frequency control strategy, the client is only responsible for displaying the push messages, namely, the client displays the push messages after receiving the push messages, any push messages are not discarded, the received push messages can be displayed, and the display scheme that the client does not discard the push messages is provided.
Based on the same inventive concept, referring to fig. 4, the embodiment of the present disclosure further provides a message pushing method applied to a client, as shown in fig. 4, the message pushing method may include the following steps:
s410, receiving a push message sent by a server side in the message.
S420, displaying the push message.
In an embodiment of the present disclosure, in conjunction with fig. 1, a message center server may push a push message to a client, so that the client may receive the push message sent by the message center server. After receiving the push message sent by the server side in the message, the client side can display the push message. Therefore, the client does not need to perform frequency control strategy detection or discard push messages, and only needs to display the push messages.
In some possible embodiments, the specific implementation manner of displaying the target push message may be as follows:
determining whether a first push message in display exists at the current moment;
and displaying the push message when the first push message in the display does not exist at the current moment.
In an embodiment of the present disclosure, if the client receives a push message sent by the server in the message, it may be detected whether the client currently has a push message in the display, i.e. the first push message. If there is no first push message in the display, the push message may be displayed directly. By way of example, taking the client as the 'XX short video' application client, the push message is a work published by the 'user 1 of special interest', and the push message may be displayed in a manner as shown in fig. 5.
In some possible implementations, if there is a first push message in the display, the method provided by the embodiments of the present disclosure may further include the steps of:
under the condition that a first push message in display exists at the current moment, determining a first priority corresponding to the first push message and a priority to which the push message belongs;
displaying the first push message and the push message according to the priority of the push message and the first priority under the condition that the priority of the push message is different from the first priority;
under the condition that the priority of the push message is the same as the first priority, acquiring a first receiving moment of the first push message and a receiving moment of the push message;
sequencing the first push message and the push message according to the time sequence, and generating a push message display list;
and displaying the first push message and the push message in the push message display list according to the time sequence.
In the embodiment of the present disclosure, if there is a first push message in the display at the current time, a priority (first priority) corresponding to the first push message and a priority to which the push message belongs may be respectively. And determining the priority level of the push message and the first priority level, and displaying the first push message and the push message according to the priority level of the push message and the first priority level. For example, if the priority to which the push message belongs is higher than the first priority, the first push message may be collected and the push message may be displayed; otherwise, if the priority to which the push message belongs is lower than the first priority, the first push message may be retracted and the push message may be displayed after the display duration of the first push message reaches the preset display duration, where the preset display duration may be set in a user-defined manner, for example, may be set to 4 seconds. If the priority to which the push message belongs is the same as the first priority, the receiving time of the first push message (i.e., the first receiving time) and the receiving time of the push message may be obtained. And then sequencing the first push message and the push message according to the time sequence, obtaining a sequenced push message display list, and displaying the first push message and the push message in the push message display list according to the time sequence. It will be appreciated that if there are multiple push messages, the ordering may be based on the respective times of receipt of the multiple push messages.
In some possible embodiments, the specific implementation manner of displaying the first push message and the push message in the push message display list according to the chronological order in the steps above may be as follows:
determining whether the service type of the first push message is the same as the service type to which the push message belongs;
under the condition that the service type of the first push message is the same as the service type of the push message, when the push message is displayed, updating the message content of the first push message in a push message display area into the message content of the push message;
when the service type of the first push message is different from the service type to which the push message belongs, the first push message is collected and the push message is displayed again when the push message is displayed.
In embodiments of the present disclosure, when a first push message and a push message in a push message display list are queued for display, it may be determined whether the message content is directly updated or the previous push message is collapsed and the next push message is displayed according to the service type (Biz). If the service types of the currently displayed push message and the push message to be displayed are the same, namely the service type of the first push message is the same as the service type of the push message, the push message can be displayed in a content updating mode, namely the message content of the first push message in the push message display area is updated to the message content of the push message. If the service types of the currently displayed push message and the push message to be displayed are different, namely the service type of the first push message is different from the service type of the push message, the push message can be displayed by packing up the previous push message and displaying the next push message, namely the previous first push message is closed and then the next push message is displayed.
In some possible embodiments, in the case that the service type of the first push message is different from the service type to which the push message belongs, if the push message is multiple, when the first push message is retracted and the push message is displayed again, the following processing may be performed:
after the display time length of the first push message reaches the preset display time length, the first push message is packed up;
acquiring an ith push message and displaying the ith push message; wherein i is [1, n ], n is the number of push messages;
after the interval is preset for the interval duration, the (i+1) th push message is obtained, and the (i) th push message is updated to the (i+1) th push message.
In the embodiment of the disclosure, in order to avoid that in some extreme cases, more push messages are queued, so that the display duration is too long, the duration of the display interval of the push messages with the same continuous service type can be shortened. For example, the first push message may be collapsed after the display duration of the first push message reaches a preset display duration (e.g., 4 s). And then, acquiring the ith push message, and displaying the ith push message, wherein i is valued from 1. After the ith push message is displayed, the ith push message is acquired at intervals of preset interval duration, and then the ith push message is updated to the ith push message of the (+1) th push message, so that the display of the (i+1) th push message is realized. For example, for a push message of a service type, a first push message may be acquired first, then the first push message is not packed up, and the next push message is acquired every 1 second, so as to directly update the content of the push message.
Fig. 6 is a block diagram of a message pushing device according to an exemplary embodiment, applied to a message center server. Referring to fig. 6, the message pushing apparatus 600 includes:
the message receiving module 610 is configured to receive a push message sent by the service server;
an information acquisition module 620 configured to acquire attribute information of the push message;
a pushing module 630, configured to send the push message to a client, so that the client displays the push message, if the attribute information of the push message meets a preset message frequency control policy; the preset message frequency control strategy is used for adjusting the frequency of sending push messages to the client by the business server.
In a possible implementation manner, the preset message frequency control strategy includes a first message frequency control strategy;
the apparatus 600 further comprises:
the first quantity acquisition module is configured to acquire a first displayed push message quantity corresponding to the priority to which the push message belongs if the attribute information comprises the priority to which the push message belongs;
the first determining module is configured to determine that the attribute information of the push message meets the first message frequency control policy when the number of the first displayed push messages is smaller than a first preset number.
In a possible implementation manner, the preset message frequency control strategy includes a second message frequency control strategy;
the apparatus 600 further comprises:
the second number acquisition module is configured to acquire a second displayed push message number corresponding to the service type to which the push message belongs if the attribute information comprises the service type to which the push message belongs;
and the second determining module is configured to determine that the attribute information of the push message meets the second message frequency control strategy when the number of the second displayed push messages is smaller than a second preset number.
In a possible implementation manner, the preset message frequency control strategy includes a third message frequency control strategy;
the apparatus 600 further comprises:
the third quantity acquisition module is configured to acquire the display time of the last push message if the attribute information comprises the current time of the push message; wherein, the last push message is the push message which has the shortest interval time with the push message and is displayed before the push message;
and the third determining module is configured to determine that the attribute information of the push message meets the third message frequency control strategy under the condition that the interval time length between the display time of the last push message and the current time is greater than or equal to the preset time length.
In one possible implementation, the apparatus 600 further includes at least one of:
the first updating module is configured to update the first displayed push message quantity corresponding to the priority to which the push message belongs if the preset message frequency control strategy comprises a first message frequency control strategy; the first message frequency control strategy is that the number of first displayed push messages corresponding to the priority to which the push messages belong is smaller than a first preset number;
the second updating module is configured to update the second displayed push message quantity corresponding to the service type to which the push message belongs if the preset message frequency control strategy comprises a second message frequency control strategy; the second message frequency control strategy is that the number of second displayed push messages corresponding to the service type to which the push messages belong is smaller than a second preset number;
the third updating module is configured to update the display time of the last push message if the preset message frequency control strategy comprises a third message frequency control strategy; the third message frequency control strategy is that the interval time length between the display time of the last push message and the current time of the push message is greater than or equal to the preset time length.
In one possible implementation, the apparatus 600 further includes at least one of:
the first resetting module is configured to reset the first displayed push message quantity corresponding to the priority to which the push message belongs at the starting moment of the effective period corresponding to the priority to which each push message belongs;
and the second resetting module is configured to reset the second displayed push message quantity corresponding to the service type to which the push message belongs at the starting moment of the effective period corresponding to the service type to which each push message belongs.
The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.
According to embodiments of the present disclosure, the present disclosure also provides an electronic device, a storage medium and a computer program product.
Fig. 7 illustrates a schematic block diagram of an example electronic device 700 that may be used to implement embodiments of the present disclosure. Electronic device 700 is intended to represent various forms of digital computers, such as laptops, desktops, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the disclosure described and/or claimed herein.
As shown in fig. 7, the electronic device 700 includes a computing unit 701 that can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) 702 or a computer program loaded from a storage unit 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data required for the operation of the device 700 may also be stored. The computing unit 701, the ROM 702, and the RAM 703 are connected to each other through a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
Various components in the electronic device 700 are connected to the I/O interface 705, including: an input unit 706 such as a keyboard, a mouse, etc.; an output unit 707 such as various types of displays, speakers, and the like; a storage unit 708 such as a magnetic disk, an optical disk, or the like; and a communication unit 709 such as a network card, modem, wireless communication transceiver, etc. The communication unit 709 allows the electronic device 700 to exchange information/data with other devices through a computer network, such as the internet, and/or various telecommunication networks.
The computing unit 701 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of computing unit 701 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 701 performs the respective methods and processes described above, such as a message pushing method. For example, in some embodiments, the message pushing method may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as storage unit 708. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 700 via the ROM 702 and/or the communication unit 709. When the computer program is loaded into the RAM 703 and executed by the computing unit 701, one or more steps of the message pushing method described above may be performed. Alternatively, in other embodiments, the computing unit 701 may be configured to perform the message pushing method by any other suitable means (e.g. by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for a computer program product for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the processor or controller, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of this disclosure, a storage medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The storage medium may be a machine-readable signal medium or a machine-readable storage medium. The storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and pointing device (e.g., a mouse or trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), the internet, and blockchain networks.
The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service ("Virtual Private Server" or simply "VPS") are overcome. The server may also be a server of a distributed system or a server that incorporates a blockchain.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps recited in the present disclosure may be performed in parallel or sequentially or in a different order, provided that the desired results of the technical solutions of the present disclosure are achieved, and are not limited herein.
The above detailed description should not be taken as limiting the scope of the present disclosure. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present disclosure are intended to be included within the scope of the present disclosure.
Claims (10)
1. A message pushing method, the method comprising:
receiving a push message sent by a service server;
acquiring attribute information of the push message;
sending the push message to a client under the condition that the attribute information of the push message meets a preset message frequency control strategy, so that the client displays the push message; the preset message frequency control strategy is used for adjusting the frequency of sending push messages to the client by the business server.
2. The message pushing method according to claim 1, wherein the preset message frequency control policy includes a first message frequency control policy;
and before the push message is sent to the client, if the attribute information of the push message meets a preset message frequency control policy, the method further comprises the following steps:
if the attribute information comprises the priority to which the push message belongs, acquiring the first displayed push message quantity corresponding to the priority to which the push message belongs;
and under the condition that the number of the first displayed push messages is smaller than a first preset number, determining that the attribute information of the push messages meets the first message frequency control strategy.
3. The message pushing method according to claim 1, wherein the preset message frequency control policy includes a second message frequency control policy;
and before the push message is sent to the client, the method further comprises the following steps of:
if the attribute information comprises the service type of the push message, acquiring a second displayed push message quantity corresponding to the service type of the push message;
And under the condition that the number of the second displayed push messages is smaller than a second preset number, determining that the attribute information of the push messages meets the second message frequency control strategy.
4. The message pushing method according to claim 1, wherein the preset message frequency control policy includes a third message frequency control policy;
and before the push message is sent to the client, the method further comprises the following steps of:
if the attribute information comprises the current time of the push message, acquiring the display time of the last push message; wherein, the last push message is the push message which has the shortest interval time with the push message and is displayed before the push message;
and under the condition that the interval time length between the display time of the last push message and the current time is longer than or equal to the preset time length, determining that the attribute information of the push message meets the third message frequency control strategy.
5. The message pushing method according to claim 1, wherein after the push message is sent to the client, further comprising at least one of:
If the preset message frequency control strategy comprises a first message frequency control strategy, updating the first displayed push message quantity corresponding to the priority to which the push message belongs; the first message frequency control strategy is that the number of first displayed push messages corresponding to the priority to which the push messages belong is smaller than a first preset number;
if the preset message frequency control strategy comprises a second message frequency control strategy, updating the second displayed push message quantity corresponding to the service type to which the push message belongs; the second message frequency control strategy is that the number of second displayed push messages corresponding to the service type to which the push messages belong is smaller than a second preset number;
if the preset message frequency control strategy comprises a third message frequency control strategy, updating the display time of the last push message; the third message frequency control strategy is that the interval time length between the display time of the last push message and the current time of the push message is greater than or equal to the preset time length.
6. The message pushing method of claim 5, further comprising at least one of:
resetting the number of the first displayed push messages corresponding to the priority to which the push messages belong at the starting time of the effective period corresponding to the priority to which each push message belongs;
And resetting the number of second displayed push messages corresponding to the service type to which the push message belongs at the starting moment of the effective period corresponding to the service type to which each push message belongs.
7. A message pushing device, the device comprising:
the message receiving module is configured to receive push messages sent by the business server side;
the information acquisition module is configured to acquire attribute information of the push message;
the pushing module is configured to send the pushing message to a client side so as to enable the client side to display the pushing message under the condition that the attribute information of the pushing message meets a preset message frequency control strategy; the preset message frequency control strategy is used for adjusting the frequency of sending push messages to the client by the business server.
8. The message pushing device of claim 7, wherein the preset message frequency control policy comprises a first message frequency control policy;
the apparatus further comprises:
the first quantity acquisition module is configured to acquire a first displayed push message quantity corresponding to the priority to which the push message belongs if the attribute information comprises the priority to which the push message belongs;
The first determining module is configured to determine that the attribute information of the push message meets the first message frequency control policy when the number of the first displayed push messages is smaller than a first preset number.
9. 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 method of any one of claims 1 to 6.
10. A storage medium, characterized in that instructions in the storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310898555.1A CN116886765A (en) | 2023-07-20 | 2023-07-20 | Message pushing method, device, equipment, medium and program product |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310898555.1A CN116886765A (en) | 2023-07-20 | 2023-07-20 | Message pushing method, device, equipment, medium and program product |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116886765A true CN116886765A (en) | 2023-10-13 |
Family
ID=88265972
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310898555.1A Pending CN116886765A (en) | 2023-07-20 | 2023-07-20 | Message pushing method, device, equipment, medium and program product |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116886765A (en) |
-
2023
- 2023-07-20 CN CN202310898555.1A patent/CN116886765A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110808922B (en) | Message processing method and device, storage medium and electronic equipment | |
| CN112597754B (en) | Text error correction method, apparatus, electronic device and readable storage medium | |
| CN112506619B (en) | Job processing method, job processing device, electronic equipment and storage medium | |
| CN112965799B (en) | Task state prompting method and device, electronic equipment and medium | |
| CN116594563A (en) | Distributed storage capacity expansion method and device, electronic equipment and storage medium | |
| CN116567077A (en) | Bare metal instruction sending method, device, equipment and storage medium | |
| CN114554110B (en) | Video generation method, device, electronic equipment and storage medium | |
| CN113900731B (en) | Request processing method, device, equipment and storage medium | |
| CN116886765A (en) | Message pushing method, device, equipment, medium and program product | |
| CN113742581B (en) | Method and device for generating list, electronic equipment and readable storage medium | |
| CN112925623B (en) | Task processing method, device, electronic equipment and medium | |
| CN115334321B (en) | Method and device for acquiring access heat of video stream, electronic equipment and medium | |
| CN115037802B (en) | Request processing method and device, electronic equipment and storage medium | |
| CN114449031B (en) | Information acquisition method, device, equipment and storage medium | |
| CN114428646B (en) | Data processing method and device, electronic equipment and storage medium | |
| CN114979471B (en) | Interface display method, device, electronic equipment and computer readable storage medium | |
| CN115840604B (en) | Data processing method, device, electronic equipment and computer readable storage medium | |
| CN113360736B (en) | Internet data capturing method and device | |
| CN115086300B (en) | Video file scheduling method and device | |
| CN115936091B (en) | Training method and device for deep learning model, electronic equipment and storage medium | |
| CN114416937B (en) | Man-machine interaction method, device, equipment, storage medium and computer program product | |
| CN116468824B (en) | Animation redirection method, device, electronic equipment and storage medium | |
| CN113886842B (en) | Dynamic intelligent scheduling method and device based on test | |
| CN113779098B (en) | Data processing method, device, electronic equipment and storage medium | |
| CN115589391B (en) | Instant messaging processing method, device and equipment based on block chain 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 |