System, method and device for realizing multi-scene automatic message pushing for operation business, processor and readable storage medium thereof

Abstract

The invention relates to a system for realizing multi-scene automatic message pushing for an operation service. The system comprises a short message and mail template configuration module which configures short message and mail sending templates in different scenes; the flow scanning module is used for regularly collecting service flows for sending short messages and mails according to the timestamps; the short message and mail template matching module is used for matching a unique short message and mail sending template for the service flow; the short message and mail content calculation module calculates short message and mail information needing to be sent to a client; and the short message and mail sending module pushes the final short message and mail information to the client. By adopting the system, the method, the device, the processor and the computer readable storage medium for realizing the multi-scene automatic message pushing aiming at the operation business, a unified management business handling short message and mail sending function is provided, the short message and mail sending content is calculated according to the short message and mail rule and the client is notified; and service handling short message and mail notification in diversified, specific and combined scenes of customer message receiving modes is met.

Description

Technical Field

[0001] This invention relates to the field of operational business, and more particularly to the field of message push systems. Specifically, it refers to a system, method, apparatus, processor, and computer-readable storage medium for realizing automated message push in multiple scenarios for operational business. Background Technology

[0002] The centralized operation system serves as a unified entry point for counter and online business processing. After a transaction is completed, customers are notified of the transaction status via SMS and guided to subsequent business procedures. However, given the diverse nature of business processing scenarios, existing SMS sending functions suffer from fragmented management and limited functionality across different components, only handling cases where the entire transaction is successful or unsuccessful. This invention proposes a multi-scenario automated message push system for operational business, unifying the management of SMS and email sending across various business scenarios, designing universal SMS and email sending rules, calculating the content for different scenarios, connecting to a unified SMS and email sending platform to inform customers of their business processing status, and implementing SMS and email distribution traffic control. Summary of the Invention

[0003] The purpose of this invention is to overcome the shortcomings of the prior art and provide a system, method, device, processor and its computer-readable storage medium for automated message push in multiple scenarios for operational business, which is personalized, easy to operate and widely applicable.

[0004] To achieve the above objectives, the present invention provides a system, method, apparatus, processor, and computer-readable storage medium for implementing automated message push in multiple scenarios for operational business, as follows: This system, designed for automated message push across multiple scenarios in operational business, is characterized by the following features: The SMS and email template configuration module is used to configure SMS and email sending templates for different scenarios. It supports configuring different templates based on business category, business initiation channel, customer scope or other factors that need to be met. The transaction scanning module is connected to the SMS and email template configuration module and is used to collect the transaction data of the business processing system. The scheduled task collects a fixed number of transaction data involving sending SMS and email according to the timestamp and generates SMS and email matching tasks. The SMS and email template matching module is connected to the transaction scanning module. It is used to query all SMS and email template configurations according to the business category and business initiation channel of the business transaction, and to match SMS and email templates according to customer scope, business completion status and other elements that need to meet the conditions. The SMS and email content calculation module is connected to the SMS and email template matching module and is used to replace the general identifiers in the SMS and email templates to calculate the SMS and email information that needs to be sent to the customer. The SMS and email sending module is connected to the SMS and email content calculation module. It is used to collect the tasks to be sent in the SMS and email sending task table, and send the SMS and email to the mobile phone number or email address left by the customer in the system to inform the customer of the business processing status and guide the subsequent business processing matters. The SMS and email traffic control module, connected to the SMS and email sending module, is used to control the quantity and speed of SMS and email sending based on the maximum number of transactions obtained from the transaction flow, the number of SMS and email sending threads, and the trigger time and frequency of the scheduled tasks.

[0005] Preferably, the SMS and email template configuration module supports single-process template configuration mode, single-combination process template configuration mode, and multi-combination process template configuration mode. The single-process template configuration mode is used to configure business categories, initiation channels, customer scope, business completion status, or other elements that need to meet certain conditions. The single-combination process template configuration mode is used to configure a parent template and several child templates. The combination process identifier of the parent template is configured to be empty, and the parent template identifier is configured to be its own template ID. The SMS and email templates are configured to be combinations of SMS and email templates in the child templates. The parent template identifier of the child template is configured to be the parent template ID, the combination process identifier is configured to be empty, and other information is configured in the same way as the single-combination process template configuration mode. The multi-combination process template configuration mode is used to configure a parent template and several child templates. The parent template identifier of the parent template is configured to be empty, the combination process identifier is configured to be a combination of multiple child templates, and the SMS and email templates are configured to be a combination of SMS and email templates in the child templates. The parent template identifier of the child template is configured to be the parent template id, the combination process identifier is configured to be empty, and other information is configured in the same way as the single process template configuration mode.

[0006] Preferably, the transaction scanning module collects transaction data from the business processing system, and the scheduled task collects a fixed number of transaction data involving sending SMS and emails at regular intervals based on timestamps, generating SMS and email matching tasks, specifically including the following steps: (2.1) Configure parameters to obtain the maximum number of transactions and the start timestamp for scanning SMS and email transaction records; (2.2) Execute the task at regular intervals to collect business transactions in the business transaction table that have completed status, whose status update timestamp is greater than the start timestamp of SMS and email transaction scanning, and whose corresponding business category is configured in the SMS and email template table. Sort the transactions in ascending order of status update timestamp and the number of transactions to be collected is the configured value of the maximum number of transactions to be collected. (2.3) The collected business transaction records are then assigned to the SMS and email matching task table; (2.4) Update the start timestamp of SMS and email transaction scanning to the maximum value of the status update timestamp in the transaction data collection.

[0007] Preferably, the SMS and email template matching module queries all SMS and email template configurations based on the business category and business initiation channel of the business flow, and matches the SMS and email templates according to the customer scope, business completion status, and other elements that need to meet the conditions. Specifically, it includes the following steps: (3.1) Poll the business transaction records in the SMS and email matching task table, and retrieve the application information of the transaction record from the business transaction record table based on the transaction record ID; (3.2) Query the SMS and email template configuration table according to the business category and initiation channel of the transaction to obtain all template configurations; (3.3) Polling template configuration.

[0008] Preferably, the SMS and email template matching module polls the template configuration, specifically including the following steps: (3.3.1) If the template type is a single process template, determine whether the customer scope, business completion status and other elements that need to meet the conditions in the flow information are consistent with the template configuration. If they are consistent, update the SMS and email templates to the matching task table. (3.3.2) If the template type is a single combination process template, determine whether the customer scope, business completion status and other elements that need to meet the conditions in the flow information are consistent with the parent template. If they are consistent, obtain all child template configurations based on the parent template ID, poll to obtain the SMS and email templates in all matching child templates, and splice the final SMS and email templates to update the matching task table. (3.3.3) If the template type is a multi-combination process template, determine whether the customer scope, business completion status and other elements that need to meet the conditions in the flow information are consistent with the parent template. If they are consistent, obtain all sub-template combinations configured in the combination process identifier of the parent template; determine whether any sub-template combination is completely matched. If it is matched, obtain the SMS and email templates in the sub-templates, and concatenate the final SMS and email templates to update the matching task table; if any process in the aforementioned matching process does not match, end the current polling and continue polling other templates.

[0009] Preferably, the SMS and email content calculation module replaces the generic identifiers in the SMS and email templates, and calculates the final SMS and email information to be sent to the customer, specifically including the following steps: (4.1) Poll the business transaction records of SMS and email matching task table, and retrieve the application information of the transaction record from the business transaction record table according to the transaction record ID; (4.2) Replace the generic identifiers in SMS and email templates with sequential application information; (4.3) Replace the specific identifiers of the corresponding business categories in the SMS and email templates according to the different business categories, and calculate the final SMS and email information sent to the customer; (4.4) Record the transaction ID, SMS and email content, and SMS and email recipients in the SMS and email sending task table, and set the task status to pending sending.

[0010] Preferably, the SMS and email sending module collects tasks to be sent from the SMS and email sending task table, and sends the SMS and email to the mobile phone number or email address registered with the customer in the system, informing them of the business processing status and guiding them through subsequent business processing matters. Specifically, it includes the following steps: (5.1) Execute tasks on a schedule, collect tasks with the status of "to be sent" in the SMS and email sending task table, and start the corresponding number of threads to process the tasks to be sent according to the configured number of SMS and email sending threads. (5.2) Query the transaction ID, SMS and email content, and SMS and email recipient in the SMS and email sending task table according to the task ID. If the mobile phone number and the unique identifier of the account are both empty, do not send an SMS; otherwise, continue to steps (5.3) to (5.4). If the email address is empty, do not send an email; otherwise, continue to step (5.5). (5.3) Calculate the length of the SMS content. Split SMS messages exceeding 230 bytes into two messages. The first 230 bytes are the first message, and the rest are the second message. (5.4) Query the SMS sending log table based on the transaction ID. If the current transaction ID has already sent an SMS, do not process it; otherwise, connect to the SMS sending platform to send an SMS to the customer, update the task status to sent, and record the transaction ID in the SMS sending log table. (5.5) Query the email sending log table based on the log ID. If the current log ID has already sent an email, do not process it; otherwise, connect to the email sending platform to send an email to the customer, update the task status to sent, and record the log ID in the email sending log table.

[0011] Preferably, the SMS and email traffic control module controls the quantity and speed of SMS and email sending based on the maximum number of transactions obtained from the transaction log, the number of SMS and email sending threads, and the trigger time and frequency of the scheduled tasks. Specifically, this includes the following steps: (6.1) Configure the transaction log to obtain the corresponding value of the maximum number of transactions based on the number of transactions; (6.2) Configure the trigger time and frequency of the timed task for the timed scanning of the business flow based on the volume of business flow; (6.3) Start the corresponding number of threads to process SMS and email sending tasks according to the configured number of SMS and email sending threads; (6.4) Set the trigger time of SMS and email sending timed tasks to maintain a certain interval with the trigger time of pipeline scanning timed tasks. The number and speed of SMS and email sending are controlled by configuring the trigger time and frequency of the two timed tasks.

[0012] The main feature of this method for achieving automated message push across multiple scenarios in operational business is that the method includes the following steps: (1) The SMS and email template configuration module configures different templates according to the business category, business initiation channel, customer scope or other elements that need to meet the conditions; (2) The flow scanning module collects the business flow of the business processing system. The timed task collects a fixed number of business flow involving sending SMS and email according to the timestamp, and generates SMS and email matching tasks. (3) The SMS and email template matching module queries all SMS and email template configurations based on the business category and business initiation channel of the business flow, and matches SMS and email templates based on customer scope, business completion status and other elements that need to meet the conditions. (4) The SMS and email content calculation module replaces the general identifier in the SMS and email templates and calculates the SMS and email information that needs to be sent to the customer. (5) The SMS and email sending module collects the tasks to be sent in the SMS and email sending task table, and sends the SMS and email to the mobile phone number or email address left by the customer in the system, informing them of the business processing status and guiding them to subsequent business processing matters. (6) The SMS and email traffic control module controls the quantity and speed of SMS and email sending based on the maximum number of transactions obtained from the transaction log, the number of SMS and email sending threads, and the trigger time and frequency of the scheduled tasks.

[0013] Preferably, step (2) specifically includes the following steps: (2.1) Configure parameters to obtain the maximum number of transactions and the start timestamp for scanning SMS and email transaction records; (2.2) Execute the task at regular intervals to collect business transactions in the business transaction table that have completed status, whose status update timestamp is greater than the start timestamp of SMS and email transaction scanning, and whose corresponding business category is configured in the SMS and email template table. Sort the transactions in ascending order of status update timestamp and the number of transactions to be collected is the configured value of the maximum number of transactions to be collected. (2.3) The collected business transaction records are then assigned to the SMS and email matching task table; (2.4) Update the start timestamp of SMS and email transaction scanning to the maximum value of the status update timestamp in the transaction data collection.

[0014] Preferably, step (3) specifically includes the following steps: (3.1) Poll the business transaction records in the SMS and email matching task table, and retrieve the application information of the transaction record from the business transaction record table based on the transaction record ID; (3.2) Query the SMS and email template configuration table according to the business category and initiation channel of the transaction to obtain all template configurations; (3.3) Poll the template configuration and match the SMS and email templates corresponding to the transaction.

[0015] Preferably, step (4) specifically includes the following steps: (4.1) Poll the business transaction records of SMS and email matching task table, and retrieve the application information of the transaction record from the business transaction record table according to the transaction record ID; (4.2) Replace the generic identifiers in SMS and email templates with sequential application information; (4.3) Replace the specific identifiers of the corresponding business categories in the SMS and email templates according to the different business categories, and calculate the final SMS and email information sent to the customer; (4.4) Record the transaction ID, SMS and email content, and SMS and email recipients in the SMS and email sending task table, and set the task status to pending sending.

[0016] Preferably, step (5) specifically includes the following steps: (5.1) Execute tasks on a schedule, collect tasks with the status of "to be sent" in the SMS and email sending task table, and start the corresponding number of threads to process the tasks to be sent according to the configured number of SMS and email sending threads. (5.2) Query the transaction ID, SMS and email content, and SMS and email recipient in the SMS and email sending task table according to the task ID. If the mobile phone number and the unique identifier of the account are both empty, do not send an SMS; otherwise, continue to steps (5.3) to (5.4). If the email address is empty, do not send an email; otherwise, continue to step (5.5). (5.3) Calculate the length of the SMS content. Split SMS messages exceeding 230 bytes into two messages. The first 230 bytes are the first message, and the rest are the second message. (5.4) Query the SMS sending log table based on the transaction ID. If the current transaction ID has already sent an SMS, do not process it; otherwise, connect to the SMS sending platform to send an SMS to the customer, update the task status to sent, and record the transaction ID in the SMS sending log table. (5.5) Query the email sending log table based on the log ID. If the current log ID has already sent an email, do not process it; otherwise, connect to the email sending platform to send an email to the customer, update the task status to sent, and record the log ID in the email sending log table.

[0017] Preferably, step (6) specifically includes the following steps: (6.1) Configure the transaction log to obtain the corresponding value of the maximum number of transactions based on the number of transactions; (6.2) Configure the trigger time and frequency of the timed task for the timed scanning of the business flow based on the volume of business flow; (6.3) Start the corresponding number of threads to process SMS and email sending tasks according to the configured number of SMS and email sending threads; (6.4) Set the trigger time of SMS and email sending timed tasks to maintain a certain interval with the trigger time of pipeline scanning timed tasks. The number and speed of SMS and email sending are controlled by configuring the trigger time and frequency of the two timed tasks.

[0018] The device for automating message push in multiple scenarios for operational business is characterized by the following features: A processor is configured to execute computer-executable instructions; The memory stores one or more computer-executable instructions, which, when executed by the processor, implement the various steps of the method described above for implementing automated message push for multi-scenario operations.

[0019] The processor for implementing automated message push for multiple scenarios in operational business is characterized in that the processor is configured to execute computer-executable instructions, and when the computer-executable instructions are executed by the processor, the various steps of the above-mentioned method for implementing automated message push for multiple scenarios in operational business are realized.

[0020] The main feature of this computer-readable storage medium is that it stores a computer program thereon, which can be executed by a processor to implement the various steps of the above-described method for implementing automated message push for multi-scenario operations.

[0021] The present invention provides a system, method, apparatus, processor, and computer-readable storage medium for automated message push in multiple scenarios for operational business. In the context of diversified business scenarios and customized customer needs, the message push system provides unified management of business processing SMS and email sending functions, calculates SMS and email sending content according to general SMS and email rules and notifies customers, and meets the diverse needs of customers for receiving messages and business processing SMS and email notifications in specific and combined scenarios. Attached Figure Description

[0022] Figure 1 This is a flowchart of the pipeline scanning module of the system for implementing automated message push in multiple scenarios for operational business, as described in this invention.

[0023] Figure 2This is a flowchart of the SMS and email template matching module of the system for automated message push in multiple scenarios for operational business, as described in this invention.

[0024] Figure 3 This is a flowchart of the SMS and email content calculation module of the system for implementing automated message push in multiple scenarios for operational business, as described in this invention.

[0025] Figure 4 This is a flowchart of the SMS sending process in the SMS and email sending module of the system for automated message push in multiple scenarios for operational business, as described in this invention.

[0026] Figure 5 This is a flowchart of the email sending process in the SMS and email sending module of the system for automated message push in multiple scenarios for operational business, as described in this invention.

[0027] Figure 6 This is a flowchart illustrating the module interaction of the system for implementing automated message push in multiple scenarios for operational business, as described in this invention. Detailed Implementation

[0028] To more clearly describe the technical content of the present invention, the following description is provided in conjunction with specific embodiments.

[0029] The present invention discloses a system for automated message push in multiple scenarios for operational business, comprising: The SMS and email template configuration module is used to configure SMS and email sending templates for different scenarios. It supports configuring different templates based on business category, business initiation channel, customer scope or other factors that need to be met. The transaction scanning module is connected to the SMS and email template configuration module and is used to collect the transaction data of the business processing system. The scheduled task collects a fixed number of transaction data involving sending SMS and email according to the timestamp and generates SMS and email matching tasks. The SMS and email template matching module is connected to the transaction scanning module. It is used to query all SMS and email template configurations according to the business category and business initiation channel of the business transaction, and to match SMS and email templates according to customer scope, business completion status and other elements that need to meet the conditions. The SMS and email content calculation module is connected to the SMS and email template matching module and is used to replace the general identifiers in the SMS and email templates to calculate the SMS and email information that needs to be sent to the customer. The SMS and email sending module is connected to the SMS and email content calculation module. It is used to collect the tasks to be sent in the SMS and email sending task table, and send the SMS and email to the mobile phone number or email address left by the customer in the system to inform the customer of the business processing status and guide the subsequent business processing matters. The SMS and email traffic control module, connected to the SMS and email sending module, is used to control the quantity and speed of SMS and email sending based on the maximum number of transactions obtained from the transaction flow, the number of SMS and email sending threads, and the trigger time and frequency of the scheduled tasks.

[0030] In a preferred embodiment of the present invention, the SMS and email template configuration module supports single-process template configuration mode, single-combination process template configuration mode, and multi-combination process template configuration mode. The single-process template configuration mode is used to configure business categories, initiation channels, customer scope, business completion status, or other elements that need to meet certain conditions. The single-combination process template configuration mode is used to configure a parent template and several child templates. The combination process identifier of the parent template is configured to be empty, and the parent template identifier is configured to be its own template ID. The SMS and email templates are configured to be combinations of SMS and email templates in the child templates. The parent template identifier of the child template is configured to be the parent template ID, the combination process identifier is configured to be empty, and other information is configured in the same way as the single-combination process template configuration mode. The multi-combination process template configuration mode is used to configure a parent template and several child templates. The parent template identifier of the parent template is configured to be empty, the combination process identifier is configured to be a combination of multiple child templates, and the SMS and email templates are configured to be a combination of SMS and email templates in the child templates. The parent template identifier of the child template is configured to be the parent template id, the combination process identifier is configured to be empty, and other information is configured in the same way as the single process template configuration mode.

[0031] In a preferred embodiment of the present invention, the transaction scanning module collects transaction data from the business processing system, and the scheduled task collects a fixed number of transaction data involving SMS and email sending based on timestamps, generating an SMS and email matching task, specifically including the following steps: (2.1) Configure parameters to obtain the maximum number of transactions and the start timestamp for scanning SMS and email transaction records; (2.2) Execute the task at regular intervals to collect business transactions in the business transaction table that have completed status, whose status update timestamp is greater than the start timestamp of SMS and email transaction scanning, and whose corresponding business category is configured in the SMS and email template table. Sort the transactions in ascending order of status update timestamp and the number of transactions to be collected is the configured value of the maximum number of transactions to be collected. (2.3) The collected business transaction records are then assigned to the SMS and email matching task table; (2.4) Update the start timestamp of SMS and email transaction scanning to the maximum value of the status update timestamp in the transaction data collection.

[0032] In a preferred embodiment of the present invention, the SMS and email template matching module queries all SMS and email template configurations based on the business category and business initiation channel of the business flow, and matches and obtains SMS and email templates based on customer scope, business completion status, and other elements that need to meet the conditions. Specifically, it includes the following steps: (3.1) Poll the business transaction records in the SMS and email matching task table, and retrieve the application information of the transaction record from the business transaction record table based on the transaction record ID; (3.2) Query the SMS and email template configuration table according to the business category and initiation channel of the transaction to obtain all template configurations; (3.3) Polling template configuration.

[0033] In a preferred embodiment of the present invention, the SMS and email template matching module polls the template configuration, specifically including the following steps: (3.3.1) If the template type is a single process template, determine whether the customer scope, business completion status and other elements that need to meet the conditions in the flow information are consistent with the template configuration. If they are consistent, update the SMS and email templates to the matching task table. (3.3.2) If the template type is a single combination process template, determine whether the customer scope, business completion status and other elements that need to meet the conditions in the flow information are consistent with the parent template. If they are consistent, obtain all child template configurations based on the parent template ID, poll to obtain the SMS and email templates in all matching child templates, and splice the final SMS and email templates to update the matching task table. (3.3.3) If the template type is a multi-combination process template, determine whether the customer scope, business completion status and other elements that need to meet the conditions in the flow information are consistent with the parent template. If they are consistent, obtain all sub-template combinations configured in the combination process identifier of the parent template; determine whether any sub-template combination is completely matched. If it is matched, obtain the SMS and email templates in the sub-templates, and concatenate the final SMS and email templates to update the matching task table; if any process in the aforementioned matching process does not match, end the current polling and continue polling other templates.

[0034] In a preferred embodiment of the present invention, the SMS and email content calculation module replaces the generic identifiers in the SMS and email templates and calculates the final SMS and email information to be sent to the customer, specifically including the following steps: (4.1) Poll the business transaction records of SMS and email matching task table, and retrieve the application information of the transaction record from the business transaction record table according to the transaction record ID; (4.2) Replace the generic identifiers in SMS and email templates with sequential application information; (4.3) Replace the specific identifiers of the corresponding business categories in the SMS and email templates according to the different business categories, and calculate the final SMS and email information sent to the customer; (4.4) Record the transaction ID, SMS and email content, and SMS and email recipients in the SMS and email sending task table, and set the task status to pending sending.

[0035] In a preferred embodiment of the present invention, the SMS and email sending module collects the tasks to be sent from the SMS and email sending task table, and sends the SMS and email to the mobile phone number or email address registered by the customer in the system, informing the customer of the business processing status and guiding them through subsequent business processing matters. Specifically, it includes the following steps: (5.1) Execute tasks on a schedule, collect tasks with the status of "to be sent" in the SMS and email sending task table, and start the corresponding number of threads to process the tasks to be sent according to the configured number of SMS and email sending threads. (5.2) Query the transaction ID, SMS and email content, and SMS and email recipient in the SMS and email sending task table according to the task ID. If the mobile phone number and the unique identifier of the account are both empty, do not send an SMS; otherwise, continue to steps (5.3) to (5.4). If the email address is empty, do not send an email; otherwise, continue to step (5.5). (5.3) Calculate the length of the SMS content. Split SMS messages exceeding 230 bytes into two messages. The first 230 bytes are the first message, and the rest are the second message. (5.4) Query the SMS sending log table based on the transaction ID. If the current transaction ID has already sent an SMS, do not process it; otherwise, connect to the SMS sending platform to send an SMS to the customer, update the task status to sent, and record the transaction ID in the SMS sending log table. (5.5) Query the email sending log table based on the log ID. If the current log ID has already sent an email, do not process it; otherwise, connect to the email sending platform to send an email to the customer, update the task status to sent, and record the log ID in the email sending log table.

[0036] In a preferred embodiment of the present invention, the SMS and email traffic control module controls the quantity and speed of SMS and email sending based on the maximum number of transactions obtained from the transaction log, the number of SMS and email sending threads, and the trigger time and frequency of the scheduled task. Specifically, this includes the following steps: (6.1) Configure the transaction log to obtain the corresponding value of the maximum number of transactions based on the number of transactions; (6.2) Configure the trigger time and frequency of the timed task for the timed scanning of the business flow based on the volume of business flow; (6.3) Start the corresponding number of threads to process SMS and email sending tasks according to the configured number of SMS and email sending threads; (6.4) Set the trigger time of SMS and email sending timed tasks to maintain a certain interval with the trigger time of pipeline scanning timed tasks. The number and speed of SMS and email sending are controlled by configuring the trigger time and frequency of the two timed tasks.

[0037] The present invention provides a method for implementing automated message push for multiple scenarios in operational business using the aforementioned system, comprising the following steps: (1) The SMS and email template configuration module configures different templates according to the business category, business initiation channel, customer scope or other elements that need to meet the conditions; (2) The flow scanning module collects the business flow of the business processing system. The timed task collects a fixed number of business flow involving sending SMS and email according to the timestamp, and generates SMS and email matching tasks. (3) The SMS and email template matching module queries all SMS and email template configurations based on the business category and business initiation channel of the business flow, and matches SMS and email templates based on customer scope, business completion status and other elements that need to meet the conditions. (4) The SMS and email content calculation module replaces the general identifier in the SMS and email templates and calculates the SMS and email information that needs to be sent to the customer. (5) The SMS and email sending module collects the tasks to be sent in the SMS and email sending task table, and sends the SMS and email to the mobile phone number or email address left by the customer in the system, informing them of the business processing status and guiding them to subsequent business processing matters. (6) The SMS and email traffic control module controls the quantity and speed of SMS and email sending based on the maximum number of transactions obtained from the transaction log, the number of SMS and email sending threads, and the trigger time and frequency of the scheduled tasks.

[0038] In a preferred embodiment of the present invention, step (2) specifically includes the following steps: (2.1) Configure parameters to obtain the maximum number of transactions and the start timestamp for scanning SMS and email transaction records; (2.2) Execute the task at regular intervals to collect business transactions in the business transaction table that have completed status, whose status update timestamp is greater than the start timestamp of SMS and email transaction scanning, and whose corresponding business category is configured in the SMS and email template table. Sort the transactions in ascending order of status update timestamp and the number of transactions to be collected is the configured value of the maximum number of transactions to be collected. (2.3) The collected business transaction records are then assigned to the SMS and email matching task table; (2.4) Update the start timestamp of SMS and email transaction scanning to the maximum value of the status update timestamp in the transaction data collection.

[0039] In a preferred embodiment of the present invention, step (3) specifically includes the following steps: (3.1) Poll the business transaction records in the SMS and email matching task table, and retrieve the application information of the transaction record from the business transaction record table based on the transaction record ID; (3.2) Query the SMS and email template configuration table according to the business category and initiation channel of the transaction to obtain all template configurations; (3.3) Poll the template configuration and match the SMS and email templates corresponding to the transaction.

[0040] In a preferred embodiment of the present invention, step (4) specifically includes the following steps: (4.1) Poll the business transaction records of SMS and email matching task table, and retrieve the application information of the transaction record from the business transaction record table according to the transaction record ID; (4.2) Replace the generic identifiers in SMS and email templates with sequential application information; (4.3) Replace the specific identifiers of the corresponding business categories in the SMS and email templates according to the different business categories, and calculate the final SMS and email information sent to the customer; (4.4) Record the transaction ID, SMS and email content, and SMS and email recipients in the SMS and email sending task table, and set the task status to pending sending.

[0041] In a preferred embodiment of the present invention, step (5) specifically includes the following steps: (5.1) Execute tasks on a schedule, collect tasks with the status of "to be sent" in the SMS and email sending task table, and start the corresponding number of threads to process the tasks to be sent according to the configured number of SMS and email sending threads. (5.2) Query the transaction ID, SMS and email content, and SMS and email recipient in the SMS and email sending task table according to the task ID. If the mobile phone number and the unique identifier of the account are both empty, do not send an SMS; otherwise, continue to steps (5.3) to (5.4). If the email address is empty, do not send an email; otherwise, continue to step (5.5). (5.3) Calculate the length of the SMS content. Split SMS messages exceeding 230 bytes into two messages. The first 230 bytes are the first message, and the rest are the second message. (5.4) Query the SMS sending log table based on the transaction ID. If the current transaction ID has already sent an SMS, do not process it; otherwise, connect to the SMS sending platform to send an SMS to the customer, update the task status to sent, and record the transaction ID in the SMS sending log table. (5.5) Query the email sending log table based on the log ID. If the current log ID has already sent an email, do not process it; otherwise, connect to the email sending platform to send an email to the customer, update the task status to sent, and record the log ID in the email sending log table.

[0042] In a preferred embodiment of the present invention, step (6) specifically includes the following steps: (6.1) Configure the transaction log to obtain the corresponding value of the maximum number of transactions based on the number of transactions; (6.2) Configure the trigger time and frequency of the timed task for the timed scanning of the business flow based on the volume of business flow; (6.3) Start the corresponding number of threads to process SMS and email sending tasks according to the configured number of SMS and email sending threads; (6.4) Set the trigger time of SMS and email sending timed tasks to maintain a certain interval with the trigger time of pipeline scanning timed tasks. The number and speed of SMS and email sending are controlled by configuring the trigger time and frequency of the two timed tasks.

[0043] The present invention provides an apparatus for automating message push in multiple scenarios for operational business, wherein the apparatus includes: A processor is configured to execute computer-executable instructions; The memory stores one or more computer-executable instructions, which, when executed by the processor, implement the various steps of the method described above for implementing automated message push for multi-scenario operations.

[0044] The present invention discloses a processor for implementing automated message push for multiple scenarios in operational services. The processor is configured to execute computer-executable instructions, and when the computer-executable instructions are executed by the processor, the various steps of the above-described method for implementing automated message push for multiple scenarios in operational services are implemented.

[0045] The computer-readable storage medium of the present invention stores a computer program thereon, which can be executed by a processor to implement the various steps of the above-described method for implementing automated message push for multiple scenarios in operational services.

[0046] Currently, securities firms primarily send SMS messages to clients regarding the overall status of a transaction, such as informing them of their account information after a successful account opening. However, with the diversification of business scenarios and the application of combined services, it is necessary to send SMS messages and emails tailored to the processing results of specific sub-processes or multiple combined processes within the transaction workflow, providing clients with targeted updates on their transaction status.

[0047] The centralized operation system serves as a unified entry point for counter and online business processing. After a transaction is completed, customers are notified of the transaction status via SMS and guided to subsequent business procedures. However, given the diverse nature of business processing scenarios, existing SMS sending functions suffer from fragmented management and limited functionality across different components, only handling cases where the entire transaction is successful or unsuccessful. This invention proposes a multi-scenario automated message push system for operational business, unifying the management of SMS and email sending across various business scenarios, designing universal SMS and email sending rules, calculating the content for different scenarios, connecting to a unified SMS and email sending platform to inform customers of their business processing status, and implementing SMS and email distribution traffic control.

[0048] The present invention provides an automated message push system for multiple scenarios in operational business, which mainly includes a text message and email template configuration module, a transaction scanning module, a text message and email template matching module, a text message and email content calculation module, a text message and email sending module, and a text message and email traffic control module.

[0049] SMS and Email Template Configuration Module: This module is mainly used to configure SMS and email sending templates for different scenarios. Different templates can be configured according to business category, business initiation channel, customer scope and other elements that need to be met. It also supports the following three modes of template configuration, basically covering production business processing scenarios. (1) Single process template configuration: Configure business category, initiation channel, customer scope, business completion status and other elements that need to meet the conditions, where the parent template identifier and combined process identifier are configured to be empty; (2) Single combination process template configuration: Configure the parent template and several child templates. The combination process identifier of the parent template is configured to be empty, and the parent template identifier is configured to be its own template ID. The SMS and email templates are configured to be combinations of SMS and email templates in the child templates. The parent template identifier of the child template is configured to be the parent template ID, and the combination process identifier is configured to be empty. Other information configurations are the same as (1). (3) Configuration of multiple combination process templates: Configure the parent template and several child templates. The parent template identifier of the parent template is configured to be empty, and the combination process identifier is configured to be a combination of multiple child templates, such as [child template 1, child template 2, child template 3] || [child template 1, child template 4, child template 5]. The SMS and email templates are configured as a combination of SMS and email templates in the child templates. The parent template identifier of the child template is configured to be the parent template id, and the combination process identifier is configured to be empty. Other information configurations are the same as (1).

[0050] Transaction Scanning Module: This module is mainly used to collect transaction records from the business processing system. The scheduled task collects a fixed number of transaction records involving sending SMS and emails based on the timestamp, and generates SMS and email matching tasks. (1) Configure parameters “Maximum number of transactions to retrieve” and “Start timestamp for SMS and email transaction scanning”; (2) The scheduled task is executed once every 5 minutes. It collects business transactions in the business transaction table that are completed, whose status update timestamp is greater than the "SMS and email transaction scan start timestamp", and whose corresponding business category is configured in the SMS and email template table. The transactions are sorted in ascending order by status update timestamp. The number of transactions to be collected is the configured value of the parameter "maximum number of transactions to be collected". (3) The collected business transaction data is then assigned to the SMS and email matching task table; (4) Update the parameter “SMS and email transaction scan start timestamp” to the maximum value of the status update timestamp in the transaction data collection.

[0051] SMS and email template matching module: This module is mainly used to query all SMS and email template configurations based on the business category and business initiation channel of the business flow, and then match the accurate SMS and email templates based on the customer scope, business completion status and other elements that need to meet the conditions. (1) Poll the business transaction records in the SMS and email matching task table, and retrieve the application information of the transaction record from the business transaction record table according to the transaction record ID; (2) Query the SMS and email template configuration table according to the business category and initiation channel of the transaction to obtain all template configurations; (3) Polling template configuration: If the template type is a single process template, determine whether the customer scope, business completion status and other elements that need to meet the conditions in the flow information are consistent with the template configuration. If they are consistent, update the SMS and email templates to the matching task table. If the template type is a single combination process template, determine whether the customer scope, business completion status and other elements that need to meet the conditions in the flow information are consistent with the parent template. If they are consistent, obtain all sub-template configurations according to the parent template ID, poll to obtain the SMS and email templates in all matching sub-templates, and concatenate the final SMS and email templates to update the matching task table. If the template type is a multi-combination process template, determine whether the customer scope, business completion status and other elements that need to meet the conditions in the flow information are consistent with the parent template. If they are consistent, obtain all sub-template combinations configured in the combination process identifier of the parent template, determine whether any sub-template combination is completely matched, and if they are matched, obtain the SMS and email templates in the sub-templates, concatenate the final SMS and email templates to update the matching task table. If any of the aforementioned matching processes does not match, end the current polling and continue to poll other templates.

[0052] SMS and Email Content Calculation Module: This module is mainly used to replace some common identifiers in SMS and email templates, such as business category and customer name, and calculate the final SMS and email information to be sent to customers. (1) Poll the business transaction records of SMS and email matching task table, and obtain the application information of the transaction record from the business transaction record table according to the transaction record ID; (2) Replace the generic identifiers in SMS and email templates, such as business category, customer name, and customer account information, with the application information in the transaction details; (3) Replace the specific identifiers of the corresponding business categories in the SMS and email templates according to the different business categories, and calculate the final SMS and email information sent to the customer; (4) Record the transaction ID, SMS and email content, and SMS and email recipients in the SMS and email sending task table, and set the task status to pending sending.

[0053] SMS and Email Sending Module: This module is mainly used to collect the tasks to be sent in the SMS and email sending task table, and send SMS and emails to the mobile phone number / email address left by the customer in the system, informing the customer of the business processing status and guiding the customer to subsequent business processing matters. (1) The scheduled task is executed once every 5 minutes. It collects the tasks in the SMS and email sending task table whose task status is pending, and starts the corresponding number of threads to process the pending tasks according to the configured "number of SMS and email sending threads" parameter. (2) Query the transaction ID, SMS and email content, and SMS and email recipients (customer mobile phone number, email address and account unique identifier) ​​in the SMS and email sending task table according to the task ID. If the mobile phone number and account unique identifier are empty, do not send SMS; otherwise, continue the subsequent process (3-4). If the email address is empty, do not send email; otherwise, continue the subsequent process (5). (3) Calculate the length of the SMS content. SMS messages exceeding 230 bytes are split into two messages. The first 230 bytes are the first message, and the rest are the second message. (4) Query the SMS sending log table based on the transaction ID. If the current transaction ID has already sent an SMS, do not process it; otherwise, connect to the SMS sending platform to send an SMS to the customer, update the task status to sent, and record the transaction ID in the SMS sending log table. (5) Query the email sending log table based on the log ID. If the current log ID has already sent an email, do not process it; otherwise, connect to the email sending platform to send an email to the customer, update the task status to sent, and record the log ID in the email sending log table.

[0054] SMS and Email Traffic Control Module: This module is mainly used to control the quantity and speed of SMS and email sending based on parameters such as the maximum number of messages, the number of SMS and email sending threads, and the trigger time and frequency of scheduled tasks. (1) The parameter “maximum number of transactions to retrieve” is configurable, and the corresponding value can be configured according to the number of business transactions; (2) Configure the trigger time and frequency of the timed task for the timed scanning of the data flow based on the volume of the data flow; (3) Start the corresponding number of threads to process SMS and email sending tasks according to the configured "number of SMS and email sending threads" parameter; The timing of SMS and email sending is kept at a certain interval from the timing of pipeline scanning. The interval configuration depends on the number of data collected in each pipeline. The number and speed of SMS and email sending are controlled by configuring the timing and frequency of the two timed tasks.

[0055] In a specific embodiment of the present invention, for a multi-scenario automated message push system for operational business, the SMS and email template configuration module includes the following three types: (1) Single process template configuration: Taking account opening business as an example, configure the account opening business category, account opening channel, account opening customer scope, account opening business completion status and other elements that need to meet the conditions (such as the shareholder account opening market). (2) Single combination process template configuration: Taking the account opening business as an example, configure the parent template "Account opening success template", the parent template identifier is configured as its own template ID, and other configurations in the parent template are the same as (1); configure sub-templates such as successful opening of fund account, successful opening of bank account, successful opening of Shanghai stock shareholder account, and successful opening of Shenzhen stock shareholder account, where the parent template identifier in the sub-template is configured as the parent template ID, and other configurations are the same as (1). (3) Configuration of multiple combination process templates: Taking the account opening business as an example, configure the parent template "Funds account opening successful, bank account opening successful, at least one Shanghai and Shenzhen stock account opening successful", and configure the combination process identifier in the parent template as [Funds account opening successful, bank account opening successful, Shanghai stock account opening successful] || [Funds account opening successful, bank account opening successful, Shenzhen stock account opening successful], and other configurations are the same as (1); configure sub-templates such as Funds account opening successful, Funds account opening failed, Bank account opening successful, Shanghai stock account opening successful, Shenzhen stock account opening failed, etc., where the parent template identifier in the sub-template is configured as the parent template id, and other configurations are the same as (1).

[0056] The sequential scanning module includes the following steps: (1) Configure the parameters "Maximum number of transactions to be retrieved" to 600 and "SMS transaction scan start timestamp" to the online time 2025-07-05 00:00:00; (2) The scheduled task is executed once every 5 minutes to collect business transactions in the business transaction table that have completed status, whose status update timestamp is greater than the "SMS transaction scan start timestamp" and have the corresponding business category configuration in the SMS and email template tables. The transactions are sorted in ascending order by status update timestamp, and 600 transactions are collected each time. (3) The collected business transaction data is then assigned to the SMS and email matching task table; (4) Update the parameter “SMS transaction scan start timestamp” to the maximum value of the status update timestamp in the transaction data collection.

[0057] The SMS and email template matching module includes the following steps: (1) Poll the business transaction records in the SMS and email matching task table, and obtain the application information (such as business category, initiation channel, customer scope and business completion status) of the transaction record from the business transaction record table according to the transaction record ID. (2) Taking online account opening as an example, query the SMS and email template configuration table according to the account opening business category and online initiation channel to obtain all template configurations; (3) Polling template configuration: If the template type is a single process template, it determines whether the customer scope, business completion status and other elements that need to be met in the transaction information are consistent with the template configuration. If they are consistent, the SMS and email templates are updated to the matching task table. If the template type is a single combined process template such as "Account Opening Successful Master Template", it determines whether the customer scope, business completion status and other elements that need to be met in the transaction information are consistent with the parent template. If they are consistent, it retrieves the configuration of all child templates based on the parent template ID, such as successful opening of fund account, successful opening of bank account, successful opening of Shanghai Stock Exchange shareholder account, successful opening of Shenzhen Stock Exchange shareholder account, successful opening of Shenzhen Stock Exchange shareholder account, successful opening of bank account, successful opening of Shanghai ... Account opening successful. If all sub-templates match successfully, the final SMS and email templates are concatenated based on the SMS and email template configurations of the sub-templates and updated to the matching task table. For template types such as "Funds account opening successful, Bank account opening successful, At least one Shanghai or Shenzhen stock account opening successful", the system checks whether the customer scope, business completion status, and other required conditions in the transaction information are consistent with the parent template. If they are consistent, all sub-template combinations in the combined process identifier configuration are retrieved, such as [Funds account opening successful, Bank account opening successful, Shanghai stock shareholder account opening successful] || [Funds account opening successful, Bank account opening successful, Shenzhen stock shareholder account opening successful]. The system checks whether any sub-template combination matches completely. If they match, the SMS and email templates in the sub-templates are retrieved and the final SMS and email templates are concatenated and updated to the matching task table. If any of the aforementioned matching processes does not match, the current polling ends, and other templates are polled again.

[0058] The SMS and email content calculation module includes the following steps: (1) Poll the business transaction records of SMS and email matching task table, and obtain the application information of the transaction record from the business transaction record table according to the transaction record ID; (2) Taking account opening as an example, the SMS template is "Dear {KHMC} customer, you have successfully completed the [{YWMC}] business. Your fund account number is {YWZJZH}, {ZQZH}{Str_1}." Replace the general identifiers {KHMC} and {YWMC} in the SMS and email templates with the application information of the transaction details; (3) Replace the specific identifiers of the corresponding business categories in the SMS and email templates according to the different business categories, such as {YWZJZH}, {ZQZH}{Str_1}, and calculate the final SMS and email information sent to the customer; (4) Record the transaction ID, SMS and email content, and SMS and email recipients in the SMS and email sending task table, and set the task status to pending sending.

[0059] The SMS and email sending module includes the following steps: (1) The scheduled task is executed every 5 minutes to collect the tasks in the SMS and email sending task table that are in the pending sending status and start 3 threads to process the pending sending tasks. (2) Query the transaction ID, SMS and email content, and SMS and email recipients (customer mobile phone number, email address and account unique identifier) ​​in the SMS and email sending task table according to the task ID. If the mobile phone number and account unique identifier are empty, do not send SMS; otherwise, continue the subsequent process (3-4). If the email address is empty, do not send email; otherwise, continue the subsequent process (5). (3) Calculate the length of the SMS content. SMS messages exceeding 230 bytes are split into two messages. The first 230 bytes are the first message, and the rest are the second message. (4) Query the SMS sending record table based on the transaction ID. If the current transaction ID has already sent an SMS, do not process it; otherwise, connect to the SMS sending platform to send an SMS to the customer and record the transaction ID in the SMS sending record table. (5) Query the email sending log table based on the log ID. If the current log ID has already sent an email, do not process it; otherwise, send an email to the customer through the email sending platform and record the log ID in the email sending log table.

[0060] The SMS and email traffic control module includes the following steps: (1) The parameter “maximum number of transactions to retrieve” is configurable, and the corresponding value can be configured according to the number of business transactions; (2) Configure the trigger time and frequency of the timed task for the timed task of the timed task of the timed task according to the number of business transactions. Under normal circumstances, it is triggered once every 5 minutes; (3) Start the corresponding number of threads to process SMS and email sending tasks according to the configured "number of SMS and email sending threads" parameter; (4) The timing of SMS and email sending is 30 seconds apart from the timing of pipeline scanning. The number and speed of SMS and email sending are controlled by configuring the timing and frequency of the two timing tasks.

[0061] This invention addresses message push for operational services across multiple scenarios. It configures a universal message template table and implements differentiated message template matching logic for different business scenarios across various business types. After obtaining the message template, the message content is reorganized based on business information and then pushed. This invention can flexibly handle message push for both simple and complex scenarios, not only segmenting push content based on the push channel but also based on different customer types, push methods, and other factors.

[0062] The present invention addresses scenarios where there is no business transaction merging, and each business transaction is matched with a unique message template. The present invention also includes flow control technology.

[0063] The message template configuration of this invention is diversified, compatible with template configurations for single-process, single-combination process and multi-combination process, and can also configure differentiated templates according to channels and customer types; it adopts scheduled tasks to collect business flow and send messages, and controls the frequency and number of business flow collection and message sending through parameters, and can perform traffic control according to different business peaks.

[0064] For the specific implementation scheme of this embodiment, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.

[0065] It is understood that the same or similar parts in the above embodiments can be referred to each other, and the contents not described in detail in some embodiments can be referred to the same or similar contents in other embodiments.

[0066] It should be noted that in the description of this invention, the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Furthermore, in the description of this invention, unless otherwise stated, "a plurality of" means at least two.

[0067] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing a particular logical function or process, and the scope of the preferred embodiments of the invention includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as will be understood by those skilled in the art to which embodiments of the invention pertain.

[0068] It should be understood that various parts of the present invention can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in memory and executed by a suitable instruction execution device. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0069] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The corresponding program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiments.

[0070] Furthermore, the functional units in the various embodiments of the present invention can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0071] The storage media mentioned above can be read-only memory, disk, or optical disk, etc.

[0072] In the description of this specification, references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0073] The present invention provides a system, method, apparatus, processor, and computer-readable storage medium for automated message push in multiple scenarios for operational business. In the context of diversified business scenarios and customized customer needs, the message push system provides unified management of business processing SMS and email sending functions, calculates SMS and email sending content according to general SMS and email rules and notifies customers, and meets the diverse needs of customers for receiving messages and business processing SMS and email notifications in specific and combined scenarios.

[0074] In this specification, the invention has been described with reference to specific embodiments thereof. However, it will be apparent that various modifications and variations can be made without departing from the spirit and scope of the invention. Therefore, the specification and drawings should be considered illustrative rather than restrictive.

Claims

1. A system for implementing multi-scenario automated message pushing for business operations, characterized in that, The system comprises: The SMS and email template configuration module is configured to configure SMS and email sending templates under different scenarios, and support configuring different templates according to business categories, business initiation channels, customer ranges or other conditions to be met; The flow scanning module is connected to the SMS and email template configuration module, and is configured to collect business flows of a business handling system, collect a fixed number of business flows related to SMS and email sending according to time stamps at regular time intervals, and generate SMS and email matching tasks; The SMS and email template matching module is connected to the flow scanning module, and is configured to query all SMS and email templates according to business categories and business initiation channels of the business flows, and match SMS and email templates according to customer ranges, business completion states and other conditions to be met; The SMS and email content calculation module is connected to the SMS and email template matching module, and is configured to replace general identifiers in the SMS and email templates, and calculate final SMS and email information to be sent to customers; The SMS and email sending module is connected to the SMS and email content calculation module, and is configured to collect tasks to be sent in an SMS and email sending task table, send the SMS and email to mobile phone numbers or email addresses retained by customers in the system, and inform business handling conditions and guide subsequent business handling matters; The SMS and email flow control module is connected to the SMS and email sending module, and is configured to control the number and speed of SMS and email sending according to the maximum number of flows, the number of SMS and email sending threads, the triggering time and frequency of the regular tasks. 2.The system for implementing multi-scene automatic message pushing for business operation according to claim 1, wherein, The SMS and email template configuration module supports single-process template configuration mode, single-combination process template configuration mode and multi-combination process template configuration mode, The single-process template configuration mode is configured to configure business categories, initiation channels, customer ranges, business completion states or other conditions to be met; The single-combination process template configuration mode is configured to configure a parent template and a plurality of child templates, the combination process identifier of the parent template is configured to be empty, the parent template identifier is configured to be the template id itself, and the SMS and email template is configured to be a combination of SMS and email templates in the child templates; the parent template identifier of the child template is configured to be the parent template id, the combination process identifier is configured to be empty, and other information is configured in the same way as the single-process template configuration mode; The multi-combination process template configuration mode is configured to configure a parent template and a plurality of child templates, the parent template identifier of the parent template is configured to be empty, the combination process identifier is configured to be a combination of the plurality of child templates, and the SMS and email template is configured to be a combination of SMS and email templates in the child templates; the parent template identifier of the child template is configured to be the parent template id, the combination process identifier is configured to be empty, and other information is configured in the same way as the single-process template configuration mode. 3.The system for implementing multi-scene automatic message pushing for business operation according to claim 1, characterized in that, The flow scanning module collects business flows of a business handling system, collects a fixed number of business flows related to SMS and email sending according to time stamps at regular time intervals, and generates SMS and email matching tasks, and specifically includes the following steps: (2.1) Configure parameter flow to obtain the maximum number of flows and the starting time stamp of the SMS and email flow scanning; (2.2) Collecting the business flow table in which the business state has been completed, the state update time stamp is greater than the short message and email flow scanning starting time stamp, and the short message and email template table has the corresponding business category configuration, and sorting in ascending order of state update time stamp, and the flow acquisition pen number is the configuration value of the maximum pen number of flow acquisition; (2.3) The collected business flow falls into the short message and email matching task table; (2.4) Update the short message and email flow scanning starting time stamp to the maximum value of the state update time stamp in the collected business flow. 4.The system for implementing multi-scene automatic message pushing for business operations according to claim 1, wherein, The short message and email template matching module queries all short message and email template configurations according to the business category and business initiation channel of the business flow, and matches the short message and email template according to the customer range, business completion state and other required elements, and specifically includes the following steps: (3.1) Polling the business flow in the short message and email matching task table, and obtaining the application information of the flow from the business flow table according to the flow id; (3.2) Querying the short message and email template configuration table according to the business category and initiation channel of the flow, and obtaining all template configurations; (3.3) Polling the template configuration. 5.The system for implementing multi-scene automatic message pushing for business operation according to claim 4, characterized in that, The short message and email template matching module polls the template configuration, specifically including the following steps: (3.3.1) If the template type is a single process template, judge whether the customer range, business completion state and other required elements in the flow information are consistent with the template configuration, if consistent, update the short message and email template to the matching task table; (3.3.2) If the template type is a single combination process template, judge whether the customer range, business completion state and other required elements in the flow information are consistent with the parent template, if consistent, obtain all sub-template configurations according to the parent template id, poll all matched sub-templates to obtain the short message and email template, and splice the final short message and email template to update to the matching task table; (3.3.3) If the template type is a multi-combination process template, judge whether the customer range, business completion state and other required elements in the flow information are consistent with the parent template, if consistent, obtain all sub-template combinations configured by the combination process identifier in the parent template; judge whether any sub-template combination is completely matched, if matched, obtain the short message and email template in the sub-template, splice the final short message and email template to update to the matching task table; if any of the foregoing matching processes does not match, end this polling and continue polling other templates. 6.The system for implementing multi-scene automatic message pushing for business operation according to claim 1, wherein, The short message and email content calculation module replaces the general identifier in the short message and email template, and calculates the final short message and email information to be sent to the customer, specifically including the following steps: (4.1) Polling the business flow in the short message and email matching task table, and obtaining the application information of the flow from the business flow table according to the flow id; (4.2) Replacing the general identifier in the short message and email template with the application information of the flow; (4.3) Replacing the specific identifier corresponding to the business category in the short message and email template according to the different business categories of the flow, and calculating the final short message and email information to be sent to the customer. (4.4) record the flow id, short message and email sending content, short message and email sending object in the short message and email sending task table, and set the task state as pending sending.

7. The system for implementing multi-scene automatic message pushing for business operations according to claim 1, characterized in that, The short message and email sending module collects the tasks to be sent in the short message and email sending task table, and sends the short message and email to the mobile phone number or email address retained by the customer in the system, informs the business handling situation and guides the subsequent business handling matters, and specifically includes the following steps: (5.1) execute the task regularly, collect the tasks with the task state as pending sending in the short message and email sending task table, and start a corresponding number of threads to process the tasks to be sent according to the configured number of short message and email sending threads; (5.2) query the flow id, short message and email sending content, short message and email sending object in the short message and email sending task table according to the task id, if the mobile phone number and account unique identifier are both empty, do not send the short message, otherwise continue to steps (5.3) to (5.4); if the email address is empty, do not send the email, otherwise continue to step (5.5); (5.3) calculate the length of the short message content, and split the short message exceeding 230 bytes into two, the first 230 bytes as the first one and the rest as the second one; (5.4) query the short message sending flow table according to the flow id, if the current flow id has sent a short message, do not process; otherwise, connect the short message sending platform to send a short message to the customer, update the task state as sent, and record the flow id in the short message sending flow table; (5.5) query the email sending flow table according to the flow id, if the current flow id has sent an email, do not process; otherwise, connect the email sending platform to send an email to the customer, update the task state as sent and record the flow id in the email sending flow table. 8.The system for implementing multi-scene automatic message pushing for business operation according to claim 1, wherein, The short message and email flow control module controls the number and speed of short message and email sending according to the maximum number of flows, the number of short message and email sending threads and the trigger time and frequency of the timing task, and specifically includes the following steps: (6.1) configure the corresponding value of the maximum number of flows according to the number of business flows; (6.2) configure the trigger time and frequency of the flow scanning timing task according to the number of business flows; (6.3) start a corresponding number of threads to process the short message and email sending task according to the configured number of short message and email sending threads; (6.4) set the short message and email sending timing task trigger time to keep a certain interval with the flow scanning timing task trigger time, and control the number and speed of short message and email sending through the two timing task trigger time and frequency configurations.

9. A method for multi-scenario automated message pushing for business operation based on the system of claim 1, characterized in that, The method includes the following steps: (1) The short message and email template configuration module configures different templates according to business categories, business initiation channels, customer ranges or other required elements; (2) The flow scanning module collects the business flows of the business handling system, and the timing task collects a fixed number of business flows involving sending short messages and emails according to the time stamp, and generates short message and email matching tasks; (3) The SMS and email template matching module queries all SMS and email template configurations according to the business category and the business initiation channel of the business flow, and matches the SMS and email template according to the customer range, the business completion state and other required elements; (4) The SMS and email content calculation module replaces the general identifier in the SMS and email template, and calculates the final SMS and email information to be sent to the customer; (5) The SMS and email sending module collects the tasks to be sent in the SMS and email sending task table, sends the SMS and email to the mobile phone number or the email address retained by the customer in the system, informs the business handling situation and guides the subsequent business handling matters; (6) The SMS and email flow control module controls the number and speed of SMS and email sending according to the maximum number of flows, the number of SMS and email sending threads and the trigger time and frequency of the timing task.

10. The method for implementing multi-scene automatic message pushing for business operations according to claim 9, characterized in that, The step (2) specifically comprises the following steps: (2.1) configuring the parameter flow to obtain the maximum number of flows and the SMS and email flow scanning start timestamp; (2.2) performing the timing task, collecting the business flow in the business flow table whose state is completed, whose state update timestamp is greater than the SMS and email flow scanning start timestamp and which has corresponding business category configuration in the SMS and email template table, and sorting the business flow in ascending order of the state update timestamp, and the number of flows obtained is the configuration value of the maximum number of flows obtained; (2.3) dropping the collected business flow into the SMS and email matching task table; (2.4) updating the SMS and email flow scanning start timestamp to the maximum value of the state update timestamp in the collected business flow. 11.The method for implementing multi-scene automatic message pushing for business operation according to claim 9, wherein, The step (3) specifically comprises the following steps: (3.1) polling the business flow in the SMS and email matching task table, and obtaining the application information of the flow from the business flow table according to the flow id; (3.2) querying the SMS and email template configuration table according to the business category and the initiation channel of the flow, and obtaining all template configurations; (3.3) polling the template configuration, and matching the SMS and email template corresponding to the flow.

12. The method for implementing multi-scene automatic message pushing for business operations according to claim 9, characterized in that, The step (4) specifically comprises the following steps: (4.1) polling the business flow in the SMS and email matching task table, and obtaining the application information of the flow from the business flow table according to the flow id; (4.2) replacing the general identifier in the SMS and email template with the application information of the flow; (4.3) replacing the specific identifier corresponding to the business category in the SMS and email template according to the different business categories of the flow, and calculating the final SMS and email information to be sent to the customer; (4.4) recording the flow id, the SMS and email sending content, the SMS and email sending object in the SMS and email sending task table, and setting the task state to be sent.

13. The method for implementing multi-scene automatic message pushing for business operations according to claim 9, characterized in that, The step (5) specifically comprises the following steps: (5.1) performing the timing task, collecting the task in the SMS and email sending task table whose task state is to be sent, and starting a corresponding number of threads to process the tasks to be sent according to the configured number of SMS and email sending threads; (5.2) According to the task id, the flow id, the SMS and email sending content, and the SMS and email sending object in the SMS and email sending task table are queried. If the mobile phone number and the account unique identifier are both empty, no SMS is sent. Otherwise, steps (5.3) to (5.4) are continued. If the mailbox is empty, no email is sent. Otherwise, step (5.5) is continued. (5.3) The length of the SMS content is calculated. If the length of the SMS content exceeds 230 bytes, the SMS is split into two parts. The first 230 bytes of the content are the first part, and the remaining content is the second part. (5.4) According to the flow id, the SMS sending flow table is queried. If the current flow id has already sent an SMS, it is not processed. Otherwise, the SMS sending platform is connected to send an SMS to the customer. The task status is updated to "has been sent", and the flow id is recorded in the SMS sending flow table. (5.5) According to the flow id, the email sending flow table is queried. If the current flow id has already sent an email, it is not processed. Otherwise, the email sending platform is connected to send an email to the customer. The task status is updated to "has been sent", and the flow id is recorded in the email sending flow table.

14. The method for implementing multi-scene automatic message pushing for business operations according to claim 9, characterized in that, The step (6) specifically includes the following steps: (6.1) According to the number of business flows, the corresponding value of the maximum number of flow acquisition is configured. (6.2) According to the number of business flows, the trigger time and frequency of the flow scanning timing task are configured. (6.3) According to the configured number of SMS and email sending threads, a corresponding number of threads are started to process the SMS and email sending tasks. (6.4) The trigger time of the SMS and email sending timing task is set to maintain a certain interval with the trigger time of the flow scanning timing task. The number and speed of SMS and email sending are controlled through the trigger time and frequency configuration of the two timing tasks.

15. An apparatus for implementing multi-scenario automatic message pushing for business operations, characterized in that, The device includes: a processor configured to execute computer executable instructions; a memory storing one or more computer executable instructions, which, when executed by the processor, implement the steps of the method for implementing multi-scene automatic message pushing for operating businesses according to any one of claims 9 to 14.

16. A processor for implementing multi-scenario automated message pushing for business operations, characterized in that, The processor is configured to execute computer executable instructions, which, when executed by the processor, implement the steps of the method for implementing multi-scene automatic message pushing for operating businesses according to any one of claims 9 to 14.

17. A computer-readable storage medium, characterized in that, The computer program is stored on the processor and can be executed by the processor to implement the steps of the method for implementing multi-scene automatic message pushing for operating businesses according to any one of claims 9 to 14.

Images