CN110995843A - Data transmission method and device, electronic equipment and readable storage medium - Google Patents
Data transmission method and device, electronic equipment and readable storage medium Download PDFInfo
- Publication number
- CN110995843A CN110995843A CN201911241939.6A CN201911241939A CN110995843A CN 110995843 A CN110995843 A CN 110995843A CN 201911241939 A CN201911241939 A CN 201911241939A CN 110995843 A CN110995843 A CN 110995843A
- Authority
- CN
- China
- Prior art keywords
- data
- transaction
- data format
- client
- format
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/563—Data redirection of data network streams
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
Abstract
The application provides a data transmission method, a data transmission device, an electronic device and a readable storage medium, wherein the data transmission method comprises the following steps: acquiring transaction data in a first data format of a client and a data conversion rule; the transaction data comprises client identity marks; converting the transaction data in the first data format into transaction data in a second data format to generate a first transaction result in the second data format according to the transaction data in the second data format; converting the first transaction result in the second data format into a second transaction result in the first data format according to the data conversion rule; and sending the second transaction result in the first data format to the client corresponding to the client identity. According to the data format conversion method and device, the data format conversion between the local server and the client can be achieved by configuring the data conversion rules, the interface butt joint is avoided when data is transmitted every time, and the development amount is reduced on a large scale.
Description
Technical Field
The present application relates to the field of data transmission technologies, and in particular, to a data transmission method and apparatus, an electronic device, and a readable storage medium.
Background
With the development of the internet, the cross-system information transmission is widely regarded as a basic means for realizing information interaction. At present, more and more enterprises carry out cross-system docking to realize cross-company information transmission.
In the prior art, different systems have respective data transmission modes and data formats, and different docking modes are generally required to be adapted according to interface protocol standards of different systems. When a new system needs to be docked, a new interface needs to be developed, which not only needs to invest a large amount of development manpower, but also needs high development cost and operation and maintenance cost.
Disclosure of Invention
In view of the above, an object of the present application is to provide a data transmission method, an apparatus, an electronic device and a readable storage medium, so as to improve the data transmission method.
In a first aspect, an embodiment of the present application provides a data transmission method, including:
acquiring transaction data in a first data format of a client and a data conversion rule; the transaction data comprises client identity identification;
converting the transaction data in the first data format into transaction data in a second data format to generate a first transaction result in the second data format according to the transaction data in the second data format;
converting the first transaction result in the second data format into a second transaction result in the first data format according to the data conversion rule;
and sending the second transaction result in the first data format to the client corresponding to the client identity.
In combination with the first aspect, the present examples provide a first possible implementation manner of the first aspect, where,
the transaction data comprises transaction parameter fields and transaction contents corresponding to the transaction parameter fields;
the converting the transaction data in the first data format into transaction data in a second data format includes:
converting the transaction content in the first data format into transaction content in a second data format;
and converting the transaction parameter field of the first data format corresponding to the transaction content of the second data format into the transaction parameter field of the second data format.
With reference to the first aspect, an embodiment of the present application provides a second possible implementation manner of the first aspect, where the obtaining a data transformation rule of a client includes:
and receiving the data conversion rule sent by the client in the form of the mail.
With reference to the first aspect, an embodiment of the present application provides a third possible implementation manner of the first aspect, where the obtaining a data transformation rule of a client further includes:
sending a request for acquiring a data conversion rule to a client;
and receiving the data conversion rule sent by the client aiming at the request for obtaining the data conversion rule.
With reference to the first aspect, an embodiment of the present application provides a fourth possible implementation manner of the first aspect, where before acquiring the transaction data in the first data format and the data conversion rule of the client, the method includes:
and acquiring the encryption mode of the client.
With reference to the fourth possible implementation manner of the first aspect, an embodiment of the present application provides a fifth possible implementation manner of the first aspect, where the encryption manner includes at least one of: digital certificate encryption, hypertext transfer security protocol encryption, key encryption, symmetric encryption, asymmetric encryption, and hybrid encryption.
With reference to the fourth possible implementation manner of the first aspect, an embodiment of the present application provides a sixth possible implementation manner of the first aspect, where sending the second transaction result in the first data format to the client corresponding to the client identifier includes:
and sending the second transaction result in the first data format to the client corresponding to the client identity according to the encryption mode.
In a second aspect, an embodiment of the present application further provides a data transmission apparatus, including:
the first acquisition module is used for acquiring the transaction data in the first data format of the client and the data conversion rule; the transaction data comprises client identity identification;
the first conversion module is used for converting the transaction data in the first data format into transaction data in a second data format so as to generate a first transaction result in the second data format according to the transaction data in the second data format;
the second conversion module is used for converting the first transaction result in the second data format into a second transaction result in the first data format according to the data conversion rule;
and the sending module is used for sending the second transaction result in the first data format to the client corresponding to the client identity.
In a third aspect, an embodiment of the present application further provides an electronic device, including: a processor, a memory and a bus, the memory storing machine-readable instructions executable by the processor, the processor and the memory communicating via the bus when the electronic device is running, the machine-readable instructions being executable by the processor to perform the steps of any one of the possible implementations of the first aspect.
In a fourth aspect, this application further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and the computer program is executed by a processor to perform the steps in any one of the possible implementation manners of the first aspect.
The data transmission method provided by the embodiment of the application comprises the following steps: acquiring transaction data in a first data format of a client and a data conversion rule; the transaction data comprises client identity marks; converting the transaction data in the first data format into transaction data in a second data format to generate a first transaction result in the second data format according to the transaction data in the second data format; converting the first transaction result in the second data format into a second transaction result in the first data format according to the data conversion rule; and sending the second transaction result in the first data format to the client corresponding to the client identity. According to the data format conversion method and device, the data format conversion of the transaction data between the local server and the client can be achieved through the configured data conversion rule, the interface butt joint is avoided when the data is transmitted every time, and the development amount is reduced on a large scale.
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 illustrates an application scenario of a data transmission method provided in an embodiment of the present application;
fig. 2 is a schematic flowchart illustrating a data transmission method according to an embodiment of the present application;
fig. 3 is a schematic flow chart of a data transmission apparatus provided in an embodiment of the present application;
fig. 4 shows a schematic structural diagram of an electronic device provided in an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all the embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present application without making any creative effort, shall fall within the protection scope of the present application.
In view of the current need for interface protocol standards for different systems, new interfaces need to be developed. Based on this, embodiments of the present application provide a data transmission method, an apparatus, an electronic device, and a readable storage medium, which are described below by way of embodiments.
For the convenience of understanding the present embodiment, a detailed description will be first given of a data transmission method disclosed in the embodiments of the present application.
The data transmission method provided by the application can be applied to the application scene diagram of the data transmission method shown in fig. 1, the local system can be connected with a plurality of remote systems, and data transmission is performed between the local system and the remote systems through an achieved data transmission protocol. The data transmission method provided by the application is mainly applied to the insurance industry or the public security industry, and the data transmission process related to transaction data is within the protection scope claimed by the application.
As shown in fig. 2, a flow chart of a data transmission method includes the following steps:
s201: acquiring transaction data in a first data format of a client and a data conversion rule; the transaction data includes a client identity.
S202: and converting the transaction data in the first data format into the transaction data in the second data format to generate a first transaction result in the second data format according to the transaction data in the second data format.
S203: and converting the first transaction result in the second data format into a second transaction result in the first data format according to the data conversion rule.
S204: and sending the second transaction result in the first data format to the client corresponding to the client identity.
In the above steps, the execution subject is a server in the local system, that is, the local server, and before the above steps are executed, the local system and the remote system need to perform a handshake operation first, mainly configuring the transmission mode. Specifically, according to the configuration file, an Internet Protocol (Internet Protocol, abbreviated as network Protocol) address, a context root, an interaction mode (such as JSON (JavaScript Object Notation), XML, etc.), an encryption mode, and a transmission mode of the remote system may be configured by using XML (Extensible Markup Language), so that the local system and the remote system may perform data transmission according to the configuration file.
For example, the configuration file may configure information such as a return transaction, an address of an insurance company, an interface type, an interface transmission parameter, an encryption address, a transmission message encoding format, a return message encoding format, and the like.
In step S201, the client refers to a client in a remote system, the client may include, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the server may be implemented by an independent server or a server set composed of a plurality of servers.
In this step, the server in the local system obtains the transaction data in the first data format and the data conversion rules from the client in the remote system. It should be noted that, unless otherwise specified, the clients described below refer to clients in a remote system.
In the specific implementation, because the data formats in the local system and the remote system are different, in order to meet the service requirement, after the local system receives the data sent by the remote system, the data format in the remote system needs to be converted into the data format in the local system; before the local system sends data to the remote system, the data format in the local system needs to be converted into the data format in the remote system. Therefore, before the local system sends data to the remote system, the local system first needs to obtain the data conversion rule from the client in the remote system.
The data conversion rule is used for converting the data to be converted into the target format data to be executed. Here, the acquired data conversion rule of the client refers to a data conversion rule for converting data to be transmitted in the local system into data in a target format in the remote system.
The local system also stores the data conversion rule for converting the data to be converted in the remote system into the target format data in the local system.
The data conversion rules in the local system and the remote system are data conversion rules specified by a data transmission protocol achieved by the two parties, and the non-standard data stream of the opposite party can be converted into the local standard data stream through the data conversion rules, so that the data transmission is realized better locally.
In a specific implementation, the following two ways may be used to obtain the data transformation rule of the client:
in the first mode, a client sends a data conversion rule to a local server offline;
in the second mode, the local server obtains the data conversion rule from the client on line.
In the first mode, the client may send the data conversion rule to the local server in the form of an email, which may reduce network resources occupied during data transmission, but needs to send the data conversion rule offline. In the second mode, the local server sends a request for obtaining the data conversion rule to the client, the request for obtaining the data conversion rule can carry an identity of the local server, and after receiving the request for obtaining the data conversion rule sent by the local server, the client can send the data conversion rule to the local server according to the identity of the local server.
It should be noted here that the obtaining of the data conversion rule may be completed before the obtaining of the transaction data in the first data format of the client. And after the local server acquires the data conversion rule of the client, storing the data conversion rule into a local database. After the local server acquires the transaction data of the client in the subsequent process, the data format of the acquired transaction data of the client can be converted according to the stored data conversion rule, and the data conversion rule does not need to be acquired again.
In a specific implementation, the data conversion rule may include a client identity, where the client identity is used to identify the client, and the local server may determine the corresponding data conversion rule according to the client identity.
The transaction data may refer to product identification, transaction type, transaction time, user information to initiate a transaction request, client information, transaction request code, transaction amount, transaction party, etc. information related to the transaction product. The transaction data may specifically include transaction content and transaction parameter fields corresponding to the transaction content.
The product identification refers to information such as a product number and a product code. The product identification is mainly used for uniquely identifying the product. The transaction type refers to the type of the initiated transaction, and taking insurance products as an example, the transaction type can be premium trial calculation, underwriting and the like.
For example, information such as the information on the basis of the applicant is included in the premium trial transaction of an insurance product in a certain insurance company. For example, the applicant's basic information includes a plurality of transaction parameter fields such as name, age, gender, etc. The trade parameter field corresponds to specific trade contents, such as Zhang III for the first name, age 35, sex, etc.
When the first data format used by the client is different from the data format used by the local system, the transaction data in the first data format may be referred to as transaction data in a non-standard data format relative to a standard data format defaulted by the system in the local server.
In a specific implementation, the transaction data may also include a client identity, specifically, a client IP address. When the local server obtains the transaction data in the first data format of the client, the corresponding data conversion rule can be determined according to the client identity.
When acquiring transaction data in a first data format of a client, a local server may send a transaction data acquisition request carrying a local identity to the client, and the client sends the transaction data in the first data format carrying the client identity to the local server according to the local identity; or the client actively sends the transaction data in the first data format containing the client identity to the local server.
In step S202, the local server may perform two conversions on the transaction data in the first data format to convert the transaction data into the transaction data in the second data format, and specifically, step S202 may be performed as follows:
the method comprises the following steps: converting the transaction content in the first data format into the transaction content in the second data format;
step two: and converting the transaction parameter field of the first data format corresponding to the transaction content of the second data format into the transaction parameter field of the second data format.
In step one, the second data format refers to a data format used and required by the local system. I.e. the local system can only process data in the second data format.
Here, in general, the transaction contents in the first data format may be converted into the transaction contents in the second data format using an XSL (eXtensible Stylesheet Language) file. Specifically, the XSL file is used for mapping the transaction content in the first data format into the second data format, namely, the transaction content in the first data format is corresponding to the second data format aiming at fields with the same meaning. For example, at the client, the transaction content in the first data format is an English-language-form date, at the local server, the transaction content in the second data format is a Chinese-language-form date, and the date have the same meaning, so that the transaction content date in the first data format is corresponding to the transaction content date in the second data format, that is, the transaction content date in the first data format is converted into the transaction content date in the second data format.
In a specific implementation, other language files may also be used to convert the transaction content in the first data format into the transaction content in the second data format, which is not limited herein.
In the second step, after the transaction content in the first data format is converted into the transaction content in the second data format, the format of the transaction parameter field corresponding to the transaction content in the second data format also needs to be converted.
Specifically, information such as codes, date formats, null strings, etc. in the transaction parameter field may be converted.
For example, if the data format of the transaction parameter field corresponding to the date of the converted transaction content in the second data format is 2019-1-1, that is, the transaction parameter field in the first data format is 2019-1-1, and the transaction parameter field in the second data format is 2019.01.01, the transaction parameter field in the first data format 2019-1-1 can be converted into the transaction parameter field 2019.01.01 in the second data format.
Then, the local server may assemble the transaction content in the second data format with the transaction parameter field in the second data format and generate transaction data in the second data format, that is, generate a standard message.
Through the two conversion processes, the transaction content is converted first, and then the transaction parameter field is converted, so that the workload can be reduced, and the conversion efficiency can be improved.
The generated transaction data in the second data format, that is, the default standard message of the system in the local server, may be processed by the local server to generate the first transaction result. In particular implementations, transaction data in the second data format may be processed according to particular business requirements.
The first transaction result may be information such as whether the transaction is successful, whether the message is acknowledged, and the transaction amount. The local server needs to send the transaction result after the transaction data is transmitted to the client.
However, the first transaction result is data in the second data format, that is, the default data format of the system in the local server, and the client cannot recognize the data in the second data format, so in step S203, the first transaction result in the second data format needs to be converted into the second transaction result in the first data format.
In step S203, here, the XSL file may be used to convert the result content in the second data format in the first transaction result into the result content in the first data format according to the pre-stored data conversion format of the client; and then converting the transaction result parameter field of the second data format corresponding to the result content of the first data format into the transaction result parameter field of the first data format. Finally, the first transaction result in the second data format is converted into a second transaction result in the first data format.
The local server assembles the transaction content in the first data format and the transaction parameter field in the first data format and generates a non-standard message.
In step S204, the local server determines a corresponding client according to the client id, and then sends the second transaction result in the first data format to the client.
In the process of sending the second transaction result in the first data format to the client, the non-standard message may be encrypted according to an encryption method agreed by the local server and the client, and specifically, the encryption method may include the following several methods: digital certificate encryption, hypertext transfer security protocol encryption, key encryption, symmetric encryption, asymmetric encryption, and hybrid encryption.
In general, the local server encrypts the non-standard message by using one of the encryption methods. In a specific implementation, when other encryption modes are required for encryption, the re-development can be carried out.
According to the data transmission method, the data format conversion of the transaction data between the local server and the client is realized by using the configured data conversion rule, the interface butt joint is avoided during each data transmission, and the development amount is reduced on a large scale.
Based on the same technical concept, embodiments of the present application further provide a data transmission device, an electronic device, a computer-readable storage medium, and the like, which can be specifically referred to in the following embodiments.
Fig. 3 is a block diagram illustrating a data transmission apparatus according to some embodiments of the present application, which implements functions corresponding to the above-described steps of performing a data transmission method on a terminal device. The apparatus may be understood as a component of a server including a processor, which is capable of implementing the above-mentioned data transmission method, as shown in fig. 3, the data transmission apparatus may include:
a first obtaining module 301, configured to obtain transaction data in a first data format of a client and a data conversion rule; the transaction data comprises client identity identification;
a first conversion module 302, configured to convert the transaction data in the first data format into transaction data in a second data format, so as to generate a first transaction result in the second data format according to the transaction data in the second data format;
a second conversion module 303, configured to convert the first transaction result in the second data format into a second transaction result in the first data format according to the data conversion rule;
a sending module 304, configured to send the second transaction result in the first data format to the client corresponding to the client identifier.
The first conversion module 302 further includes:
the first sub-conversion module is used for converting the transaction content in the first data format into the transaction content in the second data format;
and the second sub-conversion module is used for converting the transaction parameter field of the first data format corresponding to the transaction content of the second data format into the transaction parameter field of the second data format.
The first obtaining module 301 further includes:
the first receiving module is used for receiving the data conversion rule sent by the client in the form of the mail.
The first obtaining module 301 further includes:
the sub-sending module is used for sending a request for acquiring the data conversion rule to the client;
and the second receiving module is used for receiving the data conversion rule sent by the client aiming at the request for obtaining the data conversion rule.
The data transmission apparatus may include:
and the second acquisition module is used for acquiring the encryption mode of the client.
The sending module 304, a sub-sending module, is configured to send the second transaction result in the first data format to the client corresponding to the client id according to the encryption manner.
In a specific implementation, the encryption mode includes at least one of the following: digital certificate encryption, hypertext transfer security protocol encryption, key encryption, symmetric encryption, asymmetric encryption, and hybrid encryption.
As shown in fig. 4, which is a schematic structural diagram of an electronic device 400 provided in an embodiment of the present application, the electronic device 400 includes: at least one processor 401, at least one network interface 404 and at least one user interface 403, memory 405, at least one communication bus 402. A communication bus 402 is used to enable connective communication between these components. The user interface 403 includes a display (e.g., a touch screen), a keyboard, or a pointing device (e.g., a touch pad or touch screen, etc.).
In some embodiments, memory 405 stores the following elements, executable modules or data structures, or a subset thereof, or an expanded set thereof:
an operating system 4051, which contains various system programs, for implementing various basic services and processing hardware-based tasks;
the application 4052 includes various applications for implementing various application services.
In an embodiment of the present application, processor 401, by invoking programs or instructions stored by memory 405, is configured to:
acquiring transaction data in a first data format of a client and a data conversion rule; the transaction data comprises client identity identification;
converting the transaction data in the first data format into transaction data in a second data format to generate a first transaction result in the second data format according to the transaction data in the second data format;
converting the first transaction result in the second data format into a second transaction result in the first data format according to the data conversion rule;
and sending the second transaction result in the first data format to the client corresponding to the client identity.
The processor 401 is further configured to:
converting the transaction content in the first data format into transaction content in a second data format;
and converting the transaction parameter field of the first data format corresponding to the transaction content of the second data format into the transaction parameter field of the second data format.
The processor 401 is further configured to:
and receiving the data conversion rule sent by the client in the form of the mail.
The processor 401 is further configured to:
sending a request for acquiring a data conversion rule to a client;
and receiving the data conversion rule sent by the client aiming at the request for obtaining the data conversion rule.
The processor 401 is further configured to:
and acquiring the encryption mode of the client.
The processor 401 is further configured to:
and sending the second transaction result in the first data format to the client corresponding to the client identity according to the encryption mode.
In a specific implementation, the encryption mode includes at least one of the following: digital certificate encryption, hypertext transfer security protocol encryption, key encryption, symmetric encryption, asymmetric encryption, and hybrid encryption.
The computer program product for performing the data transmission method provided in the embodiment of the present application includes a computer-readable storage medium storing a nonvolatile program code executable by a processor, where instructions included in the program code may be used to execute the method described in the foregoing method embodiment, and specific implementation may refer to the method embodiment, and is not described herein again.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a non-volatile computer-readable storage medium executable by a processor. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
Finally, it should be noted that: the above-mentioned embodiments are only specific embodiments of the present application, and are used for illustrating the technical solutions of the present application, but not limiting the same, and the scope of the present application is not limited thereto, and although the present application is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope disclosed in the present application; such modifications, changes or substitutions do not depart from the spirit and scope of the exemplary embodiments of the present application, and are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A method of data transmission, comprising:
acquiring transaction data in a first data format of a client and a data conversion rule; the transaction data comprises client identity identification;
converting the transaction data in the first data format into transaction data in a second data format to generate a first transaction result in the second data format according to the transaction data in the second data format;
converting the first transaction result in the second data format into a second transaction result in the first data format according to the data conversion rule;
and sending the second transaction result in the first data format to the client corresponding to the client identity.
2. The data transmission method according to claim 1, wherein the transaction data comprises transaction parameter fields and transaction contents corresponding to the transaction parameter fields;
the converting the transaction data in the first data format into transaction data in a second data format includes:
converting the transaction content in the first data format into transaction content in a second data format;
and converting the transaction parameter field of the first data format corresponding to the transaction content of the second data format into the transaction parameter field of the second data format.
3. The data transmission method according to claim 1, wherein the obtaining of the data conversion rule of the client comprises:
and receiving the data conversion rule sent by the client in the form of the mail.
4. The data transmission method according to claim 1, wherein the obtaining the data conversion rule of the client further comprises:
sending a request for acquiring a data conversion rule to a client;
and receiving the data conversion rule sent by the client aiming at the request for obtaining the data conversion rule.
5. The data transmission method according to claim 1, before obtaining the transaction data in the first data format of the client and the data conversion rule, comprising:
and acquiring the encryption mode of the client.
6. The data transmission method according to claim 5, wherein the encryption mode comprises at least one of the following: digital certificate encryption, hypertext transfer security protocol encryption, key encryption, symmetric encryption, asymmetric encryption, and hybrid encryption.
7. The data transmission method according to claim 5, wherein the sending the second transaction result in the first data format to the client corresponding to the client id includes:
and sending the second transaction result in the first data format to the client corresponding to the client identity according to the encryption mode.
8. A data transmission apparatus, comprising:
the first acquisition module is used for acquiring the transaction data in the first data format of the client and the data conversion rule; the transaction data comprises client identity identification;
the first conversion module is used for converting the transaction data in the first data format into transaction data in a second data format so as to generate a first transaction result in the second data format according to the transaction data in the second data format;
the second conversion module is used for converting the first transaction result in the second data format into a second transaction result in the first data format according to the data conversion rule;
and the sending module is used for sending the second transaction result in the first data format to the client corresponding to the client identity.
9. An electronic device, comprising: a processor, a memory and a bus, the memory storing machine-readable instructions executable by the processor, the processor and the memory communicating over the bus when the electronic device is operating, the machine-readable instructions when executed by the processor performing the steps of the data transmission method according to any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, performs the steps of the data transmission method according to one of the claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911241939.6A CN110995843A (en) | 2019-12-06 | 2019-12-06 | Data transmission method and device, electronic equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911241939.6A CN110995843A (en) | 2019-12-06 | 2019-12-06 | Data transmission method and device, electronic equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110995843A true CN110995843A (en) | 2020-04-10 |
Family
ID=70090742
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911241939.6A Pending CN110995843A (en) | 2019-12-06 | 2019-12-06 | Data transmission method and device, electronic equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110995843A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112184230A (en) * | 2020-10-14 | 2021-01-05 | 深圳壹账通智能科技有限公司 | Transaction data processing method, system, device and storage medium based on block chain |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101447862A (en) * | 2008-10-31 | 2009-06-03 | 神州数码金程（北京）科技有限公司 | Security exchange system and security exchange method thereof |
| US20130311546A1 (en) * | 2012-05-21 | 2013-11-21 | Martin Fischer | Parameter driven data format conversion in client/server architectures |
| CN109344183A (en) * | 2018-01-30 | 2019-02-15 | 深圳壹账通智能科技有限公司 | Data interactive method, device, computer equipment and storage medium |
| CN109413154A (en) * | 2018-09-26 | 2019-03-01 | 平安普惠企业管理有限公司 | Conversion method of data format, device, computer equipment and storage medium |
| CN109829708A (en) * | 2019-02-28 | 2019-05-31 | 中国银联股份有限公司 | A kind of transaction processing system |
| CN110188558A (en) * | 2019-05-29 | 2019-08-30 | 深圳市元征科技股份有限公司 | A kind of data processing method and relevant device |
| CN110263016A (en) * | 2019-05-20 | 2019-09-20 | 平安普惠企业管理有限公司 | Data processing method, terminal device and computer storage medium |
-
2019
- 2019-12-06 CN CN201911241939.6A patent/CN110995843A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101447862A (en) * | 2008-10-31 | 2009-06-03 | 神州数码金程（北京）科技有限公司 | Security exchange system and security exchange method thereof |
| US20130311546A1 (en) * | 2012-05-21 | 2013-11-21 | Martin Fischer | Parameter driven data format conversion in client/server architectures |
| CN109344183A (en) * | 2018-01-30 | 2019-02-15 | 深圳壹账通智能科技有限公司 | Data interactive method, device, computer equipment and storage medium |
| CN109413154A (en) * | 2018-09-26 | 2019-03-01 | 平安普惠企业管理有限公司 | Conversion method of data format, device, computer equipment and storage medium |
| CN109829708A (en) * | 2019-02-28 | 2019-05-31 | 中国银联股份有限公司 | A kind of transaction processing system |
| CN110263016A (en) * | 2019-05-20 | 2019-09-20 | 平安普惠企业管理有限公司 | Data processing method, terminal device and computer storage medium |
| CN110188558A (en) * | 2019-05-29 | 2019-08-30 | 深圳市元征科技股份有限公司 | A kind of data processing method and relevant device |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112184230A (en) * | 2020-10-14 | 2021-01-05 | 深圳壹账通智能科技有限公司 | Transaction data processing method, system, device and storage medium based on block chain |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110555299B (en) | Electronic contract signing and storing method and device, computer equipment and storage medium | |
| CN112367164B (en) | Service request processing method and device, computer equipment and storage medium | |
| CN110838071B (en) | Policy data processing method, device and server | |
| CN112184367A (en) | Order processing method and device | |
| AU2014315494B2 (en) | Automatically generating certification documents | |
| CN112116474B (en) | Verification method and device for electronic contract, electronic equipment and storage medium | |
| CN111988418B (en) | Data processing method, device, equipment and computer readable storage medium | |
| CN109086592A (en) | Method, server and the system of user information and account information binding | |
| CN108052550B (en) | Annuity data receiving method and device, computer equipment and storage medium | |
| CN107240021B (en) | Insurance information conversion method and device | |
| CN110995843A (en) | Data transmission method and device, electronic equipment and readable storage medium | |
| CN111324582B (en) | Visual backtracking processing method and device for business processing behaviors | |
| CN111614762A (en) | Electronic data exchange system and apparatus comprising an electronic data exchange system | |
| CN114036364B (en) | Method, apparatus, device, medium, and system for identifying crawlers | |
| CN115361376A (en) | Government affair file uploading method and device, electronic equipment and storage medium | |
| CN111984616B (en) | Method, device and system for updating shared file | |
| CN114648775A (en) | Method and device for collecting electronic invoice based on mail | |
| CN113706299A (en) | Data processing method and device, electronic equipment and medium | |
| CN113641359A (en) | Data processing method and device | |
| CN113761566A (en) | Data processing method and device | |
| CN110189115B (en) | Transaction channel access method and device and electronic equipment | |
| CN110175305B (en) | Data processing method, data processing device, computer equipment and storage medium | |
| CN114448703B (en) | Request processing method, request processing device, electronic equipment and storage medium | |
| CN116166736B (en) | Block chain data uplink method, device and medium based on application program interface | |
| CN115242631B (en) | Message processing method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200410 |