A risk data storage and acquisition method, device, equipment and medium

Abstract

The application relates to the technical field of data processing, in particular to a risk data storage and acquisition method and device, equipment and a medium. Identity information of a to-be-stored customer and corresponding risk data are received, a preset first encoding mode is used to obtain a first code corresponding to the identity information of the to-be-stored customer, each sub-risk data in the risk data is obtained, a preset second encoding mode is used to determine a sub-code corresponding to each sub-risk data, the sub-codes corresponding to each sub-risk data are sorted according to a preset sorting rule to generate a second code, and the first code and the second code are stored correspondingly. In the embodiment of the application, each server stores risk data by using the same storage method, the consistency of the data format is ensured, the server does not need to convert the data format of the risk data when acquiring the risk data from other servers, data loss in the data conversion process is avoided, and the efficiency of acquiring the risk data is improved.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a method, apparatus, device and medium for storing and retrieving risky data. Background Technology

[0002] With the development of economy and technology, the types and numbers of financial institutions are increasing. Servers of multiple financial institutions, if geographically adjacent, will be formed into regional alliances, each containing servers from at least two financial institutions. In practical applications, each financial institution's server needs to conduct risk control based on user risk data. This risk control requires not only its own stored risk data but also data obtained from other servers of other financial institutions. These other servers may be in the same regional alliance as the current server, or they may not be in the same regional alliance.

[0003] In existing technologies, servers within the same regional consortium use the same data format to store risk data. However, servers in different regional consortia store risk data in different formats. For example, in regional consortium A, an ID card is identified by the number 1, but in regional consortium B, an ID card is identified by the number A. Therefore, when a server retrieves risk data from other servers in other regional consortia, it needs to convert the data format of the risk data stored on those servers. To enable different servers to share risk data, existing technologies add a relay server between regional consortia to perform data format conversion. Specifically, other servers send the risk data to be transmitted to the relay server, which converts the data format and then sends the converted risk data to the server.

[0004] However, using a relay server for data conversion may result in data loss and reduce data transmission efficiency. Summary of the Invention

[0005] This application provides a method, apparatus, device, and medium for storing and retrieving risky data, in order to solve the problems in the prior art where different data formats stored on servers may lead to data loss and low data transmission efficiency during the data conversion process using a relay server.

[0006] This application provides a risk data storage method, the method comprising:

[0007] Receive the identity information of the customer to be stored and the corresponding risk data, and obtain the first code corresponding to the identity information using a preset first encoding method;

[0008] Each sub-risk data in the risk data is obtained, and a sub-code corresponding to each sub-risk data is determined using a preset second encoding method; the sub-codes corresponding to each sub-risk data are sorted according to a preset sorting rule to generate a second code;

[0009] Save the first code and the second code accordingly.

[0010] Furthermore, the step of obtaining the first code corresponding to the identity information of the customer to be stored using a preset first encoding method includes:

[0011] Determine the target identity type carried in the identity information, and determine the target first identifier corresponding to the target identity type based on the pre-saved correspondence between the identity type and the first identifier;

[0012] The identity ID carried in the identity information is determined, and the first code corresponding to the target first identifier and the identity ID is determined according to the preset first order and the first encoding method.

[0013] Further, determining the first code corresponding to the target first identifier and the identity ID according to the preset first order and the first encoding method includes:

[0014] The target first identifier and the identity ID are sorted according to a preset first order;

[0015] Determine the hash value corresponding to the sorting result, and use the hash value as the first encoding.

[0016] Furthermore, after using the hash value as the first encoding, the method further includes:

[0017] The first code is sent to the data center server of the regional alliance where the server is located.

[0018] Furthermore, the step of determining the sub-code corresponding to each sub-risk data using a preset second encoding method includes:

[0019] For each sub-risk data, obtain the target sub-risk type and target risk level in the sub-risk data; determine the target second identifier corresponding to the target sub-risk type according to the pre-saved correspondence between each sub-risk type and the second identifier; determine the target third identifier corresponding to the target risk level according to the pre-saved correspondence between the risk level of each sub-risk type and the third identifier; sort and combine the target second identifier and the target third identifier according to a preset second order, and determine the identifier obtained by sorting and combining as the sub-code corresponding to the sub-risk data.

[0020] Furthermore, the method also includes:

[0021] Obtain the risk occurrence time, risk event details, and risk data validity period carried in the risk data;

[0022] The time of occurrence of the risk, the details of the risk event, and the validity period of the risk data are saved in correspondence with the first code and the second code.

[0023] This application embodiment also provides a risk data acquisition method, the method comprising:

[0024] The third code corresponding to the identity information of the customer to be analyzed is determined by using a preset first coding method;

[0025] Identify the target server that stores the risk data corresponding to the third code, send a first risk data acquisition request carrying the third code to the target server, and receive the fourth code corresponding to the risk data sent by the target server;

[0026] The fourth code is parsed according to the preset second encoding method to obtain the risk data of the customer to be analyzed.

[0027] Furthermore, the determination of the target server for storing the risk data corresponding to the third code includes:

[0028] Send a target server determination request carrying the third code to the data center server of each pre-saved regional alliance;

[0029] Receive response information from each of the data center servers, which carries the identification information of the target server.

[0030] Furthermore, the step of determining the third code corresponding to the identity information of the customer to be analyzed using a preset first encoding method includes:

[0031] Determine the target identity type carried in the identity information, and determine the target fourth identifier corresponding to the target identity type based on the pre-saved correspondence between the identity type and the fourth identifier;

[0032] The identity ID carried in the target identity information is determined, and the third code corresponding to the target fourth identifier and the identity ID is determined according to the preset first order and the first encoding method.

[0033] Further, determining the third encoding corresponding to the target fourth identifier and the identity ID according to the preset first order and the first encoding method includes:

[0034] The target fourth identifier and the identity ID are sorted according to a preset first order;

[0035] Determine the hash value corresponding to the sorting result, and use the hash value as the third encoding.

[0036] Furthermore, the step of parsing the fourth code according to the preset second encoding method to obtain the risk data of the customer to be analyzed includes:

[0037] Each sub-encoder in the fourth encoding is determined using a preset second encoding method;

[0038] For each sub-code, obtain the target fifth identifier used to identify the risk level in that sub-code, and determine the target risk level corresponding to the target fifth identifier based on the pre-saved correspondence between the risk level of each sub-risk type and the fifth identifier.

[0039] Furthermore, the method also includes:

[0040] If a request to obtain second risk data carrying a fifth code is received from another server, it is determined whether a target first code that matches the fifth code exists in the first code stored locally.

[0041] If it exists, then obtain the target second code of the risk data corresponding to the saved target first code, and send the target second code to the other servers.

[0042] This application embodiment also provides a risk data storage device, the device comprising:

[0043] The first transceiver module is used to receive the identity information of customers to be stored and the corresponding risk data;

[0044] The first processing module is used to obtain the first code corresponding to the identity information using a preset first encoding method; obtain each sub-risk data in the risk data, and determine the sub-code corresponding to each sub-risk data using a preset second encoding method; and sort the sub-codes corresponding to each sub-risk data according to a preset sorting rule to generate a second code.

[0045] A storage module is used to save the first code and the second code accordingly.

[0046] Further, the first processing module is specifically used to determine the target identity type carried in the identity information, determine the target first identifier corresponding to the target identity type according to the pre-saved correspondence between identity types and first identifiers, determine the identity ID carried in the identity information, and determine the first code corresponding to the target first identifier and the identity ID according to a preset first order and the first encoding method.

[0047] Furthermore, the first processing module is specifically used to sort the target first identifier and the identity ID according to a preset first order; determine the hash value corresponding to the sorting result, and use the hash value as the first code.

[0048] Furthermore, the first processing module is also used to send the first code to the data center server of the regional alliance where the server is located.

[0049] Further, the first processing module is specifically used to: obtain the target sub-risk type and target risk level in each sub-risk data; determine the target second identifier corresponding to the target sub-risk type according to the pre-saved correspondence between each sub-risk type and the second identifier; determine the target third identifier corresponding to the target risk level according to the pre-saved correspondence between the risk level of each sub-risk type and the third identifier; and sort and combine the target second identifier and the target third identifier according to a preset second order, and determine the identifier obtained by sorting and combining as the sub-code corresponding to the sub-risk data.

[0050] Furthermore, the first processing module is also used to obtain the risk occurrence time, risk event details, and risk data validity period carried in the risk data;

[0051] The storage module is also used to save the time of occurrence of the risk, the details of the risk event, and the validity period of the risk data in correspondence with the first code and the second code.

[0052] This application embodiment also provides a risk data acquisition device, the device comprising:

[0053] The second processing module is used to determine the third code corresponding to the identity information of the customer to be analyzed by using a preset first coding method.

[0054] The second transceiver module is used to determine the target server that stores the risk data corresponding to the third code, send a first risk data acquisition request carrying the third code to the target server, and receive the fourth code corresponding to the risk data sent by the target server.

[0055] The second processing module is further configured to parse the fourth code according to a preset second encoding method to obtain the risk data of the customer to be analyzed.

[0056] Furthermore, the second transceiver module is specifically used to send a target server determination request carrying the third code to the data center server of each pre-stored regional alliance; and to receive response information carrying the identification information of the target server sent by each of the data center servers.

[0057] Furthermore, the second processing module is specifically used to determine the target identity type carried in the identity information, and to determine the target fourth identifier corresponding to the target identity type according to the pre-saved correspondence between the identity type and the fourth identifier; to determine the identity ID carried in the target identity information, and to determine the third code corresponding to the target fourth identifier and the identity ID according to the preset first order and the first encoding method.

[0058] Furthermore, the second processing module is specifically used to sort the target fourth identifier and the identity ID according to a preset first order; determine the hash value corresponding to the sorting result, and use the hash value as the third encoding.

[0059] Furthermore, the second processing module is specifically used to determine each sub-code in the fourth code using a preset second encoding method; for each sub-code, to obtain the target fifth identifier used to identify the risk level in the sub-code; and to determine the target risk level corresponding to the target fifth identifier based on the pre-saved correspondence between the risk level of each sub-risk type and the fifth identifier.

[0060] Furthermore, the second transceiver module is also configured to, if it receives a second risk data acquisition request carrying a fifth code sent by another server, determine whether there is a target first code consistent with the fifth code in the first code stored locally; if there is, acquire the target second code of the risk data corresponding to the stored target first code, and send the target second code to the other server.

[0061] This application also provides an electronic device, which includes a processor, and the processor is configured to execute a computer program stored in a memory to implement the steps of risk data storage or risk data acquisition method as described above.

[0062] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of any of the above-described risk data storage or risk data acquisition methods.

[0063] This application also provides a computer program product, which includes computer program code. When the computer program code is run on a computer, it causes the computer to perform the steps of the risk data storage or risk data acquisition method described above.

[0064] In this embodiment, the system receives the identity information of the customer to be stored and the corresponding risk data. Using a preset first encoding method, it obtains the first code corresponding to the customer's identity information. It then obtains each sub-risk data within the risk data and uses a preset second encoding method to determine the sub-code corresponding to each sub-risk data. Following a preset sorting rule, it sorts the sub-codes corresponding to each sub-risk data to generate a second code. Finally, it saves the first code and the second code accordingly. In this embodiment, each server uses the same storage method to store the risk data, ensuring data format consistency. When a server retrieves risk data from other servers, it does not need to convert the data format of the risk data, avoiding data loss during data conversion and improving the efficiency of risk data retrieval. Attached Figure Description

[0065] To more clearly illustrate the technical solutions of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0066] Figure 1 A schematic diagram of a risk data storage process provided in an embodiment of this application;

[0067] Figure 2 This is a schematic diagram illustrating a risk data acquisition process provided in an embodiment of this application;

[0068] Figure 3 A schematic diagram illustrating the risk data provided in the embodiments of this application;

[0069] Figure 4 This is a schematic diagram of a risk data storage device provided in an embodiment of this application;

[0070] Figure 5 This is a schematic diagram of a risk data acquisition device provided in an embodiment of this application;

[0071] Figure 6 This is a schematic diagram of an electronic device structure provided in an embodiment of this application. Detailed Implementation

[0072] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only 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.

[0073] To avoid data loss during data format conversion and improve the efficiency of risk data acquisition, this application provides a risk data storage and acquisition method, apparatus, device, and medium.

[0074] In this embodiment, the system receives the identity information of the customer to be stored and the corresponding risk data, obtains the first code corresponding to the identity information of the customer to be stored using a preset first encoding method, obtains each sub-risk data in the risk data, determines the sub-code corresponding to each sub-risk data using a preset second encoding method, sorts the sub-codes corresponding to each sub-risk data according to a preset sorting rule, generates a second code, and saves the first code and the second code accordingly.

[0075] The acquisition, storage, use, and processing of data in all technical solutions of this application comply with the relevant provisions of national laws and regulations.

[0076] Example 1:

[0077] Figure 1 This application provides a schematic diagram of a risk data storage process, which includes:

[0078] S101: Receive the identity information of the customer to be stored and the corresponding risk data, and obtain the first code corresponding to the identity information using a preset first encoding method.

[0079] This application provides a risk data storage method applied to a server.

[0080] In existing technologies, servers in different regional alliances may use different data formats to store risk data. This means that when any server retrieves risk data from servers in other regional alliances, it needs to first convert the data format of the acquired risk data through a relay server. The data format of the acquired risk data needs to be converted to the target data format used by the server storing the risk data. This data format conversion reduces the efficiency of risk data retrieval and may lead to data loss during the conversion process, reducing the accuracy of the acquired risk data. Therefore, this application provides a risk data storage method that allows servers in different regional alliances to store risk data using the same data format. Subsequently, when any server retrieves risk data from other servers, it does not need to perform data format conversion, improving the efficiency and accuracy of risk data retrieval.

[0081] Specifically, in this embodiment of the application, each server can store one risk data for each customer to be stored, or it can store multiple risk data. There is no limitation here. This embodiment of the application takes the example of storing one risk data for one customer to be stored, but one risk data may contain multiple sub-risk data.

[0082] In this embodiment, the server receives the identity information of the customer to be stored and the corresponding risk data, and saves the identity information and risk data. Specifically, when storing the risk data corresponding to the customer to be stored, a preset first encoding method is first used to determine the first code corresponding to the identity information of the customer to be stored, and then the risk data is saved according to the first code.

[0083] Specifically, in this embodiment, when the server determines the identity information of a customer to be stored, it uses a preset first encoding method to encode the identity information and determine the first code corresponding to the identity information of the customer to be stored. Since different customers to be stored correspond to different identity types, in this embodiment, the identity type corresponding to each piece of identity information can be identified through the first encoding method.

[0084] The types of customers to be stored include at least individuals, enterprises, or companies. Specifically, in this embodiment, if the customer to be stored is an individual, the target identity type carried in the customer's identity information is an ID card, and the identity ID is the ID card number; if the customer to be stored is an enterprise or company, the target identity type carried in the customer's identity information can be a business license, and the identity ID can be a tax number, etc. For example, after the server encodes the identity information of the customer to be stored using the first encoding method, the first encoding corresponding to different identity types contains different identifiers.

[0085] S102: Obtain each sub-risk data in the risk data, determine the sub-code corresponding to each sub-risk data using a preset second encoding method; sort the sub-codes corresponding to each sub-risk data according to a preset sorting rule to generate a second code.

[0086] In this embodiment, when saving risk data corresponding to a customer to be stored, the server obtains each sub-risk data in the received risk data, encodes it according to the encoding method corresponding to each sub-risk data to obtain a sub-code corresponding to each sub-risk data, and then combines each sub-code to determine the second code corresponding to the risk data. In this embodiment, the risk data can be sent to the server by other servers, or it can be obtained by the server through analysis of application data of the customer to be stored sent by the application client.

[0087] In this embodiment, for each sub-risk data, the server uses a preset second encoding method to determine the sub-code corresponding to each sub-risk data. Since different sub-risk data correspond to different sub-risk types, in this embodiment, the sub-risk type corresponding to each sub-risk data can be identified through the second encoding method. For example, after encoding through the second encoding method, the sub-codes corresponding to sub-risk data of different sub-risk types contain different identifiers, etc.

[0088] After determining the sub-code corresponding to each sub-risk data, the sub-codes corresponding to each sub-risk data are sorted according to a preset order. The combined code formed by each sorted sub-code is then determined as the second code corresponding to the risk data. The preset order is the order of sub-risk types.

[0089] Specifically, the server stores a sorted order of sub-risk types, which includes all sub-risk types. For each sub-risk data, the server determines the target sub-risk type corresponding to that sub-risk data and assigns its index within the sorted order to the corresponding index of the sub-risk data. The server sorts each sub-risk data according to its index. For sub-risk types that do not have a corresponding sub-risk data, the server fills in the missing information using a preset identifier, ultimately obtaining the second code.

[0090] S103: Save the first code and the second code accordingly.

[0091] In this embodiment of the application, after determining the first code corresponding to the identity information of the customer to be stored and the second code corresponding to the risk data of the customer to be stored, the server saves the first code and the second code accordingly, thereby realizing the storage of the risk data of the customer to be stored.

[0092] In this embodiment of the application, each server uses the same storage method to store risk data, which ensures the consistency of data format. When a server obtains risk data from other servers, it does not need to convert the data format of the risk data, thus avoiding data loss during the data format conversion process and improving the efficiency of obtaining risk data.

[0093] Example 2:

[0094] To ensure that each server encodes the identity information of the customer to be stored in the same way, based on the above embodiments, in this embodiment, obtaining the first code corresponding to the identity information of the customer to be stored using a preset first encoding method includes:

[0095] Determine the target identity type carried in the identity information, and determine the target first identifier corresponding to the target identity type based on the pre-saved correspondence between the identity type and the first identifier;

[0096] The identity ID carried in the identity information is determined, and the first code corresponding to the target first identifier and the identity ID is determined according to the preset first order and the first encoding method.

[0097] To enable the server to store risk data of customers with different identity types, in this embodiment, the server stores a correspondence between identity types and first identifiers to identify each identity type. Specifically, when determining the first code corresponding to the identity information of a customer to be stored, the server first determines the target identity type carried in the identity information of the customer to be stored, and then determines the target first identifier corresponding to the target identity type according to the pre-stored correspondence between identity types and first identifiers.

[0098] For example, if the target identity type carried in the identity information of the customer to be stored is an ID card, the target first identifier corresponding to the ID card is determined to be 1010 based on the pre-saved correspondence between identity types and first identifiers.

[0099] After determining the target first identifier, in order to determine the first code corresponding to the identity information of the customer to be stored, in this embodiment of the application, the server can also determine the code corresponding to the identity ID based on the identity ID of the customer to be stored. Specifically, the server determines the identity ID carried in the identity information of the customer to be stored, encodes the identity information of the customer to be stored based on the target first identifier and the identity ID, and determines the first code corresponding to the identity information of the customer to be stored.

[0100] Specifically, in this embodiment, the server sorts the target first identifier and the identity ID according to a preset first order, and encodes the sorting result according to a first encoding method to determine the first encoding corresponding to the customer's identity information to be stored. The first encoding method can be a preset encryption method; using this first encoding method to encrypt the sorting result improves the security of the customer's identity information to be stored.

[0101] To improve the security of the identified customer's identity information to be stored, based on the above embodiments, in this embodiment, determining the first code corresponding to the target first identifier and the identity ID according to a preset first order and the first encoding method includes:

[0102] The target first identifier and the identity ID are sorted according to a preset first order;

[0103] Determine the hash value corresponding to the sorting result, and use the hash value as the first encoding.

[0104] In this embodiment of the application, in order to determine the first code, the server can sort the target first identifier and identity ID according to a preset first order. This first order can be set by a technician and is not limited here.

[0105] To improve the security of the identified identity information, in this embodiment of the application, the server sorts the target first identifier and identity ID to obtain a sorting result, performs a hash calculation on the sorting result to determine the hash value corresponding to the sorting result, and determines the hash value as the first code corresponding to the identity information of the customer to be stored.

[0106] To facilitate other servers in finding risky data, based on the above embodiments, in this embodiment of the application, after using the hash value as the first encoding, the method further includes:

[0107] The first code is sent to the data center server of the regional alliance where the server is located.

[0108] In this embodiment, to facilitate other servers in locating risk data, the server also sends the first code to the data center server of the regional consortium where it resides. This data center server stores the first code corresponding to each customer with risk data, locally stored by each server within its regional consortium. Each server can determine the server storing the risk data of the customer to be analyzed based on each first code stored in the data center server, and thus obtain the risk data from that server.

[0109] Example 3:

[0110] In order to encode each sub-risk data, based on the above embodiments, in this embodiment of the application, the step of determining the sub-code corresponding to each sub-risk data using a preset second encoding method includes:

[0111] For each sub-risk data, obtain the target sub-risk type and target risk level in the sub-risk data; determine the target second identifier corresponding to the target sub-risk type according to the pre-saved correspondence between each sub-risk type and the second identifier; determine the target third identifier corresponding to the target risk level according to the pre-saved correspondence between the risk level of each sub-risk type and the third identifier; sort and combine the target second identifier and the target third identifier according to a preset second order, and determine the identifier obtained by sorting and combining as the sub-code corresponding to the sub-risk data.

[0112] In the embodiments of this application, a risk data may contain one sub-risk data or multiple sub-risk data, and there is no limitation on this. Each sub-risk data carries a target sub-risk type and a target risk level, and different sub-risk data belonging to the same risk data correspond to different target sub-risk types.

[0113] Therefore, to ensure that the server's method of determining the sub-encoding of sub-risk data is applicable to sub-risk data of different sub-risk types, in this embodiment, the server stores a correspondence between sub-risk types and second identifiers to identify each sub-risk type. Furthermore, the server also stores a correspondence between the risk level of each sub-risk type and a third identifier to identify each risk level of sub-risk data for each sub-risk type.

[0114] Therefore, in this embodiment, for each sub-risk data, when determining the sub-code corresponding to the sub-risk data, the server obtains the target sub-risk type and target risk level from the sub-risk data, and determines the target second identifier corresponding to the target sub-risk type according to the pre-saved correspondence between sub-risk types and second identifiers. Then, according to the pre-saved correspondence between the risk level of each sub-risk type and the third identifier, the server determines the target third identifier corresponding to the target risk level.

[0115] To ensure that the sub-code corresponding to the determined sub-risk data reflects the target sub-risk type and target risk level, in this embodiment, the target second identifier and the target third identifier are sorted and combined according to a preset second order, and the resulting identifier is determined as the sub-code corresponding to the sub-risk data. Generally, to facilitate server identification of the target sub-risk type and avoid server confusion between the target second identifier corresponding to the target sub-risk type and the target third identifier corresponding to the target risk level, the preset second order can be target second identifier first, followed by target third identifier.

[0116] Example 4:

[0117] To ensure the integrity of the stored risk data, based on the above embodiments, the method in this application embodiment further includes:

[0118] Obtain the risk occurrence time, risk event details, and risk data validity period carried in the risk data;

[0119] The time of occurrence of the risk, the details of the risk event, and the validity period of the risk data are saved in correspondence with the first code and the second code.

[0120] In this embodiment of the application, the risk data also includes the time of risk occurrence, risk details, and risk validity period, enabling the server to perform risk analysis on customers more accurately.

[0121] In this embodiment of the application, when the server saves the risk data of the customer to be stored, in addition to saving the first code and the second code corresponding to the customer to be stored, the server will also save the risk occurrence time, risk event details and the validity period of the risk data together with the first code and the second code.

[0122] Furthermore, in this embodiment, in addition to the time of risk occurrence, risk details, and risk validity period, the risk data also carries other content. The content carried by the risk data varies depending on the scenario it corresponds to, and the server can store it accordingly. For example, if the risk data corresponds to a credit card business scenario, it may also carry information such as the remaining credit limit and whether the credit card application has been approved; if the risk data corresponds to a telecommunications anti-fraud business scenario, it may also carry information such as the number of bank accounts opened in the past year; if the risk data corresponds to a mortgage loan business scenario, it may also carry information such as the current value assessment of the collateral and the loan-to-value ratio.

[0123] Furthermore, in this embodiment of the application, when saving risk data, the source of the risk data is also saved accordingly. For example, if the risk data is collected by a server, the source of the risk data is determined to be local, and the identification information and acquisition time of the server are saved; if the risk data is sent by another server, the source of the risk data is determined to be another server, and the identification information and acquisition time of the other server are saved.

[0124] Example 5:

[0125] Figure 2 This application provides a schematic diagram of a risk data acquisition process, which includes:

[0126] S201: Using a preset first coding method, determine the third coding corresponding to the identity information of the customer to be analyzed.

[0127] The risk data acquisition method provided in this application embodiment is applied to a server.

[0128] In this embodiment of the application, when the server needs to evaluate a customer to be analyzed, it needs to analyze the risk data of that customer. To make the analysis results more accurate, in addition to the risk data stored locally on the server, the server also obtains the risk data of the customer to be analyzed from other target servers that store such risk data.

[0129] Specifically, in order to quickly retrieve the risk data of the customer to be analyzed, in this embodiment of the application, the server determines the third code corresponding to the identity information of the customer to be analyzed, and obtains the risk data of the customer to be analyzed from other target servers that store the risk data of the customer to be analyzed based on the third code.

[0130] In this embodiment, the server determines the identity information of the customer to be analyzed, and then encodes the identity information using a preset first encoding method to determine the third encoding corresponding to the identity information of the customer to be stored. Since different customers to be analyzed correspond to different identity types, in this embodiment, the identity type corresponding to each piece of identity information can be identified through the first encoding method. For example, after encoding through the first encoding method, the third encoding corresponding to the identity information of different identity types contains different identifiers, etc.

[0131] S202: Determine the target server that stores the risk data corresponding to the third code, send a first risk data acquisition request carrying the third code to the target server, and receive the fourth code corresponding to the risk data sent by the target server.

[0132] After identifying the third code of the customer to be analyzed, the server determines the target server that stores the risk data corresponding to the third code and sends a first risk data retrieval request carrying the third code to the target server.

[0133] Specifically, in order to avoid sending the first risk data acquisition request to a server that does not store the risk data corresponding to the third code, and to reduce the server's load pressure, in this embodiment of the application, the server will first determine the target server that stores the risk data corresponding to the third code, and then send the first risk data acquisition request carrying the third code to the target server.

[0134] In this application example, when determining the target server that stores the risk data corresponding to the third code, the server can determine it based on the data center server of each regional alliance.

[0135] After receiving a first risk data retrieval request from the target server, the target server retrieves the third code carried in the first risk data retrieval request, searches for a target first code that matches the third code in its locally stored first codes, retrieves the fourth code of the risk data stored corresponding to the target first code, and sends the fourth code to the target server. The server receives the fourth code corresponding to the risk data sent by the target server. It should be noted that in this embodiment, there can be one or more target servers, and the target server may or may not belong to the same regional alliance as the target server.

[0136] S203: Parse the fourth code according to the preset second encoding method to obtain the risk data of the customer to be analyzed.

[0137] In this embodiment of the application, after receiving the fourth encoding sent by the target server, the server can parse the fourth encoding using a preset second encoding method.

[0138] Specifically, based on the order of sub-risk types stored in the server, and according to the number of fields corresponding to each pre-saved sub-code, the sub-codes included in the fourth encoding are determined. To facilitate the determination of each sub-code, in this embodiment, the number of fields corresponding to each pre-saved sub-code is the same. Since in this embodiment, the second encoding method can identify the sub-risk type corresponding to each sub-risk data; for example, after encoding using the second encoding method, the sub-codes corresponding to sub-risk data of different sub-risk types contain different identifiers. Therefore, based on the second encoding method and the fourth encoding, the sub-risk type corresponding to each sub-code can be determined.

[0139] Furthermore, in this embodiment of the application, if multiple fourth codes are received simultaneously from multiple target servers, and each risk data corresponding to each fourth code is determined, the server can jointly display the risk data corresponding to the target servers belonging to the same regional alliance.

[0140] Figure 3 This is a schematic diagram illustrating the risk data provided in the embodiments of this application. Figure 3 As shown, the customer to be analyzed is Zhang San, and the target identity type for this customer is ID card, with the corresponding target fourth identifier being 1010; the customer's identity ID to be stored is 5**********X; this risk data contains one sub-risk data point, the sub-risk type of which is suspicious transaction, with the corresponding target sixth identifier being 1019; the target risk level for this sub-risk data is level three, with the corresponding target fifth identifier being 03. Furthermore, the risk in this sub-risk data occurred on October 23, 2021, and the risk event details state that suspicious transactions by this user were detected on October 23, 2021. The risk data is valid indefinitely.

[0141] Example 6:

[0142] To improve the efficiency of risk data retrieval, a target server storing the risk data corresponding to the third code is identified. Based on the above embodiments, in this embodiment, the identification of the target server storing the risk data corresponding to the third code includes:

[0143] Send a target server determination request carrying the third code to the data center server of each pre-saved regional alliance;

[0144] Receive response information from each of the data center servers, which carries the identification information of the target server.

[0145] In this embodiment of the application, each regional alliance includes a data center server, and each data center server stores a first code corresponding to each customer with risky data that is locally stored by each server in its regional alliance.

[0146] The server can send a target server retrieval request carrying a third code to the data center servers in each regional alliance. Upon receiving the retrieval request, any data center server checks its locally stored first codes to see if a target first code matches the third code. If so, it identifies a candidate server corresponding to that target first code, designates it as the target server containing the risk data corresponding to the third code, and sends a response message carrying the target server's identification information. Upon receiving this response message, the server determines the target server based on the identification information carried in the response message.

[0147] In this embodiment of the application, if the target center server determines that there is no target first code that is consistent with the third code in the first code stored locally, the target center server returns response information without carrying identification information to the server.

[0148] For any data center server, a timer starts when the server sends a request to the data center server. If the server does not receive a response from the data center server within a preset time period, or if the received response does not carry identification information, it is determined that there is no target server in the regional alliance where the data center server is located that stores the risk data corresponding to the third code.

[0149] Example 7:

[0150] To achieve high-speed and efficient querying of the risk data of the customer to be analyzed in the target server, based on the above embodiments, in this embodiment, the step of determining the third code corresponding to the identity information of the customer to be analyzed using a preset first encoding method includes:

[0151] Determine the target identity type carried in the identity information, and determine the target fourth identifier corresponding to the target identity type based on the pre-saved correspondence between the identity type and the fourth identifier;

[0152] The identity ID carried in the target identity information is determined, and the third encoding corresponding to the target fourth identifier and the identity ID is determined according to the preset third order and the first encoding method.

[0153] In order for the server to query the risk data of the customer to be analyzed in the target server, in this embodiment of the application, the server needs to first determine the third code corresponding to the identity information of the customer to be analyzed, and then query the risk data of the customer to be analyzed in the target server according to the third code.

[0154] Specifically, the server stores the correspondence between identity types and fourth identifiers. The server first determines the target identity type carried in the identity information of the customer to be analyzed, and then determines the target fourth identifier corresponding to the target identity type according to the pre-stored correspondence between identity types and fourth identifiers.

[0155] For example, if the target identity type carried in the identity information of the customer to be analyzed is an ID card, the target fourth identifier corresponding to the ID card is determined to be 1010 based on the pre-saved correspondence between identity types and fourth identifiers.

[0156] After determining the target fourth identifier, in order to determine the third code corresponding to the identity information of the customer to be analyzed, in this embodiment of the application, the server can also determine the code corresponding to the identity ID carried in the identity information of the customer to be analyzed. Then, the server encodes the identity information of the customer to be analyzed based on the target fourth identifier and the identity ID to determine the third code corresponding to the identity information of the customer to be analyzed.

[0157] Specifically, in this embodiment, the server sorts the target fourth identifier and the identity ID according to a preset third order, and encodes the sorting result according to a first encoding method to determine the third encoding corresponding to the identity information of the customer to be analyzed. The first encoding method can be a preset encryption method; using this first encoding method to encrypt the sorting result improves the security of the customer's identity information to be stored.

[0158] Example 8:

[0159] To enhance the security of the third encoding, based on the above embodiments, in this embodiment, determining the third encoding corresponding to the target fourth identifier and the identity ID according to a preset third order and the first encoding method includes:

[0160] The target fourth identifier and the identity ID are sorted according to a preset third order;

[0161] Determine the hash value corresponding to the sorting result, and use the hash value as the third encoding.

[0162] In this embodiment, the server sorts the target fourth identifier and the identity ID according to a preset third order. The first order can be set by a technician and is not limited here. Generally, to facilitate server identification of the identity ID and avoid server confusion between the identity ID and the target fourth identifier, the preset third order is target fourth identifier first, followed by identity ID.

[0163] To improve the security of identity information, in this embodiment of the application, the server sorts the target fourth identifier and identity ID to obtain a sorting result, performs a hash calculation on the sorting result to determine the hash value corresponding to the sorting result, and determines the hash value as the third code corresponding to the identity information of the customer to be analyzed.

[0164] Example 9:

[0165] In order to parse the fourth code and obtain the risk data corresponding to the fourth code, based on the above embodiments, in this embodiment, the step of parsing the fourth code according to a preset second coding method to obtain the risk data of the customer to be analyzed includes:

[0166] Each sub-encoder in the fourth encoding is determined using a preset second encoding method;

[0167] For each sub-code, obtain the target fifth identifier used to identify the risk level in that sub-code, and determine the target risk level corresponding to the target fifth identifier based on the pre-saved correspondence between the risk level of each sub-risk type and the fifth identifier.

[0168] In this embodiment, the fourth encoding may contain one or more sub-encodings. Each sub-encoding is obtained by arranging and combining them according to a preset second order, and the length of each sub-encoding is also known in advance. Therefore, the sub-encoding of the sub-risk data corresponding to each sub-risk type can be obtained. Each sub-encoding contains a target fifth identifier used to identify the risk level. For each sub-encoding, since it is known which sub-risk type it corresponds to, and the length of the identifier corresponding to the sub-risk type and the identifier corresponding to the sub-risk data are also known, the target fifth identifier carrying the risk level in the sub-encoding can be determined, and the sub-risk data corresponding to the sub-encoding can be parsed out based on the target fifth identifier.

[0169] Specifically, the server stores the correspondence between the risk level of each sub-risk type and the fifth identifier, which is used to identify each risk level of sub-risk data for each sub-risk type.

[0170] Based on this, in this embodiment of the application, the server determines each sub-code in the fourth encoding and determines the target fifth identifier corresponding to each sub-code. The server determines the target risk level corresponding to the target fifth identifier based on the pre-saved correspondence between the risk level of each sub-risk type and the fifth identifier.

[0171] Example 10:

[0172] To improve the speed at which the server sends risky data to other servers, based on the above embodiments, the method in this application embodiment further includes:

[0173] If a request to obtain second risk data carrying a fifth code is received from another server, it is determined whether a target first code that matches the fifth code exists in the first code stored locally.

[0174] If it exists, then obtain the target second code of the risk data corresponding to the saved target first code, and send the target second code to the other servers.

[0175] In this embodiment, the server also receives a second risk data acquisition request carrying a fifth code from another server. After receiving the second wind direction data acquisition request, the server searches for a target first code that matches the fifth code in the first code stored locally. If the server finds the target first code, it obtains the target second code corresponding to the stored target first code and sends the target second code to the other server.

[0176] Example 11:

[0177] Figure 4 This application provides a schematic diagram of a risk data storage device, which includes:

[0178] The first transceiver module 401 is used to receive the identity information of the customer to be stored and the corresponding risk data;

[0179] The first processing module 402 is used to obtain the first code corresponding to the identity information using a preset first encoding method; obtain each sub-risk data in the risk data, and determine the sub-code corresponding to each sub-risk data using a preset second encoding method; and sort the sub-codes corresponding to each sub-risk data according to a preset sorting rule to generate a second code.

[0180] Storage module 403 is used to save the first code and the second code accordingly.

[0181] In one possible implementation, the first processing module 402 is specifically used to determine the target identity type carried in the identity information, determine the target first identifier corresponding to the target identity type according to the pre-saved correspondence between identity types and first identifiers, determine the identity ID carried in the identity information, and determine the first code corresponding to the target first identifier and the identity ID according to a preset first order and the first encoding method.

[0182] In one possible implementation, the first processing module 402 is specifically used to sort the target first identifier and the identity ID according to a preset first order; determine the hash value corresponding to the sorting result, and use the hash value as the first code.

[0183] In one possible implementation, the first processing module 402 is further configured to send the first code to the data center server of the regional consortium where the server is located.

[0184] In one possible implementation, the first processing module 402 is specifically configured to: obtain the target sub-risk type and target risk level in each sub-risk data; determine the target second identifier corresponding to the target sub-risk type according to the pre-saved correspondence between each sub-risk type and the second identifier; determine the target third identifier corresponding to the target risk level according to the pre-saved correspondence between the risk level of each sub-risk type and the third identifier; and sort and combine the target second identifier and the target third identifier according to a preset second order, and determine the identifier obtained by sorting and combining as the sub-code corresponding to the sub-risk data.

[0185] In one possible implementation, the first processing module 402 is further configured to obtain the risk occurrence time, risk event details, and risk data validity period carried in the risk data;

[0186] The storage module 403 is also used to save the risk occurrence time, the risk event details, the risk data validity period and the first code and the second code in correspondence.

[0187] Example 12:

[0188] Figure 5 This application provides a schematic diagram of a risk data acquisition device, which includes:

[0189] The second processing module 501 is used to determine the third code corresponding to the identity information of the customer to be analyzed by using a preset first coding method;

[0190] The second transceiver module 502 is used to determine the target server that stores the risk data corresponding to the third code, send a first risk data acquisition request carrying the third code to the target server, and receive the fourth code corresponding to the risk data sent by the target server.

[0191] The second processing module 501 is further configured to parse the fourth code according to a preset second encoding method to obtain the risk data of the customer to be analyzed.

[0192] In one possible implementation, the second transceiver module 502 is specifically configured to send a target server determination request carrying the third code to a data center server of each regional alliance that has been pre-stored; and to receive response information carrying the identification information of the target server sent by each of the data center servers.

[0193] In one possible implementation, the second processing module 501 is specifically used to determine the target identity type carried in the identity information, determine the target fourth identifier corresponding to the target identity type according to the pre-saved correspondence between identity types and fourth identifiers, determine the identity ID carried in the target identity information, and determine the third code corresponding to the target fourth identifier and the identity ID according to a preset first order and the first encoding method.

[0194] In one possible implementation, the second processing module 501 is specifically used to sort the target fourth identifier and the identity ID according to a preset first order; determine the hash value corresponding to the sorting result, and use the hash value as the third code.

[0195] In one possible implementation, the second processing module 501 is specifically used to determine each sub-code in the fourth code using a preset second encoding method; for each sub-code, obtain the target fifth identifier used to identify the risk level in the sub-code, and determine the target risk level corresponding to the target fifth identifier according to the pre-saved correspondence between the risk level of each sub-risk type and the fifth identifier.

[0196] In one possible implementation, the second transceiver module 502 is further configured to, if it receives a second risk data acquisition request carrying a fifth code sent by another server, determine whether there is a target first code consistent with the fifth code in the first code stored locally; if there is, acquire the target second code of the risk data corresponding to the stored target first code, and send the target second code to the other server.

[0197] Example 13:

[0198] Based on the above embodiments, this application also provides an electronic device. Figure 6 This application provides a schematic diagram of an electronic device structure, such as... Figure 6 As shown, it includes: processor 61, communication interface 62, memory 63 and communication bus 64, wherein processor 61, communication interface 62 and memory 63 communicate with each other through communication bus 64.

[0199] The memory 63 stores a computer program, which, when executed by the processor 61, causes the processor 61 to perform the following steps:

[0200] Receive the identity information of the customer to be stored and the corresponding risk data, and obtain the first code corresponding to the identity information using a preset first encoding method;

[0201] Each sub-risk data in the risk data is obtained, and a sub-code corresponding to each sub-risk data is determined using a preset second encoding method; the sub-codes corresponding to each sub-risk data are sorted according to a preset sorting rule to generate a second code;

[0202] Save the first code and the second code accordingly.

[0203] In one possible implementation, obtaining the first code corresponding to the identity information of the customer to be stored using a preset first encoding method includes:

[0204] Determine the target identity type carried in the identity information, and determine the target first identifier corresponding to the target identity type based on the pre-saved correspondence between the identity type and the first identifier;

[0205] The identity ID carried in the identity information is determined, and the first code corresponding to the target first identifier and the identity ID is determined according to the preset first order and the first encoding method.

[0206] In one possible implementation, determining the first code corresponding to the target first identifier and the identity ID according to a preset first order and the first encoding method includes:

[0207] The target first identifier and the identity ID are sorted according to a preset first order;

[0208] Determine the hash value corresponding to the sorting result, and use the hash value as the first encoding.

[0209] In one possible implementation, after using the hash value as the first encoding, the method further includes:

[0210] The first code is sent to the data center server of the regional alliance where the server is located.

[0211] In one possible implementation, determining the sub-code corresponding to each sub-risk data using a preset second encoding method includes:

[0212] For each sub-risk data, obtain the target sub-risk type and target risk level in the sub-risk data; determine the target second identifier corresponding to the target sub-risk type according to the pre-saved correspondence between each sub-risk type and the second identifier; determine the target third identifier corresponding to the target risk level according to the pre-saved correspondence between the risk level of each sub-risk type and the third identifier; sort and combine the target second identifier and the target third identifier according to a preset second order, and determine the identifier obtained by sorting and combining as the sub-code corresponding to the sub-risk data.

[0213] In one possible implementation, the method further includes:

[0214] Obtain the risk occurrence time, risk event details, and risk data validity period carried in the risk data;

[0215] The time of occurrence of the risk, the details of the risk event, and the validity period of the risk data are saved in correspondence with the first code and the second code.

[0216] Since the principle of the above-mentioned electronic device in solving the problem is similar to that of the risk data storage method, the implementation of the above-mentioned electronic device can be found in the embodiments of the method, and repeated details will not be repeated.

[0217] The communication bus mentioned in the above-mentioned electronic device can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in the figure, but this does not indicate that there is only one bus or one type of bus. Communication interface 62 is used for communication between the above-mentioned electronic device and other devices. The memory can include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage device. Optionally, the memory can also be at least one storage device located remotely from the aforementioned processor.

[0218] The processors mentioned above can be general-purpose processors, including central processing units, network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits, field-programmable gate arrays or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0219] Example 14:

[0220] Based on the above embodiments, the electronic device also performs the following steps:

[0221] The third code corresponding to the identity information of the customer to be analyzed is determined by using a preset first coding method;

[0222] Identify the target server that stores the risk data corresponding to the third code, send a first risk data acquisition request carrying the third code to the target server, and receive the fourth code corresponding to the risk data sent by the target server;

[0223] The fourth code is parsed according to the preset second encoding method to obtain the risk data of the customer to be analyzed.

[0224] In one possible implementation, determining the target server for storing the risk data corresponding to the third code includes:

[0225] Send a target server determination request carrying the third code to the data center server of each pre-saved regional alliance;

[0226] Receive response information from each of the data center servers, which carries the identification information of the target server.

[0227] In one possible implementation, determining the third code corresponding to the identity information of the customer to be analyzed using a preset first encoding method includes:

[0228] Determine the target identity type carried in the identity information, and determine the target fourth identifier corresponding to the target identity type based on the pre-saved correspondence between the identity type and the fourth identifier;

[0229] The identity ID carried in the target identity information is determined, and the third code corresponding to the target fourth identifier and the identity ID is determined according to the preset first order and the first encoding method.

[0230] In one possible implementation, determining the third code corresponding to the target fourth identifier and the identity ID according to a preset first order and the first encoding method includes:

[0231] The target fourth identifier and the identity ID are sorted according to a preset first order;

[0232] Determine the hash value corresponding to the sorting result, and use the hash value as the third encoding.

[0233] In one possible implementation, parsing the fourth code according to a preset second encoding method to obtain the risk data of the customer to be analyzed includes:

[0234] Each sub-encoder in the fourth encoding is determined using a preset second encoding method;

[0235] For each sub-code, obtain the target fifth identifier used to identify the risk level in that sub-code, and determine the target risk level corresponding to the target fifth identifier based on the pre-saved correspondence between the risk level of each sub-risk type and the fifth identifier.

[0236] In one possible implementation, the method further includes:

[0237] If a request to obtain second risk data carrying a fifth code is received from another server, it is determined whether a target first code that matches the fifth code exists in the first code stored locally.

[0238] If it exists, then obtain the target second code of the risk data corresponding to the saved target first code, and send the target second code to the other servers.

[0239] Since the principle of the above-mentioned electronic device in solving the problem is similar to that of the risk data acquisition method, the implementation of the above-mentioned electronic device can be referred to the embodiments of the method, and the repeated parts will not be described again.

[0240] The communication bus mentioned in the above-mentioned electronic device can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in the figure, but this does not indicate that there is only one bus or one type of bus. Communication interface 62 is used for communication between the above-mentioned electronic device and other devices. The memory can include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage device. Optionally, the memory can also be at least one storage device located remotely from the aforementioned processor.

[0241] The processors mentioned above can be general-purpose processors, including central processing units, network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits, field-programmable gate arrays or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0242] Example 15:

[0243] Based on the above embodiments, this invention also provides a computer-readable storage medium storing a computer program executable by a processor. When the program runs on the processor, it causes the processor to perform the following steps:

[0244] Receive the identity information of the customer to be stored and the corresponding risk data, and obtain the first code corresponding to the identity information using a preset first encoding method;

[0245] Each sub-risk data in the risk data is obtained, and a sub-code corresponding to each sub-risk data is determined using a preset second encoding method; the sub-codes corresponding to each sub-risk data are sorted according to a preset sorting rule to generate a second code;

[0246] Save the first code and the second code accordingly.

[0247] In one possible implementation, obtaining the first code corresponding to the identity information of the customer to be stored using a preset first encoding method includes:

[0248] Determine the target identity type carried in the identity information, and determine the target first identifier corresponding to the target identity type based on the pre-saved correspondence between the identity type and the first identifier;

[0249] The identity ID carried in the identity information is determined, and the first code corresponding to the target first identifier and the identity ID is determined according to the preset first order and the first encoding method.

[0250] In one possible implementation, determining the first code corresponding to the target first identifier and the identity ID according to a preset first order and the first encoding method includes:

[0251] The target first identifier and the identity ID are sorted according to a preset first order;

[0252] Determine the hash value corresponding to the sorting result, and use the hash value as the first encoding.

[0253] In one possible implementation, after using the hash value as the first encoding, the method further includes:

[0254] The first code is sent to the data center server of the regional alliance where the server is located.

[0255] In one possible implementation, determining the sub-code corresponding to each sub-risk data using a preset second encoding method includes:

[0256] For each sub-risk data, obtain the target sub-risk type and target risk level in the sub-risk data; determine the target second identifier corresponding to the target sub-risk type according to the pre-saved correspondence between each sub-risk type and the second identifier; determine the target third identifier corresponding to the target risk level according to the pre-saved correspondence between the risk level of each sub-risk type and the third identifier; sort and combine the target second identifier and the target third identifier according to a preset second order, and determine the identifier obtained by sorting and combining as the sub-code corresponding to the sub-risk data.

[0257] In one possible implementation, the method further includes:

[0258] Obtain the risk occurrence time, risk event details, and risk data validity period carried in the risk data;

[0259] The time of occurrence of the risk, the details of the risk event, and the validity period of the risk data are saved in correspondence with the first code and the second code.

[0260] Since the principle of the computer-readable storage medium in solving the problem is similar to that of the risky data storage method, the implementation of the computer-readable storage medium can be found in the embodiments of the method, and repeated details will not be repeated.

[0261] Example 16:

[0262] Based on the above embodiments, this invention also provides a computer-readable storage medium storing a computer program executable by a processor. When the program runs on the processor, it causes the processor to perform the following steps:

[0263] The third code corresponding to the identity information of the customer to be analyzed is determined by using a preset first coding method;

[0264] Identify the target server that stores the risk data corresponding to the third code, send a first risk data acquisition request carrying the third code to the target server, and receive the fourth code corresponding to the risk data sent by the target server;

[0265] The fourth code is parsed according to the preset second encoding method to obtain the risk data of the customer to be analyzed.

[0266] In one possible implementation, determining the target server for storing the risk data corresponding to the third code includes:

[0267] Send a target server determination request carrying the third code to the data center server of each pre-saved regional alliance;

[0268] Receive response information from each of the data center servers, which carries the identification information of the target server.

[0269] In one possible implementation, determining the third code corresponding to the identity information of the customer to be analyzed using a preset first encoding method includes:

[0270] Determine the target identity type carried in the identity information, and determine the target fourth identifier corresponding to the target identity type based on the pre-saved correspondence between the identity type and the fourth identifier;

[0271] The identity ID carried in the target identity information is determined, and the third code corresponding to the target fourth identifier and the identity ID is determined according to the preset first order and the first encoding method.

[0272] In one possible implementation, determining the third code corresponding to the target fourth identifier and the identity ID according to a preset first order and the first encoding method includes:

[0273] The target fourth identifier and the identity ID are sorted according to a preset first order;

[0274] Determine the hash value corresponding to the sorting result, and use the hash value as the third encoding.

[0275] In one possible implementation, parsing the fourth code according to a preset second encoding method to obtain the risk data of the customer to be analyzed includes:

[0276] Each sub-encoder in the fourth encoding is determined using a preset second encoding method;

[0277] For each sub-code, obtain the target fifth identifier used to identify the risk level in that sub-code, and determine the target risk level corresponding to the target fifth identifier based on the pre-saved correspondence between the risk level of each sub-risk type and the fifth identifier.

[0278] In one possible implementation, the method further includes:

[0279] If a request to obtain second risk data carrying a fifth code is received from another server, it is determined whether a target first code that matches the fifth code exists in the first code stored locally.

[0280] If it exists, then obtain the target second code of the risk data corresponding to the saved target first code, and send the target second code to the other servers.

[0281] Since the principle of the computer-readable storage medium in solving the problem is similar to that of the risky data storage method, the implementation of the computer-readable storage medium can be found in the embodiments of the method, and repeated details will not be repeated.

[0282] Example 17:

[0283] This application also provides a computer program product that, when executed by a computer, implements the risk data storage and retrieval method described in any of the above-described method embodiments applied to electronic devices.

[0284] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof, or in whole or in part, as a computer program product. The computer program product includes one or more computer instructions, which, when loaded and executed on a computer, generate, in whole or in part, the processes or functions described in the embodiments of this application.

[0285] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0286] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0287] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0288] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0289] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A risk data storage method characterized by, The method comprises: Receiving the identity information and corresponding risk data of a client to be stored, and obtaining a first code corresponding to the identity information by using a preset first encoding mode; Obtaining each sub-risk data in the risk data, determining a sub-code corresponding to each sub-risk data by using a preset second encoding mode, and generating a second code by sorting the sub-codes corresponding to each sub-risk data according to a preset sorting rule; Correspondingly saving the first code and the second code; The method comprises: For each sub-risk data, obtaining a target sub-risk type and a target risk level in the sub-risk data, determining a target second identifier corresponding to the target sub-risk type according to a pre-stored corresponding relationship between each sub-risk type and a second identifier, determining a target third identifier corresponding to the target risk level according to a pre-stored corresponding relationship between the risk level of each sub-risk type and a third identifier, and sorting the target second identifier and the target third identifier according to a preset second order to combine the identifiers obtained by sorting as the sub-code corresponding to the sub-risk data; The method comprises: Determining a target identity type carried in the identity information, and determining a target first identifier corresponding to the target identity type according to a pre-stored corresponding relationship between an identity type and a first identifier; Determining an identity ID carried in the identity information, and determining a first code corresponding to the target first identifier and the identity ID according to a preset first order and the first encoding mode; The type of the client to be stored at least includes an individual, an enterprise or a company; If the client to be stored is an individual, the target identity type carried in the identity information of the client to be stored is an ID card, and the identity ID is an ID card number; If the client to be stored is an enterprise or a company, the target identity type carried in the identity information of the client to be stored is a business license, and the identity ID is a tax number; The method comprises: Sorting the target first identifier and the identity ID according to a preset first order; Determining a hash value corresponding to the sorting result, and taking the hash value as the first code.

2. The method of claim 1, wherein, After taking the hash value as the first code, the method further comprises: Sending the first code to a data center server of a regional alliance where a server is located.

3. The method of claim 1, wherein, The method further comprises: Obtaining a risk occurrence time, risk event details and a risk data validity period carried in the risk data; Correspondingly saving the risk occurrence time, the risk event details, the risk data validity period, the first code and the second code.

4. A risk data acquisition method characterized by, The method comprises: Determining a third code corresponding to the identity information of a client to be analyzed by using a preset first encoding mode; determine a target server storing the risk data corresponding to the third code, send a first risk data acquisition request carrying the third code to the target server, and receive a fourth code sent by the target server and corresponding to the risk data; analyze the fourth code according to a preset second encoding mode to obtain the risk data of the client to be analyzed; wherein the analyzing the fourth code according to the preset second encoding mode to obtain the risk data of the client to be analyzed comprises: determining each sub-code in the fourth code by using the preset second encoding mode; for each sub-code, obtaining a target fifth identifier for identifying a risk level in the sub-code, and determining a target risk level corresponding to the target fifth identifier according to a pre-stored corresponding relationship between risk levels of each sub-risk type and fifth identifiers; wherein the determining the third code corresponding to the identity information of the client to be analyzed by using the preset first encoding mode comprises: determining a target identity type carried in the identity information, and determining a target fourth identifier corresponding to the target identity type according to a pre-stored corresponding relationship between identity types and fourth identifiers; determining an identity ID carried in the target identity information, and determining a third code corresponding to the target fourth identifier and the identity ID according to a preset first order and the first encoding mode; wherein the type of the client to be analyzed at least includes an individual, an enterprise or a company; if the client to be analyzed is an individual, the target identity type carried in the identity information of the client to be analyzed is an ID card, and the identity ID is an ID card number; if the client to be analyzed is an enterprise or a company, the target identity type carried in the identity information of the client to be analyzed is a business license, and the identity ID is a tax number; wherein the determining the third code corresponding to the target fourth identifier and the identity ID according to the preset first order and the first encoding mode comprises: sorting the target fourth identifier and the identity ID according to a preset first order; determining a hash value corresponding to the sorting result, and taking the hash value as the third code.

5. The method of claim 4, wherein, The determining the target server storing the risk data corresponding to the third code comprises: sending a target server determination request carrying the third code to a data center server of each regional alliance pre-stored; receiving response information carrying identification information of the target server sent by each data center server.

6. The method of claim 4, wherein, The method further comprises: if a second risk data acquisition request carrying a fifth code is received from another server, determining whether a target first code consistent with the fifth code exists in the first code pre-stored locally; if the target first code exists, obtaining a target second code of the risk data corresponding to the target first code pre-stored, and sending the target second code to the another server.

7. A risk data storage device, characterized by, The apparatus comprises: a first transceiving module configured to receive identity information of a client to be stored and corresponding risk data; The first processing module is configured to obtain a first code corresponding to the identity information by using a preset first encoding mode; obtain each sub-risk data in the risk data, determine a sub-code corresponding to each sub-risk data by using a preset second encoding mode; and sort the sub-codes corresponding to each sub-risk data according to a preset sorting rule to generate a second code. The storage module is configured to save the first code and the second code correspondingly. The first processing module is specifically configured to obtain a target sub-risk type and a target risk level in each sub-risk data, determine a target second identifier corresponding to the target sub-risk type according to a preset correspondence between each sub-risk type and a second identifier, determine a target third identifier corresponding to the target risk level according to a preset correspondence between the risk level of each sub-risk type and a third identifier, sort the target second identifier and the target third identifier according to a preset second order, and determine an identifier obtained by sorting as the sub-code corresponding to the sub-risk data. The first processing module is specifically configured to determine a target identity type carried in the identity information, determine a target first identifier corresponding to the target identity type according to a preset correspondence between an identity type and a first identifier, and determine a first code corresponding to the target first identifier and an identity ID according to a preset first order and the first encoding mode. The type of the client to be stored includes at least a person, an enterprise or a company. If the client to be stored is a person, a target identity type carried in the identity information of the client to be stored is an ID card, and the identity ID is an ID card number. If the client to be stored is an enterprise or a company, a target identity type carried in the identity information of the client to be stored is a business license, and the identity ID is a tax number. The first processing module is specifically configured to sort the target first identifier and the identity ID according to a preset first order, determine a hash value corresponding to the sorting result, and take the hash value as the first code.

8. The apparatus of claim 7, wherein, The first processing module is further configured to send the first code to a data center server of a regional alliance where a server is located.

9. The apparatus of claim 7, wherein, The first processing module is further configured to obtain a risk occurrence time, risk event details and a risk data validity period carried in the risk data. The storage module is further configured to save the risk occurrence time, the risk event details, the risk data validity period, the first code and the second code correspondingly.

10. A risk data acquisition apparatus characterized by comprising: The device comprises: The second processing module is configured to determine a third code corresponding to the identity information of the client to be analyzed by using a preset first encoding mode. The second transceiver module is configured to determine a target server storing risk data corresponding to the third code, send a first risk data acquisition request carrying the third code to the target server, and receive a fourth code corresponding to the risk data sent by the target server. The second processing module is further configured to parse the fourth code according to a preset second encoding mode to obtain the risk data of the client to be analyzed. The second processing module is configured to determine each sub-code in the fourth code by using a preset second encoding mode, obtain a target fifth identifier for identifying a risk level in each sub-code, and determine a target risk level corresponding to the target fifth identifier according to a pre-stored correspondence between risk levels of each sub-risk type and fifth identifiers. The second processing module is configured to determine a target identity type carried in the identity information, determine a target fourth identifier corresponding to the target identity type according to a pre-stored correspondence between identity types and fourth identifiers, determine an identity ID carried in the target identity information, and determine a third code corresponding to the target fourth identifier and the identity ID according to a preset first order and the first encoding mode. The type of the client to be analyzed at least includes an individual, an enterprise, or a company. If the client to be analyzed is an individual, the target identity type carried in the identity information of the client to be analyzed is an ID card, and the identity ID is an ID card number. If the client to be analyzed is an enterprise or a company, the target identity type carried in the identity information of the client to be analyzed is a business license, and the identity ID is a tax number. The second processing module is configured to sort the target fourth identifier and the identity ID according to a preset first order, determine a hash value corresponding to the sorting result, and use the hash value as the third code.

11. The apparatus of claim 10, wherein, The second transceiver module is configured to send a target server determination request carrying the third code to a data center server of each pre-stored regional alliance, and receive response information carrying identification information of the target server sent by each data center server.

12. The apparatus of claim 10, wherein, The second transceiver module is further configured to determine whether there is a target first code consistent with a fifth code in the locally saved first code if a second risk data acquisition request carrying the fifth code is received from another server. If there is, the second transceiver module is configured to acquire a target second code of risk data corresponding to the target first code, and send the target second code to the other server.

13. An electronic device, comprising: The electronic device includes a processor configured to implement the steps of the risk data storage method according to any one of claims 1-3 or the steps of the risk data acquisition method according to any one of claims 4-6 when executing a computer program stored in a memory.

14. A computer-readable storage medium, characterized in that, The electronic device has a computer program stored therein, and the computer program is executed by a processor to implement the steps of the risk data storage method according to any one of claims 1-3 or the steps of the risk data acquisition method according to any one of claims 4-6.

15. A computer program product, characterised in that, The computer program product includes computer program code, which, when executed on a computer, causes the computer to perform the steps of the risk data storage method according to any one of claims 1-3 or the steps of the risk data acquisition method according to any one of claims 4-6.

Images