Bank omni-channel message intelligent management and control method and system

Abstract

The invention provides a bank omni-channel message intelligent management and control method and system, and the method comprises the steps: accessing a standard structured event pushed by a business system, carrying out the compliance and anti-repetition verification, and obtaining a standardized event object; performing three-dimensional dynamic strategy matching on the received standardized event object to obtain a decision result containing a trigger rule ID; selecting a message sending channel based on the decision result containing the trigger rule ID, adopting a policy mode to realize multi-channel routing, and setting in a failover mechanism to obtain a channel execution context; and carrying out data storage on the standardized event object, the decision result containing the trigger rule ID and the channel execution context, and meanwhile, establishing an index to construct a full-link tracking index. According to the method, unified management and control of the messages are realized through standardized access and intelligent routing, accurate touch is ensured by adopting dynamic strategy matching, and unified management and control, dynamic optimization and visual monitoring of the whole message sending process are finally realized by combining failover and full-link tracking.

Description

Technical Field

[0001] This application relates to the field of financial technology, specifically to a method and system for intelligent management and control of bank messages across all channels. Background Technology

[0002] In the current banking system, messages such as SMS, email, and WeChat are typically sent independently by each business system (such as the credit system, loan accounting system, and marketing system) by calling third-party platforms, which presents the following pain points: Multiple systems independently configured with similar rules resulted in customers receiving duplicate messages. The sending logic is tightly coupled with the business code and cannot be dynamically adjusted (e.g., paused during holidays). Each system needs to repeatedly develop channel interface code, resulting in high maintenance costs; Sending records are stored in a scattered manner, making unified querying and analysis impossible.

[0003] In the current technological context, there is a lack of a message management solution that features centralized, cross-system data aggregation, dynamic configurability, event-driven architecture, and idempotent design. Summary of the Invention

[0004] This application provides a method and system for intelligent management and control of messages across all banking channels, which can solve the technical problems existing in the prior art, such as repeated message sending, fixed rules that are difficult to adjust, redundant development of channel integration, and data silos.

[0005] Firstly, this application provides a method for intelligent management and control of messages across all banking channels, including: Access standard structured events pushed by the business system, perform compliance and anti-duplicate verification, and obtain standardized event objects after verification. Perform three-dimensional dynamic strategy matching on the received standardized event objects to obtain decision results containing trigger rule IDs; The message sending channel is selected based on the decision result containing the trigger rule ID. The strategy pattern is used to implement multi-channel routing, and a built-in failover mechanism is used to obtain the channel execution context. Standardized event objects, decision results containing trigger rule IDs, and channel execution contexts are stored, and indexes are created to construct a full-link tracing index for the obtained messages.

[0006] Furthermore, the standardized events pushed by the access business system are processed for compliance and anti-duplicate verification, and the standardized event objects that pass the verification are obtained. This specifically includes the following steps: Receive standard structured events pushed by the business system via HTTP or AMQP protocol; Perform structured validation on the received standard structured events; Perform idempotency checks on standard structured events that pass the structured validation. For standard structured events that pass idempotency checks, parse and transform them to construct standardized event objects.

[0007] Furthermore, the standard structured event includes at least the following fields: The event includes a unique identifier, business type, customer identifier, business application number, transaction event, traffic acquisition channel number, reach channel, message reach event, and specific business fields.

[0008] Furthermore, the three dimensions include the channel dimension, the message dimension, and the channel routing dimension: Based on the business type and traffic referral channel number fields in the standardized event object, the sending strategy and control requirements corresponding to the channel dimension are obtained by matching the preset channel rule base; Based on the business type and the channel dimension requirements, load the corresponding message template and frequency control rules, verify sensitive words, determine whether the current time is within the allowed sending period, and obtain the approved message content and sending time window; Based on the combination of customer tags, service type, and message content, the optimal sending carrier and alternative channel schemes are obtained by filtering the pre-configured channel priority list. Based on the aforementioned channel dimension, message dimension, and channel routing dimension, conflict resolution is performed in a hierarchical order, prioritizing channel rules over message dimensions and message dimensions over routing rules, to obtain the final determined channel type and content template; The hot-loading mechanism monitors changes in the rule base across all dimensions in real time, dynamically updates the policy entries in the rule engine, and obtains the latest set of matching rules that take effect immediately, along with decision results containing trigger rule IDs.

[0009] Furthermore, the process of selecting a message sending channel based on the decision result containing the trigger rule ID, implementing multi-channel routing using the strategy pattern, and incorporating a built-in failover mechanism to obtain the channel execution context specifically includes the following steps: Based on the channel type field in the decision result containing the trigger rule ID, the main channel processor instance is obtained by matching the predefined SMS channel implementation class through the strategy pattern; Call the main channel processor's sending interface to deliver messages, and capture HTTP status codes and channel provider responses in real time to obtain the main channel sending status; When the main channel transmission status is failed, the corresponding channel processor instance is dynamically loaded to obtain the transmission status of the alternative channel based on the alternative channel scheme in the decision result. Merge the transmission status and error information of the primary channel and the alternative channel to generate a channel execution context that includes channel switching records and final status.

[0010] Furthermore, the process of storing standardized event objects, decision results containing trigger rule IDs, and channel execution contexts, and simultaneously establishing indexes to construct a full-link tracing index for the obtained messages, specifically includes the following steps: Based on the unique event identifier and business type field generated when the event is triggered, the rule identifier and decision result output by the rule engine are correlated to obtain the complete message processing context containing the rule matching logic; Write the message processing context and the channel type and sending status returned by the channel adaptation layer to the relational database according to the time sequence to form a structured end-to-end log record containing information about the entire lifecycle of the event; A composite index is built based on the unique event identifier and customer identifier in the end-to-end log records, and an inverted index is built in the search engine to obtain a data set that supports fast multi-dimensional retrieval; By comparing the end-to-end log records in the relational database with the data set in the search engine through a scheduled task, data consistency verification is performed, and an end-to-end tracking index for the obtained messages is constructed.

[0011] Furthermore, after storing the standardized event object, the decision result containing the trigger rule ID, and the channel execution context, and simultaneously establishing an index to construct the full-link tracing index of the message, the process further includes the following steps: Based on the unique event identifier and customer identifier in the full-link tracing index, interactive statistical charts and reports can be obtained from the visualization query component in the associated monitoring and operation layer; Based on the abnormal data points in the statistical charts, query the associated event processing logs and channel execution records to obtain contextual information for problem localization; Based on the error type and frequency in the context information of problem location, the rule engine automatically triggers optimization suggestions to obtain dynamic strategy adjustment schemes; The dynamic strategy adjustment plan is pushed to the rule engine's visual configuration interface for operations personnel to review and confirm before taking effect and obtaining the updated message delivery strategy.

[0012] Secondly, this application provides a bank's omnichannel intelligent message management system, including: The standardized event object acquisition module is used to access the standardized structured events pushed by the business system, perform compliance and anti-duplicate verification, and obtain the standardized event objects after the verification is passed. The decision result acquisition module is communicatively connected to the standardized event object acquisition module and is used to perform three-dimensional dynamic strategy matching on the received standardized event objects to obtain decision results containing trigger rule IDs. The channel execution context acquisition module is communicatively connected to the decision result acquisition module. It is used to select the message sending channel based on the decision result containing the trigger rule ID, implement multi-channel routing using the strategy pattern, and has a built-in failover mechanism to acquire the channel execution context. The intelligent management and control index acquisition module is communicatively connected to the standardized event object acquisition module, the decision result acquisition module, and the channel execution context acquisition module. It is used to store standardized event objects, decision results containing trigger rule IDs, and channel execution contexts, and at the same time, to build an index to construct a full-link tracking index for the obtained messages.

[0013] Furthermore, the standardized event object acquisition module includes: The standard structured event acquisition unit is used to receive standard structured events pushed by the business system via HTTP or AMQP protocol. The structured verification unit is communicatively connected to the standard structured event acquisition unit and is used to perform structured verification on the received standard structured events. The anti-duplicate verification unit is communicatively connected to the structured verification unit and is used to perform idempotency verification on standard structured events that have passed the structured verification. The event parsing unit is communicatively connected to the anti-duplicate verification unit and is used to parse and transform standard structured events that have passed idempotency verification to construct standardized event objects.

[0014] Thirdly, this application provides a computer-readable storage medium storing a bank omnichannel message intelligent management and control program, wherein when the bank omnichannel message intelligent management and control program is executed by a processor, it implements the steps of the bank omnichannel message intelligent management and control method as described above. The beneficial effects of the technical solutions provided in this application include at least the following: By employing standardized event access and verification mechanisms, duplicate message sending and compliance risks are effectively avoided. A three-dimensional dynamic strategy matching technology is used to achieve precise adaptation between business rules and customer characteristics, significantly improving the accuracy and timeliness of message delivery. Multi-channel routing based on policy patterns, combined with an intelligent failover mechanism, ensures reliable message delivery under various abnormal conditions. Through end-to-end data storage and indexing, a complete message tracking system is formed, providing data support for operational analysis. Ultimately, unified management, dynamic optimization, and visual monitoring of the entire message sending process are achieved, improving customer experience while reducing system maintenance complexity. Attached Figure Description

[0015] Figure 1 This is a flowchart illustrating the bank's intelligent management method for all-channel messaging in this application. Figure 2 This is a functional module diagram of the bank's omnichannel intelligent message management system for this application. Detailed Implementation

[0016] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0017] The terms "comprising" and "having," and any variations thereof, in the specification, claims, and accompanying drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus. The terms "first," "second," and "third," etc., are used to distinguish different objects, etc., and do not indicate a sequence, nor do they limit "first," "second," and "third" to different types.

[0018] In the description of the embodiments in this application, terms such as "exemplary," "for example," or "for instance" are used as examples, illustrations, or explanations. Any embodiment or design described as "exemplary," "for example," or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary," "for example," or "for instance" is intended to present the relevant concepts in a specific manner.

[0019] In the description of the embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in the text is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more.

[0020] In some processes described in the embodiments of this application, multiple operations or steps are included in a specific order. However, it should be understood that these operations or steps may not be executed in the order they appear in the embodiments of this application, or they may be executed in parallel. The sequence number of the operation is only used to distinguish different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed sequentially or in parallel, and these operations or steps may be combined.

[0021] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0022] This invention provides a method for intelligent management and control of messages across all banking channels. By adopting the strategy pattern and introducing technical components such as Spring Boot, Redis, RocketMQ, Drools, Lua scripts, MySQL, and ElasticSearch, it aims to create a highly available, dynamically configurable, and unified management and control system for bank messages, thereby solving the problems of duplicate message sending, rigid rules, technical debt, and data silos in the existing bank architecture.

[0023] Firstly, such as Figure 1 As shown, this application provides a method for intelligent management and control of messages across all banking channels, including: Step S1: Access the standard structured events pushed by the business system, perform compliance and anti-duplicate verification, and obtain the standardized event object after the verification is passed; Step S2: Perform three-dimensional dynamic strategy matching on the received standardized event objects to obtain the decision results containing the trigger rule ID; Step S3: Select the message sending channel based on the decision result containing the trigger rule ID, implement multi-channel routing using the strategy pattern, and build a built-in failover mechanism to obtain the channel execution context; Step S4: Store the standardized event objects, decision results containing trigger rule IDs, and channel execution context, and simultaneously create an index to build a full-link tracing index for the obtained messages.

[0024] This application effectively avoids message duplication and compliance risks through a standardized event access and verification mechanism; it employs a three-dimensional dynamic policy matching technology to achieve precise adaptation between business rules and customer characteristics, significantly improving the accuracy and timeliness of message delivery; multi-channel routing based on policy patterns, combined with an intelligent failover mechanism, ensures reliable message delivery under various abnormal conditions; and it forms a complete message tracking system through end-to-end data storage and indexing, providing data support for operational analysis. Ultimately, it achieves unified management, dynamic optimization, and visual monitoring of the entire message sending process, improving customer experience while reducing system maintenance complexity.

[0025] In one embodiment, step S1: accessing standardized events pushed by the business system, performing compliance and anti-duplicate verification, and obtaining standardized event objects after successful verification, specifically includes the following steps: It supports receiving standard structured events pushed by business systems via both HTTP and AMQP protocols; Perform structured validation on the received standard structured events; Perform idempotency checks on standard structured events that pass the structured validation. For standard structured events that pass idempotency checks, parse and transform them to construct standardized event objects.

[0026] In one embodiment, support for both HTTP and AMQP protocols is provided, specifically including: It supports the Hypertext Transfer Protocol (HTTP), allowing business systems to synchronously request the real-time interface of the message center via the POST method, and the message center to return the results in real time; It supports the Advanced Message Queuing Protocol (AMQP), allowing business systems to asynchronously push requests to the message center via the RocketMQ middleware. After the message center consumes the requests, it provides a query interface for business systems to query the final results.

[0027] In one embodiment, idempotency verification is implemented using Redis, specifically including the following steps: Use the event's unique identifier, event_id, as the key to execute the SETNX operation; If it returns false, it is determined to be a duplicate event and discarded.

[0028] In one embodiment, the standard structured event (JSON Schema) in step S1 includes at least the following fields: json { event_id: "TRAN123456", / / Unique identifier for the event busi_type: "repayment_reminder", / / Business type customer_id: "CUST_12345", / / Customer identifier busi_no: "APPLY123456", / / Business application number trans_time: "2024-03-01 10:00:00", / / Transaction time platform_no: "MAYI", / / Traffic channel ID trigger_channel: "SMS", / / Trigger channel trigger_time: "2024-03-01 10:00:00", / / Message arrival time busi_data:{} / / Specific business data fields }

[0029] In one embodiment, step S2: the three dimensions include a channel dimension, a message dimension, and a channel routing dimension; specifically: The channel dimension refers to specific rules used to manage connections with online traffic acquisition platforms. The message dimension includes unified management of message template content settings, message delivery time settings, sensitive word filtering rules, and rules for customer-level sending frequency limits, time period control, and daily sending quantity. At the channel routing level, unified configuration selection is provided for message push carriers, such as SMS, WeChat, AI outbound calls, and emails, and configuration based on multiple conditions (customer tags + business events + channels) is supported.

[0030] In one embodiment, step S2 is implemented through the rule engine layer of the message center system; further, the rule engine layer can support hot reloading of rules through the Drools rule engine and Lua scripts, so that the rules can take effect without restarting the service. For example, dynamic policy configuration is implemented based on Drools and Lua, supporting the following rule types: Frequency control rule: The same customer can receive a maximum of one message of the same type per day; Time period rule: Sending is allowed from 9:00 to 20:00 on weekdays; Compliance rules: Sensitive word filtering (such as blocking words like "usury").

[0031] In one embodiment, step S3: selecting a message sending channel based on the decision result containing the trigger rule ID, implementing multi-channel routing using the strategy pattern, and incorporating a built-in failover mechanism to obtain the channel execution context, specifically includes the following steps: Based on the channel type field in the decision result containing the trigger rule ID, the main channel processor instance is obtained by matching the predefined SMS channel implementation class through the strategy pattern; Call the main channel processor's sending interface to deliver messages, and capture HTTP status codes and channel provider responses in real time to obtain the main channel sending status; When the main channel transmission status is failed, the corresponding channel processor instance is dynamically loaded to obtain the transmission status of the alternative channel based on the alternative channel scheme in the decision result. Merge the transmission status and error information of the primary channel and the alternative channel to generate a channel execution context that includes channel switching records and final status.

[0032] In one embodiment, step S3 is implemented through a channel adaptation layer; further, the channel adaptation layer includes: The system uses a strategy-based routing model to route SMS, WeChat, email, AI outbound calls, PUSH, and other channels. Built-in failover mechanism: When the primary channel (such as SMS) fails, it automatically switches to the backup channel (such as WeChat push).

[0033] In one embodiment, step S4: storing standardized event objects, decision results containing trigger rule IDs, and channel execution context, and simultaneously establishing an index to construct a full-link tracing index for the obtained message, specifically includes the following steps: Based on the unique event identifier and business type field generated when the event is triggered, the rule identifier and decision result output by the rule engine are correlated to obtain the complete message processing context containing the rule matching logic; Write the message processing context and the channel type and sending status returned by the channel adaptation layer to the relational database according to the time sequence to form a structured end-to-end log record containing information about the entire lifecycle of the event; A composite index is built based on the unique event identifier and customer identifier in the end-to-end log records, and an inverted index is built in the search engine to obtain a data set that supports fast multi-dimensional retrieval; By comparing the end-to-end log records in the relational database with the data set in the search engine through a scheduled task, data consistency verification is performed, and an end-to-end tracking index for the obtained messages is constructed.

[0034] In one embodiment, a data storage layer is used to store standardized event objects, decision results containing trigger rule IDs, and channel execution context; further, the data storage layer includes: Full logs: Using the open-source database MySQL, the message center's sending records (content, time, channel, status) are written to the local database for subsequent querying and analysis.

[0035] Data aggregation: All contact records of the platform and customers (including historical SMS and APP push) are displayed uniformly in the message center, supporting in-depth query by customer ID; Query acceleration: Provides fast multi-dimensional queries through Elasticsearch (such as aggregating historical messages by customer ID).

[0036] In one embodiment, after storing the standardized event object, the decision result containing the trigger rule ID, and the channel execution context, and simultaneously building an index to construct the full-link tracing index of the message, step S4 further includes the following steps: Based on the unique event identifier and customer identifier in the full-link tracing index, interactive statistical charts and reports can be obtained from the visualization query component in the associated monitoring and operation layer; Based on the abnormal data points in the statistical charts, query the associated event processing logs and channel execution records to obtain contextual information for problem localization; Based on the error type and frequency in the context information of problem location, the rule engine automatically triggers optimization suggestions to obtain dynamic strategy adjustment schemes; The dynamic strategy adjustment plan is pushed to the rule engine's visual configuration interface for operations personnel to review and confirm before taking effect and obtaining the updated message delivery strategy.

[0037] The intelligent management method for omnichannel messaging in this application includes at least the following technical effects: Achieve unified access for all bank-wide messaging (SMS, email, WeChat notifications, etc.); Supports dynamic control and sending of messages based on the interface channel, user, and time period. Achieve end-to-end message status tracking and real-time reporting; It supports business departments to respond quickly within minutes, completing the configuration and activation of new rules.

[0038] In one embodiment, the present invention provides a message center based on a basic support platform that applies a smart management and control method for omnichannel bank messages. This includes the aforementioned event receiving layer, rule engine layer, monitoring and operation layer, data storage layer, and channel adaptation layer. The visualization interfaces of the monitoring and operation layer and rule engine layer are implemented using the Vue and Element-UI frameworks, supporting a visual configuration interface, query page, and composite condition search, as well as a real-time monitoring panel. In one embodiment, the monitoring and operation layer is used to implement the visual configuration interface, which is used for a visual statistical query page and monitoring panel. In one embodiment, the monitoring and operation layer includes: It reads data from the data storage layer, uses a visual statistical query page and monitoring panel, supports real-time search queries with multiple conditions, and utilizes the open-source component Elasticsearch to accelerate queries.

[0039] Get real-time quotes from channel providers and compare prices to intelligently select the best channel.

[0040] In one embodiment, this application also provides a method for sending messages across all banking channels, specifically including the following steps: The business system generates structured events and pushes them to the event receiving layer of the message center; After receiving the event, the event receiving layer processes it into a standard data format and passes it to the rule engine layer; The rules engine layer matches the specific engine strategy based on the key fields in the event. After the strategy is verified, the message content is rendered and filled according to the predefined message template, and then sent to the channel routing layer. The channel routing layer selects the sending channel according to the channel agreed in the policy, and supports failure retry and cross-channel switching; The data storage layer is responsible for recording the entire message sending log and data, which is used for statistical queries by the monitoring and operations layer.

[0041] Secondly, such as Figure 2 As shown, this application provides a bank's omnichannel message intelligent management and control system, including a standardized event object acquisition module 100, a decision result acquisition module 200, a channel execution context acquisition module 300, and an intelligent management and control index acquisition module 400; The standardized event object acquisition module 100 is used to access the standardized structured events pushed by the business system, perform compliance and anti-duplicate verification, and acquire the standardized event objects after the verification is passed. The decision result acquisition module 200 is communicatively connected to the standardized event object acquisition module 100, and is used to perform three-dimensional dynamic strategy matching on the received standardized event objects to obtain decision results containing trigger rule IDs; The channel execution context acquisition module 300 is communicatively connected to the decision result acquisition module 200. It is used to select the message sending channel based on the decision result containing the trigger rule ID, implement multi-channel routing using the strategy pattern, and has a built-in failover mechanism to acquire the channel execution context. The intelligent management and control index acquisition module 400 is communicatively connected to the standardized event object acquisition module 100, the decision result acquisition module 200, and the channel execution context acquisition module 300. It is used to store standardized event objects, decision results containing trigger rule IDs, and channel execution contexts, and at the same time, establish an index to construct a full-link tracking index for the obtained messages.

[0042] In one embodiment, the standardized event object acquisition module includes: The standard structured event acquisition unit is used to receive standard structured events pushed by the business system via HTTP or AMQP protocol. The structured verification unit is communicatively connected to the standard structured event acquisition unit and is used to perform structured verification on the received standard structured events. The anti-duplicate verification unit is communicatively connected to the structured verification unit and is used to perform idempotency verification on standard structured events that have passed the structured verification. The event parsing unit is communicatively connected to the anti-duplicate verification unit and is used to parse and transform standard structured events that have passed idempotency verification to construct standardized event objects.

[0043] The functions of each module in the aforementioned intelligent management and control system for bank omnichannel messages correspond to the steps in the aforementioned intelligent management and control method embodiment for bank omnichannel messages, and their functions and implementation processes will not be described in detail here.

[0044] Thirdly, this application provides a smart management and control device for bank omnichannel messages. The smart management and control device for bank omnichannel messages can be a personal computer (PC), a laptop, a server, or other device with data processing capabilities.

[0045] The communication interface includes input / output (I / O) interfaces, physical interfaces, and logical interfaces used for interconnecting internal components of the bank's omnichannel intelligent message management and control equipment, as well as interfaces used for interconnecting the equipment with other devices (such as other computing devices or user equipment). Physical interfaces can be Ethernet interfaces, fiber optic interfaces, ATM interfaces, etc.; user equipment can be displays, keyboards, etc.

[0046] Memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0047] The processor can be a general-purpose processor, which can call the intelligent management and control program for all-channel bank messages stored in the memory and execute the intelligent management and control method for all-channel bank messages provided in the embodiments of this application. For example, the general-purpose processor can be a central processing unit (CPU). The method executed when the intelligent management and control program for all-channel bank messages is called can be referred to in the various embodiments of the intelligent management and control method for all-channel bank messages in this application, and will not be repeated here.

[0048] Fourthly, embodiments of this application also provide a readable storage medium.

[0049] The present application stores a bank omnichannel message intelligent management program on a readable storage medium, wherein when the bank omnichannel message intelligent management program is executed by a processor, it implements the steps of the bank omnichannel message intelligent management method described above.

[0050] The method implemented when the bank's omnichannel message intelligent control program is executed can be referred to in the various embodiments of the bank omnichannel message intelligent control method of this application, and will not be repeated here.

[0051] It should be noted that the sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0052] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of this application.

[0053] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A method for intelligent management and control of messages across all banking channels, characterized in that, include: Access standard structured events pushed by the business system, perform compliance and anti-duplicate verification, and obtain standardized event objects after verification. Perform three-dimensional dynamic strategy matching on the received standardized event objects to obtain decision results containing trigger rule IDs; The message sending channel is selected based on the decision result containing the trigger rule ID. The strategy pattern is used to implement multi-channel routing, and a built-in failover mechanism is used to obtain the channel execution context. Standardized event objects, decision results containing trigger rule IDs, and channel execution contexts are stored, and indexes are created to construct a full-link tracing index for the obtained messages.

2. The intelligent management and control method for bank omnichannel messages as described in claim 1, characterized in that, The standardized events pushed by the access business system are subjected to compliance and anti-duplicate verification, and the standardized event objects that pass the verification are obtained. The specific steps include: Receive standard structured events pushed by the business system via HTTP or AMQP protocol; Perform structured validation on the received standard structured events; Perform idempotency checks on standard structured events that pass the structured validation. For standard structured events that pass idempotency checks, parse and transform them to construct standardized event objects.

3. The intelligent management and control method for bank omnichannel messages as described in claim 1, characterized in that, The standard structured event includes at least the following fields: The event includes a unique identifier, business type, customer identifier, business application number, transaction event, traffic acquisition channel number, reach channel, message reach event, and specific business fields.

4. The intelligent management and control method for bank omnichannel messages as described in claim 1, characterized in that, The three dimensions include the channel dimension, the message dimension, and the channel routing dimension: Based on the business type and traffic referral channel number fields in the standardized event object, the sending strategy and control requirements corresponding to the channel are obtained by matching the preset channel dimension rule base; Based on the business type and the channel dimension requirements, load the corresponding message template and frequency control rules, verify sensitive words, determine whether the current time is within the allowed sending period, and obtain the approved message content and sending time window; Based on the combination of customer tags, service type, and message content, the optimal sending carrier and alternative channel schemes are obtained by filtering the pre-configured channel priority list. Based on the aforementioned channel dimension, message dimension, and channel routing dimension, conflict resolution is performed in a hierarchical order, prioritizing channel rules over message dimensions and message dimensions over routing rules, to obtain the final determined channel type and content template; The hot-loading mechanism monitors changes in the rule base across all dimensions in real time, dynamically updates the policy entries in the rule engine, and obtains the latest set of matching rules that take effect immediately, along with decision results containing trigger rule IDs.

5. The intelligent management and control method for bank omnichannel messages as described in claim 1, characterized in that, The process of selecting a message sending channel based on a decision result containing a trigger rule ID, employing a strategy pattern to implement multi-channel routing, and incorporating a built-in failover mechanism to obtain the channel execution context, specifically includes the following steps: Based on the channel type field in the decision result containing the trigger rule ID, the main channel processor instance is obtained by matching the predefined SMS channel implementation class through the strategy pattern; Call the main channel processor's sending interface to deliver messages, and capture HTTP status codes and channel provider responses in real time to obtain the main channel sending status; When the main channel transmission status is failed, the corresponding channel processor instance is dynamically loaded to obtain the transmission status of the alternative channel based on the alternative channel scheme in the decision result. Merge the transmission status and error information of the primary channel and the alternative channel to generate a channel execution context that includes channel switching records and final status.

6. The intelligent management and control method for bank omnichannel messages as described in claim 1, characterized in that, The process of storing standardized event objects, decision results containing trigger rule IDs, and channel execution context, and simultaneously establishing indexes to construct a full-link tracing index for the message, specifically includes the following steps: Based on the unique event identifier and business type field generated when the event is triggered, the rule identifier and decision result output by the rule engine are correlated to obtain the complete message processing context containing the rule matching logic; Write the message processing context and the channel type and sending status returned by the channel adaptation layer to the relational database according to the time sequence to form a structured end-to-end log record containing information about the entire lifecycle of the event; A composite index is built based on the unique event identifier and customer identifier in the full-link log records, and an inverted index is built in the search engine to obtain a data set that supports fast multi-dimensional retrieval; By comparing the end-to-end log records in the relational database with the data set in the search engine through a scheduled task, data consistency verification is performed, and an end-to-end tracking index for the obtained messages is constructed.

7. The intelligent management and control method for bank omnichannel messages as described in claim 1, characterized in that, After storing standardized event objects, decision results containing trigger rule IDs, and channel execution contexts, and simultaneously establishing indexes to construct a full-link tracing index for messages, the process further includes the following steps: Based on the unique event identifier and customer identifier in the full-link tracing index, interactive statistical charts and reports can be obtained from the visualization query component in the associated monitoring and operation layer; Based on the abnormal data points in the statistical charts, query the associated event processing logs and channel execution records to obtain contextual information for problem localization; Based on the error type and frequency in the context information of problem location, the rule engine automatically triggers optimization suggestions to obtain dynamic strategy adjustment schemes; The dynamic strategy adjustment plan is pushed to the rule engine's visual configuration interface for operations personnel to review and confirm before taking effect and obtaining the updated message delivery strategy.

8. A smart management and control system for omnichannel banking messages, characterized in that, include: The standardized event object acquisition module is used to access the standardized structured events pushed by the business system, perform compliance and anti-duplicate verification, and obtain the standardized event objects after the verification is passed. The decision result acquisition module is communicatively connected to the standardized event object acquisition module and is used to perform three-dimensional dynamic strategy matching on the received standardized event objects to obtain decision results containing trigger rule IDs. The channel execution context acquisition module is communicatively connected to the decision result acquisition module. It is used to select the message sending channel based on the decision result containing the trigger rule ID, implement multi-channel routing using the strategy pattern, and has a built-in failover mechanism to acquire the channel execution context. The intelligent management and control index acquisition module is communicatively connected to the standardized event object acquisition module, the decision result acquisition module, and the channel execution context acquisition module. It is used to store standardized event objects, decision results containing trigger rule IDs, and channel execution contexts, and at the same time, to build an index to construct a full-link tracking index for the obtained messages.

9. The intelligent management and control system for all channels of bank messages as described in claim 8, characterized in that, The standardized event object acquisition module includes: The standard structured event acquisition unit is used to receive standard structured events pushed by the business system via HTTP or AMQP protocol. The structured verification unit is communicatively connected to the standard structured event acquisition unit and is used to perform structured verification on the received standard structured events. The anti-duplicate verification unit is communicatively connected to the structured verification unit and is used to perform idempotency verification on standard structured events that have passed the structured verification. The event parsing unit is communicatively connected to the anti-duplicate verification unit and is used to parse and transform standard structured events that have passed idempotency verification to construct standardized event objects.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a bank omnichannel message intelligent management and control program, wherein when the bank omnichannel message intelligent management and control program is executed by a processor, it implements the steps of the bank omnichannel message intelligent management and control method as described in any one of claims 1 to 7.

Images