CN116600025A

CN116600025A - Configuration-supporting data protocol conversion method, device and storage medium

Info

Publication number: CN116600025A
Application number: CN202310678279.8A
Authority: CN
Inventors: 裴建中; 史晨阳; 裴亚民; 张洁; 徐丹
Original assignee: China Everbright Bank Co Ltd
Current assignee: China Everbright Bank Co Ltd
Priority date: 2023-06-08
Filing date: 2023-06-08
Publication date: 2023-08-15

Abstract

The embodiment of the application provides a data protocol conversion method, a device and a storage medium supporting configuration, wherein the method comprises the following steps: receiving a first message, unpacking a corresponding data field according to a protocol format of the first message, and storing the unpacked data field in a variable pool; operating and reading the corresponding data fields in the variable pool according to the mapping relation of the data fields of different protocols; and packaging the finally read mapping data threshold value into a second message according to the protocol format of the second message. The application solves the technical problems of heavy protocol format conversion, low efficiency and inflexibility of data interaction between systems in the related technology, and achieves the technical effects of strong applicability of protocol format conversion range and high deployment efficiency of later-stage enhancement development.

Description

Configuration-supporting data protocol conversion method, device and storage medium

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a data protocol conversion method and device supporting configuration, a storage medium and an electronic device.

Background

With the development of information technology, various IT (Information Technology ) systems are adopted in enterprises to support daily business activities, and especially the number of IT systems of financial institutions such as banks is more complicated. However, the need for digital transformation, integrated interaction between systems within an enterprise, and even the interaction between internal and external data within an enterprise, is a very popular scenario faced in the process of enterprise IT system construction. However, the application protocols adopted between different systems are difficult to keep uniform, and the low efficiency of format conversion development and maintenance of the application protocols has become a problem in the process of integration between systems. In particular, for the C language, the conventional program based on the data structure cannot meet the flexible and changeable data interaction requirement between the systems. If implemented solely by conventional hard coding, it generally suffers from the following drawbacks:

1. whether a scene is newly added or an existing scene is changed, the code is required to be compiled, packaged, and the change and delivery mode are very heavy as long as the code is changed. This problem is more pronounced if no architecture such as micro-services is employed, and the scope of impact is too large.

2. For integrated class systems such as a front class system and an enterprise bus system, protocol conversion is one of key responsibilities, and each hard coding implementation period is long and the efficiency is low.

3. Coding implementation is highly demanding for developers.

Disclosure of Invention

The embodiment of the application provides a data protocol conversion method and device supporting configuration, a storage medium and an electronic device, which at least solve the technical problems of heavy protocol format conversion, low efficiency and inflexibility of data interaction between systems in the related technology.

According to an embodiment of the present application, there is provided a data protocol conversion method supporting configuration, including the steps of:

receiving a first message, unpacking a corresponding data field according to a protocol format of the first message, and storing the unpacked data field in a variable pool;

operating and reading the corresponding data fields in the variable pool according to the mapping relation of the data fields of different protocols;

and packaging the finally read mapping data threshold value into a second message according to the protocol format of the second message.

In an exemplary embodiment, the mapping relationship of the different protocol data domains is configured through the input interface.

In one exemplary embodiment, the unpacking and packing processes and the variable pool storing, reading and operating processes are set by programming in advance.

In an exemplary embodiment, the rewriting interfaces are respectively set for unpacking pretreatment, unpacking post-treatment, packing pretreatment, packing post-treatment, variable pool storage, reading and operation processes so as to provide a developer with custom function expansion.

In one exemplary embodiment, the memory generation of the variable pool is determined by the type, length, and/or dimension of the corresponding data field.

In an exemplary embodiment, the protocol format of the first message and the protocol format of the second message define the data domain content and the organization structure of the corresponding protocol message in the form of a data dictionary.

According to another embodiment of the present application, there is provided a data protocol conversion apparatus supporting configuration, including:

the unpacking module is used for receiving the first message, unpacking the corresponding data field according to the protocol format of the first message and storing the data field into a variable pool;

the processing module is used for operating and reading the corresponding data fields in the variable pool according to the mapping relation of the data fields of different protocols;

and the packaging module is used for packaging the finally read mapping data domain value into a second message according to the protocol format of the second message.

In an exemplary embodiment, the device further comprises an input module, and the mapping relation of the different protocol data domains is configured through the input module.

According to a further embodiment of the application, there is also provided a computer readable storage medium having stored therein a computer program, wherein the computer program is arranged to perform the steps of any of the method embodiments described above when run.

According to a further embodiment of the application, there is also provided an electronic device comprising a memory having stored therein a computer program and a processor arranged to run the computer program to perform the steps of any of the method embodiments described above.

According to the embodiment of the application, the first message is received, and the corresponding data field is unpacked according to the protocol format of the first message and stored in the variable pool; operating and reading the corresponding data fields in the variable pool according to the mapping relation of the data fields of different protocols; and packaging the finally read mapping data threshold value into a second message according to the protocol format of the second message. Therefore, the technical problems of heavy protocol format conversion, low efficiency and inflexibility of data interaction between systems in the related technology can be solved, and the technical effects of strong applicability of protocol format conversion range and high deployment efficiency of later-stage enhancement development are achieved.

Drawings

Fig. 1 is a hardware configuration block diagram of a computer terminal supporting a configured data protocol conversion method according to an embodiment of the present application;

fig. 2 is a flowchart of a data protocol conversion method supporting configuration according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a data protocol conversion architecture supporting configuration according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a variable pool operation architecture according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a variable pool structure according to an embodiment of the present application;

fig. 6 is a block diagram of a configuration-supporting data protocol conversion apparatus according to an embodiment of the present application.

Detailed Description

Embodiments of the present application will be described in detail below with reference to the accompanying drawings in conjunction with the embodiments.

It should be noted that the terms "first," "second," and the like in the description and the claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order.

The method embodiments provided in the embodiments of the present application may be performed in a mobile terminal, a computer terminal or similar computing device. Taking a computer terminal as an example, fig. 1 is a block diagram of a hardware structure of a computer terminal supporting a data protocol conversion method of configuration according to an embodiment of the present application. As shown in fig. 1, a computer terminal may include one or more (only one is shown in fig. 1) processors 102 (the processors 102 may include, but are not limited to, a microprocessor, a processing arrangement such as a programmable logic device) and a memory 104 for storing data, wherein the computer terminal may also include a transmission device 106 for communication functions and an input-output device 108. It will be appreciated by those skilled in the art that the configuration shown in fig. 1 is merely illustrative and is not intended to limit the configuration of the computer terminal described above. For example, the computer terminal may also include more or fewer components than shown in FIG. 1, or have a different configuration than shown in FIG. 1.

The memory 104 may be used to store computer programs, such as software programs of application software and modules, such as computer programs corresponding to the data protocol conversion method supporting configuration in the embodiment of the present application, and the processor 102 executes the computer programs stored in the memory 104 to perform various functional applications and data processing, that is, implement the above-mentioned method. Memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory remotely located relative to the processor 102, which may be connected to the computer terminal via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission device 106 is used to receive or transmit data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of a computer terminal. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, simply referred to as NIC) that can connect to other network devices through a base station to communicate with the internet. In one example, the transmission device 106 may be a Radio Frequency (RF) module, which is configured to communicate with the internet wirelessly.

In this embodiment, a method for converting a data protocol of a support configuration running on the above-mentioned computer terminal or other architecture is provided, and fig. 2 is a flowchart of a method for converting a data protocol of a support configuration according to an embodiment of the present application, as shown in fig. 2, the method includes the following steps:

step S202, receiving a first message, unpacking a corresponding data field according to a protocol format of the first message, and storing the unpacked data field in a variable pool;

step S204, according to the mapping relation of the data domains of different protocols, the corresponding data domains in the variable pool are operated and read;

step S206, packing the finally read mapping data field value into a second message according to the protocol format of the second message.

Through the steps, the messages between different protocols can be flexibly converted, and in particular, the conversion process can occur in a request system corresponding to a sending end, a target system corresponding to a receiving end or a third party between the sending end and the receiving end. In order to simultaneously satisfy the data interaction between the request system and the target system, the first message corresponding to the request system and the second message corresponding to the target system are configured, that is, the conversion from the first message to the second message is realized through the configuration parameters, so that unified compatibility among different systems is realized, which will be described in detail below.

Protocol conversion of the intersystem data interaction process is embodied as a process of protocol parsing and unpacking of a first message (which may be a request system message, respectively) and packing and encoding of a second message (which may be a target system message, respectively) in the interaction process. However, if only the first message and the second message according to different protocols are implemented by hard coding programming, the implementation is significantly heavy and inflexible, and especially for any new or modified first message and second message protocol, the re-hard coding is required, so that the efficiency is very low. In this embodiment, the whole conversion process is reasonably divided and designed, configurable interfaces are set for protocol formats of different messages, mapping relations of data fields and the like, configuration parameters are saved and called in the form of a data dictionary and the like, dynamic adjustment is supported in the later maintenance and use process, and the running coding program is not required to be updated, but only the processes of unpacking, packing and the like are coded in advance.

Specifically, in step S202, the unpacking of the first packet is based on the protocol format of the first packet, where the protocol format of the first packet may be the data domain content and the organization structure of the corresponding protocol packet defined in the form of a data dictionary, and the corresponding data domain information may be obtained from the unpacking of the first packet according to the data domain arrangement position defined in the data dictionary and stored in the variable pool. Similarly, in step S206, the second message is packaged based on the protocol format of the second message, and the protocol format of the second message may also be a data domain content and an organization structure of the corresponding protocol message defined in a data dictionary, and the corresponding data domain in the variable pool is packaged in the corresponding field of the second message according to the data domain arrangement position defined in the data dictionary. It is further understood that, for the first message and the second message of the interaction between the systems, the information data segments are actually arranged by a plurality of data fields according to a specific organization structure, and for the unpacking process, the corresponding data segments of the information data corresponding to the request system are analyzed according to the defined protocol format and the definition of the corresponding protocol format. And for the packing process, the data field information acquired from the variable pool is organized into information data segments required by the target system according to the definition of the corresponding protocol format. Therefore, the packing and unpacking process is not changed by the change of the message types, and the relevant parameters of packing and unpacking are correspondingly changed only through the configured protocol format of the corresponding message so as to adapt to the conversion of the messages of different types. It should be added that, the protocol formats of the first message and the second message may be the data domain content and the organization structure of the corresponding protocol message defined in the form of a data dictionary, that is, may be understood as the arrangement information of a plurality of data domains in the message. The data dictionary may be a pre-embedded set or sets of protocol formats containing the definitions of the message data fields, and may include protocol formats of different messages, such as XML, 8583, and the like. Furthermore, in order to adapt to new or changed message formats, the updating configuration of the data dictionary is supported, and as the data dictionary only defines the protocol format of the message, the message types supported in the whole conversion process can be changed only by configuring the related data domain content and organization structure without encoding in advance.

As shown in fig. 3, the conversion between the first message received from the request system and the second message sent from the target system is realized around the operation of the variable pool, and the basis of the definition of the variable pool memory and the basis of the package and the unpack of the message are both dependent on the configurable data dictionary. In this embodiment, the data dictionary includes a system data dictionary and an application data dictionary according to different service scenarios, as described above, the data dictionary is a data domain set organized according to a certain order, when a corresponding dependent data dictionary is selected, the corresponding data dictionary is selected according to the service attribute and type to which the related message belongs, so that the data domain content and organization structure of the corresponding message can be obtained from the corresponding data dictionary. The variable pool allocates storage space according to the protocol format corresponding to the data dictionary, the corresponding storage space can store corresponding data domain information, and under different application requirements, the dimension of the variable pool can be further defined so as to meet the storage requirement under specific application. The pre-programmed application program can operate on the variable pool through the variable pool API, such as storing the data field information extracted by the first message in the correspondingly defined storage space of the variable pool. Because of the difference of the protocol formats of the first message and the second message, the application program also needs to perform corresponding operation on the corresponding data fields in the variable pool according to the mapping relation of the data fields to further package the message, and the mapping relation of the data fields of different protocols can be configured through an input interface, which will be described in detail below.

More specifically, describing the operation of the variable pool, as shown in fig. 4, the storage space of the corresponding variable pool may be defined according to service attributes and the like, and the basis of the definition is a system data dictionary, an application data dictionary and the like. Specifically, in the step S202, when the first packet is unpacked, the data dictionary corresponding to the first packet is correspondingly used as the basis of the definition of the variable pool, and the storage space corresponding to the variable pool is arranged and generated, so that the storage memory space is provided for the data field extracted by the first packet. Preferably, when judging the specific data dictionary depending on, the corresponding data dictionary is matched according to the scene recognition key value information corresponding to the first message, the corresponding memory space is further generated according to the data domain type, the length information and the like defined by the data dictionary, and the generation of the memory space can be further defined more finely based on the dimension configuration of the variable pool. The structure of the variable pool is specifically shown in fig. 5, the variable pool can be understood as arranging all data field columns of the data dictionary corresponding to the message into a one-dimensional array in the memory according to a specified sequence, for messages in different protocol formats, the data fields are different, such as time and date, system trace audit number, agency line code and the like, the information corresponding to the configuration of the data dictionary needs to correspondingly generate variable pool definitions with different array lengths in the variable pool, in fig. 5, variable pool definition 1, variable pool definition 2 and variable pool definition 3 are shown, the space (i.e. array length) of each variable pool definition in the memory is determined by the type and length of the corresponding data field, and further the dimension of the variable pool can be selected according to specific application requirements, i.e. the memory space defined by the variable pool is the product of the length and dimension of the corresponding data field, in a default condition, the corresponding dimension is 1, so the defined memory space can store the first data field of the unpacked message, i.e. the memory generation of the variable pool can be determined by the type, the length and/or dimension of the corresponding data field. It should be added that the defined variable pool space is kept unchanged in the whole conversion process, during which the data in the space memory can be operated until the task needing conversion is finished, and the corresponding variable pool space is triggered to be released, so that the definition can be continuously used for other conversion tasks again.

As described above, the variable pool may not only generate a corresponding memory space based on the corresponding data dictionary and the information such as the dimension configuration of the variable pool, so as to store the corresponding data domain information, but further may also access the information in the variable pool through the location parameters such as the structure name, the data domain sequence number, the dimension index, and the like, and specifically operate through the variable pool API, where the corresponding operation interface shown in fig. 4 may include three types:

1. deposit data into a variable Pool (PUT), such as storing unpacked data fields into a variable pool, etc.

2. Data (GET) is read from the variable pool, such as retrieving the data fields to be packed from the variable pool, etc.

3. Variable pool content operations (UPDATE), such as calculating and updating the values of the corresponding data fields as needed.

Further, the variable pool API may operate and read the data domain information in the variable pool in combination with a data dictionary such as a system data dictionary and an application data dictionary, and accordingly, step S204 may be implemented to operate and read the corresponding data domain in the variable pool according to the mapping relationship of the data domains of different protocols. It should be noted that, although the messages of different protocols are all information data segments arranged by a plurality of data fields according to a specific organization structure, the organization structures of the same kind of data fields are not necessarily the same from message to message, for example, in the messages of different protocol formats, the same data field may be arranged at the head and the tail, so that the same data field in different messages needs to be determined through the mapping relation of the data fields, and thus, the corresponding data field in the second packaged message can be ensured to obtain the assignment from the corresponding data field in the variable pool with certainty. The following description will be made in connection with embodiments of different protocol data domain mappings defined by configuration, and the form of the data domain mappings may be represented by the following examples, but is not limited thereto. FDC8583|10|0|FDCXML|190|0 (time date), FDC8583|14|0|PBSYS|16|0 (System trace audit number), FDC8583|36|0|XMLead|2|0 (proxy line agency code), wherein FDC8583|10|0|FDCXML|190|0 (time date) is taken as an example, FDC8583, FDCXML is a corresponding structure name, i.e. a corresponding data dictionary, each structure name is followed by a data field number (such as corresponding 10, 190), and the data field number is followed by a dimension index (such as corresponding 0, 0). FDC8583|10|0|FDCXML|190|0 means that the 0-dimensional data of the 190 th domain of the FDCXML structure is assigned to the 0-dimensional data of the 10 th domain of the FDC8583 structure, namely, the data domains of the first message and the data domains of the second message to be packaged can be established with corresponding relation through the mutual data domain mapping relation. The operation on the corresponding data fields in the variable pool can be specifically that the corresponding variable pool definition is defined in the variable pool according to the type, length and/or dimension configuration of the data fields of the data dictionary corresponding to the second message, and the same data fields in the variable pool and the variable pool are subjected to corresponding assignment according to the data domain mapping relation, namely the access operation of the memory is performed according to the data domain mapping relation parameter calculation as the corresponding variable pool address, or the specific operation is that the corresponding data fields are directly determined and the corresponding data domain values are accessed. After the operation is completed on the corresponding data field, the corresponding data is finally read out for the packing process of the second message. In addition, even if the corresponding data fields are located, the data fields of the same type are different in form in the messages of different protocol formats, for example, the time in the messages of different protocol formats needs to be converted numerically, some provisions are made in twelve hours, some provisions are made in twenty-four hours, so that in the embodiment, the operation on the corresponding data fields in the variable pool further comprises the calculation conversion of the data field values.

The step S204 is to read out the mapping data field value, that is, the data field value directly corresponding to the second message obtained by the mapping relation of the data field, and then enter step S206, package the finally read mapping data field value into the second message according to the protocol format of the second message, where the process is the inverse process of the package, and has a certain similarity, and it is based on the protocol format of the second message, and the read mapping data field value is organized into corresponding data information segments, which will not be repeated herein.

As described above, in the embodiment of the present application, the unpacking, packing process, variable pool storage, reading, and operation processes are decoupled from the protocol formats of the first packet and the second packet and the mapping relations of the different protocol data domains, so that the calling and called relations between the intrinsic program and the parameter data are formed between the two, and the parameter data can be configured and updated in the use process, thereby greatly improving the flexibility of the whole data protocol conversion. Correspondingly, the mapping relation of the data fields of different protocols is configured through the input interface, and maintenance personnel can add or delete corresponding mapping relation entries according to the needs to realize updating. The unpacking and packing processes and the variable pool storage, reading and operation processes are set through the programming in advance, so that the deployability is ensured, and the workload of maintenance operation is reduced. Furthermore, in order to improve the developability of the whole data protocol conversion, the rewriting interfaces are respectively set for the unpacking pretreatment, the unpacking post-treatment, the packing pretreatment, the packing post-treatment and the variable pool storage, reading and operation processes so as to provide the developer with the function expansion of self definition. The developer can reset or update the existing process through the rewriting interface according to the actual requirement, so that the solidified program can be ensured to have corresponding expansion performance.

From the description of the above embodiments, it will be clear to a person skilled in the art that the method according to the above embodiments may be implemented by means of software plus the necessary general hardware platform, but of course also by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method according to the embodiments of the present application.

The embodiment also provides a data protocol conversion device supporting configuration, which is used for implementing the foregoing embodiments and preferred embodiments, and is not described in detail. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. While the means described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.

According to another embodiment of the present application, there is also provided a data protocol conversion apparatus supporting configuration. Fig. 6 is a block diagram of a data protocol conversion apparatus supporting configuration according to an embodiment of the present application, as shown in fig. 6, including:

the unpacking module 22 is configured to receive a first packet, unpack a corresponding data field according to a protocol format of the first packet, and store the unpacked data field in a variable pool;

the processing module 24 is configured to operate and read the corresponding data fields in the variable pool according to the mapping relationships of the data fields of different protocols;

and the packing module 26 is configured to pack the finally read mapping data field value into a second message according to the protocol format of the second message.

The packet between different protocols can be flexibly converted by the cooperation of the unpacking module 22, the processing module 24 and the packing module 26. In order to simultaneously satisfy the data interaction between the request system and the target system, the unpacking module 22 mainly configures a first message corresponding to the request system to extract a corresponding data field, the processing module 24 mainly configures an operation and reading and packing module 26 for configuring a data field corresponding to the first message in a variable pool, and mainly configures and packs a second message corresponding to the target system according to reading of the variable pool, and the work between the whole modules realizes the conversion from the first message to the second message through configuration parameters, so that unified compatibility among different systems is realized.

In an exemplary embodiment, the system further comprises an input module, wherein the mapping relation of the different protocol data domains is configured by the input module

In an exemplary embodiment, the system further comprises an expansion module, wherein the expansion module is used for respectively setting a rewriting interface for unpacking pretreatment, unpacking post-treatment, packing pretreatment, packing post-treatment and variable pool storage, reading and operation processes so as to provide a developer with custom function expansion.

Further, the specific embodiment of the data protocol conversion device supporting configuration may refer to the specific embodiment of the data protocol conversion method supporting configuration.

It should be noted that each of the above modules may be implemented by software or hardware, and for the latter, it may be implemented by, but not limited to: the modules are all located in the same processor; alternatively, the above modules may be located in different processors in any combination.

Embodiments of the present application also provide a computer readable storage medium having a computer program stored therein, wherein the computer program is arranged to perform the steps of any of the method embodiments described above when run.

In one exemplary embodiment, the computer readable storage medium may include, but is not limited to: a usb disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing a computer program.

An embodiment of the application also provides an electronic device comprising a memory having stored therein a computer program and a processor arranged to run the computer program to perform the steps of any of the method embodiments described above.

In an exemplary embodiment, the electronic apparatus may further include a transmission device connected to the processor, and an input/output device connected to the processor.

Specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the exemplary implementation, and this embodiment is not described herein.

It will be appreciated by those skilled in the art that the modules or steps of the application described above may be implemented in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, they may be implemented in program code executable by computing devices, so that they may be stored in a storage device for execution by computing devices, and in some cases, the steps shown or described may be performed in a different order than that shown or described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple modules or steps of them may be fabricated into a single integrated circuit module. Thus, the present application is not limited to any specific combination of hardware and software.

The above description is only of the preferred embodiments of the present application and is not intended to limit the present application, but various modifications and variations can be made to the present application by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the principle of the present application should be included in the protection scope of the present application.

Claims

1. A data protocol conversion method supporting configuration, comprising the steps of:

2. The method for converting data protocol supporting configuration according to claim 1, wherein the mapping relation of different protocol data domains is configured through an input interface.

3. The method according to claim 1, wherein the unpacking, packing and variable pool storing, reading and operating processes are set by programming in advance.

4. The method according to claim 1, wherein the rewriting interfaces are set for unpacking pre-processing, unpacking post-processing, packing pre-processing, packing post-processing, variable pool storing, reading and operating processes, respectively, so as to provide a developer with a custom function extension.

5. The configuration-enabled data protocol conversion method according to claim 1, wherein the memory generation of the variable pool is determined by the type, length and/or dimension of the corresponding data field.

6. The method for supporting configuration according to claim 1, wherein the protocol format of the first message and the protocol format of the second message define the data domain content and the organization structure of the corresponding protocol message in the form of a data dictionary.

7. A data protocol conversion apparatus supporting configuration, comprising:

8. The configuration-enabled data protocol conversion device according to claim 7, further comprising an input module through which the mapping relation of the different protocol data domains is configured.

9. The configuration-enabled data protocol conversion device according to claim 7, wherein the memory generation of the variable pool is determined by the type, length and/or dimension of the corresponding data field.

10. The data protocol conversion device supporting configuration according to claim 7, wherein the protocol format of the first message and the protocol format of the second message define the data domain content and the organization structure of the corresponding protocol message in the form of a data dictionary.

11. A computer readable storage medium, characterized in that a computer program is stored in the computer readable storage medium, wherein the computer program, when being executed by a processor, implements the steps of the method according to any of the claims 1 to 6.

12. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method of any one of claims 1 to 6 when the computer program is executed.