CN114004701A

CN114004701A - Method and device for generating transaction result, electronic equipment and storage medium

Info

Publication number: CN114004701A
Application number: CN202111310077.5A
Authority: CN
Inventors: 杨铿; 徐广强; 程灿权; 郁巍
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2021-11-05
Filing date: 2021-11-05
Publication date: 2022-02-01

Abstract

The disclosure provides a method and a device for generating a transaction result, an electronic device and a storage medium. The method can be used in the technical field of big data and also can be used in the technical field of finance. The method comprises the following steps: receiving a transaction request from a channel end application; generating respective intermediate transaction results for the transaction requests in response to the transaction requests; sending each intermediate transaction result to distributed message queue middleware; and after the information consumer acquires each intermediate transaction result from the distributed message queue middleware, generating a final transaction result aiming at the transaction request according to each intermediate transaction result.

Description

Method and device for generating transaction result, electronic equipment and storage medium

Technical Field

The present disclosure relates to the field of big data, financial technology, and more particularly, to a method and apparatus for generating a transaction result, an electronic device, a computer-readable storage medium, and a computer program product.

Background

Under the current distributed framework system, in the process of processing a large number of transactions, a financial institution can identify business objects and business behaviors at different business levels, for example, by media, accounts, protocols and the like to form different processing nodes, and the cooperative work of each node is well done through distributed storage data of different business nodes. In this process, it is very important to ensure consistency of transaction data of different business layers.

In the process of implementing the concept disclosed by the present disclosure, the inventor finds that in the related art, at least the following problems exist, the final result of the transaction cannot be obtained in real time due to low timeliness in the conventional accounting processing mode, the user or business personnel cannot perform real-time account checking to confirm the consistency of transaction data of each business layer, and the user experience is poor.

Disclosure of Invention

In view of the above, the present disclosure provides a method and apparatus for generating a transaction result, an electronic device, a computer-readable storage medium, and a computer program product.

One aspect of the present disclosure provides a method of generating a transaction result, comprising:

receiving a transaction request from a channel end application;

generating respective intermediate transaction results for the transaction requests in response to the transaction requests;

sending each intermediate transaction result to distributed message queue middleware;

and after the information consumer acquires each intermediate transaction result from the distributed message queue middleware, generating a final transaction result aiming at the transaction request according to each intermediate transaction result.

According to an embodiment of the present disclosure, wherein: the information consumer includes at least one of: the system comprises a channel end application, execution nodes and a main control node, wherein the execution nodes are used for generating intermediate transaction results, and the main control node is used for responding to a transaction request and calling the execution nodes to execute and generate the intermediate transaction results.

According to an embodiment of the present disclosure, wherein: the execution node comprises a debit application node and a credit application node, wherein the debit application node is used for executing deduction of a preset amount from a preset debit account and generating an intermediate transaction result indicating whether the deduction is successful, and the credit application node is used for executing account posting of the preset amount to the preset credit account and generating an intermediate transaction result indicating whether the account posting is successful.

According to an embodiment of the present disclosure, further comprising, in case it is determined that the final transaction result for the transaction request is a failure according to the respective intermediate transaction results: and calling the debit application node through the information consumer to execute the refund of the preset amount of money to the preset debit account.

According to an embodiment of the present disclosure, further comprising:

generating a final transaction result for the transaction request in response to the transaction request; and

and sending the final transaction result to the distributed message queue middleware so that the information consumer can obtain the final transaction result from the distributed message queue middleware.

According to an embodiment of the present disclosure, wherein generating, in response to the transaction request, a final transaction result for the transaction request comprises:

responding to the transaction request, calling each execution node through the main control node to generate each intermediate transaction result;

and after the main control node acquires each intermediate transaction result from each execution node, generating a final transaction result according to each intermediate transaction result.

Another aspect of the present disclosure provides an apparatus for generating a transaction result, including a receiving module, a first generating module, a first sending module, and a second generating module.

The receiving module is used for receiving a transaction request from the channel end application.

The first generating module is used for responding to the transaction request and generating each intermediate transaction result aiming at the transaction request.

And the first sending module is used for sending each intermediate transaction result to the distributed message queue middleware.

And the second generation module is used for generating a final transaction result aiming at the transaction request according to each intermediate transaction result after each intermediate transaction result is obtained from the distributed message queue middleware through the information consumer.

According to an embodiment of the present disclosure, the method further includes, in case that it is determined that the final transaction result for the transaction request is a failure according to each intermediate transaction result: and calling the debit application node through the information consumer to execute the refund of the preset amount of money to the preset debit account.

According to the embodiment of the disclosure, the device further comprises a third generating module and a second sending module.

Wherein the third generating module is used for responding to the transaction request and generating a final transaction result aiming at the transaction request; and the second sending module is used for sending the final transaction result to the distributed message queue middleware so that the information consumer can obtain the final transaction result from the distributed message queue middleware.

According to the embodiment of the disclosure, the third generation module comprises a calling unit and a generation unit.

The calling unit is used for responding to the transaction request and calling each execution node through the main control node to generate each intermediate transaction result; and the generating unit is used for generating a final transaction result according to each intermediate transaction result after each intermediate transaction result is obtained from each execution node through the main control node.

Another aspect of the present disclosure provides an electronic device including: one or more processors, and a memory; wherein the memory is for storing one or more programs; wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of generating transaction results as described above.

Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions for implementing a method of generating transaction results as described above when executed.

Another aspect of the disclosure provides a computer program product comprising computer executable instructions for implementing a method of generating transaction results as described above when executed.

According to the embodiment of the disclosure, the method provides a background real-time reconciliation method applied to a transaction process. By generating transaction key information in the transaction process in the background and sending each intermediate transaction result of the transaction request to the distributed message queue middleware, the information consumer can obtain the intermediate results of different transaction links in real time and then generate a final transaction result aiming at the transaction request according to each intermediate transaction result, and uncertain results of financial affairs are not generated because clear responses aiming at the transaction request are not obtained in time due to network fluctuation, connection overtime and the like. And by sending each intermediate transaction result of the transaction request to the distributed message queue middleware, any type of information consumer can acquire the transaction result from the distributed message queue middleware according to respective business requirements, consume the actual posting condition of the underlying account, then check the accounts according to the consumed key transaction information, acquire the error condition in time, check and process in time on the aspect of accounts, and finally ensure the capability of providing transaction consistency for online services in the accounting processing process, thereby not only improving the timeliness of accounting processing and optimizing user experience, but also being applicable to independent reconciliation of distributed multi-application nodes.

By the method of the embodiment of the disclosure, all links in the whole transaction link, including the upstream link and the downstream link, can send the transaction elements to the intermediate message queue in a quasi-real-time manner. Each application node can also take the transaction elements from the intermediate message queue in a quasi-real-time manner, and carry out quasi-real-time accounting checking according to the obtained transaction elements and the transaction log of the application node, so that the accounting consistency is ensured through a re-calling manner such as correcting, deducting and the like in the following, a complete closed-loop flow of data production, data acquisition, accounting checking and accounting adjustment is conveniently formed, and the accounting consistency is ensured.

Drawings

The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments of the present disclosure with reference to the accompanying drawings, in which:

FIG. 1 schematically illustrates an exemplary system architecture to which the method and apparatus of generating transaction results of the present disclosure may be applied;

fig. 2 is a schematic diagram schematically showing a method of generating a transaction result in the related art;

FIG. 3 schematically shows a flow diagram of a method of generating transaction results according to an embodiment of the present disclosure;

FIG. 4 schematically shows a schematic diagram of pushing intermediate transaction results and final transaction results to distributed message queue middleware according to an embodiment of the disclosure;

FIG. 5 schematically illustrates a method of generating a transaction result where the information consumer is a borrower application node, in accordance with an embodiment of the disclosure;

FIG. 6 schematically illustrates a method of generating a transaction result where the information consumer is a lender application node, according to an embodiment of the disclosure;

FIG. 7 schematically illustrates a method of generating a transaction result where the information consumer is a master node, according to an embodiment of the disclosure;

FIG. 8 is a schematic diagram illustrating a method of generating transaction results where the information consumer is a channel-side application, according to an embodiment of the disclosure;

FIG. 9 schematically illustrates a block diagram of an apparatus for generating transaction results according to an embodiment of the disclosure; and

fig. 10 schematically illustrates a block diagram of an electronic device for implementing a method of generating transaction results according to an embodiment of the present disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

An embodiment of the present disclosure provides a method of generating a transaction result, including:

receiving a transaction request from a channel end application;

Before the embodiments of the present disclosure are explained in detail, the system structure and the application scenario related to the method provided by the embodiments of the present disclosure are described as follows.

Fig. 1 schematically illustrates an exemplary system architecture 100 to which the method and apparatus of generating transaction results of the present disclosure may be applied. It should be noted that fig. 1 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.

As shown in fig. 1, the system architecture 100 according to this embodiment may include

terminal devices

101, 102, 103, a network 104 and a server 105. The network 104 serves as a medium for providing communication links between the

terminal devices

101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired and/or wireless communication links, and so forth.

The user may use the

terminal devices

101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The

terminal devices

101, 102, 103 may have various messaging client applications installed thereon, such as a transfer transaction application, a shopping application, a web browser application, a search application, an instant messaging tool, a mailbox client, and/or social platform software for each financial institution, and the like (by way of example only).

The

terminal devices

101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 105 may be a server that provides various services, such as a background management server that provides support for websites browsed by users using the

terminal devices

101, 102, 103. (the server 105 may be a server providing various services, including but not limited to service one, service two, service three, service four, and so on, and service one, service two, service three, and service four may be, for example, services providing support for websites browsed by users using the

terminal devices

101, 102, and 103.) the background management server may analyze and process data such as received user requests, and feed back processing results (e.g., web pages, information, or data obtained or generated according to the user requests) to the terminal devices.

In the application scenario of the embodiment of the present disclosure, transaction applications in different channels, such as mobile banking, internet banking, electronic banking, and the like, may be installed on the

terminal devices

101, 102, and 103, and a user may initiate a transaction request, such as a transfer transaction, to the server 105 through the network 104 by using the client applications of the

terminal devices

101, 102, and 103.

According to the embodiment of the disclosure, after receiving the transaction requests of the

terminal devices

101, 102, 103, the server 105 invokes the respective execution application nodes to execute the corresponding transaction operations in response to the transaction requests, generates the transaction results for the transaction requests, and returns the transaction results to the

terminal devices

101, 102, 103.

According to the embodiment of the disclosure, after the server 105 invokes each execution application node to execute the corresponding transaction operation, each intermediate transaction result for the transaction request may also be generated by each application execution node, and each intermediate transaction result is sent to the distributed message queue middleware, and after each intermediate transaction result is obtained from the distributed message queue middleware by the information consumer, a final transaction result for the transaction request is generated according to each intermediate transaction result. The

terminal devices

101, 102, 103 may obtain respective intermediate transaction results and final transaction results from the distributed message queue middleware.

It should be noted that the method for generating transaction results provided by the embodiments of the present disclosure may be generally performed by the server 105. Accordingly, the apparatus for generating transaction results provided by the embodiments of the present disclosure may be generally disposed in the server 105. The method of generating transaction results provided by the embodiments of the present disclosure may also be performed by a server or a cluster of servers different from the server 105 and capable of communicating with the

terminal devices

101, 102, 103 and/or the server 105. Accordingly, the apparatus for generating transaction results provided by the embodiments of the present disclosure may also be disposed in a server or a server cluster different from the server 105 and capable of communicating with the

terminal devices

101, 102, 103 and/or the server 105. Alternatively, the method for generating the transaction result provided by the embodiment of the present disclosure may also be executed by the

terminal device

101, 102, or 103, or may also be executed by another terminal device different from the

terminal device

101, 102, or 103. Accordingly, the apparatus for generating the transaction result provided by the embodiment of the present disclosure may also be disposed in the

terminal device

101, 102, or 103, or in another terminal device different from the

terminal device

101, 102, or 103.

It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

It should be noted that the method and apparatus for generating transaction results of the present disclosure may be used in the field of big data technology, financial technology, or any field except the field of big data technology and financial technology, and the application fields of the method and apparatus for generating transaction results are not limited by the present disclosure.

In the technical scheme of the disclosure, the acquisition, storage, application and the like of the personal information of the related user all accord with the regulations of related laws and regulations, necessary security measures are taken, and the customs of the public order is not violated.

Under the current distributed framework system, in the process of processing a large number of transactions, a financial institution can identify business objects and business behaviors at different business levels, for example, by media, accounts, protocols and the like to form different processing nodes, and the cooperative work of each node is well done through distributed storage data of different business nodes. In this process, it is very important to ensure consistency of transaction data of different business layers. However, according to the CAP theory, only two of the three of availability, partition tolerance and consistency can be satisfied at the same time, and if the availability (a) and the partition tolerance (P) are to be satisfied, the consistency (C) needs to be sacrificed.

In the related art, the common practice is to give up real-time consistency and guarantee final consistency by a more complex application design according to the service characteristics to solve the problem. The consistency of the accounts is relatively critical, and particularly for the financial industry, the physical examination of the user is directly influenced by the consistency of the accounts. In general, accounting processing can only see the inconsistency problem of accounting through daily final clearing, so that the timeliness of processing the problem is low. In addition, for the accounting system under the distributed framework, different applications are different facing client groups, and if accounting information can be obtained by uniformly clearing at the end of day, the accounting information is sent to each application to execute account adjustment processing, so that the processing process is complicated. Namely, the related art has at least the following problems that the traditional accounting processing mode cannot acquire the final result of the transaction in real time due to low timeliness, and users or business personnel cannot check accounts in real time to confirm the consistency of transaction data of each business layer, so that the user experience is poor.

In the related art, under a distributed system architecture, a financial institution internally identifies business objects and business behaviors through media, accounts, protocols and the like, and splits a single system into a plurality of loosely-coupled, single-function and mutually-coordinated applications to form different application nodes: such as internet banking, cell phone banking, protocol applications, media applications, debit card application nodes, credit card applications, etc.

Fig. 2 is a schematic diagram schematically showing a method of generating a transaction result in the related art.

As shown in fig. 2, taking a transfer transaction as an example, a channel side application (for example, a mobile phone bank, an internet bank, an electronic bank, etc.) initiates a request for the transfer transaction, and a master control application S (for example, a remittance application) calls each execution node to execute a relevant transaction operation after receiving the request. The executing nodes comprise a protocol application node A, a medium application node B, a debit application node C and a credit application node D. The transaction is firstly checked through the internet bank interconnection protocol by the protocol application node A, then is checked through the medium by the medium application node B (card state and account name), then is deducted through the debit application node C, and finally is checked through the credit application node D, and the deducted debit amount is stored into the account of the credit, so that the whole transaction is completed. The final transaction result E of the transaction can be finally obtained only through the protocol application node A, the medium application node B, the debit application node C and the credit application node D in the whole transaction process, after the main control application S obtains the transaction result E, the transaction result E is returned to the channel end for application, and the transaction is finished.

As can be seen from the example shown in fig. 2, the channel end needs to execute a complete transaction process to obtain the final transaction result E. The traditional accounting processing mode is low in timeliness, the final result of the transaction cannot be obtained in real time, a user or business personnel cannot check accounts in real time to confirm the consistency of transaction data of each business layer, and user experience is poor.

According to the embodiment of the disclosure, each link of the whole transaction link can generate respective intermediate transaction results in real time, for example, the debit application node C can generate transaction results that are successful or failed in deduction after executing deduction operation, the credit application node D can also generate transaction results that are successful or failed in posting after executing posting operation, and if the intermediate transaction results can be obtained in real time, a final transaction result can be obtained according to the intermediate transaction results. For example, if the debit application node C is successfully deducted and the credit application node D is unsuccessfully credited in real time, the final transaction result of the transaction may be unsuccessfully obtained, and it is not necessary to wait until the whole transaction process is executed to obtain the transaction result. In addition, in an actual application scenario, there is no need for obtaining a transaction result only in a channel-side application, and if each application node, such as a debit application node C, a credit application node, a master control application S, can obtain an intermediate result in real time, real-time reconciliation can be performed according to respective business requirements, so that timeliness and consistency of accounting processing can be improved.

In view of the above, based on the above concept, embodiments of the present disclosure provide a method of generating a transaction result.

Fig. 3 schematically shows a flow chart of a method of generating transaction results according to an embodiment of the present disclosure.

As shown in fig. 3, the method includes operations S301 to S304.

In operation S301, a transaction request from a channel-side application is received.

According to the embodiment of the disclosure, the channel end application can be various types of client end applications, for example, mobile banking, internet banking, electronic banking and the like. The transaction request may be various types of transaction requests, such as transfers, account inquiries, and the like. The user may initiate the transaction request through the channel side application using various terminal devices (e.g., smart phones, tablets, laptop portable computers, desktop computers, etc.).

In operation S302, in response to the transaction request, respective intermediate transaction results for the transaction request are generated.

In operation S303, the respective intermediate transaction results are sent to the distributed message queue middleware. According to an embodiment of the present disclosure, the distributed message queue middleware may be, for example, a Kafka queue. By utilizing the characteristic that kafka is decoupled from information producers (producers) and consumers (consumers), different information consumers can obtain the same message data from a single message stream without influencing each Consumer.

According to the embodiment of the disclosure, the method for generating the transaction result is implemented based on a distributed system, under the architecture of the distributed system, a financial institution identifies a service object and a service behavior through a medium, an account, a protocol and the like, and splits the financial institution into a plurality of applications cooperating with each other to form different application nodes, which may include a master control application node (such as a remittance application, a query application and the like) suitable for various service requirements, and a plurality of execution nodes under various service types called by the master control application node, such as a protocol application node, a medium application node, a debit application node, a credit application node and the like.

According to the embodiment of the disclosure, in response to a transaction request, the back end calls a plurality of execution nodes under each service type through the master control application node to complete each operation link on the transaction link.

According to the embodiment of the disclosure, in each link of the whole transaction link, each application node may generate respective intermediate transaction results in real time, for example, after the debit application node and the credit application node perform the deduction and the check-in operations, transaction results of successful or failed deduction or check-in may be generated.

The intermediate transaction results may include transaction elements such as transaction identification, amount, currency, and the like. As shown in table 1, which is an example of an intermediate transaction result generated by a borrower application node, after a transaction is completed, each application node may register transaction key information, that is, an intermediate transaction result, to a log table after processing its own service data, and push transaction elements of its own transaction result, unique identifier, amount of money, currency, and the like to an intermediate message queue in the form of asynchronous push kafka message without affecting its own transaction, thereby completing the quasi-real-time production of transaction data. The lender application node and the master application node also produce transaction data in the same manner.

TABLE 1

Unique identification

Card number

Amount of money

Lending mark

Coin kind

Sign for positive and negative cross

Transaction results

AAAA

123xx

xxx

Borrowing money

BB

Positive trade

Success/failure

In operation S304, after each intermediate transaction result is obtained from the distributed message queue middleware through the information consumer, a final transaction result for the transaction request is generated according to each intermediate transaction result.

According to embodiments of the present disclosure, an information consumer may be any subject that needs to obtain an intermediate transaction result or a final transaction result. In an actual application scenario, the information consumers can acquire the intermediate result in real time, so as to execute real-time account checking according to respective business requirements.

According to the embodiment of the disclosure, in response to a transaction request, the back end calls a plurality of execution nodes under each service type through the master control application node to complete each operation link on the transaction link. For example, after receiving the request, the master control application node (e.g., remittance application) calls the protocol application node to perform internet banking interconnection protocol check, then calls the media application node to perform media check (card status and account name check) of the transaction, then calls the debit application node to deduct the amount of the debit account, finally calls the credit application node to perform an account posting operation, and then credits the deducted debit amount into the account of the credit, thereby completing the entire transaction. In the whole transaction process, each execution node generates respective intermediate transaction results after completing respective transaction operations, such as transaction elements of transaction identification, money amount, currency and the like.

According to an embodiment of the present disclosure, the information consumer may be any subject that needs to obtain an intermediate transaction result or a final transaction result, and may include, but is not limited to, a channel end application, each execution node, and a master node. In an actual application scenario, not only the channel-side application has a requirement for obtaining a transaction result, but also each application node may have a requirement for obtaining a transaction result, so as to perform real-time reconciliation according to respective business requirements.

According to the embodiment of the disclosure, because the application nodes of each link in the transaction link, including the channel end application, each execution node and the master control node, can acquire the transaction result from the distributed message queue middleware according to respective business requirements, the transaction link links can conveniently perform accounting check according to the consumed key transaction information, timely acquire error conditions, and can timely check and process on the account level, thereby finally ensuring the capability of providing transaction consistency in the accounting processing process of the online service.

According to the embodiment of the present disclosure, the executing node depends on the service requirement, and any type of executing application node related to the transaction according to the service requirement may be used, and is not limited to the debit application node and the credit application node, and for example, a protocol application node for executing internet banking protocol check, a media application node for executing media check (card status, account name check) of the transaction, and the like may also be included.

According to an embodiment of the present disclosure, further comprising: generating a final transaction result for the transaction request in response to the transaction request; and sending the final transaction result to the distributed message queue middleware so that the information consumer can obtain the final transaction result from the distributed message queue middleware.

According to an embodiment of the present disclosure, wherein generating, in response to the transaction request, a final transaction result for the transaction request comprises: responding to the transaction request, calling each execution node through the main control node to generate each intermediate transaction result; and after the main control node acquires each intermediate transaction result from each execution node, generating a final transaction result according to each intermediate transaction result.

Fig. 4 schematically shows a schematic diagram of pushing intermediate transaction results and final transaction results to distributed message queue middleware according to an embodiment of the present disclosure.

As shown in fig. 4, according to the embodiment of the present disclosure, in response to a transaction request, a back end invokes, through a master application node, a plurality of execution nodes under each service type to complete each operation link on the transaction link. For example, after receiving the request, the main control application node S (e.g., remittance application) calls the borrower application node C to deduct the amount of the borrower account, generates an intermediate transaction result-1, calls the lender application node D to perform an account posting operation, and generates an intermediate transaction result-2, and after obtaining each of the intermediate transaction results result-1 and result-2 from each of the execution nodes, the main control application node S generates a final transaction result-3 according to result-1 and result-2. For example, if result-1 is a cash-in success, result-2 is an account-in failure, and the final transaction result-3 is a transaction failure.

According to the embodiment of the disclosure, each application node pushes the respective transaction result, including the intermediate transaction result and the final transaction result, to the distributed message queue middleware, so that the information consumer can obtain not only the intermediate transaction result but also the final transaction result from the distributed message queue middleware, the consumer can obtain corresponding transaction result data according to business requirements, various business requirements can be met, and the application scene is wider.

According to the embodiment of the disclosure, the transaction success or failure can be determined in time by consuming the intermediate transaction result in real time, and under the condition of transaction failure, the debit application node can be called in time to execute the refund of the preset amount of money to the preset debit account, so that the timeliness of financial processing is improved, and the user experience is improved.

Fig. 5, 6, 7 and 8 are schematic diagrams illustrating a method for generating transaction results in a scenario in which a plurality of different types of applications are used as information consumers, respectively. The following description is made separately.

Fig. 5 schematically shows a method for generating a transaction result in the case that the information consumer is a debit application node according to an embodiment of the disclosure.

As shown in fig. 5, after receiving the request, the master application node S (e.g., remittance application) calls the borrower application node C to deduct the amount of the borrower account, and generates an intermediate transaction result-1, calls the lender application node D to perform a posting operation, and generates an intermediate transaction result-2, and after obtaining each of the intermediate transaction results result-1 and result-2 from each of the execution nodes, the master application node S generates a final transaction result-3 according to the result-1 and result-2. Wherein, result-1 is that the deduction is successful, result-2 is that the posting is failed, and the final transaction result-3 is that the transaction is failed.

Each application node will push the respective transaction results, including the intermediate transaction results and the final transaction results, to the distributed message queue middleware Kafka.

In the application scene, the debit application node C serves as a Consumer Consumer-1, and before the master control application node S generates a final transaction result-3, the debit application node C consumes from Kafka to result-1 and result-2, and the final transaction result is transaction failure according to the result-1 that the deduction is successful and the result-2 that the account is lost. The debit application node C can also directly consume the final transaction result-3 from Kafka after the master control application node S generates the final transaction result-3.

After the borrower application node C obtains a final transaction result, the account processing is carried out according to the obtained actual result under the condition that the credit account entering is failed definitely and the transaction result is also failed, the borrower application node C carries out the operation of correcting the borrower transaction in real time and refunds the deduction account, so that the quasi-real-time financial regulation is realized, account checking and refund are not carried out until the end of the day, and the problem of timeliness processing is improved.

Fig. 6 schematically shows a method for generating a transaction result in the case where the information consumer is a lender application node according to an embodiment of the disclosure.

Unlike the scenario shown in FIG. 5, the lender application node D acts as Consumer Consumer-2. In different service scenarios, according to different service requirements, some services may be the master control of the debit application node C, some services may be the master control of the credit application node D, and may also be the master control of other application nodes, so that there is a demand for consuming data by different application nodes. The scene is suitable for the condition that the debit application cannot acquire the financial data in a quasi-real-time manner to check the financial data.

The lender application node D serves as a Consumer Consumer-2, and can consume from Kafka to result-1 and result-2 before the master control application node S generates a final transaction result-3, and the final transaction result is obtained as transaction failure according to the result-1 that the deduction is successful and the result-2 that the account is entered is failure. The lender application node D may also consume the final transaction result-3 directly from Kafka after the master application node S generates the final transaction result-3.

After the lender application node D obtains the final transaction result, it is confirmed that the lender posting is failed, but the borrower deduction is successful, and the financial error problem of lending or not exists, and the borrower application node C needs to be called to execute a correction operation service to refund.

Fig. 7 schematically shows a method for generating a transaction result in a case where the information consumer is a master node according to an embodiment of the present disclosure.

In the application scenario, the master application node S serves as a Consumer-3. The master control application node S is used as a master transaction for serially connecting the whole transaction, and after the transaction flow is carried out to the lender application node D, the lender application node D does not obtain a final transaction result due to various interference factors, for example, due to network delay, the lender application node D does not feed back the transaction result to the master control application node S in time, and the master control application node S can only return an unknown transaction result to the channel end. At this time, it can become a Consumer-3 to obtain the transaction information of other applications, from Kafka consumption to debit transaction information (Result-1) and credit transaction information (Result-2), and then perform accounting check according to Result-1 and Result-2, if there is a deviation with the final transaction Result-3 returned by the master control application node S itself, then adjust the accounting in time: namely, under the condition that the transaction of the debit transaction result (result-1) is successful, but the actual transaction of the credit transaction result (result-2) is failed, the master control application node S calls the debit application node C to refund, and pushes result-3 which is the failure result of the transaction to the channel end application.

Fig. 8 schematically shows a method for generating a transaction result in the case that the information consumer is a channel-side application according to an embodiment of the disclosure.

In the application scenario, the channel-side application serves as Consumer Consumer-3. After the transaction flow is conducted to the lender application node D, the lender application node D does not obtain a final transaction result due to various interference factors, for example, due to network delay, the lender application node D does not feed back the transaction result to the master control application node S in time, and the master control application node S can only return an unknown transaction result to the channel end. At the moment, the channel-side application can become a Consumer-3 to acquire transaction information of other applications, from Kafka consumption to debit transaction information (result-1) and credit transaction information (result-2), and then account checking is carried out according to success of result-1 and success of result-2, so that the final transaction result is successful.

According to the embodiment of the disclosure, through the introduction of the scene that various different types of applications are used as information consumers, the method can find the accounting problem in a quasi-real time manner, different applications can perform accounting checking processing, and accounting adjustment is performed by adopting a service calling mode.

Fig. 9 schematically shows a block diagram of an apparatus 900 for generating transaction results according to an embodiment of the present disclosure.

The apparatus 900 may be used to implement the method described with reference to fig. 3.

As shown in fig. 9, the apparatus includes a receiving module 901, a first generating module 902, a first transmitting module 903, and a second generating module 904.

The receiving module 901 is configured to receive a transaction request from a channel-side application.

A first generating module 902 is configured to generate respective intermediate transaction results for the transaction request in response to the transaction request.

A first sending module 903, configured to send each intermediate transaction result to the distributed message queue middleware.

And a second generating module 904, configured to generate a final transaction result for the transaction request according to each intermediate transaction result after the information consumer obtains each intermediate transaction result from the distributed message queue middleware.

According to the embodiment of the disclosure, the background real-time account checking applied to the transaction process is realized through the device. The first generating module 902 generates transaction key information in the transaction process, the first sending module 903 sends each intermediate transaction result of the transaction request to the distributed message queue middleware, and the second generating module 904 enables an information consumer to obtain intermediate results of different transaction links in real time and then generate a final transaction result aiming at the transaction request according to each intermediate transaction result, so that an uncertain result of financial affairs is generated because a clear response aiming at the transaction request is not timely obtained due to network fluctuation, connection timeout and the like. And by sending each intermediate transaction result of the transaction request to the distributed message queue middleware, any type of information consumer can acquire the transaction result from the distributed message queue middleware according to respective business requirements, consume the actual posting condition of the underlying account, then check the accounts according to the consumed key transaction information, acquire the error condition in time, check and process in time on the aspect of accounts, and finally ensure the capability of providing transaction consistency for online services in the accounting processing process, thereby not only improving the timeliness of accounting processing and optimizing user experience, but also being applicable to independent reconciliation of distributed multi-application nodes.

By applying the device disclosed by the embodiment of the disclosure, all links in the whole transaction link, including an upstream link and a downstream link, can send transaction elements to the intermediate message queue in a quasi-real-time manner. Each application node can also take the transaction elements from the intermediate message queue in a quasi-real-time manner, and carry out quasi-real-time accounting checking according to the obtained transaction elements and the transaction log of the application node, so that the accounting consistency is ensured through a re-calling manner such as correcting, deducting and the like in the following, a complete closed-loop flow of data production, data acquisition, accounting checking and accounting adjustment is conveniently formed, and the accounting consistency is ensured.

Any number of modules, sub-modules, units, sub-units, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in any other reasonable manner of hardware or firmware by integrating or packaging a circuit, or in any one of or a suitable combination of software, hardware, and firmware implementations. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the disclosure may be at least partially implemented as a computer program module, which when executed may perform the corresponding functions.

For example, any plurality of the receiving module 901, the first generating module 902, the first sending module 903 and the second generating module 904 may be combined in one module/unit/sub-unit to be implemented, or any one of the modules/units/sub-units may be split into a plurality of modules/units/sub-units. Alternatively, at least part of the functionality of one or more of these modules/units/sub-units may be combined with at least part of the functionality of other modules/units/sub-units and implemented in one module/unit/sub-unit. According to an embodiment of the present disclosure, at least one of the receiving module 901, the first generating module 902, the first sending module 903 and the second generating module 904 may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or implemented by any one of three implementations of software, hardware and firmware, or an appropriate combination of any several of them. Alternatively, at least one of the receiving module 901, the first generating module 902, the first transmitting module 903 and the second generating module 904 may be at least partially implemented as a computer program module, which when executed may perform a corresponding function.

The electronic device shown in fig. 10 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 10, an electronic device 1000 according to an embodiment of the present disclosure includes a processor 1001 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)1002 or a program loaded from a storage section 1008 into a Random Access Memory (RAM) 1003. Processor 1001 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 1001 may also include onboard memory for caching purposes. The processor 1001 may include a single processing unit or multiple processing units for performing different actions of a method flow according to embodiments of the present disclosure.

In the RAM 1003, various programs and data necessary for the operation of the electronic apparatus 1000 are stored. The processor 1001, ROM 1002, and RAM 1003 are connected to each other by a bus 1004. The processor 1001 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 1002 and/or the RAM 1003. Note that the programs may also be stored in one or more memories other than the ROM 1002 and the RAM 1003. The processor 1001 may also perform various operations of the method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.

Electronic device 1000 may also include an input/output (I/O) interface 1005, the input/output (I/O) interface 1005 also being connected to bus 1004, according to an embodiment of the present disclosure. The system 1000 may also include one or more of the following components connected to the I/O interface 1005: an input section 1006 including a keyboard, a mouse, and the like; an output section 1007 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 1008 including a hard disk and the like; and a communication section 1009 including a network interface card such as a LAN card, a modem, or the like. The communication section 1009 performs communication processing via a network such as the internet. The driver 1010 is also connected to the I/O interface 1005 as necessary. A removable medium 1011 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 1010 as necessary, so that a computer program read out therefrom is mounted into the storage section 1008 as necessary.

According to embodiments of the present disclosure, method flows according to embodiments of the present disclosure may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication part 1009 and/or installed from the removable medium 1011. The computer program performs the above-described functions defined in the system of the embodiment of the present disclosure when executed by the processor 1001. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.

According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. Examples may include, but are not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

For example, according to embodiments of the present disclosure, a computer-readable storage medium may include the ROM 1002 and/or the RAM 1003 described above and/or one or more memories other than the ROM 1002 and the RAM 1003.

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method provided by the embodiments of the present disclosure, when the computer program product is run on an electronic device, the program code being adapted to cause the electronic device to carry out the method of generating a transaction result provided by the embodiments of the present disclosure.

The computer program, when executed by the processor 1001, performs the above-described functions defined in the system/apparatus of the embodiments of the present disclosure. The systems, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

In one embodiment, the computer program may be hosted on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted in the form of a signal on a network medium, distributed, downloaded and installed via the communication part 1009, and/or installed from the removable medium 1011. The computer program containing program code may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In accordance with embodiments of the present disclosure, program code for executing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, these computer programs may be implemented using high level procedural and/or object oriented programming languages, and/or assembly/machine languages. The programming language includes, but is not limited to, programming languages such as Java, C + +, python, the "C" language, or the like. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.

The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

Claims

1. A method of generating a transaction result, comprising:

receiving a transaction request from a channel end application;

generating, in response to the transaction requests, respective intermediate transaction results for the transaction requests;

and after the information consumer obtains each intermediate transaction result from the distributed message queue middleware, generating a final transaction result aiming at the transaction request according to each intermediate transaction result.

2. The method of claim 1, wherein:

the information consumer includes at least one of: the system comprises the channel end application, each execution node and a main control node, wherein each execution node is used for generating each intermediate transaction result, and the main control node is used for responding to the transaction request and calling each execution node to execute and generate each intermediate transaction result.

3. The method of claim 2, wherein:

the execution nodes comprise a debit application node and a credit application node, wherein the debit application node is used for executing deduction of a preset amount from a preset debit account and generating an intermediate transaction result indicating whether the deduction is successful, and the credit application node is used for executing posting of the preset amount to the preset credit account and generating an intermediate transaction result indicating whether the posting is successful or not.

4. The method of claim 3, further comprising, in the event that a final transaction result for the transaction request is determined to be a failure from the respective intermediate transaction results:

and calling the debit application node through the information consumer to execute the refund of the preset amount of money to the preset debit account.

5. The method of claim 1, further comprising:

6. The method of claim 5, wherein the generating, in response to the transaction request, a final transaction result for the transaction request comprises:

responding to the transaction request, calling each execution node through a main control node to generate each intermediate transaction result;

and after the main control node acquires each intermediate transaction result from each execution node, generating the final transaction result according to each intermediate transaction result.

7. An apparatus for generating transaction results, comprising:

the receiving module is used for receiving a transaction request from a channel end application;

a first generating module for generating respective intermediate transaction results for the transaction request in response to the transaction request;

the first sending module is used for sending each intermediate transaction result to the distributed message queue middleware;

and the second generation module is used for generating a final transaction result aiming at the transaction request according to each intermediate transaction result after the information consumer acquires each intermediate transaction result from the distributed message queue middleware.

8. An electronic device, comprising:

one or more processors;

a memory for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-6.

9. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to carry out the method of any one of claims 1 to 6.

10. A computer program product comprising computer executable instructions for implementing the method of any one of claims 1 to 6 when executed.