Data processing method and device, electronic equipment, storage medium and program product

Abstract

The embodiment of the invention provides a data processing method and device, electronic equipment, a storage medium and a program product. The method comprises the steps of obtaining transaction source data in a current preset period every preset period, determining transaction source data meeting a preset condition from the transaction source data according to the preset condition to obtain a plurality of hit source data, generating a corresponding to-be-reported event based on the plurality of hit source data, and reporting the to-be-reported event according to the to-be-reported event. The method comprises the following steps: when a suspicious instruction is received in a current preset period, merging a historical suspicious event with a to-be-reported event according to a preset merging strategy to obtain a merged event, generating a target message according to the merged event, pre-checking the target message, and reporting the target message when a pre-checking result indicates that the pre-checking of the target message is successful. The method is used for achieving the effects of effectively reporting the foreign exchange suspicious transaction related information and enhancing the reporting accuracy and reliability.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data processing method, device, electronic device, storage medium and program product. Background Art

[0002] Currently, banks are required to submit financial transaction data on a daily basis. Among them, foreign exchange transactions have unique reporting rules. For example, there are as many as twelve reporting scenarios for foreign exchange transactions, and the dimensions and number of customer classifications for foreign exchange transactions are also relatively large.

[0003] The existing technology can complete the reporting of information related to large-value transactions and suspicious transactions through the suspicious transaction monitoring system. However, the existing technology of reporting transaction-related information to the People's Bank of China is difficult to accurately adapt to the scenario of reporting information related to suspicious foreign exchange transactions to the State Administration of Foreign Exchange, which reduces the accuracy and reliability of determining suspicious foreign exchange transaction data, and further reduces the reporting efficiency of information related to suspicious foreign exchange transactions. Summary of the invention

[0004] The embodiments of the present application provide a data processing method, an apparatus, an electronic device, a storage medium, and a program product for effectively reporting information related to suspicious foreign exchange transactions and enhancing the accuracy and reliability of the reported information related to suspicious foreign exchange transactions.

[0005] In a first aspect, an embodiment of the present application provides a data processing method, including:

[0006] Acquire transaction source data within the current preset period at every preset period; determine a plurality of corresponding hit source data based on the transaction source data, where the hit source data is transaction source data that meets preset conditions;

[0007] Generate corresponding events to be reported based on multiple hit source data; based on suspicious indications received within the current preset period, merge historical suspicious events with events to be reported according to a preset merging strategy to obtain a merged event;

[0008] A target message is generated according to the merged event; a pre-verification is performed on the target message, and when the pre-verification result indicates that the pre-verification of the target message is successful, the target message is reported.

[0009] Optionally, historical suspicious events are merged with events to be reported according to a preset merging strategy to obtain a merged event, which specifically includes:

[0010] Determining historical hit source data of the indication based on the suspicious indication; generating a first historical suspicious event within a current preset period according to the historical hit source data;

[0011] Perform a trial operation on the reported event, and obtain the second historical suspicious event within the current preset period according to the trial operation result;

[0012] The event to be reported, the first historical suspicious event and the second historical suspicious event are merged to generate a merged event, where the merged event includes multiple events.

[0013] Optionally, before generating the target message, obtain the full amount of customer information corresponding to the transaction source data within the current preset period;

[0014] The customer grade table corresponding to the transaction source data is determined according to the full amount of customer information, and the customer grade table includes customer grades corresponding to multiple customer numbers in the current preset period.

[0015] Optionally, the customer level table corresponding to the transaction source data is determined according to the full amount of customer information, specifically including:

[0016] Generate an intermediate customer rating table based on all customer information;

[0017] Determine the qualitative weight data corresponding to the multiple customer numbers in the transaction source data based on the preset customer dimension corresponding table, and determine the quantitative weight data corresponding to the multiple customer numbers based on the preset conditions corresponding to the multiple hit source data;

[0018] The customer rating intermediate table is weighted according to the qualitative weight data and the quantitative weight data to obtain the weighted customer rating intermediate table and generate a customer grade table.

[0019] Optionally, generating a target message according to the merge event specifically includes:

[0020] Suspicious verification of merged events based on customer rating tables;

[0021] When there is a suspected verification error, multiple events in the merged event are added or deleted according to the customer level table;

[0022] When the suspicious verification is correct, a message table is generated; based on the message table, a target message is obtained, the target message includes multiple sub-target messages, and the sub-target messages are obtained by splitting the message table according to a preset number.

[0023] Optionally, when the pre-check result indicates that the target message fails to be checked, a retransmission instruction is generated;

[0024] The repair data corresponding to the target message is obtained based on the retransmission instruction, the target message is updated according to the repair data, and the target message is re-transmitted according to the updated target message.

[0025] In a second aspect, an embodiment of the present application provides a data processing device, including:

[0026] An acquisition module, used for acquiring transaction source data within a current preset period at every preset period; determining a plurality of corresponding hit source data based on the transaction source data, where the hit source data is transaction source data that meets preset conditions;

[0027] A processing module, used to generate corresponding events to be reported based on multiple hit source data; based on suspicious indications received within a current preset period, merge historical suspicious events with events to be reported according to a preset merging strategy to obtain a merged event;

[0028] The processing module is also used to generate a target message according to the merge event; perform pre-verification on the target message, and report the target message when the pre-verification result indicates that the pre-verification of the target message is successful.

[0029] Optionally, the processing module is further used to determine historical hit source data of the indication based on the suspicious indication; generate a first historical suspicious event within a current preset period according to the historical hit source data;

[0030] Perform a trial operation on the reported event, and obtain the second historical suspicious event within the current preset period according to the trial operation result;

[0031] The event to be reported, the first historical suspicious event and the second historical suspicious event are merged to generate a merged event, where the merged event includes multiple events.

[0032] Optionally, the acquisition module is further used to acquire the full amount of customer information corresponding to the transaction source data within the current preset period before generating the target message;

[0033] The customer grade table corresponding to the transaction source data is determined according to the full amount of customer information, and the customer grade table includes customer grades corresponding to multiple customer numbers in the current preset period.

[0034] Optionally, the processing module is further used to generate a customer rating intermediate table based on the full amount of customer information;

[0035] Determine the qualitative weight data corresponding to the multiple customer numbers in the transaction source data based on the preset customer dimension corresponding table, and determine the quantitative weight data corresponding to the multiple customer numbers based on the preset conditions corresponding to the multiple hit source data;

[0036] The customer rating intermediate table is weighted according to the qualitative weight data and the quantitative weight data to obtain the weighted customer rating intermediate table and generate a customer grade table.

[0037] Optionally, the processing module is further used to perform suspicious verification on the merged event based on the customer rating table;

[0038] When there is a suspected verification error, multiple events in the merged event are added or deleted according to the customer level table;

[0039] When the suspicious verification is correct, a message table is generated; based on the message table, a target message is obtained, the target message includes multiple sub-target messages, and the sub-target messages are obtained by splitting the message table according to a preset number.

[0040] Optionally, the processing module is further configured to generate a retransmission instruction when the pre-check result indicates that the target message fails to be checked;

[0041] The repair data corresponding to the target message is obtained based on the retransmission instruction, the target message is updated according to the repair data, and the target message is re-transmitted according to the updated target message.

[0042] In a third aspect, an embodiment of the present application provides an electronic device, including: a memory, a processor;

[0043] Memory stores computer-executable instructions;

[0044] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the above first aspect and / or various possible implementations of the first aspect.

[0045] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the first aspect above and / or various possible implementations of the first aspect.

[0046] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the above first aspect and / or various possible implementation methods of the first aspect.

[0047] The data processing method, device, electronic device, storage medium and program product provided by the embodiment of the present application obtain transaction source data within the current preset period at every preset period, determine the transaction source data that meets the preset condition from the transaction source data according to the preset condition, obtain multiple hit source data, generate corresponding events to be reported based on the multiple hit source data, and when a suspicious indication is received within the current preset period, merge the historical suspicious event with the event to be reported according to the preset merging strategy to obtain a merged event, generate a target message according to the merged event, and pre-check the target message, and report the target message when the pre-check result indicates that the pre-check of the target message is successful. Therefore, the present application realizes the effective reporting of information related to suspicious foreign exchange transactions, and enhances the accuracy and reliability of reporting. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0049] Figure 1 A schematic diagram of an application scenario of the data processing method provided in this application;

[0050] Figure 2 Schematic diagram of the data processing method provided for this application Figure 1 ;

[0051] Figure 3 Schematic diagram of the data processing method provided for this application Figure 2 ;

[0052] Figure 4 Schematic diagram of the data processing method provided for this application Figure 3 ;

[0053] Figure 5 Schematic diagram of the data processing method provided for this application Figure 4 ;

[0054] Figure 6 Schematic diagram of the data processing method provided for this application Figure 5 ;

[0055] Figure 7 A schematic diagram of the structure of the data processing device provided by this application;

[0056] Figure 8 A schematic diagram of the structure of the electronic device provided in this application.

[0057] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0058] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0059] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards in the relevant regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0060] Banks need to report suspicious transactions in accordance with relevant requirements. At present, banks monitor real-time non-foreign exchange transactions through transaction monitoring systems, and select non-foreign exchange transactions that need to be reported based on the monitoring results, and report the complete information of non-foreign exchange transactions that need to be reported.

[0061] At present, based on the new reporting requirements for foreign exchange transactions, the existing technology continues to use the current transaction monitoring system to report transactions, which is difficult to cover the various suspicious scenarios and / or complex scenarios corresponding to foreign exchange transactions. Therefore, the reporting method of the existing technology reduces the accuracy and comprehensiveness of the reported information, thereby further reducing the reporting efficiency and reliability of suspicious foreign exchange transactions.

[0062] Figure 1 A schematic diagram of an application scenario of the data processing method provided in this application, such as Figure 1 As shown, the specific application scenario of the present application includes the interface of the foreign exchange trading system, the suspicious foreign exchange reporting system and the pre-financial management information system, wherein the foreign exchange trading system includes transaction source data 1, ... transaction source data n, where n is a positive integer. In the application scenario, the relevant data of foreign exchange transactions are stored in the foreign exchange trading system, and multiple suspicious transaction source data are obtained from the foreign exchange trading system through the suspicious foreign exchange reporting system, and the suspicious transaction source data are sent to the pre-financial management information system through the interface of the pre-financial management information system, so as to realize the reporting of relevant information of suspicious foreign exchange transactions to the pre-financial management information system.

[0063] The data processing method provided by the present application obtains multiple transaction source data within the current preset period at every preset period, and selects the transaction source data that meets the preset conditions in the foreign exchange transaction data to obtain the hit source data. The event to be reported in the current preset period is generated according to the multiple hit source data, and when a suspicious indication is received within the current preset period, the first historical suspicious event is determined, and the first historical suspicious event and the second historical suspicious event obtained after the trial operation of the event to be reported are merged with the event to be reported to obtain a merged event, and a target message is generated when the merged event is verified, and the target message is reported after the pre-verification of the target message is passed. The present application realizes the effective reporting of relevant information of suspicious foreign exchange transactions, and enhances the accuracy and reliability of the reported information related to suspicious transactions.

[0064] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0065] Figure 2 Schematic diagram of the data processing method provided for this application Figure 1 ,like Figure 2 As shown, the method includes:

[0066] S201. Obtain transaction source data within the current preset period at every preset period, and determine a plurality of hit source data satisfying preset conditions.

[0067] More specifically, the transaction source data within the current preset period is acquired every preset period; and a plurality of corresponding hit source data are determined based on the transaction source data, where the hit source data is the transaction source data that meets the preset conditions.

[0068] Exemplarily, transaction source data includes, but is not limited to, transaction information, customer information, and account information.

[0069] Optionally, the preset condition is generated based on the configuration information input by the user. For example, by obtaining the factor parameter information of the factor analysis model input by the user, factor analysis processing is performed on the transaction source data using the factor parameter information of the factor analysis model, and multiple customer numbers hit by the factor parameter information are obtained, and multiple transaction source data corresponding to the multiple customer numbers are obtained, thereby obtaining multiple hit source data.

[0070] S202: Generate a corresponding event to be reported, and based on the suspicious indication received within the current preset period, merge the historical suspicious event with the event to be reported to obtain a merged event.

[0071] More specifically, corresponding events to be reported are generated based on multiple hit source data; based on suspicious indications received within a current preset period, historical suspicious events are merged with events to be reported according to a preset merging strategy to obtain a merged event.

[0072] Optionally, the historical suspicious event includes a first historical suspicious event and a second historical suspicious event.

[0073] Optionally, historical suspicious events are merged with events to be reported according to a preset merging strategy to obtain a merged event, which specifically includes: determining historical hit source data of the indication based on the suspicious indication; generating a first historical suspicious event within a current preset period based on the historical hit source data; performing a trial run processing on the event to be reported, and obtaining a second historical suspicious event within the current preset period based on the trial run processing result; merging the event to be reported, the first historical suspicious event and the second historical suspicious event to generate a merged event, and the merged event includes multiple events.

[0074] In a possible embodiment, the processing steps based on the preset merging strategy are: when a suspicious indication is received within the current preset period, the customer number indicated by the suspicious indication is determined, the historical hit source data corresponding to the customer number is determined, and the historical hit source data corresponding to the customer number is reviewed. When it is determined that the review has not passed, a first historical suspicious event (i.e., an event that is suspicious and has not passed the review within the current preset period) is generated based on the historical hit source data. At the same time, the trial operation result is obtained by performing a trial operation on the trial operation event, and whether the review has passed is determined based on the trial operation result. When it is determined that the review has not passed, a second historical suspicious event (i.e., an event that is not suspicious and has not passed the review within the current preset period) is generated based on the trial operation event. The first historical suspicious event and the second historical suspicious event are merged with multiple hit source data (or events to be reported) to obtain a merged event. The merged event includes the relevant foreign exchange transaction information corresponding to each transaction source data in the first historical suspicious event, the second historical suspicious event, and the event to be reported.

[0075] This embodiment obtains events that are determined to be suspicious and have not passed the review within the current preset period through suspicious indications, and merges the events, events that are determined not to be suspicious and have not passed the review, and the events to be reported, thereby improving the comprehensiveness and accuracy of suspicious events and further enhancing the reliability of event reporting.

[0076] S203: Generate a target message according to the merge event, and submit the target message when the pre-verification of the target message succeeds.

[0077] More specifically, a target message is generated according to the merging event; the target message is pre-checked according to a preset check standard, and when the pre-check result indicates that the pre-check of the target message is successful, the target message is reported.

[0078] Optionally, when the pre-check result indicates that the target message has failed to be checked, a retransmission instruction is generated; based on the retransmission instruction, the repair data corresponding to the target message is obtained, the target message is updated according to the repair data, and the updated target message is resubmitted. In this embodiment, when it is determined that the pre-check of the target message has failed, the repair data corresponding to the target message is obtained in a timely manner, and the target message is repaired according to the repair data, thereby implementing the repair step when the pre-check fails, reducing the possibility of reporting failure, improving the reliability of reporting suspicious foreign exchange transactions, and further reducing the reporting cost of suspicious foreign exchange transactions.

[0079] Optionally, before generating the target message, obtain the full customer information corresponding to the transaction source data in the current preset period; determine the customer grade table corresponding to the transaction source data based on the full customer information, the customer grade table including the customer grades corresponding to multiple customer numbers in the current preset period.

[0080] Exemplarily, the complete customer information includes, but is not limited to, corporate customer information, corporate account information, associated person information, etc.

[0081] Optionally, determining the customer rating table corresponding to the transaction source data according to the full amount of customer information specifically includes: generating a customer rating intermediate table according to the full amount of customer information; determining the qualitative weight data corresponding to the multiple customer numbers in the transaction source data based on the preset customer dimension corresponding table, and determining the quantitative weight data corresponding to the multiple customer numbers according to the preset conditions corresponding to the multiple hit source data; performing weighted processing on the customer rating intermediate table according to the qualitative weight data and the quantitative weight data, respectively, to obtain the weighted customer rating intermediate table, and generating a customer rating table. Among them, the preset customer dimension is a dimension corresponding table corresponding to the customer classification dimension of foreign exchange transactions, including a preset customer number and the customer grade or customer rating corresponding to the customer number.

[0082] In a possible embodiment, a customer scoring intermediate table is generated based on multiple customer numbers corresponding to the transaction source data within the current preset period, the full customer data and preset conditions are maintained in the customer scoring intermediate table, and quantitative weight data corresponding to multiple customer numbers are generated based on the transaction source data and the preset conditions. At the same time, the qualitative weight data corresponding to multiple customer numbers in the transaction source data are determined based on the preset customer dimension corresponding table, and the score of each customer number is updated according to the qualitative weight data and quantitative weight data corresponding to the customer number, so as to obtain a weighted customer scoring intermediate table. Before generating the target message, this embodiment obtains the full customer information involved in the transaction source data within the current preset period, and generates the customer scoring intermediate table based on the full customer information, transaction source data and preset conditions, so as to achieve accurate classification of foreign exchange trading customers.

[0083] Optionally, a target message is generated based on the merged event, specifically including: performing suspicious verification on the merged event based on the customer level table; when the suspicious verification is incorrect, adding and deleting multiple events in the merged event according to the customer level table; when the suspicious verification is correct, generating a message table; obtaining a target message based on the message table, the target message including multiple sub-target messages, and the sub-target messages are obtained by splitting the message table according to a preset number.

[0084] Exemplarily, multiple customer numbers involved in the merged event are determined, and the level corresponding to each of the above customer numbers is determined according to the customer level table. For customer numbers with a level lower than a first preset threshold, a first coefficient mapped to the first preset threshold is determined, and the first coefficient is used to process the transaction source data (or event) corresponding to the customer number to reduce the suspiciousness of the transaction source data corresponding to the customer number. For customer numbers with a level higher than a second preset threshold, a second coefficient mapped to the second preset threshold is determined, and the second coefficient is used to process the transaction source data corresponding to the customer number to increase the suspiciousness of the transaction source data corresponding to the customer number.

[0085] This embodiment further verifies the event suspicion of customers of different levels in the merged event through the customer grade table, improves the accuracy and reliability of the reported messages, and improves the accuracy and reliability of foreign exchange transaction reporting.

[0086] The data processing method provided in the embodiment of the present application obtains foreign exchange transaction source data within the current preset period at every preset period, and determines the transaction source data that meets the preset conditions to obtain the hit source data, and when a suspicious indication is received, merges the events of multiple channels within the current preset period to obtain a merged event, and reports it when the pre-verification of the target message corresponding to the merged event succeeds, thereby improving the integrity, accuracy and reliability of the reported message, realizing the effective reporting of information related to suspicious foreign exchange transactions, and improving the reliability of foreign exchange reporting.

[0087] Optionally, the data processing method of the present application is applied to a suspicious foreign exchange reporting system, which includes a data center, a system database, and a system page.

[0088] Figure 3 Schematic diagram of the data processing method provided for this application Figure 2 ,like Figure 3 As shown, in this embodiment Figure 2 Based on the embodiment, the data processing method is described in detail, and the method includes:

[0089] S301. The data center obtains transaction source data.

[0090] More specifically, the data center obtains transaction data sources through batch channels.

[0091] In a possible embodiment, Figure 4 As shown, the data middle platform obtains transaction source data and system configuration data from the data layer through a batch channel, wherein the system configuration data includes but is not limited to analysis model configuration information, and the analysis model configuration information includes preset conditions and model assembly parameters.

[0092] Exemplarily, the system configuration data is stored in the data layer by the parameter management micro-application.

[0093] In a possible embodiment, Figure 4 As shown, the access layer of the suspicious foreign exchange reporting system is used as the front end of the system to provide an access interface for foreign exchange trading business. The client handling the business interacts with the suspicious foreign exchange reporting system through the access layer, wherein the interaction method includes but is not limited to a web interface, a mobile application interface or other user interface. The application layer of the suspicious foreign exchange reporting system is used to load the data of the data layer and perform data processing. The application layer includes six types of micro-applications, namely parameter management micro-applications, suspicious message processing micro-applications, trial operation micro-applications, customer classification micro-applications, customer level query micro-applications and suspicious event reporting micro-applications. The user information and login information in the data layer of the suspicious foreign exchange reporting system are the information of each staff member who uses the suspicious foreign exchange reporting system to report. This embodiment improves the modularity and extensibility of the suspicious foreign exchange reporting system through the architectural design of the application layer, data layer and access layer, so that each layer can be independently developed and maintained, and also improves the convenience of upgrading and function expansion of the suspicious foreign exchange reporting system.

[0094] S302. The data center determines the corresponding multiple hit source data based on the transaction source data.

[0095] More specifically, the data center obtains preset conditions based on the acquired system configuration data, and filters the transaction source data based on the preset conditions to obtain multiple hit source data.

[0096] S303. The data center sends multiple hit source data to the system database.

[0097] Optionally, the data center sends multiple hit source data and system configuration data to the system database.

[0098] S304: The system database generates an event to be reported and performs a trial run process to obtain a second historical suspicious event.

[0099] More specifically, the system database performs event assembly processing on the multiple hit source data using the model assembly parameters in the above system configuration data to obtain the event to be reported. The event to be reported is copied and input into the trial run micro application, so that the trial run micro application performs a trial run on the event to be reported, and obtains the second suspicious historical event (i.e. Figure 4 The test run result information is shown).

[0100] Optionally, before the trial run micro application is trial run, the trial run micro application is also used to train and optimize the model assembly parameters.

[0101] S305. The system page sends a suspicious indication to the system database.

[0102] More specifically, after the data center sends multiple hit source data to the system database, the system page Figure 4 The suspicious event reporting micro application shown inputs suspicious indications into the system database. The suspicious indication is the input suspicious event or suspicious message (i.e. Figure 4 Suspicious reporting information shown).

[0103] S306. The system database loads historical hit source data corresponding to the suspicious indication.

[0104] More specifically, the system database determines the corresponding customer number based on the suspicious indication, and sends the customer number to the data center, so that the data center determines the matching historical hit source data based on the customer number and feeds it back to the system database.

[0105] S307. The system database sends historical hit source data to the system page.

[0106] More specifically, after the system database obtains the historical hit source data, it sends it to the system page.

[0107] S308: The system page obtains the first historical suspicious event.

[0108] More specifically, the system page is accessed through Figure 4 The suspicious event reporting micro-application shown reviews the historical hit source data to determine whether the information in the historical hit source data is suspicious foreign exchange transaction information. When it is determined to be suspicious foreign exchange transaction information (i.e., it fails the review), a first historical suspicious event is generated.

[0109] S309: The system page sends the first historical suspicious event to the system database.

[0110] S310: The system database generates a merge event.

[0111] More specifically, after the system database receives the first historical suspicious event and the second historical suspicious event, Figure 4 The suspicious message processing micro-application shown merges the first historical suspicious event, the second historical suspicious event, and the event to be reported to obtain a merged event.

[0112] S311. The system database sends a merge event to the system page.

[0113] S312, the system page performs suspicious verification and generates a verification result.

[0114] More specifically, the system page is accessed through Figure 4 The suspicious event reporting micro application shown performs suspicious verification on the merged events and generates verification results.

[0115] Optionally, before the system page performs suspicious verification, receive Figure 4 The customer classification micro application shown in the figure transmits the customer level table through Figure 4 The suspicious event reporting micro application shown performs suspicious verification on the merged events according to the customer rating table and generates a verification result.

[0116] In one possible embodiment, Figure 5 Schematic diagram of the data processing method provided for this application Figure 3 ,like Figure 5 As shown, the steps for generating the customer level table are as follows:

[0117] S501. The data center obtains all customer information.

[0118] More specifically, the data center obtains all customer information through batch channels. Figure 4 As shown, the full customer information includes but is not limited to basic information about private customers, basic information about corporate customers, suspicious information about private customers, and suspicious information about corporate customers.

[0119] S502. The data center generates an intermediate customer rating table based on the customer's full information.

[0120] More specifically, the data center generates a customer rating intermediate table for foreign exchange transactions in the current preset period based on the customer number in the full customer information. The customer rating intermediate table includes the customer number. The data center maintains the loaded analysis model configuration information and classification parameter configuration information to the above customer rating intermediate table, and updates and maintains the public customer information, public account information, and associated person information corresponding to each loaded customer number to the above customer rating intermediate table.

[0121] S503. The data center determines the qualitative weight data and the quantitative weight data, performs weighted processing on the customer rating intermediate table, and generates a customer rating table.

[0122] More specifically, the data center Figure 4 The message table shown in the figure queries the micro application to obtain the preset customer dimension corresponding table, that is, Figure 4 For example, the message table information includes a plurality of customer numbers and qualitative weight data corresponding to the plurality of customer numbers, and the scores corresponding to the customer numbers in the customer score intermediate table obtained in step S502 are updated according to the qualitative weight data.

[0123] Optionally, the data center passes Figure 4 The customer classification micro application shown determines the customer number that hits the preset conditions, determines the quantitative weight data corresponding to the hit customer number, and adds points to the score corresponding to the customer number based on the quantitative weight data.

[0124] Optionally, after completing the weighted processing, the data center generates a customer level table, that is, Figure 4 The customer classification result information is shown.

[0125] S504. The data center sends the customer level table to the system database.

[0126] S505: The system database generates a rating task.

[0127] More specifically, the system database generates a rating task based on the full customer information and the customer rating table of each customer.

[0128] S506: The system database sends the rating task to the system page.

[0129] More specifically, the system database sends a rating task to the system page, so that after receiving the rating task, the system page performs suspicious verification on the merged event according to the full customer information and the customer rating table, and generates a verification result.

[0130] This embodiment uses a customer dimension corresponding table matching foreign exchange and preset conditions to classify foreign exchange transaction customers, thereby improving the accuracy and reliability of customer classification.

[0131] S313. The system page sends the verification result to the system database.

[0132] S314. When the system database is verified to be correct, it generates a target message and performs a pre-check.

[0133] More specifically, when the system database determines that the verification result indicates that the verification is correct, Figure 4 The suspicious message processing micro application shown will merge events to generate target messages.

[0134] Optionally, the target message is pre-checked for the first time according to a preset check standard to determine whether the relevant information of the suspicious message in the target message is complete, and the relevant information of the incomplete suspicious message is added to obtain a target message with complete information. According to the preset message reporting quantity, the target message is split and processed to obtain multiple sub-target messages, wherein the number of each sub-target message does not exceed the preset message reporting quantity.

[0135] Optionally, by performing a second pre-check on each sub-target message, it is determined whether the reporting format is correct, and a pre-check result is generated.

[0136] S315. The system database sends the pre-verification result to the system page.

[0137] S316. The system page reports the target message when the pre-verification is successful.

[0138] More specifically, the foreign exchange suspicious reporting system also includes a reporting interface generated by the pre-finance management information system. The system page receives the pre-verification result, and when the pre-verification result indicates that the verification is successful, the target message is reported through the message interface. Among them, the message interface is an interface for connecting to the external system that proposes the reporting task.

[0139] In a possible embodiment, the data middle station sends the customer level table, the suspicious event audit results, the classification parameter configuration information, and the analysis model configuration information to the micro-application, so that the micro-application processes according to the respective relevant data, and outputs the customer classification result information, the trial operation result information, and the preset conditions to the data middle station. The data middle station analyzes the suspicious event according to the obtained data, obtains the target message, transmits the target message to the external system for executing the report, so as to report the foreign exchange suspicious transaction message through the external system, and after the report is completed, the report receipt is fed back to the micro-application, so that when the report fails, the micro-application analyzes the report receipt, so that when the report fails, a retransmission instruction is generated according to the receipt, and the retransmission instruction is used to instruct the micro-application to repair the target message, generate repair data, and update the target message according to the repair data, so as to re-report according to the updated target message.

[0140] The data processing method provided by the embodiment of the present application screens out the hit source data that meets the preset conditions through the data middle station, and then generates the to-be-reported events of the current preset period based on multiple hit source data through the system database, and when a suspicious indication is received within the current preset period, the to-be-reported events are merged based on the first historical suspicious event and the second historical suspicious event received subsequently, and a merged event is obtained. When the system page verifies the merged event, a target message is generated, and the target message is reported through the system page after the pre-verification of the target message. The present application realizes the effective reporting of relevant information of suspicious foreign exchange transactions, and enhances the accuracy and reliability of the reported information related to suspicious transactions.

[0141] Optionally, the foreign exchange suspicious reporting system sends the target message through the reporting interface, and receives the message receipt. Among them, five types of directories are used to store data in the embodiment of the present application, such as the directory to be sent, the sending history directory, the error file directory, the interface feedback directory and the log directory. Under the directory to be sent, the sending history directory, the error file directory and the interface feedback directory, there is a token file and a control directory. Different directories have different functions, and they need to be executed and transmitted in a controllable and orderly manner according to the corresponding control targets, and the security and integrity of the data are guaranteed.

[0142] In a possible embodiment, Figure 6 As shown, the batch server is used to obtain data in the batch database through the batch channel, process the data by running the corresponding script, obtain the merged event after the processing is completed, store it in the batch database, and send it to the suspicious message processing micro-application through the batch database, so as to generate the corresponding target message (such as XML file or ZIP file) by merging the event through the JAR package of the suspicious message processing micro-application, and store the target message in the storage server and the business data storage platform respectively, and then call the message interface corresponding to the pre-financial management system to transfer the target message to the corresponding directory to be sent. After the submission is completed, the batch server obtains the message receipt information under the interface feedback directory through the message interface corresponding to the pre-financial management system, and sends the message receipt information to the storage server and the business data storage platform respectively. Among them, the batch database is the system database, that is, the data layer.

[0143] Optionally, during night batching, the batch server obtains the corresponding message receipt information through the storage server or business data storage platform and parses it.

[0144] Figure 7 A schematic diagram of the structure of the data processing device provided in this application, such as Figure 7 As shown, the data processing device 70 provided in this embodiment includes:

[0145] The acquisition module 701 is used to acquire the transaction source data within the current preset period every preset period; determine the corresponding multiple hit source data based on the transaction source data, and the hit source data is the transaction source data that meets the preset conditions;

[0146] Processing module 702, used to generate corresponding events to be reported based on multiple hit source data; based on the suspicious indications received within the current preset period, merge the historical suspicious events with the events to be reported according to the preset merging strategy to obtain a merged event;

[0147] The processing module 702 is further configured to generate a target message according to the merge event; perform pre-verification on the target message, and report the target message when the pre-verification result indicates that the pre-verification of the target message is successful.

[0148] Optionally, the processing module 702 is further configured to determine historical hit source data of the indication based on the suspicious indication; generate a first historical suspicious event within a current preset period according to the historical hit source data;

[0149] Perform a trial operation on the reported event, and obtain the second historical suspicious event within the current preset period according to the trial operation result;

[0150] The event to be reported, the first historical suspicious event and the second historical suspicious event are merged to generate a merged event, where the merged event includes multiple events.

[0151] Optionally, the acquisition module 701 is further configured to acquire the full amount of customer information corresponding to the transaction source data within the current preset period before generating the target message;

[0152] The customer grade table corresponding to the transaction source data is determined according to the full amount of customer information, and the customer grade table includes customer grades corresponding to multiple customer numbers in the current preset period.

[0153] Optionally, the processing module 702 is further used to generate a customer rating intermediate table based on the full amount of customer information;

[0154] Determine the qualitative weight data corresponding to the multiple customer numbers in the transaction source data based on the preset customer dimension corresponding table, and determine the quantitative weight data corresponding to the multiple customer numbers based on the preset conditions corresponding to the multiple hit source data;

[0155] The customer rating intermediate table is weighted according to the qualitative weight data and the quantitative weight data to obtain the weighted customer rating intermediate table and generate a customer grade table.

[0156] Optionally, the processing module 702 is further configured to perform suspicious verification on the merged event based on the customer rating table;

[0157] When there is a suspected verification error, multiple events in the merged event are added or deleted according to the customer level table;

[0158] When the suspicious verification is correct, a message table is generated; based on the message table, a target message is obtained, the target message includes multiple sub-target messages, and the sub-target messages are obtained by splitting the message table according to a preset number.

[0159] Optionally, the processing module 702 is further configured to generate a retransmission instruction when the pre-check result indicates that the target message check fails;

[0160] The repair data corresponding to the target message is obtained based on the retransmission instruction, the target message is updated according to the repair data, and the target message is re-transmitted according to the updated target message.

[0161] The data processing device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be described in detail here.

[0162] Figure 8 This is a schematic diagram of the structure of the electronic device provided in this application. Figure 8As shown, the electronic device 80 provided in this embodiment includes: at least one processor 801 and a memory 802. Optionally, the device 80 also includes a communication component 803. The processor 801, the memory 802 and the communication component 803 are connected via a bus 804.

[0163] In a specific implementation process, at least one processor 801 executes the computer-executable instructions stored in the memory 802, so that at least one processor 801 executes the above method.

[0164] The specific implementation process of the processor 801 can be found in the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

[0165] In the above embodiments, it should be understood that the processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the invention can be directly implemented as a hardware processor, or can be implemented by a combination of hardware and software modules in the processor.

[0166] The memory may include a high-speed memory (Random Access Memory, RAM), and may also include a non-volatile memory (NVM), such as at least one disk storage.

[0167] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of this application is not limited to only one bus or one type of bus.

[0168] The present application also provides a computer program product, including a computer program, which implements the above method when executed by a processor.

[0169] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the above method is implemented.

[0170] The above-mentioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special-purpose computer.

[0171] An exemplary readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (Application Specific Integrated Circuits, referred to as: ASIC). Of course, the processor and the readable storage medium can also exist in the device as discrete components.

[0172] The division of units is only a logical function division, and there may be other divisions in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

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

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

[0175] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.

[0176] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0177] Finally, it should be noted that those skilled in the art will readily conceive of other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present invention is intended to cover any variations, uses or adaptations of the present invention, which follow the general principles of the present invention and include common knowledge or customary technical means in the art not disclosed by the present invention, are not limited to the precise structure described above and shown in the drawings, and may be modified and changed in various ways without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A data processing method, characterized in that: include: Obtain transaction source data within the current preset period at every preset period; Determining a plurality of corresponding hit source data based on the transaction source data, wherein the hit source data is transaction source data that meets a preset condition; Generate corresponding events to be reported based on the multiple hit source data; Based on the suspicious indications received within the current preset period, merging the historical suspicious events with the event to be reported according to a preset merging strategy to obtain a merged event; Generate a target message according to the merge event; The target message is pre-checked, and when the pre-check result indicates that the pre-check of the target message is successful, the target message is reported.

2. The method according to claim 1, characterized in that The historical suspicious events are merged with the events to be reported according to the preset merging strategy to obtain a merged event, which specifically includes: Determining historical hit source data of the indication based on the suspicious indication; generating a first historical suspicious event within a current preset period according to the historical hit source data; Performing a trial operation process on the event to be reported, and obtaining a second historical suspicious event within a current preset period according to the trial operation process result; The event to be reported, the first historical suspicious event, and the second historical suspicious event are merged to generate a merged event, where the merged event includes multiple events.

3. The method according to claim 1 or 2, characterized in that: Also includes: Before generating the target message, obtain the full amount of customer information corresponding to the transaction source data within the current preset period; A customer grade table corresponding to the transaction source data is determined according to the full amount of customer information, wherein the customer grade table includes customer grades corresponding to a plurality of customer numbers in a current preset period.

4. The method according to claim 3, characterized in that Determining the customer level table corresponding to the transaction source data according to the full amount of customer information specifically includes: Generate a customer rating intermediate table based on the full amount of customer information; Determine the qualitative weight data corresponding to the multiple customer numbers in the transaction source data based on the preset customer dimension corresponding table, and determine the quantitative weight data corresponding to the multiple customer numbers according to the preset conditions corresponding to the multiple hit source data; The customer scoring intermediate table is weighted according to the qualitative weight data and the quantitative weight data to obtain a weighted customer scoring intermediate table, and a customer grade table is generated.

5. The method according to claim 3, characterized in that: Generate a target message based on the merge event, including: Performing suspicious verification of the merged event based on the customer rating table; When the verification is suspected to be wrong, adding and deleting multiple events in the merged event according to the customer level table; When the suspicious verification is correct, a message table is generated; based on the message table, the target message is obtained, the target message includes multiple sub-target messages, and the sub-target messages are obtained by splitting the message table according to a preset number.

6. The method according to claim 1, characterized in that Also includes: When the pre-check result indicates that the target message fails to be checked, generating a retransmission instruction; The repair data corresponding to the target message is acquired based on the retransmission instruction, the target message is updated according to the repair data, and the updated target message is retransmitted.

7. A data processing device, characterized in that: include: An acquisition module is used to acquire transaction source data within a current preset period at every preset period; Determining a plurality of corresponding hit source data based on the transaction source data, wherein the hit source data is transaction source data that meets a preset condition; A processing module, configured to generate corresponding events to be reported based on the multiple hit source data; Based on the suspicious indications received within the current preset period, merging the historical suspicious events with the event to be reported according to a preset merging strategy to obtain a merged event; The processing module is further used to generate a target message according to the merge event; The target message is pre-checked according to a preset check standard, and when the pre-check result indicates that the pre-check of the target message is successful, the target message is reported.

8. An electronic device, characterized in that: include: Memory, processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 6 when executed by a processor.

10. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 6 when being executed by a processor.

Images