Event prompting method and device

Abstract

The invention provides an event prompting method and device, and the method is applied to a customer management platform, and the method comprises the steps: building a customer data mart based on the obtained bank internal system data and bank external system data; configuring a business event rule set for the customer data mart from at least one business participation object dimension; monitoring the customer data mart by using the business event rule set corresponding to each business participation object dimension, and identifying a target business event under each business participation object dimension; in response to the generation of the target business event, determining event prompt information, an information push mode and target business personnel for the target business event according to the target business event rule; and automatically distributing the event prompt information to the target business personnel through an information push channel included in the information push mode. In this way, timely and unified monitoring and targeted personalized information pushing of the business events can be achieved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to an event prompting method and device. Background Art

[0002] In existing banking systems, events refer to business-significant information generated by changes in customer behavior or external factors. For example, events can impact customer financial needs, leading to new sales and service opportunities. Therefore, event notifications are a crucial feature banks implement to better serve customers and strengthen risk management.

[0003] With the continuous development and innovation of banking services, various risks and issues are increasing, and various events frequently occur during business processing. However, existing technologies require developers to develop event-specific notification functions for individual business systems. These notification functions lack flexibility. Specifically, because existing technologies rely on a single event trigger mechanism and fail to account for differences in institutional hierarchies and customer profiles, they can lead to poor notification accuracy when new business scenarios are added or requirements change. Consequently, they cannot meet the rapidly evolving needs of banking services. Summary of the Invention

[0004] In view of this, the purpose of this application is to provide an event prompt method and device, which can realize timely and unified monitoring of business events through a customer management platform and configuring a business event rule set from at least one business participant object dimension; in addition, according to the target business event rules, the event prompt information, information push method and target business personnel for the target business event are determined, so as to realize targeted personalized information push.

[0005] The present invention provides an event prompt method, which is applied to a customer management platform. The method includes:

[0006] Building a customer data mart based on the acquired bank's internal system data and bank's external system data; the customer data mart includes pre-defined customer event data of various types;

[0007] Configuring a business event rule set for the customer data mart from at least one business participation object dimension;

[0008] Monitor the customer data mart using the business event rule set corresponding to each business participant object dimension to identify a target business event under each business participant object dimension; wherein the target business event refers to a business event that complies with at least one target business event rule in the business event rule set;

[0009] In response to the generation of the target business event, determining event prompt information, information push method, and target business personnel for the target business event according to the target business event rule;

[0010] The event prompt information is automatically distributed to the target business personnel through the information push channel included in the information push method.

[0011] Furthermore, the business participation object dimension includes a dimension of the role level of the business personnel and / or a dimension of the customer group type; configuring a business event rule set for the customer data mart based on at least one business participation object dimension includes:

[0012] Based on the dimension of the role level to which the business personnel belong, for each role level, a business event rule subset for the role level is configured to obtain a business event rule set for the customer data mart; the business event rule subset includes at least one business event rule;

[0013] and / or,

[0014] From the dimension of customer group type, for each pre-set customer group list, a business event rule subset for the customer group list is configured to obtain a business event rule set for the customer data mart.

[0015] Furthermore, each business event rule in the business event rule set includes a business event triggering sub-rule; monitoring the customer data mart using the business event rule set corresponding to each business participant object dimension to identify target business events under each business participant object dimension includes:

[0016] Using each business event trigger sub-rule included in the business event rule set corresponding to each business participant object dimension, monitoring the customer data mart to identify candidate target events under each business participant object dimension;

[0017] Deduplication is performed on the candidate target events to obtain the target business event.

[0018] Furthermore, deduplication processing is performed on the candidate target events to obtain the target business events, including:

[0019] Generate a message summary of each candidate target event based on the customer information and event information included in the candidate target event;

[0020] Deduplication processing is performed on the candidate target events according to the message digest of each candidate target event to obtain the target business event.

[0021] Furthermore, each business event rule in the business event rule set includes an event information push sub-rule; the event information push sub-rule includes a prompt information template; in response to the generation of the target business event, event prompt information for the target business event is determined according to the target business event rule, including:

[0022] extracting feature information from the target business event;

[0023] The characteristic information is correspondingly filled into a predetermined position in the prompt information template included in the target business event rule, and the event prompt information is assembled to obtain the event prompt information.

[0024] Furthermore, when the business participant object dimension includes a dimension of a role level to which a business person belongs, in response to the generation of the target business event, determining a target business person for the target business event according to the target business event rule includes:

[0025] Determining at least one role level corresponding to the target business event rule;

[0026] Determining customer information included in the target business event;

[0027] The target business personnel are determined based on the customer management relationship reserved in the customer management platform for each role level and the customer information.

[0028] Furthermore, when the business participant object dimension includes a customer group type dimension, in response to the generation of the target business event, determining a target business person for the target business event according to the target business event rule includes:

[0029] Determine the customer group list corresponding to the target business event rule;

[0030] The target business personnel are determined according to the list subscription relationship reserved in the customer management platform.

[0031] Furthermore, in response to the generation of the target business event, determining an information push method for the target business event according to the target business event rule includes:

[0032] Determining event information included in the target business event; the event information includes an event type;

[0033] Matching the urgency corresponding to the event type with the priority and push channel preference of the candidate information push channels included in the target business event rule to determine the information push channel for the target business event;

[0034] The information push method is determined according to the information push channel.

[0035] Furthermore, the business participant object dimension also includes at least one of the following: a dimension of the product type that the business personnel is responsible for, a dimension of the risk level that the business personnel is concerned about, and a dimension of the life cycle stage of the customer.

[0036] The present application also provides an event prompt device, which is applied to a customer management platform. The device includes:

[0037] A construction module, configured to construct a customer data mart based on the acquired bank's internal system data and bank's external system data; the customer data mart includes predefined customer event data of various types;

[0038] A configuration module, configured to configure a business event rule set for the customer data mart from at least one business participant object dimension;

[0039] a monitoring module, configured to monitor the customer data mart using the business event rule set corresponding to each business participant object dimension, and identify a target business event under each business participant object dimension; wherein the target business event is a business event that complies with at least one target business event rule in the business event rule set;

[0040] A determination module, configured to, in response to the generation of the target business event, determine event prompt information, information push method, and target business personnel for the target business event according to the target business event rule;

[0041] A distribution module is used to automatically distribute the event prompt information to the target business personnel through the information push channel included in the information push method.

[0042] An embodiment of the present application also provides an electronic device, comprising: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor and the memory communicate through the bus, and when the machine-readable instructions are executed by the processor, the steps of the event prompt method as described above are performed.

[0043] An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the event prompt method as described above are executed.

[0044] An event prompt method and device provided in an embodiment of the present application can realize timely and unified monitoring of business events by configuring a business event rule set through a customer management platform and from at least one business participant object dimension; in addition, according to the target business event rules, the event prompt information, information push method and target business personnel for the target business event are determined, so as to realize targeted personalized information push.

[0045] Among them, the business participant object dimension includes the dimension of the role level of the business personnel and / or the dimension of the customer group type. Each dimension corresponds to different business event rules, so the monitoring of business events can be flexibly achieved in different ways to meet different event prompt requirements.

[0046] Furthermore, the business participant dimension can also include at least one of the following: the product types responsible for business personnel at different role levels, the risk levels of concern to business personnel at different role levels, and the customer lifecycle stage. This allows for further refinement of the business personnel and / or customer dimensions, enabling more precise event notifications.

[0047] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without creative work.

[0049] Figure 1 One of the flow charts of an event prompt method provided in an embodiment of the present application is shown;

[0050] Figure 2 The second flowchart of an event prompt method provided by an embodiment of the present application is shown;

[0051] Figure 3 A schematic structural diagram of an event prompting device provided in an embodiment of the present application is shown;

[0052] Figure 4 A schematic structural diagram of an electronic device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0053] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application for which protection is claimed, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, each other embodiment obtained by those skilled in the art without making creative work falls within the scope of protection of the present application.

[0054] Research has found that in existing banking systems, events refer to business-significant information generated by changes in customer behavior or external factors. For example, events can impact customer financial needs, leading to new sales and service opportunities. Therefore, event notifications are a crucial feature for banks to better serve customers and strengthen risk management.

[0055] With the continuous development and innovation of banking services, various risks and issues are increasing, and various events frequently occur during business processing. However, existing technologies require developers to develop event-specific notification functions for individual business systems. These notification functions lack flexibility. Specifically, because existing technologies rely on a single event trigger mechanism and fail to account for differences in institutional hierarchies and customer profiles, they can lead to poor notification accuracy when new business scenarios are added or requirements change. Consequently, they cannot meet the rapidly evolving needs of banking services.

[0056] Based on this, an embodiment of the present application provides an event prompt method to achieve timely and unified monitoring of business events and targeted personalized information push.

[0057] See also Figure 1 , Figure 1 This is a flow chart of an event prompt method provided by an embodiment of the present application. The method provided by an embodiment of the present application is applied to a customer management platform. Figure 1 As shown in , the method includes:

[0058] S101. Construct a customer data mart based on the acquired bank internal system data and bank external system data.

[0059] Among them, bank internal system data includes data from at least one internal bank system, such as the credit system, core system, etc.; bank external system data includes data from at least one external bank system, such as the industrial and commercial system, credit reporting system, public market, etc. It should be noted that in this application, the acquisition of the above data is carried out based on the authorization of the user and relevant institutions.

[0060] In this step, based on data from the bank's internal and external systems, the frequency and key data items for each type of customer business event are determined, including event name, event type, event concept, desired goal, target customer group, detection trigger rules, required resources, and event pre-evaluation. The acquired data is then cleaned to remove duplicate, erroneous, or incomplete data. Data from various systems is then integrated into a unified public customer data mart, and business event types are defined to facilitate subsequent analysis and processing. The resulting integrated customer data mart includes data on each defined type of customer event.

[0061] S102: Configure a business event rule set for the customer data mart from at least one business participant object dimension.

[0062] The business participant dimension refers to the participant objects in the entire business process, including the dimension of the role level of the business personnel and / or the dimension of the customer group type.

[0063] Accordingly, step S102 may include:

[0064] From the dimension of the role level to which the business personnel belong, for each role level, a business event rule subset for that role level is configured to obtain a business event rule set for the customer data mart; the business event rule subset includes at least one business event rule.

[0065] For example, the role levels of business personnel may include the head office, branch, and account manager. For each role level, the rule configuration interface can be displayed through the front-end interface, and a subset of business event rules for each role level can be obtained through the front-end page operation configuration. In specific implementation, corresponding reminder rules are set according to different event types. These rules include different levels of role users, such as head office users, branch users, branch users, and account managers. Under a certain level, they can be further divided. For example, account managers can be further divided into supervisor account managers, assistant account managers, and custodial account managers, etc.; reminder time conditions (such as reminders a few days or hours in advance), reminder trigger conditions (such as the account balance is below a certain threshold), reminder frequency (one-time reminder or regular repeated reminders), reminder channels (SMS, APP push, voice call, email, etc.), and template settings for reminder content.

[0066] and / or,

[0067] From the dimension of customer group type, for each pre-set customer group list, a business event rule subset for the customer group list is configured to obtain a business event rule set for the customer data mart.

[0068] Customer lists can be sourced from a customer tagging platform. For example, these lists may include key customer lists uploaded by channels, strategic customer lists, focus lists, whitelisted customers, and risky customers. Similarly, for customer lists, a rule configuration interface can be displayed through the front-end interface. Through front-end page configuration, a subset of business event rules for each customer list can be obtained. Alert rules can also be triggered based on the list type, including time conditions, trigger conditions, reminder frequency, and reminder channel methods. Customer lists can be deduplicated using a bitmap deduplication algorithm.

[0069] Furthermore, the business participant object dimension also includes at least one of the following: the dimension of the product type that the business personnel are responsible for, the dimension of the risk level that the business personnel are concerned about, and the dimension of the life cycle stage that the customer is in. In this way, through combination, it is possible to further differentiate and refine the product types that business personnel at different role levels are responsible for and the event risk levels that business personnel at different role levels are concerned about. It is also possible to further differentiate and refine the life cycle stages of different customers in different customer lists (for example, new customers, mature customers, lost customers, etc.), thereby configuring different targeted business event rule sets, so that in subsequent steps, the target business events under the combined business participant object dimension can be more accurately identified, and more accurate event push can be achieved.

[0070] S103: Use the business event rule set corresponding to each business participant object dimension to monitor the customer data mart and identify target business events under each business participant object dimension.

[0071] The target business event refers to a business event that complies with at least one target business event rule in the business event rule set. Each business event rule in the business event rule set includes a business event triggering sub-rule.

[0072] In this step, data analysis tools and techniques are used to monitor the customer data mart in real time or periodically to identify events that meet the business event trigger sub-rules. The data interface can monitor both streaming and batch data. Once a target business event that meets the business event trigger sub-rule is detected, the system automatically triggers an alert process and records relevant information about the target business event, such as event type, trigger time, and involved customer information, for subsequent tracking and management.

[0073] In a possible implementation, step S103 may include:

[0074] S1031. Use each business event triggering sub-rule included in the business event rule set corresponding to each business participant object dimension to monitor the customer data mart and identify candidate target events under each business participant object dimension.

[0075] In this step, when the data in the customer data mart changes, the changed data can be monitored by each business event triggering sub-rule corresponding to each business participant object dimension to determine whether the generation of a candidate target event is triggered under each business participant object dimension.

[0076] S1032: De-duplicate the candidate target events to obtain the target business events.

[0077] Considering that multiple business event-triggered sub-rules may monitor the same change data, resulting in multiple candidate target events with the same content, pushing them separately would result in redundant event notifications and waste computing resources. Therefore, deduplication of candidate target events is necessary.

[0078] In a specific implementation, a message digest for each candidate target event can be generated based on the customer information and event information included in the candidate target event. Duplication of candidate target events can be performed based on the message digests of each candidate target event to obtain the target business event. For example, a message digest can be generated using a related algorithm in the prior art, such as MD5.

[0079] S104 : In response to the generation of the target business event, determine event prompt information, information push method, and target business personnel for the target business event according to the target business event rule.

[0080] Each business event rule in the business event rule set further includes an event information push sub-rule.

[0081] Regarding event prompt information, the event information push sub-rule includes a prompt information template; step S104 may include:

[0082] Extract characteristic information from the target business event; fill the characteristic information into a predetermined position in the prompt information template included in the target business event rule, and assemble to obtain the event prompt information.

[0083] Characteristic information can include customer identification, date, and transaction data. For example, a prompt message template might read: "Customer {CUST} experienced a large transaction of {amout} on {date}. Please pay attention." The event prompt message is assembled by filling the characteristic information from the target business event into the three predetermined positions in this template.

[0084] Regarding the target business personnel, when the business participant object dimension includes the dimension of the role level to which the business personnel belongs, step S104 may include:

[0085] Determine at least one role level corresponding to the target business event rule; determine the customer information included in the target business event; and determine the target business personnel based on the customer management relationship reserved in the customer management platform for each role level and the customer information.

[0086] Among them, customer information may include customer identification and customer organization, etc. According to the customer identification and customer organization, a query is performed in the customer management relationship to obtain the business personnel corresponding to each role level, and the target business personnel are obtained through integration.

[0087] When the business participation object dimension includes the dimension of customer group type, step S104 may include:

[0088] Determine the customer group list corresponding to the target business event rule; and determine the target business personnel based on the list subscription relationship reserved in the customer management platform.

[0089] In this step, the customer group lists corresponding to the target business event rules are determined, and based on the list subscription relationships, the business personnel who subscribe to these customer group lists are determined, and the target business personnel are obtained through integration.

[0090] Regarding the information push method, step S104 may include:

[0091] Determine the event information included in the target business event; the event information includes the event type; match the urgency corresponding to the event type with the priority and push channel preference of the candidate information push channels included in the target business event rules to determine the information push channel for the target business event; determine the information push method based on the information push channel.

[0092] Information push channels include, but are not limited to, system pop-ups, app message reminders, SMS notifications, email reminders, voice calls, etc. For example, for target business events of a higher-level urgency type, push notifications are made through the higher-priority information push channels; for target business events of a lower-level urgency type, push notifications are made through the information push channels preferred by the business personnel; after determining the information push channel, the information push method can be determined based on parameters such as push frequency and push time.

[0093] S105: Automatically distribute the event prompt information to the target business personnel through the information push channel included in the information push method.

[0094] In this step, the assembled event reminder information is automatically distributed to the target business personnel related to the target business event through the determined information push channel, push frequency, push time and other parameters, so as to achieve accurate personalized push.

[0095] Furthermore, after receiving event information, business tasks can perform different actions based on the information, such as viewing customer views, querying business opportunities, and querying risk events. Furthermore, various methods can be used to collect feedback from business personnel on pushed information, such as whether users clicked on the push information, performed the corresponding business operations according to the reminder, and whether they provided opinions or suggestions on the content or method of the reminder. Based on user feedback and the actual effectiveness of the reminder, business event rules, content, and channels can be evaluated and optimized.

[0096] See also Figure 2 , Figure 2 This is the second flow chart of an event prompt method provided by the embodiment of the present application. Figure 2 As shown in , the information prompting method provided by the embodiment of the present application includes:

[0097] Step 1: Data Collection and Integration: Collect customer event data from the bank's various internal and / or external systems, based on authorization. Internal data may include data from the bank's credit system, core system data, management accounting system data, and ECIF system data (Enterprise Customer Information Integration System). External data may include industrial and commercial data, judicial data, industry data, credit data, and public market data.

[0098] Step 2: Integrate the collected data into a unified corporate customer data mart to form a data architecture of subject layer - multi-dimensional layer - application layer for subsequent analysis and processing.

[0099] Step 3: Configure grading rules based on the role level of the business personnel.

[0100] Step 4: Configure the rules for the customer list based on the dimension of customer group type.

[0101] Step 5: Use data analysis tools and techniques to monitor the customer data mart to identify events that meet the target business event rules. For example, internal events include maturity events, information events, change events, repayment reminders, and early warning events; external events include news and information events, business information events, bidding events, and legal risk events.

[0102] Step 6: Push channel routing based on the customer’s marketing affiliation relationship, account manager marketing management relationship, and subscription relationship in the customer management platform.

[0103] Step 7: Collect feedback from business personnel on event information, and evaluate and optimize business event rules, event prompt information content, and information push channels.

[0104] An event prompt method provided by an embodiment of the present application constructs a customer data mart based on acquired bank internal system data and bank external system data; the customer data mart includes defined customer event data of various types; a business event rule set for the customer data mart is configured from at least one business participant object dimension; the customer data mart is monitored using the business event rule set corresponding to each business participant object dimension to identify target business events under each business participant object dimension; wherein the target business event refers to a business event that complies with at least one target business event rule in the business event rule set; in response to the generation of the target business event, event prompt information, information push method and target business personnel for the target business event are determined according to the target business event rule; and the event prompt information is automatically distributed to the target business personnel through the information push channel included in the information push method.

[0105] In this way, by configuring the business event rule set through the customer management platform and from at least one business participant object dimension, timely and unified monitoring of business events can be achieved; in addition, according to the target business event rules, the event prompt information, information push method and target business personnel for the target business event are determined, which can achieve targeted and personalized information push.

[0106] See also Figure 3 , Figure 3 This is a schematic diagram of the structure of an event prompt device provided in an embodiment of the present application. Figure 3 As shown in , the event prompting device 300 is applied to the customer management platform, including:

[0107] A construction module 310 is configured to construct a customer data mart based on the acquired bank's internal system data and bank's external system data; the customer data mart includes predefined customer event data of various types;

[0108] A configuration module 320 is configured to configure a business event rule set for the customer data mart from at least one business participant object dimension;

[0109] A monitoring module 330 is configured to monitor the customer data mart using the business event rule set corresponding to each business participant object dimension, and identify target business events under each business participant object dimension; wherein the target business event is a business event that complies with at least one target business event rule in the business event rule set;

[0110] A determination module 340 is configured to, in response to the occurrence of the target business event, determine event prompt information, information push method, and target business personnel for the target business event according to the target business event rule;

[0111] The distribution module 350 is configured to automatically distribute the event prompt information to the target business personnel through the information push channel included in the information push method.

[0112] Furthermore, the business participation object dimension includes a dimension of the role level of the business personnel and / or a dimension of the customer group type. When the configuration module 320 is used to configure the business event rule set for the customer data mart based on at least one business participation object dimension, the configuration module 320 is used to:

[0113] Based on the dimension of the role level to which the business personnel belong, for each role level, a business event rule subset for the role level is configured to obtain a business event rule set for the customer data mart; the business event rule subset includes at least one business event rule;

[0114] and / or,

[0115] From the dimension of customer group type, for each pre-set customer group list, a business event rule subset for the customer group list is configured to obtain a business event rule set for the customer data mart.

[0116] Furthermore, each business event rule in the business event rule set includes a business event triggering sub-rule. When the monitoring module 330 is used to monitor the customer data mart using the business event rule set corresponding to each business participant object dimension and identify target business events under each business participant object dimension, the monitoring module 330 is used to:

[0117] Using each business event trigger sub-rule included in the business event rule set corresponding to each business participant object dimension, monitoring the customer data mart to identify candidate target events under each business participant object dimension;

[0118] Deduplication is performed on the candidate target events to obtain the target business event.

[0119] Furthermore, when the monitoring module 330 is used to perform deduplication processing on the candidate target events to obtain the target business event, the monitoring module 330 is used to:

[0120] Generate a message summary of each candidate target event based on the customer information and event information included in the candidate target event;

[0121] Deduplication processing is performed on the candidate target events according to the message digest of each candidate target event to obtain the target business event.

[0122] Furthermore, each business event rule in the business event rule set includes an event information push sub-rule; the event information push sub-rule includes a prompt information template; when the determination module 340 is used to determine the event prompt information for the target business event in response to the generation of the target business event and according to the target business event rule, the determination module 340 is used to:

[0123] extracting feature information from the target business event;

[0124] The characteristic information is correspondingly filled into a predetermined position in the prompt information template included in the target business event rule, and the event prompt information is assembled to obtain the event prompt information.

[0125] Furthermore, when the business participant object dimension includes the dimension of the role hierarchy to which the business personnel belong, the determination module 340 is configured to determine, in response to the generation of the target business event, a target business personnel for the target business event according to the target business event rule. The determination module 340 is configured to:

[0126] Determining at least one role level corresponding to the target business event rule;

[0127] Determining customer information included in the target business event;

[0128] The target business personnel are determined based on the customer management relationship reserved in the customer management platform for each role level and the customer information.

[0129] Furthermore, when the business participant object dimension includes a customer group type dimension, the determination module 340 is configured to, in response to the generation of the target business event, determine a target business personnel for the target business event according to the target business event rule. The determination module 340 is configured to:

[0130] Determine the customer group list corresponding to the target business event rule;

[0131] The target business personnel are determined according to the list subscription relationship reserved in the customer management platform.

[0132] Furthermore, the determination module 340 is configured to determine, in response to the generation of the target business event and according to the target business event rule, an information push method for the target business event. The determination module 340 is configured to:

[0133] Determining event information included in the target business event; the event information includes an event type;

[0134] Matching the urgency corresponding to the event type with the priority and push channel preference of the candidate information push channels included in the target business event rule to determine the information push channel for the target business event;

[0135] The information push method is determined according to the information push channel.

[0136] Furthermore, the business participant object dimension also includes at least one of the following: a dimension of the product type that the business personnel is responsible for, a dimension of the risk level that the business personnel is concerned about, and a dimension of the life cycle stage of the customer.

[0137] See also Figure 4 , Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 4 As shown in FIG, the electronic device 400 includes a processor 410 , a memory 420 and a bus 430 .

[0138] The memory 420 stores machine-readable instructions executable by the processor 410. When the electronic device 400 is running, the processor 410 communicates with the memory 420 via the bus 430. When the machine-readable instructions are executed by the processor 410, the above-mentioned Figure 1 as well as Figure 2 The specific implementation of the steps of the event prompt method in the method embodiment shown can be found in the method embodiment, and will not be repeated here.

[0139] The embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the computer program can execute the above-mentioned Figure 1 as well as Figure 2 The specific implementation of the steps of the event prompt method in the method embodiment shown can be found in the method embodiment, and will not be repeated here.

[0140] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0141] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. There may be other division methods in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed may be through some communication interface, indirect coupling or communication connection of devices or units, which may be electrical, mechanical or other forms.

[0142] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0143] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0144] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0145] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The scope of protection of the present application is not limited thereto. Although the present application has been described in detail with reference to the above-mentioned embodiments, those skilled in the art should understand that any person skilled in the art can modify or easily conceive of changes to the technical solutions described in the above-mentioned embodiments within the technical scope disclosed in the present application, or perform equivalent replacements for some of the technical features thereof. These modifications, changes, or replacements do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. An event prompt method, characterized in that: Applied to a customer management platform, the method includes: Building a customer data mart based on the acquired bank's internal system data and bank's external system data; the customer data mart includes various types of defined customer event data; Configuring a business event rule set for the customer data mart from at least one business participation object dimension; Monitor the customer data mart using the business event rule set corresponding to each business participant object dimension to identify a target business event under each business participant object dimension; wherein the target business event refers to a business event that complies with at least one target business event rule in the business event rule set; In response to the generation of the target business event, determining event prompt information, information push method, and target business personnel for the target business event according to the target business event rule; The event prompt information is automatically distributed to the target business personnel through the information push channel included in the information push method.

2. The method according to claim 1, characterized in that The business participation object dimension includes the dimension of the role level of the business personnel and / or the dimension of the customer group type. Configuring a business event rule set for the customer data mart based on at least one business participation object dimension includes: Based on the dimension of the role level to which the business personnel belong, for each role level, a business event rule subset for the role level is configured to obtain a business event rule set for the customer data mart; the business event rule subset includes at least one business event rule; and / or, From the dimension of customer group type, for each pre-set customer group list, a business event rule subset for the customer group list is configured to obtain a business event rule set for the customer data mart.

3. The method according to claim 2, characterized in that Each business event rule in the business event rule set includes a business event triggering sub-rule; monitoring the customer data mart using the business event rule set corresponding to each business participant object dimension to identify target business events under each business participant object dimension includes: Using each business event trigger sub-rule included in the business event rule set corresponding to each business participant object dimension, monitoring the customer data mart to identify candidate target events under each business participant object dimension; Deduplication is performed on the candidate target events to obtain the target business event.

4. The method according to claim 3, characterized in that Deduplication processing is performed on the candidate target events to obtain the target business event, including: Generate a message summary of each candidate target event based on the customer information and event information included in the candidate target event; Deduplication processing is performed on the candidate target events according to the message digest of each candidate target event to obtain the target business event.

5. The method according to claim 2, characterized in that Each business event rule in the business event rule set includes an event information push sub-rule; the event information push sub-rule includes a prompt information template; In response to the generation of the target business event, determining event prompt information for the target business event according to the target business event rule, including: extracting feature information from the target business event; The characteristic information is correspondingly filled into a predetermined position in the prompt information template included in the target business event rule, and the event prompt information is assembled to obtain the event prompt information.

6. The method according to claim 2, characterized in that When the business participant object dimension includes the dimension of the role level to which the business personnel belong, in response to the generation of the target business event, determining the target business personnel for the target business event according to the target business event rule includes: Determining at least one role level corresponding to the target business event rule; Determining customer information included in the target business event; The target business personnel are determined based on the customer management relationship reserved in the customer management platform for each role level and the customer information.

7. The method according to claim 2, characterized in that When the business participant object dimension includes a customer group type dimension, in response to the generation of the target business event, determining a target business personnel for the target business event according to the target business event rule includes: Determine the customer group list corresponding to the target business event rule; The target business personnel are determined according to the list subscription relationship reserved in the customer management platform.

8. The method according to claim 1, characterized in that In response to the generation of the target business event, determining an information push method for the target business event according to the target business event rule, including: Determining event information included in the target business event; the event information includes an event type; Matching the urgency corresponding to the event type with the priority and push channel preference of the candidate information push channels included in the target business event rule to determine the information push channel for the target business event; The information push method is determined according to the information push channel.

9. The method according to claim 2, characterized in that The business participant object dimension also includes at least one of the following: a dimension of the product type that the business personnel is responsible for, a dimension of the risk level that the business personnel is concerned about, and a dimension of the life cycle stage of the customer.

10. An event prompting device, characterized in that: Applied to a customer management platform, the device includes: A construction module, configured to construct a customer data mart based on the acquired bank's internal system data and bank's external system data; the customer data mart includes predefined customer event data of various types; A configuration module, configured to configure a business event rule set for the customer data mart from at least one business participant object dimension; a monitoring module, configured to monitor the customer data mart using the business event rule set corresponding to each business participant object dimension, and identify a target business event under each business participant object dimension; wherein the target business event is a business event that complies with at least one target business event rule in the business event rule set; A determination module, configured to, in response to the generation of the target business event, determine event prompt information, information push method, and target business personnel for the target business event according to the target business event rule; A distribution module is used to automatically distribute the event prompt information to the target business personnel through the information push channel included in the information push method.

Images