CN114286293A - Message push management method, device, system, computer equipment and storage medium - Google Patents
Message push management method, device, system, computer equipment and storage medium Download PDFInfo
- Publication number
- CN114286293A CN114286293A CN202111578971.0A CN202111578971A CN114286293A CN 114286293 A CN114286293 A CN 114286293A CN 202111578971 A CN202111578971 A CN 202111578971A CN 114286293 A CN114286293 A CN 114286293A
- Authority
- CN
- China
- Prior art keywords
- message
- client
- pushed
- pulling
- progress
- 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.)
- Granted
Links
Images
Abstract
The invention relates to a message pushing management method, a device, a system, a computer device and a storage medium, wherein the method comprises the following steps: when receiving the release information of a message to be pushed, which is released by a message center, the first client sends the release information of the message to be pushed to a first client, and the first client requests a third-party service or a resource center to pull the message to be pushed according to the release information of the message to be pushed; receiving the pulling progress of the message to be pushed sent by the first client; and comprehensively managing the pushing management of the message to be pushed of the second client according to the pulling progress. The method can improve the message pushing efficiency and effectively utilize the server resources.
Description
Technical Field
The present invention relates to the field of message push technologies, and in particular, to a message push management method, apparatus, system, computer device, and storage medium.
Background
With the development of terminal internet and internet of things, terminal equipment intellectualization gradually becomes a mainstream trend. In order to meet the requirements of the users, the device end is used as a transmission medium or an executor to output diversified contents or function displays. Higher requirements are put forward for realizing information receiving and more efficient response of the terminal equipment. For example, the terminal device is a display screen, and after receiving the advertisement playing instruction information, the terminal device initiates a request to the resource server to download the advertisement resource, and then performs the advertisement playing and displaying.
The current message pushing mode is relatively fixed, namely, broadcasting full push and appointed push. The disadvantage of the broadcast full push mode is that a large number of terminal devices simultaneously initiate high concurrent requests to the server in a short time, which causes a great load pressure, even overload, and results in a problem of unavailable service. And the appointed push mode adopts a batch push mode for a large amount of terminal equipment, and controls a fixed push time interval or push frequency to push M terminals within N minutes. However, the implementation process of pushing has difficulty in grasping the degree of pushing. If the push is too fast, the load on the server is too large like the broadcast method, and if the push is too slow, the resources of the server cannot be fully utilized. Therefore, the current message pushing mode cannot give consideration to both the message pushing efficiency and the utilization rate of server resources.
Disclosure of Invention
The invention aims to overcome the defects of the prior art and provides a message pushing management method, a message pushing management device, a message pushing management system, computer equipment and a storage medium, which can improve the message pushing efficiency and effectively utilize server resources.
In order to solve at least one technical problem, an embodiment of the present invention provides a message push management method, where the method includes:
when receiving the release information of a message to be pushed, which is released by a message center, the first client sends the release information of the message to be pushed to a first client, and the first client requests a third-party service or a resource center to pull the message to be pushed according to the release information of the message to be pushed;
receiving the pulling progress of the message to be pushed sent by the first client;
and comprehensively managing the pushing management of the message to be pushed of the second client according to the pulling progress.
In one embodiment, the first client is a client of a service system, a client of a wireless OTT set-top box, a client of a wireless router, a client of a cloud sim card wireless device, or a client of a terminal device integrated with a wireless internet access module;
the second client is a client of the service system, a client of the wireless OTT set top box, a client of the wireless router, a client of the cloud sim card wireless device or a client of the terminal device integrated with the wireless internet module.
In one embodiment, before the step of sending the publishing information of the message to be pushed to the first client, the method further includes:
receiving a long connection establishment request of the first client;
responding to the long connection establishment request, and establishing long connection with the first client;
receiving client information sent by the first client through the long connection;
the sending, to the first client, the release information of the message to be pushed includes:
and sending the release information of the message to be pushed to a first client according to the client information.
In one embodiment, the pull progress of the message to be pushed sent by the first client includes any one of the message to be pushed that is not pulled by the first client, the progress of the message to be pushed that is pulled by the first client, and the pull of the message to be pushed that is completed by the first client.
In one embodiment, the orchestrating the push management of the message to be pushed by the second client according to the pull schedule includes:
if the pulling progress comprises that the first client does not pull the message to be pushed, pausing pushing the message to be pushed to a second client;
if the pulling progress comprises the progress of pulling the message to be pushed by the first client, sending the publishing information of the message to be pushed to a second client according to the progress of pulling the message to be pushed by the first client, and requesting a third-party service or a resource center to pull the message to be pushed by the second client according to the publishing information of the message to be pushed;
if the pulling progress comprises that the first client finishes pulling the message to be pushed, confirming the pulling condition of the message to be pushed of a second client, if it is determined according to the pull condition that the second client does not acquire the publishing information of the message to be pushed, sending the publishing information of the message to be pushed to the second client, if the second client is determined to be pulling the message to be pushed according to the pulling condition, monitoring the progress of the second client for pulling the message to be pushed, if the second client is determined to finish pulling the message to be pushed according to the pulling condition, and sending the publishing information of the message to be pushed to a third client, and requesting a third-party service or a resource center to pull the message to be pushed by the third client according to the publishing information of the message to be pushed.
A message push management device, the device comprising:
the system comprises a sending module, a receiving module and a sending module, wherein the sending module is used for sending the publishing information of the message to be pushed to a first client when the publishing information of the message to be pushed published by a message center is received, and the first client requests a third-party service or a resource center to pull the message to be pushed according to the publishing information of the message to be pushed;
the receiving module is used for receiving the pulling progress of the message to be pushed sent by the first client;
and the overall planning module is used for overall planning the pushing management of the message to be pushed of the second client according to the pulling progress.
A message pushing management system comprises a message center, a message pushing platform and a third-party service or resource center;
the message center sends the release information of the message to be pushed to the message pushing platform;
the message pushing platform sends the publishing information of the message to be pushed to a first client when receiving the publishing information of the message to be pushed issued by the message center, and the first client requests the third-party service or the resource center to pull the message to be pushed according to the publishing information of the message to be pushed;
the message pushing platform receives the pulling progress of the message to be pushed sent from the first client;
and the message pushing platform integrally stages the pushing management of the message to be pushed of the second client according to the pulling progress.
In one embodiment, the first client is a client of a service system, a client of a wireless OTT set-top box, a client of a wireless router, a client of a cloud sim card wireless device, or a client of a terminal device integrated with a wireless internet access module;
the second client is a client of the service system, a client of the wireless OTT set top box, a client of the wireless router, a client of the cloud sim card wireless device or a client of the terminal device integrated with the wireless internet module.
A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the method of any of the above embodiments when executing the computer program.
A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method of any of the above embodiments.
According to the message pushing management method, the device, the system, the computer equipment and the storage medium, when the release information of the message to be pushed released by the message center is received, the release information of the message to be pushed is sent to the first client side, the first client side requests a third-party service or a resource center to pull the message to be pushed according to the release information of the message to be pushed, the pulling progress of the message to be pushed sent by the first client side is received, and the pushing management of the message to be pushed of the second client side is comprehensively planned according to the pulling progress. Therefore, management of message pushing and pulling of message pushing resources are separated, a third-party service or a resource center provides resource downloading service of the message pushing, a server side of the message pushing only needs to send issuing information of the message to be pushed to a client side, and resource downloading of the message to be pushed is not needed, so that resource occupation of the server side can be reduced, and resource utilization rate of the server side is improved. In addition, the message center can also comprehensively manage the message pushing of the first client and the second client, so that the message pushing efficiency is improved.
Drawings
FIG. 1 is a flowchart illustrating a message push management method according to an embodiment of the present invention
Fig. 2 is a schematic diagram of information interaction between devices in a message push management system according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a message push management apparatus in an embodiment of the present invention;
fig. 4 is a schematic structural composition diagram of a computer device in the embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The embodiment of the invention provides a message pushing management method, which is applied to a message center. As shown in fig. 1, the message push management method includes the following steps:
s102, when receiving the release information of the message to be pushed released by the message center, the first client sends the release information of the message to be pushed to the first client, and the first client requests a third-party service or a resource center to pull the message to be pushed according to the release information of the message to be pushed.
In this embodiment, the message center orchestrates the push messages of the client, for example, determines the release information of the to-be-pushed message to be pushed to the client, and releases the release information of the to-be-pushed message to the message push platform. And when the message pushing platform receives the publishing information of the message to be pushed, which is published by the message center, the publishing information of the message to be pushed is sent to the first client. And when receiving the release information of the message to be pushed, the first client requests a third-party service or a resource center to pull the message to be pushed. The message pushing platform may send the network link address of the third-party service or resource center to the first client, and the first client requests the third-party service or resource center to pull the message to be pushed based on the publishing information of the message to be pushed and the network link address of the third-party service or resource center.
The third-party service or the resource center stores the message to be pushed and provides the message downloading party service for the outside. The first client pulls the message to be pushed to the request based on the publishing information of the message to be pushed and the network link address of the third-party service or the resource center. And the third-party service or the resource center returns the message to be pushed to the first client, so that the first client can pull the message to be pushed.
S104, receiving the pulling progress of the message to be pushed sent by the first client.
In this embodiment, when the first client pulls the message to be pushed from the third-party service or the resource center, the pulling progress of the message to be pushed is fed back to the message pushing platform. The pull progress may include any one of the first client having completed pulling of the message to be pushed, the first client pulling the message to be pushed and a proportion of the message to be pushed that has been pulled, and the first client not performing pulling of the message to be pushed. The message pushing platform receives a pulling progress of a message to be pushed sent by a first client.
The first client is a client of a service system, a client of a wireless OTT set top box, a client of a wireless router, a client of cloud sim card wireless equipment or a client of terminal equipment integrated with a wireless internet module; the second client is a client of the service system, a client of the wireless OTT set-top box, a client of the wireless router, a client of the cloud sim card wireless device or a client of the terminal device integrated with the wireless internet module.
And S106, comprehensively planning the pushing management of the message to be pushed of the second client according to the pulling progress.
In this embodiment, the message push platform orchestrates the push management of the message to be pushed of the second client according to the pull progress of the first client. The first client and the second client are different clients.
The message push platform integrally stages push management of a message to be pushed of a second client according to the pull progress of the first client, and the push management comprises the following steps: and if the pulling progress of the first client represents that the first client finishes the message to be pushed, controlling the second client to pull the message to be pushed. And if the pulling progress of the first client indicates that the first client is pulling the message to be pushed, controlling the second client to be in a state of waiting for pulling the message to be pushed or in a state of starting to pull the message to be pushed.
The message pushing management method includes the steps of sending release information of a message to be pushed to a first client when the release information of the message to be pushed issued by a message center is received, requesting a third-party service or a resource center to pull the message to be pushed by the first client according to the release information of the message to be pushed, receiving the pulling progress of the message to be pushed sent by the first client, and performing pushing management on the message to be pushed of a second client according to the pulling progress. Therefore, management of message pushing and pulling of message pushing resources are separated, a third-party service or a resource center provides resource downloading service of the message pushing, a server side of the message pushing only needs to send issuing information of the message to be pushed to a client side, and resource downloading of the message to be pushed is not needed, so that resource occupation of the server side can be reduced, and resource utilization rate of the server side is improved. In addition, the message center can also comprehensively manage the message pushing of the first client and the second client, so that the message pushing efficiency is improved.
In one embodiment, before the step of sending the publishing information of the message to be pushed to the first client, the method further includes: receiving a long connection establishment request of the first client; responding to the long connection establishment request, and establishing long connection with the first client; receiving client information sent by the first client through the long connection; the sending, to the first client, the release information of the message to be pushed includes: and sending the release information of the message to be pushed to a first client according to the client information.
In this embodiment, after the first client is started, a networking request is initiated to the message push platform to request for establishing a long connection with the message push platform. The message pushing platform receives a long connection establishment request of the first client, responds to the long connection establishment request, establishes long connection with the first client and keeps heartbeat interaction. The first client sends client information to the message push platform through long connection. The client information may include account information of the first client, and the like. The message pushing platform identifies the first client according to the client information of the first client, so that the issuing information of the message to be pushed is sent to the first client.
In one embodiment, the pull progress of the message to be pushed sent by the first client includes any one of the message to be pushed that is not pulled by the first client, the progress of the message to be pushed that is pulled by the first client, and the pull of the message to be pushed that is completed by the first client.
Wherein, the pushing management of the message to be pushed of the second client is orchestrated according to the pulling progress, and the method comprises the following steps: if the pulling progress comprises that the first client does not pull the message to be pushed, pausing pushing the message to be pushed to a second client; if the pulling progress comprises the progress of pulling the message to be pushed by the first client, sending the publishing information of the message to be pushed to a second client according to the progress of pulling the message to be pushed by the first client, and requesting a third-party service or a resource center to pull the message to be pushed by the second client according to the publishing information of the message to be pushed; if the pulling progress comprises that the first client finishes pulling the message to be pushed, confirming the pulling condition of the message to be pushed of a second client, if it is determined according to the pull condition that the second client does not acquire the publishing information of the message to be pushed, sending the publishing information of the message to be pushed to the second client, if the second client is determined to be pulling the message to be pushed according to the pulling condition, monitoring the progress of the second client for pulling the message to be pushed, if the second client is determined to finish pulling the message to be pushed according to the pulling condition, and sending the publishing information of the message to be pushed to a third client, and requesting a third-party service or a resource center to pull the message to be pushed by the third client according to the publishing information of the message to be pushed.
In this embodiment, the message push platform orchestrates the push management of the message to be pushed of the second client according to the pull progress of the message to be pushed of the first client. Specifically, if the pulling progress of the message to be pushed of the first client includes that the first client does not pull the message to be pushed, it indicates that the first client fails to pull the message to be pushed from the third-party service or the resource center, and at this time, if the second client has entered the pulling flow of the message to be pushed, the message to be pushed is controlled to be suspended from being pushed to the second client, so that the message pushing platform can perform balanced control on the pushing operations of the message to be pushed of the first client and the second client. If the pulling progress of the message to be pushed of the first client comprises the progress of the first client pulling the message to be pushed, the fact that the first client establishes information interactive connection with a third-party service or a resource center and executes the pulling of the message to be pushed is indicated, if the second client does not establish information interactive connection with the third-party service or the resource center, the second client sends the issuing information of the message to be pushed to the second client according to the progress of the first client pulling the message to be pushed, the second client requests the third-party service or the resource center to pull the message to be pushed according to the issuing information of the message to be pushed, and therefore the message pushing platform can conduct balance control on the pushing operation of the message to be pushed of the first client and the second client.
And if the pulling progress of the message to be pushed of the first client comprises that the first client finishes pulling the message to be pushed, determining the pulling condition of the message to be pushed of the second client. At this time, the second client may be in any situation of having pulled the message to be pushed, executing the operation of pulling the message to be pushed, or not establishing a connection with the third-party service or the resource center. And if the second client does not acquire the publishing information of the message to be pushed according to the pulling condition, sending the publishing information of the message to be pushed to the second client so as to inform the second client to pull the message to be pushed from a third-party service or resource center. If the second client side is determined to be pulling the message to be pushed according to the pulling condition, other operations do not need to be executed on the second client side, and only the progress of the second client side in pulling the message to be pushed needs to be monitored. And if the second client finishes pulling the message to be pushed according to the pulling condition, sending the publishing information of the message to be pushed to a third client, and requesting a third-party service or a resource center to pull the message to be pushed by the third client according to the publishing information of the message to be pushed. And the third client is the client which does not pull the message to be pushed. Therefore, the message pushing platform can perform balance control on the pushing operation of the messages to be pushed of the first client and the second client.
One specific embodiment is given below, as shown in fig. 2:
first, after a first client, namely an agent client, is started, a request message pushing platform establishes a long connection and maintains heartbeat interaction, and reports client information to the message pushing platform. The message center issues the push message to the message push center. And the message pushing center sends the publishing information of the pushed message to the agent client. And the proxy client receives the release information and requests a third-party service or a resource center to acquire the push message. And the agent client reports the execution progress to the message pushing center. And after overall calculation, the message pushing center continues to push messages to other clients and enters the circular arrangement of pushing scheduling.
Therefore, the resource cost of the server can be controlled, the resource utilization rate is improved, the message pushing efficiency is improved to the maximum extent, and the overall pushing progress is promoted.
In an embodiment, the present invention further provides a message pushing management apparatus, which includes a sending module 302, a receiving module 304, and an orchestration module 306.
The sending module 302 is configured to send, when receiving publishing information of a message to be pushed, published by a message center, the publishing information of the message to be pushed to a first client, where the first client requests a third-party service or a resource center to pull the message to be pushed according to the publishing information of the message to be pushed.
In this embodiment, the message center orchestrates the push messages of the client, for example, determines the release information of the to-be-pushed message to be pushed to the client, and releases the release information of the to-be-pushed message to the message push platform. And when the message pushing platform receives the publishing information of the message to be pushed, which is published by the message center, the publishing information of the message to be pushed is sent to the first client. And when receiving the release information of the message to be pushed, the first client requests a third-party service or a resource center to pull the message to be pushed. The message pushing platform may send the network link address of the third-party service or resource center to the first client, and the first client requests the third-party service or resource center to pull the message to be pushed based on the publishing information of the message to be pushed and the network link address of the third-party service or resource center.
The third-party service or the resource center stores the message to be pushed and provides the message downloading party service for the outside. The first client pulls the message to be pushed to the request based on the publishing information of the message to be pushed and the network link address of the third-party service or the resource center. And the third-party service or the resource center returns the message to be pushed to the first client, so that the first client can pull the message to be pushed.
A receiving module 304, configured to receive a pull progress of the to-be-pushed message sent by the first client.
In this embodiment, when the first client pulls the message to be pushed from the third-party service or the resource center, the pulling progress of the message to be pushed is fed back to the message pushing platform. The pull progress may include any one of the first client having completed pulling of the message to be pushed, the first client pulling the message to be pushed and a proportion of the message to be pushed that has been pulled, and the first client not performing pulling of the message to be pushed. The message pushing platform receives a pulling progress of a message to be pushed sent by a first client.
The first client is a client of a service system, a client of a wireless OTT set top box, a client of a wireless router, a client of cloud sim card wireless equipment or a client of terminal equipment integrated with a wireless internet module; the second client is a client of the service system, a client of the wireless OTT set-top box, a client of the wireless router, a client of the cloud sim card wireless device or a client of the terminal device integrated with the wireless internet module.
A orchestration module 306, configured to orchestrate, according to the pull progress, push management of the message to be pushed of the second client. In this embodiment, the message push platform orchestrates the push management of the message to be pushed of the second client according to the pull progress of the first client. The first client and the second client are different clients.
The message push platform integrally stages push management of a message to be pushed of a second client according to the pull progress of the first client, and the push management comprises the following steps: and if the pulling progress of the first client represents that the first client finishes the message to be pushed, controlling the second client to pull the message to be pushed. And if the pulling progress of the first client indicates that the first client is pulling the message to be pushed, controlling the second client to be in a state of waiting for pulling the message to be pushed or in a state of starting to pull the message to be pushed.
When receiving the release information of the message to be pushed issued by the message center, the message to be pushed is sent to the first client, the first client requests a third-party service or a resource center to pull the message to be pushed according to the release information of the message to be pushed, the pulling progress of the message to be pushed sent by the first client is received, and the pushing management of the message to be pushed of the second client is overall planned according to the pulling progress. Therefore, management of message pushing and pulling of message pushing resources are separated, a third-party service or a resource center provides resource downloading service of the message pushing, a server side of the message pushing only needs to send issuing information of the message to be pushed to a client side, and resource downloading of the message to be pushed is not needed, so that resource occupation of the server side can be reduced, and resource utilization rate of the server side is improved. In addition, the message center can also comprehensively manage the message pushing of the first client and the second client, so that the message pushing efficiency is improved.
In one embodiment, before the step of sending the publishing information of the message to be pushed to the first client, the method further includes: receiving a long connection establishment request of the first client; responding to the long connection establishment request, and establishing long connection with the first client; receiving client information sent by the first client through the long connection; the sending, to the first client, the release information of the message to be pushed includes: and sending the release information of the message to be pushed to a first client according to the client information.
In this embodiment, after the first client is started, a networking request is initiated to the message push platform to request for establishing a long connection with the message push platform. The message pushing platform receives a long connection establishment request of the first client, responds to the long connection establishment request, establishes long connection with the first client and keeps heartbeat interaction. The first client sends client information to the message push platform through long connection. The client information may include account information of the first client, and the like. The message pushing platform identifies the first client according to the client information of the first client, so that the issuing information of the message to be pushed is sent to the first client.
In one embodiment, the pull progress of the message to be pushed sent by the first client includes any one of the message to be pushed that is not pulled by the first client, the progress of the message to be pushed that is pulled by the first client, and the pull of the message to be pushed that is completed by the first client.
Wherein, the pushing management of the message to be pushed of the second client is orchestrated according to the pulling progress, and the method comprises the following steps: if the pulling progress comprises that the first client does not pull the message to be pushed, pausing pushing the message to be pushed to a second client; if the pulling progress comprises the progress of pulling the message to be pushed by the first client, sending the publishing information of the message to be pushed to a second client according to the progress of pulling the message to be pushed by the first client, and requesting a third-party service or a resource center to pull the message to be pushed by the second client according to the publishing information of the message to be pushed; if the pulling progress comprises that the first client finishes pulling the message to be pushed, confirming the pulling condition of the message to be pushed of a second client, if it is determined according to the pull condition that the second client does not acquire the publishing information of the message to be pushed, sending the publishing information of the message to be pushed to the second client, if the second client is determined to be pulling the message to be pushed according to the pulling condition, monitoring the progress of the second client for pulling the message to be pushed, if the second client is determined to finish pulling the message to be pushed according to the pulling condition, and sending the publishing information of the message to be pushed to a third client, and requesting a third-party service or a resource center to pull the message to be pushed by the third client according to the publishing information of the message to be pushed.
In this embodiment, the message push platform orchestrates the push management of the message to be pushed of the second client according to the pull progress of the message to be pushed of the first client. Specifically, if the pulling progress of the message to be pushed of the first client includes that the first client does not pull the message to be pushed, it indicates that the first client fails to pull the message to be pushed from the third-party service or the resource center, and at this time, if the second client has entered the pulling flow of the message to be pushed, the message to be pushed is controlled to be suspended from being pushed to the second client, so that the message pushing platform can perform balanced control on the pushing operations of the message to be pushed of the first client and the second client. If the pulling progress of the message to be pushed of the first client comprises the progress of the first client pulling the message to be pushed, the fact that the first client establishes information interactive connection with a third-party service or a resource center and executes the pulling of the message to be pushed is indicated, if the second client does not establish information interactive connection with the third-party service or the resource center, the second client sends the issuing information of the message to be pushed to the second client according to the progress of the first client pulling the message to be pushed, the second client requests the third-party service or the resource center to pull the message to be pushed according to the issuing information of the message to be pushed, and therefore the message pushing platform can conduct balance control on the pushing operation of the message to be pushed of the first client and the second client.
And if the pulling progress of the message to be pushed of the first client comprises that the first client finishes pulling the message to be pushed, determining the pulling condition of the message to be pushed of the second client. At this time, the second client may be in any situation of having pulled the message to be pushed, executing the operation of pulling the message to be pushed, or not establishing a connection with the third-party service or the resource center. And if the second client does not acquire the publishing information of the message to be pushed according to the pulling condition, sending the publishing information of the message to be pushed to the second client so as to inform the second client to pull the message to be pushed from a third-party service or resource center. If the second client side is determined to be pulling the message to be pushed according to the pulling condition, other operations do not need to be executed on the second client side, and only the progress of the second client side in pulling the message to be pushed needs to be monitored. And if the second client finishes pulling the message to be pushed according to the pulling condition, sending the publishing information of the message to be pushed to a third client, and requesting a third-party service or a resource center to pull the message to be pushed by the third client according to the publishing information of the message to be pushed. And the third client is the client which does not pull the message to be pushed. Therefore, the message pushing platform can perform balance control on the pushing operation of the messages to be pushed of the first client and the second client.
For a specific limitation of the message push management apparatus, reference may be made to the above limitation on a message push management method, which is not described herein again. The modules in the message pushing management device can be wholly or partially implemented by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
The invention also provides a message pushing management system, which comprises a message center, a message pushing platform and a third-party service or resource center; the message center sends the release information of the message to be pushed to the message pushing platform; the message pushing platform sends the publishing information of the message to be pushed to a first client when receiving the publishing information of the message to be pushed issued by the message center, and the first client requests the third-party service or the resource center to pull the message to be pushed according to the publishing information of the message to be pushed; the message pushing platform receives the pulling progress of the message to be pushed sent from the first client; and the message pushing platform integrally stages the pushing management of the message to be pushed of the second client according to the pulling progress.
The first client is a client of a service system, a client of a wireless OTT set top box, a client of a wireless router, a client of cloud sim card wireless equipment or a client of terminal equipment integrated with a wireless internet access module; the second client is a client of the service system, a client of the wireless OTT set top box, a client of the wireless router, a client of the cloud sim card wireless device or a client of the terminal device integrated with the wireless internet module.
Specifically, the message center: and issuing the message. And issuing the message to a message pushing platform, and pushing the message to the first client by the message pushing platform. The first client is connected with the message pushing platform, receives the release information of the message to be pushed sent by the message pushing platform, requests resources from the third-party service/resource center/downloads the message to be pushed, and calls back the execution information to the message pushing platform. The message pushing platform maintains connection with the first client, receives information issued by the message center, executes an information issuing instruction to the first client, receives data information report of the first client, performs overall calculation and initiates information pushing again. Third party service/resource center: and the third party application service/responsible resource uploading and storing provides resource downloading service for the outside.
A message pushing workflow of a message pushing management system mainly comprises the following steps:
1. the first client starts.
2. After the first client side initializes the network connection, the first client side requests the message pushing platform to establish long connection, the connection is successfully established, the first client side information is reported, and the pushing message is also received.
3. The message center issues information to the message pushing platform, and the message center also requests the pushing platform to inquire the pushing condition.
4. And after receiving the information, the information pushing platform pushes the information to the client.
5. And after receiving the message, the first client enters other operations such as requesting a third-party service or resource downloading and pushing the message.
6. The first client submits execution information and calls back the pushing platform.
7. And the message pushing platform receives the execution callback information, and overall calculation is carried out to continue to push the message to a new client.
And returning to the 5 th point to continue the circulation processing.
In summary, the message push management system provided by the invention has the advantages of strong expansibility, unified access to the push platform management and control terminal standard, and flexible adaptation and support of various remote management and control terminals. The resource load of a third-party service or a resource center is pre-estimated, resources are squeezed as much as possible, the load is guaranteed, and the resource utilization rate is improved. The response type pushing mode promotes the progress of the whole pushing message to the greatest extent and improves the pushing efficiency.
In an embodiment of the present invention, an application program is stored on a computer-readable storage medium, and when the application program is executed by a processor, the application program implements a message push management method according to any one of the above embodiments. The computer-readable storage medium includes, but is not limited to, any type of disk including floppy disks, hard disks, optical disks, CD-ROMs, and magneto-optical disks, ROMs (Read-Only memories), RAMs (Random AcceSS memories), EPROMs (EraSable Programmable Read-Only memories), EEPROMs (Electrically EraSable Programmable Read-Only memories), flash memories, magnetic cards, or optical cards. That is, a storage device includes any medium that stores or transmits information in a form readable by a device (e.g., a computer, a cellular phone), and may be a read-only memory, a magnetic or optical disk, or the like.
The embodiment of the present invention further provides a computer application program, which runs on a computer, and the computer application program is configured to execute a message push management method according to any one of the above embodiments.
Fig. 4 is a schematic structural diagram of a computer device in the embodiment of the present invention.
An embodiment of the present invention further provides a computer device, as shown in fig. 4. The computer device comprises a processor 402, a memory 403, an input unit 404, and a display unit 405. Those skilled in the art will appreciate that the device configuration means shown in fig. 4 do not constitute a limitation of all devices and may include more or less components than those shown, or some components in combination. The memory 403 may be used to store the application 401 and various functional modules, and the processor 402 executes the application 401 stored in the memory 403, thereby performing various functional applications of the device and data processing. The memory may be internal or external memory, or include both internal and external memory. The memory may comprise read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or random access memory. The external memory may include a hard disk, a floppy disk, a ZIP disk, a usb-disk, a magnetic tape, etc. The disclosed memory includes, but is not limited to, these types of memory. The disclosed memory is by way of example only and not by way of limitation.
The input unit 404 is used for receiving input of signals and receiving keywords input by a user. The input unit 404 may include a touch panel and other input devices. The touch panel can collect touch operations of a user on or near the touch panel (for example, operations of the user on or near the touch panel by using any suitable object or accessory such as a finger, a stylus and the like) and drive the corresponding connecting device according to a preset program; other input devices may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., play control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like. The display unit 405 may be used to display information input by a user or information provided to the user and various menus of the terminal device. The display unit 405 may take the form of a liquid crystal display, an organic light emitting diode, or the like. The processor 402 is a control center of the terminal device, connects various parts of the entire device using various interfaces and lines, and performs various functions and processes data by running or executing software programs and/or modules stored in the memory 403 and calling data stored in the memory.
As one embodiment, the computer device includes: one or more processors 402, a memory 403, one or more applications 401, wherein the one or more applications 401 are stored in the memory 403 and configured to be executed by the one or more processors 402, and wherein the one or more applications 401 are configured to perform a message push management method in any of the above embodiments.
In addition, the message push management method, apparatus, system, computer device and storage medium provided by the embodiments of the present invention are described in detail above, and a specific example should be used herein to explain the principle and the implementation of the present invention, and the description of the above embodiments is only used to help understanding the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (10)
1. A message push management method, comprising:
when receiving the release information of a message to be pushed, which is released by a message center, the first client sends the release information of the message to be pushed to a first client, and the first client requests a third-party service or a resource center to pull the message to be pushed according to the release information of the message to be pushed;
receiving the pulling progress of the message to be pushed sent by the first client;
and comprehensively managing the pushing management of the message to be pushed of the second client according to the pulling progress.
2. The method according to claim 1, wherein the first client is a client of a service system, a client of a wireless OTT set-top box, a client of a wireless router, a client of a cloud sim card wireless device, or a client of a terminal device integrated with a wireless internet access module;
the second client is a client of the service system, a client of the wireless OTT set top box, a client of the wireless router, a client of the cloud sim card wireless device or a client of the terminal device integrated with the wireless internet module.
3. The method according to claim 1, wherein the step of sending the publishing information of the message to be pushed to the first client is preceded by:
receiving a long connection establishment request of the first client;
responding to the long connection establishment request, and establishing long connection with the first client;
receiving client information sent by the first client through the long connection;
the sending, to the first client, the release information of the message to be pushed includes:
and sending the release information of the message to be pushed to a first client according to the client information.
4. The method according to claim 1, wherein the pull progress of the to-be-pushed message sent by the first client includes any one of the first client not pulling the to-be-pushed message, the first client pulling progress of the to-be-pushed message, and the first client having completed pulling the to-be-pushed message.
5. The method of claim 4, wherein orchestrating the push management of the message to be pushed for the second client according to the pull schedule comprises:
if the pulling progress comprises that the first client does not pull the message to be pushed, pausing pushing the message to be pushed to a second client;
if the pulling progress comprises the progress of pulling the message to be pushed by the first client, sending the publishing information of the message to be pushed to a second client according to the progress of pulling the message to be pushed by the first client, and requesting a third-party service or a resource center to pull the message to be pushed by the second client according to the publishing information of the message to be pushed;
if the pulling progress comprises that the first client finishes pulling the message to be pushed, confirming the pulling condition of the message to be pushed of a second client, if it is determined according to the pull condition that the second client does not acquire the publishing information of the message to be pushed, sending the publishing information of the message to be pushed to the second client, if the second client is determined to be pulling the message to be pushed according to the pulling condition, monitoring the progress of the second client for pulling the message to be pushed, if the second client is determined to finish pulling the message to be pushed according to the pulling condition, and sending the publishing information of the message to be pushed to a third client, and requesting a third-party service or a resource center to pull the message to be pushed by the third client according to the publishing information of the message to be pushed.
6. A message push management device, the device comprising:
the system comprises a sending module, a receiving module and a sending module, wherein the sending module is used for sending the publishing information of the message to be pushed to a first client when the publishing information of the message to be pushed published by a message center is received, and the first client requests a third-party service or a resource center to pull the message to be pushed according to the publishing information of the message to be pushed;
the receiving module is used for receiving the pulling progress of the message to be pushed sent by the first client;
and the overall planning module is used for overall planning the pushing management of the message to be pushed of the second client according to the pulling progress.
7. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method of any of claims 1 to 5 are implemented when the computer program is executed by the processor.
8. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 5.
9. A message pushing management system is characterized by comprising a message center, a message pushing platform and a third-party service or resource center;
the message center sends the release information of the message to be pushed to the message pushing platform;
the message pushing platform sends the publishing information of the message to be pushed to a first client when receiving the publishing information of the message to be pushed issued by the message center, and the first client requests the third-party service or the resource center to pull the message to be pushed according to the publishing information of the message to be pushed;
the message pushing platform receives the pulling progress of the message to be pushed sent from the first client;
and the message pushing platform integrally stages the pushing management of the message to be pushed of the second client according to the pulling progress.
10. The system according to claim 9, wherein the first client is a client of a service system, a client of a wireless OTT set-top box, a client of a wireless router, a client of a cloud sim card wireless device, or a client of a terminal device integrated with a wireless internet access module;
the second client is a client of the service system, a client of the wireless OTT set top box, a client of the wireless router, a client of the cloud sim card wireless device or a client of the terminal device integrated with the wireless internet module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111578971.0A CN114286293B (en) | 2021-12-22 | 2021-12-22 | Message push management method, device, system, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111578971.0A CN114286293B (en) | 2021-12-22 | 2021-12-22 | Message push management method, device, system, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114286293A true CN114286293A (en) | 2022-04-05 |
| CN114286293B CN114286293B (en) | 2023-03-14 |
Family
ID=80874273
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111578971.0A Active CN114286293B (en) | 2021-12-22 | 2021-12-22 | Message push management method, device, system, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114286293B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115174587A (en) * | 2022-06-06 | 2022-10-11 | 蚂蚁区块链科技(上海)有限公司 | Data transmission system, method and device |
| CN115174587B (en) * | 2022-06-06 | 2024-05-03 | 蚂蚁区块链科技(上海)有限公司 | Data transmission system, method and device, computer readable storage medium and electronic equipment |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1509049A1 (en) * | 2003-08-20 | 2005-02-23 | Accenture Global Services GmbH | Methods and systems for providing information to mobile users over limited bandwidth |
| CN103312523A (en) * | 2012-03-16 | 2013-09-18 | 腾讯科技（深圳）有限公司 | Business reminding message pushing method, device and system |
| CN108768775A (en) * | 2018-05-30 | 2018-11-06 | 努比亚技术有限公司 | Information processing method, electronic equipment and computer storage media |
| CN109800008A (en) * | 2018-12-29 | 2019-05-24 | 深圳云天励飞技术有限公司 | Configure update method and Related product |
| CN110300050A (en) * | 2019-05-23 | 2019-10-01 | 中国平安人寿保险股份有限公司 | Information push method, device, computer equipment and storage medium |
| CN112492048A (en) * | 2020-12-14 | 2021-03-12 | 招商局金融科技有限公司 | Message synchronization method and device, electronic equipment and readable storage medium |
| CN113238808A (en) * | 2020-01-22 | 2021-08-10 | 北京沃东天骏信息技术有限公司 | Message pushing method and device |
| CN113783913A (en) * | 2020-08-31 | 2021-12-10 | 北京沃东天骏信息技术有限公司 | Message pushing management method and device |
-
2021
- 2021-12-22 CN CN202111578971.0A patent/CN114286293B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1509049A1 (en) * | 2003-08-20 | 2005-02-23 | Accenture Global Services GmbH | Methods and systems for providing information to mobile users over limited bandwidth |
| CN103312523A (en) * | 2012-03-16 | 2013-09-18 | 腾讯科技（深圳）有限公司 | Business reminding message pushing method, device and system |
| CN108768775A (en) * | 2018-05-30 | 2018-11-06 | 努比亚技术有限公司 | Information processing method, electronic equipment and computer storage media |
| CN109800008A (en) * | 2018-12-29 | 2019-05-24 | 深圳云天励飞技术有限公司 | Configure update method and Related product |
| CN110300050A (en) * | 2019-05-23 | 2019-10-01 | 中国平安人寿保险股份有限公司 | Information push method, device, computer equipment and storage medium |
| CN113238808A (en) * | 2020-01-22 | 2021-08-10 | 北京沃东天骏信息技术有限公司 | Message pushing method and device |
| CN113783913A (en) * | 2020-08-31 | 2021-12-10 | 北京沃东天骏信息技术有限公司 | Message pushing management method and device |
| CN112492048A (en) * | 2020-12-14 | 2021-03-12 | 招商局金融科技有限公司 | Message synchronization method and device, electronic equipment and readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 庄国强: "一种基于Netty的环保物联网实时双向通信模型研究", 《郑州师范教育》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115174587A (en) * | 2022-06-06 | 2022-10-11 | 蚂蚁区块链科技(上海)有限公司 | Data transmission system, method and device |
| CN115174587B (en) * | 2022-06-06 | 2024-05-03 | 蚂蚁区块链科技(上海)有限公司 | Data transmission system, method and device, computer readable storage medium and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114286293B (en) | 2023-03-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109936587B (en) | Control method, control device, electronic apparatus, and storage medium | |
| EP3355528A1 (en) | Methods for providing continuity in chatbot communications | |
| CN108958922B (en) | Method and device for executing task | |
| CN113132489A (en) | Method, device, computing equipment and medium for downloading file | |
| CN110166791B (en) | Connection establishing method, device, equipment and storage medium | |
| CN102752369B (en) | The supplying method of TV applications service and virtual content service platform | |
| CN113489772A (en) | Network request processing method and device and electronic equipment | |
| US20100241732A1 (en) | User Interfaces for Electronic Devices | |
| CN113312165B (en) | Task processing method and device | |
| CN112328362A (en) | Method for realizing function calculation service based on container technology | |
| US20040177353A1 (en) | Electronic device network having graceful denial of service | |
| CN108958933B (en) | Configuration parameter updating method, device and equipment of task executor | |
| CN111026406A (en) | Application running method, device and computer readable storage medium | |
| CN114296953A (en) | Multi-cloud heterogeneous system and task processing method | |
| CN114048441A (en) | Control method and device for login user, storage medium and terminal equipment | |
| CN114286293B (en) | Message push management method, device, system, computer equipment and storage medium | |
| CN111147885B (en) | Live broadcast room interaction method and device, readable medium and electronic equipment | |
| CN111767176B (en) | Method and device for remotely controlling terminal equipment | |
| WO2016202202A1 (en) | Device connection method and apparatus, and smart television system | |
| WO2023130748A1 (en) | Task processing method and apparatus for unmanned vehicle | |
| CN111770043A (en) | Game data communication method, device, storage medium and electronic equipment | |
| CN111479137B (en) | Method and device for providing line address, server and storage medium | |
| CN114244894A (en) | Halt and recovery service processing method and system, computer storage medium and electronic equipment | |
| CN114253582A (en) | Terminal equipment upgrade management method, device and system and computer equipment | |
| CN114090104A (en) | Applet starting control method and device |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |