Transaction management method and device, equipment, storage medium and program product
By receiving and processing the original data sent by the data source module in the financial system, generating replica data, and obtaining authorization results from the replica data during transaction requests, the problem of poor transaction management stability in the financial system is solved and the coupling between systems is reduced improves the stability of the transaction process.
Patent Information
- Application Number
- CN202411289043.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-14
- Publication Date
- 2024-12-13
AI Technical Summary
When conducting resource transactions, the logical system is divided into multiple physical systems, so when determining whether to perform resource management, control information needs to be obtained from other systems, which increases the coupling between systems, and failures may lead to transaction management. Poor stability.
By receiving the original data sent by the data source module, data processing is carried out to generate copy data. When receiving the transaction request, the data corresponding to the transaction request is obtained from the copy data and the original data, and the authorization results are determined based on the data to reduce the number of other data sources. Frequent access to modules.
This reduces the coupling between systems and improves the stability of transaction management, so that the failure of a certain data source module will not immediately affect the entire transaction process.
Smart Images
Figure CN119130649A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of information security technology, and in particular, relates to a transaction management method, device, equipment, storage medium and program product. Background Art
[0002] As financial supervision becomes increasingly strict, account security protection becomes increasingly important. When financial systems conduct resource transactions, they need to conduct resource control based on more and more control information. For example, when a bank's financial system conducts transfers and payments, it needs to determine whether the transaction can be conducted based on the customer's transaction behavior data, anti-money laundering risk data, anti-fraud data, basic account opening data, etc. However, with the development and evolution of the financial system, a logical financial system is usually divided into multiple physical systems: including the main resource management module and other systems. When conducting resource transactions, data from multiple physical systems may be used.
[0003] Then, every time when judging whether to perform resource control, it is necessary to obtain control information from other systems, which increases the coupling between various physical systems. When a single non-important system fails, it may also cause resource transactions in the entire logical system to be unavailable, resulting in poor stability of transaction management. Summary of the invention
[0004] The embodiments of the present application provide a transaction management method, apparatus, device, storage medium and program product, which can solve the problem of poor stability of existing transaction management.
[0005] In a first aspect, an embodiment of the present application provides a transaction management method, the method comprising:
[0006] Receiving raw data sent by at least one data source module, the raw data including historical behavior information and risk control information of users and accounts, the data source module being in communication connection with the resource management module;
[0007] Processing the original data to generate copy data;
[0008] When receiving a transaction request, obtaining first data corresponding to the transaction request from at least one of the copy data and the original data;
[0009] An authorization result of the transaction request is determined according to the first data.
[0010] In some embodiments, after processing the original data to generate the copy data, the method further includes:
[0011] In the case where there is changed second data in the at least one data source module, data processing is performed on the changed second data to obtain third data, and the original data includes the second data;
[0012] When the third data and a portion of the duplicate data corresponding to the second data are inconsistent, the duplicate data is updated according to the third data.
[0013] In some embodiments, the receiving raw data sent by at least one data source module includes:
[0014] Receiving, in a synchronous transmission manner, first original data associated with the resource transaction from among the original data;
[0015] Second original data in the original data that has no association with the resource transaction is received in an asynchronous transmission manner.
[0016] In some embodiments, obtaining the first data corresponding to the transaction request from at least one of the copy data and the original data includes:
[0017] Acquire the user ID of the user participating in the transaction and the account ID of the account participating in the transaction from the transaction request;
[0018] Acquire fourth data corresponding to the user identifier and the account identifier from the copy data, wherein the first data includes the fourth data.
[0019] In some embodiments, determining the authorization result of the transaction request according to the first data includes:
[0020] determining a preliminary result of the transaction request according to the fourth data;
[0021] When the preliminary result is that the transaction request is allowed, determining the authorization result as allowing the transaction;
[0022] When the preliminary result is that the transaction request is not allowed, fifth data corresponding to the user identifier and the account identifier is obtained from the original data, and the authorization result of the transaction request is determined according to the fifth data, wherein the first data includes the fifth data.
[0023] In some embodiments, processing the original data to generate the copy data includes:
[0024] Acquire the first original data associated with the resource transaction from the original data;
[0025] Performing data aggregation on the first original data to obtain aggregated data;
[0026] A data index is established for the aggregated data, and the copy data is generated according to the aggregated data and the data index.
[0027] In a second aspect, an embodiment of the present application provides a transaction management device, the device comprising:
[0028] A receiving module, used to receive raw data sent by at least one data source module, the raw data including historical behavior information and risk control information of users and accounts, the data source module being in communication connection with the resource management module;
[0029] A processing module, used for processing the original data to generate copy data;
[0030] an acquisition module, configured to acquire, upon receiving a transaction request, first data corresponding to the transaction request from at least one of the copy data and the original data;
[0031] A determination module is used to determine the authorization result of the transaction request according to the first data.
[0032] In a third aspect, an embodiment of the present application provides a transaction management device, the device comprising: a processor and a memory storing computer program instructions;
[0033] The above transaction management method is implemented when the processor executes the computer program instructions.
[0034] In a fourth aspect, an embodiment of the present application provides a computer storage medium having computer program instructions stored thereon, and the computer program instructions, when executed by a processor, implement the above transaction management method.
[0035] In a fifth aspect, an embodiment of the present application provides a computer program product, which includes computer program instructions, and when the computer program instructions are executed by a processor, the above transaction management method is implemented.
[0036] In the present application, by receiving the original data sent by at least one data source module, the original data includes the historical behavior information and risk control information of the user and the account; processing the original data to generate the copy data; in the case of receiving the transaction request, obtaining the first data corresponding to the transaction request from at least one item of the copy data and the original data; determining the authorization result of the transaction request according to the first data. In this way, by processing the original data provided by the data source module in advance and generating the copy data, the copy data is stored in the resource management module. In most cases, the resource management module can rely on the local copy data for transaction judgment without frequently accessing other data source modules. This greatly reduces the coupling between systems, so that the failure of a data source module will not immediately affect the entire transaction process, thereby improving the stability of transaction management. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. 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 creative work.
[0038] Figure 1 It is a flowchart of a transaction management method provided in an embodiment of the present application;
[0039] Figure 2 It is a structural diagram of a transaction management device provided in one embodiment of the present application;
[0040] Figure 3 It is a schematic diagram of the hardware structure of a transaction management device provided in one embodiment of the present application. DETAILED DESCRIPTION
[0041] The features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by illustrating the examples of the present application.
[0042] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "include..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.
[0043] It should be noted that the acquisition, storage, use, and processing of data in the technical solution of this application are in compliance with the relevant provisions of national laws and regulations.
[0044] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.
[0045] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The embodiments will be described in detail below in conjunction with the accompanying drawings.
[0046] Specifically, in order to solve the problems of the prior art, the embodiments of the present application provide a transaction management method, device, equipment, storage medium and program product. The transaction management method provided by the embodiments of the present application is first introduced below.
[0047] Figure 1 A flow chart of a transaction management method provided by an embodiment of the present application is shown. The method comprises the following steps:
[0048] S110, receiving original data sent by at least one data source module, the original data including historical behavior information and risk control information of users and accounts, the data source module being communicatively connected with the resource management module.
[0049] In this embodiment, the data source module is a physical system in the financial system that is responsible for collecting, storing and managing specific types of data. Each data source module usually covers a specific business area, and the data stored in the data source module is the original data. The resource management module is a computer module specifically used to process and manage financial transactions and related resource information.
[0050] There is a communication connection between the data source module and the resource management module, so the data source module can periodically transmit the raw data therein to the resource management module. The raw data includes historical behavior data of users and accounts (e.g., transaction history, account activities, etc.) and risk control information (e.g., anti-money laundering risk data, anti-fraud data, etc.).
[0051] As an optional embodiment, the receiving original data sent by at least one data source module includes:
[0052] Receiving, in a synchronous transmission manner, first original data associated with the resource transaction from among the original data;
[0053] Second original data in the original data that has no association with the resource transaction is received in an asynchronous transmission manner.
[0054] In this embodiment, the first original data is data that is directly associated with resource transactions. Such data is usually crucial to the conduct and judgment of transactions and needs to be immediately obtained and verified during the transaction processing. The first original data at least includes: transaction amount, account balance, historical transaction records, anti-money laundering data, and anti-fraud data; the second original data is data that is not directly associated with resource transactions, such as customer preference data.
[0055] Synchronous transmission is a transmission method in which the sender waits for the receiver's confirmation before continuing with other operations when transmitting data. Asynchronous transmission is a transmission method in which the sender does not need to wait for the receiver's confirmation after transmitting data before continuing with other operations.
[0056] Therefore, it can be determined first whether the original data to be transmitted is the first original data or the second original data. If it is the first original data, after the data source module sends the first original data to the resource management module, it is necessary to receive a confirmation notification of the first original data fed back by the resource management module before subsequent operations can be performed. Otherwise, it is necessary to repeatedly send the first original data to the resource management module again to ensure that the resource management module successfully receives the first original data. If the original data to be transmitted is the second original data, after the data source module sends the first original data to the resource management module, the data source module can directly perform subsequent steps.
[0057] In this way, it can ensure that important data related to resource transactions are successfully received by the resource management module, and when transmitting data unrelated to resource transactions, the impact of data transmission on other businesses in the data source system can be avoided as much as possible.
[0058] S120, processing the original data to generate copy data.
[0059] In this embodiment, since the amount of original data is often large and there are usually invalid fields in the original data, and the copy data only needs to include fields related to resource transactions, the amount of data stored and transmitted can be significantly reduced by trimming unnecessary fields and records in the copy data, thereby improving the processing speed and efficiency of the system.
[0060] As an optional embodiment, the processing the original data to generate the copy data includes:
[0061] Acquire the first original data associated with the resource transaction from the original data;
[0062] Performing data aggregation on the first original data to obtain aggregated data;
[0063] A data index is established for the aggregated data, and the copy data is generated according to the aggregated data and the data index.
[0064] In this embodiment, the original data can be first filtered to obtain only the data directly related to resource management and control, that is, the first original data, from the original data. Then, since the original data obtained from the data source module is a detailed record, the first original data is also a detailed record, so the first original data can be summarized and counted, and the first original data can be aggregated from detailed records into statistical results. For example, the detailed records of multiple transactions of a customer are aggregated into the total transaction amount and number of transactions of the customer in a specific time period. Finally, indexes can be established for commonly used query fields in aggregated data to improve the efficiency of data query. For example, an index is established for important information such as customer ID and transaction date in aggregated data, and the copy data is generated based on the aggregated data and the data index.
[0065] Then users can quickly obtain the required batch data only through data indexes to speed up query operations from the replica data.
[0066] S130, when receiving a transaction request, obtaining first data corresponding to the transaction request from at least one of the copy data and the original data;
[0067] In this embodiment, if a user wants to conduct a resource transaction through a financial system, a transaction request will be sent to the financial system to request the resource transaction. The financial system will then send the transaction request to the resource management module, and the resource management module will obtain the first data related to the transaction request from at least one of the copy data and the original data. The copy data is stored inside the resource management module, and the original data is stored in a data source module that is in communication with the resource management module.
[0068] As an optional embodiment, the obtaining the first data corresponding to the transaction request from at least one of the copy data and the original data includes:
[0069] Acquire the user ID of the user participating in the transaction and the account ID of the account participating in the transaction from the transaction request;
[0070] Acquire fourth data corresponding to the user identifier and the account identifier from the copy data, wherein the first data includes the fourth data.
[0071] In this embodiment, since the transaction request is used to request a resource transaction, it is possible to determine whether the resource transaction should be allowed based on the characteristics of the user initiating the transaction and the account initiating the transaction. Among them, the user identifier is used to uniquely identify the user initiating the transaction. The account identifier is used to uniquely identify the account initiating the transaction. After receiving the transaction request, the user identifier and the account identifier can be first extracted from the transaction request, and then, through the user identifier and the account identifier, the specific data corresponding to these identifiers, i.e., the fourth data, can be extracted from the copy data stored in the system; and then, based on the fourth data, it is determined whether to authorize the transaction request.
[0072] In this way, the replica data can be effectively utilized to reduce the dependence on real-time original data and improve the processing efficiency and stability of the system.
[0073] S140: Determine an authorization result of the transaction request according to the first data.
[0074] In this embodiment, the authorization result includes two results: allowing the transaction and not allowing the transaction. Since the original data includes historical behavior information and risk control information of users and accounts, the first data may include transaction behavior data of customers and accounts, anti-money laundering risk data, anti-fraud data, basic account opening data, etc. It can be judged based on the above first data whether the transaction can be carried out.
[0075] As an optional embodiment, determining the authorization result of the transaction request according to the first data includes:
[0076] determining a preliminary result of the transaction request according to the fourth data;
[0077] When the preliminary result is that the transaction request is allowed, determining the authorization result as allowing the transaction;
[0078] When the preliminary result is that the transaction request is not allowed, fifth data corresponding to the user identifier and the account identifier is obtained from the original data, and the authorization result of the transaction request is determined according to the fifth data, wherein the first data includes the fifth data.
[0079] In this embodiment, the fourth data is data associated with the transaction request in the copy data. The preliminary result of the transaction request can be first determined based on the fourth data in the copy data. Since most transaction requests are usually allowed, if the preliminary result is to allow the transaction request, then the final authorization result can also be determined as allowing the transaction request. If the preliminary result is not to allow the transaction request, the resource management module needs to access other data source modules, obtain the fifth data corresponding to the user identifier and the account identifier from the original data of the data source module, and determine again whether the transaction request is allowed based on the fifth data. If it is determined based on the fifth data that the transaction request is still not allowed, the authorization result of the transaction request is determined as not allowing the transaction request. If it is determined based on the fifth data that the transaction request is allowed, the authorization result is also determined as allowing the transaction.
[0080] Through this staged decision-making process, the system can make decisions on transaction requests quickly in most cases, improving efficiency. When the initial assessment does not allow the transaction, the system will further obtain detailed information from the original data for verification to ensure the accuracy and security of the final decision. This approach effectively balances processing speed and decision quality, and improves the stability and reliability of the system.
[0081] In this embodiment, by receiving the original data sent by at least one data source module, the original data includes historical behavior information and risk control information of users and accounts; processing the original data to generate copy data; in the case of receiving a transaction request, obtaining the first data corresponding to the transaction request from at least one item of the copy data and the original data; determining the authorization result of the transaction request according to the first data. In this way, by processing the original data provided by the data source module in advance and generating copy data, the copy data is stored in the resource management module. In most cases, the resource management module can rely on the local copy data for transaction judgment without frequently accessing other data source modules. This greatly reduces the coupling between systems, so that the failure of a data source module will not immediately affect the entire transaction process, thereby improving the stability of transaction management.
[0082] As an optional embodiment, after processing the original data to generate the copy data, the method further includes:
[0083] In the case where there is changed second data in the at least one data source module, data processing is performed on the changed second data to obtain third data, wherein the original data includes the second data;
[0084] When the third data and a portion of the duplicate data corresponding to the second data are inconsistent, the duplicate data is updated according to the third data.
[0085] In this embodiment, whenever it is detected that part of the original data in the data source module has changed, that is, when the second data has changed, the changed second data is processed and processed to generate third data. This processing process is performed according to the needs of the resource system. Then, the processed third data can be compared with the part corresponding to the second data in the existing copy data to check whether there is an inconsistent part between the two. If inconsistency is found, the copy data is updated according to the third data to ensure the accuracy and timeliness of the copy data.
[0086] In this way, by processing the changed data and comparing it with the replica data, it can be ensured that the replica data in the resource system is up-to-date and accurate. This helps to improve the reliability of resource system decisions. In addition, synchronization is only performed when the processed third data is inconsistent with the replica data, reducing unnecessary data transmission and system overhead, and optimizing system performance.
[0087] Based on the transaction management method provided in the above embodiment, the present application also provides a specific implementation of a transaction management device. Please refer to the following embodiment.
[0088] See first Figure 2 The transaction management device 200 provided in the embodiment of the present application includes the following modules:
[0089] A receiving module 201, configured to receive raw data sent by at least one data source module, the raw data including historical behavior information and risk control information of users and accounts, the data source module being in communication connection with the resource management module;
[0090] A processing module 202, used for processing the original data to generate duplicate data;
[0091] An acquisition module 203, configured to acquire, upon receiving a transaction request, first data corresponding to the transaction request from at least one of the copy data and the original data;
[0092] The determination module 204 is configured to determine the authorization result of the transaction request according to the first data.
[0093] The device can receive the original data sent by at least one data source module, the original data includes historical behavior information and risk control information of users and accounts; process the original data to generate copy data; when receiving a transaction request, obtain the first data corresponding to the transaction request from at least one of the copy data and the original data; and determine the authorization result of the transaction request based on the first data. In this way, by processing the original data provided by the data source module in advance and generating copy data, the copy data is stored in the resource management module. In most cases, the resource management module can rely on the local copy data for transaction judgment without frequently accessing other data source modules. This greatly reduces the coupling between systems, so that the failure of a data source module will not immediately affect the entire transaction process, thereby improving the stability of transaction management.
[0094] As an implementation of the present application, the transaction management device 200 may further include:
[0095] a change module, configured to, when there is changed second data in the at least one data source module, perform data processing on the changed second data to obtain third data, wherein the original data includes the second data;
[0096] An updating module is used to update the copy data according to the third data when the third data and the part of the copy data corresponding to the second data are inconsistent.
[0097] As an implementation of the present application, the receiving module 201 may further include:
[0098] A first transmission unit, configured to receive, in a synchronous transmission manner, first original data associated with the resource transaction in the original data;
[0099] The second transmission unit is used to receive second original data in the original data that has no association with the resource transaction in an asynchronous transmission manner.
[0100] As an implementation of the present application, the acquisition module 203 may further include:
[0101] A first acquisition unit, configured to acquire, from the transaction request, a user identifier of a user participating in the transaction and an account identifier of an account participating in the transaction;
[0102] The second acquisition unit is configured to acquire fourth data corresponding to the user identifier and the account identifier from the copy data, wherein the first data includes the fourth data.
[0103] As an implementation of the present application, the above-mentioned determination module 204 may also include:
[0104] a first determining unit, configured to determine a preliminary result of the transaction request according to the fourth data;
[0105] A second determining unit, configured to determine the authorization result as allowing the transaction if the preliminary result is allowing the transaction request;
[0106] a third determination unit, for obtaining, when the preliminary result is that the transaction request is not allowed, fifth data corresponding to the user identifier and the account identifier from the original data, and determining an authorization result of the transaction request according to the fifth data, wherein the first data includes the fifth data.
[0107] As an implementation of the present application, the processing module 202 may further include:
[0108] A third acquisition unit is used to acquire first original data associated with the resource transaction in the original data;
[0109] an aggregation unit, configured to aggregate the first original data to obtain aggregated data;
[0110] An indexing unit is used to establish a data index for the aggregated data, and generate the copy data according to the aggregated data and the data index.
[0111] The transaction management device provided in the embodiment of the present invention can implement each step in the above method embodiment, and will not be described again here to avoid repetition.
[0112] Figure 3 A schematic diagram of the hardware structure of a transaction management device provided in an embodiment of the present application is shown.
[0113] The transaction management device may include a processor 1001 and a memory 1002 storing computer program instructions.
[0114] Specifically, the processor 1001 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.
[0115] The memory 1002 may include a large capacity memory for data or instructions. By way of example and not limitation, the memory 1002 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive or a combination of two or more of these. In appropriate cases, the memory 1002 may include a removable or non-removable (or fixed) medium. In appropriate cases, the memory 1002 may be inside or outside the integrated gateway disaster recovery device. In a specific embodiment, the memory 1002 is a non-volatile solid-state memory.
[0116] The memory may include read-only memory (ROM), random access memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical or other physical / tangible memory storage devices. Thus, typically, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to an aspect of the present disclosure.
[0117] The processor 1001 implements any one of the transaction management methods in the above embodiments by reading and executing computer program instructions stored in the memory 1002 .
[0118] In one example, the transaction management device may further include a communication interface 1003 and a bus 1010. Figure 3 As shown, the processor 1001, the memory 1002, and the communication interface 1003 are connected via a bus 1010 and communicate with each other.
[0119] The communication interface 1003 is mainly used to implement communication between various modules, devices, units and / or equipment in the embodiments of the present application.
[0120] Bus 1010 includes hardware, software or both, and the parts of the management equipment of transaction are coupled to each other.For example, but not limitation, bus may include accelerated graphics port (AGP) or other graphics bus, enhanced industrial standard architecture (EISA) bus, front side bus (FSB), hypertransport (HT) interconnection, industrial standard architecture (ISA) bus, infinite bandwidth interconnection, low pin count (LPC) bus, memory bus, micro channel architecture (MCA) bus, peripheral component interconnection (PCI) bus, PCI-Express (PCI-X) bus, serial advanced technology attachment (SATA) bus, video electronics standard association local (VLB) bus or other suitable bus or two or more of these combinations. In suitable cases, bus 1010 may include one or more buses. Although the present application embodiment describes and shows a specific bus, the application considers any suitable bus or interconnection.
[0121] The transaction management device may be based on the above embodiment, thereby realizing the transaction management method and apparatus combined with the above embodiment.
[0122] In addition, in combination with the transaction management method in the above-mentioned embodiment, the embodiment of the present application may provide a computer storage medium for implementation. The computer storage medium stores computer program instructions; when the computer program instructions are executed by the processor, any one of the transaction management methods in the above-mentioned embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here. Among them, the above-mentioned computer-readable storage medium may include a non-transitory computer-readable storage medium, such as a read-only memory (Read-Only Memory, referred to as ROM), a random access memory (Random Access Memory, referred to as RAM), a disk or an optical disk, etc., which is not limited here.
[0123] In addition, an embodiment of the present application further provides a computer program product, including computer program instructions, which can implement the steps and corresponding contents of the aforementioned method embodiment when the computer program instructions are executed by a processor.
[0124] It should be clear that the present application is not limited to the specific configuration and processing described above and shown in the figures. For the sake of simplicity, a detailed description of the known method is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present application is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present application.
[0125] The functional blocks shown in the above block diagram can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), appropriate firmware, a plug-in, a function card, etc. When implemented in software, the elements of the present application are programs or code segments that are used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link by a data signal carried in a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, optical fiber media, radio frequency (RF) links, etc. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.
[0126] It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, this application is not limited to the order of the above steps, that is, the steps can be performed in the order mentioned in the embodiment, or in a different order from the embodiment, or several steps can be performed simultaneously.
[0127] Aspects of the present disclosure are described above with reference to the flowchart and / or block diagram of the method, device and computer program product according to the embodiment of the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box 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, or other programmable data processing device to produce a machine so that these instructions executed by the processor of the computer or other programmable data processing device enable the implementation of the function / action specified in one or more boxes of the flowchart and / or block diagram. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field programmable logic circuit. It can also be understood that each box in the block diagram and / or flowchart and the combination of boxes in the block diagram and / or flowchart can also be implemented by dedicated hardware that performs a specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions.
[0128] The above are only specific implementation methods of the present application. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. It should be understood that the protection scope of the present application is not limited to this. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in this application, and these modifications or replacements should be included in the protection scope of this application.
Claims
1. A transaction management method, characterized in that: The method is applied to a resource management module, and the method comprises: Receiving raw data sent by at least one data source module, the raw data including historical behavior information and risk control information of users and accounts, the data source module being in communication connection with the resource management module; Processing the original data to generate copy data; When receiving a transaction request, obtaining first data corresponding to the transaction request from at least one of the copy data and the original data; An authorization result of the transaction request is determined according to the first data.
2. The transaction management method according to claim 1, characterized in that: After processing the original data to generate duplicate data, the method further includes: In the case where there is changed second data in the at least one data source module, data processing is performed on the changed second data to obtain third data, and the original data includes the second data; When the third data and a portion of the duplicate data corresponding to the second data are inconsistent, the duplicate data is updated according to the third data.
3. The transaction management method according to claim 1, characterized in that: The receiving of original data sent by at least one data source module includes: Receiving, in a synchronous transmission manner, first original data associated with the resource transaction from among the original data; Second original data in the original data that has no association with the resource transaction is received in an asynchronous transmission manner.
4. The transaction management method according to claim 1, characterized in that: The obtaining the first data corresponding to the transaction request from at least one of the copy data and the original data includes: Acquire the user ID of the user participating in the transaction and the account ID of the account participating in the transaction from the transaction request; Acquire fourth data corresponding to the user identifier and the account identifier from the copy data, wherein the first data includes the fourth data.
5. The transaction management method according to claim 4, characterized in that: The determining the authorization result of the transaction request according to the first data includes: determining a preliminary result of the transaction request according to the fourth data; When the preliminary result is that the transaction request is allowed, determining the authorization result as allowing the transaction; When the preliminary result is that the transaction request is not allowed, fifth data corresponding to the user identifier and the account identifier is obtained from the original data, and the authorization result of the transaction request is determined according to the fifth data, wherein the first data includes the fifth data.
6. The transaction management method according to claim 1, characterized in that: The processing of the original data to generate duplicate data includes: Acquire the first original data associated with the resource transaction from the original data; Performing data aggregation on the first original data to obtain aggregated data; A data index is established for the aggregated data, and the copy data is generated according to the aggregated data and the data index.
7. A transaction management device, characterized in that: The device comprises: A receiving module, used to receive raw data sent by at least one data source module, the raw data including historical behavior information and risk control information of users and accounts, the data source module being in communication connection with the resource management module; A processing module, used for processing the original data to generate copy data; an acquisition module, configured to acquire, upon receiving a transaction request, first data corresponding to the transaction request from at least one of the copy data and the original data; A determination module is used to determine the authorization result of the transaction request according to the first data.
8. A transaction management device, characterized in that: The transaction management device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the transaction management method according to any one of claims 1 to 6 is implemented.
9. A computer storage medium, characterized in that The computer storage medium stores computer program instructions, which, when executed by a processor, implement the transaction management method according to any one of claims 1 to 6.
10. A computer program product, characterized in that The computer program product comprises computer program instructions, and when the computer program instructions are executed by a processor, the transaction management method according to any one of claims 1 to 6 is implemented.