CN110992188A - Transaction processing method, device and equipment - Google Patents

Abstract

The embodiment of the specification provides a transaction processing method, a device and equipment, wherein the method comprises the following steps: receiving a transaction canceling request sent by a transaction platform; the transaction canceling request is a request sent to a management user by a transaction platform when at least one transaction element is determined to be failed to be locked after a transaction element locking request is sent to the management user of each transaction element associated with the transaction request based on a transaction request sent by a transaction request user; determining whether a transaction element locking request associated with the transaction identifier in the transaction cancellation request is received; if not, generating null transaction record information according to the transaction identifier, and storing the null transaction record information into the block chain.

Description

Transaction processing method, device and equipment

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a transaction processing method, apparatus, and device.

Background

With the continuous development of internet technology, online shopping has been widely entered into people's lives with the characteristics of convenience, time saving, labor saving and the like. In order to promote the enthusiasm of online shopping of users, some merchants also put forward shopping strategies such as red packages and points, so that one successful online shopping, namely one successful transaction, involves data management operations of multiple levels such as inventory updating, red package management and point increase and decrease, and each data management operation is equivalent to multiple parallel sub-transactions in distributed transactions. However, for the distributed transaction, the sub-transaction may cause an abnormal receiving sequence of the data sent by the upper layer due to network failure and other factors, thereby causing data processing failure and possibly triggering some unnecessary operations, which also exists in the transaction of online shopping.

Disclosure of Invention

One or more embodiments of the present specification provide a transaction processing method. The method comprises the step of receiving a transaction cancellation request sent by a transaction platform. The transaction canceling request is a request sent to a management user by the transaction platform when it is determined that locking of at least one transaction element fails after a transaction element locking request is sent to the management user of each transaction element associated with the transaction request based on a transaction request sent by a transaction request user. Wherein the transaction cancellation request includes a transaction identification. Determining whether the transaction element lock request associated with the transaction identification is received. If not, generating null transaction record information according to the transaction identifier, and storing the null transaction record information into the block chain.

One or more embodiments of the present specification provide a transaction processing device. The device comprises a receiving module which receives a transaction cancellation request sent by a transaction platform. The transaction canceling request is a request sent to a management user by the transaction platform when it is determined that locking of at least one transaction element fails after a transaction element locking request is sent to the management user of each transaction element associated with the transaction request based on a transaction request sent by a transaction request user. Wherein the transaction cancellation request includes a transaction identification. The apparatus also includes a first determination module that determines whether the transaction element lock request associated with the transaction identification is received. The device also comprises a generating module, if the determination result of the first determining module is negative, generating empty transaction record information according to the transaction identifier, and storing the empty transaction record information into the block chain.

One or more embodiments of the present specification provide a transaction processing device. The apparatus includes a processor. The apparatus also comprises a memory arranged to store computer executable instructions. The computer-executable instructions, when executed, receive a transaction cancellation request sent by a transaction platform. The transaction canceling request is a request sent to a management user by the transaction platform when it is determined that locking of at least one transaction element fails after a transaction element locking request is sent to the management user of each transaction element associated with the transaction request based on a transaction request sent by a transaction request user. Wherein the transaction cancellation request includes a transaction identification. Determining whether the transaction element lock request associated with the transaction identification is received. If not, generating null transaction record information according to the transaction identifier, and storing the null transaction record information into the block chain.

One or more embodiments of the present specification provide a storage medium. The storage medium is used to store computer-executable instructions. The computer-executable instructions, when executed, receive a transaction cancellation request sent by a transaction platform. The transaction canceling request is a request sent to a management user by the transaction platform when it is determined that locking of at least one transaction element fails after a transaction element locking request is sent to the management user of each transaction element associated with the transaction request based on a transaction request sent by a transaction request user. Wherein the transaction cancellation request includes a transaction identification. Determining whether the transaction element lock request associated with the transaction identification is received. If not, generating null transaction record information according to the transaction identifier, and storing the null transaction record information into the block chain.

Drawings

In order to more clearly illustrate one or more embodiments or prior art solutions of the present specification, the drawings that are needed in the description of the embodiments or prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and that other drawings can be obtained by those skilled in the art without inventive exercise.

Fig. 1 is a schematic diagram of a first scenario of a transaction processing method according to one or more embodiments of the present disclosure;

fig. 2 is a schematic diagram of a second scenario of a transaction processing method according to one or more embodiments of the present disclosure;

FIG. 3 provides a first schematic flow chart of a transaction processing method according to one or more embodiments of the present disclosure;

FIG. 4 provides a second flowchart of a transaction processing method according to one or more embodiments of the disclosure;

FIG. 5 provides a third flowchart of a transaction processing method according to one or more embodiments of the disclosure;

FIG. 6 provides a fourth flowchart of a transaction processing method according to one or more embodiments of the disclosure;

FIG. 7 is a detailed diagram of step S114 provided in one or more embodiments of the present description;

FIG. 8 is a block diagram of a transaction processing device according to one or more embodiments of the present disclosure;

fig. 9 is a schematic structural diagram of a transaction processing device according to one or more embodiments of the present disclosure.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present disclosure, the technical solutions in one or more embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in one or more embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments. All other embodiments that can be derived by a person skilled in the art from one or more of the embodiments described herein without making any inventive step shall fall within the scope of protection of this document.

Fig. 1 is a schematic view of an application scenario of a transaction processing method according to one or more embodiments of the present specification, and as shown in fig. 1, the application scenario includes: the method comprises the steps that a first terminal device of a management user, a second terminal device of a transaction request user, a transaction platform and a block chain of at least one transaction element related to transaction are obtained; the first terminal device and the second terminal device may be a mobile phone, a tablet computer, a desktop computer, a portable notebook computer, etc. (not all shown in fig. 1); the first terminal equipment and the second terminal equipment are in communication connection with the trading platform through a wireless network. For convenience of description, the first terminal device is denoted as a first terminal device 1, a first terminal device 2 …, and a first terminal device N, where N is a positive integer.

Specifically, the second terminal device responds to the transaction operation of the transaction request user and sends a transaction request to the transaction platform; the transaction platform determines transaction elements related to the transaction according to the received transaction requests, and respectively sends transaction element locking requests to the first terminal device 1, the second terminal device 2 … and the first terminal device N of the management user of the corresponding transaction elements, and if at least one transaction element is determined to be locked unsuccessfully, sends a transaction cancellation request to the first terminal device of each management user; as an example, because the transaction element locking request sent by the transaction platform to the first terminal device 1 is blocked due to a network failure, when the first terminal device 2 has sent the locking failure information of the transaction element to the transaction platform, and further the transaction platform has sent the transaction cancellation request to each first terminal device, the first terminal device 1 has received the transaction element cancellation request under the condition that the transaction element locking request has not been received yet, that is, the reception of the request data is abnormal; in order to avoid unnecessary processing caused by abnormal reception of the request data, when the first terminal device receives the transaction cancellation request, whether a transaction element locking request associated with the transaction identifier in the transaction cancellation request is received or not is determined, and when the determination result is negative, empty transaction record information is generated according to the transaction identifier and stored in the blockchain.

Further, in one or more embodiments of the present specification, as shown in fig. 2, an application scenario diagram of the transaction processing method may further include a block link point accessing the block chain, and after generating the null transaction record information, the first terminal device sends the null transaction record information to the block link point, so that the null transaction record information is stored in the block chain through the block link point.

Therefore, when the first terminal equipment of the management user of the transaction element related to the transaction receives a transaction cancellation request sent by the transaction platform, the first terminal equipment can effectively identify request receiving abnormity caused by network faults and other factors by determining whether the related transaction element locking request is received or not; when the abnormity is identified, the empty transaction record information is stored in the block chain, so that an effective abnormity verification basis can be provided for the subsequent receiving of a corresponding transaction element locking request, and useless transaction element locking operation and other operations triggered by the transaction element locking operation are avoided; furthermore, when the transaction platform receives the transaction request, the transaction elements related to the transaction are firstly locked rather than directly processed, so that the transaction failure caused by the fact that a certain transaction element does not meet the transaction condition can be effectively avoided.

Based on the application scenario architecture, one or more embodiments of the present specification provide a transaction processing method. Fig. 3 is a flowchart of a transaction processing method according to one or more embodiments of the present disclosure, where the method in fig. 3 can be executed by the first terminal device in fig. 1, as shown in fig. 3, and the method includes the following steps:

step S102, receiving a transaction cancellation request sent by a transaction platform; the transaction canceling request is a request sent to a management user by a transaction platform when at least one transaction element is determined to be failed to be locked after a transaction element locking request is sent to the management user of each transaction element associated with the transaction request based on a transaction request sent by a transaction request user; wherein the transaction cancellation request includes a transaction identification;

specifically, considering the current successful forward transaction, there are many data management operations at multiple levels, such as stock update, red pack management, and point increase and decrease. In order to avoid a transaction failure caused by failure of data management operations of one or more layers, in one or more embodiments of the present specification, when a transaction platform receives a transaction request sent by a transaction requesting user, for example, the transaction request is used to request that a first amount of resources be transferred from the transaction requesting user to a target transaction user; the transaction platform firstly determines locking information of each transaction element associated with the transaction, and sends a transaction element locking request to a management user of the transaction element according to the locking information and a transaction identifier included in the transaction request so as to lock the transaction element associated with the transaction, and if the transaction element is determined to be successfully locked, a first amount of resources are transferred from a resource account of a transaction request user to a resource account of a target transaction user according to the transaction information included in the transaction request; if it is determined that the locking of the at least one transaction element fails, a transaction cancellation request is sent to an administrative user of the transaction element to release the locked transaction element. The resource may be an entity resource (e.g., currency) or a virtual resource (e.g., points).

As an example, the transaction request includes transaction identification and transaction information, the transaction information includes information that the transaction requesting user transfers 70 points to the target transaction user and redeems a coupon identified as Y for a milk 1 box of brand X provided by the target transaction user; the transaction platform determines that transaction elements related to the transaction comprise milk and a coupon according to the transaction information, determines that locking information of the milk comprises brand X and box 1, and determines that locking information of the coupon comprises identification Y; according to the transaction identification and the determined locking information, transaction element locking requests are respectively sent to milk stock management users, namely target transaction users and coupon management users; when the transaction platform determines that the target transaction user and the coupon management user both successfully lock the corresponding transaction elements, transferring 70 points from the resource account of the transaction request user to the resource account of the target transaction user according to the transaction information; and when the transaction platform determines that the target transaction user and/or the coupon management user fail to lock the corresponding transaction elements, respectively sending transaction cancel requests to the target transaction user and the coupon management user according to the transaction identifiers so as to release the locked transaction elements and end the transaction. Therefore, the transaction platform firstly locks each transaction element of the transaction based on the transaction request, rather than directly transferring resources, thereby effectively avoiding transaction failure caused by that a certain transaction element does not meet transaction conditions.

Step S104, determining whether a transaction element locking request associated with the transaction identifier is received;

and step S106, if not, generating null transaction record information according to the transaction identifier, and storing the null transaction record information into the block chain through the block chain link point.

In one or more embodiments of the present specification, when receiving a transaction cancellation request sent by a transaction platform, a first terminal device of a management user of a transaction element can effectively identify request reception abnormality caused by factors such as a network fault by determining whether a related transaction element locking request is received; when the abnormity is identified, the empty transaction record information is stored in the block chain, so that an effective abnormity verification basis can be provided for the subsequent receiving of a corresponding transaction element locking request, and useless transaction element locking operation and other processing triggered by the transaction element locking operation are avoided; furthermore, when the transaction platform receives the transaction request, the transaction elements related to the transaction are firstly locked rather than directly processed, so that the transaction failure caused by the fact that a certain transaction element does not meet the transaction condition can be effectively avoided.

In order to determine a transaction corresponding to a locked transaction element and provide a verification basis for receiving an abnormal request data when a network fails, in one or more embodiments of the present specification, when a first terminal device performs a locking process on a transaction element based on a locking request of the transaction element, corresponding locking record information is generated according to a transaction identifier, related information of the transaction element, and the like, and the generated locking record information is stored in a specified database; the process of performing the locking process of the transaction element will be described in detail later. Correspondingly, as shown in fig. 4, step S104 includes:

step S104', determining whether the related locking record information is inquired from the designated database according to the transaction identifier; the locking record information is information generated when the locking processing of the transaction element is carried out based on the transaction element locking request;

specifically, if the associated locking record information is inquired from the specified database according to the transaction identifier, determining that the transaction element locking request associated with the transaction identifier is received; and if the associated locking record information is not inquired from the specified database according to the transaction identifier, determining that the transaction element locking request associated with the transaction identifier is not received. The locking record information can be first locking record information and can also be second locking record information; the first locking record information represents that the corresponding transaction element is successfully locked, and the second locking record information represents that the corresponding transaction element is failed to be locked.

And determining whether the locking record information associated with the transaction identifier is inquired or not to determine whether the transaction element locking request associated with the transaction identifier is received or not, and further determining whether the receiving exception of the request data occurs or not.

Further, when the reception of the request data is abnormal, that is, when a transaction cancellation request sent by the transaction platform is received, the transaction element locking request sent by the transaction platform is not received temporarily, and then the first terminal device receives the transaction element locking request after delaying due to factors such as network recovery, that is, after the first terminal device receives the transaction cancellation request sent by the transaction platform, the corresponding transaction element locking request is received. Correspondingly, as shown in fig. 5, step S106 may further include, after:

step S108, receiving a trading element locking request sent by a trading platform;

step S110, determining whether related empty transaction record information is inquired from the blockchain according to the transaction identifier included in the transaction element locking request;

specifically, according to a transaction identifier included in the transaction element locking request, sending an inquiry request to the block chain node, so that the block chain node inquires related empty transaction record information from the block chain according to the transaction identifier and sends an inquiry result to the first terminal device; and the first terminal equipment determines whether the empty transaction record information associated with the transaction identifier is inquired from the blockchain or not according to the received inquiry result.

Step S112, if the associated empty transaction record information is inquired from the block chain, transaction termination information is sent to the transaction platform; the transaction termination information is used for indicating that the related processing of the transaction element locking request is terminated;

specifically, when the query result represents that the associated empty transaction record information is queried, it is determined that a transaction cancellation request associated with the transaction identifier in the transaction element locking request is received before the transaction element locking request is received, and since the transaction is cancelled, the transaction element locking processing is not executed any more, and transaction termination information is sent to the transaction platform to indicate that the related processing of the transaction element locking request is terminated.

Further, the above steps S108 and S110 may also be executed before step S102, that is, the receiving exception of the request data does not occur, and the first terminal device receives the transaction cancellation request after receiving the transaction element locking request sent by the transaction platform, and as shown in fig. 6, the method further includes the following step S114:

step S114, if no associated empty transaction record information is queried from the blockchain, performing transaction element locking processing according to the transaction element locking request.

Specifically, as shown in fig. 7, step S114 may include:

step S114-2, if the associated empty transaction record information is not inquired from the blockchain, determining whether the transaction element to be locked is in a tradable state or not according to the locking information included in the transaction element locking request, if so, executing step S114-4, otherwise, executing step S114-8;

the locking information is different according to different transaction elements, for example, a transaction element is a certain commodity, and the locking information may include a commodity brand, a transaction amount, and the like of the commodity; as another example, the transaction element is a coupon issued by a merchant, and the locking information may include information such as a coupon identifier for the coupon.

Step S114-4, generating first locking record information according to the preset locking success identification, the transaction identification and the related information of the transaction element, wherein the first locking record information represents that the transaction element is successfully locked;

the related information of the transaction element may be set in practical application according to needs, for example, the transaction element is a certain commodity, and the related information of the transaction element may include a commodity brand, a transaction amount, a transaction price, and the like of the commodity.

Step S114-6, storing the first locking record information into a specified database, and sending locking success information to the trading platform;

step S114-8, generating second locking record information according to the preset locking failure identification, the transaction identification and the related information of the transaction element, wherein the second locking record information represents the locking failure of the transaction element;

and step S114-10, storing the second locking record information into a specified database, and sending locking failure information to the trading platform.

Still by way of the foregoing example, when a first terminal device of a target trading user receives a trading element locking request, if it is determined that associated empty trading record information is not queried from a blockchain according to a trading identifier included in the trading element locking request, querying an inventory quantity of milk of a brand X and using the inventory quantity as state information of the milk of the brand X, for example, the queried inventory quantity is 0, determining that the milk of the brand X is in a non-trading state, generating second locking record information according to information of the brand X, a quantity 1 box, a trading identifier, a preset locking failure identifier and the like, storing the second locking record information into a designated database, and sending locking failure information to a trading platform; further, when a first terminal device of a coupon management user receives a transaction element locking request, if it is determined that associated empty transaction record information is not queried from a blockchain according to a transaction identifier included in the transaction element locking request, whether the coupon identified as Y is within a validity period and serves as state information of the coupon is detected, for example, within the validity period, it is determined that the coupon is in a tradable state, first locking record information is generated according to the identifier Y of the coupon, the transaction identifier and a preset locking success identifier, the first locking record information is stored in a specified database, and locking success information is sent to a transaction platform.

It should be noted that the lock record information can also be saved in the block chain, which can be set as required in practical applications. Therefore, when the first terminal equipment of the transaction element management user receives the locking request of the transaction element, whether the receiving abnormality of the request data exists is determined based on the record information in the block chain, and useless and even wrong processing is avoided being executed due to the receiving abnormality of the request data; when the receiving abnormity is determined to be absent, the locking processing of the transaction element is carried out based on the transaction element locking request, and the transaction failure caused by that a certain transaction element does not meet the transaction condition can be effectively avoided; by storing the locking record information into the designated database, a verification basis for receiving abnormity is provided when a transaction cancellation request is received.

Further, as shown in fig. 6, when the above steps S108 and S110 are performed before the step S102, the step S104 may include the following step S104-2, the step S106 may include the following step S106-2, and the method further includes the following step S116:

step S104-2, determining whether a transaction element locking request associated with the transaction identifier in the transaction canceling request is received, if so, executing step S116, otherwise, executing step S106-2;

step S106-2, generating null transaction record information according to the transaction identifier, and storing the null transaction record information into a block chain;

specifically, the transaction identifier and a preset empty transaction identifier are recorded in an associated manner, the recorded information is determined to be empty transaction record information, and the empty transaction record information is stored in the block chain.

In step S116, a transaction cancellation process is performed according to the transaction cancellation request.

Specifically, according to the transaction identification included in the transaction cancel request, the associated locking record information is inquired from the specified database; storing the preset transaction canceling identification and the inquired locking record information in a correlation manner; and when the inquired locking record information is the first locking record information, storing the preset transaction canceling identifier in association with the first locking record information so as to represent that the locked transaction element is released and the transaction is ended. And when the inquired locking record information is second locking record information, storing the preset transaction canceling identifier and the first locking record information in a correlation mode to represent the end of the transaction.

In one or more embodiments of the present specification, when receiving a transaction cancellation request sent by a transaction platform, a first terminal device of a management user corresponding to a transaction element can effectively identify request reception abnormality caused by factors such as a network fault by determining whether a related transaction element locking request is received; when the abnormity is identified, the empty transaction record information is stored in the block chain, so that an effective abnormity verification basis can be provided for the subsequent receiving of a corresponding transaction element locking request, and useless transaction element locking operation and other processing triggered by the transaction element locking operation are avoided; furthermore, when the transaction platform receives the transaction request, the transaction elements related to the transaction are firstly locked rather than directly processed, so that the transaction failure caused by the fact that a certain transaction element does not meet the transaction condition can be effectively avoided.

On the basis of the same technical concept, corresponding to the transaction processing methods described in fig. 3 to 7, one or more embodiments of the present disclosure further provide a transaction processing apparatus. Fig. 8 is a schematic diagram of a module composition of a transaction processing apparatus according to one or more embodiments of the present disclosure, the apparatus being configured to execute the transaction processing method described in fig. 3 to 7, and as shown in fig. 8, the apparatus includes:

a receiving module 201, which receives a transaction cancellation request sent by a transaction platform; the transaction canceling request is a request sent to a management user of each transaction element associated with a transaction request after the transaction canceling request is sent to the management user of the transaction element based on the transaction request sent by a transaction request user by the transaction platform, and when at least one transaction element is determined to be locked unsuccessfully; wherein the transaction cancellation request includes a transaction identification;

a first determination module 202 that determines whether the transaction element lock request associated with the transaction identification is received;

if the determination result of the first determination module is negative, the generation module 203 generates empty transaction record information according to the transaction identifier, and stores the empty transaction record information into the blockchain.

The transaction processing device provided in one or more embodiments of the present specification can effectively identify request reception abnormalities caused by network failures and other factors by determining whether a related transaction element locking request is received or not when a transaction cancellation request sent by a transaction platform is received; when the abnormity is identified, the empty transaction record information is stored in the block chain, so that an effective abnormity verification basis can be provided for the subsequent receiving of a corresponding transaction element locking request, and useless transaction element locking operation and other processing triggered by the transaction element locking operation are avoided; furthermore, when the transaction platform receives the transaction request, the transaction elements related to the transaction are firstly locked rather than directly processed, so that the transaction failure caused by the fact that a certain transaction element does not meet the transaction condition can be effectively avoided.

Optionally, the first determining module 202 determines whether to query the associated locking record information from the designated database according to the transaction identifier; the locking record information is information generated when the locking processing of the transaction element is carried out based on the transaction element locking request;

if yes, determining that the transaction element locking request associated with the transaction identification is received;

if not, determining that the transaction element locking request associated with the transaction identifier is not received.

Optionally, the apparatus further comprises: the device comprises a second determining module, a sending module and a locking module;

the receiving module 201 is configured to receive the transaction element locking request sent by the transaction platform;

the second determining module is used for determining whether the associated null transaction record information is inquired from the block chain according to the transaction identifier included in the transaction element locking request;

the sending module is used for sending transaction termination information to the transaction platform if the determination result of the second determining module is positive; wherein the transaction termination information is used for indicating that the related processing of the transaction element locking request is terminated;

and if the determination result of the second determination module is negative, the locking module performs transaction element locking processing according to the transaction element locking request.

Optionally, the transaction element lock request comprises: locking information of a transaction element to be locked;

the locking module is used for determining whether the transaction element to be locked is in a tradable state or not according to the locking information;

if yes, generating first locking record information according to a preset locking success identifier, the transaction identifier and the related information of the transaction element, wherein the first locking record information represents that the transaction element is successfully locked; storing the first locking record information into a designated database, and sending locking success information to the trading platform;

if not, generating second locking record information according to a preset locking failure identifier, the transaction identifier and the related information of the transaction element, wherein the second locking record information represents that the transaction element is failed to be locked; and storing the second locking record information into a specified database, and sending locking failure information to the trading platform.

Optionally, the apparatus further comprises: a cancellation module;

and the canceling module is used for canceling the transaction if the first determining module determines that the transaction element locking request associated with the transaction identifier is not received.

Optionally, the canceling module queries related locking record information from the specified database according to the transaction identifier; and the number of the first and second groups,

and storing the preset transaction canceling identification in association with the inquired locking record information.

Optionally, the generating module 203 associates the transaction identifier with a preset empty transaction identifier to record, and determines the recorded information as empty transaction record information.

The transaction processing device provided in one or more embodiments of the present specification can effectively identify request reception abnormalities caused by network failures and other factors by determining whether a related transaction element locking request is received or not when a transaction cancellation request sent by a transaction platform is received; when the abnormity is identified, the empty transaction record information is stored in the block chain, so that an effective abnormity verification basis can be provided for the subsequent receiving of a corresponding transaction element locking request, and useless transaction element locking operation and other processing triggered by the transaction element locking operation are avoided; furthermore, when the transaction platform receives the transaction request, the transaction elements related to the transaction are firstly locked rather than directly processed, so that the transaction failure caused by the fact that a certain transaction element does not meet the transaction condition can be effectively avoided.

It should be noted that the embodiment of the transaction processing apparatus in this specification and the embodiment of the transaction processing method in this specification are based on the same inventive concept, and therefore, for specific implementation of this embodiment, reference may be made to implementation of the corresponding transaction processing method, and repeated details are not described again.

Further, corresponding to the transaction processing methods described in fig. 3 to fig. 7, based on the same technical concept, one or more embodiments of the present specification further provide a transaction processing device, which is used for executing the transaction processing method described above, and fig. 9 is a schematic structural diagram of a transaction processing device provided in one or more embodiments of the present specification.

As shown in fig. 9, the transaction processing device may have a large difference due to different configurations or performances, and may include one or more processors 301 and a memory 302, and one or more stored applications or data may be stored in the memory 302. Memory 302 may be, among other things, transient storage or persistent storage. The application program stored in memory 302 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in a transaction processing device. Still further, the processor 301 may be arranged in communication with the memory 302 to execute a series of computer executable instructions in the memory 302 on the transaction processing device. The transaction processing device may also include one or more power supplies 303, one or more wired or wireless network interfaces 304, one or more input-output interfaces 305, one or more keyboards 306, and the like.

In one particular embodiment, the transaction processing apparatus includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the transaction processing apparatus, and the one or more programs configured to be executed by the one or more processors include computer-executable instructions for:

receiving a transaction canceling request sent by a transaction platform; the transaction canceling request is a request sent to a management user of each transaction element associated with a transaction request after the transaction canceling request is sent to the management user of the transaction element based on the transaction request sent by a transaction request user by the transaction platform, and when at least one transaction element is determined to be locked unsuccessfully; wherein the transaction cancellation request includes a transaction identification;

determining whether the transaction element locking request associated with the transaction identification is received;

if not, generating null transaction record information according to the transaction identifier, and storing the null transaction record information into the block chain.

The transaction processing device provided in one or more embodiments of the present specification can effectively identify request reception abnormalities caused by network failures and other factors by determining whether a related transaction element locking request is received or not when a transaction cancellation request sent by a transaction platform is received; when the abnormity is identified, the empty transaction record information is stored in the block chain, so that an effective abnormity verification basis can be provided for the subsequent receiving of a corresponding transaction element locking request, and useless transaction element locking operation and other processing triggered by the transaction element locking operation are avoided; furthermore, when the transaction platform receives the transaction request, the transaction elements related to the transaction are firstly locked rather than directly processed, so that the transaction failure caused by the fact that a certain transaction element does not meet the transaction condition can be effectively avoided.

Optionally, the computer executable instructions, when executed, determine whether associated locking record information is queried from a designated database according to the transaction identification; the locking record information is information generated when the locking processing of the transaction element is carried out based on the transaction element locking request;

if yes, determining that the transaction element locking request associated with the transaction identification is received;

if not, determining that the transaction element locking request associated with the transaction identifier is not received.

Optionally, the computer executable instructions, when executed, further comprise:

receiving the transaction element locking request sent by the transaction platform;

determining whether the associated null transaction record information is queried from the blockchain according to the transaction identifier included in the transaction element locking request;

if yes, sending transaction termination information to the transaction platform; wherein the transaction termination information is used for indicating that the related processing of the transaction element locking request is terminated;

if not, transaction element locking processing is carried out according to the transaction element locking request.

Optionally, the computer executable instructions, when executed, further comprise: locking information of a transaction element to be locked;

the performing transaction element locking processing according to the transaction element locking request includes:

determining whether the transaction element to be locked is in a tradable state or not according to the locking information;

if yes, generating first locking record information according to a preset locking success identifier, the transaction identifier and the related information of the transaction element, wherein the first locking record information represents that the transaction element is successfully locked; storing the first locking record information into a designated database, and sending locking success information to the trading platform;

if not, generating second locking record information according to a preset locking failure identifier, the transaction identifier and the related information of the transaction element, wherein the second locking record information represents that the transaction element is failed to be locked; and storing the second locking record information into a specified database, and sending locking failure information to the trading platform.

Optionally, the computer executable instructions, when executed, further comprise:

and if the transaction element locking request associated with the transaction identifier is determined to be received, performing transaction cancellation processing.

Optionally, the computer executable instructions, when executed, perform a transaction cancellation process comprising:

inquiring related locking record information from the specified database according to the transaction identifier;

and storing the preset transaction canceling identification in association with the inquired locking record information.

Optionally, when executed, the computer-executable instructions generate null transaction record information according to the transaction identifier, including:

and recording the transaction identification and a preset empty transaction identification in an associated manner, and determining the recorded information as empty transaction record information.

The transaction processing device provided in one or more embodiments of the present specification can effectively identify request reception abnormalities caused by network failures and other factors by determining whether a related transaction element locking request is received or not when a transaction cancellation request sent by a transaction platform is received; when the abnormity is identified, the empty transaction record information is stored in the block chain, so that an effective abnormity verification basis can be provided for the subsequent receiving of a corresponding transaction element locking request, and useless transaction element locking operation and other processing triggered by the transaction element locking operation are avoided; furthermore, when the transaction platform receives the transaction request, the transaction elements related to the transaction are firstly locked rather than directly processed, so that the transaction failure caused by the fact that a certain transaction element does not meet the transaction condition can be effectively avoided.

It should be noted that the embodiment of the transaction processing device in this specification and the embodiment of the transaction processing method in this specification are based on the same inventive concept, and therefore, for specific implementation of this embodiment, reference may be made to implementation of the corresponding transaction processing method, and repeated details are not described again.

Further, based on the same technical concept, corresponding to the methods shown in fig. 3 to fig. 7, one or more embodiments of the present specification further provide a storage medium for storing computer-executable instructions, where in a specific embodiment, the storage medium may be a usb disk, an optical disk, a hard disk, and the like, and the storage medium stores computer-executable instructions that, when executed by a processor, implement the following processes:

receiving a transaction canceling request sent by a transaction platform; the transaction canceling request is a request sent to a management user of each transaction element associated with a transaction request after the transaction canceling request is sent to the management user of the transaction element based on the transaction request sent by a transaction request user by the transaction platform, and when at least one transaction element is determined to be locked unsuccessfully; wherein the transaction cancellation request includes a transaction identification;

determining whether the transaction element locking request associated with the transaction identification is received;

if not, generating null transaction record information according to the transaction identifier, and storing the null transaction record information into the block chain.

When executed by a processor, computer-executable instructions stored in a storage medium provided in one or more embodiments of the present specification can effectively identify request reception anomalies caused by network failures and other factors by determining whether an associated transaction element locking request is received or not when a transaction cancellation request sent by a transaction platform is received; when the abnormity is identified, the empty transaction record information is stored in the block chain, so that an effective abnormity verification basis can be provided for the subsequent receiving of a corresponding transaction element locking request, and useless transaction element locking operation and other processing triggered by the transaction element locking operation are avoided; furthermore, when the transaction platform receives the transaction request, the transaction elements related to the transaction are firstly locked rather than directly processed, so that the transaction failure caused by the fact that a certain transaction element does not meet the transaction condition can be effectively avoided.

Optionally, the storage medium stores computer-executable instructions that, when executed by the processor, determine whether associated lock record information is queried from a specified database based on the transaction identification; the locking record information is information generated when the locking processing of the transaction element is carried out based on the transaction element locking request;

if yes, determining that the transaction element locking request associated with the transaction identification is received;

if not, determining that the transaction element locking request associated with the transaction identifier is not received.

Optionally, the storage medium stores computer-executable instructions that, when executed by the processor, further comprise:

receiving the transaction element locking request sent by the transaction platform;

determining whether the associated null transaction record information is queried from the blockchain according to the transaction identifier included in the transaction element locking request;

if yes, sending transaction termination information to the transaction platform; wherein the transaction termination information is used for indicating that the related processing of the transaction element locking request is terminated;

if not, transaction element locking processing is carried out according to the transaction element locking request.

Optionally, the storage medium stores computer-executable instructions that, when executed by the processor, cause the transaction element lock request to comprise: locking information of a transaction element to be locked;

the performing transaction element locking processing according to the transaction element locking request includes:

determining whether the transaction element to be locked is in a tradable state or not according to the locking information;

if yes, generating first locking record information according to a preset locking success identifier, the transaction identifier and the related information of the transaction element, wherein the first locking record information represents that the transaction element is successfully locked; storing the first locking record information into a designated database, and sending locking success information to the trading platform;

if not, generating second locking record information according to a preset locking failure identifier, the transaction identifier and the related information of the transaction element, wherein the second locking record information represents that the transaction element is failed to be locked; and storing the second locking record information into a specified database, and sending locking failure information to the trading platform.

Optionally, the storage medium stores computer-executable instructions that, when executed by the processor, further comprise:

and if the transaction element locking request associated with the transaction identifier is determined to be received, performing transaction cancellation processing.

Optionally, the storage medium stores computer-executable instructions that, when executed by the processor, perform a transaction cancellation process, comprising:

inquiring related locking record information from the specified database according to the transaction identifier;

and storing the preset transaction canceling identification in association with the inquired locking record information.

Optionally, the storage medium stores computer-executable instructions that, when executed by the processor, generate null transaction record information according to the transaction identifier, including:

and recording the transaction identification and a preset empty transaction identification in an associated manner, and determining the recorded information as empty transaction record information.

When executed by a processor, the computer-executable instructions stored in the storage medium provided by one or more embodiments of the present specification can effectively identify request reception anomalies caused by network failures and other factors by determining whether an associated transaction element locking request is received or not when a transaction cancellation request sent by a transaction platform is received; when the abnormity is identified, the empty transaction record information is stored in the block chain, so that an effective abnormity verification basis can be provided for the subsequent receiving of a corresponding transaction element locking request, and useless transaction element locking operation and other processing triggered by the transaction element locking operation are avoided; furthermore, when the transaction platform receives the transaction request, the transaction elements related to the transaction are firstly locked rather than directly processed, so that the transaction failure caused by the fact that a certain transaction element does not meet the transaction condition can be effectively avoided.

It should be noted that the embodiment of the storage medium in this specification and the embodiment of the transaction processing method in this specification are based on the same inventive concept, and therefore, for specific implementation of this embodiment, reference may be made to implementation of the corresponding transaction processing method, and repeated details are not described again.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

In the 30 s of the 20 th century, improvements in a technology could clearly be distinguished between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardsradware (Hardware Description Language), vhjhd (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the units may be implemented in the same software and/or hardware or in multiple software and/or hardware when implementing the embodiments of the present description.

One skilled in the art will recognize that one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The above description is only an example of this document and is not intended to limit this document. Various modifications and changes may occur to those skilled in the art from this document. Any modifications, equivalents, improvements, etc. which come within the spirit and principle of the disclosure are intended to be included within the scope of the claims of this document.

Claims (13)

1. A transaction processing method, comprising:

receiving a transaction canceling request sent by a transaction platform; the transaction canceling request is a request sent to a management user of each transaction element associated with a transaction request after the transaction canceling request is sent to the management user of the transaction element based on the transaction request sent by a transaction request user by the transaction platform, and when at least one transaction element is determined to be locked unsuccessfully; wherein the transaction cancellation request includes a transaction identification;

determining whether the transaction element locking request associated with the transaction identification is received;

if not, generating null transaction record information according to the transaction identifier, and storing the null transaction record information into the block chain.

2. The method of claim 1, the determining whether the transaction element lock request associated with the transaction identification is received, comprising:

determining whether the related locking record information is inquired from a designated database according to the transaction identifier; the locking record information is information generated when the locking processing of the transaction element is carried out based on the transaction element locking request;

if yes, determining that the transaction element locking request associated with the transaction identification is received;

if not, determining that the transaction element locking request associated with the transaction identifier is not received.

3. The method of claim 1, further comprising:

receiving the transaction element locking request sent by the transaction platform;

determining whether the associated null transaction record information is queried from the blockchain according to the transaction identifier included in the transaction element locking request;

if yes, sending transaction termination information to the transaction platform; wherein the transaction termination information is used for indicating that the related processing of the transaction element locking request is terminated;

if not, transaction element locking processing is carried out according to the transaction element locking request.

4. The method of claim 3, the transaction element lock request comprising: locking information of a transaction element to be locked;

the performing transaction element locking processing according to the transaction element locking request includes:

determining whether the transaction element to be locked is in a tradable state or not according to the locking information;

if yes, generating first locking record information according to a preset locking success identifier, the transaction identifier and the related information of the transaction element, wherein the first locking record information represents that the transaction element is successfully locked; storing the first locking record information into a designated database, and sending locking success information to the trading platform;

if not, generating second locking record information according to a preset locking failure identifier, the transaction identifier and the related information of the transaction element, wherein the second locking record information represents that the transaction element is failed to be locked; and storing the second locking record information into a specified database, and sending locking failure information to the trading platform.

5. The method of claim 4, further comprising:

and if the transaction element locking request associated with the transaction identifier is determined to be received, performing transaction cancellation processing.

6. The method of claim 5, the conducting transaction cancellation processing, comprising:

inquiring related locking record information from the specified database according to the transaction identifier;

and storing the preset transaction canceling identification in association with the inquired locking record information.

7. The method of any of claims 1-6, the generating empty transaction record information from the transaction identification, comprising:

and recording the transaction identification and a preset empty transaction identification in an associated manner, and determining the recorded information as empty transaction record information.

8. A transaction processing device comprising:

the receiving module is used for receiving a transaction canceling request sent by the transaction platform; the transaction canceling request is a request sent to a management user of each transaction element associated with a transaction request after the transaction canceling request is sent to the management user of the transaction element based on the transaction request sent by a transaction request user by the transaction platform, and when at least one transaction element is determined to be locked unsuccessfully; wherein the transaction cancellation request includes a transaction identification;

a first determination module that determines whether the transaction element lock request associated with the transaction identification is received;

and the generating module is used for generating empty transaction record information according to the transaction identifier and storing the empty transaction record information into the block chain if the determination result of the first determining module is negative.

9. The apparatus of claim 8, wherein the first and second electrodes are disposed on opposite sides of the substrate,

the determining module is used for determining whether the related locking record information is inquired from the specified database according to the transaction identifier; the locking record information is information generated when the locking processing of the transaction element is carried out based on the transaction element locking request;

if yes, determining that the transaction element locking request associated with the transaction identification is received;

if not, determining that the transaction element locking request associated with the transaction identifier is not received.

10. The apparatus of claim 8, the apparatus further comprising: the device comprises a second determining module, a sending module and a locking module;

the receiving module is used for receiving the transaction element locking request sent by the transaction platform;

the second determining module is used for determining whether the associated null transaction record information is inquired from the block chain according to the transaction identifier included in the transaction element locking request;

the sending module is used for sending transaction termination information to the transaction platform if the determination result of the second determining module is positive; wherein the transaction termination information is used for indicating that the related processing of the transaction element locking request is terminated;

and if the determination result of the second determination module is negative, the locking module performs transaction element locking processing according to the transaction element locking request.

11. The apparatus of claim 10, the apparatus further comprising: a cancellation module;

and the canceling module is used for canceling the transaction if the first determining module determines that the transaction element locking request associated with the transaction identifier is not received.

12. A transaction processing device comprising:

a processor; and the number of the first and second groups,

a memory arranged to store computer executable instructions that, when executed, cause the processor to:

receiving a transaction canceling request sent by a transaction platform; the transaction canceling request is a request sent to a management user of each transaction element associated with a transaction request after the transaction canceling request is sent to the management user of the transaction element based on the transaction request sent by a transaction request user by the transaction platform, and when at least one transaction element is determined to be locked unsuccessfully; wherein the transaction cancellation request includes a transaction identification;

determining whether the transaction element locking request associated with the transaction identification is received;

if not, generating null transaction record information according to the transaction identifier, and storing the null transaction record information into the block chain.

13. A storage medium storing computer-executable instructions that when executed implement the following:

receiving a transaction canceling request sent by a transaction platform; the transaction canceling request is a request sent to a management user of each transaction element associated with a transaction request after the transaction canceling request is sent to the management user of the transaction element based on the transaction request sent by a transaction request user by the transaction platform, and when at least one transaction element is determined to be locked unsuccessfully; wherein the transaction cancellation request includes a transaction identification;

determining whether the transaction element locking request associated with the transaction identification is received;

if not, generating null transaction record information according to the transaction identifier, and storing the null transaction record information into the block chain.

Images