CN111695970A

CN111695970A - Order processing method and system

Info

Publication number: CN111695970A
Application number: CN202010527397.5A
Authority: CN
Inventors: 刘晨曦; 姚刚
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2020-06-11
Filing date: 2020-06-11
Publication date: 2020-09-22

Abstract

The embodiment of the specification discloses an order processing method and a system, wherein the method comprises the following steps: acquiring order information of at least two orders and a combination processing identifier corresponding to the at least two orders; performing a merging processing operation on the at least two orders based on the merging processing identifier, wherein the merging processing operation comprises: acquiring combined order information based on the order information of the at least two orders, wherein the combined order information comprises at least two types of asset settlement data; and performing settlement processing on the at least two types of asset settlement data in a distributed transaction mode respectively to ensure the consistent success or failure of each settlement processing; and acquiring the result of each settlement processing to determine the processing results of at least two orders corresponding to the combined order information.

Description

Order processing method and system

Technical Field

The present application relates to the field of electronic payment technologies, and in particular, to an order processing method and system.

Background

In recent years, with the development of internet technology and the combination of finance and network technology, electronic payment is widely used in various aspects of production and life. The electronic payment platform scenario has more and more application scenarios that need to maintain consolidated payment consistency (which may mean that the order of the consolidated payment of the buyer is finally maintained while being successful or while failing), for example, the consolidated payment order of the payment member is opened (i.e. the user purchases the physical goods supporting the discount of the payment member while purchasing the member (qualification or authority)), the customer enjoys the benefit, i.e. the customer purchases the physical goods supporting the discount of the payment member while purchasing the member (qualification or authority), or the customer pays the consolidated order of the member (qualification or authority) and the physical goods, and can enjoy the member-preferential price of the physical goods.

At present, because the combined payment consistency can not be completely realized in an online electronic payment store, the successful payment and the failure of partial order payment in combined orders are easy to occur. For example, when the user places an order to pay a paid member (qualification or authority) and a physical commodity supporting discount of the paid member, the user receives a member preferential price of the physical commodity but fails to purchase the paid member when the consolidated payment consistency fails.

Disclosure of Invention

One embodiment of the present disclosure provides an order processing method. The method comprises the following steps: obtaining order information of at least two orders; performing a merge processing operation on the at least two orders, the merge processing operation comprising: acquiring combined order information based on the order information of the at least two orders, wherein the combined order information comprises at least one type of asset settlement data; and, separately performing settlement processing on the at least one type of asset settlement data in a distributed transaction form to ensure consistent success or failure of each settlement processing; and acquiring the result of each settlement processing to determine the processing results of at least two orders corresponding to the combined order information.

Another order processing method provided in one embodiment of this specification, the method includes: acquiring consolidated order information determined by order information of at least two orders, wherein the consolidated order information comprises at least one type of asset settlement data; executing a merging processing operation on the merged order information, wherein the merging processing operation comprises: performing settlement processing on the at least two types of asset settlement data in a distributed transaction mode respectively to ensure the consistent success or failure of each settlement processing; and acquiring the result of each settlement processing to determine the processing results of at least two orders corresponding to the combined order information.

One of the embodiments of the present specification provides an order processing system, including: the acquisition module is used for acquiring order information of at least two orders; a processing module, configured to perform a merge processing operation on the at least two orders, where the merge processing operation includes: acquiring combined order information based on the order information of the at least two orders, wherein the combined order information comprises at least two types of asset settlement data; and performing settlement processing on the at least two types of asset settlement data in a distributed transaction mode respectively to ensure the consistent success or failure of each settlement processing; and the determining module is used for acquiring the result of each settlement processing so as to determine the processing results of at least two orders corresponding to the combined order information.

One of the embodiments of the present specification provides an order processing apparatus, including a processor, configured to execute an order processing method.

Drawings

The present application will be further explained by way of exemplary embodiments, which will be described in detail by way of the accompanying drawings. These embodiments are not intended to be limiting, and in these embodiments like numerals are used to indicate like structures, wherein:

FIG. 1 is a schematic diagram of an application scenario of an order processing system according to some embodiments of the present description;

FIG. 2 is an exemplary flow diagram of an order processing method according to some embodiments of the present description;

FIG. 3 is an exemplary flow diagram of a distributed transaction processing method according to some embodiments of the present description; and

FIG. 4 is a block diagram of an order processing system according to some embodiments of the present description.

Detailed Description

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings used in the description of the embodiments will be briefly introduced below. It is obvious that the drawings in the following description are only examples or embodiments of the application, from which the application can also be applied to other similar scenarios without inventive effort for a person skilled in the art. Unless otherwise apparent from the context, or otherwise indicated, like reference numbers in the figures refer to the same structure or operation.

It should be understood that "system", "device", "unit" and/or "module" as used herein is a method for distinguishing different components, elements, parts, portions or assemblies at different levels. However, other words may be substituted by other expressions if they accomplish the same purpose.

As used in this application and the appended claims, the terms "a," "an," "the," and/or "the" are not intended to be inclusive in the singular, but rather are intended to be inclusive in the plural unless the context clearly dictates otherwise. In general, the terms "comprises" and "comprising" merely indicate that steps and elements are included which are explicitly identified, that the steps and elements do not form an exclusive list, and that a method or apparatus may include other steps or elements.

Flow charts are used herein to illustrate operations performed by systems according to embodiments of the present application. It should be understood that the preceding or following operations are not necessarily performed in the exact order in which they are performed. Rather, the various steps may be processed in reverse order or simultaneously. Meanwhile, other operations may be added to the processes, or a certain step or several steps of operations may be removed from the processes.

Currently, for the combination process of multiple orders, each order is processed separately. The processing results for each order may be inconsistent. For example, some orders are processed successfully (e.g., successful payments), while some orders are processed unsuccessfully (e.g., failed payments). Therefore, on one hand, the order processing state is inconsistent, and cash register and other problems can be caused. On the other hand, the processing of each order requires initiation of a process flow and termination of the process flow when the processing is complete (whether successful or failed). The process of initiating and finishing a plurality of times required for processing a plurality of orders takes longer time, and occupies more processing resources.

The technical scheme disclosed by the specification can ensure the consistency of processing a plurality of orders. I.e., success at the same time, or failure at the same time. Meanwhile, for the processing of a plurality of orders, only one-time processing resource is required to be called without repeated calling, so that the resources are saved.

FIG. 1 is a schematic diagram of an application scenario of an order processing system according to some embodiments of the present description. The order processing system 100 may be used in the field of electronic payment. For example, the order processing system 100 may ensure consistent success or failure of order processing by performing a merge process on at least two acquired orders. As shown in FIG. 1, the order processing system 100 may include a web services platform 110, a network 120, and a web payment platform 130.

The network services platform 110 may be a platform that provides various products and/or services. For example, the web services platform 110 may include a web shopping platform for providing merchandise purchases. As another example, the network services platform 110 may include a network entertainment platform for providing services such as video, games, and the like. Also for example, the web services platform 110 may include a web life platform for providing services such as current affairs news, home services, and the like. A user of the web services platform 110 (which may also be a subscriber) may utilize a front-end application of the web services platform 110 (e.g., an application installed on a smart terminal, such as a mobile application installed on a smart phone) to access the web services platform 110 and request and/or purchase services thereon. For example, to purchase goods or account number VIP services. When the user consumes on the network service platform 110, the network service platform 110 may produce a corresponding purchase order according to the goods selected by the user. When a user selects a plurality of services, for example, the user purchases a plurality of goods, and for example, the user purchases a member (qualification or authority) under a certain service and a service or physical goods supporting a member discount, the network service platform 110 may generate an order for each purchase object, such as a good, a service or a member (qualification or authority). In some embodiments, the network services platform 110 may send information related to the order to further process the order, e.g., pay, via the network 120 to other components of the order processing system 100, e.g., the network payment platform 130.

The network 120 may facilitate the exchange of data and/or information, which may include order information for orders sent by the web services platform 110 to the web payment platform 130. In some embodiments, one or more components (web services platform 110, web payment platform 130) in the order processing system 100 may send data and/or information to other components in the order processing system 100 via the network 120. In some embodiments, network 120 may be any type of wired or wireless network. For example, network 120 may include a wireline network, a fiber optic network, a telecommunications network, an intranet, the Internet, a Local Area Network (LAN), a Wide Area Network (WAN), a Wireless Local Area Network (WLAN), a Metropolitan Area Network (MAN), a Wide Area Network (WAN), a Public Switched Telephone Network (PSTN), a Bluetooth network, a ZigBee network, a Near Field Communication (NFC) network, a global system for mobile communications (GSM) network, a Code Division Multiple Access (CDMA) network, a Time Division Multiple Access (TDMA) network, a General Packet Radio Service (GPRS) network, an enhanced data rates for GSM evolution (EDGE) network, a Wideband Code Division Multiple Access (WCDMA) network, a High Speed Downlink Packet Access (HSDPA) network, a Long Term Evolution (LTE) network, a User Datagram Protocol (UDP) network, a Transmission control protocol/Internet protocol (TCP/IP) network, a Short Message Service (SMS) network, a Wireless Application Protocol (WAP) network, One or more combinations of ultra-wideband (UWB) networks, mobile communication (1G, 2G, 3G, 4G, 5G) networks, Wi-Fi, Li-Fi, narrowband Internet of things (NB-IoT), infrared communication, and the like.

The network payment platform 130 may be used to enable online transaction payments. For example, the network payment platform 130 may perform payment processing for orders generated on the network services platform 110. In some embodiments, the network payment platform 130 may include a processing system. The processing system may be configured to process the received order, for example, to process a consolidated order consisting of two or more orders. In some embodiments, the processing system may obtain order information for at least two orders and a consolidated process identification corresponding to the at least two orders. And executing the merging processing operation on the at least two orders based on the merging processing identifier. The merging processing operation may be to obtain merged order information based on the order information of the at least two orders, where the merged order information includes at least two types of asset settlement data, and perform settlement processing on the at least two types of asset settlement data in a distributed transaction manner, so as to ensure consistent success or failure of each settlement processing. The processing system may further obtain a result of each settlement processing to determine a processing result of at least two orders corresponding to the consolidated order information. In some embodiments, the web payment platform 130 may be integral with the web services platform 110.

FIG. 2 is an exemplary flow diagram of an order processing method according to some embodiments of the present description. In some embodiments, process 200 may be performed by network payment platform 130. For example, the process 200 may be stored in a storage device (e.g., an on-board storage unit or an external storage device of the network payment platform 130) in the form of a program or instructions that, when executed, may implement the process 200. In some embodiments, the process 200 may be performed by the order processing system 400, and the order processing system 400 may be part of the networked payment platform 130. As shown in fig. 2, the process 200 may include the following steps.

Step 202, obtaining order information of at least two orders. This step may be performed by the acquisition module 410.

It is to be appreciated that when a user makes a service purchase on a network services platform (e.g., network services platform 110), the network services platform can generate an order related to the service that the user wants to purchase when determining to purchase the service, e.g., service a and service B. Each order may correspond to a purchased service, e.g., order a corresponds to service a and order b corresponds to service b. Wherein each order may display information related to its corresponding service, such as a service ID, a payment account, a collection account, a service price, payment asset information, etc. Each order needs to be transferred to a subsequent step for processing, e.g., payment. In the above description, the generated order may be the at least two orders, and the related information of the service corresponding to the order may be the order information. In some embodiments, the at least two orders may be associated with the same payment account. For example, orders generated when two or more services are purchased by the same user.

In some embodiments, the at least two orders may be orders to be processed, e.g., orders requiring payment to be made. In some embodiments, the user's payment assets may be transacted with the purchased goods by processing order information for one or more orders. In particular, the payment platform may complete a transaction of the user's payment assets with the purchased goods by processing order information for one or more orders.

In some embodiments, a merging process identifier corresponding to the order information of the at least two orders may also be obtained. The consolidated process identification may be an identification indicating whether the at least two orders support consolidated payment reconciliation. For illustration, the processing of the order will be in the form of a transaction in a subsequent process. Based on transactional consistency, the processing of a single order under constraints can result in success, as well as failure. The consolidated payment consistency may be a request that all order processes succeed at the same time or fail at the same time. Rather than some success and some failure. In some embodiments, the consolidated process identification may be generated by the web services platform at the same time as generating the at least two orders according to its own decision. For example, when some network service platforms pursue order-to-volume rates, a merged process identifier will not be generated when multiple orders are generated for multiple service orders of a user. Each order is processed separately. However, some network service platforms pursue to promote more people to open a member by supporting the discounted goods of the paid member, when the user purchases the member and the discounted goods at the same time, a merged processing identifier is generated for a plurality of related orders (such as at least an order for purchasing the member and an order for purchasing the goods).

In some embodiments, the obtaining module 410 may obtain the order information of the at least two orders and the combined processing identifier corresponding to the at least two orders by communicating with a network service platform (e.g., the network service platform 110). When a user selects at least two commodities in the E-commerce platform and initiates payment, order information (order ID, payer, payee, commodity price, payment asset information and the like) corresponding to the at least two commodities selected by the user is acquired from the E-commerce platform. The obtaining module 410 may further obtain, from the e-commerce platform, a merged processing identifier generated by the e-commerce platform for an order corresponding to at least two commodities based on each order information. In some embodiments, the at least two orders corresponding to the at least two obtained commodities and the combined processing identifier in the at least two orders may be placed in the payment platform to combine the at least two orders with the combined processing identifier, and the combined orders are processed, so that the transactions between the commodities corresponding to the at least two orders and the payment assets of the user for the at least two orders are completed.

And step 204, executing a combination processing operation on the at least two orders. This step may be performed by the processing module 420.

In some embodiments, the consolidated processing operation may be a simultaneous processing of the at least two orders, such as a data processing operation implemented in the form of a transaction. As an example, the processing module 420 may first merge the at least two orders, e.g., merge order information of the two orders, such as a payment amount. The processing module 420 may then process the consolidated order information, for example, to settle the consolidated payment amount in the form of a transaction, to effect the consolidation processing operation. Before processing the combined order information, the processing module 420 may perform a data conversion operation on it, for example, converting it into a format more suitable for subsequent processing. This is, of course, not necessary.

In some embodiments, to implement the merge processing operation, the processing module 420 may obtain the merged order information based on the order information of the at least two orders. The merged order information may be information obtained by merging and/or adding the same items in the order information of the at least two orders. For example, the payment assets may be accumulated to obtain all payment assets that need to be paid. In some embodiments, the consolidated order information includes at least one type of asset settlement data. The asset settlement data may refer to a certain sum of assets used by the user when making order payments. It is understood that the web services platform 110 may issue various virtual assets to the user, such as red packs, coupons, vouchers, and the like. The user may use these virtual assets to make service requests and/or purchases on the network services platform 110. At the same time, the user may also need to pay for his/her own physical assets when requesting and/or purchasing services (e.g., the user's funds stored in an account in a third party payment platform, such as the network payment platform 130, or in an account in a bank, which may be RMB, USD, etc.). Based on this, the assets may be one or more virtual assets, including the user, as well as actual assets. The asset settlement data may then be the sum of a certain asset used when making the order payment. For example, the payment asset information in order 1 is 10-membered real asset and 5-membered red pack, then the assets required for the order at the time of payment may include two categories, one for 10-membered real asset and one for 5-membered red pack asset. For another example, the user may also specify different asset managers for settlement for the same asset. For this reason, the type of the asset settlement data may be divided based on the asset manager in addition to the asset type. For example, the payment asset information in order 3 is 15-dollar RMB, which is settled by the first bank. The payment asset information in order 4 is 5-dollar RMB, which is settled by the second bank. At this point, the asset settlement data type in order 3 is different from the asset data type in order 4. It can be seen that the partitioning of asset settlement data types can be based on different dimensions, which is not limited in any way by this specification.

In some embodiments, to obtain the asset settlement data, for each order, the processing module 420 may obtain the settlement data of each asset type in the order information of the order, and accumulate the settlement data of the same asset type of the at least two orders to obtain the asset settlement data corresponding to the asset type in the combined order information. As an example, a user has purchased two items on the web services platform 110, corresponding to two orders (order 1 and order 2), for example. Wherein the payment asset information in order 1 is 10-element real asset and 5-element red package asset. The paid asset information in order 2 is a 5-membered real asset and a 5-membered red-pack asset. The types of assets involved in order 1 and order 2 may include two categories, real assets and red pack assets. The 10 and 5-membered in order 1 and the 5 and 5-membered in order 2 are the settlement data for the two types of assets, respectively. By accumulating the settlement data for the same type of asset, i.e., 10+5 and 5+5, the asset settlement data for that asset can be obtained. That is, the asset settlement data of the actual asset is 15-ary, and the asset settlement data of the red-covered asset is 10-ary.

In some embodiments, the processing module 420 may perform settlement processing on the at least two types of asset settlement data separately in a distributed transaction after acquiring the consolidated order information to ensure consistent success or failure of each settlement processing. In general, the form of a distributed transaction may include one or more solutions of Two-phase Commit (2 PC), compensation Transaction (TCC), local message table (asynchronous assurance), or MQ transaction messages. By way of example, a two-phase commit will be described in this specification. Further, the payment platform may act as a coordinator and a multi-party asset system (e.g., the bank card system, red envelope system described above) may act as a participant.

A processing device 420 (e.g., the processing device 420 of the order processing system 400 of the networked payment platform 130) may initiate a transaction with multiple participants (e.g., multiple asset systems) based on the consolidated order information as a coordinator. Each participant (asset system) will process its respective corresponding asset settlement data separately (which may be equivalent to each participant processing a branch transaction). For example, the actual asset system will process the asset settlement data corresponding to the actual asset in the consolidated order information, and the red pack asset system will process the asset settlement data corresponding to the red pack asset in the consolidated order information. The result of the processing of the asset settlement data by each participant may be a success or a failure. For example, success may be that the asset over balance data corresponding to the payment account for the order in the asset system may be settled. Conversely, failure to count is failure. After processing, each participant may return the execution results to the coordinator (commit branch transaction). The coordinator performs transaction commit (e.g., all branch transactions are successful) or transaction rollback (one or more branch transactions fail and all branch transactions are considered to be failed) based on the returned execution result, and as for the detailed description of settlement processing performed by the multiple types of asset settlement data in the form of distributed transactions, please refer to the related description in fig. 3. It should be appreciated that in some embodiments, the asset settlement data in the consolidated order information may be of only one type, for example, the payment asset information in order 3 is 15-dollar RMB. The payment asset information in order 5 is 8-dollar RMB. After the merging process, the asset settlement data in the merged order information is 23 yuan RMB. At this time, the coordinator may still process the asset settlement data in the form of multi-branch distributed transaction, for example, the coordinator calls the asset system 1 to process the asset settlement data, and when the processing is successful, the asset system 1 commits the transaction, otherwise, the asset system 1 performs transaction rollback.

In some embodiments, the consolidated order information may also include a consolidated order identification. The consolidated order identification may be an order ID for any of the at least two orders. For example, assuming that order A, order B, and order C are consolidated, the consolidated order identification may be the order ID of any of order A, order B, and order C.

In some embodiments, the order processing system 400 (e.g., the assistance module 440) may add and lock the consolidated order identification to the consolidated order identification data set before performing the consolidated processing operation on the at least two orders. The consolidated order identification data set may be a database formed of order IDs for orders placed and in-progress order payments generated by the web services platform 110. It will be appreciated that the repeated processing of an order not only wastes processing resources, but also presents problems for asset settlement. In order for each order to be processed only once, the assistance module 440 may lock the order ID. Any new order being processed will have its order ID compared to the order ID in the order identification dataset. If the order ID already exists, no processing is performed. And if not, writing the order ID into the order identification data set and locking. Thus, the consolidated order identification corresponding to the at least two orders may be added to the consolidated order identification dataset and locked before the at least two orders are processed.

Further, after performing a merge processing operation on at least two orders, the assistance module 440 may delete the merged order identification from the merged order identification dataset. After the order is processed, since there is no need for order ID comparison, and in order to prevent the data volume in the combined order identification data set from increasing without limit, the auxiliary module 440 may delete the combined order identification from the combined order identification data set. By adding the prepared order to the combined order identification data set and deleting the order ID corresponding to the processed order from the data set, the repeated order placement of the user can be avoided, the processing resources occupied by too many repeated orders can be prevented, and the order can be correctly processed.

Step 206, obtaining the result of each settlement processing to determine the processing result of at least two orders corresponding to the merged order information. This step may be performed by the determination module 430.

In some embodiments, the processing result may include that both of the at least two orders were successfully processed or that both of the orders were failed to be processed. When all the results of each settlement processing are successful, the determining module 430 determines that all the processing results of at least two orders in the corresponding consolidated order information are successful. When one or more processing results in each settlement processing result are failures, the determining module 430 determines that all of at least two order processing results in the corresponding consolidated order information are failures.

In some embodiments, after the at least two orders are processed, the order processing system 400 (or the transmission module 450) may send the processing result of the at least two orders, for example, send a front-end application of the network payment platform 130, for example, a mobile application installed on a smartphone terminal for implementing the network payment platform 130. The front-end application may display the results of the processing of the at least two orders as they are received. The user can check whether the order is paid successfully through the displayed result.

In another embodiment, the obtaining module 410 may obtain the consolidated order information determined by the order information of at least two orders and the consolidated process identifier corresponding to the two orders directly from the web service platform 110. Wherein the consolidated order information includes at least two types of asset settlement data. For the merging of the two orders, the merging may be performed by the web services platform 110 while the orders are generated. Subsequently, the determining module 410 may perform a merge processing operation based on the merge processing identification, including performing separate settlement processing on the at least one type of asset settlement data in the form of distributed transactions to ensure consistent success or failure of the respective settlement processing. Thereafter, the determining module 430 may obtain a result of each settlement processing to determine a processing result of at least two orders corresponding to the consolidated order information.

It should be noted that the above description related to the flow 200 is only for illustration and description, and does not limit the applicable scope of the present specification. Various modifications and alterations to flow 200 will be apparent to those skilled in the art in light of this description. However, such modifications and variations are intended to be within the scope of the present description. For example, the steps of acquiring the merging process identifier corresponding to the two orders and determining whether to merge the at least two orders based on the merging process identifier in the flow 200 may be omitted. Or it can be appreciated that the process 200 defaults to merging the received at least two orders when there is no merging process identification.

Fig. 3 is an exemplary flow diagram of a distributed transaction processing method in accordance with some embodiments of the present description. In some embodiments, the process 300 may be performed by the network payment platform 130. For example, the process 300 may be stored in a storage device (e.g., an on-board storage unit or an external storage device of the network payment platform 130) in the form of a program or instructions that, when executed, may implement the process 300. In some embodiments, the process 300 may be performed by the processing module 420 of the order processing system 400, and the order processing system 400 may be part of the networked payment platform 130. As shown in fig. 3, the process 300 may include the following steps.

Step 302, the at least two types of asset settlement data are sent to the respective corresponding asset settlement nodes.

In some embodiments, the network payment platform 130 (or the processing module 420 of the order processing system 400) may send at least two types of settlement data to respective corresponding asset settlement nodes. The asset settlement node may include an asset system corresponding to an asset type or an asset manager designated by a user. For example, for an actual asset, the asset settlement node may be a bank asset system. For another example, for red-packed assets, the asset settlement node may be a red-packed system. In some embodiments, asset settlement may occur to an asset settlement node after receiving corresponding asset settlement data. For example, when the bank asset system receives at least two orders that need to pay 15 yuan of the user's assets within the bank asset system after being merged to complete the order payment, the bank asset system may deduct 15 yuan of the user's actual assets within the bank asset system if the constraint is satisfied (e.g., the user's actual assets cannot be less than 0).

At step 304, the settlement transaction execution results are queried from the asset settlement nodes.

In some embodiments, the settlement transaction execution result may be a result of asset settlement by an asset settlement node based on asset settlement data. Continuing with the example in step 302, when the bank asset system needs to settle the assets of the user therein (deducting 15 dollars), if the assets of the user in the bank asset system exceed 15 dollars, the asset settlement can be successfully completed, and the result of the settlement transaction can be successful. Otherwise, the execution result of the settlement transaction may be a failure.

Step 306, obtaining the settlement transaction execution result returned by each asset settlement node.

In some embodiments, after receiving the query, the asset settlement nodes may feed back an execution result to the network payment platform 130 (or the processing module 420 of the order processing system 400) according to the operation of performing the settlement transaction. The returned result may be "YES" or "success", indicating that the asset settlement operation has been successfully performed. Or "NO" or "failure," indicating that the asset settlement transaction operation failed.

And step 308, confirming whether the settlement transaction execution results returned by the asset settlement nodes are successful.

In some embodiments, the determination module 420 may determine whether the executed asset settlement data returned by each asset settlement node is successful based on the obtained execution result of the asset settlement data by each asset settlement node. If both are successful, the process 300 may proceed to step 310. If one or more are unsuccessful, the process 300 may proceed to step 312.

At step 310, each asset settlement node is instructed to submit the results of the settlement process.

In some embodiments, the result of submitting the settlement process may be understood as ultimately determining to perform the settlement process. For example, when the bank asset system needs to settle the assets in the bank asset system (deducting 15 dollars), if the assets in the bank asset system of the user exceed 15 dollars, such as 30 dollars, the bank asset system is successful in executing the settlement transaction. The user's assets in the bank asset system will change from 30-dollars to 15-dollars. And the result of submitting the settlement processing is the confirmation of the bank asset system for the settlement transaction again, and the settlement transaction is determined to be correct. In some embodiments, the asset settlement node will finalize the settlement transaction upon receiving an indication to submit the results of the settlement process.

At step 312, each asset settlement node is instructed to roll back its respective settlement transaction.

In some embodiments, the rollback may be understood as restoring the data to a state prior to the settlement of the transaction. For example, when the bank asset system and the red envelope system need to settle the assets of the user (for example, 15 dollars are deducted in the bank asset system and 10 dollars are deducted in the red envelope system), it is assumed that the assets of the user in the bank card system have 12 dollars and the assets in the red envelope system have 15 dollars. At this time, the execution result of the settlement transaction is successful (15>10) for the red envelope system, and the assets of the user are deducted to 5 yuan in the red envelope system. And the execution result of the settlement transaction of the bank asset system is failed (12<15), and the settlement cannot be completed. In this case, the execution results of the settlement transaction fed back by both asset settlement nodes are not both successful (one successful, one failed). The red envelope system will roll back the calculation transaction in which the user's assets will be changed from 5 to 15 before execution.

It should be noted that the above description of the process 300 is for illustration and description only and is not intended to limit the scope of the present disclosure. Various modifications and changes to flow 300 will be apparent to those skilled in the art in light of this description. However, such modifications and variations are intended to be within the scope of the present description.

FIG. 4 is a block diagram of an order processing system according to some embodiments of the present description. As shown in FIG. 4, the order processing system may include an acquisition module 410, a processing module 420, a determination module 430, an assistance module 440, and a transmission module 450.

The obtaining module 410 may be configured to obtain order information for at least two orders. The at least two orders may be orders to be processed, e.g. orders requiring payment to be made. The obtaining module 410 may further obtain a merging processing identifier corresponding to the order information of the at least two orders. The consolidated process identification may be an identification indicating whether the at least two orders support consolidated payment reconciliation. In some embodiments, the obtaining module 410 may obtain the order information of the at least two orders and the combined processing identifier corresponding to the at least two orders by communicating with a network service platform (e.g., the network service platform 110).

The processing module 420 may be configured to perform a merge processing operation on the at least two orders. The merge processing operation may be a simultaneous processing of the at least two orders, e.g. a data processing operation implemented in the form of a transaction. To implement the merge processing operation, the processing module 420 may obtain the merged order information based on the order information of the at least two orders. The merged order information may be information obtained by merging and/or adding the same items in the order information of the at least two orders. For example, the payment assets may be accumulated to obtain all payment assets that need to be paid. In some embodiments, the consolidated order information includes at least one type of asset settlement data. The asset settlement data may refer to a certain sum of assets used by the user when making order payments. For obtaining the asset settlement data, for each order, the processing module 420 may obtain the settlement data of each asset type in the order information of the order, and accumulate the settlement data of the same asset type of the at least two orders to obtain the asset settlement data corresponding to the asset type in the combined order information. After acquiring the consolidated order information, the processing module 420 may perform settlement processing on the at least two types of asset settlement data in a distributed transaction manner, so as to ensure consistent success or failure of each settlement processing.

In some embodiments, in order to perform settlement processing on multiple types of asset settlement data in a distributed transaction form, the processing module 420 may send the at least two types of asset settlement data to respective corresponding asset settlement nodes, and query each asset settlement node about a result of performing the settlement transaction, so as to obtain a result of performing the settlement transaction returned by each asset settlement node. The asset settlement node may include an asset system corresponding to an asset type or an asset manager designated by a user. The settlement transaction execution result may be a result of asset settlement by the asset settlement node based on the asset settlement data, including success or failure. Subsequently, the processing module 420 may confirm whether the results of the settlement transaction execution returned by the asset settlement nodes are both successful. If both are successful, the processing module 420 may instruct each asset settlement node to submit the results of the settlement process. Otherwise, the processing module 420 may instruct each asset settlement node to roll back the respective settlement transaction.

The determining module 430 may be configured to obtain a result of each settlement process to determine a processing result of at least two orders corresponding to the merged order information. The processing result may include that both of the at least two orders were processed successfully or that both of the orders were processed failed. When all the results of each settlement processing are successful, the determining module 430 determines that all the processing results of at least two orders in the corresponding consolidated order information are successful. When one or more processing results in each settlement processing result are failures, the determining module 430 determines that all of at least two order processing results in the corresponding consolidated order information are failures.

The auxiliary module 440 may be configured to add and lock the consolidated order identification to the consolidated order identification dataset before performing the consolidation processing operations on the at least two orders. After performing the merge processing operation on at least two orders, the assistance module 440 may delete the merged order identification from the merged order identification dataset.

The transmission module 450 may be configured to transmit the processing result of the at least two orders, for example, transmit a front-end application of the network payment platform 130, for example, a mobile application installed on a smartphone terminal for implementing the network payment platform 130.

Other descriptions of modules may refer to other parts of this specification, such as fig. 2-3.

It should be understood that the system and its modules shown in FIG. 4 may be implemented in a variety of ways. For example, in some embodiments, the system and its modules may be implemented in hardware, software, or a combination of software and hardware. Wherein the hardware portion may be implemented using dedicated logic; the software portions may be stored in a memory for execution by a suitable instruction execution system, such as a microprocessor or specially designed hardware. Those skilled in the art will appreciate that the methods and systems described above may be implemented using computer executable instructions and/or embodied in processor control code, such code being provided, for example, on a carrier medium such as a diskette, CD-or DVD-ROM, a programmable memory such as read-only memory (firmware), or a data carrier such as an optical or electronic signal carrier. The system and its modules in this specification may be implemented not only by hardware circuits such as very large scale integrated circuits or gate arrays, semiconductors such as logic chips, transistors, or programmable hardware devices such as field programmable gate arrays, programmable logic devices, etc., but also by software executed by various types of processors, for example, or by a combination of the above hardware circuits and software (e.g., firmware).

It should be noted that the above descriptions of the candidate item display and determination system and the modules thereof are only for convenience of description, and the description is not limited to the scope of the illustrated embodiments. It will be appreciated by those skilled in the art that, given the teachings of the present system, any combination of modules or sub-system configurations may be used to connect to other modules without departing from such teachings. For example, each module may share one memory module, and each module may have its own memory module. Such variations are within the scope of the present disclosure.

The beneficial effects that may be brought by the embodiments of the present description include, but are not limited to: (1) by adding the processing form of the distributed transaction in order payment, multiple orders in the same transaction are paid successfully or failed at the same time, and the consistency of the payment results of the multiple orders is ensured. (2) The affairs are initiated after the multiple orders are combined, and only one affair needs to be initiated for the multiple orders, so that the expense of the original N-1 affairs is saved, and the order processing timeliness is improved. (3) The orders are merged and then processed, when the asset system is called based on the asset settlement data in the orders, each related asset system is called only once, and the overhead of system interaction is saved. It is to be noted that different embodiments may produce different advantages, and in different embodiments, any one or combination of the above advantages may be produced, or any other advantages may be obtained.

Having thus described the basic concept, it will be apparent to those skilled in the art that the foregoing detailed disclosure is to be considered merely illustrative and not restrictive of the broad application. Various modifications, improvements and adaptations to the present application may occur to those skilled in the art, although not explicitly described herein. Such modifications, improvements and adaptations are proposed in the present application and thus fall within the spirit and scope of the exemplary embodiments of the present application.

Also, this application uses specific language to describe embodiments of the application. Reference throughout this specification to "one embodiment," "an embodiment," and/or "some embodiments" means that a particular feature, structure, or characteristic described in connection with at least one embodiment of the present application is included in at least one embodiment of the present application. Therefore, it is emphasized and should be appreciated that two or more references to "an embodiment" or "one embodiment" or "an alternative embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, some features, structures, or characteristics of one or more embodiments of the present application may be combined as appropriate.

Moreover, those skilled in the art will appreciate that aspects of the present application may be illustrated and described in terms of several patentable species or situations, including any new and useful combination of processes, machines, manufacture, or materials, or any new and useful improvement thereon. Accordingly, various aspects of the present application may be embodied entirely in hardware, entirely in software (including firmware, resident software, micro-code, etc.) or in a combination of hardware and software. The above hardware or software may be referred to as "data block," module, "" engine, "" unit, "" component, "or" system. Furthermore, aspects of the present application may be represented as a computer product, including computer readable program code, embodied in one or more computer readable media.

The computer storage medium may comprise a propagated data signal with the computer program code embodied therewith, for example, on baseband or as part of a carrier wave. The propagated signal may take any of a variety of forms, including electromagnetic, optical, etc., or any suitable combination. A computer storage medium may be any computer-readable medium that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code located on a computer storage medium may be propagated over any suitable medium, including radio, cable, fiber optic cable, RF, or the like, or any combination of the preceding.

Computer program code required for the operation of various portions of the present application may be written in any one or more programming languages, including an object oriented programming language such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C + +, C #, VB.NET, Python, and the like, a conventional programming language such as C, Visual Basic, Fortran 2003, Perl, COBOL 2002, PHP, ABAP, a dynamic programming language such as Python, Ruby, and Groovy, or other programming languages, and the like. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any network format, such as a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet), or in a cloud computing environment, or as a service, such as a software as a service (SaaS).

Additionally, the order in which elements and sequences of the processes described herein are processed, the use of alphanumeric characters, or the use of other designations, is not intended to limit the order of the processes and methods described herein, unless explicitly claimed. While various presently contemplated embodiments of the invention have been discussed in the foregoing disclosure by way of example, it is to be understood that such detail is solely for that purpose and that the appended claims are not limited to the disclosed embodiments, but, on the contrary, are intended to cover all modifications and equivalent arrangements that are within the spirit and scope of the embodiments herein. For example, although the system components described above may be implemented by hardware devices, they may also be implemented by software-only solutions, such as installing the described system on an existing server or mobile device.

Similarly, it should be noted that in the preceding description of embodiments of the application, various features are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure aiding in the understanding of one or more of the embodiments. This method of disclosure, however, is not intended to require more features than are expressly recited in the claims. Indeed, the embodiments may be characterized as having less than all of the features of a single embodiment disclosed above.

Numerals describing the number of components, attributes, etc. are used in some embodiments, it being understood that such numerals used in the description of the embodiments are modified in some instances by the use of the modifier "about", "approximately" or "substantially". Unless otherwise indicated, "about", "approximately" or "substantially" indicates that the number allows a variation of ± 20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximations that may vary depending upon the desired properties of the individual embodiments. In some embodiments, the numerical parameter should take into account the specified significant digits and employ a general digit preserving approach. Notwithstanding that the numerical ranges and parameters setting forth the broad scope of the range are approximations, in the specific examples, such numerical values are set forth as precisely as possible within the scope of the application.

The entire contents of each patent, patent application publication, and other material cited in this application, such as articles, books, specifications, publications, documents, and the like, are hereby incorporated by reference into this application. Except where the application is filed in a manner inconsistent or contrary to the present disclosure, and except where the claim is filed in its broadest scope (whether present or later appended to the application) as well. It is noted that the descriptions, definitions and/or use of terms in this application shall control if they are inconsistent or contrary to the statements and/or uses of the present application in the material attached to this application.

Finally, it should be understood that the embodiments described herein are merely illustrative of the principles of the embodiments of the present application. Other variations are also possible within the scope of the present application. Thus, by way of example, and not limitation, alternative configurations of the embodiments of the present application can be viewed as being consistent with the teachings of the present application. Accordingly, the embodiments of the present application are not limited to only those embodiments explicitly described and depicted herein.

Claims

1. An order processing method, wherein the method comprises:

obtaining order information of at least two orders;

performing a merge processing operation on the at least two orders, the merge processing operation comprising:

acquiring combined order information based on the order information of the at least two orders, wherein the combined order information comprises at least one type of asset settlement data;

and, separately performing settlement processing on the at least one type of asset settlement data in a distributed transaction form to ensure consistent success or failure of each settlement processing;

and acquiring the result of each settlement processing to determine the processing results of at least two orders corresponding to the combined order information.

2. The method of claim 1, wherein said separately performing settlement processing on said at least two types of asset settlement data in the form of distributed transactions to ensure consistent success or failure of each settlement processing comprises:

sending the at least two types of asset settlement data to the respective corresponding asset settlement nodes;

inquiring the settlement transaction execution result from each asset settlement node;

acquiring a settlement transaction execution result returned by each asset settlement node;

if the settlement transaction execution results returned by the asset settlement nodes are successful, indicating the asset settlement nodes to submit the settlement processing results;

and if the settlement transaction execution result returned by at least one asset settlement node is failure, indicating each asset settlement node to roll back the respective settlement transaction.

3. The method of claim 2, wherein the determining the processing result of the at least two orders corresponding to the merged order information comprises:

if the settlement transaction execution results returned by the asset settlement nodes are successful, determining that the processing results of the at least two orders are successful;

and if the settlement transaction execution result returned by at least one asset settlement node is failure, determining that the processing results of the at least two orders are processing failures.

4. The method of claim 1, wherein the obtaining consolidated order information based on the order information of the at least two orders comprises:

for each order, acquiring settlement data of each asset type in order information of the order;

and accumulating the settlement data of the same asset type of the at least two orders to obtain the asset settlement data corresponding to the asset type in the combined order information.

5. The method of claim 1, wherein the consolidated order information further comprises a consolidated order identification;

before performing the merge processing operation on the at least two orders, the method further comprises:

adding the merged order mark to a merged order mark data set and locking;

after the merge processing operation, the method further comprises:

and deleting the merged order identification from the merged order identification data set.

6. The method of claim 1, wherein the method further comprises:

and sending the processing results of the at least two orders.

7. The method of claim 1, wherein the method further comprises:

acquiring a merging processing identifier corresponding to the at least two orders;

the performing a merge processing operation on the at least two orders includes: and executing a merging processing operation on the at least two orders based on the merging processing identifier.

8. An order processing method, wherein the method comprises:

acquiring consolidated order information determined by order information of at least two orders, wherein the consolidated order information comprises at least one type of asset settlement data;

executing a merging processing operation on the merged order information, wherein the merging processing operation comprises:

performing settlement processing on the at least two types of asset settlement data in a distributed transaction mode respectively to ensure the consistent success or failure of each settlement processing;

9. An order processing system, wherein the system comprises:

the acquisition module is used for acquiring order information of at least two orders;

a processing module, configured to perform a merge processing operation on the at least two orders, where the merge processing operation includes:

acquiring combined order information based on the order information of the at least two orders, wherein the combined order information comprises at least two types of asset settlement data;

and performing settlement processing on the at least two types of asset settlement data in a distributed transaction mode respectively to ensure the consistent success or failure of each settlement processing;

and the determining module is used for acquiring the result of each settlement processing so as to determine the processing results of at least two orders corresponding to the combined order information.

10. The system of claim 9, wherein to separately perform settlement processing on the at least two types of asset settlement data in the form of distributed transactions to ensure consistent success or failure of each settlement processing, the processing module is configured to:

11. The system of claim 10, wherein to determine the processing results of at least two orders corresponding to the consolidated order information, the determining module is configured to:

12. The system of claim 9, wherein to obtain consolidated order information based on order information for at least two orders, the determination module is to:

13. The system of claim 9, wherein the consolidated order information further comprises a consolidated order identification; the system further includes an assistance module to, prior to performing a merge processing operation on the at least two orders:

adding the merged order mark to a merged order mark data set and locking;

after the merge processing operation, the assistance module is to:

14. The system of claim 9, wherein the system further comprises:

and the transmission module is used for transmitting the processing results of the at least two orders.

15. The system of claim 9, wherein the obtaining module is further configured to obtain a merged process identifier corresponding to the at least two orders;

the processing module is further configured to: and executing a merging processing operation on the at least two orders based on the merging processing identifier.

16. An order processing apparatus, wherein the apparatus comprises a processor for performing the method of claims 1-7.