A Message Push Method, System, Medium and Device Based on Browser Plug-ins

Abstract

The present invention discloses a message push method, system, medium and device based on a browser plugin. The method includes: listening for a message push request; popping up a configuration form of the browser plugin to obtain the content filled in by the user, including: message recipients, the push quantity of each message type, push environment and custom content; the plugin determines the push address of each message type according to the push environment; calls the push address to obtain the message scenarios of each message type, and extracts the push parameters of each message scenario; matches the message recipient information, the custom content of each message type, combines with the message scenarios of each message type, and matches with the push parameters of each message scenario to assemble the push message of each message type; according to the push quantity of each message type, circularly calls the push address to push the push message of each message type to the message recipient. The present invention reduces the threshold of message push and effectively improves the message push efficiency.

Description

Technical Field

[0001] The present invention relates to the technical field of computer development, and particularly to a message pushing method, system, medium and device based on a browser plugin. Background Art

[0002] In the prior art, the message pushing work of the message center generally includes the following steps:

[0003] 1. The user enters the message center management background, finds the message scenario to be pushed, and checks which type of message this scenario belongs to (for example: text message, card message, markdown message, rich text message, etc., a total of 14 message types, and only one message type can be selected for each scenario). Moreover, the message environment can be divided into a production environment and a test environment, and the configuration of the two environments is completely different, so they need to be searched separately;

[0004] 2. Through the name of the message recipient, find the user ID of the recipient in the background system;

[0005] 3. Assemble the message packet body in json format according to the message scenario, message type, and user ID found in steps 1 and 2. Among them, the rich text format and markdown format are relatively complex. For users who have not studied relevant courses, they need to search the Internet to find the writing methods of the corresponding formats to complete the writing of the message packet body;

[0006] 4. Determine the message pushing environment (production environment or test environment). The url addresses for sending messages in different environments are different;

[0007] 5. After the above information is determined, use tools such as postman to send an http request to push the message. If it is necessary to push each of the 14 messages once, the above steps need to be repeated at least 14 times.

[0008] It can be seen that in the message pushing method in the prior art, it is necessary to manually search and determine information such as the message scenario, environment address, user ID, etc. corresponding to different message types, and manually write complex message pushing packets including rich text format, markdown format, etc. At the same time, due to manpower limitations, a large number of messages cannot be pushed in a short time, consuming a lot of time, manpower and material resources. The message pushing efficiency and accuracy are low, and the user experience is poor. Summary of the Invention

[0009] Based on this, it is necessary to propose a message pushing method, system, medium and device based on a browser plugin for the above problems.

[0010] The present invention discloses a message pushing method based on a browser plugin, and the method includes:

[0011] The browser is used to monitor the user's message push request;

[0012] According to the message push request, a configuration form of the browser plugin is popped up for the user to fill in, and the filled content is obtained. The filled content includes: message recipient information, the push quantity of each message type, the push environment, and custom content;

[0013] The browser plugin determines the push address of each message type according to the push environment of each message type in the filled content;

[0014] The browser plugin calls the push address of each message type to obtain the message scenario of each message type and extracts the push parameters of each message scenario;

[0015] The browser plugin matches the message recipient information and the custom content of each message type in the filled content with the message scenario of each message type and the push parameters of each message scenario, and assembles and constructs the push message of each message type;

[0016] The browser plugin traverses all messages, and according to the push quantity of each message type, cyclically calls the push address of each message type, and pushes the push message of each message type to the message recipient.

[0017] Further, after using the browser to monitor the user's message push request, it further includes:

[0018] Save the user information;

[0019] The push parameters of each message scenario include: message recipient identity identifier, message title, message text;

[0020] The browser plugin matches the message recipient information and the custom content of each message type in the filled content with the message scenario of each message type and the push parameters of each message scenario, and assembles and constructs the push message of each message type, specifically including:

[0021] The browser plugin parses whether the custom content of each message type in the filled content is filled in by the user. If so, the custom content of each message type in the filled content is assigned to the message text in the push parameters of each message scenario. If not, the preset default content is assigned to the message text in the push parameters of each message scenario;

[0022] When the browser plugin parses the filled content, it checks whether the message recipient information is filled by the user. If so, it looks up the identity identifier of the message recipient based on the message recipient information and assigns the identity identifier of the message recipient to the identity identifier of the message recipient in the push parameters for each message scenario. If not, it extracts the user identity identifier from the user information and assigns the user identity identifier to the identity identifier of the message recipient in the push parameters for each message scenario;

[0023] The browser plugin extracts the scenario name for each message scenario and assigns the scenario name to the message title in the push parameters for each message scenario;

[0024] According to the push parameters for each message scenario with the assignment completed, a push message for each message type is assembled.

[0025] Furthermore, the custom content for each message type includes: the custom syntax formats for the rich text message type and the markdown message type, and the custom message texts for other message types other than the rich text message type and the markdown message type;

[0026] When the browser plugin parses the filled content, it checks whether the user fills in the custom content for each message type. If so, it assigns the custom content for each message type in the filled content to the message text in the push parameters for each message scenario. If not, it assigns the preset default content to the message text in the push parameters for each message scenario, specifically including:

[0027] When the browser plugin parses the filled content, it checks whether the user fills in the custom syntax format for the rich text message type and / or the markdown message type. If so, it uses the user-defined syntax format to generate the push message for the rich text message type and / or the markdown message type. If not, it uses the pre-encapsulated default syntax format to automatically generate the push message for the rich text message type and / or the markdown message type;

[0028] When the browser plugin parses the filled content, it checks whether the user fills in the custom message text for other message types other than the rich text message type and the markdown message type. If so, it uses the user-defined message text to generate the push message for other message types other than the rich text message type and the markdown message type. If not, it uses the pre-encapsulated default text to generate the push message for other message types other than the rich text message type and the markdown message type.

[0029] Furthermore, the push quantity for each message type in the filled content specifically includes: the push rounds for each message type, and the push quantity for each message type in one round of push.

[0030] Further, the method further includes:

[0031] Sending a browser reminder notification to the user through the browser to notify the user that the message push is completed.

[0032] Further, the method further includes:

[0033] The browser plugin searches for all historical messages of the user according to the user information and deletes them all.

[0034] Further, the method further includes:

[0035] The browser plugin searches for all historical messages of the user according to the user information, obtains the dates of each historical message, and deletes the historical messages on the specified date.

[0036] On the other hand, the present invention also discloses a message push system based on a browser plugin, and the system includes:

[0037] A push request monitoring module, configured to monitor the user's message push request by using the browser;

[0038] A plugin form filling module, configured to pop up a configuration form of the browser plugin according to the message push request for the user to fill in, and obtain the filled content, where the filled content includes: message recipient information, the push quantity of each message type, the push environment, and custom content;

[0039] A push address determination module, configured to run the browser plugin and determine the push address of each message type according to the push environment of each message type in the filled content;

[0040] A message scenario acquisition and parameter extraction module, configured to call the push address of each message type by the browser plugin, obtain the message scenario of each message type, and extract the push parameters of each message scenario;

[0041] A push message assembly module, configured to match the message recipient information and the custom content of each message type in the filled content with the message scenario of each message type and the push parameters of each message scenario by the browser plugin, and assemble and constitute the push message of each message type;

[0042] A message push module, configured to traverse all messages by the browser plugin, and cyclically call the push address of each message type according to the push quantity of each message type, and push the push message of each message type to the message recipient.

[0043] On the other hand, the present invention also discloses a computer device, including a memory and a processor. The memory stores a computer program. When the computer program is executed by the processor, the processor performs the following steps:

[0044] Use a browser to listen for a user's message push request;

[0045] According to the message push request, pop up a configuration form of the browser plugin for the user to fill in, and obtain the filled content. The filled content includes: message recipient information, the push quantity of each message type, the push environment, and custom content;

[0046] The browser plugin determines the push address of each message type according to the push environment of each message type in the filled content;

[0047] The browser plugin calls the push address of each message type, obtains the message scenario of each message type, and extracts the push parameters of each message scenario;

[0048] The browser plugin matches the message recipient information and the custom content of each message type in the filled content, combines with the message scenario of each message type, and matches with the push parameters of each message scenario to assemble and form a push message of each message type;

[0049] The browser plugin traverses all messages, and according to the push quantity of each message type, cyclically calls the push address of each message type, and pushes the push message of each message type to the message recipient.

[0050] On the other hand, the present invention also discloses a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, the processor performs the following steps:

[0051] Use a browser to listen for a user's message push request;

[0052] According to the message push request, pop up a configuration form of the browser plugin for the user to fill in, and obtain the filled content. The filled content includes: message recipient information, the push quantity of each message type, the push environment, and custom content;

[0053] The browser plugin determines the push address of each message type according to the push environment of each message type in the filled content;

[0054] The browser plugin calls the push address of each message type, obtains the message scenario of each message type, and extracts the push parameters of each message scenario;

[0055] The browser plugin matches the message recipient information and the custom content of each message type in the filled content, combines the message scenarios of each message type with the push parameters of each message scenario, and assembles and constructs the push message of each message type;

[0056] The browser plugin traverses all messages, and according to the push quantity of each message type, circularly calls the push address of each message type, and pushes the push message of each message type to the message recipient.

[0057] Adopting the technical solution of the present invention has the following beneficial effects:

[0058] In the present invention, by using a browser plugin, according to the message type and push requirements, the push address of the message and the message recipient are automatically searched and confirmed, and the push message of the message is automatically assembled and pushed, so that the user can complete the message push without mastering the complex writing of the message type syntax format, reducing the threshold of message push. At the same time, the technical solution of this embodiment also supports the functions of mass pushing or deleting messages, as well as the custom function of message push, which can effectively improve the efficiency and quality of message push, expand the automation and intelligence level of the browser plugin, and enhance the user experience. Description of the Drawings

[0059] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the following drawings are only some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0060] Among them:

[0061] Figure 1 is a flowchart of a message push method based on a browser plugin in an embodiment;

[0062] Figure 2 is a flowchart of step S500 in a message push method based on a browser plugin in an embodiment;

[0063] Figure 3 is a structural block diagram of a message push system based on a browser plugin in an embodiment;

[0064] Figure 4 is a structural block diagram of a computer device in an embodiment.

[0065] Explanation of the reference numerals: push request monitoring module 100, plugin form filling module 200, push address determination module 300, message scenario acquisition and parameter extraction module 400, push message assembly module 500, message push module 600. Detailed implementation manners

[0066] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without making creative efforts shall fall within the protection scope of the present invention.

[0067] As Figure 1 shown, in one embodiment, a message push method based on a browser plug-in is provided. The method specifically includes the following steps:

[0068] S100. Use the browser to monitor the user's message push request.

[0069] In the specific implementation process, after using the browser to monitor the user's message push request, it further includes: saving user information. The browser can specifically be the Chrome browser. After the user opens the one-stop platform and completes the login, the webRequest.onBeforeSendHeaders.addListener method provided by the Chrome browser can be used to monitor the message push request of the specified user on the one-stop platform. When the message push request is monitored, the cookies in the header are saved to the storage of Chrome. The saved cookies contain the user's login information and user ID, that is, user information.

[0070] S200. According to the message push request, pop up a configuration form of the browser plug-in for the user to fill in, and obtain the filled content. The filled content includes: message recipient information, the push quantity of each message type, the push environment, and custom content.

[0071] In the specific implementation process, the user opens the Chrome browser, imports the local plug-in package in the plug-in panel, and after the import, left-click to open the plug-in, and a front-end page will pop up. This front-end page is the configuration form of the browser plug-in and needs to be filled in by the user. The filled content can include:

[0072] Message recipient information, that is, the user to whom the message needs to be pushed. This user can be the user himself or someone other than the user himself. When pushing to the user himself, this item can be left blank, and it is default that the message is pushed to himself. When pushing to someone else, the user name of the message recipient or other relevant information that can find the message recipient can be filled in;

[0073] The push quantity of each message type. When pushing messages, there are 14 types of messages in total. The number of messages pushed for each type can be filled in by the user according to their own needs. If not filled in, it is default that one message of each type is pushed. Further, in one embodiment, the push quantity can also include the push rounds of each message type. For example, if 14 types of messages are each pushed 1 time and pushed 1 round, then 14 messages will be pushed to the user. And if 14 types of messages are each pushed 2 times and pushed 2 rounds, then 56 messages will be pushed to the user, thus achieving the effect of batch pushing;

[0074] The push environment of each message type. The message push environment is divided into a production environment and a test environment, which the user can fill in according to their own needs. If not filled in, it is default to push to the test environment;

[0075] The custom content of each message type. A custom content input box can be set on the right side of the push quantity input box for each message type. Among them, for the rich text message type and the markdown message type, it is a custom syntax format input box. The user can fill the desired syntax format into the input box. In this way, when pushing these 2 types of messages, the user-defined syntax format will be preferentially used. If the user does not input, the browser plugin will automatically generate the pre-encapsulated mainstream default syntax format. For other message types, it is a message text input box, and the user can customize the text of the pushed message. If the user does not input, the browser plugin will automatically generate the pre-encapsulated default text.

[0076] S300. The browser plugin determines the push address of each message type according to the push environment of each message type in the filled content.

[0077] S400. The browser plugin calls the push address of each message type, obtains the message scenarios of each message type, and extracts the push parameters of each message scenario.

[0078] In the specific implementation process, after the user fills in the configuration form of the browser plugin, the user can click a button to push messages, and the browser plugin will start running and perform the message push work according to the user's needs. First, the browser plugin will determine the push address of each message type according to the push environment of each message type filled in by the user, and then call the message center background interface to obtain the message scenarios of each message type. The interface address is the push address of each message type just determined. The message scenarios can specifically include the scenario code and the scenario name, and then extract the push parameters of each message scenario.

[0079] S500. The browser plugin matches the message recipient information and the custom content of each message type in the filled content with the message scenarios of each message type and the push parameters of each message scenario, and assembles and constructs the push message for each message type.

[0080] Specifically, the push parameters for each message scenario include: the identity identifier of the message recipient, the message title, and the message text;

[0081] Step S500 specifically includes:

[0082] S510. In the browser plugin's parsing of the filled content, check whether the user has filled in the custom content for each message type. If so, execute step S511; if not, execute step S512;

[0083] S511. Assign the custom content of each message type in the filled content to the message text in the push parameters for each message scenario;

[0084] S512. Assign the preset default content to the message text in the push parameters for each message scenario;

[0085] Among them, more specifically, the custom content of each message type includes: the custom syntax formats of the rich text message type and the markdown message type, and the custom message texts of other message types other than the rich text message type and the markdown message type;

[0086] Steps S510, S511, and S512 specifically include:

[0087] In the browser plugin's parsing of the filled content, check whether the user has filled in the custom syntax format of the rich text message type and / or the markdown message type. If so, use the user-defined syntax format to generate the push packets of the rich text message type and / or the markdown message type; if not, use the pre-encapsulated default syntax format to automatically generate the push packets of the rich text message type and / or the markdown message type;

[0088] In the browser plugin's parsing of the filled content, check whether the user has filled in the custom message text of other message types other than the rich text message type and the markdown message type. If so, use the user-defined message text to generate the push packets of other message types other than the rich text message type and the markdown message type; if not, use the pre-encapsulated default text to generate the push packets of other message types other than the rich text message type and the markdown message type.

[0089] S520. In the browser plugin's parsing of the filled content, check whether the user has filled in the message recipient information. If so, execute step S521; if not, execute step S522;

[0090] S522, searching for a message recipient identity identifier through the message recipient information, and assigning the message recipient identity identifier to the message recipient identity identifier in the push parameters of each message scenario;

[0091] S522, extracting the user identity in the user information, and assigning the user identity to the message recipient identity in the push parameters of each message scenario;

[0092] Among them, the message recipient identity identifier can be the message recipient ID, and the message recipient information can be the user name or other relevant information of the message recipient. When the user fills in the message recipient information, the background system interface can be called to search for the message recipient ID through the user name or other relevant information of the message recipient, and directly assign the found message recipient ID to the message recipient ID in the push parameters of each message scenario; when the user does not fill in the message recipient information, it is assumed that the user sends the message to himself, and the user ID of the user who initiates the message push request is assigned to the message recipient ID in the push parameters of each message scenario.

[0093] S530, the browser plug-in extracts the scene name of each message scene, and assigns the scene name to the message title in the push parameters of each message scene;

[0094] Among them, assigning the scene name to the message title in the push parameters of each message scene helps the user to immediately identify which scene the pushed or received message is based on.

[0095] S540: Assemble push messages constituting each message type according to the push parameters of each message scenario that have been assigned.

[0096] S600: The browser plug-in traverses all messages, and according to the push quantity of each message type, cyclically calls the push address of each message type, and pushes the push message of each message type to the message recipient.

[0097] In this embodiment, the user uses the browser plug-in to automatically search and confirm the message push address and message recipient according to the message type and push requirements, and automatically assemble the message push message and push the message, so that the user can complete the message push without having to master the complex message type syntax format writing such as rich text message type and markdown message type, thereby lowering the threshold for message push. At the same time, the technical solution of this embodiment also supports the function of pushing or deleting messages in large quantities, as well as the function of customizing message push, which can effectively improve the efficiency and quality of message push, expand the automation and intelligence level of the browser plug-in, and enhance the user experience.

[0098] Further, in one embodiment, the message push method based on a browser plugin further includes:

[0099] Use the browser to send a browser reminder notification to the user, notifying the user that the message push is complete.

[0100] In the specific implementation process, after the message push is complete, the chrome.notifications.create method provided by the Chrome browser can be used to send a browser reminder notification to the user, notifying the user that the message has been pushed successfully, which can effectively enhance the interaction ability between the browser and the user, timely feedback the message push status, facilitate the user to understand the message push progress, and improve the user experience.

[0101] Further, in one embodiment, the message push method based on a browser plugin further includes:

[0102] The browser plugin searches for all historical messages of the user according to the user information and deletes them all.

[0103] Further, in one embodiment, the message push method based on a browser plugin further includes:

[0104] The browser plugin searches for all historical messages of the user according to the user information, obtains the dates of each historical message, and deletes the historical messages on the specified date.

[0105] In the specific implementation process, a button for clearing historical messages can also be set on the browser plugin panel. The browser plugin searches for all historical messages under the user ID in the database according to the user information such as the user ID. When the user clicks the button for clearing historical messages and selects to clear all historical messages, or the browser plugin also obtains the dates of each historical message, sets a date selection box for displaying historical messages on the right side of the clear button, and the user can select to delete the historical messages on the specified date by clicking the button and checking the selection box, enabling the user to batch clear historical messages simply and quickly with one click through the browser plugin, realizing the function expansion of the browser plugin, improving the intelligent level of message push and clearing, and enhancing the user experience.

[0106] On the other hand, as Figure 3 shown, in one embodiment, a message push system based on a browser plugin is further provided, and the system includes:

[0107] A push request monitoring module 100, configured to use the browser to monitor the user's message push request;

[0108] The plug-in form filling module 200 is used to pop up a configuration form of the browser plug-in according to the message push request for the user to fill in and obtain the filled content, where the filled content includes: message recipient information, the push quantity of each message type, the push environment, and custom content;

[0109] The push address determination module 300 is used to run the browser plug-in and determine the push address of each message type according to the push environment of each message type in the filled content;

[0110] The message scenario acquisition and parameter extraction module 400 is used for the browser plug-in to call the push address of each message type, obtain the message scenario of each message type, and extract the push parameters of each message scenario;

[0111] The push message assembly module 500 is used for the browser plug-in to match the message recipient information and the custom content of each message type in the filled content with the message scenario of each message type and the push parameters of each message scenario, and assemble and construct the push message of each message type;

[0112] The message push module 600 is used for the browser plug-in to traverse all messages, and according to the push quantity of each message type, loop to call the push address of each message type, and push the push message of each message type to the message recipient.

[0113] Figure 4 The internal structure diagram of a computer device in an embodiment is shown. The computer device can specifically be a terminal or a server. As Figure 4 shown, the computer device includes a processor 700, a memory, and a network interface 800 connected through a system bus. Among them, the memory includes a non-volatile storage medium 910 and an internal memory 920. The non-volatile storage medium 910 of the computer device stores an operating system and can also store a computer program. When the computer program is executed by the processor 700, the processor 700 can implement the message push method based on the browser plug-in. The internal memory 920 can also store a computer program. When the computer program is executed by the processor 700, the processor 700 can execute the message push method based on the browser plug-in. Those skilled in the art can understand that Figure 4 the structure shown in

[0114] In one embodiment, a computer device is provided, including a memory and a processor. The memory stores a computer program. When the computer program is executed by the processor, the processor is caused to perform the following steps:

[0115] Use a browser to listen for a user's message push request;

[0116] According to the message push request, pop up a configuration form of the browser plugin for the user to fill in, and obtain the filled content, where the filled content includes: message recipient information, the push quantity of each message type, the push environment, and custom content;

[0117] The browser plugin determines the push address of each message type according to the push environment of each message type in the filled content;

[0118] The browser plugin calls the push address of each message type, obtains the message scenario of each message type, and extracts the push parameters of each message scenario;

[0119] The browser plugin matches the message recipient information and the custom content of each message type in the filled content, combines them with the message scenario of each message type, and matches them with the push parameters of each message scenario, and assembles and constructs the push message of each message type;

[0120] The browser plugin traverses all messages, and according to the push quantity of each message type, cyclically calls the push address of each message type, and pushes the push message of each message type to the message recipient.

[0121] In one embodiment, a computer-readable storage medium is provided, storing a computer program. When the computer program is executed by a processor, the processor is caused to perform the following steps:

[0122] Use a browser to listen for a user's message push request;

[0123] According to the message push request, pop up a configuration form of the browser plugin for the user to fill in, and obtain the filled content, where the filled content includes: message recipient information, the push quantity of each message type, the push environment, and custom content;

[0124] The browser plugin determines the push address of each message type according to the push environment of each message type in the filled content;

[0125] The browser plugin calls the push address of each message type, obtains the message scenario of each message type, and extracts the push parameters of each message scenario;

[0126] The browser plugin matches the message recipient information and the custom content of each message type in the filled content, combines the message scenarios of each message type, and matches them with the push parameters of each message scenario to assemble and form the push message of each message type.

[0127] The browser plugin traverses all messages and, according to the push quantity of each message type, repeatedly calls the push address of each message type to push the push message of each message type to the message recipient.

[0128] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The program can be stored in a non-volatile computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, storage, database, or other medium used in the various embodiments provided in the present application can include non-volatile and / or volatile memories. Non-volatile memories can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memories can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0129] The technical features of the above embodiments can be combined arbitrarily. For the sake of concise description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope recorded in this specification.

[0130] The above-described embodiments merely represent several implementation manners of the present application. Their descriptions are relatively specific and detailed, but they should not be construed as limiting the patent scope of the present application. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can still be made, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application should be subject to the appended claims.

Claims

1. A message push method based on a browser plugin, characterized in that The method includes: Using a browser to listen for a user's message push request; According to the message push request, pop up a configuration form of the browser plugin for the user to fill in, and obtain the filled content, where the filled content includes: message recipient information, the push quantity of each message type, the push environment, and custom content; The browser plugin determines the push address of each message type according to the push environment of each message type in the filled content; The browser plugin calls the push address of each message type, obtains the message scenario of each message type, and extracts the push parameters of each message scenario; The browser plugin matches the message recipient information and the custom content of each message type in the filled content with the message scenario of each message type, and matches them with the push parameters of each message scenario, and assembles and constructs the push message of each message type; The browser plugin traverses all messages, and according to the push quantity of each message type, repeatedly calls the push address of each message type, and pushes the push message of each message type to the message recipient.

2. The message pushing method based on a browser plug-in according to claim 1, wherein After using the browser to listen for the user's message push request, it further includes: Saving user information; The push parameters of each message scenario include: message recipient identity identifier, message title, message text; The browser plugin matches the message recipient information and the custom content of each message type in the filled content with the message scenario of each message type, and matches them with the push parameters of each message scenario, and assembles and constructs the push message of each message type, specifically including: The browser plugin parses whether the custom content of each message type in the filled content is filled in by the user. If so, it assigns the custom content of each message type in the filled content to the message text in the push parameters of each message scenario. If not, it assigns the preset default content to the message text in the push parameters of each message scenario; The browser plugin parses whether the message recipient information in the filled content is filled in by the user. If so, it finds the message recipient identity identifier through the message recipient information, and assigns the message recipient identity identifier to the message recipient identity identifier in the push parameters of each message scenario. If not, it extracts the user identity identifier in the user information, and assigns the user identity identifier to the message recipient identity identifier in the push parameters of each message scenario; The browser plugin extracts the scenario name of each message scenario, and assigns the scenario name to the message title in the push parameters of each message scenario; According to the push parameters of each message scenario after the assignment is completed, assemble and construct the push message of each message type.

3. The message push method based on a browser plug-in according to claim 2, characterized in that The custom content of each message type includes: the custom syntax format of the rich text message type and the markdown message type, and the custom message text of other message types other than the rich text message type and the markdown message type; When the browser plugin parses the filled content, it checks whether the user has filled in the custom content for each message type. If so, it assigns the custom content of each message type in the filled content to the message text in the push parameters for each message scenario. If not, it assigns the preset default content to the message text in the push parameters for each message scenario. Specifically, it includes: When the browser plugin parses the filled content, it checks whether the user has filled in the custom syntax format for the rich text message type and / or the markdown message type. If so, it uses the user-defined syntax format to generate the push message for the rich text message type and / or the markdown message type. If not, it uses the pre-encapsulated default syntax format to automatically generate the push message for the rich text message type and / or the markdown message type; When the browser plugin parses the filled content, it checks whether the user has filled in the custom message text for message types other than the rich text message type and the markdown message type. If so, it uses the user-defined message text to generate the push message for message types other than the rich text message type and the markdown message type. If not, it uses the pre-encapsulated default text to generate the push message for message types other than the rich text message type and the markdown message type.

4. The message push method based on a browser plug-in according to claim 1, wherein The push quantity of each message type in the filled content specifically includes: the push rounds of each message type and the push quantity of each message type in one push round.

5. A message pushing method based on a browser plug-in according to claim 1, characterized in that, The method further includes: Using the browser to send a browser reminder notification to the user to notify that the message push is completed.

6. The message push method based on a browser plugin according to claim 2, wherein The method further includes: The browser plugin searches for all historical messages of the user according to the user information and deletes them all.

7. A message pushing method based on a browser plug-in according to claim 2, characterized in that, The method further includes: The browser plugin searches for all historical messages of the user according to the user information, obtains the dates of each historical message, and deletes the historical messages on the specified date.

8. A message push system based on a browser plugin, characterized in that, The system includes: A push request monitoring module for using the browser to monitor the user's message push request; A plugin form filling module for popping up a configuration form of the browser plugin according to the message push request for the user to fill in and obtaining the filled content, where the filled content includes: message recipient information, the push quantity of each message type, the push environment, and custom content; A push address determination module for running the browser plugin and determining the push address of each message type according to the push environment of each message type in the filled content; A message scenario acquisition and parameter extraction module for the browser plugin to call the push address of each message type, obtain the message scenario of each message type, and extract the push parameters of each message scenario; A push message assembly module for the browser plugin to match the message recipient information and the custom content of each message type in the filled content with the message scenario of each message type and the push parameters of each message scenario, and assemble and construct the push message of each message type; The message push module is used for the browser plug-in to traverse all messages, and according to the push quantity of each message type, circularly call the push address of each message type, and push the push message of each message type to the message recipient.

9. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, the processor is caused to execute the steps of the method according to any one of claims 1 to 7.

10. A computer device, comprising a memory and a processor, the memory storing a computer program, characterized in that, When the computer program is executed by the processor, the processor is caused to execute the steps of the method according to any one of claims 1 to 7.

Images