Batch business processing method and system

Abstract

This application provides a batch business processing method and system that can be used in the financial field. The method includes: extracting the business processing data of the batch business to be processed by key fields to obtain multiple discrete data of different processing nodes; setting a task identifier for each discrete data, and obtaining a discrete task based on each discrete data and the corresponding task identifier; repeatedly executing the steps of sending each discrete task to the corresponding business processing thread according to the task identifier, performing business processing through the business processing thread, and updating the task identifier after the business processing is completed until all discrete task business processing is completed. This application can improve the efficiency of batch business processing.

Description

Technical Field

[0001] The present application relates to the technical field of batch business processing, particularly to the financial field, and more particularly to a batch business processing method and system. Background Art

[0002] Batch agent services are a key model for centralized business processing at banks and other financial institutions. Existing batch agent services typically utilize online compressed messages or signed, encrypted files for both delivery and return, enabling centralized interaction between banks and clients. Banks internally orchestrate and process business data in a timed, near-real-time manner, enabling centralized and unified business processing. To improve business processing timeliness, the system typically splits and processes data by file + record group. This increases the degree of parallelism in business processing and improves the overall timeliness of the batch system.

[0003] When business data is evenly distributed, system processing performance can be effectively improved. However, if a large number of interactive applications are involved (such as social security payments), business processing timeliness will be greatly reduced. The number of concurrent threads cannot solve the problem of business processing timeliness, resulting in significant differences in the business processing experience for payments. In addition, controlling the order of business processing through sessions and dependencies between previous and next items lacks flexibility, which can easily lead to overall business processing being blocked due to slowness in a single link, greatly affecting the business experience of agent batch processing. Summary of the Invention

[0004] One object of the present application is to provide a batch business processing method to improve the efficiency of batch business processing. Another object of the present application is to provide a batch business processing system. Another object of the present application is to provide a computer device. Another object of the present application is to provide a readable medium.

[0005] To achieve the above objectives, the present application discloses a batch service processing method, including:

[0006] Extract key fields from the business processing data of batch business to obtain multiple discrete data of different processing nodes;

[0007] Setting a task identifier for each discrete data, and obtaining a discrete task according to each discrete data and the corresponding task identifier;

[0008] Repeat the steps of sending each discrete task to a corresponding business processing thread according to the task identifier, performing business processing through the business processing thread, and updating the task identifier after the business processing is completed until all discrete task business processing is completed.

[0009] Preferably, the step of extracting the business processing data of the batch business to be processed by key fields to obtain a plurality of discrete data of different processing nodes specifically includes:

[0010] Extracting the business processing data according to the first key field to obtain business processing data;

[0011] Extracting the business processing data according to the second key field to obtain data to be checked;

[0012] Extracting the business processing data according to the third key field to obtain a summary record;

[0013] The business processing data is extracted according to the fourth key field to obtain a detailed record.

[0014] Preferably, sending each discrete task to a corresponding business processing thread according to the task identifier, performing business processing through the business processing thread, and updating the task identifier after the business processing is completed specifically includes:

[0015] Determine the next processing node for processing the discrete task according to the task identifier as the current node;

[0016] Sending the discrete task to the target business processing thread corresponding to the current node, and performing business processing through the target business processing thread;

[0017] After the business processing is completed, the task identifier is updated to the task identifier of the task completed by the current node.

[0018] Preferably, the processing nodes include a business acceptance node, a data inspection node, a summary debit processing node, a detail processing node, a summary credit processing node and a data return node.

[0019] Preferably, when the task identifier is a pending business acceptance identifier, sending each discrete task to a corresponding business processing thread according to the task identifier, performing business processing through the business processing thread, and updating the task identifier after the business processing is completed specifically includes:

[0020] The business acceptance discrete task formed according to the business processing data and the pending business acceptance identifier is sent to the business processing thread corresponding to the business acceptance node for business processing. After the business processing is completed, the pending business acceptance identifier is updated to a business accepted identifier.

[0021] Preferably, when the task identifier is a business accepted identifier, sending each discrete task to a corresponding business processing thread according to the task identifier, performing business processing through the business processing thread, and updating the task identifier after the business processing is completed specifically includes:

[0022] The data inspection task formed according to the data to be inspected and the business accepted flag is sent to the business processing thread corresponding to the data inspection node for business processing. After the business processing is completed, the business accepted flag is updated to the data inspection passed flag.

[0023] Preferably, when the task identifier is a data check pass identifier, sending each discrete task to a corresponding business processing thread according to the task identifier, performing business processing through the business processing thread, and updating the task identifier after the business processing is completed specifically includes:

[0024] The summary borrowing processing task formed according to the summary record and the data check pass identifier is sent to the business processing thread corresponding to the summary borrowing processing node for business processing. After the business processing is completed, the data check pass identifier is updated to the summary borrowing processing completion identifier.

[0025] Preferably, when the task identifier is a data check pass identifier, sending each discrete task to a corresponding business processing thread according to the task identifier, performing business processing through the business processing thread, and updating the task identifier after the business processing is completed specifically includes:

[0026] The detail processing task formed according to the detail record and the data check pass identifier is sent to the business processing thread corresponding to the detail party processing node for business processing. After the business processing is completed, the data check pass identifier is updated to the detail party processing completion identifier.

[0027] Preferably, when the task identifier of the summary borrowing processing task is a summary borrowing processing completion identifier, and the task identifier of the detail processing task is a detail processing completion identifier, sending each discrete task to a corresponding business processing thread according to the task identifier, performing business processing through the business processing thread, and updating the task identifier after the business processing is completed specifically includes:

[0028] The summary loan processing task formed according to the summary record, the detailed record and the corresponding identifier is sent to the business processing thread corresponding to the summary loan processing node for business processing. After the business processing is completed, the summary debit processing completion identifier and the detailed party processing completion identifier are updated to the summary loan processing completion identifier.

[0029] Preferably, when the task identifier of the aggregate loan processing task is a aggregate loan processing completion identifier, sending each discrete task to a corresponding business processing thread according to the task identifier, performing business processing through the business processing thread, and updating the task identifier after the business processing is completed specifically includes:

[0030] The data return task formed according to the summary record, the detailed record and the summary loan processing completion mark is sent to the business processing thread corresponding to the data return node for business processing. After the business processing is completed, the summary loan processing completion mark is updated to the business processing completion mark, and all discrete task business processing is completed.

[0031] This application also discloses a batch business processing system, including:

[0032] The data discretization module is used to extract the key fields of the business processing data of the batch business to be processed to obtain multiple discrete data of different processing nodes;

[0033] A discrete task module is used to set a task identifier for each discrete data and obtain a discrete task according to each discrete data and the corresponding task identifier;

[0034] The task processing module is used to repeatedly execute the steps of sending each discrete task to the corresponding business processing thread according to the task identifier, performing business processing through the business processing thread, and updating the task identifier after the business processing is completed until all discrete task business processing is completed.

[0035] The present application also discloses a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor.

[0036] When the processor executes the program, the method described above is implemented.

[0037] The present application also discloses a computer-readable medium having a computer program stored thereon.

[0038] When the program is executed by a processor, the above-mentioned method is implemented.

[0039] The batch business processing method of the present application extracts the business processing data of the batch business to be processed by key fields to obtain multiple discrete data of different processing nodes, sets a task identifier for each discrete data, obtains a discrete task according to each discrete data and the corresponding task identifier, repeatedly executes the steps of sending each discrete task to the corresponding business processing thread according to the task identifier, performing business processing through the business processing thread, and updating the task identifier after the business processing is completed until all discrete task business processing is completed. Thus, the present application integrates and splits the business links of the batch proxy business to obtain multiple processing nodes, and determines the discrete data corresponding to different processing nodes, performs business processing on different discrete data respectively through the business processing threads of different processing nodes, and sets task identifiers for the discrete data to form discrete tasks, and controls the processing order of discrete tasks through task identifiers to ensure the correct processing of batch business. Thus, large batch business can be divided into discrete tasks and assigned to different business threads for processing, preventing the problem of slow batch business processing due to processor performance limitations when a single thread is processed, realizing peak shaving and valley filling of batch business processing, reducing the system pressure for processing batch business, and improving the processing efficiency of batch business to be processed. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0041] Figure 1 A flowchart showing a specific embodiment of the batch business processing method of the present application;

[0042] Figure 2 A flowchart showing a specific embodiment S100 of the batch business processing method of the present application is shown;

[0043] Figure 3 A schematic diagram showing a comparison between a specific embodiment of the batch business processing method of the present application and the process of the prior art;

[0044] Figure 4 A schematic diagram showing a comparison between an embodiment of the batch service processing method of the present application and an introduction queue of the prior art is shown;

[0045] Figure 5 A flowchart showing a specific embodiment S300 of the batch business processing method of the present application is shown;

[0046] Figure 6 A structural diagram showing a specific embodiment of the batch business processing system of the present application;

[0047] Figure 7 A schematic diagram of the structure of a computer device suitable for implementing the embodiments of the present application is shown. DETAILED DESCRIPTION

[0048] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0049] It should be noted that the batch business processing method and system disclosed in this application can be used in the financial field, and can also be used in any field other than the financial field. The application field of the batch business processing method and system disclosed in this application is not limited.

[0050] It should be noted that in one or more embodiments of the present application, the agency batch refers to a background batch mode for handling related businesses according to the agency principal, which usually adopts online or batch file acceptance business, and the business processing data of the batch business usually includes summary records and detailed records. Among them, the summary record refers to the summary statistical record sent up when the principal initiates the agency processing, such as the agency payment business, the summary record is the source of funds of the agency payment customer, which is the debit side. The summary record may include the agency agreement information, the number of detailed summary items and the detailed summary amount, which are used for total and sub-checking. The detailed record refers to the detailed information sent up when the principal initiates the agency processing, such as the agency payment business, the detailed record is the destination of funds of the agency payment customer, which is the credit side. The detailed record may include elements such as the agency payment serial number, agency payment account and amount.

[0051] In order to facilitate the understanding of the technical solution provided by the present application, the relevant contents of the technical solution of the present application are first explained below. The batch business processing method provided by the embodiment of the present application integrates and splits the business links of the batch proxy business to obtain multiple processing nodes, and determines the discrete data corresponding to different processing nodes, performs business processing on different discrete data respectively through the business processing threads of different processing nodes, and sets task identifiers for discrete data to form discrete tasks, and controls the processing order of discrete tasks through task identifiers to ensure the correct processing of batch business. Thus, large batch business can be divided into discrete tasks and assigned to different business threads for processing, preventing the problem of slow batch business processing due to processor performance limitations when a single thread is processed, realizing peak shaving and valley filling of batch business processing, reducing the system pressure for processing batch business, and improving the processing efficiency of batch business to be processed.

[0052] The following uses a batch business processing system as an example to illustrate the implementation process of the batch business processing method provided by the embodiment of the present application. It is understandable that the execution subject of the batch business processing method provided by the embodiment of the present application includes but is not limited to the batch business processing system.

[0053] According to one aspect of the present application, this embodiment discloses a batch service processing method. Figure 1 As shown, in this embodiment, the method includes:

[0054] S100: extracting the business processing data of the batch business to be processed by key fields to obtain multiple discrete data of different processing nodes.

[0055] S200: Setting a task identifier for each discrete data, and obtaining a discrete task according to each discrete data and the corresponding task identifier.

[0056] S300: Repeat the steps of sending each discrete task to a corresponding business processing thread according to the task identifier, performing business processing through the business processing thread, and updating the task identifier after the business processing is completed until all discrete task business processing is completed.

[0057] The batch business processing method of the present application extracts the business processing data of the batch business to be processed by key fields to obtain multiple discrete data of different processing nodes, sets a task identifier for each discrete data, obtains a discrete task according to each discrete data and the corresponding task identifier, repeatedly executes the steps of sending each discrete task to the corresponding business processing thread according to the task identifier, performing business processing through the business processing thread, and updating the task identifier after the business processing is completed until all discrete task business processing is completed. Thus, the present application integrates and splits the business links of the batch proxy business to obtain multiple processing nodes, and determines the discrete data corresponding to different processing nodes, performs business processing on different discrete data respectively through the business processing threads of different processing nodes, and sets task identifiers for the discrete data to form discrete tasks, and controls the processing order of discrete tasks through task identifiers to ensure the correct processing of batch business. Thus, large batch business can be divided into discrete tasks and assigned to different business threads for processing, preventing the problem of slow batch business processing due to processor performance limitations when a single thread is processed, realizing peak shaving and valley filling of batch business processing, reducing the system pressure for processing batch business, and improving the processing efficiency of batch business to be processed.

[0058] In a preferred embodiment, Figure 2 As shown, the S100 extracts the business processing data of the batch business to be processed by key fields to obtain multiple discrete data of different processing nodes, specifically including:

[0059] S110: Extracting the business processing data according to the first key field to obtain business processing data.

[0060] S120: Extract the business processing data according to the second key field to obtain data to be checked.

[0061] S130: Extracting the business processing data according to the third key field to obtain a summary record.

[0062] S140: Extract the business processing data according to the fourth key field to obtain a detailed record.

[0063] Specifically, it is understood that the business processing data of batch business usually includes summary records and detailed records. Among them, the summary record refers to the summary statistical record submitted when the principal initiates the agency processing. For example, for the agency payment business, the summary record is the source of funds for the agency payment customer, which is the debit side. The summary record may include agency agreement information, the number of detailed summary items and the detailed summary amount, which are used for total and sub-total verification. The detailed record refers to the detailed information submitted when the principal initiates the agency processing. For example, for the agency payment business, the detailed record is the destination of funds for the agency payment customer, which is the credit side. The detailed record may include elements such as the agency payment serial number, agency payment account and amount.

[0064] In the process of batch business processing, the business processing flow usually includes business acceptance, data inspection, data hashing, business inspection, summary debit processing, detailed party processing, summary credit processing (backwash) and business return processing links. In order to realize the discrete processing of batch business to be processed, the present application constructs independent business processing threads for different processing links in the business processing flow, which are used to process the business data of different links respectively, to realize a fast and flexible proxy batch processing mode. Preferably, according to the characteristics of batch business processing, multiple processing nodes including business acceptance nodes, data inspection nodes, summary debit processing nodes, detailed party processing nodes, summary credit processing nodes and data return nodes can be set to break up the group processing flow of the old process, adjust the original serial process formed by the dependency control of the previous and next items of the job into a concurrent control model of the thread pipeline, simplify the complexity of a single process, and improve the concurrency and timeliness of business processing. For example, in the business acceptance link, by scanning the business processing data packet, if the data packet is not processed normally, the business data packet acceptance operation is performed. After the acceptance is completed, the mobile data enters the waiting business processing area, waiting for subsequent data inspection and processing thread processing, such as Figure 3 shown.

[0065] Therefore, in order to obtain the discrete business data required for different processing links, in this preferred embodiment, the business processing data is extracted through the preset keywords of different processing links to obtain multiple discrete data, and the business processing data is broken up and no longer passed through multiple processing links in sequence in a serial control manner. Specifically, the KAFKA message queue can be introduced to process the data to be processed uniformly and discretely through the specified key fields. Each business processing layer adds a KAFKA acceptance thread to accept and implement the business data for subsequent business processing, such as Figure 4 shown.

[0066] In this preferred embodiment, the business processing data is extracted using the first, second, third, and fourth keywords, respectively, to obtain business processing data, pending data, summary records, and detailed records. In the prior art, data is discretely split into groups, and business processing is performed serially based on these groups. This can easily lead to data processing bottlenecks when one group of data is particularly large. In the present application, the system uses a hash function (e.g., a media number) to distinguish the data distribution of the aggregator and detail parties, resulting in summary records and detailed records. These records are then formed into a summary record hash queue and a detailed record hash queue, respectively. Summary records are processed uniformly in the summary record hash queue, while detailed records are processed uniformly in the detailed record hash queue. After the summary is processed, it is inserted into the summary master control queue for subsequent control of the detailed party's business processing. During the aggregator's processing, only the pre-processing performed by the aggregator is considered, while during the detail processing, only the pre-processing performed by the detail party is considered. This achieves highly discrete business data and logically rigorous, orderly, and efficient streaming processing. The first, second, third, and fourth keywords can be determined based on the specific batch of business transactions, and this application does not impose any restrictions on this.

[0067] In a preferred embodiment, Figure 5 As shown, the step S300 sends each discrete task to a corresponding business processing thread according to the task identifier, and performs business processing through the business processing thread. After the business processing is completed, updating the task identifier specifically includes:

[0068] S301: Determine the next processing node for processing the discrete task according to the task identifier as the current node.

[0069] S302: Send the discrete task to the target business processing thread corresponding to the current node, and perform business processing through the target business processing thread.

[0070] S303: After the business processing is completed, the task identifier is updated to the task identifier of the current node processing completed task.

[0071] Specifically, it can be understood that a task identifier can be set for discrete data. During the business processing process, after the business processing of the current thread is completed, the task identifier can be updated to determine the next business processing thread through the content of the task identifier, thereby realizing orderly control of the processing processes of multiple discrete data and ensuring the correct processing of batch business.

[0072] In the implementation example, the processing nodes include a business acceptance node, a data check node, a summary debit processing node, a detail processing node, a summary credit processing node, and a data return node. When the task identifier is a pending business acceptance identifier, S300 sends each discrete task to the corresponding business processing thread based on the task identifier, and the business processing is performed by the business processing thread. After the business processing is completed, updating the task identifier specifically includes:

[0073] S310: Send the business acceptance discrete task formed according to the business processing data and the pending business acceptance flag to the business processing thread corresponding to the business acceptance node for business processing. After the business processing is completed, update the pending business acceptance flag to a business accepted flag.

[0074] Specifically, it is understandable that before batch business processing, it is necessary to confirm whether the business can be processed, that is, business acceptance processing is required. The specific business acceptance processing process is a conventional technical means in this field and will not be repeated here. The business processing data can be extracted according to the preset first key field to obtain the business processing data. After the task identifier of the pending business acceptance identifier is initially set for the business processing data, a business acceptance discrete task is formed according to the pending business acceptance identifier and the business processing data. According to the pending business acceptance identifier, it is determined that the business acceptance discrete task needs to be sent to the business processing thread corresponding to the business acceptance node for business processing. When the business processing is completed, that is, when it is determined that it can be accepted according to the business processing data, the pending business acceptance identifier is updated to the business accepted identifier. Thus, the next processing node is determined according to the business accepted identifier and the order of multiple processing nodes, and the discrete task corresponding to the next processing node can be sent to the next processing node for business processing.

[0075] Further, optionally, when the task identifier is a business accepted identifier, S300 sends each discrete task to a corresponding business processing thread according to the task identifier, and performs business processing through the business processing thread. After the business processing is completed, updating the task identifier may also include:

[0076] S320: Send the data inspection task formed according to the data to be inspected and the business accepted flag to the business processing thread corresponding to the data inspection node for business processing. After the business processing is completed, update the business accepted flag to the data inspection passed flag.

[0077] Specifically, it can be understood that before batch business processing, it is necessary to perform data inspection on the accepted batch business. The specific data inspection process is a conventional technical means in this field and will not be described in detail here. The business processing data can be extracted according to the preset second key field to obtain the data to be inspected. At this time, the task identifier of the data to be inspected for the batch business to be processed is the business accepted identifier. A data inspection task is formed based on the business accepted identifier and the data to be inspected, and it is determined based on the business accepted identifier that the data inspection task needs to be sent to the business processing thread corresponding to the data inspection node for business processing. When the business processing is completed, that is, the data inspection passes, the business accepted identifier is updated to the data inspection pass identifier. Thus, the next processing node is determined based on the data inspection pass identifier and the sequence of multiple processing nodes, and the discrete task corresponding to the next processing node can be sent to the next processing node for business processing.

[0078] Further, optionally, when the task identifier is a data check pass identifier, S300 sends each discrete task to a corresponding business processing thread according to the task identifier, and performs business processing through the business processing thread. After the business processing is completed, updating the task identifier may also include:

[0079] S330: Send the summary borrow processing task formed according to the summary record and the data check pass identifier to the business processing thread corresponding to the summary borrow processing node for business processing. After the business processing is completed, update the data check pass identifier to the summary borrow processing completion identifier.

[0080] Specifically, it can be understood that the business processing data can be extracted according to the preset third key field to obtain a summary record. At this time, the task identifier of the summary record of the batch business to be processed is the data check pass identifier. A summary debit processing task is formed based on the data check pass identifier and the summary record. According to the data check pass identifier, it is determined that the summary debit processing task needs to be sent to the business processing thread corresponding to the summary debit processing node for business processing. When the business processing is completed, that is, when the debit debit business processing is completed, the data check pass identifier is updated to the summary debit processing completion identifier. Thus, the next processing node is determined based on the summary debit processing completion identifier and the sequence of multiple processing nodes, and the discrete task corresponding to the next processing node can be sent to the next processing node for business processing.

[0081] Further, optionally, when the task identifier is a data check pass identifier, S300 sends each discrete task to a corresponding business processing thread according to the task identifier, and performs business processing through the business processing thread. After the business processing is completed, updating the task identifier may also include:

[0082] S340: Send the detail processing task formed according to the detail record and the data check pass identifier to the business processing thread corresponding to the detail party processing node for business processing. After the business processing is completed, update the data check pass identifier to the detail party processing completion identifier.

[0083] Specifically, it can be understood that the business processing data can be extracted according to the preset fourth key field to obtain a detailed record. At this time, the task identifier of the summary record of the batch business to be processed is the data check pass identifier. A detailed processing task is formed based on the data check pass identifier and the detailed record. According to the data check pass identifier, it is determined that the detailed processing task needs to be sent to the business processing thread corresponding to the detail party processing node for business processing. When the business processing is completed, that is, when the transfer processing of the detail party is completed, the data check pass identifier is updated to the detail party processing completion identifier. Thus, the next processing node is determined based on the detail party processing completion identifier and the sequence of multiple processing nodes, and the discrete task corresponding to the next processing node can be sent to the next processing node for business processing.

[0084] Further, optionally, when the task identifier of the aggregate borrowing processing task is an aggregate borrowing processing completion identifier, and the task identifier of the detail processing task is a detail side processing completion identifier, S300 sends each discrete task to a corresponding business processing thread according to the task identifier, and performs business processing through the business processing thread. After the business processing is completed, updating the task identifier may further include:

[0085] S350: Send the summary loan processing task formed according to the summary record, the detailed record and the corresponding identifier to the business processing thread corresponding to the summary loan processing node for business processing. After the business processing is completed, update the summary debit processing completion identifier and the detailed party processing completion identifier to the summary loan processing completion identifier.

[0086] Specifically, it can be understood that after S330 and S340 are completed, that is, when the task identifiers of the summary debit processing task and the detailed processing task are the summary debit processing completion identifier and the detailed side processing completion identifier respectively, it is necessary to perform summary credit (backoffset) processing based on the business processing results of the summary debit processing task and the detailed processing task, that is, the business of failed transfer in the detailed side processing process is returned to the debit side, completing the backoff and preventing the occurrence of inconsistent credits and debits. A summary credit processing task can be formed based on the summary record and the detailed record and the corresponding identifiers, and the summary credit processing task is sent to the business processing thread corresponding to the summary credit processing node for business processing. After the business processing is completed, the summary debit processing completion identifier and the detailed side processing completion identifier are updated to the summary credit processing completion identifier. Thus, the next processing node is determined based on the summary credit processing completion identifier and the sequence of multiple processing nodes, and the discrete task corresponding to the next processing node can be sent to the next processing node for business processing.

[0087] Further, optionally, when the task identifier of the aggregate loan processing task is a aggregate loan processing completion identifier, S300 sends each discrete task to a corresponding business processing thread according to the task identifier, and performs business processing through the business processing thread. After the business processing is completed, updating the task identifier specifically includes:

[0088] S360: Send the data return task formed according to the summary record, the detailed record and the summary loan processing completion mark to the business processing thread corresponding to the data return node for business processing. After the business processing is completed, the summary loan processing completion mark is updated to the business processing completion mark, and all discrete task business processing is completed.

[0089] Specifically, it is understood that after the summary loan processing is completed, the batch business needs to be returned to disk, that is, the processing results of the batch business need to be determined and fed back to the client. When the batch business has been processed at all processing nodes before the data return node, that is, the task identifier is the summary loan processing completion identifier, the return operation can be triggered. Through the multi-database parallel approach, the small files of the processing results of the summary loan processing node, the detailed party processing node, and the summary loan processing node are merged into a large file, realizing the rapid return of data files, on the one hand improving efficiency, and on the other hand reducing the dependency coupling of different data files.

[0090] This application can introduce a message engine by decoupling each link of the proxy batch business processing, and can process the proxy batch business data uniformly and discretely, and realize the orderly processing of the business with the help of refined command signals. The main advantages are as follows: 1) The business processing links are decoupled to reduce the abnormal impact of the business processing links and improve the security of the system operation. 2) The business processing data is discretized to effectively realize the peak shaving and valley filling of business processing, reduce the cost loss of the system, and improve the stability of the system operation. 3) The message engine is introduced to construct the command signal of the business processing steps, effectively realize the orderly processing of the business, and improve the flexibility of the batch proxy business system. 4) The centralized unified processing is adjusted to the streaming parallel business processing mode to reduce the mutual influence between interactive applications.

[0091] Based on the same principle, this embodiment also discloses a batch business processing system. Figure 6 As shown, in this embodiment, the system includes a data discrete module 11 , a discrete task module 12 and a task processing module 13 .

[0092] The data discretization module 11 is used to extract the business processing data of the batch business to be processed by key fields to obtain multiple discrete data of different processing nodes.

[0093] The discrete task module 12 is used to set a task identifier for each discrete data, and obtain a discrete task according to each discrete data and the corresponding task identifier.

[0094] The task processing module 13 is used to repeatedly execute the steps of sending each discrete task to the corresponding business processing thread according to the task identifier, performing business processing through the business processing thread, and updating the task identifier after the business processing is completed until all discrete task business processing is completed.

[0095] Since the principle of solving the problem by this system is similar to that of the above method, the implementation of this system can refer to the implementation of the method and will not be repeated here.

[0096] The systems, devices, modules, or units described in the above embodiments may be implemented by computer chips or entities, or by products having certain functions. A typical implementation device is a computer device. Specifically, the computer device may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0097] In a typical example, a computer device specifically includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, the method executed by the client as described above is implemented, or when the processor executes the program, the method executed by the server as described above is implemented.

[0098] Reference below Figure 7 , which shows a structural diagram of a computer device 600 suitable for implementing an embodiment of the present application.

[0099] like Figure 7 As shown, computer device 600 includes a central processing unit (CPU) 601, which can perform various appropriate tasks and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage portion 608 into a random access memory (RAM) 603. Various programs and data required for the operation of system 600 are also stored in RAM 603. CPU 601, ROM 602, and RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to bus 604.

[0100] The following components are connected to the I / O interface 605: an input section 606 including a keyboard, a mouse, and the like; an output section 607 including devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), and a speaker; a storage section 608 including devices such as a hard disk; and a communication section 609 including a network interface card such as a LAN card or a modem. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. Removable media 611, such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, is installed in the drive 610 as needed, so that computer programs read therefrom can be installed in the storage section 608 as needed.

[0101] In particular, according to embodiments of the present application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program comprising program code for executing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via the communication portion 609 and / or installed from a removable medium 611.

[0102] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0103] For the convenience of description, the above devices are described as being divided into various units according to their functions. Of course, when implementing this application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0104] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0105] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0106] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0107] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

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

[0109] The present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communications network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0110] The various embodiments in this specification are described in a progressive manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the system embodiments are generally similar to the method embodiments, so the description is relatively simple. For relevant parts, refer to the description of the method embodiments.

[0111] The foregoing is merely an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should all be included within the scope of the claims of the present application.

Claims

1. A batch business processing method, characterized in that: include: Extract key fields from the business processing data of batch business to obtain multiple discrete data of different processing nodes; Setting a task identifier for each discrete data, and obtaining a discrete task according to each discrete data and the corresponding task identifier; Repeating the steps of sending each discrete task to a corresponding business processing thread according to the task identifier, performing business processing through the business processing thread, and updating the task identifier after the business processing is completed until all discrete task business processing is completed; The step of extracting the business processing data of the batch business to be processed by key fields to obtain multiple discrete data of different processing nodes specifically includes: Extracting the business processing data according to the first key field to obtain business processing data; Extracting the business processing data according to the second key field to obtain data to be checked; Extracting the business processing data according to the third key field to obtain a summary record; Extracting the business processing data according to the fourth key field to obtain a detailed record; The processing nodes include business acceptance nodes, data inspection nodes, summary debit processing nodes, detail processing nodes, summary credit processing nodes and data return nodes.

2. The batch business processing method according to claim 1, characterized in that: The step of sending each discrete task to a corresponding business processing thread according to the task identifier, performing business processing through the business processing thread, and updating the task identifier after the business processing is completed specifically includes: Determine the next processing node for processing the discrete task according to the task identifier as the current node; Sending the discrete task to the target business processing thread corresponding to the current node, and performing business processing through the target business processing thread; After the business processing is completed, the task identifier is updated to the task identifier of the task completed by the current node.

3. The batch business processing method according to claim 1, characterized in that: When the task identifier is a pending business acceptance identifier, sending each discrete task to a corresponding business processing thread according to the task identifier, performing business processing through the business processing thread, and updating the task identifier after the business processing is completed specifically includes: The business acceptance discrete task formed according to the business processing data and the pending business acceptance identifier is sent to the business processing thread corresponding to the business acceptance node for business processing. After the business processing is completed, the pending business acceptance identifier is updated to a business accepted identifier.

4. The batch business processing method according to claim 3, characterized in that: When the task identifier is a business accepted identifier, sending each discrete task to a corresponding business processing thread according to the task identifier, performing business processing through the business processing thread, and updating the task identifier after the business processing is completed specifically includes: The data inspection task formed according to the data to be inspected and the business accepted flag is sent to the business processing thread corresponding to the data inspection node for business processing. After the business processing is completed, the business accepted flag is updated to the data inspection passed flag.

5. The batch business processing method according to claim 4, characterized in that: When the task identifier is a data check pass identifier, sending each discrete task to a corresponding business processing thread according to the task identifier, performing business processing by the business processing thread, and updating the task identifier after the business processing is completed specifically includes: The summary borrowing processing task formed according to the summary record and the data check pass identifier is sent to the business processing thread corresponding to the summary borrowing processing node for business processing. After the business processing is completed, the data check pass identifier is updated to the summary borrowing processing completion identifier.

6. The batch business processing method according to claim 5, characterized in that: When the task identifier is a data check pass identifier, sending each discrete task to a corresponding business processing thread according to the task identifier, performing business processing by the business processing thread, and updating the task identifier after the business processing is completed specifically includes: The detail processing task formed according to the detail record and the data check pass identifier is sent to the business processing thread corresponding to the detail party processing node for business processing. After the business processing is completed, the data check pass identifier is updated to the detail party processing completion identifier.

7. The batch business processing method according to claim 6, characterized in that: When the task identifier of the aggregate borrowing processing task is the aggregate borrowing processing completion identifier, and the task identifier of the detail processing task is the detail processing completion identifier, sending each discrete task to a corresponding business processing thread according to the task identifier, performing business processing by the business processing thread, and updating the task identifier after the business processing is completed specifically includes: The summary loan processing task formed according to the summary record, the detailed record and the corresponding identifier is sent to the business processing thread corresponding to the summary loan processing node for business processing. After the business processing is completed, the summary debit processing completion identifier and the detailed debit processing completion identifier are updated to the summary loan processing completion identifier.

8. The batch business processing method according to claim 7, characterized in that: When the task identifier of the aggregate loan processing task is a aggregate loan processing completion identifier, sending each discrete task to a corresponding business processing thread according to the task identifier, performing business processing by the business processing thread, and updating the task identifier after the business processing is completed specifically includes: The data return task formed according to the summary record, the detailed record and the summary loan processing completion mark is sent to the business processing thread corresponding to the data return node for business processing. After the business processing is completed, the summary loan processing completion mark is updated to the business processing completion mark, and all discrete task business processing is completed.

9. A batch business processing system, characterized in that: include: The data discretization module is used to extract the key fields of the business processing data of the batch business to be processed to obtain multiple discrete data of different processing nodes; A discrete task module is used to set a task identifier for each discrete data and obtain a discrete task according to each discrete data and the corresponding task identifier; A task processing module is configured to repeatedly execute the steps of sending each discrete task to a corresponding business processing thread according to the task identifier, performing business processing through the business processing thread, and updating the task identifier after the business processing is completed until all discrete task business processing is completed; The data discretization module is specifically configured to extract the business processing data according to the first key field to obtain business processing data; Extracting the business processing data according to the second key field to obtain data to be checked; Extracting the business processing data according to the third key field to obtain a summary record; Extracting the business processing data according to the fourth key field to obtain a detailed record; The processing nodes include business acceptance nodes, data inspection nodes, summary debit processing nodes, detail processing nodes, summary credit processing nodes and data return nodes.

10. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the program, the method according to any one of claims 1 to 8 is implemented.

11. A computer-readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 8 is implemented.

Images