CN111711697A - Message pushing method, device, equipment and storage medium - Google Patents
Message pushing method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN111711697A CN111711697A CN202010552825.XA CN202010552825A CN111711697A CN 111711697 A CN111711697 A CN 111711697A CN 202010552825 A CN202010552825 A CN 202010552825A CN 111711697 A CN111711697 A CN 111711697A
- Authority
- CN
- China
- Prior art keywords
- message
- pushed
- pushing
- server
- application program
- 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 55
- 238000003860 storage Methods 0.000 title claims abstract description 12
- 230000002159 abnormal effect Effects 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 10
- 238000012545 processing Methods 0.000 claims description 10
- 238000012544 monitoring process Methods 0.000 claims description 2
- 230000006870 function Effects 0.000 description 11
- 230000008878 coupling Effects 0.000 description 7
- 238000010168 coupling process Methods 0.000 description 7
- 238000005859 coupling reaction Methods 0.000 description 7
- 238000004891 communication Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 239000000284 extract Substances 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000009826 distribution Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
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
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/56—Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the invention provides a message pushing method, a message pushing device and a message pushing storage medium, wherein a task management server generates and sends a to-do task to a message center after acquiring the to-do task; the message pushing server side obtains a message to be pushed from a message center, the message to be pushed comprises a target pushing mode and recipient information, a target application program interface corresponding to the target pushing mode is determined according to the message to be pushed, and the message to be pushed is pushed to terminal equipment corresponding to the recipient information through the target application program interface. The message center and the task management server are configured, application program interfaces of various pushing modes are integrated at the message pushing server, message pushing is executed by the message pushing server, the message pushing function and the task management server are decoupled, system stability and safety are improved, complexity and delay of message pushing are reduced, stable message pushing is guaranteed, expanding and upgrading operations of the pushing modes are facilitated, and the task management server is not affected.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a message pushing method, a message pushing device, message pushing equipment and a message pushing storage medium.
Background
In the task management process, after acquiring a proxy task of a certain participant, the task management server generally needs to send a notification message to the participant, or a proxy system of the participant. For example, if the recipient is a proxy, the message may be pushed in a manner of in-site message, Instant Messaging (IM), mail, or short message, and if the recipient is a proxy system, the message may be pushed in a manner of HTTP request or RPC (Remote Procedure Call).
In the prior art, since the task management server may need to push messages in different push manners, the task management server needs to integrate third party Application Programming Interfaces (APIs) in different push manners, and when a message needs to be pushed in a certain push manner, the corresponding API is called.
In the prior art, a task management server integrates a plurality of third-party application program interfaces, and the task management server depends on the third-party application programs, so that the system complexity of the task management server is high, the system stability is influenced, and meanwhile, the complexity and the delay of message pushing are also influenced, and the message cannot be stably pushed.
Disclosure of Invention
The embodiment of the invention provides a message pushing method, a message pushing device, message pushing equipment and a storage medium, which are used for stably pushing messages and improving the system stability of a task management server.
In a first aspect, an embodiment of the present invention provides a message pushing method, which is applied to a message pushing server, where the message pushing server integrates application program interfaces in at least two pushing manners, and the method includes:
acquiring a message to be pushed from a message center, wherein the message to be pushed comprises a target pushing mode and recipient information; the message to be pushed is generated and sent to the message center after the task management server side obtains the task to be handled;
determining a target application program interface corresponding to the target pushing mode according to the message to be pushed;
and pushing the message to be pushed to the terminal equipment corresponding to the recipient information through the target application program interface.
In a second aspect, an embodiment of the present invention provides a message pushing apparatus, which is applied to a message pushing server, where the message pushing server integrates application program interfaces in at least two pushing manners, and the apparatus includes:
the system comprises an acquisition module, a sending module and a sending module, wherein the acquisition module is used for acquiring a message to be pushed from a message center, and the message to be pushed comprises a target pushing mode and recipient information; the message to be pushed is generated and sent to the message center after the task management server side obtains the task to be handled;
the processing module is used for determining a target application program interface corresponding to the target pushing mode according to the message to be pushed;
and the sending module is used for pushing the message to be pushed to the terminal equipment corresponding to the recipient information through the target application program interface.
In a third aspect, an embodiment of the present invention provides an electronic device, including:
a memory for storing a computer program;
a processor for executing a computer program stored in the memory to implement the method according to the first aspect.
In a fourth aspect, the present invention provides a computer-readable storage medium, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, the computer-executable instructions are used to implement the method according to the first aspect.
The message pushing method, the device, the equipment and the storage medium provided by the embodiment of the invention are generated and sent to the message center after the task management server acquires the task to be handled; the method comprises the steps that a message to be pushed is obtained from a message center by a message pushing server side, the message to be pushed comprises a target pushing mode and recipient information, a target application program interface corresponding to the target pushing mode is determined according to the message to be pushed, and the message to be pushed is pushed to terminal equipment corresponding to the recipient information through the target application program interface. In the embodiment, the message center and the task management server are configured, application program interfaces of various pushing modes are integrated at the message pushing server, and message pushing is executed by the message pushing server independent of the task management server, so that the decoupling of the message pushing function and the task management server is realized, the coupling degree of the whole system is reduced, the stability and the safety of the system are improved, the complexity and the delay of message pushing are reduced, the stable pushing of messages is ensured, and the operations of expanding and upgrading the pushing modes are facilitated without affecting the task management server.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
Fig. 1 is a schematic diagram of a communication system of a message pushing method according to an embodiment of the present invention;
fig. 2 is a flowchart of a message pushing method according to an embodiment of the present invention;
fig. 3 is a flowchart of a message pushing method according to another embodiment of the present invention;
fig. 4 is a structural diagram of a message pushing apparatus according to an embodiment of the present invention;
fig. 5 is a block diagram of an electronic device according to an embodiment of the present invention.
With the above figures, certain embodiments of the invention have been illustrated and described in more detail below. The drawings and the description are not intended to limit the scope of the inventive concept in any way, but rather to illustrate it by those skilled in the art with reference to specific embodiments.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the invention, as detailed in the appended claims.
In the prior art, since the task management server may need to push messages in different push modes, the task management server needs to integrate third-party application program interfaces APIs in different push modes, and when a message needs to be pushed in a certain push mode, the corresponding API is called. In the prior art, a task management server integrates a plurality of third-party application program interfaces, and the task management server depends on the third-party application programs, so that the system complexity of the task management server is high, the system stability is influenced, and meanwhile, the complexity and the delay of message pushing are also influenced, and the message cannot be stably pushed.
Aiming at the technical problems, the invention integrates application program interfaces of various pushing modes into a message pushing server by configuring a message center and a task management server, the message pushing is executed by the message pushing server independent of the task management server, thereby realizing the decoupling of the message pushing function and the task management server, the task management server can mainly consider the core service of task management without paying attention to the message pushing service function, reducing the coupling degree of the whole system, respectively maintaining the core service and the message pushing service of the task management, improving the stability and the safety of the system, reducing the complexity and the delay of the message pushing and ensuring the stable pushing of the message.
The message pushing method provided by the invention can be applied to a communication system shown in fig. 1, and the communication system comprises a task management server 11, a message center 12 and a message pushing server 13, wherein the message pushing server is integrated with application program interfaces of at least two pushing modes, such as application program interfaces of WeChat pushing, mail pushing, short message pushing, HTTP requests, RPC requests and the like. The task management server is used for acquiring tasks to be handled, for example, the task management server can specifically acquire the flow of the tasks to be handled, and can generate a message to be pushed for notifying a task executor after the tasks to be handled are acquired, wherein the message to be pushed comprises a target pushing mode and recipient information, and the message to be pushed is sent to the message center; the message center sends the message to be pushed to the message pushing server, or the message pushing server extracts the message to be pushed from the message center; after the message pushing server side obtains the message to be pushed, a target application program interface corresponding to the target pushing mode is determined according to the message to be pushed, and the message to be pushed is pushed to the terminal equipment corresponding to the recipient information through the target application program interface.
Optionally, the message center may be a message queue or a database, and the message center may be implemented by using an independent server, or may be integrated on a task management server or a message push server. The task management server may be a server, a server cluster composed of a plurality of servers, or a cloud computing service center, and similarly, the message push server may also be a server, a server cluster composed of a plurality of servers, or a cloud computing service center.
The following describes the technical solutions of the present invention and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present invention will be described below with reference to the accompanying drawings.
Fig. 2 is a flowchart of a message pushing method according to an embodiment of the present invention. This embodiment provides a message pushing method, where an execution main body is a message pushing server, and the message pushing server integrates application program interfaces of at least two pushing modes, as shown in fig. 2, the message pushing method includes the following specific steps:
s201, obtaining a message to be pushed from a message center, wherein the message to be pushed comprises a target pushing mode and recipient information; the message to be pushed is generated by the task management server after the task to be processed is obtained and is sent to the message center.
In this embodiment, after the task management server obtains the to-be-done task, a message needs to be pushed to the task executor to notify the task executor to execute the to-be-done task, so when the to-be-pushed message is generated, the task executor is used as a receiver of the to-be-pushed message, and determines a target pushing mode, so that the to-be-pushed message carries a target pushing mode and receiver information. Of course, a message to be pushed may include multiple targeted push methods and/or multiple recipient information.
Further, the task management server sends the message to be pushed to the message center, and the message center sends the message to be pushed to the message pushing server, or the message pushing server extracts the message to be pushed from the message center, for example, the message to be pushed is extracted from the message center in a publish/subscribe manner. Optionally, the message center may adopt a message queue, such as a Fast Message Queue (FMQ), and may decouple the task management server from the message pushing function, and may implement asynchronous and peak-eliminating functions, so as to ensure the stability of the operation of the entire system, and the message queue has higher read-write performance, and may improve the efficiency of message pushing. In addition, the message center can also adopt a database, a production and consumption mode based on the database needs to be designed independently, and the read-write performance of the database is far inferior to that of the message middleware. In addition, the message center can also persist the messages to be pushed so as to facilitate management and query.
S202, determining a target application program interface corresponding to the target pushing mode according to the message to be pushed.
In this embodiment, after the message push server obtains the message to be pushed from the message center, the corresponding target application program interface API may be determined according to a target push manner included in the message to be pushed, for example, if the target push manner is a mail push manner, it is determined that the target application program interface is an API related to a mail, and if the target push manner is a short message push manner, it is determined that the target application program interface is an API related to a short message.
S203, pushing the message to be pushed to the terminal equipment corresponding to the receiver information through the target application program interface.
In this embodiment, after the target application program interface is determined, the message is pushed through the target application program interface, and the message to be pushed is pushed to the terminal device corresponding to the recipient information through the target application program interface. And when the message to be pushed comprises a plurality of target pushing modes, pushing the message to be pushed to the terminal equipment corresponding to the recipient information through target application program interfaces corresponding to the plurality of target pushing modes respectively.
In the message pushing method provided by this embodiment, after the task management server acquires the task to be handled, the task to be handled is generated and sent to the message center; the method comprises the steps that a message to be pushed is obtained from a message center by a message pushing server side, the message to be pushed comprises a target pushing mode and recipient information, a target application program interface corresponding to the target pushing mode is determined according to the message to be pushed, and the message to be pushed is pushed to terminal equipment corresponding to the recipient information through the target application program interface. In the embodiment, the message center and the task management server are configured, application program interfaces of various pushing modes are integrated at the message pushing server, and message pushing is executed by the message pushing server independent of the task management server, so that the decoupling of the message pushing function and the task management server is realized, the coupling degree of the whole system is reduced, the stability and the safety of the system are improved, the complexity and the delay of message pushing are reduced, the stable pushing of messages is ensured, and the operations of expanding and upgrading the pushing modes are facilitated without affecting the task management server.
On the basis of any of the above embodiments, the message pushing method further includes:
and if the message to be pushed is determined to be unsuccessfully pushed to the terminal equipment corresponding to the recipient information, the message to be pushed is pushed to the terminal equipment corresponding to the recipient information again.
In this embodiment, in the case of abnormal conditions such as network fluctuation, a situation of failure in pushing the message to be pushed may exist, so that a compensation mechanism after the failure in pushing the message is added, and when it is determined that the message to be pushed fails to be pushed, the message to be pushed may be pushed again, so as to avoid that the message to be pushed cannot reach the recipient and data is lost, thereby providing a basic guarantee for final consistency of data.
In this embodiment, the message to be pushed that fails to be pushed may be directly attempted to be pushed again by the message push server, or may be periodically pushed again, for example, the message to be pushed that fails to be pushed is pushed again at every predetermined time interval; in addition, the message to be pushed which fails to be pushed can be added to the message center again by the message pushing server, and the message center is responsible for sending the message to be pushed which fails to be pushed to the message pushing server again according to a certain strategy; or the message pushing server side can also push a failure notification to the message center, so that the message center adds the message to be pushed, which has failed in pushing, to the message queue again.
On the basis of the embodiment, if the message to be pushed is not successfully pushed to the terminal equipment corresponding to the recipient information, the times of the unsuccessful pushing of the message to be pushed are recorded;
further, the pushing the message to be pushed to the terminal device corresponding to the recipient information again may include:
and when the times of the unsuccessful pushing of the message to be pushed do not exceed the preset times, pushing the message to be pushed to the terminal equipment corresponding to the recipient information again.
In this embodiment, when the number of times of unsuccessful pushing of the message to be pushed does not exceed the preset number of times, the message to be pushed can be continuously pushed to the terminal device corresponding to the recipient information again; when the number of times of unsuccessful pushing of the message to be pushed exceeds the preset number of times, the message to be pushed can be stopped from being pushed again, a prompt message is sent to the terminal equipment of a manager to prompt that the message to be pushed fails to be pushed, and then the manager can manually process the message to be pushed on the terminal equipment of the manager, so that the message to be pushed which fails to be pushed for multiple times is prevented from occupying system resources, and the stability of the system is ensured.
On the basis of any of the above embodiments, as shown in fig. 3, the message to be pushed further includes a message identifier of the message to be pushed; pushing the message to be pushed to the terminal device corresponding to the recipient information, including:
s301, carrying out repeated judgment on the message to be pushed according to the message identification of the message to be pushed and the pre-recorded message identification of the pushed message;
s302, if the message identification of the message to be pushed is different from the message identification of the pushed message, and the message to be pushed is determined not to be a repeated message, pushing the message to be pushed to the terminal equipment corresponding to the recipient information.
In this embodiment, in order to avoid that a message to be pushed is repeatedly pushed, an idempotent determination may be performed through a unique message identifier of the message to be pushed, that is, after each message is pushed, the message identifier may be recorded, before the message to be pushed is pushed, the message identifier of the message to be pushed is matched with a pre-recorded message identifier of a pushed message, and a repetition determination is performed, and if the message identifier of the message to be pushed is different from any message identifier of a pushed message, it is determined that the message to be pushed is not repeated with the pushed message, and then the message to be pushed is pushed to a terminal device corresponding to recipient information, so that repeated pushing of the message is avoided, reliability of a pushing function is ensured, and occupation of system resources by the repeatedly pushed message and inconvenience for a recipient user are also avoided.
On the basis of any of the above embodiments, the message push server includes a cluster formed by at least two message push servers, and a registration center of the cluster, where each message push server includes an application program interface in at least one push mode. In the embodiment, considering that the message push service of the message push server side has high risk, frequent network input/output interaction and is easy to be abnormal, a cluster is built through at least two message push servers, each message push server is registered in a registration center of the cluster, the registration center realizes calling, discovery, load balancing and the like of the push service in the message push servers, and high availability of the message push service is ensured. Each message push server can integrate application program interfaces of all push modes, namely, push of any push mode can be realized; of course, each message push server may also integrate one or more application program interfaces of a specific push manner, so as to implement the push of the specific push manner.
Further, the acquiring, from the message center, the message to be pushed and the related data of the message to be pushed in S201 may specifically include:
acquiring the message to be pushed from the message center through the registration center;
selecting a target message pushing server from the cluster through the registration center, routing the message to be pushed to the target message pushing server, determining a target application program interface corresponding to the target pushing mode by the target message pushing server according to the message to be pushed, and pushing the message to be pushed to the terminal equipment corresponding to the recipient information through the target application program interface.
In this embodiment, when a message to be pushed is obtained from a message center, a registration center of a cluster obtains the message to be pushed, and then a target message push server is selected from the cluster, and the message to be pushed is routed to the target message push server, where the selected target message push server may be selected according to a load balancing mechanism, may be randomly selected, or may be selected according to other predetermined policies, and of course, if the message push servers may also be respectively integrated with one or more application program interfaces of a specific push manner, the message push server integrated with the application program interface of the target push manner may be selected as the target message push server according to the target push manner.
Further, after receiving the message to be pushed which is routed by the registration center, the target message pushing server may determine a target application program interface corresponding to a target pushing mode according to the message to be pushed, and push the message to be pushed to the terminal device corresponding to the recipient information through the target application program interface.
On the basis of the above embodiment, the registration center may also monitor the status of each message push server in the cluster; and if the message pushing server with the abnormal state is determined to exist, controlling the message pushing server with the abnormal state to stop working. The registration center monitors the state of each message pushing server in the cluster, so that the message pushing servers in abnormal states can be timely offline, the situation that the message to be pushed is routed to the message pushing server in the abnormal state again by the registration center to cause the message to be pushed out in an untimely manner is avoided, and the stability of the message pushing service is improved.
On the basis of any of the above embodiments, the method further comprises:
receiving a push mode upgrading instruction; and upgrading the application program and/or the application program interface of the push mode corresponding to the push mode upgrading instruction according to the push mode upgrading instruction.
In this embodiment, when one or more push modes need to be upgraded, a manager may send a push mode upgrade instruction to the message push server through the terminal device, and then the message push server may upgrade the corresponding push mode according to the push mode upgrade instruction. Specifically, if the push mode upgrade only needs to upgrade the application program and does not need to upgrade the application program interface, the push mode upgrade instruction may carry an upgrade file of the application program, such as an installation package or an upgrade package; if the push mode upgrading requires upgrading the application program interface, the application program interface needs to be reconfigured, and the push mode upgrading instruction can include relevant codes or data for reconfiguring the application program interface.
Fig. 4 is a structural diagram of a message pushing apparatus according to an embodiment of the present invention. The message pushing apparatus provided in this embodiment is applied to a message pushing server, where the message pushing server is integrated with application program interfaces of at least two pushing manners, and the message pushing apparatus may execute a processing procedure provided in the message pushing method embodiment, as shown in fig. 4, the message pushing apparatus 400 includes an obtaining module 401, a processing module 402, and a sending module 403.
An obtaining module 401, configured to obtain a message to be pushed from a message center, where the message to be pushed includes a target pushing mode and recipient information; the message to be pushed is generated and sent to the message center after the task management server side obtains the task to be handled;
a processing module 402, configured to determine, according to the message to be pushed, a target application program interface corresponding to the target pushing manner;
a sending module 403, configured to push the message to be pushed to a terminal device corresponding to the recipient information through the target application program interface.
On the basis of the foregoing embodiment, the sending module 403 is further configured to:
and if the message to be pushed is determined to be unsuccessfully pushed to the terminal equipment corresponding to the recipient information, the message to be pushed is pushed to the terminal equipment corresponding to the recipient information again.
On the basis of the foregoing embodiment, the sending module 403 is further configured to record the number of times that the message to be pushed is not successfully pushed;
the sending module 403, when pushing the message to be pushed to the terminal device corresponding to the recipient information again, is configured to:
and when the times of the unsuccessful pushing of the message to be pushed do not exceed the preset times, pushing the message to be pushed to the terminal equipment corresponding to the recipient information again.
On the basis of the foregoing embodiment, the sending module 403 is further configured to:
and when the times of unsuccessfully pushing the message to be pushed exceed the preset times, stopping the re-pushing of the message to be pushed, and sending a prompt message to the terminal equipment of a manager so as to prompt that the message to be pushed fails to be pushed.
On the basis of any of the above embodiments, the message to be pushed further includes a message identifier of the message to be pushed; the processing module 402 is further configured to perform a repetitive judgment on the message to be pushed according to the message identifier of the message to be pushed and a pre-recorded message identifier of a pushed message;
the sending module 403 is configured to, if the message identifier of the message to be pushed is different from the message identifier of the pushed message, determine that the message to be pushed is not a duplicate message, push the message to be pushed to the terminal device corresponding to the recipient information.
On the basis of any of the above embodiments, the message push server includes a cluster formed by at least two message push servers, and a registration center of the cluster, where each message push server includes an application program interface in at least one push mode;
when the obtaining module 401 obtains the message to be pushed and the related data of the message to be pushed from the message center, it is configured to:
acquiring the message to be pushed from the message center through the registration center;
selecting a target message pushing server from the cluster through the registration center, routing the message to be pushed to the target message pushing server, determining a target application program interface corresponding to the target pushing mode by the target message pushing server according to the message to be pushed, and pushing the message to be pushed to the terminal equipment corresponding to the recipient information through the target application program interface.
On the basis of any of the above embodiments, the processing module 402 is further configured to:
monitoring the state of each message push server in the cluster through the registration center;
and if the message pushing server with the abnormal state is determined to exist, controlling the message pushing server with the abnormal state to stop working.
On the basis of any of the above embodiments, the processing module 402 is further configured to:
receiving a push mode upgrading instruction;
and upgrading the application program and/or the application program interface of the push mode corresponding to the push mode upgrading instruction according to the push mode upgrading instruction.
On the basis of any of the above embodiments, the message center is a message queue or a database.
The message pushing apparatus provided in the embodiment of the present invention may be specifically configured to execute the method embodiments provided in fig. 2 to 3, and specific functions are not described herein again.
The message pushing device provided by the embodiment of the invention is generated and sent to the message center after the task management server side obtains the task to be handled; the method comprises the steps that a message to be pushed is obtained from a message center by a message pushing server side, the message to be pushed comprises a target pushing mode and recipient information, a target application program interface corresponding to the target pushing mode is determined according to the message to be pushed, and the message to be pushed is pushed to terminal equipment corresponding to the recipient information through the target application program interface. In the embodiment, the message center and the task management server are configured, application program interfaces of various pushing modes are integrated at the message pushing server, and message pushing is executed by the message pushing server independent of the task management server, so that the decoupling of the message pushing function and the task management server is realized, the coupling degree of the whole system is reduced, the stability and the safety of the system are improved, the complexity and the delay of message pushing are reduced, the stable pushing of messages is ensured, and the operations of expanding and upgrading the pushing modes are facilitated without affecting the task management server.
Fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present invention. The electronic device provided by the embodiment of the present invention is the message push server in the above embodiment, and can execute the processing procedure provided by the message push method embodiment. As shown in fig. 5, the electronic device 50 comprises a memory 51, a processor 52, computer programs and a communication interface 53; wherein a computer program is stored in the memory 51 and is configured to execute the message push method described in the above embodiments by the processor 52.
The electronic device in the embodiment shown in fig. 5 may be configured to execute the technical solution of the above-mentioned message pushing method embodiment, and the implementation principle and the technical effect are similar, which are not described herein again.
In addition, the present embodiment also provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the message pushing method described in the foregoing embodiments.
The present application also provides a computer program comprising a program code for performing the message push method according to the above embodiments when the computer program is run by a computer.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) or a processor (processor) to execute some steps of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
It is obvious to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be performed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to perform all or part of the above described functions. For the specific working process of the device described above, reference may be made to the corresponding process in the foregoing method embodiment, which is not described herein again.
Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the embodiments of the present invention, and are not limited thereto; although embodiments of the present invention have been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (15)
1. A message pushing method is applied to a message pushing server side, the message pushing server side is integrated with application program interfaces of at least two pushing modes, and the method comprises the following steps:
acquiring a message to be pushed from a message center, wherein the message to be pushed comprises a target pushing mode and recipient information; the message to be pushed is generated and sent to the message center after the task management server side obtains the task to be handled;
determining a target application program interface corresponding to the target pushing mode according to the message to be pushed;
and pushing the message to be pushed to the terminal equipment corresponding to the recipient information through the target application program interface.
2. The method of claim 1, further comprising:
and if the message to be pushed is determined to be unsuccessfully pushed to the terminal equipment corresponding to the recipient information, the message to be pushed is pushed to the terminal equipment corresponding to the recipient information again.
3. The method of claim 2, further comprising:
recording the times of unsuccessful pushing of the message to be pushed;
the re-pushing the message to be pushed to the terminal device corresponding to the recipient information includes:
and when the times of the unsuccessful pushing of the message to be pushed do not exceed the preset times, pushing the message to be pushed to the terminal equipment corresponding to the recipient information again.
4. The method of claim 3, further comprising:
and when the times of unsuccessfully pushing the message to be pushed exceed the preset times, stopping the re-pushing of the message to be pushed, and sending a prompt message to the terminal equipment of a manager so as to prompt that the message to be pushed fails to be pushed.
5. The method of claim 1, wherein the message to be pushed further comprises a message identifier of the message to be pushed; pushing the message to be pushed to the terminal device corresponding to the recipient information, including:
carrying out repeatability judgment on the message to be pushed according to the message identification of the message to be pushed and the pre-recorded message identification of the pushed message;
and if the message identification of the message to be pushed is different from the message identification of the pushed message, determining that the message to be pushed is not a repeated message, and pushing the message to be pushed to the terminal equipment corresponding to the recipient information.
6. The method according to claim 1, wherein the message push server comprises a cluster formed by at least two message push servers, and a registration center of the cluster, wherein each message push server comprises at least one push mode application program interface;
the obtaining of the message to be pushed and the related data of the message to be pushed from the message center includes:
acquiring the message to be pushed from the message center through the registration center;
selecting a target message pushing server from the cluster through the registration center, routing the message to be pushed to the target message pushing server, determining a target application program interface corresponding to the target pushing mode by the target message pushing server according to the message to be pushed, and pushing the message to be pushed to the terminal equipment corresponding to the recipient information through the target application program interface.
7. The method of claim 5, further comprising:
monitoring the state of each message push server in the cluster through the registration center;
and if the message pushing server with the abnormal state is determined to exist, controlling the message pushing server with the abnormal state to stop working.
8. The method of claim 1, further comprising:
receiving a push mode upgrading instruction;
and upgrading the application program and/or the application program interface of the push mode corresponding to the push mode upgrading instruction according to the push mode upgrading instruction.
9. The method according to any of claims 1-8, wherein the message center is a message queue or a database.
10. A message pushing apparatus, applied to a message pushing server, where the message pushing server integrates application program interfaces of at least two pushing modes, and the apparatus includes:
the system comprises an acquisition module, a sending module and a sending module, wherein the acquisition module is used for acquiring a message to be pushed from a message center, and the message to be pushed comprises a target pushing mode and recipient information; the message to be pushed is generated and sent to the message center after the task management server side obtains the task to be handled;
the processing module is used for determining a target application program interface corresponding to the target pushing mode according to the message to be pushed;
and the sending module is used for pushing the message to be pushed to the terminal equipment corresponding to the recipient information through the target application program interface.
11. The apparatus of claim 10, wherein the sending module is further configured to:
and if the message to be pushed is determined to be unsuccessfully pushed to the terminal equipment corresponding to the recipient information, the message to be pushed is pushed to the terminal equipment corresponding to the recipient information again.
12. The apparatus of claim 11,
the sending module is further configured to record the number of times that the message to be pushed is not successfully pushed;
when the sending module pushes the message to be pushed to the terminal device corresponding to the recipient information again, the sending module is configured to:
and when the times of the unsuccessful pushing of the message to be pushed do not exceed the preset times, pushing the message to be pushed to the terminal equipment corresponding to the recipient information again.
13. The apparatus of claim 12, wherein the sending module is further configured to:
and when the times of unsuccessfully pushing the message to be pushed exceed the preset times, stopping the re-pushing of the message to be pushed, and sending a prompt message to the terminal equipment of a manager so as to prompt that the message to be pushed fails to be pushed.
14. An electronic device, comprising:
a memory for storing a computer program;
a processor for executing a computer program stored in the memory to implement the method of any one of claims 1-9.
15. A computer-readable storage medium having computer-executable instructions stored thereon, which when executed by a processor, perform the method of any one of claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010552825.XA CN111711697A (en) | 2020-06-17 | 2020-06-17 | Message pushing method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010552825.XA CN111711697A (en) | 2020-06-17 | 2020-06-17 | Message pushing method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111711697A true CN111711697A (en) | 2020-09-25 |
Family
ID=72540894
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010552825.XA Pending CN111711697A (en) | 2020-06-17 | 2020-06-17 | Message pushing method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111711697A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112182377A (en) * | 2020-09-28 | 2021-01-05 | 厦门美柚股份有限公司 | Message pushing processing method, device, terminal and medium |
| CN112468600A (en) * | 2021-02-02 | 2021-03-09 | 上海有孚智数云创数字科技有限公司 | Application message notification method, system and storage medium based on network matrix |
| CN112532681A (en) * | 2020-10-16 | 2021-03-19 | 深圳市科漫达智能管理科技有限公司 | Parking lot software data exception handling method and device |
| CN112769889A (en) * | 2020-11-18 | 2021-05-07 | 青岛海尔科技有限公司 | Service data pushing method and device, storage medium and electronic device |
| CN112788128A (en) * | 2020-12-31 | 2021-05-11 | 青岛海尔科技有限公司 | Business information pushing method and device, storage medium and electronic device |
| CN114338792A (en) * | 2021-12-29 | 2022-04-12 | 掌阅科技股份有限公司 | Application message pushing method, electronic equipment and storage medium |
| CN114553946A (en) * | 2022-01-29 | 2022-05-27 | 北京金堤科技有限公司 | Method and device for processing message |
| CN115242870A (en) * | 2022-06-23 | 2022-10-25 | 宁波三星医疗电气股份有限公司 | Electricity consumption data pushing method and device, server and computer readable storage medium |
| CN115550093A (en) * | 2022-09-13 | 2022-12-30 | 海尔优家智能科技（北京）有限公司 | Application research method, storage medium and electronic device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103199968A (en) * | 2012-01-09 | 2013-07-10 | 卓望数码技术（深圳）有限公司 | Sending method of messages and system |
| CN104468649A (en) * | 2013-09-16 | 2015-03-25 | 北大方正集团有限公司 | Server, terminal, data pushing system and data pushing method |
| WO2016182271A1 (en) * | 2015-05-08 | 2016-11-17 | 주식회사 카우치그램 | Method and system for transmitting/receiving push data |
| CN109639782A (en) * | 2018-11-30 | 2019-04-16 | 中体彩科技发展有限公司 | Message sends platform, method |
| CN110149392A (en) * | 2019-05-17 | 2019-08-20 | 优信拍（北京）信息科技有限公司 | A kind of management method and device of PUSH message |
| CN110300050A (en) * | 2019-05-23 | 2019-10-01 | 中国平安人寿保险股份有限公司 | Information push method, device, computer equipment and storage medium |
-
2020
- 2020-06-17 CN CN202010552825.XA patent/CN111711697A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103199968A (en) * | 2012-01-09 | 2013-07-10 | 卓望数码技术（深圳）有限公司 | Sending method of messages and system |
| CN104468649A (en) * | 2013-09-16 | 2015-03-25 | 北大方正集团有限公司 | Server, terminal, data pushing system and data pushing method |
| WO2016182271A1 (en) * | 2015-05-08 | 2016-11-17 | 주식회사 카우치그램 | Method and system for transmitting/receiving push data |
| CN109639782A (en) * | 2018-11-30 | 2019-04-16 | 中体彩科技发展有限公司 | Message sends platform, method |
| CN110149392A (en) * | 2019-05-17 | 2019-08-20 | 优信拍（北京）信息科技有限公司 | A kind of management method and device of PUSH message |
| CN110300050A (en) * | 2019-05-23 | 2019-10-01 | 中国平安人寿保险股份有限公司 | Information push method, device, computer equipment and storage medium |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112182377A (en) * | 2020-09-28 | 2021-01-05 | 厦门美柚股份有限公司 | Message pushing processing method, device, terminal and medium |
| CN112532681A (en) * | 2020-10-16 | 2021-03-19 | 深圳市科漫达智能管理科技有限公司 | Parking lot software data exception handling method and device |
| CN112769889A (en) * | 2020-11-18 | 2021-05-07 | 青岛海尔科技有限公司 | Service data pushing method and device, storage medium and electronic device |
| CN112788128A (en) * | 2020-12-31 | 2021-05-11 | 青岛海尔科技有限公司 | Business information pushing method and device, storage medium and electronic device |
| CN112468600A (en) * | 2021-02-02 | 2021-03-09 | 上海有孚智数云创数字科技有限公司 | Application message notification method, system and storage medium based on network matrix |
| CN112468600B (en) * | 2021-02-02 | 2021-04-06 | 上海有孚智数云创数字科技有限公司 | Application message notification method, system and storage medium based on network matrix |
| CN114338792A (en) * | 2021-12-29 | 2022-04-12 | 掌阅科技股份有限公司 | Application message pushing method, electronic equipment and storage medium |
| CN114553946A (en) * | 2022-01-29 | 2022-05-27 | 北京金堤科技有限公司 | Method and device for processing message |
| CN114553946B (en) * | 2022-01-29 | 2024-01-19 | 北京金堤科技有限公司 | Method and device for processing message |
| CN115242870A (en) * | 2022-06-23 | 2022-10-25 | 宁波三星医疗电气股份有限公司 | Electricity consumption data pushing method and device, server and computer readable storage medium |
| CN115242870B (en) * | 2022-06-23 | 2023-10-27 | 宁波三星医疗电气股份有限公司 | Power consumption data pushing method, device, server and computer readable storage medium |
| CN115550093A (en) * | 2022-09-13 | 2022-12-30 | 海尔优家智能科技（北京）有限公司 | Application research method, storage medium and electronic device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111711697A (en) | Message pushing method, device, equipment and storage medium | |
| CN108449410B (en) | Message management method, system and related device in cloud platform | |
| CN108388479B (en) | Delayed message pushing method and device, computer equipment and storage medium | |
| US8938510B2 (en) | On-demand mailbox synchronization and migration system | |
| CN111897633A (en) | Task processing method and device | |
| CN112328418B (en) | Method and system for improving MQ synchronization reliability | |
| US20090138751A1 (en) | De-centralized nodal failover handling | |
| CN111625301A (en) | Idempotent processing method, apparatus, device and storage medium | |
| CN111666145A (en) | Message processing method and system of message queue and computer equipment | |
| CN111200606A (en) | Deep learning model task processing method, system, server and storage medium | |
| CN112395107A (en) | Tax control equipment control method and device, storage medium and electronic equipment | |
| CN112559461A (en) | File transmission method and device, storage medium and electronic equipment | |
| CN110138753B (en) | Distributed message service system, method, apparatus, and computer-readable storage medium | |
| CN111541762A (en) | Data processing method, management server, device and storage medium | |
| CN111124717A (en) | Message delivery method, system and computer storage medium | |
| CN113064740A (en) | Message processing method and device | |
| CN114844809A (en) | Multi-factor arbitration method and device based on network heartbeat and kernel disk heartbeat | |
| CN113971098A (en) | RabbitMQ consumption management method and system | |
| US9860149B2 (en) | Continuous monitoring of data servers using a shadowing proxy | |
| CN111831503B (en) | Monitoring method based on monitoring agent and monitoring agent device | |
| CN115981826A (en) | Task scheduling processing method and device, computer equipment and readable storage medium | |
| CN115629909A (en) | Service data processing method and device, electronic equipment and storage medium | |
| CN114938388A (en) | Distributed data transmission method, device, system and storage medium | |
| CN114374657A (en) | Data processing method and device | |
| CN112463616A (en) | Chaos testing method and device for Kubernetes container platform |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200925 |