Message pushing method and device
By introducing data source identification and dynamic filtering rules, decoupling message sources and business logic, the flexibility and customization capabilities of message push are realized, and the problems of poor message push flexibility and strong code invasiveness in the existing technology are solved.
Patent Information
- Application Number
- CN202510386518.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-03-28
- Publication Date
- 2025-06-27
AI Technical Summary
In the prior art, message pushing is poor, code invasive, and it is difficult to meet the needs of multiple message pushing.
By introducing data source identification, the source of messages and business logic are decoupled and diversified data source access is supported. Based on the data source identification matching filtering rules, dynamic filtering of messages is realized, and push rules are independently defined, and push methods and targets are dynamically matched according to message attributes.
It improves the flexibility of message push, reduces the code intrusion of the business system, enhances the customized ability of message push, and supports diversified demand scenarios and business changes.
Smart Images
Figure CN120223746A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of computer technology, and in particular, to a message pushing method and device. Background Art
[0002] In the prior art, different message pushing types are often split into independent service modules in the business system, and communication protocols are used for interaction between services. The business system implements message pushing by writing code. However, when the business system performs message pushing, corresponding code needs to be written for different message pushing requirements, resulting in poor flexibility of message pushing and strong code invasiveness. Summary of the Invention
[0003] In view of this, the embodiments of the present disclosure at least provide a message pushing method, device, electronic device, and storage medium, which can meet various message pushing requirements, improve the flexibility of message pushing, and reduce the invasiveness of code to the business system.
[0004] In a first aspect, an embodiment of the present disclosure provides a message pushing method, including:
[0005] Determine the data source identifier of the message to be pushed;
[0006] Based on the data source identifier, determine at least one filtering rule corresponding to the data source identifier, so as to filter the message to be pushed based on the filtering rule;
[0007] In response to the message to be pushed satisfying the filtering rule, push the message to be pushed based on the pushing rule corresponding to the message to be pushed.
[0008] Optionally, filtering the message to be pushed based on the filtering rule includes:
[0009] Determine whether the message to be pushed matches at least one filtering rule; wherein, the filtering rule is pre-configured; the filtering rules corresponding to different data source identifiers are different;
[0010] In response to the existence of a filtering rule that matches the message to be pushed among at least one filtering rule, determine that the message to be pushed satisfies the filtering rule;
[0011] In response to the non-existence of a filtering rule that matches the message to be pushed among at least one filtering rule, determine that the message to be pushed does not satisfy the filtering rule, and do not push the message to be pushed.
[0012] Optionally, before pushing the message to be pushed based on the pushing rule corresponding to the message to be pushed, it further includes:
[0013] Determine the data processing rule corresponding to the message to be pushed; the data processing rule includes a target data format and a target service field;
[0014] Extract the message data under the target service field from the message to be pushed based on the data processing rules, and convert the message data into the target data format to obtain the message to be pushed with the data processing completed.
[0015] Optionally, before pushing the message to be pushed based on the push rule corresponding to the message to be pushed, it further includes:
[0016] Determine the push rule corresponding to the message to be pushed based on the push type selected by the user and the message template corresponding to the push type.
[0017] Optionally, pushing the message to be pushed based on the push rule corresponding to the message to be pushed includes:
[0018] Assemble the message to be pushed according to the message template, and push the assembled message to be pushed according to the push type.
[0019] Optionally, the method further includes:
[0020] Configure the filtering rule, data processing rule and push rule based on the low-code method.
[0021] In a second aspect, an embodiment of the present disclosure provides a message push device, including:
[0022] A determination module, configured to determine the data source identifier of the message to be pushed;
[0023] A filtering module, configured to determine at least one filtering rule corresponding to the data source identifier based on the data source identifier, so as to filter the message to be pushed based on the filtering rule;
[0024] A push module, configured to push the message to be pushed based on the push rule corresponding to the message to be pushed in response to the message to be pushed passing the filter.
[0025] In a third aspect, an embodiment of the present disclosure further provides an electronic device, including: a processor, a memory and a bus, the memory stores machine-readable instructions executable by the processor, when the computer device runs, the processor communicates with the memory through the bus, and when the machine-readable instructions are executed by the processor, the steps in the first aspect, or any optional implementation manner in the first aspect are executed.
[0026] In a fourth aspect, an embodiment of the present disclosure further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is run by a processor, the steps in the first aspect, or any optional implementation manner in the first aspect are executed.
[0027] Fifth aspect, an embodiment of the present disclosure further provides a computer program product, including a computer program which, when executed by a processor, implements the method of any of the above embodiments.
[0028] In any of the above aspects or any implementation manner of any aspect, by introducing a data source identifier, the source of the message is decoupled from the specific business logic, supporting access to diverse data sources. Based on the data source identifier to match the filtering rules, dynamic filtering of messages is achieved, ensuring that only messages meeting specific conditions can enter the subsequent push process. Thus, the filtering rules can be flexibly adjusted without directly modifying the business system code, greatly reducing the invasiveness to the business system. In addition, by independently defining the push rules and dynamically matching suitable push methods and targets according to the attributes of the messages to be pushed, the customization ability of message pushing is further improved. The flexible configuration of the push rules can not only meet the requirements of diverse push scenarios, but also quickly respond to business changes, such as adding new push channels or adjusting push strategies, avoiding frequent adjustment of the core logic code. Through the above method, the embodiments of the present disclosure process data filtering and push logic in layers, effectively separating the coupling relationship between message management and business functions, ensuring both the generality of the message push system and providing a solution with high controllability and low maintenance cost for business expansion, thereby achieving flexible and efficient message pushing in diverse demand scenarios.
[0029] For the effects of the above message push device, electronic device and storage medium, refer to the description of the above message push method and will not be elaborated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0030] To more clearly illustrate the technical solutions of the embodiments of the present disclosure, the following will briefly introduce the drawings required for use in the embodiments. The drawings here are incorporated into the specification and constitute a part of this specification. These drawings show embodiments conforming to the present disclosure and are used together with the specification to illustrate the technical solutions of the present disclosure. It should be understood that the following drawings only show some embodiments of the present disclosure and should not be regarded as limiting the scope. For those of ordinary skill in the art, without creative efforts, other relevant drawings can also be obtained based on these drawings.
[0031] Figure 1 Shows a flowchart of a message push method provided by an embodiment of the present disclosure;
[0032] Figure 2 Shows a schematic flow diagram of a message push method provided by an embodiment of the present disclosure;
[0033] Figure 3 Shows a schematic diagram of the association relationship between a data source, filtering rules and push rules provided by an embodiment of the present disclosure;
[0034] Figure 4 Shows a schematic diagram of a message push device provided by an embodiment of the present disclosure;
[0035] Figure 5 Shows an exemplary system architecture to which an embodiment of the present disclosure can be applied;
[0036] Figure 6 Shows a schematic structural diagram of a computer system of a terminal device or a server for implementing an embodiment of the present disclosure. Detailed implementation manners
[0037] To make the objectives, technical solutions and advantages of the embodiments of the present disclosure clearer, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only a part rather than all of the embodiments of the present disclosure. Usually, the components of the embodiments of the present disclosure described and illustrated in the accompanying drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present disclosure provided in the accompanying drawings is not intended to limit the scope of the claimed present disclosure, but merely represents selected embodiments of the present disclosure. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without creative efforts shall fall within the scope of protection of the present disclosure.
[0038] It should be noted that in the technical solutions of the present invention, the processing of collection, use, storage, sharing, transfer, etc. of the user's personal information complies with the provisions of relevant laws and regulations, and the user needs to be informed and obtain the consent or authorization of the user. When applicable, technical processing of de-identifying and / or anonymizing and / or encrypting the user's personal information is performed.
[0039] The above problems and the solutions to them are all the results obtained by the inventors after practice and careful research. The discovery process of the above problems and the solutions proposed for the above problems should all be the contributions made by the inventors to the present disclosure during the process of the present disclosure.
[0040] The technical solutions in the present disclosure will be clearly and completely described below with reference to the accompanying drawings in the present disclosure. Obviously, the described embodiments are only a part rather than all of the embodiments of the present disclosure. Usually, the components of the present disclosure described and illustrated in the accompanying drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present disclosure provided in the accompanying drawings is not intended to limit the scope of the claimed present disclosure, but merely represents selected embodiments of the present disclosure. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without creative efforts shall fall within the scope of protection of the present disclosure.
[0041] It should be noted that like reference numerals and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
[0042] For ease of understanding of this embodiment, first, a message push method disclosed in the embodiments of the present disclosure will be introduced in detail. The execution subject of the message push method provided in the embodiments of the present disclosure is generally a computer device with certain computing capabilities. Such a computer device includes, for example: a terminal device, a server, or other processing devices. The terminal device may be a user equipment (UE), a mobile device, a user terminal, a terminal, a cellular phone, a cordless phone, a personal digital assistant (PDA), a handheld device, a computing device, a vehicle-mounted device, a wearable device, etc. In some possible implementation manners, the message push method may be implemented by a processor calling computer-readable instructions stored in a memory.
[0043] See Figure 1 As shown in the figure, it is a flowchart of the message push method provided in the embodiments of the present disclosure. The method includes S101 to S103, where:
[0044] S101: Determine the data source identifier of the message to be pushed.
[0045] The execution subject of the embodiments of the present disclosure may be a message push platform independent of the business system, which is used to receive messages sent by the business system and process and push the messages according to filtering rules, data processing rules, and push rules. Alternatively, the execution subject of the embodiments of the present disclosure may also be a message push module integrated inside the business system, which is used to receive messages forwarded by other modules in the business system and process and push the messages according to filtering rules, data processing rules, and push rules. The embodiments of the present disclosure do not make specific limitations on this, as long as its functions can be realized.
[0046] In the embodiments of the present disclosure, the data source may correspond to a specific business scenario. For example, as Figure 2 shown, assuming that the current application scenario is the monitoring message push in the medical and health field, the data source may include fields indicating the business source of the data, such as "acute illness", "abnormal health detection", etc.; it may also include event identifiers for distinguishing specific business scenarios, such as "urgent health event", etc.; it may also include detailed data related to the business for rule matching, filtering, and data processing.
[0047] In a specific implementation, the source system of the message to be pushed can determine the data source identifier of the message to be pushed. For example, when the source system of the message to be pushed is an emergency management system, the data source identifier of the message to be pushed can be determined as "Emergency - Urgent Health Event". Alternatively, the data source identifier of the message to be pushed can also be determined based on the field information in the message to be pushed. For example, the corresponding data source identifier can be matched by analyzing fields such as the classification field or event type field in the message to be pushed. It should be noted that the above methods are only examples of feasible implementation methods in the embodiments of the present disclosure, and do not constitute improper limitations on the present invention. In actual applications, the corresponding method for determining the data source identifier can be set according to actual situations, and the embodiments of the present disclosure do not make specific limitations on this, as long as its function can be realized.
[0048] S102: Based on the data source identifier, determine at least one filtering rule corresponding to the data source identifier, so as to filter the message to be pushed based on the filtering rule.
[0049] The filtering rule can be defined and implemented in a low - code manner, and is used to determine whether the message to be pushed in the data source meets the preset conditions, so as to decide whether the message passes the filtering and enters the subsequent processing flow. Among them, low - code means defining the filtering rule through simple configuration, graphical interface or simplified code, without requiring developers to write complex programs.
[0050] In the embodiments of the present disclosure, as Figure 3 shown, each data source can maintain multiple filtering rules. After determining the data source identifier of the message to be pushed, the message to be pushed can be matched with the filtering rules corresponding to the data source one by one. Specifically, filtering the message to be pushed based on the filtering rule includes: determining whether the message to be pushed matches at least one filtering rule; where the filtering rule is pre - configured; the filtering rules corresponding to different data source identifiers are different; in response to the existence of a filtering rule that matches the message to be pushed among at least one filtering rule, determining that the message to be pushed meets the filtering rule; in response to the non - existence of a filtering rule that matches the message to be pushed among at least one filtering rule, determining that the message to be pushed does not meet the filtering rule and not pushing the message to be pushed.
[0051] In a specific implementation, assume that the data source only maintains one filtering rule in advance, then the message to be pushed can be matched with this filtering rule. Exemplarily, Figure 2Taking the "specified value" in the filtering rule part as an example, assume that the filtering rule is preset as "the severity field must be equal to critical", that is, a value is specified for the severity field in the filtering rule. When the value of the severity field in the message to be pushed is critical, the message to be pushed meets the filtering rule; otherwise, it does not meet the filtering rule. When multiple filtering rules are pre-maintained in the data source, the message to be pushed can be matched with each filtering rule one by one. If it is found that the message to be pushed does not match any of the multiple filtering rules after matching, it means that the message to be pushed does not meet the push requirements. At this time, the push process of this message can be terminated and this message is not pushed. Alternatively, the matching operation of the message to be pushed with multiple filtering rules can also be executed in parallel. Exemplarily, as Figure 3 shown, assume that the data source maintains Filtering Rule 1, Filtering Rule 2, and Filtering Rule 3. Three parallel tasks can be started to match the message to be pushed with the filtering rules simultaneously. Assume that Filtering Rule 1 is a rule indicating the "specified value", specifically "the severity field must be equal to critical"; Filtering Rule 2 is a rule indicating "existence", specifically "including the location field and the field value is not empty"; Filtering Rule 3 is a rule indicating "exclusion", specifically "the value of the department field cannot be test". Thus, it can be determined whether the message to be pushed meets at least one of the multiple filtering rules corresponding to the data source. If it meets, it means that the message to be pushed needs to be pushed for subsequent push steps.
[0052] It should be noted that the above specific filtering rules are only examples of feasible implementation manners in the embodiments of the present disclosure and do not constitute improper limitations on the present invention. In actual applications, corresponding filtering rules can be set according to actual situations and requirements. For example, it can also include prefix filtering, suffix filtering, inclusion filtering, etc. The embodiments of the present disclosure do not make specific limitations on this and are subject to the achievement of its functions.
[0053] S103: In response to the message to be pushed meeting the filtering rule, push the message to be pushed based on the push rule corresponding to the message to be pushed.
[0054] In the embodiments of the present disclosure, before pushing the message to be pushed based on the push rule corresponding to the message to be pushed, it further includes: determining a data processing rule corresponding to the message to be pushed; the data processing rule includes a target data format and target service fields; based on the data processing rule, extracting the message data under the target service fields from the message to be pushed and converting the message data into the target data format to obtain the message to be pushed after completing data processing.
[0055] In specific implementations, to ensure that the message to be pushed can meet the target business requirements, data processing can be performed on the message to achieve format standardization and content adaptation. First, the system can determine the corresponding data processing rules based on the characteristics of the message to be pushed and the business requirements. The data processing rules can include two core elements: the target data format and the target business fields. Among them, the target data format can be used to define the structure or template that the message ultimately needs to follow, such as JSON, XML, or other formats, to adapt to the requirements of the recipient; the target business fields can clarify the key information that needs to be retained or extracted in the message, such as user identification, event type, timestamp, etc. Based on the above data processing rules, the system can extract the message data corresponding to the target business fields from the original message to be pushed, while removing redundant information to simplify the message content. After extracting the message data, the system can perform format conversion on the extracted content through data processing logic to make it consistent with the target data format; for example, mapping of field names, adjustment of data types, or reorganization of content. For example, some fields may need to be combined into a new field, or the original data may be split into multiple parts to adapt to the new format. After completing the data processing, a message to be pushed that conforms to the target data format can be generated. Finally, the message after data processing not only retains the core information of the original message but also meets the format requirements of the push target. This not only improves the standardization of the message but also ensures the availability and adaptability of the data, and enhances the system's expansion ability and flexibility in multi-business scenarios.
[0056] In another possible implementation, in addition to including the target data format and the target business fields, the data processing rules can also include data verification rules, field mapping rules, or default value configurations, etc. The data verification rules can be used to ensure the accuracy and integrity of the data to be processed, for example, verifying whether the value of a field is within a predefined range, whether the date format conforms to the standard, or whether a key field is empty, etc.; the field mapping rules can define the corresponding relationship between the original data fields and the target data fields, for example, mapping the original field user_id to the target field uid, or combining multiple original fields into a new field such as full_name. In addition, the default value configuration is used to fill in the preset value when the data is missing. For example, when the field location is empty, it is default filled with "unknown" to ensure the integrity of the message push. This not only improves the flexibility of data processing but also reduces the risk of push failure caused by data problems, and further enhances the system's adaptability to complex scenarios.
[0057] In the embodiments of the present disclosure, the push rule may be determined by the push type and the message template. Specifically, before pushing the message to be pushed based on the push rule corresponding to the message to be pushed, it further includes: determining the push rule corresponding to the message to be pushed based on the push type selected by the user and the message template corresponding to the push type.
[0058] In the embodiments of the present disclosure, the user may select the push type of the message, such as text message, email, phone call, etc. Each push type may correspond to one or more message templates. By assembling the message template with the message to be pushed, a standard message can be obtained, and the message can be pushed based on the standard message. Among them, the push type and the message template under the push type may be selected by the user himself / herself, or determined according to the pre-configured association relationship in the system. For example, assuming that the push type selected by the user is a text message, the message template used to assemble the message to be pushed can be selected from multiple message templates under the text message type by specifying the template identifier. In addition, the system can also assemble preview messages corresponding to different message templates based on multiple message templates under the text message type, enabling the user to more intuitively obtain the form of message pushing based on different message templates, so as to select a message template that meets the expectations. The embodiments of the present disclosure do not make specific limitations on this, as long as its functions can be realized.
[0059] In the embodiments of the present disclosure, pushing the message to be pushed based on the push rule corresponding to the message to be pushed includes: assembling the message to be pushed according to the message template, and pushing the assembled message to be pushed according to the push type.
[0060] In a specific implementation, after determining the push type and the message template, the message to be pushed can be assembled according to the message template, and the message to be pushed can be pushed according to the push type. Exemplarily, assuming that the push type selected by the user is text message push and the selected message template is "{$.nickname}'s physical health detection is completed, {$.number} abnormal indicators appear. It is recommended that you {$.suggestion}. If necessary, you can call your exclusive doctor for consultation". At this time, the data under the fields of $.nickname, $.number, and $.suggestion in the message to be pushed can be assembled in the message template to obtain the final message data to be pushed. Or, before pushing the assembled message to be pushed according to the push type, a preview style can also be generated and displayed to the user. In addition, after pushing the message to be pushed, the feedback information of the recipient can be used to verify whether the message is pushed successfully. If the push fails, it can be pushed again.
[0061] In the embodiments of the present disclosure, filtering rules, data processing rules, and push rules can all be flexibly adapted in a low-code manner, no longer relying on traditional hard coding or pre-agreed interface configurations. Instead, the input parameters of data are dynamically configured according to the definition of the interface, thereby greatly simplifying the development process. Thus, developers can directly complete rule configuration through visual operations or simple scripts without having to deeply understand the underlying code implementation. During the data processing and conversion process, if additional data sources or calculation logics are required, the system also supports dynamically obtaining or processing data by calling external APIs (Application Programming Interfaces). The above method enhances the flexibility and scalability of rule adaptation, making data assembly and message sending in complex scenarios more efficient. For example, in an application with multiple business scenarios, different data sources may have different formats and fields. The low-code configuration method can easily adjust field mapping, data verification, or push logic without modifying the code, supporting rapid iteration of business requirements and enabling complex message assembly and precise push.
[0062] In another possible implementation, filtering rules, data processing rules, and push rules can also be pre-configured using dynamic configuration files or rule engines, etc. The embodiments of the present disclosure do not make specific limitations on this, and in actual applications, it can be set according to actual situations to enable its functions. For example, developers can pre-design the configuration format of the rules, and the system can load and parse these configuration files during runtime for execution.
[0063] According to the second aspect of the embodiments of the present disclosure, as Figure 4 shown, a message push device 400 is provided, including:
[0064] A determination module 401, configured to determine the data source identifier of the message to be pushed;
[0065] A filtering module 402, configured to determine at least one filtering rule corresponding to the data source identifier based on the data source identifier, so as to filter the message to be pushed based on the filtering rule;
[0066] A push module 403, configured to push the message to be pushed based on the push rule corresponding to the message to be pushed in response to the message to be pushed passing the filter.
[0067] Optionally, the filtering module 402 is specifically configured to:
[0068] Determine whether the message to be pushed matches at least one filtering rule; wherein, the filtering rule is pre-configured; different filtering rules correspond to different data source identifiers;
[0069] In response to the existence of a filtering rule that matches the message to be pushed in at least one filtering rule, it is determined that the message to be pushed meets the filtering rule;
[0070] In response to the non-existence of a filtering rule that matches the message to be pushed in at least one filtering rule, it is determined that the message to be pushed does not meet the filtering rule, and the message to be pushed is not pushed.
[0071] Optionally, the pushing module 403 is further configured to:
[0072] Determine a data processing rule corresponding to the message to be pushed; the data processing rule includes a target data format and target service fields;
[0073] Based on the data processing rule, extract the message data under the target service field from the message to be pushed, and convert the message data into the target data format to obtain the message to be pushed after completing data processing.
[0074] Optionally, the pushing module 403 is further configured to:
[0075] Determine a pushing rule corresponding to the message to be pushed based on the selected pushing type and the message template corresponding to the pushing type.
[0076] Optionally, the pushing module 403 is specifically configured to:
[0077] Assemble the message to be pushed according to the message template, and push the assembled message to be pushed according to the pushing type.
[0078] Optionally, the device further includes a configuration module 404; the configuration module 404 is specifically configured to:
[0079] Configure the filtering rule, data processing rule, and pushing rule based on a low-code method.
[0080] According to the third aspect of the embodiments of the present disclosure, there is provided an electronic device for message pushing, including: one or more processors; a storage device for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors implement the method provided in the first aspect of the embodiments of the present invention.
[0081] According to the fourth aspect of the embodiments of the present disclosure, there is provided a computer-readable medium, on which a computer program is stored, and when the program is executed by a processor, the method provided in the first aspect of the embodiments of the present invention is implemented.
[0082] According to the fifth aspect of the embodiments of the present invention, there is provided a computer program product, including a computer program, and when the computer program is executed by a processor, the method of any of the above embodiments is implemented.
[0083] Figure 5Fig. 500 shows an exemplary system architecture to which the message push method or message push device according to the present disclosure can be applied.
[0084] As Figure 5 shown, the system architecture 500 may include terminal devices 501, 502, 503, a network 504, and a server 505. The network 504 is used to provide a medium for communication links between the terminal devices 501, 502, 503 and the server 505. The network 504 may include various connection types, such as wired, wireless communication links, or fiber optic cables, etc.
[0085] Users can use the terminal devices 501, 502, 503 to interact with the server 505 through the network 504 to receive or send messages, etc. Various communication client applications may be installed on the terminal devices 501, 502, 503, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only as examples).
[0086] The terminal devices 501, 502, 503 may be various electronic devices with a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, and desktop computers, etc.
[0087] The server 505 may be a server providing various services, such as a background management server that supports the shopping websites browsed by users using the terminal devices 501, 502, 503 (only as an example). The background management server may process the received message push requests and feedback the processing results (only as an example) to the terminal devices.
[0088] It should be noted that the message push method provided by the embodiments of the present invention is generally executed by the server 505. Correspondingly, the message push device is generally set in the server 505. The message push method provided by the embodiments of the present invention may also be executed by the terminal devices 501, 502, 503. Correspondingly, the message push device may be set in the terminal devices 501, 502, 503.
[0089] It should be understood that Figure 5 the numbers of the terminal devices, the network, and the server in
[0090] are merely illustrative. According to the implementation requirements, there may be any number of terminal devices, networks, and servers. Figure 6 is merely illustrative. According to the implementation requirements, there may be any number of terminal devices, networks, and servers. Figure 6 The terminal device shown is only an example and should not impose any limitations on the functions and usage scope of the embodiments of the present invention.
[0091] As shown Figure 6 As shown in FIG. 2, a computer system 600 includes a central processing unit (CPU) 601 that can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded into a random access memory (RAM) 603 from a storage section 608. In the RAM 603, various programs and data required for the operation of the system 600 are also stored. The CPU 601, ROM 602, and RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.
[0092] The following components are connected to the I / O interface 605: an input section 606 including a keyboard, a mouse, etc.; an output section 607 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc. and a speaker, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, a modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is mounted on the drive 610 as needed so that a computer program read therefrom is installed into the storage section 608 as needed.
[0093] Specifically, according to the embodiments disclosed in the present invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, the embodiments disclosed in the present invention include a computer program product that includes a computer program carried on a computer-readable medium, and the computer program includes program codes for performing the methods shown in the flowcharts. In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 609, and / or installed from the removable medium 611. When the computer program is executed by the central processing unit (CPU) 601, the above-described functions defined in the system of the present invention are executed.
[0094] It should be noted that the computer-readable medium shown in the present invention can be a computer-readable signal medium, a computer-readable storage medium, or any combination of the above two. A computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of a computer-readable storage medium can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium can be any tangible medium that contains or stores a program, and this program can be used by or in combination with an instruction execution system, apparatus, or device. In the present invention, a computer-readable signal medium can include a data signal propagated in a baseband or as part of a carrier wave, in which computer-readable program code is carried. Such a propagated data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, and this computer-readable medium can send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device. The program code contained on a computer-readable medium can be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.
[0095] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagram can represent a module, a program segment, or a part of code, and the above module, program segment, or part of code contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram or flowchart, as well as the combination of blocks in the block diagram or flowchart, can be implemented by a dedicated hardware-based system for performing the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.
[0096] The modules involved in the embodiments of the present invention can be implemented in software or in hardware. The described modules can also be provided in a processor. For example, a processor includes a determination module, a filtering module, and a pushing module. In some cases, the names of these modules do not constitute a limitation on the module itself. For example, the determination module can also be described as the "module for determining the data source identifier of the message to be pushed".
[0097] As another aspect, the present invention also provides a computer-readable medium. The computer-readable medium can be included in the device described in the above embodiments; or it can exist alone without being assembled into the device. The above computer-readable medium carries one or more programs. When the above one or more programs are executed by the device, the device implements the following method: determining the data source identifier of the message to be pushed; determining at least one filtering rule corresponding to the data source identifier based on the data source identifier to filter the message to be pushed based on the filtering rule; and in response to the message to be pushed satisfying the filtering rule, pushing the message to be pushed based on the pushing rule corresponding to the message to be pushed.
[0098] Finally, it should be noted that the above embodiments are only specific implementation manners of the present disclosure, used to illustrate the technical solutions of the present disclosure, rather than limiting them. The protection scope of the present disclosure is not limited thereto. Although the present disclosure has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: any person skilled in the art within the technical scope disclosed by the present disclosure can still modify the technical solutions recorded in the foregoing embodiments or easily think of changes, or perform equivalent replacements on some of the technical features; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present disclosure, and should all be covered by the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be subject to the protection scope of the claims.
Claims
1. A message push method, characterized in that: include: Determine the data source identifier of the message to be pushed; Based on the data source identifier, determining at least one filtering rule corresponding to the data source identifier, so as to filter the push message based on the filtering rule; In response to the message to be pushed satisfying the filtering rule, the message to be pushed is pushed based on a push rule corresponding to the message to be pushed.
2. The method according to claim 1, characterized in that Filtering the push message based on the filtering rule includes: Determine whether the message to be pushed matches at least one of the filtering rules; wherein the filtering rules are pre-configured; different data source identifiers correspond to different filtering rules; In response to the existence of a filtering rule matching the message to be pushed in at least one of the filtering rules, determining that the message to be pushed satisfies the filtering rule; In response to the absence of a filtering rule matching the message to be pushed in at least one of the filtering rules, it is determined that the message to be pushed does not satisfy the filtering rule, and the message to be pushed is not pushed.
3. The method according to claim 1, characterized in that Before pushing the message to be pushed based on the push rule corresponding to the message to be pushed, the method further includes: Determine a data processing rule corresponding to the message to be pushed; the data processing rule includes a target data format and a target business field; Based on the data processing rule, the message data under the target business field is extracted from the message to be pushed, and the message data is converted into the target data format to obtain the message to be pushed after completing the data processing.
4. The method according to claim 3, characterized in that Before pushing the message to be pushed based on the push rule corresponding to the message to be pushed, the method further includes: Based on the push type selected by the user and the message template corresponding to the push type, a push rule corresponding to the message to be pushed is determined.
5. The method according to claim 4, characterized in that Pushing the message to be pushed based on a push rule corresponding to the message to be pushed includes: The message to be pushed is assembled according to the message template, and the assembled message to be pushed is pushed according to the push type.
6. The method according to any one of claims 3 to 5, characterized in that: The method further comprises: The filtering rules, data processing rules and push rules are configured based on a low-code approach.
7. A message push device, characterized in that: include: A determination module, used to determine the data source identifier of the message to be pushed; A filtering module, configured to determine, based on the data source identifier, at least one filtering rule corresponding to the data source identifier, so as to filter the push message based on the filtering rule; The push module is used for pushing the message to be pushed based on the push rule corresponding to the message to be pushed in response to the message to be pushed passing the filtering.
8. An electronic device, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 6.
9. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.
10. A computer program product, comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 6.