CN116260783A - Message event pushing method, message pushing terminal and readable storage medium - Google Patents
Message event pushing method, message pushing terminal and readable storage medium Download PDFInfo
- Publication number
- CN116260783A CN116260783A CN202211088675.7A CN202211088675A CN116260783A CN 116260783 A CN116260783 A CN 116260783A CN 202211088675 A CN202211088675 A CN 202211088675A CN 116260783 A CN116260783 A CN 116260783A
- Authority
- CN
- China
- Prior art keywords
- message
- notification
- information
- pushing
- notifier
- 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 47
- 238000004891 communication Methods 0.000 claims description 6
- 230000008520 organization Effects 0.000 claims description 6
- 230000000694 effects Effects 0.000 abstract description 3
- 238000010586 diagram Methods 0.000 description 6
- 238000004590 computer program Methods 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention relates to the technical field of computers, in particular to a message event pushing method, a message pushing terminal and a readable storage medium, wherein the method comprises the following steps: when a message configuration request is received, a message configuration window is started; configuring the notification type, interface information and/or notification party receiving address of the message event according to the message configuration request in a message configuration module in the message configuration window; when a message push request is received, configuring notification party information corresponding to a notification party according to the notification type, the interface information and the notification party receiving address, wherein the notification party information comprises in-station notification party information and out-of-station notification party information; and pushing the message event to the notifier according to the configured notifier information. The method realizes pushing in multiple modes, achieves the effect of reducing message pushing cost, and solves the problem of how to combine volunteer service items with multiple pushing modes.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method for pushing a message event, a message pushing terminal, and a readable storage medium.
Background
In the conventional volunteer service, when a message such as a notification notice or other event is sent to push, the related message is mainly sent by way of mail. The single message pushing mode is difficult to meet the current requirements on the instantaneity and the accuracy of message pushing.
Along with the development of the Internet and the smart phone, message pushing gradually derives various pushing modes such as mobile phone short messages, weChat, in-station messages and the like. The pushing modes well make up the defect of insufficient instantaneity of the traditional mail pushing. Therefore, a configuration mode of relevant information of the volunteer service items is needed, so that the volunteer service items are combined with various pushing modes, and the pushing efficiency of the volunteer service messages is improved.
The foregoing is provided merely for the purpose of facilitating understanding of the technical solutions of the present invention and is not intended to represent an admission that the foregoing is prior art.
Disclosure of Invention
The invention mainly aims to provide a pushing method of message events, which aims to solve the problem of how to combine volunteer service items with various pushing modes.
In order to achieve the above object, the present invention provides a method for pushing a message event, including:
when a message configuration request is received, a message configuration window is started;
configuring the notification type, interface information and/or notification party receiving address of the message event according to the message configuration request in a message configuration module in the message configuration window;
when a message push request is received, configuring notification party information corresponding to a notification party according to the notification type, the interface information and the notification party receiving address, wherein the notification party information comprises in-station notification party information and out-of-station notification party information;
and pushing the message event to the notifier according to the configured notifier information.
Optionally, the notification types include an in-station notification and an out-of-station notification, the interface information includes volunteer information, volunteer team information, and volunteer institution information, the notification party receiving address includes a short message address, a mail address, a public number address, and an in-station message address, and the notification party information includes a notification type, at least one interface information, and at least one notification party receiving address.
Optionally, the step of configuring the notifier information corresponding to the notifier according to the notification type, the interface information and the receiving address of the notifier includes:
configuring the notifier information as the in-station notifier information 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 notifier reception address is at least one of the mail address and the in-station communication address;
and 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 institution information, and the notification party receiving address is at least one of the short message address, the mail address and the public number address, the notification party information is configured as the off-site notification party information.
Optionally, the step of pushing the message event to the notifier according to the configured notifier information includes:
pushing the message event to the notifier having the pushing authority of the in-station notifier information according to the in-station notifier information;
and/or pushing the message event to the notifier having the pushing authority of the information of the out-of-station notifier according to the information of the out-of-station notifier.
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 a notification type, interface information and/or a notification party receiving address of the message event according to the message configuration request includes:
generating a first subtask window for configuring the notification type according to the first configuration request based on the first sub-message configuration module;
acquiring a first configuration parameter input in the first subtask window;
and determining the notification type of the message event according to the first configuration parameter.
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, the interface information and/or the notification party receiving address of the message event according to the message configuration request includes:
generating a second subtask window for configuring the interface information according to the second configuration request based on the second sub-message configuration module;
acquiring a second configuration parameter input in the second subtask window;
and determining the interface information of the message event according to the second configuration parameters.
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, the interface information and/or the notification party receiving address of the message event according to the message configuration request includes:
generating a third subtask window for configuring a notification party receiving address according to the third configuration request based on the third sub-message configuration module;
acquiring a third configuration parameter input in the third subtask window;
and determining the receiving address of the notifier of the message event according to the third configuration parameters.
Optionally, before the step of configuring the notifier information corresponding to the notifier according to the notification type, the interface information and the receiving address of the notifier when the message push request is received, the method includes:
storing the configured message event in a preset time period into a preset record table;
when receiving a message push request, the step of configuring the information of the notifier corresponding to the notifier according to the notification type, the interface information and the receiving address of the notifier comprises the following steps:
when the message pushing request is received, determining whether a target message event corresponding to the message pushing request exists in the preset record table;
if yes, acquiring the notification type, the interface information and the notification party receiving address of the target message event, and configuring notification party information corresponding to a notification party according to the notification type, the interface information and the notification party receiving address;
and if not, returning to the step of executing the message configuration module in the message configuration window, and configuring the notification type, interface information and/or notification party receiving address of the message event according to the message configuration request.
In addition, in order to achieve the above object, the present invention further provides a message pushing terminal, including: the message event pushing device comprises a memory, a processor and a message event pushing program which is stored in the memory and can run on the processor, wherein the message event pushing program realizes the steps of the message event pushing method when being executed by the processor.
In addition, to achieve the above object, the present invention also provides a computer-readable storage medium having stored thereon a push program of a message event, which when executed by a processor, implements the steps of the push method of a message event as described above.
The embodiment of the invention provides a message event pushing method, a message pushing terminal and a readable storage medium, wherein the method comprises the following steps: when a message configuration request is received, a message configuration window is started; configuring the notification type, interface information and/or notification party receiving address of the message event according to the message configuration request in a message configuration module in the message configuration window; when a message push request is received, configuring notification party information corresponding to a notification party according to the notification type, the interface information and the notification party receiving address, wherein the notification party information comprises in-station notification party information and out-of-station notification party information; and pushing the message event to the notifier according to the configured notifier information. The notification type, the interface information and/or the notification party receiving address of the message event are configured, when a message pushing request is received, the configured notification type, interface information and notification party receiving address are not used, and the notification party information of the message event is configured in the sending and receiving of the message event, so that the message event is pushed to different notification parties such as volunteers, institutions and the like, and the pushing modes are various, including short message pushing, mail pushing, public number pushing and in-station pushing, so that the effect of reducing the message pushing cost is achieved.
Drawings
Fig. 1 is a schematic diagram of a hardware architecture of a message push terminal according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a first embodiment of a method for pushing a message event according to the present invention;
FIG. 3 is a flowchart illustrating a second embodiment of a method for pushing a message event according to the present invention;
FIG. 4 is a diagram illustrating a message configuration window in an embodiment of a method for pushing a message event according to the present invention;
FIG. 5 is a diagram of a sub-task window in an embodiment of a method for pushing a message event according to the present invention;
FIG. 6 is a diagram of another sub-task window in an embodiment of a method for pushing a message event according to the present invention;
the achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
Detailed Description
According to the method, different single or combined pushing modes are configured through the event, the event is sent to the receiver according to the configuration when the event is sent, and one-to-many, multi-mechanism and multi-post sending is supported.
In order that the above-described aspects may be better understood, exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
As an implementation, the hardware architecture of the message push terminal may be as shown in fig. 1.
The embodiment of the invention relates to a hardware architecture of a message pushing terminal, which comprises the following components: a processor 101, such as a CPU, a memory 102, and a communication bus 103. Wherein the communication bus 103 is used to enable connected communication among the components.
The memory 102 may be a high-speed RAM memory or a stable memory, such as a disk memory. As shown in fig. 1, a push program of message events may be included in a memory 102, which is a computer-readable storage medium; and the processor 101 may be configured to invoke a push procedure for message events stored in the memory 102 and perform the following operations:
when a message configuration request is received, a message configuration window is started;
configuring the notification type, interface information and/or notification party receiving address of the message event according to the message configuration request in a message configuration module in the message configuration window;
when a message push request is received, configuring notification party information corresponding to a notification party according to the notification type, the interface information and the notification party receiving address, wherein the notification party information comprises in-station notification party information and out-of-station notification party information;
and pushing the message event to the notifier according to the configured notifier information.
In one embodiment, the processor 101 may be configured to invoke a push program for message events stored in the memory 102 and perform the following operations:
configuring the notifier information as the in-station notifier information 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 notifier reception address is at least one of the mail address and the in-station communication address;
and 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 institution information, and the notification party receiving address is at least one of the short message address, the mail address and the public number address, the notification party information is configured as the off-site notification party information.
In one embodiment, the processor 101 may be configured to invoke a push program for message events stored in the memory 102 and perform the following operations:
pushing the message event to the notifier having the pushing authority of the in-station notifier information according to the in-station notifier information;
and/or pushing the message event to the notifier having the pushing authority of the information of the out-of-station notifier according to the information of the out-of-station notifier.
In one embodiment, the processor 101 may be configured to invoke a push program for message events stored in the memory 102 and perform the following operations:
generating a first subtask window for configuring the notification type according to the first configuration request based on the first sub-message configuration module;
acquiring a first configuration parameter input in the first subtask window;
and determining the notification type of the message event according to the first configuration parameter.
In one embodiment, the processor 101 may be configured to invoke a push program for message events stored in the memory 102 and perform the following operations:
generating a second subtask window for configuring the interface information according to the second configuration request based on the second sub-message configuration module;
acquiring a second configuration parameter input in the second subtask window;
and determining the interface information of the message event according to the second configuration parameters.
In one embodiment, the processor 101 may be configured to invoke a push program for message events stored in the memory 102 and perform the following operations:
generating a third subtask window for configuring a notification party receiving address according to the third configuration request based on the third sub-message configuration module;
acquiring a third configuration parameter input in the third subtask window;
and determining the receiving address of the notifier of the message event according to the third configuration parameters.
In one embodiment, the processor 101 may be configured to invoke a push program for message events stored in the memory 102 and perform the following operations:
storing the configured message event in a preset time period into a preset record table;
when receiving a message push request, the step of configuring the information of the notifier corresponding to the notifier according to the notification type, the interface information and the receiving address of the notifier comprises the following steps:
when the message pushing request is received, determining whether a target message event corresponding to the message pushing request exists in the preset record table;
if yes, acquiring the notification type, the interface information and the notification party receiving address of the target message event, and configuring notification party information corresponding to a notification party according to the notification type, the interface information and the notification party receiving address;
and if not, returning to the step of executing the message configuration module in the message configuration window, and configuring the notification type, interface information and/or notification party receiving address of the message event according to the message configuration request.
Based on the hardware architecture of the message pushing terminal based on the computer technology, the embodiment of the pushing method of the message event is provided.
Referring to fig. 2, in a first embodiment, the method for pushing a message event includes the following steps:
step S10, when a message configuration request is received, a message configuration window is started;
in this embodiment, when the message pushing terminal receives the message configuration request, the message configuration window is started. The message configuration request is a request for configuring a pushing mode of a message event, which is sent by a target application installed in a message pushing terminal, the target application is an enterprise application running in an operating system of the message pushing terminal, a message pushing service module is pre-embedded in the enterprise application, and when the message pushing terminal executes the message pushing service module, the step of the pushing party of the message event is executed. The message pushing terminal may be a mobile phone, a computer, a notebook, etc., which is not limited herein. The message configuration window is a visual operation interface window of the message push service module, and the message push terminal configures the message event in the message configuration window according to the message configuration request.
Step S20, in the message configuration module in the message configuration window, configuring the notification type, interface information and/or notification party receiving address of the message event according to the message configuration request;
after the step of starting the message configuration window, configuring the notification type, the interface information and/or the notification party receiving address of the message event in the notification type, the interface information and/or the notification party receiving address of the message event according to the message configuration request.
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 for triggering a corresponding message configuration module in the message configuration window, wherein the first configuration request is used for triggering a first sub-message configuration module, the second configuration request is used for triggering a second sub-message configuration module, and the third configuration request is used for triggering a third sub-message configuration module.
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 for configuring a notification type of a message event, the second subtask window is used for configuring interface information of the message event, and the third subtask window is used for configuring a notification party receiving address of the message event. The corresponding message configuration modules in different subtask windows are also different, the message configuration modules are integrated code blocks arranged in the subtask windows, the different message configuration modules correspond to different functions, in the embodiment, the configuration module of the first subtask window corresponds to a first subtask message configuration module, and the first subtask message configuration module comprises a code block for configuring the notification type of the message event; the configuration module of the second subtask window corresponds to a second sub-message configuration module, and the second sub-message configuration module comprises a code block for configuring interface information of the message event; the configuration module of the third subtask window corresponds to a third sub-message configuration module, and the third sub-message configuration module comprises a code block for configuring the receiving address of the notifier of the message event.
Optionally, the notification types are classified into an in-station notification type and an out-station notification type, where the in-station notification type is characterized by pushing in a site, and when the message pushing terminal is a mobile phone, for example, a volunteer item APP is installed on the mobile phone, and if the notification type is an in-station notification, the message event is pushed to the volunteer item APP. The off-site notification type is characterized by pushing to the outside of the site, and when the message pushing terminal is a computer, if the notification type is the off-site notification, the message event is pushed in an off-site mode such as a mailbox, a mobile phone short message and the like.
Optionally, the interface information includes volunteer information, volunteer team information, and volunteer institution information. The volunteer information is characterized in that the notifier of the message event is the volunteer per se, the volunteer team information is characterized in that the notifier of the message event is the volunteer team (can be a manager of the team or everyone in the team), and the volunteer organization information is characterized in that the notifier of the message event is the volunteer organization (can be a manager in a local volunteer organization). Alternatively, the interface information may be grouped in advance by the body information type and the area.
Optionally, the notifier receiving address includes a short message address, a mail address, a public number address, and an in-station letter address. The short message address is characterized by being sent in a short message mode (such as a mobile phone short message); the mail address is characterized in that the mail is sent by a mail mode, and the public number address is characterized in that the public number is used as a notification party for sending; the in-station address is characterized as being sent in-station (e.g., in the volunteer website). Different notification parties receive different notification groups corresponding to addresses, and can be configured according to actual needs.
Optionally, when the message configuration request is a first configuration request, a first subtask window is generated according to the first configuration request, a first subtask configuration module in the first subtask window is triggered, and when a first configuration parameter input in the first subtask window is acquired, the notification type of the message event is determined according to the first configuration parameter, wherein an input object can be input by a user or can be automatically configured and generated for the message pushing terminal.
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 subtask configuration module in the second subtask window is triggered, when a second configuration parameter input in the second subtask window is acquired, interface information of the message event is determined according to the second configuration parameter, wherein an input object can be input by a user or can be automatically configured and generated for the message pushing terminal.
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 subtask configuration module in the third subtask window is triggered, and when a third configuration parameter input in the third subtask window is acquired, a notification party receiving address of the message event is determined according to the third configuration parameter, wherein an input object can be user input or can be automatically configured and generated for the message pushing terminal.
It should be noted that, in this embodiment, when configuring a message event, the notification type, the interface information and the notification party receiving address may be selected and configured, or a plurality of message events may be configured at the same time, which is not limited in this embodiment, however, when pushing a message event, each message event needs to be configured with the notification type, the interface information and the notification party receiving address to be pushed.
Step S30, when a message push request is received, configuring notification party information corresponding to a notification party according to the notification type, the interface information and the notification party receiving address, wherein the notification party information comprises in-station notification party information and out-of-station notification party information;
in this embodiment, after the notification type, interface information, and/or notification party receiving address of the message event are configured, notification party information corresponding to the notification party is configured according to the notification type, interface information, and/or notification party receiving address, and the notification party information includes in-station notification party information and out-of-station notification party information. The in-station notifier information is characterized in that the notification object is information of a receiver of the message event in the station (such as in a volunteer website), and the out-of-station notifier information is characterized in that the notification object is information of a receiver of the message event outside the website (such as public numbers, mails, short messages and the like).
Alternatively, the configuration condition of the in-station notifier information may be: the notification type is an in-station notification; the interface information is at least one of volunteer information and volunteer team information; the notifier receiving address is at least one of a mail address and an in-station address. That is, when the message event is an in-station notification event, and the information of the notifier can be configured as in-station notifier information by volunteer information and/or volunteer team information as a target object of transmission data, and the message event can be pushed by mail and/or in-station letter.
Alternatively, the configuration condition of the off-site notifier information may be: the notification type is 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 short message address, a mail address and a public number address. That is, when the notification type of the message event is an off-site notification event and the message event can be pushed by at least one of interface information of volunteer information, volunteer team information, and volunteer organization information as a target object of transmission data, and by at least one of short message, mail, and public number, the notifier information is configured as an off-site notifier information.
Step S40, pushing the message event to the notifier according to the configured notifier information.
In this embodiment, after the notification party information is configured, the message event is pushed to the notification party according to the configured notification party information, where one-to-many sending, multi-mechanism sending, and multi-post sending can be supported when the message event is sent.
In the technical scheme provided by the implementation, the notification type, the interface information and/or the notification party receiving address of the message event are configured, when a message pushing request is received, the configured notification type, the interface information and the notification party receiving address are configured, and the notification party information of the notification party of the message event is configured in the sending and receiving of the message event, so that the message event is pushed to different notification parties, such as volunteers, institutions and the like, and the pushing modes are various, including short message pushing, mail pushing, public number pushing and in-station pushing, so that the effect of reducing the message pushing cost is achieved.
Referring to fig. 3, in the second embodiment, based on the first embodiment, before the step S30, it includes:
step S50, storing the configured message event in a preset time period into a preset record table;
the step S30 includes:
step S31, when the message pushing request is received, determining whether a target message event corresponding to the message pushing request exists in the preset record table;
step S32, if yes, the notification type, the interface information and the notification party receiving address of the target message event are obtained, and notification party information corresponding to the notification party is configured according to the notification type, the interface information and the notification party receiving address; and if not, returning to the step of executing the message configuration module in the message configuration window, and configuring the notification type, interface information and/or notification party receiving address of the message event according to the message configuration request.
Optionally, in order to improve the pushing efficiency of the message event, in this embodiment, before receiving the message pushing request, the message event in a preset time period is stored in a preset record table, the preset record table is stored in a memory of the message pushing terminal, when receiving the message pushing request, it is determined whether a target message event corresponding to the message pushing request exists in the preset record table, if so, a notification type, interface information and a notification party receiving address of the target message event are obtained, and the notification party information configuration of this step is executed according to the notification type, interface information and notification party receiving address of the target message event; if not, returning to the message event configuration of the last step.
In this embodiment, the preset time period is a high-frequency time period (for example, 8:00-22:00 of each day) of message event pushing, and the message events configured in this time period are stored in the preset record table, so that when a message pushing request is received, a target message event corresponding to the message pushing request is quickly traversed from the preset record table, and the notifier information is configured according to the notification type, the interface information and the notifier of the target message event, and the target message event is pushed to the notifier according to the configured notifier information.
In the technical solution provided in this embodiment, by storing the message event configured in the preset time period in a preset record table, when the message push request is received, it is determined whether a target message event corresponding to the message push request exists in the preset record table. If yes, acquiring the notification type, the interface information and the notification party receiving address of the target message event, and configuring notification party information corresponding to a notification party according to the notification type, the interface information and the notification party receiving address; if not, returning to execute the message configuration module in the message configuration window, and configuring the notification type of the message event, the interface information and/or the mode of receiving the address by the notification party according to the message configuration request, thereby improving the pushing efficiency of the message event.
In addition, referring to fig. 4, for example, fig. 4 is a schematic diagram of a message configuration window set by a pushing method based on a message event according to an embodiment of the present invention, and clicking a "reply" button under an operation field may pop up a subtask window "reply to a station letter" shown in fig. 5 to configure the station letter (i.e. a message event).
In addition, referring to fig. 6, fig. 6 is a schematic diagram of a subtask window set by the pushing method based on the message event according to the present invention in an embodiment of the present invention, where the message event is a mail event, and the mail event can be sequenced by sequence numbers, and the type, state, title and recipient (i.e. the pushing party) of the message event can be displayed, and operations such as restoring and deleting the mail event can be performed through a corresponding button in an "operation" column.
Furthermore, it will be appreciated by those of ordinary skill in the art that implementing all or part of the processes in the methods of the above embodiments may be accomplished by computer programs to instruct related hardware. The computer program comprises 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 pushing terminal to implement the flow steps of the embodiments of the method described above.
The present invention thus also provides a computer readable storage medium storing a push program of message events which when executed by a processor implements the steps of the method of pushing message events as described in the above embodiments.
The computer readable storage medium may be a usb disk, a removable hard disk, a Read-Only Memory (ROM), a magnetic disk, or an optical disk, etc. which may store the program code.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a computer readable storage medium (e.g. ROM/RAM, magnetic disk, optical disk) as described above, comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present invention.
The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.
Claims (10)
1. The message event pushing method is characterized by being applied to a message pushing terminal, and comprises the following steps:
when a message configuration request is received, a message configuration window is started;
configuring the notification type, interface information and/or notification party receiving address of the message event according to the message configuration request in a message configuration module in the message configuration window;
when a message push request is received, configuring notification party information corresponding to a notification party according to the notification type, the interface information and the notification party receiving address, wherein the notification party information comprises in-station notification party information and out-of-station notification party information;
and pushing the message event to the notifier according to the configured notifier information.
2. The method of pushing a message event according to claim 1, wherein the notification types include an in-station notification and an out-of-station notification, the interface information includes volunteer information, volunteer team information, and volunteer organization information, the notification party reception address includes a short message address, a mail address, a public number address, and an in-station message address, and the notification party information includes one notification type, at least one interface information, and at least one notification party reception address.
3. The method for pushing a message event according to claim 2, wherein the step of configuring the notifier information corresponding to the notifier according to the notification type, the interface information, and the notifier receiving address comprises:
configuring the notifier information as the in-station notifier information 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 notifier reception address is at least one of the mail address and the in-station communication address;
and 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 institution information, and the notification party receiving address is at least one of the short message address, the mail address and the public number address, the notification party information is configured as the off-site notification party information.
4. The pushing method of message event according to claim 3, wherein the step of pushing the message event to the notifier according to the configured notifier information comprises:
pushing the message event to the notifier having the pushing authority of the in-station notifier information according to the in-station notifier information;
and/or pushing the message event to the notifier having the pushing authority of the information of the out-of-station notifier according to the information of the out-of-station notifier.
5. The method for pushing a message event according to claim 2, wherein the message configuration request comprises a first configuration request, the message configuration module comprises a first sub-message configuration module, and the step of configuring a notification type, interface information and/or a notification party receiving address of the message event according to the message configuration request comprises:
generating a first subtask window for configuring the notification type according to the first configuration request based on the first sub-message configuration module;
acquiring a first configuration parameter input in the first subtask window;
and determining the notification type of the message event according to the first configuration parameter.
6. The method for pushing a message event according to claim 5, wherein the message configuration request includes a second configuration request, the message configuration module includes a second sub-message configuration module, and the configuring the notification type, interface information, and/or notification party receiving address of the message event according to the message configuration request includes:
generating a second subtask window for configuring the interface information according to the second configuration request based on the second sub-message configuration module;
acquiring a second configuration parameter input in the second subtask window;
and determining the interface information of the message event according to the second configuration parameters.
7. The method for pushing a message event according to claim 6, wherein the message configuration request includes a third configuration request, the message configuration module includes a third sub-message configuration module, and the configuring the notification type, interface information, and/or notification party receiving address of the message event according to the message configuration request includes:
generating a third subtask window for configuring a notification party receiving address according to the third configuration request based on the third sub-message configuration module;
acquiring a third configuration parameter input in the third subtask window;
and determining the receiving address of the notifier of the message event according to the third configuration parameters.
8. The method for pushing a message event according to claim 1, wherein 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 the message pushing request is received, comprises:
storing the configured message event in a preset time period into a preset record table;
when receiving a message push request, the step of configuring the information of the notifier corresponding to the notifier according to the notification type, the interface information and the receiving address of the notifier comprises the following steps:
when the message pushing request is received, determining whether a target message event corresponding to the message pushing request exists in the preset record table;
if yes, acquiring the notification type, the interface information and the notification party receiving address of the target message event, and configuring notification party information corresponding to a notification party according to the notification type, the interface information and the notification party receiving address;
and if not, returning to the step of executing the message configuration module in the message configuration window, and configuring the notification type, interface information and/or notification party receiving address of the message event according to the message configuration request.
9. A message pushing terminal, characterized in that the message pushing terminal comprises: memory, a processor and a push program of message events stored on the memory and executable on the processor, which when executed by the processor, implements the steps of the push method of message events according to any of claims 1 to 8.
10. A computer readable storage medium, characterized in that a push program of message events is stored on the computer readable storage medium, which when executed by a processor implements the steps of the method of pushing message events according to any of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211088675.7A CN116260783A (en) | 2022-09-07 | 2022-09-07 | Message event pushing method, message pushing terminal and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211088675.7A CN116260783A (en) | 2022-09-07 | 2022-09-07 | Message event pushing method, message pushing terminal and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116260783A true CN116260783A (en) | 2023-06-13 |
Family
ID=86686797
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211088675.7A Pending CN116260783A (en) | 2022-09-07 | 2022-09-07 | Message event pushing method, message pushing terminal and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116260783A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016029417A1 (en) * | 2014-08-29 | 2016-03-03 | 华为技术有限公司 | Method and apparatus for pushing and displaying message |
| US20160283985A1 (en) * | 2015-03-16 | 2016-09-29 | Swrve New Media, Inc. | Enhanced system and method for enhanced multi channel, multi-option, highly targeted automated campaigns using templates |
| CN109639824A (en) * | 2018-12-28 | 2019-04-16 | 深圳市恒创智达信息技术有限公司 | A kind of message push management system and method |
| CN112367241A (en) * | 2020-10-16 | 2021-02-12 | 北京五八信息技术有限公司 | Message generation and message transmission method, device, equipment and computer readable medium |
| CN113379501A (en) * | 2021-06-21 | 2021-09-10 | 广东三维家信息科技有限公司 | Message pushing method and device, electronic equipment and storage medium |
| CN114125047A (en) * | 2021-11-10 | 2022-03-01 | 携程商旅信息服务（上海）有限公司 | Message pushing method, system, equipment and storage medium based on third-party system |
-
2022
- 2022-09-07 CN CN202211088675.7A patent/CN116260783A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016029417A1 (en) * | 2014-08-29 | 2016-03-03 | 华为技术有限公司 | Method and apparatus for pushing and displaying message |
| US20160283985A1 (en) * | 2015-03-16 | 2016-09-29 | Swrve New Media, Inc. | Enhanced system and method for enhanced multi channel, multi-option, highly targeted automated campaigns using templates |
| CN109639824A (en) * | 2018-12-28 | 2019-04-16 | 深圳市恒创智达信息技术有限公司 | A kind of message push management system and method |
| CN112367241A (en) * | 2020-10-16 | 2021-02-12 | 北京五八信息技术有限公司 | Message generation and message transmission method, device, equipment and computer readable medium |
| CN113379501A (en) * | 2021-06-21 | 2021-09-10 | 广东三维家信息科技有限公司 | Message pushing method and device, electronic equipment and storage medium |
| CN114125047A (en) * | 2021-11-10 | 2022-03-01 | 携程商旅信息服务（上海）有限公司 | Message pushing method, system, equipment and storage medium based on third-party system |
Non-Patent Citations (2)
| Title |
|---|
| T JOKELA: ""Multimedia public warning alert trials using eMBMS broadcast, dynamic spectrum allocation and connection bonding"", 《IEEE》, 31 December 2020 (2020-12-31) * |
| 杨武博: ""消息推送方案"", 《CSDN博客》, 31 December 2018 (2018-12-31) * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9552137B2 (en) | System and method for managing informational objects on mobile devices | |
| US20140220942A1 (en) | Managing communications utilizing communication categories | |
| EP2410704B1 (en) | System and method of posting messages to different messaging services | |
| US20050204009A1 (en) | System, method and computer program product for prioritizing messages | |
| US20040141004A1 (en) | Electronic messaging system and method with automatic prompting | |
| US8874678B2 (en) | Recipient change notification | |
| US9253272B2 (en) | Reliable delivery of a push-state aware client device | |
| US8326935B2 (en) | Group list exclusions for messaging | |
| CN110971447A (en) | Test information management method and device, electronic equipment and readable storage medium | |
| CN101202760B (en) | Remote control operation | |
| US9736090B2 (en) | Method and apparatus for processing message | |
| CN106888149B (en) | Subscription mail unsubscribing method and device | |
| US20060224968A1 (en) | Confirmation system and method for instant messaging | |
| CN116260783A (en) | Message event pushing method, message pushing terminal and readable storage medium | |
| CA2746921C (en) | Recipient change notification | |
| CN107679871B (en) | List management method, device, system and computer readable storage medium | |
| US20220158962A1 (en) | Method for Providing an Email User Experience By Contacts Instead of Folders | |
| CN102223446B (en) | Information transmission method and terminal | |
| US20130054710A1 (en) | Categorizing email recipients into logical groups when sending a mass email | |
| CN115345428A (en) | Complaint information processing method, complaint information processing system, and computer-readable storage medium | |
| CN108924270B (en) | Method for updating terminal contact information, server and storage medium | |
| CN102982435B (en) | A kind of method of information association and electronic equipment | |
| TW201644234A (en) | Email handling method, device and system | |
| EP1617637A1 (en) | System and method for managing informational objects on mobile devices | |
| JP2005141753A (en) | System and method for reducing size of electronic message on mobile communication device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |