System based on risk control index management channel

Abstract

The invention provides a system for managing channels based on risk control indexes. The system comprises a back-end service unit and a front-end interaction unit, the back-end service unit is constructed based on a Java technology stack and is configured with a core framework, a data storage component and a business processing module, the core framework is used for constructing a service architecture, the data storage component comprises a cache database and a relational database which are respectively used for caching dynamic data and storing static configuration data, and the business processing module is used for processing the dynamic data and the static configuration data. The business processing module comprises a main control module and at least four sub-function modules, and the main control module is used for monitoring the running state of the sub-function modules and realizing exception recovery; the front-end interaction unit is constructed based on a Web technology, and is used for providing a visual operation interface, real-time data display and early warning information pushing and receiving functions, and establishing a data interaction channel with the rear-end service unit through a real-time communication protocol; the problem of automatic updating of strategy configuration of a virtual merchant management channel and the problem of real-time monitoring of channel violation data are solved.

Description

Technical Field

[0001] This invention belongs to the field of telecommunications, and in particular relates to a system for managing channels based on risk control indicators. Background Technology

[0002] The current channel management model for mobile virtual network operators (MVNOs) has significant drawbacks. Essentially, it's a passive management mechanism reliant on manual operation. Specifically, staff only intervene when a partner channel's business development exceeds predetermined targets. This intervention includes manually shutting down the channel, halting its new user acquisition process, and even suspending services and limiting call frequency for existing users. This traditional manual management model is not only inefficient, wasting significant human resources on repetitive manual tasks, but also suffers from significant delays due to human error. The entire process lacks automation and intelligent support, failing to meet the demands of efficient operation, and urgently requires the introduction of more advanced technologies to achieve a transformation and upgrade in management. Summary of the Invention

[0003] The purpose of this embodiment is to provide a system for managing channels based on risk control indicators, which can solve the problems of automatic updating of strategy configurations for virtual merchant management channels and real-time monitoring of channel violation data.

[0004] A system based on risk control indicator management channels includes a backend service unit and a frontend interaction unit. The backend service unit is built on a Java technology stack and is configured with a core framework, data storage components, and business processing modules. The core framework is used to build the service architecture. The data storage components include a cache database and a relational database, used to cache dynamic data and store static configuration data, respectively. The business processing modules include a main control module and at least four sub-functional modules. The main control module is used to monitor the running status of the sub-functional modules and realize anomaly recovery. The frontend interaction unit is built on Web technology and is used to provide a visual operation interface, real-time data display, and early warning information push and reception functions. It also establishes a data interaction channel with the backend service unit through a real-time communication protocol.

[0005] Furthermore, the core framework of the backend service unit includes the Spring Boot framework. Among the data storage components, the cache database includes Redis, which is used to cache policy configuration data and violation statistics data, and the relational database includes MySQL, which is used to store indicator configuration tables and handling rule tables. The indicator configuration table at least includes a channel identifier field and indicator fields corresponding to different operators or regulatory agencies. The handling rule table at least includes a policy identifier field, a channel association field, a package type field, a risk control type field, a trigger threshold field, and a handling method field, and establishes a relationship with the indicator configuration table through the channel association field.

[0006] Furthermore, the indicator configuration table is specifically a channel master indicator configuration table, whose table structure includes: a channel id field as the primary key, fields storing China Mobile indicators, fields storing China Telecom indicators, fields storing China Unicom indicators, fields storing Joint Office indicators, and fields storing whistleblower indicators; the handling rules table is specifically a channel violation handling rules table, whose table structure includes: a strategy id field as an auto-incrementing primary key, a channel id field associated with the primary key of the channel master indicator configuration table, fields representing package types (including basic packages, data packages, and bundled packages), fields representing risk control indicator types (including mobile violations, telecom violations, Unicom violations, Joint Office violations, and fraud violations), fields representing the upper limit trigger ratio, and fields representing the handling method (including call frequency limiting, service suspension, and account suspension); the storage engine for the channel master indicator configuration table and the channel violation handling rules table is InnoDB, and the character set is utf8mb4.

[0007] Furthermore, the main control module implements operation monitoring and abnormal restart through a daemon process. The working mechanism of the daemon process includes: when the backend service unit starts, the main control module creates an independent thread as a daemon process to automatically trigger the initialization and startup of each sub-functional module; the daemon process reads the sub-functional module running status identifiers stored in the cache database at preset time intervals to determine whether each sub-functional module is running normally; if a sub-functional module is detected to be running abnormally or not started, the instance object of the sub-functional module is obtained through the context container of the backend service unit, a new thread is created to load and run the instance, and the running status identifier of the corresponding sub-functional module in the cache database is updated to normal.

[0008] Furthermore, the sub-functional module includes an automatic policy configuration update module, which is an executable thread component used to synchronize configuration data between the relational database and the cache database. Its synchronization mechanism includes: scanning the indicator configuration table and the disposal rule table in the relational database at preset time intervals to obtain the latest configuration data; comparing the latest configuration data with historical configuration data stored in the cache database to identify newly added, deleted, or changed configuration data; for newly added configuration data, creating a corresponding storage key in the cache database and writing the data; for deleted configuration data, deleting the corresponding storage key and data in the cache database; if it is indicator configuration data that is deleted, also synchronously deleting the associated disposal rule cache data; for changed configuration data, updating the value of the corresponding storage key in the cache database; the preset time interval is 1 second; the storage key used to store indicator configuration data in the cache database is of hash type, and the storage key used to store disposal rule data is of value type; and the disposal rule data is grouped and stored according to channel identifiers.

[0009] Furthermore, the sub-functional module includes a violation data monitoring module, which is an executable thread component used to collect, statistically analyze, and validate violation data. Its workflow includes: monitoring violation data pushed from external data sources at preset time intervals; the violation data at least includes channel identifier, violation type, and violation time information; parsing the monitored violation data, extracting key fields, and generating data statistical keys according to the rule of "channel identifier + violation type + time segment," where the time segment is a time unit divided by hours, formatted from the violation time; cumulatively counting the number of violation data entries corresponding to each statistical key through a cache database; reading the corresponding handling rule data from the cache database based on the channel identifier in the violation data; comparing the cumulative count result with the trigger threshold in the handling rule data; if the cumulative count reaches or exceeds the trigger threshold, constructing a violation warning message and pushing it to a preset message queue.

[0010] Furthermore, the sub-functional module includes a data tagging module, which is a message subscription component used to receive violation warning messages and generate handling instructions. Its processing mechanism includes: subscribing to a message queue that stores violation warning messages and obtaining violation warning messages in the queue in real time; parsing the violation warning messages to extract channel identifier, violation type, cumulative violation count, and corresponding handling method information; cumulatively updating the number of violation tags corresponding to the channel identifier through a cache database; based on the extracted information and the cumulative number of violation tags, constructing a channel handling message containing channel identifier, violation information, handling method, and tag count, and pushing the message to another preset message queue; the storage key used to store the number of violation tags in the cache database is associated with the channel identifier and stored as a value type.

[0011] Furthermore, the sub-functional module includes a channel handling module, which is a message subscription component used to receive channel handling messages and perform automated handling. Its handling mechanism includes: subscribing to a message queue that stores channel handling messages and obtaining channel handling messages in the queue in real time; parsing the channel handling messages to extract the channel identifier, number of violation markers, and handling method information; and performing tiered handling operations based on the number of violation markers: when the number of violation markers is 1, call frequency limiting is performed, that is, calling an external interface to limit the call frequency of users under this channel; when the number of violation markers is 2, service suspension is performed, that is, calling an external interface to suspend the service of all users under this channel; when the number of violation markers is ≥3, account opening suspension is performed, that is, calling an external interface to prohibit the opening of new user accounts for this channel; after the handling operation is executed, a handling notification containing the channel identifier, handling time, violation type, and handling result is constructed and pushed to the front-end interaction unit through a real-time communication protocol.

[0012] Furthermore, the real-time communication protocol between the front-end interaction unit and the back-end service unit is WebSocket. The back-end service unit is configured with a WebSocket service component, which establishes a communication endpoint through a preset URL path to manage the connection, disconnection, and message push of the front-end interaction unit. The working mechanism of the WebSocket service component includes: when the front-end interaction unit initiates a connection request, a session object is created and added to the session collection; when the front-end interaction unit disconnects, the corresponding session object is removed from the session collection; when the back-end service unit generates a disposal notification, all session objects in the session collection are traversed, the disposal notification is converted into a JSON format string, and then pushed to each session object; if a connection abnormality occurs during communication, the front-end interaction unit automatically re-initiates a connection request at preset time intervals.

[0013] Furthermore, the front-end interaction unit includes the following functional modules: a tag switching module, used to switch between different functional pages, automatically loading the latest configuration data when switching to the strategy configuration page; a data rendering module, used to render the loaded indicator configuration data and disposal rule data into tables, and to render the received disposal notifications into real-time warning entries and disposal record entries; a warning management module, used to control the number of real-time warning entries, deleting the oldest generated warning entry when the number of entries exceeds a preset limit; and a date formatting module, used to convert the timestamp in the disposal notification into a date string in a preset format; the preset limit includes 10 entries, and the preset format is "yyyy-MM-ddHH:mm:ss". This invention provides a system based on risk control indicator management channels, which solves the following problems:

[0014] The issue of automatic updates to strategy configurations for virtual merchant management channels.

[0015] The issue of real-time monitoring of channel violation data includes the system automatically accumulating the number, triggering rules, executing actions, and pushing the data to the front end.

[0016] The lack of a tiered strategy for handling channel violations includes situations where a first violation triggers call frequency throttling, a second violation results in service suspension, and a third violation results in account suspension.

[0017] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0018] Figure 1 : A system structure diagram of a risk control indicator management channel provided in an embodiment of the present invention;

[0019] Figure 2 : This is a flowchart of the main control module based on the risk control indicator management channel provided in an embodiment of the present invention;

[0020] Figure 3 : Flowchart of the automatic update module for strategy configuration based on risk control indicator management channels provided in this embodiment of the invention;

[0021] Figure 4 : A flowchart of a violation data monitoring module based on risk control indicator management channels provided in an embodiment of the present invention;

[0022] Figure 5 : A flowchart of the data tagging module based on risk control indicator management channels provided in this embodiment of the invention;

[0023] Figure 6 : A flowchart of the channel handling module based on risk control indicator management channels provided in an embodiment of the present invention. Detailed Implementation

[0024] The technical solutions of the present invention will now be described with reference to the accompanying drawings in the embodiments of the present invention.

[0025] This invention provides a system based on risk control indicator management channels (see...). Figure 1 ),include:

[0026] I. Technical Architecture of this Embodiment:

[0027] This embodiment is implemented using Java (backend) and HTML+JS (frontend), adopting a "backend service + frontend visualization" architecture. The backend uses the Spring Boot framework to build the main control system and four sub-modules, utilizes Redis to cache policy configuration and violation data, and MySQL to store indicator configuration tables and handling rule tables; the frontend uses HTML to build a visualization interface, and JS to implement real-time data rendering and early warning notification display.

[0028] II. Backend Implementation (Java Language) in this Implementation Example:

[0029] (a) The environmental dependencies in specific implementations include:

[0030] Development framework: Spring Boot 2.7.x

[0031] - Database: MySQL 8.0, Redis 6.2.x

[0032] - Core dependencies: Spring Data JPA (data access), Redisson (Redis distributed lock), Quartz (scheduled tasks), WebSocket (real-time push).

[0033] (II) Specific database table design in this embodiment:

[0034]

[0035] (III) Implementation of the main core modules:

[0036] 1. Main control module (daemon process), (see...) Figure 2 This is used to monitor the status of submodule worker processes and automatically restart them in case of abnormalities. In practice, it's implemented by creating a daemon process through the Spring Boot startup class. This includes the backend starting the Spring Boot application, the main control system creating the daemon process, automatically starting the worker processes of the four main submodules, and the frontend opening an HTML page and establishing a WebSocket connection.

[0037]

[0038]

[0039] 2. The strategy configuration auto-update module (timed scan + cache synchronization) scans the MySQL database every second to synchronize the main indicators and action rules to the Redis cache (including the indicator pool and rule pool). (See...) Figure 3 ):

[0040]

[0041]

[0042]

[0043] 3. Violation Data Monitoring Module (Data Listening + Rule Comparison): This module listens for violation data (simulating retrieval from a message queue), splits the data, accumulates the number of violations by channel, violation type, and time period, and compares it with the rules in the cache. If a violation is triggered, a message is sent to the marking queue (see...). Figure 4 ):

[0044]

[0045]

[0046]

[0047]

[0048] 4. Data Tagging Module (Message Subscription + Queue Enqueue): This module subscribes to the tagging queue, accumulates the number of channel tags after receiving messages, and sends the processing information to the processing queue. (See...) Figure 5 ):

[0049]

[0050]

[0051]

[0052] 5. Channel Processing Module (Tiered Automated Processing): This module subscribes to the processing queue and executes tiered processing based on the number of marked occurrences (call frequency limiting -> service suspension -> account opening suspension), pushing the results to the front end via WebSocket. (See...) Figure 6 Includes code:

[0053]

[0054]

[0055] 6. Front-end display module: Used for real-time display of handling records, real-time alerts and policy configurations on the front end, including visual viewing and monitoring front-end implementation.

[0056] This invention provides a system based on risk control indicator management channels, which solves the following problems:

[0057] The issue of automatic updates to strategy configurations for virtual merchant management channels.

[0058] The issue of real-time monitoring of channel violation data includes the system automatically accumulating the number, triggering rules, executing actions, and pushing the data to the front end.

[0059] The lack of a tiered strategy for handling channel violations includes situations where a first violation triggers call frequency throttling, a second violation results in service suspension, and a third violation results in account suspension.

[0060] The above description is merely an embodiment of the present invention and is not intended to limit the scope of protection of the present invention. For those skilled in the art, the present invention can have various modifications and variations. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A system based on risk control indicator management channels, characterized in that, It includes a backend service unit and a frontend interaction unit. The backend service unit is built on the Java technology stack and is configured with a core framework, data storage components, and business processing modules. The core framework is used to build the service architecture. The data storage components include a cache database and a relational database, used to cache dynamic data and store static configuration data, respectively. The business processing modules include a main control module and at least four sub-functional modules. The main control module is used to monitor the running status of the sub-functional modules and realize anomaly recovery. The frontend interaction unit is built on Web technology and is used to provide a visual operation interface, real-time data display, and early warning information push and receiving functions. It also establishes a data interaction channel with the backend service unit through a real-time communication protocol.

2. The system based on risk control indicator management channels according to claim 1, characterized in that, The core framework of the backend service unit includes the Spring Boot framework. Among the data storage components, the cache database includes Redis, which is used to cache policy configuration data and violation statistics data, and the relational database includes MySQL, which is used to store indicator configuration tables and handling rule tables. The indicator configuration table at least includes a channel identifier field and indicator fields corresponding to different operators or regulatory agencies. The handling rule table at least includes a policy identifier field, a channel association field, a package type field, a risk control type field, a trigger threshold field, and a handling method field, and establishes a relationship with the indicator configuration table through the channel association field.

3. The system based on risk control indicator management channels according to claim 2, characterized in that, The indicator configuration table is specifically a channel master indicator configuration table, whose structure includes: a channel id field as the primary key, fields storing China Mobile indicators, fields storing China Telecom indicators, fields storing China Unicom indicators, fields storing Joint Office indicators, and fields storing whistleblower indicators; the handling rules table is specifically a channel violation handling rules table, whose structure includes: a strategy id field as an auto-incrementing primary key, a channel id field associated with the primary key of the channel master indicator configuration table, fields representing package types (including basic packages, data packages, and bundled packages), fields representing risk control indicator types (including mobile violations, telecom violations, Unicom violations, Joint Office violations, and fraud violations), fields representing the upper limit trigger ratio, and fields representing the handling method (including call frequency limiting, service suspension, and account suspension); the storage engine for both the channel master indicator configuration table and the channel violation handling rules table is InnoDB, and the character set is utf8mb4.

4. The system based on risk control indicator management channels according to claim 1, characterized in that, The main control module implements operation monitoring and abnormal restart through a daemon process. The working mechanism of the daemon process includes: when the backend service unit starts, the main control module creates an independent thread as a daemon process to automatically trigger the initialization and startup of each sub-functional module; the daemon process reads the sub-functional module running status identifiers stored in the cache database at preset time intervals to determine whether each sub-functional module is running normally; if a sub-functional module is detected to be running abnormally or not started, the instance object of the sub-functional module is obtained through the context container of the backend service unit, a new thread is created to load and run the instance, and the running status identifier of the corresponding sub-functional module in the cache database is updated to normal.

5. The system based on risk control indicator management channels according to claim 4, characterized in that, The sub-functional module includes a strategy configuration automatic update module, which is an executable thread component used to synchronize configuration data between the relational database and the cache database. Its synchronization mechanism includes: scanning the indicator configuration table and the processing rule table in the relational database at preset time intervals to obtain the latest configuration data; The latest configuration data is compared with the historical configuration data stored in the cache database to identify newly added, deleted, or modified configuration data. For newly added configuration data, a corresponding storage key is created in the cache database and the data is written. For deleted configuration data, the corresponding storage key and data in the cache database are deleted. If the deletion is of indicator configuration data, the associated processing rule cache data is also deleted simultaneously. For modified configuration data, the value of the corresponding storage key in the cache database is updated. The preset time interval is 1 second. The storage key used to store indicator configuration data in the cache database is of hash type, and the storage key used to store processing rule data is of value type. The processing rule data is grouped and stored according to channel identifier.

6. The system based on risk control indicator management channels according to claim 4, characterized in that, The sub-functional module includes a violation data monitoring module, which is an executable thread component used to collect, count and verify violation data; Its workflow includes: monitoring violation data pushed by external data sources at preset time intervals, wherein the violation data includes at least channel identifier, violation type, and violation time information; parsing the monitored violation data, extracting key fields, and generating data statistics keys according to the rule of "channel identifier + violation type + time segment", wherein the time segment is a time unit divided by hours and obtained by formatting the violation time; cumulatively counting the number of violation data entries corresponding to each statistics key through a cache database; reading the corresponding handling rule data of the channel from the cache database according to the channel identifier in the violation data; comparing the cumulative count result with the trigger threshold in the handling rule data, and if the cumulative count reaches or exceeds the trigger threshold, constructing a violation warning message and pushing it to a preset message queue.

7. The system based on risk control indicator management channels according to claim 6, characterized in that, The sub-functional module includes a data tagging module, which is a message subscription component used to receive violation warning messages and generate handling instructions; Its processing mechanism includes: subscribing to a message queue that stores violation warning messages, and retrieving violation warning messages from the queue in real time; The system parses violation warning messages to extract information such as channel identifier, violation type, cumulative number of violations, and corresponding handling methods. It then updates the cumulative number of violation markers corresponding to the channel identifier using a cache database. Based on the extracted information and the cumulative number of violation markers, it constructs a channel handling message containing the channel identifier, violation information, handling method, and number of markers, and pushes this message to another preset message queue. The storage key in the cache database used to store the number of violation markers is associated with the channel identifier and stored as a value.

8. The system based on risk control indicator management channels according to claim 7, characterized in that, The sub-functional module includes a channel processing module, which is a message subscription component used to receive channel processing messages and perform automated processing; Its handling mechanism includes: subscribing to a message queue that stores channel handling messages and retrieving channel handling messages from the queue in real time; Parse the channel handling message to extract the channel identifier, number of violation markers, and handling method information; execute tiered handling operations based on the number of violation markers: when the number of violation markers includes 1, execute call frequency limiting, i.e., call an external interface to limit the call frequency of users under this channel; when the number of violation markers includes 2, execute service suspension, i.e., call an external interface to suspend the service of all users under this channel; when the number of violation markers is ≥3, execute account opening suspension, i.e., call an external interface to prohibit the opening of new user accounts for this channel; after the handling operation is executed, construct a handling notification containing the channel identifier, handling time, violation type, and handling result, and push it to the front-end interaction unit through a real-time communication protocol.

9. The system based on risk control indicator management channels according to claim 1, characterized in that, The real-time communication protocol between the front-end interaction unit and the back-end service unit is WebSocket. The back-end service unit is configured with a WebSocket service component, which establishes a communication endpoint through a preset URL path and is used to manage the connection, disconnection and message push of the front-end interaction unit. The working mechanism of the WebSocket service component includes: when the front-end interaction unit initiates a connection request, it creates a session object and adds it to the session collection; when the front-end interaction unit disconnects, it removes the corresponding session object from the session collection; when the back-end service unit generates a disposal notification, it iterates through all session objects in the session collection, converts the disposal notification into a JSON format string, and pushes it to each session object; if a connection error occurs during communication, the front-end interaction unit automatically re-initiates a connection request at a preset time interval.

10. The system based on risk control indicator management channels according to claim 9, characterized in that, The functional modules of the front-end interaction unit include: a tag switching module, used to switch between different functional pages, and automatically load the latest configuration data when switching to the strategy configuration page; a data rendering module, used to render the loaded indicator configuration data and disposal rule data into tables for display, and render the received disposal notifications into real-time warning entries and disposal record entries for display; a warning management module, used to control the number of real-time warning entries, and delete the oldest warning entry when the number of entries exceeds the preset limit; and a date formatting module, used to convert the timestamp in the disposal notification into a date string in a preset format; the preset limit includes 10 entries, and the preset format is "yyyy-MM-dd HH:mm:ss".

Images