Transaction processing method and equipment

Abstract

The invention provides a transaction processing method and device, relates to the technical field of big data, and is applied to a transaction processing system, the transaction processing system comprises a business device and a transaction center device, and the method comprises the following steps: the business device sends a first transaction execution request to the transaction center device, the first transaction execution request carries a first transaction identifier of the first transaction; the transaction center equipment adds the first transaction identifier into a transaction reconciliation table; the transaction center device obtains a first execution result of the first transaction and adds the execution result of the first transaction into the transaction reconciliation table, and the first transaction identifier and the first execution result are correspondingly recorded in the transaction reconciliation table. Whenever the transaction reconciliation condition is met, the transaction center equipment compares the transaction identifier in the transaction reconciliation table with the corresponding execution result to determine whether the transaction which is missed to be processed exists or not. By adopting the method and the device, missed transactions can be found in time.

Description

Technical Field

[0001] This application relates to the field of big data technology, and in particular to a method and apparatus for transaction processing. Background Technology

[0002] In the Internet of Things (IoT) field, business systems typically treat actions to be performed as transactions, place them in a transaction queue, and process each transaction in the queue in a round-robin fashion. For example, updating song charts, closing unpaid orders, and scheduling playlist releases can all be performed as transactions in the transaction queue.

[0003] However, in current transaction processing systems, transaction consistency processing is only performed after a transaction fails. If a transaction is missed for some reason, the transaction processing system will not be aware of it. In this case, business problems may occur, and it will be impossible to locate which transaction caused the problem. Summary of the Invention

[0004] This application provides a method and apparatus for transaction processing, which can promptly detect missed transactions for subsequent problem localization. The technical solution is as follows: Firstly, a transaction processing method is provided, the method being applied to a transaction processing system, the transaction processing system including business equipment and transaction center equipment, the method comprising: The service device sends a first transaction execution request to the transaction center device, wherein the first transaction execution request carries a first transaction identifier of the first transaction; The transaction center device adds the first transaction identifier to the transaction reconciliation table; The transaction center device obtains the first execution result of the first transaction and adds the execution result of the first transaction to the transaction reconciliation table, wherein the first transaction identifier and the first execution result are recorded in the transaction reconciliation table. Whenever the transaction reconciliation conditions are met, the transaction center compares the transaction identifiers and corresponding execution results in the transaction reconciliation table to determine whether there are any missed transactions.

[0005] In one possible implementation, whenever the transaction reconciliation conditions are met, the transaction center compares the transaction identifier and the corresponding execution result in the transaction reconciliation table, including: Every specified period of time, the transaction center determines whether the transaction reconciliation conditions are met, and compares the newly added transaction identifiers and corresponding execution results in the transaction reconciliation table within the specified period of time.

[0006] In a possible implementation, the transaction center compares the transaction identifier and the corresponding execution result in the transaction account table to determine whether there is a missed transaction, including: If the second transaction identifier is recorded in the transaction account table and the corresponding execution result of the second transaction identifier is not recorded, it is determined that the transaction corresponding to the second transaction identifier is a missed transaction.

[0007] In a possible implementation, after the business device sends the first transaction execution request to the transaction center device, the method further includes: The transaction center device adds the first transaction to a distributed time wheel as a to-be-executed transaction according to the execution time of the first transaction; The business device sends a transaction query request to the transaction center; The transaction center device queries a target to-be-executed transaction that reaches the execution time in the distributed time wheel, and sends a transaction execution instruction for the target to-be-executed transaction to the business device; The business device executes the target to-be-executed transaction; The transaction center device obtains the first execution result of the first transaction, including: After the business device executes the first transaction, the business device sends the first execution result of the first transaction to the transaction center device, and the first execution result is execution success or execution failure.

[0008] In a possible implementation, the transaction processing system further includes a management device, and the method further includes: If the transaction center determines that there is a missed transaction, the transaction center sends a transaction exception message to the management device, and the transaction exception message carries the transaction identifier of the missed transaction.

[0009] In a second aspect, a transaction processing method is provided, and the method is applied to a transaction center device in a transaction processing system, the transaction processing system further includes a business device, and the method includes: Receiving a first transaction execution request sent by the business device, wherein the first transaction execution request carries a first transaction identifier of a first transaction; Adding the first transaction identifier to a transaction account table; Obtaining a first execution result of the first transaction, and adding the execution result of the first transaction to the transaction account table, wherein the first transaction identifier and the first execution result are recorded in the transaction account table.

[0010] When a transaction reconciliation condition is met, transaction identifiers in the transaction reconciliation table and corresponding execution results are compared to determine whether there is a missed transaction.

[0011] In a possible implementation, the comparing, when the transaction reconciliation condition is met, the transaction identifiers in the transaction reconciliation table and the corresponding execution results includes: Every specified time length, it is determined that the transaction reconciliation condition is met, and the newly added transaction identifiers and the corresponding execution results in the transaction reconciliation table within the specified time length are compared.

[0012] In a possible implementation, the comparing, when the transaction reconciliation condition is met, the transaction identifiers in the transaction reconciliation table and the corresponding execution results includes: If the second transaction identifier is recorded in the transaction reconciliation table, and the corresponding execution result of the second transaction identifier is not recorded, it is determined that the transaction corresponding to the second transaction identifier is a missed transaction.

[0013] In a possible implementation, the transaction processing system further includes a management device, and the method further includes: If it is determined that there is a missed transaction, a transaction exception message is sent to the management device, and the transaction identifier of the missed transaction is carried in the transaction exception message.

[0014] In a third aspect, a transaction processing apparatus is provided, which is applied to a transaction center device in a transaction processing system, and the transaction processing system further includes a business device, and the apparatus includes: A receiving module is configured to receive a first transaction execution request sent by the business device, and the first transaction execution request carries a first transaction identifier of a first transaction. An adding module is configured to add the first transaction identifier to a transaction reconciliation table. An obtaining module is configured to obtain a first execution result of the first transaction, and add the execution result of the first transaction to the transaction reconciliation table, and the first transaction identifier and the first execution result are recorded correspondingly in the transaction reconciliation table. A reconciliation module is configured to compare transaction identifiers in the transaction reconciliation table and corresponding execution results when a transaction reconciliation condition is met, to determine whether there is a missed transaction.

[0015] In a possible implementation, the reconciliation module is configured to: Every specified time length, it is determined that the transaction reconciliation condition is met, and the newly added transaction identifiers and the corresponding execution results in the transaction reconciliation table within the specified time length are compared.

[0016] In a possible implementation, the transaction checking module is configured to: If the second transaction identifier is recorded in the transaction checking table and the execution result corresponding to the second transaction identifier is not recorded, it is determined that the transaction corresponding to the second transaction identifier is a missed transaction.

[0017] In a possible implementation, the transaction processing system further includes a management device, and the apparatus further includes a sending module configured to: If it is determined that there is a missed transaction, a transaction exception message is sent to the management device, and the transaction identifier of the missed transaction is carried in the transaction exception message.

[0018] In a fourth aspect, a business device is provided, which includes a processor and a memory, and the memory stores at least one instruction, which is loaded and executed by the processor to implement the operation performed by the business device in the method of audio processing according to the first aspect and any possible implementation thereof.

[0019] In a fifth aspect, a transaction center device is provided, which includes a processor and a memory, and the memory stores at least one instruction, which is loaded and executed by the processor to implement the operation performed by the transaction center device in the method of audio processing according to the first aspect, the second aspect and any possible implementation thereof.

[0020] In a sixth aspect, a computer readable storage medium is provided, which stores at least one instruction, which is loaded and executed by a processor to implement the operation performed in the method of transaction processing according to the first aspect, the second aspect and any possible implementation thereof.

[0021] In a seventh aspect, a computer program product is provided, which stores at least one instruction, which is loaded and executed by a processor to implement the operation performed in the method of transaction processing according to the first aspect, the second aspect and any possible implementation thereof.

[0022] The technical scheme provided in the application has the beneficial effects that: In the technical solutions provided in the present application, when the business device is triggered to execute a first transaction, the business device can send a first transaction execution request to the transaction center device, the first transaction execution request carrying a first transaction identifier of the first transaction, and then the transaction center device adds the first transaction identifier to a transaction reconciliation table, in addition, the transaction center device also acquires a first execution result of the first transaction and adds the execution result of the first transaction to the transaction reconciliation table, the first transaction identifier and the first execution result being recorded in the transaction reconciliation table. On this basis, the transaction center compares the transaction identifiers and the corresponding execution results in the transaction reconciliation table whenever the transaction reconciliation condition is met, if there is a transaction identifier but no corresponding execution result, it means that the transaction may be missed, thus, through the above transaction reconciliation table recording mechanism and the transaction reconciliation table comparison mechanism, it can be found whether there is a missed transaction in time, so as to locate the problem when the subsequent business problem occurs. BRIEF DESCRIPTION OF DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed in the embodiment description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0024] Figure 1 is a transaction processing method provided by an embodiment of the present application; Figure 2 is a transaction processing method flowchart provided by an embodiment of the present application; Figure 3 is a transaction processing device structure schematic diagram provided by an embodiment of the present application; Figure 4 is a computer device structure schematic diagram provided by an embodiment of the present application. DETAILED DESCRIPTION

[0025] In order to make the purpose, technical solutions and advantages of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the drawings.

[0026] In the Internet of Things (IoT) field, business systems typically treat actions to be performed as transactions, placing them in a transaction queue and processing each transaction in the queue in a round-robin fashion. For example, updating song charts, closing unpaid orders, and scheduled playlist publishing can all be executed as transactions in the transaction queue. However, current transaction processing systems only perform consistency checks after a transaction fails. If a transaction is missed for some reason, the system is unaware of this. In such cases, business operations may encounter problems, and it may be impossible to pinpoint which transaction caused the issue.

[0027] Based on this, embodiments of this application provide a transaction processing method, which can be implemented by a transaction processing system. The transaction processing system includes business devices and transaction center devices, wherein both business devices and transaction center devices can be computer devices, and they can be the same device or different devices. Both can be deployed as single devices or in a cluster. Embodiments of this application do not limit this.

[0028] like Figure 1 As shown in the transaction processing method provided in this application embodiment, when a business device is triggered to execute a first transaction, it can send a first transaction execution request to the transaction center device. The first transaction execution request carries the first transaction identifier of the first transaction. Then, the transaction center device adds the first transaction identifier to the transaction reconciliation table. In addition, the transaction center device also obtains the first execution result of the first transaction and adds the first execution result of the first transaction to the transaction reconciliation table. The first transaction identifier and the first execution result are recorded correspondingly in the transaction reconciliation table. Here, the first transaction is any transaction of the business system. Based on this, whenever the transaction reconciliation conditions are met, the transaction center compares the transaction identifier and the corresponding execution result in the transaction reconciliation table. If there is a transaction identifier but no corresponding execution result, it means that the transaction may have been missed. In this way, through the above recording mechanism and comparison mechanism of the transaction reconciliation table, it is possible to promptly detect whether there are any missed transactions, so as to locate the problem when subsequent business problems occur.

[0029] The transaction processing method provided in the embodiments of this application will be described below with reference to the accompanying drawings. See also Figure 2 The processing flow of this method may include the following steps: Step 201: The business device sends the first transaction execution request to the transaction center device.

[0030] The first transaction execution request carries the first transaction identifier of the first transaction, and the first transaction is any transaction that the business device needs to execute.

[0031] In implementation, the conditions that trigger the business device to send the corresponding transaction execution request to the transaction center device may differ for different types of transactions. The following example, using the update of the karaoke app's leaderboard, illustrates step 201: For example, a music application might display daily, weekly, and overall leaderboards for music users. Each update to the daily leaderboard is a transaction, each update to the weekly leaderboard is a transaction, and each update to the overall leaderboard is also a transaction. The rankings in the music user leaderboards are determined by the amount of virtual gifts each user receives. For the daily leaderboard, the more virtual gifts a user receives that day, the higher their ranking. For the weekly leaderboard, the more virtual gifts a user receives that week, the higher their ranking. For the overall leaderboard, the more virtual gifts a user receives in total, the higher their ranking. User A can open a karaoke application on a terminal and enter User B's live stream. User A sends a virtual gift of value (first value) to User B in User B's live stream. The terminal then sends a virtual gift request to the service device. Upon receiving the request, the service device generates three transaction flows: one for updating the daily ranking, one for updating the weekly ranking, and one for updating the overall ranking. Each of these three transactions can be the first transaction mentioned above. For each first transaction, the service device sends a transaction execution request to the transaction center. This request can carry information such as the first transaction identifier, the execution time, and the data required to execute the first transaction. The first transaction identifier can be a globally unique identifier (Identity Document, ID) assigned when the transaction flow for that first transaction was generated, and the execution time indicates when the first transaction should be executed.

[0032] Step 202: The transaction center device adds the first transaction identifier to the transaction reconciliation table.

[0033] In implementation, after receiving the first transaction execution request from the business device, the transaction center device records the first transaction in the distributed time wheel as a transaction to be executed, based on the execution time of the first transaction. In addition, the transaction center device also records the first transaction identifier in the transaction reconciliation table.

[0034] Step 203: The transaction center device obtains the first execution result of the first transaction and adds the execution result of the first transaction to the transaction reconciliation table.

[0035] The first transaction identifier and the first execution result are recorded in the transaction reconciliation table.

[0036] In implementation, the device actually executing the transaction is a business device, and the business device can acquire the to-be-executed transaction in various manners, and two manners are exemplarily listed below for description: Manner one: push mode For each to-be-executed transaction recorded in the distributed time wheel, the transaction center device can send a transaction execution instruction to the business device when the execution time of the to-be-executed transaction is reached, and the transaction execution instruction can carry the transaction identifier of the to-be-executed transaction and the data required for executing the to-be-executed transaction. After receiving the transaction execution instruction, the business device executes the to-be-executed transaction according to the data required for executing the to-be-executed transaction carried in the transaction execution instruction.

[0037] If the business device executes the to-be-executed transaction successfully, the business device sends a first transaction execution response to the transaction center device, wherein the first transaction execution response carries the transaction identifier of the to-be-executed transaction and execution success indication information, and the execution success indication information is used to indicate that the transaction is executed successfully. Correspondingly, after receiving the first transaction execution response, if the transaction center device determines that the first transaction execution response carries the execution success indication information, the transaction center device deletes the to-be-executed transaction in the distributed time wheel, and records the execution result of the to-be-executed transaction as execution success in the transaction account table, for example, 1 can be recorded as execution success, and the transaction identifier and the execution result of the same transaction are correspondingly recorded in the transaction account table.

[0038] If the business device executes the to-be-executed transaction unsuccessfully, the business device sends a second transaction execution response to the transaction center device, wherein the second transaction execution response carries the transaction identifier of the to-be-executed transaction and execution failure indication information, and the execution failure indication information is used to indicate that the transaction is executed unsuccessfully. Correspondingly, after receiving the second transaction execution response, if the transaction center device determines that the second transaction execution response carries the execution failure indication information, the transaction center device adds one to the execution failure number of the to-be-executed transaction. If the execution failure number of the to-be-executed transaction is added by one and reaches a specified threshold, the transaction center device adds the to-be-executed transaction to the dead letter queue, and records the execution result of the to-be-executed transaction as execution failure and addition to the dead letter queue in the transaction account table, for example, 0 can be recorded as execution failure and addition to the dead letter queue. If the execution failure number of the to-be-executed transaction is added by one and does not reach the specified threshold, the transaction center device updates the execution time of the to-be-executed transaction in the distributed time wheel according to a preset delay rule, and waits for subsequent re-execution.

[0039] The transaction account table can be as shown in Table 1 below: Table 1

[0040] In the above Table 1, the transaction with the transaction identifier ID1 has the execution result of "1", indicating that the execution result of the transaction is execution success; the transaction with the transaction identifier ID2 has the execution result of "0", indicating that the execution result of the transaction is execution failure and joining the dead letter queue; and the transaction with the transaction identifier ID3 has no execution result, indicating that the transaction has not been executed, or has not been executed completely, or has failed to execute but has not joined the dead letter queue.

[0041] Mode two: pull mode The business device can send a transaction query request to the transaction center device in a polling manner. After receiving the transaction query request, the transaction center device queries whether there is a to-be-executed transaction reaching the execution time in the distributed time wheel. If there is a to-be-executed transaction reaching the execution time, the transaction center device sends a transaction execution instruction for the to-be-executed transaction to the business device. The transaction execution instruction can carry the transaction identifier of the to-be-executed transaction and the data required for executing the to-be-executed transaction. After receiving the transaction execution instruction, the business device executes the to-be-executed transaction according to the data required for executing the to-be-executed transaction carried in the transaction execution instruction.

[0042] If the business device successfully executes the to-be-executed transaction, the business device sends a first transaction execution response to the transaction center device. The first transaction execution response carries the transaction identifier of the to-be-executed transaction and execution success indication information. The execution success indication information is used to indicate that the transaction execution is successful. Correspondingly, after receiving the first transaction execution response, if the transaction center device determines that the first transaction execution response carries the execution success indication information, the transaction center device deletes the to-be-executed transaction in the distributed time wheel, and records the execution result of the to-be-executed transaction as execution success in the transaction account table. For example, the execution success can be recorded as 1. The transaction identifier and the execution result of the same transaction correspond to the records in the transaction account table.

[0043] If the business device fails to execute the to-be-executed transaction, the business device sends a second transaction execution response to the transaction center device. The second transaction execution response carries the transaction identifier of the to-be-executed transaction and execution failure indication information. The execution failure indication information is used to indicate that the transaction execution is failed. Correspondingly, after receiving the second transaction execution response, if the transaction center device determines that the second transaction execution response carries the execution failure indication information, the transaction center device adds one to the execution failure number of the to-be-executed transaction. If the execution failure number of the to-be-executed transaction is added by one and reaches a specified threshold, the transaction center device adds the to-be-executed transaction to the dead letter queue, and records the execution result of the to-be-executed transaction as execution failure and joining the dead letter queue in the transaction account table. For example, the execution failure and joining the dead letter queue can be recorded as 0. If the execution failure number of the to-be-executed transaction is added by one and does not reach the specified threshold, the transaction center device updates the execution time of the to-be-executed transaction in the distributed time wheel according to a preset delay rule, and waits for subsequent execution again.

[0044] Step 204, whenever the transaction reconciliation condition is met, the transaction center compares the transaction identifier and the corresponding execution result in the transaction reconciliation table to determine whether there is a missed transaction.

[0045] In implementation, the transaction reconciliation condition can be various, and the following examples are listed for illustration: Transaction reconciliation condition one: After the second transaction identifier of the second transaction is newly added in the transaction reconciliation table, the transaction center device can perform transaction reconciliation timing for the second transaction. When the transaction reconciliation timing reaches the first duration, it is determined that the transaction reconciliation condition is met. The transaction center device then queries the transaction reconciliation table to determine whether the execution result corresponding to the second transaction identifier is recorded. If the execution result corresponding to the second transaction identifier is recorded in the transaction reconciliation table, it is determined that the second transaction is reconciled. If the execution result corresponding to the second transaction identifier is not recorded in the transaction reconciliation table, it is determined that the second transaction is a missed transaction.

[0046] The second transaction is any transaction, and the first duration is the maximum execution duration of the second transaction. The maximum duration of the second transaction refers to the sum of the duration between the time when the second transaction identifier is added to the transaction reconciliation table and the execution time of the second transaction and the maximum duration of possible failure retries of the second transaction. The maximum duration of possible failure retries of the second transaction refers to the maximum duration required from the first execution of the second transaction to the end of the specified threshold number of executions. This duration can be an estimated value configured by relevant personnel according to the transaction type, and the maximum execution duration corresponding to different transaction types can be different. Specifically, the transaction center device can first determine the target transaction type to which the second transaction belongs, and then determine the maximum duration corresponding to the target transaction type in the stored correspondence between transaction types and maximum durations, as the maximum duration of possible failure retries of the second transaction.

[0047] Transaction reconciliation condition two: The transaction center determines that the transaction reconciliation condition is met every specified duration, and compares each transaction identifier and the corresponding execution result newly added (newly added) in the transaction reconciliation table within the specified duration. If the third transaction identifier is recorded in the transaction reconciliation table and the execution result corresponding to the third transaction identifier is not recorded, it is determined that the transaction corresponding to the second transaction identifier is a missed transaction. If the execution result corresponding to the third transaction identifier is recorded in the transaction reconciliation table, it is determined that the second transaction is reconciled. The third transaction identifier is any transaction identifier newly added in the transaction reconciliation table within the specified duration, and the specified duration can be configured by relevant personnel, for example, the specified duration is 5 minutes.

[0048] In addition, the audit table of the transaction affairs can record the execution result of the third transaction identification in multiple cases, for example, the transaction corresponding to the third transaction identification has not reached the execution time, or the transaction corresponding to the third transaction identification has not been executed, or the transaction corresponding to the third transaction identification has failed but has not been added to the dead letter queue, or the transaction corresponding to the third transaction identification is missed. Among these possible cases, only the case that the transaction corresponding to the third transaction identification is missed is an abnormal case. Therefore, in order to avoid misjudgment, the following mechanism can be added: If the transaction audit table records the third transaction identification and does not record the execution result corresponding to the third transaction identification, it is determined whether the audit duration of the transaction corresponding to the third transaction identification reaches the second duration. If the audit duration of the transaction corresponding to the third transaction identification reaches the second duration, it is determined that the transaction corresponding to the third transaction identification is a missed transaction. If the audit duration of the transaction corresponding to the third transaction identification does not reach the second duration, the transaction audit table is queried again after the audit duration of the transaction corresponding to the third transaction identification reaches the second duration. If the execution result corresponding to the third transaction identification is still not recorded, it is determined that the transaction corresponding to the third transaction identification is a missed transaction.

[0049] The above audit duration is the duration between the time when the third transaction identification is added to the transaction audit table and the current time. The second duration is the maximum execution duration of the transaction corresponding to the third transaction identification. The maximum execution duration of the transaction corresponding to the third transaction identification refers to the sum of the duration between the time when the third transaction identification is added to the transaction audit table and the execution time of the transaction corresponding to the third transaction identification and the maximum duration of possible failure retries of the transaction corresponding to the third transaction identification. The maximum duration of possible failure retries of the transaction corresponding to the third transaction identification refers to the maximum duration required from the first execution of the transaction to the end of the specified threshold number of executions. This duration can be a preset value configured by relevant personnel according to the transaction type, and the maximum execution duration corresponding to different transaction types can be different. Specifically, the transaction center device can first determine the target transaction type to which the transaction corresponding to the third transaction identification belongs, and then determine the maximum duration corresponding to the target transaction type in the stored correspondence between transaction types and maximum durations, as the maximum duration of possible failure retries of the transaction corresponding to the third transaction identification.

[0050] In addition, if the transaction center determines that there is a missed transaction, it can send a transaction exception message to the management device in the transaction processing system, and the transaction exception message carries the transaction identification of the missed transaction. Further, relevant personnel can know which transaction is abnormal through the management device and timely perform abnormal processing.

[0051] All the optional technical solutions described above can be combined to form optional embodiments of the present application, which will not be described again here.

[0052] In the transaction processing method provided by the embodiments of the present application, when triggered to execute a first transaction, the business device can send a first transaction execution request to the transaction center device, the first transaction execution request carrying a first transaction identifier of the first transaction, and then the transaction center device adds the first transaction identifier to a transaction reconciliation table, in addition, the transaction center device also acquires a first execution result of the first transaction and adds the first execution result of the first transaction to the transaction reconciliation table, the first transaction identifier and the first execution result being recorded in correspondence in the transaction reconciliation table, and the first transaction being any transaction of the business system. On this basis, the transaction center compares the transaction identifier and the corresponding execution result in the transaction reconciliation table whenever the transaction reconciliation condition is met, if there is a transaction identifier but no corresponding execution result, it means that the transaction may be missed, so that through the above recording mechanism of the transaction reconciliation table and the comparison mechanism of the transaction reconciliation table, it can be found whether there is a missed transaction in time, so as to locate the problem when the subsequent business problem occurs.

[0053] Based on the same technical concept, the embodiments of the present application also provide a transaction processing device, which is applied to a transaction center device in a transaction processing system, and the transaction processing system further includes a business device, as shown in Figure 3 The device includes a receiving module 310, an adding module 320, an acquiring module 330 and a reconciliation module 340, wherein: The receiving module 310 is configured to receive a first transaction execution request sent by the business device, wherein the first transaction execution request carries a first transaction identifier of a first transaction; The adding module 320 is configured to add the first transaction identifier to a transaction reconciliation table; The acquiring module 330 is configured to acquire a first execution result of the first transaction and add the execution result of the first transaction to the transaction reconciliation table, wherein the first transaction identifier and the first execution result are recorded in correspondence in the transaction reconciliation table.

[0054] The reconciliation module 340 is configured to compare the transaction identifier and the corresponding execution result in the transaction reconciliation table whenever a transaction reconciliation condition is met, and determine whether there is a missed transaction.

[0055] In a possible implementation, the reconciliation module 340 is configured to: Determine that the transaction reconciliation condition is met every specified time length, and compare the newly added transaction identifier and the corresponding execution result in the transaction reconciliation table within the specified time length.

[0056] In a possible implementation, the transaction reconciliation module 340 is configured to: If the second transaction identifier is recorded in the transaction reconciliation table, and the execution result corresponding to the second transaction identifier is not recorded, it is determined that the transaction corresponding to the second transaction identifier is a missed transaction.

[0057] In a possible implementation, the transaction processing system further includes a management device, and the apparatus further includes a sending module configured to: If it is determined that there is a missed transaction, a transaction exception message is sent to the management device, and the transaction exception message carries the transaction identifier of the missed transaction.

[0058] In the technical solutions provided in the present application, when the business device is triggered to execute a first transaction, the business device can send a first transaction execution request to the transaction center device, and the first transaction execution request carries a first transaction identifier of the first transaction. Then, the transaction center device adds the first transaction identifier to a transaction reconciliation table, and further acquires a first execution result of the first transaction and adds the execution result of the first transaction to the transaction reconciliation table. The first transaction identifier and the first execution result are recorded in the transaction reconciliation table. On this basis, the transaction center compares the transaction identifiers and the corresponding execution results in the transaction reconciliation table whenever the transaction reconciliation condition is met. If there is a transaction identifier but no corresponding execution result, it indicates that the transaction may be missed. Thus, through the recording mechanism of the transaction reconciliation table and the comparison mechanism of the transaction reconciliation table, it can be determined whether there is a missed transaction in time, so as to facilitate problem positioning when a subsequent business problem occurs.

[0059] It should be noted that the transaction processing apparatus provided in the above embodiments is only used as an example to illustrate the division of the above functional modules. In actual applications, the above functions can be completed by different functional modules according to needs, that is, the internal structure of the terminal device is divided into different functional modules to complete all or part of the above described functions. In addition, the transaction processing apparatus and the transaction processing method provided in the above embodiments belong to the same concept, and the specific implementation process is described in the method embodiments, which will not be repeated here.

[0060] Figure 4 A structural block diagram of a computer device 800 provided in an example embodiment of the present application is shown. The computer device 800 can be the business device, the transaction center device, or the management device.

[0061] Generally, the computer device 800 includes a processor 801 and a memory 802.

[0062] The processor 801 can include one or more processing cores, such as a 4-core processor, an 8-core processor, and the like. The processor 801 can be implemented in at least one of a hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), a PLA (Programmable Logic Array), and the like. The processor 801 can also include a main processor and a coprocessor, the main processor being a processor for processing data in an awake state, also referred to as a CPU (Central Processing Unit), and the coprocessor being a low-power processor for processing data in a standby state. In some embodiments, the processor 801 can be integrated with a GPU (Graphics Processing Unit) for rendering and drawing content required to be displayed by the display screen. In some embodiments, the processor 801 can further include an AI (Artificial Intelligence) processor for processing computing operations related to machine learning.

[0063] The memory 802 can include one or more computer-readable storage media that can be non-transitory. The memory 802 can also include a high-speed random access memory, and a nonvolatile memory such as one or more disk storage devices, flash storage devices. In some embodiments, the non-transitory computer-readable storage medium in the memory 802 is used to store at least one instruction for being executed by the processor 801 to implement the method of transaction processing provided by the method embodiments in the present application.

[0064] In some embodiments, the computer device 800 can also optionally include a peripheral device interface 803 and at least one peripheral device. The processor 801, the memory 802, and the peripheral device interface 803 can be connected through a bus or a signal line. Each peripheral device can be connected to the peripheral device interface 803 through a bus, a signal line, or a circuit board. Specifically, the peripheral device includes at least one of a radio frequency circuit 804, a display screen 805, a camera component 806, an audio circuit 807, a positioning component 808, and a power supply 809.

[0065] The peripheral interface 803 can be used to connect at least one I / O (Input / Output) related peripheral device to the processor 801 and the memory 802. In some embodiments, the processor 801, the memory 802 and the peripheral interface 803 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 801, the memory 802 and the peripheral interface 803 can be implemented on a separate chip or circuit board, and the present embodiments are not limited in this regard.

[0066] The radio frequency circuit 804 is used to receive and send RF (Radio Frequency) signals, also known as electromagnetic signals. The radio frequency circuit 804 communicates with a communication network and other communication devices through electromagnetic signals. The radio frequency circuit 804 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals into electrical signals. Optionally, the radio frequency circuit 804 includes an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and the like. The radio frequency circuit 804 can communicate with other terminals through at least one wireless communication protocol. The wireless communication protocol includes but is not limited to: the World Wide Web, a metropolitan area network, an intranet, various generations of mobile communication networks (2G, 3G, 4G and 5G), a wireless local area network and / or a WiFi (Wireless Fidelity) network. In some embodiments, the radio frequency circuit 804 can also include NFC (Near Field Communication) related circuitry, and the present application is not limited in this regard.

[0067] The display screen 805 is configured to display a UI (User Interface). The UI can include graphics, text, icons, video, and any combination thereof. When the display screen 805 is a touch display screen, the display screen 805 is further configured to capture touch signals on or above the surface of the display screen 805. The touch signals can be input to the processor 801 as control signals for processing. In this case, the display screen 805 can also be configured to provide virtual buttons and / or virtual keyboard, also known as soft buttons and / or soft keyboard. In some embodiments, the display screen 805 can be one, disposed on the front panel of the computer device 800; in other embodiments, the display screen 805 can be at least two, respectively disposed on different surfaces of the computer device 800 or in a folding design; in other embodiments, the display screen 805 can be a flexible display screen, disposed on a curved surface or a folding surface of the computer device 800. Even, the display screen 805 can also be disposed in an irregular shape, i.e., a special-shaped screen. The display screen 805 can be made of LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), etc.

[0068] The camera assembly 806 is configured to capture images or videos. Optionally, the camera assembly 806 includes a front camera and a rear camera. Typically, the front camera is disposed on the front panel of the terminal, and the rear camera is disposed on the back of the terminal. In some embodiments, the rear camera is at least two, which are any one of a main camera, a depth-of-field camera, a wide-angle camera, and a telephoto camera, to realize the background blur function by fusing the main camera and the depth-of-field camera, the panoramic shooting and VR (Virtual Reality) shooting function by fusing the main camera and the wide-angle camera, or other fusion shooting functions. In some embodiments, the camera assembly 806 can further include a flash. The flash can be a single-color-temperature flash or a dual-color-temperature flash. The dual-color-temperature flash refers to the combination of a warm light flash and a cold light flash, which can be used for light compensation under different color temperatures.

[0069] The audio circuit 807 can include a microphone and a speaker. The microphone is used to collect sound waves of a user and an environment, and convert the sound waves into an electrical signal input to the processor 801 for processing, or input to the radio frequency circuit 804 to realize voice communication. The microphone can be multiple for the purpose of stereo sound collection or noise reduction, and arranged at different parts of the computer device 800. The microphone can also be an array microphone or an omnidirectional collection microphone. The speaker is used to convert an electrical signal from the processor 801 or the radio frequency circuit 804 into sound waves. The speaker can be a conventional diaphragm speaker, or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can not only convert an electrical signal into a sound wave audible to humans, but also convert an electrical signal into an inaudible sound wave to humans for ranging purposes, etc. In some embodiments, the audio circuit 807 can also include a headphone jack.

[0070] The positioning component 808 is used to position the current geographic location of the computer device 800 to realize navigation or LBS (Location Based Service, location-based service). The positioning component 808 can be a GPS (Global Positioning System, global positioning system), Beidou system or Galileo system positioning component.

[0071] The power supply 809 is used to supply power to various components in the computer device 800. The power supply 809 can be alternating current, direct current, disposable battery or rechargeable battery. When the power supply 809 includes a rechargeable battery, the rechargeable battery can be a wired charging battery or a wireless charging battery. The wired charging battery is a battery charged through a wired line, and the wireless charging battery is a battery charged through a wireless coil. The rechargeable battery can also be used to support fast charging technology.

[0072] In some embodiments, the computer device 800 further includes one or more sensors 810. The one or more sensors 810 include but are not limited to: an acceleration sensor 811, a gyroscope sensor 812, a pressure sensor 813, a fingerprint sensor 814, an optical sensor 815 and a proximity sensor 816.

[0073] The acceleration sensor 811 can detect the acceleration in three coordinate axes of the coordinate system established by the computer device 800. For example, the acceleration sensor 811 can be used to detect the components of gravitational acceleration in three coordinate axes. The processor 801 can control the display screen 805 to display the user interface in a landscape view or a portrait view according to the gravitational acceleration signal collected by the acceleration sensor 811. The acceleration sensor 811 can also be used for gaming or user motion data collection.

[0074] The gyroscope sensor 812 can detect the body direction and rotation angle of the computer device 800, and the gyroscope sensor 812 can cooperate with the acceleration sensor 811 to collect the 3D action of the user on the computer device 800. According to the data collected by the gyroscope sensor 812, the processor 801 can realize the following functions: motion sensing (such as changing the UI according to the user's tilt operation), image stabilization when shooting, game control, and inertial navigation.

[0075] The pressure sensor 813 can be arranged on the side frame of the computer device 800 and / or the lower layer of the display screen 805. When the pressure sensor 813 is arranged on the side frame of the computer device 800, the user's holding signal on the computer device 800 can be detected, and the left and right hand recognition or shortcut operation can be performed by the processor 801 according to the holding signal collected by the pressure sensor 813. When the pressure sensor 813 is arranged on the lower layer of the display screen 805, the operable control on the UI interface can be controlled by the processor 801 according to the pressure operation of the user on the display screen 805. The operable control includes at least one of a button control, a scroll bar control, an icon control, and a menu control.

[0076] The fingerprint sensor 814 is used to collect the fingerprint of the user, and the identity of the user can be recognized by the processor 801 according to the fingerprint collected by the fingerprint sensor 814, or by the fingerprint sensor 814 according to the collected fingerprint. When the identity of the user is recognized as a trusted identity, the processor 801 authorizes the user to perform related sensitive operations, including unlocking the screen, viewing encrypted information, downloading software, payment, and changing settings. The fingerprint sensor 814 can be arranged on the front, back or side of the computer device 800. When the computer device 800 is provided with a physical button or a manufacturer's logo, the fingerprint sensor 814 can be integrated with the physical button or the manufacturer's logo.

[0077] The optical sensor 815 is used to collect the ambient light intensity. In one embodiment, the processor 801 can control the display brightness of the display screen 805 according to the ambient light intensity collected by the optical sensor 815. Specifically, when the ambient light intensity is high, the display brightness of the display screen 805 is increased; when the ambient light intensity is low, the display brightness of the display screen 805 is decreased. In another embodiment, the processor 801 can also dynamically adjust the shooting parameters of the camera assembly 806 according to the ambient light intensity collected by the optical sensor 815.

[0078] The proximity sensor 816, also referred to as a distance sensor, is usually arranged on the front panel of the computer device 800. The proximity sensor 816 is used to collect the distance between the user and the front of the computer device 800. In an embodiment, when the proximity sensor 816 detects that the distance between the user and the front of the computer device 800 gradually decreases, the display screen 805 is switched from the bright screen state to the screen-off state under the control of the processor 801; when the proximity sensor 816 detects that the distance between the user and the front of the computer device 800 gradually increases, the display screen 805 is switched from the screen-off state to the bright screen state under the control of the processor 801.

[0079] Those skilled in the art can understand that, Figure 4 The structure shown in the above embodiments does not constitute a limitation on the computer device 800, and can include more or fewer components than shown, or combine certain components, or adopt a different arrangement of components.

[0080] In an exemplary embodiment, a computer readable storage medium, such as a memory including instructions executable by a processor in a terminal to perform the method of transaction processing in the above embodiments, is also provided. The computer readable storage medium can be non-transitory. For example, the computer readable storage medium can be a ROM (Read-Only Memory), a RAM (Random Access Memory), a CD-ROM (Compact Disc Read-Only Memory), a magnetic tape, a floppy disk, an optical data storage device, etc.

[0081] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data for analysis, stored data, displayed data, etc.) and signals (including but not limited to signals transmitted between user terminals and other devices, etc.) involved in the present application are all authorized by the user or fully authorized by all parties, and the collection, use and processing of related data need to comply with relevant laws, regulations and standards of relevant countries and regions. For example, all audio, text, song information, etc. involved in the present application are obtained under full authorization.

[0082] Those of ordinary skill in the art can understand that all or part of the steps of the above embodiments can be completed by hardware, or by a program instructing related hardware, and the program can be stored in a computer readable storage medium, and the storage medium mentioned above can be a read-only memory, a magnetic disk or an optical disk, etc.

[0083] It should be understood that "multiple" mentioned herein refers to two or more than two. The "and / or" describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent the following three cases: A exists alone, A and B exist together, and B exists alone. The character " / " generally represents that the associated objects before and after it are in an "or" relationship. In addition, the step numbers described herein only exemplarily show a possible execution order between steps, and in some other embodiments, the above steps can also be executed in a non-numbered order, such as two different numbered steps being executed at the same time, or two different numbered steps being executed in an order opposite to that shown in the figure, and the embodiments of the present application are not limited in this regard.

[0084] The above only describes optional embodiments of the present application and is not intended to limit the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A transaction processing method, characterized in that, The method is applied to a transaction processing system, which includes business equipment and transaction center equipment, and the method includes: The service device sends a first transaction execution request to the transaction center device, wherein the first transaction execution request carries a first transaction identifier of the first transaction; The transaction center device adds the first transaction identifier to the transaction reconciliation table; The transaction center device obtains the first execution result of the first transaction and adds the execution result of the first transaction to the transaction reconciliation table, wherein the first transaction identifier and the first execution result are recorded in the transaction reconciliation table. Whenever the transaction reconciliation conditions are met, the transaction center device compares the transaction identifier and the corresponding execution result in the transaction reconciliation table to determine whether there are any missed transactions.

2. The method according to claim 1, characterized in that, Whenever the transaction reconciliation conditions are met, the transaction center device compares the transaction identifier and the corresponding execution result in the transaction reconciliation table, including: Every specified period of time, the transaction center device determines whether the transaction reconciliation conditions are met, and compares the newly added transaction identifiers and corresponding execution results in the transaction reconciliation table within the specified period of time.

3. The method according to claim 1, characterized in that, The transaction center device compares the transaction identifiers and corresponding execution results in the transaction reconciliation table to determine whether any transactions have been missed, including: If the transaction reconciliation table records a second transaction identifier but does not record the execution result corresponding to the second transaction identifier, then the transaction corresponding to the second transaction identifier is determined to be a missed transaction.

4. The method according to claim 1, characterized in that, After the service device sends the first transaction execution request to the transaction center device, the method further includes: The transaction center device adds the first transaction to the distributed time wheel as a transaction to be executed based on the execution time of the first transaction; The business device sends a transaction query request to the transaction center device; The transaction center device queries the target pending transactions that have reached their execution time in the distributed time wheel, and sends a transaction execution instruction to the business device for the target pending transactions; The service device executes the target transaction to be executed; The transaction center device obtains the first execution result of the first transaction, including: After completing the first transaction, the business device sends the first execution result of the first transaction to the transaction center device. The first execution result is either successful or unsuccessful.

5. The method according to any one of claims 1-4, characterized in that, The transaction processing system further includes a management device, and the method further includes: If the transaction center device determines that there is a missed transaction, it sends a transaction exception message to the management device, and the transaction exception message carries the transaction identifier of the missed transaction.

6. A transaction processing method, characterized in that, The method is applied to a transaction center device in a transaction processing system, the transaction processing system further including business devices, and the method includes: Receive a first transaction execution request sent by the service device, wherein the first transaction execution request carries a first transaction identifier of the first transaction; Add the first transaction identifier to the transaction reconciliation table; Obtain the first execution result of the first transaction and add the execution result of the first transaction to the transaction reconciliation table, wherein the first transaction identifier and the first execution result are recorded in the transaction reconciliation table. Whenever the transaction reconciliation conditions are met, the transaction identifiers and corresponding execution results in the transaction reconciliation table are compared to determine whether any transactions have been missed.

7. A transaction center device, characterized in that, The transaction center device includes a processor and a memory, the memory storing at least one instruction, which is loaded and executed by the processor to perform the operation performed by the transaction center device in the transaction processing method as described in any one of claims 1-6.

8. A business equipment, characterized in that, The service device includes a processor and a memory, the memory storing at least one instruction, which is loaded and executed by the processor to implement the operation performed by the service device in the transaction processing method as described in any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The storage medium stores at least one instruction, which is loaded and executed by a processor to perform the operation performed by the transaction processing method as described in any one of claims 1-6.

10. A computer program product, characterized in that, The computer program product stores at least one instruction, which is loaded and executed by a processor to perform the operation performed by the transaction processing method as described in any one of claims 1-6.

Images