CN111917843A - Message pushing method, computer equipment and storage medium - Google Patents
Message pushing method, computer equipment and storage medium Download PDFInfo
- Publication number
- CN111917843A CN111917843A CN202010687572.7A CN202010687572A CN111917843A CN 111917843 A CN111917843 A CN 111917843A CN 202010687572 A CN202010687572 A CN 202010687572A CN 111917843 A CN111917843 A CN 111917843A
- Authority
- CN
- China
- Prior art keywords
- client
- message
- information
- pushed
- pushing
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
Abstract
The application discloses a message pushing method, computer equipment and a storage medium, wherein the method comprises the following steps: acquiring a message pushing instruction, wherein the message pushing instruction comprises a message to be pushed and a target message type; determining a push service of a client associated with the target message type based on preset configuration information of the target message type; and pushing the message to be pushed to the client associated with the target message type according to the pushing service. By the mode, the configuration information can be set for the specific message type, so that the client side of the specific message type and the personalized requirements of the pushed message of the client side can be met, and the operation is simple and convenient.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a message pushing method, a computer device, and a computer-readable storage medium.
Background
With the continuous development of computer and internet technologies, networks have become an important way for people to acquire information, and various push messages can be pushed to a user terminal by means of a server and can be displayed to users through the user terminal, so that a great deal of convenience is brought to the life of people.
At present, with the development of enterprises, more and more enterprises distribute messages to each client in a message pushing mode, and in the internal management of the enterprises, the messages can also be distributed to staff of departments in the enterprises. Most of the prior art is developed on a specific platform aiming at specific clients and specific scenes, and cannot meet the requirement that enterprises or individuals push messages under a specific environment.
Disclosure of Invention
The application provides a message pushing method, computer equipment and a storage medium, which can set configuration information for a specific message type so as to meet the client side of the specific message type and the personalized requirements of the message pushing of the client side, and are simple and convenient to operate.
In order to solve the technical problem, the application adopts a technical scheme that: a method for pushing a message is provided. The method comprises the following steps: acquiring a message pushing instruction, wherein the message pushing instruction comprises a message to be pushed and a target message type; determining a push service of a client associated with the target message type based on preset configuration information of the target message type; and pushing the message to be pushed to the client associated with the target message type according to the pushing service.
In order to solve the above technical problem, another technical solution adopted by the present application is: a computer device is provided. The computer device includes: a processor and a memory for storing a computer program for execution by the processor to implement the push method of the message.
In order to solve the above technical problem, another technical solution adopted by the present application is: a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program that is executed by a processor to implement the above-described push method of a message.
The beneficial effect of this application is: according to the method and the device, the target message type is associated with the client side needing to push the message based on the preset configuration information of the target message type, and the push service of the client side associated with the target message type is realized, so that the message to be pushed of the target message type is pushed to each client side according to the push message requirement of each client side, the configuration information can be set for the specific message type, the client side of the specific message type and the personalized requirement of the push message of the client side can be met, and the operation is simple and convenient.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a schematic flowchart of a first embodiment of a message pushing method provided in the present application;
fig. 2 is a flowchart illustrating a second embodiment of a message pushing method provided in the present application;
fig. 3 is a schematic flowchart of a third embodiment of a message pushing method provided in the present application;
fig. 4 is a schematic flowchart of a fourth embodiment of a message pushing method provided in the present application;
fig. 5 is a schematic structural diagram of a message pushing device provided in the present application;
FIG. 6 is a schematic diagram of a computer device provided herein;
fig. 7 is a schematic structural diagram of a computer-readable storage medium provided in the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms "first", "second" and "third" in this application are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implying any indication of the number of technical features indicated. Thus, a feature defined as "first," "second," or "third" may explicitly or implicitly include at least one of the feature. In the description of the present application, "plurality" means at least two, e.g., two, three, etc., unless explicitly specifically limited otherwise. All directional indications (such as up, down, left, right, front, and rear … …) in the embodiments of the present application are only used to explain the relative positional relationship between the components, the movement, and the like in a specific posture (as shown in the drawings), and if the specific posture is changed, the directional indication is changed accordingly. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those skilled in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments without conflict.
The following describes embodiments of the present application.
Referring to fig. 1, fig. 1 is a schematic flowchart of a first embodiment of a message pushing method provided in the present application, where the method includes the following steps:
s110: and acquiring a message pushing instruction, wherein the message pushing instruction comprises a message to be pushed and a target message type.
The target message type may be a message type related to a target service, for example, in the process of processing a service message, some information often needs to be pushed to a user in time for reminding, such as a pending prompt message, an early warning prompt message, an error prompt message, an operation prompt message, and the like, and various messages may be divided into different message types, which is not limited in this application.
When the message needs to be pushed, a message pushing instruction is obtained, wherein the message pushing instruction comprises the message to be pushed and the target message type, so that the message to be pushed is pushed according to the target message type. The message to be pushed may be a message content that needs to be pushed, which is not limited in the present application.
In some embodiments, the message push instruction further includes sender information and receiver information, wherein the sender information includes: at least one of the name of the sender, the account number of the sender, the contact way of the sender, the sending time and the sending equipment; the receiver information includes: at least one of the name of the receiver, the account number of the receiver and the contact way of the receiver. The contact information may include a mobile phone number, a telephone number, a user mailbox, and the like. In some application scenarios, the display, content, style, and the like of the sender information and the receiver information may be set according to specific requirements, which is not limited in the present application.
S120: and determining the push service of the client associated with the target message type based on the preset configuration information of the target message type.
The preset configuration information of the target message type comprises: the system comprises at least one piece of client information and a push service corresponding to each piece of client information, wherein the client corresponding to each piece of client information is a client associated with a target message type.
After the target message type is obtained, client information to be pushed of the target message type and a pushing service corresponding to each client of the target message type can be obtained based on preset configuration information of the target message type. For example, in some application scenarios, because the types of the target messages are different, some messages need to be sent to multiple different clients and some messages need to be sent to only one client, possibly because of the importance and urgency of the types of the target messages, so different client information can be configured according to the types of the target messages. In addition, according to the characteristics of different clients and the target message types of different services, the push service corresponding to the client corresponding to the target message type can be configured.
S130: and pushing the message to be pushed to the client associated with the target message type according to the pushing service.
After the client information required to be pushed by the target message type is obtained and the push service corresponding to each client of the target message type is obtained, the messages to be pushed can be respectively pushed to the clients associated with the target message type according to the push service.
In the embodiment, the target message type is associated with the client side needing to push the message based on the preset configuration information of the target message type, and the target message type is associated with the push service of the client side, so that the message to be pushed of the target type is pushed to each client side according to the push service requirement of each client side, the configuration information can be set for the specific message type, the client side of the specific message type and the personalized requirement of the pushed message can be met, and the operation is simple and convenient.
Before the step S110, preset configuration information may also be configured, please refer to fig. 2, where fig. 2 is a schematic flow diagram of a second embodiment of a message pushing method provided in the present application, and the method includes the following steps:
s210: first registration information of at least one client is received, wherein the first registration information comprises client information of a corresponding client and push service configured for the client.
Before a message push instruction is obtained to push a message to be pushed, configuring preset configuration information of a target message type of the message, for example, when client information is configured, a distribution tool receives first registration information of at least one client, wherein the first registration information includes client information of a corresponding client and push service configured for the client.
In some embodiments, receiving first registration information of at least one client includes: the method comprises the steps of obtaining client information of at least one client input by a user, and displaying a plurality of selectable items for generating the push service for each client. For example, the selectable option may include at least one of a push type, a display configuration, a subscription configuration, and a feedback configuration of a message to be pushed by the push service, so that the push service of the corresponding client is configured according to the selected selectable option.
Wherein, the client information includes: at least one of a client name, a client type, and a client service address. The client types include, for example: PC end (Personal Computer) message, mobile phone end message, PC end session, mobile phone end session, email, etc., which is not limited in this application.
The push service includes: at least one of a push type, a display configuration, a subscription configuration and a feedback configuration of the message to be pushed. In some application scenarios, a client type corresponding to each client may be further configured to display selectable options corresponding to the push service, so as to configure a personalized push service for each type of client. Of course, other push services may be included, which is not limited in this application.
For the push service, the push type of the message to be pushed includes: at least one of mail pushing, short message pushing and application offline pushing. For example, a push mode of a client type can be configured for the client type of the client, and when the client is a PC end or a mobile phone end, different push modes can be configured for the PC end and the mobile phone end. In addition, the push type of the message to be pushed may be configured for each client, or the push type may be configured for the target message type, which is not limited in this application.
The display configuration includes: at least one of the amount of information displayed, the display duration, or the display style. According to different clients and different message types of service types, when each client receives a message and displays the message, the configuration can be performed according to different display requirements, for example, the displayed information amount includes displaying all information, displaying part information, displaying a message title of the message, and the like, the display duration is the message display time after the client receives the message, the display style is the message display style after the client receives the message, for example, the display style is the displayed content, the position of the displayed content, and the like, and the message content display font style is not limited in this application. The display configuration may be set according to the client or the message type, and the present application is not limited herein.
The subscription configuration includes: whether to allow unsubscription of a single record message, whether to allow unsubscription of all messages sent based on the type of message to which it belongs, and whether to resume subscription.
If receiving the selectable option to allow the cancellation of the single record message, after pushing the message to be pushed to the client associated with the target message type according to the pushing service, the client can select whether to cancel the single record message, if the client selects to cancel the single record message, the client returns an identifier of the single record message to be canceled to the sender, so that the sender does not send the message associated with the message to be pushed after receiving the identifier, the associated message can be the same recorded record message, such as a password expiration reminding record message, and after receiving the password expiration reminding record message, the client selects to cancel the single record message, and then subsequently does not send the password expiration reminding record message to the client. In some embodiments, after the client selects to unsubscribe a single recording message, the message to be pushed may be set at the front end of the client to be not displayed, and the message to be pushed may not be displayed after being subsequently received. In addition, the single logging message also belongs to one of message types, and the application does not limit this.
If the client selects to unsubscribe all the messages sent based on the message type, the client can select whether to unsubscribe all the messages sent based on the message type, and if the client selects to unsubscribe all the messages sent based on the message type, the client does not send the messages to be pushed of the target message type.
And if the subscription can be restored, the client can select whether to restore the subscription when pushing the message to be pushed to the client associated with the target message type according to the pushing service and selecting to cancel the single recording message of the subscription or cancel the subscription of all the messages sent based on the affiliated message type. For example, the message to be pushed may be opened again, and a single recorded message may be restored to the subscription, or all messages sent based on the type of the message to which the subscription belongs may be subscribed.
For the subscription configuration, the subscription configuration may further include other subscription messages, and whether the subscription can be restored or not may also be configured separately according to the subscription messages, for example, whether the single recording message for canceling the subscription is allowed to be configured as the unrecoverable subscription or not, whether the subscription is allowed to be canceled or not may be configured as the recoverable subscription based on all messages sent by the message type to which the subscription belongs, and may be configured according to specific requirements, which is not limited in the present application.
The feedback configuration comprises: whether to feed back the message read information. And after the read information of the feedback message is that the client receives the message and displays the message, if the mark received by the client is unread, the feedback message is unread, and if the mark received by the client is read, the feedback message is read. For example, some messages need only to be simply prompted at some clients and displayed for a preset time, some messages need to be closed after being marked and read by a user at some clients, and some messages need to be closed after being processed by the user at some clients.
Based on the user's selection of the plurality of selectable options, a push service is determined for each client. Specifically, the push service of each client is determined based on the selection of the plurality of selectable options displayed by each client for generating the push service by the user, so that personalized message push configuration can be performed on each client.
S220: and storing the client information and the push service corresponding to each client into a preset storage space.
After the client information corresponding to the client and the push service corresponding to the client are obtained, the client information and the push service corresponding to the client may be stored in an appointed path or in a preset storage space, so that the client information and the push service corresponding to the client may be subsequently read in the preset storage space in the above steps S110 to S130 according to the obtained message push instruction, and the message to be pushed is pushed to the client associated with the target message type according to the read client information and push service corresponding to the client.
For the above embodiment, before the step S110, preset configuration information may also be configured, please refer to fig. 3, where fig. 3 is a schematic flow diagram of a third embodiment of a message pushing method provided in the present application, and the method includes the following steps:
s310: and receiving second registration information of at least one message type, wherein the second registration information comprises at least one piece of client information of the corresponding message type.
Before obtaining a message push instruction to push a message to be pushed, configuring preset configuration information of a target message type of the message, for example, when configuring the message type, a distribution tool receives second registration information of at least one message type, where the second registration information includes at least one client information corresponding to the message type. For example, the registered message types are pending prompt messages, early warning prompt messages, error prompt messages, operation prompt messages and the like, different message types need to be pushed, and when the message types are registered, the client corresponding to the message types can be selected, so that the different message types can push messages to different clients.
The target message type is one of the message types. After the message types are registered, one of the message types may be used as a target message type of the message to be pushed.
S320: and acquiring the client information in the second registration information, acquiring the push service of the client information in the second registration information from a preset storage space, and taking the acquired client information and the push service as preset configuration information of the message type.
When registering the second registration message, after receiving the registered message type, selecting the client corresponding to the message type, acquiring the client information corresponding to the message type in the second registration message, acquiring the client information and the push service corresponding to the client information in the preset storage space of the first registration message, and taking the acquired client information and push service as the preset configuration information of the message type in the second registration message.
In some embodiments, the obtained message type, each piece of client information corresponding to the obtained message type, and the push service may be stored in a preset storage space, so that the client information and the push service corresponding to the obtained message type may be obtained in a subsequent message push process.
In some embodiments, the push service of the client may also be configured for the message type, specifically, client information of at least one client corresponding to the message type input by the user is obtained, and a plurality of selectable options for generating the push service are displayed for each client. For example, the selectable option may include at least one of a push type, a display configuration, a subscription configuration, and a feedback configuration of the message to be pushed by the push service, so that the message type corresponds to the push service of the client according to the selected selectable option configuration.
In some embodiments, the first registration information and the second registration information may be modified, when the first registration information is modified, the client that acquires the first registration information that needs to be modified reads the client information and the push service corresponding to the client that needs to be modified in the preset storage space, acquires the client information and the push service that are newly input by the user and updates, and stores the updated client information and the updated push service in the preset storage space. In addition, when the second registration message is modified, the message type to be modified is acquired, the client and the client information corresponding to the message type are read, at least one client and the client information which are newly input by the user are acquired for updating, the client information of at least one client which is input by the user is acquired, a plurality of selectable items for generating the push service are displayed for each client, and the push service is updated and stored in the preset storage space.
In addition, in the prior art, when a message is pushed in a specific scene and a specific client, the message pushing configuration needs to be designed separately for different messages and pushing modes of different clients, so that application developers need to learn and develop separately for different clients and pushing modes of different messages, and further work efficiency is low.
Compared with the prior art, in the embodiment of the application, the first registration information of at least one client can be received, so that the client information can be registered, the push service of the client can be configured, and personalized configuration push service can be performed for each client. In addition, the second registration information of at least one message type can be received, so that the message types can be registered, the received client corresponding to the message types can be configured, the corresponding received client and the push service corresponding to the client and the message types can be configured for the push messages of each message type, the personalized requirements of push messages of specific environments, specific clients and specific message types can be met, and the operation is simple and convenient. Furthermore, the distribution tool is configured, so that the workload of application developers can be reduced, and the working efficiency is improved.
Referring to fig. 4, fig. 4 is a schematic flowchart of a fourth embodiment of a message pushing method provided in the present application, where the method includes the following steps:
s410: and acquiring a message pushing instruction, wherein the message pushing instruction comprises a message to be pushed and a target message type.
The message pushing instruction further comprises sender information including: at least one of the name of the sender, the account number of the sender, the contact way of the sender, the sending time and the sending equipment; the receiver information includes: at least one of the name of the receiver, the account number of the receiver and the contact way of the receiver.
S420: and determining the push service of the client associated with the target message type based on the preset configuration information of the target message type.
The preset configuration information of the target message type comprises: the system comprises at least one piece of client information and a push service corresponding to each piece of client information, wherein the client corresponding to each piece of client information is a client associated with a target message type.
S430: and pushing the message to be pushed to the client associated with the target message type according to the pushing service.
The specific implementation of the steps S410-430 can refer to the implementation processes of the steps S110-S130 in the above embodiments, and will not be described herein again.
After the step S430, the method further includes at least one of the following steps:
s440: and if a first subscription cancellation indication fed back by the client is received, determining that the message associated with the message to be pushed is not pushed to the client any more subsequently.
If a first unsubscribe instruction fed back by the client is received, determining that the client unsubscribes, for example, receiving a single record message instruction of the selected unsubscribe fed back by the client, determining that a message associated with the message to be pushed is not pushed to the client any more subsequently, where the message associated with the message to be pushed may be a record message recorded in the same way as the message to be pushed, such as a password expiration reminding message. The first unsubscribe instruction may also be an unsubscribe instruction of other messages, which is not limited in the present application.
S450: and if a second subscription cancellation indication fed back by the client is received, determining that all messages sent based on the target message type are not pushed to the client any more subsequently.
The second unsubscribe instruction may be a unsubscribe instruction fed back after the client receives the message to be pushed and selects unsubscribe from all messages sent based on the message type to which the client belongs, and if the client determines that the client unsubscribes from the push message of the message type, all messages sent based on the target message type are not pushed to the client subsequently.
S460: and if the read indication of the message to be pushed fed back by the client is received, determining that the message to be pushed is read by the client.
After the message to be pushed is pushed to the client, the client can perform read feedback on the received message to be pushed, and if a read indication of the message to be pushed fed back by the client is received, the client is determined to read the message to be pushed. The control of the feedback message is at the sending end, so that when the important message to be pushed is pushed to the client, the read information of the feedback message sent by the client can be received, the message to be pushed is determined to be read by the client, and the client is prevented from missing the reading of the important message to be pushed.
In some embodiments, if the feedback configuration selectable item in the preset configuration information selects whether to feed back the message read information, the client receives the message to be pushed, and then performs feedback message selection on a display interface or a setting interface, and may select the feedback message read information or not feed back the message read information, the feedback message is controlled by the receiving client, and if the feedback message read information is selected, the sender can receive a read instruction of the message to be pushed, which is fed back by the client, and then determines that the client has read the message to be pushed.
The order of the steps of implementing steps S440-S460 is not limited herein, and steps S440-S460 may be implemented simultaneously, or one of steps S440, S450, or S460 may be implemented separately, and the present application is not limited herein.
In this embodiment, by feeding back the received to-be-pushed message by the receiving client, the interaction between the sending party and the receiving client can be enhanced, and in addition, the client can configure the received to-be-pushed message, for example, perform operations such as subscription or unsubscribe, so that the client can subscribe the message as required.
For the above embodiment, please refer to fig. 5, and fig. 5 is a schematic structural diagram of a message pushing device provided in the present application. The push apparatus 500 of the message includes a configuration module 510, an obtaining module 520, and a push module 530.
The configuration module 510 is configured to receive first registration information of at least one client, where the first registration information includes client information of a corresponding client and a push service configured for the client; and storing the client information and the push service corresponding to each client into a preset storage space.
Wherein, the client information includes: at least one of a client name, a client type, and a client service address.
The push service includes: at least one of a push type, a display configuration, a subscription configuration and a feedback configuration of the message to be pushed.
The push types include: at least one of mail pushing, short message pushing and application offline pushing.
The display configuration includes: at least one of the amount of information displayed, the display duration, or the display style.
The subscription configuration includes: whether to allow unsubscription of a single record message, whether to allow unsubscription of all messages sent based on the type of message to which it belongs, and whether to resume subscription.
The feedback configuration comprises: whether to feed back the message read information.
In some embodiments, the configuration module 510 is further configured to receive first registration information of at least one client, including: the method comprises the steps of obtaining client information of at least one client input by a user, and displaying a plurality of selectable items for generating push service for each client; based on the user's selection of the plurality of selectable options, a push service is determined for each client.
In some embodiments, the configuration module 510 is further configured to receive second registration information of at least one message type, where the second registration information includes at least one client information of a corresponding message type; and acquiring the client information in the second registration information, acquiring the push service of the client information in the second registration information from a preset storage space, and taking the acquired client information and the push service as preset configuration information of the message type.
The obtaining module 520 is configured to obtain a message pushing instruction, where the message pushing instruction includes a message to be pushed and a target message type, and determine, based on preset configuration information of the target message type, a pushing service of a client associated with the target message type; the target message type is one of the message types.
The preset configuration information of the target message type comprises: the system comprises at least one piece of client information and a push service corresponding to each piece of client information, wherein the client corresponding to each piece of client information is a client associated with a target message type.
The message pushing instruction also comprises sender information and receiver information; wherein, the sender information includes: at least one of the name of the sender, the account number of the sender, the contact way of the sender, the sending time and the sending equipment; the receiver information includes: at least one of the name of the receiver, the account number of the receiver and the contact way of the receiver.
The pushing module 530 is configured to push the message to be pushed to the client associated with the target message type according to the pushing service.
In some embodiments, after the pushing module 530 sends the message to be pushed to the client associated with the target message type according to the pushing service, the pushing module 530 is further configured to determine that the message associated with the message to be pushed is not to be pushed to the client subsequently if the first unsubscribe indication fed back by the client is received.
In some embodiments, the pushing module 530 determines that all messages sent based on the target message type are not to be subsequently pushed to the client if the second unsubscribe indication fed back by the client is received.
In some embodiments, the pushing module 530 determines that the client has read the message to be pushed if the read indication of the message to be pushed fed back by the client is received.
The specific implementation of this embodiment can refer to the implementation process of the above embodiment, and is not described herein again.
For the above embodiment, please refer to fig. 6, where fig. 6 is a schematic structural diagram of a computer device provided in the present application. The computer device 600 includes: comprises a processor 610 and a memory 620, wherein the processor 610 is connected with the memory 620, the memory 620 is used for storing computer programs, and the computer programs are executed by the processor 610 to realize the pushing method of the messages.
In this embodiment, the processor 610 may also be referred to as a CPU (Central Processing Unit). The processor 610 may be an integrated circuit chip having signal processing capabilities. The processor 610 may also be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. A general purpose processor may be a microprocessor or the processor 610 may be any conventional processor or the like.
The specific implementation of this embodiment can refer to the implementation process of the above embodiment, and is not described herein again.
For the method of the above embodiment, it may exist in the form of a computer program, so that the present application provides a computer readable storage medium, please refer to fig. 7, and fig. 7 is a schematic structural diagram of the computer readable storage medium provided in the present application. The computer-readable storage medium 700 of the present embodiment stores therein a computer program 710 that can be executed to implement the method in the above-described embodiments.
The computer-readable storage medium 700 of this embodiment may be a medium that can store program instructions, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk, or may be a server that stores the program instructions, and the server may send the stored program instructions to other devices for operation, or may self-execute the stored program instructions.
In the several embodiments provided in the present application, it should be understood that the disclosed method and apparatus may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of a module or a unit is merely a logical division, and an actual implementation may have another division, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
Units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
It will be apparent to those skilled in the art that the modules or steps of the present application described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and they may alternatively be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, or fabricated separately as individual integrated circuit modules, or fabricated as a single integrated circuit module from multiple modules or steps. Thus, the present application is not limited to any specific combination of hardware and software.
The above description is only for the purpose of illustrating embodiments of the present application and is not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application or are directly or indirectly applied to other related technical fields, are also included in the scope of the present application.
Claims (10)
1. A method for pushing a message, the method comprising:
acquiring a message pushing instruction, wherein the message pushing instruction comprises a message to be pushed and a target message type;
determining a push service of a client associated with the target message type based on preset configuration information of the target message type;
and pushing the message to be pushed to a client associated with the target message type according to the pushing service.
2. The method of claim 1,
the preset configuration information of the target message type comprises: the client side corresponding to each piece of client side information is the client side related to the target message type.
3. The method of claim 2, wherein prior to obtaining the message push instruction, the method further comprises:
receiving first registration information of at least one client, wherein the first registration information comprises client information corresponding to the client and push service configured for the client;
storing the client information and the push service corresponding to each client into a preset storage space;
receiving second registration information of at least one message type, wherein the second registration information comprises at least one piece of client information corresponding to the message type;
and acquiring the client information in the second registration information, acquiring a push service of the client information in the second registration information from the preset storage space, and using the acquired client information and the push service as preset configuration information of the message type, wherein the target message type is one of the message types.
4. The method of claim 3, wherein receiving the first registration information of at least one of the clients comprises:
acquiring client information of at least one client input by a user, and displaying a plurality of selectable items for generating the push service for each client;
determining a push service for each of the clients based on the user's selection of the plurality of selectable items.
5. The method of claim 2,
the client information includes: at least one of a client name, a client type, and a client service address;
the push service includes: and at least one of a pushing type, a display configuration, a subscription configuration and a feedback configuration of the message to be pushed.
6. The method of claim 5,
the push types include: at least one of mail pushing, short message pushing and application offline pushing;
the display configuration includes: at least one of the amount of information displayed, the display duration, or the display style;
the subscription configuration includes: whether to allow to cancel at least one of a single recording message of the subscription, whether to allow to cancel all messages sent based on the type of the messages to which the subscription belongs, and whether to recover the subscription;
the feedback configuration comprises: whether to feed back the message read information.
7. The method of claim 6, wherein after the sending the message to be pushed to the client associated with the target message type according to the push service, the method further comprises:
if a first subscription cancellation indication fed back by the client is received, determining that a message associated with the message to be pushed is not pushed to the client any more subsequently;
if a second unsubscribe instruction fed back by the client is received, determining that all messages sent based on the target message type are not pushed to the client any more subsequently;
and if the read indication of the message to be pushed fed back by the client is received, determining that the message to be pushed is read by the client.
8. The method of claim 1, wherein the message push instruction further comprises sender information and recipient information;
the sender information includes: at least one of the name of the sender, the account number of the sender, the contact way of the sender, the sending time and the sending equipment;
the receiver information includes: at least one of the name of the receiver, the account number of the receiver and the contact way of the receiver.
9. A computer device, characterized in that the computer device comprises: a processor and a memory for storing a computer program for execution by the processor to implement the method of any one of claims 1 to 8.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which is executed by a processor to implement the method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010687572.7A CN111917843A (en) | 2020-07-16 | 2020-07-16 | Message pushing method, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010687572.7A CN111917843A (en) | 2020-07-16 | 2020-07-16 | Message pushing method, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111917843A true CN111917843A (en) | 2020-11-10 |
Family
ID=73281146
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010687572.7A Pending CN111917843A (en) | 2020-07-16 | 2020-07-16 | Message pushing method, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111917843A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112532712A (en) * | 2020-11-24 | 2021-03-19 | 青岛海尔科技有限公司 | Protocol transmission method and device, storage medium, and electronic device |
| CN112689202A (en) * | 2021-03-22 | 2021-04-20 | 北京达佳互联信息技术有限公司 | Live broadcast room message processing method and device, server and storage medium |
| CN112839087A (en) * | 2021-01-06 | 2021-05-25 | 深圳市芯中芯科技有限公司 | Cluster-based multi-terminal control method and system |
| CN113038201A (en) * | 2021-02-07 | 2021-06-25 | 深圳创维－Rgb电子有限公司 | Data interaction method and device, television equipment and computer readable storage medium |
| CN113225699A (en) * | 2021-04-30 | 2021-08-06 | 西安热工研究院有限公司 | Message sending system and method based on alarm platform, and medium and equipment of storage method |
| CN113641762A (en) * | 2021-08-20 | 2021-11-12 | 深圳市四格互联信息技术有限公司 | Information pushing method, device and system and computer readable storage device |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104202733A (en) * | 2014-09-17 | 2014-12-10 | 合一网络技术(北京)有限公司 | Personalized data information pushing method and system based on wireless terminals |
| CN106453582A (en) * | 2016-10-20 | 2017-02-22 | 深圳市证通电子股份有限公司 | Asynchronous message pushing method and system |
| CN106572146A (en) * | 2015-10-13 | 2017-04-19 | 腾讯科技（深圳）有限公司 | Message sending method and message sending device |
| CN107105066A (en) * | 2017-07-09 | 2017-08-29 | 孝感市青谷信息科技有限公司 | A kind of information push method based on user profile |
| CN108460115A (en) * | 2018-02-10 | 2018-08-28 | 深圳壹账通智能科技有限公司 | Information push method, device, computer equipment and storage medium |
| CN108629045A (en) * | 2018-05-14 | 2018-10-09 | 平安科技（深圳）有限公司 | A kind of information push method, storage medium and server |
| CN109067897A (en) * | 2018-08-24 | 2018-12-21 | 优视科技新加坡有限公司 | Information push method and its device, equipment/terminal/server, computer-readable medium |
| CN109246220A (en) * | 2018-09-19 | 2019-01-18 | 南方科技大学 | A kind of message push system and method |
| CN109783720A (en) * | 2018-11-30 | 2019-05-21 | 平安科技（深圳）有限公司 | Information push method, device, computer installation and storage medium |
| CN109787884A (en) * | 2019-01-02 | 2019-05-21 | 中国联合网络通信集团有限公司 | A kind of information push method and device |
| CN110149363A (en) * | 2019-04-15 | 2019-08-20 | 深圳壹账通智能科技有限公司 | A kind of information push method, device and storage medium |
| CN110321481A (en) * | 2019-06-05 | 2019-10-11 | 平安科技（深圳）有限公司 | Information push method, system, computer equipment and storage medium |
| CN110381166A (en) * | 2019-08-07 | 2019-10-25 | Oppo（重庆）智能科技有限公司 | A kind of message informing management method, device and computer readable storage medium |
-
2020
- 2020-07-16 CN CN202010687572.7A patent/CN111917843A/en active Pending
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104202733A (en) * | 2014-09-17 | 2014-12-10 | 合一网络技术(北京)有限公司 | Personalized data information pushing method and system based on wireless terminals |
| CN106572146A (en) * | 2015-10-13 | 2017-04-19 | 腾讯科技（深圳）有限公司 | Message sending method and message sending device |
| CN106453582A (en) * | 2016-10-20 | 2017-02-22 | 深圳市证通电子股份有限公司 | Asynchronous message pushing method and system |
| CN107105066A (en) * | 2017-07-09 | 2017-08-29 | 孝感市青谷信息科技有限公司 | A kind of information push method based on user profile |
| CN108460115A (en) * | 2018-02-10 | 2018-08-28 | 深圳壹账通智能科技有限公司 | Information push method, device, computer equipment and storage medium |
| CN108629045A (en) * | 2018-05-14 | 2018-10-09 | 平安科技（深圳）有限公司 | A kind of information push method, storage medium and server |
| CN109067897A (en) * | 2018-08-24 | 2018-12-21 | 优视科技新加坡有限公司 | Information push method and its device, equipment/terminal/server, computer-readable medium |
| CN109246220A (en) * | 2018-09-19 | 2019-01-18 | 南方科技大学 | A kind of message push system and method |
| CN109783720A (en) * | 2018-11-30 | 2019-05-21 | 平安科技（深圳）有限公司 | Information push method, device, computer installation and storage medium |
| CN109787884A (en) * | 2019-01-02 | 2019-05-21 | 中国联合网络通信集团有限公司 | A kind of information push method and device |
| CN110149363A (en) * | 2019-04-15 | 2019-08-20 | 深圳壹账通智能科技有限公司 | A kind of information push method, device and storage medium |
| CN110321481A (en) * | 2019-06-05 | 2019-10-11 | 平安科技（深圳）有限公司 | Information push method, system, computer equipment and storage medium |
| CN110381166A (en) * | 2019-08-07 | 2019-10-25 | Oppo（重庆）智能科技有限公司 | A kind of message informing management method, device and computer readable storage medium |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112532712A (en) * | 2020-11-24 | 2021-03-19 | 青岛海尔科技有限公司 | Protocol transmission method and device, storage medium, and electronic device |
| CN112839087A (en) * | 2021-01-06 | 2021-05-25 | 深圳市芯中芯科技有限公司 | Cluster-based multi-terminal control method and system |
| CN113038201A (en) * | 2021-02-07 | 2021-06-25 | 深圳创维－Rgb电子有限公司 | Data interaction method and device, television equipment and computer readable storage medium |
| CN112689202A (en) * | 2021-03-22 | 2021-04-20 | 北京达佳互联信息技术有限公司 | Live broadcast room message processing method and device, server and storage medium |
| CN112689202B (en) * | 2021-03-22 | 2021-06-15 | 北京达佳互联信息技术有限公司 | Live broadcast room message processing method and device, server and storage medium |
| US11553256B2 (en) | 2021-03-22 | 2023-01-10 | Beijing Dajia Internet Information Technology Co., Ltd. | Method and device for processing message in live broadcast room |
| CN113225699A (en) * | 2021-04-30 | 2021-08-06 | 西安热工研究院有限公司 | Message sending system and method based on alarm platform, and medium and equipment of storage method |
| CN113225699B (en) * | 2021-04-30 | 2022-07-01 | 西安热工研究院有限公司 | Message sending system and method based on alarm platform, and medium and equipment of storage method |
| CN113641762A (en) * | 2021-08-20 | 2021-11-12 | 深圳市四格互联信息技术有限公司 | Information pushing method, device and system and computer readable storage device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111917843A (en) | Message pushing method, computer equipment and storage medium | |
| CN109905315B (en) | Information acquisition method and device for group tasks | |
| US8121147B2 (en) | Context-sensitive multimedia message service response | |
| CN102567299B (en) | Interacted with electrical form using text message | |
| CN109347934B (en) | Message pushing method and system, server, storage medium and electronic device | |
| JP6501919B2 (en) | Voice chat mode self-adaptation method and apparatus | |
| US20150229598A1 (en) | Method and system of synchroning an unread message in instant communication | |
| CN105282013A (en) | Item message notification method, device and system | |
| WO2016153824A1 (en) | Method and system for providing private chat within a group chat | |
| US9497602B2 (en) | System and method of enterprise mobile message | |
| CN111669311A (en) | Communication method, communication device, communication system, electronic equipment and readable storage medium | |
| US10200338B2 (en) | Integrating communication modes in persistent conversations | |
| CN111913625A (en) | Message processing method and device and electronic equipment | |
| WO2007139538A1 (en) | Active polling technique | |
| WO2019062390A1 (en) | Information operating method and device, and medium | |
| CN112702255A (en) | Instant messaging message processing method and device and electronic equipment | |
| WO2019124302A1 (en) | Management server, message communication method, and message communication program | |
| CN111698147B (en) | Message prompting method, device, terminal and storage medium | |
| CN113014404B (en) | Message transmission method and device, server and second client | |
| CN109150696B (en) | Information processing method, server, client, and computer-readable storage medium | |
| CN114390452A (en) | Message sending method and related equipment | |
| CN116627666A (en) | Processing method and device of notification message, computer equipment and storage medium | |
| CN110300048B (en) | Audio message sending method, equipment and system based on instant messaging | |
| CN110769386A (en) | Short message pushing method and device applied to server side | |
| WO2023029557A1 (en) | Information pushing method and apparatus, and electronic device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |