Message pushing method and device, computer equipment, readable storage medium and product

Abstract

The invention relates to the technical field of big data, and discloses a message pushing method and device, computer equipment, a readable storage medium and a product. The method comprises the steps of obtaining message content and a message identifier of a to-be-pushed message; based on the message identifier, carrying out push strategy matching to obtain a message push strategy matched with the to-be-pushed message, the message push strategy comprising a message push template and a message push rule; filling the message pushing template with the message content to obtain a target message; under the condition that the message pushing template is configured with a message processing mechanism, based on message processing logic corresponding to the message processing mechanism, performing service logic processing on the target message to obtain a pushed message; and pushing the push message according to the message push rule. By adopting the method, the message pushing flexibility can be improved.

Description

Technical Field

[0001] This application relates to the field of big data technology, and in particular to a message push method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Technology

[0002] With the rapid development of big data and the deepening of enterprise informatization, message push mechanisms have become a key link supporting business operations, widely used in scenarios such as notifications, status synchronization, and monitoring alarms. Against this backdrop, how to achieve efficient and accurate message push has become a pressing issue that needs to be addressed.

[0003] In traditional technologies, once a user subscribes to messages, they can only receive messages based on pre-defined content. This limited approach has the following drawbacks: first, it cannot support customized push notifications, making it difficult to meet users' personalized message needs; second, it does not consider actual push scenarios, resulting in push messages that are not compatible with the specific context. Therefore, current message push methods suffer from low flexibility. Summary of the Invention

[0004] Therefore, it is necessary to provide a message push method, apparatus, computer device, computer-readable storage medium, and computer program product that can improve the flexibility of message push in order to address the above-mentioned technical problems.

[0005] Firstly, this application provides a message push method, including:

[0006] Get the message content and message identifier of the message to be pushed;

[0007] Based on the message identifier, push strategy matching is performed to obtain a message push strategy that matches the message to be pushed. The message push strategy includes a message push template and message push rules.

[0008] Fill the message push template with the message content to get the target message;

[0009] When the message push template is configured with a message processing mechanism, the target message is processed by business logic based on the message processing logic corresponding to the message processing mechanism to obtain the push message;

[0010] Push messages will be sent according to the message push rules.

[0011] In one embodiment, the message push method further includes:

[0012] Parse the template configuration information of the message push template;

[0013] In the case that the template configuration information contains a configuration field for the message processing mechanism, it is determined that the message push template is configured with the message processing mechanism;

[0014] The message processing logic matching the field content of the configuration field is queried.

[0015] In one embodiment, based on the message identifier, push strategy matching is performed to obtain a message push strategy matching the to-be-pushed message, which includes:

[0016] An initial push template matching the message identifier is determined;

[0017] In response to a configuration event for the initial push template, configuration parameters carried by the configuration event are obtained;

[0018] According to the configuration parameters, the initial push template is updated to obtain the message push template.

[0019] In one embodiment, determining the initial push template matching the message identifier includes:

[0020] A basic push template matching the message identifier is determined;

[0021] According to the template identifier of the basic push template, inheritance chain query is performed to obtain a template inheritance chain of the basic push template;

[0022] Template configuration parameters of each parent template in the template inheritance chain are recursively combined to obtain the initial push template.

[0023] In one embodiment, based on the message identifier, push strategy matching is performed to obtain a message push strategy matching the to-be-pushed message, which further includes:

[0024] Based on the message identifier, push rule matching is performed to obtain at least one candidate push rule matching the to-be-pushed message;

[0025] A message push end of the to-be-pushed message is determined;

[0026] From the plurality of candidate push rules, a message push rule matching the message push end is selected.

[0027] In one embodiment, the message push method further includes:

[0028] In the case that the to-be-pushed message has an associated resource push demand, description information of the to-be-pushed message is obtained;

[0029] According to the description information, an associated resource of the to-be-pushed message is constructed;

[0030] The pushed message is pushed according to the message push rule, which includes:

[0031] The push message and the associated resource are pushed according to the message push rule.

[0032] In a second aspect, the present application further provides a message push device, comprising:

[0033] An information acquisition module is configured to acquire message content and a message identifier of a message to be pushed.

[0034] A push strategy matching module is configured to perform push strategy matching based on the message identifier, to obtain a message push strategy matched with the message to be pushed, wherein the message push strategy comprises a message push template and a message push rule.

[0035] A template filling module is configured to fill the message push template with the message content, to obtain a target message.

[0036] A message processing module is configured to, in a case where the message push template is configured with a message processing mechanism, perform business logic processing on the target message based on message processing logic corresponding to the message processing mechanism, to obtain a push message.

[0037] A message push module is configured to push the push message according to the message push rule.

[0038] In one of the embodiments, the message push device further comprises:

[0039] An analysis module is configured to analyze template configuration information of the message push template.

[0040] A mechanism determination module is configured to, in a case where the template configuration information contains a configuration field for the message processing mechanism, determine that the message push template is configured with the message processing mechanism.

[0041] A logic query module is configured to query message processing logic matched with field content of the configuration field.

[0042] In one of the embodiments, the push strategy matching module further comprises:

[0043] A template determination unit is configured to determine an initial push template matched with the message identifier.

[0044] A parameter acquisition unit is configured to, in response to a configuration event for the initial push template, acquire configuration parameters carried by the configuration event.

[0045] A template updating unit is configured to update the initial push template according to the configuration parameters, to obtain the message push template.

[0046] In one of the embodiments, the template determination unit is further configured to:

[0047] determine a basic push template matched with the message identifier.

[0048] According to the template identifier of the basic push template, the inheritance chain query is performed to obtain a template inheritance chain of the basic push template;

[0049] The template configuration parameters of each parent template in the template inheritance chain are subjected to parameter recursive merging processing to obtain an initial push template.

[0050] In one of the embodiments, the push strategy matching module further comprises:

[0051] The rule matching unit is configured to perform push rule matching based on the message identifier to obtain at least one candidate push rule matched with the to-be-pushed message;

[0052] The push end determination unit is configured to determine a message push end of the to-be-pushed message;

[0053] The rule screening unit is configured to screen a message push rule matched with the message push end from the plurality of candidate push rules.

[0054] In one of the embodiments, the message push device further comprises:

[0055] The description information acquisition module is configured to acquire description information of the to-be-pushed message in a case where the to-be-pushed message has an associated resource push demand;

[0056] The associated resource construction module is configured to construct an associated resource of the to-be-pushed message according to the description information;

[0057] The message push module is further configured to push the push message and the associated resource according to the message push rule.

[0058] In a third aspect, the present application further provides a computer device comprising a memory and a processor, the memory stores a computer program, and the processor implements the following steps when executing the computer program:

[0059] Acquire the message content and the message identifier of the to-be-pushed message;

[0060] Perform push strategy matching based on the message identifier to obtain a message push strategy matched with the to-be-pushed message, wherein the message push strategy comprises a message push template and a message push rule;

[0061] Fill the message push template with the message content to obtain a target message;

[0062] In a case where the message push template is configured with a message processing mechanism, perform business logic processing on the target message based on a message processing logic corresponding to the message processing mechanism to obtain a push message;

[0063] Push the push message according to the message push rule.

[0064] In a fourth aspect, the present application also provides a computer readable storage medium, having stored thereon a computer program, which when executed by a processor implements the following steps:

[0065] obtaining message content and a message identifier of a message to be pushed;

[0066] performing push strategy matching based on the message identifier to obtain a message push strategy matched with the message to be pushed, wherein the message push strategy comprises a message push template and a message push rule;

[0067] filling the message push template with the message content to obtain a target message;

[0068] in a case where the message push template is configured with a message processing mechanism, performing business logic processing on the target message based on message processing logic corresponding to the message processing mechanism to obtain a push message;

[0069] pushing the push message according to the message push rule.

[0070] In a fifth aspect, the present application also provides a computer program product comprising a computer program, which when executed by a processor implements the following steps:

[0071] obtaining message content and a message identifier of a message to be pushed;

[0072] performing push strategy matching based on the message identifier to obtain a message push strategy matched with the message to be pushed, wherein the message push strategy comprises a message push template and a message push rule;

[0073] filling the message push template with the message content to obtain a target message;

[0074] in a case where the message push template is configured with a message processing mechanism, performing business logic processing on the target message based on message processing logic corresponding to the message processing mechanism to obtain a push message;

[0075] pushing the push message according to the message push rule.

[0076] The message pushing method, device, computer device, computer readable storage medium and computer program product can obtain the message content and message identifier of the message to be pushed, match a corresponding pushing strategy based on the message identifier, the strategy includes a message pushing template and a message pushing rule, the pushing strategy matching mechanism can dynamically adapt the most suitable pushing mode according to the message characteristics, and the flexibility of message pushing is improved. Then, the message content is used to fill the message pushing template, a target message is generated, and in the case that the message pushing template is configured with a message processing mechanism, the message processing logic corresponding to the message processing mechanism is called to perform business logic processing on the target message, and a final pushing message is formed. Finally, the message pushing is completed according to the message pushing rule. In this way, the message processing mechanism is introduced, and the intelligent pushing strategy matching is combined, the decoupling of the message content and the business logic is realized, the message pushing can be flexibly adapted to diversified business scenarios and dynamically changed processing requirements, and the flexibility, accuracy and business adaptability of the message pushing are significantly improved. BRIEF DESCRIPTION OF DRAWINGS

[0077] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related art, the drawings needed to be used in the description of the embodiments of the present application or the related art will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other related drawings can be obtained by those skilled in the art without creative labor.

[0078] Figure 1 An application environment diagram of the message pushing method in an embodiment;

[0079] Figure 2 A flowchart of the message pushing method in an embodiment;

[0080] Figure 3 A query flowchart of the message processing logic in an embodiment;

[0081] Figure 4 A flowchart of the message pushing template matching in an embodiment;

[0082] Figure 5 A flowchart of the pushing template inheritance in an embodiment;

[0083] Figure 6 A flowchart of the message pushing rule matching in an embodiment;

[0084] Figure 7 A flowchart of the associated resource generation in an embodiment;

[0085] Figure 8Fig. 1 is a flowchart of a message pushing method according to an embodiment of the present application;

[0086] Figure 9 Fig. 2 is a block diagram of a message pushing device according to an embodiment of the present application;

[0087] Figure 10 Fig. 3 is a diagram of an internal structure of a computer device according to an embodiment of the present application. DETAILED DESCRIPTION

[0088] In order to make the objects, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and should not be used to limit the present application. It should be noted that in the embodiments of the present application, some software, groups, models and other industry existing solutions may be mentioned, which should be considered as exemplary, and the purpose is only to illustrate the feasibility of the technical solution of the present application, but does not mean that the applicant has or will necessarily use the solution.

[0089] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with relevant regulations. The acquisition, storage, use, processing and other data in the technical solution of the present application comply with the relevant regulations of national laws and regulations.

[0090] The terms "first", "second", and the like used in the present application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "include" and "have" and any variations thereof used in the present application are intended to cover non-exclusive inclusion. The term "a plurality of" used in the present application means two or more. The term "and / or" used in the present application means one of the solutions or any combination of a plurality of solutions.

[0091] The message pushing method provided by the embodiments of the present application can be applied to, for example, Figure 1The application environment shown. Among them, the terminal 102 communicates with the server 104 through the network. The data storage system can store the data required by the server 104 to process. The data storage system can be integrated on the server 104, or placed on the cloud or other network servers. The terminal 102 can be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, unmanned aerial vehicles, low-altitude aircraft, Internet of Things devices, and portable wearable devices. The Internet of Things device can be a smart speaker, a smart TV, a smart car device, a projection device, etc. The portable wearable device can be a smart watch, a smart bracelet, a head-mounted device, etc. The server 104 can be a standalone physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services.

[0092] Specifically, the server 104 obtains the message content and the message identifier of the to-be-pushed message; based on the message identifier, performs push strategy matching to obtain a message push strategy matched with the to-be-pushed message, wherein the message push strategy includes a message push template and a message push rule; fills the message push template with the message content to obtain a target message; in the case that the message push template is configured with a message processing mechanism, performs business logic processing on the target message based on the message processing logic corresponding to the message processing mechanism to obtain a push message; and the server 104 pushes the push message to the terminal 102 according to the message push rule.

[0093] In an exemplary embodiment, as shown in Figure 2 , a message push method is provided, which can be performed by the terminal 102 or the server 104 in Figure 1 alone, or by the terminal 102 and the server 104 in cooperation. The following method is applied to the server 104 in Figure 1 for example, including the following steps S202 to S210, wherein:

[0094] Step S202, obtaining the message content and the message identifier of the to-be-pushed message.

[0095] The to-be-pushed message refers to a message that has been generated but not yet pushed, and is usually included in a to-be-pushed message list or a to-be-pushed message queue. The message content refers to a specific data entity to be pushed, and is usually structured or semi-structured business data, such as at least one of a message generation time, a number of a user object creating the message, a dynamic parameter value, a message category, a message data value, a message description, a message title, and a priority. The message generation time refers to a timestamp when the to-be-pushed message is created. The number of the user object creating the message refers to a unique identity of a user creating the to-be-pushed message. The dynamic parameter value refers to variable data that needs to be filled into a push template. The message category refers to a category of the to-be-pushed message, such as a notification message or an alarm message. The message data value refers to structured business data related to the to-be-pushed message, including complete context information. The message description refers to an information description of the to-be-pushed message, such as a use and an attribute. The message title refers to a brief summary or a subject identifier of the message. The priority refers to an emergency degree identifier of the message in push scheduling, used to determine the order of message processing and resource allocation strategies. The more urgent the message is, the more preferentially the message is processed and pushed, and the higher network bandwidth resources and powerful computing resources are allocated to ensure that the high-priority message is quickly and reliably pushed. These data items collectively constitute a complete information system for message pushing, including content data required for business display and control parameters required for the pushing process. In actual applications, these fields can be flexibly combined and extended according to specific business needs, for example, adding a region identifier to support multi-language pushing, or adding an expiration time field to realize automatic message invalidation. Through such structured data design, the system can achieve fine-grained management and intelligent control of message pushing.

[0096] The message identifier is a globally unique identifier of the to-be-pushed message, such as a message ID ( ‌Identifier, Identifier). Of course, other parameters that can represent the global uniqueness of the to-be-pushed message can also be used as the message identifier, and the present embodiment does not limit this. In the present embodiment, the message identifier can be one identifier or a combination of multiple identifiers. The message identifier can be used to associate a predefined push configuration, and is usually assigned a corresponding message identifier at the time of message generation.

[0097] For example, the server can query at least one to-be-pushed message, and the message content and the message identifier corresponding to the message, by listening to the to-be-pushed message queue or polling the to-be-pushed list. In the present embodiment, compression and encryption of the message content are also supported to improve the efficiency and security of message transmission. In addition, multi-data source access is also supported, including message middleware, database logs, and API (Application Programming Interface, Application Programming Interface).

[0098] Step S204, based on the message identifier, a push strategy matching is performed to obtain a message push strategy matched with the to-be-pushed message, wherein the message push strategy comprises a message push template and a message push rule.

[0099] The message push strategy defines a push manner of the to-be-pushed message, and comprises a message push template determining a message display form and a message push rule defining a push channel, a push time and the like.

[0100] For example, the server can previously establish an association table between the message identifier and the message push template, so that after obtaining the message identifier of the to-be-pushed message, the server can query the table to obtain the message push template matched with the to-be-pushed message. In addition, the template number can also be directly written in the message content, and the server can directly search in the template library based on the template number to determine the message push template matched with the to-be-pushed message. Similarly, the server can also previously establish an association table between the message identifier and the message push rule, so that after obtaining the message identifier of the to-be-pushed message, the server can query the table to obtain the message push rule matched with the to-be-pushed message. In addition, the message content can also directly write the fields related to the message push rule, such as a message push end description, a push manner description, a push time, a communication protocol specification at the push time, a transmission configuration and the like, and the server can directly know the message push rule of the to-be-pushed message based on these fields.

[0101] In some embodiments, when multiple message push strategies are matched according to the message identifier, the server can simulate the message push effect of each message push strategy, and in the case that the message push effect reaches the expected effect, it is used as the final message push strategy. The multiple message push strategies can also be fed back to the front-end interface for selection by the user. The specific determination can be made according to the actual situation, and the present embodiment does not limit this.

[0102] Step S206, the message content is filled into the message push template to obtain a target message.

[0103] The target message refers to the message generated after the message content is filled into the message push template.

[0104] Exemplarily, after obtaining the message content of the to-be-pushed message, the server can inject the message data value, the dynamic parameter value, the message title, etc. in the message content into the corresponding field positions in the template through a template engine such as FreeMarker, so as to generate a target message containing the message pushing template and the complete message content. In this process, data format conversion and verification of the message content are supported, and after being converted into a data format suitable for the message pushing template and passing the data specification verification, the message pushing template can be filled. After the filling is completed, real-time preview of the target message is also supported.

[0105] Step S208, in the case where the message pushing template is configured with a message processing mechanism, performing business logic processing on the target message based on the message processing logic corresponding to the message processing mechanism, to obtain a pushing message.

[0106] The message processing mechanism is a pre-configured business processing logic. The message processing logic is a code unit for specifically executing the message processing mechanism. The pushing message is a message generated after business logic processing.

[0107] Exemplarily, the server also detects whether the message pushing template is configured with a message processing mechanism. If the message processing mechanism is configured, the message processing logic corresponding to the message processing mechanism is called to perform business logic processing, such as data desensitization, specific data format conversion, etc., on the target message, so as to obtain the final pushing message. If the message pushing template is not configured with the message processing mechanism, no additional business logic processing is required, and the target message is directly taken as the final pushing message.

[0108] Step S210, pushing the pushing message according to the message pushing rule.

[0109] Exemplarily, after obtaining the pushing message, the message can be pushed to the corresponding pushing end according to the message pushing rule matched previously, and the pushing state and the pushing result are recorded for subsequent tracking and analysis. The pushing state and the pushing result can be recorded in a message log table, which can record at least one of the server address, the message ID, the message pushing state, the message content, the message pushing end time, the message pushing start time, etc. This embodiment also supports a message concurrent pushing mechanism, that is, the server sets independent concurrent control strategies for different message types and pushing channels by dynamically configuring concurrent task parameters.

[0110] In this embodiment, by obtaining the message content and the message identifier of the to-be-pushed message, the corresponding push strategy is matched based on the message identifier, the strategy including a message push template and a message push rule, and the push strategy matching mechanism can dynamically adapt the most suitable push mode according to the message characteristics, which is beneficial to improve the flexibility of message pushing. Subsequently, the message content is used to fill the message push template, a target message is generated, and in the case that the message push template is configured with a message processing mechanism, the message processing logic corresponding to the message processing mechanism is called to perform business logic processing on the target message, thereby forming a final push message. Finally, the message is pushed according to the message push rule. In this way, by introducing a configurable and extensible message processing mechanism and combining intelligent push strategy matching, the decoupling of message content and business logic is realized, so that the message pushing can flexibly adapt to diversified business scenarios and dynamically changing processing requirements, and the flexibility, accuracy and business adaptability of message pushing are significantly improved.

[0111] In one exemplary embodiment, as shown in Figure 3 The message pushing method further includes the following steps S302 to S306, wherein:

[0112] In step S302, template configuration information of the message push template is parsed.

[0113] The template configuration information is a metadata set of the message push template, which can include but is not limited to template creation time, database access identifier, table name of dependent data table, message content field, message description field, data format rule, message title field, preview data, preview result, template description, template type, etc. The template creation time refers to the creation timestamp of the message push template; the database access identifier refers to the connection identifier of the template accessing the source database; the table name of the dependent data table refers to the source data table name on which the template depends; the message content field refers to the field to be filled with the message content; the message description field refers to the field to be filled with the message description; the data format rule refers to the data format rule supported by the template; the message title field refers to the field to be filled with the message title; the preview data refers to the data used for template preview, which can be used to verify the template display effect; the preview result is the preview template generated using the preview data; the template description is the description information of the message push template such as name, purpose, etc.; and the template type refers to the type of the message push template such as HTML template, text template, file template, etc. In actual application, these fields can be flexibly combined and extended according to specific business requirements, and the specific content of the template parameter information is not limited in this embodiment.

[0114] For example, after the server matches the message push template, the configuration information of the message push template can be read accordingly, so as to subsequently judge whether the message push template is configured with a field for the message processing mechanism based on the configuration information.

[0115] Step S304, in the case that the configuration field for the message processing mechanism is contained in the template configuration information, it is determined that the message push template is configured with the message processing mechanism.

[0116] The configuration field refers to a specific field for defining the message processing mechanism, such as a handler processor field or other processor field, which is not limited in the embodiment.

[0117] For example, after the server reads the configuration information of the message push template, it can query whether the configuration field for the message processing mechanism exists in the configuration information. If it exists, it further detects whether the field content of the configuration field is empty and whether the field content is valid. If the field content is not empty and valid, it is considered that the message push template is configured with the message processing mechanism. Conversely, if the configuration field does not exist, or the field content is empty and / or the field content is invalid, it is considered that the message push template is not configured with the message processing mechanism.

[0118] In some embodiments, the server can also determine whether the message push template is configured with the message processing mechanism by checking the predefined annotation mark or querying the independent processor registry. Specifically, the server can scan the class file corresponding to the message push template to detect whether the annotation mark for the message processing mechanism exists in the class file. If it exists, it is determined that the message push template is configured with the message processing mechanism. If it does not exist, it is considered that the message push template is not configured with the message processing mechanism. When the processor registry method is used, the server can maintain an independent processor registry center which stores the mapping relationship between the template number and the corresponding processor implementation in the form of key-value pair. The server queries the registry to find whether there is a registered processor configuration according to the number of the current message push template. Of course, other methods can also be selected to detect whether the message push template is configured with the message processing mechanism in actual application, which is not limited in the embodiment.

[0119] In some embodiments, multi-processor configuration is also supported, and multiple processors can be specified in the form of comma separation or array. In addition, the processor can also be verified, that is, the existence, interface compatibility and instance feasibility of the processor are verified to prevent configuration errors.

[0120] Step S306, querying the message processing logic matched with the field content of the configuration field.

[0121] Exemplarily, in the case that the field content of the configuration field is not empty and valid, the server can perform processor lookup according to the field content, and a hierarchical lookup strategy can be adopted, that is, first searching in the local processor cache, and then dynamically loading from the processor warehouse when not hit. After searching for the corresponding processor, the server can verify the interface compatibility and instance feasibility of the processor to ensure that the processing logic of the processor can be correctly executed. After verification, the message processing logic of the processor can be called.

[0122] In this embodiment, by analyzing the template configuration information and detecting the message processing mechanism configuration field therein, accurate identification of the message processing logic is achieved, which is conducive to improving the accuracy and flexibility of subsequent message processing, and further improving the accuracy and flexibility of message pushing.

[0123] In an exemplary embodiment, as shown in Figure 4 Based on the message identifier, the push strategy matching is performed to obtain the message pushing strategy matched with the to-be-pushed message, including the following steps S402 to S406, wherein:

[0124] Step S402, determining an initial pushing template matched with the message identifier.

[0125] The initial pushing template refers to the initial state message pushing template matched with the message identifier or the to-be-pushed message.

[0126] Exemplarily, after the server obtains the message identifier of the to-be-pushed message, the template matching can be performed based on the message identifier, so as to obtain the message pushing template matched with the message identifier, and at this time, the template is in an initial state.

[0127] Step S404, in response to the configuration event of the initial pushing template, obtaining the configuration parameters carried by the configuration event.

[0128] The configuration event is a trigger event for configuring the initial pushing template. The configuration parameters are specific template adjustment parameters carried in the configuration event, including at least one of template content, style rule, business logic, etc.

[0129] Exemplarily, the server captures the configuration event for the initial pushing template through the event monitor, and analyzes the configuration parameters carried by the event. In this process, the server can verify the validity of the configuration parameters to ensure the compliance of the template configuration adjustment, in addition, the user object triggering the configuration event can be checked for permission to avoid unauthorized template configuration adjustment, so as to ensure the security of the template configuration adjustment. This embodiment also supports the configuration rollback function, that is, quickly recovering to any historical template version.

[0130] Step S406, updating the initial push template according to the configuration parameter to obtain a message push template.

[0131] For example, after the configuration parameter is parsed, the server can update the initial push template based on the configuration parameter. The update can be incremental, i.e., modifying or replacing a specific part of the template, such as updating dynamic parameters, adjusting local styles, or supplementing missing components, while keeping the main structure of the template unchanged. The update can also be full, i.e., using a new template definition to completely cover all contents of the initial template, including template structure, style rules, and other core elements. The specific selection can be made according to actual conditions. After the update is completed, syntax checking can be performed on the template to ensure that the template meets the syntax specification, and / or dependency verification can be performed to verify the accessibility of external resources or data sources referenced by the target, and other operations. After passing the above detection, the final message push template can be generated.

[0132] In this embodiment, by dynamically responding to configuration events and updating the initial push template based on the configuration parameter in real time, flexible configuration of the message template is achieved, and the final message push target is more in line with actual business requirements.

[0133] In one exemplary embodiment, as shown in FIG. 5, an initial push template matching the message identifier is determined, including the following steps S502 to S506, wherein: Figure 5

[0134] Step S502, determining a basic push template matching the message identifier.

[0135] The basic push template refers to the original template matching the message identifier or the message to be pushed. It can be understood that the basic push template is the original template entity directly matched by the message identifier, which serves as an entry point of the template inheritance system, while the initial push template is a complete and usable template generated by recursively merging all parent template parameters of the basic push template in the inheritance chain. The two constitute a corresponding relationship between static configuration and dynamic generation results in the inheritance mechanism.

[0136] For example, the server performs template matching based on the message identifier to obtain the original template matching the message identifier, i.e., the basic push template.

[0137] Step S504, performing inheritance chain query according to the template identifier of the basic push template to obtain the template inheritance chain of the basic push template.

[0138] The template inheritance chain refers to the inheritance path of the basic push template, including all levels of parent templates of the basic push template.

[0139] ​Exemplarily, after matching to the base push template, the server can query the inheritance relationship graph by template number, and traverse the inheritance tree by using a depth-first or breadth-first algorithm, so as to construct a complete template inheritance chain containing parent templates of the base push template at all levels.

[0140] In step S506, the template configuration parameters of each parent template in the template inheritance chain are subjected to parameter recursive merging processing, to obtain an initial push template.

[0141] The parameter recursive merging refers to a process of merging the template configuration parameters of each parent template layer by layer.

[0142] Exemplarily, after the template inheritance chain is constructed, the server can develop from the root node of the inheritance chain, and merge the configuration parameters of parent templates at each level layer by layer. In this process, the parameter covering rule that the parameters of a child template are prior to the parameters of a parent template can be followed. After the merging is completed, the initial push template can be obtained.

[0143] In this embodiment, by establishing the template inheritance chain and recursively merging the configuration parameters of templates at each layer in the chain, effective reuse and flexible combination of template resources are realized, and the maintainability and configuration efficiency of template management are significantly improved.

[0144] In an exemplary embodiment, as shown in FIG. 6, based on the message identifier, push strategy matching is performed to obtain a message push strategy matched with the to-be-pushed message, and the following steps S602 to S606 are further included, wherein: Figure 6

[0145] In step S602, based on the message identifier, push rule matching is performed to obtain at least one candidate push rule matched with the to-be-pushed message.

[0146] The candidate push rule refers to a plurality of push rules obtained by preliminary matching, which constitute an optional set for subsequent fine selection.

[0147] Exemplarily, after obtaining the message identifier of the to-be-pushed message, the server can perform push rule matching based on the message identifier to obtain at least one push rule matched with the message, and the push rule defines push time, push channel, push form and other information.

[0148] ​In some embodiments, the push channel can include, but is not limited to, at least one of mail push, short message push, application push, etc., and the push form can include, but is not limited to, at least one of file push, text push, picture push, etc. When the file push form is adopted, the core elements such as the file name, the file content body and the push end information need to be generated in sequence. The file name supports configuration through a template containing specific placeholders, for example, in the form of "@field name@", the field name can be a date field name, a serial number field name, etc. The server will automatically identify and replace these placeholders when performing the push. The date field name will be replaced with the current date, and the serial number field name will be replaced with an incremental serial number automatically generated according to the count of the pushed files.

[0149] Step S604, determining the message push end of the to-be-pushed message.

[0150] The message push end refers to the final recipient of the message, which can be a specific application component, a business service or a user terminal, and the specific embodiment does not make any limitation.

[0151] For example, the server can parse the message push end description in the message content, and the message push end description records the push end identifier. Based on the push end identifier, the server can query the corresponding message push end. In this process, the server can detect the message receiving capability of the message push end, and perform message push if it is determined that the message push end has the message receiving capability. The detection content can include, but is not limited to, at least one of the running state, memory, response capability, etc. of the message push end.

[0152] Step S606, screening the message push rule matched with the message push end from the multiple candidate push rules.

[0153] For example, after determining the multiple candidate push rules, the server can analyze the matching degree between the characteristic parameters of the message push end such as protocol support, processing capability, network status, etc. and the technical requirements of the candidate push rules, and select the candidate push rule with the highest matching degree as the final message push rule.

[0154] In this embodiment, by matching multiple candidate push rules based on the message identifier and accurately screening in combination with the characteristics of the message push end, the optimal adaptation of the push rule to the push end is achieved, and the accuracy of message push in different push scenarios is effectively improved.

[0155] In an exemplary embodiment, as shown in Figure 7 The message push method further includes the following steps S702 to S704.

[0156] Step S702, acquiring the description information of the to-be-pushed message if the to-be-pushed message has an associated resource push demand.

[0157] The associated resource pushing requirement refers to a requirement of synchronously pushing an auxiliary resource related to the message in addition to the message to be pushed. The description information refers to a data set for describing the basic attributes of the message to be pushed, and can include at least one of a file name, a file path, a file content body, a generation timestamp of a message file corresponding to the message to be pushed, and the like.

[0158] For example, the server can detect, before pushing, whether the message to be pushed has an associated resource pushing requirement by parsing the requirement identifier in the message content, that is, whether an auxiliary resource related to the message to be pushed, such as an attachment corresponding to the message, needs to be synchronously pushed in addition to the message to be pushed. If the requirement identifier is not empty or the identifier is an identifier indicating that the message to be pushed has an associated resource pushing requirement, the description information of the message to be pushed is obtained for subsequent construction of the associated resource. If the requirement identifier is empty or the identifier is not an identifier indicating that the message to be pushed has an associated resource pushing requirement, the generated push message can be directly pushed.

[0159] In step S704, the associated resource of the message to be pushed is constructed according to the description information.

[0160] The associated resource refers to an auxiliary file or data structure related to the message to be pushed.

[0161] For example, after obtaining the description information of the message file corresponding to the message to be pushed, the description information can be used to generate the corresponding associated resource, such as a metadata attachment.

[0162] In some embodiments, the push message is pushed according to the message pushing rule, including: pushing the push message and the associated resource according to the message pushing rule.

[0163] For example, after the associated resource is generated, the push message and the associated resource can be pushed together according to the message pushing rule.

[0164] In this embodiment, by automatically detecting the associated resource requirement when pushing the main message and dynamically constructing the associated resource based on the message description information, the collaborative pushing of the message and the auxiliary content is realized, and the completeness and business adaptability of the message pushing are effectively enhanced.

[0165] In one specific embodiment, as shown in Figure 8 the message pushing method includes the following steps:

[0166] S1, reading the message content and the message ID of the message to be pushed;

[0167] S2, match the message push template based on the message ID, wherein the message push template is obtained through template inheritance;

[0168] S3, fill the message content into the message push template through the FreeMarker engine to obtain a target message;

[0169] S4, detect whether the message push template is configured with a message processing mechanism, if yes, execute step S5, and if not, execute step S6;

[0170] S5, perform business logic processing on the target message based on the message processing logic corresponding to the message processing mechanism to obtain a push message;

[0171] S6, match the message push rule based on the message ID;

[0172] S7, detect whether the to-be-pushed message has an associated resource push demand, if yes, execute step S8, and if not, execute step S9;

[0173] S8, push the push message according to the message push rule;

[0174] S9, push the push message and the associated resource according to the message push rule.

[0175] In this embodiment, the message content and the message identifier of the to-be-pushed message are obtained, and the corresponding push strategy is matched based on the message identifier, the strategy including a message push template and a message push rule. The push strategy matching mechanism can dynamically adapt the most suitable push mode according to the message characteristics, which is conducive to improving the flexibility of message push. Subsequently, the message push template is filled with the message content to generate a target message, and in the case that the message push template is configured with a message processing mechanism, the message processing logic corresponding to the message processing mechanism is called to perform business logic processing on the target message to form a final push message. Finally, the message push is completed according to the message push rule. In this way, this embodiment introduces a configurable and extensible message processing mechanism and combines intelligent push strategy matching to realize the decoupling of message content and business logic, so that the message push can flexibly adapt to diversified business scenarios and dynamically changing processing requirements, significantly improving the flexibility, accuracy and business adaptability of message push.

[0176] It should be understood that although each step in the flowchart involved in the above-described embodiments is shown in sequence according to the direction of the arrow, these steps are not necessarily executed in the order indicated by the arrow. Unless otherwise specified herein, the execution of these steps is not strictly limited in sequence, and these steps can be executed in other orders. Moreover, at least some of the steps in the flowchart involved in the above-described embodiments can include multiple steps or multiple stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution of these steps or stages is not necessarily sequential, but can be executed alternately or alternately with at least some of the other steps or steps or stages in other steps. It can be understood that the steps in different embodiments can be freely combined as needed, and various non-contradictory schemes formed by the combination are within the scope of protection of the present application.

[0177] Based on the same inventive concept, the embodiments of the present application also provide a message pushing device for implementing the above-mentioned message pushing method. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme described in the above method, so the specific limitations in one or more message pushing device embodiments provided below can refer to the limitations of the message pushing method in the above text, which will not be repeated here.

[0178] In one exemplary embodiment, as shown in Figure 9 A message pushing device 90 is provided, comprising an information acquisition module 902, a pushing strategy matching module 904, a template filling module 906, a message processing module 908, and a message pushing module 910, wherein:

[0179] The information acquisition module 902 is configured to acquire message content and a message identifier of a message to be pushed.

[0180] The pushing strategy matching module 904 is configured to perform pushing strategy matching based on the message identifier to obtain a message pushing strategy matched with the message to be pushed, wherein the message pushing strategy comprises a message pushing template and a message pushing rule.

[0181] The template filling module 906 is configured to fill the message pushing template with the message content to obtain a target message.

[0182] The message processing module 908 is configured to, in a case where the message pushing template is configured with a message processing mechanism, perform business logic processing on the target message based on message processing logic corresponding to the message processing mechanism to obtain a pushing message.

[0183] The message pushing module 910 is configured to push the pushing message according to the message pushing rule.

[0184] In one of the embodiments, the message pushing device 90 further comprises:

[0185] a parsing module, configured to parse template configuration information of the message pushing template;

[0186] a mechanism determining module, configured to determine that the message pushing template is configured with the message processing mechanism in a case that the template configuration information contains a configuration field for the message processing mechanism;

[0187] a logic querying module, configured to query message processing logic matching the field content of the configuration field.

[0188] In one of the embodiments, the pushing strategy matching module 904 further comprises:

[0189] a template determining unit, configured to determine an initial pushing template matching the message identifier;

[0190] a parameter obtaining unit, configured to obtain configuration parameters carried by a configuration event in response to the configuration event for the initial pushing template;

[0191] a template updating unit, configured to update the initial pushing template according to the configuration parameters to obtain the message pushing template.

[0192] In one of the embodiments, the template determining unit is further configured to:

[0193] determine a basic pushing template matching the message identifier;

[0194] perform inheritance chain query according to a template identifier of the basic pushing template to obtain a template inheritance chain of the basic pushing template;

[0195] perform parameter recursive merging processing on template configuration parameters of each parent template in the template inheritance chain to obtain the initial pushing template.

[0196] In one of the embodiments, the pushing strategy matching module further comprises:

[0197] a rule matching unit, configured to perform pushing rule matching based on the message identifier to obtain at least one candidate pushing rule matching the message to be pushed;

[0198] a pushing end determining unit, configured to determine a message pushing end of the message to be pushed;

[0199] a rule screening unit, configured to screen a message pushing rule matching the message pushing end from the multiple candidate pushing rules.

[0200] In one of the embodiments, the message pushing device 90 further comprises:

[0201] The description information acquisition module is configured to acquire description information of the to-be-pushed message in a case where the to-be-pushed message has an associated resource pushing demand.

[0202] The associated resource construction module is configured to construct the associated resource of the to-be-pushed message according to the description information.

[0203] In one of the embodiments, the message pushing module 910 is further configured to push the pushed message and the associated resource according to the message pushing rule.

[0204] The modules in the message pushing apparatus can be implemented by software, hardware, or a combination thereof. The modules can be embedded in or independent of a processor in a computer device in hardware form, or stored in a memory in the computer device in software form, so as to be called and executed by a processor to perform operations corresponding to the modules.

[0205] In one example embodiment, a computer device is provided, which can be a server. An internal structure diagram of the computer device can be as shown in Figure 10 The computer device includes a processor, a memory, an input / output interface, and a communication interface. The processor, the memory, and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for running the operating system and the computer program in the non-volatile storage medium. The database of the computer device is configured to store message pushing data. The input / output interface of the computer device is configured to exchange information between the processor and external devices. The communication interface of the computer device is configured to communicate with external terminals through a network connection. The computer program is executed by the processor to implement a message pushing method.

[0206] Those skilled in the art can understand that Figure 10 The structure shown in the figure is only a block diagram of part of the structure related to the scheme of the present application, and does not constitute a limitation on the computer device to which the scheme of the present application is applied. A specific computer device can include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0207] In one example embodiment, a computer device is provided, which includes a memory and a processor. The memory stores a computer program. The processor executes the computer program to implement the following steps:

[0208] Acquire message content and a message identifier of a to-be-pushed message.

[0209] based on the message identifier, performing push strategy matching to obtain a message push strategy matched with the message to be pushed, wherein the message push strategy comprises a message push template and a message push rule;

[0210] filling the message push template with the message content to obtain a target message;

[0211] in a case where the message push template is configured with a message processing mechanism, performing business logic processing on the target message based on message processing logic corresponding to the message processing mechanism to obtain a push message;

[0212] pushing the push message according to the message push rule.

[0213] In one embodiment, the processor, when executing the computer program, also implements the following steps:

[0214] parsing template configuration information of the message push template;

[0215] in a case where the template configuration information contains a configuration field for the message processing mechanism, determining that the message push template is configured with the message processing mechanism;

[0216] querying message processing logic matched with field content of the configuration field.

[0217] In one embodiment, the processor, when executing the computer program, also implements the following steps:

[0218] determining an initial push template matched with the message identifier;

[0219] in response to a configuration event for the initial push template, obtaining configuration parameters carried by the configuration event;

[0220] updating the initial push template according to the configuration parameters to obtain the message push template.

[0221] In one embodiment, the processor, when executing the computer program, also implements the following steps:

[0222] determining a basic push template matched with the message identifier;

[0223] performing inheritance chain query according to a template identifier of the basic push template to obtain a template inheritance chain of the basic push template;

[0224] performing parameter recursive merging processing on template configuration parameters of each parent template in the template inheritance chain to obtain the initial push template.

[0225] In one embodiment, the processor, when executing the computer program, also implements the following steps:

[0226] Based on the message identifier, push rule matching is performed to obtain at least one candidate push rule matched with the push message;

[0227] A message push end of the push message is determined.

[0228] From the plurality of candidate push rules, a message push rule matched with the message push end is screened.

[0229] In one embodiment, the processor further implements the following steps when executing the computer program:

[0230] In a case where the push message has an associated resource push demand, description information of the push message is obtained.

[0231] According to the description information, an associated resource of the push message is constructed.

[0232] The push message is pushed according to the message push rule, including:

[0233] The push message and the associated resource are pushed according to the message push rule.

[0234] In one embodiment, a computer readable storage medium is provided, and the computer readable storage medium stores a computer program. The computer program is executed by a processor to implement the following steps:

[0235] Message content and a message identifier of a push message are obtained.

[0236] Based on the message identifier, push strategy matching is performed to obtain a message push strategy matched with the push message, wherein the message push strategy includes a message push template and a message push rule.

[0237] The message push template is filled with the message content to obtain a target message.

[0238] In a case where the message push template is configured with a message processing mechanism, the target message is processed based on a message processing logic corresponding to the message processing mechanism to obtain a push message.

[0239] The push message is pushed according to the message push rule.

[0240] In one embodiment, the computer program is executed by the processor to further implement the following steps:

[0241] Template configuration information of the message push template is parsed.

[0242] In a case where the template configuration information includes a configuration field for the message processing mechanism, it is determined that the message push template is configured with the message processing mechanism.

[0243] Message processing logic matched with the field content of the configuration field is queried.

[0244] In one embodiment, the computer program, when executed by the processor, further implements the following steps:

[0245] determining an initial push template matching the message identifier;

[0246] in response to a configuration event for the initial push template, obtaining configuration parameters carried by the configuration event;

[0247] updating the initial push template according to the configuration parameters to obtain a message push template.

[0248] In one embodiment, the computer program, when executed by the processor, further implements the following steps:

[0249] determining a basic push template matching the message identifier;

[0250] performing inheritance chain query according to the template identifier of the basic push template to obtain a template inheritance chain of the basic push template;

[0251] performing parameter recursive merging processing on template configuration parameters of each parent template in the template inheritance chain to obtain an initial push template.

[0252] In one embodiment, the computer program, when executed by the processor, further implements the following steps:

[0253] performing push rule matching based on the message identifier to obtain at least one candidate push rule matching the to-be-pushed message;

[0254] determining a message push end of the to-be-pushed message;

[0255] screening a message push rule matching the message push end from the plurality of candidate push rules.

[0256] In one embodiment, the computer program, when executed by the processor, further implements the following steps:

[0257] in a case where the to-be-pushed message has an associated resource push demand, obtaining description information of the to-be-pushed message;

[0258] constructing an associated resource of the to-be-pushed message according to the description information;

[0259] pushing the push message according to the message push rule, comprising:

[0260] pushing the push message and the associated resource according to the message push rule.

[0261] In one embodiment, a computer program product is provided, comprising a computer program which, when executed by the processor, implements the following steps:

[0262] obtaining message content and a message identifier of a message to be pushed;

[0263] performing push strategy matching based on the message identifier to obtain a message push strategy matched with the message to be pushed, wherein the message push strategy comprises a message push template and a message push rule;

[0264] filling the message push template with the message content to obtain a target message;

[0265] in a case where the message push template is configured with a message processing mechanism, performing business logic processing on the target message based on message processing logic corresponding to the message processing mechanism to obtain a push message;

[0266] pushing the push message according to the message push rule.

[0267] In one embodiment, the computer program is further implemented when executed by the processor to implement the following steps:

[0268] parsing template configuration information of the message push template;

[0269] in a case where the template configuration information contains a configuration field for the message processing mechanism, determining that the message push template is configured with the message processing mechanism;

[0270] querying message processing logic matched with field content of the configuration field.

[0271] In one embodiment, the computer program is further implemented when executed by the processor to implement the following steps:

[0272] determining an initial push template matched with the message identifier;

[0273] in response to a configuration event for the initial push template, obtaining configuration parameters carried by the configuration event;

[0274] updating the initial push template according to the configuration parameters to obtain the message push template.

[0275] In one embodiment, the computer program is further implemented when executed by the processor to implement the following steps:

[0276] determining a basic push template matched with the message identifier;

[0277] performing inheritance chain query according to a template identifier of the basic push template to obtain a template inheritance chain of the basic push template;

[0278] performing parameter recursive merging processing on template configuration parameters of each parent template in the template inheritance chain to obtain the initial push template.

[0279] In one embodiment, the computer program is further implemented when executed by the processor to implement the following steps:

[0280] based on the message identifier, performing push rule matching to obtain at least one candidate push rule matched with the to-be-pushed message;

[0281] determining a message push end of the to-be-pushed message;

[0282] from the plurality of candidate push rules, screening a message push rule matched with the message push end.

[0283] In one embodiment, the computer program, when executed by the processor, further implements the following steps:

[0284] in a case where the to-be-pushed message exists an associated resource push demand, obtaining description information of the to-be-pushed message;

[0285] according to the description information, constructing an associated resource of the to-be-pushed message;

[0286] pushing the push message according to the message push rule, comprising:

[0287] pushing the push message and the associated resource according to the message push rule.

[0288] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer readable storage medium, and when executed, can include the processes of the above-mentioned embodiment methods. Any reference to memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. The non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical storage, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. The volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration but not limitation, the RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The database involved in the embodiments provided in the present application can include at least one of a relational database and a non-relational database. The non-relational database can include a distributed database based on a block chain, etc., without being limited thereto. The processor involved in the embodiments provided in the present application can be a general-purpose processor, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., without being limited thereto.

[0289] The technical features of the above embodiments can be combined in any way. To make the description concise, not all possible combinations of the technical features in the above embodiments are described, but as long as the combinations of the technical features do not exist contradictions, they should be considered as the scope of the present application.

[0290] The above-described embodiments are merely illustrative of several embodiments of the present application, and the description is relatively specific and detailed, but should not be understood as a limitation on the scope of the patent. It should be noted that for those skilled in the art, without departing from the concept of the present application, a number of modifications and improvements can be made, which are all within the scope of the present application. Therefore, the scope of protection of the present application should be subject to the appended claims.

Claims

1. A message push method, characterized in that, The method includes: Get the message content and message identifier of the message to be pushed; Based on the message identifier, push strategy matching is performed to obtain a message push strategy that matches the message to be pushed, wherein the message push strategy includes a message push template and message push rules; The message content is used to populate the message push template to obtain the target message; When the message push template is configured with a message processing mechanism, the target message is processed by business logic based on the message processing logic corresponding to the message processing mechanism to obtain the push message; The push message is pushed according to the message push rules.

2. The method according to claim 1, characterized in that, The method further includes: Parse the template configuration information of the message push template; If the template configuration information includes a configuration field for the message processing mechanism, it is determined that the message push template is configured with a message processing mechanism. Query the message processing logic that matches the field content of the configured field.

3. The method according to claim 1, characterized in that, The step of performing push strategy matching based on the message identifier to obtain a message push strategy that matches the message to be pushed includes: Determine an initial push template that matches the message identifier; In response to a configuration event for the initial push template, obtain the configuration parameters carried by the configuration event; The initial push template is updated according to the configuration parameters to obtain the message push template.

4. The method according to claim 3, characterized in that, The process of determining the initial push template that matches the message identifier includes: Determine the basic push template that matches the message identifier; Based on the template identifier of the basic push template, an inheritance chain query is performed to obtain the template inheritance chain of the basic push template; The template configuration parameters of each parent template in the template inheritance chain are recursively merged to obtain the initial push template.

5. The method according to claim 1, characterized in that, The step of performing push strategy matching based on the message identifier to obtain a message push strategy that matches the message to be pushed also includes: Based on the message identifier, push rule matching is performed to obtain at least one candidate push rule that matches the message to be pushed; Determine the message pusher for the message to be pushed; From multiple candidate push rules, filter the push rules that match the push client.

6. The method according to claim 1, characterized in that, The method further includes: If the message to be pushed has a related resource push requirement, obtain the description information of the message to be pushed; Based on the description information, construct the associated resources for the message to be pushed; The step of pushing the push message according to the message push rules includes: The push message and the associated resources are pushed according to the message push rules.

7. A message push device, characterized in that, The device includes: The information acquisition module is used to acquire the message content and message identifier of the message to be pushed; The push strategy matching module is used to perform push strategy matching based on the message identifier to obtain a message push strategy that matches the message to be pushed, wherein the message push strategy includes a message push template and message push rules; The template filling module is used to fill the message push template with the message content to obtain the target message; The message processing module is used to perform business logic processing on the target message based on the message processing logic corresponding to the message processing mechanism when the message push template is configured with a message processing mechanism, so as to obtain the push message. The message push module is used to push the push message according to the message push rules.

8. The apparatus according to claim 7, characterized in that, The device further includes: The parsing module is used to parse the template configuration information of the message push template; The mechanism determination module is used to determine that the message push template is configured with a message processing mechanism when the template configuration information includes a configuration field for the message processing mechanism. The logic query module is used to query message processing logic that matches the field content of the configured field.

9. The apparatus according to claim 7, characterized in that, The push strategy matching module further includes: The template determination unit is used to determine an initial push template that matches the message identifier; The parameter acquisition unit is used to acquire the configuration parameters carried by the configuration event in response to the configuration event for the initial push template. The template update unit is used to update the initial push template according to the configuration parameters to obtain the message push template.

10. The apparatus according to claim 9, characterized in that, The template determining unit is also used for: Determine the basic push template that matches the message identifier; Based on the template identifier of the basic push template, an inheritance chain query is performed to obtain the template inheritance chain of the basic push template; The template configuration parameters of each parent template in the template inheritance chain are recursively merged to obtain the initial push template.

11. The apparatus according to claim 7, characterized in that, The push strategy matching module further includes: The rule matching unit is used to perform push rule matching based on the message identifier to obtain at least one candidate push rule that matches the message to be pushed. A push terminal determination unit is used to determine the message push terminal of the message to be pushed. The rule filtering unit is used to filter message push rules that match the message push terminal from multiple candidate push rules.

12. The apparatus according to claim 7, characterized in that, The device further includes: The description information acquisition module is used to acquire the description information of the message to be pushed when there is a related resource push requirement for the message to be pushed. An associated resource construction module is used to construct associated resources for the message to be pushed based on the description information. The message push module is also used to push the push message and the associated resources according to the message push rules.

13. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

15. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images