CN114170007A

CN114170007A - Orthogonal easy return message assembly method, program product, medium, and electronic device

Info

Publication number: CN114170007A
Application number: CN202111524733.1A
Authority: CN
Inventors: 丁陈飞; 唐成山
Original assignee: China Construction Bank Corp
Current assignee: China Construction Bank Corp
Priority date: 2021-12-14
Filing date: 2021-12-14
Publication date: 2022-03-11

Abstract

The application relates to the technical field of data processing, in particular to an orthogonal easy return message assembly method, a program product, a medium and electronic equipment, wherein the method is applied to a distributed transaction system and comprises the following steps: acquiring orthogonal transaction data of an orthogonal transaction, wherein the orthogonal transaction data comprises data fields and data values respectively corresponding to the data fields; acquiring mapping logic between each transaction parameter and each data field in the orthogonal cover corresponding to the orthogonal cover; determining the mapping relation between each transaction parameter and each data field in the forward transaction from the mapping logic, and taking the mapping relation as the mapping relation between each transaction parameter and each data field in the forward transaction; and mapping the data fields in the hedge orthogonal easy data according to the mapping relation between each transaction parameter and each data field in the hedge orthogonal easy transaction to generate a hedge orthogonal easy return message. Therefore, a large amount of manpower and material resources are saved without developing orthogonal business logic.

Description

Orthogonal easy return message assembly method, program product, medium, and electronic device

Technical Field

The present application relates to the field of data processing technologies, and in particular, to an assembly method, a program product, a medium, and an electronic device for an orthogonal easy return packet.

Background

The distributed banking system is divided into a plurality of hierarchies, for example, as shown in fig. 1, the distributed banking system 1000 may include a user layer 100, an integration layer 200, and a micro-service layer 300. The user layer 100 includes clients such as internet banking, mobile banking, and telephone banking.

The process of the distributed banking system 1000 for performing transactions includes: the user layer 100 may receive the transaction request and send the transaction request to the integration layer 200, and the integration layer 200 may send the transaction request to the microservice layer 300, where the microservice layer 300 may be configured to execute a transaction corresponding to the received transaction request. After the micro service layer 300 executes the transaction, the transaction data corresponding to the transaction is sent to the integration layer 200, the integration layer 200 deploys the business logic corresponding to the transaction request, and the integration layer 200 assembles the transaction data from the micro service layer 300 according to the business logic to obtain a transaction return message required by the client and returns the transaction return message to the client.

The transaction request received by the user layer 100 includes an orthogonal transaction request initiated by a user and an orthogonal transaction request automatically initiated by the distributed banking system 1000. Orthogonal reciprocity represents a forward business logic, a type of business developed to achieve a business effect. For example, orthogonal transactions may include user initiated transfer transactions, deposit transactions, and the like. The forward transaction is a transaction which is orthogonal and easy to have reverse logic, for example, when the distributed banking system 1000 detects that the transfer transaction fails, but the transfer party deducts money, the distributed banking system 1000 automatically performs the forward transaction of the transfer transaction, and sends a forward transaction request to the user layer, and the user layer receives the forward transaction request and performs the transaction process to remove the business effect of the money deduction of the transfer party.

The service logic in the integration layer 200 includes an orthogonal easy service logic for assembling transaction return messages for forward transactions and an orthogonal easy service logic for assembling transaction return messages for orthogonal easy transactions, and at present, both the orthogonal easy service logic and the orthogonal easy service logic corresponding to each transaction need to be designed and developed by developers respectively, which consumes a large amount of manpower and material resources.

Disclosure of Invention

Embodiments of the present application provide a method, a program product, a medium, and an electronic device for assembling a quick return message, which are described below in various aspects, and embodiments and advantageous effects of the following aspects may be mutually referred to.

In a first aspect, an embodiment of the present application provides an orthogonal easy return packet assembling method, which is applied to a distributed transaction system, and the method includes: acquiring orthogonal reciprocity data of an orthogonal transaction, wherein the orthogonal reciprocity data comprises at least one data field and data values respectively corresponding to the at least one data field; acquiring mapping logic between each transaction parameter and each data field in the orthogonal cover corresponding to the orthogonal cover; determining the mapping relation between each transaction parameter and each data field in the forward transaction from the mapping logic, and taking the mapping relation between each transaction parameter and each data field in the forward transaction as the mapping relation between each transaction parameter and each data field in the forward transaction; and mapping the data fields in the impulse orthogonal exchange data according to the mapping relation between each transaction parameter and each data field in the impulse orthogonal exchange to obtain the data value corresponding to each transaction parameter in the impulse orthogonal exchange so as to generate an impulse orthogonal exchange return message. Therefore, developers do not need to develop orthogonal business logic again, and can obtain the orthogonal business logic only by modifying the orthogonal business logic on the basis of the orthogonal business logic, so that the repeated development work can be effectively avoided, the efficiency of developing and testing the business logic of the transaction return message is improved, and meanwhile, the manpower and material resources are saved.

In an implementation of the first aspect, the distributed transaction system includes at least one service component, where each service component in the at least one service component is configured to execute a corresponding forward trade and an orthogonal easy and generate orthogonal easy data corresponding to the orthogonal easy and orthogonal easy; the orthogonal easy data comprises at least one data field and at least one data value corresponding to the data field respectively; the mapping logic includes: the judgment rule is used for judging the corresponding relation between each transaction parameter and each service component in the transaction, and the mapping relation between each transaction parameter and the data field in the orthogonal exchange data generated by the corresponding service component in the transaction. For the forward transaction and the forward transaction which correspond to each other, the transaction parameters in the forward transaction comprise the transaction parameters in the forward transaction, so that the mapping relation between each transaction parameter in the forward transaction and the data field in the orthogonal transaction data generated by the corresponding service component is modified into the mapping relation between the transaction parameters in the forward transaction and the data field, so that the forward transaction return message is generated in the forward transaction, and the development of the forward transaction business logic is not needed.

Under the condition that the mapping logic is complex, the process of acquiring the mapping relation between the transaction parameter in the transaction and the data field from the mapping logic (namely the process of analyzing the mapping logic) is time-consuming and energy-consuming, and in some embodiments of the application, the mapping relation between the transaction parameter in the transaction and the data field can be set in a user-defined mode. The more flexible orthogonal easy-return message assembling function is provided for developers; the developer sets the mapping relation by self-definition, so that the problem of time and energy consumption caused by analyzing mapping logic is avoided.

In an implementation of the first aspect, mapping data fields in the orthogonal cover data according to a mapping relationship between each transaction parameter and each data field in the orthogonal cover to obtain a data value corresponding to each transaction parameter in the orthogonal cover, includes: determining data fields in the forward transaction data corresponding to the transaction parameters in the forward transaction according to the mapping relation between the transaction parameters and the data fields in the forward transaction; and taking the data value corresponding to the data field in the transaction data as the data value of each transaction parameter in the transaction.

In an implementation of the first aspect, the method further includes: setting a judgment identifier for each transaction parameter in the positive transaction, wherein the judgment identifier is used for identifying a service component corresponding to each transaction parameter; and/or setting a judgment identifier for each transaction parameter in the transaction, wherein the judgment identifier is used for identifying the service component corresponding to each transaction parameter.

In an implementation of the first aspect, the method further includes: determining service components corresponding to all transaction parameters in the forward trade based on the judgment identification; and mapping the data value corresponding to the data field in the orthogonal transaction data generated by the corresponding service component into the data value of each transaction parameter in the forward transaction. Therefore, under the condition that a plurality of service components are accessed in forward conflict transaction, the corresponding relation between forward conflict data returned by each service component and the corresponding mapping relation of each transaction parameter and/or data field can be confirmed through the judgment identification, and the data value corresponding to the data field in the forward conflict data returned by the service component is mapped to the transaction parameter in the corresponding mapping relation, so as to generate a forward conflict return message. The problem that under the condition of accessing a plurality of service components, due to the fact that no forward business logic exists, mapping relations cannot be corresponding to transaction parameters returned by the service components, and forward and easy-to-return messages cannot be generated is solved.

In an implementation of the first aspect, the method further includes: setting a first assembly identifier for a record of an orthogonal easy access service assembly; setting a second assembly identifier corresponding to the first assembly identifier for each transaction parameter and/or data field in the transaction; and acquiring the corresponding relation between the record of accessing the service component and each transaction parameter and/or data field based on the corresponding relation between the first assembly identifier and the second assembly identifier. It can be understood that, in the case that the same service component is accessed multiple times in the transaction, the correspondence between the orthogonal easy data returned by the service component recorded in each record and the mapping relationship corresponding to each transaction parameter and/or data field is determined through the correspondence between the first assembly identifier and the second assembly identifier, and the orthogonal easy return message is generated based on the correspondence. The problem that under the condition that the same service component is accessed for multiple times, due to the fact that the forward business logic is not available, mapping relations cannot be corresponding to transaction parameters returned by the service components, and the forward and backward messages cannot be generated is solved.

In a second aspect, an embodiment of the present application provides an apparatus for assembling an orthogonal easy return packet, where the apparatus includes: the device comprises a first acquisition module, a second acquisition module and a processing module, wherein the first acquisition module is used for acquiring orthogonal easy data of the orthogonal easy, and the orthogonal easy data comprises at least one data field and data values corresponding to the at least one data field respectively; the second acquisition module is used for acquiring mapping logics between each transaction parameter and each data field in the orthogonal exchange corresponding to the orthogonal exchange; the determining module is used for determining the mapping relation between each transaction parameter and each data field in the forward transaction from the mapping logic, and taking the mapping relation between each transaction parameter and each data field in the forward transaction as the mapping relation between each transaction parameter and each data field in the forward transaction; and the mapping module is used for mapping the data fields in the orthogonal transaction data according to the mapping relation between each transaction parameter and each data field in the orthogonal transaction so as to obtain the data value corresponding to each transaction parameter in the orthogonal transaction and generate an orthogonal transaction return message.

In a third aspect, an embodiment of the present application provides a distributed transaction system, where the distributed transaction system includes a user layer, an integration layer, and a micro-service layer, and includes: the microservice layer executes a request of forward trade of the user layer and generates forward trade data corresponding to forward trade; the integration layer acquires impulse orthogonal easy data of impulse orthogonal transaction, wherein the impulse orthogonal easy data comprises at least one data field and data values corresponding to the at least one data field; the integration layer acquires mapping logic between each transaction parameter in the orthogonal cover corresponding to the orthogonal cover and each data field; the integration layer determines the mapping relation between each transaction parameter and each data field in the forward transaction from the mapping logic, and takes the mapping relation between each transaction parameter and each data field in the forward transaction as the mapping relation between each transaction parameter and each data field in the forward transaction; the integration layer maps the data fields in the impulse orthogonal exchange data according to the mapping relation between each transaction parameter and each data field in the impulse orthogonal exchange to obtain the data value corresponding to each transaction parameter in the impulse orthogonal exchange so as to generate an impulse orthogonal exchange return message; and the integration layer sends the orthogonal easy return message to the user layer.

In a fourth aspect, embodiments of the present application provide a readable medium having stored thereon instructions that, when executed on an electronic device, cause the electronic device to perform the method for assembling a quadrature-reciprocal message as described above.

In a fifth aspect, an embodiment of the present application provides an electronic device, including: a memory for storing instructions for execution by one or more processors of the electronic device, and a processor, which is one of the processors of the electronic device, for performing the orthogonal reciprocal message assembly method as described above.

Drawings

Fig. 1 is a scene diagram of an assembly method for an orthogonal easy return packet according to some embodiments of the present application;

fig. 2 is a schematic diagram of a collision orthogonal easy return message assembly according to some embodiments of the present application;

fig. 3 is a scene diagram of another method for assembling an orthogonal easy return packet according to some embodiments of the present application;

FIG. 4 is a block diagram of a business logic 220 according to some embodiments of the present application;

fig. 5 is a flowchart of an assembly method for an orthogonal easy return packet provided in the present application;

FIG. 6 is a flow chart of a method for punching orthogonal vectors according to the present disclosure;

FIG. 7A is a schematic illustration of a transaction flow meter 251 in a database 240 according to some embodiments of the present application;

FIG. 7B is a block diagram of another business logic 220 according to some embodiments of the present application;

fig. 8 is another method for assembling an orthogonal easy return packet according to the present application;

FIG. 9 is a block diagram of an electronic device according to some embodiments of the present application.

Detailed Description

Illustrative embodiments of the present application include, but are not limited to, a method, apparatus, readable medium, and electronic device of a transaction message assembly method.

In order to better understand the content of the present solution, the following explanation is made on the related nouns.

Trading: the functions developed for performing a particular function include positive transactions and negative transactions.

Positive transaction: orthogonal reciprocity represents a forward business logic, a type of business developed to achieve a business effect. For example, the transfer transaction is a positive transaction.

The punching orthogonal is easy: the forward trade is a kind of trade which is orthogonal and easy to have reverse logic, and the reverse trade logic is developed for removing the business effect of the forward trade. For example, if the transfer transaction fails, but the transfer party has deducted money, a correction transaction for the transfer transaction is performed to remove the business effect of the deduction of money from the transfer party.

Temporary variables: refers to variables that are not declared at the beginning of a program, whose type is to be declared when it is to be used. Variables defined by functions, loop statements and conditional statements are common. In a program for determining access to a service component, such as orthogonal business logic (including the mapping logic described above), temporary variables are used to temporarily store the determination results to transition multiple determination logics.

For a clearer understanding of the present disclosure, the following describes a process of executing a transaction in the distributed banking system 1000. Specifically, taking a transfer transaction as an example, it can be understood that the transfer transaction is a positive transaction initiated by a user, and after the orthogonal transaction is executed, the user receives a transaction return message corresponding to the orthogonal transaction; when the distributed banking system 1000 detects that the transfer fails, for example, the opposite side account fails and cannot receive the transfer of funds, a forward transaction of the transfer transaction is automatically initiated, so that the funds transferred by the user return to the user account, and after the forward transaction is easily executed, the user can receive a transaction return message corresponding to the forward transaction.

The orthogonal transaction flow of the transfer transaction includes:the user layer 100 receives a transfer transaction request of the user, such as a transaction request (for transferring the account a to the account B), and sends the transfer transaction request to the integration layer 200, and the integration layer 200 sends the transfer transaction request to the service component of the microservice layer 300. The service component of the micro service layer 300 executes the transaction corresponding to the transfer transaction request to obtain transfer transaction data, and sends the transfer transaction data to the integration layer 200, and the integration layer 200 assembles the transfer transaction data according to the transaction business logic to obtain the transaction dataThe transaction return message required by the user is returned to the user layer 100. If the transaction return message required by the user needs to contain values of parameters such as the balance of the transfer-out account and the balance of the transfer-in account, the integration layer 200 acquires transfer data fields (such as the balance) corresponding to the parameters (such as the balance of the transfer-out account) from the transfer transaction data based on orthogonal easy logic, and assembles the values corresponding to the transfer data fields into values corresponding to the parameters (in the transaction return message), so that the transaction return message required by the user is obtained.

The orthogonal transaction flow of the transfer transaction comprises the following steps:when the distributed banking system 1000 detects that the transfer transaction fails, but the transfer party deducts money, the distributed banking system 1000 automatically performs a transaction for correcting the transfer transaction, and sends a transaction request to the user layer.

The user layer 100 receives the forward-ledger transaction request of the distributed banking system 1000, and sends the forward-ledger transaction request to the integration layer 200, and the integration layer 200 sends the forward-ledger transaction request to the service component of the micro-service layer 300. The service component of the microservice layer 300 executes the transaction corresponding to the transfer transaction request to obtain transfer transaction data, and sends the transfer transaction data to the integration layer 200, and the integration layer 200 assembles the transfer transaction data according to the transaction logic to obtain a transaction return message required by the user, and returns the transaction return message to the user layer 100.

As described above, in the prior art, both the orthogonal easy service logic and the orthogonal easy service logic corresponding to each transaction need to be designed and developed by developers, which consumes a lot of manpower and material resources.

In order to solve the above problem, an orthogonal easy return message assembly method provided in an embodiment of the present application may be applied to a distributed system, where the system may analyze and adjust an orthogonal easy service logic (including the mapping logic) corresponding to a transaction request initiated by a user to obtain the orthogonal easy service logic, and then assemble orthogonal easy data returned by a micro service layer according to the obtained orthogonal easy service logic. Therefore, developers do not need to develop orthogonal business logic again, and can obtain the orthogonal business logic only by modifying the orthogonal business logic on the basis of the orthogonal business logic, so that the repeated development work can be effectively avoided, the efficiency of developing and testing the business logic of the transaction return message is improved, and meanwhile, the manpower and material resources are saved.

The analyzing and adjusting of the transaction business logic specifically comprises the following steps: determining the mapping relation between each transaction parameter and each data field in forward transaction from orthogonal business logic, and taking the mapping relation as the mapping relation between each transaction parameter and each data field in forward transaction; and taking the mapping relation between each transaction parameter and each data field in the transaction as orthogonal business logic. And mapping the data field in the forward transaction data based on the forward transaction logic to generate a forward transaction return message. The parsing and adjustment process is described below by way of example.

First, an exemplary description of the transaction business logic (i.e., a description of the mapping logic) is presented. Specifically, the orthogonal business logic includes mapping logic between each transaction parameter and each data field in the transaction. The mapping logic comprises a judgment rule for judging the corresponding relation between each transaction parameter and each service component in the transaction; and the mapping relation between each transaction parameter in the positive transaction and the data field in the orthogonal easy data generated by the corresponding service component. The judgment process for mapping logic is as follows:

the mapping logic includes the judgment rule and the mapping relationship, for example, the judgment rule includes a first judgment logic and a second judgment logic, and each judgment logic includes a temporary variable; the mapping relationship may be an indirect mapping relationship between the orthogonal transaction parameter a and the data field D in the orthogonal transaction data generated by the corresponding service component, such as "a ═ B, B ═ C, and C ═ D". Where B and C are temporary variables involved in the mapping of transaction parameter a to data field D. Specifically, the temporary variable B maps B to a (a ═ B) when the first determination logic is performed, and if the determination result of the first determination logic is XX1, B ═ 1, and if the determination result is XX2, B ═ 2; in the case of the second judgment logic, the temporary variable C maps C to B (B equals C), and if the judgment result of the second judgment logic is XX3, C equals 1. And if B is 1 and C is 1, the service component needing to be accessed is the service component M, and the data value corresponding to the data field D in the transaction data returned by the service component M is used for assembling the transaction parameter A so as to generate a transaction return message. Meanwhile, the indirect mapping relation of the transaction parameter A and the data field D in the mapping logic is that the transaction parameter A and the data field D have the mapping relation through the indirect mapping relation of B, C and D. Based on the mapping logic, the service components required to be accessed based on the transaction parameters in the transaction can be determined, and meanwhile, the mapping relation between the transaction parameters in the orthogonal transaction and the data fields is determined.

No temporary variables are required in the forward trade. The integration layer 200 directly initiates access to the service components accessed in the orthogonal easy (corresponding to the orthogonal easy), without judging the service components to be accessed, and without the above judgment rules, so that the orthogonal easy business logic does not need temporary variables.

Secondly, the analyzed indirect mapping relation is converted into orthogonal business logic, namely the mapping relation between the transaction parameters and the data fields in the transaction. Wherein, the mapping relation is the relation without temporary variables between each transaction parameter and data field in the transaction. For example, the indirect mapping relationship is "a ═ B, B ═ C, and C ═ D" is adjusted to the mapping relationship "a ═ D".

And finally, assembling the transaction return message (namely the orthogonal transaction return message) for the orthogonal transaction. And assembling the orthogonal easy data returned to the integration layer 200 by the service component based on the mapping relation in the orthogonal easy service logic so as to obtain an orthogonal easy return message.

The following illustrates an assembly process of hedged orthogonal easy return messages. As shown in fig. 2, if the quadrature reciprocal data obtained by the integration layer 200 includes "balance D: 1000 yuan (that is, the data field D means a balance), that is, the numerical value corresponding to the field "balance D" is "1000 yuan", the integration layer 200 assembles the numerical value "1000 yuan" into the value of the transaction parameter "roll-out account balance a" in the forward transaction easy return message based on "roll-out account balance a ═ balance D" (that is, the transaction parameter a means a roll-out account balance), and the obtained forward transaction easy return message includes "roll-out account balance a: 1000 yuan. The transaction return message includes various information, such as account and transaction amount.

It can be understood that the transaction parameters and the data fields are only examples, in some embodiments, the transaction parameters in the forward transaction backward return text may further include "balance of transferred account", "refund amount", and the like, the system may obtain an indirect mapping relationship including the transaction parameters from the analyzed orthogonal transaction logic based on the transaction parameters, then determine the mapping relationship of the transaction parameters, and assemble the values of each transaction parameter and each corresponding transaction parameter in the forward transaction backward return text based on the forward transaction data by using the corresponding mapping relationship, so that the obtained forward transaction backward message includes each transaction parameter and the value corresponding to each transaction parameter.

Before describing the method for assembling the backward-facing easy-return message according to the embodiment of the present application, a distributed banking system for executing the method is described first. Fig. 3 is a schematic diagram of a distributed banking system, which will be described in detail below.

As shown in fig. 3, the distributed banking system 1000 includes a user layer 100 integration layer and a service layer, where the user layer 100 includes a plurality of clients, for example, including a client a110, a client B120, a client C130, and the like, and each client may be an internet bank, a mobile phone bank, a telephone bank, and the like. The integration layer 200 includes a message parsing 210, business logic 220, a call center 230, and a database 240. The microservice layer 300 includes service components such as a service component a310, a service component B320, and a service component C330, each for performing transactions related to transfers, deposits, withdrawals, loans, and the like.

The user layer 100 shown in fig. 3 initiates a transaction to the integration layer 200, the integration layer 200 establishes access to each service component in the microservice layer 300 through the call center 230, and the database 240 is used for storing transaction-related data, such as a deposit and withdrawal transaction record formed by the transaction. The message parsing 210 is configured to parse a transaction request (i.e., a transaction request message) sent by the receiving user layer 100 to obtain information related to the transaction request, such as information of a roll-out party, information of a roll-in party, a transfer amount, a transaction number, and the like of a transaction.

Business logic 220 includes forward transaction business logic 221 and forward transaction business logic 222. Orthogonal transaction logic 221 the user determines the service components accessed and assembles the transaction return message being transacted. The forward transaction service logic 221 includes an orthogonal easy assignment rule 2211 for assembling a transaction return message of a forward transaction, where the orthogonal easy assignment rule 2211 includes an indirect mapping relationship between each transaction parameter and a data field in the forward transaction, for example, the orthogonal easy assignment rule 2211 includes the above-mentioned "rolling-out account balance a is B, B is C, and C is balance D". The fast forward business logic 222 contains fast forward assignment rules 2221 for assembling fast forward return messages. The conflict orthogonal easy assignment rule 2221 includes a mapping relationship between each transaction parameter and a data field in a conflict positive transaction, for example, the conflict orthogonal easy assignment rule 2221 includes "balance a of roll-out account is equal to balance D".

According to the foregoing method for assembling an orthogonal easy return packet, fig. 5 shows a flowchart of the method for assembling an orthogonal easy return packet, and the following describes in detail the steps of the method for assembling an orthogonal easy return packet with reference to fig. 4.

S101: and acquiring orthogonal reciprocity data of the transaction, wherein the orthogonal reciprocity data comprises at least one data field and at least one data value corresponding to the data field respectively.

The following are exemplary: the integration layer 200 receives orthogonal cover data resulting from the service component performing orthogonal cover traffic. It can be understood that, after the orthogonal volatile is failed, the user side may initiate an orthogonal volatile request, the user layer 100 receives the orthogonal volatile request of the user and sends the orthogonal volatile request to the integration layer 200, the integration layer 200 sends the orthogonal volatile request to the orthogonal accessible service component, and the service component sends orthogonal volatile data obtained after executing a service requested by the orthogonal volatile request to the integration layer 200. The specific forward trade process is as described in fig. 6 below, and will not be described herein.

Specifically, the integration layer 200 needs to obtain data required by the client from the forward transaction data, and assemble the data into preset values of transaction parameters in the forward transaction to obtain a forward transaction return message, which includes the following specific steps.

S102: and acquiring mapping logic between each transaction parameter and each data field in the orthogonal cover corresponding to the orthogonal cover.

The following are exemplary: the integration layer 200 shown in fig. 1 obtains mapping logic between each transaction parameter and each data field in the orthogonal cover corresponding to the orthogonal cover from the orthogonal cover service logic 221; the indirect mapping relationship between each transaction parameter and the data field in the preset forward trade is determined from the orthogonal easy assignment rule 2211 in the orthogonal easy service logic 221.

As described above, each transaction parameter in all positive transactions also belongs to each transaction parameter in the positive transactions, that is, the orthogonal easy assignment rule 2211 includes an indirect mapping relationship between each transaction parameter in all positive transactions and the data field. Illustratively, as shown in fig. 4, the indirect mapping relationship in the orthogonal easy assignment rule 2211 includes "rule 1: the roll-out account balance a ═ B, B ═ C, C ═ data field D "," rule 2: the load account balance E. · data field F "and" rule 3: the transfer-out amount G is the data field H ". The indirect mapping relationship in the orthogonal easy assignment rule 2221 includes "rule 11: roll-out account balance a ═ data field D "and" rule 22: the transferred account balance E is the data field F ". Wherein, the 'rule 1' comprises the indirect mapping relation of each transaction parameter 'transferring account balance A' and 'data field D' in the transaction; the 'rule 2' contains an indirect mapping relation between each transaction parameter 'transferred account balance E' and 'data field F' in the transaction.

In some embodiments of the present application, the preset transaction parameters in the forward transaction include parameters such as an account balance transfer, an account number transfer, an orthogonal balance, and time.

S103: and determining the mapping relation between each transaction parameter and each data field in the forward transaction from the mapping logic, and taking the mapping relation between each transaction parameter and each data field in the forward transaction as the mapping relation between each transaction parameter and each data field in the forward transaction.

For example, the integration layer 200 determines a mapping relationship between each transaction parameter and each data field in the forward transaction from the mapping logic, for example, the mapping relationship is a mapping relationship between each transaction parameter and each data field in the orthogonal transaction determined from the indirect mapping relationship, and uses the mapping relationship between each transaction parameter and each data field in the forward transaction as the mapping relationship between each transaction parameter and each data field in the forward transaction.

For example, each transaction parameter in the pre-set correction transaction is "balance a of the transferred-out account" and "balance E of the transferred-in account", and "rule 1" and "rule 2" shown in fig. 2 are respectively related indirect mapping rules of "balance a of the transferred-out account" and "balance E of the transferred-in account", and a mapping relationship exists between "balance a of the transferred-out account" and "field D" according to "rule 1", so that "rule 11" is obtained, and similarly "rule 22" is obtained based on "rule 2".

S104: and mapping the data fields in the impulse orthogonal exchange data according to the mapping relation between each transaction parameter and each data field in the impulse orthogonal exchange to obtain the data value corresponding to each transaction parameter in the impulse orthogonal exchange so as to generate an impulse orthogonal exchange return message.

The following are exemplary: the integration layer 200 maps the data fields in the forward transaction data based on the mapping relationship between the transaction parameters and the data fields in the forward transaction data. For example, in the orthogonal data returned by the service component a310 to the integration layer 200, if the data corresponding to the data field D is "s", then "s" is assigned data. The assembled punching orthogonal easy-return text comprises the following steps: s ", the integration layer 200 will contain" roll out account balance: and the collision angle of s' is easy to return the message and send to the client.

By the method for assembling the orthogonal easy return message, repeated development and test work of the opposite transaction business judgment logic is avoided, the development efficiency of the business logic 220 is improved, and manpower and material resources are saved.

In some embodiments, the orthogonal reciprocity data in step S101 may be obtained by the orthogonal reciprocity method shown in fig. 6. The steps of the orthogonal method will be described in detail below.

S201: the integration layer 200 receives a fast forwarding easy request message sent by a client of the user layer 100.

S202: the integration layer 200 calls the message parsing layer 210 to parse the orthogonal transaction request message to obtain the transaction number of the orthogonal transaction corresponding to the orthogonal transaction. Wherein the transaction number is used to identify an orthogonal transaction to which the orthogonal transaction corresponds.

S203: the integration layer 200 obtains the component identifier corresponding to the transaction number from the database 240 based on the transaction number.

For example, after executing the positive transaction, the flow meter in the database 240 stores the relevant information of the positive transaction, as shown in fig. 7A, the transaction flow meter 251 includes the transaction number of the positive transaction as "1001"; the components corresponding to "1001" are identified as "310" and "320" (corresponding to service component A310 and service component A320), and the components identified as "310" and "320" correspond to serial numbers "222" and "333", respectively. The serial number refers to identification information of orthogonal easy data obtained by executing relevant services in the orthogonal easy process by a service component corresponding to the serial number (i.e., a service component corresponding to a component identifier) in the transaction flow meter 251.

S204: the integration layer 200 calls the call center 230 to send a conflict transaction request to the service component corresponding to the component identifier in the microservice layer 200.

For example, call center 230 sends a conflict facilitation request regarding serial number "222" to service component a 310. I.e., access service component a 310.

S205: the service component in the microserver layer 200 executes the service requested by the conflict orthogonal easy service request, obtains conflict orthogonal easy data, and sends the conflict orthogonal easy data to the integration layer 200.

It is understood that, in the case that one orthogonal transaction request includes a plurality of transaction tasks, each transaction task requiring access to one service component, the orthogonal transaction corresponding to the orthogonal transaction also requires multiple accesses to the service component, and the integration layer 200 obtains orthogonal transaction data of the plurality of service components.

According to the embodiment provided by the present application, the service determination logic 220 does not include a mapping relationship between the mapping relationship and the mapping relationship between the mapping relationship and the mapping relationship between the mapping relationship and the mapping relationship between the mapping relationship and the mapping relationship between the mapping relationship and the mapping relationship between the mapping relationship and the mapping relationship between the mapping relationship and. As shown in fig. 7A, in the transaction flow meter 251, one transaction number "1001" corresponds to records of two times of accessing service components, that is, "310" and "320", and the integration layer 200 cannot determine the correspondence between "rule 11" in the conflict orthogonal easy assignment rule 2221 and conflict orthogonal easy data obtained by accessing the service components, that is, it is determined whether each transaction parameter "transfer account balance a" in the conflict orthogonal easy is assembled by using the conflict orthogonal easy data obtained by the service component a310 or the conflict orthogonal easy data obtained by the service component B320.

Based on this, in the transaction process, the application adds an assignment identifier to the component identifier in the transaction flow water meter 251 shown in fig. 7A (i.e., the first component identifier and the second component identifier are consistent as the assignment identifier above), so as to obtain the transaction flow water meter 251; adding an assignment identifier corresponding to the assignment identifier of the component identifier to the mapping relationship in the positive transaction assignment rule 2211 to obtain an orthogonal easy assignment rule 2211a shown in fig. 7B. In this way, the integration layer 200 can determine, based on the assignment identifier, a mapping relationship between the orthogonal easy data returned by each service component and the orthogonal easy assignment rule 2221 a.

Illustratively, in the orthogonal easy process, the integration layer 200 adds assignment identifiers "-1" and "-2" to the recorded component identifiers "310" and "320", respectively, in the transaction flow meter 251 shown in FIG. 7A, resulting in a transaction flow meter 251a containing "310-1" and "320-2", and adds assignment identifiers "-1" and "-2" to the "data field D" of the "rule 1" and the "data field F" of the "rule 2", respectively, in the orthogonal easy assignment rule 2211 shown in FIG. 7B, resulting in an orthogonal easy assignment rule 2211a containing the "data field D-1" and the "data field F-2". In the foregoing method for assembling a forward backward compatible message (fig. 3), after the forward backward compatible rule 2221a shown in fig. 7B is obtained based on the mapping relationship of the forward transaction assignment rule 2211a (S103), the mapping relationship in the forward compatible rule 2221a includes the assignment identifiers "-1" and "-2", when the forward compatible message is assembled by the integration layer 200, the assignment identifiers are used to determine the correspondence between the component identifier in the transaction flow water meter 251a and the mapping relationship in the forward compatible rule 2221a, and based on the correspondence, the forward compatible data returned by the service component corresponding to the component identifier is assembled into each transaction parameter in the forward transaction in the corresponding mapping relationship.

As described above, the integration layer 200 may determine, based on the assignment identifier, a mapping relationship between the backward orthogonal easy data returned by each service component and the backward orthogonal easy assignment rule 2221, so that the integration layer 200 may perform backward orthogonal easy return packet assembly based on the assignment identifier when the service components are accessed for multiple times. In some embodiments, a method for performing orthogonal easy return packet assembly by the integration layer 200 based on the assigned identifier is shown in fig. 8, and is described in detail below with reference to fig. 7A, 7B, and 8.

S301: the integration layer 200 receives orthogonal data resulting from multiple accesses to the service components.

For example, based on the component identifications "310" and "320" of the service component being accessed by the exchange in the transaction flow meter 251a shown in fig. 7A, the integration layer 200 initiates access to the service component a310 and the service component B320, respectively, and obtains a first orthogonal reciprocity data obtained by the service component a310 and a second orthogonal reciprocity data obtained by the service component B320.

S302: the integration layer 200 determines the indirect mapping relationship between each transaction parameter and each data field in the preset forward trade from the orthogonal easy assignment rule 2211 a. This step is the same as step S102, and is not described herein again.

S303: the integration layer 200 determines a mapping relation between each transaction parameter in the orthogonal reciprocity and the data field with the assignment identifier from the indirect mapping relation, and uses the mapping relation as an orthogonal reciprocity assignment rule 2221 a.

For example, as shown in FIG. 7B, "rule 1" and "rule 2" in orthogonal easy assignment rule 2211a contain "data field D-1" and "data field F-2" with assignment identification, respectively, "rule 11" and "rule 22" derived based on "rule 1" and "rule 2", and contain "data field D-1" and "data field F-2", respectively.

S304: the integration layer 200 determines the correspondence between the component identifier with assigned identifier and the data field with assigned identifier (in the orthogonal easy assignment rule 2221 a) in the database 240, so as to determine the correspondence between the orthogonal easy data and the data field returned by the service component identified by each component identifier.

For example, as shown in FIG. 7A, the component identifications "310-1" and "320-2" having assigned identifications in the transaction flow meter 251a, and the "data field D-1" having assigned identifications in the data field of "rule 11" and the "data field F-2" in "rule 22" in the orthogonal easy assignment rule 2221a shown in FIG. 7B. Thus, based on assignment identifications "-1" and "-2", data field D "of" rule 11 "is associated with the first orthogonal volatile data resulting from accessing service component a310 (the service component corresponding to component identification" 310 "); the "data field F" of the "rule 22" corresponds to the second orthogonal volatile data resulting from accessing the service component B320 (the service component corresponding to the component identification "320").

S305: the integration layer 200 obtains assigned value data (i.e., data value) corresponding to each data field from the orthogonal transaction data corresponding to each data field, and assembles the assigned value data and each transaction parameter in the orthogonal transaction corresponding to each data field as an orthogonal transaction return message.

For example, the assigned data corresponding to the "data field D" of the first orthogonal reciprocal data is "s"; the assigned data corresponding to the "data field F" of the second orthogonal data is "m". The forward return text contains "transfer account balance: s; transferring into account balance: m' are adopted.

Through the above embodiment, under the condition that the service determination logic 220 does not include the forward transaction facilitation determination logic, by storing the correspondence between the component identifier in the transaction flow meter 251 and the mapping relationship in the orthogonal facilitation assignment rule 2211 in advance (setting the assignment identifier as described above) during forward transaction, and during forward transaction, based on the correspondence between the component identifier and the assignment rule stored in advance, the forward transaction facilitation data returned by the service component corresponding to each component identifier is assembled into each transaction parameter in the forward transaction in the corresponding mapping relationship. Therefore, the problem that when the service judgment logic 220 does not include the conflict orthogonal easy service judgment logic, the integration layer 200 cannot judge the corresponding relationship between the conflict orthogonal easy data returned by each service component and the mapping relationship in the conflict orthogonal easy assignment rule 2221, so that a conflict orthogonal easy return message cannot be assembled is solved.

In some embodiments of the present application, a judgment identifier is set for each transaction parameter in a positive transaction, and the judgment identifier is used to identify a service component corresponding to each transaction parameter; and/or setting a judgment identifier for each transaction parameter in the transaction, wherein the judgment identifier is used for identifying the service component corresponding to each transaction parameter. Determining service components corresponding to all transaction parameters in the forward trade based on the judgment identification; and mapping the data value corresponding to the data field in the orthogonal transaction data generated by the corresponding service component into the data value of each transaction parameter in the forward transaction. Therefore, the problem that the integration layer 200 cannot judge the corresponding relationship between the mapping relationship between the orthogonal-conflict easy data returned by each service component and the orthogonal-conflict easy assignment rule 2221, so that the orthogonal-conflict easy return message cannot be assembled can be solved.

The present application also provides a readable medium having stored thereon instructions that, when executed on an electronic device, cause the electronic device to perform the method for assembling a backward-facing easy-return message as described above.

The present application also provides an electronic device comprising a memory for storing instructions for execution by one or more processors of the electronic device, and a processor, which is one of the processors of the electronic device, for performing the method for assembling a quadrature-ready return message as described above.

FIG. 9 is a block diagram illustrating an electronic device according to one embodiment of the present application. FIG. 9 schematically illustrates an example electronic device 90 in accordance with various embodiments. In one embodiment, electronic device 90 may include one or more processors 901, system control logic 902 coupled to at least one of processors 901, system memory 903 coupled to system control logic 902, non-volatile memory (NVM)904 coupled to system control logic 902, and network interface 906 coupled to system control logic 902.

In some embodiments, processor 901 may include one or more single-core or multi-core processors. In some embodiments, the processor 901 may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, baseband processors, etc.). In embodiments where the electronic device 90 employs an eNB (enhanced Node B) or RAN (Radio Access Network) controller, the processor 901 may be configured to perform various consistent embodiments, e.g., as one or more of the embodiments shown in fig. 4-8. For example, process 901 may be used to perform the above-described orthogonal easy return message assembly method.

In some embodiments, system control logic 902 may include any suitable interface controllers to provide any suitable interface to at least one of processors 901 and/or to any suitable device or component in communication with system control logic 902.

In some embodiments, system control logic 902 may include one or more memory controllers to provide an interface to system memory 903. System memory 903 may be used to load and store data and/or instructions. The memory 903 of the system 90 may comprise any suitable volatile memory in some embodiments, such as suitable Dynamic Random Access Memory (DRAM).

NVM/memory 904 may include one or more tangible, non-transitory computer-readable media for storing data and/or instructions. In some embodiments, the NVM/memory 904 may include any suitable non-volatile memory, such as flash memory, and/or any suitable non-volatile storage device, such as at least one of a HDD (Hard Disk Drive), CD (Compact Disc) Drive, DVD (Digital Versatile Disc) Drive.

The NVM/memory 904 may comprise a portion of the storage resource on the device on which the electronic device 90 is installed, or it may be accessible by, but not necessarily a part of, the device. The NVM/storage 904 may be accessed over a network via the network interface 906, for example.

In particular, system memory 903 and NVM/storage 904 may each include: a temporary copy and a permanent copy of the instructions 905. The instructions 905 may include: instructions that, when executed by at least one of the processors 901, cause the electronic device 90 to implement the method as shown in fig. 3. In some embodiments, the instructions 905, hardware, firmware, and/or software components thereof may additionally/alternatively be disposed in the system control logic 902, the network interface 906, and/or the processor 901.

Network interface 906 may include a transceiver to provide a radio interface for electronic device 90 to communicate with any other suitable device (e.g., front end module, antenna, etc.) over one or more networks. In some embodiments, the network interface 906 may be integrated with other components of the electronic device 90. For example, the network interface 906 may be integrated with at least one of the processor 901, the system memory 903, the NVM/storage 904, and a firmware device (not shown) having instructions that, when executed by at least one of the processors 901, the electronic device 90 implements the methods shown in the above-described method embodiments.

Network interface 906 may further include any suitable hardware and/or firmware to provide a multiple-input multiple-output radio interface. For example, network interface 906 may be a network adapter, a wireless network adapter, a telephone modem, and/or a wireless modem.

The electronic device 90 may further include: input/output (I/O) device 907. I/O device 907 may include a user interface to enable a user to interact with electronic device 90; the design of the peripheral component interface enables peripheral components to also interact with the electronic device 90.

In some embodiments, the user interface may include, but is not limited to, a display (e.g., a liquid crystal display, a touch screen display, etc.), a speaker, a microphone, one or more cameras (e.g., still image cameras and/or video cameras), a flashlight (e.g., a light emitting diode flash), and a keyboard.

In some embodiments, the peripheral component interfaces may include, but are not limited to, a non-volatile memory port, an audio jack, and a power interface.

In some embodiments, the sensors may include, but are not limited to, a gyroscope sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of the network interface 606 or interact with the network interface 606 to communicate with components of a positioning network, such as Global Positioning System (GPS) satellites.

It is to be understood that the illustrated structure of the embodiment of the present invention does not specifically limit the electronic device 90. In other embodiments of the present application, the electronic device 90 may include more or fewer components than shown, or some components may be combined, some components may be split, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Program code may be applied to input instructions to perform the functions described herein and generate output information. The output information may be applied to one or more output devices in a known manner. For purposes of this application, a processing system includes any system having a processor such as, for example, a Digital Signal Processor (DSP), a microcontroller, an Application Specific Integrated Circuit (ASIC), or a microprocessor.

The program code may be implemented in a high level procedural or object oriented programming language to communicate with a processing system. The program code can also be implemented in assembly or machine language, if desired. Indeed, the mechanisms described herein are not limited in scope to any particular programming language. In any case, the language may be a compiled or interpreted language.

One or more aspects of at least one embodiment may be implemented by representative instructions stored on a computer-readable storage medium, which represent various logic in a processor, which when read by a machine causes the machine to fabricate logic to perform the techniques described herein. These representations, known as "one core less," may be stored on a tangible computer-readable storage medium and provided to a plurality of customers or production facilities to load into the manufacturing machines that actually make the logic or processor.

In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the application may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the application, various features of the application are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the application and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: this application is intended to cover such departures from the present disclosure as come within known or customary practice in the art to which this invention pertains. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this application.

Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the application and form different embodiments. For example, in the claims, any of the claimed embodiments may be used in any combination.

Claims

1. A method for assembling orthogonal easy return messages is applied to a distributed transaction system and is characterized by comprising the following steps:

acquiring impulse orthogonal reciprocity data of impulse orthogonal transaction, wherein the impulse orthogonal reciprocity data comprises at least one data field and data values corresponding to the at least one data field respectively;

acquiring mapping logic between each transaction parameter in the orthogonal cover corresponding to the orthogonal cover and each data field;

determining a mapping relation between each transaction parameter and each data field in the forward transaction from the mapping logic, and using the mapping relation between each transaction parameter and each data field in the forward transaction as the mapping relation between each transaction parameter and each data field in the forward transaction;

and mapping the data fields in the forward transaction data according to the mapping relation between each transaction parameter and each data field in the forward transaction to obtain the data value corresponding to each transaction parameter in the forward transaction so as to generate a forward transaction return message.

2. The method of claim 1, wherein the distributed transaction system comprises at least one service component, each service component of the at least one service component configured to perform the forward transaction and the forward transaction, respectively, and generate forward transaction data corresponding to the forward transaction and orthogonal transaction data corresponding to the orthogonal transaction;

the orthogonal easy data comprises data values corresponding to the at least one data field and the at least one data field respectively;

the mapping logic comprises:

a determination rule for determining a correspondence between each of the transaction parameters and each of the service components in the transaction, an

The mapping relation between each transaction parameter in the positive transaction and the data field in the orthogonal easy data generated by the corresponding service component.

3. The method according to claim 2, wherein mapping the data fields in the transaction data according to the mapping relationship between each transaction parameter and each data field in the forward transaction to obtain the data value corresponding to each transaction parameter in the forward transaction comprises:

determining data fields in the forward transaction data corresponding to the transaction parameters in the forward transaction according to the mapping relation between the transaction parameters and the data fields in the forward transaction;

and taking the data value corresponding to the data field in the transaction data as the data value of each transaction parameter in the transaction.

4. The method of claim 3, further comprising:

setting a judgment identifier for each transaction parameter in the positive transaction, wherein the judgment identifier is used for identifying the service component corresponding to each transaction parameter;

and/or

And setting the judgment identification for each transaction parameter in the positive transaction, wherein the judgment identification is used for identifying the service component corresponding to each transaction parameter.

5. The method of claim 4, further comprising:

determining the service components corresponding to the transaction parameters in the forward trade based on the judgment identification;

and mapping the data value corresponding to the data field in the orthogonal transaction data generated by the corresponding service component to the data value of each transaction parameter in the forward transaction.

6. A method according to claim 2 or 3, characterized in that the method further comprises:

setting a first assembly identification for a record of access to the service assembly in the positive transaction;

setting a second assembly identifier corresponding to the first assembly identifier for each transaction parameter and/or the data field in the positive transaction;

and acquiring the corresponding relation between the record of the access service component and each transaction parameter and/or the data field based on the corresponding relation between the first assembly identification and the second assembly identification.

7. An apparatus for assembling an orthogonal easy return message, the apparatus comprising:

the device comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring orthogonal easy data of an orthogonal easy, and the orthogonal easy data comprises at least one data field and data values corresponding to the at least one data field respectively;

the second acquisition module is used for acquiring mapping logic between each transaction parameter in the orthogonal transaction corresponding to the orthogonal transaction and each data field;

a determining module, configured to determine, from the mapping logic, a mapping relationship between each transaction parameter and each data field in the forward transaction, and use the mapping relationship between each transaction parameter and each data field in the forward transaction as the mapping relationship between each transaction parameter and each data field in the forward transaction;

and the mapping module is used for mapping the data fields in the transaction data according to the mapping relation between each transaction parameter and each data field in the transaction to obtain the data value corresponding to each transaction parameter in the transaction to generate the transaction return message.

8. A distributed transaction system, the distributed transaction system including a user layer, an integration layer and a microservice layer, comprising:

the microservice layer executes a request of forward trade of the user layer and generates forward trade data corresponding to the forward trade;

the integration layer acquires forward trade data, wherein the forward trade data comprises at least one data field and data values corresponding to the at least one data field respectively;

the integration layer acquires mapping logic between each transaction parameter in the orthogonal cover corresponding to the orthogonal cover and each data field;

the integration layer determines a mapping relation between each transaction parameter and each data field in the forward transaction from the mapping logic, and uses the mapping relation between each transaction parameter and each data field in the forward transaction as the mapping relation between each transaction parameter and each data field in the forward transaction;

the integration layer maps the data fields in the transaction data according to the mapping relation between each transaction parameter and each data field in the transaction to obtain the data value corresponding to each transaction parameter in the transaction to generate a transaction return message;

and the integration layer sends the orthogonal easy return message to the user layer.

9. A computer program product, characterized in that it comprises instructions for implementing the orthogonal easy return message assembly method according to any one of claims 1 to 6.

10. A readable medium having stored thereon instructions which, when executed on an electronic device, cause the electronic device to perform the orthogonal easy return message assembly method of any one of claims 1 to 6.

11. An electronic device, comprising:

a memory for storing instructions for execution by one or more processors of the electronic device, an

A processor, which is one of the processors of the electronic device, configured to perform the orthogonal easy return message assembly method according to any one of claims 1 to 6.