Message conversion method and device, equipment, storage medium and program product

Abstract

The invention discloses a message conversion method and device, equipment, a storage medium and a program product, and relates to the technical field of data processing. The method comprises the following steps: acquiring a first analysis result of a first request message sent by a target client, and storing the first analysis result in a request variable data item space in an internal storage space; obtaining a target request message template and first configuration information according to identification information corresponding to the first request message; according to the first configuration information and the request variable data item space, setting the value of each first standard variable field in the target request message template as the value of a first variable field corresponding to the first standard variable field, and obtaining a request message template after the variable fields are instantiated; and setting the value of each first standard constant field in the request message template after instantiating the variable fields as the value of the first standard constant field read from the constant data item space to obtain a converted second request message. According to the method, the message conversion efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a message conversion method, device, equipment, storage medium and program product. Background Art

[0002] In the enterprise treasury management system, the bank accounts of the enterprise are opened in different banks. The multi-bank routing system can manage different bank accounts of the enterprise, and is responsible for distributing the request message sent by the enterprise treasury management system to the corresponding bank front-end system according to the bank to which the bank account belongs. Since the message format required by each bank is different, after receiving the request message, the multi-bank routing system needs to convert the request message according to the message format required by the bank to which the request message is sent and then send it.

[0003] At present, after receiving the request message sent by the enterprise treasury management system, the multi-bank routing system determines the bank to which the request message corresponds, and converts the request message into a message that meets the bank's requirements according to the pre-configured message conversion method of the bank before sending it.

[0004] However, during the above message conversion process, for each bank, its corresponding message conversion method needs to be pre-configured in the multi-line routing system, which requires developers to write message conversion methods for each bank, which is difficult and labor-intensive, resulting in low message conversion efficiency. Summary of the invention

[0005] The present application provides a message conversion method, device, equipment, storage medium and program product, which are used to solve the technical problem of low conversion efficiency when performing message conversion in related technologies.

[0006] In a first aspect, the present application provides a message conversion method, comprising:

[0007] Obtaining a first parsing result of a first request message sent by a target client, and storing the first parsing result in a request variable data item space in an internal storage space; wherein the first parsing result includes each first variable field and a value of the first variable field;

[0008] Acquire a target request message template and first configuration information according to the identification information corresponding to the first request message; wherein the target request message template includes a first standard variable field and a first standard constant field, and the first configuration information is used to indicate a corresponding relationship between the first standard variable field and the first variable field;

[0009] According to the first configuration information and the request variable data item space, the value of each first standard variable field in the target request message template is set to the value of the first variable field corresponding to the first standard variable field, so as to obtain the request message template after instantiating the variable field;

[0010] In the request message template after the instantiated variable field, the value of each first standard constant field is set to the value of the first standard constant field read from the constant data item space, so as to obtain a converted second request message; wherein, the constant data item space is located in the internal storage space.

[0011] In a second aspect, the present application provides a message conversion device, the device comprising:

[0012] A first acquisition module, configured to acquire a first parsing result of a first request message sent by a target client, and store the first parsing result in a request variable data item space in an internal storage space; wherein the first parsing result includes each first variable field and a value of the first variable field;

[0013] a second acquisition module, configured to acquire a target request message template and first configuration information according to identification information corresponding to the first request message; wherein the target request message template includes a first standard variable field and a first standard constant field, and the first configuration information is used to indicate a corresponding relationship between the first standard variable field and the first variable field;

[0014] A first setting module, configured to set the value of each first standard variable field in the target request message template to the value of the first variable field corresponding to the first standard variable field according to the first configuration information and the request variable data item space, so as to obtain the request message template after instantiating the variable field;

[0015] The second setting module is used to set the value of each first standard constant field in the request message template after the instantiated variable field to the value of the first standard constant field read from the constant data item space, so as to obtain a converted second request message; wherein, the constant data item space is located in the internal storage space.

[0016] In a third aspect, the present application also provides an electronic 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, a message conversion method as described in any one of the present applications is implemented.

[0017] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a message conversion method as described in any one of the present applications.

[0018] In a fifth aspect, the present application also provides a computer program product, including a computer program, which, when executed by a processor, implements a message conversion method as described in any one of the present applications.

[0019] The technical solution provided by the present application, on the one hand, realizes the conversion of the first request message through the target request message template, the request variable data item space and the constant data item space, realizes configurable message conversion, and no longer requires developers to write the message conversion method of each bank, reduces the difficulty and workload of message conversion, thereby improving the message conversion efficiency, and at the same time, realizes the rapid access of the interface of the newly connected financial institution. On the other hand, the first parsing result is stored in the request variable data item space in the internal storage space, so that the value of the first variable field can be quickly read, thereby further improving the message conversion efficiency. On the other hand, by setting the constant data item space, and by dividing the fields into two categories of the first standard constant field and the first standard variable field in the target request message template, the content of the constant field does not need to be included in the first request message, and the data volume of the first request message is reduced without affecting the normal operation of the business, thereby saving network transmission resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0021] Figure 1 A schematic diagram of an application scenario of the message conversion method provided in an embodiment of the present application;

[0022] Figure 2 A flowchart of a message conversion method provided in an embodiment of the present application;

[0023] Figure 3 This is a schematic diagram of a first request message in an embodiment of the present application;

[0024] Figure 4 A schematic diagram of a target request message template and first configuration information in an embodiment of the present application;

[0025] Figure 5 This is a schematic diagram of a second request message in an embodiment of the present application;

[0026] Figure 6 A flowchart of another message conversion method provided in an embodiment of the present application;

[0027] Figure 7 A flowchart of another message conversion method provided in an embodiment of the present application;

[0028] Figure 8 A flowchart of another message conversion method provided in an embodiment of the present application;

[0029] Fig. 9 A flowchart of another message conversion method provided in an embodiment of the present application;

[0030] Fig.10 A schematic diagram of an application scenario in an embodiment of the present application;

[0031] Fig.11 A schematic diagram of the structure of a message conversion device provided in an embodiment of the present application;

[0032] Fig.12 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0033] The present application will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present application, rather than to limit the present application. It should also be noted that, for ease of description, only the parts related to the present application, rather than all structures, are shown in the accompanying drawings.

[0034] It should be noted that similar numbers and letters represent similar items in the following figures. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. At the same time, in the description of this application, the terms "first" and "second" are only used to distinguish the description and cannot be understood as indicating or implying relative importance. The acquisition, storage, use, and processing of data in the technical solution of this application comply with the relevant provisions of national laws and regulations. It should be noted that in the embodiments of this application, certain software, components, models, and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. The 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.

[0035] Figure 1 A schematic diagram of an application scenario of the message conversion method provided in the embodiment of the present application. Figure 1 As shown, the message conversion method provided in this embodiment can be applied to Figure 1The electronic device 11 shown in the figure. The electronic device 11 in this embodiment can be a computer device, a server, etc. The electronic device 11 in this embodiment is arranged between the client 12 and the server 13 of the financial institution. The server 13 of the financial institution in this embodiment refers to the servers of at least two financial institutions. Figure 1 The number of financial institutions is 3 for illustrative purposes. The client in this embodiment can be installed in a user terminal such as a mobile phone, a personal computer device, a tablet computer or a vehicle-mounted terminal. The electronic device 11 is installed with multiple routing systems. Optionally, a public cloud external connection adaptation platform can also be provided between the electronic device 11 and the client 12. Front-end systems of various financial institutions can also be provided between the electronic device 11 and the server 13 of the financial institution. The front-end system of the financial institution can be deployed on the same machine as the electronic device 11, or it can be deployed separately. The user can generate a request message to the corresponding financial institution through the client 12. After the public cloud external connection adaptation platform performs security processing on the request message, it sends the processed request message to the electronic device 11. After receiving the request message, the electronic device 11 needs to convert the request message according to the message format required by the financial institution to which the processed request message is sent, and then send it. The electronic device 11 in this embodiment can convert the request message based on the request message template, the request variable data item space and the constant data item space by executing the message conversion method provided in this embodiment, thereby realizing configurable message conversion. It is no longer necessary for developers to write message conversion methods for each bank, which reduces the difficulty and workload of message conversion, thereby improving the efficiency of message conversion.

[0036] The message conversion method of the present application is further described in detail below through several specific embodiments.

[0037] Figure 2 The present invention provides a flow chart of a message conversion method. The method can be executed by a message conversion device, which can be implemented in the form of hardware and / or software, and can be configured in an electronic device. The electronic device here can be Figure 1 The first electronic device in the embodiment. Exemplarily, the electronic device in this embodiment may be a server. Figure 2 As shown, the message conversion method provided in this embodiment includes the following steps.

[0038] Step 201: Obtain a first parsing result of a first request message sent by a target client, and store the first parsing result in a request variable data item space in an internal storage space.

[0039] The first parsing result includes each first variable field and the value of the first variable field.

[0040] The target client in this embodiment refers to a client that needs to request a message. Optionally, the client in this embodiment may be each client of an enterprise treasury management system in an enterprise. The first request message in this embodiment refers to a request message sent to a server of a target financial institution. The financial institution in this embodiment may be a bank, a securities company, or an insurance company, etc.

[0041] The user can access the client through a browser in the user terminal or an application installed in the user device. The first request message in this embodiment is used to implement business interaction with the server of the target financial institution. Exemplarily, the first request message in this embodiment is used to obtain business-related data from the server of the target financial institution.

[0042] In this embodiment, in order to realize message conversion, the first parsing result of the first request message is first obtained. In order to improve the efficiency of subsequent message conversion, the first parsing result is stored in the request variable data item space in the internal storage space. The first parsing result in this embodiment includes each first variable field and the value of the first variable field. The variable field in this embodiment refers to a field whose corresponding value will change.

[0043] Figure 3 FIG. 1 is a schematic diagram of a first request message in an embodiment of the present application. Figure 3 As shown, it is assumed that the first request message has three first variable fields, and the three first variable fields and their values ​​are: the first variable field 311, whose value is 312, the first variable field 321, whose value is 322, and the first variable field 331, whose value is 332.

[0044] The internal storage space in this embodiment may be a memory, cache, etc. in an electronic device. The request variable data item space in this embodiment refers to a storage space in the internal storage space that stores the first parsing result. Since the reading of data in the internal storage space is fast, therefore, in this embodiment, the first parsing result is stored in the internal storage space, which can facilitate the rapid reading of the value of the first variable field when step 203 is subsequently executed, thereby improving the efficiency of message conversion.

[0045] Optionally, in order to further improve the flexibility of the client's message configuration, before step 201, the message conversion method provided in this embodiment also includes the following steps: determining the variable fields included in the request message of each client according to the data items and the message content requirement information of each client, wherein the data items are a collection of variable fields; determining the request message configuration information of the client according to the variable fields included in the request message of the client and the message format requirement information of the client, wherein the message formats indicated in the message format requirement information of at least two clients are different; sending the request message configuration information to the client, so that the client generates a request message according to the request message configuration information when sending the request message. This implementation method can be implemented in the same transaction scenario, determining the request message configuration information of the client according to the client's requirements, configuring the required request message configuration information for different clients, and improving the flexibility of configuring the request message.

[0046] The message content requirement information of the client is used to indicate the variable fields included in the request message of the client. The message format in this embodiment can be: Extensible Markup Language (XML) or JavaScript Object Notation (JSON).

[0047] Step 202: Acquire a target request message template and first configuration information according to identification information corresponding to the first request message.

[0048] The target request message template includes a first standard variable field and a first standard constant field. The first configuration information is used to indicate a corresponding relationship between the first standard variable field and the first variable field.

[0049] The identification information corresponding to the first request message in this embodiment is used to indicate the server of the target financial institution to which the first request message needs to be sent. Optionally, the identification information corresponding to the first request message in this embodiment may include: a financial institution code and / or a transaction code.

[0050] When obtaining the target request message template and the first configuration information, the target request message template and the first configuration information matching the first request message may be obtained from a plurality of pre-stored message templates and their configuration information according to the identification information corresponding to the first request message.

[0051] The target request message template in this embodiment includes two types of fields: a first standard variable field and a first standard constant field. The standard variable field in this embodiment refers to a variable field that complies with the regulations of the target financial institution. The constant field in this embodiment refers to a field with a corresponding fixed value, that is, for the same financial institution, the value of the constant field in the converted request message sent by different clients is the same. Exemplarily, the constant field may include at least one of the following: the Internet Protocol (IP) address, port, data exchange class and other required parameters of the financial institution server.

[0052] Figure 4 Schematic diagram of a target request message template and first configuration information in an embodiment of the present application. Figure 4 As shown, it is assumed that the target request message template includes 4 fields, including 3 first standard constant fields and 1 first standard variable field. The 4 fields are: first standard variable field 411, first standard variable field 421, first standard variable field 431 and first standard constant field 441. The value corresponding to each field in the target request message template is vacant or a default value. Figure 4 The following example uses the missing values ​​of each field as an example. Figure 4 As shown, the first configuration information indicates the correspondence between the first standard variable field and the first variable field: the first standard variable field 411 corresponds to the first variable field 331, the first standard variable field 421 corresponds to the first variable field 321, and the first standard variable field 431 corresponds to the first variable field 311.

[0053] Optionally, before step 203, the request message template may be initialized. The initialization process of the request message template includes the following procedures: loading the configuration information of each request message template; loading the request message template files of each financial institution by polling; initializing the request message template file and instantiating it as a template of a template engine (e.g., freemarker). Exemplarily, the file name of the request message template file may be "transaction name-req.ftl". After the request message template is initialized, it is convenient to quickly determine the target request message template in step 202, further improving the message conversion efficiency.

[0054] Step 203: according to the first configuration information and the request variable data item space, the value of each first standard variable field in the target request message template is set to the value of the first variable field corresponding to the first standard variable field, and the request message template after instantiating the variable field is obtained.

[0055] Step 203 is used to implement dynamic mapping of the first standard variable field in the target request message template, that is, instantiate the variable field of the target request message template. The implementation process is to fill in the value of the standard variable field in the target request message template.

[0056] For each first standard variable field in the target request message template, based on the first configuration information, the value of the first variable field corresponding to the first standard variable field is read from the request variable data item space, and the value is used as the value of the first standard variable field.

[0057] Step 204: In the request message template after the instantiation of the variable field, the value of each first standard constant field is set to the value of the first standard constant field read from the constant data item space, to obtain a converted second request message.

[0058] Among them, the constant data item space is located in the internal storage space.

[0059] After the variable field is instantiated, the value of the standard constant field in the request message template has not been written yet, so in step 204, the standard constant field is instantiated.

[0060] In this embodiment, a constant data item space is pre-set. The constant data item space includes standard constant fields and their values. In step 204, the value of each first standard constant field in the request message template after the instantiated variable field is set to the value of the first standard constant field read from the constant data item space, and the converted second request message is obtained.

[0061] Figure 5 Schematic diagram of a second request message in an embodiment of the present application. Figure 4 The value of the first standard constant field in is 442. Figure 3 as well as Figure 4 On the basis of Figure 5 As shown, the second request message after converting the first request message may include: a first standard variable field 411 and its value 332, a first standard variable field 421 and its value 322, a first standard variable field 431 and its value 312, and a first standard constant field 441 and its value 442.

[0062] In one implementation, in this embodiment, after obtaining the second request message, the following operation may be performed: sending the second request message to a target server, wherein the target server is a server in a target financial institution determined according to the identification information corresponding to the first request message.

[0063] In another implementation, in order to improve the security during the message transmission process, in this embodiment, after obtaining the second request message, the following operations may be performed: encrypting the second request message to obtain an encrypted second request message; sending the encrypted second request message to a target server at a first moment, wherein the target server is a server in a target financial institution determined according to the identification information corresponding to the first request message; sending a key for decrypting the encrypted second request message to the target server at a second moment. The first moment is different from the second moment.

[0064] In this implementation, the time of sending the encrypted second request message is different from the time of sending the key for decrypting the encrypted second request message, which avoids the possibility of the second request message being tampered with, improves the security of the second request message transmission, and further improves the security of business operations.

[0065] It should be noted that in the above two implementations, in the scenario where a financial institution front-end system is set up, the target server refers to the server where the front-end system of the target financial institution is located. The front-end system in this embodiment refers to a system that can call the interface of the financial institution. The front-end system can ensure the security of the interface call of the financial institution.

[0066] In the related art, in the development process of a new access financial institution interface in a multi-bank routing system, developers are required to connect to the corresponding bank's interface, including request message assembly, request method, message encryption and decryption, response message parsing, etc. However, the message conversion method provided in this embodiment only needs to configure the request message template and corresponding configuration information when a new access financial institution interface is connected, which simplifies the development process of the new access financial institution interface and improves the rapid access capability of the new financial institution interface.

[0067] Furthermore, after a preset time after sending the second request message, the first parsing result in the request variable data item space can be deleted to release storage space and save storage resources. In order to facilitate the use of the constant data item space in the subsequent message conversion process, the value in the constant data item space in this embodiment is always retained without deletion.

[0068] The message conversion method provided in this embodiment, on the one hand, realizes the conversion of the first request message through the target request message template, the request variable data item space and the constant data item space, realizes configurable message conversion, and no longer requires developers to write the message conversion methods of each bank, reduces the difficulty and workload of message conversion, thereby improving the message conversion efficiency, and at the same time, realizes the rapid access of the interface of the newly connected financial institution. On the other hand, the first parsing result is stored in the request variable data item space in the internal storage space, so that the value of the first variable field can be quickly read, thereby further improving the message conversion efficiency. On the other hand, by setting the constant data item space, and by dividing the fields into the first standard constant field and the first standard variable field in the target request message template, the content of the constant field does not need to be included in the first request message, and the data volume of the first request message is reduced without affecting the normal operation of the business, thereby saving network transmission resources.

[0069] Figure 6 A flow chart of another message conversion method provided in an embodiment of the present application. Figure 2 Based on the illustrated embodiment and various optional implementations, a detailed description is given of how to obtain the first parsing result of the first request message. Figure 6 As shown, the message conversion method provided in this embodiment includes the following steps.

[0070] Step 601: Determine the message format of the first request message.

[0071] In one implementation, step 601 is implemented by the following steps: determining the identifier of the target client according to the source address of the first request message; determining the message format corresponding to the identifier of the target client according to the mapping relationship between the identifier of the client and the message format; and determining the message format corresponding to the identifier of the target client as the message format of the first request message. Table 1 shows the mapping relationship between the identifier of the client and the message format. This implementation can efficiently and accurately determine the message format of the first request message.

[0072] Table 1 Mapping relationship between client identifier and message format

[0073] Client ID Message Format Logo 61 JSON Logo 62 XML Logo 63 XML

[0074] In another implementation, step 601 is implemented by the following steps: inputting the first request message into a pre-trained message format recognition model to obtain the message format of the first request message output by the message format recognition model. The message format recognition model is a model obtained by training based on the training request message. This implementation method realizes the recognition of the message format of the request message by the message format recognition model trained based on big data, thereby improving the accuracy of the recognized message format.

[0075] Step 602: According to the message format of the first request message, a message parsing tool for the first request message is obtained.

[0076] The message parsing tool in this embodiment is a pre-packaged program for parsing the message format of the request message. Different message formats correspond to different message parsing tools: XML format corresponds to XML parsing tool, and JSON format corresponds to JSON parsing tool.

[0077] Step 603: Parse the first request message through the message parsing tool of the first request message to obtain a first parsing result of the first request message, and store the first parsing result in the request variable data item space in the internal storage space.

[0078] The first parsing result includes each first variable field and the value of the first variable field.

[0079] In this embodiment, the first request message can be parsed by a message parsing tool of the first request message, thereby improving the efficiency of message parsing and further improving the message conversion efficiency.

[0080] Step 604: Obtain a target request message template and first configuration information according to the identification information corresponding to the first request message.

[0081] The target request message template includes a first standard variable field and a first standard constant field. The first configuration information is used to indicate a corresponding relationship between the first standard variable field and the first variable field.

[0082] Step 605: According to the first configuration information and the request variable data item space, the value of each first standard variable field in the target request message template is set to the value of the first variable field corresponding to the first standard variable field, and the request message template after instantiating the variable field is obtained.

[0083] Step 606: In the request message template after instantiating the variable field, the value of each first standard constant field is set to the value of the first standard constant field read from the constant data item space, to obtain a converted second request message.

[0084] Among them, the constant data item space is located in the internal storage space.

[0085] The implementation process and technical principle of step 604 and step 202, step 605 and step 203, and step 606 and step 204 are similar, and will not be repeated here.

[0086] The message conversion method provided in this embodiment obtains a message parsing tool for the first request message according to the message format of the first request message, and parses the first request message through the message parsing tool to obtain a first parsing result of the first request message, thereby improving the efficiency of message parsing and further improving the message conversion efficiency.

[0087] Figure 7 A flowchart of another message conversion method provided in an embodiment of the present application. Figure 2 and Figure 6 Based on the illustrated embodiment and various optional implementations, a detailed description is given of how to obtain the target request message template and the implementation of the first configuration information. Figure 7 As shown, the message conversion method provided in this embodiment includes the following steps.

[0088] Step 701: Obtain a first parsing result of a first request message sent by a target client, and store the first parsing result in a request variable data item space in an internal storage space.

[0089] The first parsing result includes each first variable field and the value of the first variable field.

[0090] The implementation method and technical principle of step 701 are similar to those of step 201 and will not be repeated here.

[0091] In this embodiment, the request message template is an encrypted and stored message template, and the first configuration information is encrypted and stored information, so as to avoid attacks on the message template and the first configuration information, improve the security of the request message conversion process, and ensure information security.

[0092] Step 702: Acquire verification information of the first request message sent by the target client.

[0093] In this embodiment, the verification information of the first request message is used to verify the security of the first request message. Exemplarily, the verification information of the first request message can be a cyclic redundancy check (CRC) code of the first request message or a hash value of the first request message.

[0094] Step 703: Verify the security of the first request message according to the verification information of the first request message, and obtain a security verification result.

[0095] Optionally, the security of the first request message may be verified based on the verification information of the first request message and the pre-stored or acquired standard verification information: if the verification information of the first request message is consistent with the standard verification information, the security verification result is verification passed; if the verification information of the first request message is inconsistent with the standard verification information, the security verification result is verification failed. The standard verification information refers to the verification information corresponding to the correctly transmitted first request message.

[0096] Step 704: If the security verification result is that the verification is passed, the identification information corresponding to the first request message is obtained.

[0097] In this embodiment, the subsequent steps are performed only when it is determined that the security verification result of the first request message is passed, thereby improving the security of message conversion and the service success rate.

[0098] Optionally, if the security verification result is verification failure, a message sending failure information is fed back to the target client.

[0099] Optionally, the identification information corresponding to the first request message in this embodiment includes: a financial institution code and / or a transaction code. In one implementation, in step 704, the identification information corresponding to the first request message can be determined based on the values ​​of some of the first variable fields in each first variable field. In this implementation, the financial institution code and / or the transaction code are included in the first request message. In another implementation, in step 704, the identification information corresponding to the first request message can be determined based on the target client. In this implementation, the identification information corresponding to the first request message can be determined based on the target client that sends the first request message and the mapping relationship between the client and the identification information. These two implementations can accurately determine the identification information corresponding to the first request message, thereby improving the success rate of message conversion.

[0100] Step 705: According to the identification information corresponding to the first request message, the ciphertext of the target request message template and the ciphertext of the first configuration information are obtained.

[0101] In this embodiment, there is no restriction on the encryption method of the target request message template and the first configuration information.

[0102] Step 706: Decrypt the ciphertext of the target request message template to obtain the target request message template.

[0103] Step 707: Decrypt the ciphertext of the first configuration information to obtain the first configuration information.

[0104] The target request message template includes a first standard variable field and a first standard constant field. The first configuration information is used to indicate a corresponding relationship between the first standard variable field and the first variable field.

[0105] In step 706, the ciphertext of the target request message template is decrypted to obtain the target request message template. In step 707, the ciphertext of the first configuration information is decrypted to obtain the first configuration information.

[0106] Step 708: According to the first configuration information and the request variable data item space, the value of each first standard variable field in the target request message template is set to the value of the first variable field corresponding to the first standard variable field, and the request message template after instantiating the variable field is obtained.

[0107] Step 709: In the request message template after instantiating the variable field, the value of each first standard constant field is set to the value of the first standard constant field read from the constant data item space, to obtain a converted second request message.

[0108] Among them, the constant data item space is located in the internal storage space.

[0109] The implementation methods and technical principles of step 708 and step 203, and step 709 and step 204 are similar, and will not be repeated here.

[0110] The message conversion method provided in this embodiment, on the one hand, verifies the security of the first request message according to the verification information of the first request message by obtaining the verification information of the first request message sent by the target client, obtains the security verification result, and if the security verification result is a passed verification, obtains the identification information corresponding to the first request message, so that the subsequent steps are executed only when it is determined that the security verification result of the first request message is a passed verification, thereby improving the security of message conversion and the success rate of the service. On the other hand, the request message template is a message template stored after encryption, and the first configuration information is information stored after encryption, so as to avoid attacks on the message template and the first configuration information, thereby improving the security of the request message conversion process and ensuring information security.

[0111] Figure 8 A flowchart of another message conversion method provided in an embodiment of the present application. Figure 2 , Figure 6 , Figure 7 Based on the illustrated embodiment and various optional implementations, other steps included in the message conversion method provided in this embodiment are described in detail. Figure 8 As shown, the message conversion method provided in this embodiment includes the following steps.

[0112] Step 801: Obtain a first parsing result of a first request message sent by a target client, and store the first parsing result in a request variable data item space in an internal storage space.

[0113] The first parsing result includes each first variable field and the value of the first variable field.

[0114] Step 802: Acquire a target request message template and first configuration information according to identification information corresponding to the first request message.

[0115] The target request message template includes a first standard variable field and a first standard constant field. The first configuration information is used to indicate a corresponding relationship between the first standard variable field and the first variable field.

[0116] The implementation process and technical principle of step 801 and step 201, and step 802 and step 202 are similar, and will not be repeated here.

[0117] Step 803: Compare the number of the first variable field with the number of the first standard variable field.

[0118] In this embodiment, in order to avoid conversion failure, the number of first variable fields is first compared with the number of first standard variable fields to avoid the scenario where the number of first variable fields is smaller than the number of first standard variable fields, and some first standard variable fields in the target request message template cannot read corresponding values, resulting in conversion failure.

[0119] Step 804: If the number of the first variable fields is greater than or equal to the number of the first standard variable fields, determine to execute step 806.

[0120] It can be understood that a successful conversion can be achieved in step 804 .

[0121] Step 805: If the number of the first variable fields is less than the number of the first standard variable fields, processing is performed according to a processing strategy corresponding to the target client.

[0122] In one implementation, if the number of the first variable fields is less than the number of the first standard variable fields, a message sending failure message is sent to the target client.

[0123] In another implementation, step 805 includes the following steps 8051 to 8055.

[0124] Step 8051: Determine the vacant first standard variable fields in the first standard variable fields.

[0125] The missing first standard variable field is a field whose corresponding value cannot be obtained from the request variable data item space.

[0126] Step 8052: According to the first configuration information, determine the vacant first variable field corresponding to the vacant first standard variable field.

[0127] Step 8053: Send a data acquisition message to the target client.

[0128] The data acquisition message is used to instruct the target client to feedback the value of the missing first variable field.

[0129] Step 8054: If a data feedback message is received from the target client according to the data acquisition message, the first variable field and the corresponding value in the data feedback message are obtained, and the first variable field and the corresponding value in the data feedback message are stored in the request variable data item space, and the step of executing step 803 is returned.

[0130] In step 8054, a data feedback message may be obtained from the target client, thereby obtaining the first variable field and the corresponding value in the data feedback message, and storing the first variable field and the corresponding value in the data feedback message in the request variable data item space. At this time, the process returns to step 803.

[0131] Step 8055: If the data feedback message sent by the target client according to the data acquisition message is not received within the preset time, a message sending failure message is sent to the target client.

[0132] In step 8055, if the target client does not provide feedback based on the data acquisition message within the preset time period, it means that the message conversion process cannot be successful, and a message sending failure information is sent to the target client.

[0133] Step 806: According to the first configuration information and the request variable data item space, the value of each first standard variable field in the target request message template is set to the value of the first variable field corresponding to the first standard variable field, and the request message template after instantiating the variable field is obtained.

[0134] Step 807: In the request message template after the instantiation of the variable field, the value of each first standard constant field is set to the value of the first standard constant field read from the constant data item space, to obtain a converted second request message.

[0135] Among them, the constant data item space is located in the internal storage space.

[0136] The implementation process and technical principle of step 806 and step 203, and step 807 and step 204 are similar, and will not be repeated here.

[0137] The message conversion method provided in this embodiment compares the number of first variable fields with the number of first standard variable fields. If the number of first variable fields is greater than or equal to the number of first standard variable fields, it determines to execute the step of instantiating the target request message template. If the number of first variable fields is less than the number of first standard variable fields, it processes according to the processing strategy corresponding to the target client. It compares the number of first variable fields with the number of first standard variable fields first to avoid the conversion failure caused by the inability to read the corresponding values ​​of some first standard variable fields in the target request message template in the scenario where the number of first variable fields is less than the number of first standard variable fields, thereby improving the message conversion success rate.

[0138] Fig. 9 A flowchart of another message conversion method provided in an embodiment of the present application. Figure 2 , Figure 6 , Figure 7 , Figure 8 Based on the illustrated embodiment and various optional implementations, the steps of converting the response message fed back by the target server are described in detail. For simplicity, only the steps included in the message conversion method are described in this embodiment. Fig. 9 As shown, the message conversion method provided in this embodiment also includes the following steps.

[0139] Step 901: Send a second request message to a target server, and receive a first response message sent by the target server according to the second request message.

[0140] The target server is a server in a target financial institution determined according to identification information corresponding to the first request message.

[0141] In this embodiment, after the second request message is obtained through conversion, the second request message is sent to the target server. Exemplarily, it can be sent through the Internet or through a dedicated line.

[0142] Optionally, in a scenario where a financial institution front-end processor system is provided between the multi-bank routing system and the server of the financial institution, in step 901, a second request message is sent to a target server through the front-end processor system of the target financial institution.

[0143] After receiving the second request message, the target server parses the second request message, determines the response content according to the parsing result, encapsulates the response content into a first response message, and directly sends it to the multi-line routing system or sends it through the front-end system.

[0144] Step 902: Obtain a second parsing result of the first response message, and store the second parsing result in a response variable data item space in the internal storage space.

[0145] The second parsing result includes each second standard variable field and the value of the second standard variable field.

[0146] The implementation process and technical principle of step 902 are similar to those of step 201, and will not be repeated here. The difference is that the second parsing result in step 902 includes the second standard variable field and its corresponding value. The implementation method of the response variable data item space is similar to that of the request variable data item space.

[0147] Step 903: Obtain a target response message template and second configuration information according to the identification information corresponding to the first response message.

[0148] The target response message template includes a second variable field, and the second configuration information is used to indicate the correspondence between the second standard variable field and the second variable field.

[0149] The implementation process and technical principle of step 903 are similar to those of step 202, and will not be repeated here. The difference is that what is obtained in step 903 is the target response message template.

[0150] Optionally, the response message template may be initialized before step 903. Exemplarily, the file name of the response message template file may be "transaction name-rsp.ftl".

[0151] Step 904: according to the second configuration information and the response variable data item space, the value of each second variable field in the target response message template is set to the value of the second standard variable field corresponding to the second variable field, to obtain a converted second response message.

[0152] The implementation process and technical principle of step 904 are similar to those of step 203, and will not be repeated here. The difference is that in step 904, the value of each second variable field in the target response message template is set to the value of the second standard variable field corresponding to the second variable field.

[0153] Step 905: Send a second response message to the target client.

[0154] Optionally, the message conversion method provided in this embodiment further includes the following steps: obtaining a third parsing result of the first response message, wherein the third parsing result includes a second standard constant field and a value of the second standard constant field; updating the fields and corresponding values ​​in the second standard constant field that are not stored in the constant data item space to the constant data item space. This implementation method realizes updating the constant data item space according to the standard constant field and the value of the standard constant field in the response message, so as to use the data in the constant data item space in the subsequent message conversion process, further improving the message conversion efficiency.

[0155] Fig.10 Schematic diagram of the application scenario in the embodiment of the present application. Fig.10 As shown, in this embodiment, the message conversion process includes a request message conversion process and a response message conversion process.

[0156] The conversion process of the request message includes the following process: the target client A sends a first request message; the multi-line routing system obtains a first parsing result of the first request message and stores it in the request variable data item space; according to the identification information corresponding to the first request message, the target request message template and the first configuration information are obtained; steps 203 and 204 are executed to obtain a second request message, and the second request message is sent to the target server.

[0157] The conversion process of the response message includes the following process: after the target server receives the second request message, it generates and sends a first response message; the multi-line routing system obtains the second parsing result of the first response message and stores it in the response variable data item space; according to the identification information corresponding to the first response message, the target response message template and the second configuration information are obtained; step 904 is executed to obtain the second response message, and the second response message is sent to the target client A.

[0158] The message conversion method provided in this embodiment, on the one hand, realizes the conversion process of the request message and the conversion process of the response message, thereby improving the communication efficiency between the client and the server of the financial institution. On the other hand, it realizes updating the constant data item space according to the standard constant field and the value of the standard constant field in the response message, so as to facilitate the use of the data in the constant data item space in the subsequent message conversion process, thereby further improving the message conversion efficiency.

[0159] Fig.11 A schematic diagram of the structure of a message conversion device provided in an embodiment of the present application. Fig.11 As shown, the message conversion device provided in this embodiment includes the following modules: a first acquisition module 111 , a second acquisition module 112 , a first setting module 113 and a second setting module 114 .

[0160] The first acquisition module 111 is used to acquire a first parsing result of a first request message sent by a target client, and store the first parsing result in a request variable data item space in an internal storage space.

[0161] The first parsing result includes each first variable field and the value of the first variable field.

[0162] The second acquisition module 112 is used to acquire a target request message template and first configuration information according to the identification information corresponding to the first request message.

[0163] The target request message template includes a first standard variable field and a first standard constant field. The first configuration information is used to indicate a corresponding relationship between the first standard variable field and the first variable field.

[0164] The first setting module 113 is used to set the value of each first standard variable field in the target request message template to the value of the first variable field corresponding to the first standard variable field according to the first configuration information and the request variable data item space, so as to obtain the request message template after instantiating the variable field.

[0165] The second setting module 114 is used to set the value of each first standard constant field in the request message template after the instantiated variable field to the value of the first standard constant field read from the constant data item space to obtain a converted second request message.

[0166] Wherein, the constant data item space is located in the internal storage space.

[0167] In one embodiment, the device further includes: a first determining module, a second determining module and a sending module.

[0168] The first determination module is used to determine the variable fields included in the request message of each client according to the data items and the message content requirement information of each client.

[0169] The data item is a set of variable fields.

[0170] The second determination module is used to determine the request message configuration information of the client according to the variable field included in the request message of the client and the message format requirement information of the client.

[0171] The message formats indicated in the message format requirement information of at least two clients are different.

[0172] The sending module is used to send the request message configuration information to the client, so that the client generates a request message according to the request message configuration information when sending the request message.

[0173] In one embodiment, the device further includes: a third determining module and a third acquiring module.

[0174] The third determining module is used to determine the message format of the first request message.

[0175] The third acquisition module is used to acquire a message parsing tool of the first request message according to the message format of the first request message.

[0176] In terms of obtaining the first parsing result of the first request message sent by the target client, the first obtaining module 111 is specifically used to: parse the first request message through a message parsing tool of the first request message to obtain the first parsing result of the first request message.

[0177] In one embodiment, the third determination module is specifically used to: determine the identifier of the target client based on the source address of the first request message; determine the message format corresponding to the identifier of the target client based on the mapping relationship between the client identifier and the message format; and determine the message format corresponding to the identifier of the target client as the message format of the first request message.

[0178] In one embodiment, the third determination module is specifically used to: input the first request message into a pre-trained message format recognition model to obtain the message format of the first request message output by the message format recognition model. The message format recognition model is a model trained according to a training request message.

[0179] In one embodiment, the request message template is a message template stored after being encrypted, and the first configuration information is information stored after being encrypted. The device further includes: a fourth acquisition module and a security verification module.

[0180] The fourth acquisition module is used to obtain verification information of the first request message sent by the target client.

[0181] A security verification module is used to verify the security of the first request message according to the verification information of the first request message and obtain a security verification result.

[0182] The second acquisition module 112 is specifically used for: if the security verification result is verification passed, obtaining the identification information corresponding to the first request message; obtaining the ciphertext of the target request message template and the ciphertext of the first configuration information according to the identification information corresponding to the first request message; decrypting the ciphertext of the target request message template to obtain the target request message template; decrypting the ciphertext of the first configuration information to obtain the first configuration information.

[0183] In one embodiment, the identification information corresponding to the first request message includes: a financial institution code and / or a transaction code. In the aspect of obtaining the identification information corresponding to the first request message, the second obtaining module 112 is specifically used to: determine the identification information corresponding to the first request message according to the values ​​of some of the first variable fields in the first variable fields; or determine the identification information corresponding to the first request message according to the target client.

[0184] In one embodiment, the device further includes: a comparison module, a fourth determination module and a processing module.

[0185] A comparison module is used to compare the number of the first variable field with the number of the first standard variable field.

[0186] The fourth determining module is used to determine to execute the steps executed by the first setting module 113 if the number of the first variable fields is greater than or equal to the number of the first standard variable fields.

[0187] A processing module is used to perform processing according to a processing strategy corresponding to the target client if the number of the first variable fields is less than the number of the first standard variable fields.

[0188] In one embodiment, the processing module is specifically used to: determine a vacant first standard variable field in the first standard variable field, wherein the vacant first standard variable field is a field whose corresponding value cannot be obtained from the request variable data item space; determine a vacant first variable field corresponding to the vacant first standard variable field according to the first configuration information; send a data acquisition message to the target client, wherein the data acquisition message is used to instruct the target client to feedback the value of the vacant first variable field; if a data feedback message sent by the target client according to the data acquisition message is received, then obtain the first variable field and the corresponding value in the data feedback message, and store the first variable field and the corresponding value in the data feedback message in the request variable data item space, and return to execute the steps executed by the comparison module; if the data feedback message sent by the target client according to the data acquisition message is not received within a preset time length, then send a message sending failure information to the target client.

[0189] In one embodiment, the device further includes an encryption module. The encryption module is used to encrypt the second request message to obtain an encrypted second request message. The sending module is also used to send the encrypted second request message to a target server at a first moment, wherein the target server is a server in a target financial institution determined according to identification information corresponding to the first request message. The sending module is also used to send a key for decrypting the encrypted second request message to the target server at a second moment. The first moment is different from the second moment.

[0190] In one embodiment, the sending module is further used to send the second request message to the target server and receive a first response message sent by the target server according to the second request message. The target server is a server in a target financial institution determined according to the identification information corresponding to the first request message. The device also includes a fifth acquisition module, a sixth acquisition module and a third setting module.

[0191] The fifth acquisition module is used to acquire a second parsing result of the first response message, and store the second parsing result in the response variable data item space in the internal storage space, wherein the second parsing result includes each second standard variable field and the value of the second standard variable field.

[0192] The sixth acquisition module is used to acquire a target response message template and second configuration information according to the identification information corresponding to the first response message.

[0193] The target response message template includes a second variable field, and the second configuration information is used to indicate the correspondence between the second standard variable field and the second variable field.

[0194] A third setting module is used to set the value of each second variable field in the target response message template to the value of the second standard variable field corresponding to the second variable field according to the second configuration information and the response variable data item space, so as to obtain a converted second response message.

[0195] The sending module is also used to send the second response message to the target client.

[0196] In one embodiment, the device further includes a seventh acquisition module and an update module.

[0197] The seventh acquisition module is used to obtain a third parsing result of the first response message, wherein the third parsing result includes a second standard constant field and a value of the second standard constant field.

[0198] An updating module is used to update the fields in the second standard constant field that are not stored in the constant data item space and the corresponding values ​​into the constant data item space.

[0199] The message conversion device provided in the embodiment of the present application can be used to execute the technical solution of the message conversion method in the above embodiment. Its implementation principle and technical effect are similar and will not be repeated here.

[0200] It should be noted that it should be understood that the division of the various modules of the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. And these modules can all be implemented in the form of software called by processing elements; they can also be all implemented in the form of hardware; some modules can also be implemented in the form of software called by processing elements, and some modules can be implemented in the form of hardware. For example, the first acquisition module 111, the second acquisition module 112, the first setting module 113 and the second setting module 114 can be separately established processing elements, or they can be integrated in a chip of the above device. In addition, they can also be stored in the memory of the above device in the form of program code, and called and executed by a processing element of the above device. The functions of the first acquisition module 111, the second acquisition module 112, the first setting module 113 and the second setting module 114. The implementation of other modules is similar. In addition, all or part of these modules can be integrated together, or they can be implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or instructions in the form of software.

[0201] Fig.12 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Fig.12 As shown, the electronic device may include: a processor 142 and a memory 143.

[0202] The processor 142 executes the computer execution instructions stored in the memory, so that the processor 142 executes the scheme in the above embodiment. The processor 142 can be a general-purpose processor, including a central processing unit CPU, a network processor (network processor, NP), etc.; it can also be a digital signal processor DSP, an application-specific integrated circuit ASIC, a field programmable gate array FPGA or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

[0203] The memory 143 is connected to the processor 142 via a system bus to complete the communication between them. The memory 143 is used to store computer program instructions.

[0204] Optionally, the electronic device may further include a transceiver 141. The transceiver 141 may be configured to receive a first request message. The transceiver 141 may also be configured to send a second request message.

[0205] The system bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The system bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus. The transceiver is used to realize the communication between the message conversion device and other computer devices. The memory may include random access memory (RAM) and may also include non-volatile memory.

[0206] An embodiment of the present application also provides a chip for running instructions, which is used to execute the technical solution of the message conversion method in the above embodiment.

[0207] An embodiment of the present application further provides a computer-readable storage medium, in which computer instructions are stored. When the computer instructions are executed on a computer, the computer executes the technical solution of the message conversion method of the above embodiment.

[0208] An embodiment of the present application also provides a computer program product, including a computer program, which, when executed by a processor, implements a message conversion method as provided in any embodiment of the present application.

[0209] In the process of implementation, the computer program product can be written in one or more programming languages ​​or a combination thereof to perform the computer program code of the present application, and the programming language includes an object-oriented programming language, such as Java, Smalltalk, C++, and also includes a conventional procedural programming language, such as "C" language or similar programming language. The program code can be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on the remote computer, or completely on the remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (for example, using an Internet service provider to connect through the Internet).

[0210] Note that the above are only preferred embodiments of the present application and the technical principles used. Those skilled in the art will understand that the present application is not limited to the specific embodiments herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present application. Therefore, although the present application is described in more detail through the above embodiments, the present application is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present application, and the scope of the present application is determined by the scope of the appended claims.

Claims

1. A message conversion method, characterized in that: include: Obtaining a first parsing result of a first request message sent by a target client, and storing the first parsing result in a request variable data item space in an internal storage space; wherein the first parsing result includes each first variable field and a value of the first variable field; Acquire a target request message template and first configuration information according to the identification information corresponding to the first request message; wherein the target request message template includes a first standard variable field and a first standard constant field, and the first configuration information is used to indicate a corresponding relationship between the first standard variable field and the first variable field; According to the first configuration information and the request variable data item space, the value of each first standard variable field in the target request message template is set to the value of the first variable field corresponding to the first standard variable field, so as to obtain the request message template after instantiating the variable field; In the request message template after the instantiated variable field, the value of each first standard constant field is set to the value of the first standard constant field read from the constant data item space, so as to obtain a converted second request message; wherein, the constant data item space is located in the internal storage space.

2. The method according to claim 1, characterized in that Before obtaining the first parsing result of the first request message sent by the target client, the method further includes: Determine the variable fields included in the request message of each client according to the data item and the message content requirement information of each client; wherein the data item is a set of variable fields; Determining request message configuration information of the client according to the variable field included in the request message of the client and the message format requirement information of the client; wherein the message formats indicated in the message format requirement information of at least two clients are different; The request message configuration information is sent to the client, so that the client generates a request message according to the request message configuration information when sending the request message.

3. The method according to claim 1, characterized in that Before obtaining the first parsing result of the first request message sent by the target client, the method further includes: Determining a message format of the first request message; Obtaining a message parsing tool for the first request message according to the message format of the first request message; The obtaining of a first parsing result of a first request message sent by a target client includes: The first request message is parsed by using a message parsing tool for the first request message to obtain a first parsing result of the first request message.

4. The method according to claim 3, characterized in that: The determining the message format of the first request message includes: Determining an identifier of the target client according to a source address of the first request message; Determine the message format corresponding to the identifier of the target client according to the mapping relationship between the identifier of the client and the message format; The message format corresponding to the identifier of the target client is determined as the message format of the first request message.

5. The method according to claim 3, characterized in that: The determining the message format of the first request message includes: The first request message is input into a pre-trained message format recognition model to obtain the message format of the first request message output by the message format recognition model; wherein the message format recognition model is a model obtained by training according to training request messages.

6. The method according to any one of claims 1 to 5, characterized in that: The request message template is a message template stored after encryption, and the first configuration information is information stored after encryption; Before acquiring the target request message template and the first configuration information according to the identification information corresponding to the first request message, the method further includes: Obtaining verification information of a first request message sent by the target client; Verifying the security of the first request message according to the verification information of the first request message, and obtaining a security verification result; The acquiring, according to the identification information corresponding to the first request message, a target request message template and first configuration information, includes: If the security verification result is verification passed, obtaining identification information corresponding to the first request message; Acquire the ciphertext of the target request message template and the ciphertext of the first configuration information according to the identification information corresponding to the first request message; Decrypting the ciphertext of the target request message template to obtain the target request message template; The ciphertext of the first configuration information is decrypted to obtain the first configuration information.

7. The method according to claim 6, characterized in that The identification information corresponding to the first request message includes: a financial institution code and / or a transaction code; The obtaining identification information corresponding to the first request message includes: determining identification information corresponding to the first request message according to values ​​of some of the first variable fields in the first variable fields; or, According to the target client, identification information corresponding to the first request message is determined.

8. The method according to any one of claims 1 to 5, characterized in that: Before setting the value of each first standard variable field in the target request message template to the value of the first variable field corresponding to the first standard variable field according to the first configuration information and the request variable data item space to obtain the request message template after instantiating the variable field, the method further includes: comparing the number of the first variable fields to the number of the first standard variable fields; If the number of the first variable fields is greater than or equal to the number of the first standard variable fields, determine to execute the step of "setting the value of each first standard variable field in the target request message template to the value of the first variable field corresponding to the first standard variable field according to the first configuration information and the request variable data item space, to obtain the request message template after instantiating the variable fields"; If the number of the first variable fields is less than the number of the first standard variable fields, processing is performed according to the processing strategy corresponding to the target client.

9. The method according to claim 8, characterized in that If the number of the first variable fields is less than the number of the first standard variable fields, processing is performed according to a processing strategy corresponding to the target client, including: Determine a vacant first standard variable field in the first standard variable field; wherein the vacant first standard variable field is a field whose corresponding value cannot be obtained from the request variable data item space; Determine, according to the first configuration information, a vacant first variable field corresponding to the vacant first standard variable field; Sending a data acquisition message to the target client; wherein the data acquisition message is used to instruct the target client to feedback the value of the missing first variable field; If a data feedback message sent by the target client according to the data acquisition message is received, the first variable field and the corresponding value in the data feedback message are obtained, and the first variable field and the corresponding value in the data feedback message are stored in the request variable data item space, and the step of "comparing the number of the first variable field with the number of the first standard variable field" is returned to be executed; If the data feedback message sent by the target client according to the data acquisition message is not received within the preset time period, message sending failure information is sent to the target client.

10. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: Encrypting the second request message to obtain an encrypted second request message; Sending the encrypted second request message to a target server at a first moment; wherein the target server is a server in a target financial institution determined according to identification information corresponding to the first request message; At a second moment, a key for decrypting the encrypted second request message is sent to the target server; wherein the first moment is different from the second moment.

11. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: Sending the second request message to the target server, and receiving a first response message sent by the target server according to the second request message; wherein the target server is a server in a target financial institution determined according to the identification information corresponding to the first request message; Obtaining a second parsing result of the first response message, and storing the second parsing result in the response variable data item space in the internal storage space; wherein the second parsing result includes each second standard variable field and the value of the second standard variable field; According to the identification information corresponding to the first response message, a target response message template and second configuration information are acquired; wherein the target response message template includes a second variable field, and the second configuration information is used to indicate a correspondence between the second standard variable field and the second variable field; According to the second configuration information and the response variable data item space, the value of each second variable field in the target response message template is set to the value of the second standard variable field corresponding to the second variable field, to obtain a converted second response message; Send the second response message to the target client.

12. The method according to claim 11, characterized in that The method further comprises: Obtain a third parsing result of the first response message; wherein the third parsing result includes a second standard constant field and a value of the second standard constant field; The fields in the second standard constant field that are not stored in the constant data item space and the corresponding values ​​are updated to the constant data item space.

13. A message conversion device, characterized in that: include: A first acquisition module, configured to acquire a first parsing result of a first request message sent by a target client, and store the first parsing result in a request variable data item space in an internal storage space; wherein the first parsing result includes each first variable field and a value of the first variable field; a second acquisition module, configured to acquire a target request message template and first configuration information according to identification information corresponding to the first request message; wherein the target request message template includes a first standard variable field and a first standard constant field, and the first configuration information is used to indicate a corresponding relationship between the first standard variable field and the first variable field; A first setting module, configured to set the value of each first standard variable field in the target request message template to the value of the first variable field corresponding to the first standard variable field according to the first configuration information and the request variable data item space, so as to obtain the request message template after instantiating the variable field; The second setting module is used to set the value of each first standard constant field in the request message template after the instantiated variable field to the value of the first standard constant field read from the constant data item space, so as to obtain a converted second request message; wherein, the constant data item space is located in the internal storage space.

14. An electronic device, characterized in that: The method comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the message conversion method as claimed in any one of claims 1 to 12 when executing the computer program.

15. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the message conversion method according to any one of claims 1 to 12 is implemented.

16. 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 message conversion method according to any one of claims 1 to 12.

Images