CN114374737A - Message pushing method and device, computer equipment and storage medium - Google Patents
Message pushing method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN114374737A CN114374737A CN202210029851.3A CN202210029851A CN114374737A CN 114374737 A CN114374737 A CN 114374737A CN 202210029851 A CN202210029851 A CN 202210029851A CN 114374737 A CN114374737 A CN 114374737A
- Authority
- CN
- China
- Prior art keywords
- message
- data
- order data
- rule
- pushing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Abstract
The application belongs to the field of data transmission optimization, and particularly relates to a message pushing method, a message pushing device, computer equipment and a storage medium, wherein the message pushing method comprises the steps of obtaining a message to be pushed; calling a preset rule engine to filter all service order data in the service order data set to obtain filtered service order data, configuring the filtered service order data based on a preset template engine, and generating a push message body; acquiring a data receiving object corresponding to the filtered business order data, determining a receiving rule of the data receiving object, and filtering the push data in the push message body according to the receiving rule to obtain a target message body; and the target message body is pushed to the data receiving object, so that the time period and the cost of message configuration are reduced, and the message interaction efficiency is improved. In addition, the application also relates to a block chain technology, and both the rule template and the engine template can be stored in the block chain.
Description
Technical Field
The present application relates to the field of data transmission optimization, and in particular, to a message pushing method and apparatus, a computer device, and a storage medium.
Background
Generally, interaction between service platforms is generally performed by means of message pushing. However, because different service platforms exist in various channels and the organization architecture of each channel is also differentiated, the message push process of different service platforms and different channels needs to be specially debugged, so that the time period and the cost of message configuration are increased, and the message interaction efficiency between the service platforms is extremely low.
Disclosure of Invention
An object of the embodiments of the present application is to provide a message pushing method, a message pushing apparatus, a computer device, and a storage medium, so as to solve the problems of time period and cost increase of message configuration and extremely low message interaction efficiency.
In order to solve the foregoing technical problem, an embodiment of the present application provides a message pushing method, which adopts the following technical solutions:
acquiring a message to be pushed, wherein the message comprises a service order data set;
calling a preset rule engine to filter all the business order data in the business order data set to obtain filtered business order data, configuring the filtered business order data based on a preset template engine, and generating a push message body;
acquiring a data receiving object corresponding to the filtered business order data, determining a receiving rule of the data receiving object, and filtering the push data in the push message body according to the receiving rule to obtain a target message body;
and pushing the target message body to the data receiving object.
In order to solve the above technical problem, an embodiment of the present application further provides a message pushing apparatus, which adopts the following technical solutions:
the system comprises an acquisition module, a push module and a push module, wherein the acquisition module is used for acquiring a message to be pushed, and the message comprises a service order data set;
the filtering configuration module is used for calling a preset rule engine to filter all the business order data in the business order data set to obtain filtered business order data, configuring the filtered business order data based on a preset template engine, and generating a push message body;
the message filtering module is used for acquiring a data receiving object corresponding to the filtered business order data, determining a receiving rule of the data receiving object, and filtering the push data in the push message body according to the receiving rule to obtain a target message body;
and the pushing module is used for pushing the target message body to the data receiving object.
In order to solve the above technical problem, an embodiment of the present application further provides a computer device, which includes a memory and a processor, where the memory stores a computer program, and the processor implements the steps of the message pushing method when executing the computer program.
In order to solve the above technical problem, an embodiment of the present application further provides a storage medium, where a computer program is stored, and when the computer program is executed by a processor, the steps of the message pushing method are implemented.
Compared with the prior art, the embodiment of the application mainly has the following beneficial effects: the method comprises the steps of obtaining a message to be pushed, calling a preset rule engine to filter all service order data in a service order data set to obtain filtered service order data, configuring the filtered service order data based on a preset template engine to generate a pushed message body, obtaining a data receiving object corresponding to the filtered service order data, determining a receiving rule of the data receiving object, filtering the pushed data in the pushed message body according to the receiving rule to obtain a target message body, and pushing the target message body to the data receiving object, so that the time period and the cost of message configuration are reduced, and the interaction efficiency of the message is improved.
Drawings
In order to more clearly illustrate the solution of the present application, the drawings needed for describing the embodiments of the present application will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and that other drawings can be obtained by those skilled in the art without inventive effort.
FIG. 1 is an exemplary system architecture diagram in which the present application may be applied;
FIG. 2 is a flow diagram of one embodiment of a message push method according to the present application;
FIG. 3 is a flowchart of one embodiment of step S202 in FIG. 2;
FIG. 4 is a flow diagram of another embodiment of step S202 in FIG. 2;
FIG. 5 is a schematic diagram illustrating one embodiment of a message pushing device according to the present application;
FIG. 6 is a schematic block diagram of one embodiment of a computer device according to the present application.
Detailed Description
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "including" and "having," and any variations thereof, in the description and claims of this application and the description of the above figures are intended to cover non-exclusive inclusions. The terms "first," "second," and the like in the description and claims of this application or in the above-described drawings are used for distinguishing between different objects and not for describing a particular order.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.
As shown in fig. 1, the system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may use the terminal devices 101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The terminal devices 101, 102, 103 may have various communication client applications installed thereon, such as a web browser application, a shopping application, a search application, an instant messaging tool, a mailbox client, social platform software, and the like.
The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture experts Group Audio Layer III, mpeg compression standard Audio Layer 3), MP4 players (Moving Picture experts Group Audio Layer IV, mpeg compression standard Audio Layer 4), laptop portable computers, desktop computers, and the like.
The server 105 may be a server providing various services, such as a background server providing support for pages displayed on the terminal devices 101, 102, 103.
It should be noted that, the message pushing method provided in the embodiment of the present application is generally executed by a server, and accordingly, the client intention recognition device based on artificial intelligence is generally disposed in the server.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
With continuing reference to fig. 2, a flow diagram of one embodiment of a message push method in accordance with the present application is shown. The message pushing method comprises the following steps:
step S201, a message to be pushed is obtained, where the message includes a service order data set.
The message pushing method provided by this embodiment may be implemented by an MQ service platform (message queue service platform) disposed at a service end. The message queue server is a core component of the message queue service platform and provides core service for the message queue, namely the message queue server acquires a message to be pushed, wherein the message to be pushed is a message generated after a message production end receives a message production instruction of the message queue server. The file-in system is a system for receiving the service appeal of the client, and the file-in system converts the service appeal of the client into a message.
Further, the message production end is a component feeding system. That is, the incoming system issues the message to the sales system, and after the sales system receives the issued message, the sales system usually enters the message of the client into the sales system through the terminal by the salesperson, and the sales system sends the message to the message queue service platform and the message queue server processes the message. That is, the message is a piece-entering information, where the piece-entering information includes a service order data set, and the service order data set is composed of channel information, salesman information, customer information, node status, customer label, and the like, but in this embodiment, the service order data set may further include other information, such as: reservation information, etc., and is not limited herein.
In this embodiment, the electronic device (for example, the message queue server shown in fig. 1) on which the message pushing method operates may communicate with the sales system through a wired connection or a wireless connection. It should be noted that the wireless connection means may include, but is not limited to, a 3G/4G connection, a WiFi connection, a bluetooth connection, a WiMAX connection, a Zigbee connection, a uwb (ultra wideband) connection, and other wireless connection means now known or developed in the future.
Furthermore, each sales system corresponds to a plurality of message production terminals, that is, corresponds to a plurality of parts feeding systems, so that when a message issued by the parts feeding system is acquired, a message acquisition interface needs to be determined. Namely, the above steps may include:
step S2011, when the message production node of the message production end is turned over, determining a message acquisition interface corresponding to the message production end;
step S2012, a message sent by the message producing end is obtained from the message obtaining interface.
Because each sales system corresponds to a plurality of message production ends and is provided with a plurality of message acquisition interfaces, namely when a message production node of the message production end is turned over, namely the message production end has a service demand, the message acquisition interface corresponding to the message production end is determined first, so that the message sent by the message production end can be transmitted to the message queue server through the message acquisition interface. Namely, the message queue server can acquire the message issued by the message production end from the determined message acquisition interface so as to ensure the accuracy and timeliness of the message.
Since the message production end is a component feeding system, that is, the message production node in this embodiment is a component feeding node. And when the piece feeding node of the piece feeding system is overturned, determining a message acquisition interface corresponding to the piece feeding system.
Step S202, a preset rule engine is called to filter all the business order data in the business order data set to obtain filtered business order data, the filtered business order data is configured based on a preset template engine, and a push message body is generated.
In this embodiment, after the message queue server obtains the service order data set, a preset rule engine is called to filter all service order data in the service order data set to obtain filtered service order data, and the filtered service order data is configured based on a preset template engine to generate a push message body. Namely, the risk in the process of message configuration is reduced through the functions of the preset rule engine and the preset template engine.
It is emphasized that to further ensure privacy and security of the rule engine and template engine, the rule engine and template engine may also be stored in a node of a blockchain.
The block chain referred by the application is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.
Step S203, obtaining a data receiving object corresponding to the filtered service order data, and determining a receiving rule of the data receiving object, so as to filter the push data in the push message body according to the receiving rule, thereby obtaining a target message body.
In this embodiment, after the push message body is obtained, the push needs to be performed only by determining the object to be pushed. And determining a receiving rule of the data receiving object, and filtering the push data in the push message body according to the receiving rule to obtain a target message body.
In this embodiment, a node state obtained by filtering the service order data by a preset rule engine is obtained, and a target object corresponding to the node state is analyzed and used as a data receiving object. For example, the node state is a state to be signed, that is, the target object is a customer manager; the node state is a subscription failure state, namely the target object is a client manager and the upper level of the client manager.
After the data receiving objects are determined, because the authority of different data receiving objects is different, different data receiving objects have corresponding receiving rules, that is, the pushed message body can be pushed smoothly, the pushed message body needs to meet the receiving rules of the data receiving objects, that is, the pushed data in the pushed message body is filtered according to the receiving rules to obtain a target message body, so that the situation that the message cannot be pushed is prevented.
Further, after the data receiving object is obtained, the step of determining the receiving rule of the data receiving object includes:
receiving a registration request sent by the data receiving object;
and registering the data receiving object according to the registration request, and receiving the receiving rule sent by the data receiving object after the registration is successful.
That is, in this embodiment, after the data receiving object is determined and before the receiving rule of the data receiving object is acquired, the registration of the data receiving object may be accepted. After registration is complete, the receiving rules may be obtained from the data receiving object and stored. When storing the receiving rule, the receiving rule may be set according to actual needs, for example, the receiving rule may be a certain data table in a rule database. Here, security of message usage is ensured by registering a data reception object.
And receiving a registration request sent by the data receiving object to ensure the legality of the data receiving object. And registering the data receiving object according to the registration request, and receiving the receiving rule sent by the message producer after the registration is successful so as to obtain the receiving rule for determining the data receiving object.
Step S204, the target message body is pushed to the data receiving object.
In this embodiment, after a data receiving object and a target message body are obtained, the target message body is pushed to the data receiving object. The risk in the process of message configuration is reduced through the functions of the rule engine and the template engine, the time period and the cost of the message configuration can be reduced, and the interaction efficiency of the messages is improved.
Performing first filtering on all service order data in the service order data set through a preset rule engine to obtain service order data after the first filtering, and configuring the filtered service order data based on a preset template engine to generate a push message body; further, the push message body is filtered for the second time according to the receiving rule, so that the target data which can be received by the data receiving object is obtained, and the target message body is formed, namely, the time period and the cost of message configuration are reduced, and the message interaction efficiency is improved.
In the technical scheme provided by this embodiment, a message to be pushed is acquired, a preset rule engine is called to filter all service order data in a service order data set to obtain filtered service order data, the filtered service order data is configured based on a preset template engine to generate a pushed message body, a data receiving object corresponding to the filtered service order data is acquired, a receiving rule of the data receiving object is determined, the pushed data in the pushed message body is filtered according to the receiving rule to obtain a target message body, and the target message body is pushed to the data receiving object, so that a time period and cost of message configuration are reduced, and interaction efficiency of the message is improved.
Further, as shown in fig. 3, the step of calling a preset rule engine to filter all the service order data in the service order data set, and obtaining the filtered service order data includes:
s2021, acquiring service parameters corresponding to all service order data in the service order data set.
Specifically, business parameters corresponding to all business order data in the business order data set are obtained, wherein the business parameters can be represented by codes. Such as: when the service order data is the information of the service staff, the service parameter is salesman; when the service order data is customer information, the service parameter is a client; and other service order data are not listed here.
Further, when the number of the operator information is two, the service parameters corresponding to the two operator information are salesman-A, salesman-B, and so on, and when the number of the operator information is more than two, the corresponding service parameters are salesman-C, salesman-D, and so on, so that the service parameters corresponding to all the service order data in the service order data set can be obtained.
Of course, in this embodiment, the service parameter may also be represented in other forms, and is not limited herein.
And S2022, matching the service parameters with the parameters of each service rule in the preset rule engine, outputting the successfully matched service parameters, and taking the service order data corresponding to the successfully matched service parameters as the filtered service order data.
In this embodiment, after obtaining the service parameters corresponding to all the service order data in the service order data set, the service parameters are matched with the parameters of each service rule in the preset rule engine, the service parameters successfully matched are output, and the service order data corresponding to the service parameters successfully matched are used as the filtered service order data.
It is understood that there are a variety of business rules in the pre-defined rules engine. For example, the preset rule engine includes a channel rule, an operator rule, a customer rule, a node rule, a tag rule, and the like, which are not limited herein.
In this embodiment, the salesman rule includes a plurality of rule parameters. For example, the salesman rules include three rule parameters, namely salesman-B, salesman-E, salesman-H, that is, the salesman rules in the rule engine are composed of the rule parameters salesman-B, salesman-E, salesman-H. Therefore, the business parameters corresponding to all the business order data in the selected business order data set can be determined according to the business rules (parameters in the business rules), and the successfully matched business parameters are determined according to the matching results of the business parameters and the parameters of all the business rules in the preset rule engine, so that the filtering of the business order data is realized.
Further, after the successfully matched service parameters are output, the service order data corresponding to the successfully matched service parameters are used as the filtered service order data. For example, the salesman rules include three rule parameters, namely salesman-B, salesman-E, salesman-H, and the business parameters are salesman-A, salesman-B, at this time, the successfully matched business parameter is salesman-B, that is, the salesman information corresponding to the business parameter salesman-B is used as the filtered business order data.
In this embodiment, since a plurality of different business rules are configured in different rule engines, and the business rules are established based on rule parameters, it is necessary to configure rule parameters such as a channel rule, a salesman rule, a customer rule, a node rule, a label rule, and the like in advance, so that the rule engine for processing the business order data can be determined quickly, and the processing speed of the rule engine is increased.
Further, as shown in fig. 4, the step of configuring the filtered service order data based on a preset template engine and generating a push message body includes:
s2023, acquiring a data cleaning rule from the preset template engine;
s2024, performing data cleaning on the filtered business order data according to the data cleaning rule to obtain cleaned business order data;
and S2025, obtaining a message template associated with the cleaned service order data from the preset template engine, and performing format conversion on the cleaned service order data according to the message template to obtain the push message body.
In this embodiment, a preset template engine is provided with a data cleaning rule, that is, the data cleaning rule in the preset template engine is obtained first, so as to perform data cleaning on the filtered service order data according to the data cleaning rule, and obtain the cleaned service order data, thereby solving the problem that the service order data has different formats and cannot be processed.
For example, the filtered service order data includes channel information represented by formats a, B, and C, and the data cleaning rule is channel information satisfying the format a, that is, the channel information represented by formats B and C can be cleaned by performing data cleaning on the filtered service order data according to the data cleaning rule, and at this time, the channel information represented by format a is obtained, that is, the channel information meeting the processing condition obtained in this embodiment.
And after the cleaned service order data is obtained, obtaining a message template associated with the cleaned service order data from the preset template engine, and performing format conversion on the cleaned service order data according to the message template to obtain the push message body. Here, the preset template engine has a plurality of preconfigured message templates, and specifically, the message template may be configured by opening a template configuration panel of the template engine to configure the message template through the template configuration panel.
In this embodiment, in the process of configuring the message templates, each message template may define a template tag, so that the template tag associated with the cleaned service order data may be subsequently obtained from the preset template engine, and thus the message template associated with the service order data is obtained. At this time, format conversion may be performed on the cleaned service order data according to the acquired message template, so as to obtain the push message body.
Alternatively, the template tag may be a receiving object tag. That is, when the message template associated with the cleaned service order data is obtained, the data receiving object corresponding to the cleaned service order data may be obtained first, so as to obtain the receiving object tag associated with the data receiving object in the template engine, thereby obtaining the message template corresponding to the receiving object tag quickly and accurately.
Further, the S204 may include:
s2041, acquiring a receiving device of the data receiving object, and determining a push mode of the target message body according to attribute information of the receiving device, where the push mode includes: e-mail, short message or in-station information;
s2042, pushing the target message body to the data receiving object according to the pushing mode.
That is, in the present embodiment, when the target message body is pushed to the data receiving object, it is necessary to determine the pushing method so that the target message body can be accurately and quickly pushed to the data receiving object.
Specifically, receiving equipment of the data receiving object is obtained, and a pushing mode of the target message body is determined according to attribute information of the receiving equipment. Wherein, the pushing mode comprises: mail, text message, or in-station information. For example, if the attribute information of the receiving device is network connection information, and the network connection information is in a unified local area network with the message queue server, the pushing mode is in-station information.
And after the push mode of the target message body is acquired, the target message body is pushed to the data receiving object according to the push mode, so that the message can be pushed accurately and quickly.
Further, the S2042 may include:
s20421, after pushing the target message body to the data receiving object, if no acknowledgement information returned by the data receiving object is received, pushing the target message body to the data receiving object;
s20422, when the push times of the target message body are greater than the preset push times, generating a push failure notification, and sending the push failure notification to the message production end.
In this embodiment, after the target message body is pushed to the data receiving object, if the acknowledgement information returned by the data receiving object is not received, it indicates that the pushing is failed, and at this time, the target message body needs to be continuously pushed to the data receiving object.
Specifically, the target message body is pushed to the data receiving object according to the retransmission rule in the receiving rule. And the retransmission rules define whether retransmission is required, the number of retransmissions, and the repetition interval. If receiving the confirmation information returned by the data receiving object, indicating that the pushing is successful, and at the moment, the data receiving object processes the corresponding service task to the received target message body.
And when the push times of the target message body are greater than the push times (namely the retransmission times) set by the receiving rule, generating a push failure notice according to the message failure rule, and sending the push failure notice to the message production end. In this embodiment, the preset pushing times may be selected to be 5 times, or in other embodiments, the preset pushing times are set to be other numbers, which is not limited herein.
That is, after the target message body is pushed to the data receiving object, if the confirmation information returned by the data receiving object is not received, the target message body is pushed to the data receiving object according to the retransmission rule in the receiving rule, so as to realize the retransmission of the target message body. And when the pushing times of the target message body are greater than the pushing times set by the receiving rule, generating a pushing failure notice, and sending the pushing failure notice to the message production end to determine the pushing failure of the target message body.
That is, in this embodiment, by determining the push times of the target message body and comparing the push times with the preset push times, it is determined whether the target message body is pushed to the data receiving object according to the comparison result, so as to accurately determine the push result of the target message body.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the computer program is executed. The storage medium may be a non-volatile storage medium such as a magnetic disk, an optical disk, a Read-Only Memory (ROM), or a Random Access Memory (RAM).
It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least a portion of the steps in the flow chart of the figure may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
With further reference to fig. 5, as an implementation of the method shown in fig. 2, the present application provides an embodiment of a message-based pushing apparatus, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 2, and the apparatus may be specifically applied to various electronic devices.
As shown in fig. 5, the artificial intelligence based client intention recognition apparatus 300 according to this embodiment includes: an obtaining module 301, a filtering configuration module 302, a message filtering module 303, and a pushing module 304, wherein:
an obtaining module 301, configured to obtain a message to be pushed, where the message includes a service order data set;
a filtering configuration module 302, configured to invoke a preset rule engine to filter all the service order data in the service order data set, to obtain filtered service order data, and configure the filtered service order data based on a preset template engine, to generate a push message body;
a message filtering module 303, configured to obtain a data receiving object corresponding to the filtered service order data, and determine a receiving rule of the data receiving object, so as to filter the push data in the push message body according to the receiving rule, so as to obtain a target message body;
a pushing module 304, configured to push the target message body to the data receiving object.
In this embodiment, a message to be pushed is obtained, a preset rule engine is called to filter all service order data in a service order data set to obtain filtered service order data, the filtered service order data is configured based on a preset template engine to generate a pushed message body, a data receiving object corresponding to the filtered service order data is obtained, a receiving rule of the data receiving object is determined, the pushed data in the pushed message body is filtered according to the receiving rule to obtain a target message body, and the target message body is pushed to the data receiving object, so that a time period and cost of message configuration are reduced, and interaction efficiency of the message is improved.
In some optional implementations of this embodiment, the obtaining module 301 includes: a determining unit and a first obtaining unit, wherein:
and the determining unit is used for determining the message acquisition interface corresponding to the message production end when the message production node of the message production end is turned over.
And the first acquisition unit is used for acquiring the message sent by the message production end from the message acquisition interface.
In this embodiment, each sales system corresponds to a plurality of message production ends, and the sales system is provided with a plurality of message acquisition interfaces, that is, when a message production node of the message production end is turned over, that is, the message production end has a service demand, the message acquisition interface corresponding to the message production end is determined first, so that a message issued by the message production end can be transmitted to the message queue server through the message acquisition interface. Namely, the message queue server can acquire the message issued by the message production end from the determined message acquisition interface so as to ensure the accuracy and timeliness of the message.
In some optional implementations of this embodiment, the filtering configuration module 302 includes: a second acquisition unit and a matching unit, wherein:
and the second obtaining unit is used for obtaining the service parameters corresponding to all the service order data in the service order data set.
And the matching unit is used for matching the service parameters with the parameters of each service rule in the preset rule engine, outputting the successfully matched service parameters, and taking the service order data corresponding to the successfully matched service parameters as the filtered service order data.
In this embodiment, since a plurality of different business rules are configured in different rule engines, and the business rules are established based on rule parameters, it is necessary to configure rule parameters such as a channel rule, a salesman rule, a customer rule, a node rule, a label rule, and the like in advance, so that the rule engine for processing the business order data can be determined quickly, and the processing speed of the rule engine is increased.
In some optional implementations of this embodiment, the filtering configuration module 302 further includes: third acquisition unit, washing unit and conversion unit, wherein:
the third acquisition unit is used for acquiring a data cleaning rule from the preset template engine;
the cleaning unit is used for carrying out data cleaning on the filtered business order data through the data cleaning rule to obtain the cleaned business order data;
and the conversion unit is used for acquiring a message template associated with the cleaned service order data from the preset template engine, and performing format conversion on the cleaned service order data according to the message template to obtain the push message body.
In this embodiment, when the message template associated with the cleaned service order data is obtained, the data receiving object corresponding to the cleaned service order data may be obtained first, so as to obtain the receiving object tag associated with the data receiving object in the template engine, thereby obtaining the message template corresponding to the receiving object tag quickly and accurately.
In some optional implementations of this embodiment, the pushing module 304 includes: fourth acquisition unit and push unit, wherein:
a fourth obtaining unit, configured to obtain a receiving device of the data receiving object, and determine a push manner of the target message body according to attribute information of the receiving device, where the push manner includes: e-mail, short message or in-station information;
and the pushing unit is used for pushing the target message body to the data receiving object according to the pushing mode.
That is, in this embodiment, after the push method of the target message body is acquired, the target message body is pushed to the data receiving object according to the push method, so that message push can be performed accurately and quickly.
In some optional implementations of this embodiment, the pushing unit includes: screening unit, form acquisition unit, statistical unit and evaluation calculation subunit, wherein:
a confirmation subunit, configured to, after pushing the target message body to the data receiving object, if confirmation information returned by the data receiving object is not received, push the target message body to the data receiving object;
and the generating subunit is configured to generate a push failure notification when the push frequency of the target message body is greater than a preset push frequency, and send the push failure notification to the message production end.
In this embodiment, by determining the pushing times of the target message body and comparing the pushing times with the preset pushing times, whether the target message body is pushed to the data receiving object is determined according to the comparison result, so that the result of pushing the target message body can be accurately determined.
In order to solve the technical problem, an embodiment of the present application further provides a computer device. Referring to fig. 6, fig. 6 is a block diagram of a basic structure of a computer device according to the present embodiment.
The computer device 4 comprises a memory 41, a processor 42, a network interface 43 communicatively connected to each other via a system bus. It is noted that only computer device 4 having components 41-43 is shown, but it is understood that not all of the shown components are required to be implemented, and that more or fewer components may be implemented instead. As will be understood by those skilled in the art, the computer device is a device capable of automatically performing numerical calculation and/or information processing according to a preset or stored instruction, and the hardware includes, but is not limited to, a microprocessor, an Application Specific Integrated Circuit (ASIC), a Programmable Gate Array (FPGA), a Digital Signal Processor (DSP), an embedded device, and the like.
The computer device can be a desktop computer, a notebook, a palm computer, a cloud server and other computing devices. The computer equipment can carry out man-machine interaction with a user through a keyboard, a mouse, a remote controller, a touch panel or voice control equipment and the like.
The memory 41 includes at least one type of readable storage medium including a flash memory, a hard disk, a multimedia card, a card type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, etc. In some embodiments, the memory 41 may be an internal storage unit of the computer device 4, such as a hard disk or a memory of the computer device 4. In other embodiments, the memory 41 may also be an external storage device of the computer device 4, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the computer device 4. Of course, the memory 41 may also include both internal and external storage devices of the computer device 4. In this embodiment, the memory 41 is generally used for storing an operating system installed in the computer device 4 and various types of application software, such as computer readable instructions of a message pushing method. Further, the memory 41 may also be used to temporarily store various types of data that have been output or are to be output.
The processor 42 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data Processing chip in some embodiments. The processor 42 is typically used to control the overall operation of the computer device 4. In this embodiment, the processor 42 is configured to execute computer readable instructions stored in the memory 41 or process data, for example, execute computer readable instructions of the message pushing method.
The network interface 43 may comprise a wireless network interface or a wired network interface, and the network interface 43 is generally used for establishing communication connection between the computer device 4 and other electronic devices.
The computer device provided in this embodiment may perform the steps of the message pushing method. Here, the steps of the message pushing method may be steps in the message pushing methods of the above-described embodiments.
In the technical scheme provided by this embodiment, a message to be pushed is acquired, a preset rule engine is called to filter all service order data in a service order data set to obtain filtered service order data, the filtered service order data is configured based on a preset template engine to generate a pushed message body, a data receiving object corresponding to the filtered service order data is acquired, a receiving rule of the data receiving object is determined, the pushed data in the pushed message body is filtered according to the receiving rule to obtain a target message body, and the target message body is pushed to the data receiving object, so that a time period and cost of message configuration are reduced, and interaction efficiency of the message is improved.
The present application further provides another embodiment, which is to provide a storage medium storing computer readable instructions executable by at least one processor to cause the at least one processor to perform the steps of the message pushing method as described above.
In the technical scheme provided by this embodiment, a message to be pushed is acquired, a preset rule engine is called to filter all service order data in a service order data set to obtain filtered service order data, the filtered service order data is configured based on a preset template engine to generate a pushed message body, a data receiving object corresponding to the filtered service order data is acquired, a receiving rule of the data receiving object is determined, the pushed data in the pushed message body is filtered according to the receiving rule to obtain a target message body, and the target message body is pushed to the data receiving object, so that a time period and cost of message configuration are reduced, and interaction efficiency of the message is improved.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present application.
It is to be understood that the above-described embodiments are merely illustrative of some, but not restrictive, of the broad invention, and that the appended drawings illustrate preferred embodiments of the invention and do not limit the scope of the invention. This application is capable of embodiments in many different forms and is provided for the purpose of enabling a thorough understanding of the disclosure of the application. Although the present application has been described in detail with reference to the foregoing embodiments, it will be apparent to one skilled in the art that the present application may be practiced without modification or with equivalents of some of the features described in the foregoing embodiments. All equivalent structures made by using the contents of the specification and the drawings of the present application are directly or indirectly applied to other related technical fields and are within the protection scope of the present application.
Claims (10)
1. A message pushing method is characterized by comprising the following steps:
acquiring a message to be pushed, wherein the message to be pushed comprises a service order data set;
calling a preset rule engine to filter all the business order data in the business order data set to obtain filtered business order data, configuring the filtered business order data based on a preset template engine, and generating a push message body;
acquiring a data receiving object corresponding to the filtered business order data, determining a receiving rule of the data receiving object, and filtering the push data in the push message body according to the receiving rule to obtain a target message body;
and pushing the target message body to the data receiving object.
2. The message pushing method according to claim 1, wherein the step of calling a preset rule engine to filter all the service order data in the service order data set to obtain filtered service order data comprises:
acquiring service parameters corresponding to all service order data in the service order data set;
and matching the service parameters with the parameters of each service rule in the preset rule engine, outputting the successfully matched service parameters, and taking the service order data corresponding to the successfully matched service parameters as the filtered service order data.
3. The message pushing method according to claim 1, wherein the step of configuring the filtered service order data based on a preset template engine and generating a pushed message body comprises:
acquiring a data cleaning rule from the preset template engine;
performing data cleaning on the filtered service order data according to the data cleaning rule to obtain cleaned service order data;
and acquiring a message template associated with the cleaned service order data from the preset template engine, and performing format conversion on the cleaned service order data according to the message template to obtain the push message body.
4. The message pushing method according to claim 1, wherein the step of determining the receiving rule of the data receiving object comprises:
receiving a registration request sent by the data receiving object;
and registering the data receiving object according to the registration request, and receiving the receiving rule sent by the data receiving object after the registration is successful.
5. The message pushing method according to claim 1, wherein the step of pushing the target message body to the data receiving object comprises:
acquiring receiving equipment of the data receiving object, and determining a pushing mode of the target message body according to attribute information of the receiving equipment, wherein the pushing mode comprises the following steps: e-mail, short message or in-station information;
and pushing the target message body to the data receiving object according to the pushing mode.
6. The message pushing method according to claim 5, wherein the step of pushing the target message body to the data receiving object in the pushing manner comprises:
after the target message body is pushed to the data receiving object, if the confirmation information returned by the data receiving object is not received, the target message body is pushed to the data receiving object;
and when the pushing times of the target message body are greater than the preset pushing times, generating a pushing failure notice, and sending the pushing failure notice to a message production end.
7. The message pushing method according to claim 6, wherein the step of acquiring the message to be pushed comprises:
when the message production node of the message production end is turned over, determining a message acquisition interface corresponding to the message production end;
and acquiring the message sent by the message production end from the message acquisition interface.
8. A message push apparatus, comprising:
the system comprises an acquisition module, a push module and a push module, wherein the acquisition module is used for acquiring a message to be pushed, and the message comprises a service order data set;
the filtering configuration module is used for calling a preset rule engine to filter all the business order data in the business order data set to obtain filtered business order data, configuring the filtered business order data based on a preset template engine, and generating a push message body;
the message filtering module is used for acquiring a data receiving object corresponding to the filtered business order data, determining a receiving rule of the data receiving object, and filtering the push data in the push message body according to the receiving rule to obtain a target message body;
and the pushing module is used for pushing the target message body to the data receiving object.
9. A computer device comprising a memory having computer readable instructions stored therein and a processor which when executed implements the steps of the message push method of any of claims 1 to 7.
10. A storage medium having stored thereon computer readable instructions which, when executed by a processor, carry out the steps of the message push method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210029851.3A CN114374737A (en) | 2022-01-12 | 2022-01-12 | Message pushing method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210029851.3A CN114374737A (en) | 2022-01-12 | 2022-01-12 | Message pushing method and device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114374737A true CN114374737A (en) | 2022-04-19 |
Family
ID=81143543
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210029851.3A Pending CN114374737A (en) | 2022-01-12 | 2022-01-12 | Message pushing method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114374737A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116384956A (en) * | 2023-06-05 | 2023-07-04 | 天津金城银行股份有限公司 | Message batch sending method, device, equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109787882A (en) * | 2018-12-28 | 2019-05-21 | 广东益萃网络科技有限公司 | Information push method, device, computer equipment and storage medium |
| CN111967236A (en) * | 2020-07-30 | 2020-11-20 | 武汉联影医疗科技有限公司 | Message processing method and device, computer equipment and storage medium |
| CN112437000A (en) * | 2020-11-16 | 2021-03-02 | 平安信托有限责任公司 | Message queue pushing method and device, computer equipment and storage medium |
-
2022
- 2022-01-12 CN CN202210029851.3A patent/CN114374737A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109787882A (en) * | 2018-12-28 | 2019-05-21 | 广东益萃网络科技有限公司 | Information push method, device, computer equipment and storage medium |
| CN111967236A (en) * | 2020-07-30 | 2020-11-20 | 武汉联影医疗科技有限公司 | Message processing method and device, computer equipment and storage medium |
| CN112437000A (en) * | 2020-11-16 | 2021-03-02 | 平安信托有限责任公司 | Message queue pushing method and device, computer equipment and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116384956A (en) * | 2023-06-05 | 2023-07-04 | 天津金城银行股份有限公司 | Message batch sending method, device, equipment and storage medium |
| CN116384956B (en) * | 2023-06-05 | 2023-08-15 | 天津金城银行股份有限公司 | Message batch sending method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112162965B (en) | Log data processing method, device, computer equipment and storage medium | |
| CN112052111A (en) | Processing method, device and equipment for server abnormity early warning and storage medium | |
| CN112184169A (en) | Dynamic planning method, device, equipment and storage medium for user backlogs | |
| CN110688828A (en) | File processing method and device, file processing system and computer equipment | |
| CN113268336A (en) | Service acquisition method, device, equipment and readable medium | |
| CN114564294A (en) | Intelligent service arranging method and device, computer equipment and storage medium | |
| CN112631884A (en) | Pressure measurement method and device based on data synchronization, computer equipment and storage medium | |
| CN112631751A (en) | Task scheduling method and device, computer equipment and storage medium | |
| CN112468409A (en) | Access control method, device, computer equipment and storage medium | |
| CN112631911A (en) | Automatic testing method and device, computer equipment and storage medium | |
| CN109547322A (en) | System prompt control method, device, computer and computer readable storage medium | |
| CN114281552A (en) | Task scheduling method, device, equipment and medium based on directed acyclic graph | |
| CN114374737A (en) | Message pushing method and device, computer equipment and storage medium | |
| CN112860662A (en) | Data blood relationship establishing method and device, computer equipment and storage medium | |
| CN109299173A (en) | Data transmission method, device and storage medium | |
| CN114356335A (en) | Data processing method, device, equipment and medium | |
| CN112988311A (en) | On-line experimental method based on WEB server | |
| CN116956326A (en) | Authority data processing method and device, computer equipment and storage medium | |
| CN113489714B (en) | Multi-module-based intelligent message cross processing method and system | |
| WO2023066258A1 (en) | Data processing method and apparatus for private data, computer device and medium | |
| CN114281817A (en) | Data cleaning method and device, computer equipment and storage medium | |
| CN114615325A (en) | Message pushing method and device, computer equipment and storage medium | |
| CN114168552A (en) | Space sharing method and device based on block chain technology and computer equipment | |
| CN113590243A (en) | Energy enterprise project creation method and device, computer equipment and medium | |
| CN113779984A (en) | Information processing method, device, server and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |