Transaction message processing method and device, computer equipment and storage medium

Abstract

The invention provides a transaction message processing method and device, computer equipment and a storage medium, and belongs to the technical field of data processing. The method comprises the following steps: receiving source messages of different types of business transactions initiated by a first system through calling the same transaction service interface, and storing message contents into a transaction message table; according to a field mapping relation obtained from a pre-configured field conversion rule, establishing a corresponding relation between a field in a current to-be-processed source message in the transaction message table and a target message field, and according to a field processing rule obtained from the pre-configured field conversion rule, processing the target message in the current to-be-processed source message in the transaction message table, processing a field value of a field in the source message with the established corresponding relation, and assigning the field value to a corresponding target message field; and assembling the target message, and sending the target message to the second system. According to the method, the universal transaction service interface is defined in a field configuration mode, so that the development workload of the transaction service interface is reduced, and rapid support for new-type business transactions and field changes is realized.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and specifically to a transaction message processing method, a transaction message processing apparatus, a computer device, a machine-readable storage medium, and a computer program product. Background Art

[0002] In a business system with separated front-end and back-end, the front-end system is responsible for business entry and generating business transactions, while the back-end system is responsible for the background processing of business transactions. In the case of separation of the front-end and back-end business, the front-end system and the back-end system are usually designed and developed by different project teams. For the same type of business transactions, due to differences in transaction fields and database structure design, when a back-end system automatically accesses a transaction of a front-end system, the back-end system needs to develop and publish a transaction service interface service according to the transaction field requirements of this system, and the front-end system develops and calls it according to the transaction service interface. A business transaction of the front-end system entering the back-end system requires mapping, conversion and assembly processing of the transaction message. Typical processing methods are as follows: Figure 1 As shown, this treatment mainly faces the following two problems:

[0003] (1) Every time a new business transaction is added, the front-end and back-end systems need to add and develop transaction service interfaces, which takes a long time to develop and test;

[0004] (2) When the existing transaction service interface changes fields due to changes in business requirements, both the front-end and back-end systems need to be redeveloped and deployed, and the system is not flexible enough. Summary of the invention

[0005] The purpose of the embodiments of the present application is to provide a transaction message processing method, a transaction message processing device, a computer device, a machine-readable storage medium and a computer program product, so as to overcome the problems in the prior art of long development and testing cycles and inflexible field changes caused by developing different transaction service interfaces for different types of business transactions in order to support field mapping conversions for different types of business transactions.

[0006] In order to achieve the above-mentioned purpose, the first aspect of the present application provides a transaction message processing method, comprising:

[0007] receiving source messages of different types of business transactions initiated by the first system by calling the same transaction service interface, and storing message contents of the source messages in a transaction message table;

[0008] According to the field mapping relationship obtained from the pre-configured field conversion rules, a corresponding relationship between the field in the current source message to be processed and the field in the target message in the transaction message table is established, and according to the field processing rules obtained from the pre-configured field conversion rules, the field values ​​of the fields in the source message with established corresponding relationship are processed and assigned to the corresponding target message fields;

[0009] The target message is assembled according to the assigned target message fields and sent to the second system.

[0010] In the embodiment of the present application, the field processing rule is a processing calculation method for different fields composed of if-elseif branch structure statements, and the field values ​​of the fields in the source message with established corresponding relationships are processed and assigned to the corresponding target message fields, including:

[0011] Find the processing and calculation method of the source message field with established corresponding relationship from the processing and calculation methods of different fields composed of the if-elseif branch structure statement, and perform processing and calculation on the field value of the source message field according to the found processing and calculation method, and assign the processing and calculation result to the target message field corresponding to the source message field.

[0012] In the embodiment of the present application, the processing calculation method is one of the following calculation methods:

[0013] Assign fixed values ​​to the target message fields;

[0014] The field value of the target message field is equal to the field value of the corresponding source message field;

[0015] A combination of predefined character processing rules, wherein the character processing rules are processing and / or operation rules for the characters constituting the field value.

[0016] In an embodiment of the present application, the character processing rule includes at least one of the following rules:

[0017] Search for a specified string in a field value;

[0018] Extract the string in the field value;

[0019] Perform operations on the values ​​in the field values;

[0020] Keep the value in the field to the preset number of decimal places.

[0021] In an embodiment of the present application, the pre-configured field conversion rules are stored in a field conversion configuration table, and the field conversion configuration table is updated according to the received configuration instructions, and the updating method includes multiple of the following methods:

[0022] Add the source message field information and target message field information corresponding to the newly added business transaction type to the field conversion configuration table;

[0023] Delete the source message field information and target message field information corresponding to the existing business transaction type in the field conversion configuration table;

[0024] Update the field changes of the source message corresponding to the existing business transaction type to the field conversion configuration table;

[0025] Update the field changes of the target message corresponding to the existing business transaction type to the field conversion configuration table;

[0026] When any of the above updates is performed, the field mapping relationship and / or the field processing rule in the field conversion configuration table is updated according to the field change of the source message and / or the field change of the target message.

[0027] In an embodiment of the present application, the pre-configured field conversion rules are stored in a field conversion configuration table, a source message field configuration table, and a target message field configuration table. The field conversion configuration table, the source message field configuration table, and the target message field configuration table are updated according to the received configuration instructions. The updating method includes multiple of the following methods:

[0028] Adding source message field information corresponding to the newly added business transaction type to the source message field configuration table and adding target message field information corresponding to the newly added business transaction type to the target message field configuration table;

[0029] Deleting source message field information corresponding to an existing business transaction type in the source message field configuration table and deleting target message field information corresponding to the existing business transaction type in the target message field configuration table;

[0030] Update the field changes of the source message corresponding to the existing business transaction type to the source message field configuration table;

[0031] Update the target message field changes corresponding to the existing business transaction type to the target message field configuration table;

[0032] When any of the above updates is performed, the field mapping relationship and / or field processing rules in the field conversion configuration table are updated according to the field changes in the source message field configuration table and / or the target message field configuration table.

[0033] In the embodiment of the present application, the corresponding relationship between the field in the current source message to be processed and the target message field in the transaction message table is established according to the field mapping relationship obtained from the pre-configured field conversion rule, and the field value of the field in the source message with the established corresponding relationship is processed and assigned to the corresponding target message field according to the field processing rule obtained from the pre-configured field conversion rule, including:

[0034] Reading the current source message to be processed from the transaction message table;

[0035] Parse the message content of the current source message to be processed to obtain the source message fields and field values;

[0036] Using the parsed source message field, matching the source message field information in the source message field configuration table with the parsed source message field value;

[0037] The matching source message field information and source message field value are stored in the source message field information table, and registered in the to-be-processed message table;

[0038] Read the current pending record from the pending message table, and extract the source message field and field value corresponding to the current pending record from the source message field information table through the association of the primary key, and extract the field mapping relationship of the source message field corresponding to the current pending record and the field processing rule of the field value corresponding to the current pending record from the field conversion configuration table;

[0039] A correspondence between source message fields and target message fields is established according to the field mapping relationship, and the field values ​​of the source message fields with established correspondence are processed according to the field processing rules and then assigned to the corresponding target message fields.

[0040] In an embodiment of the present application, the fields in the field conversion configuration table include a first system identifier, a business transaction type, a source message field name, a target message field name, and a field processing rule.

[0041] In an embodiment of the present application, the fields in the source message field configuration table include a first system identifier, a business transaction type, a source message field name, and a data type of a source message field value.

[0042] In an embodiment of the present application, the fields in the target message field configuration table include business transaction type, target message field name and data type of target message field value.

[0043] In the embodiment of the present application, the primary key is the source message number.

[0044] A second aspect of the present application provides a transaction message processing device, comprising:

[0045] A transaction message receiving module, used to receive source messages of different types of business transactions initiated by the first system by calling the same transaction service interface, and store the message content of the source message into the transaction message table;

[0046] The message processing module is used to establish a correspondence between the fields in the current source message to be processed and the target message fields in the transaction message table according to the field mapping relationship obtained from the pre-configured field conversion rules, and to process the field values ​​of the fields in the source message with established correspondence and assign them to the corresponding target message fields according to the field processing rules obtained from the pre-configured field conversion rules;

[0047] The transaction message assembly module is used to assemble the target message according to the assigned target message fields and send the target message to the second system.

[0048] The third aspect of the present application provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the transaction message processing method described in the first aspect of the present application when executing the program.

[0049] The fourth aspect of the present application provides a machine-readable storage medium, on which instructions are stored. When the instructions are executed by a processor, the processor is configured to execute the transaction message processing method described in the first aspect of the present application.

[0050] The fifth aspect of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the transaction message processing method described in the first aspect of the present application.

[0051] The above technical solution proposes a universal transaction message processing framework, using a universal transaction service interface to replace a group of transaction service interfaces of the same type between the first system and the second system. In the transaction message processing framework, the field mapping and processing of the source message to the target message are performed through the pre-configured field conversion rules. It can be seen that the above technical solution sets the field conversion rules in a configurable manner, that is, by defining the universal transaction service interface in a field configurable manner, the definition and development workload of the transaction service interface is reduced, and rapid support for new types of business transactions and field changes is achieved, which can flexibly meet the addition and change of business transaction requirements.

[0052] Other features and advantages of the embodiments of the present application will be described in detail in the subsequent specific implementation section. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] The accompanying drawings are used to provide a further understanding of the embodiments of the present application and constitute a part of the specification. Together with the following specific implementations, they are used to explain the embodiments of the present application, but do not constitute a limitation on the embodiments of the present application. In the accompanying drawings:

[0054] Figure 1 A schematic diagram of a typical processing method in the background technology is schematically shown;

[0055] Figure 2 The following is a schematic diagram showing a flow chart of a transaction message processing method according to an embodiment of the present application;

[0056] Figure 3 A diagram schematically shows an application environment in which the second system according to an embodiment of the present application is located;

[0057] Figure 4 A schematic diagram schematically shows a process diagram of a transaction message processing method according to an embodiment of the present application;

[0058] Figure 5 The structure block diagram of the transaction message processing device according to the embodiment of the present application is schematically shown;

[0059] Figure 6 The block diagram schematically shows the composition of the transaction message processing device in a specific application example;

[0060] Figure 7 The block diagram schematically shows a composition of a computer device according to an embodiment of the present application. DETAILED DESCRIPTION

[0061] In order to make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It should be understood that the specific implementation methods described herein are only used to illustrate and explain the embodiments of the present application, and are not used to limit the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0062] It should be noted that if the embodiments of the present application involve directional indications (such as up, down, left, right, front, back...), the directional indications are only used to explain the relative position relationship, movement status, etc. between the components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication will also change accordingly.

[0063] In addition, if there are descriptions involving "first", "second", etc. in the embodiments of the present application, the descriptions of "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or suggesting their relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the ability of ordinary technicians in the field to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such combination of technical solutions does not exist and is not within the scope of protection required by this application.

[0064] The acquisition, transmission, storage, use, and processing of data in the technical solution of this application are in compliance with the relevant provisions of national laws and regulations. In addition, it should be noted that in the embodiments of this application, some existing solutions in the industry such as certain software, components, and models may be mentioned, which should be considered as exemplary, and their purpose is only to illustrate the feasibility of the implementation of the technical solution of this application, but it does not mean that the applicant has or will necessarily use the solution.

[0065] Figure 1 The schematic diagram of the process of a typical transaction message processing method in the prior art is schematically shown. The front-end system enters different types of transactions, and the front-end system initiates calls to different transaction service interfaces according to the different types of business transactions entered. The back-end system performs service interface processing for different types of business transactions, and generates business transactions after message processing and performs subsequent transaction processing. Figure 1 In the example, there are multiple transactions entered into the front-end system, including entry of transaction A, entry of transaction B, and entry of transaction N, etc. There are multiple transaction service interface calls initiated by the front-end system, including request service interface A, request service interface B, and request service interface N, etc. There are multiple service interface processings executed by the back-end system, including service interface A processing, service interface B processing, and service interface N processing, etc. There are multiple transaction generation executed by the back-end system, including generation of transaction A, generation of transaction B, and generation of transaction N.

[0066] Different from the above-mentioned typical transaction message processing method, the present application proposes a universal transaction message processing method. Figure 2 The following is a schematic diagram showing a flow chart of a transaction message processing method according to an embodiment of the present application. Figure 2 As shown, in one embodiment of the present application, a transaction message processing method is provided, comprising the following steps:

[0067] Step 202: receiving source messages of different types of business transactions initiated by the first system by calling the same transaction service interface, and storing the message contents of the received source messages into a transaction message table.

[0068] Step 204, based on the field mapping relationship obtained from the pre-configured field conversion rules, establish a correspondence between the fields in the current source message to be processed in the transaction message table and the target message fields, and based on the field processing rules obtained from the pre-configured field conversion rules, process the field values ​​of the fields in the source message with the established correspondence and assign them to the corresponding target message fields.

[0069] In the present application, the pre-configured field conversion rules may be stored in a configuration table.

[0070] Step 206, assembling the target message according to the assigned target message fields to obtain the target message, and sending the target message to the second system.

[0071] In the present application, the first system sends a source message, and thus may also be referred to as a source system, and the second system receives a target message, and thus may also be referred to as a target system.

[0072] In the above embodiment, a universal transaction message processing method is defined. Universal means that it can process messages of multiple different types of business transactions. From the perspective of the transaction message processing framework, universal means that the transaction service interface is universal, that is, a unified transaction service interface is used to replace multiple transaction service interfaces of the same type, and the implementation of the universal transaction service interface is realized in a configured manner. The configured manner means that the field conversion rules are pre-entered in the transaction message processing framework in a configured manner. The field conversion rules include the field mapping relationship and field processing rules from the source message field to the target message field of different types of business transactions. Through the universality of the transaction message processing method, it is avoided to develop different transaction service interfaces for different types of business transactions, thereby saving the development cycle, testing cycle and labor costs, and when the business requirements change and the fields are changed and new business requirements are added, it is only necessary to reconfigure the configured field conversion rules, realizing low-code dynamic support for the addition and change of business requirements, and having strong flexibility.

[0073] For example, in a specific application, the transaction message processing method implemented in the above embodiment of the present application is executed by the second system, that is, the transaction message processing method is applied to the second system, and the application environment of the second system is as follows: Figure 3 As shown. The first system 102 communicates with the second system 104 through a network. The first system 102 may be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, and portable wearable devices, and the second system 104 may be implemented by an independent server or a server cluster consisting of multiple servers. By proposing the general transaction message processing method in the above embodiment, the flexibility of the second system is enhanced, that is, the second system can quickly support different types of business transactions.

[0074] exist Figure 4 In the specific embodiment shown, the first system that sends the source message is the front-end system, and the second system that receives the target message is the back-end system. The transaction entry of the front-end system includes multiple transactions, namely, transaction A, transaction B, and transaction N. After each transaction is entered, the source message is sent by calling the same transaction service interface ( Figure 4 The request service interface process shown in the figure) is then carried out through the transaction message processing method of the above embodiment of the present application to realize the mapping conversion from the source message to the target message. After the target message is assembled, the back-end system obtains each target message through the service interface processing, that is, the transaction generation of the back-end system includes multiple, namely, generating transaction A, generating transaction B and generating transaction N, etc., and finally the back-end system performs subsequent transaction processing.

[0075] In a specific embodiment of the present application, the pre-configured column conversion rules are stored in a column conversion configuration table. The column conversion configuration table is updated according to the received configuration instructions, and the updating method includes multiple of the following methods:

[0076] Add the source message field information and target message field information corresponding to the newly added business transaction type to the field conversion configuration table;

[0077] Delete the source message field information and target message field information corresponding to the existing business transaction type in the field conversion configuration table;

[0078] Update the field changes of the source message corresponding to the existing business transaction type to the field conversion configuration table;

[0079] Update the field changes of the target message corresponding to the existing business transaction type to the field conversion configuration table;

[0080] When any of the above updates is performed, the field mapping relationship and / or the field processing rule in the field conversion configuration table is updated according to the field change of the source message and / or the field change of the target message.

[0081] It should be understood that updating the field mapping relationship and / or field processing rules in the field conversion configuration table according to the field changes of the source message and / or the field changes of the target message means that: for the first update method mentioned above, because it is a new business transaction type, the source message field information and the target message field information are both newly added in the field conversion configuration table, and accordingly, new field mapping relationships and field processing rules need to be added; for the second update method mentioned above, because it is a deletion of an existing business transaction type, the source message field information and the target message field information are both newly added in the field conversion configuration table. If there is deletion, the corresponding field mapping relationship and field processing rules need to be deleted accordingly; for the third update method mentioned above, it involves field changes of the source message of the existing business transaction type, so the field changes need to be updated in the field conversion configuration table, and accordingly, the changed field processing rules need to be updated in the field conversion configuration table; similarly, for the fourth update method mentioned above, it involves field changes of the target message of the existing business transaction type, so the field changes need to be updated in the field conversion configuration table, and accordingly, the changed field processing rules need to be updated in the field conversion configuration table.

[0082] In the above embodiment of the present application, by modifying the field conversion configuration table according to the configuration instructions input externally, rapid support for changes in business transaction types and / or transaction fields is achieved.

[0083] In a specific embodiment of the present application, the pre-configured field conversion rules are stored in a field conversion configuration table, a source message field configuration table, and a target message field configuration table. The field conversion configuration table, the source message field configuration table, and the target message field configuration table are updated according to the received configuration instructions. The updating method includes multiple of the following methods:

[0084] Adding source message field information corresponding to the newly added business transaction type to the source message field configuration table and adding target message field information corresponding to the newly added business transaction type to the target message field configuration table;

[0085] Deleting source message field information corresponding to an existing business transaction type in the source message field configuration table and deleting target message field information corresponding to the existing business transaction type in the target message field configuration table;

[0086] Update the field changes of the source message corresponding to the existing business transaction type to the source message field configuration table;

[0087] Update the target message field changes corresponding to the existing business transaction type to the target message field configuration table;

[0088] When any of the above updates is performed, the field mapping relationship and / or field processing rules in the field conversion configuration table are updated according to the field changes in the source message field configuration table and / or the target message field configuration table.

[0089] In the above embodiment of the present application, by modifying multiple of the source message field configuration table, the target message field configuration table and the field conversion configuration table according to the configuration instructions input externally, rapid support for changes in business transaction types and / or transaction fields is achieved. Compared with only using one field conversion configuration table, the source message field information, the target message field information, the field mapping relationship and the field processing rules are saved and updated in a separate table manner, which is convenient for maintenance.

[0090] Figure 2 FIG. 1 is a flow chart of a transaction message processing method in one embodiment. It should be understood that although Figure 2 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 2 At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.

[0091] In a specific embodiment of the present application, step 204, according to the field mapping relationship obtained from the pre-configured field conversion rule, establishes a correspondence between the field in the current source message to be processed in the transaction message table and the target message field, and according to the field processing rule obtained from the pre-configured field conversion rule, processes the field value of the field in the source message with the established correspondence and assigns it to the corresponding target message field, including the following steps:

[0092] Read the current source message to be processed from the transaction message table;

[0093] Parse the message content of the current message to be processed to obtain the source message field and field value;

[0094] Using the parsed source message field, matching the source message field information in the source message field configuration table with the parsed source message field value;

[0095] The matching source message field information and source message field value are stored in the source message field information table, and registered in the to-be-processed message table;

[0096] Read the current pending record from the pending message table, and extract the source message field and field value corresponding to the current pending record from the source message field information table through the association of the primary key, and extract the field mapping relationship of the source message field corresponding to the current pending record and the field processing rule of the field value corresponding to the current pending record from the field conversion configuration table;

[0097] A correspondence between source message fields and target message fields is established according to the extracted field mapping relationship, and the field value of the source message field with the established correspondence is processed according to the extracted field processing rule and then assigned to the corresponding target message field.

[0098] As in the above embodiment, on the basis of preserving the source message field information, the target message field information, the field mapping relationship and the field processing rules in the form of separate tables, after receiving the source message from the first system, in the process of sequentially processing the source message to be processed in the transaction message table, in order to facilitate the information maintenance in the source message to target message mapping conversion process, the source message is first parsed, and the source message field information is extracted from the source message field configuration table using the fields during the parsing process, and a source message field information table and a to-be-processed message table for storing the parsed data are set, and the two tables are associated by a primary key, and then the mapping conversion of the source message is performed, and the current to-be-processed record is read from the to-be-processed message table during the mapping conversion, and the source message field and field value are extracted from the source message field information table by the primary key association, and then the field conversion configuration table is associated to retrieve the target message field and the field processing rule. Through the parsing process, the key information of the source message field is stored separately, and a table of pending messages associated with the source message field information table through a primary key is separated out, and then the target message fields and field processing rules are extracted from the pending records in the table of pending messages. The separate storage of the source message field information, the table separation method, and the primary key association and matching between multiple tables improve the reliability and efficiency of the mapping and conversion process from the source message to the target message when the number of messages is large, and support the reliability and efficiency of transaction message processing under the general transaction message processing framework proposed in this application.

[0099] In a specific embodiment of the present application, the source message field information table and the to-be-processed message table may be associated by primary key through the source message number.

[0100] For example, the fields in the source message field information table may include the first system identifier, business transaction type, source message number, source message field sequence number, source message field name and field value, etc.; the fields in the pending message table may include the first system identifier, business transaction type, source message number, current status, etc. The current status refers to the processing status of the corresponding record. For example, if the source message corresponding to a record has completed the mapping conversion to the target message, the current status may be processed. If the source message corresponding to a record has not completed the mapping conversion to the target message, the current status may be pending.

[0101] In a specific embodiment of the present application, the fields in the field conversion configuration table may include the first system identifier, the business transaction type, the source message field name, the target message field name, and the field processing rule, etc. For example, in a specific application example, the fields in the field conversion configuration table include the first system identifier, the first system identifier, the business transaction type, the source message field sequence number, the source message field name, the target message field sequence number, the target message field name, and the field processing rule.

[0102] In a specific embodiment of the present application, the fields in the source message field configuration table may include the first system identifier, the business transaction type, the source message field name, and the data type of the source message field value, etc. For example, in a specific application example, the fields in the source message field configuration table may include the first system identifier, the business transaction type, the source message field sequence number, the source message field name, and the data type of the source message field value.

[0103] In a specific embodiment of the present application, the fields in the target message field configuration table may include business transaction type, target message field name, and data type of target message field value, etc. For example, in a specific application example, the fields in the target message field configuration table include business transaction type, target message field sequence number, target message field name, and data type of target message field value.

[0104] In a specific embodiment of the present application, the fields in the transaction message table may include a first system identifier, a business transaction type, a source message number, message content of the source message, a current status, and the like.

[0105] In a specific embodiment of the present application, an improved field processing rule is also proposed. Specifically, the improved field processing rule is a processing calculation method for different fields composed of if-elseif branch structure statements. Accordingly, in step 204, the field value of the field in the source message with established corresponding relationship is processed and assigned to the corresponding target message field, including:

[0106] Find the processing and calculation method of the source message field with established corresponding relationship from the processing and calculation methods of different fields composed of the if-elseif branch structure statement, and perform processing and calculation on the field value of the source message field according to the found processing and calculation method, and assign the processing and calculation result to the target message field corresponding to the source message field.

[0107] In the present application, the if-elseif branch structure statement refers to: IF (expression 1) THEN (expression 2) ELSEIF (expression 3) ... ENDIF. For example, IF EqualStr($col1$, "FX") THEN "CFX" ELSEIF EqualStr($col1$, "DL") THEN "DLD" ENDIF, this statement means: if the source message field col1 = FX, then the target field value is set to the processing calculation result CFX; if the source message field col1 = DL, then the target field value is set to the processing calculation result DLD.

[0108] As in the above embodiment, the field processing rules defined based on the if-elseif branch structure statement are easy to expand the program, and can support flexible customization to meet the different field assignment requirements of different types of business transactions. Therefore, under the above-mentioned general transaction message processing framework, when faced with a large number of types of business transaction messages, the field processing rules can be quickly defined and expanded, saving development time.

[0109] In a specific embodiment of the present application, the processing calculation method is one of the following calculation methods:

[0110] Assign fixed values ​​to the target message fields;

[0111] The field value of the target message field is equal to the field value of the corresponding source message field;

[0112] A combination of predefined character processing rules, where the character processing rules are processing and / or operation rules for the characters that make up the field value.

[0113] Because the field value is composed of characters, which can be numerical values, strings, dates, etc., the first processing and calculation method is to assign a fixed value (which may include a null value) to the target message field, the second processing and calculation method is to assign a value directly, and the third method is to combine predefined character processing rules. By predefining character processing rules and then obtaining the required processing and calculation method through the combination of character processing rules, the program is easy to expand and can support flexible and customized methods to meet the different field assignment requirements of different types of business transactions.

[0114] For example, in a specific application, the defined processing calculation method is shown in the following table.

[0115] Table 1

[0116]

[0117] Exemplarily, the character processing rules may include at least one of the following rules:

[0118] Search for a specified string in a field value;

[0119] Extract the string in the field value;

[0120] Perform operations on the values ​​in the field values;

[0121] Keep the value in the field to the preset number of decimal places.

[0122] For example, in a specific application, the predefined character processing rules are shown in the following table.

[0123] Table 2

[0124] Character processing rules Function Description FindInStr Search for the specified content in the target string SubStr Extract a substring from the target string EqualStr Compare strings for equality MultiNums Multiply / divide numbers AddNums Adding / subtracting numbers RoundNum Keep decimal precision for the value according to the parameter

[0125] It should be understood that Table 1 and Table 2 are only exemplary descriptions, and other processing calculation methods and character processing rules may be included in combination with specific application requirements.

[0126] In a specific embodiment of the present application, step 206, assembling the target message according to the assigned target message fields and sending the target message to the second system, includes the following steps:

[0127] The information of the assigned target message field is stored in the target message field information table;

[0128] Extracting information of all target message fields with the same target message number from the target message field information table and assembling them to obtain the target message;

[0129] Send the target message to the second system.

[0130] In one embodiment, Figure 5 As shown, a transaction message processing device 400 is provided, comprising a transaction message receiving module 402, a message processing module 404 and a transaction message assembling module 406, wherein:

[0131] The transaction message receiving module 402 is used to receive source messages of different types of business transactions initiated by the first system by calling the same transaction service interface, and store the message content of the source message into the transaction message table;

[0132] The message processing module 404 is used to establish a correspondence between the fields in the current source message to be processed and the target message fields in the transaction message table according to the field mapping relationship obtained from the pre-configured field conversion rules, and to process the field values ​​of the fields in the source message with established correspondence and assign them to the corresponding target message fields according to the field processing rules obtained from the pre-configured field conversion rules;

[0133] The transaction message assembling module 406 is used to assemble the target message according to the assigned target message fields and send the target message to the second system.

[0134] In a specific embodiment, the field processing rule is a processing calculation method for different fields composed of if-elseif branch structure statements, and the field values ​​of the fields in the source message with established corresponding relationships are processed and assigned to the corresponding target message fields, including:

[0135] Find the processing and calculation method of the source message field with established corresponding relationship from the processing and calculation methods of different fields composed of the if-elseif branch structure statement, and perform processing and calculation on the field value of the source message field according to the found processing and calculation method, and assign the processing and calculation result to the target message field corresponding to the source message field.

[0136] In a specific embodiment, the processing calculation method is one of the following calculation methods:

[0137] Assign fixed values ​​to the target message fields;

[0138] The field value of the target message field is equal to the field value of the corresponding source message field;

[0139] A combination of predefined character processing rules, wherein the character processing rules are processing and / or operation rules for the characters constituting the field value.

[0140] In a specific embodiment, the character processing rule includes at least one of the following rules:

[0141] Search for a specified string in a field value;

[0142] Extract the string in the field value;

[0143] Perform operations on the values ​​in the field values;

[0144] Keep the value in the field to the preset number of decimal places.

[0145] In a specific embodiment, the pre-configured field conversion rules are stored in a field conversion configuration table, and the field conversion configuration table is updated according to the received configuration instructions, and the updating method includes multiple methods of the following methods:

[0146] Add the source message field information and target message field information corresponding to the newly added business transaction type to the field conversion configuration table;

[0147] Delete the source message field information and target message field information corresponding to the existing business transaction type in the field conversion configuration table;

[0148] Update the field changes of the source message corresponding to the existing business transaction type to the field conversion configuration table;

[0149] Update the field changes of the target message corresponding to the existing business transaction type to the field conversion configuration table;

[0150] When any of the above updates is performed, the field mapping relationship and / or the field processing rule in the field conversion configuration table is updated according to the field change of the source message and / or the field change of the target message.

[0151] In a specific embodiment, the pre-configured field conversion rules are stored in a field conversion configuration table, a source message field configuration table, and a target message field configuration table. The field conversion configuration table, the source message field configuration table, and the target message field configuration table are updated according to the received configuration instructions. The updating method includes multiple of the following methods:

[0152] Adding source message field information corresponding to the newly added business transaction type to the source message field configuration table and adding target message field information corresponding to the newly added business transaction type to the target message field configuration table;

[0153] Deleting source message field information corresponding to an existing business transaction type in the source message field configuration table and deleting target message field information corresponding to the existing business transaction type in the target message field configuration table;

[0154] Update the field changes of the source message corresponding to the existing business transaction type to the source message field configuration table;

[0155] Update the target message field changes corresponding to the existing business transaction type to the target message field configuration table;

[0156] When any of the above updates is performed, the field mapping relationship and / or field processing rules in the field conversion configuration table are updated according to the field changes in the source message field configuration table and / or the target message field configuration table.

[0157] In a specific embodiment, according to the field mapping relationship obtained from the pre-configured field conversion rule, a corresponding relationship between the field in the current source message to be processed and the target message field in the transaction message table is established, and according to the field processing rule obtained from the pre-configured field conversion rule, the field value of the field in the source message with the established corresponding relationship is processed and assigned to the corresponding target message field, including:

[0158] Reading the current source message to be processed from the transaction message table;

[0159] Parse the message content of the current source message to be processed to obtain the source message fields and field values;

[0160] Using the parsed source message field, matching the source message field information in the source message field configuration table with the parsed source message field value;

[0161] The matching source message field information and source message field value are stored in the source message field information table, and registered in the to-be-processed message table;

[0162] Read the current pending record from the pending message table, and extract the source message field and field value corresponding to the current pending record from the source message field information table through the association of the primary key, and extract the field mapping relationship of the source message field corresponding to the current pending record and the field processing rule of the field value corresponding to the current pending record from the field conversion configuration table;

[0163] A correspondence between source message fields and target message fields is established according to the field mapping relationship, and the field values ​​of the source message fields with established correspondence are processed according to the field processing rules and then assigned to the corresponding target message fields.

[0164] In a specific embodiment, the fields in the field conversion configuration table include a first system identifier, a business transaction type, a source message field name, a target message field name, and a field processing rule.

[0165] In a specific embodiment, the fields in the source message field configuration table include a first system identifier, a business transaction type, a source message field name, and a data type of a source message field value.

[0166] In a specific embodiment, the fields in the target message field configuration table include business transaction type, target message field name and data type of target message field value.

[0167] In a specific embodiment, the primary key is the source message number.

[0168] Figure 6 The framework diagram of a transaction message processing device in a specific application is schematically shown. Figure 6In the embodiment, the transaction message processing device includes a transaction message configuration module, a transaction message receiving module, a transaction message parsing module, a transaction message conversion module and a data storage module, wherein the transaction message configuration module is used to configure the field conversion configuration table, the source message field configuration table and the target message field configuration table, and the transaction message conversion module is composed of a transaction message mapping module and a transaction message assembly module. Preferably, the message reception performed by the transaction message receiving module, the message parsing performed by the transaction message parsing module, the message mapping conversion performed by the transaction message mapping module and the message assembly performed by the transaction message assembly module can be processed asynchronously by multiple threads.

[0169] The transaction message processing device includes a processor and a memory. The transaction message receiving module 402, message processing module 404 and transaction message assembling module 406 are all stored in the memory as program units, and the processor executes the program modules stored in the memory to implement corresponding functions.

[0170] The processor includes a kernel, which calls the corresponding program unit from the memory. One or more kernels can be set, and the transaction message processing method is implemented by adjusting the kernel parameters.

[0171] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0172] An embodiment of the present application provides a machine-readable storage medium on which a program is stored, and when the program is executed by a processor, the above-mentioned transaction message processing method is implemented.

[0173] An embodiment of the present application provides a processor, which is used to run a program, wherein the program executes the above-mentioned transaction message processing method when running.

[0174] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 7As shown. The computer device includes a processor A01, a network interface A02, a display screen A04, an input device A05 and a memory (not shown in the figure) connected through a system bus. Among them, the processor A01 of the computer device is used to provide computing and control capabilities. The memory of the computer device includes an internal memory A03 and a non-volatile storage medium A06. The non-volatile storage medium A06 stores an operating system B01 and a computer program B02. The internal memory A03 provides an environment for the operation of the operating system B01 and the computer program B02 in the non-volatile storage medium A06. The network interface A02 of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor A01, a transaction message processing method is implemented. The display screen A04 of the computer device can be a liquid crystal display or an electronic ink display, and the input device A05 of the computer device can be a touch layer covered on the display screen, or a button, trackball or touchpad set on the computer device housing, or an external keyboard, touchpad or mouse, etc.

[0175] Those skilled in the art will understand that Figure 7 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0176] In one embodiment, the transaction message processing device provided by the present application can be implemented in the form of a computer program. The computer program can be Figure 7 The memory of the computer device can store various program modules constituting the transaction message processing device, for example, Figure 5 The transaction message receiving module 402, the message processing module 404 and the transaction message assembling module 406 are shown. The computer program composed of each program module enables the processor to execute the steps in the transaction message processing method of each embodiment of the present application described in this specification.

[0177] Figure 7 The computer device shown can be Figure 5 The transaction message receiving module 402 in the transaction message processing apparatus shown executes step 202 , the computer device may execute step 204 through the message processing module 404 , and the computer device may execute step 206 through the transaction message assembling module 406 .

[0178] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing a program for initializing the following method steps:

[0179] receiving source messages of different types of business transactions initiated by the first system by calling the same transaction service interface, and storing message contents of the source messages in a transaction message table;

[0180] According to the field mapping relationship obtained from the pre-configured field conversion rules, a corresponding relationship between the field in the current source message to be processed and the field in the target message in the transaction message table is established, and according to the field processing rules obtained from the pre-configured field conversion rules, the field values ​​of the fields in the source message with established corresponding relationship are processed and assigned to the corresponding target message fields;

[0181] The target message is assembled according to the assigned target message fields and sent to the second system.

[0182] In a specific embodiment, the field processing rule is a processing calculation method for different fields composed of if-elseif branch structure statements, and the field values ​​of the fields in the source message with established corresponding relationships are processed and assigned to the corresponding target message fields, including:

[0183] Find the processing and calculation method of the source message field with established corresponding relationship from the processing and calculation methods of different fields composed of the if-elseif branch structure statement, and perform processing and calculation on the field value of the source message field according to the found processing and calculation method, and assign the processing and calculation result to the target message field corresponding to the source message field.

[0184] In a specific embodiment, the processing calculation method is one of the following calculation methods:

[0185] Assign fixed values ​​to the target message fields;

[0186] The field value of the target message field is equal to the field value of the corresponding source message field;

[0187] A combination of predefined character processing rules, wherein the character processing rules are processing and / or operation rules for the characters constituting the field value.

[0188] In a specific embodiment, the character processing rule includes at least one of the following rules:

[0189] Search for a specified string in a field value;

[0190] Extract the string in the field value;

[0191] Perform operations on the values ​​in the field values;

[0192] Keep the value in the field to the preset number of decimal places.

[0193] In a specific embodiment, the pre-configured field conversion rules are stored in a field conversion configuration table, and the field conversion configuration table is updated according to the received configuration instructions, and the updating method includes multiple of the following methods:

[0194] Add the source message field information and target message field information corresponding to the newly added business transaction type to the field conversion configuration table;

[0195] Delete the source message field information and target message field information corresponding to the existing business transaction type in the field conversion configuration table;

[0196] Update the field changes of the source message corresponding to the existing business transaction type to the field conversion configuration table;

[0197] Update the field changes of the target message corresponding to the existing business transaction type to the field conversion configuration table;

[0198] When any of the above updates is performed, the field mapping relationship and / or the field processing rule in the field conversion configuration table is updated according to the field change of the source message and / or the field change of the target message.

[0199] In a specific embodiment, the pre-configured field conversion rules are stored in a field conversion configuration table, a source message field configuration table, and a target message field configuration table. The field conversion configuration table, the source message field configuration table, and the target message field configuration table are updated according to the received configuration instructions. The updating method includes multiple of the following methods:

[0200] Adding source message field information corresponding to the newly added business transaction type to the source message field configuration table and adding target message field information corresponding to the newly added business transaction type to the target message field configuration table;

[0201] Deleting source message field information corresponding to an existing business transaction type in the source message field configuration table and deleting target message field information corresponding to the existing business transaction type in the target message field configuration table;

[0202] Update the field changes of the source message corresponding to the existing business transaction type to the source message field configuration table;

[0203] Update the target message field changes corresponding to the existing business transaction type to the target message field configuration table;

[0204] When any of the above updates is performed, the field mapping relationship and / or field processing rules in the field conversion configuration table are updated according to the field changes in the source message field configuration table and / or the target message field configuration table.

[0205] In a specific embodiment, the corresponding relationship between the field in the current source message to be processed and the target message field in the transaction message table is established according to the field mapping relationship obtained from the pre-configured field conversion rule, and the field value of the field in the source message with the established corresponding relationship is processed and assigned to the corresponding target message field according to the field processing rule obtained from the pre-configured field conversion rule, including:

[0206] Reading the current source message to be processed from the transaction message table;

[0207] Parse the message content of the current source message to be processed to obtain the source message fields and field values;

[0208] Using the parsed source message field, matching the source message field information in the source message field configuration table with the parsed source message field value;

[0209] The matching source message field information and source message field value are stored in the source message field information table, and registered in the to-be-processed message table;

[0210] Read the current pending record from the pending message table, and extract the source message field and field value corresponding to the current pending record from the source message field information table through the association of the primary key, and extract the field mapping relationship of the source message field corresponding to the current pending record and the field processing rule of the field value corresponding to the current pending record from the field conversion configuration table;

[0211] A correspondence between source message fields and target message fields is established according to the field mapping relationship, and the field values ​​of the source message fields with established correspondence are processed according to the field processing rules and then assigned to the corresponding target message fields.

[0212] In a specific embodiment, the fields in the field conversion configuration table include a first system identifier, a business transaction type, a source message field name, a target message field name, and a field processing rule.

[0213] In a specific embodiment, the fields in the source message field configuration table include a first system identifier, a business transaction type, a source message field name, and a data type of a source message field value.

[0214] In a specific embodiment, the fields in the target message field configuration table include business transaction type, target message field name and data type of target message field value.

[0215] In a specific embodiment, the primary key is the source message number.

[0216] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0217] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0218] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0219] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

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

[0221] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0222] Computer readable media include permanent and non-permanent, removable and non-removable media, and can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0223] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0224] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A transaction message processing method, characterized in that: include: receiving source messages of different types of business transactions initiated by the first system by calling the same transaction service interface, and storing message contents of the source messages in a transaction message table; According to the field mapping relationship obtained from the pre-configured field conversion rules, a corresponding relationship between the field in the current source message to be processed and the field in the target message in the transaction message table is established, and according to the field processing rules obtained from the pre-configured field conversion rules, the field values ​​of the fields in the source message with established corresponding relationship are processed and assigned to the corresponding target message fields; The target message is assembled according to the assigned target message fields and sent to the second system.

2. The method according to claim 1, characterized in that: The field processing rule is a processing calculation method for different fields composed of if-elseif branch structure statements, and the field values ​​of the fields in the source message with established corresponding relationships are processed and assigned to the corresponding target message fields, including: Find the processing and calculation method of the source message field with established corresponding relationship from the processing and calculation methods of different fields composed of the if-elseif branch structure statement, and perform processing and calculation on the field value of the source message field according to the found processing and calculation method, and assign the processing and calculation result to the target message field corresponding to the source message field.

3. The method according to claim 2, characterized in that The processing calculation method is one of the following calculation methods: Assign fixed values ​​to the target message fields; The field value of the target message field is equal to the field value of the corresponding source message field; A combination of predefined character processing rules, wherein the character processing rules are processing and / or operation rules for the characters constituting the field value.

4. The method according to claim 3, characterized in that The character processing rules include at least one of the following rules: Search for a specified string in a field value; Extract the string in the field value; Perform operations on the values ​​in the field values; Keep the value in the field to the preset number of decimal places.

5. The method according to claim 1, characterized in that: The pre-configured field conversion rules are stored in a field conversion configuration table, and the field conversion configuration table is updated according to the received configuration instructions. The updating method includes multiple methods of the following methods: Add the source message field information and target message field information corresponding to the newly added business transaction type to the field conversion configuration table; Delete the source message field information and target message field information corresponding to the existing business transaction type in the field conversion configuration table; Update the field changes of the source message corresponding to the existing business transaction type to the field conversion configuration table; Update the field changes of the target message corresponding to the existing business transaction type to the field conversion configuration table; When any of the above updates is performed, the field mapping relationship and / or the field processing rule in the field conversion configuration table is updated according to the field change of the source message and / or the field change of the target message.

6. The method according to claim 1, characterized in that The pre-configured field conversion rules are stored in a field conversion configuration table, a source message field configuration table, and a target message field configuration table. The field conversion configuration table, the source message field configuration table, and the target message field configuration table are updated according to the received configuration instructions. The updating method includes multiple of the following methods: Adding source message field information corresponding to the newly added business transaction type to the source message field configuration table and adding target message field information corresponding to the newly added business transaction type to the target message field configuration table; Deleting source message field information corresponding to an existing business transaction type in the source message field configuration table and deleting target message field information corresponding to the existing business transaction type in the target message field configuration table; Update the field changes of the source message corresponding to the existing business transaction type to the source message field configuration table; Update the target message field changes corresponding to the existing business transaction type to the target message field configuration table; When any of the above updates is performed, the field mapping relationship and / or field processing rules in the field conversion configuration table are updated according to the field changes in the source message field configuration table and / or the target message field configuration table.

7. The method according to claim 6, characterized in that The step of establishing a correspondence between the fields in the current source message to be processed and the target message fields in the transaction message table according to the field mapping relationship obtained from the pre-configured field conversion rules, and processing the field values ​​of the fields in the source message with the established correspondence and assigning them to the corresponding target message fields according to the field processing rules obtained from the pre-configured field conversion rules, includes: Reading the current source message to be processed from the transaction message table; Parse the message content of the current source message to be processed to obtain the source message fields and field values; Using the parsed source message field, matching the source message field information in the source message field configuration table with the parsed source message field value; The matching source message field information and source message field value are stored in the source message field information table and registered in the to-be-processed message table; Read the current pending record from the pending message table, and extract the source message field and field value corresponding to the current pending record from the source message field information table through the association of the primary key, and extract the field mapping relationship of the source message field corresponding to the current pending record and the field processing rule of the field value corresponding to the current pending record from the field conversion configuration table; A correspondence between source message fields and target message fields is established according to the field mapping relationship, and the field values ​​of the source message fields with established correspondence are processed according to the field processing rules and then assigned to the corresponding target message fields.

8. The method according to any one of claims 5 to 7, characterized in that The fields in the field conversion configuration table include a first system identifier, a business transaction type, a source message field name, a target message field name, and a field processing rule.

9. The method according to claim 6 or 7, characterized in that: The fields in the source message field configuration table include a first system identifier, a business transaction type, a source message field name, and a data type of a source message field value.

10. The method according to claim 6 or 7, characterized in that: The fields in the target message field configuration table include business transaction type, target message field name and data type of target message field value.

11. The method according to claim 7, characterized in that The primary key is the source message number.

12. A transaction message processing device, characterized in that: include: A transaction message receiving module, used to receive source messages of different types of business transactions initiated by the first system by calling the same transaction service interface, and store the message content of the source message into the transaction message table; The message processing module is used to establish a correspondence between the fields in the current source message to be processed and the target message fields in the transaction message table according to the field mapping relationship obtained from the pre-configured field conversion rules, and to process the field values ​​of the fields in the source message with established correspondence and assign them to the corresponding target message fields according to the field processing rules obtained from the pre-configured field conversion rules; The transaction message assembly module is used to assemble the target message according to the assigned target message fields and send the target message to the second system.

13. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the program, it implements the transaction message processing method according to any one of claims 1 to 11.

14. A machine-readable storage medium having instructions stored thereon, characterized in that: When the instruction is executed by a processor, the processor is configured to execute the transaction message processing method according to any one of claims 1 to 11.

15. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the computer program implements the transaction message processing method according to any one of claims 1 to 11.

Images