Message push method, computer device and storage medium
By obtaining message push instructions and determining the client's push service based on preset configuration information, the problem of the inability to meet the message push needs in a specific environment in the prior art is solved, personalized push of messages is realized, and operation is simplified and work efficiency is improved. .
Patent Information
- Application Number
- CN202010687572.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-07-16
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2040-07-16
AI Technical Summary
The prior art cannot meet the personalized needs of enterprises or individuals to push messages in specific environments, and the operation is complicated, so configuration information cannot be set for specific message types.
By obtaining message push instructions, based on the preset configuration information of the target message type, the push service of the client associated with the target message type is determined, and the push message to be pushed to the client associated with the target message type is pushed according to the push service, realizing the personalization of the message Push.
It realizes pushing messages according to the needs of each client, meeting the personalized needs of specific message types, and is simple and convenient to operate, reducing the workload of application developers and improving work efficiency.
Smart Images

Figure CN111917843B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a message pushing method, a computer device, and a computer-readable storage medium. Background Art
[0002] With the continuous development of computer and Internet technology, the Internet has become an important way for people to obtain information. Various push messages can be pushed to user terminals with the help of servers and displayed to users through user terminals, bringing many conveniences to people's lives.
[0003] At present, with the development of enterprises, more and more enterprises use message push to distribute messages to various clients. In the internal management of enterprises, messages can also be distributed to internal department employees. Most of the existing technologies are developed on specific platforms, for specific customers and specific scenarios, and cannot meet the needs of enterprises or individuals to push messages in specific environments. Summary of the invention
[0004] The present application provides a message push method, computer device and storage medium, which can set configuration information for a specific message type to meet the personalized needs of clients of the specific message type and their pushed messages, and the operation is simple and convenient.
[0005] In order to solve the above technical problems, a technical solution adopted by the present application is to provide a message push method. The method includes: obtaining a message push instruction, wherein the message push instruction includes a message to be pushed and a target message type; based on preset configuration information of the target message type, determining a push service of a client associated with the target message type; and according to the push service, pushing the message to be pushed to the client associated with the target message type.
[0006] To solve the above technical problem, another technical solution adopted by the present application is to provide a computer device, which includes a processor and a memory, wherein the memory is used to store a computer program, and the computer program is executed by the processor to implement the above message push method.
[0007] To solve the above technical problem, another technical solution adopted by the present application is to provide a computer-readable storage medium. The computer-readable storage medium stores a computer program, and the computer program is executed by a processor to implement the above message push method.
[0008] The beneficial effects of the present application are as follows: the present application associates the target message type with the client to which the message needs to be pushed based on the preset configuration information of the target message type, and the push service of the client associated with the target message type, so that the messages to be pushed of the target message type are pushed to each client according to the push message requirements of each client, and configuration information can be set for a specific message type to meet the personalized needs of the client of the specific message type and its push messages, and the operation is simple and convenient. BRIEF DESCRIPTION OF THE DRAWINGS
[0009] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0010] Figure 1 This is a flowchart of a first embodiment of a message push method provided by the present application;
[0011] Figure 2 It is a flowchart of a second embodiment of the message push method provided by the present application;
[0012] Figure 3 It is a flowchart of a third embodiment of the message push method provided by the present application;
[0013] Figure 4 It is a flowchart of a fourth embodiment of the message push method provided by the present application;
[0014] Figure 5 It is a structural diagram of a message push device provided by this application;
[0015] Figure 6 It is a structural schematic diagram of a computer device provided by this application;
[0016] Figure 7 It is a schematic diagram of the structure of the computer-readable storage medium provided in this application. DETAILED DESCRIPTION
[0017] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0018] The terms "first", "second", "third" in this application are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Thus, the features defined as "first", "second", "third" can expressly or implicitly include at least one of the features. In the description of this application, the meaning of "multiple" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined. In the embodiments of this application, all directional indications (such as up, down, left, right, front, back...) are only used to explain the relative position relationship, movement, etc. between the components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication also changes accordingly. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the steps or units listed, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices.
[0019] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments without conflict.
[0020] The following describes various embodiments of the present application.
[0021] See also Figure 1 , Figure 1 This is a flow chart of a first embodiment of a method for pushing a message provided by the present application, the method comprising the following steps:
[0022] S110: Obtain a message push instruction, wherein the message push instruction includes a message to be pushed and a target message type.
[0023] The target message type can be a message type about the target business. For example, in the process of processing business messages, there are often some information that needs to be pushed to users in a timely manner for reminders, such as pending approval prompt messages, early warning prompt messages, error reminder messages, operation prompt messages, etc. Various messages can be divided into different message types, and this application does not impose any restrictions on this.
[0024] When a message needs to be pushed, a message push instruction is obtained, which includes 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. Among them, the message to be pushed can be the message content that needs to be pushed, and this application does not limit this.
[0025] In some embodiments, the message push instruction also includes sender information and receiver information, wherein the sender information includes: at least one of the sender's name, sender's account, sender's contact information, sending time, and sending device; the receiver information includes: at least one of the receiver's name, receiver's account, and receiver's contact information. The contact information may include a mobile phone number, a telephone number, a user's email address, etc. In some application scenarios, the display, content, style, etc. of the sender's information and the receiver's information can be set according to specific needs, and this application does not limit this.
[0026] S120: Determine a push service for a client associated with the target message type based on preset configuration information of the target message type.
[0027] The preset configuration information of the target message type includes: at least one client information and a push service corresponding to each client information, wherein the client corresponding to each client information is a client associated with the target message type.
[0028] After obtaining the target message type, the client information to which the target message type needs to be pushed and the push service corresponding to each client of the target message type can be obtained based on the preset configuration information of the target message type. For example, in some application scenarios, due to different target message types, some messages may need to be sent to multiple different clients, and some messages may only need to be sent to one client due to the importance and urgency of the target message type. Therefore, different client information can be configured according to the target message type. 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.
[0029] S130: Pushing the message to be pushed to the client associated with the target message type according to the push service.
[0030] After obtaining the client information to which the target message type needs to be pushed and obtaining the push service corresponding to each client of the target message type, the messages to be pushed can be pushed to the clients associated with the target message type according to the push service.
[0031] In this embodiment, the application associates the target message type with the client to which the message needs to be pushed based on the preset configuration information of the target message type, and associates the target message type with the client's push service, so that the target type of messages to be pushed are pushed to each client according to the push service requirements of each client. Configuration information can be set for specific message types to meet the personalized needs of clients of specific message types and their push messages, and the operation is simple and convenient.
[0032] Before the above step S110, the preset configuration information may also be configured. Figure 2 , Figure 2 1 is a flow chart of a second embodiment of a method for pushing a message provided by the present application, the method comprising the following steps:
[0033] S210: Receive first registration information of at least one client, wherein the first registration information includes client information of the corresponding client and a push service configured for the client.
[0034] Before obtaining the message push instruction to push the message to be pushed, the preset configuration information of the target message type is configured. For example, when configuring the client information, the distribution tool receives the first registration information of at least one client, wherein the first registration information includes the client information of the corresponding client and the push service configured for the client.
[0035] In some embodiments, receiving the first registration information of at least one client includes: obtaining the client information of at least one client input by a user, and displaying a plurality of options for generating a push service for each client. For example, the options may include at least one of a push type, display configuration, subscription configuration, and 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 options.
[0036] The client information includes at least one of the client name, client type, and client service address. The client type includes, for example, PC (Personal Computer) messages, mobile phone messages, PC conversations, mobile phone conversations, emails, etc., which are not limited in this application.
[0037] The push service includes: at least one of the push type, display configuration, subscription configuration, and feedback configuration of the message to be pushed. In some application scenarios, the client type corresponding to each client can also be configured to display the corresponding options of the push service end, so as to configure personalized push services for each type of client. Of course, other push services can also be included, and this application does not limit this.
[0038] For the push service, the push type of the message to be pushed includes at least one of: email push, SMS push, and application offline push. For example, for the client type of the client, the push method of the client type can be configured. When the client is a PC or a mobile phone, different push methods can be configured for the PC and the mobile phone. In addition, the push type of the message to be pushed can be configured for each client, or the push type can be configured for the target message type, and this application does not limit this.
[0039] The display configuration includes: at least one of the amount of information displayed, the display duration, or the display style. Depending on the different clients and the different message types of the business types, each client can be configured according to different display requirements when receiving a message for display. For example, the amount of information displayed includes displaying all information, displaying part of the information, displaying the title of the message, etc. The display duration is the time the message is displayed after the client receives the message. The display style is the style of the message after the client receives the message, such as the display style of the displayed content, the location of the displayed content, etc. The message content is displayed in a font style, etc. This application does not impose any restrictions on this. The display configuration can be set according to the client or message type, and this application does not impose any restrictions on this.
[0040] The subscription configuration includes at least one of: whether to allow unsubscribing a single record message, whether to allow unsubscribing all messages sent based on the message type to which they belong, and whether to restore the subscription.
[0041] Among them, if an optional option is received to allow unsubscribing from a single recorded message, when the message to be pushed is pushed to the client associated with the target message type according to the push service, the client can choose whether to unsubscribe from the single recorded message. If the client chooses to unsubscribe from the single recorded message, the client returns an identifier of unsubscribing from the single recorded message to the sender, so that after the sender receives the identifier, it will no longer send messages associated with the message to be pushed. The associated message can be a recorded message of the same record, such as a password expiration reminder recorded message. After the client receives the password expiration reminder recorded message, it chooses to unsubscribe from the single recorded message, and then the password expiration reminder recorded message will no longer be sent to the client subsequently. In some embodiments, after the client chooses to unsubscribe from the single recorded message, it can set the message to be pushed not to be displayed on the front end of its client, and after receiving the message to be pushed subsequently, it will no longer be displayed. In addition, the above-mentioned single recorded message also belongs to a type of message type, and this application does not limit this.
[0042] If you select whether to allow unsubscribing from all messages sent based on the message type, after the push service pushes the message to be pushed to the client associated with the target message type, the client can choose whether to unsubscribe from all messages sent based on the message type. If the client chooses to unsubscribe from all messages sent based on the message type, the target message type will no longer be sent to the client.
[0043] If you select whether to restore the subscription, when the push service pushes the message to be pushed to the client associated with the target message type, and you choose to unsubscribe from a single recorded message or unsubscribe from all messages sent based on the message type, the client can choose whether to restore the subscription. For example, you can open the message to be pushed again, restore the subscription to a single recorded message or subscribe to all messages sent based on the message type, and this application does not limit this.
[0044] The above-mentioned subscription configuration in the present application may also include other subscription messages, and whether the subscription can be restored can also be configured separately according to the subscription message. For example, whether the above-mentioned cancellation of subscription for a single record message is allowed can be configured as an irreversible subscription, and whether the cancellation of subscription for all messages sent based on the corresponding message type is allowed can be configured as a reversible subscription. It can be configured according to specific needs, and the present application does not impose any restrictions on this.
[0045] Feedback configuration includes: whether to feedback the message reading information. The feedback message reading information is that after the client receives the message and displays it, if the client receives the message marked as unread, the feedback message is unread; if the client receives the message marked as read, the feedback message is read. For example, some messages only require a simple prompt on some clients, and the display time is sufficient. Some messages require the user to mark the message as read before closing it on some clients. Some messages require the user to process it before closing it on some clients. This application does not impose any restrictions on this.
[0046] Based on the user's selection of multiple options, the push service of each client is determined. Specifically, based on the user's selection of multiple options displayed on each client for generating push services, the push service of each client is determined, so that personalized message push configuration can be performed on each client.
[0047] S220: Saving the client information and push service corresponding to each client into a preset storage space.
[0048] After obtaining the client information corresponding to the above-mentioned client and the push service of the corresponding client, they can be stored in a specified path or in a preset storage space, so that in the subsequent steps S110-130, the client information and the push service corresponding to the client can be read in the preset storage space according to the message push instruction, so as to push the message to be pushed to the client associated with the target message type according to the read client information corresponding to the client and the push service.
[0049] For the above embodiment, before the above step S110, the preset configuration information may also be configured. Figure 3 , Figure 3 : is a flow chart of a third embodiment of a method for pushing a message provided by the present application, the method comprising the following steps:
[0050] S310: Receive second registration information of at least one message type, wherein the second registration information includes at least one client information corresponding to the message type.
[0051] Before obtaining the message push instruction to push the message to be pushed, the preset configuration information of the target message type is configured. For example, when configuring the message type, the distribution tool receives the second registration information of at least one message type, wherein the second registration information includes at least one client information of the corresponding message type. For example, the registered message types are pending approval prompt messages, early warning prompt messages, error reminder messages, operation prompt messages, etc. Different message types need to be pushed to the client. When registering the message type, the client corresponding to the message type can be selected so that different message types can push messages to different clients.
[0052] The target message type is one of the message types. After registering the message type, one of the message types can be used as the target message type of the message to be pushed.
[0053] S320: Acquire the client information in the second registration information, and acquire the push service of the client information in the second registration information from the preset storage space, and use the acquired client information and push service as preset configuration information of the message type.
[0054] When registering the second registration message, after receiving the registered message type, you can select the client associated with the message type, obtain the client information corresponding to the message type in the second registration message, and obtain the client information and the push service corresponding to the client information in the preset storage space of the first registration message, and use the obtained client information and push service as the preset configuration information of the message type in the second registration message.
[0055] In some embodiments, the message type and the corresponding information of each client and the push service obtained above can be saved in a preset storage space, so that the client information and the push service corresponding to the message type can be obtained when pushing messages later.
[0056] In some embodiments, the push service of the client can also be configured for the message type. Specifically, the client information of at least one client corresponding to the message type input by the user is obtained, and multiple options for generating the push service are displayed for each client. For example, the options may include at least one of the push type, display configuration, subscription configuration, and feedback configuration of the message to be pushed by the push service, so that the push service of the client corresponding to the message type is configured according to the selected options.
[0057] In some embodiments, the first registration information and the second registration information can be modified. When modifying the first registration information, the client of the first registration information to be modified is obtained, the client information and push service corresponding to the client to be modified are read in the preset storage space, the client information and push service newly input by the user are obtained for update, and the updated client information and push service are stored in the preset storage space. In addition, when modifying the second registration message, the message type to be modified is obtained, the client and client information corresponding to the message type are read, at least one client newly input by the user and the client information are obtained for update, and the client information of at least one client input by the user is obtained, and multiple options for generating a push service are displayed for each client, so that the push service is updated and stored in the preset storage space.
[0058] In addition, in the prior art, when pushing messages in specific scenarios or to specific customers, it is necessary to design message push configurations separately for different messages and push methods of different clients, which results in application developers having to learn and develop separately for different clients and different message push methods, which in turn leads to low work efficiency.
[0059] Compared with the prior art, in the embodiments of the present application, the first registration information of at least one client can be received, so that the client information can be registered and the push service of the client can be configured, and the push service can be configured in a personalized manner for each client. In addition, the second registration information of at least one message type can be received, so that the message type can be registered and the corresponding receiving client of the message type can be configured. The corresponding receiving client and the push service of the corresponding client and message type can be configured for the push message of each message type, which can meet the personalized needs of push messages of specific environments, specific clients, and specific message types, and the operation is simple and convenient. Furthermore, the present application configures the use of the above-mentioned distribution tool, which can reduce the workload of application developers and improve work efficiency.
[0060] For the above examples, see Figure 4 , Figure 4 4 is a flow chart of a fourth embodiment of a method for pushing a message provided by the present application, the method comprising the following steps:
[0061] S410: Obtain a message push instruction, wherein the message push instruction includes a message to be pushed and a target message type.
[0062] The message push instruction also includes sender information including: at least one of the sender's name, sender's account, sender's contact information, sending time, and sending device; recipient information includes: at least one of the recipient's name, recipient's account, and recipient's contact information.
[0063] S420: Determine a push service for a client associated with the target message type based on preset configuration information of the target message type.
[0064] The preset configuration information of the target message type includes: at least one client information and a push service corresponding to each client information, wherein the client corresponding to each client information is a client associated with the target message type.
[0065] S430: Pushing the message to be pushed to the client associated with the target message type according to the push service.
[0066] The specific implementation of the above steps S410-430 can refer to the implementation process of steps S110-S130 in the above embodiment, which will not be repeated here.
[0067] After the above step S430, the method further includes at least one of the following steps:
[0068] S440: If a first unsubscribe instruction fed back by the client is received, determine that messages associated with the message to be pushed will no longer be pushed to the client in the future.
[0069] If a first unsubscribe indication is received from the client, it is determined that the client has unsubscribed, for example, an indication is received from the client that a single record message has been selected to unsubscribe, then it is determined that no message associated with the message to be pushed will be pushed to the client in the future. The message associated with the message to be pushed can be a record message of the same record as the message to be pushed, such as a password expiration reminder message. The first unsubscribe indication can also be an unsubscribe indication for other messages, which is not limited in this application.
[0070] S450: If a second unsubscribe instruction fed back by the client is received, it is determined that all messages sent based on the target message type will no longer be pushed to the client in the future.
[0071] Among them, based on whether the above-mentioned subscription configuration allows unsubscribing from all messages sent based on the corresponding message type, the second unsubscribe indication can be an unsubscribe indication fed back after the client receives the message to be pushed and chooses to unsubscribe from all messages sent based on the corresponding message type. It is determined that the client cancels the subscription to the push messages of this message type, and subsequently all messages sent based on the target message type will no longer be pushed to the client.
[0072] S460: If a read indication of the message to be pushed is received from the client, it is determined that the client has read the message to be pushed.
[0073] After the message to be pushed is pushed to the client, the client can provide feedback on the received message with push. If the client receives a read indication of the message to be pushed, it is determined that the client has read the message to be pushed. The control of the feedback message is at the sending end, so that when an important message to be pushed is pushed to the client, the feedback message sent by the client can be received to determine that the client has read the message to be pushed, thereby preventing the client from missing important messages to be pushed.
[0074] In some embodiments, if the feedback configuration option in the preset configuration information is selected as whether to provide feedback on message reading information, then after the client receives the message to be pushed, it selects the feedback message in the display interface or the setting interface. It can choose to provide feedback on message reading information or not. The control of the feedback message lies with the receiving client. If it is chosen to provide feedback on message reading information, the sender can receive the read indication of the message to be pushed from the client, thereby determining that the client has read the message to be pushed.
[0075] The order of implementing the above steps S440-S460 is not limited here. Steps S440-S460 can be implemented simultaneously, or one of the steps S440, S450 or S460 can be implemented separately. This application does not impose any restrictions on this.
[0076] In this embodiment, by receiving the client's feedback on the received message to be pushed, the interaction between the sender and the receiving client can be enhanced. In addition, the client can configure the received message to be pushed, such as subscribing or unsubscribing, so that the client can subscribe to the message according to demand.
[0077] For the above implementation, see Figure 5 , Figure 5 5 is a schematic diagram of the structure of the message push device provided by the present application. The message push device 500 includes a configuration module 510, an acquisition module 520 and a push module 530.
[0078] The configuration module 510 is used to receive first registration information of at least one client, wherein the first registration information includes client information of the corresponding client and a push service configured for the client; and save the client information and push service corresponding to each client into a preset storage space.
[0079] The client information includes at least one of a client name, a client type, and a client service address.
[0080] The push service includes: at least one of the push type, display configuration, subscription configuration, and feedback configuration of the message to be pushed.
[0081] The push type includes: at least one of email push, SMS push, and application offline push.
[0082] The display configuration includes at least one of the amount of information displayed, the display duration, or the display style.
[0083] The subscription configuration includes at least one of: whether to allow unsubscribing a single record message, whether to allow unsubscribing all messages sent based on the message type to which they belong, and whether to restore the subscription.
[0084] Feedback configuration includes: whether to feedback message reading information.
[0085] In some embodiments, the configuration module 510 is also used to receive first registration information of at least one client, including: obtaining client information of at least one client input by a user, and displaying multiple options for generating a push service for each client; and determining the push service for each client based on the user's selection of multiple options.
[0086] In some embodiments, the configuration module 510 is also used to receive second registration information of at least one message type, wherein the second registration information includes at least one client information of the corresponding message type; obtain the client information in the second registration information, and obtain the push service of the client information in the second registration information from a preset storage space, and use the obtained client information and push service as preset configuration information of the message type.
[0087] The acquisition module 520 is used to obtain a message push instruction, wherein the message push instruction includes a message to be pushed and a target message type, and based on preset configuration information of the target message type, determines a push service of a client associated with the target message type; the target message type is one of the message types.
[0088] The preset configuration information of the target message type includes: at least one client information and a push service corresponding to each client information, wherein the client corresponding to each client information is a client associated with the target message type.
[0089] The message push instruction also includes sender information and receiver information; wherein the sender information includes: at least one of the sender's name, sender's account, sender's contact information, sending time, and sending device; the receiver information includes: at least one of the receiver's name, receiver's account, and receiver's contact information.
[0090] The push module 530 is used to push the message to be pushed to the client associated with the target message type according to the push service.
[0091] In some embodiments, after the push module 530 sends the message to be pushed to the client associated with the target message type according to the push service, the push module 530 is also used to determine that messages associated with the message to be pushed will no longer be pushed to the client in the future if a first unsubscribe indication is received from the client.
[0092] In some embodiments, if the push module 530 receives the second unsubscribe instruction fed back by the client, it determines that all messages sent based on the target message type will no longer be pushed to the client in the future.
[0093] In some embodiments, if the push module 530 receives a read indication from the client for the message to be pushed, it determines that the client has read the message to be pushed.
[0094] The specific implementation of this embodiment can refer to the implementation process of the above embodiment, which will not be repeated here.
[0095] For the above implementation, see Figure 6 , Figure 6 The computer device 600 includes a processor 610 and a memory 620, wherein the processor 610 is connected to the memory 620, and the memory 620 is used to store a computer program, and the computer program is executed by the processor 610 to implement the above message push method.
[0096] 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 devices, discrete gate or transistor logic devices, discrete hardware components. A general-purpose processor may be a microprocessor or the processor 610 may also be any conventional processor, etc.
[0097] The specific implementation of this embodiment can refer to the implementation process of the above embodiment, which will not be repeated here.
[0098] The method of the above-mentioned embodiment may exist in the form of a computer program, so the present application proposes a computer-readable storage medium, see Figure 7 , Figure 7 The computer-readable storage medium 700 of this embodiment stores a computer program 710, which can be executed to implement the method in the above embodiment.
[0099] The computer-readable storage medium 700 of this embodiment may be a medium that can store program instructions, such as a USB flash drive, a mobile 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. The server may send the stored program instructions to other devices for execution, or may execute the stored program instructions by itself.
[0100] In the several embodiments provided in the present application, it should be understood that the disclosed methods and devices can be implemented in other ways. For example, the device implementation described above is only schematic. For example, the division of modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0101] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.
[0102] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0103] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of each implementation method of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program code.
[0104] Obviously, those skilled in the art should understand that the above modules or steps of the present application can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, and optionally, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. In this way, the present application is not limited to any specific combination of hardware and software.
[0105] The above description is only an implementation method of the present application, and does not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly used in other related technical fields, are also included in the patent protection scope of the present application.
Claims
1. A method for pushing a message. It is characterized in that The method comprises: Receiving first registration information of at least one client, wherein the first registration information includes client information corresponding to the client and a push service configured for the client; Saving 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 includes at least one client information corresponding to the message type; Acquire the client information in the second registration information, and acquire the push service of the client information in the second registration information from the preset storage space, and use the acquired client information and push service as preset configuration information of the message type; Obtain a message push instruction, wherein the message push instruction includes a message to be pushed and a target message type; wherein the target message type is one of the message types, and the target message type is a message type related to a target business, including a pending approval prompt message, a warning prompt message, an error prompt message, and an operation prompt message; Based on the preset configuration information of the target message type, determine the push service of the client associated with the target message type, wherein the push service includes: display configuration, subscription configuration, and feedback configuration of the message to be pushed, and 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 unsubscribing a single recorded message, whether to allow unsubscribing all messages sent based on the message type to which they belong, and whether the subscription can be restored; the feedback configuration includes: whether to feedback message reading information; According to the push service, push the message to be pushed to a client associated with the target message type; The preset configuration information of the target message type includes: at least one client information, and a push service corresponding to each piece of the client information, wherein the client corresponding to each piece of the client information is a client associated with the target message type.
2. The method according to claim 1, It is characterized in that The receiving of first registration information of at least one of the clients includes: Acquire client information of at least one client input by a user, and display multiple options for generating the push service for each client; Based on the user's selection of the multiple optional items, a push service for each of the clients is determined.
3. The method according to claim 1, It is characterized in that The client information includes: at least one of a client name, a client type, and a client service address; The push service also includes: the push type of the message to be pushed.
4. The method according to claim 3, It is characterized in that The push type includes: at least one of email push, SMS push, and application offline push.
5. The method according to claim 4, It is characterized in that After sending the message to be pushed to the client associated with the target message type according to the push service, the method further includes: If a first unsubscribe indication fed back by the client is received, determining that no message associated with the message to be pushed will be pushed to the client in the future; If a second unsubscribe indication fed back by the client is received, determining that all messages sent based on the target message type will no longer be pushed to the client in the future; If a read indication of the message to be pushed fed back by the client is received, it is determined that the client has read the message to be pushed.
6. The method according to claim 1, It is characterized in that The message push instruction also includes sender information and receiver information; The sender information includes: at least one of the sender's name, sender's account, sender's contact information, sending time, and sending device; The recipient information includes at least one of the recipient's name, the recipient's account number, and the recipient's contact information.
7. A computer device, It is characterized in that The computer device comprises: a processor and a memory, wherein the memory is used to store a computer program, and the computer program is executed by the processor to implement the method according to any one of claims 1 to 6.
8. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores a computer program, and the computer program is executed by a processor to implement the method according to any one of claims 1 to 6.
