Message event push method, message push terminal and readable storage medium

Abstract

The present invention relates to the field of computer technology, and in particular to a method for pushing message events, a message push terminal, and a readable storage medium, wherein the method comprises: upon receiving a message configuration request, starting a message configuration window; in a message configuration module in the message configuration window, configuring the notification type, interface information, and / or receiving address of the notifier of the message event according to the message configuration request; upon receiving a message push request, configuring the notifier information corresponding to the notifier according to the notification type, the interface information, and the receiving address of the notifier, wherein the notifier information includes in-station notifier information and out-station notifier information; and according to the configured notifier information, pushing the message event to the notifier. A plurality of push modes are realized, the effect of reducing the cost of message push is achieved, and the problem of how to combine volunteer service projects with a plurality of push modes is solved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a message event pushing method, a message pushing terminal and a readable storage medium. Background Art

[0002] In traditional volunteer services, when sending notifications or other event messages, the main way to send them is to send relevant messages via email. This single message push method is difficult to meet the current needs for real-time and accuracy of message push.

[0003] With the development of the Internet and smart phones, message push has gradually evolved into a variety of push methods such as mobile phone text messages, WeChat, and station messages. These push methods have made up for the lack of real-time performance of traditional email push. Therefore, a configuration method for relevant information of volunteer service projects is needed, so that volunteer service projects can be combined with multiple push methods, thereby improving the push efficiency of volunteer service messages.

[0004] The above contents are only used to assist in understanding the technical solution of the present invention and do not constitute an admission that the above contents are prior art. Summary of the invention

[0005] The main purpose of the present invention is to provide a method for pushing message events, aiming to solve the problem of how to combine volunteer service projects with multiple push methods.

[0006] To achieve the above object, the present invention provides a method for pushing a message event, the method comprising:

[0007] When receiving a message configuration request, start the message configuration window;

[0008] In the message configuration module in the message configuration window, configure the notification type, interface information and / or notification recipient address of the message event according to the message configuration request;

[0009] When receiving a message push request, configure the notifier information corresponding to the notifier according to the notification type, the interface information and the notifier receiving address, wherein the notifier information includes the in-station notifier information and the out-station notifier information;

[0010] According to the configured notification party information, the message event is pushed to the notification party.

[0011] Optionally, the notification types include on-site notifications and off-site notifications, the interface information includes volunteer information, volunteer team information and volunteer organization information, the notification party receiving address includes a SMS address, an email address, a public account address and an on-site letter address, and the notification party information includes a notification type, at least one interface information and at least one notification party receiving address.

[0012] Optionally, the step of configuring the notifying party information corresponding to the notifying party according to the notification type, the interface information and the notifying party receiving address includes:

[0013] When the notification type is the in-station notification, the interface information is at least one of the volunteer information and the volunteer team information, and the notification party receiving address is at least one of the email address and the in-station letter address, the notification party information is configured as the in-station notification party information;

[0014] When the notification type is the off-site notification, the interface information is at least one of the volunteer information, the volunteer team information and the volunteer organization information, and the notification party receiving address is at least one of the SMS address, the email address and the public account address, the notification party information is configured as the off-site notification party information.

[0015] Optionally, the step of pushing the message event to the notifying party according to the configured notifying party information includes:

[0016] According to the in-site notification party information, the message event is pushed to the notification party who has the push permission for the in-site notification party information;

[0017] And / or, based on the off-site notification party information, the message event is pushed to the notification party that has the push permission for the off-site notification party information.

[0018] Optionally, the message configuration request includes a first configuration request, the message configuration module includes a first sub-message configuration module, and the step of configuring the notification type, interface information and / or notifier receiving address of the message event according to the message configuration request includes:

[0019] Based on the first sub-message configuration module, generating a first sub-task window for configuring the notification type according to the first configuration request;

[0020] Acquire a first configuration parameter input in the first subtask window;

[0021] A notification type of the message event is determined according to the first configuration parameter.

[0022] Optionally, the message configuration request includes a second configuration request, the message configuration module includes a second sub-message configuration module, and the step of configuring the notification type, interface information and / or notifier receiving address of the message event according to the message configuration request includes:

[0023] Based on the second sub-message configuration module, generating a second sub-task window for configuring the interface information according to the second configuration request;

[0024] Acquire a second configuration parameter input in the second subtask window;

[0025] The interface information of the message event is determined according to the second configuration parameter.

[0026] Optionally, the message configuration request includes a third configuration request, the message configuration module includes a third sub-message configuration module, and the step of configuring the notification type, interface information and / or notifier receiving address of the message event according to the message configuration request includes:

[0027] Based on the third sub-message configuration module, generating a third sub-task window for configuring a notifying party receiving address according to the third configuration request;

[0028] Acquire a third configuration parameter input in the third subtask window;

[0029] The notification party receiving address of the message event is determined according to the third configuration parameter.

[0030] Optionally, before the step of configuring the notifier information corresponding to the notifier according to the notification type, the interface information and the notifier receiving address when receiving the message push request, the step includes:

[0031] Storing the message events configured within a preset time period into a preset record table;

[0032] The step of configuring the notifying party information corresponding to the notifying party according to the notification type, the interface information and the notifying party receiving address upon receiving the message push request comprises:

[0033] When receiving the message push request, determining whether there is a target message event corresponding to the message push request in the preset record table;

[0034] If so, obtaining the notification type, the interface information and the notifier receiving address of the target message event, and configuring the notifier information corresponding to the notifier according to the notification type, the interface information and the notifier receiving address;

[0035] If not, return to execute the step of configuring the notification type, interface information and / or notification recipient address of the message event according to the message configuration request in the message configuration module in the message configuration window.

[0036] In addition, to achieve the above-mentioned purpose, the present invention also provides a message push terminal, which includes: a memory, a processor, and a message event push program stored in the memory and runnable on the processor, and when the message event push program is executed by the processor, the steps of the message event push method as described above are implemented.

[0037] In addition, to achieve the above-mentioned purpose, the present invention also provides a computer-readable storage medium, on which a message event push program is stored, and when the message event push program is executed by a processor, the steps of the message event push method described above are implemented.

[0038] The embodiment of the present invention provides a method for pushing a message event, a message push terminal and a readable storage medium, wherein the method comprises: upon receiving a message configuration request, starting a message configuration window; in the message configuration module in the message configuration window, configuring the notification type, interface information and / or receiving address of the notification party of the message event according to the message configuration request; upon receiving a message push request, configuring the notification party information corresponding to the notification party according to the notification type, the interface information and the receiving address of the notification party, wherein the notification party information includes the in-station notification party information and the out-station notification party information; and according to the configured notification party information, pushing the message event to the notification party. By configuring the notification type, interface information and / or receiving address of the message event, and when receiving a message push request, the configured notification type, interface information and receiving address of the notification party are not configured, the sending and receiving of the message event are configured, thereby pushing message events to different types of notification parties, such as volunteer teams, volunteers, institutions, etc., and the push methods are diverse, including SMS push, email push, public account push and in-station push, thereby achieving the effect of reducing the cost of message push. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 A schematic diagram of the hardware architecture of a message push terminal involved in an embodiment of the present invention;

[0040] Figure 2 It is a flowchart of a first embodiment of a method for pushing message events of the present invention;

[0041] Figure 3 It is a flowchart of a second embodiment of a method for pushing message events of the present invention;

[0042] Figure 4 A schematic diagram of a message configuration window in a specific implementation of a method for pushing message events of the present invention;

[0043] Figure 5 A schematic diagram of a subtask window in a specific implementation of a method for pushing message events of the present invention;

[0044] Figure 6 A schematic diagram of another subtask window in a specific implementation of the method for pushing message events of the present invention;

[0045] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0046] This application configures different single or combined push methods through events. When sending events, they are sent to the recipient according to the configuration, supporting one-to-many, multi-institutional, and multi-position sending.

[0047] In order to better understand the above technical solution, exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments described herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0048] As an implementation solution, the hardware architecture of the message push terminal can be as follows Figure 1 shown.

[0049] The embodiment of the present invention relates to the hardware architecture of a message push terminal, which includes: a processor 101, such as a CPU, a memory 102, and a communication bus 103. The communication bus 103 is used to realize the connection and communication between these components.

[0050] The memory 102 may be a high-speed RAM memory or a stable memory, such as a disk memory. Figure 1 As shown, the memory 102 as a computer-readable storage medium may include a message event push program; and the processor 101 may be used to call the message event push program stored in the memory 102 and perform the following operations:

[0051] When receiving a message configuration request, start the message configuration window;

[0052] In the message configuration module in the message configuration window, configure the notification type, interface information and / or notification recipient address of the message event according to the message configuration request;

[0053] When receiving a message push request, configure the notifier information corresponding to the notifier according to the notification type, the interface information and the notifier receiving address, wherein the notifier information includes the in-station notifier information and the out-station notifier information;

[0054] According to the configured notification party information, the message event is pushed to the notification party.

[0055] In one embodiment, the processor 101 may be used to call a push program for a message event stored in the memory 102, and perform the following operations:

[0056] When the notification type is the in-station notification, the interface information is at least one of the volunteer information and the volunteer team information, and the notification party receiving address is at least one of the email address and the in-station letter address, the notification party information is configured as the in-station notification party information;

[0057] When the notification type is the off-site notification, the interface information is at least one of the volunteer information, the volunteer team information and the volunteer organization information, and the notification party receiving address is at least one of the SMS address, the email address and the public account address, the notification party information is configured as the off-site notification party information.

[0058] In one embodiment, the processor 101 may be used to call a push program for a message event stored in the memory 102, and perform the following operations:

[0059] According to the in-site notification party information, the message event is pushed to the notification party who has the push permission for the in-site notification party information;

[0060] And / or, based on the off-site notification party information, the message event is pushed to the notification party that has the push permission for the off-site notification party information.

[0061] In one embodiment, the processor 101 may be used to call a push program for a message event stored in the memory 102, and perform the following operations:

[0062] Based on the first sub-message configuration module, generating a first sub-task window for configuring the notification type according to the first configuration request;

[0063] Acquire a first configuration parameter input in the first subtask window;

[0064] A notification type of the message event is determined according to the first configuration parameter.

[0065] In one embodiment, the processor 101 may be used to call a push program for a message event stored in the memory 102, and perform the following operations:

[0066] Based on the second sub-message configuration module, generating a second sub-task window for configuring the interface information according to the second configuration request;

[0067] Acquire a second configuration parameter input in the second subtask window;

[0068] The interface information of the message event is determined according to the second configuration parameter.

[0069] In one embodiment, the processor 101 may be used to call a push program for a message event stored in the memory 102, and perform the following operations:

[0070] Based on the third sub-message configuration module, generating a third sub-task window for configuring a notifying party receiving address according to the third configuration request;

[0071] Acquire a third configuration parameter input in the third subtask window;

[0072] The notification party receiving address of the message event is determined according to the third configuration parameter.

[0073] In one embodiment, the processor 101 may be used to call a push program for a message event stored in the memory 102, and perform the following operations:

[0074] Storing the message events configured within a preset time period into a preset record table;

[0075] The step of configuring the notifying party information corresponding to the notifying party according to the notification type, the interface information and the notifying party receiving address upon receiving the message push request comprises:

[0076] When receiving the message push request, determining whether there is a target message event corresponding to the message push request in the preset record table;

[0077] If so, obtaining the notification type, the interface information and the notifier receiving address of the target message event, and configuring the notifier information corresponding to the notifier according to the notification type, the interface information and the notifier receiving address;

[0078] If not, return to execute the step of configuring the notification type, interface information and / or notification recipient address of the message event according to the message configuration request in the message configuration module in the message configuration window.

[0079] Based on the hardware architecture of the message push terminal based on computer technology, an embodiment of the method for pushing message events of the present invention is proposed.

[0080] Reference Figure 2 In the first embodiment, the method for pushing the message event includes the following steps:

[0081] Step S10, when a message configuration request is received, starting a message configuration window;

[0082] In this embodiment, when the message push terminal receives a message configuration request, the message configuration window is started. The message configuration request is a request sent by the target application installed in the message push terminal to configure the push method of the message event. The target application is an enterprise application running in the operating system of the message push terminal, in which the message push service module is pre-implanted. When the message push terminal executes the message push service module, the steps of the message event pusher of the present invention are executed. The message push terminal can be a mobile phone, a computer, a notebook, etc., which is not limited here. The message configuration window is a visual operation interface window of the message push service module. The message push terminal configures the message event according to the message configuration request in the message configuration window.

[0083] Step S20, in the message configuration module in the message configuration window, configuring the notification type, interface information and / or notification recipient address of the message event according to the message configuration request;

[0084] After the step of starting the message configuration window, according to the message configuration request, configure the notification type, interface information and / or notifier receiving address of the message event within the configuration according to the message configuration request.

[0085] Optionally, the message configuration request includes a first configuration request, a second configuration request and a third configuration request. The message configuration request is used to trigger a corresponding message configuration module in the message configuration window, wherein the first configuration request is used to trigger a first sub-message configuration module, the second configuration request is used to trigger a second sub-message configuration module, and the third configuration request is used to trigger a third sub-message configuration module.

[0086] Optionally, the message configuration window includes a first subtask window, a second subtask window, and a third subtask window. The first subtask window is used to configure the notification type of the message event, the second subtask window is used to configure the interface information of the message event, and the third subtask window is used to configure the notifier receiving address of the message event. The corresponding message configuration modules in different subtask windows are also different. The message configuration module is an integrated code block set in the subtask window. Different message configuration modules correspond to different functions. In this embodiment, the configuration module of the first subtask window corresponds to the first sub-message configuration module, and the first sub-message configuration module contains a code block for configuring the notification type of the message event; the configuration module of the second subtask window corresponds to the second sub-message configuration module, and the second sub-message configuration module contains a code block for configuring the interface information of the message event; the configuration module of the third subtask window corresponds to the third sub-message configuration module, and the third sub-message configuration module contains a code block for configuring the notifier receiving address of the message event.

[0087] Optionally, the notification type is divided into an in-site notification type and an off-site notification type. The in-site notification type is characterized by being pushed within the site. For example, when the message push terminal is a mobile phone, and the volunteer project APP is installed on the mobile phone, if the notification type is an in-site notification, the message event is pushed to the volunteer project APP. The off-site notification type is characterized by being pushed outside the site. For example, when the message push terminal is a computer, if the notification type is an off-site notification, the message event is pushed through external methods such as email and mobile phone text messages.

[0088] Optionally, the interface information includes volunteer information, volunteer team information, and volunteer organization information. Volunteer information is characterized as the notification party of the message event is the volunteer himself, volunteer team information is characterized as the notification party of the message event is the volunteer team (which can be the manager of the team or everyone in the team), and volunteer organization information is characterized as the notification party of the message event is the volunteer organization (which can be the management personnel in the local volunteer organization). Optionally, the interface information can be pre-grouped according to the subject information type and region.

[0089] Optionally, the notification recipient address includes a text message address, an email address, a public account address, and an internal letter address. The text message address is characterized by sending via text messages (such as mobile phone text messages); the email address is characterized by sending via email; the public account address is characterized by sending with the public account as the notification party; the internal letter address is characterized by sending within the site (such as a volunteer website). Different notification recipient addresses correspond to different notification groups, which can be configured according to actual needs.

[0090] Optionally, when the message configuration request is a first configuration request, a first subtask window is generated according to the first configuration request, and a first sub-message configuration module in the first subtask window is triggered, and when the first configuration parameter entered in the first subtask window is obtained, the notification type of the message event is determined according to the first configuration parameter, wherein the input object can be user input or automatically generated by the message push terminal.

[0091] Optionally, when the message configuration request is a second configuration request, a second subtask window is generated according to the second configuration request, and a second sub-message configuration module in the second subtask window is triggered; when the second configuration parameters entered in the second subtask window are obtained, the interface information of the message event is determined according to the second configuration parameters, wherein the input object can be user input or automatically generated by the message push terminal.

[0092] Optionally, when the message configuration request is a third configuration request, a third subtask window is generated according to the third configuration request, and a third sub-message configuration module in the third subtask window is triggered, and when the third configuration parameters entered in the third subtask window are obtained, the notification party receiving address of the message event is determined according to the third configuration parameters, wherein the input object can be user input or automatically generated by the message push terminal.

[0093] It should be noted that in this embodiment, when configuring a message event, the notification type, interface information, and the receiving address of the notifier can be selected one by one, or multiple message events can be configured at the same time. This is not limited in this embodiment. However, when pushing a message event, each message event needs to be configured with the notification type, interface information, and the receiving address of the notifier before it can be pushed.

[0094] Step S30, when receiving the message push request, configuring the notifier information corresponding to the notifier according to the notification type, the interface information and the notifier receiving address, the notifier information including the in-station notifier information and the out-station notifier information;

[0095] In this embodiment, after configuring the notification type, interface information and / or notifier receiving address of the message event, the notifier information corresponding to the notifier is configured according to the notification type, interface information and / or notifier receiving address, and the notifier information includes the in-site notifier information and the out-site notifier information. The in-site notifier information is characterized as the information that the notification object is within the site (such as the volunteer website) as the recipient of the message event, and the out-site notifier information is characterized as the information that the notification object is outside the website (such as a public account, email, SMS, etc.) as the recipient of the message event.

[0096] Optionally, the configuration conditions of the in-station notification party information may be: the notification type is in-station notification; the interface information is at least one of volunteer information and volunteer team information; the notification party receiving address is at least one of an email address and an in-station letter address. That is, when the message event is an in-station notification event, and the volunteer information and / or volunteer team information can be used as the target object for transmitting data, and the message event can be pushed through email and / or in-station letter, the notification party information is configured as the in-station notification party information.

[0097] Optionally, the configuration conditions of the off-site notification party information can be: the notification type is an off-site notification, the interface information is at least one of volunteer information, volunteer team information and volunteer organization information, and the notification party receiving address is at least one of a text message address, an email address and a public account address. That is, when the notification type of the message event is an off-site notification event, and at least one of the interface information of volunteer information, volunteer team information and volunteer organization information can be used as the target object for transmitting data, and the message event can be pushed through at least one of text messages, emails and public accounts, the notification party information is configured as the off-site notification party information.

[0098] Step S40: Push the message event to the notifying party according to the configured notifying party information.

[0099] In this embodiment, after configuring the notifying party information, the message event is pushed to the notifying party according to the configured notifying party information, wherein sending the message event can support one-to-many people sending, multi-institution sending, and multi-position sending.

[0100] In the technical solution provided in this embodiment, the notification type, interface information and / or receiving address of the notification party of the message event are configured, and when a message push request is received, the configured notification type, interface information and receiving address of the notification party, and the notification party information of the notification party of the message event are configured, the sending and receiving of the message event are configured, so as to push message events to different types of notification parties, such as volunteer teams, volunteers, organizations, etc., and the push methods are diverse, including SMS push, email push, public account push and site push, thereby achieving the effect of reducing the cost of message push.

[0101] Reference Figure 3 In the second embodiment, based on the first embodiment, before step S30, the steps include:

[0102] Step S50, storing the message events configured within a preset time period into a preset record table;

[0103] The step S30 comprises:

[0104] Step S31, upon receiving the message push request, determining whether there is a target message event corresponding to the message push request in the preset record table;

[0105] Step S32, if it exists, obtain the notification type, the interface information and the notifier receiving address of the target message event, and configure the notification party information corresponding to the notifier according to the notification type, the interface information and the notifier receiving address; if it does not exist, return to execute the message configuration module in the message configuration window, and configure the notification type, interface information and / or notification party receiving address of the message event according to the message configuration request.

[0106] Optionally, in order to improve the push efficiency of message events, in this embodiment, before receiving a message push request, message events within a preset time period will be stored in a preset record table, and the preset record table is stored in the memory of the message push terminal. When a message push request is received, it is determined whether there is a target message event corresponding to the message push request in the preset record table. If so, the notification type, interface information and notifier receiving address of the target message event are obtained, and the notifier information configuration of this step is executed according to the notification type, interface information and notifier receiving address of the target message event; if not, return to execute the message event configuration of the previous step.

[0107] In this embodiment, the preset time period is a high-frequency time period for message event push (for example, 8:00-22:00 every day). The message events configured in this time period are stored in a preset record table, so that when a message push request is received, the target message event corresponding to the message push request is quickly traversed from the preset record table, and the notification party information is configured according to the notification type, interface information and notification party receiving address of the target message event, and the target message event is pushed to the notification party according to the configured notification party information.

[0108] In the technical solution provided by this embodiment, by storing the message event configured within the preset time period into the preset record table, when receiving the message push request, it is determined whether there is a target message event corresponding to the message push request in the preset record table. If it exists, the notification type, the interface information and the notifier receiving address of the target message event are obtained, and the notifier information corresponding to the notifier is configured according to the notification type, the interface information and the notifier receiving address; if it does not exist, it returns to the message configuration module in the message configuration window and configures the notification type, interface information and / or notifier receiving address of the message event according to the message configuration request, thereby improving the push efficiency of message events.

[0109] In addition, illustratively, referring to Figure 4 , Figure 4 FIG. 1 is a schematic diagram of a message configuration window set by a method for pushing a message event according to a specific embodiment of the present invention. Clicking the “Reply” button under the operation column can pop up a message window as shown in FIG. Figure 5 The subtask window "Reply to Internal Message" shown is used to configure the internal message (ie, message event).

[0110] In addition, illustratively, referring to Figure 6 , Figure 6 This is a schematic diagram of a subtask window set up for a method for pushing message events based on the present invention in a specific embodiment of the present invention. In this subtask window, the message event is an email event, and the email events can be sorted by serial number, and the type, status, title and recipient (i.e., the pusher) of the message event can be displayed. The email event can also be restored and deleted through the corresponding buttons in the "Operation" column.

[0111] In addition, it can be understood by a person skilled in the art that all or part of the processes in the method for implementing the above embodiment can be completed by instructing the relevant hardware through a computer program. The computer program includes program instructions, and the computer program can be stored in a storage medium, which is a computer-readable storage medium. The program instructions are executed by at least one processor in the message push terminal to implement the process steps of the embodiment of the above method.

[0112] Therefore, the present invention also provides a computer-readable storage medium, which stores a message event push program. When the message event push program is executed by a processor, the various steps of the message event push method described in the above embodiment are implemented.

[0113] The computer-readable storage medium may be a USB flash drive, a mobile hard disk, a read-only memory (ROM), a magnetic disk, or an optical disk, etc., which may store program codes.

[0114] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0115] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a computer-readable storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present invention.

[0116] The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A method for pushing a message event, characterized in that: Applied to a message push terminal, the message push method includes: Storing the message events configured within a preset time period into a preset record table; When receiving a message configuration request, start the message configuration window; In the message configuration module in the message configuration window, configure the notification type, interface information and / or notification recipient address of the message event according to the message configuration request; When a message push request is received, the notifier information corresponding to the notifier is configured according to the notification type, the interface information and the notifier receiving address, the notifier information including the in-station notifier information and the out-station notifier information, including: when the message push request is received, determining whether there is a target message event corresponding to the message push request in the preset record table; if so, obtaining the notification type, the interface information and the notifier receiving address of the target message event, and configuring the notifier information corresponding to the notifier according to the notification type, the interface information and the notifier receiving address; if not, returning to execute the step of configuring the notification type, the interface information and / or the notifier receiving address of the message event in the message configuration module in the message configuration window according to the message configuration request; According to the configured notification party information, the message event is pushed to the notification party.

2. The method for pushing a message event according to claim 1, characterized in that: The notification types include in-site notifications and off-site notifications, the interface information includes volunteer information, volunteer team information and volunteer organization information, the notification party receiving address includes SMS address, email address, public account address and in-site letter address, and the notification party information includes a notification type, at least one interface information and at least one notification party receiving address.

3. The method for pushing a message event as claimed in claim 2, characterized in that: The step of configuring the notifying party information corresponding to the notifying party according to the notification type, the interface information and the notifying party receiving address comprises: When the notification type is the in-station notification, the interface information is at least one of the volunteer information and the volunteer team information, and the notification party receiving address is at least one of the email address and the in-station letter address, the notification party information is configured as the in-station notification party information; When the notification type is the off-site notification, the interface information is at least one of the volunteer information, the volunteer team information and the volunteer organization information, and the notification party receiving address is at least one of the SMS address, the email address and the public account address, the notification party information is configured as the off-site notification party information.

4. The method for pushing a message event as claimed in claim 3, characterized in that: The step of pushing the message event to the notification party according to the configured notification party information includes: According to the in-site notification party information, the message event is pushed to the notification party who has the push permission for the in-site notification party information; And / or, based on the off-site notification party information, the message event is pushed to the notification party that has the push permission for the off-site notification party information.

5. The method for pushing a message event as claimed in claim 2, characterized in that: The message configuration request includes a first configuration request, the message configuration module includes a first sub-message configuration module, and the step of configuring the notification type, interface information and / or notifier receiving address of the message event according to the message configuration request includes: Based on the first sub-message configuration module, generating a first sub-task window for configuring the notification type according to the first configuration request; Acquire a first configuration parameter input in the first subtask window; A notification type of the message event is determined according to the first configuration parameter.

6. The method for pushing a message event as claimed in claim 5, characterized in that: The message configuration request includes a second configuration request, the message configuration module includes a second sub-message configuration module, and the step of configuring the notification type, interface information and / or notifier receiving address of the message event according to the message configuration request includes: Based on the second sub-message configuration module, generating a second sub-task window for configuring the interface information according to the second configuration request; Acquire a second configuration parameter input in the second subtask window; The interface information of the message event is determined according to the second configuration parameter.

7. The method for pushing a message event as claimed in claim 6, characterized in that: The message configuration request includes a third configuration request, the message configuration module includes a third sub-message configuration module, and the step of configuring the notification type, interface information and / or notifier receiving address of the message event according to the message configuration request includes: Based on the third sub-message configuration module, generating a third sub-task window for configuring a notifying party receiving address according to the third configuration request; Acquire a third configuration parameter input in the third subtask window; The notification party receiving address of the message event is determined according to the third configuration parameter.

8. A message push terminal, characterized in that: The message push terminal includes: a memory, a processor, and a message event push program stored in the memory and executable on the processor. When the message event push program is executed by the processor, the steps of the message event push method according to any one of claims 1 to 7 are implemented.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a message event push program, and when the message event push program is executed by a processor, the steps of the message event push method according to any one of claims 1 to 7 are implemented.

Images