Data management system, method, electronic device, and storage medium
By constructing a single data source ledger module, a service ledger module, a variable ledger module, and a variable relationship engine ledger module, the complexity of risk variable management was solved, and the accuracy of risk decision-making results was improved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- WEBANK (CHINA)
- Filing Date
- 2023-11-28
- Publication Date
- 2026-05-29
AI Technical Summary
Existing technologies cannot effectively manage risk variables, leading to inaccurate risk decision-making results. This is mainly due to the complexity of risk variable sources and the variety of data sources, as well as the lack of unified registration and management.
The system constructs a single data source ledger module, a service ledger module, a variable ledger module, and a variable relationship engine ledger module to achieve full-process management of risk variables. By storing and monitoring the flow of risk variables through mapping relationships, the system improves the accuracy of decision-making.
It enables full lifecycle management of risk variables, improves the accuracy of risk decision-making results, and ensures effective management of risk data through full-process monitoring and registration management.
Smart Images
Figure CN117632906B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of data processing technology, and in particular to a data management system, method, electronic device and storage medium. Background Technology
[0002] Currently, when processing risk data for decision-making, it is generally necessary to acquire risk variables, input them into a decision engine, and output the corresponding decision. Since risk variables directly affect the outcome of risk decisions, their management is particularly important. However, due to the complexity of risk routing (risk variables can be calculated directly from external data sources or be the output of the decision engine used as input to downstream engines), their large number, and the variety of data sources, effective management of risk variables is impossible, thus affecting the outcome of risk decisions. Summary of the Invention
[0003] The main objective of this application is to provide a data management system, method, electronic device, and storage medium, which aims to solve the technical problem of how to effectively manage risk variables and thereby improve the accuracy of risk decision-making results.
[0004] To achieve the above objectives, this application provides a data management system, which includes:
[0005] The Single Data Source Ledger Module is used to determine the data source information for making risk variable decisions and store the data source information in a preset Single Data Source Ledger.
[0006] The service ledger module is used to obtain the script information, policy information and service information of abnormal accounts in the target data source corresponding to the data source information, and assign a script identifier to the script information, a policy identifier to the policy information and a service identifier to the service information, and store the first mapping relationship between the script identifier, policy identifier and service identifier in the preset service ledger.
[0007] The variable ledger module is used to determine a specific variable strategy based on the strategy information, and to determine a second mapping relationship between the script identifier and the specific variable strategy based on the first mapping relationship, and to store the second mapping relationship in a preset variable ledger;
[0008] The variable relationship engine ledger module is used to determine the full-process mapping relationship between the script identifier and the specific variable strategy, and to store the full-process mapping relationship in a preset variable relationship engine ledger.
[0009] Optionally, the single data source ledger module is used to determine the data source type included in the data source information. If the data source type is a single data source, when it is determined that the first data source name included in the data source information does not match the preset single data source ledger, a single data source identifier corresponding to the data source information is assigned, and the third mapping relationship between the single data source identifier and the first data source name is stored in the single data source ledger.
[0010] Optionally, the single data source ledger module is used to determine the second data source name corresponding to each single data source information contained in the data source information when the data source type is determined to be a combined data source;
[0011] Determine the single data source identifier corresponding to all the second data source names, and merge all the single data source identifiers corresponding to the second data source names to obtain a new single data source identifier.
[0012] All the second data source names are merged to obtain the target data source name. The fourth mapping relationship between the new single data source identifier and the target data source name is stored in the single data source ledger.
[0013] Optionally, the single data source ledger module is used to traverse each second data source name and detect whether there is a matching data source name in the single data source ledger that matches the traversed second data source name;
[0014] If a matching data source name exists, the single data source identifier corresponding to the matching data source name in the single data source ledger will be used as the single data source identifier corresponding to the second data source name to be traversed.
[0015] If no matching data source name is found, a single data source identifier is assigned to the second data source name being iterated over.
[0016] Optionally, the service ledger module is used to determine the script information corresponding to the abnormal account in the data source information, determine the abnormal type based on the script information, and determine the service information and policy information to be applied for the abnormal type. The module assigns a script identifier to the script information, a policy identifier to the policy information, and a service identifier to the service information. It stores the first mapping relationship between the script identifier, policy identifier, and service identifier in a preset service ledger. The service information includes at least one of the following: service name, whether it is a main path, service type, service release status, service version number, service dependencies for rule-based services, service dependencies for variable-based services, whether it is allowed to calculate variables when the service is not called by the engine, service registration personnel, and service registration department.
[0017] Optionally, the variable ledger module is used to determine the variable data in the script information based on the strategy information, determine the specific variable strategy based on the data characteristics in the variable data, determine the second mapping relationship between the script identifier and the specific variable strategy based on the first mapping relationship, and store the second mapping relationship in a preset variable ledger. The specific variable strategy includes variable identifier, variable name, variable logic, variable default value, variable data type, variable release status, variable registration personnel, and variable registration department.
[0018] Optionally, the variable relationship engine ledger module is used to determine the fifth mapping relationship between script identifier, service identifier, strategy identifier, variable identifier and rule-type strategy identifier, and to use the fifth mapping relationship as the full-process mapping relationship, and to store the full-process mapping relationship in the preset variable relationship engine ledger.
[0019] Furthermore, to achieve the above objectives, this application also provides a data management method applied to the aforementioned data management system, comprising the following steps:
[0020] Determine the data source information for making risk variable decisions and store the data source information in a preset single data source ledger;
[0021] Obtain the script information, policy information, and service information of the abnormal account in the target data source corresponding to the data source information, and assign a script identifier to the script information, a policy identifier to the policy information, and a service identifier to the service information. Store the first mapping relationship between the script identifier, policy identifier, and service identifier in a preset service ledger.
[0022] A specific variable strategy is determined based on the strategy information, and a second mapping relationship between the script identifier and the specific variable strategy is determined based on the first mapping relationship. The second mapping relationship is then stored in a preset variable ledger.
[0023] Determine the full-process mapping relationship between the script identifier and the specific variable strategy, and store the full-process mapping relationship in a preset variable relationship engine ledger.
[0024] This application also provides an electronic device, which is a physical device, comprising: a memory, a processor, and a program of the data management method stored in the memory and executable on the processor. When the program of the data management method is executed by the processor, it can implement the steps of the data management method as described above.
[0025] This application also provides a readable storage medium, which is a computer-readable storage medium, on which a program implementing a data management method is stored, and the program implementing the data management method is executed by a processor to implement the steps of the data management method as described above.
[0026] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the data management method described above.
[0027] The technical solution of this application achieves comprehensive management of these ledgers by constructing a single data source ledger module, a service ledger module, a variable ledger module, and a variable relationship engine ledger module. This improves the effectiveness of risk variable decision-making throughout the entire process, from business to technology to risk management, and enhances the accuracy of risk decision results. Furthermore, it enables full lifecycle management of risk variable flows through these ledgers. By transferring complex risk routing to the service ledger, variable ledger, and variable relationship engine ledger for registration and management, and managing multiple data sources through a single data source ledger, it achieves full monitoring and management of the risk data decision-making process, realizing effective management of risk variables and improving the accuracy of risk decision results. Attached Figure Description
[0028] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.
[0029] To more clearly illustrate the technical solutions in this embodiment or the prior art, the accompanying drawings used in the description of the embodiment or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0030] Figure 1 This is a schematic diagram of the system framework modules of the first embodiment of the data management system of this application;
[0031] Figure 2 This is a schematic diagram of each level in the first embodiment of the data management system of this application;
[0032] Figure 3 This is a flowchart illustrating the data management method of this application;
[0033] Figure 4 This is a schematic diagram of the hardware operating environment involved in the device in this embodiment.
[0034] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation
[0035] To make the above-mentioned objectives, features, and advantages of this application more apparent and understandable, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of this application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0036] The data management system in this embodiment can be designed for risk decision-making processes, automatically recording and updating relevant parameter information to various ledgers according to the risk decision-making process. Optionally, the risk decision-making process includes pulling data sources from external sources, calculating risk variables based on the data sources, transmitting the calculated risk variables to the decision engine, and the decision engine outputting the results.
[0037] Optionally, current risk variables suffer from several drawbacks. Firstly, there's a lack of unified registration (e.g., due to rapid business growth, unified registration is not implemented); secondly, development is often siloed, with variable development distributed across multiple teams; and thirdly, management is complex (e.g., unclear origins, processing locations, and destinations of variables, with past deficiencies in intermediate steps). These issues hinder effective management of risk variables and negatively impact the validity of risk decision-making. To address this deficiency, this embodiment provides a data management system that integrates a single data source ledger module A10, a service ledger module A20, a variable ledger module A30, and a variable relationship engine ledger module A40 to comprehensively manage risk variables, thereby improving the effectiveness of risk decision-making.
[0038] Optionally, when managing risk variables through a data management system, the entire lifecycle management of the risk variable flow will be comprehensively considered: where the variable comes from (e.g., which data source), where it is processed in the middle (e.g., at various plugins), and where it is finally sent (e.g., to the decision engine or model). The entire process of deploying risk variables will also be considered, including variable registration, variable development, and variable state reversal after development, supporting bypass and main path functions, and diverse variable processing (e.g., data source variables, system variables, and big data variables).
[0039] Example 1
[0040] Based on this, please refer to Figure 1 This embodiment provides a data management system, which includes:
[0041] The single data source ledger module A10 is used to determine the data source information for making risk variable decisions and store the data source information in a preset single data source ledger.
[0042] Service ledger module A20 is used to obtain script information, policy information and service information of abnormal accounts in the target data source corresponding to the data source information, and assign script identifier to the script information, policy identifier to the policy information and service identifier to the service information, and store the first mapping relationship between the script identifier, policy identifier and service identifier in the preset service ledger.
[0043] The variable ledger module A30 is used to determine a specific variable strategy based on the strategy information, and to determine a second mapping relationship between the script identifier and the specific variable strategy based on the first mapping relationship, and to store the second mapping relationship in a preset variable ledger;
[0044] The variable relationship engine ledger module A40 is used to determine the full-process mapping relationship between the script identifier and the specific variable strategy, and to store the full-process mapping relationship in the preset variable relationship engine ledger.
[0045] In this embodiment, the data management system can run on a terminal, and the terminal's processor can be equipped with a single data source ledger module A10, a service ledger module A20, a variable ledger module A30, and a variable relationship engine ledger module A40. A controller connected to the processor controls the single data source ledger module A10 to maintain and manage the single data source ledger, the service ledger module A20 to maintain and manage the service ledger, the variable ledger module A30 to maintain and manage the variable ledger, and the variable relationship engine ledger module A40 to maintain and manage the variable relationship engine ledger. Optionally, the single data source ledger, service ledger, variable ledger, and variable relationship engine ledger can be stored in a memory. Optionally, the single data source ledger, service ledger, variable ledger, and variable relationship engine ledger can be tables, numerical values, or images, etc. In this embodiment, only tables are used as an example.
[0046] Optionally, such as Figure 2As shown, the data management system can include an access layer, a business layer, and a service layer. The access layer connects to external terminals and servers. The business layer handles rule configuration, rule execution, and early warning services. The service layer can include a variable center to store various variables, and can also include a single data source ledger module A10, a service ledger module A20, a variable ledger module A30, and a variable relationship engine ledger module A40, which manage the single data source ledger, service ledger, variable ledger, and variable relationship engine ledger respectively. Optionally, the single data source ledger module A10, service ledger module A20, variable ledger module A30, and variable relationship engine ledger module A40 can be a sensor, a functional module, or a chip; no restrictions are placed here.
[0047] Optionally, when making risk variable decisions at the terminal, it is necessary to retrieve data from an external source. At this point, the data source information, such as the data source name and type, can be determined. The system then checks whether the single data source ledger stores matching data source information corresponding to the retrieved data source. If so, the matching data source information in the single data source ledger can be updated based on the retrieved data source information, such as updating the date and time. If not, the data source information can be directly added to the single data source ledger.
[0048] Optionally, when the single data source ledger module A10 detects that the terminal is pulling at least one external data source, it records the data source information of at least one data source and stores or updates it to the single data source ledger.
[0049] Optionally, in the risk decision-making process, when it is necessary to retrieve data from an external source for risk variable calculation, the target data source can be determined through the service ledger module A20 based on the latest recorded or updated data source information of the single data source ledger module A10, and the script information, strategy information, and service information of the abnormal account can be extracted from the target data source. Optionally, the abnormal account can be an account with credit risk (such as an account with abnormal data transactions). Optionally, the script information can include the abnormal information of the abnormal account. The strategy information can include the processing strategies that may be adopted for the abnormal information. The service information can include the services that may be applied based on the processing strategies.
[0050] Optionally, script information can be assigned a script identifier, such as a script ID of TKYCRT; policy information can be assigned a policy identifier, such as a policy ID of ATKYCRT; and service information can be assigned a service tag, such as a service ID of ERM_ATKYCRT_001. Optionally, different identifiers can be assigned to the script information, policy information, and service information corresponding to each abnormal account. Optionally, since there is a certain correlation between script information, policy information, and service information, policy identifiers can be set based on script identifiers, and service identifiers can be set based on policy identifiers. For example, adding new characters to the script identifier yields the policy identifier, and adding new characters to the policy identifier yields the service identifier.
[0051] Optionally, the service ledger module A20 can establish a primary mapping relationship between script identifiers, policy identifiers, and service identifiers based on the correlation between script information, policy information, and service information. Optionally, if multiple abnormal accounts correspond to different script identifiers, policy identifiers, and service identifiers, the script identifier for each abnormal account can be determined first, and then the associated policy identifier and service identifier can be determined based on that script identifier. Optionally, the associated policy identifier and service identifier can be determined by recognizing characters. This establishes the primary mapping relationship between the script identifier, policy identifier, and service identifier for each abnormal account, and the primary mapping relationship is stored or updated in the pre-set service ledger.
[0052] Optionally, when the variable ledger module A30 detects an update in the service ledger, it determines the first mapping relationship between the updated script identifier, policy identifier, and service identifier in the service ledger, and determines the specific variable policy based on the policy information corresponding to the policy identifier. For example, if the policy information includes processing strategies that may be adopted for abnormal information, such as prediction through a withdrawal prediction model, then the specific variable policy may include all variables (i.e., risk variables) required to implement that processing strategy.
[0053] Optionally, a second mapping relationship between script identifiers and specific variable policies can be determined based on the first mapping relationship. Optionally, the second mapping relationship may include the mapping relationship between script identifiers, policy identifiers, service identifiers, and specific variable policies, and this mapping relationship is stored or updated to a pre-set variable ledger.
[0054] Optionally, the variable relationship engine ledger module A40 can monitor and record the entire process from the script of the abnormal account to the strategy and then to the specific variable strategy, and output corresponding alarm information when an anomaly is detected. Optionally, the variable relationship engine ledger module A40 can store or update the monitored process to a pre-set variable relationship engine ledger.
[0055] Optionally, for each abnormal account, the mapping relationship between its corresponding script identifier, service identifier, policy identifier, and specific variable policy can be determined, stored, or updated in the variable relationship engine ledger.
[0056] In this embodiment, a single data source ledger module, a service ledger module, a variable ledger module, and a variable relationship engine ledger module are constructed to achieve comprehensive management of these ledgers. This improves the effectiveness of risk variable decision-making throughout the entire process, from business to technology to risk management, and enhances the accuracy of risk decision results. Furthermore, the single data source ledger, service ledger, variable ledger, and variable relationship engine ledger enable full lifecycle management of risk variable flows. By transferring complex risk routing to these ledgers for registration and management, and managing multiple data sources through a single data source ledger, full monitoring and management of the risk data decision-making process is achieved, resulting in effective management of risk variables and improved accuracy of risk decision results.
[0057] Example 2
[0058] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to that in the first embodiment can be referred to the above description, and will not be repeated hereafter. In this embodiment, the single data source ledger module A10 is used to determine the data source type included in the data source information. If the data source type is a single data source, when it is determined that the first data source name included in the data source information does not match the preset single data source ledger, a single data source identifier corresponding to the data source information is assigned, and the third mapping relationship between the single data source identifier and the first data source name is stored in the single data source ledger.
[0059] In this embodiment, the single data source ledger module A10 can record the data source information of at least one external data source when it detects that the terminal is pulling at least one external data source, and determine the data source type included in the data source information. When the data source type is a single data source, it needs to check whether the single data source has been recorded in the single data source ledger. That is, when the terminal pulls one external data source, the data source information includes the data source type of a single data source; when the terminal pulls multiple external data sources, the data source information includes the data source type of a combined data source.
[0060] Optionally, the name of a single data source can be determined based on the data source information. Then, all single data source names stored in the single data source ledger at the current moment are identified. The single data source names contained in the data source information are compared sequentially with the single data source names in the single data source ledger. If a single data source name matching the one in the data source information exists, then the single data source name in the data source information matches the single data source ledger. Otherwise, it is determined that the single data source name in the data source information does not match the single data source ledger.
[0061] Optionally, when the single data source name in the data source information does not match the single data source ledger, a corresponding identifier can be assigned to the data source information according to a preset identifier rule to obtain a single data source identifier. Optionally, the single data source identifier corresponding to each data source is different. Optionally, the single data source identifier corresponding to the data source can be determined based on the single data source name.
[0062] Optionally, the mapping relationship between the single data source identifier and the first data source name (i.e., the third mapping relationship) can be stored in the single data source ledger.
[0063] In this embodiment, the data source type is determined based on the single data source ledger. When it is determined to be a single data source and does not match the single data source ledger, a single data source identifier corresponding to the single data source is assigned. The third mapping relationship between the first data source name and the single data source identifier of the single data source is stored in the single data source ledger, thereby realizing the control of the data source. This enables the control of the risk variable from the source of the risk variable, thereby improving the effective management of the risk variable.
[0064] Furthermore, the single data source ledger module A10 is used to determine the second data source name corresponding to each single data source information contained in the data source information when the data source type is determined to be a combined data source;
[0065] Determine the single data source identifier corresponding to all the second data source names, and merge all the single data source identifiers corresponding to the second data source names to obtain a new single data source identifier.
[0066] All the second data source names are merged to obtain the target data source name. The fourth mapping relationship between the new single data source identifier and the target data source name is stored in the single data source ledger.
[0067] In this embodiment, if the single data source ledger module A10 obtains data source information and determines that the data source type included in the data source information is a combined data source, it can determine that the external data source pulled by the terminal is multiple.
[0068] Optionally, the data source information corresponding to each external data source pulled by the terminal can be used as a single data source information. Optionally, the name of each external data source pulled by the terminal can be determined based on each single data source information, and used as the second data source name. Optionally, it can be determined whether an identifier corresponding to the second data source name exists in the single data source ledger. If it does not exist, a single data source identifier corresponding to the second data source name can be assigned according to a preset identifier rule. If it exists, the single data source identifier corresponding to the second data source name can be directly obtained from the single data source ledger.
[0069] Optionally, a single data source identifier corresponding to all second data source names is determined, and these identifiers are merged to obtain a new single data source identifier. Then, all second data source names are merged to obtain the target data source name. For example, if there are two second data source names, data source 1 and data source 2, and the single data source identifier for data source 1 is identifier 1, and the single data source identifier for data source 2 is identifier 2, then after merging, the new single data source identifier is identifier 1+2, and the target data source name is data source 1+2. Optionally, the merging process can be a simple addition of the single data source identifier or the data source name, or it can be a simple addition followed by some transformation, such as performing other addition or subtraction operations, or adding a new identifier.
[0070] Optionally, a new mapping relationship between a single data source identifier and a target data source name can be constructed and stored as a fourth mapping relationship in the single data source ledger.
[0071] For example, a single data source ledger can be as shown in Table 1 below, but is not limited to the format of Table 1.
[0072] Single data source identifier Single data source name V2_CRIS_PBC_ENT_G2 People's Bank of China Enterprise Second Generation V2_TAX Tax Silver
[0073] Table 1
[0074] In this embodiment, when the data source type is determined to be a combined data source, the single data source ledger module merges the second data source names corresponding to each single data source information contained in the data source information to obtain the target data source name. Then, it merges the corresponding single data source identifiers to obtain a new single data source identifier. Finally, the fourth mapping relationship between the new single data source identifier and the target data source name is stored in the single data source ledger. This enables control over risk variables from their source, i.e., the data source, thereby improving the effective management of risk variables.
[0075] Furthermore, the single data source ledger module A10 is used to traverse each second data source name and detect whether there is a matching data source name in the single data source ledger that matches the traversed second data source name;
[0076] If a matching data source name exists, the single data source identifier corresponding to the matching data source name in the single data source ledger will be used as the single data source identifier corresponding to the second data source name to be traversed.
[0077] If no matching data source name is found, a single data source identifier is assigned to the second data source name being iterated over.
[0078] In this embodiment, if the terminal retrieves multiple data sources and the second data source name corresponding to each data source has been determined, the second data source names can be traversed, and each traversed second data source name can be compared with all single data source names recorded in the single data source ledger. If a single data source name matching the traversed second data source name exists in the single data source ledger, it is used as the single data source identifier corresponding to the traversed second data source name. However, if no single data source name matching the traversed second data source name exists in the single data source ledger, the data source corresponding to the traversed second data source name can be assigned a corresponding single data source identifier according to a preset identifier rule. After determining the single data source identifiers and second data source names corresponding to all data sources, a merging process can be performed to obtain a new single data source identifier and a target data source name, and these two can be stored in the single data source ledger in a mapping relationship.
[0079] In this embodiment, the single data source ledger module iterates through each second data source name. If a matching data source name exists in the single data source ledger that matches the iterated second data source name, its corresponding single data source identifier is used as the single data source identifier for the iterated second data source name. If no matching data source name exists, the corresponding single data source identifier is directly assigned. This ensures the validity of the single data source identifier corresponding to the determined data source, facilitates the storage of relevant information of the data source in the single data source ledger, and enables control over the data source.
[0080] Furthermore, the service ledger module A20 is used to determine the script information corresponding to the abnormal account in the data source information, determine the abnormal type based on the script information, and determine the service information and policy information to be applied for the abnormal type. It assigns a script identifier to the script information, a policy identifier to the policy information, and a service identifier to the service information. It stores the first mapping relationship between the script identifier, policy identifier, and service identifier in a preset service ledger. The service information includes at least one of the following: service name, whether it is a main path, service type, service release status, service version number, service dependencies for rule-based services, service dependencies for variable-based services, whether it is allowed to calculate variables when the service is not called by the engine, service registration personnel, and service registration department.
[0081] In this embodiment, the service ledger module A20 determines the target data source based on the latest recorded or updated data source information of the single data source ledger module A10, and extracts the script information, policy information, and service information of the abnormal account from the target data source. Optionally, the exception type can be determined based on the script information, and the policy information and service information to be applied can be determined based on the exception type. Then, the script information, policy information, and service information are assigned corresponding identifiers in sequence to obtain the script identifier, policy identifier, and service identifier. The specific generation of the script identifier, policy identifier, and service identifier can be referred to the above embodiment, and will not be elaborated here.
[0082] Optionally, a first mapping relationship can be determined between the script identifier, the policy identifier, and the service identifier. If it is determined that the first mapping relationship does not exist in the service ledger, the first mapping relationship can be stored and updated in the service ledger.
[0083] Optionally, the service ledger can be referenced as shown in Table 2 below. The bytes in Table 2 can be updated and adjusted.
[0084]
[0085] Table 2
[0086] In this embodiment, the first mapping relationship corresponding to the script identifier, policy identifier and service identifier is stored in the service ledger through the service ledger module, and then the corresponding service information is managed through the service ledger, which facilitates the effective management of risk variables determined based on the service information in the future.
[0087] Furthermore, the variable ledger module A30 is used to determine the variable data in the script information based on the strategy information, determine the specific variable strategy based on the data characteristics in the variable data, determine the second mapping relationship between the script identifier and the specific variable strategy based on the first mapping relationship, and store the second mapping relationship in a preset variable ledger. The specific variable strategy includes variable identifier, variable name, variable logic, variable default value, variable data type, variable release status, variable registration personnel, and variable registration department.
[0088] In this embodiment, the variable ledger module A30 can determine the specific variable strategy to be adopted for abnormal accounts based on the mapping relationship between script identifiers, policy identifiers, and service identifiers recorded in the service ledger. Optionally, variable data corresponding to abnormal accounts in the data source can be obtained through script information, and the data characteristics of the variable data can be identified, such as variable data type and traversal publication status. Based on the data characteristics, the specific variable strategy to be adopted can be determined, and then a second mapping relationship between script identifiers and specific variable strategies can be constructed. Optionally, the second mapping relationship can be stored in the variable ledger.
[0089] Optionally, the components of the variable ledger may refer to Table 3 below, but are not limited to Table 3.
[0090] The bytes in the variable ledger can be adjusted accordingly.
[0091]
[0092] Table 3
[0093] In this embodiment, the second mapping relationship between script identifiers and specific variable strategies is stored in the variable ledger through the variable ledger module, thereby achieving effective control over various risk variables.
[0094] Furthermore, the variable relationship engine ledger module A40 is used to determine the fifth mapping relationship between script identifier, service identifier, strategy identifier, variable identifier and rule-type strategy identifier, and to use the fifth mapping relationship as the whole process mapping relationship, and to store the whole process mapping relationship in the preset variable relationship engine ledger.
[0095] In this embodiment, the variable relationship engine ledger module A40 can monitor and record the entire process of risk decision-making, and issue alarms when obvious anomalies are detected. Optionally, the mapping relationship between script identifiers, service identifiers, policy identifiers, variable identifiers, and rule-based policy identifiers can be determined and used as the fifth mapping relationship, i.e., the entire process mapping relationship, and then stored in the variable relationship engine ledger. The variable relationship engine ledger is as follows:
[0096] As shown in Table 4.
[0097]
[0098] Table 4
[0099] Optionally, in this embodiment, the single data source ledger, service ledger, variable ledger, and variable engine relationship ledger are interconnected and interdependent in storage and updates. This improves the effectiveness of risk variable decision-making throughout the entire process from business to technology to risk management, and enhances the accuracy of risk decision results.
[0100] Example 3
[0101] This application also provides a data management method, applicable to the data management system in any of the above embodiments. Please refer to [link / reference needed]. Figure 3 The data management method includes:
[0102] Step S10: Determine the data source information for making risk variable decisions and store the data source information in a preset single data source ledger.
[0103] Step S20: Obtain the script information, policy information and service information of the abnormal account in the target data source corresponding to the data source information, and assign a script identifier to the script information, a policy identifier to the policy information and a service identifier to the service information, and store the first mapping relationship between the script identifier, policy identifier and service identifier in the preset service ledger.
[0104] Step S30: Determine a specific variable strategy based on the strategy information, and determine a second mapping relationship between the script identifier and the specific variable strategy based on the first mapping relationship, and store the second mapping relationship in a preset variable ledger;
[0105] Step S30: Determine the full-process mapping relationship between the script identifier and the specific variable strategy, and store the full-process mapping relationship in the preset variable relationship engine ledger.
[0106] The data management method provided in this application adopts the data management system of any one of the embodiments in Example 1 to Example 2 above, which can effectively manage risk variables and thus improve the accuracy of risk decision-making results. Compared with the prior art, the beneficial effects of the data management method provided in this application are the same as those of the data management system provided in the above embodiments, and other technical features in the data management method are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.
[0107] Example 4
[0108] This application provides an electronic device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, which are executed by the at least one processor to enable the at least one processor to perform the data management method in the first embodiment described above.
[0109] The following is for reference. Figure 4 It shows a schematic diagram of the structure of an electronic device suitable for implementing the embodiments of the present disclosure. Figure 4 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.
[0110] like Figure 4 As shown, an electronic device may include a processing unit (such as a central processing unit, graphics processing unit, etc.) that can perform various appropriate actions and processes based on a program stored in read-only memory (ROM) or a program loaded from a storage device into random access memory (RAM). The RAM also stores various programs and data required for the operation of the electronic device. The processing unit, ROM, and RAM are interconnected via a bus. Input / output (I / O) interfaces are also connected to the bus.
[0111] Typically, the following systems can be connected to the I / O interface: input devices including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices including, for example, magnetic tapes, hard disks, etc.; and communication devices. Communication devices allow electronic devices to communicate wirelessly or wiredly with other devices to exchange data. Although electronic devices with various systems are shown in the figures, it should be understood that it is not required to implement or possess all the systems shown. More or fewer systems may be implemented alternatively.
[0112] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from a storage device, or installed from a ROM. When the computer program is executed by a processing device, it performs the functions defined above in the methods of embodiments of this disclosure.
[0113] The electronic device provided in this application, employing the data management method described in the above embodiments, can effectively manage risk variables, thereby improving the accuracy of risk decision-making results. Compared with the prior art, the beneficial effects of the electronic device provided in this application are the same as those of the data management method described in the above embodiments, and other technical features of the electronic device are the same as those disclosed in the previous embodiment method, and will not be repeated here.
[0114] It should be understood that various parts of this disclosure can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics may be combined in any suitable manner in one or more embodiments or examples.
[0115] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
[0116] Example 5
[0117] This application provides a computer-readable storage medium having computer-readable program instructions stored thereon, which are used to execute the data management method described above.
[0118] The computer-readable storage medium provided in this application embodiment may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination thereof.
[0119] The aforementioned computer-readable storage medium may be included in an electronic device or may exist independently without being assembled into an electronic device.
[0120] The aforementioned computer-readable storage medium carries one or more programs, which, when executed by an electronic device, enable the electronic device to perform the steps in the above embodiments.
[0121] Computer program code for performing the operations of this disclosure can be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, and C++, and conventional procedural programming languages such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0122] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.
[0123] The modules described in the embodiments of this disclosure can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.
[0124] The computer-readable storage medium provided in this application stores computer-readable program instructions for executing the above-described data management method, which enables effective management of risk variables and thereby improves the accuracy of risk decision-making results. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as the beneficial effects of the data management method provided in Embodiment 1 or Embodiment 2, and will not be repeated here.
[0125] Example 6
[0126] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the data management method described above.
[0127] The computer program product provided in this application can effectively manage risk variables, thereby improving the accuracy of risk decision-making results. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as the beneficial effects of the data management method provided in any of the above embodiments, and will not be repeated here.
[0128] 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 scope of this application.
Claims
1. A data management system, characterized in that, The data management system includes: A single data source ledger module is used to determine the data source information for making risk variable decisions and store the data source information in a preset single data source ledger; wherein, the single data source ledger module is also used to determine the data source type included in the data source information; if the data source type is a single data source, then when it is determined that the first data source name included in the data source information does not match the preset single data source ledger, a single data source identifier corresponding to the data source information is assigned, and a third mapping relationship between the single data source identifier and the first data source name is stored in the single data source ledger; The service ledger module is used to obtain the script information, policy information and service information of abnormal accounts in the target data source corresponding to the data source information, and assign a script identifier to the script information, a policy identifier to the policy information and a service identifier to the service information, and store the first mapping relationship between the script identifier, policy identifier and service identifier in the preset service ledger. The variable ledger module is used to determine specific variable strategies based on the strategy information, and to determine a second mapping relationship between the script identifier and the specific variable strategy based on the first mapping relationship, and to store the second mapping relationship in a preset variable ledger; wherein, the variable ledger module is used to determine variable data in the script information based on the strategy information, and to determine specific variable strategies based on the data characteristics in the variable data, and to determine a second mapping relationship between the script identifier and the specific variable strategy based on the first mapping relationship, and to store the second mapping relationship in a preset variable ledger, wherein the specific variable strategy includes variable identifier, variable name, variable logic, variable default value, variable data type, variable release status, variable registration personnel, and variable registration department; The variable relationship engine ledger module is used to determine the full-process mapping relationship between the script identifier and the specific variable strategy, and to store the full-process mapping relationship in a preset variable relationship engine ledger.
2. The data management system as described in claim 1, characterized in that, The single data source ledger module is used to determine the second data source name corresponding to each single data source information contained in the data source information when the data source type is determined to be a combined data source; Determine the single data source identifier corresponding to all the second data source names, and merge all the single data source identifiers corresponding to the second data source names to obtain a new single data source identifier. All the second data source names are merged to obtain the target data source name. The fourth mapping relationship between the new single data source identifier and the target data source name is stored in the single data source ledger.
3. The data management system as described in claim 2, characterized in that, The single data source ledger module is used to traverse each second data source name and detect whether there is a matching data source name in the single data source ledger that matches the traversed second data source name. If a matching data source name exists, the single data source identifier corresponding to the matching data source name in the single data source ledger will be used as the single data source identifier corresponding to the second data source name to be traversed. If no matching data source name is found, a single data source identifier is assigned to the second data source name being iterated over.
4. The data management system as described in claim 1, characterized in that, The service ledger module is used to determine the script information corresponding to the abnormal account in the data source information, determine the abnormal type based on the script information, and determine the service information and policy information to be applied for the abnormal type. The module assigns a script identifier to the script information, a policy identifier to the policy information, and a service identifier to the service information. The module stores the first mapping relationship between the script identifier, policy identifier, and service identifier in a preset service ledger. The service information includes at least one of the following: service name, whether it is a main path, service type, service release status, service version number, service dependent on rule-type services, service dependent on variable-type services, whether it is allowed to calculate variables when the service is not called by the engine, service registration personnel, and service registration department.
5. The data management system as described in claim 1, characterized in that, The variable relationship engine ledger module is used to determine the fifth mapping relationship between script identifier, service identifier, strategy identifier, variable identifier and rule-type strategy identifier, and to use the fifth mapping relationship as the full-process mapping relationship, and to store the full-process mapping relationship in the preset variable relationship engine ledger.
6. A data management method, characterized in that, The data management method is applied to the data management system as described in claim 1, and includes the following steps: Determine the data source information for making risk variable decisions and store the data source information in a preset single data source ledger; Obtain the script information, policy information, and service information of the abnormal account in the target data source corresponding to the data source information, and assign a script identifier to the script information, a policy identifier to the policy information, and a service identifier to the service information. Store the first mapping relationship between the script identifier, policy identifier, and service identifier in a preset service ledger. A specific variable strategy is determined based on the strategy information, and a second mapping relationship between the script identifier and the specific variable strategy is determined based on the first mapping relationship. The second mapping relationship is then stored in a preset variable ledger. Determine the full-process mapping relationship between the script identifier and the specific variable strategy, and store the full-process mapping relationship in a preset variable relationship engine ledger.
7. An electronic device, characterized in that, The electronic device includes: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the steps of the data management method of claim 6.
8. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and the computer-readable storage medium stores a program that implements the data management method. The program that implements the data management method is executed by a processor to implement the steps of the data management method as described in claim 6.