WO2019001125A1

WO2019001125A1 - Method and device for processing transaction files, storage medium, and computer apparatus

Info

Publication number: WO2019001125A1
Application number: PCT/CN2018/084841
Authority: WO
Inventors: 刘星; 仝西乐; 姜胜文; 蒋波
Original assignee: 平安科技（深圳）有限公司
Priority date: 2017-06-26
Filing date: 2018-04-27
Publication date: 2019-01-03
Also published as: CN107797854B; CN107797854A

Abstract

A method for processing transaction files, comprising: receiving uploaded batch transaction files; creating a corresponding file parsing asynchronous task for each transaction file; and executing each file parsing asynchronous task in parallel, wherein executing each file parsing asynchronous task comprises: obtaining the transaction type of the transaction file; if the transaction type matches a pre-stored transaction type successfully, obtaining a file parsing method corresponding to the transaction type from a database; and storing transaction data obtained by parsing in the database.

Description

Transaction file processing method, device, storage medium and computer device

This application claims the priority of the Chinese Patent Application entitled "Transaction Document Processing Method, Apparatus, Storage Medium, and Computer Equipment", filed on June 26, 2017, filed at the Chinese Patent Office No. 2017104954614, the entire contents of Combined in this application.

Technical field

The present application relates to a transaction finger file processing method, apparatus, storage medium and computer device.

Background technique

The traditional transaction file processing method is to process each transaction file in the order of receiving time of the transaction file, including parsing the received transaction file to obtain transaction data, and using the transaction data.

However, the inventor realized that when the parsing process of a certain file in the same batch of transaction files is abnormal, the conventional such file processing method can only resolve the abnormal problem of the file before parsing the same batch. Other transaction files, and in turn use other transaction data, make the file processing inefficient.

Summary of the invention

According to various embodiments disclosed herein, a transaction file processing method, apparatus, storage medium, and computer device are provided.

A transaction file processing method includes: receiving an uploaded batch transaction file; creating a corresponding file parsing asynchronous task for each of the transaction files; performing each of the file parsing asynchronous tasks in parallel; and executing each of the files Parsing the asynchronous task includes: acquiring a transaction type of the transaction file; if the transaction type matches the pre-stored transaction type, obtaining a file parsing method corresponding to the transaction type in the database; and according to the file parsing method Parsing the transaction file and saving the parsed transaction data to the database.

A transaction file processing device includes: a transaction file receiving module, configured to receive an uploaded batch transaction file; a file parsing asynchronous task creation module, configured to create a corresponding file parsing asynchronous task for each of the transaction files; a task execution module, configured to execute each of the file parsing asynchronous tasks in parallel; the file parsing asynchronous task execution module is configured to acquire a transaction type of the transaction file; if the transaction type matches a pre-stored transaction type, the Obtaining a file parsing method corresponding to the transaction type in the database; and parsing the transaction file according to the file parsing method, and saving the parsed transaction data to a database.

One or more non-transitory computer readable storage mediums storing computer readable instructions, when executed by one or more processors, cause one or more processors to perform the steps of: receiving an uploaded batch Transaction file; creating a corresponding file parsing asynchronous task for each of the transaction files; executing each of the file parsing asynchronous tasks in parallel; performing each of the parsing of the asynchronous tasks, including: acquiring a transaction of the transaction file a type; if the transaction type matches the pre-stored transaction type, obtaining a file parsing method corresponding to the transaction type in the database; and parsing the transaction file according to the file parsing method, and parsing the obtained transaction data Save to the database.

A computer device comprising a memory and one or more processors having stored therein computer readable instructions, the computer readable instructions being executable by the processor to cause the one or more processors to execute The following steps: receiving the uploaded bulk transaction file; creating a corresponding file parsing asynchronous task for each of the transaction files; performing each of the file parsing asynchronous tasks in parallel; and executing each of the file parsing asynchronous tasks, including: Obtaining a transaction type of the transaction file; if the transaction type is successfully matched with the pre-stored transaction type, obtaining a file parsing method corresponding to the transaction type in a database; and parsing the transaction file according to the file parsing method, The parsed transaction data is saved to the database.

Details of one or more embodiments of the present application are set forth in the accompanying drawings and description below. Other features and advantages of the present invention will be apparent from the description, drawings and claims.

DRAWINGS

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present application, and other drawings can be obtained according to the drawings without any creative work for those skilled in the art.

1 is an application environment diagram of a transaction file processing method in accordance with one or more embodiments.

2 is a diagram showing the internal structure of a server in accordance with one or more embodiments.

3 is a flow diagram of a method of processing a transaction file in accordance with one or more embodiments.

4 is a flow diagram of a method of verifying a transaction file in accordance with still another embodiment.

FIG. 5 is a flow diagram of a method of performing transaction data in accordance with one or more embodiments.

FIG. 6 is a block diagram showing the structure of a transaction file processing apparatus in accordance with one or more embodiments.

Detailed ways

In order to make the technical solutions and advantages of the present application more clear, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.

The transaction file processing method provided by the embodiment of the present application can be applied to the environment as shown in FIG. 1. Referring to FIG. 1, the server 102 can receive the bulk transaction file uploaded by the terminal 104 and process the transaction file. Specifically, the server 102 communicates with the terminal 104 through the network, the server 102 receives the uploaded batch transaction file, creates a corresponding file parsing asynchronous task for each of the transaction files, and executes each of the file parsing asynchronous tasks in parallel, Executing each of the file parsing asynchronous tasks includes: acquiring a transaction type of the transaction file, and if the transaction type matches the pre-stored transaction type, obtaining a file parsing method corresponding to the transaction type in the database, according to The file parsing method parses the transaction file and saves the parsed transaction data to a database or the like. Terminals herein include, but are not limited to, various personal computers, notebook computers, smart phones, tablets, portable wearable devices, and the like.

In one embodiment, as shown in FIG. 2, there is also provided a server including a processor connected through a system bus, a non-volatile storage medium, an internal memory, a network connection port, and non-volatile storage. An operating system and computer readable instructions are stored in the medium, and the computer readable instructions are used to implement a transaction file processing method applicable to the terminal provided in the embodiments of the present application. The non-volatile storage medium can be a non-transitory computer readable storage medium. This processor is used to improve computing and control capabilities and support the operation of the entire server. The internal memory is used to provide an environment for the operation of operating systems and computer readable instructions in a non-volatile storage medium. The network interface is used for network communication with the terminal. It will be understood by those skilled in the art that the structure shown in FIG. 2 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the server to which the solution of the present application is applied. Specifically, the server may include a ratio. More or fewer components are shown in the figures, or some components are combined, or have different component arrangements.

In one embodiment, as shown in FIG. 3, a transaction file processing method is provided, which is applied to the server as shown in FIG. 2, and includes:

Step 302: Receive an uploaded batch transaction file.

The transaction file is a data file formed by the user performing various operations in the commodity trading system, such as applying for registration of an account, modifying account information, and purchasing goods. Transaction documents are distinguished by transaction type, such as account opening documents, account modification documents, purchase documents, and subscription documents. The server can receive bulk transaction files uploaded by the user through the commodity trading system.

Each transaction file corresponds to a transaction type, and the transaction file processing method provided in this embodiment is based on a plurality of transaction file processing methods.

Step 304: Create a corresponding file parsing asynchronous task for each transaction file.

An asynchronous task refers to a task that executes a subsequent task without waiting for the current task to finish executing, but directly performs a subsequent operation, that is, an asynchronous task is used to execute multiple tasks at the same time.

After the bulk transaction file is received, the server creates a corresponding file parsing asynchronous task for each received transaction file, which is used to quickly parse each transaction file.

In step 306, each file parsing asynchronous task is executed in parallel.

After the file parsing asynchronous task is created, the file parsing asynchronous task is created according to the number of file parsing asynchronous tasks and the preset maximum task processing number. When the number of file parsing asynchronous tasks does not exceed the preset maximum task processing number, the created file parsing asynchronous task can be directly assigned to the server that currently creates the file parsing asynchronous task; when the number of file parsing asynchronous tasks is greater than the preset maximum When the number of tasks is processed, the first ratio of the number of file parsing asynchronous tasks to the preset maximum number of task processing may be calculated, and the first ratio is rounded up to obtain a second ratio, and then the file parsing asynchronous task is assigned to the number of files. For the second ratio server, for example, the number of file parsing asynchronous tasks is 18 (that is, the number of received batch transaction files is 18), and the preset maximum number of task processing is 7, the asynchronous task is assigned to 3 servers are executed, and the number of file parsing asynchronous tasks allocated by the three servers can be 7, 7, 4 (that is, according to the preset maximum number of task processing), or it can be 6, 6, and 6 (ie, Average allocation) and so on.

File parsing After the asynchronous task assignment is completed, all created file parsing asynchronous tasks are executed in parallel. The steps to perform each file parsing asynchronous task, including:

Step 3062: Obtain a transaction type of the transaction file.

Transaction documents are divided by transaction type. For example, the transaction type may be, but is not limited to, an account opening document, an account modification file, a purchase document, and a subscription document. The transaction file can be directly parsed to obtain the transaction type, or the transaction file can be parsed first to obtain the file source (such as PC-side system, WeChat platform, etc.), and then the transaction type of the transaction file is obtained according to the file source.

Step 3064: If the transaction type matches the pre-stored transaction type, the file parsing method corresponding to the transaction type is obtained in the database.

The file parsing method is a method pre-existing in the database for parsing files. In this embodiment, the transaction type of the received transaction file needs to be matched with the pre-stored transaction type to filter out the misplaced file of the terminal. If the matching is successful, the file parsing method corresponding to the transaction type is obtained in the database, that is, the file parsing method is pre-stored in the database, so that the template of the subsequent transaction file is changed, and the corresponding new file parsing method can directly replace the database. The original file parsing method in the file reduces operations such as connection tests that are stored in the program in the program.

Step 3066, parsing the transaction file according to the file parsing method, and saving the parsed transaction data to the database.

After the server parses the transaction file according to the parsing method corresponding to the transaction file to obtain the transaction data, the transaction data is saved to the database for subsequent use.

Since each transaction file of the same batch corresponds to a file parsing asynchronous task, each file parsing asynchronous task obtains the corresponding file parsing method directly from the database according to the transaction type of the respective transaction file, thereby realizing parallel parsing of the transaction file and improving The processing efficiency of the transaction file.

In one embodiment, before step 304, the method further includes verifying the security of the bulk transaction file; if the bulk transaction file is verified to be secure, the step of creating a corresponding file parsing asynchronous task for each transaction file is entered.

The security identifier of each transaction file can be obtained, and if the security identifier is consistent with the preset security identifier, the transaction file is verified to be secure. For example, the corresponding field of the security identifier is “safety signs”, the default value of “safety signs” is “DEAL-R”, and the value corresponding to “safety signs” in the received transaction file is also “DEAL-R”. ", then the transaction file is verified to be secure. In this embodiment, the security of the transaction file is ensured by adding security verification steps to the received batch transaction file.

In one embodiment, as shown in FIG. 4, before the file parsing method corresponding to the transaction type is obtained in the database, a file verification method of the transaction file is further provided, and the method further includes:

Step 402: If the transaction type matches the pre-stored transaction type, the file verification method corresponding to the transaction type is obtained in the database.

File verification methods include physical and logical verification of files. The physical check is used to verify the encoding of the file and the integrity of the data. The commonly used data integrity check can be a Cyclic Redundancy Check (CRC), including CRC8, CRC16 and CRC32, and a secure hash algorithm. (Secure Hash Algorithm, SHA, including SHA1, SHA256, SHA384, SHA512) or Message Digest Algorithm (including MD2, MD4, MD5), etc.; logic check is used to check the logic of the data, such as the same field. Whether the repeated input is consistent, whether the sequential execution order of the data conforms to the preset logic, and the like.

The file verification method corresponding to the pre-stored transaction type is pre-stored in the database, and after obtaining the transaction type of the transaction file, the corresponding file verification method can be easily found.

Step 404, verifying the transaction file according to the file verification method.

The transaction file is verified by the file verification method corresponding to the transaction file type, and if the verification is passed, the subsequent step of obtaining the file parsing corresponding to the transaction type in the database is entered; if the verification fails, the processing of the transaction file is terminated. .

By verifying the received transaction file, the illegal file is filtered out, and the data integrity of the transaction file is guaranteed.

In one embodiment, as shown in FIG. 5, after step 306, the method further includes:

Step 502: Determine whether the transaction type of the batch transaction file is the same transaction type. If yes, proceed to step 504, otherwise proceed to step 508.

Step 504, creating a corresponding transaction request asynchronous task for each transaction file.

A transaction request asynchronous task is an execution request task of transaction data in a transaction file. When the transaction types of the same batch of transaction files received are the same, such as opening an account file, the task efficiency can be improved by creating multiple task threads.

Step 506, executing each transaction request asynchronous task in parallel.

Similar to step 306, after the transaction request asynchronous task is created, the created transaction request asynchronous task can be allocated according to the number of the transaction request asynchronous task and the preset maximum task processing number, and then all the created transaction request asynchronous tasks are executed in parallel. Execute each transaction to request an asynchronous task, including:

Step 5062: Obtain transaction data corresponding to the transaction file from the database.

After the transaction file is parsed, the corresponding parsed data is stored in the database, so when the transaction data needs to be used, it can be directly obtained from the database. The transaction data is data for the user to perform arbitrary operations on the transaction system, including but not limited to the login account of the transaction system, the login password, and the purchased product information.

At step 5064, transaction data is executed.

After the transaction data corresponding to the transaction file is obtained in the database, the transaction data is executed in the preset logical order of the transaction type, thereby completing the entire transaction application. For example, for a fund subscription document, the server obtains the fund type and the number of funds selected by the user in the fund subscription application form, and obtains the fund unit price, handling fee, discount, etc. corresponding to the fund type in the fund information table, according to The preset calculation rule calculates the fee that the user needs to pay, obtains the payment information of the user for the fee, and generates a corresponding fund subscription order, thereby realizing the complete process of the fund subscription.

Step 508: Acquire corresponding transaction data from the database in sequence according to a preset transaction logic sequence, and execute the transaction data.

The preset transaction logic is set according to the pre-stored transaction type, such as processing the account opening file, the account modification file, the purchase document and the subscription file in turn. This can be achieved by setting different processing priorities for transaction files of different transaction types.

By judging whether the transaction type of the same batch of transaction files is the same or not, if the same, creating a corresponding transaction request asynchronous task for each transaction file, and then executing each transaction request asynchronous task in parallel; if not, then The batch transaction file creates a transaction request asynchronous task and executes the transaction request asynchronous task, including: obtaining the corresponding transaction data from the database in turn according to the preset transaction logic order, executing the transaction data, and improving the execution efficiency of the transaction data. At the same time, the parsing of each transaction file and the execution process of the transaction data are separated, which reduces the dependence of the use and execution of the transaction data on the parsing of the transaction file, and improves the stability of the use and execution functions of the transaction data.

The above embodiment is for a batch transaction to be processed for a single batch (here, the batch transaction to be processed refers to a batch transaction in which the batch transaction file has been parsed and stored in the database but has not been executed according to the preset execution logic). In other embodiments, if there are two or more batches of batch transactions to be processed, a corresponding transaction request asynchronous task is created for each batch of batch transactions to be processed, and each transaction is executed in parallel. Apply for an asynchronous task. Executing an asynchronous task for each transaction, including: determining whether the transaction type of the batch transaction file in a batch is the same transaction type, and if so, creating a corresponding transaction request for each batch transaction file in the same batch. Subtask, then execute each transaction request asynchronous subtask in parallel, and execute each transaction request asynchronous subtask, including: obtaining transaction data corresponding to the transaction file from the database, executing the transaction data; if not, according to the preset The transaction logic sequence sequentially obtains the corresponding transaction data from the database and executes the transaction data.

In one of the embodiments, before step 502, it further comprises detecting whether the batch transaction file has been parsed, and if so, entering the step of determining whether the transaction type of the bulk transaction file is of the same transaction type.

It can traverse the file processing status corresponding to the batch number in the file list (including batch number, file encoding, transaction type, file source, file status, initial status of the file status), if the file processing status If the analysis is completed, the batch transaction file is parsed.

It should be understood that although the various steps in the flowcharts of FIGS. 3-5 are sequentially displayed as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Except as explicitly stated herein, the execution of these steps is not strictly limited, and the steps may be performed in other orders. Moreover, at least some of the steps in FIGS. 3-5 may include a plurality of sub-steps or stages, which are not necessarily performed at the same time, but may be executed at different times, these sub-steps or stages The order of execution is not necessarily performed sequentially, but may be performed alternately or alternately with at least a portion of other steps or sub-steps or stages of other steps.

In one embodiment, as shown in FIG. 6, a transaction file processing apparatus is provided, including: a transaction file receiving module 602, configured to receive an uploaded bulk transaction file; and a file parsing asynchronous task creation module 604, configured to Each transaction file creates a corresponding file parsing asynchronous task; a file parsing asynchronous task execution module 606 is configured to execute each file parsing asynchronous task in parallel; and a file parsing asynchronous task executing module 606 is configured to obtain a transaction type of the transaction file; If the type matches the pre-stored transaction type successfully, the file parsing method corresponding to the transaction type is obtained in the database; the transaction file is parsed according to the file parsing method, and the parsed transaction data is saved in the database.

In one embodiment, the file parsing asynchronous task execution module 606 is further configured to verify the security of the bulk transaction file; and if the bulk transaction file is verified to be secure, enter the step of creating a corresponding file parsing asynchronous task for each transaction file. .

In one embodiment, the file parsing asynchronous task execution module 606 is further configured to obtain a file verification method corresponding to the transaction type in the database; verify the transaction file according to the file verification method; and if the verification passes, Enter the step of obtaining a file parsing method corresponding to the transaction type in the database.

In one embodiment, the apparatus further includes a transaction type determining module, configured to determine whether the transaction type of the batch transaction file is the same transaction type; if yes, create a corresponding transaction request asynchronous task for each transaction file; Each transaction applies for an asynchronous task, and each transaction requests an asynchronous task, including: obtaining transaction data corresponding to the transaction file from the database; executing the transaction data; and if not, acquiring the transaction data in order according to a preset business logic sequence Corresponding transaction data, executing transaction data.

In one embodiment, the transaction type judging module is further configured to detect whether the bulk transaction file is parsed; and if so, enter a step of determining whether the transaction type of the bulk transaction file is the same transaction type.

For the specific definition of the transaction file processing device, reference may be made to the above description of the transaction file processing method, and details are not described herein again. Each of the above-described transaction file processing devices may be implemented in whole or in part by software, hardware, and combinations thereof. Each of the above modules may be embedded in or independent of the processor in the computer device, or may be stored in a memory in the computer device in a software form, so that the processor invokes the operations corresponding to the above modules.

One or more non-transitory computer readable storage mediums storing computer readable instructions, when executed by one or more processors, cause one or more processors to perform the steps of: receiving an uploaded batch Transaction file; create corresponding file parsing asynchronous task for each transaction file; execute each file parsing asynchronous task in parallel; execute each file parsing asynchronous task, including: obtaining the transaction type of the transaction file; if the transaction type matches the pre-stored transaction type If successful, the file parsing method corresponding to the transaction type is obtained in the database; and the transaction file is parsed according to the file parsing method, and the parsed transaction data is saved in the database.

In one of the embodiments, when the computer readable instructions are executed by the processor, before performing the step of creating a corresponding file parsing asynchronous task for each transaction file, the method further comprises the step of: verifying the security of the bulk transaction file; If the bulk transaction file is verified to be secure, then the step of creating a corresponding file parsing asynchronous task for each transaction file is entered.

In one embodiment, when the computer readable instructions are executed by the processor, before performing the step of obtaining a file parsing method corresponding to the transaction type in the database, the method further comprises the step of: obtaining, in the database, corresponding to the transaction type The file verification method; the transaction file is verified according to the file verification method; and if the verification is passed, the file parsing method corresponding to the transaction type is obtained in the database.

In one embodiment, the computer readable instructions are further executed by the processor to: determine whether the transaction type of the bulk transaction file is the same transaction type; if so, create a corresponding transaction request asynchronous task for each transaction file Parallel execution of each transaction request asynchronous task, executing each transaction request asynchronous task, including: obtaining transaction data corresponding to the transaction file from the database; executing the transaction data; and if not, proceeding according to the preset transaction logic order The corresponding transaction data is obtained in the database, and the transaction data is executed.

In one embodiment, when the computer readable instructions are executed by the processor, before performing the step of determining whether the transaction type of the batch transaction file is the same transaction type, the method further comprises the step of: detecting whether the batch transaction file is parsed; And if so, enter the step of determining whether the transaction type of the bulk transaction file is the same transaction type.

A computer device comprising a memory and one or more processors, the memory storing computer readable instructions, the computer readable instructions being executed by the processor, causing the one or more processors to perform the step of: receiving the uploaded bulk transaction File; create a corresponding file parsing asynchronous task for each transaction file; execute each file parsing asynchronous task in parallel; execute each file parsing asynchronous task, including: obtaining the transaction type of the transaction file; if the transaction type matches the pre-stored transaction type successfully , the file parsing method corresponding to the transaction type is obtained in the database; and the transaction file is parsed according to the file parsing method, and the parsed transaction data is saved in the database.

In one of the embodiments, when the processor executes the computer readable instructions, before performing the step of creating a corresponding file parsing asynchronous task for each transaction file, the method further comprises the step of: verifying the security of the bulk transaction file; If the batch transaction file is verified to be secure, then the step of creating a corresponding file parsing asynchronous task for each transaction file is entered.

In one embodiment, when the processor executes the computer readable instructions, before executing the file parsing method corresponding to the transaction type in the database, the method further includes: performing the following steps: obtaining a file check corresponding to the transaction type in the database Method; verifying the transaction file according to the file verification method; if the verification is passed, entering the step of obtaining a file parsing method corresponding to the transaction type in the database.

In one embodiment, the processor executes the computer readable instructions to: determine whether the transaction type of the batch transaction file is the same transaction type; if so, create a corresponding transaction request asynchronous task for each transaction file; Execute each transaction request asynchronous task in parallel, execute each transaction request asynchronous task, including: obtaining transaction data corresponding to the transaction file from the database; executing the transaction data; and if not, proceeding from the database according to the preset transaction logic order Obtain the corresponding transaction data and execute the transaction data.

In one embodiment, when the processor executes the computer readable instructions, before performing the step of determining whether the transaction type of the batch transaction file is the same transaction type, the method further comprises the step of: detecting whether the batch transaction file is parsed; and If so, the step of determining whether the transaction type of the bulk transaction file is the same transaction type is entered.

One of ordinary skill in the art can understand that all or part of the process of implementing the above embodiments can be completed by computer readable instructions, which can be stored in a non-volatile computer. The readable storage medium, which when executed, may include the flow of an embodiment of the methods as described above. Any reference to a memory, storage, database, or other medium used in the various embodiments provided herein can include non-volatile and/or volatile memory. Non-volatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of formats, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronization chain. Synchlink DRAM (SLDRAM), Memory Bus (Rambus) Direct RAM (RDRAM), Direct Memory Bus Dynamic RAM (DRDRAM), and Memory Bus Dynamic RAM (RDRAM).

The technical features of the above-described embodiments may be arbitrarily combined. For the sake of brevity of description, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction between the combinations of these technical features, All should be considered as the scope of this manual.

The above-mentioned embodiments are merely illustrative of several embodiments of the present application, and the description thereof is more specific and detailed, but is not to be construed as limiting the scope of the invention. It should be noted that a number of variations and modifications may be made by those skilled in the art without departing from the spirit and scope of the present application. Therefore, the scope of the invention should be determined by the appended claims.

Claims

A transaction file processing method, comprising:

Receive uploaded bulk transaction files;

Creating a corresponding file parsing asynchronous task for each of the transaction files;

Executing each of the file parsing asynchronous tasks in parallel;

The performing each of the file parsing asynchronous tasks includes:

Obtaining the transaction type of the transaction file;

If the transaction type is successfully matched with the pre-stored transaction type, obtaining a file parsing method corresponding to the transaction type in the database; and

The transaction file is parsed according to the file parsing method, and the parsed transaction data is saved in a database.
The method according to claim 1, wherein before the creating a corresponding file parsing asynchronous task for each of the transaction files, the method further comprises:

Verifying the security of the bulk transaction file; and

If the batch transaction file is verified to be secure, a step of creating a corresponding file parsing asynchronous task for each of the transaction files is entered.
The method according to claim 1, wherein before the obtaining the file parsing method corresponding to the transaction type in the database, the method further comprises:

Obtaining a file verification method corresponding to the transaction type in a database;

Verifying the transaction file according to the file verification method; and

If the verification passes, the process proceeds to the step of obtaining a file parsing method corresponding to the transaction type in the database.
The method of claim 1 further comprising:

Determining whether the transaction type of the batch transaction file is the same transaction type;

If yes, create a corresponding transaction request asynchronous task for each transaction file; execute each of the transaction request asynchronous tasks in parallel, and execute each of the transaction request asynchronous tasks, including: obtaining from the database Transaction data corresponding to the transaction file; executing the transaction data; and

If not, the corresponding transaction data is sequentially acquired from the database according to a preset business logic sequence, and the transaction data is executed.
The method according to claim 4, further comprising: before determining whether the transaction type of the batch transaction file is the same transaction type, further comprising:

Detecting whether the batch transaction file is parsed; and

If yes, a step is entered to determine whether the transaction type of the bulk transaction file is the same transaction type.
A transaction file processing device comprising:

a transaction file receiving module, configured to receive the uploaded batch transaction file;

a file parsing asynchronous task creation module, configured to create a corresponding file parsing asynchronous task for each of the transaction files; and

a file parsing asynchronous task execution module, configured to execute each of the file parsing asynchronous tasks in parallel;

The file parsing asynchronous task execution module is configured to obtain a transaction type of the transaction file; if the transaction type matches the pre-stored transaction type, the file parsing method corresponding to the transaction type is obtained in the database; The file parsing method parses the transaction file and saves the parsed transaction data to a database.
The device according to claim 6, wherein the file parsing asynchronous task creation module is further configured to verify security of the bulk transaction file; and if the bulk transaction file is verified to be secure, enter each for each The transaction file creates a step of parsing an asynchronous task for the corresponding file.
The apparatus according to claim 6, wherein the file parsing asynchronous task execution module is further configured to acquire a file verification method corresponding to the transaction type in a database; and verify the location according to the file verification method. Transmitting the transaction file; and if the verification is passed, entering the step of obtaining a file parsing method corresponding to the transaction type in the database.
The device according to claim 6, wherein the device further comprises a transaction type judging module, configured to determine whether the transaction type of the bulk transaction file is the same transaction type; if yes, create for each transaction file Corresponding transaction application asynchronous task; executing each of the transaction request asynchronous tasks in parallel, and executing each of the transaction request asynchronous tasks comprises: obtaining transaction data corresponding to the transaction file from a database; Executing the transaction data; and if not, acquiring corresponding transaction data from the database in sequence according to a preset business logic sequence, and executing the transaction data.
The device according to claim 9, wherein the transaction type judging module is further configured to detect whether the batch transaction file is parsed; and if so, enter whether the transaction type of the bulk transaction file is the same The steps for the transaction type.
One or more non-transitory computer readable storage mediums storing computer readable instructions, when executed by one or more processors, cause the one or more processors to perform the following steps:

Receive uploaded bulk transaction files;

Creating a corresponding file parsing asynchronous task for each of the transaction files;

Executing each of the file parsing asynchronous tasks in parallel;

The performing each of the file parsing asynchronous tasks includes:

Obtaining the transaction type of the transaction file;

If the transaction type is successfully matched with the pre-stored transaction type, obtaining a file parsing method corresponding to the transaction type in the database; and

The transaction file is parsed according to the file parsing method, and the parsed transaction data is saved in a database.
The storage medium of claim 11 wherein said computer readable instructions are executed by said processor, said step of creating a corresponding file parsing asynchronous task for each of said transaction files executed Previously, it also included the following steps:

Verifying the security of the bulk transaction file; and

If the batch transaction file is verified to be secure, a step of creating a corresponding file parsing asynchronous task for each of the transaction files is entered.
A storage medium according to claim 11, wherein when said computer readable instructions are executed by said processor, said step of obtaining said file parsing method corresponding to said transaction type in said database is executed Previously, it also included the following steps:

Obtaining a file verification method corresponding to the transaction type in a database;

Verifying the transaction file according to the file verification method; and

If the verification passes, the process proceeds to the step of obtaining a file parsing method corresponding to the transaction type in the database.
The storage medium of claim 11 wherein said computer readable instructions, when executed by said processor, further perform the following steps:

Determining whether the transaction type of the batch transaction file is the same transaction type;

If yes, create a corresponding transaction request asynchronous task for each transaction file; execute each of the transaction request asynchronous tasks in parallel, and execute each of the transaction request asynchronous tasks, including: obtaining from the database Transaction data corresponding to the transaction file; executing the transaction data; and

If not, the corresponding transaction data is sequentially acquired from the database according to a preset business logic sequence, and the transaction data is executed.
The storage medium according to claim 14, wherein when said computer readable instructions are executed by said processor, said at said execution determines whether said transaction type of said bulk transaction file is of the same transaction type Before the step, it also includes the following steps:

Detecting whether the batch transaction file is parsed; and

If yes, a step is entered to determine whether the transaction type of the bulk transaction file is the same transaction type.
A computer device comprising a memory and one or more processors having stored therein computer readable instructions, the computer readable instructions being executed by the one or more processors to cause the one or more The processors perform the following steps:

Receive uploaded bulk transaction files;

Creating a corresponding file parsing asynchronous task for each of the transaction files;

Executing each of the file parsing asynchronous tasks in parallel;

The performing each of the file parsing asynchronous tasks includes:

Obtaining the transaction type of the transaction file;

If the transaction type is successfully matched with the pre-stored transaction type, obtaining a file parsing method corresponding to the transaction type in the database; and

The transaction file is parsed according to the file parsing method, and the parsed transaction data is saved in a database.
A computer apparatus according to claim 16 wherein said processor executes said computer readable instructions prior to said step of creating said corresponding file parsing asynchronous task for each of said transaction files Also includes the following steps:

Verifying the security of the bulk transaction file; and

If the batch transaction file is verified to be secure, a step of creating a corresponding file parsing asynchronous task for each of the transaction files is entered.
A computer apparatus according to claim 16, wherein said processor executes said computer readable instructions prior to said step of obtaining said file parsing method corresponding to said transaction type in said database Also includes the following steps:

Obtaining a file verification method corresponding to the transaction type in a database;

Verifying the transaction file according to the file verification method; and

If the verification passes, the process proceeds to the step of obtaining a file parsing method corresponding to the transaction type in the database.
The computer apparatus according to claim 16, wherein said processor further performs the following steps when said computer readable instructions are executed:

Determining whether the transaction type of the batch transaction file is the same transaction type;

If yes, create a corresponding transaction request asynchronous task for each transaction file; execute each of the transaction request asynchronous tasks in parallel, and execute each of the transaction request asynchronous tasks, including: obtaining from the database Transaction data corresponding to the transaction file; executing the transaction data; and

If not, the corresponding transaction data is sequentially acquired from the database according to a preset business logic sequence, and the transaction data is executed.
The computer apparatus according to claim 19, wherein said step of determining whether said transaction type of said bulk transaction file is the same transaction type is performed when said processor executes said computer readable instruction Previously, it also included the following steps:

Detecting whether the batch transaction file is parsed; and

If yes, a step is entered to determine whether the transaction type of the bulk transaction file is the same transaction type.